Deploy Phase Sample Clauses

Deploy Phase. Administrator training – train the trainer approach. Training is captured by participation in the Analyze, Build and Certify phases. No additional administrator training is part of the scope of this SOW.  End user training. Company will provide two one hour training sessions to Subscriber’s end users. The training will be conducted via Go-To-Meeting or in person as needed.  Go live.
Sample 1
AutoNDA by SimpleDocs
Deploy Phase. (Go-Live) In the Deploy Stage, IMPLEMENTOR shall support the go-live activities, monitor the new business procedures, the functional and technical system performance, and solve problems with regard to these topics. IMPLEMENTOR will provide one (1) week on-site go-live support, after which the responsibility for the production system shall be transferred to CUSTOMER. Another one (1) week on- site support for the 1st month-end closing is also provided. This stage shall be concluded with a Project Review Report. Support services after post-production shall be limited to the clause provided in the Article XII – XIII.
Sample 1
Deploy Phase. In the Deploy Phase, the following are the listed deliverables: IMPLEMENTOR to provide for CUSTOMER: ❑ Live System. ❑ Production Support. ❑ Project Sign-Off.
Sample 1
Deploy Phase. 35. Medidata will be responsible for setting up the production URL site and moving the Rave application into production following deployment approval by Customer.
Sample 1
Deploy Phase. The Deploy Phases focuses on end user training and the deployment of the Campus Management Products into the Production Environment based on the configured and tested Customer Blueprints. Activities and deliverables supported by CMC in the Deploy phase will be as follows: Activities Deliverables/Actions • Customer will conduct the UAT in accordance with the Testing Plan of the Customer Blueprints with guidance from CMC • CMC and Customer will deliver training in accordance with the Training Plan • CMC and Customer will discuss go / no-go decision-making strategy for deployment of the Campus Management Products in the Production Environment • Legacy freeze: Customer produces final legacy extracts for data migration. CMC loads final extracts into Campus Management Products Production Environment. • Customer performs final smoke test to confirm all Customer Blueprints can be deployed to Campus Management Products Production Environment • Campus Management Products Go-Live • Customer provides go / no-go decision for deployment of the Campus Management Products in the Production Environment • CMC to provide production deployment checklist for Customer to follow • Deployment of the final dataset to the Campus Management Products Production Environment implies the Approval to Proceed (ATP) to the Transition Phase.
Sample 1

Related to Deploy Phase

  • Development Work The Support Standards do not include development work either (i) on software not licensed from CentralSquare or (ii) development work for enhancements or features that are outside the documented functionality of the Solutions, except such work as may be specifically purchased and outlined in Exhibit 1. CentralSquare retains all Intellectual Property Rights in development work performed and Customer may request consulting and development work from CentralSquare as a separate billable service.

  • Construction Phase Part 1 –

  • Maintenance Program LESSEE's Maintenance Program

  • Development Program A. Development activities to be undertaken (Please break activities into subunits with the date of completion of major milestones)

  • Maintenance and Support Services As long as you are not using the Help Desk as a substitute for our training services on the Tyler Software, and you timely pay your maintenance and support fees, we will, consistent with our then-current Support Call Process:

  • Launch Customer shall use commercially reasonable efforts to begin distribution of the Google Desktop Applications promptly following the launch of the Desktop Portal.

  • TECHNICAL SUPPORT SERVICES 2.1 The technical support services (the "Services"): Party A agrees to provide to Party B the relevant services requested by Party B, which are specified in Exhibit 1 attached hereto ("Exhibit 1").

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

  • Commissioning Commissioning tests of the Interconnection Customer's installed equipment shall be performed pursuant to applicable codes and standards. If the Interconnection Customer is not proceeding under Section 2.3.2, the Utility must be given at least ten (10) Business Days written notice, or as otherwise mutually agreed to by the Parties, of the tests and may be present to witness the commissioning tests.

  • Development Efforts 4.2.1 Hana shall use Commercially Reasonable Efforts to Develop each Product in the Territory (including carrying out its responsibilities under the Development Plan) to:

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