Skip to content
servomatrix.
Services

The technical work behind every controls package.

Eleven services across four engineering stages. Solutions describe the outcome; these are the disciplines that deliver it.

Design & Engineering

BMS Design Support

01

Control system architecture and documentation that holds up to scrutiny.

What it solves

Controls packages often reach procurement with incomplete points schedules, unclear interfaces or network architecture that has not been resolved.

When it is required

During design development and before tender, when the controls scope and integration boundaries need to be defined.

What we deliver

servomatrix develops the architecture, I/O mapping, integration boundaries and sequence framework required for a coherent controls package.

Typical deliverables
  • BMS architecture and topology diagram
  • Points schedule and I/O budget
  • Controller selection basis
  • Integration schedule
  • Sequence-of-operation framework
Inputs required from the client
  • Mechanical equipment schedules
  • Consultant specifications
  • HVAC schematics
  • Available layouts and electrical interfaces
RelatedBACnet/IPModbus TCPDDC controllers

DDC Panel Engineering

02

Field panels built and documented to a repeatable, serviceable standard.

What it solves

Inconsistent panel design and poor documentation make systems difficult to terminate, fault-find and maintain over their life.

When it is required

Once the architecture and points schedule are set and panels need to be engineered and fabricated.

What we deliver

Direct digital control panel design, fabrication oversight and as-built documentation for plant rooms, risers and field locations.

Typical deliverables
  • Panel schematics and wiring diagrams
  • Termination schedules and labelling
  • Bill of materials and component schedules
  • Factory acceptance documentation
Inputs required from the client
  • Approved points schedule
  • Controller selection
  • Plant room and riser layouts
  • Electrical supply details
RelatedDDC controllersField I/OVariable speed drives

HVAC Control Strategy

03

Sequences engineered for stability, comfort and energy discipline.

What it solves

Poor control logic causes comfort complaints, hunting, short cycling and unnecessary plant runtime.

When it is required

Whenever air handling, water plant, terminal units or ventilation need defined, defensible control sequences.

What we deliver

Control strategies for air handling, chilled and heating water plant, terminal units and ventilation, written as clear sequences of operation.

Typical deliverables
  • Plant and zone control sequences
  • Setpoint and reset strategies
  • Staging, optimisation and interlock logic
  • Alarm and safety strategy
Inputs required from the client
  • Mechanical design intent
  • Plant schedules
  • Zoning and occupancy information
  • Safety and interlock requirements
RelatedAHUs & FCUsChiller plantVentilation systems

Delivery & Integration

BMS Programming

04

Controller logic written to be read, audited and maintained.

What it solves

Programming written only to function — not to be read — leaves the next engineer unable to maintain the system without a translator.

When it is required

During delivery, once sequences and graphics requirements are defined.

What we deliver

Application programming across DDC controllers and supervisory platforms, structured so the next engineer can understand it without a translator.

Typical deliverables
  • Structured, commented controller logic
  • Reusable function blocks and templates
  • Trends, schedules and alarm configuration
  • Version-controlled program backups
Inputs required from the client
  • Approved sequences of operation
  • Points schedule
  • Controller platform
  • Trend and alarm requirements
RelatedDDC controllersSupervisory platforms

System Integration

05

BACnet, Modbus and IP devices brought under one operator view.

What it solves

Mechanical equipment, meters and third-party systems operate in isolation without disciplined integration.

When it is required

When mechanical plant, metering and third-party equipment must be brought under one supervisory layer.

What we deliver

Integration of mechanical plant, metering and third-party equipment over BACnet/IP, BACnet MS/TP, Modbus TCP and Modbus RTU into a single supervisory layer.

Typical deliverables
  • Protocol gateways and device mapping
  • Register and object mapping documentation
  • Unified alarming and trending
  • Single operator interface across systems
Inputs required from the client
  • Manufacturer protocol documentation
  • Register / object lists
  • Network design
  • Interface ownership matrix
RelatedBACnet/IPBACnet MS/TPModbus TCPModbus RTU

Operator Graphics

06

Front-end interfaces operators can actually run a building from.

What it solves

An operator interface built without regard to how facilities teams work gets ignored, and the system loses its value.

