Concept of Operations (CONOPS)

A Concept of Operations (CONOPS) is a user-oriented document that describes the characteristics of a proposed system or capability from the perspective of those who will operate, maintain, and interact with it, defining how the system will be used to accomplish its intended mission in the actual operational environment.

What is a Concept of Operations?

The CONOPS is typically one of the first documents produced in a new system's development lifecycle, often preceding detailed requirements definition. It describes: the operational environment in which the system will function, the tasks and activities the system must support, the organizations and personnel who will use the system, how the system integrates with other systems and processes, and what operational scenarios the system must handle, including normal operations, contingency operations, and emergency scenarios.

For DoD programs, the CONOPS is developed by the operational user (the warfighter) and is a primary input to the Capability Development Document (CDD). For civilian agency programs, the CONOPS is often developed by the program office in collaboration with end users as part of the requirements development process.

Contractors proposing on new system development must demonstrate in their proposals that they understand the operational context described in the CONOPS. Proposal evaluators assess whether the contractor's technical approach is aligned with the operational realities described in the CONOPS, a generic technical approach that ignores operational constraints is a significant proposal weakness.

Why the CONOPS matters for government contractors

The CONOPS is the user's voice in the development process. Contractors who deeply understand and reference the CONOPS in their technical approach build credibility with evaluators. During development, the CONOPS provides the human-centered requirements context that keeps design decisions grounded in operational reality rather than technical elegance alone.

Example

The Air Force publishes a CONOPS for a new close air support communications system describing how ground controllers in contested environments will coordinate with aircraft under electronic jamming conditions, with limited communications windows and rapidly changing target situations. A contractor's proposal that demonstrates system design choices driven by these specific operational constraints, ruggedized hardware, offline capability, rapid data transmission in compressed burst mode, is more compelling than a proposal focused primarily on technical specifications without operational context.

Frequently Asked Questions

Who writes the CONOPS for a government acquisition program?

For DoD programs, the operational user community (the warfighter) writes the CONOPS with support from concept development and experimentation activities. For civilian programs, the program office works with stakeholders and end users to document operational needs. Contractors do not write the CONOPS; they respond to it.

How does the CONOPS relate to the System Requirements Specification?

The CONOPS is user-focused and describes operational needs in terms of tasks, missions, and scenarios. The System Requirements Specification (SRS) is engineering-focused and translates those operational needs into specific, testable system requirements. The CONOPS feeds the SRS; the SRS feeds detailed design.

Is a CONOPS the same as an operational architecture?

No. The CONOPS is a narrative description of operational use. An operational architecture (such as those produced using DoD Architecture Framework, DoDAF) provides formalized graphical and structured models of operational activities, information flows, and organizational relationships. The CONOPS informs the operational architecture.

Can a contractor develop its own CONOPS as part of an unsolicited proposal?

Yes. When a contractor is proposing an innovative system through an unsolicited proposal or a commercial solutions opening, it may develop its own CONOPS to describe how the proposed capability would be used and what operational problems it addresses. A contractor-developed CONOPS helps government evaluators understand the proposed operational value and the user interactions the system must support.