Aconcept of operations (abbreviatedCONOPS,CONOPs,[1] orConOps[2]) is a document describing the characteristics of a proposedsystem from the viewpoint of an individual who will use that system. Examples includebusiness requirements specification orstakeholder requirements specification (StRS). CONOPS is used to communicate thequantitative andqualitative system characteristics to allstakeholders.[2] CONOPS are widely used in the military, governmental services and other fields.
A CONOPS generally evolves from aconcept and is a description of how a set ofcapabilities may be employed to achieve desiredobjectives or end state.[1]
Concept of Operations documents can be developed in many different ways but usually share the same properties. In general, a CONOPS will include the following:[3]
A CONOPS should relate anarrative of the process to be followed inimplementing a system. It should define the roles of the stakeholders involved throughout the process. Ideally it offers clearmethodology to realize the goals and objectives for the system, while not intending to be an implementation or transition plan itself.[3]
CONOPS standards are available to guide the development of a CONOPS document.[4][5] TheInstitute of Electrical and Electronics Engineers (IEEE) Standard is structured aroundinformation systems, but the standard may be applied to other complex systems as well.
The first standard was1362-1998 - IEEE Guide for Information Technology - System Definition - Concept of Operations (ConOps) Document that was superseded by the document29148-2011 - ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle processes --Requirements engineering.
Then came the 2012 AIAA revision proposalGuide: Guide to the Preparation of Operational Concept Documents (ANSI/AIAA G-043A-2012) (Revision of G-043-1992), and today we haveISO/IEC/IEEE 15288:2015 Systems and software engineering -- System life cycle processes.
In the field of jointmilitary operations, a CONOPS inDoD terminology is a verbal or graphic statement that clearly and concisely expresses what the joint force commander intends to accomplish and how it will be done using available resources.[6][7] CONOPS may also be used or summarized in system acquisitionDODAF descriptions such as theOV-1 High Level Operational Concept Graphic.[8]
