Deployment Plan. 16.5.1 The Authority shall develop a Deployment Plan containing details including but not limited to number and type of Buses, details of the assured availability during the Contract Period, Operational Routes, schedules of Buses including description of Bus Stops, frequency and table of schedule providing Bus headways, based on peak and off peak hour (the “Deployment Plan”), more particularly specified in Schedule-J.
Deployment Plan. Flock shall advise Customer on the location and positioning of the Flock Hardware for optimal product functionality, as conditions and locations allow. Flock will collaborate with Customer to design the strategic geographic mapping of the location(s) and implementation of Flock Hardware to create a deployment plan (“Deployment Plan”). In the event that Flock determines that Flock Hardware will not achieve optimal functionality at a designated location, Flock shall have final discretion to veto a specific location, and will provide alternative options to Customer.
Deployment Plan. The Deployment Plan is a staged approach to the implementation of processes, procedures and systems required by this Agreement. The Deployment Plan describes the Parties’ attempt to implement a process for attaining performance at or better than the performance threshold. The Parties agree to implement the provisions of this Agreement in accordance with the Deployment Plan set forth in Appendix 4 to this Attachment. The Parties agree to negotiate, by the end of Contract Month 1, additional requirements which relate to those obligations of the parties in this Agreement that are not addressed in the Deployment Plan. Thereafter, the Deployment Plan may be revised from time to time to add any additional requirements established by the Parties as part of the implementation process.
Deployment Plan. 1.1 Exhibit C of the Agreement is hereby amended by ADDING the following provisions, which shall terminate three (3) years after the effective date of this Amendment:
Deployment Plan. The Parties agree to use their best commercially reasonable efforts to effectuate the transition set forth in the Deployment Plan, which efforts shall include seeking all necessary consents required from, and giving all required notices to, third parties, including programmers, redistributors and landlords. In the event that another station participating in the Deployment Plan is required to host any program stream of either the Host Station or the Guest Station pursuant to an agreement contemplated by the Deployment Plan, and fails to host such program stream, then Host and Guest agree to negotiate in good faith to find another host (in ATSC 1.0 or 3.0 format, as applicable) for such program stream. Each Party acknowledges that conditions in the Market during the Term may warrant changes to the Deployment Plan to facilitate the provision of more ATSC 3.0 capacity or programming to stations participating in the Deployment Plan. Each Party agrees to negotiate in good faith with other parties in the market to implement such changes as to which the Parties mutually agree.
Deployment Plan. Exhibit C of the Agreement is hereby amended by ADDING the following provisions, which shall terminate three (3) years after the effective date of this Amendment: ---------- -------------------------------------- ----------------- AOL DESIGNATED CITIES MODEMS ---------- -------------------------------------- ----------------- 1. BAURU - SP [ ** ] ---------- -------------------------------------- ----------------- 2. BELEM - SP [ ** ] ---------- -------------------------------------- ----------------- 3. BENTO GXXXXXXXX - RS [ ** ] ---------- -------------------------------------- ----------------- 4. CXXXXXX - MT [ ** ] ---------- -------------------------------------- ----------------- 5. ACHOEIRA DO ITAPEMERIM - ES [ ** ] ---------- -------------------------------------- ----------------- 6. CAMPINA GRANDE - PS [ ** ] ---------- -------------------------------------- ----------------- 7. CXXXXX DOS GOYTACAZES - RJ [ ** ] ---------- -------------------------------------- ----------------- 8. CAXIAS DO SUL - RS [ ** ] ---------- -------------------------------------- ----------------- 9. COLATINA - ES [ ** ] ---------- -------------------------------------- ----------------- 10. CORUMBA - MS [ ** ] ---------- -------------------------------------- ----------------- 11. DOURADQS - MS [ ** ] ---------- -------------------------------------- -----------------
Deployment Plan. Sl. No. Shift name Remarks 1 General Shift 9.30AM to 6.30PM Dedicated Manpower required at NIC HO for Call Coordination as per Section 5.1 2 Period beyond General Shift After the general shift, the Bidder has to provide Toll Free Number to log the service calls.
Deployment Plan. The goal of this task is to finalize the Deployment Plan in consultation with key Energy Commission staff. · The Recipient shall: • Finalize the Deployment Plan to include, but not be limited to: • Market projections of vehicles. • Site selection criteria. • Residential, workplace, fleet, commercial, and retail charging • Mitigation of any impacts to the grid. • Consideration of overlapping areas with other ARFVT funded infrastructure projects. • Affirmation of consistency from the local jurisdictions and utilities. [A CPR WILL BE HELD DURING THIS TASK IN RELATION TO THE DEPLOYMENT PLAN. See Task 1.2 for details.] [Before work done by a subcontractor begins their subcontract must be executed. See Task 1.8 for details] Products: • Draft Deployment Plan • Final Deployment Plan
Deployment Plan. 16.5.1 The Authority shall develop a Deployment Plan according to which the Operator shall operate the Buses. The parameters to be included in the Deployment Plan are set out in Schedule-J and shall include:
Deployment Plan. Based on the output of 2.1 Strategic Analysis, and in support of all features and functions in: RFP Response Template, Attachment 16, Section 3.0 Implementation Overview, the vendor will deliver a comprehensive implementation and deployment plan, including proposals for organizing site sections, site domain management, end-user and administrator roles, and end-user permissions. Work products under this deliverable include but are not limited to: • A “mobile-first” strategy to ensure all content and templates are optimized for responsive adaptation to tablets and phones; • A site administration plan to support federated management across the platform; • End-user Workflow and Permissions schemas for all sites on the platform; • A strategy for implementing a design pattern system, such as US Design System into Drupal. • The deployment strategy that should articulate and document the approach for delivering: o An intuitive WYSYWG authoring/editing environment for end-users; o A Headless CMS strategy that allow the Judicial Council to “syndicate” content to other websites either on or off our platform; o Support for design and/or integration of interactive ‘guided interviews’ that users along a decision-tree of questions and answers; o Support for dynamic content presentation, driven by simple end-user input, such as selecting a category and seeing a list of relevant forms; o A digital asset management plan, including planned approach for storing, uploading, and retrieving files; o Administration & User guide documentation; o Development & deployment documentation; o Quality assurance plan; o Go live deployment plan.
