4.2.17. In-Service Review
4.2.17. In-Service Review
The In-Service Review (ISR) is a multidisciplined assessment to characterize the in-service health of the deployed system and enabling system elements (training, user manuals, documentation, etc.). The ISR provides feedback to the Program Manager on how well the system is delivering the capability to the warfighter, with acceptable operational performance. In addition, the feedback substantiates in-service support budget priorities.
DoDI 5000.02, Enclosure 2, 8.c.(1)(f) requires DoD Components to conduct continuing reviews to compare expected performance to actual performance. The ISR is typically conducted shortly after Initial Operational Capability (IOC); however, the Program Manager should schedule additional ISRs with the end user until the system is retired. Typical focus areas for additional ISRs might include: modifications, upgrades, product improvement, technology refresh, and technology insertion (see DAG Chapter 5 Life-Cycle Logistics for additional information). Additional ISRs are typically critical for systems that change more frequently, such as commercial-off-the-shelf and software-intensive systems. The DoD ISR Checklist can be used to plan and implement this review.
Roles and Responsibilities
The Program Manager establishes the relationships between the developer and the end-user to facilitate system feedback and assessment. In addition, the Program Manager determines priorities and approves changes and implementation plans.
The Systems Engineer supports efforts to translate end user feedback into corrective action plans for possible modifications, technology refresh and/or insertion, Diminishing Manufacturing Sources and Material Shortages (DMSMS) issues, and other types of system or system element improvements.
The ISR can be used to:
- Assess risk in the operational environment
- Identify trends in metrics to substantiate in-service budget or corrective actions
Inputs and Review Criteria
Figure 4.2.17.F1 provides the end-to-end perspective and the integration of SE technical reviews and audits across the acquisition life cycle.
Figure 4.2.17.F1. Weapon System Development Life Cycle
![Figure 4.2.17.F1. Weapon System Development Life Cycle Figure 4.2.17.F1. Weapon System Development Life Cycle](https://webarchive.library.unt.edu/web/20170211064828im_/https://acc.dau.mil/GetRichTextImage.aspx?id=638324&imageid=b27b0ba8-7fbb-43e6-ac32-85f96ab8a348)
To enter an ISR, the review should not begin until these criteria are considered met:
-
IOC status has been reached
-
System hazard risk assessment has been performed (see DAG section 4.3.18.9. Environment, Safety, and Occupational Health)
-
Trend assessment has been performed for preplanned technical metrics
Outputs and Products
The Technical Review Chair determines when the review is complete. The ISR should result in a plan of corrective action for all issues recommended by the Systems Engineer as warranting resolution. Areas of particular interest usually include:
- System problems are categorized and support the operating and support requirements determination process
- Required budgets (in terms of work years) are established to address all system problems in all priority categories
- Current levels of system operational risk and system readiness are quantified and related to current operations and systems and procurement budgets
- Future levels of system operational risk and system readiness are quantified and related to future operations and systems and procurement budgets