Digital Archiving and Retention of PPAP and Quality Records

The “active + 1 year” retention rule for PPAP and quality records, archive folders and metadata, open file formats, hash checks and an annual retrieval test.
Technical summary
Technology
IATF 16949, PPAP, PDF/A, STEP, SHA-256, DMS
Topic
Long-term digital archive of automotive quality records
Level
Intermediate
Prerequisites
  • Record list and current customer CSRs
  • Part lifecycle information in the ERP
  • Admin access to the archive store
In this article8 sections

When a customer complaint comes in or a recall investigation starts, the first things requested are the control plan, measurement report and process parameters in force on that date. If the part was in series production for ten years and the spare parts period is still running, that file is ten years old. If you can’t find it, or can’t open it, the result is the same: the record is treated as nonexistent. Below we explain how the retention period for PPAP and production quality records is calculated, how the archive is set up and what needs to be done on the IT side so files stay readable years later.

Sources of the record retention requirement

The retention period doesn’t come from a single source. Three layers are read together, and the longest applies.

  • IATF 16949 clause 7.5.3.2.1: Requires the organization to define a record retention policy. For production part approval (PPAP) records, tooling records (including maintenance and ownership), product and process design records, purchase orders and contracts and their amendments, it sets the minimum period as the time the part is active for production and service requirements plus one calendar year. If the customer or legislation requires a longer period, that applies.
  • Customer-specific requirements (CSRs): Many OEMs define fixed numbers of years for certain record types, or extended periods for safety/regulation-critical characteristics. German OEMs’ CSRs may refer to VDA Volume 1 on documented information and record retention; in that case, the current edition of that volume also goes on the source list.
  • Legal obligations: Legislation on commercial books and documents, product liability and the rules of export markets can create separate periods. Determine these together with the legal and finance departments; IT shouldn’t decide alone.

The practical consequence of the “active + 1 year” rule is often overlooked. The period is counted not from the date the record was created but from the date the part’s service life ends. That date isn’t known when the record is created. That’s why the archive must support a retention rule tied to the “part no longer active” event, not a fixed disposal date. Writing a “delete after 7 years” rule on the file server is the wrong solution here.

Factors that determine the retention period

When preparing the record list, the following questions are answered for each record type. The answers determine which retention class the record falls into.

Factor Question Effect
Part lifecycle When do series production and the service period end? Starting point of the period
Characteristic type Does it include a special/safety characteristic? Extended period under the CSR
Record type Is it a PPAP, tooling, process or shipping record? Which rule applies
Customer Which OEM’s CSR applies? The longer period takes priority
Legislation Is there a legal retention obligation? Lower limit

The method that works in the field is to build a retention matrix by combination of record type and customer, and to add an “active/service/inactive” status and an “inactive since” date field to each part number. When the part goes inactive, the status change in the ERP starts the retention counter in the archive. If this link isn’t set up, the counter never starts, or starts from the wrong point. The list structure for general ISMS records is in the article record list and retention periods; here we focus on the differences specific to automotive quality records.

Archive folder and metadata structure

A folder structure speeds up searching, but it isn’t enough on its own. In a recall investigation, the question comes like this: “Which control plan was in force on the date the part shipped under this lot number was produced?” A folder name doesn’t answer that. Metadata does.

A sample folder hierarchy:

Archive/
  <Customer>/
    <PartNo>/
      PPAP/
        2024-03_Rev-C_Level3/
          PSW.pdf
          Control_Plan_RevC.pdf
          PFMEA_RevC.pdf
          Dimensional_Results.pdf
          MSA/
          Process_Capability/
          _manifest.sha256
      Production_Records/
        2024/
          2024-Q2/
      Tooling_Records/
      Engineering_Changes/

Each PPAP submission is kept in its own folder in a way that won’t change. A new revision isn’t written over the previous folder; a new folder is created. Having the date, revision and submission level in the folder name shortens manual searching. A mistake you may come across is a single folder called “current” being overwritten again and again. The previous revision silently disappears that way.

If a document management system (DMS) is used, these metadata fields should be required:

  • Customer, part number, customer part number and engineering change level
  • Record type (PSW, control plan, PFMEA, dimensional report, MSA, capability study)
  • Validity start and end (the approval date of the next revision)
  • Retention class and retention rule
  • Record owner (as a role, not a person)
  • Source system (PLM, ERP, CAQ, file server)

With validity dates, a “revision in force on this date” query takes a single step. Without this field, in an audit or a customer request you open and check the approval dates of revisions one by one. The reason for writing the record owner as a role rather than a name is simple: people leave, roles remain.

Long-term readability: file formats

It isn’t enough for the file to sit on disk fifteen years later; it has to open. Proprietary database backups from old CAQ software, native formats of CAD programs whose licenses have expired and Excel files with macros are the riskiest content in a long-term archive. They all lead to the same problem: the software to open the file no longer exists.

