OFCI is the right procurement model for medical equipment, but coordination between vendor, contractor, and architect lives in the gap between contracts, and that gap belongs to the owner. Savings erode through rough-in changes, storage, and delays unless one named party owns a responsibility matrix.
Owner-furnished, contractor-installed equipment, known as OFCI, is the standard delivery model for medical equipment on institutional healthcare projects, and for good reason. Group purchasing organization contracts give health systems pricing no builder could access, vendor relationships carry warranties and service agreements the owner needs to hold directly, and equipment often sits on a separate capital budget from construction. On projects where medical equipment can approach a third of total cost, buying direct is simply correct. The risk begins after the purchase order.
Every OFCI item carries three coordination obligations: rough-in data delivered to the design team in time to inform the documents, a delivery date sequenced against construction readiness, and a clear answer to who receives, uncrates, sets, and connects the item. The vendor assumes the contractor handles site logistics. The contractor assumes the equipment arrives ready to install, with utilities already defined. The architect assumes someone sent them current cut sheets. Each party is behaving reasonably within its contract. The coordination lives in the space between contracts, and that space belongs to the owner.
This is how procurement savings erode. Rough-in changes discovered after walls close become change orders. Equipment arriving before the building is ready becomes storage, insurance, and rehandling cost. Equipment arriving late becomes schedule delay priced at general conditions rates. A single imaging unit with an outdated cut sheet can cascade into structural revisions, shielding rework, and a resequenced inspection schedule. None of these costs appear on the group purchasing contract, which is why the savings look real in the budget and vanish in the closeout report.
The fix is administrative rather than technical: a single responsibility matrix, one line per item, tracking vendor, rough-in status, delivery date, receiving party, and installing party, reviewed at every owner-architect-contractor meeting. Someone has to own that document. The owner can hold it internally, or assign it to their project manager, but it exists only if the owner names it as scope. Assume the document has no owner until someone is named.