Development Interface Agreement (DIA)
ISO 26262-8: Supplier-Integrator Safety Contracts
- Chapters
- 14
- Chapters
- Interactive Diagrams
- 6
- Interactive Diagrams
- Matrix
- RASIC
- Matrix
- Clause 5.4
- ISO 8
- Clause 5.4
Quick answers
- What is a development interface agreement in ISO 26262?
- A development interface agreement (DIA) is the bilateral safety contract required by ISO 26262-8 Clause 5 whenever development is distributed between a customer (integrator) and a supplier. It defines who performs each safety activity, who provides which work products and evidence, how the parties exchange safety-relevant information, and how the joint safety plan hangs together across company boundaries. The DIA is agreed before development work starts, is signed by both parties, and is maintained as a living document through change. Without it, responsibility gaps between customer and supplier are discovered at the assessment - or in the field.
- When is a DIA mandatory?
- Whenever any part of the safety lifecycle for an item or element is distributed - the customer develops the item and a supplier develops an element, or activities like safety analyses, verification, or production are delegated. That covers essentially every OEM-Tier 1 and Tier 1-Tier 2 relationship on an ASIL-rated system, including software-only and SEooC suppliers. The required depth scales with ASIL: higher integrity levels demand more explicit content on confirmation measures, assessments, and evidence. A general quality agreement or statement of work does not substitute, because neither allocates ISO 26262 activities and work products specifically.
Why it pays for itself
Know what a DIA must contain
Learn the mandatory content per ISO 26262-8 Clause 5.4 - responsibilities, activities, work products, and evidence by ASIL - so nothing an assessor expects is missing when the audit reaches the supplier interface.
Master the RASIC matrix
Allocate every safety activity between customer and supplier as responsible, approving, supporting, informed, or consulted, turning vague "the supplier handles safety" assumptions into an enforceable, auditable split.
Run the DIA as a living document
Follow the lifecycle from an initial DIA at RFQ through negotiation, signature, change-driven updates, and closure at product release - the process that keeps the agreement matching reality as the project evolves.
What you’ll be able to do
Draft Compliant DIA Documents
Create DIAs with all mandatory content per ISO 26262-8 Clause 5.4, including work product lists, delivery schedules, and ASIL-graded requirements.
Build RASIC Responsibility Matrices
Assign clear responsibilities for every safety activity and work product across the customer-supplier interface using the RASIC framework.
Manage DIA Through the Lifecycle
Update and maintain the DIA as a living document through RFQ, development, production, and post-SOP phases, tracking changes and obligations.
Coordinate Joint Confirmation Measures
Organize FSA access, evidence sharing, and joint review participation between customer and supplier organizations in compliance with independence requirements.
Handle Multi-Tier DIA Chains
Design nested DIA structures for three-tier supply chains, ensuring requirements and evidence flow consistently from Tier2 through Tier1 to OEM.
Assess Change Impact on DIA Obligations
Evaluate supplier change requests for DIA revision triggers, ASIL impact, and re-confirmation measure requirements before change approval.
Chapter by chapter
- 01
What Is a DIA?
Define the Development Interface Agreement as a bilateral safety contract between customer (integrator) and supplier. Understand its legal and technical purpose, when it is mandatory, and how it differs from a general quality agreement or SOW.
- DIA definition
- Customer vs. supplier
- DIA vs. QA agreement
- 02
ISO 26262-8 Requirements
Navigate ISO 26262-8 Clause 5.4 requirements: mandatory DIA for developed items and elements, required content by ASIL, revision and change management obligations, and the connection to the safety plan.
- Clause 5.4 requirements
- ASIL-dependent content
- Change management
- 03
DIA Lifecycle Process
Follow the DIA from quotation phase through development execution to production: initial DIA draft at RFQ, negotiation, mutual signature, living document updates on change, and final DIA closure at product release.
- RFQ phase DIA
- Negotiation process
- Lifecycle updates
- 04
Mandatory DIA Content
Enumerate all mandatory sections: item/element definition, ASILs, safety goals, safety requirements allocation, distributed development responsibilities, and required work products with their expected format and delivery dates.
- Mandatory sections
- Work product list
- Delivery schedule
- 05
RASIC Matrix
Construct the Responsible, Accountable, Supporting, Informed, Consulted (RASIC) responsibility matrix for all safety activities, analyses, and work products across the customer-supplier interface.
- RASIC structure
- Activity mapping
- Accountability assignment
- 06
Organizational Interfaces
Define the organizational interface: safety manager contacts, escalation paths, review participation agreements, joint confirmation measure arrangements, and decision authority for safety-critical changes.
- Contact matrix
- Escalation paths
- Joint reviews
- 07
Technical Requirements Flow
Manage bidirectional requirements flow: how safety goals decompose to safety requirements, how supplier-specified TSRs flow back to the customer, and how interface specifications are controlled across development levels.
- Requirements decomposition
- TSR flow-back
- Interface control
- 08
Execution Phase
Run the DIA during active development: progress reporting against the DIA work product schedule, handling late deliveries, joint technical reviews, and managing change requests that affect safety requirements or ASILs.
- Progress reporting
- Late delivery handling
- Change request impact
- 09
Safety Assessment Coordination
Coordinate confirmation measures between customer and supplier: joint FSA access, sharing of evidence packages, customer-side review of supplier safety cases, and managing external assessor access to both organizations.
- Joint FSA coordination
- Evidence sharing
- Assessor access
- 10
Production & Operation
Extend DIA obligations into production: change notification requirements, field anomaly reporting, production safety monitoring, and responsibilities for updates to safety documentation during the operational phase.
- Change notification
- Field anomaly reporting
- Post-SOP obligations
- 11
Work Products
Define the complete DIA work product set: the DIA document itself, RASIC matrix, requirements traceability matrix, joint confirmation reports, evidence exchange protocols, and final sign-off documentation.
- DIA document
- RTM linkage
- Sign-off package
- 12
Case Studies
Two detailed case studies: (1) OEM-Tier1 DIA for an ASIL D steering controller with complex distributed development; (2) Tier1-Tier2 DIA for a semiconductor safety element out of context (SEooC) at ASIL B.
- OEM-Tier1 DIA
- Tier1-Tier2 DIA
- SEooC DIA
- 13
DIA Checklist
Apply the comprehensive DIA compliance checklist covering all ISO 26262-8 Clause 5.4 requirements, common omissions found in audits, and ASIL-specific additions for ASIL C and D systems.
- Compliance checklist
- Common omissions
- ASIL C/D additions
- 14
FAQ
Answers to the most common DIA questions: when is a DIA needed between internal departments? Can one DIA cover multiple items? What happens when DIA obligations are not met? How to handle multi-tier supply chains?
- Internal DIA
- Multi-item DIA
- Multi-tier supply chain
Not just text: the visual toolkit
DIA Lifecycle Timeline
Interactive timeline showing DIA creation, negotiation, signature, updates, and closure milestones mapped to ISO 26262 lifecycle phases from concept to production.
RASIC Responsibility Matrix
Editable RASIC template with rows for all safety activities and columns for customer, Tier1, and Tier2 roles - exportable as CSV for inclusion in DIA documents.
Requirements Flow Diagram
Visual representation of safety requirements flowing from vehicle level through item to element, with supplier TSR flow-back and interface specification control points highlighted.
DIA Content Completeness Checker
Interactive checklist mapped to ISO 26262-8 Clause 5.4 with ASIL-conditional requirements highlighted - check off items to see a completeness percentage for your DIA draft.
Multi-Tier Supply Chain Map
Visual diagram of nested DIA relationships in a three-tier supply chain: OEM-Tier1 DIA, Tier1-Tier2 DIA, and the flow of safety requirements and evidence across all levels.
Change Impact Assessment Flow
Decision flowchart for evaluating a supplier change request against DIA obligations: ASIL impact check, requirement change assessment, DIA revision trigger decision, and re-confirmation measure initiation.
ASIL D Steering Controller OEM-Tier1 DIA
Complete DIA negotiation and execution for an ASIL D EPS controller between a German OEM and a Tier1 supplier: RFQ-phase DIA draft, RASIC negotiation, work product schedule agreement, mid-project change management, and FSA coordination.
- RFQ DIA draft: ASIL D safety goals, 47 work products listed with delivery dates
- RASIC negotiation: 3 contested items resolved - Tier1 accepts FMEDA responsibility
- Change CR-047: steering angle sensor change - DIA revision triggered, re-review required
- Joint FSA: external assessor attended both OEM and supplier sites over 3 days
- Finding F-12: missing DIA update for SW V2.3 - corrected and re-signed in 2 weeks
- DIA closed at SOP: all 47 work products delivered and accepted
Unlock in course
Who this guide is for
- Safety managers at OEMs or Tier 1s setting up a distributed development with suppliers
- Supplier engineers who must negotiate and live with a customer's DIA
- Project and purchasing leads handling safety obligations at the RFQ stage
- Auditors and assessors reviewing supplier interfaces for ASIL projects
Frequently Asked Questions
Common questions about Development Interface Agreement (DIA)
Start the course today
A free account unlocks one full concept guide, 3 work product templates, 1 guided process, the Markov simulator, and 5 practice exams per month. The Pro and Expert plans unlock more of the 78-guide library. No credit card required.