Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/TR 28821 — Road Vehicles — Product Data Management
Technical Report on PDM Practices and Lifecycle Data Management for the Automotive Industry
Introduction to ISO/TR 28821
ISO/TR 28821 is a Technical Report that addresses product data management (PDM) practices specifically tailored for the road vehicle industry. It provides guidelines and best practices for managing the complete lifecycle of vehicle product data, from initial design concepts through manufacturing, service, and end-of-life disposal. As a Technical Report, it offers advisory guidance rather than mandatory requirements, enabling automotive manufacturers and suppliers to adopt data management strategies that align with their specific organizational contexts.
This Technical Report recognizes that modern vehicles are increasingly complex systems-of-systems, integrating mechanical, electrical, electronic, and software components. Effective PDM is essential for maintaining consistency across engineering changes, supply chain communications, regulatory compliance documentation, and aftermarket service information. The report draws on established PDM principles defined in ISO 10303 (STEP) standards while adapting them to the specific workflows and data exchange requirements of the automotive sector.
Automotive suppliers should use ISO/TR 28821 as a checklist when evaluating their PDM systems. The gap analysis between current capabilities and TR recommendations often reveals opportunities for reducing engineering change order cycle times by 20-30%.
Core Data Management Domains
ISO/TR 28821 organizes product data management into several interconnected domains. The following table summarizes the key data categories and their lifecycle considerations.
| Data Domain | Content Description | Lifecycle Phase | Key Stakeholders | Typical Standards Interface |
|---|---|---|---|---|
| Geometric design data | 3D CAD models, 2D drawings, surface definitions | Concept → Detailed design | Design engineering, styling | ISO 10303-203, ISO 10303-214 |
| Bill of Materials (BOM) | Part lists, variants, configuration rules | Design → Manufacturing | PDM/PLM, purchasing | ISO 10303-21 (STEP physical file) |
| Electrical/electronic data | Wiring harnesses, ECU specifications, signal lists | Design → Testing | E/E engineering, EMC testing | ISO 10303-210, IEC 81346 |
| Software artifact data | Source code, binaries, calibration files, version history | Development → Maintenance | Embedded software, calibration | ISO 26262, AUTOSAR meta-model |
| Validation & verification data | Test plans, simulation results, physical test reports | Validation → Production | Validation engineering, quality | ISO 9001, IATF 16949 |
| Service & aftermarket data | Service manuals, diagnostic procedures, spare parts catalogs | Production → End-of-life | After-sales, technical publications | ISO 26262 (safety concept updates) |
Implementing ISO/TR 28821-aligned PDM practices enables seamless digital thread integration across the automotive supply chain. Companies that adopt structured PDM early report 40% fewer ECO-related production disruptions.
Engineering Change Management and Traceability
A major focus of ISO/TR 28821 is the management of engineering changes throughout the vehicle development lifecycle. The Technical Report recommends a structured change management process that includes change request documentation, impact analysis across affected systems, approval workflows, and implementation tracking. For safety-critical systems, the report emphasizes the need for full bidirectional traceability between requirements, design artifacts, verification results, and change records — a concept that aligns closely with ISO 26262 functional safety requirements.
The advisory nature of ISO/TR 28821 means that organizations can tailor these recommendations to their existing workflows. A tier-1 supplier may implement a lightweight change process for non-safety interior trim components while applying rigorous traceability for brake system electronic control units. This flexibility is one of the key advantages of Technical Reports over full normative standards.
One of the most common PDM failures in automotive programs is the loss of traceability between software calibration versions and hardware release levels. ISO/TR 28821 provides guidance on maintaining these cross-domain links, which is critical for field return analysis and recall management.
Interoperability with Supply Chain Partners
Modern vehicle development involves extensive collaboration between OEMs, tier-1 suppliers, and specialized engineering firms. ISO/TR 28821 addresses data exchange interoperability by recommending standardized exchange formats (particularly STEP AP242 for 3D data) and consistent metadata schemas. The Technical Report also discusses the use of product lifecycle management (PLM) collaboration platforms that provide secure, role-based access to shared product data while maintaining intellectual property protection.
Without structured PDM aligned with ISO/TR 28821 principles, automotive recalls become significantly more expensive. The inability to rapidly identify which vehicles contain which component versions (from which production batch) can delay recall execution by weeks and increase costs by millions.
Frequently Asked Questions
Q: How does ISO/TR 28821 relate to ISO 26262 functional safety data management requirements?
A: ISO/TR 28821 provides the general PDM framework applicable to all vehicle data. For functional safety specifically, ISO 26262-8 (Chapter 12 on configuration management) and ISO 26262-6 (software verification) impose additional rigor requirements that should be layered on top of the baseline PDM practices described in this TR.
Q: Is ISO/TR 28821 applicable to electric vehicle (EV) powertrain development?
A: Yes. The data management principles apply regardless of powertrain type. For EVs, additional attention is needed for battery system data (cell genealogy, thermal management calibration) and electric drive unit software configuration management, which are well supported by the TR’s domain-oriented framework.
Q: Can small automotive suppliers implement ISO/TR 28821 without expensive PLM software?
A: Yes. The Technical Report provides principles and practices that can be implemented using a range of tools from simple spreadsheet-and-folder structures (for very small suppliers) up to enterprise PLM suites. The key is establishing clear naming conventions, version control discipline, and documented change workflows.
📥 Standard Documents Download
No download files available yet