Plant closure checklist: preserving records before systems shut off

What a plant closure records checklist protects#

A plant closure records checklist protects three things: records the company must keep, records needed to answer warranty, product and environmental questions after closing, and operating history that may have value. Plants spread these records across more systems than most businesses, from ERP and MES to quality, maintenance, historians and controllers.

The risk comes from the order of events. Notices trigger departures, equipment sales trigger hardware removal, and cost cutting triggers subscription cancellations. Each one can erase records unless the checklist runs ahead of it. The closure notices themselves may be governed by the WARN Act and state equivalents, which counsel should assess separately.

Stage one: before closure notices go out#

Before closure notices go out, the priority is capturing knowledge: who administers each system, where records live and which records carry restrictions. Once the announcement lands, the IT lead, the quality manager and the maintenance planner may start looking for new jobs.

Plants often run critical records in places no subscription list shows: an Access database the quality team built, a spreadsheet of calibration due dates, a shared folder of setup sheets. Ask each department head to name those before the announcement.

• 1List every plant system, including spreadsheets and shared folders that act as systems.
• 2Record each system's administrator, vendor, contract end date and export route.
• 3Ask key staff to document where records live, and arrange stay terms for the people the records work depends on.
• 4Pause automatic deletion in email, file shares and backup rotation.
• 5Flag customer-owned drawings, specifications and tooling data that must be returned or destroyed under customer agreements.
• 6Flag export-controlled technical data so it is handled under the company's export compliance procedures.
• 7Confirm with counsel whether any claims, recalls or environmental matters require a legal hold.

Stage two: before subscriptions and support contracts lapse#

Before subscriptions and support contracts lapse, each system's records should be exported in a form someone can still read after the vendor relationship ends. For older on-premises systems, that usually means a database backup plus an image of the server that runs the application.

Keep support contracts or licenses long enough to verify that each export opens. A database you cannot query without a license you no longer hold is a preservation copy, not a usable record.

Stage three: before hardware is sold, scrapped or recycled#

Before hardware leaves the site, every server, workstation, storage device and controller should be checked for records that exist nowhere else, then imaged, wiped or destroyed with a log. Equipment auctions and scrap contracts move quickly once the production floor goes quiet.

Machines sold with their controllers can carry programs and parameters that reflect process know-how. Decide before the sale whether those programs transfer with the equipment, are backed up and removed, or are wiped.

• 1Image servers and engineering workstations that hold application data or PLC and HMI programs.
• 2Back up controller programs and configurations before machines are sold with their controls.
• 3Collect backup tapes and external drives, and record what each one contains.
• 4Wipe or destroy drives using a documented method, and keep certificates from any recycler.
• 5Remove company data from leased copiers, printers and network equipment before return.

Which plant records deserve a value review#

Plant records that deserve a value review are the ones that capture decisions and outcomes: nonconformances and their corrective actions, maintenance work orders with failure causes, quote-to-order histories and supply exceptions. They show how an experienced team solved problems, which is the kind of operational record AI developers license.

The review starts with metadata only and does not delay the closure. What it changes is the order of destruction: candidate records stay in storage until the review and any rights questions are settled.

Illustrative: a castings company closes one of its two plants#

Illustrative: Pell River Castings, a fictional foundry group, consolidates production and closes its older plant. That plant runs Epicor E9 on an on-premises server, a standalone QMS for NCRs and CAPAs, a CMMS used by the maintenance team and a historian that records furnace temperatures.

Before the announcement, the plant manager asks the IT lead and the quality manager to document admins, contract dates and export routes, and the company offers both of them stay terms through the shutdown. The Epicor database is backed up with an image of the application server, because the surviving plant runs a newer version that cannot open the old data directly. Customer pattern drawings are returned under the customer agreements.

The value review identifies years of NCRs linked to CAPAs and maintenance history linked to failure codes. Leadership authorizes a rights review of that slice. Servers and workstations are wiped under certificates after imaging, and the images go to encrypted storage at the surviving plant, with the quality manager named as custodian.

How SourceX approaches a closing plant's records#

SourceX approaches a closing plant's records with a metadata-only fit check that excludes customer-owned designs and export-controlled work from the outset. Large exports, such as ERP databases and historian archives, stay in the company's own storage or ship on encrypted drives; SourceX does not host multi-terabyte datasets.

If a package proceeds, the SourceX five-step transaction moves through Supply, Rights, Preparation, Approval and Delivery, and the SourceX Evidence Packet documents provenance and the release authorization the company signs.