CMMS for Government Agencies and Municipalities

What a CMMS does for a government agency or municipality

A CMMS for government is a computerised maintenance management system that a ministry, agency or municipality uses to log every maintenance request, turn it into an approved work order, plan preventive and statutory work, and keep a dated, signed history per asset and site. It matters because public bodies must prove to auditors, councillors and citizens that buildings and plant were inspected, repaired and paid for correctly.

This guide is vendor-neutral. It covers what public bodies maintain, the request-to-sign-off chain, visibility across many sites, planned and statutory work, contractor control, cost and budget tracking, the procurement rules that apply when you buy a CMMS in the EU, Saudi Arabia and Canada, and an RFP checklist. Rules and thresholds are stated as of October 2026.

What public bodies maintain, and why spreadsheets fail at audit

ISO 55000:2024 defines an asset as an item, thing or entity that has potential or actual value to an organisation, and asset management as the coordinated activity of an organisation to realise value from assets. For a public body that value is public service: a school that stays open, a pumping station that keeps running, a lift that passes its examination.

Spreadsheets and paper job sheets break down at audit for three reasons. They hold the current state but not the history, so nobody can show when the fire panel in a school was last tested and by whom. They do not tie a cost to an asset, so a councillor asking what the leisure centre costs to maintain gets an estimate rather than a figure. And they are easy to edit after the event, so an auditor cannot rely on them.

The asset base is also unusually wide. A typical local authority looks after:

• Buildings: town halls, schools, libraries, depots, sports centres and social housing
• Building plant: boilers, chillers, air-handling units, lifts, standby generators, fire alarm and sprinkler systems, emergency lighting
• Fleets: refuse trucks, gritters, minibuses and pool cars, each with servicing and inspection dates
• Parks and open spaces: play equipment, irrigation, mowers and grounds machinery
• Street assets: street lighting, traffic signals, signs, bridges and culverts
• Utility networks where the authority owns them: water, wastewater and stormwater assets

The request-to-sign-off chain

Every maintenance job in a public body should follow one traceable chain, whoever raises it: a teacher reporting a broken radiator, a contact-centre agent logging a citizen's complaint about a park bench, or an inspector finding a defect. The chain is what lets you answer the audit question: who authorised this job, who did it, and how do we know it was done?

Two controls make the chain credible. Approval must sit before the work, not after it, so a job still awaiting approval cannot move to in progress. And the approval limit should scale with risk: low-cost, low-priority jobs can be approved automatically, while urgent or safety-critical work always needs a named person to decide. The steps are:

• Request: staff or the contact centre log the problem against a site and, where known, an asset
• Triage: a supervisor removes duplicates, sets the priority and decides whether the request is maintenance at all
• Approval: jobs above a cost threshold, or of a sensitive type, need a named approver before work starts
• Work order: the approved request becomes a work order with a type, a priority and a target date
• Assignment: the job goes to an in-house technician by skill and location, or to a contractor under a framework contract
• Execution: start and finish times, parts, labour hours, readings and photos are recorded on the job
• Sign-off: the technician signs, and for higher-risk work a client-side officer accepts the job before it closes
• Close and analyse: the closed record feeds cost, downtime and repeat-failure reports

Many sites, one register: visibility by site and department

A municipality rarely has one building. It has dozens or hundreds, run by departments with their own budgets: education, leisure, highways, social care. A ministry may have regional offices across the country. The CMMS has to show each manager their own sites while letting the central estates team see everything.

The practical design is a hierarchy of site, building and asset, with users given access by site. A school business manager sees and requests work for one school; the head of property sees the whole estate and can compare maintenance cost per square metre across all schools. Site-level access also supports segregation of duties: the officer who accepts a contractor's work at one site should not be able to close jobs at another.

Keep one asset register across all sites. When each depot keeps its own list, the same model of generator ends up with three different names, and an estate-wide question such as how many units of this model failed last year cannot be answered.

Planned maintenance and statutory inspections

Planned preventive maintenance (PPM) is work done before failure on a calendar or usage interval. In the public sector much of it is statutory or insurance-driven inspection: fire alarm and sprinkler testing, lift examinations, gas safety, emergency lighting, standby generator runs and water hygiene. Each produces a certificate or report with an expiry date, and an expired certificate on a public building is a finding in any audit or inspection.

