Skip to content

Operations Management

Operations Management handles operational data diagrams, milestone planning, dependencies, and readiness tracking.

Operational objective

Keep schedule logic, readiness evidence, and operational data diagrams aligned so deployment decisions are based on current execution state.

What You Can Do

  • Manage operational data diagrams (CRUD, editor, sync/resync, XML download).
  • Maintain operations project records.
  • Manage timetable states.
  • Maintain milestones and milestone-state links.
  • Track milestone dependencies.
  • Manage operational readiness items and readiness dependencies.

Typical Workflow

  1. Define ops project context and timetable states.
  2. Build milestone plan and link milestone/state applicability.
  3. Capture milestone dependencies.
  4. Track readiness items by state applicability.
  5. Use readiness dependencies to identify sequencing risks.
  6. Maintain operational data diagrams for implementation communication.

Operations Planning Flow

flowchart TD
    A[Define Ops Project Context] --> B[Set Timetable States]
    B --> C[Plan Milestones]
    C --> D[Link Milestones to States]
    D --> E[Manage Dependencies]
    E --> F[Track Readiness Items]
    F --> G[Maintain Ops Data Diagrams]

Key Pages

  • Ops dashboard.
  • Data diagram list/detail/editor/sync/resync/download.
  • Project, timetable state, milestone, and dependency CRUD pages.
  • Readiness item and readiness dependency CRUD pages.
Collapsed sequencing caution

Adjusting milestone dates without revisiting dependency links can create hidden readiness conflicts.

Practical Tips

  • Review dependencies before milestone date changes.
  • Keep readiness item ownership explicit to reduce rollout risk.

Routine check

Before major updates, review both milestone dependencies and readiness dependencies in the same session.