What BIM information do facilities managers actually need?

Facilities managers need the information that lets them identify, operate, inspect, maintain and replace the assets in their care, and they need to find it quickly, in the systems they actually use. That is usually a far smaller and more specific set than a design model contains: reliable identifiers, locations, types, key properties, the relationships between equipment and the spaces or systems it serves, and the right documents linked to each asset.

The exact list depends on the maintenance strategy and the receiving systems. The most reliable way to define it is to start from the tasks the operations team performs, involve that team early, and test real tasks before the information schedule is finalised. A single bad weekend shows why.

Work back from the tasks

For each task, identify the minimum properties and documents, who provides them and at what stage. A long property set is of little use if the essential identifiers or relationships are unreliable. ISO 19650-3:2020, which ISO has put under revision, sets out information management for the operational phase of assets and the exchanges within it, and a task list like this is where those requirements become concrete for a particular building.

Not every object needs its own record

Not every object in a model should become an asset in the maintenance system. A large air-handling unit should; individual ceiling tiles should not; a run of light fittings might be managed as a group. That decision belongs to the maintenance policy and should not be driven by how easily model objects export. Guidance on information requirements from the IMI Framework (formerly the UK BIM Framework) frames this as defining the information required according to its purpose, "no more and no less", and warns against generating wasteful information.

Shape the deliverable to the receiving system

Much of the operational information ends up in a CAFM or CMMS (computer-aided facilities management or computerised maintenance management system). Check early how that system expects asset types, location hierarchies, classification, units and document links, and specify the deliverable to match. A technically valid exchange can still need weeks of manual rework if it does not fit the way the receiving team works.

Name who provides and who checks

Information arrives at different times from different parties. Design teams provide types and locations; installers provide makes, models and serial numbers; commissioning engineers provide settings and test records. For each item, the schedule should name who provides it, who checks it and when. Serial numbers and installed locations should be verified on site, not copied from submittals.

The equipment that is easiest to forget

Network switches, wireless access points, BMS controllers, sensors, meters and access-control hardware are often missing from handover information, or listed without locations and relationships. Yet they are increasingly the assets operators need to find fastest when something stops working. They belong in the same schedule, under the same identifier rules, as the boilers and pumps.

Let the users try it before handover

Before final handover, import a representative sample into the CAFM or CMMS and ask facilities staff to carry out normal tasks with it. Whatever fails can then be fixed while the delivery team is still engaged.