The structure of every dictionary, the attributes of every property, and the formats of every export follow published international and industry standards. That is what makes the record portable between organizations and tools.
An international framework for organizing construction information as objects, properties, and the relationships between them.
In the platform: the shape of the dictionary itself. Objects, property groups, and templates follow this model.
Defines how a property should be described: its name, definition, data type, units, physical quantity, and allowed values.
In the platform: the attribute columns on every property and datasheet. Checks validate each attribute against this method.
Defines data templates: reusable sets of properties that describe a type of object consistently across projects.
In the platform: object templates and their property assignments, including the checks that keep groups and properties consistent.
The buildingSMART open standard for exchanging built-asset models between software, extended in 4.3 to cover infrastructure.
In the platform: objects carry IFC entity mappings, and the master record exports property sets in ifcXML.
A North American classification system for the built environment, organized as numbered tables.
In the platform: objects carry OmniClass codes so downstream systems can classify them without translation.
Standards sound abstract until two teams try to share data. One calls a field Diameter, the other calls it NominalSize, and a third stores it as text. A dictionary built on these standards settles those questions once, in a form other organizations and software already understand.
The review process exists to enforce that promise. Every check in the platform traces back to a requirement in one of these documents or in the owner's own governance rules.
See how these standards become checks, marks, and a governed record.