Production Cutover Clause Samples

Production Cutover. ‌ 3.9.1. CGI Responsibilities during Pre-Go-Live Phase Provide Written Deliverable No. 4 –Technical Readiness Checklist – and Written Deliverable No. 5 –Technical Cutover Plan. With input from the Client, identify mutually agreed transmission methodology and format for each cutover data source and create checklists, unload steps, and verification procedures as part of the Technical Cutover Plan. Provide input into go/no-go decision and jointly perform production cutover with Client according to the Technical Cutover Plan. Populate non-production environment(s) with production data after Go-Live Date. 3.9.2. Client Responsibilities during Pre-Go-Live Phase Deliver end user training, including but not limited to, training new or existing users, training about additional functionality from CGI Advantage® Updates, maintaining and updating training materials and training environment data as needed. Coordinate with CGI to provide the requested information to define the Technical Cutover Plan and Technical Readiness Checklist Deliverables. Participate in the execution of the Technical Cutover Plan and Technical Readiness Checklist. 3.9.3. CGI Responsibilities during Ongoing Phase Not applicable. 3.9.4. Client Responsibilities during Ongoing Phase Not applicable.

Production Cutover. “Go Live” Output: Accela Responsibilities:

Production Cutover. Starboard will work with the TAA IT team to schedule and execute the production cutover for this project. Starboard will use the migration to the Test environment as a “mock” cutover to verify that all configurations and data updates are properly documented and to identify the needed cutover schedule. The production cutover will follow TAA IT change management policies and procedures and be set at a time mutually agreed by Starboard and TAA. Post go-live Starboard will provide remote support to the TAA maintenance and IT teams on an as needed basis to address any issues that may arise in the first 10 days of using the interface. During this time, Starboard will answer any questions from the users, provide additional coaching, and assess and resolve any defects found. Any new requirements introduced will be placed on an enhancement list for prioritization with other TAA Maximo initiatives. • Go-Live Checklist • ▇▇▇ will lead and perform all required User Acceptance Testing activities. • TAA will schedule personnel and locations for End User training activities as required. • TAA will provide remote access for Starboard to the Maximo applications, databases, and servers for this effort. • Starboard will perform development activities off site and provide TAA configuration documents for change control. • Starboard will perform changes in the DEV environment where they will be unit tested. Once successfully validated, the changes will be applied to TEST and user tested by TAA. Once approved, the updates will be applied to PROD as part of a scheduled release. • This project scope is priced and based entirely on the information and the requirements provided by TAA. If any variances are determined by Starboard or requested by TAA, a change order for adjustment to scope, schedule, or cost will be submitted. • Starboard cannot be held responsible for any defects in the Maximo applications as delivered from the vendor, IBM. If any defects are found, Starboard will open a PMR with IBM support and Starboard will work with TAA IT staff as needed with obtaining log files and communicating findings to the L1 or L2 IBM support personnel. If necessary for Starboard to install an IBM delivered fix, create a work around process, or develop a TAA specific solution to an IBM defect, a PCR will be created to address the change.

Production Cutover. The vital stage of Production Cutover is comprised of production and post production support. Final data conversion is completed as necessary. All the prior training and planning now culminates as your organization is self-sufficient within the new Tyler environment. Now you are operating in the production environment with the support of the Tyler project team. If required or planned upon during the initial stages, post-live education and training is implemented. The phase closes with a transition to the product support team. Stage 6: Phase/Project Closure The final stage of implementation, Phase/Project Closure, is to bring a formal closure to the project phases, or to the whole Tyler implementation if no additional phases are required. Through a formal project close-out meeting and acceptance from stakeholders, both teams formalize the completion of a successful Tyler implementation. The deliverables completed through the project close-out meeting may include such topics as lessons learned, a review of accomplishments and final acceptance of the project work completed.

Production Cutover. Contractor shall prepare a detailed Production Cutover Script. This script shall define the County and the Contractor roles/responsibilities and sequence/timing of tasks that are nePcaegess4a2royf 2t4o0 File Folder: C030087 Page 42 of 240 cutover the non-production environment into the Jail’s production environment. Contractor shall also provide the assistance and support outlined in the Production Cutover Script to facilitate the completion of the final conversion process and other cutover activities. These activities include a full back-up of the County’s production data by the County prior to the final conversion. County will participate in the production cutover and rehearsal activities in accordance with the Production Cutover Script developed by the Contractor. County responsibilities include by are not limited to: - Review cutover scripts developed by Contractor - Review Projection Tables - Verify converted data - Conduct Production Migration - Backup Production data prior to cutover

Production Cutover. 3.9.1. CGI Responsibilities during Pre-Go-Live Phase 3.9.1.1. Provide Written Deliverable No. 4 –Technical Readiness Checklist – and Written Deliverable No. 5 –Technical Cutover Plan. 3.9.1.2. With input from the Client, identify mutually agreed transmission methodology and format for each cutover data source and create checklists, unload steps, and verification procedures as part of the Technical Cutover Plan. 3.9.1.3. Provide input into go/no-go decision and jointly perform production cutover with Client according to the Technical Cutover Plan. 3.9.1.4. Populate non-production environment(s) with production data after Go-Live Date. 3.9.2. Client Responsibilities during Pre-Go-Live Phase 3.9.2.1. Except as otherwise set forth in an Annual Planning Document or Statement of Work, deliver end user training, including but not limited to, training new or existing users, training about additional functionality from CGI Advantage® Updates, maintaining and updating training materials and training environment data as needed. 3.9.2.2. Coordinate with CGI to provide the requested information to define the Technical Cutover Plan and Technical Readiness Checklist Deliverables. 3.9.2.3. Participate in the execution of the Technical Cutover Plan and Technical Readiness Checklist. 3.9.3. CGI Responsibilities during Ongoing Phase Not applicable. 3.9.4. Client Responsibilities during Ongoing Phase Not applicable.