Smart Building BMS Protocol Gateway Matrix
Structure and score communication gateway options for unifying legacy and modern building management systems.
Use this prompt during commercial building retrofits or handovers to evaluate protocol conversion gateways between legacy physical plant equipment and modern real estate IoT platforms.
Role: Senior Building Automation Systems Engineer with deep domain expertise in industrial telemetry and facility protocol normalization.
Context
- Real Estate Asset Type: {{asset_class}}
- Legacy Field Subsystems: {{legacy_subsystems}}
- Destination Telemetry Target: {{cloud_platform_target}}
- Cyber Protection Standard: {{cybersecurity_framework}}
- On-Site Compute Constraint: {{edge_compute_capability}}
- Retrofit Go-Live Window: {{commissioning_timeline}}
Task
Deliver a protocol gateway conversion matrix that systematically evaluates integration mechanisms to bridge {{legacy_subsystems}} to {{cloud_platform_target}} within the structural constraints of {{asset_class}}.
Method
- Enumerate field-level communication protocols present in {{legacy_subsystems}} (e.g., BACnet MS/TP, Modbus RTU, LonWorks, proprietary serial).
- Define ingestion interfaces, schema standards, and transport mechanisms required by {{cloud_platform_target}} (e.g., MQTT over TLS, OPC UA, HTTPS REST).
- Establish edge-processing requirements for protocol translation relative to {{edge_compute_capability}}.
- Profile four gateway architectural approaches: Hardware embedded converters, Industrial PC edge containers, Direct cloud connectors, and Virtualized PLC software bridges.
- Screen each approach against {{cybersecurity_framework}} requirements (e.g., network segmentation, TLS 1.3, encrypted local keystores).
- Evaluate schedule feasibility against {{commissioning_timeline}} to highlight quick-win vs complex deployment pathways.
- Construct a standardized decision matrix ranking hardware and software bridge options across key operational metrics.
Constraints
- MUST evaluate at least three field protocol conversion approaches.
- MUST NOT allow unencrypted plaintext protocol transmission beyond the local field subnet.
- Matrix scores must be justified with technical reasoning in adjacent summary notes.
- Edge compute constraints from {{edge_compute_capability}} must govern the hardware tier selections.
Output format
- Technical Scope (1 paragraph defining protocol boundaries)
- Gateway Architecture Matrix (Markdown table with columns: Gateway Approach, Supported Legacy Protocols, Target Protocol Output, Edge Hardware Requirement, Security Compliance, Commissioning Effort, Overall Score 1-5)
- Hardening & Deployment Roadmap (Bullet list of 4 chronological deployment steps)
Self-review
- Ensure every legacy protocol mentioned in {{legacy_subsystems}} is represented in the matrix.
- Verify that the security evaluation directly addresses {{cybersecurity_framework}}.
- Check that the proposed gateway approaches do not exceed {{edge_compute_capability}}.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.