 |
OCD & CONOPS
|
Introduction | Training Objective | Course Outline | Course Method & Materials | Key Questions | Who Should Attend? | About the Presenter | Course Schedule
 |
 |
This course is recognised by Engineers Australia for CPD purposes (40 hours) |
Introduction
This course is a 5-day immersion in the development of military capability, with a focus on problem definition, Operational Concept Description (OCD - how the capability, and each element of its solution, will be used), and concept of operations (CONOPS - how the military outcome is to be achieved). The course requires no background or previous experience in CONOPS development.
The training is consistent with a systems approach to problem solving, as advocated by defence administrations worldwide. Systems engineering is an interdisciplinary, collaborative approach to the engineering of system solutions (of any type). The approach aims to capture stakeholder needs and objectives and to transform these into a description of a holistic, life-cycle balanced system solution which both satisfies the minimum requirements of the stakeholders, and optimises overall solution effectiveness according to the values of the stakeholders.
Stakeholder measures of effectiveness could include, for example, measures of military capability, ease of use, maintainability... and programmatic measures such as investment cost, recurring cost, National Industry Content..., as applicable. Within the concepts of overall effectiveness, Operational Effectiveness, of primary concern to the Commander, is isolated.
Training Objective
At the conclusion of this course, delegates are expected to:
- understand the types of information that collectively define a military (or any other) problem
- understand how to capture and validate the information which defines the problem
- understand the distinctly different information content and purpose of on OCD (Operational Concept Description) and a CONOPS (concept of operations)
- understand the role of each of these documents in development of military capability, and their relationship to requirements documents, various forms of solution description, architectural frameworks such as DODAF, and to acquisition
- have at least basic skills in capturing and validating requirements, etc.
- have at least basic skills in preparing an OCD
- have at least basic skills in preparing a CONOPS
Course Outline
1. Definitions
- problem
- problem description
- requirement
- measure of effectiveness
- target/goal
- value (effectiveness) model
- operational effectiveness
- requirement specification
- concepts related to problem description
- need
- want
- intent
- expectation
- constraint
- OCD – operational concept description
- solution
- solution description
- architecture
- architectural design description
- architectural framework
- CONOPS – concept of operation(s)
- detailed design
- verification
- verification requirement
- verification requirements specification
- validation
2. Concepts of Problem Solving
- problem definition
- emergence
- divergence
- convergence
- systems thinking
3. Relationships Between Requirements Document, OCD, Architectural Design Description, CONOPS
4. Types of Requirements
- eight basic types
- Workshop1 - categorising requirements for a military capability by type
5. The Quality of Requirements
- requirements quality attributes
6. Requirements Analysis for the Military Capability
- purpose of requirements analysis
- relationship to OCD
- relationship to CONOPS
- requirements analysis methodology
- context analysis
- Workshop 2 - context analysis for a military capability
- states & modes analysis
- Workshop 3 - states and modes for a military capability
- parsing analysis
- Workshop 4 – parsing analysis
- functional analysis
- Workshop 5 - functional analysis for a military capability
- rest of scenario analysis
- ERA analysis
- out-of-range analysis
- value analysis
- Workshop 6 – building a system effectiveness model
- operational effectiveness
- operational effectiveness versus overall effectiveness
- other analysis techniques
- extracting information for an OCD and requirements document from users (and others)
7. Operational Concept Description (OCD) for the Military Capability
7.1 Content and Purpose of an OCD
- users and uses of an OCD
- types of OCD
- principles regarding content
- use cases, mission profiles, scenarios and the OCD
- how does support relate to an OCD?
- relationship of the OCD to the requirements document
- OCD standards and guides
- Operational Concept Documents, DID DI-MCCR-80023, SDS Documentation Set – Data Item Descriptions for DoD-STD-2167, U.S.A. Department of Defense, 1985.
- Concept Data Item Description, SMA-DID-P100, NASA Product Specification Document Standard, Release 4.3, 1989
- ANSI/AIAA G-043-1992, Guide for the Preparation of Operational Concept Documents, 1992
- Operational Concept Description (OCD), DID DI-IPSC-81430, Data Item Descriptions for MIL-STD-STD-498, U.S.A. Department of Defense, 1994.
- IEEE Standard 1362, IEEE Guide for Information Technology – System Definition – Concept of Operations Document, 1998
- ACC Instruction 10-650, Development and Use of Concepts of Operations, U.S. Department of the Air Force, 1998
- Guide for the Preparation of Operational Concept Documents, ANSI/INCOSE/AIAA, G-043-200x Draft 2.0, 2006
- PPI’s OCD DID
- who should prepare on OCD
- timing of preparation of an OCD versus requirements document
7.2 Preparing an OCD
- Workshop 7: Review of Sample OCDs
- characteristics of a good OCD
- Workshop 8: Preparing a Basic OCD
- pitfalls in OCD preparation
- Workshop 9: Review of an OCD for a Military Capability
- use of graphics in OCDs
- level of detail in the OCD
- design content – when, and when not?
- makeup of an OCD development team
- the role of users
- beyond the basic OCD
- extending OCDs to other stakeholders
- pitfalls in preparing OCDs
8. CONOPS
8.1 Content and Purpose of CONOPS
8.2 Relationship of CONOPS to Overall Solution
8.3 Styles of Solution Development
- the solution domain: key concepts, relationships, and work products
- Workshop 10 – principles of CONOPS development
- waterfall, incremental, evolutionary and spiral development approaches
- Workshop 11 – solution development strategies for a military problem
8.4 Concepts of Architecture - Physical and Logical, in CONOPS Development
- physical architecture (structural view) – basic concepts
- the role of technology and innovation
- techniques for stimulating innovation in solution development
- perspiration engineering: configuration items
- criteria for selecting configuration items
- relationship of CI definition to future system integration
- Workshop 12 – physical conceptualisation for a military problem
- logical architecture – basic concepts
- logical architecture related to physical architecture
- useful forms of logical representation – functional, state-based, mathematical, …
- model-based design in practice
8.5 Functional Modelling in CONOPS Development
- functional modelling in CONOPS development – how to do it
- functional analysis/architecture process
- item flow and control flow
- coupling, cohesion, connectivity
- unallocatable and allocatable functions
- pitfalls in defining functions
- Workshop 13 – a simple functional solution for a military problem
- Workshop 14 – physical and functional solution for a military problem
- FMECA in functional solution
- performance thread analysis
- SysML, and alternative languages incorporating behavior modelling
- other functional modelling languages
- software tools supporting functional and physical solution
- pitfalls in functional solution development
8.6 Return to Physical Solution Development in CONOPS Development
- use of design driver requirements
- facilities, procedures, people, and other types of solution element
- some common pitfalls in developing CONOPS
- adding the detail to the solution
- solution creates requirements – the duality of requirements and solution
- interface engineering
- evolution of interfaces in solutions having levels of structure
- interface requirements specifications versus interface design descriptions
- some common pitfalls in interface engineering
8.7 Decision Making in CONOPS Development
- solution development for feasibility
- solution development for effectiveness: approach to solution optimisation
- the role of MOEs and goals
- using a system effectiveness model
- taking account of risk relating to goals
- taking account of risk relating to satisfaction of requirements
- event-based uncertainty
- risk-aversion
- Workshop 15 – using a system effectiveness model in developing solution for a military problem
- cost/capability, return on investment and like concepts
- iterative optimisation of solution – an amazingly effective methodology
- software tools supporting CONOPS decision making
- common pitfalls in CONOPS development
8.8 CONOPS Development
- CONOPS Template
- Example CONOPS
9. Development of Requirements for Elements of Solution
10. Summary and Key Points
- action plan
11. References and Recommended Reading
Training Method and Materials
A mixture of stand-up instruction, with numerous examples, and substantial workshop activity, is used to deliver a very practically-oriented learning experience. A single military problem with evolving solution is the focus for the workshops. You will be provided with:- comprehensive bound Course Notes containing presentation material;
- a Workbook containing workshop exercises, with worked examples also distributed in most cases;
- numerous supplementary decriptions, checklists, forms and charts which you can put to use immediately.
Key Questions
- What is the difference between an OCD and a CONOPS?
- How should each be developed?
- How does each relate to requirements?
- What are the best public domain standards for OCD and CONOPS?
Who Should Attend This Seminar/Workshop?
Military Capability Developers, Systems Engineers working on military programs, Requirements Managers for military systems, Program and Project Managers for development of military capability, and parts thereof.
About the Presenter
An executive professional engineer, manager and engineering practitioner, Mr Halligan is renowned internationally for his role in the practice and improvement of technology-based projects. Mr Halligan obtained his qualifications at the University of Melbourne and the Royal Melbourne Institute of Technology (now Victoria University). After early engineering, engineering management and project management roles with Telecom Australia, Department of Defence (Australia), Rockwell International and Andrew Corporation, Mr Halligan has for the last seventeen years contributed to major systems projects worldwide as a consultant and trainer... |  |
Course Schedule
| P958-02 15 Sep to 19 Sep 2008 | Melbourne, Australia Mercure Hotel Melbourne | Earlybird Fee: AUD3375.00 Standard Fee: AUD3750.00 | Download Brochure Download Regform | Enquire Online Register Online |
| P958-04 25 May to 29 May 2009 | Melbourne, Australia Mercure Hotel Melbourne | Earlybird Fee: AUD3375.00 Standard Fee: AUD3750.00 | Brochure Not Available Download Regform | Enquire Online Register Online |
| P958-05 10 Aug to 14 Aug 2009 | Adelaide, Australia Freedom Adelaide Meridien Hotel | Earlybird Fee: AUD3375.00 Standard Fee: AUD3750.00 | Brochure Not Available Download Regform | Enquire Online Register Online |
Top
* All AUD$ amounts are inclusive of GST