3. DESCRIPTION/PURPOSE OF THE CONOPS
3.1 The Concept of Operations (CONOPS/OSD) describes the conceptual approach to achieving an enterprise outcome or capability, focussing on operations, as contrasted to the whole of the solution to the whole of the problem on a life cycle
basis. The CONOPS/OSD also may contain a description of solution or solution element external behavior (how the solution/solution element will behave, from a user's point of view, in meeting its requirements, to the extent that the design defines behavior more detailed than, and consistent with, solution requirements, and ignoring internal implementation).
3.2 The CONOPS/OSD is used to communicate the conceptual solution within the solution development team, to internal and external stakeholders (especially to system and solution element users), to independent verifiers, to acquirers of
solution elements, maintainers and modifiers, as applicable. The term “system” is used throughout section 5.2 “Content Requirements”, to mean the solution, within the scope of the CONOPS/OSD, to provision of the outcome or capability.
3.3 Note that a CONOPS/OSD is not an Operational Concept Description (OCD) – see PPA-000950.
Defines standard
Replaced/Superseded by document(s)
Cancelled by
Amended by
| File | MIME type | Size (KB) | Language | Download | |
|---|---|---|---|---|---|
| PPA-004023-7 PPI DID (CONOPS_OSD) 201116_0.pdf | application/pdf | 302.5 KB | English | DOWNLOAD! |
Provides definitions
Cover images
Extract(s)
The Concept of Operations (CONOPS) describes the conceptual approach to achieving an enterprise
outcome or capability, focussing on operations, as contrasted to the whole of the solution to the whole of
the problem on a life cycle basis. The CONOPS also may contain a description of solution or solution
element external behaviour (how the solution/solution element will behave, from a user's point of view, in
meeting its requirements, to the extent that the design defines behaviour more detailed than, and consistent
with, solution requirements, and ignoring internal implementation).
The CONOPS is used to communicate the conceptual solution within the solution development team, to
external stakeholders (especially to users), to independent verifiers, to acquirers of solution elements,
maintainers and modifiers, as applicable.
Alternative to the CONOPS, a System/Subsystem Design Description (SSDD) to DID PPA-003461 may be
used. The SSDD describes the whole of the architectural (conceptual) design to the whole of the problem
definition (not just the operational aspects of the problem definition). Thus, the SSDD is of broader scope
than the CONOPS. The content of the CONOPS is subsumed within this broader scope.