Long-Term Digital Archiving in Manufacturing: IT Director Inspects Archiving System in the Server Room
Korbinian HermannNov 19, 2026, 1:12:30 PM20 min read

Digital Long-Term Archiving: How to Keep Data Readable, Accessible, and Traceable

An auditor requests the screwdriving logs for a vehicle series from 2014. The data still exists, somewhere on a server nobody has touched for years. But the database version is no longer supported by the vendor, the application does not start, and the colleague who knew the table schema left the company long ago. The data is stored, but nobody can read it. This is the case digital long term archiving is designed for, and it shows whether a company has actually implemented it or only described it in its procedural documentation.

Key Takeaways
  • Digital long term archiving preserves digital data for ten years and more so that it remains readable, findable and unchanged despite changes in hardware, software and file formats.
  • The three core goals are readability through open, documented formats, availability through access independent of the source system and traceability through checksums, time stamps and complete logs.
  • The OAIS reference model according to ISO 14721 describes six functional entities: ingest, archival storage, data management, administration, preservation planning and access.
  • For manufacturing companies, periods typically range from 8 years for accounting vouchers (Section 147(3) of the German Fiscal Code) to 15 years for implantable medical devices (Article 10(8) MDR). The new EU Product Liability Directive 2024/2853 provides for 25 years in exceptional cases.
In a nutshell

Format, not backup

A backup protects against data loss, but not against format obsolescence.

Database as a package

Open packages such as SIARD make the legacy system unnecessary for data access.

Provide evidence

Check integrity, log every access, document every deletion.

Download the white paper for free

Digital long term archiving for a legacy system: quality engineer checks an inspection report on a retired industrial computer

 

01 · Definition

What is digital long term archiving?

Digital long term archiving is the lasting preservation of digital data so that it remains readable, available, unchanged and understandable for decades, regardless of the hardware, software or file formats in use later. The term comes from archives and libraries. It has become more common in industry since quality records, process data and design data are created almost exclusively in digital form.

A production database is designed for speed and changeability, a long term archive for stability: data is ingested once, never changed again and maintained throughout the retention period so that it can be retrieved at any time. The Association of German Business Archivists points out that in IT, long term archiving often refers to a period of no more than ten years, while archivists generally plan without a time limit. Manufacturing companies usually sit in between, as their periods result from law, standards and product liability risk.

Readable

The data is in a format that can be opened and interpreted even without the original application.

Available

Authorized people find the data in reasonable time without having to revive a legacy system.

Traceable

The archive proves that the data has been complete and unchanged since ingest and who accessed it when.

8 years

Retention of accounting vouchers in Germany since 1 January 2025

Source: Section 147(3) AO, amended by BEG IV

15 years

Technical documentation of implantable medical devices

Source: Article 10(8) Regulation (EU) 2017/745

25 years

Maximum liability period for latent personal injury

Source: Article 17 Directive (EU) 2024/2853

6

Functional entities in the OAIS reference model

Source: ISO 14721

A record created today may have to serve as evidence into the 2050s in extreme cases. The servers, operating systems and database versions it currently sits on will long have been replaced by then.

 

02 · Data decay

Why does digital data decay faster than paper?

A paper document loses its content gradually and visibly. A digital object often loses it suddenly and completely: a single missing program, an unknown character encoding or an unreadable storage medium is enough, and the information is practically lost even though every bit is still there. This is known as digital obsolescence.

The causes fall into six risk classes. Each needs its own countermeasure, and a classic backup helps with none of them.

Decay matrix: six risks to the readability of archived data
Risk What happens Countermeasure
Bit rot Individual bits flip unnoticed on the storage medium and the file becomes corrupted. Create checksums at ingest and verify them regularly; keep redundant copies at separate locations
Media aging Storage media become physically unreadable or matching drives disappear from the market. Media migration in fixed cycles, storage with built in integrity checks
Format obsolescence Current software can no longer open the file format or displays it incorrectly. Open, standardized archive formats; format monitoring and planned format migration
System dependency Data can only be interpreted through the original application, for example proprietary database schemas. Export into a system independent structure, for example SIARD or an archive database
Loss of context Nobody knows anymore what a field, a status code or a unit means. Archive metadata, data dictionary and procedural documentation along with the data
Key loss Encrypted or signed data can no longer be decrypted or verified. Central key management; renewed signatures and evidence records according to BSI TR 03125

