Prepare the Equipment Information Needed for a Compatibility Decision
- 01 · Requirement
Visitors do not know which technical facts are needed to judge compatibility.
- 02 · Failure risk
Without exact device and use-case facts, a compatibility answer becomes a guess that shifts risk into design, testing, or field startup.
- 03 · Technical method
A local worksheet that records a protocol/device use case and produces the evidence needed for lab or engineering review.
- 04 · Acceptance evidence
Test the exact device, version, transport, mappings, commands, timing, failure behavior, and security boundary for the stated use case.
Technical detail begins here, with system names, authority, safety, evidence, and operating limits kept in view.
Use this standard to guide a decision, then confirm the project-specific facts and evidence before relying on a claim.
Technical boundary: Published decision standard, not project history, certification, partnership, or customer-result evidence.
Illustrative closeout—not a customer result, case study, warranty, or measured savings claim.
Network, mapping, command, failure, and evidence details matter more than a protocol name alone.
Make the supported result and its limits reviewable
Test the exact device, version, transport, mappings, commands, timing, failure behavior, and security boundary for the stated use case.
- Known or suspected protocol
- Device model and version
- Required points, trends, alarms, and command authority
Representative commissioning detail—not a building automation system (BAS) test record or result.
Technical boundary
Published decision standard, not project history, certification, partnership, or customer-result evidence.
Documents and records that support field execution
Use the outputs for coordination, commissioning, review, and later troubleshooting.
Source and destination definition
Versioned point, transport, and authority scope
Test result, limits, failure behavior, and support status
Define, test, record, and close the technical gap
Use this standard to guide a decision, then confirm the project-specific facts and evidence before relying on a claim.
Capture requirements
Record the exact device, version, transport, mappings, and required functions.
Test the stated use case
Define data, command, timing, failure, cybersecurity, and ownership boundaries.
Publish the supported result
Test the stated use case and publish the supported result with limits and review date.
Reduce rework and make acceptance easier to defend
Requirements, interfaces, tests, exceptions, and handover stay connected to the decision.
Reduce back-and-forth and expose missing model, firmware, transport, mapping, and authority details.
Versioned compatibility testing confirms the exact equipment and software combination before support is promised.
Documented read, write, timing, and failure limits protect the building from unsafe integration assumptions.
Test the exact equipment before promising integration
A protocol name is not a compatibility result. The record must bind the device, version, transport, point meaning, write authority, failure behavior, security boundary, and named evidence.
Truth boundary: Illustrative record only. It does not claim support for a manufacturer, model, firmware version, protocol combination, or control function.
- 01 · Identify
Freeze the exact combination
Manufacturer, model, firmware, software, gateway, transport, and network role are recorded together.
- 02 · Define
Describe the required behavior
Points, units, timing, alarms, trends, commands, priorities, fallback, and authority are made explicit.
- 03 · Evaluate
Run a bounded test
The test plan states the environment, tools, reviewer, acceptance criteria, safety boundary, and rollback.
- 04 · Publish
Version the result and limits
Status, test date, evidence, exceptions, lifecycle, and retest triggers travel with the decision.
Compatibility evidence request
Record the exact source, destination, version, points, and authority needed for a defensible test request.
Related protocols & compatibility
Request a Structured Compatibility Test for Specific Equipment
Prepare a Test Request
Know What Can Connect Before You Commit to Integration
Check Compatibility
Understand What BACnet Support Does—and Does Not—Guarantee
Prepare a BACnet Check
Understand What BACnet Secure Connect Requires
Review BACnet/SC Requirements