| |
Listed below are the most common errors committed by organizations and managers who have not been through our training courses, as reported by our students and consultants working in the defense industry and DOD over the past six months (this list changes regularly)
|
| |
Our custom courses can be presented at your facility:
| |
- Waiting (and waiting) for the client's users to write the CONOPS
- Treating CONOPS as an afterthought and then fighting with the customer as to who pays for it
- Assigning an internal team but allocating far too little money and time
- Assigning internal "operations experienced" team lead, with no formal training, to lead the CONOPS-building team
- Using an old CONOPS as a template for a new CONOPS (just transfers shortcomings and mistakes from the old document to the new one)
- Letting a "finished" CONOPS gather dust while software people (without help from end users) write Use Cases and Test Plans and guess at evolving operational requirements
- Failing to assign an Operations Engineer to drive OpCons and CONOPS; participate in Operations Analysis, Operations Requirements and Concept Analysis; help build functional flow block diagrams, AV-1, OV-1 and OV-2; help write test plans and perform/witness all Human Systems Interface designs and functional testing; help select and write software Use Cases; certify the CONOPS; write the Users Manuals
|
| |
|
|
| |
If your organization and/or managers are guilty of any of these CONOPS sins, or you just want to prevent their commission, call Solid Thinking and get the training scheduled. |
| |
If you or your colleagues are already leading CONOPS-building teams, watch for these common mistakes: |
| |
|
| |
- Lack of agreement with team as to use, scope, cost of CONOPS
- No formal training provided to CONOPS team
- Insufficient time and money budgeted for team to do a thorough job (often because there was no proven, bottoms-up costing process or Work Breakdown Structure to permit accurate costing)
- Top-down budget implemented without input from the CONOPS team (often for same reason as above)
- Budget based solely on a previous CONOPS effort
- No clear expectations, hence poor/no direction to the team (“bring me a rock”)
- CONOPS drafted by 1-2 people, without face-to-face discussions with current, operational, end/combat users
|
| |
Remember: "If you build a CONOPS in a vacuum, it will suck" (CONOPS Course)
Don't forget the users: "A CONOPS without ops is just a con". (Lt. David Sidewand, USN)
|
| |
|
|
| |
|
|
| |
Hunter gets a problemectomy by
US Army avionics technician
|
|
| |
|
|
| |
Solid Thinking Corporation
The CONOPS People (TM)
A Veteran-Owned Small Business
Located near the birthplace of aviation, Kitty Hawk, NC
Solid Thinking Corp.
PO Box 338
Maple, NC 27956
T: 315-420-6593
F: 252-453-6627
www.SolidThinking.org
To E-mail Us Click Here
|
|
|
