Mixed-fleet is the default state
Hospitals that started with one robotics OEM rarely stay there. Different vendors lead in different verticals: one platform is dominant in materials transport, another in pharmacy delivery, another in lab specimen handling, another in specialized clinical-adjacent applications. As the use cases expand, the vendor footprint expands with them. Within three years of the first deployment, most mid-size and large health systems are running two or more OEMs on the same campus.
Each OEM arrives with its own contract structure, its own service portal, its own ticketing system, its own SLA framework, its own escalation path, and its own quarterly business review cadence. Without a deliberate vendor management model, the hospital ends up running three contracts where it needs one, three escalation paths where it needs one, and three accountabilities where it needs one. This piece is the framework for managing that complexity.
The cost of poor vendor management
Mixed-fleet sprawl with no operating layer produces predictable problems:
- No single uptime number. Each OEM reports against its own definition, and the hospital cannot produce a fleet-wide view.
- Finger-pointing during incidents. When a robot fails to interface with an elevator or a network, OEM A blames the elevator vendor and OEM B blames the network. Nobody owns resolution.
- Inconsistent parts strategies. Some OEMs hold critical spares on-site, others ship from a central depot, others require part orders. The hospital absorbs the variance as downtime.
- Duplicated supervisory overhead. The supply chain team ends up running parallel governance for each OEM relationship, consuming time that should go to the program as a whole.
- No data integration. Telemetry from each OEM lives in its own portal. There is no consolidated fleet view, no consolidated reporting, no consolidated predictive maintenance signal.
Two viable models — and one that doesn’t work
Model A — Hospital-managed vendor portfolio
The hospital retains direct contracts with each OEM and builds an internal team to manage the portfolio. This model works when the hospital has the scale to justify a dedicated vendor management function, a robotics-experienced operations leader, and the willingness to be the integration layer across OEMs. It is most common in very large academic medical centers and IDNs with central robotics offices.
The trade-off: it is expensive. The hospital is, in effect, building an internal operations layer from scratch — duplicating capabilities that exist commercially, often at higher cost than contracting for them.
Model B — Vendor-neutral operating partner
The hospital retains OEM contracts where it makes sense (hardware, firmware, parts) but contracts a vendor-neutral operating partner to take responsibility for day-to-day operations, maintenance, SLA performance, and consolidated reporting across the entire fleet. The hospital sees one team, one SLA, one report. The operating partner manages the OEM relationships on the back end.
This is the model with the strongest economics at most scales, and it is the one CoolSmart was built to deliver. It also produces the cleanest governance, the cleanest reporting, and the cleanest accountability.
Model C — Distributed self-management (doesn’t work)
The hospital lets each OEM manage its own portion of the fleet without a unifying operating layer. This is the default outcome when nobody makes a deliberate decision. Every problem in the prior section appears, predictably, within twelve months.
Contract terms that protect mixed-fleet operations
Whichever model the hospital chooses, the OEM contracts themselves should include terms that make portfolio management possible. Five clauses every OEM contract should contain:
- Telemetry rights. The hospital — or its designated operating partner — must have access to the full telemetry stream from every robot. No proprietary lockout.
- Service interoperability. The OEM must permit third-party maintenance on agreed components and provide parts at agreed prices, even when the hospital uses a different operating partner.
- SLA standardization. Where possible, align SLA definitions across OEMs. Uptime measured the same way. MTTR measured the same way. Reporting cadence aligned.
- Data portability. Fleet management data, performance history, and maintenance records belong to the hospital and must be exportable in standard formats.
- Exit terms. Defined off-ramp if the OEM is acquired, exits the market, or fails to perform — including transition support and data handover.
Operating governance for mixed-fleet
Three governance practices distinguish well-managed mixed-fleet hospitals:
- A single weekly operations review covering the entire fleet, regardless of OEM. The operating partner — or the internal operations leader, in Model A — runs the meeting. Every robot’s performance is visible in one report.
- A consolidated incident review. When something goes wrong, one investigation, one root cause, one corrective action plan. Not three OEM reports that don’t reconcile.
- A quarterly OEM business review that the operating partner runs, not the hospital. The hospital attends; the operating partner manages the conversation, the metrics, and the accountability.
What good looks like, in practice
- One executive dashboard shows fleet-wide uptime, throughput, and incidents across every OEM.
- The hospital’s supply chain leader has one number to call when anything in the robotics estate is not performing.
- Service credits flow through one contractual mechanism, not three.
- OEM relationships remain healthy — the hospital is not playing OEMs against each other, the operating partner is managing each vendor on the merits.
- Adding a new OEM to the fleet is a project, not a re-architecture of the operating model.
The takeaway
Multi-OEM hospital robotics fleets are now the norm, not the exception. The operating model has to be designed for that reality. The most reliable approach is a vendor-neutral operating layer that consolidates accountability, telemetry, governance, and reporting across whatever OEMs the hospital chose — preserving OEM relationships where they add value, and absorbing the integration burden where they don’t. The hospitals that get this right scale automation cleanly. The hospitals that don’t end up with three vendor relationships, three escalation paths, and one set of frustrated floors.
| Three OEMs. One operating partner.
Stop juggling three contracts, three on-call lines, and three reporting formats. See how mixed-fleet operations actually run. → Get the Vendor Management Checklist |
