RH Operating Flow Explorer

Start here

This is a proposed operating model for review. Follow the manufacturing process first. The software details are optional and stay out of the way until you ask for them.

Follow the processRead the manufacturing steps from left to right, or use Walk the cycle to see one stage at a time.
Open a plain explanationSelect any stage or process step for a plain-language explanation of who acts and what happens.
Add the software viewTurn on System support and controls only when you want to review application behavior or future safeguards.

System support and controls add the technical record names, current-versus-proposed status labels, and source references. The manufacturing process stays visible either way.

The RH manufacturing scheduling process, start to finish

RH gathers the work and plant facts, checks that the inputs are ready, builds and reviews the production schedule, releases one schedule to the floor, performs the work, records what happened, resolves differences, and closes the planning effort.

Each step below names what the reader is looking at and the main result it produces. Select a stage in the canvas underneath for the full explanation.

In short Orders and plant facts→ readiness check→ draft production schedule→ reviewed schedule→ official floor schedule→ work performed→ actual results→ differences resolved and cycle closed

System support and controls

What the software records as the work moves

Behind the process, the application would keep a connected set of information records that become more authoritative as the work moves from inputs to an official plan and then to actual results. These proposed software records sit behind the process and do not add manufacturing steps.

Select any item for its business definition, a synthetic example, and an explanation of what exists today versus what is proposed.

A simple synthetic example

Demand, labor, delivery, and inventory information is prepared for a sample planning day.
The exact usable versions are confirmed together as the planning basis.
The optimizer creates a candidate plan linked to those versions.
An approved version becomes the official released plan.
The floor records starts, blocks, quantities, and completion against that version.
The scheduler compares the plan with actual work and closes or explains the remaining differences.

The full cycle as one picture

Each row is a participant. Rows with a person mark are people, the row with a chip mark is the deterministic system, and the middle row is the information and schedule that gains authority as it moves from one person to the next. Step through the stages, or follow one participant to see only what they touch.

Tip: Select a shape to open its plain-language meaning, example, and next step. Select a stage, then use Stage details for the stage-level explanation.

Traceability: ten stages plus a governance and recovery control row, matching the stage contract in rh-scheduling-operating-model.md. WF-00 numbers governance as its step 11. Turn on Open decisions to see which of OM-01 through OM-14 affects each step, and Who can act to see who performs it and where the owner is still undecided.

RH manufacturing scheduling cycle, print summary

Return paths:

Not ready: correct inputs and confirm again.
Blocking warning: correct the source, confirm again, and create another draft plan.
Material block: create a draft successor while the current released plan remains active.
Completion problem: correct the recorded work before approval.
Unresolved difference: record or correct actual work before closing.

RH may prepare tomorrow's schedule while the floor still performs today's

Four parts of the work move at the same time. While the scheduler prepares and reviews the next schedule, the floor keeps performing the official schedule that is already released. This table shows what each part is doing at each stage.

One official schedule, many views

The floor and every plan-based view should show the same official schedule. Forecasts and actual results must be labeled separately. Today two views build their own schedule instead of showing the released one, so this rule is not yet true.

Current-plan marker → Plan N

Official released plan

Locked lines · unique identifier and hash · release actor and time · replaces Plan N-1 only when a newer plan is released

Finding to resolve before cutover. Weekly Plan and Daily Plan build their own schedule from the open orders instead of only showing the released plan. Until that is corrected, the floor and reports cannot be guaranteed to show the same official schedule.

System support and controls
Evidence in the accepted prototype: renderWeeklyPlan() lines 18062-18123 flattens and schedules current open orders rather than projecting the released plan, and generateDayPlan() lines 20360-20429 adds assignment behavior before consuming scheduled rows. Proposed remediation: characterize both paths and move them into candidate generation, or label them advisory, before any single-authority cutover.

Plain-language key

The exact technical names remain available in the detail panel and canonical specifications. This key explains the terms used in the review package.

Draft plan (candidate)The optimizer's proposed plan. The floor does not follow it until it is released.

Official released planThe one current plan the floor and reports must use.

Recorded outcome (disposition)What happens next to an item or block: for example, schedule, correct, hold, resume, or cancel.

Actual work recordedWhat was actually produced, when it happened, and any difference from the plan.

Approve completionCheck a submitted completion before inventory, shipment, booking, or reporting effects can post.

Compare and explain differencesCheck the plan, actual work, inventory, customer status, shipment, and reports before closing.

Operating Flow Explorer