If you maintain elevators, fire alarm systems, industrial HVAC, or emergency power equipment, you already know that generic field service management software was not built for you. The platform designed for a heating and plumbing company, where a missed appointment means a cold house for a day, is a poor fit for a business where a missed inspection means a trapped passenger, a failed fire alarm, or a refrigeration unit losing a consignment of pharmaceuticals overnight.
This guide is for service directors, operations managers, and IT leads at companies with 5–200 technicians who are either evaluating FSM platforms for the first time, replacing something that stopped scaling, or wondering whether their current spreadsheets-and-email approach has a ceiling they're about to hit.
We will cover what distinguishes critical infrastructure FSM from standard field service software, the features that matter by vertical, compliance tracking requirements, mobile app capabilities, and the practical questions to ask vendors before signing anything.
Why critical infrastructure is a different category
The FSM market broadly divides into two customer segments. The first serves residential and light commercial trades, plumbing, electrical, landscaping, pest control, HVAC maintenance for single-family homes. These businesses care about scheduling efficiency, invoicing speed, and customer communications. Their risk profile is low; a callback means an irritated customer, not a regulatory investigation.
The second segment, which is where this guide lives, covers assets where failure has legal, financial, or life-safety consequences. The characteristics that define this segment are worth being explicit about.
Regulatory obligation, not optional maintenance. An elevator in a commercial building in the UK must be inspected under LOLER every six months. A fire alarm system under BS 5839-1 requires at minimum two contractor visits per year, with quarterly visits for higher-risk premises. An HVAC system containing more than 3kg CO2-equivalent of F-Gas refrigerant requires annual leak checks under EU Regulation 517/2014 and the UK equivalent. These are not recommendations. Your client faces enforcement action, your company faces liability, and in some cases individual engineers face personal prosecution if records cannot be produced.
Phone-to-asset identification. In elevator maintenance, every lift shaft contains a mandatory two-way communication device connected to a dedicated telephone line or SIM. When a passenger is trapped and activates the alarm, the incoming call identifies the specific shaft, not just the building, the shaft. A generic CRM that logs this as a call from "ABC Property Management" wastes the 20–30 seconds needed to ask which building and which elevator before dispatch can act. When your SLA for trapped passenger response is 90 minutes from first contact, those 20 seconds become a documented gap if things go wrong.
Fire alarm panels, GSM dialers on refrigeration units, telemetry modules on remote pumping stations, all of these generate inbound calls and alerts that carry an asset identity in the calling number. Software that misses this is making your dispatchers slower under pressure.
Multi-standard compliance tracking. A single maintenance company operating across elevators, fire safety, and HVAC will have technicians working to obligations under ASME A17.1, EN 81-20, EN 81-28, BS 5839-1, BS 5839-6, EN 54, NFPA 72, F-Gas Regulation 517/2014, LOLER 1998, PSSR 2000, EN 13241, and BS 6266, depending on geography and contract type. Each standard has different inspection intervals, different documentation requirements, and different competency thresholds for the engineers performing the work. No single spreadsheet handles this coherently once you get above 50 contracts.
Consequence of getting it wrong. A missed preventive maintenance visit for a domestic boiler leads to a cold house and an unhappy customer. A missed six-monthly inspection for a traction elevator leads to a prohibition notice, a closed elevator shaft, and a building owner with legal exposure. The documentation gap is not a minor CRM problem, it is evidence in an enforcement action or a civil claim.
Feature checklist: what to evaluate
Use this list when assessing any FSM platform. Not every feature is relevant to every company, but this covers the scope that a critical infrastructure maintenance business will encounter as it grows.
Core work order management
- Work order creation from inbound call, email, customer portal, or automated rule
- Asset linkage, every work order attached to a specific asset with its full service history
- Priority tiers that map to contract SLAs (emergency, urgent, high, standard)
- Status workflow with timestamps at each transition (created, assigned, en route, on site, completed, invoiced)
- Follow-up work order creation from within a completed job (defect-to-remedial workflow)
- Work order templates per asset type, with pre-populated checklist items
SLA and contract management
- Contract storage with individual SLA definitions per contract
- SLA clock that starts at work order creation, not at assignment
- Real-time SLA breach warnings, not just post-breach reports
- Contract expiry tracking with automated renewal reminders
- Coverage tracking, which assets are under contract, which are ad-hoc only
- Planned preventive maintenance (PPM) scheduling that generates work orders automatically based on contract frequency
Asset and compliance management
This is where most generic tools fall short.
- Asset register with custom fields per vertical (elevator: car capacity, traction/hydraulic/MRL, shaft count; fire panel: panel type, protocol, zone count; HVAC: refrigerant type, charge weight, GWP value)
- Standards compliance matrix per asset, which standards apply, what intervals, what documentation is required
- Certificate and inspection record storage attached to the asset
- Expiry date tracking for time-limited certificates with configurable warning periods
- Automatic next-visit scheduling from completed service records
- Defect tracking from discovery to remediation with notification to client
Dispatch and scheduling
- Skills-based assignment, only engineers with the required competency are offered for a given job type
- Real-time technician location and availability
- Travel time estimation integrated into scheduling
- Drag-and-drop scheduling board with capacity view
- Automated assignment based on proximity, skills, and workload
- Emergency interrupt, ability to reassign a technician mid-job without losing the original job record
Mobile application
- Offline operation, full job data available without network connectivity
- Checklist capture with mandatory field enforcement (engineer cannot complete job without filling required fields)
- Photo attachment with GPS and timestamp metadata
- Customer signature capture on site
- Parts consumption recording per job
- Real-time sync when connectivity resumes
- Multi-language support for international or multilingual workforces
Inventory and parts management
- Parts catalogue with supplier, part number, and reorder point
- Van stock tracking per vehicle
- Parts usage attached to work orders for job costing
- Low-stock alerts and reorder workflows
- Return-to-stock process for unused parts
Reporting and analytics
- First-time fix rate by engineer, asset type, and customer
- Mean time to repair by priority tier
- SLA compliance rate per contract and per client
- Technician utilisation (productive hours vs. total hours)
- Repeat call rate (work orders reopened within 30 days)
- Compliance certificate expiry dashboard
Integration and API
- REST API with documented endpoints
- Webhook outbound events for work order status changes
- Accounting system integration (Xero, QuickBooks, Sage)
- ERP integration (SAP, Oracle) for larger operations
- Telephony integration for inbound call handling
- Customer portal for self-service work order submission and tracking
Vertical-specific requirements
Elevators and escalators
The elevator vertical has a feature requirement that no general FSM platform addresses by default: phone-to-shaft mapping.
EN 81-28:2018 (remote alarm systems for passenger and goods passenger lifts) requires every lift to have a two-way voice communication device connecting passengers in the car to a 24/7 monitoring point. That monitoring point is your emergency control room or answering service. The incoming call carries the DID number assigned to that specific shaft. Your software needs to resolve that number to the exact lift, car number, building, floor levels served, emergency contacts, before your operator picks up.
The practical requirement list for elevator FSM:
- Phone number registry mapping each DID to a specific asset (shaft) record
- Automatic asset identification from inbound call presentation
- Trapped passenger workflow with SLA clock starting at call pickup
- EN 81-28 compliance tracking, two-way communication device test records
- LOLER (UK) or equivalent periodic inspection certificate tracking (six-monthly intervals)
- Competency tracking, engineers authorised to work on traction vs. hydraulic vs. MRL installations
- Modernisation project support, ability to track multi-visit projects against a single asset record
- Out-of-service record with client notification and estimated return-to-service date
For ASME A17.1 compliance (North America), the test and inspection categories differ, but the underlying requirement, documented test intervals, witnessed tests, certificate issuance, maps directly onto the same platform needs.
Full details on EN 81-28 compliance documentation requirements are covered in our elevator maintenance compliance guide.
Fire safety systems
Fire alarm maintenance under BS 5839-1 and EN 54 has more documentation requirements per visit than almost any other maintenance vertical. An annual service for a medium-sized addressable system might generate 40–60 individual test records (one per device) plus panel diagnostics, battery test data, and signalling confirmation from the Alarm Receiving Centre.
Vertical-specific requirements:
- Site and zone structure within the asset record (panel → zone → device)
- Zone rotation tracking for weekly user tests (rolling confirmation that all zones have been tested within the required period)
- Detector sensitivity log capture, addressable panel diagnostic data per device
- Battery load test record with measured values, not just pass/fail
- Cause-and-effect matrix documentation per annual service
- ARC signalling test log with confirmation timestamp
- Defect notification workflow, written notification to responsible person with device reference, fault description, and system capability assessment
- BS 5839-6 vs. BS 5839-1 tagging for mixed residential/commercial contracts
- BS 5839-1 Clause 45.1 compliance, site log book generated and stored per premises
For suppression systems (FM-200, Novec 1230, CO2, inert gas), additional records are required per the relevant standard (BS 15004, ISO 14520). If your company maintains both detection and suppression assets, the platform needs to handle both without a separate database.
Critical HVAC and refrigeration
The regulatory burden in HVAC is primarily driven by F-Gas Regulation EU 517/2014 and its UK equivalent. Every company that installs, maintains, or services equipment containing fluorinated greenhouse gases must hold the relevant F-Gas certificate, maintain equipment logs, and in some cases report to national registers.
The critical data capture requirements per refrigerant-containing unit:
- Refrigerant type and charge weight per unit
- F-Gas leak check interval (annual for 3–30kg CO2e; bi-annual for 30–300kg CO2e; quarterly for >300kg CO2e)
- Leak check records with engineer certificate number
- Refrigerant addition and recovery log per visit with batch/cylinder reference
- F-Gas log book requirement, this is a legal document that must be kept for at least 5 years
- Engineer F-Gas certificate number captured on records (category-specific)
For cold chain and food-critical refrigeration:
- Temperature excursion logging and root cause documentation
- Scheduled temperature compliance checks between PPM visits
- HACCP audit trail, documentation that refrigeration systems maintained specified temperatures
For data centre and server room cooling, the additional requirement is uptime-focused rather than regulatory:
- Chiller and AHU runtime hours tracking for interval-based maintenance
- Redundancy status, which units are duty, which are standby
- Alarm integration with BMS or DCIM systems
Access control and automatic gates
EN 13241:2003+A2:2016 (industrial, commercial, and garage doors) and EN 12453:2017 (safety in use of power-operated pedestrian doorsets) define the maintenance obligations for automatic gates, barriers, and door systems. These are enforced through product liability law rather than a regulatory inspection regime, which means the risk lands directly on the maintenance company if an incident occurs and records are absent.
Specific requirements:
- Force measurement records per annual service (closing/opening forces, EN 12453 limits)
- Safety edge and loop detector test records
- Battery backup test for barrier and gate operators
- Photo evidence at each service, courts have asked for this in personal injury claims
- Compliance declaration storage per installation (DoP, Declaration of Performance)
For access control panels (PACP), card readers, and biometric systems:
- Access control system configuration backup record
- Anti-passback and time-zone rule verification record
- Battery backup test on panel and door hardware
- Integration test with fire alarm system (fail-safe override on fire signal)
Emergency power systems (generators, UPS, ATS)
BS 6266:2011 (fire protection for electronic equipment installations) and BS EN 62040-3 (UPS performance) apply to this vertical. Beyond these, most generator and UPS maintenance is governed by insurance requirements and owner's risk policies rather than a single enforced standard.
The documentation requirements are nonetheless detailed:
- Generator load test records, load bank testing at minimum 70% of rated output, typically quarterly
- Monthly no-load start test records with run time and output voltage
- Fuel stock level and fuel polishing records (contaminated fuel is the most common cause of generator failure on test)
- ATS (Automatic Transfer Switch) exercise and transfer time measurement
- UPS battery capacity test records, measured capacity vs. rated capacity, with replacement threshold
- Battery age tracking, most VRLA batteries have a 4–5 year replacement cycle, AGM may be shorter in high-temperature installations
- DRUPS (Diesel Rotary UPS) speed and flywheel inspection records
Building management systems
BMS maintenance sits across multiple disciplines, HVAC controls, lighting automation, access, energy monitoring. The platform requirement is less about regulatory compliance and more about change management documentation:
- BMS programme version control, what was changed, when, by whom
- Point-to-point test records for I/O commissioning and recommissioning
- Alarm and fault code log with resolution records
- Energy baseline documentation before and after optimisation changes
- Protocol documentation per site (BACnet, Modbus, KNX, LON)
- Integration test records for BMS-to-fire, BMS-to-access, and BMS-to-UPS interfaces
Compliance tracking: what the software must do
A maintenance company operating across two or more of the verticals above will be working to 20–30 distinct standards simultaneously. Manually tracking which certificates are due, which visits are overdue, and which assets have open defects is functionally impossible above a certain portfolio size, typically around 150–200 assets under management.
The software needs to handle compliance tracking at three levels.
Asset-level compliance status. Each asset should show at a glance: current certificate status, date of last service, next service due, open defects, and any overdue items. A traffic-light system is the correct UX here, not a list of dates that someone has to mentally process.
Contract-level compliance status. A portfolio view across all assets under a given contract showing PPM completion rate, overdue visits, and certificate health. This is what a service manager needs to prepare for a client review meeting.
Regulatory interval enforcement. The platform should know the required service interval for each asset type and standard, and flag overdue items automatically. This means the platform needs a configurable rules engine, not just a manual reminder field. "LOLER inspection every 6 months" and "F-Gas leak check annually for 3–30kg CO2e units" are different rules for different assets, the software should enforce them, not the service manager's memory.
Mobile app: what your technicians actually need
A field service mobile app that lacks offline capability is not a field service mobile app. It's a mobile website with a poor antenna. Engineers working in lift shafts, plant rooms, underground car parks, and data centre cold aisles routinely lose connectivity mid-job. The app must store the full job data locally and sync when network is available.
Beyond offline support, the mobile app requirements for critical infrastructure are:
Structured checklist capture. For a BS 5839-1 annual service, the checklist is 40+ items. The app needs to enforce completion, an engineer cannot mark a job done without closing all mandatory items. This is not about trust; it's about having auditable records that confirm each task was addressed.
Photo capture with evidence-grade metadata. Photographs should carry GPS coordinates, timestamp, and the engineer's identity. For access control and gate maintenance, where injury claims can arise years after a service, photo evidence is the difference between a clear defence and an extended claim process.
Electronic signature capture. Customer signature on the service record, on site. This eliminates the "we never received the service report" conversation.
Multi-language support. If your company operates across more than one country, or employs technicians who work in their native language rather than the country's majority language, the app needs to present forms, checklists, and navigation in the engineer's preferred language. This is not a nice-to-have when you have Polish-speaking engineers on UK sites, Ukrainian-speaking engineers in German operations, or Slovak technicians working in Czech facilities.
Parts consumption recording. Engineers must be able to record parts used on a job against the van stock, with the record tied to the work order for job costing and reorder triggering.
AI and automation capabilities
The FSM market has spent the last two years adding AI labels to features that were already algorithmic. When evaluating platforms, the distinction worth making is between genuine decision support and rebranded scheduling rules.
Automatic asset identification from inbound contacts is not AI in the conventional sense, but it requires the software to resolve an incoming phone number or email address to a specific asset record in under two seconds. For the elevator and fire alarm verticals, this is the single highest-value automation in the entire platform. The time saving is minimal; the reduction in dispatcher error under pressure is significant.
Smart dispatch, the software suggesting or automatically assigning the right technician to a job based on location, skills, current workload, and SLA priority, is worth evaluating carefully. The feature is only as good as the underlying data: skills must be accurately recorded, technician locations must be live, and SLA priorities must be correctly configured. A platform that dispatches the nearest engineer rather than the nearest certified engineer creates compliance risk.
AI copilot for operations managers. The more recent generation of FSM platforms is embedding conversational AI for operational queries: "Which contracts have assets with overdue certificates this month?" or "Which technicians have the highest repeat-call rate on elevator door operators?" This replaces what was previously a reporting exercise that required someone to build a custom filter or write a query. For operations managers managing 50+ technicians across multiple verticals, the ability to ask natural-language questions of the data is a genuine time saving.
Automated certificate generation. After a completed service visit, the platform should generate the inspection certificate automatically from the captured records, in the correct format for the standard. For BS 5839-1 services, this means a document that includes device test records, battery data, ARC confirmation, and the service engineer's details. For LOLER thorough examinations, it means an examination report meeting Schedule 1 of the Regulations. Manual certificate generation from field notes is where errors and omissions occur.
SLA management and contract tracking
SLA management in critical infrastructure is more layered than it appears. A single contract might define:
- Response time from first contact to technician on site (e.g., 4 hours for urgent, 8 hours for standard)
- Resolution time from arrival to system restored to service
- PPM completion rate across the contract period (e.g., 95% of scheduled visits completed within ±7 days of due date)
- Certificate availability, inspection certificates issued within 5 business days of visit
Most generic FSM platforms track only response time. The others require configuration that many platforms cannot support.
The SLA clock start point matters. In most contracts, the SLA clock starts when the client reports the fault, not when the work order is created in your system. If there's a 15-minute delay between the client's call and your dispatcher creating the work order, those 15 minutes count against your SLA. Software that starts the clock at work order creation understates your response time compared to contractual reality.
Breach notifications must be pre-breach. Receiving a notification that an SLA was breached is information with zero operational value. The notification needs to arrive 60–90 minutes before the breach threshold, while there is still time to act. An emergency reallocation at T-90 minutes is possible; at T+0 it is a report with a paper apology.
Inventory and fleet management
For maintenance companies where technicians carry stock in vans, inventory management is directly connected to first-time fix rate. An engineer who arrives at a fan coil unit fault without the correct capacitor, or at a fire panel without the correct detector replacement, generates a return visit that costs the same as the first visit with none of the revenue.
The chain of custody requirement for van stock:
- Parts received into central warehouse stock, recorded against a purchase order
- Parts transferred from warehouse to van stock before or during a job allocation
- Parts consumed on a job, recorded against the work order with the quantity used
- Unused parts returned to van stock or warehouse stock with the same traceability
Companies that skip steps in this chain lose track of where stock is and cannot reconcile job costs against parts usage. The minimum platform requirement is a parts catalogue, van stock visibility per vehicle, and parts usage recording per work order.
Fleet management. For companies with more than 5 vehicles, the platform should track vehicle service intervals, MOT and insurance expiry dates, and mileage logs. This is less about asset maintenance (your vehicles are not critical infrastructure) and more about operational risk, a van with an expired MOT on a customer site is a reputational and legal exposure.
Integration requirements
A growing maintenance company will eventually need its FSM platform to talk to other systems. The integration requirements to evaluate:
Accounting systems. Work order completion should trigger invoice generation, with parts, labour, and any agreed surcharges populated automatically. Manual re-entry between FSM and accounting software is where billing errors accumulate. Xero and QuickBooks are the most common targets for smaller operations; Sage and SAP for mid-market and enterprise.
Customer portal. Clients with large property portfolios expect to see their asset status, service history, and open defects without calling your office. A self-service portal reduces inbound calls and creates a transparent record that supports contract renewal conversations.
ERP systems. For larger organisations (50+ technicians, multiple business units), integration with an ERP for procurement, HR, and financial consolidation becomes necessary. This typically requires a documented REST API rather than pre-built connectors.
Telephony systems. For elevator and fire alarm companies, this is not optional, it is the core feature. The platform must integrate with your VoIP or PBX system to receive inbound call events and resolve them against the asset registry in real time.
IoT and remote monitoring. As elevator door controllers, fire panel communication modules, and refrigeration units gain connectivity, the platform needs to receive automated alerts from those devices and generate work orders without human dispatch involvement. The trigger is a machine event (door fault code, panel zone fault, temperature excursion); the response is an automatically created work order assigned to the correct on-call technician.
Self-assessment: is your current system failing you?
Before committing to a platform evaluation, work through these questions. They are not rhetorical, they identify the gaps that cost you money and compliance exposure.
Compliance tracking
- Can you produce, within 10 minutes, a list of every asset under management with an overdue inspection certificate?
- If a fire authority inspector asks for the service history of a specific panel you maintain, can your team pull the complete record, including device test data and defect notifications, without contacting the engineer who did the last visit?
- Do you have an automated process for tracking F-Gas log book requirements, or does this sit in a spreadsheet someone updates manually?
Operations and dispatch
- When a trapped passenger call comes in, does your dispatcher know the exact shaft identity, building address, and emergency contact before picking up the phone, or do they have to ask?
- When an engineer goes on sick leave, can you identify every job assigned to them for the next two weeks, their open defects, and the van stock they're carrying, in under five minutes?
- What is your actual SLA compliance rate for the last quarter, broken down by contract? If you cannot answer this from memory and it would take more than 30 minutes to produce the data, the system is not working for you.
Technician experience
- Are your engineers completing paper-based or PDF service records that someone then re-enters into a back-office system?
- Do technicians regularly arrive at jobs without the parts they need because van stock is tracked in a separate spreadsheet?
- Do your engineers work in more than one language, and if so, are they using the system in a language that is not their first?
Business risk
- If your largest client requested an audit of all service records for their assets in the last 24 months, how long would it take to compile the documentation?
- When was the last time you discovered an overdue PPM visit only because the client called to ask where the engineer was?
Pricing models in the FSM market
FSM platforms price in three main ways, and the differences become significant at scale.
Per-technician pricing. You pay a monthly fee per field technician, typically in a range of £40–£150 per technician per month depending on the platform tier. This model is straightforward and scales directly with field headcount. The downside is that back-office users (dispatchers, managers, administrators) may be charged at the same rate, which inflates cost for companies with high dispatcher-to-technician ratios.
Per-user pricing. A flat fee per seat, regardless of role. More common in platforms targeting the enterprise market. The advantage is simplicity; the disadvantage is that an operations team with 60 technicians and 8 office staff pays for 68 seats including 8 people who generate no field revenue.
Flat rate (unlimited users). Some platforms charge a flat monthly fee with unlimited users, differentiated by feature tier. This model works well for growing companies where adding a user shouldn't require a budget conversation. The risk is that the flat rate may be high enough to be poor value at small scale.
Usage-based add-ons. Several platforms charge separately for features like SMS notifications, outbound call integration, advanced API access, or high-volume data storage. These add-ons are easy to miss in the initial evaluation and can materially change the total cost at scale. Always ask vendors for a total cost illustration at your current size and at 2x your current size.
When comparing platforms, calculate cost per work order completed rather than cost per user, this normalises across pricing models and reflects the actual value you're purchasing.
Migration considerations
Switching FSM platforms is not a weekend project. The practical considerations that are frequently underestimated:
Data import. Asset records, service history, and contract data accumulated over years represent significant business value. Before selecting a platform, confirm: can the vendor import asset records in bulk from CSV or Excel? Can they import historical service records? What is the standard format they accept, and what will it cost?
Historical compliance records. For critical infrastructure companies, historical service records are not just operational data, they are legal evidence. If you cannot migrate five years of fire alarm service records into the new platform, you need a parallel archive that is accessible, searchable, and preserved.
Training timeline. Field technicians adopting a new mobile app need 2–4 hours of training to be productive on basic jobs. Back-office users adopting a new dispatch and contract management system need a week of supervised use before they stop reverting to the old system under pressure. Plan for a 4–8 week parallel-running period where both systems are live.
Go-live timing. Do not switch platforms during your busiest season. For most critical infrastructure companies, Q1 and Q4 carry the highest reactive call volumes. Go live in Q2 or Q3. Do not go live during the week before a major client contract review.
Technician buy-in. FSM migrations fail more often from technician resistance than from technical problems. Engineers who have been completing paper records for 10 years will not spontaneously adopt a new mobile app unless they understand why it benefits them. The platforms that succeed in field rollouts are the ones with mobile apps that make the engineer's job easier, faster job access, pre-populated checklists, parts availability visible before departure, not platforms that feel like surveillance tools.
Frequently asked questions
What is the difference between field service management software and a CMMS?
A CMMS (Computerised Maintenance Management System) focuses on the asset, preventive maintenance scheduling, work order history, and asset lifecycle. An FSM platform focuses on the service delivery, dispatching technicians, managing customer relationships, handling inbound calls, and invoicing. Modern FSM platforms for critical infrastructure increasingly combine both, because an elevator maintenance company needs asset lifecycle tracking (CMMS) as well as dispatch management and SLA tracking (FSM). If a vendor uses one term, ask explicitly whether the other capability is included.
How many technicians do you need before FSM software makes financial sense?
At 3–4 technicians, the administrative overhead of managing work orders, scheduling, and compliance records manually starts to become a part-time job for someone in the office. Most companies find the crossover point, where the platform cost is less than the labour it saves, at around 5 technicians. For critical infrastructure companies with compliance obligations, the business case is stronger at lower headcount because the cost of a missed inspection or a lost service record is not just administrative inconvenience.
Does FSM software replace a CAFM system?
Not typically. CAFM (Computer-Aided Facilities Management) systems are used by building owners and facilities managers to manage the assets they own and the contractors who service them. FSM software is used by the contractor side to manage the work they perform. Some large in-house facilities teams use an FSM-type tool for their own engineering teams, but the systems are solving different problems from different sides of the same relationship.
What is the typical implementation timeline?
For a company with 10–30 technicians replacing an existing system, a realistic timeline is: 2–4 weeks for data migration and system configuration, 1–2 weeks for internal user training, 2–4 weeks of parallel running. Full adoption, where the old system is no longer being checked and all records are in the new platform, typically takes 3–4 months. Vendors who promise full deployment in one week are describing the go-live date, not the adoption timeline.
How should we handle compliance records for assets that were serviced before we implemented FSM software?
Import or scan historical records and attach them to the asset record in the new system, even if they are PDFs of paper records rather than structured data. The goal is a single-source record per asset. Courts and regulators are not concerned about whether records are typed or scanned, they are concerned about whether records exist and whether they are retrievable. An asset with five years of PDF service records attached to its record is more defensible than an asset with five years of records in a filing cabinet in a different building.
Choosing the right platform
The right FSM platform for a critical infrastructure maintenance company is the one that treats the asset, the elevator shaft, the fire panel, the chiller, as the primary entity around which everything else is organised. Work orders happen to assets. Contracts cover assets. Compliance obligations attach to assets. If a platform is primarily designed around jobs or customers, it will require workarounds that accumulate over time into operational friction.
The features that distinguish platforms built for this vertical from those adapted from general trade software are: phone-to-asset mapping, standards-aware compliance intervals, and multi-language mobile support. A platform that handles all three was designed for this work. One that handles none of them was not, regardless of what the sales deck says.
The companies that get the most value from FSM platforms are the ones that configure the asset registry properly before go-live, train technicians to capture data at the point of work rather than back at the depot, and use the reporting tools to have better conversations with clients about asset condition and service history.
Explore how RemoteOps handles the specific requirements of each vertical: Elevators & Escalators, Fire Safety, Critical HVAC, Access Control & Gates, Emergency Power, Building Management Systems. See pricing for current plans.