Operational Concept Document Development Workshop


This workshop provides groups from within the Australian Defence Organisation, other government agencies, and industry with an opportunity to apply the systems engineering process as it maps to the development of the Operational Concept Document (OCD), including tailoring ) for Capability Assurance/Capability Alignment Projects (CAP). After a brief review of systems acquisition and conceptual design processes, attendees will participate in a series of design exercises focused on the development of a real-life OCD. The exercises are conducted as a combination of tutorials and activities that step through relevant activities.

Who Should Attend

Course Outline

Presenter Background

Dates & Registration

Duration: 2 - 4 days

Delivery mode: Classroom


Advertised: Not available

In-house: All states and neighbouring countries, contact the  for more information. Recommended for groups of 10 or more.

What you will receive:

  • Comprehensive course notes
  • UNSW Canberra certificate of completion/attendance*

In-house delivery: Contact the  for more information. Recommended for groups of 10 or more.

Affiliated course: Introduction to Capability Development (3 days)

*pending final results 




Any group responsible for the development or maintenance of a project's OCD.




Systems Acquisition Review

Systems | Systems acquisition | Systems engineering | Requirements engineering | Revision of Conceptual Design Activities

Selected Important OCD Activities

Identify Stakeholders | Identify CS Boundaries (Context Diagram, Consider External Interfaces) | Identify Mission Objectives (Identify Mission and Operational Needs, Secondary Missions) | Identify Policies and Doctrine | Glossary and Referenced Documents | Define Capability System Needs (Identify all End-user Classes, Select Operational Scenarios) | Define Capability System Constraints (Enterprise, Project, External and Design) | A Cautionary Note WRT Constraints | Describe Existing System Capability | Define Materiel System Requirements

Design Exercise 

Define mission, goals and objectives | Define measures of effectiveness | Consider design constraints | Consider external interfaces | Produce context diagram | Define system boundary | Identify system-level trade studies | Practical OCD development



Mike Ryan


Dr Mike Ryan holds BE, MEngSc and PhD degrees in electrical engineering from the University of New South Wales. He is a Fellow of Engineers Australia (FIEAust), a Chartered Professional Engineer (CPEng) in electrical and ITEE colleges, a Senior Member of IEEE (SMIEEE), a Fellow of the International Council on Systems Engineering (INCOSE), and a Member of the Australian Institute of Management (AIMM). Since 1981, he has held a number of positions in communications and systems engineering and in management and project management. Since 1998, he has been with the School of Engineering and Information Technology, University of New South Wales, Canberra where he is currently the Director of the Capability Systems Centre. His research and teaching interests are in communications and information systems, requirements engineering, systems engineering, and project management. He is the Editor-in-Chief of an international journal, and is the Chair of the Requirements Working Group of INCOSE. He is the author or co-author of twelve books, three book chapters, and over 180 technical papers and reports.