over the network as an automatically installable download). If, however, the capability is complex, and especially if there are interdependencies with other programs, complex installation procedures not suitable for “point-and-click” installation by the end user, and/or unique training requirements, significant planning and effort may be required to deploy the capability. This is especially the case for deployable or deploying units because the capability deployment activities of the acquisition program must then be integrated into the overall operational employment schedule for each unit. In that case, capability deployments will generally be planned during the periods between a unit’s operational deployments so that training can be conducted prior to the workup process preceding the next operational unit deployment to a forward area of responsibility.
During the Deployment Phase for these more complex cases, the PM must perform the detailed coordination with the operating forces to plan, schedule, and execute capability deployment activities including preparatory work, pre-installation test and checkout specific to each installation, installation, post-installation operational validation, training, and, if appropriate, integration validation with other interdependent capabilities (for example, across a portfolio). In Figure 3.2, the end of the Deployment Phase for an increment is aligned with the Milestone C decision for the next increment since generally, the subsequent increment will represent improved capability and, once it is available, should be utilized for subsequent deployments whenever possible.
The purpose of the Operations and Sustainment Phase is to support all previously deployed versions of a capability still in operational use. This support includes activities such as operating an end-user help desk and responding to problems encountered in operational use of the capability, including the development and distribution of patches and maintaining a configuration status accounting baseline for all installations of the capability. This phase also includes the collection of metrics built into the deployed capability such as data on utilization of specific features, so that unused elements of the capability can be removed.
This phase is shown with an indeterminate duration in Figure 3.2, since the complexities discussed above in conjunction with the Deployment Phase will, in general, result in multiple versions in use at any given point in time. Even in the simplest case, when end-user “point-and-click” automatic download and installation is the deployment approach, a predetermined interval is typically necessary to allow time for the installed base of end users to update their installations prior to terminating support for previously released versions, as is often the case in commercial software applications.