Back to all posts
Plant Data7 min read·October 26, 2026

How Long Should You Keep Plant Historian Data?

TB
ThynkBlox Automation Team
Automation Engineering

How long to retain plant historian data should depend on its operational purpose and the record obligations that apply to your site. Set separate retention rules for detailed readings, summaries and investigation records. Before approving deletion, confirm what each record supports, whether an applicable obligation requires it, and who can authorise its removal.

Last reviewed: October 2026.

What should determine your retention periods?

Start with the questions people need the data to answer. An operator investigating a recent trip needs different detail from a manager comparing energy use across production campaigns.

For each use, ask:

  • What decision or investigation depends on this record?
  • How far back must someone be able to look?
  • What detail would make the record useful?
  • What event starts the retention period?
  • Who confirms that the proposed period meets applicable obligations?

Check the requirements relevant to your products, industry, contracts and location with the responsible quality or legal adviser. Use the relevant official portal for current requirements. Do not treat a historian supplier's default setting as evidence that your record obligations are covered.

Where several requirements apply to the same record, resolve them together before setting deletion rules. Longer storage should have a stated purpose too.

Should raw readings and summaries have different rules?

Usually, they deserve separate decisions. First define what “raw” means in your installation: every acquired sample, every stored change, or another form of detailed record. Document any filtering or compression applied before storage.

An aggregate is a summary calculated from a set of readings. Its usefulness depends on what you retain and how you calculate it.

Consider this illustrative example: two sets of readings are 40, 40, 40 and 20, 40, 60. Both average 40. Keeping only the average removes the difference between the steady condition and the changing one.

A minimum and maximum would preserve more information, but would still omit the order of those readings. Choose summaries around the questions they must answer.

Record typeIntended useRetention decision to make
Detailed process readingsReconstruct a trip or process changeHow far back is detailed reconstruction needed?
Aggregated trendsCompare shifts, campaigns or operating periodsWhich calculations and context make comparisons meaningful?
Batch-linked recordsInvestigate a particular production batchWhich readings, events and supporting records belong together?
Investigation extractsPreserve evidence for an open issueWho controls the hold and authorises its release?
Tag definitions and configuration historyInterpret older recordsWhat must remain available alongside the values?

For summaries used in performance reporting, retain the calculation definition and relevant exclusions. Our guide to what the OEE number hides offers a useful starting point for deciding what a performance figure needs to explain.

What should you preserve for batch investigations?

Define a batch investigation package before an investigation is needed. Make it possible to connect the process readings to the batch being examined.

Depending on the process, your proposed package might include:

  • Batch identity, equipment and production start and finish.
  • Relevant process readings and their quality indicators.
  • Recipe or setpoint versions.
  • Alarms, operator actions and recorded interruptions.
  • References to quality results and material records held elsewhere.

Choose these records with production and quality staff. Do not assume that every related record belongs in the historian; agree how records in different systems will be located and connected.

Also decide whether the investigation needs time before the batch started or after it finished. For example, an illustrative investigation into heating behaviour might include the preceding warm-up period.

Put relevant records on hold when an investigation requires preservation. Record the scope, owner and release condition. Confirm whether automatic deletion actually respects that hold; a note in an investigation report is not sufficient verification.

What would a practical retention schedule look like?

Use one schedule for record classes with similar purposes. Avoid assigning every tag a unique rule unless its use requires one.

The following is an illustrative decision schedule, not a recommended storage duration or statement of legal requirements.

Record classProposed approachCondition before deletion
Routine troubleshooting readingsKeep detailed records through an agreed investigation windowOperations confirms the window covers the intended use
Long-term operating trendsRetain agreed summaries and calculation definitionsValidate summaries before deleting their source detail
Batch investigation recordsRetain the agreed batch packageQuality confirms applicable obligations and checks for holds
Temporary commissioning tagsReview at project handoverThe project owner confirms which records remain necessary
Records under an active holdPreserve the defined scopeThe hold owner formally releases it

For each row, add the actual duration, its starting event, the approving owner, the storage location and the retrieval requirement.

Separate these decisions from storage capacity planning. Work out what the plant needs to preserve first, then assess how to store it.

How will you retrieve archived records?

An archive is useful only if the people who need it can retrieve and interpret its contents. Give retrieval an acceptance test.

Choose a representative older period and ask an authorised user to retrieve it through the agreed process. Check that the result includes the requested time range, tag identities, units, timestamps and quality information. Confirm that any supporting batch references remain usable.

Set an acceptable retrieval time according to the use. An investigation needed during production may require a different arrangement from an occasional historical review.

Document:

  • Who requests access and who fulfils the request.
  • Which software, permissions and equipment retrieval requires.
  • How missing or unreadable records are reported.
  • Who maintains the archive after system changes.
  • How retrieval will be tested again.

Include an archive retrieval test when planning a historian replacement or controls upgrade. Our guide to planning a PLC retrofit around a shutdown window can help place that work within the wider project plan.

Who should own deletion decisions?

Assign a named business owner to approve each retention rule. The person operating the historian should implement the approved decision and report failures, rather than decide alone which production evidence has lost its value.

A practical division of responsibility is:

  • Operations: defines troubleshooting and operating-history needs.
  • Quality or the relevant record owner: confirms product-record needs and investigation holds.
  • Legal or the designated adviser: resolves applicable legal and contractual questions.
  • The system administrator: configures the rule and verifies its behaviour.
  • The accountable approver: accepts the final schedule and subsequent changes.

Record each approved change, its scope and when it takes effect. Treat a shorter retention period as a deletion decision because it may affect records already stored.

Put these responsibilities into the functional design specification, alongside archive access and failure handling.

What common mistakes should you avoid?

Giving every tag the same retention period. Group records by purpose, then document justified exceptions.

Deleting detail before checking the summaries. Compare representative summaries against the detailed records and the questions users expect them to answer.

Keeping values without their meaning. Include the units, tag descriptions and relevant configuration history in your preservation plan.

Treating an archive export as a completed handover. Test retrieval and interpretation with the intended user.

Leaving automatic deletion unowned. Assign someone to review failures, holds and proposed rule changes.

Keeping everything indefinitely without review. Require an explicit decision about purpose, access and eventual disposal.

What questions do plant teams ask most often?

Can we keep only averages?

Only if averages support every intended use of those records and the applicable record requirements permit it. Review investigation needs before removing detailed readings.

Should every batch use the same retention rule?

Use a shared rule where the purpose and obligations are the same. Document exceptions where products, contracts or investigation needs differ.

Does moving records to an archive count as deletion?

Define the distinction in your schedule. Archiving should preserve the agreed ability to retrieve and use records; deletion removes that ability for the affected copy.

What if nobody can justify an existing retention period?

Do not shorten it by guesswork. Identify the record owner, review actual uses and obligations, test retrieval, then approve a documented decision.


Need help defining historian retention and archive responsibilities? Explore our plant automation services or contact us to discuss the records your plant needs to keep.

Next step

Want to apply this to your plant?

Every project starts with a fixed-fee assessment, and you can stop after the report.