Read Now, Latest Guide + Template: Establishing a CONOPs
DOWNLOAD
Your Mission
HomepageCONOPs Guide + Template
All news

Establishing A CONOPs For ISR Design And Development

// 09.03.2024
// Your mission first

Explanatory Guide

Introduction

Implementing or upgrading an ISR capability is a significant and complex project. Platform, sensor, and mission management selection are interdependent variables demanding a deep understanding of end-user mission requirements, desired performance levels, operating environments, locations, and use. 
Beyond immediate needs, the system design must consider future requirements, scalability, and technological improvements to remain relevant while meeting planned operational life cycles. Finally, system useability, efficiency, and interoperability with partners will define the success or otherwise of the implementation. 
Taming the complexity and integrating these diverse variables requires the context and strategic direction of the project to be set by generating a document called a concept of operations, or CONOPs. 

CONOPs Explained

The CONOPs is the first step in the design process, and it’s a document that provides a conceptual, high-level, and holistic view of a proposed system from the user’s perspective. It communicates your vision of the system for subsequent client review, feedback, and approval after several drafting and review iterations. 

A CONOPs document helps to align all stakeholders on the characteristics of a proposed new ISR system, thereby mitigating design, build, and implementation risks. When finally accepted and signed off by the client, it forms a contractual scope document that defines user requirements, guides the acquisition and development effort, and facilitates system integration. 

In simple terms, a CONOPs addresses the “why” and high-level “what” of a new ISR system, becoming an input into the next step in the design process, which is a lower-level and more granular requirements analysis that defines the “how.” 

Understanding a CONOPs also requires understanding what it is not. It is not a requirements analysis or a technical design document and should not focus on the in-depth technical aspects of a system or include detailed technical design information other than that necessary to convey the concept or scope of the desired system to the design team.

Three Steps to Writing a CONOP

Data Collection

Writing accurate and concise CONOPs requires a comprehensive data collection process to capture stakeholder needs and expectations. Often the client will know what they wish to achieve with the new ISR system but will be unaware of the information the project team needs for optimal system development. 

The CONOPs author and colleagues are responsible for using the framing questions provided later in this document to elicit the required details from the client stakeholders. Drafting these responses into a concise, informative CONOPs narrative will guide subsequent design and development initiatives. 

Drafting/Review

Collate the data captured from the stakeholder responses into the standard CONOPs document format supplied later in this document. The data presented must be empirical and derived solely from stakeholder input, without subjective interpretation by the author. Once the first draft of the document comprises all collected information, send it to the client for formal review and feedback. 

Complex ISR systems may require multiple iterations of the draft/review/feedback cycle before the client accepts the document content. Maintain records of client feedback and use version control of subsequent drafts to ensure traceability through the CONOPs development.

Client Approval

When the client indicates acceptance of the CONOPs document, create a clean version for signed and dated approval by an authorized client representative. The approved CONOPs will form the basis for future design and development initiatives. 

Ensure subsequent revisions follow the draft, review, and approval process before advancing the document version number and reissuing the revised CONOPs to relevant stakeholders.

Suggested Framing Questions

Operational Context

The framing questions for operational context cover three key categories:

  • The system’s alignment with organizational strategy and business objectives
  • The operational environment
  • The needs of stakeholders

The questions and answers in this section are predominantly strategic or tactical.

What are the intelligence requirements and operational goals of the new ISR system?

  • You wish to understand the information the client needs and what they will use the data for. 
  • Are they simply exercising a presence, or do they need data for subsequent use? 

How do these goals align with and support the overarching business strategy and objectives?

  • Understanding the raison d’être of the organization allows you to broaden your perspective and offer holistic solutions rather than focus on the immediate ISR problem the client seeks to solve. 
  • If ISR operations are a small part of a larger operation, is there functionality, or optionality, that might support the broader organization? 
  • What is the client not doing now that they could be doing with incremental software or hardware additions? 

In what way will it augment organizational effectiveness and efficiency?

  • Is this a greenfield system rollout, is it replacing an existing system, or is it required to integrate with a legacy system? 

In what parts of the world will the system operate?

  • Localization hints at political dynamics influencing system deployment, including platform, hardware, and software choices. 
  • Are there regulatory or legal requirements that may shape or impact the operation of the ISR system? 

Describe the system’s operational domains

  • What is being surveilled, air, ground, maritime, space, or cyber 
  • If multiple domains, will operations be simultaneous or shift focus when the platform is retasked?

Over what terrain will the system operate?

  • Will it be mountainous, forested, deserts, urban areas, or dense vegetation? 
  • Are there natural or man-made features that may impact sensor coverage and line of sight? 

