FDA 21 CFR Part 820 in Windchill: Design Controls & DHF
Compliance
Eric Horn
Managing Partner
How Does PLM Support FDA 21 CFR Part 820 Compliance?
FDA 21 CFR Part 820 — the Quality System Regulation for medical devices — requires manufacturers to maintain design controls, a Design History File (DHF), a Device Master Record (DMR), and rigorous change control. A PLM system like PTC Windchill operationalizes these requirements: it structures the DHF, links design inputs to outputs, enforces design reviews, and maintains the change history regulators expect. Done right, the quality system is enforced by the PLM rather than maintained alongside it in documents.
Key Fact | Detail |
|---|---|
Regulation | FDA 21 CFR Part 820 (Quality System Regulation / QSR) |
Note | Harmonizing with ISO 13485 under FDA's QMSR (effective 2026) |
Key artifacts | Design controls (820.30), DHF, DMR, DHR |
PLM's role | Structure DHF/DMR, link inputs↔outputs, enforce design review & change control |
Related standard | ISO 13485 |
Key platform | PTC Windchill |
The Part 820 Requirements PLM Addresses
1. Design Controls (820.30) — The heart of Part 820. Design controls require managing design inputs, outputs, reviews, verification, validation, transfer, and changes. PLM links each design output back to its input (traceability), routes formal design reviews, and records V&V — turning design controls from a binder exercise into an enforced workflow.
2. Design History File (DHF) — The DHF must demonstrate the device was developed per the approved design plan. PLM structures the DHF as a living, linked record rather than a folder assembled before audit.
3. Device Master Record (DMR) — The DMR is the recipe for the device (specifications, production processes, QA procedures). PLM manages the controlled product definition that the DMR comprises.
4. Change Control (820.30(i), 820.40) — Part 820 requires that design and document changes be reviewed, validated, and approved before implementation. PLM enforces a formal change workflow with approvals, effectivity, and audit trail.
5. Document Controls (820.40) — PLM is a controlled document system by design: versioning, approval, and controlled access replace uncontrolled documents.
Why "Enforced by PLM" Beats "Maintained Alongside It"
Many device makers keep the quality system in parallel — documents and spreadsheets that mirror what's in engineering. That duplication is where compliance breaks: the DHF drifts from the actual design, change records get out of sync, and audits surface gaps. When the DHF, DMR structure, design reviews, and change control all live in PLM and are linked to the actual product data, the quality record is the engineering record. There's nothing to reconcile, and traceability holds under inspection.
Common Pitfalls
DHF as an afterthought. Assembling the DHF at the end, from scattered sources, instead of building it continuously in PLM.
Broken input→output traceability. Without linked requirements, you can't show a design output traces to an input — a core design-controls expectation.
Uncontrolled change. Implementing design changes without the review/validation/approval Part 820 requires.
Parallel quality system. Maintaining quality records outside PLM, guaranteeing drift between "what's designed" and "what's documented."
Validation gaps for the PLM itself. Software used in the quality system is expected to be validated for its intended use.
How Element Approaches Part 820-Ready PLM
Element configures Windchill for medical device makers around design controls, DHF/DMR structure, and validated change-control workflows — so the FDA quality system is enforced by the PLM, not maintained in parallel. Implementations are run by engineers familiar with Class II and Class III device requirements. See our medical devices PLM page.
General guidance, not regulatory advice. Validation and compliance decisions should involve your quality/regulatory function.
Frequently Asked Questions
Does FDA 21 CFR Part 820 require a PLM system?
No — Part 820 doesn't mandate PLM. But its design-control, DHF, DMR, and change-control requirements are very difficult to satisfy and keep audit-ready without one, which is why most device manufacturers operationalize the QSR in PLM.
How does Windchill support the Design History File?
Windchill structures the DHF as a linked, living record — connecting design inputs, outputs, reviews, and V&V — so it demonstrates the device was developed per the approved plan, rather than being assembled from folders before an audit.
How is 21 CFR Part 820 changing in 2026?
FDA is harmonizing the QSR with ISO 13485 under the Quality Management System Regulation (QMSR). The underlying expectations for design controls, records, and change control remain — and PLM continues to be how manufacturers enforce them. Confirm specifics with your regulatory team.
Does the PLM system itself need to be validated?
Software used as part of the quality system is generally expected to be validated for its intended use. A Part 820-ready PLM implementation includes a validation approach for the configured system.
See Also
About the author
Eric Horn
Eric Horn is Managing Partner at Element Consulting and a PTC Certified Windchill Implementation Practitioner with 20+ years in PLM across aerospace, industrial, and medical.
