The complete set of assertions about a building that a competent operator would need in order to run it as it is currently run: what exists, how it is arranged, how it is connected, what it is for, how it is operated through, what is known about it, and where each assertion came from.

That subset of building understanding which this standard requires to survive transfer between conforming systems.

Any addressable object in the model. Every entity has a durable identifier and a type. Relationships, bindings, and presentation elements are entities.

True of a thing in itself, independently of anything else. The test that decides whether a fact is a property or a relationship (5.3.1).

An addressable item of operational data: a measurement, an instruction, a state, a configured parameter, a calculated value, or a meter register. A point is not a value; it is the thing a value is about.

A declaration of what a property name means, its datatype, and its unit. Required for every property an exporter emits (7.8).

What a building or system is expected to achieve, as distinct from what it is doing and what it has done.

The durable definition of a condition, its limits and timing, its severity, and how it is to be routed, acknowledged, and shelved.

A timestamped occurrence attached to a subject: an alarm instance, an override, a mode change, a command, a service action. Not a time-series sample.

A page of portable presentation: a floor plan, equipment graphic, schematic, or one-line.

A placed thing on a drawing, identified by a symbol role, an embedded figure, or geometry.

A hierarchical dotted path naming what an element depicts, independently of how it is drawn.

A declaration that an element is driven by, or writes to, a building entity through a named channel.

The aspect of an element that a bound value drives: its displayed value, its state, its fill, its rotation, and so on. A closed vocabulary (13.6.1).

The protocol-specific information needed to reach a point in a live system. Distinct from a presentation binding.

A single artifact conveying a portable understanding of one or more buildings, with a manifest that declares and verifies its contents.

Building, in a receiving system, a portable understanding semantically equivalent to the one in a package, without assistance from the system that produced it.

The relation holding between two models when, after canonicalization, there is a mapping between their entities preserving identity, type, normative properties, and the labeled relationship graph. Defined operationally in 17.5.

The mandatory statement, in the manifest, of which substrate domains the package carries in full, in part, or not at all, and why.

The capability, carried by a write binding, to command plant from a graphic.