Skip to main content
Controls & BMS Maintenance

BMS Head-End / Supervisor Workstation Maintenance Checklist

Keep your BMS supervisor working for you — database backups, alarm and trend health, graphics accuracy, software and security patching, and network checks.

What is a bms head-end maintenance checklist?

A bms head-end / supervisor workstation maintenance checklist is a structured list of the 10 preventive maintenance tasks — covering visual, functional and record-keeping checks — that keep a bms head-end / supervisor workstation running safely and reliably. It groups routine checks by frequency, from daily inspections to annual servicing, so FM teams and building engineers can plan and evidence preventive maintenance.

Core bms head-end checks

  • Verify graphics match the installed plant and read live, correct values
  • Review active and standing alarms
  • Confirm a current, tested backup of the BMS database and configuration exists

What is a bms head-end / supervisor workstation?

The BMS head-end (or supervisor workstation) is the front-end of a building management system — the PC or server, software, graphics, alarm handling, trending, and scheduling that let operators monitor and control HVAC, lighting, and energy across the building. It sits above the field controllers and outstations on the BMS network. The head-end is often neglected because it is software rather than plant, but unbacked-up databases, unmanaged alarms, drifting clocks, and out-of-date graphics quietly erode the value of the whole system. Maintenance focuses on backups, alarm hygiene, trend integrity, and keeping software and security current.

This checklist is one of 7 in our BMS and controls maintenance checklists, covering bMS panels and head-ends, DDC controllers, inverters, sensors and actuators — calibration, overrides and strategy backups.

Typical BMS Head-End maintenance checklist

A practical starting point for planned preventive maintenance. Always refer to the manufacturer's O&M manual and site-specific requirements.

BMS Head-End / Supervisor Workstation maintenance checklist showing tasks such as verify backup completed, review active alarms and spot-check trends and graphics, each with its service frequency
A preview of the BMS Head-End maintenance checklist — the full 10-task routine, service frequencies and safety notes are below, free to download as a PDF.

Visual Checks

  • Verify graphics match the installed plant and read live, correct values

Functional Checks

  • Review active and standing alarms — investigate, action, or rationalise
  • Check trend logs are recording correctly with no gaps or stuck points
  • Confirm time synchronisation across the head-end and controllers
  • Check schedules and setpoints reflect current occupancy and seasons
  • Apply OS and BMS software updates and security patches per policy
  • Confirm network communications to all controllers are healthy

Record Keeping

  • Confirm a current, tested backup of the BMS database and configuration exists
  • Review user accounts and access levels, removing leavers
  • Record backups, software versions, alarm review, and changes in the log

Download the free BMS Head-End maintenance checklist PDF

Get all 10 tasks as a printable PDF — free, no signup needed. Keep a copy in the plant room, attach it to work orders, or share it with your maintenance contractor.

Typical maintenance frequency

Suggested intervals for bms head-end / supervisor workstation maintenance. Actual frequencies should follow manufacturer guidance and site-specific risk assessments.

Monthly

  • Verify backup completed
  • Review active alarms
  • Spot-check trends and graphics

Quarterly

  • Rationalise standing alarms
  • Review schedules and setpoints
  • Check user accounts and time sync

Annually

  • Full database backup and restore test
  • Software/security update review
  • Graphics and point audit
  • Network health review

Common faults and issues

Issues to be aware of when maintaining bms head-end / supervisor workstation equipment.

No tested backup, so a PC failure loses years of configuration and trends
Alarm flooding — hundreds of standing alarms mask the ones that matter
Graphics out of date after plant changes, showing values that no longer exist
Clock drift between head-end and controllers corrupting trends and schedules
Unpatched, out-of-support operating system creating a security and reliability risk
Leaver accounts left active, undermining access control

Safety and compliance notes

Key safety considerations for bms head-end / supervisor workstation maintenance. This is general guidance only — always follow OEM instructions, statutory requirements, and your organisation's safe systems of work.

Coordinate any software updates or restarts so safety-critical control is not interrupted
Keep BMS networks segregated and patched — they are a known cyber-attack surface
Verify backups by test-restoring, not just by assuming the job ran
Do not change setpoints affecting life-safety or critical environments without authorisation
Record all configuration changes so they can be reviewed and reversed

Reference standards and frameworks

United Kingdom
SFG20 schedules and CIBSE Guide H (building control systems)
North America
ASHRAE Guideline 13 (specifying building automation systems)

Frameworks commonly referenced when planning bms head-end maintenance programmes. Always confirm the requirements that apply to your site and jurisdiction.

How PM Assist helps

Managing BMS Head-End documentation with PM Assist

PM Assist helps FM and building operations teams search their O&M manuals and building drawings in seconds. Upload your bms head-end / supervisor workstation documentation and ask questions like “When was the BMS database last backed up?” or “What are the current AHU setpoints?” — and get source-cited answers instantly.

See PM Assist answer questions about a real bms head-end manual — try the live demo, no signup needed.

Take this checklist with you

Download the branded PDF, generate a custom version for your asset, or run AI search across all your building documentation.

Generate a custom checklist

Frequently asked questions

Why does a BMS head-end need maintenance if it's just software?
Because the software is where the building's control intelligence lives. Without tested backups a single PC failure can lose all configuration, graphics, and trends. Unmanaged alarms hide real faults, drifting clocks corrupt schedules and energy data, and unpatched operating systems become security and reliability risks. Treating the head-end as a maintained asset protects the value of the entire BMS.
How often should the BMS database be backed up?
At minimum monthly, with critical sites backing up more frequently and after every significant configuration change. Crucially, backups should be tested by occasionally restoring them — a backup that has never been verified may not work when needed. Keep copies off the head-end PC itself so a hardware failure does not take the backup with it.
What is alarm rationalisation on a BMS?
Alarm rationalisation is reviewing the configured alarms to ensure each one is meaningful, correctly prioritised, and actionable, and removing or re-tuning nuisance alarms. Over time BMS systems accumulate standing and repeating alarms that operators learn to ignore — which means a genuine fault can be missed. Periodic rationalisation restores trust in the alarm list.

Manage your building documentation with AI

PM Assist gives FM teams instant access to O&M manuals, drawings, and maintenance knowledge — all searchable with AI.

  • Upload and organise building documentation
  • AI-powered search across all your manuals
  • Source-cited answers for maintenance queries
  • Team collaboration and access control
  • No credit card required to start