Bleuwave Controls

Controls Service & Repair

Building Automation & Controls Service

Alarms, communication failures, failed points, sequence problems and comfort complaints — diagnosed from the system's own data rather than by replacing parts until something changes.
Request Controls ServiceAsk About a Service Agreement

What is happening?

Give us the short version and we will route it to the right technician. Need to send drawings or a longer history? Use the full service request form.

if known
Urgency (required)
Documents

Optional — a photo of the panel or a screenshot of the alarm helps us arrive prepared.

PDF, images, Office documents, DWG/DXF or ZIP · up to 25 MB each

You will receive a confirmation email. See our Privacy Policy.

What we service

Issues we are called out for

  • BAS alarms and communication failures
  • Controller, sensor and actuator troubleshooting
  • Network issues across BACnet and Modbus trunks
  • Failed graphics or missing points
  • Sequence problems and unexpected equipment behaviour
  • Comfort complaints tied to controls rather than capacity
  • Scheduling issues after occupancy or tenant changes
  • Remote-access issues
  • VFD and equipment integration faults
  • Legacy controls troubleshooting
  • Lighting controls faults, zones and schedule problems
  • Software and database support where we hold the required access

Diagnostics

How we work a controls problem

The order matters. Most repeat service calls happen because someone skipped the first two steps.

  1. Confirm the symptom

    What is actually being observed, where, and when. A "too cold" complaint and a "cold at 6am only" complaint are different problems.

  2. Check the data before the hardware

    Trends, alarm history and current point values. The system usually already recorded what happened.

  3. Verify the point is true

    Compare the reported value against reality at the device. A large share of "sequence problems" are a sensor reading the wrong thing.

  4. Check for overrides and manual commands

    Points left in manual after a previous service call are one of the most common causes we find.

  5. Test the sequence, not the theory

    Drive the system through the affected mode and observe. Assumptions about what the logic does get verified here.

  6. Correct and re-test

    The fix is applied, then the original condition is re-created to confirm it is actually resolved.

  7. Report what was found

    A written record of the symptom, root cause, correction and any recommendation — so the same call is not repeated in six months.

Common findings

What these calls usually turn out to be

Published because knowing the pattern helps you describe the problem — and sometimes resolve it before calling anyone.

What you’re seeing

Half the building lost communication with the BAS.

How we approach it

Usually a network segment issue: a failed repeater, a device dragging down an MS/TP trunk, a duplicate address after a controller swap, or a switch port change made by IT.

What you’re seeing

One zone has been in reheat since last spring.

How we approach it

Typically a minimum airflow set too high for the current load, a failed damper actuator, or a zone sensor reading several degrees off.

What you’re seeing

Alarms flood the console every morning.

How we approach it

Alarm delays and deadbands that do not account for startup transients. The equipment is fine; the alarm strategy is not.

What you’re seeing

A schedule change did not take effect.

How we approach it

A local override at the controller, a holiday calendar entry, or a schedule written at the wrong level of the hierarchy so a higher priority is winning.

What you’re seeing

Graphics show points that no longer exist.

How we approach it

Controller replaced without updating the database or the graphics. The screen is showing a stale object reference.

What you’re seeing

Equipment runs at night despite an unoccupied schedule.

How we approach it

An after-hours override with no timeout, a tenant override button wired to the wrong point, or optimal start pulling equipment on far earlier than intended.

Ongoing support

Service agreements and preventive maintenance

Reactive service keeps a building running. Planned service keeps it from degrading in the first place — sensors verified before they drift far enough to matter, schedules reviewed against the current calendar, overrides cleared, database backups taken, and trends reviewed by someone who knows what to look for.

Agreement scope, coverage hours and inclusions are set per facility. Talk to us about what your building actually needs rather than fitting it to a tier.

HVAC controls service technician inspecting rooftop equipment
Service starts with the symptom, then follows points, sequences and equipment behavior to the cause.
Controls technician commissioning building automation equipment in a mechanical room
Commercial facility operator reviewing building automation performance

Questions

Frequently asked questions

Yes — most of our service work is on systems installed by someone else. The practical limit is platform access: some manufacturers restrict programming software or require licensed credentials. We check that early and tell you if we cannot fully support a platform, rather than taking the call and discovering it on site.

The facility and address, the BAS or lighting-control platform if you know it, which equipment or spaces are affected, the exact alarm text if there is one, when it started, and what has already been tried. A photo of the controller label and a screenshot of the alarm or the affected trend will often save an entire diagnostic visit.

Where remote access already exists and the owner has authorized it, yes — schedule corrections, override clearing, database changes, graphics fixes and a great deal of diagnosis can be done remotely. Anything requiring physical verification of a sensor, actuator or wiring needs someone on site.

Diagnostic time is billable regardless of what it finds, and we say so up front. What we will not do is quote a controls repair for a mechanical failure. If the trend shows a failed compressor rather than a control problem, we tell you that and hand you the evidence to take to your mechanical contractor.

Response depends on the urgency, the building impact, and current coverage. Rather than publish a number we have not staffed for, we ask you to describe the urgency in the service request — routine, urgent, building impact or after-hours — and our team will confirm timing directly when we contact you.

Related capabilities

Next step

Have a controls problem right now?

Submit a service request with the facility, platform, affected equipment and what is happening. Attach a screenshot or photo if you have one — it usually shortens the diagnosis considerably.
Request Controls ServiceAsk About a Service Agreement
CallServiceGet Quote