Short answer: archive a heat-treatment record as an identifiable package, not as an isolated CSV. Keep the raw time series, batch and furnace identity, events, corrections, report version and retrieval index together; then prove that the package can be restored.
Long-term retrieval usually fails before storage capacity runs out. A missing heat number, a workstation clock that drifted, an operator's renamed spreadsheet or a report detached from its raw log can make perfectly readable data commercially useless.
Define the record before choosing storage
A durable record normally needs more than timestamp and temperature. Agree which fields make one run unique in your plant:
- batch, heat, job or work-order identity;
- furnace, zone and channel identity;
- sensor type and relevant calibration/correction context;
- start, stop, interruption and restart events;
- operator, recipe or customer fields only where the process requires them;
- raw data plus the exact report version generated from it.
Use retention layers deliberately
A useful architecture can keep recent production data in a fast local database, replicate it to a plant server, and move older immutable packages to lower-cost storage. Local, LAN, managed cloud or hybrid are project choices. The important questions are whether recording continues during a network failure, how replicas reconcile, and which copy is authoritative.
| Layer | Purpose | Question to settle |
|---|---|---|
| Acquisition store | Continue recording close to the furnace | What happens on power loss or full storage? |
| Operational archive | Fast search and routine report regeneration | Which identifiers and indexes are mandatory? |
| Backup / cold copy | Recovery after loss or corruption | Who tests restoration, and how often? |
Make integrity visible
Restrict silent overwrites. Record who or what regenerated a report, which software/report template version was used, and whether a correction value changed. File hashes or signed packages may be useful in higher-assurance environments, but they do not rescue weak identity or missing raw data.
Test retrieval with a real question
- Choose an older batch using only the information a customer or auditor would provide.
- Find its report, raw series, alarms/events and relevant identities.
- Open the package on a maintained system rather than the original operator PC.
- Confirm that the report can be explained from the preserved record.
- Document the time taken and every manual workaround.
The storage calculator estimates raw capacity. Add space for indexes, reports, events, replication and backup; capacity is only one part of archival design.