Contents
- Cover Page
- Table of Contents
- 1.0 Introduction
- 1.1 Project Description
- 1.2 Overview of the Envisioned System
- 2.0 Documents
- 2.1 Applicable Documents
- 2.2 Reference Documents
- 3.0 Description of Envisioned System
- 3.1 Needs, Goals and Objectives of Envisioned System
- 3.2 Overview of System and Key Elements
- 3.3 Interfaces
- 3.4 Modes of Operations
- 3.5 Proposed Capabilities
- 4.0 Physical Environment
- 5.0 Support Environment
- 6.0 Operational Scenarios, Use Cases and/or Design Reference Missions
- 6.1 Nominal Conditions
- 6.2 Off-Nominal Conditions
- 7.0 Impact Considerations
- 7.1 Environmental Impacts
- 7.2 Organizational Impacts
- 7.3 Scientific/Technical Impacts
- 8.0 Risks and Potential Issues
- Appendix A: Acronyms
- Appendix B: Glossary of Terms
Appendix A Acronyms
Appendix B Glossary
Appendix C How to Write a Good Requirement— Checklist
Appendix D Requirements Verification Matrix
Appendix E Creating the Validation Plan with a Validation Requirements Matrix
Appendix F Functional, Timing, and State Analysis
Appendix G Technology Assessment/Insertion
Appendix H Integration Plan Outline
Appendix I Verification and Validation Plan Outline
Appendix J SEMP Content Outline
Appendix K Technical Plans
Appendix L Interface Requirements Document Outline
Appendix M CM Plan Outline
Appendix N Guidance on Technical Peer Reviews/Inspections
Appendix O Reserved
Appendix P SOW Review Checklist
Appendix Q Reserved
Appendix R HSI Plan Content Outline
Appendix S Concept of Operations Annotated Outline
Appendix T Systems Engineering in Phase E
This Concept of Operations (ConOps) annotated outline describes the type and sequence of information that should be contained in a ConOps, although the exact content and sequence will be a function of the type, size, and complexity of the project. The text in italics describes the type of information that would be provided in the associated subsection. Additional subsections should be added as necessary to fully describe the envisioned system.
Cover Page
Table of Contents
1.0 Introduction
1.1 Project Description
This section will provide a brief overview of the development activity and system context as delineated in the following two subsections.
1.1.1 Background
Summarize the conditions that created the need for the new system. Provide the high-level mission goals and objective of the system operation. Provide the rationale for the development of the system.
1.1.2 Assumptions and Constraints
State the basic assumptions and constraints in the development of the concept. For example, that some technology will be matured enough by the time the system is ready to be fielded, or that the system has to be provided by a certain date in order to accomplish the mission.
1.2 Overview of the Envisioned System
This section provides an executive summary overview of the envisioned system. A more detailed description will be provided in Section 3.0
1.2.1 Overview
This subsection provides a high-level overview of the system and its operation. Pictorials, graphics, videos, models, or other means may be used to provide this basic understanding of the concept.
1.2.2 System Scope
This section gives an estimate of the size and complexity of the system. It defines the system’s external interfaces and enabling systems. It describes what the project will encompass and what will lie outside of the project’s development.
2.0 Documents
2.1 Applicable Documents
This section lists all the documents, models, standards or other material that are applicable and some or all of which will form part of the requirements of the project.
2.2 Reference Documents
This section provides supplemental information that might be useful in understanding the system or its scenarios.
3.0 Description of Envisioned System
This section provides a more detailed description of the envisioned system and its operation as contained in the following subsections.
3.1 Needs, Goals and Objectives of Envisioned System
This section describes the needs, goals, and objectives as expectations for the system capabilities, behavior, and operations. It may also point to a separate document or model that contains the current up-to-date agreed-to expectations.
3.2 Overview of System and Key Elements
This section describes at a functional level the various elements that will make up the system, including the users and operators. These descriptions should be implementation free; that is, not specific to any implementation or design but rather a general description of what the system and its elements will be expected to do. Graphics, pictorials, videos, and models may be used to aid this description.
3.3 Interfaces
This section describes the interfaces of the system with any other systems that are external to the project. It may also include high-level interfaces between the major envisioned elements of the system. Interfaces may include mechanical, electrical, human user/operator, fluid, radio frequency, data, or other types of interactions.
3.4 Modes of Operations
This section describes the various modes or configurations that the system may need in order to accomplish its intended purpose throughout its life cycle. This may include modes needed in the development of the system, such as for testing or training, as well as various modes that will be needed during it operational and disposal phases.
3.5 Proposed Capabilities
This section describes the various capabilities that the envisioned system will provide. These capabilities cover the entire life cycle of the system’s operation, including special capabilities needed for the verification/validation of the system, its capabilities during its intended operations, and any special capabilities needed during the decommissioning or disposal process.
4.0 Physical Environment
This section should describe the environment that the system will be expected to perform in throughout its life cycle, including integration, tests, and transportation. This may include expected and off-nominal temperatures, pressures, radiation, winds, and other atmospheric, space, or aquatic conditions. A description of whether the system needs to operate, tolerate with degraded performance, or just survive in these conditions should be noted.
5.0 Support Environment
This section describes how the envisioned system will be supported after being fielded. This includes how operational planning will be performed and how commanding or other uploads will be determined and provided, as required. Discussions may include how the envisioned system would be maintained, repaired, replaced, it’s sparing philosophy, and how future upgrades may be performed. It may also include assumptions on the level of continued support from the design teams.
6.0 Operational Scenarios, Use Cases and/or Design Reference Missions
This section takes key scenarios, use cases, or DRM and discusses what the envisioned system provides or how it functions throughout that single-thread timeline.
The number of scenarios, use cases, or DRMs discussed should cover both nominal and off-nominal conditions and cover all expected functions and capabilities. A good practice is to label each of these scenarios to facilitate requirements traceability; e.g., [DRM-0100], [DRM- 0200], etc.
6.1 Nominal Conditions
These scenarios, use cases, or DRMs cover how the envisioned system will operate under normal circumstances where there are no problems or anomalies taking place.
6.2 Off-Nominal Conditions
These scenarios cover cases where some condition has occurred that will need the system to perform in a way that is different from normal. This would cover failures, low performance, unexpected environmental conditions, or operator errors. These scenarios should reveal any additional capabilities or safeguards that are needed in the system.
7.0 Impact Considerations
This section describes the potential impacts, both positive and negative, on the environment and other areas.
7.1 Environmental Impacts
Describes how the envisioned system could impact the environment of the local area, state, country, worldwide, space, and other planetary bodies as appropriate for the systems intended purpose. This includes the possibility of the generation of any orbital debris, potential contamination of other planetary bodies or atmosphere, and generation of hazardous wastes that will need disposal on earth and other factors. Impacts should cover the entire life cycle of the system from development through disposal.
7.2 Organizational Impacts
Describes how the envisioned system could impact existing or future organizational aspects. This would include the need for hiring specialists or operators, specialized or widespread training or retraining, and use of multiple organizations.
7.3 Scientific/Technical Impacts
This subsection describes the anticipated scientific or technical impact of a successful mission or deployment, what scientific questions will be answered, what knowledge gaps will be filled, and what services will be provided. If the purpose of this system is to improve operations or logistics instead of science, describe the anticipated impact of the system in those terms.
8.0 Risks and Potential Issues
This section describes any risks and potential issues associated with the development, operations or disposal of the envisioned system. Also includes concerns/risks with the project schedule, staffing support, or implementation approach. Allocate subsections as needed for each risk or issue consideration. Pay special attention to closeout issues at the end of the project.
Appendix A: Acronyms
This part lists each acronym used in the ConOps and spells it out.
Appendix B: Glossary of Terms
The part lists key terms used in the ConOps and provides a description of their meaning.