Diodote · operational planning — COPD
Plan an operation along the COPD —
from the first indications to the OPLAN.
Hold a planning case and walk it through the operational planning process: appreciate the strategic environment, analyse the mission, draw the operational design, develop and wargame courses of action, and write the CONOPS and the OPLAN. At each step you may ask for a draft from a cited case file; every drafted field says who wrote it, and a person accepts, corrects or rejects it.
Sign in, then choose your operation in the Operation ▾ menu of the bar, or open one on Cases — a new one, or one handed over by a game of Diodote Arena Tactical (“Handover to plan”). The page of the case shows its COPD timeline, what is filled in and what is missing. Every page opens on its explanation; “Draft with Mistral” asks Mistral Large for a draft from the case file, which a person accepts or rejects.
The planning process, and how its parts interact
The diagram of the COPD steps loads here; the phases are listed below.
The COPD, step by step
- 1 Initial situational awareness Record the indications of a crisis, the strategic assessment and the warning you receive (COPD 4.5–4.9).
- 2 Operational appreciation of the strategic environment Appreciate the strategic assessment and give operational advice on the military response options (4.10–4.22).
- 3a Mission analysis Frame the problem; analyse actors, factors, centres of gravity, limitations, assumptions, risks and CCIRs; draw the initial operational design; brief the MAB and issue the OPG (4.24–4.33).
- 3b Course of action development Develop own and opposing courses of action, check them against FACES, wargame them, compare them, brief the CoA decision and issue the OPD (4.34–4.40).
- 4a CONOPS development Write the operational CONOPS from the case file (4.41–4.51).
- 4b OPLAN development Write the OPLAN — the main body and the annexes that matter (4.52–4.60).
- 5 Execution Reserved Assess the operation (MoE, MoP, the collection plan) and adapt it: battle rhythm, FRAGOs, review.
- 6 Transition Reserved Hand the operation over and transition.
What it does today, and what is reserved
-
Today
- Planning cases: the COPD timeline, the directives and the guidance received (phases 1–2), the commander’s decisions, and a current operation chosen in the bar.
- Mission analysis (3a): actors, the operating environment, factors → deductions → conclusions, centres of gravity, limitations, assumptions, risks and opportunities, CCIRs; the initial operational design and its DSM.
- Course of action development (3b): own and opposing COAs, FACES, the wargame (action, reaction, counter-action) and its synchronisation matrix — its outcome is the staff’s assessment —, the weighted comparison, the decision.
- The products: the operational advice on the MROs, the WNGO, the MAB, the OPG, the CoA DB, the OPD, the CONOPS and the OPLAN, written from the case file.
- Drafts by Mistral Large from a cited case file — every drafted field says who wrote it, and a person accepts or rejects it.
- The maps: the great view of a COA (map, matrix, schematic, opposing COAs) and the animated scenes of the units.
- The links within Diodote: a game of Diodote Arena Tactical hands its problem over to a case; the game pulls the decided COA and runs the simulation there; system analysis, the maritime environment (MDA) and the osint and intell libraries feed the case file; a chat shared by the services.
-
Reserved
- Phases 5 and 6 of the COPD: execution (MoE, MoP, the collection plan, battle rhythm, FRAGOs, review) and transition.
- The analysis matrices of the military response options (Annex B, App 1 A–D) and the operational assessment (4.19–4.20).
- The return of the game’s simulation results (its Monte-Carlo) into the plan’s confrontation.
- A local semantic search (today: full text here, and semantic search through osint).
- A search of assertions at intell.
- The strategic level (Annex A).
- The SORs (CJSOR, TCSOR, Manpower, ROEREQ) beyond a simple table in the OPLAN.