Executive Control Centre

Friday, 23 October 2026 · Shift A · Updated 8 minutes ago

ViewingSource: loading
Back to Docs

Connected decision paths

Operating flows

These are local prototype flows: they help a team trace a decision from the first signal to an owned operational response.

The PPC operating loop

From commitment to controlled recovery

The platform connects the buyer promise to finite capacity, the released plan, shop-floor actuals, and a named response when delivery is exposed.

  1. 1

    Control Centre

    Which delivery commitment needs a decision now?

  2. 2

    Order 360

    Can we still honour this buyer commitment?

  3. 3

    Capacity Workbench

    Where is capacity constrained and what recovery option protects delivery?

  4. 4

    Plan Builder

    Which allocation and plan version should go to the floor?

  5. 5

    Shop-floor

    What is happening on this line during the current shift?

  6. 6

    Exceptions

    Who owns this operational risk and what action will resolve it?

How to read this prototype
The screens use synthetic local data. Actions update the current browser session only, so the walkthrough is safe to explore and reset by refreshing the page.
Start with the Control Centre, then follow the signal to the screen that owns the next decision. The Viewing bar keeps the selected role and factory while you navigate; in this prototype the role changes the workspace label and factory filtering is limited to selected Control Centre sections.

Use the flow that fits the conversation

Three ways to navigate the same operating loop

Protect a buyer commitment
Use this when leadership needs to understand whether an order will meet its dispatch commitment and what recovery decision is available.
  1. 1
    Control Centre

    Find the delivery risk, capacity pressure, or exception that deserves attention.

  2. 2
    Order 360

    Confirm the buyer promise, good output, critical path, and projected delivery position.

  3. 3
    Capacity Workbench

    Inspect the constrained line and record a local recovery option. The workbench does not compare scenarios or recalculate capacity.

  4. 4
    Plan Builder

    Select a version and use local allocation fields to discuss the recovery. Releasing changes the version status; it does not apply those edited allocations to execution.

Respond to a shop-floor constraint
Use this when the line reports downtime or output that may expose delivery.
  1. 1
    Shop-floor

    Record downtime or post output so the current demonstration state reflects the line event.

  2. 2
    Exception Detail

    Acknowledge, investigate, start an action, or close a known operational risk.

  3. 3
    Plan Builder

    Review the recovery allocation when the exception requires a planning response.

  4. 4
    Control Centre

    Return to the operating picture to discuss the remaining delivery impact and ownership.

Review the effect of a plan change
Use this to communicate the difference between a baseline plan and a recovery choice before action is taken.
  1. 1
    Plan Builder

    Compare the seeded plan versions and edit local allocation values for the conversation.

  2. 2
    Capacity Workbench

    Create a local what-if scenario record. Capacity metrics remain the seeded demonstration values.

  3. 3
    Order 360

    Re-read the order commitment and connected risks from the buyer perspective.

  4. 4
    Production Gantt

    Review the milestone sequence and dependency timing across the demonstration plan.

A useful leadership habit
In each flow, ask the same three questions: what commitment is exposed, what capacity or execution fact explains it, and who owns the next action?