Skip to main content
IBDT Intelligent Buildings Digital Twinning University of Toronto

IBDT · University of Toronto

Data Portal

A single, governed platform for discovering, requesting, and using campus building data—serving operations and research alike.

Drawings, meters, work orders, and models all describe the same buildings, yet they typically reside in separate systems. The IBDT Data Portal brings them together in a single governed layer. Using knowledge graphs, it creates interoperability between datasets without requiring prior knowledge of each source’s schema.

What the Portal Provides

Data streams and records are catalogued with lineage and retention policies, and published as queryable views in which permissions follow the asset.

  • Structured data — BIM models, sensor logs, and standardized records such as work orders and facility condition reports.
  • Unstructured data — documents, reports, and spreadsheets, registered with version and scope.
  • Operational telemetry — utilities, sub-metering, and environmental measurements where instrumentation exists.
  • Managed access — role-based permissions, auditable exports, and separation between production and research environments.
Abstract view of building data layers and digital model context

How It Is Engineered

Three capabilities underpin the portal: harmonization that makes relationships between datasets explicit, analytics tied to shared definitions, and governance policies for consistent collection, quality control, and use of data.

Harmonization

Identifiers, units, and time zones are normalized before publication; conflicting sources are versioned rather than silently overwritten.

Decision-Ready Views

Indicators and summaries are documented with their refresh cadence and known limitations, so every figure can be traced to its source.

Governed Evolution

Policy updates are introduced with notice, and usage patterns guide ongoing refinement—so the platform grows sustainably.

Why a Shared Data Layer

Data volume is rarely the obstacle—ambiguity is. When the same room carries three different identifiers across maintenance, drawing, and energy systems, every retrofit and every study inherits that inconsistency. The portal does not replace source systems; it makes the connections between them explicit, reliable, and governed.

Design Principles

  • Interfaces designed for operational staff as well as researchers
  • Explicit scope: what the pilot includes, what it does not, and who owns updates
  • An architecture that new models and APIs can extend without rework
  • A federated structure built to scale campus-wide