Go Live Clause Samples
POPULAR SAMPLE Copied 16 times
Go Live. The use of the System as a live, non-test-bed system. This can be exhibited by events such as the completion of the first real-world booking, the taking of the first real-world call for service, the entry of the first real-world case report, or a similar event dealing with real- world use.
Go Live. The term “Go Live” shall mean the milestone in Attachment B where County provides Contractor written notice that the PIMS implementation and system is fully functional and finally accepted, except for the final acceptance of the CAPS+ and CRM Integration.
Go Live. The term “Go-Live” shall mean County’s acceptance of installation and customization of the CMMS after Contractor provides County written notice that the CMMS is fully functional and ready for access and use by County.
Go Live. The Use Case will be promoted from the staging environment to production and Customer shall conduct end to end user acceptance testing of the Use Case (for the period set forth in Appendix 1). Upon the conclusion of such user acceptance testing, Customer will deliver to Unqork written acceptance of the Use Case or provide written notice stating with specificity as to why the Use Case or such or portion(s) of the Use Case are not acceptable to Customer. If Unqork does not receive acceptance or rejection from Customer by the end of this acceptance testing period, then Company shall be deemed to have accepted the Use Case. Upon Customer’s written direction, the Use Case will be available for use in Customer’s GovCloud Production Environment (the “Go-Live Date”). Thereafter, Unqork’s team will monitor the deployment into production and Customers will be provided with applicable Documentation, training and user guides with respect to the Use Case. Hypercare Support – For a period of no more than thirty (30) days following the Go-Live Date (the “Hypercare Period”), on a time and materials basis, Unqork will resolve Defects (as defined in Appendix 4) in the Use Case that are identified during the Hypercare Period by Customer. If Customer encounters an issue with the operation of the Use Case during the Hypercare Period, Customer shall provide written notice to Unqork, including the following information: ● Browser type and version ● Detailed steps to reproduce the issue ● Specific feature/functionality of the Use Case relating to the issue ● Detailed description of Requirement versus actual operation of such functionality or feature of the Use Case ● Available workarounds ● Detailed description of troubleshooting/debugging activity (e.g. order of steps) Customer has performed ● Copy of erroneous file (if generated from the Use Case) Upon the receipt of such written notice, Unqork and the Customer shall diagnose such issue. If it is determined that such issue is a Defect, Unqork shall remediate such Defect in coordination with Customer. If Customer requests in writing (1) that Unqork correct an issue not (a) caused by a Defect in the Use Case; (b) attributable to the fault of Unqork; and/or (c) caused by the Unqork Systems, or (2) an enhancement to Requirements set forth in the Scope of Services section of the applicable Order and/or this SOW, as applicable, then Customer shall negotiate a Change Order to this SOW or separate SOW to perform the work necessary to r...
Go Live. ▇▇▇▇▇ will notify Client when one or more Services are available to Client’s Designated Users (“Go Live Date”). ▇▇▇▇▇ will host a welcome call and provide Client with information needed for Designated Users to access Marco Services. ▇▇▇▇▇ will also notify Client when all remaining components of onboarding are completed. Additional services may be implemented post Go Live Date. An implementation plan with timelines will be discussed for Services during the welcome call.
Go Live. 8 Date upon which CONTRACTOR begins live operation of Large Item Billing 9 Services as set forth in Article 7 (“Large Item Billing Services”).
Go Live. 3.1. Holibob will make available the Holibob API from the relevant Go Live Date, which will not be before the Target Go Live Date.
Go Live. Upon the occurrence of each Go Live of the Licensed Software for a Project, Client is deemed to have recognized that the Deliverables provided in respect of such Project satisfy the applicable requirements therefor, except to the extent otherwise expressly set forth in a writing signed by both parties in connection with such Go Live.
Go Live. Upon the occurrence of System Acceptance of the Licensed Software for a Project, which shall occur at the time of or prior to Go Live for that Project, Client is deemed to have recognized that the Deliverables provided in respect of such Project satisfy the applicable functionality requirements therefor. In addition, except and to the extent otherwise expressly set forth in a writing signed by both parties in connection with such System Acceptance, all other obligations of JTI under this Agreement shall be deemed satisfied with respect to such Project. For the avoidance of doubt, Client’s decision to Go Live with a given Project, whether or not accompanied by an executed formal acceptance certificate, shall constitute System Aceptance and signify Client’s acceptance of that Project and upon the occurrence of Go Live of that Project JTI shall be deemed to have satisfied its performance obligations with respect to that Project. Notwithstanding the foregoing, and for the sake of clarity, any license, maintenance, and support obligations set forth in the License Agreement shall continue as set forth in the License Agreement.
Go Live. SBTech agrees to have the Software ready for a Commercial Launch Date (“Go-Live”), as specified in the applicable SOW, contingent upon Lottery, and any applicable Third Party Providers (but not SBTech Third Party Providers) and other Lottery subcontractors, providing full cooperation and commitment of resources to facilitate Go-Live and all necessary integrations, all as set forth in more detail in an SOW.