Expiration Date Each Letter of Credit shall expire at or prior to the close of business on the earlier of (i) the date one year after the date of the issuance of such Letter of Credit (or, in the case of any renewal or extension thereof, one year after such renewal or extension) and (ii) the date that is five Business Days prior to the Maturity Date.
Extended Work Day Teachers who, during the 196-day work year, are employed for 36 instruction at the District office or a school beyond the defined teacher work day, will be paid 37 according to their current base rate of pay, exclusive of any supplements paid. 39 (3) Professional Development
Deadline Date The parties agree to enter into collective negotiation over a successor Agreement in accordance with Chapter 123, Public Laws of 1974 in good-faith effort to reach agreement on all matters concerning the terms and conditions of employee’s employment. Such negotiations shall begin not later than October 15 of the year preceding the year in which this Agreement expires. Any Agreement so negotiated shall apply to all employees, subject to ratification by the Association, be reduced to writing, be signed by the Board and the Association and be adopted by the Board.
Extended Work Year A teacher requested by the Board to work in his/her regular assignment beyond the contracted number of days shall be offered an extended contract and compensated at the scheduled per diem rate, as specified in Article XXV. Compensation for weeks worked after July 1 shall be at the new rate.
Extended Term Tenant shall have the option to extend the Term for two (2) consecutive five (5) year periods (the "FIRST EXTENDED TERM" and "SECOND EXTENDED TERM", respectively) on all the terms and conditions contained in this Lease including, without limitation, continuation of the adjustment of the Base Rent on an annual basis as provided in Section 3.3 below (provided only that upon commencement of the First Extended Term the only remaining option to extend the Term shall be the Second Extended Term and upon exercise of the option with respect to the Second Extended Term, no further right to extend the Term shall exist). Tenant shall deliver, if at all, written notice of its exercise of the option ("OPTION NOTICE") to Landlord at least six (6) months but not more than one (1) year before the expiration of the Term or First Extended Term, as the case may be. In the event Tenant fails to deliver the applicable Option Notice within the time allowed, Landlord shall deliver written notice to Tenant of Tenant's failure to deliver the Option Notice, and Tenant shall then have thirty (30) days from receipt of such notice within which to deliver the Option Notice, if at all, to Landlord. In the event (and only in the event) that, Tenant fails to deliver an Option Notice to Landlord within such thirty (30) days, Tenant shall be considered to have elected not to extend the Term of this Lease and thereafter, Tenant shall have no further right to extend the Term of this Lease. References in this Lease to the "Term" shall include the initial Term of fifteen (15) years and shall, in addition, include the First Extended Term and the Second Extended Term, if applicable.
COMMENCEMENT/EXPIRATION DATE This instrument is executed as of the date of last signature and is effective for five years from that date, at which time it will expire unless extended.
Grant Completion Deadline The grant completion deadline is the end date of this Agreement set forth in Section 2 above. The Grant Completion Deadline is the date when all grant and matching funds have been paid out or incurred in accordance with the work described in the Scope of Work, detailed in the Estimated Project Budget. If the Grantee finds it necessary to request an extension of the Grant Completion Deadline, an Amendment to the Agreement must be executed as per Section 7, and the stipulations in Section 15 must be met.
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
Extended Reporting Period If any required insurance coverage is on a claims-made basis (rather than occurrence), Contractor shall maintain such coverage for a period of no less than three (3) years following expiration or termination of the Master Contract.
Initial Term The initial term will begin on the date set forth in the Contract documents or on the date the Contract is signed by all Parties, whichever is later.