Content Risky format Preferred for archiving
Approved documents DOCX, macro-enabled XLSM PDF/A (ISO 19005)
Raw measurement data Manufacturer-proprietary format CSV or XML + format description
3D model Native CAD format STEP (ISO 10303) + native file
Image record Compressed proprietary format TIFF or PNG
Database records Application backup Export (CSV/XML) + schema definition

Two rules work here. First, keep two formats wherever possible: the native format for editing and an open format for long-term access. Second, for data that depends on its own application (CAQ, MES), don’t rely only on a database backup. When the application version changes or vendor support ends, setting up an environment to restore an old backup becomes difficult; sometimes even the operating system can no longer be installed. Periodically exporting critical records to an open format breaks this dependency.

For an impartial assessment of the long-term sustainability of formats, the US Library of Congress’s digital format sustainability resource is a good starting point.

Archive integrity, backup and retrieval testing

An archive isn’t a backup. If the only copy in the archive is lost, the record is lost too. The archive store must be included in the backup policy, with at least one copy kept at a different location on immutable or offline media. Ransomware first encrypts the shares it can reach; the archive share is one of them. If you’re choosing between tape and object storage for long-term retention, the LTO tape vs object storage comparison gives the technical details.

For integrity, putting a manifest file in each archived folder is a simple and effective method. On Linux:

# Create the manifest at archiving time
cd /archive/CustomerA/12345-678/PPAP/2024-03_Rev-C_Level3
find . -type f ! -name '_manifest.sha256' -print0 | sort -z | xargs -0 sha256sum > _manifest.sha256

# Periodic integrity check (show errors only)
sha256sum -c --quiet _manifest.sha256

On Windows, the same check is done with Get-FileHash -Algorithm SHA256. If the manifest check runs regularly, silent data corruption and unauthorized changes are caught before the backup cycle fills up and the last good copy is deleted. If the check never runs, the first person to notice the corruption is the auditor trying to open the file.

A retrieval test is a test of the archive, not of backup. At least once a year, run this scenario for a few randomly selected part numbers: “Bring the control plan and PSW in force for this part on a specific date, and the production records for that month.” Measure the time, note any file that can’t be opened or found, and record the result. This one test checks restore from backup, metadata accuracy and format readability at the same time. For documenting restore tests as evidence, see the article backup and restore audit evidence.

Access, immutability and disposal

An archived quality record isn’t changed. On the file server, give read-only permission to the archive folders, limit write permission to the role that performs archiving and log that role’s use. The first place to look in the console is the folder’s ACL: if you see a “Domain Users – Modify” line, the archive isn’t immutable. If a DMS is used, the records declaration feature locks the document and binds the retention rule.

Disposal is the natural consequence of retention, but it isn’t uncontrolled. Records whose retention period has expired should drop onto a disposal list instead of being deleted automatically. After the quality owner confirms there’s no open complaint, warranty claim or legal process, they approve the disposal, and a disposal record is kept. In the case of a legal hold, disposal is suspended.

Archive audit checklist

  • The record retention policy includes the record types in 7.5.3.2.1 and the “active + 1 year” rule.
  • The retention requirements in each active customer’s CSR are entered in the matrix, with the CSR revision stated.
  • Part status information (active/service/inactive) is passed from the ERP to the archive’s retention rule.
  • PPAP submissions are stored separately by revision, in a way that can’t be altered.
  • Thanks to validity dates, the “revision in force on a given date” can be queried.
  • There’s an inventory of archive formats, with open-format equivalents defined.
  • The archive store is backed up; at least one copy is at a separate location and immutable.
  • Manifest/hash checks run regularly and their results are kept.
  • An annual retrieval test has been done; time taken and problems are recorded.
  • The disposal list, approval and disposal record process are defined; there’s a legal hold exception.

How these checks combine with other IT evidence in the IATF audit is covered in the guide IT evidence in the IATF 16949 audit. If you’d like to build the archive structure and retention matrix together, our IATF 16949 IT requirements and audit preparation and backup and restore audit services bring the quality and IT sides to the same table.

Frequently asked questions

How long should PPAP records be kept?

Under IATF 16949 clause 7.5.3.2.1, PPAP records are kept for as long as the part is active for production and service requirements, plus one calendar year. If customer-specific requirements or legislation define a longer period, the longer one applies.

Do scanned paper records replace the originals?

It depends on the customer’s specific requirements and the relevant legislation. You must be able to show that scans are legible, complete and stored unalterably, and that the scanning process is defined. For documents requiring a wet signature, get your legal department’s opinion.

Can the backup system be used instead of an archive?

It shouldn’t be. Backup retention cycles are usually on the scale of months or a few years, and old copies are deleted at the end of the cycle. The archive must have its own retention rules, metadata and search capability; the archive itself must also be backed up separately.

How often should a retrieval test be done?

Doing it at least once a year is common practice. An additional test should be done when the archive system, storage media or related application changes, and the result should be recorded.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Compliance

We work with you on compliance with ISO 27001, IATF 16949, TISAX and similar standards, covering risk assessment, control design, documentation and audit preparation.

Knowledge Center

Other articles