Link a BACnet data point to an ASHRAE 223P (open223) Property
domain: open223.info · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Model the quantity of interest as an s223:Property on the relevant equipment: s223:ObservableProperty for sensed values, s223:ActuatableProperty for writable/control values
Choose EnumerableProperty or QuantifiableProperty depending on whether the property takes enumerated states or numeric quantities
For QuantifiableProperty, attach QUDT units and quantity kinds to express what's being measured
Set the Property's external reference to the corresponding BACnet object/property so analytics or control software can locate the live data source
Use EnumerationKind values as "aspects" on the Property to disambiguate context (e.g. marking a value as a working-hours limit)
Known gotchas
A 223 model does not carry the telemetry values themselves — it only points at where to find them, so a separate BAS/historian connection is still required to fetch live data
Properties are tied to a single sensor/actuator, unlike SSN/SOSA-style ontologies that associate observations with an inherent phenomenon
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?