Recurring alarms
Repeated events are reviewed in context to distinguish persistent conditions from isolated occurrences.
Preventive maintenance
Routine attention to the installed control environment.
Preventive maintenance provides a structured review of system condition, configured operation and accessible records. It supports the wider lifecycle of BMS & Building Automation without assuming a standard scope for every building.
01
System health checks
Controller status and communications health are reviewed across the BMS architecture and connected networks within the agreed scope.
02
Alarms & schedules
Active alarms, alarm history and operating schedules are checked for consistency with current site requirements.
03
Trends & operation
Available trend data and operating conditions are reviewed to help identify control issues and abnormal system behaviour.
04
Backups
Available controller and supervisory configurations are backed up according to the installed platform and agreed maintenance scope.
05
Operator interface
Graphics, point values, commands and navigation are reviewed for operational consistency and visible discrepancies.
06
Field-device condition
Sensors, actuators and other field devices may be checked where they form part of the defined maintenance scope.
BMS troubleshooting
Diagnostics grounded in the complete control path.
Troubleshooting considers the relationship between field devices, controllers, networks, interfaces and the supervisory layer. The diagnostic path depends on the reported issue, installed platform and accessible system information.
- Communication faults
- Controller faults
- Point & sensor issues
- Actuator issues
- Alarm faults
- Graphics inconsistencies
- Schedule issues
- Control-sequence issues
- Network & interface diagnostics
Backup & configuration management
System records prepared for continued support.
Maintaining available configuration records helps establish a clearer technical baseline for troubleshooting, approved changes and recovery planning. The available backup method and record detail depend on the installed system and access provided.
- 01Controller backups
- 02Supervisory backups
- 03Configuration records
- 04Graphics records
- 05Logic and version control where applicable
- 06Recovery preparedness
Alarm & trend review
Operational records interpreted in context.
Alarm and trend information can support the identification of control issues when it is reviewed alongside schedules, equipment states and known operating conditions.
Nuisance alarms
Alarm behaviour can be assessed against the approved operating intent and configured system parameters.
Abnormal trends
Available historical data is reviewed for patterns that may indicate a control, sensing or operating issue.
Schedules & conditions
Schedules and observed operating conditions are checked against current site requirements and approved changes.
Logic & graphics changes
Controlled changes around the approved site scope.
Adjustments to control logic, schedules, setpoints and operator graphics are developed subject to the approved site scope, access permissions and compatibility of the installed system.
- Setpoint adjustments
- Schedule changes
- Sequence modifications
- Logic updates
- Graphics updates
- Point naming & organization where relevant
System upgrades & lifecycle support
A considered path for systems that need to evolve.
Lifecycle work may address individual control components, supervisory platforms, networks or wider migration requirements. Modernization can be phased around the existing installation, technical viability and approved project boundaries, with recommissioning where relevant.
BMS Upgrade & Retrofit- Controller upgrades
- Supervisory upgrades
- Network upgrades
- Migration planning
- Phased modernization
- Support for legacy systems
- Recommissioning where relevant
AMC scope
A maintenance scope defined for the installed system.
An Annual Maintenance Contract is defined project by project. Its scope reflects the installed BMS, connected equipment, site operating context and the support responsibilities agreed for that specific installation.
- Installed BMS platform
- System size
- Equipment scope
- Site access requirements
- Maintenance frequency
- Support boundaries
- Agreed exclusions
Maintenance frequency, support boundaries and exclusions are documented for the agreed scope. No fixed visit pattern is assumed across different sites and platforms.
Maintenance requirements