EXTENDED SICK Sample Clauses

EXTENDED SICK. 23-13 An employee with one or more years of University service and a fifty percent or greater appointment is eligible for extended sick for the employee’s own illness or injury as outlined in the following schedule. The one year of University service must be attained as of the last day worked. If an employee is absent for a reason recognized by this Article at the employee's one-year anniversary, the employee will not be eligible for extended sick until the employee returns to work. Maximum Hours of University Seniority Extended Sick One through two years 192 Over two through three years 288 Over three through four years 384 Over four through five years 480 Over five through six years 576 Over six through seven years 672 Over seven through eight years 768 Over eight through nine years 864 Over nine years 960 23-14 Extended sick, short-term sick, vacation, and excused time without pay are used as follows for a continuous absence for the employee’s own illness or injury beginning on the first, full workday of the continuous absence. If the first workday of a continuous absence includes a period of work, i.e., the employee left work early due to illness or injury, the period of absence on that day will be covered by short-term sick, vacation or excused time without pay. EXPLANATION OF TIME USAGE- with Dr. Note per contract Workday1 Short-term sick followed by vacation followed by excused time without pay Extended sick2 1 84 104 06 06 3 4 5 4 5 4 4 5 4 5 5 4 5 4 5 6 4 5 4 5 7 4 5 4 5 8 4 2.5 4 7.5 9 2 2.5 6 7.5 10 2 2.5 6 7.5 11 2 2.5 6 7.5 12 2 2.5 6 7.5 13 2 2.5 6 7.5 1 ”Workday” does not include holidays, season days or the employee’s regular days off (RDO).
AutoNDA by SimpleDocs
EXTENDED SICK. 23-12 An employee with two or more years of University service and a fifty percent or greater appointment is eligible for extended sick for the employee’s own illness or injury as outlined in the following schedule. The two years of University service must be attained as of the last day worked. If an employee is absent for a reason recognized by this Article at the employee's two-year anniversary, the employee will not be eligible for extended sick until the employee returns to work. Maximum Hours of University Seniority Extended Sick One through two years 192 Over two through three years 288 Over three through four years 384 Over four through five years 480 Over five through six years 576 Over six through seven years 672 Over seven through eight years 768 Over eight through nine years 864 Over nine years 960 SECTION G ABUSE SICK TIME MANAGEMENT 23-22 It is understood that the parties do not condone any abuse of this Article. W here there is cause to suspect an employee’s absence is for reasons that are not legitimate, corrective action may be initiated including requiring a doctor’s note, sick time counseling and/or disciplinary action. W here an employee’s unscheduled sick time usage, or sick time usage that is unsupported by a physician’s statement, raises concern of possible sick time misuse, notice will be given to the President and a Sick Time Conference may be scheduled with the employee. Any sick time conference will be initiated through the appropriate Human Resources representative. Other attendees will include the President, other Union representatives identified by the President, a representative of University Human Resources, and unit management representatives as determined by the University. Other University resource personnel may also attend.
EXTENDED SICK. 23-13 An employee with one or more years of University service and a fifty percent or greater appointment is eligible for extended sick for the employee’s own illness or injury as outlined in the following schedule. The one year of University service must be attained as of the last day worked. If an employee is absent for a reason recognized by this Article at the employee's one-year anniversary, the employee will not be eligible employee returns to work. f extended sick until the University Seniority Maximum Hours of Extended Sick One through two years 192 Over two through three years 288 Over three through four years 384 Over four through five years 480 Over five through six years 576 Over six through seven years 672 Over seven through eight years 768 Over eight through nine years 864 Over nine years 960 23-14 Extended sick, short-term sick, vacation, and excused time without pay are used as follows for a continuous absence for the employee’s own illness or injury beginning on the first, full workday of the continuous absence. If the first workday of a continuous absence includes a period of work, i.e., the employee left work early due to illness or injury, the period of absence on that day will be covered by short-term sick, vacation or excused time without pay. 06 5 5 5 5 5 5