When it is required

During delivery, alongside programming, before commissioning and handover.

What we deliver

Graphics and dashboards built around how facilities teams actually work — plant overviews, floor plans, live values and drill-down detail.

Typical deliverables
  • Plant and zone graphic pages
  • Live value, status and alarm display
  • Trend and reporting views
  • Role-based navigation and access
Inputs required from the client
  • Plant layouts and floor plans
  • Points schedule
  • Operator workflow expectations
  • Access-level requirements
RelatedSupervisory platformsTrends & loggingUser access levels

Verification & Handover

Testing & Commissioning

07

Point-by-point verification with documented, signed-off results.

What it solves

Untested sequences and incomplete checks leave defects that surface as call-backs after handover.

When it is required

At handover stage, to prove the installed system against the design intent.

What we deliver

Pre-functional checks, point-to-point testing and functional performance testing of sequences against the design intent.

Typical deliverables
  • Point-to-point test records
  • Functional performance test results
  • Witnessed commissioning sign-off
  • Defect register and close-out
Inputs required from the client
  • Approved sequences
  • Installed and powered system
  • Points schedule
  • Access to plant for testing
RelatedCommissioning recordsSequence verification

Documentation & Operator Training

08

An as-built record and operators who can confidently run the system.

What it solves

Incomplete documentation and untrained operators leave a facility team with a system they cannot confidently maintain.

When it is required

At handover, to transfer the system to the operating team properly.

What we deliver

As-built documentation, operations and maintenance records, and structured operator training on the system the facility team will actually use.

Typical deliverables
  • As-built drawings and schedules
  • Operations and maintenance pack
  • Backup and recovery records
  • Operator training sessions and reference material
Inputs required from the client
  • Completed commissioning records
  • Final program backups
  • Operator availability for training
RelatedAs-built documentationBackup & handover records

Performance & Lifecycle

Energy Monitoring

09

Metering and analytics that turn consumption into decisions.

What it solves

Without visibility of consumption and demand, there is no basis for tuning, reporting or verifying savings.

When it is required

When operational visibility of energy and utilities is required, on new or existing buildings.

What we deliver

Energy and utility metering integration, sub-metering strategy, and dashboards that make consumption, demand and anomalies visible.

Typical deliverables
  • Metering point strategy and integration
  • Consumption and demand dashboards
  • Anomaly and threshold alerting
  • Reporting framework agreed to the project's monitoring objectives
Inputs required from the client
  • Meter schedule and locations
  • Network access
  • Reporting objectives
  • Tariff and tenancy structure
RelatedEnergy & utility metersTrends & logging

Remote Support

10

Secure remote monitoring and a defined response path.

What it solves

Buildings drift after handover; without ongoing support, performance degrades and faults go unnoticed.

When it is required

After handover, under an agreed lifecycle support scope.

What we deliver

Secure remote access, proactive monitoring and a structured support model for diagnosis, tuning and fault resolution.

Typical deliverables
  • Secure remote access setup
  • Proactive alarm and trend monitoring
  • Support response model agreed under the service scope
  • Periodic performance reviews
Inputs required from the client
  • Network and access policy
  • Supervisory platform access
  • Agreed support scope
RelatedSecure remote accessAlarms & events

Retrofit & Upgrade Works

11

Migrating ageing controls without shutting the building down.

What it solves

Legacy and obsolete control systems become unsupportable, but the building has to keep operating through any upgrade.

When it is required

When an existing system reaches end of support or no longer meets operational needs.

What we deliver

Staged migration of legacy and obsolete control systems to current, supportable platforms — planned around an operating building.

Typical deliverables
  • Existing system audit and migration plan
  • Staged cutover with minimal disruption
  • Supportable replacement architecture selected against the project's operational, integration and procurement requirements
  • Full re-commissioning and documentation
Inputs required from the client
  • Existing system records
  • Site survey access
  • Operational constraints
  • Phasing requirements
RelatedOpen-protocol interfaces where specifiedCommissioning records

Planning a BMS package, controls upgrade or commissioning scope?

Send the available drawings, specifications, points schedule or project brief. We will review the control requirements and identify the most practical next step.