Skip to main content

7. ROC Drill

Intent

The ROC (Rehearsal of Concept) Drill validates that the TMP is executable without interpretation.

It is a structured, controlled validation of task sequencing, integration, triggers, contingencies, authorities, and decision points.

7.1. Preconditions for ROC​

The ROC Drill will not begin unless:

  • All MPOs are assessed as complete
  • Major cross-LOE dependencies are identified
  • High-risk TTs have defined contingencies
  • Integration artifacts are consolidated into a single working execution view
  • Timeline and phasing are stable
  • All high-impact assumptions have defined contingencies
  • GICL has been enforced

The ROC is a validation event - not a planning session.

7.2. ROC Structure​

The ROC is conducted in execution order.

7.2.1. Walk the Plan by Phase​

For each phase:

  1. Identify:
    • The phase objective
    • Supported TO(s)
    • Supported MPO(s)
  2. By LOE, "execute" (tabletop-simulated):
    • Each TT in sequence
  3. For each TT, validate:
    • Inputs required
    • Trigger conditions (if applicable)
    • Responsible crew position
    • Expected outputs
    • Time estimate
    • Dependencies
    • Decision authority (if required)

NOTE: No step is assumed - every action is verbalized

7.2.2. Contingency Validation​

For each high-risk TT or event:

  • Confirm a documented Contingency exists (if required)
  • State the defined Trigger
  • Simulate Contingency activation:
    • Walk the Response
    • Confirm:
      • Authority exists
      • Required resources exist
      • Cross-LOE impacts understood
      • Timeline impact assessed

7.2.3. Assumption Stress Test​

For each critical assumption:

  • Ask: "What if this is false?"
  • Identify:
    • Impact to current phase
    • Required contingency
    • Escalation requirements
  • Confirm assumption-to-contingency linkage exists

NOTE: Unlinked assumptions represent execution risk

7.3. Friction Identification​

During ROC, actively identify:

  • Timeline compression points
  • Resource contention
  • Authority gaps
  • Conflicting LOE outputs
  • Undefined decision triggers
  • Ambiguous task language
  • Gaps in contingency coverage

NOTE: Friction must be captured visibly and assigned an owner for resolution before proceeding

7.4. ROC Adjudication​

At ROC completion, the MPCC determines if:

  • The plan is executable
  • The plan requires refinement
  • The plan requires structural adjustment

Possible outcomes:

  • Minor refinements (language, sequencing)
  • Contingency additions
  • Task reallocation
  • Phase restructuring
  • MPO/MPT modification (if required)
  • Scope reduction due to timeline or risk constraints

NOTE: Major changes require re-validation.

7.5. ROC Discipline Rules​

  • The ROC is not a re-brief of the plan
  • No new planning scope introduced unless tied to identified friction
  • All changes must map to:
    • An existing MPO
    • A defined Tactical Problem
  • Deviations must remain within constraints and ALR
  • If integration failure is discovered, the ROC pauses until resolved

7.6. ROC Close-Out Requirements​

Before concluding the ROC Drill:

  • All identified friction has:
    • An owner
    • A suspense
  • All contingencies validated or updated
  • Timeline updated if required
  • Integration confirmed across LOEs
  • Final plan version designated for Mission Commander Brief
  • No unresolved assumption remains without a contingency