Related to EXTENDED SICK

  • Extended Sick Leave When sick leave extends for more than 25 consecutive working days, the appointing authority shall initiate the following procedure:

  • Extended Leaves Extended leaves of absence of at least three (3) but not more than five (5) years may be granted in accordance with Minnesota Statutes § 136F.43. Notwithstanding any other section of this Agreement, retention and accrual of all rights and benefits for faculty on extended leave shall be governed by Minnesota Statutes § 136F.43. Faculty members shall be returned to the unit in accordance with Article 29, Section B, Subd. 1, and shall be returned to the salary schedule at the step at which they were placed when they left the unit, with accommodation for general increases in the indicated step. If the faculty member’s service to the university in the year the faculty member left the unit qualified for an increase in the succeeding year, then the faculty member shall be entitled to that increase upon return to the unit. Seniority shall not accrue during the years faculty members are on extended leave.

  • Extended Leave Extended leaves of absence of at least three (3) but not more than five (5) years may be granted in accordance with Minnesota law. Notwithstanding any other provision of this Agreement, retention and accrual of all rights and benefits for ASF Members on extended leave shall be governed by Minnesota Statute Section 136F.43.

  • Extended School Year For the extended school year program for 44 students receiving a 1 or 2 score on the state mandated assessments, a listing 45 of anticipated openings with instructions for submitting applications for 46 such openings, including any pertinent information regarding the positions, 1 shall be posted at each school site at which openings are expected to occur.

  • Extended Illness Sick leave for extended illness (5 or more days) will be paid only during the time period in which a physician certifies the employee to be physically or mentally disabled, and only to the extent of the number of days accumulated.

  • Extended After Hours: any time or day not within standard business hours Initial Response Times: CRITICAL support or service requests will be responded to within the following times. Calls to 933-3333 after hour calls will be answered by the WashU IT Systems Operations Center (SOC). The SOC will either resolve the issue or page on call staff to resolve the issue. On call staff will respond to the after hour pager on average* within 30 minutes *averages are calculated on a monthly basis Support Request Resolution Targets‌ WashU IT has established the following general support escalation procedures and resolution targets to meet customer support request needs. Note that service request fulfillment is addressed in a latter section titled “Service Fulfillment Targets”. This section is only addressing support escalation and resolution. Support Escalation & Resolution Procedures – all support requests will be escalated from the initial general support team to a specialized support team based on the priority of the support request or if the general support team cannot resolve the issue within 20 minutes. Once the request is escalated to a specialized support team, the customer will be notified and the specialized support team may contact the customer for further information and testing. Once the specialized support team resolves the request, the general support team will review the resolution to ensure quality control. Once the general support team confirms the resolution has met the customer’s needs, the request will be closed. Communication with the customer will be via email. If the customer does not reply within 3 business days, the ticket will be automatically closed. Prioritization – all support requests will be given a medium priority unless the customer indicates an impact or urgency that requires a higher prioritization. Impact is defined as the affect to which a technology service or system is inhibiting the customer’s ability to conduct University business. Urgency is defined as the timeframe in which the customer needs the technology issues resolved or a workaround put in place. WashU IT uses the following priority scale for systems and services not performing normally. Priority Description Response Target Resolution Target Critical Global Issues Business critical issues – impacting ability to perform mission Issues affecting multiple users unable to be productive 15 minutes 4 hours High Issues affecting individual or multiple users with no workaround available 1 hour 1 Business Day Medium Default priority assigned to all tickets. Issues affecting multiple users with workaround available 1 Business Day 3 Business Days Low Issues affecting individual users with workaround available 2 Business Days 5 Business Days Service Request Fulfillment Targets‌ WashU IT Service Owners work with customers to establish service fulfillment targets for each service request that comprise the Service Features listed in this document. The following table lists the service fulfillment target for each service request: Note: There is a freeze on all enhancement work during Fiscal Year end beginning mid-June thru the 2nd week of July. Service Request Fulfillment Target ID Enablements Response 2 business days Fulfillment: Requests will be taken to AIS Updates committee for prioritization/authorization of work. This committee meets the second Tuesday of each month. Once prioritized/authorization of the work has occurred, within 3 business days WUIT will follow up with the requestor in order to schedule the necessary work. Data Requests All requests must come from a manager within the department. Response 2 business days after receipt of the request. Fulfillment Data requests with a large scope will be escalated to the AIS Updates committee for prioritization/authorization prior to any work being done. The AIS Committee will be made aware of all requests for informational purposes. If approved by either the AIS Updates Committee or WUIT Management in charge of the Finance and Procurement Systems support team for smaller scope requests, the data will be provided within 5 business days of approval. The AIS Updates Committee meets monthly on the 2nd Tuesday. Security of the requestor will be reviewed to ensure that they have the appropriate access to receive the requested data. All requests will additionally be forwarded along to the Business Intelligence Data Warehouse group for assessment of availability of the data within the Data Warehouse. MarketPlace Vendor Enablements 1 vendor enablement will be fulfilled at a time (This could include both CXML Purchase orders and CXML Invoicing) CXML Purchase Order Response 2 Business Days Fulfillment Work will be scheduled after coordination between WUIT, SciQuest, Vendor and Procurement. CXML Invoicing Response 2 Business Days Fulfillment Work will be scheduled after coordination between WUIT, SciQuest, Vendor, Procurement and Accounts Payable. Punch-Out Catalog Enablement Response 2 Business Days Fulfillment Work will be scheduled after coordination between WUIT, SciQuest, Vendor, and Procurement. Enhancement/Integration requests Will be responded to within 2 business days to schedule a follow up meeting to gather requirements. All requests must be presented to the AIS Updates Committee for prioritization or referral to the AIS Domain Governance Committee depending on the scope of the request. Service Availability‌ Monday - Friday 7:00 am - 9:00 pm Saturday 9:00 am - 5:00 pm Service Reliability, Performance & Continuity‌ Service Reliability and Performance The Finance and Procurement Systems service has an expected uptime percentage of 100% during all times noted above under the Service Availability section. The service will handle up to 3000 concurrent. Service Continuity Washington University IT will be responsible for providing a highly available environment to host the Finance and Procurement Systems Service that will fail over to a secondary data center in the case of loss of service from the primary data center and will be fully functional with some exceptions noted below within 10 minutes. This loss of service could be caused by many different events such as power outage, fire, flood, tornado, and etc. In the case of an unplanned outage to the service, Washington University IT will maintain customer contacts initially within the first 30 minutes of the outage, and hourly updates after that. The following Finance and Procurement Systems Services are currently not considered highly available and further planning and project work will need to be completed in order to obtain a 100% highly available environment if deemed a priority: • Batch Processing – This is currently at a level in which up to a day may be needed in order to recover, and therefore, overnight processing may be delayed or skipped for one evening. This would affect the ability to run certain processes that execute periodically during the day as well.

Time is Money Join Law Insider Premium to draft better contracts faster.