Cart
How documenting control settings can simplify troubleshooting, protect system performance, and make life easier for technicians.
A building automation system can be working exactly as intended when the installation is complete. The controllers are programmed, setpoints are established, equipment is operating, and the commissioning team has verified performance. Everything is where it should be.
Then, somewhere along the way, something changes.
Maybe a technician adjusts a cooling setpoint to troubleshoot a comfort complaint. Maybe a balancing contractor modifies settings during testing. Or perhaps someone makes a temporary adjustment that never gets changed back.
Months later, another technician arrives to investigate a problem. The equipment is running, the controllers are communicating, and nothing immediately appears broken. But the building isn’t performing the way it did when the job was completed.
The question becomes surprisingly difficult to answer: What changed?
The Problem with Undocumented Changes
Building automation systems aren’t static. They’re adjusted, maintained, expanded, and occasionally modified to accommodate changing building needs.
That’s normal, and often necessary. The challenge comes when those adjustments aren’t documented.
Consider a building with dozens of variable air volume (VAV) controllers. During commissioning, technicians establish airflow settings, temperature setpoints, and other operating parameters. Those settings represent the intended operating conditions at that point in the building’s life.
Now imagine that several settings are changed during testing and balancing. Some adjustments are intentional and should remain. Others are temporary and should be reversed.
If nobody records which settings changed, the next technician may have no reliable way to distinguish the two.
The problem isn’t necessarily that someone made an adjustment. It’s that the original settings—and the reasons for changing them—may no longer be readily available.
Over time, that uncertainty can complicate troubleshooting and make it harder to maintain consistent system performance.
A Baseline Gives Technicians a Starting Point
One way to address this challenge is to establish a baseline: a documented record of selected controller settings at a known point in time.
A baseline doesn’t prevent changes. Instead, it provides a reference for evaluating them.
When a technician returns to investigate an issue, the question no longer has to be, ‘What do I think this setting used to be?’
It can become, ‘How does this setting compare with the documented baseline?’
That distinction is important. Rather than searching through controllers and relying on memory, technicians can identify differences and begin determining whether those differences are related to the problem.
A baseline is particularly useful at key project milestones, such as after initial configuration, before testing and balancing, or before turning a completed system over to the building owner.
It can also provide a valuable reference during future service visits.
Finding the Differences Without Checking Every Point
During a recent KMC Controls Stuck on a Bucket webinar, technical trainer Billy Gayton demonstrated how the Audit tool in KMC Connect™ supports this process.
The Audit tool is supported exclusively on compatible KMC Conquest®, KMC AppStat™, and SimplyVAV™ controllers that use KMC Controls factory applications or custom applications developed through the Custom Application Wizard. On supported devices, technicians can evaluate selected settings and store those results as a baseline.
When the technician returns later, another evaluation compares the current settings with the stored values and identifies differences.
To demonstrate, Billy established a baseline for a group of controllers and then deliberately changed an occupied cooling setpoint from 74°F to 72°F.
When he ran the Audit tool again, it identified the difference. Because the application used a setpoint differential, the associated heating setting also changed, and the audit displayed those related differences.
This is where the value becomes clear.
A technician investigating a comfort issue doesn’t necessarily have to open every object individually and manually compare its properties with old notes or project documentation. The Audit tool can highlight differences in the settings it evaluates, giving the technician a more focused place to begin.
That doesn’t automatically identify the cause of a comfort problem, but it can eliminate some of the guesswork involved in finding it.
Not Every Change Is a Mistake
Of course, identifying a difference is only part of the process.
Suppose a facility manager approves a new temperature setpoint to accommodate changes in how a space is used. The setting is different from the original baseline, but that doesn’t mean it’s wrong.
In this case, the technician may want to preserve the adjustment and update the baseline to reflect the approved operating conditions.
Alternatively, if a temporary adjustment was never reversed, the technician may need to restore the original value.
KMC Connect’s Audit tool supports both approaches. Technicians can store selected changes as the new baseline or restore selected settings to their previously stored values.
This makes the baseline more than a historical record. It becomes a reference that can evolve alongside the building.
The important distinction is that changes should be evaluated before they’re accepted or reversed. A stored baseline tells technicians what was different; understanding whether the change was appropriate still requires professional judgment.
Why This Matters During Commissioning and Service
The period surrounding commissioning and testing can be particularly challenging because multiple people may interact with the same system.
A controls contractor configures the equipment. A balancing contractor tests airflow. A commissioning agent verifies sequences. Building operators may request additional adjustments.
Each person has a legitimate responsibility, but those responsibilities can involve changing controller settings.
During the webinar, Harold Collier, Chief Technology Officer at EdgePoint Automation, discussed how easily settings can be left in an unintended state after commissioning activities.
He also pointed to the practical value of restoring settings across multiple controllers without manually opening and adjusting every affected object.
Billy noted that some technicians establish an audit baseline before VAV balancing, then evaluate the controllers again afterward to see what changed.
That approach can help make the handoff between project activities more transparent.
Instead of assuming every setting has been returned to its intended value, technicians have a way to check.
Building a Better Change-Management Habit
A useful baseline is only as good as the process surrounding it. Capturing settings once and never reviewing them again limits its value.
For controls technicians and facility teams, a practical approach might include:
-
- Establish a baseline at a meaningful milestone. Capture the selected settings once the system has been configured and verified for that stage of the project.
- Evaluate settings after major testing or adjustments. Use comparisons to identify what changed during balancing, commissioning, or troubleshooting.
- Review differences before taking action. Determine whether changes were intentional, approved, temporary, or unexpected.
- Update the baseline when appropriate. If an adjustment represents a new approved operating condition, preserve it as part of the reference.
- Keep project documentation accessible. A baseline is most useful when technicians can also consult the intended sequence of operations, commissioning records, and other relevant project information.
These habits won’t eliminate every troubleshooting challenge. They can, however, make it easier to understand how the system has changed and reduce the time spent reconstructing its history.
Better Troubleshooting Starts with Better Information
Building automation systems are designed to respond to changing conditions. Their settings will evolve as buildings are commissioned, occupied, maintained, and modified.
The goal isn’t to prevent every change. It’s to make those changes easier to understand.
With a documented baseline, technicians have a clearer reference for evaluating unexpected behavior, confirming approved adjustments, and restoring settings when necessary.
Tools such as the Audit feature in KMC Connect help make that process more manageable, particularly when working across multiple controllers.
And sometimes, the difference between a frustrating service call and a productive one is simply knowing where to start.
For more practical building automation tips, explore KMC Controls’ Stuck on a Bucket webinar series and check out October’s episode below: