Start here
What should a building automation troubleshooting packet contain?
Use one incident record connecting the affected asset, source timestamps, command, feedback and data quality to an independent observation and the approved sequence. Keep competing explanations separate from confirmed findings. Assign missing evidence and record verification after any authorized correction; an alarm disappearing is not the same as the original function being restored.
Give the incident a clear boundary
Name the equipment tag, served area, complaint and relevant period. Record the effect in ordinary language: a room did not cool during its occupied period, for example. Include the existing work order or incident reference so reports from the controls provider and mechanical team can be linked.
Begin with copies of available exports, event notes and the approved sequence revision. Record timestamp conventions and known data gaps; the separate trend-log guide explains clock alignment and graph interpretation in more detail. Here the goal is a handoff packet that lets each party answer the same event question.
Separate commands, feedback and independent observations
A command is what the control system requests. Feedback may report actuator position, equipment status or another variable, but its label does not prove which physical quantity it measures. Ask the point owner for the definition, source, units, sample behavior and quality indication. A value can remain on a graphic after its source stops updating.
An independent observation is a separate record relevant to the function, made by an appropriately qualified person or a documented measurement source. Keep the observation and its limits intact. “Actuator visibly moved” is not the same finding as “water flow and heat transfer were verified.”
DOE FEMP’s controls-assessment discussion calls for checking design occupancy, controls and sensor calibration when ventilation behavior is questionable. That supports treating sensing and equipment response as separate evidence questions. The valve incident below is our own hypothetical record structure, not a DOE troubleshooting procedure.
References: [1]
Worked incident packet: commanded-open cooling valve
Fictional incident IC-07 concerns AHU-X during a warm-room complaint. At the example source time 14:10, the BMS export shows a 100% open command. A displayed feedback point stays at 0%, and supply-air temperature has not fallen. There is no verified valve-position or water-side assessment yet. These observations do not establish which component failed.
| Packet field | Recorded evidence | What it supports | What remains open |
|---|---|---|---|
| Time / source | BMS export at 14:10; operator note at 14:12 | An event window to compare | Timestamp convention and data alignment confirmed by source owner |
| Command | Valve command 100% | The controller requested opening | Receipt and physical response |
| Feedback / quality | Displayed 0%; quality flag absent | A disagreement needing definition | Position source, freshness, scaling and point mapping |
| Independent observation | Warm-room complaint; supply air unchanged | Requested cooling effect not evident in these records | Qualified physical and water-side findings |
| Sequence | Cooling sequence revision C attached | A stated intended behavior to review | Whether all enabling conditions were met |
Preserve three explanations until they can be distinguished
The packet should contain a question, an evidence owner and a way to resolve each plausible explanation. Avoid converting the first plausible explanation into the work order’s confirmed cause. More than one defect can also be present.
| Possible explanation | Why it remains plausible | Evidence to request | Responsible scope |
|---|---|---|---|
| Actuator or mechanical movement issue | Command alone does not establish movement | Qualified observation of command receipt and physical response | Controls and mechanical responsibilities defined together |
| Feedback or mapping issue | Displayed 0% may be stale or represent another quantity | Point definition, quality and comparison with verified physical state | Authorized controls provider |
| Water-side condition | An open valve alone does not establish useful cooling | Relevant supply/return and water-side findings under the same condition | Qualified mechanical assessment |
Record the authorized correction and the result separately
Continue the fictional example: suppose an authorized provider later establishes that the displayed feedback point was mapped incorrectly and issues a dated correction record. That explains the misleading display. It does not automatically explain the warm room, so the incident cannot close solely because the graphic now looks consistent.
Request the follow-up record under a relevant comparable operating condition. It should identify the changed point or component, the sequence revision, the observed equipment response and whether the original complaint remains. If the room remains warm, retain the water-side and other unresolved questions. If no suitable verification condition was available, record that limit and the planned responsible follow-up.
This packet does not ask staff to force outputs, bypass interlocks, share passwords or reproduce a fault. Access, operating tests and changes remain within the site’s authorized process. Collect available records first and agree the scope of any additional investigation.
Send a small packet with an evidence index
Use a short incident summary followed by source files, point definitions, sequence reference, explanation matrix and correction-verification record. Give each attachment a clear name and date. A screenshot can support the summary, but keep raw values when available so another reviewer can check the interpretation.
In an occupied multi-tenant building, identify the property contact, the controls provider and the party responsible for connected plant conditions. That assignment prevents a room-level request from silently assuming access to shared systems. Share only relevant technical records through an agreed channel; credentials and unrelated tenant or network details do not belong in the packet.
A complete packet can still end with an unresolved diagnosis. Its value is that the next investigation has a defined question and an owner, instead of another general instruction to check the BMS.
Put this guide to work
BMS incident evidence packet
Use one register per incident. Enter references to existing records; this worksheet does not authorize access, tests or controls changes.
Open each item to add your notes, then download the CSV to keep a copy. This tool does not save or submit your entries; do not rely on your browser restoring them.
Incident ID, asset and served area
Complaint and operating mode
Command point and source definition
Feedback point, units and quality
Independent physical observation
Relevant supply / return or water-side evidence
Approved sequence and enabling conditions
Actuator / mechanical explanation
Feedback / mapping explanation
Water-side explanation
Authorized correction and revision
Verification of original function / open items
Continue with a related decision
Questions & answers
Does an open command prove the valve is open?
No. It records a request. Establish what feedback represents and obtain appropriate independent evidence before attributing the fault.
Can the incident close when the alarm clears?
Only if the required evidence supports closure. An alarm can clear after a reporting change while the original mechanical concern remains.
Should staff override the valve to make the packet complete?
No. Use existing records and observations. Any additional test or change needs the site’s authorized plan and qualified responsible team.
Sources & technical references
- DOE FEMP: Energy Efficiency and Indoor Environmental Quality Assessment Guide, February 2024
Appendix F controls and sensor assessment discussion, PDF pages 39–40, read November 16, 2026. Supports the distinction between sensing and intended operation; IC-07 is an original hypothetical example.
NYC & Northern New Jersey
Start with the event and the missing evidence
Share the equipment tag, incident summary and available records with Airplex Mechanical to define the mechanical investigation and controls coordination needed.
Discuss the controls incidentCall (347) 627-7146