Set frequencies from manufacturers' instructions, national regulations and your insurer. What matters for control is that each schedule has a next-due date, that the work order raised from it carries the checklist and readings, and that the certificate is attached to the asset with its expiry date. A weekly list of schedules due and certificates expiring in the next 60 days is the simplest control a council can run.

Volume is what defeats manual tracking. Take a town with 40 buildings and this illustrative plan:

• Weekly fire alarm test in 40 buildings: 40 × 52 = 2,080 work orders a year
• Monthly standby generator run at 12 sites: 12 × 12 = 144
• Quarterly service of 60 air-handling units: 60 × 4 = 240
• Annual thorough examination of 25 lifts: 25 × 1 = 25
• Total: 2,080 + 144 + 240 + 25 = 2,489 planned jobs a year, or about 48 a week before a single breakdown is logged

Contractors: response times, resolution times and warranty recovery

Most public bodies outsource part of their maintenance: lifts to the lift maker, fire systems to a specialist, and often a whole region to a facilities contractor. The CMMS must hold each contract's terms so that performance can be measured against them: covered assets and exclusions, response time, resolution time, the number of planned visits a year, and whether parts, labour and calibration are included.

Measure performance from your own timestamps, not from the contractor's monthly report. Example: a lift contract promises a 4-hour response. Over a year the council logs 200 call-outs and 170 are attended within 4 hours, so response compliance is 170 ÷ 200 = 85 per cent. Against a 95 per cent target, the council now has evidence for the contract review and for any deduction the contract allows; our guide on maintenance contract SLAs and penalty deductions shows how to price one.

Warranty recovery is the quieter loss. Suppose 30 corrective jobs in a year were on assets still under the manufacturer's warranty, each costing an average of €1,200 in external labour and parts, so €36,000 in total. If staff noticed and claimed only 12 of them, the council recovered 12 × €1,200 = €14,400 and paid €21,600 it did not need to. Flagging warranty status on the work order when it is raised, and tracking each claim's claimed, approved and recovered amounts, closes the gap.

Costs by asset, department and cost centre, against budget

Elected members and finance officers ask money questions: what does this building cost to maintain, which department is over budget, and is it cheaper to replace the boiler than to keep repairing it? To answer them, every work order needs labour, parts and external cost recorded against an asset, a department and a cost centre, and the maintenance budget must be held on the same cost centres.

Worked example. A library service has an annual maintenance budget of €180,000, phased evenly at €45,000 a quarter, so the budget after three quarters is €135,000. Work orders closed in the period show labour €62,000, parts €38,000 and external contractors €50,000, a total of €150,000. The service is €15,000 over budget to date, an overspend of 15,000 ÷ 135,000 = 11.1 per cent.

The cost detail then explains the variance. If €21,000 of the €50,000 contractor spend went on one heating system across 14 call-outs, the replacement case for that system is half written: the repair history is exactly the evidence a capital bid needs.

Buying a CMMS in the EU: MEAT, life-cycle cost and thresholds

In the EU, Directive 2014/24/EU requires contracting authorities to award public contracts on the basis of the most economically advantageous tender (MEAT, Article 67). MEAT is identified on price or cost using a cost-effectiveness approach such as life-cycle costing under Article 68, and may use the best price-quality ratio; award criteria can include after-sales service and technical assistance, and the weightings must be stated in the procurement documents. Article 68 lists the life-cycle costs to consider: acquisition, use (such as energy), maintenance and end-of-life costs.

EU procedures apply above thresholds. For 2026 and 2027, Commission Delegated Regulation (EU) 2025/2152 sets the threshold for supply and service contracts at €140,000 for central government authorities and €216,000 for sub-central authorities such as municipalities and regions (as of October 2026). A worked five-year life-cycle comparison of two CMMS offers:

• Offer A: implementation €40,000 + subscription €30,000 a year × 5 = €150,000 + data export at exit €5,000, total €195,000
• Offer B: implementation €15,000 + subscription €36,000 a year × 5 = €180,000 + data export at exit €12,000, total €207,000
• Offer A costs €12,000 less over the contract, although its first-year cost of €70,000 is higher than Offer B's €51,000
• At an estimated €195,000, a contract like Offer A would be above the €140,000 threshold for a ministry but below the €216,000 threshold for a municipality, which would then follow its national rules

