Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11BI(m) is a proposal to make structured building data—not 3D geometry—the durable center of an owner’s information system. In John Tobin’s February 8, 2019 article for Building Design + Construction, the capital “BI” preserves the goal of building information, while the lower-case “m” signals that the model can become less central after construction. Asset records can live in linked tables, be visualized in a plan-like interface, and still be referenced from a model whenever spatial context is valuable.
This is an author’s framework, not evidence of an industry-wide standard or measured performance advantage. Its value is as a design question: for each operational task, should the source of truth be model geometry, a relational data store, or a deliberate combination of both?
As an Amazon Associate I earn from qualifying purchases.
What BI(m) means after handover
Building information modeling combines information with a digital representation of a facility. During design and construction, geometry is often the most useful organizing context: a team can select a wall, valve, door, or air-handling unit and inspect its properties in place. Operations teams, however, frequently need answers that are primarily tabular. A maintenance coordinator may need every pump due for inspection, the manufacturer’s spare-part number, the room in which each pump sits, and the open work orders. A three-dimensional view may add little to that query.
BI(m) separates those concerns. It treats building information as structured records about components, spaces, floors, zones, buildings, manufacturers, models, and spare parts. A model remains available as a view or reference when location and geometry matter, but it is not automatically the permanent container for every operational field. Tobin summarizes the underlying choice as: “What is at the center of a building database, BIM or Data?”
#1 Best Overall
What the lowercase “m” is—and is not
The lowercase letter does not mean that models are discarded. It indicates reduced emphasis on the model once the building is operating. Fire protection inspection history, warranty dates, cleaning schedules, energy readings, and replacement costs may be easier to manage in databases connected to work-order or facilities systems than in a heavy authoring file. Geometry can still be linked for navigation, spatial verification, renovation planning, or situations in which shape and clearance are operationally important.
The proposal therefore changes the center of gravity, not the existence of BIM. The right arrangement depends on the task, the people using the information, and the systems that must exchange it.
Why keep operational data outside model geometry?
Tobin identifies three risks in a model-centered operational workflow. They are stated concerns in his 2019 account, not quantified failure rates or universal properties of BIM software.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors1. Geometry can add performance and access overhead
Operational questions are often lightweight database queries, yet a user may have to open, load, and navigate a geometrically rich file to reach a small set of properties. Large models can require specialized applications, powerful hardware, disciplined views, and staff trained in 3D navigation. A table or dashboard can expose the same component identifiers and maintenance fields with less visual and technical overhead. That does not prove a database is always faster; it identifies a mismatch between the weight of the container and the weight of the question.
2. Transfers can lose fields
Information commonly moves from authoring tools to handover packages, computerized maintenance-management systems (CMMS), document stores, and specialist applications. Tobin warns that transfers between systems can drop fields or change their meaning. A component that has a complete property set in the authoring file may arrive in a destination system without a spare-part number, classification, room relationship, or responsible party. A data-centered design makes mappings, required fields, and validation visible instead of assuming that a model export preserves everything.
3. Long-term access can depend on discontinued software
An owner may need asset information years after a project team has changed products, licenses, or file formats. If essential records can be read only through a particular 3D application, future retrieval is exposed to that product’s availability and compatibility. Keeping durable records in documented tables or databases can reduce dependence on a single viewer, while retaining a model reference for cases that genuinely require geometry. BI(m) raises this as a longevity concern; the article supplies no forecast about which products or formats will remain supported.
How a data-centered building database is organized
The proposed structure is relational: records are separated into logical tables and connected by identifiers. One table can describe components; others can describe spaces, floor levels, zones, and buildings. Relationships answer both “where” and “what” questions without duplicating every attribute in every view.
Where relationships
- Space: the room or named area containing an asset.
- Floor: the level on which the space is located.
- Zone: an operational or spatial grouping that may cross rooms.
- Building: the facility or campus location.
A space record can link to many component records. Selecting a room can therefore filter all associated equipment, fixtures, or maintainable assets. A floor or building filter can broaden the same query without editing the component records.
What relationships
- Component identity: a stable asset or equipment identifier.
- Model and manufacturer: the product designation and maker.
- Spare part: compatible replacement information.
- Operational attributes: fields such as service responsibility, warranty details, or inspection requirements when the owner defines them.
The critical design choice is a stable key that lets systems refer to the same asset. Names and room labels can change; an identifier should remain traceable through handover, maintenance, replacement, and refurbishment. Tobin does not prescribe a complete governance scheme, so an owner must define who creates keys, who can change them, and how retired components are recorded.
COBie as a tabular exchange example
Tobin presents COBie as an example of linked tables rather than as a 3D geometry format. His description includes tables for components, spaces, floor levels, and other project information, with relationships that let a user identify which components belong to a space and inspect what those components are. In the workflow he discusses, COBie was commonly delivered as an export from a BIM file.
BI(m) reverses the assumed direction: the structured data could originate in a durable data source and be linked into a model when a model view is useful. That is a conceptual alternative, not a claim about current COBie implementations or standards status. Teams should verify the exchange requirements of their own owner, contract, and facilities systems before choosing a source-of-truth arrangement.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →What a COBie-like table set must preserve
- Unique component identifiers that remain consistent across exports.
- Explicit links between a component and its space, floor, zone, and building.
- Human-readable names plus manufacturer, model, and spare-part fields where required.
- Defined data types, allowed values, and rules for missing information.
- Change history or a process for reconciling updates after handover.
These controls matter whether records begin in a model or in a database. A spreadsheet that has attractive columns but no reliable keys or update responsibility is not a dependable operational system.
A practical BI(m) workflow
The following sequence translates the article’s proposal into an implementation pattern. It is a framework, not a prescribed software stack.
- Start with operational questions. List the decisions staff must make: which assets are due for service, what is in a room, which supplier provides a replacement, or which work orders affect a floor. Avoid collecting fields merely because an authoring tool can export them.
- Define the minimum asset record. Agree on identifiers, component type, location links, manufacturer and model fields, spare-part references, responsible organization, and required dates. Mark each field as required, optional, or not applicable.
- Choose the system of record. Decide whether a relational database, facilities platform, or model will own each field. Record the owner and update event for every critical attribute. Where two systems must display a value, designate one as authoritative and synchronize the other.
- Map spaces and components. Build relationships among building, floor, zone, space, and component IDs. Test queries such as “show every maintainable component in Room 204” and “show the room and spare part for this pump.”
- Validate exchange fields. Export a representative set and compare source and destination values. Check that identifiers, dates, classifications, and location links survive the transfer. Treat any missing field as a mapping defect to resolve, not as an invisible assumption.
- Connect a model selectively. Link records to geometry when users need visual orientation, clearance checks, spatial inspection, or design context. Keep operational attributes in the data source when a model adds no decision value.
- Publish role-appropriate views. Provide a table or dashboard for routine maintenance, a plan-like view for location, and a model view for geometry-dependent work. Apply permissions and show the record’s last-updated date.
- Operate a change process. When equipment moves, is replaced, or is decommissioned, update the location relationship and status, preserve the history required by the owner, and test links from the model and facilities systems.
Visual context without storing everything in 3D
A data-centered system does not have to look like a spreadsheet. Tobin names Power BI and Tableau as examples of visualization tools that can link to datasets. His illustration uses a floor-plan-like visual with interactive filtering: a user can select a space and see the associated components, or filter by an equipment attribute and identify where those assets are located.
This approach is useful when the operational question needs orientation but not full geometry. A simplified plan can show rooms, floors, and zones while the selected asset list supplies manufacturer, model, or maintenance fields. The article’s examples demonstrate a possible workflow; they are not a current comparison of either product’s features, licensing, price, or suitability.
When a model view remains the better interface
- Clearance, routing, and constructability depend on three-dimensional shape.
- A technician must see the exact physical relationship among connected systems.
- Renovation planning requires geometric coordination with new design work.
- Visual inspection is faster or safer than interpreting a plan and table.
In those cases, the model can consume or reference governed data rather than becoming the only place that data exists.
Harvesting data from existing BIM files
Many owners inherit information embedded in models. Tobin describes using scripting tools such as Dynamo and Python to extract model properties into tables, then combine those results with other operational information. A harvesting exercise can turn an existing handover file into a starting dataset without requiring staff to re-enter every property manually.
Extraction checks
- Identify which model elements are actual maintainable assets and which are graphical or temporary objects.
- Map property names to the owner’s canonical fields; do not assume similar labels have identical meanings.
- Capture the element’s stable identifier and its space, floor, zone, and building relationships.
- Flag blank, duplicated, or conflicting values for human review.
- Record the model file, version, extraction date, and script version used to create the table.
After extraction, reconcile the table with commissioning records, equipment schedules, warranties, and the CMMS. Scripting can accelerate collection, but it cannot decide whether a manufacturer field is correct or whether a replaced unit should remain active.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Model-centered versus data-centered: a decision guide
Neither arrangement wins for every asset or task. Use the following axes to make the choice explicit.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
| Decision axis | Model-centered emphasis | Data-centered emphasis | Question to ask |
|---|---|---|---|
| Context | Geometry is the primary way to find and understand the asset. | Linked tables or a simplified visual provide enough location context. | Does the task require shape, clearance, or connected-system relationships? |
| Interoperability | Properties travel with model exports and viewer workflows. | Fields are mapped between governed tables and destination systems. | Can required values move without loss or changed meaning? |
| Longevity | Future access depends more heavily on model software and format support. | Durable records are readable independently, with model references retained. | How will an owner retrieve the data if a product is discontinued? |
| Accessibility and performance | Users need model navigation and potentially specialized hardware. | Users query tables or dashboards designed for their role. | What is the simplest reliable interface for the people doing the work? |
| Governance | The model may act as the de facto source of truth. | Each field has an owner, key, validation rule, and synchronization policy. | Which system is authoritative when values disagree? |
| Fit by use case | Best where geometry drives the decision. | Best where filtering, history, and system exchange drive the decision. | Should this record live in one place, or be referenced in both? |
Common failure modes and practical fixes
Putting every field in the model
Symptom: staff struggle to find simple maintenance information and exports become unwieldy. Fix: separate operational records from geometry where the visual model does not improve the task, then link the asset identifier back to the model.
Best Value
Assuming an export is a complete handover
Symptom: the destination CMMS lacks fields that appeared in the authoring file. Fix: create a field-level mapping, test a sample export, and obtain acceptance from the operations team before handover.
Using names instead of stable identifiers
Symptom: a renamed room or replaced asset breaks filters and historical records. Fix: assign persistent component and space keys, retain aliases for search, and mark retired records rather than deleting them.
Publishing a dashboard without stewardship
Symptom: a polished visualization shows outdated equipment or conflicting locations. Fix: define update triggers, responsible roles, validation checks, and a visible last-updated value.
Recommended Free Tools
Replacing useful geometry too aggressively
Symptom: technicians lack the spatial detail needed for routing, access, or safety decisions. Fix: keep model references for geometry-dependent work and use the data-centered approach selectively.
What BI(m) means for an owner’s information strategy
BI(m) is best understood as a placement and governance question, not a mandate to abandon BIM. Keep geometry where it carries operational meaning; keep durable, frequently queried records where they can be exchanged, validated, and maintained efficiently. In some cases the same asset should appear in a relational data source, a dashboard, a CMMS, and a model, with one clearly identified source of truth and controlled links among them.
Tobin’s 2019 article does not report adoption statistics, cost savings, data-loss percentages, or a controlled comparison. It offers a way to challenge an automatic assumption: that every piece of building information must remain embedded in a 3D file forever. Owners can use that challenge to design information deliverables around real operational questions, longevity, interoperability, and the level of visual context each task actually requires.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →
