Manufacturer Insights
Medical Device Installed-Base Management: A Practical Guide
A practical way to turn scattered distributor records into a more reliable view of equipment after delivery.
· 5 min read · For manufacturers, channel managers, after-sales leaders
A sale tells you where a device was shipped. An installed-base record helps you understand what happened after it arrived.
For manufacturers selling through independent distributors, those are often two different kinds of visibility. Commercial teams may know which distributor purchased a system, while the installation location, warranty start, service visits and training activity are maintained elsewhere. As the network grows, a simple spreadsheet can become difficult to reconcile.
An installed-base management process makes post-sale information more consistent without assuming that every organisation should see every record.
Key takeaway: Start with a reliable record for each installed unit, then connect the relevant lifecycle events and grant access according to business relationships and permissions.
What is an installed base?
A medical-device installed base is the set of equipment units that have been placed into use with customers. It is more specific than a product catalogue or sales shipment list. A catalogue describes a model; an installed-base record describes an individual unit in a real operating context.
A useful record may include the manufacturer, brand and model, serial or other appropriate identifier, distributor, healthcare customer or location, installation date, warranty coverage, maintenance schedule, service events and responsible contacts. Not every field will apply to every product or be shareable with every partner.
The World Health Organization describes inventory, maintenance and training as connected parts of health-technology management, continuing from equipment receipt through decommissioning. This supports treating installed-base information as a living operational resource rather than a one-time registration step. WHO, 2025.
Why manufacturers lose visibility after delivery
A common channel structure creates a natural information gap:
- The manufacturer records production, shipment and distributor sales.
- The distributor installs equipment and manages local customer relationships.
- Service engineers maintain visit notes, warranty details and maintenance schedules.
- Hospital teams keep their own asset lists and contact different suppliers for support.
Each party has legitimate responsibilities. The problem arises when useful facts are stored in separate systems, email chains, spreadsheets and individual employees' knowledge. A manufacturer may therefore understand sell-in better than the post-sale condition of an installed unit.
The post-sale visibility gap
The broken post-sale link
Through the sale, manufacturer and distributor are tightly connected. The moment the equipment is delivered, that connection breaks.
- Order placed
- Processed
- Shipped
- Delivered to distributor
No line of sight back to the factory
After delivery · post-sale zone
Not visible to the manufacturer
- Installation?
- Warranty?
- Service?
- Training?
- Consumables?
Link breaks
after delivery
The seven fields to establish first
Start with a manageable minimum data set rather than requesting every possible detail at once.
| Field | Why it matters |
|---|---|
| Unit identifier and model | Distinguishes an individual device from its product family |
| Installing organisation | Establishes who completed deployment |
| Healthcare site or permitted location | Supports customer service and regional coverage |
| Installation or commissioning date | Anchors lifecycle and contractual dates |
| Warranty status | Clarifies service coverage and expiry |
| Service and maintenance history | Creates continuity across engineer visits |
| Record owner and sharing permissions | Clarifies responsibility and protects commercial relationships |
A record is useful only if it is maintained. Assign ownership for initial registration, updates following a visit, and correction of duplicate or incomplete records.
Device identification is not the same as installed-base visibility
Unique Device Identification (UDI) frameworks help identify devices, but they are not equivalent to a manufacturer's local installation and after-sales system. The US FDA states that GUDID holds device-identifier information and does not include production identifiers such as individual serial numbers. It also does not identify who uses a device. FDA UDI Basics.
In the EU, EUDAMED's first four modules became mandatory to use on 28 May 2026, including the UDI/Device registration module. Those obligations address regulatory information systems; they do not, by themselves, replace day-to-day distributor service collaboration. European Commission EUDAMED overview.
Important: An operational installed-base platform should not be represented as a regulatory UDI submission service unless it actually provides that functionality. NOVENTRA does not submit data to GUDID or EUDAMED.
A practical five-step improvement plan
Step 1 — Choose a unit-level record. Standardise identification, model information and lifecycle fields before migrating every historic spreadsheet.
Step 2 — Assign responsibility. Specify who registers installations, confirms warranty terms and closes service records. Avoid multiple conflicting versions of the same record.
Step 3 — Introduce permission-based collaboration. Define what a distributor may share with a manufacturer and what a healthcare organisation can view. A shared platform should not require exposing confidential customer data indiscriminately.
Step 4 — Connect useful events. Link installation, service visits, maintenance, training and warranty information to the same unit where appropriate.
Step 5 — Review completeness, not just record count. Track missing installation dates, duplicated serial numbers, overdue service follow-ups and records that have not been updated after a visit.
What better visibility changes
Reliable installed-base information can help channel managers understand service coverage, identify records needing attention, coordinate distributor training and support more informed territory planning. It can also help distributors demonstrate documented work to manufacturers and healthcare customers.
These are potential operational advantages, not automatic financial returns. Results depend on the completeness of the records, the people updating them and the permissions agreed between parties.
How NOVENTRA fits
NOVENTRA is designed around connected, permission-controlled equipment records across manufacturers, distributors and healthcare organisations. Its verified capabilities include unit records, installed-base maps, service and warranty workflows, and manufacturer–distributor relationships. Distributors control what information is shared.
Instead of positioning installed-base management as a separate spreadsheet project, NOVENTRA connects that record to the post-sale work taking place around the equipment.
For manufacturers: Explore NOVENTRA Connect or book a demonstration.
Frequently asked questions
Is an installed-base list the same as an ERP inventory? No. An ERP may establish stock movements and sales transactions. An installed-base record emphasises the individual unit at its installed location and subsequent operational history.
Must manufacturers see every distributor customer? No. Sharing should follow agreed business permissions and privacy requirements.
Does installed-base software replace regulatory UDI registration? No. Regulatory submission obligations remain separate.