Saudi Arabia and Canada: tendering and asset management plans

In Saudi Arabia, government purchasing falls under the Government Tenders and Procurement Law, issued by Royal Decree No. M/128 dated 13/11/1440H (16 July 2019) and in force since 1 December 2019, with Implementing Regulations issued by Minister of Finance Decision No. 1242 (19 November 2019). Tender procedures and documents for government entities are posted on Etimad, the Ministry of Finance's unified procurement portal. Keep the Etimad tender or contract reference against each maintenance contract so the procurement file and the maintenance record point to each other.

For government operation and maintenance, the national reference is the Expenditure and Projects Efficiency Authority (EXPRO). Its National Manual of Assets and Facilities Management, in 17 volumes, aims to unify asset and facilities management processes in government entities and includes volumes on maintenance management, work control and contracts management. Our guide on government facility management covers it in more detail.

In Canada, Ontario's O. Reg. 588/17 required municipalities to have asset management plans for core infrastructure (water, wastewater, stormwater, roads, bridges and culverts) by 1 July 2022 and for all other municipal infrastructure assets by 1 July 2024, and by 1 July 2025 every plan must include proposed levels of service, lifecycle activities and a financial strategy. Nationally, the Municipal Asset Management Program, funded by Infrastructure Canada and delivered by the Federation of Canadian Municipalities, builds municipal capacity. A CMMS is where the lifecycle activities in those plans are scheduled and evidenced.

RFP checklist for a government CMMS

Put these questions in the request for proposal and score the answers against the weightings you publish, as MEAT requires in the EU. Ask for a demonstration with your own data, not a scripted tour.

• Request intake: can staff and the contact centre log requests against a site and asset, and can a reviewer approve or reject them?
• Approval rules: can you set cost thresholds and force manual approval for urgent or safety-critical jobs?
• Planned maintenance: do schedules hold frequency, checklist, next-due date and approval status, and can you see what is due by site?
• Statutory records: can certificates be stored per asset with issue date, expiry date, issuing authority and the scanned document?
• Contracts: are response and resolution times and planned visits per year held per contract, with warranty claims tracked to recovery?
• Costs: are labour, parts and external costs captured per work order and reportable by asset, department and cost centre against budget?
• Audit and exit: is there an audit trail of changes, and can you export all records and attachments in a usable format at the end of the contract?
• Hosting and languages: where is the data hosted, which interface languages are offered, and what does regional hosting involve if your rules require it?

How Skyline Nexus ERP handles maintenance for public bodies

Skyline Nexus ERP includes a CMMS alongside its asset register and accounting, all part of the current Skyline Nexus ERP plans. Staff use Submit Request; reviewers approve a request, which converts it into a work order, or reject it. Work orders carry a type (Corrective, Preventive, Calibration, Installation or Acceptance), a priority, the asset and branch, start and completion times, downtime hours, labour, parts and external cost, a cost centre and a technician sign-off with signature. CMMS settings let you require approval, set a cost approval threshold and auto-approve by cost and priority, while critical priority always needs manual approval.

PPM Schedules hold the frequency (Daily to Annual), checklist, assigned engineer and next due date, and you raise each work order from its schedule or from the Planner view. Compliance Management stores certificates per asset with issue and expiry dates, issuing authority and the document; Contracts hold response and resolution hours and visits per year; Warranty Claims track claimed, approved and recovered amounts. Each site is a business location, so a council can run many sites under one account with users limited to their permitted branches. Reports include Maintenance Costs, Department Costs, Downtime Analysis and PPM Compliance, and on the finance side Budgets and the Budget vs Actual report compare the ledger's actual spending, such as posted contractor invoices, with budget by account and cost centre.

CMMS screens are available in English, Arabic, German, French, Spanish and Italian. Skyline Nexus ERP is a cloud service hosted in the EU (Frankfurt), with regional hosting on request. Try the free month or book a demo, and we will walk through your sites, assets and approval rules with you.