BACnet/IP Level 1 PICS Addendum

Protocol Implementation Conformance Statement (PICS) for the MHT Technologies Inspextor AIDA Controller BACnet/IP server at Integration Level 1.

Use this document in municipal and commercial submittal packages to confirm which BACnet objects are writable from the BMS and which are read-only. It satisfies requests such as Oakland County–style PICS validation for command/control capability, not monitoring-only integration.

:::info Live PICS after commissioning On a commissioned controller with the BACnet module enabled, export a project-specific PICS with actual object instances and cluster names:

# Authenticated controller API (after login)
curl -s "https://{controller-host}/api/v1/bacnet/pics.md" \
  -H "Authorization: Bearer $ACCESS_TOKEN"

JSON inventory: GET /api/v1/bacnet/inventory · JSON PICS: GET /api/v1/bacnet/pics :::

Project information (complete before submittal)

Field	Value
Project name	[Owner / facility name]
Controller hostname / IP	[e.g. 192.168.10.50]
BACnet device instance	[e.g. 389001 — unique on Owner network]
BACnet device name	[e.g. AIDA-CTRL-01]
Integration level	1
Controller firmware version	[from /api/v1/bacnet/status or About screen]
Commissioning date	[date]
BMS integrator	[company / contact]

Product identification

Property	Value
Vendor name	MHT Technologies
Vendor identifier	[BACnet vendor ID — see controller export]
Model name	Inspextor AIDA Controller
Application software version	[controller APP_VERSION]
Protocol revision	BACnet/IP (ISO 16484-5)
Data link	BACnet/IP, UDP port 47808

BACnet services

Supported (Level 1)

Service	Supported
Who-Is	Yes
I-Am	Yes
ReadProperty	Yes
WriteProperty	Yes (writable object types only)

Not supported (Level 1)

Service	Supported	Notes
SubscribeCOV	No	BMS must poll ReadProperty
ReadPropertyMultiple	No	Phase 2
COV Notification	No	Requires Level 2

Object types summary

Writable object types (BMS WriteProperty permitted)

BACnet object type	Role	Write action
binary-output	Zone power ({cluster}-PWR)	Dispatch on / off INX event
analog-output	Zone dim ({cluster}-DIM)	Dispatch fl event, 0–100 %
analog-output	Zone CCT ({cluster}-CCT)	Dispatch attune event, Kelvin

CCT object is exported only when the cluster contains tunable-white fixtures. Otherwise omitted or out-of-service=true.

Read-only object types (BMS ReadProperty only)

BACnet object type	Role	Data source
binary-input	Occupancy ({cluster}-OCC)	Last mot / vac / on / off INX event
analog-input	Illuminance ({cluster}-LUX)	Lux sentype INX events
analog-input	Temperature ({cluster}-TEMP)	Temp sentype INX events
analog-input	Sound ({cluster}-SND)	Sound sentype INX events

Sensor objects are exported only when sensors of that type exist in the cluster. Otherwise omitted or out-of-service=true.

Read / write matrix (Level 1)

Basis for municipal monitoring and control validation. Per-cluster instances depend on legacy cluster ID × instance block size (default block 100). Replace the example table below with the live export from /api/v1/bacnet/pics.md at commissioning.

Cluster	Object name	BACnet type	Instance (example)	BMS read	BMS write
Lobby	Lobby-PWR	binary-output	101	Yes	Yes
Lobby	Lobby-DIM	analog-output	102	Yes	Yes
Lobby	Lobby-CCT	analog-output	103	Yes¹	Yes
Lobby	Lobby-OCC	binary-input	110	Yes	No
Lobby	Lobby-LUX	analog-input	111	Yes²	No
Lobby	Lobby-TEMP	analog-input	113	Yes²	No
Lobby	Lobby-SND	analog-input	115	Yes²	No

¹ Omitted if no tunable-white fixtures.
² Omitted if no sensor of that type in cluster.

Explicitly excluded at Level 1

The following object types are not exported at Integration Level 1:

• multi-state-output — scene ({cluster}-SCN)
• analog-input — CO₂ ({cluster}-CO2), humidity ({cluster}-RH)
• multi-state-value — zone status ({cluster}-STS)
• binary-value — BMS override ({cluster}-OVR), demand response ({cluster}-DR)

Reliability and read freshness statement

Include this language in the Owner submittal:

Integration Level 1 uses controller-native state in device_states, aggregated per cluster at ReadProperty time. Reads are last-known values, not a certified live sensor stream:

• Dim / CCT / power readback: Health-check actuator poll (default interval 300 s) plus command echo after successful WriteProperty.
• Occupancy: Last occupancy-related INX event (mot, vac, on, off) for the cluster.
• Lux / temperature / sound: INX sentype events when sensors report.
• Refresh: BACnet presentValue updated from device_states on state_refresh_sec interval (default 30 s).
• Offline devices: reliability=no-confidence when data exceeds staleness threshold.
• SubscribeCOV: Not supported. BMS must poll.

Level 2 with Realtime Controller is required for SubscribeCOV, CO₂/humidity BACnet points, BMS override, demand-response BACnet points, and full municipal commissioning per project specification §3.6 where CO₂ verification at the BMS is required.

Conformance statement

The Inspextor AIDA Controller BACnet/IP server at Integration Level 1 provides:

1. Command and control — BMS WriteProperty on zone power, dim, and CCT (where applicable).
2. Supervisory monitoring — BMS ReadProperty on occupancy and environmental sensors (where installed).
3. Single BACnet device per controller — cluster-level aggregation of PoE nodes.

PoE field devices communicate via CoAP/MQTT to the controller; they do not implement BACnet natively.

Signature block (optional)

Role	Name	Signature	Date
MHT Technologies representative
BMS integrator
Owner / commissioning agent

Related documentation

• Municipal BMS Integration Brief — FAQ and Level 1 vs Level 2 selection
• BACnet/IP Server — Configuration and architecture
• BACnet Commissioning Checklist — Acceptance testing

---

Vendor: MHT Technologies · Product: Inspextor AIDA Controller 2.0 · PICS template version: 1.0