System Deployment Sample Clauses

System Deployment. Following completion and sign off of User Acceptance Testing, StarCompliance will deploy the final configuration to Production (“System Deployment”).
AutoNDA by SimpleDocs
System Deployment. TransCore and KLD will install the ACDSS into the Overland Park TransSuite production system. The City will provide any field hardware installation or configuration required for the operation of the system. KLD will provide services and any additional required training for the installation, configuration, and optimization of the ASCT system. Deliverables • Operational field deployment of ACDSS
System Deployment. Contractor shall deploy the System as set forth in the Technical Specification and the Payment Milestone Schedule. The System shall be considered fully installed upon installation and deployment of the entire System pursuant to the Payment Milestone Schedule, in accordance with the Technical Specification and upon Final Acceptance.
System Deployment. At the beginning of this phase, the software construction will have been completed and accepted by the State, and the software will be in the process of being rolled-out. During this phase, ISG will assist in:  Reviewing and validating results of user acceptance testing;  Evaluating the effectiveness of end-user training;  Monitoring completion and testing of cutover plans and go-live checklists; and  Participating in a project governance assessment of State’s readiness to “go live” with the new system.
System Deployment. Plan The deployment plan must document the specific activities and timeframes that are required to ensure a full and successful roll- out of the MVP and Phase 2 System. ✓ Agency-accepted DED. ✓ Deliverable contains all criteria agreed-upon in the DED. ✓ Agency PM approval. 8.3.2
System Deployment. 4.2.1 LCC shall rank candidate sites and validate that the site is acceptable for the design according to the information provided by Site Acquisition.
System Deployment. The Tyler Technical Services team installs Tyler Applications on the server (hosted or client‐based) and ensures the platform operates as expected. RACI MATRIX KEY: R = Responsible A = Accountable C = Consulted I = Informed STAGE 2 System Deployment TYLER CLIENT TASKS Tyler Executive Manager Tyler Implementation Manager Tyler Project Manager Tyler Implementation Consultant Tyler Data Conversion Experts Tyler Forms & Reports Experts Tyler Customization Programmers Tyler Technical Support Tyler Sales Client Executive Sponsor Client Steering Committee Client Project Manager Client Functional Leads Client Change Management Leads Client Power Users Client Department Heads Client End Users Client Technical Leads Client Project Toolset Coordinator Client Upgrade Coordinator Install contracted software on server A I R I C Ensure platform operates as expected A I R I C 4.3.8 Control Point 2: Assess & Define Stage Acceptance Acceptance criteria for this Stage includes completion of all criteria listed below. Advancement to the Build & Validate Stage is dependent upon Tyler’s receipt of the Stage Acceptance.
AutoNDA by SimpleDocs
System Deployment. The Tyler technical services team Installs Tyler Applications on the server and ensures the platform operates as expected. RACI MATRIX KEY: R = Responsible A = Accountable C = Consulted I = Informed STAGE 2 System Deployment TYLER CLIENT TASKS Tyler Executive Manager Tyler Implementation Manager Tyler Project Manager Tyler Implementation Consultant Tyler Data Conversion Experts Tyler Forms & Reports Experts Tyler Modification Programmers Tyler Technical Support Tyler Sales Client Executive Sponsor Client Steering Committee Client Project Manager Client Functional Leads Client Change Management Leads Client Power Users Client Department Heads Client End Users Client Technical Leads Client Project Toolset Coordinator Client Upgrade Coordinator Install contracted software on server A I R I C Ensure platform operates as expected A I R I C
System Deployment. Time Commitment 1 FTE 1 FTE Scheduled Beginning and End Dates September – October 2020 September – October 2020 Subtask 4.1 – Subtask 4.2 – Core Implementation Endpoint Setup
System Deployment. The goal of this task is to deploy the systems in multiple tribal communities across the state to test the equipment with different prospective partners in different use cases, including different climate zones and weather conditions. The Recipient shall: ● Prepare a Deployment Plan including: o Proposed deployment sites information: ▪ California climate zone (minimum of three unique zones) ▪ Tribal Community or Disadvantaged area and low-income status ▪ Description of potential non-emergency applications o Description of deployment testing and verification that will occur, including, but not limited to: ▪ Duration ▪ Power output ▪ Use case and application ▪ Planned weather conditions. o Planned deployment schedule. ● Confirm deployment site hosts ability to host and the preferred schedule. ● Document site deployment with photographs and videos. ● Prepare a Deployment Report upon the completion of each site deployment documenting the testing, performance, community feedback and additional community lead applications for each system: o Proposed use case for the deployment ▪ Non-emergency applications, including off-grid uses throughout the year, special events, vehicle charging, electric equipment operation, and others ▪ Emergency applications consistent with the findings from the Task 2 Community Engagement Plan in the unforeseen event of a local emergencyRenewable energy connectivity and ability to leverage existing renewable assets in the community during outages and emergencies.
Time is Money Join Law Insider Premium to draft better contracts faster.