For manufacturing data, system dependency and loss of context weigh particularly heavily. A screwdriving log is only evidence if it is clear which torque was measured in which unit against which target value and with which tool. This meaning rarely sits in the file itself but in the application’s data model. Anyone who shuts down the application without documenting and archiving the data model keeps numbers that nobody can make sense of in an audit.

The German Federal Office for Information Security (BSI) has therefore long recommended open standard formats for archiving documents and images, including PDF/A, XML, TIFF and JPEG. The principle applies to all data types: the less a format depends on a vendor, the more likely it is to still open in 15 years.

 

03 · Retention periods

Which retention periods apply to production and quality data?

How long data must be retained determines the effort of every archiving concept. In manufacturing, tax law, commercial law, industry standards and product liability overlap, and the longest applicable period counts for each data class.

Retention map: periods for production and quality data (Germany and EU)
Regulation Data concerned Period Reference
German Fiscal Code, Commercial Code Accounting vouchers, invoices 8 years Section 147(3) AO, Section 257(4) HGB (since 1 January 2025)
German Fiscal Code, Commercial Code Books, inventories, annual financial statements, organizational documents 10 years Section 147(3) AO, Section 257(4) HGB
German Fiscal Code, Commercial Code Commercial and business letters received and sent 6 years Section 147(3) AO, Section 257(4) HGB
IATF 16949 Quality records in the automotive industry Duration of production and service requirements plus one calendar year, unless otherwise specified by the customer or a regulatory agency IATF 16949 section 7.5.3.2.1
MDR Technical documentation, declaration of conformity At least 10 years after the last device was placed on the market, 15 years for implantable devices Article 10(8) Regulation (EU) 2017/745
EU product liability Evidence on design, manufacturing and testing Liability expires after 10 years, after 25 years for latent personal injury Article 17 Directive (EU) 2024/2853
GDPR Personal data, such as worker IDs Only as long as necessary for the purpose Article 5(1)(e) GDPR

Member states must transpose the new Product Liability Directive by 9 December 2026, and it applies to products placed on the market after that date. For older products in Germany, the ten years under Section 13 of the Product Liability Act (ProdHaftG) continue to apply.

Two details are easy to overlook. First, the German tax retention period only starts at the end of the calendar year in which the record was created, and under Section 147(3) AO it does not expire as long as the assessment period for the taxes concerned is still open. Second, IATF 16949 ties the automotive supplier to the product’s lifetime. If a part is produced for twelve years and then supplied as a spare part, 15 to 20 years of retention quickly add up.

Something similar applies in medical technology. There, the periods are tied to the last device placed on the market, not to the date the record was created.

When changing systems, Section 147(6) AO is worth a look. After a system change or an offloading from the production system, it is sufficient to keep the tax relevant data on a machine readable and evaluable data carrier once the fifth calendar year after the change has ended. Until then, the tax authority’s full data access must remain possible. Without an archive that provides this access, the legacy system may not be shut down at all.

White paper

Keep your data readable and provable

The CHRONOS white paper shows how to meet retention obligations without keeping legacy systems running and how to answer requests from auditors without a special project.

Download the white paper for free

 

04 · Formats

Which file formats are suitable for digital long term archiving?

The choice of format is the most important technical decision in an archiving project. A good archive format is openly documented, ideally standardized and widely used. It contains no encryption or copy protection and carries all information needed to render it. Proprietary formats are not ruled out, but they need an export path into an open format.

