# Schedule recovery system map: MES, ERP, CMMS keys | SourceX

Canonical: https://refer.sourcex.si/guides/production-schedule-recovery-records-across-systems
Last updated: 2026-11-04

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.

This system map is part of the guide on [production schedule change logs](/data-types/production-schedule-change-log). The [worked hard case](/guides/production-schedule-recovery-exception-examples) 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.

| System | Record it holds in a recovery | Linking key it carries | Usual owner |
|---|---|---|---|
| MES | Downtime events, operation starts and stops, piece counts | Order and operation number; machine ID; timestamps | Manufacturing systems lead |
| ERP | Production orders, missing part status, partial and final confirmations, purchase orders | Order and operation number; material; dates | ERP administrator, plant controller |
| Scheduling tool | Sequence changes, rescheduled dates, scenario runs, comment fields | Order and operation number; work center | Planning manager |
| Maintenance system | Work orders, failure codes, repair times | Asset ID; sometimes the production order | Maintenance manager |
| Quality system | Holds, inspection results, dispositions | Notification number; production order; batch | Quality manager |
| Email and chat | The reason for the decision, approvals, customer agreement | Time and machine name only, unless someone typed the order number | IT, 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.

| From | To | Linking key | Strength |
|---|---|---|---|
| MES | ERP | Order and operation number | Strong when integrated |
| MES | Maintenance | Asset ID plus downtime start time | Strong for the machine, medium for the order |
| ERP | Scheduling tool | Order and operation number | Strong |
| ERP | Quality | Production order on the notification | Medium; depends on a required field |
| Maintenance | ERP | Production order on the work order | Weak; often left blank |
| Email | Any | Time window and machine name | Weak; 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.

| Time | System | Record | Key used to join it |
|---|---|---|---|
| Wed 03:10 | MES | Downtime event, press 14, cause code hydraulic | Machine ID and timestamp |
| Wed 03:25 | Maintenance | Work order for pump replacement, estimate 4 days | Asset ID press 14; downtime start |
| Wed 06:40 | ERP | Missing part status on the customer's delivery | Order number |
| Wed 09:15 | Email | Plant manager approves moving the mold to a sister plant's 500-ton press | Time window and "press 14" in the subject |
| Wed 09:50 | Scheduling tool | Order resequenced to the sister plant; two jobs pushed | Order and operation number |
| Fri 14:00 | Quality | First-article inspection at the sister plant passes | Notification citing the order |
| Mon 18:00 | ERP | Partial confirmation 70,000 at plant 1; final confirmation 50,000 at plant 2 with 600 scrap | Order 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](/guides/preserve-production-schedule-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](/guides/msp-for-manufacturing-companies) and the [metadata-only inventory guide](/guides/how-to-prepare-a-metadata-only-inventory-of-business-systems); related records are on the [maintenance data page](/data-types/maintenance-data-ai-training) and the [manufacturing industry page](/industries/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 can name the key that joins each pair of its systems and say where the reasons are written, [register as a partner](/register), confirm the company against [who qualifies](/who-qualifies), and read the [program terms](/terms) before introducing its decision-maker.

## Sources

- https://www.isa.org/products/ansi-isa-95-00-04-2018-enterprise-control-system-i
- https://help.sap.com/docs/s4hana-cloud-best-practices/quality-management-in-discrete-and-process-manufacturing-1e1-jp/confirm-production
- https://help.sap.com/docs/PRODUCT_ID/34de0103497c4b80a7c7fbf6952ff971/db02b753128eb44ce10000000a174cb4.html
- https://refer.sourcex.si/terms
