Section 72 of 101
71. Command Arbitration
Stable section ID: S05-CON-006-SECTION-72 · 35 content blocks
Command Arbitration resolves competing commands directed toward the same component, resource, or building function.
Every command shall include:
Command ID;
issuing identity;
target;
requested action;
priority;
authority;
operating mode;
issue time;
validity period;
preconditions;
expected result;
acknowledgment requirement.
Arbitration shall consider:
physical safety constraints;
certified local protection;
emergency commands;
regulatory requirements;
active interlocks;
authorized manual overrides;
operational control;
automated optimization;
occupant preferences;
advisory recommendations.
Higher priority shall not by itself permit a command that violates safety, configuration, capability, or Interface limits.
Conflicting commands shall produce an explicit arbitration decision identifying:
accepted command;
rejected or deferred commands;
applicable rule;
resulting state;
- required notification.
- Commands with expired validity shall not be executed.
The BIOS shall distinguish between command acceptance and successful execution. Physical confirmation shall be required where appropriate.
Rapidly alternating commands shall be controlled through timing rules, minimum dwell periods, hysteresis, rate limits, or local controller logic to prevent instability and equipment damage.