Format ladder: recommended archive formats per data type in manufacturing
Data type Archive format Standard or specification What to watch out for
Inspection reports, certificates, text documents PDF/A ISO 19005 Fonts embedded, no external references, no active content
Scanned documents, photos, microscope images TIFF or PNG TIFF 6.0, ISO/IEC 15948 Lossless compression, document the resolution
Tables, measurement series, exports CSV RFC 4180 Describe character encoding, delimiter, units and column meaning separately
Structured data, master data XML or JSON with schema W3C XML Schema, JSON Schema Always archive the schema as well
Relational databases SIARD eCH 0165 Tables, keys, relationships and metadata in one open package
3D design data STEP ISO 10303 Also keep the native CAD format as long as the software is available
Process curves, screwdriving curves CSV or XML plus metadata Vendor neutral Store sampling rate, unit, target values and tool reference as context

SIARD is particularly interesting for manufacturing companies. The acronym stands for Software Independent Archiving of Relational Databases. The format was developed by the Swiss Federal Archives and published as the eCH 0165 standard. It stores the content of a relational database as a ZIP package with XML files and also describes primary keys, foreign keys and column types. A database from an MES, an inspection system or an ERP thus remains evaluable even when the original database software has long since stopped being licensed.

No format guarantees readability forever. PDF/A also comes in several parts, and validation tools change. After choosing formats, someone therefore has to monitor whether they remain supported. The OAIS model calls this task preservation planning.

 

05 · OAIS

How does the OAIS reference model according to ISO 14721 work?

The OAIS reference model (Open Archival Information System) is the international standard for digital long term archives and is standardized as ISO 14721. It does not prescribe any technology. It describes the tasks an archive has and how information flows through it. Other standards are based on it, such as DIN 31644 with criteria for trustworthy digital archives from the German nestor network and ISO 16363 for auditing such archives.

SIP · Submission package

Submission Information Package: comes from the source system.

AIP · Archival package

Archival Information Package: is stored permanently and contains data plus preservation metadata.

DIP · Dissemination package

Dissemination Information Package: is delivered to the user on request.

Six functional entities work in between:

OAIS path: the six functional entities according to ISO 14721 in manufacturing
No. Functional entity Task Example from manufacturing
1 Ingest Receive data, check it, convert it into archival packages Export of inspection data from a system being replaced, with record count
2 Archival storage Store archival packages securely, check integrity, migrate media Storage with checksums and a copy at a second location
3 Data management Maintain descriptive metadata, enable search Search by serial number, batch or order number
4 Administration Operation, rules, access rights, agreements with data producers Retention plan and role model for QM and IT
5 Preservation planning Monitor technology, plan format migration Annual check whether archive formats are still supported
6 Access Handle requests, create dissemination packages Audit report as PDF or data export for a complaint case

An industrial company does not need OAIS certification, but the model works well as a checklist. Does each of the six functional entities have an owner and a tool in your archiving concept? Where it does not, there is a gap. A typical gap is preservation planning: the archive is filled, but nobody is responsible for whether the formats will still be supported in ten years.

 

06 · Evidence

How does archived data stay traceable and valid as evidence?

An auditor or a court also wants to know whether the record presented is the same one created twelve years ago. Five building blocks support this proof:

01

Checksum at ingest

The archive creates a cryptographic hash for each object, for example with SHA 256, and stores it separately. If the value differs later, the object has been changed.

02

Regular integrity checks

Checksums are verified against the stock at fixed intervals. Bit rot is detected before all copies are affected.

03

Immutable storage

Archived data sits on write protected storage (WORM, Write Once Read Many) or in an archive database without change rights. This meets the immutability the GoBD require.

04

Complete log

Ingest, access, export, migration and deletion are logged with a time stamp and user.

05

Renewal of signatures

Electronic signatures lose security over time as algorithms weaken. The German technical guideline BSI TR 03125 (TR ESOR) describes how signatures are renewed in time using time stamps and evidence records according to RFC 4998.

Common mistake: converted, original deleted

When legacy systems are replaced, database content is often converted into PDF reports and the raw data is then deleted. That looks tidy but destroys the machine evaluability that Section 147(2) AO requires for tax relevant data. When converting into a company specific format, the GoBD generally require both the original and the converted version to be kept. For quality data there is also a practical reason: you cannot analyze 50,000 serial numbers in a complaint case in a PDF.

In addition, the GoBD require procedural documentation describing how data is created, processed, archived and deleted. For digital long term archiving it has two functions: it is a mandatory document for the tax authority, and it explains the archive even after the people involved have left the company. The requirements are explained in detail in the article GoBD compliant archiving.

 

07 · Comparison

Backup, legacy system or archive: what really lasts 15 years?

In many manufacturing companies, three approaches that are all called archiving run side by side: backups on tape or in the cloud, legacy systems kept running in read only mode and real archiving systems. Only the third meets the requirements of digital long term archiving. The article Backup vs. Archiving explains the difference between backup and archive in detail.

Before and after: legacy system in read only mode versus digital long term archiving
Criterion Before: legacy system in read only mode After: digital long term archiving
License costs Database and application licenses keep running Eliminated once the legacy system is shut down
IT security No more security updates, growing attack surface Current, maintained archive platform
Expertise Depends on a few people who know the system Data model and context are documented and archived
Access Via IT ticket, often with waiting time Search by authorized business units
Readability in 15 years Uncertain, depends on hardware and operating system Planned through open formats and preservation planning
Deletion after the period ends Usually not provided Rule based and logged
Proof in an audit Hard to prove that data is unchanged Checksums and logs prove integrity

Keeping a legacy system running looks cheap at first because no migration project is needed. Over 10 to 15 years, the math no longer works. The hardware ages, the operating system drops out of support, and at some point the system no longer starts.

Key message

“Whether an archive is any good shows when, after 15 years, someone asks a question nobody anticipated at ingest.”

Guiding principle from CSP archiving projects

 

08 · Approach

How do you achieve digital long term archiving in 7 steps?

The following seven steps translate the six OAIS functional entities to a manufacturing company. They work for replacing a single legacy system as well as for a company wide archiving concept.

01

Inventory and classify data sources

Record all systems in which data subject to retention is created: MES, inspection systems, screwdriving controllers, ERP, CAD and document storage. Assign each data type to a class, for example tax record, quality record, technical documentation or personal data.

02

Create a retention plan with periods and deletion rules

For each class, define the longest applicable period and the triggering event, such as the end of the fiscal year or the last delivery of a product. Also define when and how data is deleted. The article GDPR deletion concept for manufacturing companies provides the basics.

03

Define a format catalog

Determine the target format for each data type using the format ladder above. Document which formats are accepted, which are converted and which are also kept in the original.

04

Define metadata and context

Describe which metadata each archive object carries: serial number, batch, order, plant, period, source system. Archive the data dictionary, units, status codes and procedural documentation as well.

05

Ingest with proof of integrity

Count the records per table before export, create checksums and reconcile both after ingest. Log deviations and how they were resolved. Only after an error free reconciliation may the source system be shut down.

06

Govern access and roles

Define who may search, export and delete. Quality management, the tax department, data protection and auditors need different views. The article Archive access without an IT ticket shows how business units can access data without going through IT.

07

Organize preservation permanently

Appoint a person responsible for preservation planning. At least once a year, check the integrity of the stock, the support for archive formats and the recoverability of a sample. Run deletion jobs after the periods end and log every run.

Use the following grid to assess where your company stands today.

Maturity grid for digital long term archiving in four levels
Level Characteristic Risk in an audit Next step
0: Legacy system Data remains in the replaced system High, access depends on old technology Inventory and retention plan
1: Backup Data exists as a backup or file storage High, readability and integrity unproven Introduce archive formats and checksums
2: Audit proof archive Immutable storage with log Medium, long term readability not planned Preservation planning and format monitoring
3: Long term archive Open formats, integrity checks, deletion rules, preservation planning Low, evidence on demand Regular reviews and sample tests

 

09 · Solution

How does CHRONOS implement digital long term archiving?

