Supportability Maturity Level gates

Gate
Triplet
Definition
Edit
1
Operational Requirements Document
ORD

Operational requirements must be defined in a quantitative and qualitative way. Supportability requirements are developed directly from the operational requirements. Each supportability requirement should be based on an operational requirement, and that relationship should be clearly identified.

2
Usage Requirements Document
URD

To ensure the proper usage of the Product, the customer should consider all the logistic requirements. The logistician can most efficiently influence the supportability and design of a newsystem during its early stages of development.

3
System Requirements Document
SRD

The SRD defines the system requirements that meet user needs. The IPS manager must: Ensure that the SRD is supported by the IPSP that details the IPS strategy developed by the IPS team in response to the ORD and URD IPS requirements and identifies and justify supportability objectives. Include supportability aspects in the requirements repository which forms the basis of the SRD Ensure that supportability issues are addressed. The IPS manager will put forward the justification for the inclusion of the supportability requirements statement as one of the key product requirements for the Product or service.

4
Guidance Conference Document
GCD

The GC must be the central event with participation of management staff and specialists from both the customer and the IPS provider. At this conference, the binding agreements for the performance of the IPS activities must be established. To ensure best performance of this conference, it is necessary to have prepared inputs and to have a clear expectation of the results and final agreements. Through the potential procurement process the Statement Of Work (SOW) is negotiated until final bids can be made. The GCD is an agreed and contractual based agreement of what industry must provide and therefore an essential part of the SOW.

5
System Requirements Review
SRR

Initial system capabilities and supportability objectives/requirements have been analyzed and allocated to downstream product elements. Initial RAMCT strategy has been formulated and integrated with the system engineering process. The IPSP is updated accordingly. Design features to achieve the product IPS strategy, including diagnostics and prognostics, are incorporated into system performance specifications. The Test, Verification and Evaluation Plan (TVEP) addresses when and how required IPS related design features and key performance indicators/measures will be verified.

6
Preliminary Design Review
PDR

The PDR demonstrates that the preliminary design meets all Product requirements with acceptable risk and within the cost and schedule constraints and establishes the basis for proceeding with detailed design. It will show that the correct design options have been selected, interfaces have been identified, and verification methods have been described. The IPS provider must address the IPS planning and management of requirements, defining IPS requirements, major cost drivers and risks. Respective evidence must be provided. IPS activities to develop IPS system alternatives and determining the optimum solution using analysis must underpin the evidence with facts.

7
Critical Design Review
CDR

The CDR demonstrates that the maturity of the design is such that it can proceed with prototyping, assembly, integration and test. IPS element requirements are integrated, finalized and consistent with the approved system design and IPS concept. Validation that the design conforms to IPS requirements. Metrics are predicted based on CDR results and projected to supply chain performance.

8
Final Acceptance Review
FAR

The FAR demonstrates that the Product IPS planning is completed. The in-service strategy, roles, responsibilities, and partnerships are identified and are ready to be implemented. Design inherent Product IPS capabilities like RAMC- T or technical documentation must be tested and demonstrated to validate the supply chain performance and IPS products. Budget requirements are adjusted based on the design and test results

9
Support Solution Review
SSR

Applicable to: All The SSR demonstrates that the IPS capabilities (including associated support processes and products) are proven in an operational environment. SML Milestone/Decision gate Definition For validation purposes it is likely to involve evidence from engineering evaluation and test and demonstration of the IPS system. A Logistic Demonstration (LogDemo) must be carried out which will form part of the TVEP. IPS systems and products must be delivered to the operational site. Key performance indicators must be measured against agreed availability, materiel reliability, ownership cost and other IPS metrics. Needed improvement actions are taken based on performance data.

10
Product Delivery/In-Service Date
ISD

The ISD is defined as the date at which the IPS system is in place in range and scale to meet and sustain the INTO requirements. The ISD also includes the Product Support date (PSD). IPS systems and services are delivered and fully integrated into the operational environment. IPS in-service products like warehousing and depot maintenance are in place.

11
In Service Review
ISR

The ISR should be carried out to verify that the IPS system is working. The Product IPS performance must be regularly measured against metrics and corrective actions should be taken. Product improvement, modifications, upgrades must be planned. The IPS concept is refined leveraging the best value mix of organic and contractor IPS for logistics processes, services and products according to changing environment and customer needs.

12
Out of Service Date
OSD

Applicable to: All This is the date from which the Product will be decommissioned according to the disposal plan.