How it works

Catch late jobs, then get the moves to recover them

Between the half-hour checks it also wakes when a machine stops or faults, or a quality hold opens, so a problem on the floor reaches the schedule in minutes, not at the next meeting.

  • Largest projected miss 38h 24m

Planning issues

Find late jobs before they slip

Every half hour the Planner looks across the job orders in its horizon and flags the ones that won’t finish on time. A job it has already flagged isn’t raised twice.

  • At-risk job orders flagged inside the monitoring horizon
  • A stopped or faulted asset triggers its own check
  • A job already flagged is not raised a second time
  • WO-118351 eligibility Capacity clear Tooling clear Operator qualified
  • Held: not yet eligible

Proposed moves

Get only the moves the floor can run

Before it suggests anything, each move is checked against the constraint model, so the plan it puts forward is one the floor can actually run. If planning comes back empty, a fixed rule picks the move.

  • Eligibility checked before a job is considered for a move
  • A reschedule planned from the eligible candidates only
  • A deterministic fallback picks the move when planning returns nothing
  • WO-118363: Machining Cell B Inside authority Applied
  • 1 Outside authority, routed

Authority model

Set what it can do alone and what needs a yes

You decide what it may do alone. Inside that authority it applies the move. Outside it, the move waits in the Approval Queue for a person. Every job it skips comes with a note in plain words.

  • Autonomous inside its authority, approval-gated outside it
  • Every skipped job carries a note in plain words
  • Applied and proposed moves both land in the record
  • Reschedule applied, WO-118363
  • Notified: 3 roles on the job

Downstream reaction

Tell the rest of the plant what changed

When a job goes at risk, the Planner posts it for the other Modules and Agents, and the roles the job belongs to get notified. If a quality hold opens, it replans the work sitting behind it.

  • Schedule at risk, reschedule proposed, and reschedule applied are published
  • A quality hold opening makes the Planner replan what sits behind it
  • Notifications go to the roles the job belongs to
  • 3 Planner raised this shift

Shift schedule

Work from the schedule you already use

What the Planner moves shows up in the schedule and orders your planners already use. Planning issues lists what it raised this shift. The bell carries the one thing that needs a person now.

  • The schedule and the orders stay the working screens
  • Planning issues collects what the Planner raised this shift
  • The bell carries the one thing that needs a person now
  • Golden set v6 scenarios12 of 13

Plan validation

Every change to how it plans passes a fixed test set first

Before any change to how it plans ships, it has to pass a fixed set of test scenarios. Every run it makes can be reviewed. It moves jobs. It never changes what was ordered.

  • A golden set of scenarios it has to pass
  • Monitoring and diagnostics show every run it made
  • It moves jobs, it does not change what was ordered

What the Planner flags before a job slips

    • WO-118351 reschedule Check eligibility Plan the move Apply or send for approval
    • Eligible

    Every move checked before it is proposed.

    The Planner checks a move against the constraint model before it is ever proposed, so what reaches you is one the floor can run. A fallback picks the move when planning finds nothing.

    See eligibility rules
    • At risk this horizon 3 jobs
    • Reschedule applied, WO-118363

    Every late job flagged before it slips.

    The Planner scans the job orders on the horizon every half hour and flags any that will not finish on time. A hold opening behind one makes the Planner replan.

    How notifications route out

FAQ

Bring the job order that's about to run late.

30 minutes on your schedule and the moves the Planner would put forward.