Write Operational Concept Description

(Activity) for Tier: Product

View Training

PURPOSE

During project planning, an Operational Concept Description (OCD) document needs to be created, capturing the problem or business need as well as the intended solution’s goals, constraints, and operational modes of the product/system to the sponsor, stakeholders, development, support, operations, and test. This document is used to provide a context and expectations for developing, deploying, maintaining, or evaluating the product and product solutions that will be delivered to the customer. The OCD describes the current system (if one exists) as well as the proposed system/solution and includes information on operational environments, interfaces, as well as the major components of the current/new systems. The OCD also provides information related to performance expectations, reliability, maintainability, availability, usability, etc. This document also captures information on the types of users, training requirements, and support concepts for facilities, equipment, and personnel required to support and maintain the system.

While the OCD Template covers all information needed within the document, not all sections of the Template will apply to every project. However, at a minimum, the initial OCD should describe:

  • Introduction to the Product/System
  • Business needs for the Product/System
  • Operational concepts related to interfaces, modes of operation, and environments
  • Security and User Access considerations
  • Usage scenarios and possible workflows
  • System constraints
  • Deployment, delivery, support, and sustainment concepts
  • Maintenance concepts, if applicable
  • Disposal concepts, if applicable

Note

The term “product” represents the overall product being developed, tested, and delivered to the customer. A system could consist of hardware, software, or a combination of both, depending upon the requirements of the contract and the needs of the customer, sponsor and the user community.

WHEN

At contract and/or task order award.

PARTICIPATING ROLES

ENTRY CRITERIA

  • Contract Statement of Work, Performance Work Statement, or Contract Task Order has been delivered.

SUB-ACTIVITIES

  1. Review Contract Documents for High-Level Requirements

    • Before writing the initial OCD, review the contract Statement of Work, the Performance Work Statement, or Task Order for specific requirements related to usage, environments, documentation, training, or other operational requirements, such as security, how users will interact with the system, or expectations for support related to the product/system.

  2. Review Business Objectives and Scenarios

    • Additional research that could help to develop an OCD might include:

      • Reviewing business objectives that describe operational and business requirements for the product/system.
      • Using existing scenarios to document the high-level operational needs of the product/system.
      • Meeting with other stakeholders and/or subject matter experts to gather additional operational scenarios or expected workflows that would apply to the product/system.

  3. Define Operational Concepts

    • Using all information gathered for the product, develop operational concepts and scenarios that include considerations and descriptions of operations, installation, development, maintenance, support, security, and disposal, as appropriate for the project’s needs.
    • Define the environment(s) in which the product or product components will operate, including boundaries, interfaces, and constraints.

  4. Write Operational Concepts Description

    • Now that you have all the information necessary, you can begin writing the OCD by:

      • Using the ISI OCD Template, create an OCD by completing all sections and paragraphs that apply to the product/system to develop an OCD that defines the current product/system, describes the proposed/new product/system, and provides a justification for the new product/system.
      • Including information on components, interfaces, security, end users, constraints, environments as well as the operational, maintenance, support, and disposal needs that pertain to the product/system being developed/delivered.

  5. Review Operational Concept Description

    • Once a draft is created, present and discuss the OCD with necessary stakeholders to ensure that all initial and planned operational concepts and scenarios are captured within the OCD.

    • Accept feedback and update OCD to capture any additional information related to the product’s operational concepts and scenarios.

      Note

      Note that developing operational concepts and scenarios are an iterative process. The OCD should also be reviewed and updated periodically throughout the life of the project to ensure that all new or updated operational scenarios are captured within the OCD as well as refining any existing concepts while discovering new requirements for the product/system.

  6. Publish the Operational Concept Description

    • Publish the OCD according to the team procedures.

OUTPUTS

EXIT CRITERIA

  • An OCD has been created that will help establish Epics and Features for requirements development and architecture analysis.

NEXT ACTIVITY

SEE ALSO

Process Guidance Version: 10.4