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.
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.
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.
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.
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.
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.
Deployment Phase
