Production schedule recovery hard case: a heat-treat furnace fails mid-batch, decision by decision

Short answer

The records that explain how a plant handled a production exception are the ones that capture each decision as it happened: the equipment alarm and the downtime event, the shortage status on the orders that could no longer be met, the rescheduling choice and who approved it, the quality decision on parts caught mid-process, any outside processing order, and the partial and final confirmations that show what was actually built. Lined up in time, they let a reviewer test every judgment the plant made.

Visual briefFull-size diagram
A case timeline runs from Monday to Friday, branches after the Monday night furnace trip into a path not taken, waiting for repair, and the path chosen, outside heat treat, with each decision showing the record it left and ending in a Friday shipment.
Illustrative case invented for this page. Quantities, days and roles are fictional.

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.

RecordSystemHolderWhat it shows
Burner trip alarm with timestampFurnace controller and data loggerHeat-treat leadThe exact moment and cause code of the stop
Downtime event against furnace 1MESShift supervisorWhen the stop began, logged within minutes
Maintenance work orderMaintenance systemMaintenance plannerThe 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.

DayActionWhoRecord it left
Tue 07:30Availability rerun on the assembly orderPlannerMissing part status on the assembly order
Tue 08:00Maintenance estimate: burner valve on order, three daysMaintenance plannerUpdated work order with parts request
Tue 08:20Morning meeting flags the gapPlant managerMeeting 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.

DecisionDecided byRecord it left
Send 280 gears to an outside heat treaterPlant managerApproval email; outside processing purchase order
Accept a Friday ship dateCustomer service lead with the customerUpdated sales order date; customer email
Move a lower-priority spline shaft job to furnace 2 overtimePlannerRescheduled 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.

DayActionWhoRecord
Tue 11:00Hold on 80 gearsQuality managerQuality notification with hold status
Wed 14:00Sample tests show case depth below specificationMetallurgical labTest report attached to the notification
Wed 16:00Disposition: 80 gears re-treated at the outside heat treaterQuality manager with engineeringDisposition 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

DayConfirmationQuantitySystem
MonPartial confirmation, in-house heat treat240 yieldERP production order
ThuGoods receipt from outside heat treater360 receivedERP purchasing
ThuFinal confirmation after inspection358 yield, 2 scrapERP production order
FriAssembly order confirmed and shipped1 lotERP 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.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Why use a case where something went wrong?

Because a recovery has several decisions, each with a reason and an owner. A batch that runs to plan leaves one confirmation and explains nothing about judgment.

Does the plant need to have handled the exception well?

No. A late shipment or a scrapped load is still a complete case if the alert, the decisions and the outcome were recorded. The record matters, not the score.

Should a partner ask for the actual records of a case like this?

No. Ask whether such cases happen, which systems capture each step and for how many years. Never ask for orders, logs or emails.

Sources

  1. help.sap.com/docs/PRODUCT_ID/34de0103497c4b80a7c7fbf6952f…
  2. help.sap.com/docs/s4hana-cloud-best-practices/quality-man…
  3. isa.org/products/ansi-isa-95-00-04-2018-enterprise-c…
  4. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment