Course Number: 4999
Length: 5 Days
Print Friendly, PDF & Email

Military Operational Capability Concept Training | OCD Training

Military Operational Capability Concept Training,OCD training is a 5-day bootcampstyle training preparing attendees with Operational Concept and capability description, ConOps and requirements documentation.

Learn from the experts with recognized military systems engineering best practices how to develop operational concepts and new military capabilities during system development and documentation of those operational concepts in one or more operational concept documents. Learn DoD and NASA’s best practices and standard procedures to develop system operational concepts to support new capabilities leading to specification and development of systems including DoD’s Data Item Descriptions (DIDs), and NASA’s Data Requirements Documents (DRDs).

Learning Objectives

Upon completion of this course, the attendees are able to:

  • Describe military capability definition and creation
  • Describe military problem solving techniques and tools for Gap Analysis
  • Use tools to document and model new military capabilities
  • Describe systems engineering processes and tools applied
  • Work with various techniques for systems engineering, including use cases, IDEF modeling, Structured Analysis (SA), object-oriented analysis and design (OOAD), and behavioral modeling
  • Prepare OCD and ConOps
  • Develop Operational Concept Descrition (OCD) and Concepts of Operations (CONOPS)
  • Map capabilities to organization, operation and systems and System of Systems (SoS) requirements
  • Write and manage requirements
  • Map ConOps to system validation
  • Validate the mission scope and system boundaries
  • Define system boundary using mission needs, goals and objectives
  • Create operational context diagram
  • Develop OCD and operational scenarios and timelines
  • Synthesize, analyze, and assess key implementing concepts for the system and its elements
  • Map OCD and CONOPS and the System’s operational architecture
  • Tools to validate and baseline the system’s operational architecture
  • Use executable models, operational demonstration master plan and other verification techniques

Course Agenda

Introduction and Overview of Military Capabilities

  • Purpose and Scope
  • Capability Portfolio Management
  • Capability Transformational programs within the DoD
  • Mapping OCD and ConOps to requirements?
  • DoD and NASA standards for OCD and CONOPS
  • Defense Acquisition Initiative (DAI)
  • Mission Operations Concepts and System Elements
  • Military Capability Vision: Goals and Objectives
  • Phase Definitions
  • Environment
  • Operation Description
  • Operation Goals
  • Concerns of Capability Portfolio Managers
  • Capability Models
  • Capability taxonomy and capability evolution
  • Capability Model Descriptions
  • Capability Phasing
  • Capability Dependencies
  • Capability to Organizational Development Mapping
  • Capability to Operational Activities Mapping A mapping between the capabilities required and the operational activities that those
  • Capability to Services Mapping

Operational Concept Description (OCD)

  • Solutions and Solution Architecture
  • Military Integrated Architecture
  • Military Architectural Frameworks
  • DoDAF, NAF and MoDAF Viewpoints

Military Concept of Operation (ConOps)

  • ConOps and stakeholders
  • Concepts of Military problem solving
  • ConOps mapping to system acquisition

Military OCD and Requirements Engineering Workshops

  • Building new military capabilities
  • Tools and templates for Gap Analysis
  • Capability Vision Creation Templates
  • ConOps and System Validation Examples and Case Studies

Military Capability Development Workshop

  • Military OCD and ConOps Case Studies and Examples
  • Military Capability Vision
  • Military Capability Taxonomy
  • Military Capability Phasing
  • Military Capability Dependencies
  • Military Capability to Organizational Development Mapping
  • Military Capability to Operational Activities Mapping
  • Military Capability to Services Mapping

Relationships between Use Cases and OD, ConOps, Validation, Requirement and Verification

  • Preparation of OCD and ConOps
  • Transforming the ConOps to new system acquisition
  • ConOps Lifecycle
  • Use cases and Scenarios
  • Use of the Operational Concept for Validation
  • Requirements Definition from the Operational Concept
  • Techniques for Evaluating and Writing Requirements
  • Problem Description
  • Solution Description
  • User’s and Operator’s viewpoint
  • Selection of standards of acceptance
  • Basis for verification and validation planning
  • Design of End Products and Enabling Products
  • Number of units, availability, deployment location decisions
  • Evaluation for future change requests

Creation and Development of Military OCD and ConOps

  • Military users of the OCD and ConOps
  • OCD and ConOps in the DoD Acquisition Life Cycle
  • OCD, ConOps and Use Cases
  • Scope relative to an Operational Concept Document (OCD)
  • Use Case analysis leading to OCD and ConOps
  • Mapping OCD and ConOps to DoDAF/NAF OV-1, OV-2, OV-3, OV-4 and OV-5
  • Transforming OCD and ConOps to DoDAF OV-6
  • When to Write OCD
  • When to Write the ConOps
  • Types of OCD and ConOps
  • Operations Concept
  • Production Concept
  • Deployment Concept
  • Support Concept
  • Disposal Concept
  • Concept development phase
  • System Development
  • Modeling
  • Unified Modeling Language (UML)
  • System Modeling Language (SysML)
  • Production and Deployment
  • Operations and Support
  • Disposal

System Engineering and Operations

  • Military capability and operational overview
  • Capability views
  • Operational Processes
  • Other Operational Needs
  • System Overview
  • System Operational Scenarios
  • Developing Requirements from the Operational Concepts
  • Use of the Operational Concept for Validation
  • Operational Concept Document in the Development Process
  • Perspectives on Operational Concept Analysis

Creating Operational Concept Description (OCD), ConOps and Requirements

  • Life Cycle Phases
  • Who, What, When, Where, How, and Why
  • OCD and CopOps Maintenance
  • Establish OCD Development Team
  • Participants
  • Generating OCD and ConOps Content
  • Defining the System Scope
  • Writing requirements
  • Attributes of good requirements
  • Operational requirements
  • Functional requirements
  • Non-Functional requirements
  • Validation requirements
  • Verification requirements
  • Requirements management
  • Defining the System Context and Boundaries
  • Defining Useful Operational Scenarios
  • Developing the Scenarios
  • Validating the Scenarios
  • Agreed Format and Style
  • Recommended OCD Content (Informative)
  • System Overview
  • System Scope
  • System Goals and Objectives
  • Users and Operators
  • System Interfaces and Boundaries
  • System States and Modes
  • System Capabilities
  • System Architecture
  • Operational Processes
  • Other Operational Needs
  • Mission Needs
  • Personnel Needs
  • Quality Factors
  • Alternatives and Tradeoffs Considered

 

Request More Information

  • Please complete the following form and a Tonex Training Specialist will contact you as soon as is possible.

    * Indicates required fields

  • This field is for validation purposes and should be left unchanged.