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 necessary to cutover the non-production environment into the 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
Production Cutover. “Go Live” Production date is defined as the official date in which Accela Civic Platform moves from the test environment to production for daily Health District usage. This date will be agreed to in writing by both Accela and the Health District at project inception. It may be altered only by written change order agreed to by both parties. In the weeks prior to moving to Production, Accela will assist in final data conversions, system validation, staff preparation and training, and coordination of deployment. Output: Deployment support prior to moving to Production. Assistance with setup of Integration points in Production. Final Conversion run during cutover. Accela Civic Platform used in Production environment for District daily use. Accela Responsibilities: With assistance from the Health District, lead the effort to transfer the system configuration and any required data from Test to Production. Assist in the development of a Cutover checklist that details the critical tasks that must be accomplished prior to moving to Production.
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. Deliverable: • Go-Live Checklist TAA Responsibilities • XXX will lead and perform all required User Acceptance Testing activities. • TAA will schedule personnel and locations for End User training activities as required. Assumptions • 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. 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
