This retention timeline is part of the guide on production schedule change logs. The system map shows where each record sits; this page shows when each one is at risk.
The timeline: what disappears first
Illustrative timeline, invented for this page. A 450-person maker of agricultural implements signs for a new advanced planning and scheduling tool. Go-live is in month 6, the old tool's license ends in month 9 and the old MES database is decommissioned in month 18. Every date below is fictional; real ones come from the company's own contracts and policies.
| When | Record type | What happens to it | Why at that point |
|---|---|---|---|
| Already gone | Availability check logs | Not stored after the planner leaves the order | System behavior, not policy |
| Month 3 | Planner chat messages | Deleted under a 90-day chat retention rule | Company retention setting |
| Month 9 | Scenario runs and sequence history in the old tool | Unreadable when the license ends | Vendor contract |
| Month 12 | Mailboxes of planners who left | Purged a year after departure | Company retention setting |
| Month 18 | MES downtime and piece-count history | Lost when the old database is switched off | IT decommission plan |
| Retained | Closed production orders and confirmations | Archived and retrievable | ERP archiving process |
The first row is the surprise for most people. SAP documents that a failed availability check sets a missing part status in the order header, but the availability log itself is not kept after the user exits the order; the missing parts overview shows only the last check, and a check at release is written to the release log. So in plants that work this way, the moment an alert was raised was never kept at all, and only the status and the release log survive.
How each record class tends to be kept
Retention varies by company, contract and law, so there are no standard periods to quote. What tends to be true is the mechanism, which a partner can ask about.
| Record class | What usually governs how long it lasts | Who can say | Question to ask |
|---|---|---|---|
| Shortage statuses and release logs | ERP configuration and archiving | ERP administrator | Are release logs archived with the order? |
| Rescheduled dates and scenario runs | The old tool's license and any migration scope | Planning manager, vendor contract owner | Does history migrate, or only open orders? |
| Downtime and fault events | The MES database's decommission plan | Manufacturing systems lead | Will the old database stay read-only, and until when? |
| Maintenance work orders | Maintenance system retention | Maintenance manager | Is the maintenance system changing too? |
| Confirmations with yield and scrap | ERP archiving residence times | Plant controller | Can archived orders be retrieved after cutover? |
| Reasons in email and chat | Company retention policy | IT, under policy set by legal | What happens to leavers' mailboxes? |
SAP documents that production orders are archived in stages: a deletion flag, then a deletion indicator after a residence time, then an archiving run that removes them from the database, with a retrieval function to display them later. That is why closed orders tend to outlast everything else on the timeline. ISA-95 Part 4 defines object models for exchanging scheduling, performance and work-record data between systems, but it does not decide whether closed history moves to a new tool; that is a separate decision in the migration scope.
Six dates to pin down before the cutover
Ask for each date in writing. If a date is not documented, write "unknown"; there is then no deadline to mention.
- Contract signature for the new tool. Starts the clock.
- Migration scope sign-off. Decides whether closed orders and history move.
- Go-live. After this, the old tool is rarely updated.
- Old license end. Scenario runs and sequence history become unreadable.
- Old database decommission. MES downtime history goes unless retained.
- Next retention purge. Chat and leavers' mailboxes, under the company's policy.
Who must approve keeping anything
Keeping records beyond their normal life is a company decision, not a partner's or a consultant's. It needs someone with authority over the records, acting within the company's retention policy, customer agreements and applicable law.
| Decision | Who usually approves | Who advises |
|---|---|---|
| Extend the old license read-only | CFO or COO | Planning manager, IT |
| Keep the old MES database read-only | CIO or IT director | Manufacturing systems lead |
| Include closed history in the migration | Project sponsor, often the COO | Integrator, planning manager |
| Change mailbox or chat retention | Legal and IT under company policy | Compliance |
| Discuss licensing any of the records | CEO, COO or CFO | Plant operations director |
The last row is separate from the others. Preserving records for operations does not mean the company has agreed to discuss licensing them; see who can license these records.
What a partner notes, and what it never does
A partner notes record classes, years covered, system owners, the documented dates above and who sponsors the conversation. A partner never recommends keeping data the company has not authorized, never copies or handles records, and never presents a retention date as urgency unless it is documented. What stays unknown until SourceX reviews it: rights in customer designs inside orders, employee data in email, SourceX's current data needs and any offer. 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.
The manufacturing screening worksheet covers the size and history checks that come first. If the system change is part of a closure, the plant closure page covers the different timeline, and lean manufacturing consultants explains how improvement advisors often see these projects first.
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 facing a scheduling or MES replacement can document its access dates and name who owns each record class, register as a partner, confirm the company against who qualifies, and read the program terms before introducing its decision-maker.