Multi-Site Asset Register with PM Alerts

What should one multi-site asset register hold?

A multi-site asset register should hold one record per maintainable asset with a unique ID, its place in a site and system hierarchy, its physical location, a criticality rating, and the links that drive maintenance: PM plans, meters, warranties and parent assets. Every site uses the same fields, so head office can compare them directly.

• Asset ID: A unique, permanent identifier that stays the same when an asset moves between sites or gets a new name.
• Hierarchy: Site, building or area, system and asset, with child components where they are maintained separately, such as the motor on a pump.
• Location: The room, zone or coordinates where a technician will find the asset, held apart from the hierarchy so a move does not break history.
• Criticality: A rating on a small fixed scale, such as high, medium and low, based on the safety, production or patient impact if the asset fails.
• Class and attributes: The asset class, such as chiller, forklift or infusion pump, with the attributes that class needs.
• Maintenance links: PM plans, meters, warranties, manuals, service contracts and the work order history.

Keep location and hierarchy apart. A portable generator belongs to one system on paper but sits in a different room every week, and mixing the two means editing the hierarchy each time it moves.

How should assets be named and tagged across sites?

Use one naming standard for every site, written down before any import, with IDs that carry no meaning that can go out of date. Descriptive names and codes belong in separate fields.

Meaningful IDs such as BLDG2-AHU-03 look tidy until the unit moves or the building is renamed. Then the ID is wrong, or the history breaks when someone edits it.

• Asset ID: Generated by the system, unique across all sites, printed on the tag and never reused after disposal.
• Display name: A short readable label built from a fixed pattern, such as class, area and number, which can change without touching history.
• Class codes: One shared list of asset classes and attributes, owned centrally, so a pump at one site is a pump at every site.
• Tags: A durable label with a barcode or QR code that encodes the asset ID, fixed where it can be scanned without removing guards or panels.
• Legacy numbers: Old site numbers kept as a searchable field, so technicians can still find assets by the number they know.

Published taxonomies can save design time in some sectors. In oil, gas and petrochemical plants, ISO 14224:2016 covers the collection and exchange of reliability and maintenance data for equipment, and aligning class codes with it makes failure data easier to compare between sites and with partners.

How do you import assets from spreadsheets and an existing CMMS?

Import in stages: map every source to the new standard, clean and deduplicate in a staging area, load one pilot site, and reconcile it against a physical walk before loading the rest. A single bulk load from every source copies each site's errors into the new register.

• 1. Inventory sources: List every spreadsheet, legacy CMMS, ERP fixed asset list and contractor record that holds asset data, with an owner for each.
• 2. Map fields: Match each source column to the new standard, with a written rule for every value that needs translating.
• 3. Stage and clean: Load into a staging area, flag duplicates, missing IDs and orphan components, and fix them there rather than in the live system.
• 4. Bring history selectively: Carry over open work orders, active PM plans, meter readings and recent history, and archive older closed work orders in a read-only store.
• 5. Pilot one site: Load it, walk the floor with a scanner, and correct what the walk finds before moving on.
• 6. Freeze the old system: Make the legacy tool read-only once a site is live, so two registers never drift apart again.

Expect the walk to change the data: scrapped equipment, unrecorded units and items listed twice under two names are each cheaper to fix during the pilot than after go-live.

Should PM schedules run on time, meter or condition?

Most registers need all three. Time-based PM suits inspections and statutory checks, meter-based PM suits assets whose wear follows use, and condition-based PM suits critical assets where a reading shows decline before failure.

• Time-based: A fixed interval, such as monthly or yearly. Simple and predictable, but it services lightly used assets as often as busy ones.
• Meter-based: Triggered by run hours, cycles, distance or units produced. It depends on reliable meter readings, entered by technicians or fed from the equipment.
• Condition-based: Triggered when a reading crosses a limit, such as vibration, temperature or pressure drop across a filter. It needs sensors or regular readings and a clear limit for each asset class.
• Combined: A set number of run hours or a calendar interval, whichever comes first. A common pattern for vehicles and rotating equipment.

Choose fixed or floating schedules deliberately. A fixed schedule keeps the next due date even when the last job was late, which suits compliance checks. A floating schedule counts from the last completion, which suits wear-based work. Start from manufacturer intervals per asset class, and let failure records justify any change.

How should PM alerts be routed and escalated so they get acted on?

PM alerts get acted on when each one goes to a named person or team for that site and asset class, arrives as a work order rather than an email, and escalates on a clock if nobody accepts it. Alerts sent to everyone are treated as noise by everyone.

• Generate work, not messages: Create the work order with a due date and a lead time that suits the job, so planners can arrange parts and access.
• Route by rule: Use site, asset class, trade and criticality to choose the assignee, with a backup rule for leave and vacancies.
• Escalate on time: If a high-criticality job is not accepted within a set window, notify the site supervisor, then the regional manager. Lower criticality jobs escalate later or roll into a weekly review.
• Bundle by location: Group jobs due in the same plant room in the same week, so one visit clears several.
• Record the reason: When a PM is deferred or skipped, require a reason code, so repeated deferrals on one asset show up in reports.

