EXTENDED SERVICE 156 Upon application, a military leave of absence (without pay) will be granted to employees who are employed in other than temporary positions. This applies to employees who are inducted through a selective service system or voluntary enlistment, or if the employee is called through membership in the National Guard or reserve component into the Armed Forces of the United States.
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 Sick Leave When sick leave extends for more than 25 consecutive working days, the appointing authority shall initiate the following procedure:
Night Shift Differential 1. An employee who works an assigned night shift shall, in addition to his or her regular salary, be paid a night shift differential for each hour actually worked on the assigned night shift.
CAISO Monthly Billed Fuel Cost [for Geysers Main only] The CAISO Monthly Billed Fuel Cost is given by Equation C2-1. CAISO Monthly Billed Fuel Cost Equation C2-1 = Billable MWh ◆ Steam Price ($/MWh) Where: • Steam Price is $16.34/MWh. • For purposes of Equation C2-1, Billable MWh is all Billable MWh Delivered after cumulative Hourly Metered Total Net Generation during the Contract Year from all Units exceeds the Minimum Annual Generation given by Equation C2-2. Equation C2-2 Minimum Annual Generation = (Annual Average Field Capacity ◆ 8760 hours ◆ 0.4) - (A+B+C) Where: • Annual Average Field Capacity is the arithmetic average of the two Field Capacities in MW for each Contract Year, determined as described below. Field Capacity shall be determined for each six-month period from July 1 through December 31 of the preceding calendar year and January 1 through June 30 of the Contract Year. Field Capacity shall be the average of the five highest amounts of net generation (in MWh) simultaneously achieved by all Units during eight-hour periods within the six-month period. The capacity simultaneously achieved by all Units during each eight-hour period shall be the sum of Hourly Metered Total Net Generation for all Units during such eight-hour period, divided by eight hours. Such eight-hour periods shall not overlap or be counted more than once but may be consecutive. Within 30 days after the end of each six-month period, Owner shall provide CAISO and the Responsible Utility with its determination of Field Capacity, including all information necessary to validate that determination. • A is the amount of Energy that cannot be produced (as defined below) due to the curtailment of a Unit during a test of the Facility, a Unit or the steam field agreed to by CAISO and Owner. • B is the amount of Energy that cannot be produced (as defined below) due to the retirement of a Unit or due to a Unit’s Availability remaining at zero after a period of ten Months during which the Unit’s Availability has been zero. • C is the amount of Energy that cannot be produced (as defined below) because a Force Majeure Event reduces a Unit’s Availability to zero for at least thirty (30) days or because a Force Majeure Event reduces a Unit’s Availability for at least one hundred eighty (180) days to a level below the Unit Availability Limit immediately prior to the Force Majeure Event. • The amount of Energy that cannot be produced is the sum, for each Settlement Period during which the condition applicable to A, B or C above exists, of the difference between the Unit Availability Limit immediately prior to the condition and the Unit Availability Limit during the condition.
Contract Year A twelve (12) month period during the term of the Agreement commencing on the Effective Date and each anniversary thereof.
Evening Shift Differential A shift premium of two dollars and seventy-five cents ($2.75) per hour shall be paid:
Extended Hours Depending upon local service capabilities, available extended hour plans include 5-, 6-, and 7-day, 8-, 16-, and 24-hour options at additional cost. Alaris will use commercially reasonable efforts to provide Service outside of Agreement Hours as shown below. Any such service performed will be billed at prevailing Alaris Per Call Overtime rates.
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: Service Request Fulfillment Target • Availability of new internal and external data sources • Review/recommendation of analytics solution strategies • Enhancement and support of existing reporting and analytics delivery to meet customer needs, regulatory changes, and tool improvement • Customers who submit request during normal business hours will receive an initial response within 1 business day. • Requests will be reviewed by the team and the customer will receive additional follow-up contact after the initial response to determine appropriate request fulfillment steps. Service Availability • Reporting and Analytics environment is available Monday through Friday, 8 a.m.-5 p.m., with >= 95% day-of data availability quarterly. Service Reliability, Performance & Continuity Business customer obligation: The customer should develop and maintain a business continuity plan specific to their area of activity with respect to Reporting and Analytics service outages, so that in case of an unexpected or prolonged service outage, they might still be able to conduct their business appropriately. Change Management and Service Reviews WashU IT has established a change management and service review process to ensure changes and enhancements of services and systems are done in a controlled manner to prevent unintended consequences and to confirm that changes and updates are implemented according to an approved framework. Change Management The complete change management process is documented in the WashU IT Change Management Charter, but the following highlights from this charter are worth noting. Changes and updates to systems and services fall into one of three general categories: Standard – changes and updates that are considered routine, well documented and of low risk to the University. Normal – changes and updates that require scheduled review and approval by the Change Advisory Board (CAB) to ensure mitigation of risk to the University. Emergency – changes and updates that cannot wait until the next scheduled CAB meeting for approval and must be reviewed by the CAB to address a CRITICAL incident or upgrade. All non-standard changes will be communicated to customer according to established customer communication channels. All customer requests for a non-standard change or upgrade to a WashU IT supported service or system must follow the WashU IT change management process. General Maintenance Windows Non-standard changes approved by the CAB will occur during the following maintenance windows: M – Sat: 6pm – 6am Sunday: Anytime of the Day Regularly Scheduled Maintenance for Reporting and Analytics • Server patching occurs the 2nd Tuesday of each month from 5 – 10 pm and results in COGNOS and TM1 servers being unavailable for up to 30 minutes. Roles and Responsibilities The following roles and responsibilities between WashU IT and the customer are called out to highlight the important partnership that must exist between WashU IT as the service provider and WashU departments as the consumers of existing services and systems. Both parties play an important role in ensuring the overall health of services. WashU IT Responsibilities • Provide qualified support personnel to support WashU IT services and systems. • Document specific features and warranties of each service provided by WashU IT • Produce metrics that demonstrate the health of each service. • Provide customers with appropriate communication and governance channels to effect change to WashU IT services and systems in a way that furthers the University’s mission without posing significant risks. Customer’s Responsibilities • Provide an ongoing point of contact within their department with which WashU IT can interface to ensure support and service requests are addressed in a timely manner. • Make support and service requests as outlined in this document. • Use WashU IT established communication and governance channels to request changes to existing services and systems. Service Reporting & Metrics WashU IT will provide the customer with a quarterly report that documents key support and service metrics. Customers may request additional metrics and reporting schedules by contacting their CRM representative. The BIDW website will maintain a metric showing the prior quarter’s percentage of on-time data delivery. Review and Revision Timeline
