Slides From ATI Professional Development Short Course
                         Technical CONOPS and Concepts



                                     Instructors:

                                 Mack McKinney
                                 John Venable


ATI Course Schedule:      http://www.ATIcourses.com/schedule.htm

ATI's CONOPS:             http://www.aticourses.com/technical_CONOPS_concepts.htm
OCD Flows To OpCons and CONOPS
   Operational Concept                            Formal CONOPS
   Document Sections                                 Sections
• Overview                                • EXECSUM

• Problem Statement                       • Section 3 – Situation
                                            Today
• Changes Needed                          • Section 4 – Justification
                                            for Changes
• New Capability or System                • Section 5 – End State
  Envisioned                                & OpCon

• Operational Uses                        • Section 6 - Scenarios
                      Copyright STC March 2008.                   141
                         All rights reserved.
Data-Driven OpCon and                               Future 
                                                     Concepts                    Standard Operating
   User- Focused CONOPS
                                                    (e.g. JOpsC)                 Procedures (SOP),
     Are the Linchpins                                                           OPORDS, EXORDs,
                                                                                  Ops Assessments
                                            Scenarios, Current
                                            System/Situation,
        P3I & ECPs                          Justif for Delta,      Scenarios
                                            Summary of Impacts
                           Features Left Out &
                                                                                           Training
                                                                      Personas
                           Obsolescence Analyses                      & Scenarios          Programs
                                                                       Personas,
                                                                       Use Cases
                        OpCon            CONOPS                        & Scenarios
                                                                                         User Manuals *

              OpCon Text, Scenarios,             Effects-Based Solutions,      Lessons
              Regular Input From Users           Regular Input From Users,     Learned
                                                 Modeling & Simulation                        TTPs
Copyright STC 2010.
 All rights reserved.


     Architecture                                         Requirements
                                DODAF                                            CBAs         JCIDS
                                                             DOD/DHS
       AV-Xs              OV-Xs          SV-Xs               Reviews           Effects-Based SE

           * Operators, maintainers, SysAdmin & downstream product users all need User Manuals
Copyright STC 2008.
                                                                                               All rights reserved.

  Structured Dialogue With Operational Users
   - - - especially with Hands-On Operators - - -           OpCon, CONOPS,
     (to learn current concepts, ops scenarios,
       biases, lessons from exercises & ops,               Modeling & Simulation
future needs, impressions of similar systems, etc.)


                                                                                       Operating
                                                                                      Environment

                                                                                   Existing      New

                                                                        Existing   m&s         m&S
                                                            System or
                                                            Component
        OpCon             CONOPS                                         New       M &s        M&S

                                                                               2 X 2 Matrix addresses most
                                                                               common M&S situations.
          Modeling & Simulation (M&S)
      - - - Traditional Decision Points - - -

       1.    What do we want from the M&S effort?
       2.    What real-world things are we examining with the M&S?
       3.    What systems/platforms should be modeled?
       4.    At what fidelity?
       5.    What operational environment should be modeled?
       6.    What combination of systems/platforms is appropriate?
       7.    What operational scenario should be employed?
       8.    What combination of dependent and independent variables is best?
       9.    What roles should be scripted?
       10.   Does the M&S result make sense?
WHAT You Build Is Driven by Client’s Interests
           Client’s Interest . . .       Your Course of Action . . .

•   Set up a new organization
•   Get people to accept new
    approach
•   Offer new system                                        Build CONOPS w/
                                      Build OpCon &          Formal Template
•   Host an exercise
                                        Scenarios
•   Assess operational utility of a
    system
     – That is completely new
                                                            Build CONOPS w/
     – That already exists                                  Fielded Template

•   Assess disruptive technology         Envision
    or rapidly build a prototype      Technology in a
                                         System
                                                                  Copyright Solid Thinking
                                                                  All Rights Reserved
•   Explore utility of a device,
                                      Build EmpCon &
    weapon, etc (not a system)             OpCon
You have enjoyed ATI's preview of
           Technical CONOPS and Concepts




    Please post your comments and questions to our blog:
        http://www.aticourses.com/blog/

     Sign-up for ATI's monthly Course Schedule Updates :
http://www.aticourses.com/email_signup_page.html

Technical conops concepts_technical_training_course_sampler

  • 1.
    Slides From ATIProfessional Development Short Course Technical CONOPS and Concepts Instructors: Mack McKinney John Venable ATI Course Schedule: http://www.ATIcourses.com/schedule.htm ATI's CONOPS: http://www.aticourses.com/technical_CONOPS_concepts.htm
  • 2.
    OCD Flows ToOpCons and CONOPS Operational Concept Formal CONOPS Document Sections Sections • Overview • EXECSUM • Problem Statement • Section 3 – Situation Today • Changes Needed • Section 4 – Justification for Changes • New Capability or System • Section 5 – End State Envisioned & OpCon • Operational Uses • Section 6 - Scenarios Copyright STC March 2008. 141 All rights reserved.
  • 3.
    Data-Driven OpCon and Future  Concepts  Standard Operating User- Focused CONOPS (e.g. JOpsC) Procedures (SOP), Are the Linchpins OPORDS, EXORDs, Ops Assessments Scenarios, Current System/Situation, P3I & ECPs Justif for Delta, Scenarios Summary of Impacts Features Left Out & Training Personas Obsolescence Analyses & Scenarios Programs Personas, Use Cases OpCon CONOPS & Scenarios User Manuals * OpCon Text, Scenarios, Effects-Based Solutions, Lessons Regular Input From Users Regular Input From Users, Learned Modeling & Simulation TTPs Copyright STC 2010. All rights reserved. Architecture Requirements DODAF CBAs JCIDS DOD/DHS AV-Xs OV-Xs SV-Xs Reviews Effects-Based SE * Operators, maintainers, SysAdmin & downstream product users all need User Manuals
  • 4.
    Copyright STC 2008. All rights reserved. Structured Dialogue With Operational Users - - - especially with Hands-On Operators - - - OpCon, CONOPS, (to learn current concepts, ops scenarios, biases, lessons from exercises & ops, Modeling & Simulation future needs, impressions of similar systems, etc.) Operating Environment Existing New Existing m&s m&S System or Component OpCon CONOPS New M &s M&S 2 X 2 Matrix addresses most common M&S situations. Modeling & Simulation (M&S) - - - Traditional Decision Points - - - 1. What do we want from the M&S effort? 2. What real-world things are we examining with the M&S? 3. What systems/platforms should be modeled? 4. At what fidelity? 5. What operational environment should be modeled? 6. What combination of systems/platforms is appropriate? 7. What operational scenario should be employed? 8. What combination of dependent and independent variables is best? 9. What roles should be scripted? 10. Does the M&S result make sense?
  • 5.
    WHAT You BuildIs Driven by Client’s Interests Client’s Interest . . . Your Course of Action . . . • Set up a new organization • Get people to accept new approach • Offer new system Build CONOPS w/ Build OpCon & Formal Template • Host an exercise Scenarios • Assess operational utility of a system – That is completely new Build CONOPS w/ – That already exists Fielded Template • Assess disruptive technology Envision or rapidly build a prototype Technology in a System Copyright Solid Thinking All Rights Reserved • Explore utility of a device, Build EmpCon & weapon, etc (not a system) OpCon
  • 6.
    You have enjoyedATI's preview of Technical CONOPS and Concepts Please post your comments and questions to our blog: http://www.aticourses.com/blog/ Sign-up for ATI's monthly Course Schedule Updates : http://www.aticourses.com/email_signup_page.html