Engineering Data as Customer Property: Protecting CAD and Drawings

How are customer CAD models and drawings managed under IATF 16949? Steps for receipt, registration, access, transfer to sub-suppliers, return and disposal, with a responsibility table.
Technical summary
Technology
ISO 9001:2015 8.5.3, IATF 16949:2016 7.5.3.2.2, OFTP2, NIST SP 800-88, TISAX
Topic
Process-based management of customer-owned engineering data throughout its lifecycle
Level
Intermediate
Prerequisites
  • Access to customer contracts and confidentiality agreements
  • Knowledge of the CAD/PDM environment and file sharing channels
In this article7 sections

At an automotive supplier, “customer property” first brings to mind customer-owned tooling, fixtures and packaging. But the 3D CAD models, technical drawings, specifications and software the customer sends are part of the same concept. And there’s a difference from tooling: a STEP file is copied in seconds, goes out by email and is never found again. Below you’ll find the steps from receiving engineering data to disposing of it, the rules for passing it to sub-suppliers and a table showing who is responsible for what.

Intellectual property within customer property

As IATF 16949 builds on the structure of ISO 9001, the customer property requirement comes from clause 8.5.3 (Property belonging to customers or external providers) of ISO 9001:2015. The clause requires the organization to exercise care with customer property while it’s under the organization’s control or being used by it; to identify, verify, protect and safeguard it. If the property is lost, damaged or found to be unsuitable for use, the organization reports this to the customer and retains documented information on what occurred. The clause’s note explicitly states that customer property can include intellectual property and personal data.

IATF 16949 clause 7.5.3.2.2 (Engineering specifications) requires customer engineering standards, specifications and their revisions to be reviewed, distributed and implemented according to the customer’s schedule; the review must not exceed 10 working days from receipt of notification. Read together from the perspective of IATF 16949 IT requirements, the picture becomes clear: customer data is both an asset to be protected and a controlled document to be kept up to date. Both at once.

Data types in scope in practice:

  • 3D models (native CAD formats, STEP, JT) and 2D drawings
  • Customer engineering standards, material and test specifications
  • Prototype and pre-series data, design change notifications
  • Customer-owned software, calibration data sets, test programs
  • Supplier manuals and confidential documents downloaded from customer portals

The lifecycle of engineering data

Control isn’t achieved with individual tools but with a defined step and record at every stage of the lifecycle:

  1. Receipt: Data is accepted only through defined channels: the customer portal, corporate file transfer protocols such as OFTP2 or a secure sharing space approved by the customer. Data that arrives by personal email or USB stick isn’t used until it’s registered.
  2. Registration: Each data package gets a registration number. The record includes the customer, project, part number, revision, confidentiality class, contract or confidentiality agreement reference and storage location.
  3. Classification: The confidentiality level given by the customer (e.g. prototype data, confidential, restricted) is mapped to the organization’s own classification scheme. In organizations within TISAX scope, this mapping must be consistent with the label selection.
  4. Storage: Data is kept in the PDM/PLM system or in a repository whose access list is managed per project. Local disks and personal cloud folders don’t count as storage locations.
  5. Use and distribution: Only people assigned to the project access the data; drawings issued to production or quality are distributed as controlled copies.
  6. Revision: When a new revision arrives, it’s recorded that the old revision has been withdrawn from use and the copies at production points replaced.
  7. Project end: Return, disposal or controlled archiving according to the contract; each closed with a record.

The registration number ensures the data corresponds to a single row in the inventory. This inventory doesn’t have to be a separate system; it can be a subset of the organization’s information asset inventory. How to design the fields is explained in detail in the guide preparing an information asset inventory. A gap you may come across is at the very first step: the data arrives in the sales team’s mailbox, is copied from there into the project folder and never gets a registration number.

Access and distribution rules

In most organizations, access to engineering data spreads across design, process engineering, quality, the tool shop and purchasing. Loss of control usually happens at three points: access left open after the project ends, drawings issued to the shop floor on paper or as PDFs and never collected back, and sharing with external parties by email. All three are easy to find in an audit.

Workable rules:

  • Project-based permission groups: Access is given to a group tied to the project, not to individuals; when the project closes, the group is closed. Access reviews are tied to project milestones.
  • Controlled copies: Drawings going to the shop floor carry the revision and a “controlled copy” marking; with a new revision, the collection of the old copy is recorded. At stations where drawings are viewed on screen, only the current revision should be able to open.
  • Derived data: Files derived from customer data, such as tool designs, CNC programs or fixture models, also contain customer data and inherit the same classification.
  • Export record: Every time data leaves the organization (sub-supplier, test laboratory, consultant), who sent what to whom through which channel is recorded.

