Look beyond the drawing title block
The review needs to cover visible information and content held within the files:
- Drawing content: designer and checker names, signatures, customer logos, addresses and project references in title blocks or annotations.
- File properties: authors, company names, custom properties, comments and references to internal storage locations.
- Project structure: filenames, layer names, part and order references, external links and relationships between models, drawings and BOMs.
- Supporting material: PDFs, embedded previews, scanned drawings and associated inspection records. Image-based text may require recognition methods; searching file text alone will not necessarily find it.
A design itself can also identify a product, customer or location. A distinctive shape, bespoke assembly or site layout may remain recognisable after names have been removed. Some projects or files may need to be excluded from the proposed scope.
Preserve relationships across the prepared collection
A drawing should still point to the right model. A revision must remain attributable to its assembly, and a BOM to the correct design state. Treating every file in isolation can break the connections that make the collection understandable.
Where replacement identifiers are appropriate, use them consistently within the agreed collection. The same project reference should receive the same replacement across the model, drawing and supporting records. Renamed files also require attention to affected references. Otherwise, preparation can leave a technically unusable file set.
What is removed, replaced or retained depends on the sensitivity and intended purpose. Geometry and technical features are shared only within the approved scope; preserving them is not an unconditional promise to disclose every design.
A fictional drawing title block
The following example illustrates one possible treatment. It contains no real project information.
| Detail | Original example | Prepared example |
|---|---|---|
Customer |
Example Company North |
Company U-024 |
Prepared by |
Example Person A |
Person P-016 |
Project |
North special fixture / 2021 |
Project K-038 |
Drawing reference |
NORTH-2021-471 |
Drawing Z-112 |
Technical detail |
Bore Ø 12 H7 |
Bore Ø 12 H7 |
The technical detail is retained in this example. Whether other features would need treatment can only be decided in the context of the actual project.
Agree the review before sharing material
Define the collection and authority. Identify the projects in scope and any customer documents, current product information or confidential material to exclude. Permission for the intended use is reviewed separately from technical preparation.
Identify information needing protection. Consider visible drawing details, metadata, references and supporting documents. Recognition methods and their combination depend on file types and the risks involved.
Agree the treatment and the relationships to retain. Establish what will be removed or replaced and how models, revisions and BOMs will continue to fit together. The prepared result must remain technically suitable for the agreed purpose.
Review the result and record approval. The prepared collection is checked before delivery to AI customers. The review method and evidence required are agreed for that archive, rather than assumed to follow one universal procedure.
Establish responsibilities before the first file access
Roles, recipients and permitted uses need to match the real arrangement. Discuss processing location, authorised access, transfer methods and the treatment of originals, working copies and any mapping tables. Retention, deletion and available review or deletion evidence also need to be settled in advance.
Where the arrangement constitutes processing on behalf of a controller under the GDPR, Article 28 requires a corresponding agreement. An NDA does not resolve that role question or replace all other rights and data-protection considerations.
Pseudonymisation is not automatically anonymity
Replacement identifiers may preserve relationships and reduce identification risks. They do not prove anonymity by themselves. Additional information, indirect features and the surrounding context may still permit a person to be identified.
Trade secrets and rights in drawings or models also remain relevant independently of personal data. Technical preparation is not permission to license the material.
For the first enquiry, simply describe your archive. The enquiry and initial conversation are non-binding. Please do not send CAD files or examples containing personal information.
References for the review questions
- GDPR: Articles 4, 6 and 28, and Recital 26
- European Commission: GDPR application and personal data
- For the German context, Copyright Act section 2 and section 31, plus Trade Secrets Act section 2 and section 4.
These references explain general review questions. They do not determine the outcome for a specific archive or establish one legal rule for every country.