Production schedule recovery system map: which system holds each record and the keys that join them

Short answer

Reconstructing a production schedule recovery takes five kinds of link: the production order and operation number shared by the MES and the ERP, the machine or asset ID shared with the maintenance system, the maintenance work order or quality notification number where those records cite the order, timestamps in every system, and a time window plus machine name to attach the email or chat where the reason was written. With those joins, one case reads end to end; without them, it is five unrelated lists.

Visual briefFull-size diagram
Six system nodes, MES, ERP, scheduling tool, maintenance system, quality system and email, arranged around one recovery case; keys labeled order and operation, asset ID, work order, notification and time window travel along the connectors to join them.
Illustrative map. The email link is joined by time window and machine, the weakest key on the map.

This system map is part of the guide on production schedule change logs. The worked hard case follows one recovery decision by decision; this page maps where each record sits and what joins it.

The six systems on the map

Most plants hold a recovery across six places. Not every plant has all six, and some combine two in one product.

SystemRecord it holds in a recoveryLinking key it carriesUsual owner
MESDowntime events, operation starts and stops, piece countsOrder and operation number; machine ID; timestampsManufacturing systems lead
ERPProduction orders, missing part status, partial and final confirmations, purchase ordersOrder and operation number; material; datesERP administrator, plant controller
Scheduling toolSequence changes, rescheduled dates, scenario runs, comment fieldsOrder and operation number; work centerPlanning manager
Maintenance systemWork orders, failure codes, repair timesAsset ID; sometimes the production orderMaintenance manager
Quality systemHolds, inspection results, dispositionsNotification number; production order; batchQuality manager
Email and chatThe reason for the decision, approvals, customer agreementTime and machine name only, unless someone typed the order numberIT, under company policy

ISA-95 Part 4 defines object models and attributes for exchanging scheduling, performance and work-record data between business and plant systems. Plants that follow it tend to share order and operation keys cleanly between the ERP and the MES. The standard does not reach the planner's inbox, which is why the last row is almost always the weak one.

The keys that travel between systems

Read the map as pairs. Each pair has one key that should travel between the two systems.

FromToLinking keyStrength
MESERPOrder and operation numberStrong when integrated
MESMaintenanceAsset ID plus downtime start timeStrong for the machine, medium for the order
ERPScheduling toolOrder and operation numberStrong
ERPQualityProduction order on the notificationMedium; depends on a required field
MaintenanceERPProduction order on the work orderWeak; often left blank
EmailAnyTime window and machine nameWeak; joined by inference

The ERP's own alert can be a gap. SAP documents that a failed availability check sets a missing part status in the order header, but the availability log is not kept after the user exits the order, and the missing parts overview shows only the last check. On the map, the alert may exist only as a status with no timestamp of its own, so the MES downtime time often stands in for it.

One case joined end to end

Illustrative case, invented for this page. A 280-person custom injection molder runs a 120,000-part order for appliance housings on press 14, its only 450-ton press with the right platen size. On Wednesday at 03:10, with 70,000 parts molded, the press's hydraulic pump fails.

TimeSystemRecordKey used to join it
Wed 03:10MESDowntime event, press 14, cause code hydraulicMachine ID and timestamp
Wed 03:25MaintenanceWork order for pump replacement, estimate 4 daysAsset ID press 14; downtime start
Wed 06:40ERPMissing part status on the customer's deliveryOrder number
Wed 09:15EmailPlant manager approves moving the mold to a sister plant's 500-ton pressTime window and "press 14" in the subject
Wed 09:50Scheduling toolOrder resequenced to the sister plant; two jobs pushedOrder and operation number
Fri 14:00QualityFirst-article inspection at the sister plant passesNotification citing the order
Mon 18:00ERPPartial confirmation 70,000 at plant 1; final confirmation 50,000 at plant 2 with 600 scrapOrder and operation number

Totals line up: 70,000 good parts from press 14 and 50,000 from the sister plant meet the 120,000 order, with 600 scrapped in setup. SAP documents that confirmations can be partial or final and carry yield and scrap, which is why the last row joins cleanly. The email row is the only one that relies on inference, and it is the one that explains why the mold moved.

Where the map usually breaks

Three breaks show up again and again:

  • Maintenance to order. Work orders name the asset but not the production order, so the repair joins the machine, not the customer delivery.
  • Reason text. Scheduling tool comment fields are often empty; the reason survives only in email, joined by time.
  • Cross-plant moves. When work moves to another site, the second plant may create a new order number, breaking the operation key unless someone links them.

A partner does not test these breaks; the company's systems people describe them. For the archive side, including what disappears first when a tool is replaced, see preserving recovery records.

Questions for the plant, and who owns the answers

Ask the plant operations director and the manufacturing systems lead, at metadata level only:

  • Which of the six systems does the plant use, and since when?
  • Does the maintenance work order carry the production order number?
  • Do quality notifications require the order number?
  • Where is the reason for a reschedule usually written?
  • What happens to order numbers when work moves between plants?

Ownership is usually split: operations owns the MES and scheduling, finance owns the ERP, maintenance and quality own their systems, IT governs email under company policy. Running a system is not authority to license it; the executive who can authorize a licensing discussion is the CEO. What stays unknown until SourceX reviews it: customer ownership of part designs, employee data in approvals and whether the records fit any buyer's use. 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. IT partners can use the MSP guide for manufacturing companies and the metadata-only inventory guide; related records are on the maintenance data page and the manufacturing industry page.

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 can name the key that joins each pair of its systems and say where the reasons are written, register as a partner, confirm 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

What if the plant has no separate scheduling tool?

Then the ERP holds the date changes and the planner's spreadsheet or whiteboard photos hold the sequence. Put whatever holds the decision on the map; the keys are the same.

Is a time-window join good enough?

It is weaker than a shared key but often the only way to attach email and chat. It works best when the machine is named in the message and the window is narrow.

Does SourceX connect to the MES or ERP to build the joins?

Do not assume so. Partners name systems only. How records would be extracted and joined is agreed with the company after it applies and a rights review starts.

Sources

  1. isa.org/products/ansi-isa-95-00-04-2018-enterprise-c…
  2. help.sap.com/docs/s4hana-cloud-best-practices/quality-man…
  3. help.sap.com/docs/PRODUCT_ID/34de0103497c4b80a7c7fbf6952f…
  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