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. Xxxxx will notify Client when one or more Products are available to Client’s Designated Users (“Go Live Date”). Xxxxx will host a welcome call and provide Client and the Designated IT Technical User with information needed for DesignatedUsers to access Marco Services. Xxxxx 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. Marco will notify Client when one or more Services are available to Client’s Designated Users (“Go Live Date”). Marco will host a welcome call and provide Client with information needed for Designated Users to access Marco Services. Marco 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. 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. Beginning on completion of delivery and after GEHC verifies each Component meets specifications, Customer will have ten business (10) days to determine if such Component operates substantially in accordance with the applicable Documentation or specifications (“Validation Test Period”), after which the Component will be available for productive use (“First Productive Use”). Customer will then have fifteen (15) business days to conduct further testing (“Production Test Period”). If the Component fails to perform accordingly, Customer will provide to GEHC: (i) written notice; (ii) unencumbered access to the specific Component; and (iii) a reasonable time to bring it into compliance. After correction by GEHC, Customer will have the remainder of the Production Test Period or ten (10) business days, whichever is greater, to continue testing. Each Component is accepted (“Go-Live”) on the earlier of (a) expiration of the Production Test Period; or (b) the date the Component is first used for non-acceptance testing purposes, at which point the subscription will commence.
Go Live a. Contractor will provide a Go Live assessment plan and activities plan for ORIA approval. The purpose of the plan is to identify and assess readiness for transition to production, and to document planned activities for going live. ORIA may identify additional readiness criteria at any time.
Go Live a. It is recognised by both parties that this is go-live version of the MOU which will require further review by either or both parties
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. 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. 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.
