Launch Phase Sample Clauses

Launch Phase. During the Launch phase the Customer prepares for final system deployment. Communication and change management plans are executed, and end-users and support teams are trained. The Customer is supported by their consultant through go-live. Upon Go Live, Neeyamo shall provide L2/L3 level support to the Customer, at no additional cost, for a maximum of fifteen (15) days. Such support will be provided remotely and shall ensure any configuration changes (which are not Change Requests) required by the Customer are carried out as part of the one-time implementation cost that the Customer pays to Neeyamo under this Agreement.
Sample 1Sample 2Sample 3See All (7)
AutoNDA by SimpleDocs
Launch Phase. User Acceptance Testing: Once the Platform is set-up, Mercatus will provide key Customer users materials for User Acceptance Testing (UAT). Expectations for process: o Limit to 1-2 users per key function (up to 10 total users) o Tests are based on specific list of requirements within the approved FRD o Approval is based on fulfillment of the requirements, not on configuration change requests. Following Customer approval, Mercatus will proceed with full Customer training, which will have a mutually agreed upon rollout plan between the Customer and Mercatus across the Customer and any external users (if applicable). Any Change Requests to the approved FRD suggested by Customer will be tracked and communicated back to Customer for formal approval prior to configuration adjustments. These items will be scoped for time and cost impact and billed according to applicable Professional Services rates. • Training: o Once ICS and UAT processes are complete, Mercatus will provide training to key Customer Administrators for managing a hosted environment in the Platform. Such initial training will equip Administrators to maintain and configure all key features to best accelerate broader user workings in the Platform. • Post-Launch Training Tools: o Mercatus University: • Online Training Platform including custom training paths, videos, practice exercises, help articles, best practices recommendations. • Certifications available for all Power User, Admin & Custodian Roles o In-App Tutorials: • Standard walkthroughs guiding users through primary activities • Custom walkthroughs available upon request with independent Services scope o Ad-hoc Webinars: • Virtual, open-forum webinars highlighting new features, best practices, case studies
Sample 1Sample 2Sample 3See All (4)
Launch Phase. Once the system has been completed, SolutionX prepares for final launch. An import of user and billing information is made. Quality assurance testers continue to work through the system, tracking and submitting bugs. The client’s team and online support are trained in how to use the system and XXXXXXXXX.XXX | 801.224.4444 0.022 SCHEDULE.
Sample 1Sample 2
Launch Phase. | JUNE 16 - JULY 28 (29 BUSINESS DAYS) • Internal Quality Assurance (Jun 16 - Jun 29) • Continue bug testing, tweaking and fixing • Train Client on using and administering system • Beta Launch with select users (Jun 30 - Jul 13) • Final import/migration of users (if required) • Final Launch (Jul 14) • Old Vi-Net system remains publicly accessible (Jul 14 - Jul 27) • Old Vi-Net system is closed (Jul 28)** * Start of schedule is contingent upon completion of the Scope Phase and the signing of the final contract. Schedule is contingent upon timely submission, review and approval of materials by Client. Any changes in the scope document after the Scope Phase is complete or failure by Client to adhere to deadlines outlined above may affect the schedule and pricing, in which case, additional costs will be paid for by Client. ** If the client wants to extend the beta period or keep the old Vi-Net system running concurrently with the Unity system longer than the dates outlined above, additional costs will be incurred and charged to the Client. XXXXXXXXX.XXX | 801.224.4444 0.024 THIS EXHIBIT HAS BEEN REDACTED AND IS THE SUBJECT OF A CONFIDENTIAL TREATMENT REQUEST PURSUANT TO RULE 24b-2. REDACTED MATERIAL IS MARKED WITH [***] AND HAS BEEN FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION. PRICING. VI-NET UNITY SCOPE CUSTOM DEVELOPMENT PRICING SolutionX estimates the billable new features to cost the following: Total Estimated Hours of Billable Custom Development: * ** hours Total Estimated Cost of Billable Custom Development: $ * ** COST DESCRIPTION $*** Landing Pages - Landing pages are now 2-tiered. We will include up to 1 tier for free, and xxxx for the 2nd tier. $*** Share - The groundwork for sharing will be included for free, but new features (i.e. selecting a website for Facebook and Twitter shares) will be billed as custom dev. $*** Marketing Site - display the latest blog post on the home page of the marketing site. $*** Notifications - Integrate with Exigo to support Vi-Net specific notifications and feed items. Full list in comments. Billable items marked as NEW. $*** Home Page - My Business Snapshot. Displays the business information pulled from Exigo. (http:// xxxxxxxxx.xxx/Xxxxxxxx/XxXxxxx/xxxxx_xxxx_xxx.xxx). All information not currently being displayed on the Prosperity landing page of Vi-Net will be billed as custom development $*** My Business - Business Dashboard. All content not currently working on the Prosperity landing page of Vi-N...
Sample 1
Launch Phase. Deliverable: Provide onsite go live assistance at Xxxxxxxx’s office as outlined in the agreement.
Sample 1
Launch Phase 
Sample 1

Related to Launch Phase

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

  • 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.

  • Commencement of Work Engineer shall not commence any field work under this Contract until he/she/it has obtained all required insurance and such insurance has been approved by County. As further set out below, Engineer shall not allow any subcontractor/subconsultant(s) to commence work to be performed in connection with this Contract until all required insurance has been obtained and approved and such approval shall not be unreasonably withheld. Approval of the insurance by County shall not relieve or decrease the liability of Engineer hereunder.

  • 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.

  • Development Plan document specifying the work program, schedule, and relevant investments required for the Development and the Production of a Discovery or set of Discoveries of Oil and Gas in the Contract Area, including its abandonment.

  • Project Schedule Construction must begin within 30 days of the date set forth in Appendix A, Page 2, for the start of construction, or this Agreement may become null and void, at the sole discretion of the Director. However, the Recipient may apply to the Director in writing for an extension of the date to initiate construction. The Recipient shall specify the reasons for the delay in the start of construction and provide the Director with a new start of construction date. The Director will review such requests for extensions and may extend the start date, providing that the Project can be completed within a reasonable time frame.

  • Development and Regulatory Milestones With respect to each of the following milestones, Ikaria shall pay BioLineRx the corresponding payment set forth below within [**] days after the achievement by Ikaria, its Affiliates or Licensees of such milestone: MILESTONE PAYMENT

  • Development Schedule The Project shall substantially comply with the specific timetables and triggers for action set forth in Article 5 of this Agreement. The parties acknowledge that, as provided in G.S. 160A-400.25(b), the failure to meet a commencement or completion date shall not, in and of itself, constitute a material breach of this Agreement pursuant to G.S. 160A-400.27 but must be judged based upon the totality of the circumstances.

  • Statement of Work The Contractor shall provide the services and staff, and otherwise do all things necessary for or incidental to the performance of work, as set forth below:

  • Project Scope The physical scope of the Project shall be limited to only those capital improvements as described in Appendix A of this Agreement. In the event that circumstances require a change in such physical scope, the change must be approved by the District Committee, recorded in the District Committee's official meeting minutes, and provided to the OPWC Director for the execution of an amendment to this Agreement.

Time is Money Join Law Insider Premium to draft better contracts faster.