Decision right
The organization names the decision the data supports, the user, response, threshold, and accountable owner.
The building produces data. Who keeps the leverage?
A data point is only useful when its meaning, quality, permitted use, owner, access path, decision role, retention, and exit are clear. Put those rules in the operating model and the contract.
Begin with the decision, not the lake.
For each promised use, name the operational decision, required source points, context and identifiers, acceptable quality, response owner, retention need, permissions, and exit format. Data with no decision or owner is an unmanaged cost and exposure.
Data path in view
Govern the full data lifecycle.
Collection, decision rights, and a usable export path should be designed before the building starts producing data.
01
02
03Published 8 September 2026 · reviewed 9 September 2026. Editorial illustrations generated for Hamed Helped; they do not depict a named site, vendor, or client.
Decision criteria
Six rights turn data access into operational control.
Context right
Points retain asset, location, unit, timestamp, status, units, lineage, and semantic relationships.
Challenge right
Users can see completeness, freshness, calibration, transformations, exceptions, and disputed values.
Use right
Authorized roles can retrieve required raw and normalized data through workable interfaces and formats.
Governance right
Collection, sharing, model use, retention, deletion, and secondary use have named approval and review.
Portability right
The owner can export data, context, configuration, and history in documented formats on a tested timeline.
Questions to ask
Follow one point from sensor to decision.
- Where did it come from?
Identify the physical source, controller, gateway, transformations, quality checks, timestamps, and current status.
- What does it mean?
Preserve units, asset relationship, location, ontology or tagging, calculation method, and business context.
- Who may use it?
Separate access for operations, tenants, vendors, analysts, models, service providers, and downstream systems.
- Which decision changes?
Name the person, trigger, action, exception path, response time, and record created.
- How long is it useful?
Set retention by operating, legal, privacy, maintenance, analytical, and dispute needs—not unlimited default.
- What leaves with the vendor?
Test export of raw data, normalized data, tags, relationships, rules, configurations, logs, and history.
Evidence table
A data clause needs an operating test.
| Claim or decision | Evidence | Owner | When checked |
|---|---|---|---|
| Data purpose | Decision-to-data map with named action, owner, threshold, and outcome | Business process owner | Before collection |
| Point meaning | Data dictionary, identifiers, units, semantic model, lineage, quality status | Data steward + system owner | Integration and change |
| Permitted use | Role matrix, contract terms, privacy basis where applicable, sharing and model-use rules | Data owner + legal/privacy | Before access and at review |
| Decision reliability | Freshness, completeness, exception, calibration, and disputed-data process | Operations + data steward | During operation |
| Exit portability | Sample export, schema, context, configuration, transfer timing, deletion confirmation | Property owner + procurement | Before contract and before exit |
Failure modes
Four ways a building loses data leverage.
Access without meaning
A CSV exists, but identifiers, units, relationships, calculations, and status cannot be reconstructed.
Dashboard without extraction
The owner can view a vendor interface but cannot reuse or transfer the underlying operational record.
More data without a decision
Collection grows while no workflow, threshold, response, or accountable person changes.
Ownership without an exit test
Contract language promises control, but the team has never received a complete usable export.
Connect the decision
Put data rights inside vendor due diligence before signature.
Evidence trail
Sources behind this guide
- 01BOMA BEST Field GuideR1.1 Data Access and Ownership (external link)
Owner/operator considerations for direct data access and common-format export.
- 02IEA EBC Annex 81A Guide on Data Platforms for Data-Driven Smart Buildings (external link)
Research guidance on data platforms, semantic models, lineage, and governance capabilities.
- 03Telecommunications Industry AssociationWhite Paper: Building Operating Systems (external link)
Industry guidance connecting data management with smart-building architecture and lifecycle.