Service Transition. The Parties acknowledge that prior to the date on which specific Services shall be supplied by NCPA for a specific Customer generating resource, the Parties may be required perform certain work and other activities to establish and enable the systems and processes that are required to perform Services as of the date on which Services for a specific Customer generating resource is to commence. Such activities may include establishing common business practices, developing business requirements, establishing connectivity of systems and equipment, coordinated training of staff, and other activities that may be required to enable NCPA to provide, and Customer to receive, Services. During this transition period (the "Transition Period"), the Parties agree to cooperate in good faith to establish and enable the systems and processes that are required to perform Services. All activities to be performed by NCPA during the Transition Period are included as part of the comprehensive Services provided to Customer, pursuant to this Agreement, even though such work and activities may be performed by NCPA prior to the date on which specific Services shall be supplied by NCPA for a specific Customer generating resource. APPENDIX B COMPENSATION SCHEDULE Pursuant to Section 7.1 of this Agreement, Customer shall pay NCPA the amounts listed in this Appendix B (the “Compensation Schedule”) in consideration for Services provided under this Agreement.
Service Transition. The Contractor shall coordinate the development and deployment of IT services. It shall ensure that changes to services and Service Management processes are carried out in a coordinated way.
Service Transition. Is a Lifecycle stage that moves an IT Service or its components from one lifecycle status to the next.
Service Transition. Service Transition encompasses the planning and execution of all system changes for GCSS-MC/LCM Increment 1. System changes are divided into two categories, CRs and ECPs. Proposed system changes require a responsive, agile, yet disciplined approach to the GCSS-MC system and are categorized by components of the system and are aligned with the Program’s organization: • Infrastructure including hardware, operating system, and databases • Functional business processes • Cybersecurity System Security • Data Quality/Interfaces GCSS-MC/LCM Increment 1 currently has a documented backlog of approximately 600 CRs awaiting disposition. The CRs cover a broad area including functional, system security, interface management, infrastructure, training, audit, and WAN optimization. The CRs vary in level of priority (based on IEEE 12207 classification) and impact to the user community with the majority of changes classified as priority 2. The backlog is managed by the GCSS-MC CCB. GCSS-MC releases updates to the production system as fixes become available. In FY 2017, there were 288 CRs addressed. Of the 288 CRs, 175 CRs were children, meaning a parent CR resolution closed the child CR. Of the 113 CRs applied to production, 57 were for System Security & Infrastructure and 56 were configuration or code fixes. In addition, GCSS-MC released an average 5 CRs per quarter to address cybersecurity issues in FY 2017. The schedule also accounts for implementation of quarterly Oracle CPUs to maintain system security compliance. The SRs elevated from Incident and Problem Management from the Tier 1, 2, and 3 Service Desks are associated with a respective CR. CRs generated as a result of testing another change are associated to each other. Issues can be identified by a sub-type which identifies the GCSS-MC change authority (Change Assessment Board [CAB], CCB) and the associated configuration items impacted by the change. System changes come from a variety of sources, including, changes to the hardware or software design, code fixes, configuration fixes, and data scripts changes. System changes are also necessary to comply with and/or respond to IA/Cybersecurity requirements, integrating new capabilities (from external development, and design changes to make functions more responsive to customer needs). The Contractor shall provide responsive, disciplined support to sustain, change, and enhance the GCSS-MC/LCM Increment 1 system following the Configuration Management Process detailed in ...
Service Transition. If this Agreement is terminated for any reason, provided Licensee is current on all payments to DataSelf and Licensee pays all applicable Software Maintenance fees and any fees related to the transition services, DataSelf may continue, for a period of at least one hundred twenty (120) days but not to exceed one hundred eighty (180) days from the date of the notice of termination, to provide Software Maintenance to Licensee pursuant to the terms of this Agreement, but only to the extent reasonably necessary to facilitate the transition of the Software from DataSelf to another provider. To facilitate this transition, Licensee and DataSelf will jointly develop a plan for the transition services.
Service Transition. At the initiation of this contract and should management and operation of PVTA’s transportation services be transferred in the future to another management firm or entity, a smooth, seamless transition that is as transparent to PVTA's riders as possible is required. The CONTRACTOR shall take all actions necessary to facilitate a smooth and professional transition, including, at a minimum:
1. CONTRACTOR shall provide PVTA a detailed service transition plan & budget . Said plan shall identify key milestones, such as, acquisition of facility and equipment, interviewing and training of personnel, etc.
2. The CONTRACTOR's Project Manager shall be on-site no later than November 15, 2013.
3. Retention of current drivers and staff is significant concern for the PVTA. It is the PVTA's desire that as many of the qualified existing personnel be retained as possible and that these personnel not experience a diminishment in wages, benefits or working conditions. The CONTRACTOR's transition plan must address their approach to retention and training current personnel. Said transition plan will be major factor in the proposal evaluation.
4. All start-up and transition costs shall be identified and amortized into proposer's monthly rate.
5. Adherence to milestone proposed and the commitment of resources presented in the approved transition plan shall be a measure of contract compliance. Failure to adhere to plan requirements may be considered a material breach by the PVTA.
6. Should CONTRACTOR be required to transition this contract to another management firm or entity in the future, CONTRACTOR shall cooperate and facilitate such transition in an open, honest and professional manner. THIS AMENDMENT AND EXTENSION is made this 1010h day of February 2016 by and between the Pomona Valley Transportation Authority, hereinafter referred to as "PVTA" and First Transit Inc., hereinafter referred as "CONTRACTOR".
Service Transition. IMPLEMENTATION
Service Transition. At the expiry or early termination of the contract the supplier will be required to support and assist RBG Kew and any incoming supplier in the transfer of the service. The supplier will agree to issue to RBG Kew all information relating to the service (management information, proofs etc). The transition period may be up to 3 months from expiry or early termination of the contract and the supplier agrees that the required levels of service will not fall below the levels expected and outlined in section 8. Redacted Redacted Redacted
1.1 Without prejudice to the Authority's general obligation of confidentiality, the Parties acknowledge that the Authority may have to disclose Information in or relating to the Contract following a Request for Information pursuant to clause E5 (Freedom of Information).
1.2 In this Schedule the Parties have sought to identify the Contractor's Confidential Information that is genuinely commercially sensitive and the disclosure of which would be contrary to the public interest.
1.3 Where possible the Parties have sought to identify when any relevant Information will cease to fall into the category of Information to which this Schedule applies.
1.4 Without prejudice to the Authority’s obligation to disclose Information in accordance with the Freedom of Information Xxx 0000 and the Environmental Information Regulations, the Authority will, acting reasonably but in its sole discretion, seek to apply the commercial interests exemption set out in s.43 of the Freedom of Information Xxx 0000 to the Information listed below. CONTRACTOR’S COMMERCIALLY SENSITIVE INFORMATION DATE DURATION OF CONFIDENTIALITY registered in England and Wales under number 05095978 whose registered office is situated at Xxxx 0 000 Xxxxxx Xxx Xxxxxxx Xxxxxx XX0 0XX And The Royal Botanic Gardens Estates Yard Ferry Lane Richmond Surrey TW9 3AG (the "Disclosee") each a “Party” and together the “Parties”.
Service Transition. In the event that Customer decides to switch providers upon the expiration and/or termination of this Agreement (for a reason other than a material breach of the Agreement), Customer shall notify Company of such decision, inform Company of the offer extended by the other provider(s), and allow Company three (3) business days within which to match or beat such other provider’s offer before Customer will agree to switch Services under this Agreement to such other carrier. In any event, if Customer changes service providers, Customer will pay Company for Services in accordance with the terms and conditions of this Agreement until such time as the transfer of the Services to the new provider is actually performed.
