General engineering
AuraScore 81/100

Smart Building BMS Automation Integration Brief

Establish protocol mapping, telemetry gateways, and failover parameters for integrating commercial HVAC into modern BMS platforms.

Deploy this template when modernizing commercial real estate facility operations through automated central building management protocols. It guides systems engineers in defining gateway architectures, register mappings, and safety interlocks.

Template

Role: Senior Automation and Controls Engineer specializing in building management systems (BMS) and MEP integration.

Context

  • Facility identifier: {{facility_name}}
  • Mechanical plant topology: {{hvac_architecture}}
  • Target BMS environment: {{bms_platform}}
  • Target energy framework: {{energy_compliance_standard}}
  • Legacy control hardware: {{legacy_hardware_stack}}
  • Maximum electrical demand: {{peak_load_threshold}}

Task

Draft a technical automation integration brief that specifies communication bridge architectures, telemetry register mappings, automated load shedding routines, and safety overrides for {{facility_name}}.

Method

  1. Review the communication interfaces of {{legacy_hardware_stack}} to identify field bus compatibility with {{bms_platform}}.
  2. Detail edge gateway hardware requirements to bridge legacy field buses to standard IP-based building automation protocols.
  3. Define the read/write point register map for primary chillers, air handling units, and variable air volume boxes in {{hvac_architecture}}.
  4. Design demand-limiting algorithms to stage equipment shutoffs before approaching {{peak_load_threshold}}.
  5. Align control loops and temperature deadbands with the operational efficiency mandates of {{energy_compliance_standard}}.
  6. Specify hardware-level safety interlocks that override software commands during freeze-stat or smoke alarm events.
  7. Establish failover states for all modulating actuators in the event of BMS communication loss.

Constraints

  • MUST specify fail-safe hardware states (Normally Open vs Normally Closed) for all critical valves.
  • MUST NOT allow software-only commands to override physical life-safety and freeze-protection interlocks.
  • All register mappings must specify exact data types (e.g., 16-bit unsigned integer, IEEE 754 float).
  • Gateway latency must be constrained to sub-500ms response times for critical control loops.

Output format

  • Section 1: Architecture Overview (max 120 words defining topology and gateway specs)
  • Section 2: Point Register & Protocol Mapping (markdown table: Point Name, Legacy Register, BMS Point, Type, Access Level)
  • Section 3: Peak Load Shedding & Efficiency Strategy (concise operational logic rules, 3-5 rules)
  • Section 4: Safety Interlocks & Fail-Safe Matrix (table: Trigger Event, Controlled Equipment, Safe State) Total word count must not exceed 600 words.

Self-review

  • Ensure all legacy controllers named in {{legacy_hardware_stack}} have explicit protocol translation paths.
  • Validate that load shedding rules prevent exceeding {{peak_load_threshold}}.
  • Check that control strategies explicitly satisfy {{energy_compliance_standard}} requirements.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

developers
developers-general
real-estate-construction
bms
mep-engineering
automation