The practical way to check permission groups is simple: list groups from the directory service whose project closing date has passed and look at the number of members. Every closed project group that isn’t empty is a finding.

Passing data to sub-suppliers

Sending customer data to a sub-supplier for tooling, heat treatment, coating or fixture production is a common need and the riskiest step in the process. Many OEM contracts make sharing data with third parties subject to prior approval or at least an equivalent confidentiality obligation. Before the transfer, these questions must be answered:

  • Does the contract allow this sharing, and is customer approval needed?
  • Is there a confidentiality agreement with the sub-supplier that’s no weaker than the agreement with the customer?
  • Is the data being sent the minimum needed to do the job? Instead of the whole assembly model, only the relevant part, simplified geometry instead of the full model, or just a 2D drawing may be enough.
  • Is the transfer channel secure, and does it produce a record?
  • How will confirmation of return or disposal be obtained from the sub-supplier at the end of the project?

The method for assessing a sub-supplier’s information security level is explained in the guide supplier information security risk assessment. If prototype data is involved, the customer may require the sub-supplier to hold a TISAX label too; which label corresponds to which data is explained in the article choosing TISAX labels.

Return and disposal at project end

Project closure is the most neglected stage. As long as series production continues, part of the data stays in use; but for projects received at the quotation stage that never turned into work, cancelled variants and completed prototype work, the data is returned or destroyed according to the contract. Quotation data is the most often forgotten. There are two technical challenges here.

Finding the copies: Data doesn’t stay only in PDM; it’s also on engineers’ computers, in email attachments, in CAM and simulation folders and in shared areas. The registration number and export record make it possible to trace the copies; searching file servers by part number is a complementary control.

Data in backups: Deleting individual files from backups is usually not possible. The right approach is to write in the disposal record that the backups will be deleted automatically when their own retention period expires, that the data will be destroyed again if a restore happens within that period, and to agree this with the customer. For media sanitization on decommissioned disks and devices, NIST SP 800-88 methods are the common reference.

The disposal or return record includes: the registration number, the data destroyed and its locations, the method, the date, who did it and who approved it, confirmations received from sub-suppliers and the notification sent to the customer.

Responsibility table and records

Step Owner Support Record
Receipt and registration Project engineer Document control Data register row
Classification Project manager Information security Class and justification
Repository and permissions IT Project manager Permission group list
Applying revisions Document control Quality Review date
Transfer to sub-supplier Purchasing Project, information security Approval and transfer record
Loss/leak notification Information security Sales, quality Incident and customer notification
Return and disposal Project manager IT Disposal record

In the event of loss or unauthorized access, 8.5.3’s requirement to report to the customer applies directly. Who reports, through which channel and within what time must be defined in the information security incident procedure; if the customer contract defines a notification period, that period applies.

The auditor usually follows this process through an example: they pick a part number and ask how the data arrived, who can access it, whether the drawing on the shop floor is the current revision and, if applicable, for the record of sending it to a sub-supplier. If you can show this trail from start to finish, the process works. If you can’t, it doesn’t. Protecting physical prototypes is outside the scope of this article; it’s covered in the guide TISAX prototype protection requirements. For technical controls on CAD workstations and the network side, see the article technical controls for prototype data.

If you need to prove this process in OEM audits and customer questionnaires, we build the process and record structure together as part of automotive supplier information security work. The official source for the ISO 9001 text is the ISO 9001:2015 page.

Frequently asked questions

Does customer CAD data really count as “customer property”?

Yes. The note to ISO 9001:2015 clause 8.5.3 states that customer property can include intellectual property and personal data. CAD models, drawings, specifications and software supplied by the customer fall within this scope; they must be identified, protected and reported to the customer if lost.

Is approval required to send customer data to a sub-supplier?

This depends more on the contract than on the standard. Many OEM contracts or confidentiality agreements make sharing with third parties subject to prior approval or an equivalent confidentiality obligation. If the contract doesn’t explicitly allow it, get approval, keep the shared data to a minimum and record the transfer.

Do we have to destroy customer data in backups?

Deleting individual files from backups is often technically impossible. The defensible approach is: write in the disposal record that the backups will be deleted when their own retention period expires, commit to destroying the data again if a restore happens within that period, and agree this approach with the customer.

How quickly should we review a customer specification revision?

IATF 16949 clause 7.5.3.2.2 requires changes to customer engineering standards and specifications to be reviewed within no more than 10 working days of receiving notification. The review date and result are recorded; implementation is planned according to the customer’s timeline.

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