Upstream CMMS scoping starts in the field
Before approaching a CMMS vendor or integrator, organisations must assess the assets to be maintained, maintenance processes, data to be migrated, mobile use cases and interfaces with the wider IT landscape. In water and wastewater operations, GIS, equipment master data and field constraints must be addressed from the scoping stage.
Scoping must examine how teams prepare, carry out and close maintenance tasks. It must also distinguish between business processes, field operations, data, software configuration and interfaces with the wider information system.
Assets, equipment and technical hierarchy
The technical hierarchy determines the quality of the entire CMMS. It must make it possible to find equipment, track its history, schedule maintenance and produce actionable reports. A hierarchy that is too detailed becomes impossible to maintain, while one that is too limited prevents effective analysis of incidents and costs.
Before going to tender, the required levels must therefore be defined: site, facility, area, equipment, sub-equipment, meter, device or critical component. The right level depends on the intended uses, including preventive maintenance, on-call support, regulatory monitoring, inventory, costs, availability and traceability.
Master data and data quality
The master data to be scoped includes equipment, locations, technical categories, maintenance procedures, parts, suppliers, contracts, teams, authorisations and maintenance priorities. This data must be assessed before import, as late migration often delays configuration, acceptance testing and field deployment.
CMMS data migration must be prepared before final configuration. Equipment, locations, technical hierarchies, maintenance histories, inventory and maintenance procedures must be assessed before import. The scoping phase must specify what will be migrated, cleansed, discarded or rebuilt.
Preventive and corrective maintenance, mobility and inventory
Preventive maintenance requires clear procedures, justified frequencies and well-defined responsibilities. Corrective maintenance requires straightforward request classification, clear priorities and a closure process that produces actionable information. Field mobility must be designed around real operating conditions: areas without network coverage, rapid data entry, attachments, photos, signatures and geolocation where useful and authorised.
Inventory processes must be scoped with maintenance and finance teams, covering critical parts, thresholds, issues, returns, valuation, stocktaking and potential links with procurement. A theoretical inventory accuracy target should not be promised without confirming the organisation’s actual ability to keep the data current.
Interfaces to clarify before going to tender
A CMMS may need to exchange data with a GIS, ERP, customer information system, supervisory control system, request portal, finance solution or HR master data system. Each interface must be described in terms of its purpose, exchanged data, frequency, flow direction, owner and expected controls.
GIS is often central to water and wastewater operations, but it does not replace the maintenance hierarchy. Organisations must decide which system is the authoritative source for each type of data and how discrepancies will be detected.
Tendering, acceptance testing and deployment
The tender documentation must reflect priority use cases without locking the project into a predetermined solution. Selection criteria must cover functional fit, data migration, mobility, interfaces, field usability, administration capabilities and implementation commitments.
Acceptance testing must not focus solely on screens. It must replay business scenarios: creating a request, converting it into a maintenance task, assignment, field data entry, issuing inventory, closure, verification, reporting and correcting an error. Deployment must include training, go-live support, final data migration and data governance rules.
For support with requirements scoping, tendering, data migration and acceptance testing, see our CMMS advisory services. When the CMMS forms part of a broader programme, scoping may also be covered by our IT project advisory and transformation management services.
Are you preparing a tender or data migration for a water, wastewater or technical services CMMS? Discuss your CMMS scoping requirements.