What platform(s) will carry the system?

  • Is it a fixed-wing aircraft, helicopter, or UAV? 
  • Do they have a specific make or model of platform selected? 
  • What is its range, endurance, altitude, and speed capabilities? 
  • How long will the platform remain on station for each tasking? 

Specifically, what will the ISR system look for?

  • The system design is defined by whether targets are fast/slow-moving or carrying out legal/illegal activities. 

Are there any unique features or modifications important to ISR operations?

  • What are the client’s pain points the system should solve?
  • Should positive capabilities experienced with previous systems be included? 

What stakeholders besides the client will have input to or receive data from the new ISR system?

  • How will the captured data be processed and disseminated to all stakeholder levels, including command and operating personnel? 
  • What will those additional stakeholders do with the system data? 
  • What components, protocols, interfaces, and infrastructure are necessary for effective communication with stakeholders and other ISR systems? 
  • Define and list a standard technical terminology that can be recognized and understood by all relevant stakeholders. 

Identify where the ISR system will interface with networks, operational systems, and decision-making processes.

  • Describe the security protocols to protect system and data integrity, reliability, and confidentiality. 

What sensor payloads, types, and capabilities will require integration into the airborne platform?

  • What type of data supports mission success, and what are the levels of detail for each? 
  • Describe how the intelligence will support and augment situational awareness and decision-making.

Outline the roles and responsibilities of those directly monitoring and managing the system.

  • What tasks and functions does each role acquit managing or operating the system? 
  • What qualifications and training will be possessed by those using the system? 
  • Describe the range of system operator capabilities and competencies. 
  • Define the performance metrics used to assess human performance. 

To provide intuitive and efficient human interaction, what considerations apply to user interfaces, displays, and control mechanisms?

  • What data visualization techniques, feedback mechanisms, and information displays will be required to support effective decision-making and enhance situational awareness? 
  • Do visual interfaces require the utilization of specific colors or symbology? 
  • To account for human capabilities and limitations, what requirements should exist for anthropometric, ergonomic, and user-centered design principles? 
  • What map sets, shapes, and overlays are required, or will the system utilize existing client assets? 
  • Explain the requirements for redundancy and error-proofing to increase system resilience and mitigate human error. 

Is there a need to integrate diverse sensor types, models, and manufacturers?

  • Given each sensor’s capabilities and the required intelligence, what sensors do you consider are required to cover all operational scenarios? 
  • Define the operational procedures for sensor activation, calibration, data acquisition, and storage. 
  • To what extent is track correlation required to combine and associate sensor data from diverse sources? 
  • What data formats and metadata requirements are needed? 

How will hardware and software be installed and upgraded?

  • What are the required maintenance checks? 
  • How will new capabilities, sensors, platforms, or upgraded hardware and software be integrated? 
  • How will the system maintain relevancy and currency as technology advances and operational needs shift? 

Define the metrics and indicators used to assess system performance

  • For example, sensor availability, data collection rates, storage capacity, and system uptime.

Outline the roles and responsibilities of those directly monitoring and managing the system.

  • What tasks and functions does each role acquit managing or operating the system? 
  • What qualifications and training will be possessed by those using the system? 
  • Describe the range of system operator capabilities and competencies. 
  • Define the performance metrics used to assess human performance. 

To provide intuitive and efficient human interaction, what considerations apply to user interfaces, displays, and control mechanisms?

  • What data visualization techniques, feedback mechanisms, and information displays will be required to support effective decision-making and enhance situational awareness? 
  • Do visual interfaces require the utilization of specific colors or symbology? 
  • To account for human capabilities and limitations, what requirements should exist for anthropometric, ergonomic, and user-centered design principles? 
  • What map sets, shapes, and overlays are required, or will the system utilize existing client assets? 
  • Explain the requirements for redundancy and error-proofing to increase system resilience and mitigate human error. 

Is there a need to integrate diverse sensor types, models, and manufacturers?

  • Given each sensor’s capabilities and the required intelligence, what sensors do you consider are required to cover all operational scenarios? 
  • Define the operational procedures for sensor activation, calibration, data acquisition, and storage. 
  • To what extent is track correlation required to combine and associate sensor data from diverse sources? 
  • What data formats and metadata requirements are needed? 

How will hardware and software be installed and upgraded?

  • What are the required maintenance checks? 
  • How will new capabilities, sensors, platforms, or upgraded hardware and software be integrated? 
  • How will the system maintain relevancy and currency as technology advances and operational needs shift? 

Define the metrics and indicators used to assess system performance

  • For example, sensor availability, data collection rates, storage capacity, and system uptime.