This worked case is part of the guide on production schedule change logs. The main guide explains which record types exist. Here the job is one hard case, walked through step by step, ending with how to spot similar cases at a client.
Step 1: the furnace trips with the batch half done
Illustrative and invented for this page. A 310-person maker of industrial gearboxes carburizes gears in two batch furnaces. Furnace 1 is the only one with a fixture sized for a 600-gear lot of large ring gears due to final assembly on Thursday.
On Monday at 22:15 the furnace's burner management system trips during the third load. Two loads, 240 gears, have finished the full cycle. Eighty gears are in the furnace mid-cycle. The remaining 280 are waiting.
| Record | System | Holder | What it shows |
|---|---|---|---|
| Burner trip alarm with timestamp | Furnace controller and data logger | Heat-treat lead | The exact moment and cause code of the stop |
| Downtime event against furnace 1 | MES | Shift supervisor | When the stop began, logged within minutes |
| Maintenance work order | Maintenance system | Maintenance planner | The repair request and its estimated duration |
Nothing yet tells anyone the Thursday assembly is at risk. A stopped machine is only an exception once someone connects it to a promised date.
Step 2: the alert that the plan no longer holds
On Tuesday at 07:30 the planner reruns availability for the assembly order. It now shows 360 ring gears short for Thursday.
| Day | Action | Who | Record it left |
|---|---|---|---|
| Tue 07:30 | Availability rerun on the assembly order | Planner | Missing part status on the assembly order |
| Tue 08:00 | Maintenance estimate: burner valve on order, three days | Maintenance planner | Updated work order with parts request |
| Tue 08:20 | Morning meeting flags the gap | Plant manager | Meeting notes or chat thread |
This is the step most often lost. In SAP, for example, a failed availability check sets a missing part status in the order header, but the availability log itself is not kept once the user leaves the order; the missing parts overview shows only the last check, and date or quantity changes do not automatically rerun it. A plant can keep the status and lose the evidence of when, and how badly, the plan broke.
Step 3: the branch point, wait or send it out
Two options are on the table. Waiting for the burner valve means the gears ship next Tuesday. Sending the 280 untreated gears to a commercial heat treater, at extra cost and with a first-article check, means Friday.
The plant manager chooses outside processing on Tuesday at 10:00, and the customer service lead gets the customer's agreement to a Friday ship date.
| Decision | Decided by | Record it left |
|---|---|---|
| Send 280 gears to an outside heat treater | Plant manager | Approval email; outside processing purchase order |
| Accept a Friday ship date | Customer service lead with the customer | Updated sales order date; customer email |
| Move a lower-priority spline shaft job to furnace 2 overtime | Planner | Rescheduled operation dates in the scheduling tool |
The approval email carries the reasoning: cost against a four-day slip. If the scheduling tool's comment field was left empty, as it often is, that email is the only record of why.
Step 4: the 80 gears caught mid-cycle
The 80 gears in the furnace at the trip have an incomplete carburizing cycle. The quality manager places them on hold and orders hardness and case-depth tests on samples.
| Day | Action | Who | Record |
|---|---|---|---|
| Tue 11:00 | Hold on 80 gears | Quality manager | Quality notification with hold status |
| Wed 14:00 | Sample tests show case depth below specification | Metallurgical lab | Test report attached to the notification |
| Wed 16:00 | Disposition: 80 gears re-treated at the outside heat treater | Quality manager with engineering | Disposition on the notification; amended purchase order |
Now the outside order covers 360 gears, not 280. That change is visible only if the purchase order amendment and the quality notification can be read together.
Step 5: completion and what was confirmed
| Day | Confirmation | Quantity | System |
|---|---|---|---|
| Mon | Partial confirmation, in-house heat treat | 240 yield | ERP production order |
| Thu | Goods receipt from outside heat treater | 360 received | ERP purchasing |
| Thu | Final confirmation after inspection | 358 yield, 2 scrap | ERP production order |
| Fri | Assembly order confirmed and shipped | 1 lot | ERP and shipping |
SAP documents that production confirmations can be partial or final and carry yield and scrap quantities, so the completion end of the chain is usually the most solid. The lot ships Friday, on the date agreed with the customer, with two gears scrapped and 598 good gears against the 600 planned; the assembly used spares from stock for the shortfall.
Why this sequence is useful evidence
Every judgment in the case can be checked against a dated record: when the furnace stopped, when the shortage was recognized, what options existed, who chose outside processing and why, how the mid-cycle parts were tested and dispositioned, and what was finally built. ISA-95 Part 4 defines object models for exchanging scheduling, performance and work-record data between business and plant systems, so business and plant systems built around it are designed to share order and operation keys. The decisions, though, sit in email, quality notifications and purchase order amendments. A plant that kept all of them holds a complete worked problem, not just a schedule. The system map shows how each record joins to the next.
Recognizing similar cases at a client
MES consultants, lean advisors and maintenance specialists can spot companies with cases like this without seeing a record. Ask the plant operations director:
- Do constrained machines fail mid-batch a few times a year? Furnaces, presses, five-axis centers and paint lines are typical.
- Is the shortage visible as a status, and is the rerun kept anywhere? That is the record most often missing.
- Where does the reason for a reschedule get written? If the answer is email, the history is still there, but joined only by time and machine.
- Do quality holds and outside processing orders reference the production order?
- Which systems and years hold all of this, and is any of it about to change?
Then introduce the person who can authorize a licensing discussion, the CEO, with the plant operations director as working contact; see who can license these records. Customer drawings inside orders and employee names on approvals are for SourceX's rights review, not the partner. The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Related records appear on the maintenance data page, in logistics exceptions and across manufacturing.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If a plant you advise keeps the alarms, holds, approvals and confirmations that tell recoveries like this one, register as a partner, check the company against who qualifies, and read the program terms before introducing its decision-maker.