Production Cutover Sample Clauses

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. File Folder: C030087 Page 72 of 240 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
Sample 1
AutoNDA by SimpleDocs
Production Cutover. “Go Live” Output: Accela Responsibilities:
Sample 1
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.
Sample 1
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
Sample 1
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.
Sample 1
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 • XXX 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.
Sample 1

Related to Production Cutover

  • Interconnection Customer (1) Interconnection Customer shall construct and, unless otherwise indicated, shall own, the following Interconnection Facilities: None (2) In the event that, in accordance with the Interconnection Construction Service Agreement, Interconnection Customer has exercised the Option to Build, it is hereby permitted to build in accordance with and subject to the conditions and limitations set forth in that Section, the following portions of the Transmission Owner Interconnection Facilities which constitute or are part of the Customer Facility: None Ownership of the facilities built by Interconnection Customer pursuant to the Option to Build shall be as provided in the Interconnection Construction Service Agreement.

  • Interconnection Customer Drawings Within one hundred twenty (120) days after the date of Initial Operation, unless the Interconnection Parties agree on another mutually acceptable deadline, the Interconnection Customer shall deliver to the Transmission Provider and the Interconnected Transmission Owner final, “as-built” drawings, information and documents regarding the Customer Interconnection Facilities, including, as and to the extent applicable: a one-line diagram, a site plan showing the Customer Facility and the Customer Interconnection Facilities, plan and elevation drawings showing the layout of the Customer Interconnection Facilities, a relay functional diagram, relaying AC and DC schematic wiring diagrams and relay settings for all facilities associated with the Interconnection Customer's step-up transformers, the facilities connecting the Customer Facility to the step-up transformers and the Customer Interconnection Facilities, and the impedances (determined by factory tests) for the associated step-up transformers and the Customer Facility. As applicable, the Interconnection Customer shall provide Transmission Provider and the Interconnected Transmission Owner specifications for the excitation system, automatic voltage regulator, Customer Facility control and protection settings, transformer tap settings, and communications.

  • Interconnection Customer Compensation If the CAISO requests or directs the Interconnection Customer to provide a service pursuant to Articles 9.6.3 (Payment for Reactive Power) or 13.5.1 of this LGIA, the CAISO shall compensate the Interconnection Customer in accordance with the CAISO Tariff.

  • Interconnection Customer Provided Services The services provided by Interconnection Customer under this LGIA are set forth in Article 9.6 and Article 13.5. 1. Interconnection Customer shall be paid for such services in accordance with Article 11.6.

  • Interconnection Customer Authority Consistent with Good Utility Practice, this LGIA, and the CAISO Tariff, the Interconnection Customer may take actions or inactions with regard to the Large Generating Facility or the Interconnection Customer’s Interconnection Facilities during an Emergency Condition in order to (i) preserve public health and safety, (ii) preserve the reliability of the Large Generating Facility or the Interconnection Customer’s Interconnection Facilities,

  • Hearing Services Hearing Exams and Tests Hearing Aids

  • Manufacturing Services Jabil will manufacture the Product in accordance with the Specifications and any applicable Build Schedules. Jabil will reply to each proposed Build Schedule that is submitted in accordance with the terms of this Agreement by notifying Company of its acceptance or rejection within three (3) business days of receipt of any proposed Build Schedule. In the event of Jabil’s rejection of a proposed Build Schedule, Jabil’s notice of rejection will specify the basis for such rejection. When requested by Company, and subject to appropriate fee and cost adjustments, Jabil will provide Additional Services for existing or future Product manufactured by Jabil. Company shall be solely responsible for the sufficiency and adequacy of the Specifications [***].

  • Interconnection Customer Payments Not Taxable The Parties intend that all payments or property transfers made by the Interconnection Customer to the Participating TO for the installation of the Participating TO's Interconnection Facilities and the Network Upgrades shall be non-taxable, either as contributions to capital, or as a refundable advance, in accordance with the Internal Revenue Code and any applicable state income tax laws and shall not be taxable as contributions in aid of construction or otherwise under the Internal Revenue Code and any applicable state income tax laws.

  • Interconnection Customer Obligations The Interconnection Customer shall maintain the Large Generating Facility and the Interconnection Customer’s Interconnection Facilities in a safe and reliable manner and in accordance with this LGIA.

  • Engineering Services Definition: Engineering Services includes any service or creative work, the adequate performance of which requires education, training and experience in the application of special knowledge in consulting, investigating, evaluating, planning and designing, engineering principles. Engineering Services covered by the Xxxxxx Architect-Engineers Act (40 U.S.C. 1102) are not covered in the primary scope of OASIS SB. Examples: Service areas that are included under the Engineering Services discipline include, but are not limited to the following: 1. Systems Engineering 2. Advanced Technology Pilots and Trials 3. Alternative Energy Sources and Engineering 4. Configuration Management 5. Concept Development

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!