Sustaining engineering is the set of engineering activities that keep a medical device safe, compliant, and manufacturable after market release. It covers change control, component obsolescence, supplier transitions, cost reduction, and corrective design updates, all managed under the device’s quality system and risk management file across the product’s commercial life.

---

What is sustaining engineering?

Sustaining engineering covers the work that begins after a device clears design transfer and enters routine production. The design history file is frozen, the device is on the market, and the job shifts from creating the product to keeping it viable. Engineers handle component end-of-life, respond to field complaints, reduce manufacturing cost, and update the design when a supplier or a regulation forces a change.

Some teams call it sustenance engineering or product lifecycle engineering; the scope is the same. It sits at the long tail of the lifecycle and often runs years longer than the original development program. Every change made here flows back through the same design controls, risk file, and change-control process that governed the original design.

---

Why sustaining engineering matters in medical device development

A released device is not static. Electronic components go obsolete, raw materials get reformulated, suppliers exit the business, and standards get revised. Left unmanaged, any of these can stop a production line or quietly degrade safety.

Patient safety is the first stake. A substituted resistor or a reformulated adhesive can shift a device’s performance or biocompatibility in ways that are not obvious until the device reaches a patient. The second stake is regulatory. Under ISO 13485 and the FDA QMSR (21 CFR Part 820, effective February 2, 2026), every change to a released device must be evaluated, documented, and, where needed, verified or validated before it ships. Skipping that creates audit findings. In the EU, it can turn a routine update into a significant change that triggers notified-body review under EU MDR 2017/745. The third stake is commercial: an unplanned obsolescence event can idle a line for months.

---

How sustaining engineering works

Sustaining engineering runs as a continuous loop of monitoring, assessment, and controlled change. The core activities:

• Change control. Every proposed change, whether driven by a complaint, a cost target, or a supplier, enters a formal change-control process. The team assesses the impact on design inputs, design outputs, risk, and regulatory status before approval.
• Risk re-evaluation. Each change runs back through the risk management file per ISO 14971. A change that looks minor on a drawing can introduce a new hazard or invalidate an existing control.
• Obsolescence and component management. Teams track end-of-life notices for parts, qualify alternates, and stage last-time buys so production never stalls.
• Corrective design changes. CAPA findings and field complaints feed design updates that remove the root cause rather than patching the symptom.
• Cost and value engineering. Value analysis and value engineering (VAVE) reduce cost without altering form, fit, or function in ways that would demand revalidation.
• Regulatory sustenance. Technical documentation, labeling, and the risk file are kept current as standards and regulations evolve.

For software, the loop is governed by the maintenance process in IEC 62304, which treats problem resolution and modification as a formal lifecycle, not ad hoc patching. The decision that drives everything is classification: is this change significant enough to require new verification, validation, or regulatory notification? MDCG 2020-3 guidance helps EU teams make that call.

---

Common challenges and best practices

The most common failure is treating a change as too small to document. A like-for-like part swap still needs an impact assessment; regulators expect a record showing the change was evaluated, even when the conclusion is no further action.

A second trap is reacting to obsolescence instead of forecasting it. Strong teams monitor supplier roadmaps and component lifecycles continuously, so a discontinuation notice triggers a planned response rather than a scramble.

Good practice ties sustaining engineering directly to the original design controls. The same traceability that linked design inputs to outputs during development should govern every post-market change, so the design history file stays a true record of the device as it ships today. Keep the risk file and the technical documentation living, not archived. Decide significance early, because misjudging a significant change under EU MDR can cost a CE certificate, while over-classifying minor changes wastes engineering capacity on needless revalidation.

---

How SJML helps with sustaining engineering

Syrma Johari MedTech (SJML) supports sustaining engineering as part of its product lifecycle management services. Teams handle change governance, obsolescence management, and value analysis and value engineering (VAVE) for devices already on the market, alongside RMA and replacement management and sustainability re-engineering. Regulatory sustenance work covers design history file remediation, ISO 14971 risk file updates, and technical documentation upkeep, structured to minimize revalidation burden. Capabilities span electromechanical hardware, embedded software under IEC 62304, and supplier qualification, so a change can be assessed across design, manufacturing, and compliance at once.

Talk to SJML’s engineering team →

---

Frequently asked questions

---

Related terms

• Obsolescence Management
• Design Change Control
• Lifecycle Management
• Value Analysis and Value Engineering (VAVE)
• Design History File