%20(1920%20x%201080%20px)%20(8).png)
Episode Description:
In this episode of the Smart Buildings Academy Podcast, we tackle one of the most common sources of friction on a controls project: coordination between electrical, mechanical, and controls teams.
As a building automation professional, you often sit directly between multiple trades. When responsibilities are unclear, a missing connection or misunderstood scope can quickly become a schedule problem, a budget problem, and eventually a relationship problem.
This episode explores how you can approach those coordination points earlier and gain better visibility into the interfaces that affect your work. You'll hear how to identify potential gaps before they reach the field and how to navigate conflicts without damaging the working relationships you'll need on this project and the next one.
Topics Covered
- Why electrical, mechanical, and controls handoffs break down
- Where Division 23 and Division 26 responsibilities can create scope gaps
- How furnish, install, and terminate responsibilities affect controls projects
- What to consider when coordinating controls interfaces and field dependencies
- How to approach jobsite conflicts while protecting schedules and relationships
When controls sits in the middle of the project, you have a unique view of how the building fits together. This episode will help you think differently about using that position to keep projects moving.
Click here to download or listen to this episode now.Podcast Video
How Better Electrical and Mechanical Coordination Protects Controls Projects
A controls technician arrives on site, ready to terminate an air handler. The unit is set, the ductwork is complete, and the control panel is ready.
Then the panel is opened.
There is no power. No conduit. No whip. Nothing.
The electrical foreman says power to the control panel was not included in the electrical scope. The controls team believes it was. Work stops while everyone starts reviewing drawings, specifications, and scope letters.
This situation is common because building automation sits at the intersection of multiple trades. Controls contractors depend on electrical contractors, mechanical contractors, equipment vendors, engineers, and general contractors to complete work that directly affects controls installation and commissioning.
That position creates risk, but it also gives control professionals an important advantage. Few people on a project have the same visibility into how individual building systems connect.
Using that visibility effectively starts with better coordination.
Why Controls Coordination Breaks Down
Many coordination problems are not caused by someone failing to do their job. They happen because multiple companies are working from different documents, assumptions, and interpretations of scope.
A controls contractor may assume an electrical contractor is responsible for providing power to a control panel. The electrical contractor may interpret the contract documents differently. Both teams can believe their interpretation is correct.
The same problem appears with mechanical equipment.
Who provides a sensor?
Who installs it?
Who provides the wiring?
Who terminates the wiring?
Who installs an actuator?
Who provides an interlock?
Who is responsible for the final connection to packaged equipment?
These questions can look minor during preconstruction. In the field, each one can become a dependency that prevents another task from being completed.
The later the team discovers the discrepancy, the more expensive it becomes to resolve.
Understanding the Division 23 and Division 26 Interface
Controls work frequently crosses the boundary between Division 23 and Division 26.
Division 23 generally covers heating, ventilation, air conditioning, and related controls requirements. Division 26 generally covers electrical systems. A building automation system may depend heavily on work performed under both divisions.
The specification divisions themselves do not eliminate ambiguity.
A controls contractor still needs to understand exactly where responsibility changes from one contractor to another. Drawings, specifications, equipment schedules, sequences, scope letters, submittals, and contract requirements may all contain pieces of that answer.
Problems develop when teams rely on assumptions instead of identifying those boundaries before installation begins.
For controls professionals, the goal is not simply to know what is included in the controls scope. It is to understand the interfaces surrounding that scope.
Ask Three Questions at Every Interface
One useful way to examine an interface is to separate responsibility into three questions:
Who furnishes it?
Who installs it?
Who terminates it?
Those responsibilities are not always assigned to the same contractor.
A controls contractor might furnish a device while another trade physically installs it. An electrical contractor might install wiring while the controls contractor completes the termination. A mechanical contractor might install equipment that contains factory controls requiring connections to the building automation system.
If the project team treats all three responsibilities as one task, scope gaps can remain hidden.
Breaking each interface into furnish, install, and terminate responsibilities makes those gaps easier to identify.
The important point is to ask these questions before the work reaches the field.
Build a Controls Interface Matrix
A control interface matrix provides a structured way to document the connections between the control system and the other trades.
Instead of relying on conversations, assumptions, or scattered notes, the matrix identifies important interfaces and assigns responsibilities.
Depending on the project, a matrix might address:
- Control panel power
- Sensors and transmitters
- Dampers and actuators
- Variable frequency drives
- Equipment enables signals
- Safety interlocks
- Current switches
- Packaged equipment integration
- Network connections
- Low-voltage and line-voltage wiring
- Device installation and termination responsibilities
The matrix becomes especially valuable when it is reviewed with the other contractors.
A document created by the controls team but never discussed with the electrical and mechanical teams has limited value. Coordination happens when the responsible parties review the interfaces, identify disagreements, and resolve them before those disagreements affect installation.
The matrix should also evolve with the project. Submittals change. Equipment selections change. Field conditions change. Coordination documentation needs to reflect those changes.
Pay Attention to Field Dependencies
Controls installation rarely happens independently.
A technician may need power before a panel can be commissioned. A mechanical system may need to be operational before functional testing can begin. A network connection may need to be available before equipment integration can be verified.
Every one of those items represents a dependency.
Controls professionals should identify these dependencies early and connect them to the project schedule.
Ask what needs to happen before your work can begin. Then ask what work cannot continue until your task is complete.
That creates a clearer picture of where controls fits into the construction sequence.
It also helps teams distinguish between an inconvenience and a schedule threat.
If a missing electrical connection will prevent startup next week, the issue should not wait until startup day to receive attention.
Walk the Seams Between Trades
Coordination cannot happen entirely through drawings and meetings.
Field conditions matter.
Controls professionals should inspect the physical locations where their work intersects with another contractor's work. Verify that the required infrastructure exists and that the installation matches the assumptions used during coordination.
Look at panel locations. Check equipment connections. Verify pathways. Review device locations. Confirm that the equipment supplied by another contractor contains the expected interface.
These inspections are most useful when they happen early.
Discovering a missing connection while another contractor is still mobilized and working in the area is very different from discovering it after that contractor has demobilized.
The objective is to find problems while they are still inexpensive to solve.
Handle Conflict as a Project Problem
Even strong coordination will not eliminate every disagreement.
When a conflict appears, the response matters.
Start by separating the technical problem from the person involved. The electrical foreman or mechanical contractor is usually working from the same types of project documents and contractual requirements as the controls team.
Turning a scope disagreement into a personal confrontation does nothing to restore the schedule.
Instead, define the issue clearly and bring potential solutions into the conversation.
There is a major difference between reporting that power is missing and identifying that power is missing while also presenting a practical path that could keep the work moving.
That approach changes the conversation from assigning blame to resolving a project constraint.
Use the Contractual Process Early
Some disagreements cannot be solved between field teams.
That is why projects have formal processes such as requests for information.
An RFI should not be treated as an escalation of hostility. It is a mechanism for obtaining clarification when the contract documents do not provide a clear answer.
Timing matters.
An unresolved scope issue identified early may be addressed while the schedule still has flexibility. The same issue discovered near the end of the project can interfere with startup, commissioning, inspections, or turnover.
Document uncertainties while there is still time to resolve them.
Written documentation also creates clarity for everyone involved. Conversations are useful for moving quickly, but important decisions should not exist only in someone's memory.
Protect the Working Relationship
Building automation professionals often work with the same general contractors, engineers, electrical contractors, and mechanical contractors across multiple projects.
How a controls team handles a disagreement can therefore matter long after the immediate issue is resolved.
Being technically correct is important. Being technically capable and easy to work with is more valuable.
That does not mean accepting responsibility for work that is outside your scope. It means approaching disagreements professionally, documenting them appropriately, and remaining focused on completing the project.
Strong working relationships make future coordination easier because teams develop trust in one another's communication and execution.
Controls Has One of the Best Views of the Building
Controls are often described as the trade in the middle.
That position can feel difficult when several contractors need to complete their work before the controls team can finish its own. It also provides a perspective that few other trades have.
Controls touches mechanical equipment, electrical systems, networks, sensors, actuators, sequences, and integration points. The building automation team sees how systems that were designed and installed separately must eventually operate together.
That visibility can be used to identify problems before they become expensive.
Know the interfaces. Clarify who furnishes, installs, and terminates each component. Build an interface matrix. Track dependencies. Walk the field. Document decisions. Address conflicts early.
Coordination is not an administrative task separate from control work. It is part of delivering a control system that can be installed, commissioned, and turned over successfully.
When the controls team manages the seams between trades effectively, it protects more than its own scope. It helps protect the project schedule, the budget, and the professional relationships that lead to the next project.
For a deeper discussion and insights from the field, listen to this episode on the Smart Buildings Academy podcast.
%20(1920%20x%201080%20px)%20(7).png)
