Deployment Phase Clause Samples

Deployment Phase. Involves deployment of the Software Release; that is the software is presented to AT&T’s end users. Deployment Phase is closed when AT&T accepts this release into production. Release notes will be provided within 5 BD which define the features and any known issues -associated with the implementation. During the Inception, Elaboration and Construction phases there are 3 ongoing activities. These • Managing project issues and risks • Managing changes to requirements • Ensuring common understanding/capturing a common vocabulary AT&T change requests (submitted after the Project Plan is baselined at end of Elaboration Phase) are managed through the Motricity Change Request Process. AT&T specific features or time critical features may be implemented on top of the latest core software version by Motricity Professional Services.
View SourceView Similar (2)
Deployment Phase. To deploy the solution, SSP will travel onsite to DME for a full week. The week will include installation and configuration of an enterprise-ready ArcGIS Online configuration including secure access of mapping services via the internet. SSP will then install and validate the NBS automation application for consuming streetlight outages entered via ArcGIS Online. SSP will also create the various web maps to be used in collecting the outages and for displaying the outage map to the public via the DME website. SSP will conclude the week by fully training DME administrative personnel on the solution, to allow them to deploy similar solutions on their own in the future. The goal is to enable DME to be as self- sufficient with the technology as possible. Finally, immediately upon conclusion of the onsite week, SSP will provide a remote support period for DME’s production usage of the application, up to five business days or 10 hours of labor, whichever occurs first. Should additional support be required, a change order may be necessary, or the DME-SSP retainer may be used.
View Source
Deployment Phase. Scientific experiments frequently encounter situations which require deviations from the original plan. It is important that all Participants be alerted to any required changes to the plan after the deployment phase has commenced. The following steps will be taken to ensure effective communications: 3.3.1. NSF will remain in contact with the PI during the deployment phase and will notify the OOSSG of any significant changes to the experiment plan (e.g., new geographic location, additional sensors). The OOSSG will review the changes, determine if the changes will affect the mitigation plan, and will provide the results to NSF and the PI. 3.3.2. NSF will provide the OOSSG with final positional information for all deployed OBS units. 3.3.3. The U.S. Navy will inform NSF, who will in turn inform the PIs, of the sensors of interest to the U.S. Navy as soon as possible prior to retrieval of the OBSs.
View Source
Deployment Phase. To deploy the solution, SSP will travel onsite to DME offices for ~four days. It is expected that Trilliant and the CIS department would also be present onsite for this implementation, testing, and validation exercise. SSP will install the integration code into the client production environment. SSP will test and validate the functionality within each system as well. For the balance of the visit, SSP will provide onsite production support as DME users test and validate the new functionality. Any issues will be addressed by either SSP or Trilliant as needed to ensure that the integration is working as designed. DME will be expected to validate that the functionality meets the design documentation and operates correctly. Finally, upon completion of the onsite trip, SSP will provide remote support for the solution, up to 40 hours, over the following 10 business days. If support is required beyond the 10 business days or the 40 hours (whichever is achieved first) a change order may be required. Additional time has not been included for a second environment installation, however if this becomes a requirement, the DME SSP retainer may be utilized for the work. At the completion of the offsite support period, the integration project will be considered complete.
View Source
Deployment Phase. Upon completion of the review, Dimension Data shall commence the deployment phase, which is expected to last no longer than two (2) months thereafter (“Deployment Phase”), Dimension Data shall deploy the Service to all Elements eligible for the Service as determined in Clause 4. 2.1.1. Customer shall be liable for payment of the Service during the Deployment Phase in accordance with Schedule 1.
View Source
Deployment Phase. To deploy the solution, SSP will travel onsite to DME offices for ~three days. It is expected that Clevest would also be present onsite for this implementation, testing, and validation exercise. SSP will install the integration code into the client production environment. For the balance of the visit, SSP will provide onsite production support as DME users test and validate the new functionality utilizing the Clevest software against their Responder environment. Any issues will be addressed by either SSP or Clevest as needed to ensure that the integration is working as designed. DME will be expected to validate that the functionality meets the design documentation and operates correctly. Finally, upon completion of the onsite trip, SSP will provide remote support for the solution, up to 40 hours, over the following 10 business days. If support is required beyond the 10 business days or the 40 hours (whichever is achieved first) a change order may be required. At the completion of the offsite support period, the integration project will be considered complete.
View Source
Deployment Phase 
View Source

Related to Deployment Phase

  • Deployment If the Tenant is deployed with a military unit for a period of not less than 90 days.

  • Development Phase contractual phase initiated with the approval of ANP for the Development Plan and which is extended during the Production Phase while investments in ▇▇▇▇▇, equipment, and facilities for the Production of Oil and Gas according to the Best Practices of the Oil Industry are required.

  • Design Development Phase 1.3.1 Based on the approved Schematic Design Documents, model(s) and any adjustments to the Program of Requirements, BIM Execution Plan or Amount Available for the Construction Contract authorized by the Owner, the Architect/Engineer shall prepare, for approval by the Owner and review by the Construction Manager, Design Development Documents derived from the model(s) in accordance with Owner’s written requirements to further define and finalize the size and character of the Project in accordance with the BIM Execution Plan, “Facility Design Guidelines” and any additional requirements set forth in Article 15. The Architect/Engineer shall review the Design Development documents as they are being modeled at intervals appropriate to the progress of the Project with the Owner and Construction Manager at the Project site or other location specified by Owner in the State of Texas. The Architect/Engineer shall utilize the model(s) to support the review process during Design Development. The Architect/Engineer shall allow the Construction Manager to utilize the information uploaded into Owner’s PMIS to assist the Construction Manager in fulfilling its responsibilities to the Owner. 1.3.2 As a part of Design Development Phase, Architect/Engineer shall accomplish model coordination, aggregation and “clash detection” to remove conflicts in design between systems, structures and components. Architect/Engineer shall utilize Owner’s PMIS to accomplish model coordination and collaborate with Construction Manager in the resolution of critical clashes identified by the Construction Manager. Architect/Engineer shall demonstrate and provide written assurance to Owner that conflicts/collisions between models have been resolved. 1.3.3 The Architect/Engineer shall review the Estimated Construction Cost prepared by the Construction Manager, and shall provide written comments. 1.3.4 Before proceeding into the Construction Document Phase, the Architect/Engineer shall obtain Owner’s written acceptance of the Design Development documents and approval of the mutually established Amount Available for the Construction Contract and schedule. 1.3.5 The Architect/Engineer shall prepare presentation materials including an animation derived from the model(s) as defined in “Facility Design Guidelines” at completion of Design Development and if so requested shall present same to the Board of Regents at a regular meeting where scheduled within the state. 1.3.6 The Architect/Engineer shall prepare preliminary recommended furniture layouts for all spaces where it is deemed important to substantiate the fulfillment of program space requirements, or to coordinate with specific architectural, mechanical and electrical elements. 1.3.7 Architect/Engineer shall assist the Owner, if requested, with seeking approval of the Project by the Texas Higher Education Coordinating Board (THECB). Such assistance shall include (i) the preparation of a listing of the rooms and square footages in the Project, and (ii) the preparation of project cost information, in accordance with THECB Guidelines. This information shall be provided at the completion of the Design Development Phase when requested by the Owner. The listing of rooms and square footages shall then be updated to reflect any changes occurring during construction and provided to the Owner at Substantial Completion. 1.3.8 At the completion of the Design Development Phase, or such other time as Owner may specify to Architect/Engineer, at Owner’s sole option and discretion, Owner will furnish Architect/Engineer with a Guaranteed Maximum Price proposal prepared by Construction Manager based upon the Design Development documents prepared by the Architect/Engineer and approved by the Owner. The Architect/Engineer shall assist the Owner and endeavor to further and advocate the Owner’s interests in Owner’s communications with the Construction Manager in an effort to develop a Guaranteed Maximum Price proposal acceptable to Owner, in Owner’s sole option and discretion. If the Owner does not accept the Construction Manager’s Guaranteed Maximum Price proposal, the Architect/Engineer shall participate with the Owner and Construction Manager in constructability reviews and shall revise the documents as necessary in order to reach an agreement. If the Construction Manager’s Guaranteed Maximum Price proposal exceeds the Schematic Design Phase Estimated Construction Cost prepared by, or otherwise accepted by the Construction Manager due to an increase in the scope of the Project caused by further development of the design documents by the Architect/Engineer to the extent that such could not be reasonably inferred by the Construction Manager from the Schematic Design documents, and Owner directs Architect/Engineer to revise the documents, the Architect/Engineer shall revise the documents at its own expense so that the Guaranteed Maximum Price proposal for constructing the Project shall not exceed the Owner’s Amount Available for the Construction Contract and any previously approved Estimated Construction Costs. If it is determined to be in the Owner’s best interest, instead of requiring the Architect/Engineer to revise the Drawings and Specifications, the Owner reserves the right to accept a Guaranteed Maximum Price proposal that exceeds the stipulated Amount Available for the Construction Contract. The Architect/Engineer shall analyze the final Guaranteed Maximum Price proposal document, together with its supporting assumptions, clarifications, and contingencies, and shall submit a detailed written analysis of the document to the Owner. Such analysis shall include, without limitation, reference to and explanation of any inaccurate or improper assumptions and clarifications. The A/E will not be required to make revisions to the documents at its own expense under the provisions of this paragraph if the Owner’s rejection of the Guaranteed Maximum Price proposal is not due to a failure of the A/E to provide the services otherwise required herein. 1.3.9 After the Guaranteed Maximum Price has been accepted, the Architect/Engineer shall incorporate necessary revisions into the Design Development documents. The A/E will not be required to make revisions to the documents at its own expense under the provisions of this paragraph if the revisions are required as the result of inaccurate assumptions and clarifications made in the development of the Guaranteed Maximum Price proposal that are not due to a failure of the A/E to provide the services otherwise required herein.

  • Programming Phase Schematic Design Phase: 2.2.1.3. Design Development Phase:

  • Production Phase contract period in which the Development and the Production are to be performed.