Concept of Operations/Operational Mode Summary/Mission Profile (CONOPS/OMS/MP)
Did you know that the recently updated versions of both DoDI 5000.02 (January 2015) and the JCIDS Manual (February 2015) focus attention on the Concept of Operations/Operational Mode Summary/Mission Profile (CONOPS/OMS/MP). Specifically:
· DoDI 5000.02, Materiel Solution Analysis Phase, Para 5.d.(2)3. (page 17) “Prior to the completion of this phase, the DoD Component combat developer will prepare a Concept of Operations/Operational Mode Summary/Mission Profile (CONOPS/OMS/MP) that will include the operational tasks, events, durations, frequency, operating conditions and environment in which the recommended materiel solution is to perform each mission and each phase of a mission. The CONOPS/OMS/MP will be provided to the Program Manager and will inform development of the plans for the next phase including: acquisition strategy, test planning, and capability requirements trades. It will be provided to industry as an attachment for the next acquisition phase RFP.”
· DoDI 5000.02, Enclosure 1, Table 2 (page 50) “Regulatory. The CONOPS/OMS/MP is a Component approved acquisition document that is derived from and consistent with the validated/approved capability requirements document. The CONOPS/OMS/MP describes the operational tasks, events, durations, frequency and environment in which the materiel solution is expected to perform each mission and each phase of the mission. The CONOPS/OMS/MP will be provided to the MDA at the specified decision events and normally provided to industry as part of the RFP.”
· JCIDS Manual, Appendix A, Enclosure D, Page D-A-5, Para 4 “CONOPS Update and/or OMS/MP documentation.
a. Additional data required. If not already contained within the CONOPS used during the CBA, the following information must be provided – as an update to the associated CONOPS and/or as OMS/MP documentation:
(1) Typical mission scenarios or profiles for each mission. The profiles should state specific amounts of operation (hours, rounds, miles, cycles, etc.) for each mission essential function within the mission.
(2) When appropriate, the CONOPS should address special conditions of use, such as any unique high-intensity cycles of use within a mission.
(3) Expected breakdown of environmental conditions.
(4) Total operating time for expected missions.
b. Data submission. Updates to CONOPS and/or OMS/MP documentation will be provided with the submission of CDDs and CPDs unless already available on the KM/DS system.
c. Follow-on usage. The additional detail provides traceability for the combinations of KPPs, KSAs, and APAs in the CDD (including the draft CDD supporting MS A) and the CPD. It also provides a baseline of specific mission performance to ensure T&E later in the acquisition process can directly measure missions intended by the warfighter.
What does this mean for the life cycle logistician and product support manager? We need to be familiar with the CONOPS and/or OMS/MP documentation for not only the reasons outlined in the DoDI 5000.02 and JCIDS Manuals, but because of the implications for our product support strategies. The CONOPS and/or OMS/MP serves as a key source document for developing and updating your Life Cycle Sustainment Plan (LCSP). Additionally, it is a key source of information about the operational environment and how the system will be used, operated, and employed. Indeed the LCSP Outline template specifically acknowledges this, indicating:
· Planning for product support begins at system initiation and builds on system information documented in other requirements and acquisition deliverables available, such as the…CONOPS…. (Section 3, Product Support Strategy)
· Example of considerations and cost drivers (Table 3-2) that impact affordability of the Sustainment Strategy. (Section 3.1 Sustainment Strategy Considerations)
The DoD Product Support Manager’s (PSM) Guidebook goes on to discuss CONOPS in the context of a “day in the life” scenario, saying
· Operational CONOPs. Conduct a “Day in the Life” use-case scenario to understand how the system might be supported in an operational environment (5.2.2. Sustainment Maturity Levels (SML) in the MSA Phase)
· Operational CONOPs. Expand the “Day in the Life” use-case scenarios developed previously to include sparing levels, fleet sizes, operator and maintainer training, operating locations, manpower, information technology infrastructure, support equipment plans, and operating tempos.(Para 5.3.2. Sustainment Maturity Levels in the TD Phase)
For further information, check out our Concept of Operations (CONOPS) ACQuipedia article.