03 / Braincord Systems

A BMS project is only complete when the controls work.

A connected screen is the beginning, not the outcome. Define the operating sequence, test the equipment response and give the facility team the information to run the building.

Built for scale

One operations hub.
An entire campus behind it.

Switch system layers on and off to see how HVAC, energy, lighting, access interfaces and water services each reach the same operator view. Drag to rotate, double-click to reset.

Rooftop & plant sensorsLive data and commands50 buildings · 5 system layers · 1 operator view

Illustrative model, not a customer site. Real topology, device counts and communication paths are defined after the site survey.

The five layers

What each system layer brings in.

Typical examples only. Scope is set by the equipment survey and points list.

01

HVAC & plant

Chillers, AHUs, FCUs, pumps and VRF gateways. Temperatures, status, valve and damper feedback, schedules and alarms.

02

Energy & metering

Electricity, water, gas and thermal meters, plus DG sets and UPS. Consumption by area and time, demand and power-factor trends.

03

Lighting

Zone schedules and occupancy-based control where the installed lighting system supports it, with manual override kept distinct.

04

Access & security interfaces

Status and alarm monitoring through defined interfaces. Dedicated access, fire and CCTV systems remain independent.

05

Water & utilities

Tank levels, pump status, leak and overflow alarms, STP and other utility plant where connected.

02 / Why intelligent buildings

Measure what matters.
Improve how the building runs.

Good controls connect a measurable operating problem with a practical response—not a dashboard alone.

↓ kWh

Find avoidable energy use.

Trend metered consumption alongside plant schedules. Investigate equipment running outside occupancy hours and compare results against a defined baseline.

°C +

Track conditions by zone.

Review temperature trends and repeated comfort complaints together. Check sensors, setpoints and equipment response before changing the control strategy.

→ !

Make alarms actionable.

Prioritize equipment exceptions and define who responds. Repeated nuisance alarms and persistent overrides deserve investigation, not permanent acknowledgement.

From survey to operation

Four stages. Clear decisions at each one.

01

Survey the property

Establish equipment, existing controls, occupancy hours and the problems the facility team needs to solve. For an occupied site, identify access constraints and acceptable shutdown windows.

02

Define the control strategy

Agree the points to monitor and control, operating sequences, alarm priorities and integration boundaries. Check communication capabilities and responsibilities before specifying hardware.

03

Install and prove the response

Test sensor readings, commands, feedback, schedules and alarms against the approved sequence. Record exceptions and retest corrections before accepting the system.

04

Hand over and review

Set out operator access, drawings, configuration backups and routine tasks. Review operating trends after the building is in use and document any changes to schedules or setpoints.

Integration and operational access

Plan the connections.
Protect the controls.

Open communication standards such as BACnet help compatible building devices exchange information. They do not remove the need to check device capabilities, point mapping, software licences and integration testing.

Agree network access with the property’s IT team. Define operator permissions, remote-access arrangements, backups and change records. Independent equipment protections and dedicated life-safety controls must remain intact.

Large systems

Scaling from one building to a whole estate.

The principles are the same. The discipline matters more as the point count grows.

01

Start with a template

Design one standard sequence, graphic and alarm set for each equipment type (AHU, chiller, meter). Reuse it across buildings so operators see the same thing everywhere.

02

Pilot, then roll out

Prove the design on one building or floor, correct what the pilot teaches, then replicate in agreed phases. This reduces risk on occupied sites.

03

Plan the network hierarchy

Separate field buses, building-level networks and the campus backbone. Define bandwidth, redundancy and how each building behaves if the backbone is unavailable.

04

Keep control local

Controllers run their own sequences. A loss of the central server should not stop plant from operating or manual override from working.

05

Central operations view

One operator view across buildings with roles per site, tenant or contractor, so people see and change only what they are responsible for.

06

Multi-site portfolios

For owners with buildings in several cities, consistent naming, graphics and reporting make comparison possible and allow a central team to support local sites.

Design rules for large systems

Decide it once.
Repeat it everywhere.

Large installations succeed or fail on consistency. Agree these rules before the first point is wired.

  • A single naming convention for sites, buildings, floors, equipment and points
  • Consistent point tagging so reports and analytics can find the same data in every building
  • Standard alarm priorities and escalation routes across the estate
  • Documented IP addressing, device ID ranges and network diagrams
  • Spare capacity in panels, network and licences for expansion
  • Backup, restore and change-control procedures tested before handover

Open tagging approaches such as Project Haystack or Brick Schema can help structure data for analytics. Whether they are used is agreed per project.

Operations & reporting

Turning a lot of data into a few decisions.

The more points a system has, the more important it is to filter what reaches people.

01

Alarm rationalisation

Group related alarms, set delays and priorities, and review nuisance alarms regularly. Operators should be shown what needs action, not everything that changed.

02

Exception reports

Highlight equipment running out of hours, persistent overrides, drifting sensors and comfort complaints by zone, rather than expecting people to read every trend.

03

Energy review cadence

Agree who reviews consumption against the baseline, how often, and what actions follow. Record changes so results can be traced to causes.

04

Management reporting

Summaries for owners and boards: availability, alarm response, energy against baseline and open actions, in language that does not need a controls background.

What you receive

Deliverables at every stage.

Exact documents are listed in the project scope. This is a typical set.

Deliverables and client inputs at each project stage
StageTypical deliverablesWhat we need from you
1 · SurveyEquipment inventory, existing-controls assessment, site constraints and a list of operating problems to solve.Site access, existing drawings, operating hours, a facility contact.
2 · Control strategyPoints list, control sequences, alarm priorities, network architecture and integration boundaries.Review and sign-off, IT network requirements, tenant and safety constraints.
3 · Install & proveInstalled field devices and panels, point-to-point and functional test records, an exceptions log with retests.Shutdown windows, coordination with other trades, witness attendance for key tests.
4 · Handover & reviewAs-built drawings, configuration backups, operator instructions, training record and a post-occupancy trend review.Named operators for training, agreement on support and review arrangements.
Who does what

Clear responsibilities prevent delays.

Agree these at kick-off and record them in the scope.

01

Owner & facility team

Provide access, drawings and decisions on schedules and setpoints. Nominate who can approve changes and who responds to alarms.

02

Braincord Systems

Survey, design the control strategy, install and integrate the BMS, commission it, document it and train the operators within the agreed scope.

03

MEP, IT and equipment suppliers

Mechanical and electrical contractors supply equipment interfaces. IT approves network access. Suppliers confirm protocol support and licences for their devices.

Commissioning checklist

What “working” means,
in writing.

Each item is tested against the approved sequence and recorded, not assumed from a screen colour.

  • Sensor readings checked against a reference instrument
  • Every command confirmed by physical equipment response and feedback
  • Schedules, setpoints and manual overrides tested
  • Alarm triggers, priorities and notification routes verified
  • Behaviour on loss of communication or power recovery checked
  • Exceptions logged, corrected and retested before acceptance
Risks we plan for

Most delays are predictable.

Raising them early keeps the project on track.

01

Undocumented equipment

Drawings often differ from what is installed. The survey verifies equipment and wiring before design is fixed.

02

Closed or legacy controllers

Proprietary or obsolete controllers may need a gateway or replacement. Licences and access rights are checked up front.

03

Network access

Late IT approval is a common cause of delay. Network requirements are shared at the strategy stage.

04

Trade coordination

Controls depend on plant being installed and running. Test dates are planned with the other contractors.

05

Occupant disruption

Work in occupied buildings is phased around operating hours and agreed shutdown windows.

Define the right BMS scope for your building.

Start with your property, existing systems and operational priorities.

Discuss your project