This three-day course is designed for engineers, scientists,
project managers and other professionals who design, build, test or sell complex systems. Each topic is illustrated by real-world case studies discussed by experienced CONOPS and requirements professionals. Key topics are reinforced with small-team exercises. Over 200 pages of sample CONOPS (six) and templates are provided. Students outline CONOPS and build OpCons in class. Each student gets instructor’s slides; college-level textbook; ~250 pages of case studies, templates, checklists, technical writing tips, good and bad CONOPS; Hi-Resolution personalized Certificate of CONOPS Competency and class photo, opportunity to join US/Coalition CONOPS Community of Interest.
"Your CONOPS course was the most worthwhile training I've had since. . . kindergarten!"
"This was probably the most interesting training course I have ever taken. The instructor's experience/knowledge really added to the value of the class - phenomenal real-world stories. Enjoyed MBTI portion. Can't think of any way to improve the course."
Mack McKinney, president and founder of a consulting company, has worked in the defense industry since 1975, first as an Air Force officer for 8 years, then with Westinghouse Defense and Northrop Grumman for 16 years, then with a SIGINT company in NY for 6 years. He now teaches, consults and writes Concepts of Operations for Boeing, Sikorsky, Lockheed Martin Skunk Works, Raytheon Missile Systems, Booz Allen Hamilton, DARPA, Joint Forces Command, all the uniformed services and the IC. He has US patents in radar processing and hyperspectral sensing.
What are CONOPS and how do they differ from CONEMPS, OPCONS and OCDs? How are they related to the DODAF and JCIDS in the US DOD?
What makes a “good” CONOPS?
What are the two types and five levels of CONOPS and when is each used?
How do you get their active, vocal support in your CONOPS?
After this course you will be able to build and update OpCons and CONOPS using a robust CONOPS team, determine the appropriate type and level for a CONOPS effort, work closely with end users of your products and systems and elicit solid, actionable, user-driven requirements.
Course Outline:
How to build CONOPS.
Operating Concepts (OpCons) and Concepts of Employment (ConEmps). Five levels of CONOPS & two CONOPS templates, when to use each.
The elegantly simple Operating Concept and the
mathematics behind it (X2-X)/2
What Scientists, Engineers and Project Managers
need to know when working with operational end users. Proven, time-tested techniques for understanding the end user’s perspective – a primer for non-users. Rules for visiting an operational unit/site and working with difficult users and operators.
Modeling and Simulation. Detailed cross-walk for
CONOPS and Modeling and Simulation (determining the scenarios, deciding on the level of fidelity needed, modeling operational utility, etc.)
Clear technical writing in English. (1 hour crash
course). Getting non-technical people to embrace scientific methods and principles for requirements to drive solid CONOPS.
Survey of major weapons and sensor systems in trouble and lessons learned. Getting better collaboration among engineers, scientists, managers and users to build more effective systems and powerful CONOPS. Special challenges when updating existing CONOPS.
Forming the CONOPS team. Collaborating with people from other professions. Working With Non-Technical People: Forces that drive Program Managers, Requirements Writers, Acquisition/Contracts Professionals. What motivates them, how work with them.
Concepts, CONOPS, JCIDS and DODAF. How does it all tie together?
All users are not operators. (Where to find the good ones and how to gain access to them). Getting actionable information from operational users without getting thrown out of the office. The two questions you must ALWAYS ask, one of which may get you bounced.
Relationship of CONOPS to requirements &
contracts. Legal minefields in CONOPS.
OpCons, ConEmps & CONOPS for systems, reorganizations & exercises – how to build them. OpCons and CONOPS for IT-intensive systems (benefits and special risks)
R&D and CONOPS. Using CONOPS to increase the Transition Rate (getting R&D projects from the lab to adopted, fielded systems). People Mover and Robotic Medic team exercises reinforce lecture points, provide skills practice. Checklist to achieve team consensus on types of R&D needed for CONOPS (effects-driven, blue sky, capability-driven, new spectra, observed phenomenon, product/process improvement, basic science). Unclassified R&D Case Histories: $$$ millions invested - - - what went wrong & key lessons learned: (Software for automated imagery analysis; low cost, lightweight, hyperspectral sensor; non-traditional ISR; innovative ATC aircraft tracking system; full motion video for bandwidth-disadvantaged users in combat - - - Getting it Right!).
Critical thinking, creative thinking, empathic thinking,
counterintuitive thinking and when engineers and scientists use each type in developing concepts and CONOPS.
DoD Architectural Framework (DoDAF), JCIDS and CONOPS: how they play together and support each other.
Lessons Learned From No/Poor CONOPS. Real world problems with fighters, attack helicopters, C3I systems, DHS border security project, humanitarian relief effort, DIVAD, air defense radar, E/O imager, civil aircraft ATC tracking systems and more.
Beyond the CONOPS: Configuring a program for
success and the critical attributes and crucial considerations
that can be program-killers; case histories and lessons-learned.
Tuition:
Tuition for this three-day course is $1490 per person per person at one of our scheduled public courses. Onsite pricing is available. Please call us at 410-956-8805 or send an email to ati@aticourses.com.
Mack McKinney, president and founder of a consulting company, has worked in the defense industry since 1975, first as an Air Force officer for 8 years, then with Westinghouse Defense and Northrop Grumman for 16 years, then with a SIGINT company in NY for 6 years. He now teaches, consults and writes Concepts of Operations for Boeing, Sikorsky, Lockheed Martin Skunk Works, Raytheon Missile Systems, Booz Allen Hamilton, DARPA, Joint Forces Command, all the uniformed services and the IC. He has US patents in radar processing and hyperspectral sensing.