CHRONOS is the archiving solution in the CSP Manufacturing OS. It transfers structured data from databases and applications into an audit proof long term archive and makes it searchable for business units. This mainly concerns database content from inspection, production and administration systems whose meaning depends on the data model of the original application. This is exactly the data that is hardest to keep readable over long periods.

Audit proof

Long term archiving of database and application data in line with the GoBD, MDR and IATF 16949.

Access without a ticket

Business units search themselves through a fine grained permission concept.

Analysis in the archive

Reports directly from the archive without burdening the production system.

Rule based deletion

Data is deleted after the retention period ends and every run is logged.

Retire legacy systems

The basis for shutting down legacy systems in an orderly way.

The KLS Martin Group success story shows what this looks like in practice. You can find more about the solution on the CHRONOS data archiving page.

For simply storing office documents, a document management system with PDF/A support is often sufficient. CHRONOS is designed for cases where structured data from databases must remain evaluable for many years and the source system is to be replaced. The article Audit compliant archiving: choosing the right software describes selection criteria.

 

FAQ

Frequently asked questions

What is digital long term archiving?+

Digital long term archiving covers all organizational and technical measures that keep digital data readable, findable, unchanged and interpretable for ten years and longer. It includes open archive formats, metadata, integrity checks, media and format migration as well as controlled access. The reference model for it is OAIS according to ISO 14721.

How long is long term in digital long term archiving?+

In the specialist literature, retention of about ten years or more counts as long term archiving. For manufacturing companies in Germany and the EU, the specific periods result from law and standards: 8 years for accounting vouchers under Section 147(3) of the German Fiscal Code (AO), 10 years for annual financial statements, at least 10 years after the last device was placed on the market for medical devices and 15 years for implantable devices under Article 10(8) MDR.

Which file format is best for long term archiving?+

There is no single best format, but a suitable format for each data type. PDF/A according to ISO 19005 is the standard for documents, TIFF or PNG for raster images, CSV with documented character encoding for tabular data, XML with a schema for structured data, SIARD for relational databases and STEP according to ISO 10303 for 3D design data.

Is a backup a form of long term archiving?+

No. A backup is a copy for recovery after data loss and is overwritten regularly. It remains tied to the original system and format. Long term archiving separates the data from the source system, converts it into durable formats, checks its integrity and governs search, access and deletion throughout the entire retention period.

What is the difference between audit proof archiving and long term archiving?+

Audit proof archiving ensures that data is kept complete, unchanged and tamper proof, as required by the GoBD and the German Commercial Code. Long term archiving adds the question of whether this data can still be opened and understood in 15 years. In practice, a manufacturing company needs both: immutability and lasting readability.

How do you archive a database for the long term?+

A database is archived for the long term by transferring tables, keys, relationships and metadata into a vendor neutral format such as SIARD or into a documented archive database. Before the transfer, records are counted and checksums are created; afterwards, completeness is reconciled. The source system can then be shut down without losing access to the data.

May archived data be converted into another format?+

Yes, format migration is even necessary for long term archiving. However, tax relevant data must remain machine evaluable, and when converting into a company specific format, the GoBD generally require both the original and the converted version to be kept. Every migration should be documented with checksums, record reconciliation and a log.

What happens to archived data after the retention period ends?+

After the retention period ends, personal data must be deleted under Article 5(1)(e) and Article 17 GDPR unless another legal basis permits further storage. Tax relevant records are additionally subject to the suspension of expiry under Section 147(3) AO. A good archiving system deletes data based on rules and logs every deletion.

Conclusion

Storage space alone solves little in digital long term archiving. What matters is that formats, metadata, proof of integrity and responsibilities are defined today. Then the questions of an auditor, customer or court can still be answered with reliable data in 15 years.

Next step

Data that still delivers answers in 15 years

Define today the rules by which your production and quality data is archived, checked and deleted. The white paper provides the framework, the demo shows the implementation with CHRONOS.

Download the white paper for free Book a CHRONOS demo

Korbinian Hermann
CEO, CSP Intelligence GmbH
Responsible for strategy and innovative software solutions for the manufacturing industry.

RELATED ARTICLES