Point Dictionary: SYS

System-level / cross-equipment point dictionary. The sensor-health rules (SYS-0005/SYS-0009/SYS-0010) bind ROLE POINTS, not canonical equipment points — the documented exception to the canonical-name convention (SCHEMA.md points contract; decided 2026-08-17, internal sensor-health design note §3). The reference’s own SYS-0005 card does the same (‘varies by application’). The host’s instance configuration records which real point each role is bound to; that same record drives the adjudicates NO_EVAL fan-out. Role entries carry brick/s223 null — the semantics belong to whatever the role is bound to. The reference ch.16 waste/schedule rules (SYS-0001..SYS-0004, SYS-0007, SYS-0008) bind CANONICAL cross-equipment points (grounded below); SYS-0006 binds the physical_sensor/virtual_value role pair. Points that also exist in equipment dictionaries remain duplicated here when their ownership is contextual (oat, sf_status, rht_vlv_cmd). occ_sensor is a compatibility alias to the canonical zone point.

sensor_value

ROLE: the single sensor under adjudication (flatline/spike rules)

Role point: bound per instance to any real-valued sensor (temperature, pressure, flow…). Thresholds on the rules that consume it are in the BOUND point’s units and MUST be retuned per binding — a 0.1 degC flatline band is nonsense for a Pa sensor. Binding record doubles as the adjudicates target.

sensor_value_a

ROLE: primary sensor of a redundancy pair (SYS-0005)

Role point; the reference’s own required-points table for SYS-0005 lists sensor_a/sensor_b with ‘varies by application’. Pair members must share quantity kind and units at binding.

sensor_value_b

ROLE: reference sensor of a redundancy pair (SYS-0005)

Role point; see sensor_value_a. The pair rule’s verdict is ambiguous — it cannot name which member drifted.

equip_active

ROLE: owning equipment is running/active (gates flatline evaluation)

Role point: bound to the owning equipment’s run/enable status (sf_status, pump_status, boiler_status…). A flat signal on idle equipment is normal; flatline only accuses the sensor while the process should be moving.

physical_sensor

ROLE: the physical sensor cross-checked against a virtual-sensor prediction (SYS-0006)

Role point; the reference’s required-points table lists physical_sensor plus 3+ correlated features. Thresholds (bias/noise) are in the BOUND point’s units — the reference’s defaults are for temperature bindings and MUST be retuned for other quantity kinds. Binding record doubles as the adjudicates target.

virtual_value

ROLE: host-computed virtual-sensor prediction of the bound physical_sensor (SYS-0006)

Host-derived role point: the host evaluates a regression model (reference: Ridge trained over a learning period on 3+ correlated features) each tick and exposes the prediction as this point. The graph computes only the residual statistics — model training/inference is host-side, per the host-fitted baseline convention (SCHEMA.md; HP-0001/VAV-0001 precedent).

chw_flow

Chilled water plant supply flow

• 223P: Sensor observes QuantifiableObservableProperty on the CHW supply segment
• QUDT unit: L-PER-SEC

hw_flow

Hot water plant supply flow

• 223P: Sensor observes QuantifiableObservableProperty on the HW supply segment
• QUDT unit: L-PER-SEC

ahu_clg_vlv_max

Maximum cooling-coil valve command across all AHUs served by the CHW plant

• 223P: host-derived aggregate; no single physical point
• QUDT unit: PERCENT

Host computes max(clg_vlv_cmd) over the served-AHU set each tick (chw_valve_max precedent, points/chw.points.json). The reference’s all-valves-closed condition is equivalently max(valves) below the closed threshold — one aggregate point instead of a variable-width vector, which the graph cannot express.

ahu_htg_vlv_max

Maximum heating-coil valve command across all AHUs/zones served by the HW plant

• 223P: host-derived aggregate; no single physical point
• QUDT unit: PERCENT

HW mirror of ahu_clg_vlv_max; include reheat valves in the served set where the HW plant feeds zone reheat.

occ_scheduled

TRUE while current time falls inside the occupied schedule (host-evaluated)

The reference’s in_occupied_schedule(current_time, occ_schedule) is a calendar function; the graph has no clock, so the host evaluates the schedule and exposes the boolean. Same treatment as AHU-0018’s occupancy gate.

lighting_status

Lighting circuit on/off status

• 223P: EnumeratedObservableProperty on the lighting Equipment via hasProperty

Brick 1.4.4 has no lighting-specific run status class; On_Off_Status on the lighting equipment/zone is the closest grounding.

ef_status

Exhaust fan run status

• 223P: EnumeratedObservableProperty on the Exhaust Fan via hasProperty

Brick 1.4.4 has no exhaust-specific fan status point class (only Exhaust_Fan equipment + enable/disable commands); Fan_On_Off_Status on the Exhaust_Fan equipment is the grounding, matching sf_status convention.

sf_status

Supply fan run status of the paired AHU (SYS-0008)

• 223P: EnumeratedObservableProperty on the Fan via hasProperty

Duplicate of points/ahu.points.json sf_status — SYS-0008 is a cross-equipment rule instantiated per exhaust-fan/AHU pair.

demand_override_active

TRUE while a demand-based exhaust override (e.g. kitchen hood, restroom call) legitimately holds the fan on

BAS override flag; no Brick 1.4.4 point class models an override status. Host exposes the controller’s override/demand flag directly.

rht_vlv_cmd

Zone reheat valve command (SYS-0007, instantiated per zone)

• 223P: QuantifiableActuatableProperty on the reheat Valve via hasProperty; Actuator actuates the valve
• QUDT unit: PERCENT

Duplicate of points/vav.points.json rht_vlv_cmd — the reference files SYS-0007 under SYS but scopes it to VAV/FCU zones; bind per zone.

oat

Outdoor air temperature

• 223P: Sensor observes QuantifiableObservableProperty at the outdoor-air intake
• QUDT unit: DEG_C

Compatibility aliases

• occ_sensor → points/zone.points.json#occ_sensor