Change scenario: Example infusion pump program
- Requirements management | DI-PUMP-042 | Flow rate accuracy | ±5% → ±3% | Rev C
- MBSE | Pump Drive Module | System block | Accuracy budget ±5% → ±3%
- PLM | MTR-2210 | Drive motor | Encoder 512 → 2,048 counts
- ALM | HAZ-021 | Over-infusion risk item | Risk control updated for ±3%
- Test management | VER-FLOW-09 | Flow accuracy verification | Re-run per AAMI TIR101 at ±3%
- Baseline | DHF-BL-04 | Pump drive, every item verified against the ±3% requirement and ready for design review
The challenge
Every design decision has to be defensible.
Medical device programs live under design controls. Every input, output, risk control, and test has to stay connected as the device evolves.
- Design controls. Regulators expect a traceable path from user needs to verification, and building it by hand slows submissions.
- Validated environments. Quality and PLM systems are validated, so consolidating or replacing them is costly, slow, and risky.
- Risk tied to design. Risk controls must stay linked to the design and tests that implement them every time the device changes.
How SBE Vision helps
Traceability that holds up to an audit.
SBE Vision connects your requirements, design, quality, and test tools, so design history builds itself as engineering happens.
- Design history on demand. Design inputs, outputs, and tests stay linked, so design history is ready for review.
- Impact before approval. See every design output, risk control, and test a change touches before it’s approved.
- Design review baselines. Capture the thread at each design review to show exactly what was approved and when.
- Validated systems intact. Validated tools stay in place, and the thread connects them without copying data.
Standards
Built for how medical devices are regulated.
SBE Vision supports the traceability and evidence these regulations and standards ask for. It works alongside your quality system, not in place of it.
- FDA QMSR (21 CFR 820)
- ISO 13485 Quality Management
- ISO 14971 Risk Management
- IEC 62304 Medical Device Software
Typical toolchain
Connects the tools device teams already run.
Pre-built adapters cover the requirements, ALM, modeling, PLM, and test tools most common in medical devices, plus an SDK for in-house systems.
- IBM DOORS Next
- Jama Connect
- Siemens Polarion
- PTC Codebeamer
- Cameo Systems Modeler
- PTC Windchill
- Aras Innovator
- Gurock TestRail
- Jira
Program examples
How device teams use SBE Vision.
Medical device teams are putting the thread to work on live programs today.
- Customer scenarioDesign reviews, made easy. Device teams baseline the thread before each design review, so reviewers see exactly what changed.
- Customer scenarioDesign history, always current. Design inputs, outputs, and verification stay linked across DOORS Next, Cameo, and Windchill.
- Customer scenarioValidated systems, connected. A quality team links its validated PLM and requirements tools without replacing them or copying data.