An engineering firm delivers a BIM+ project on a new industrial facility: eight thousand modeled elements at LOD 400, MEP disciplines resolved, an IFC 4 handover file that passes every formal check. Three months into commissioning, the plant's maintenance lead calls the firm with a simple question: which valves sit downstream of centrifugal pump B on line three. The firm points to the IFC. The maintenance lead explains that his CMMS does not query IFC files, that his team does not hold the BIM authoring license and that answering the question requires two qualified modelers to open the file back at the office. The conversation ends with a reluctant commitment: the firm will prepare an extraction of the model. What starts as an extraction turns into a second three-month project.
The scene describes the BIM/O&M boundary without naming it. A BIM model is a design and construction tool; an asset register in a CMMS-plus-GIS is an operations tool. The two data models exist to answer different questions and hold value when each one answers its own. Treating the step from one to the other as an export is what produces the conversation above, and it also erodes the engineering firm's margin in a class of project where the differentiator has moved from producing the BIM to delivering its operational dividend.
What BIM preserves and what O&M actually needs
A BIM model delivers rich geometry, a defined level of development, constructional material information, MEP layers with connectivity for the installation phase and, often, cost information. All of that is useful during the project; part of it loses relevance the day the plant begins to operate. The operator's CMMS-plus-GIS needs a different set of fields: georeference against a real coordinate system, operational network topology — which element connects to which at a network level, not at an MEP connector level — asset criticality, maintenance window, contractor responsibility, intervention history and links to the operator's document system. The two sets overlap partially. The translation is neither literal nor clean: some BIM fields are discarded, some O&M fields are added, some geometry is simplified.
The three losses at the boundary
Three concrete losses happen consistently when the model crosses the boundary into the operational system, and all three can be anticipated in the design phase of the deliverable. The first is georeference. A BIM model typically lives in local or model coordinates defined against a project origin; the operator's CMMS-plus-GIS lives in a geographic projection — ETRS89, a UTM zone or whichever coordinate reference system the asset scope requires. Without an explicit and validated transformation, the asset's location in the operational system does not match its real-world position, and any spatial query stops meaning what it should. The second is topology. BIM connects MEP elements so the installation phase is coherent; operational network topology — which valve isolates which sector, which segment feeds which service connection — is a different model that is rarely declared explicitly in the IFC. The engineering firm assumes a downstream topological exporter will infer it; in practice, the inference demands substantial human validation. The third is operational metadata. Criticality, maintenance windows, responsible contractor and links to the preventive plan are not part of the standard BIM scope; they are born outside the model and need to be brought into the asset register at transformation time.
BIM to GIS as a defined process
A useful asset register is not exported from BIM; it is built from BIM through a defined process. The process has four concrete steps that the technical office can protocolize. First, coordinate transformation from the model's local system to the client's geographic system, validated through sampling against known control points. Second, explicit modeling of operational topology: identification of nodes, arcs and connectivity rules, and validation against the same spatial rules any GIS audit would apply — endpoint integrity, absence of dangles and overshoots, connectivity by component. Third, LOD reduction for operability. LOD 400 loads the operational model with geometry irrelevant to querying; LOD 250 preserves what matters and releases performance. Fourth, enrichment with operational metadata through a form or an import from the criticality matrix the operator provides. The result is not a simplified BIM. It is an asset register born out of BIM, purpose-designed for operational querying. The cost of running this process, when it is protocolized inside the BIM+ project, translates into a small percentage of the total scope — typically between five and ten percent — and absorbs a meaningful share of the rework that today consumes the commissioning phase. Without the process, that percentage is paid later, either as a second engagement or as degraded operations for the client during the first months of the plant's life.
What changes for the engineering firm
At Maptainer, we work with this engineering profile by folding the BIM-to-GIS step into the modular deliverable. The common inventory module receives the transformed geometry, the validated topology and the enriched metadata; the operator activates the corrective and preventive modules when the process requires it, without a second migration. The step is executed once, inside the natural project window, and the asset register lands operable from day one.
The technical differentiator for an engineering firm in a BIM+ project is no longer whether it can produce the BIM. It is whether the BIM produces an operational dividend within the project itself, without demanding a second contract from the client three months later. The conversation with the client shifts: the firm no longer defends the LOD of the model; it defends the operability of the asset register that emerges from it. That is the ground where a technical office can differentiate today without falling back on price. A client that has lived through one operational dividend delivered from a BIM will actively look for the same firm on the next project, because they will remember the exact day the plant started operating without having to ask the engineering office for a rescue call, and how quickly the same firm turned that memory into the next signed contract.