Appendix J-8 Concept of Operations Template.docx

Appendix J-8

<Product / System name> Concept of Operations (CONOPS) Version <0.0>

DRAFT

Produced for:

Produced by

DATE: <MM/DD/YYYY>

Equipment type: < >

EXECUTIVE SUMMARY

Concept of Operations: <Product / System name>

Content Description: Briefly summarize the system under consideration (new technology). Include components and operations for the proposed systems. Provide a short description of the justification for the new system, how it will be used and its benefits and limitations.

PUBLICATION HISTORY

This document can be found on the OpenNet at:

https://intranet.ds.state.sbu/DS/C/ST/FSE/TDB/default.aspx Please refer to the TDB website for the latest version.

Corrections, comments, or questions should be sent to:

Table of Contents

Table of Figures

List of Tables S-AQMMA-11-R-0186 Appendix J-8 Supply Chain Management Supply Chain Management

S-AQMMA-11-R-0186 Appendix J-8 Supply Chain Management Supply Chain Management

Introduction

CONOPS Introduction

The Concept of Operations (CONOPS) document describes the components and operations of the <system / product name>. This document is only a guideline and is not considered the only method of operation. As a guideline, it is subject to change at any time.

NOTE: A CONOPS may contain some examples of typical design strategies for the purpose of clarification, but should not contain design specifications.

References

<Provide concise identifying information for all documents referenced within the CONOPS document (e.g., legislation, feasibility studies, documents concerning related projects, relevant technical documentation, etc.>

Current Overview Description of Current Situation

<Provide a clear, concise description of the current situation. The description may include any of the following as appropriate:

· Background (as needed)

· The operational environment, e.g., facilities, equipment, personnel

· Major components and the interconnection among those components

· Interfaces to external situation

· Flow charts and accompanying descriptions from the user’s point of view

· Cost of operations

· Operational risk factors

· Performance characteristics, such as speed, volume, frequency, availability, reliability

· Provisions for safety and security

· Current Users and Stakeholders

The description may include some type of diagram that depicts the overview and its environment. >

Justification for New Technology

Justification for Changes

<Briefly summarize the user needs, missions, objectives, etc. that require a new system. Summarize the deficiencies or limitations of the current system. Provide justification for a new or modified system (e.g., improvements, new functional capabilities).> Description of Desired Capabilities

<Summarize the new or modified capabilities, functions, processes, etc. needed to respond to the factors identified in 3.1. Changes should be based on the current system (if any) described in Section 2 of this document.> Priorities among Changes

<Identify priorities among the desired changes and new features. Each change should be classified as essential, desirable, or optional and a reason provided for the classification.> Changes Considered But Not Included

<Identify desired changes and new features considered but not included in section 3.2 and the rationale for not including them.>

Proposed Technology

Description of the Proposed System

<Provide a clear, concise description of the proposed system. The description should include any of the following as appropriate:

· Background (as needed)

· Cost of technology/system, operations, and associate expenses

· The operational environment, e.g., facilities, equipment, personnel

· Major system components and the interconnection among those components

· Interfaces to external systems

· Flow charts and accompanying descriptions from the user’s point of view

· Operational risk factors

· Performance characteristics, such as speed, volume, frequency, availability, reliability

· Provisions for safety and security

· Anticipated users and stakeholders

The description may include some type of diagram that depicts the system and its environment. >

Operational Scenarios

<Provide step-by-step descriptions of how the proposed system should operate and interact with its users and external interfaces under a given set of circumstances. The scenarios should be described in a manner that will allow readers to walk through them and gain an understanding of how all the various parts of the proposed system function.

The scenarios tie together all parts of the system by describing how they interact. The scenario may also be used to describe what the system should not do.

Each scenario should include events, actions, stimuli, information, and interactions as appropriate to provide a comprehensive understanding of the operational aspects of the proposed system. The scenarios can be presented in several different ways:

1. For each major processing function of the proposed system

2. Thread-based, where each scenario follows one transaction through the proposed system

3. Following the information flow through the system for each user capability

The number of scenarios and level of detail specified will be proportional to the perceived risk and the criticality of the project. The scenarios developed for the CONOPS can serve as the basis for the subsequent System Requirements Specification document, Case Testing Necessities/Specifications, and Users Manual.>

Summary of Impacts

Operational Impacts

<The impacts to consider include the following:

· Changes in procedures

· New modes of operation based on emergency, disaster, or accident conditions

· New methods for providing feedback

· Changes in operational budget

· Changes in operational risks Organizational Impacts

<The impacts to consider include the following:

· Modification of responsibilities

· Addition or elimination of job positions

· Training or retraining users

· Changes in numbers, skill levels, position identifiers, or locations of personnel Impacts during Development

<The impacts to consider include the following:

· Involvement in studies, meetings, and discussions prior to evaluation

· User and support involvement in reviews and demonstrations, evaluation of initial operating capabilities, and evolving versions of the system, development or modification of databases, and required training

· Parallel operation of the new and existing systems (if any)

· Operational impacts during system testing of the proposed system

Analysis of the Proposed System

Disadvantages and Limitations

<Provide a qualitative (and to the extent possible, quantitative) summary of the disadvantages and/or limitations of the proposed system. Disadvantages might include the need to retrain personnel or change to a new style of user interface.

Limitations might include features desired by users but not included, or a response time that is greater-than desired due to hardware constraints.> Alternatives and Trade-Offs Considered

<Describe major alternatives considered, the trade-offs among them, and the rationale for the decisions reached. In the context of the CONOPS, alternatives are operational alternatives, not design alternatives, except to the extent that design alternatives may be limited by the operational capabilities desired in the new system.>

Appendices

Use appendices to facilitate ease of use and maintenance of the CONOPS document.

Each appendix should be referenced in the main body of the document where that information would normally have been provided.

S-AQMMA-11-R-0186 Appendix J-8 Supply Chain Management

S-AQMMA-11-R-0186 Appendix J-8 Supply Chain Management

<Month date, year>

UNCLASSIFIED

ACTION MEMORANDUM FOR DS/ST/FSE, MR. MICHAEL J. BARELA

FROM: DS/FSE/TDB – Warren Garrett

SUBJECT: <Product name> Concept of Operations (CONOPS) Decision

Recommendation:

That you authorize DS/FSE/TDB, to move to the next phase of the <product name> evaluation flow, system requirements specification.

Approve_________________ Disapprove_________________

Summary:

This concept of operations (CONOPS) describes the components and operations of the proposed new technology to answer the requirements of the client for a(n) <equipment type>, TDB Technology Needs Assessment dated <month date, year>. Identification of specific system requirements for the new technology is recommended by the Technology Development Branch (DS/FSE/TDB) test and evaluation staff. If chosen to move forward, a system requirements specification document will be generated.

image1.png image2.png image3.png