Watch the PM workload per technician after go-live. If a site gets more work orders than its team can finish, change frequencies or staffing instead of letting overdue work pile up.

How do technicians work on mobile when a site has no signal?

Technicians work without signal when the mobile app is built offline first: it downloads their jobs, asset records and checklists before the shift, records everything on the device, and syncs when a connection returns. Plant rooms, basements, rooftops and remote sites often have weak or no coverage.

• Local data: Cache assigned work orders, their assets, procedures, checklists and recent history.
• Scan to confirm: Scanning the asset tag opens the right record and shows the technician was at the asset.
• Sync and conflicts: Queue changes with timestamps and resolve conflicts with written rules, such as the latest meter reading wins and a closed work order cannot be reopened offline.
• Found assets: Let technicians add an untagged asset as a pending record that a central administrator approves, so the register grows without new duplicates.

Close-out screens should capture what an audit needs. For process equipment covered by OSHA's process safety management standard, 29 CFR 1910.119(j)(4)(iv) requires each inspection and test to be documented with its date, the name of the person who performed it, the serial number or other identifier of the equipment, a description of the inspection or test, and its results.

Make those fields mandatory on the mobile form, and fill the name and equipment ID from the login and the tag scan, so records are not written up from memory after the shift.

How do fixed assets and software licenses fit in the same register?

Fixed assets and software licenses fit as linked views of one register: finance sees cost, depreciation and disposal, IT sees entitlements and renewals, and maintenance keeps the service record. A shared asset ID ties the three together, so nobody keeps a parallel list.

Finance may group many items into one fixed asset, while maintenance tracks each item it services. A mapping table between maintenance assets and fixed asset numbers lets both teams keep their own grain.

• Finance view: Acquisition cost, capitalization date, cost center, depreciation method and disposal, synced with the ERP fixed asset module rather than retyped.
• Lifecycle cost: Maintenance labor and parts rolled up per asset, so repair or replace decisions use actual spend.
• Software licenses: Entitlements, seat counts, versions, renewal dates and the devices or users they are assigned to, with renewal reminders routed the same way as PM alerts.
• Embedded software: Firmware and control software versions recorded against the equipment they run on, so a vendor advisory can be matched to the affected assets.

ISO/TC 251, the ISO committee for asset management, lists ISO 55000:2024 for vocabulary, overview and principles and ISO 55001:2024 for asset management system requirements, and states that its standards apply to all types of assets and to all organizations. Managing licenses as assets fits within that scope.

What should reporting across sites show?

Reporting across sites should show PM compliance, overdue work by criticality, backlog and maintenance cost per asset class, calculated on the same definitions at every site. The definitions matter more than the charts.

• PM compliance: Jobs completed on time against jobs scheduled, with the on-time window written down, such as within the due week.
• Overdue by criticality: Overdue jobs on critical assets listed by name, not only counted.
• Backlog: Open work in estimated labor hours per site, compared with the hours the team has available.
• Reactive share: Unplanned work as a share of all work, by site and class, to show where PM is not preventing failures.
• Data quality: Assets missing a criticality, location or PM plan, and meters with no reading in the expected period.

Publish the definitions alongside the reports. If one site counts a job as on time when it closes within the month and another only by the due date, the comparison means nothing.

What are the best practices for a multi-site asset register?

The best practices are a central data owner, one standard enforced by the software itself, and regular checks that the register matches what is on the floor. A register decays when its rules exist only in a document.

• Name a data owner: One central role approves new classes, attribute changes and merges of duplicate records.
• Enforce in the form: Required fields, pick lists and validation in the app, not in a guidance note.
• Start with critical assets: Get criticality, PM plans and alert routing right for the assets that matter most before expanding to everything.
• Audit on a cycle: Scan a sample of assets at each site on a schedule and fix mismatches at the source.
• Review PM plans yearly: Retire tasks that never find anything and add tasks where failures keep recurring.
• Plan for disposal: Close the asset, its PM plans, meters and licenses together, so retired equipment stops generating alerts.

How Agnotic can help

Agnotic Technologies builds custom CMMS and enterprise asset management software for organizations that run many sites and have outgrown spreadsheets or a tool designed around one building. The work covers the register data model, migration from existing systems, PM scheduling by time, meter and condition, alert routing and an offline mobile app for technicians.

Agnotic also connects the register to the client's ERP, purchasing and sensor platforms, and builds the cross-site reports that operations and finance teams share.

Sources

• OSHA: 29 CFR 1910.119, Process safety management of highly hazardous chemicals
• ISO/TC 251: Asset management standards (ISO 55000 series)
• ISO 14224:2016: Reliability and maintenance data for equipment