01
What a facility asset register should achieve
A facility asset register should tell an authorised user what maintainable assets exist, where they are located, how they are identified, who is responsible for them and which records support their operation. It becomes a common reference for planned maintenance, reactive work, supplier coordination, handover and owner reporting. A register that cannot be matched to the physical property is only an inventory claim, not an operating control.
The register should support decisions without pretending to answer questions that require competent assessment. It may record an observed status, known warranty, assigned provider or latest report, but it should not invent condition, remaining life, capacity or compliance. Asset-management frameworks emphasise lifecycle information and decision support; the appropriate level of detail still depends on the property, contract, systems, risk and owner requirements.
02
Define purpose, boundaries and ownership first
Begin by naming the business purpose. The same property can need an operational maintenance register, a financial fixed-asset register, an insurance schedule and specialist statutory records. These records may share references, but they are not automatically interchangeable. The facility register should state which buildings, common areas, landlord systems, tenant-controlled equipment and specialist assets are included or excluded from its operating scope.
Assign a data owner and an operating custodian. The owner approves the purpose, scope and important changes; the custodian maintains records through agreed workflows. Identify who may create an asset, edit core identity fields, change responsibility, close a duplicate or mark an item removed. Without that authority map, several teams can create conflicting versions and the register loses value during a fault, transition or budget review.
03
Build a location and system hierarchy
Create a hierarchy that reflects how people navigate the property: portfolio or site, building, zone or wing, floor, room or plant area, system and asset. Use names that appear on drawings, doors and operating records where practical. A location such as “roof plant area, east side” is more useful than “site” when a technician, manager or specialist must find the equipment and confirm the correct record.
Parent-and-child relationships help users understand systems. A main panel may feed several distribution boards; a chilled-water system may include pumps, valves and terminal equipment; a pump set may contain duty and standby units. Record relationships only where they improve work planning or reporting. Excessive hierarchy creates administrative effort, while insufficient hierarchy makes defects, costs and maintenance history difficult to trace.
04
Choose minimum fields that people can maintain
A practical core record may include asset ID, description, category, site, building, floor or area, system, manufacturer, model, serial number where available, installation or commissioning information where evidenced, operational responsibility and current record status. Optional fields can cover warranty, supplier, specialist contract, manual reference, maintenance schedule, criticality, observed condition, photograph and related work history.
Define every field before collection. State whether a date means manufacture, installation, commissioning, warranty start or last verification. Use controlled lists for category, status and location instead of allowing several spellings for the same value. Make unknown, not applicable, not visible and awaiting verification distinct. Blank cells should not silently mean all four, and an estimated value should never appear as a confirmed fact.
05
Create stable IDs and useful asset categories
Give each asset or approved asset group a unique, stable reference. The identifier should not change merely because a contractor, room name or condition changes. Avoid codes that depend on information likely to be revised. If labels, barcodes or QR codes are used, agree how damaged labels, duplicate labels and replaced equipment are handled so the physical tag and digital record remain aligned.
Use categories that support maintenance and reporting rather than copying an uncontrolled supplier list. A simple taxonomy might separate HVAC, electrical, water and plumbing, pumps, life-safety interfaces, vertical transport, access systems and relevant building fabric. Specialist systems should remain linked to the competent provider responsible for their work. Categories can be expanded when the operating need is clear; they should not imply that every listed system is maintained directly by one FM provider.
06
Verify records against the property
Start with available drawings, manuals, schedules, previous registers, service reports, warranties and handover files, then reconcile priority information on site through safe and authorised access. Mark each record as received, reviewed, observed, sampled, technically verified or superseded using agreed definitions. This preserves the difference between inherited data and information confirmed by the current team.
Prioritise systems whose failure could affect safety, essential services, many occupants or material property damage, but keep the classification subject to competent review. Record discrepancies with location, date, evidence and an owner for follow-up. Do not expose people to live electrical equipment, restricted plant, confined areas or other hazards merely to complete a spreadsheet. The verification method must follow property procedures and appropriate technical supervision.
07
Record condition without creating false precision
Condition information needs a documented basis. A simple scale can work when every rating has a definition, evidence expectation and date. Distinguish visible observation from functional test, specialist inspection and engineering assessment. A clean external appearance does not prove internal performance, while an older asset is not automatically unserviceable. Record limitations so decision-makers understand what was and was not assessed.
Link defects and recommendations to work items rather than overwriting the asset record with free-text notes. The register can show the latest approved status and reference the detailed inspection, quotation or work order. This keeps history traceable and prevents a completed repair from erasing the reason it was raised. Remaining-life or replacement recommendations should identify their evidence and competent author instead of being generated from age alone.
08
Connect maintenance, contracts and documents
Each relevant asset should connect to the maintenance responsibility and schedule that apply to it. Useful links include the planned task or frequency basis, current service provider, contract reference, warranty, manufacturer guidance, approved method, recent report and open recommendation. The register does not need to store every document inside one cell; it needs a controlled reference that helps an authorised user reach the current evidence.
Separate recurring included work from chargeable materials, replacements, specialist services and owner approvals according to the accepted contract. If responsibility is uncertain, mark it for decision instead of assigning it by assumption. During provider change, preserve open faults, temporary measures, pending quotations and warranty matters alongside the asset so unresolved work does not disappear when a new operating team receives the register.
09
Use criticality to focus decisions and reporting
Criticality can help determine verification priority, maintenance review, spare-parts attention and escalation, but the method should be agreed. Consider consequence to people, essential services, property, operations and recoverability together with redundancy and available controls. Do not allow a software default or an informal label to become an unsupported safety or compliance classification.
Keep criticality distinct from current condition and work priority. A critical asset may be in good condition, while a non-critical item may still need prompt repair because it is leaking or creating damage. Reporting should show important missing data, overdue planned work, repeated faults, open recommendations and responsibility gaps. A large asset count is not a performance measure; useful reporting directs an owner to decisions and unresolved exposure.
10
Control updates through the asset lifecycle
Define update events such as installation, replacement, relocation, major repair, warranty change, responsibility change, verification and removal. Record who changed the data, when it changed, why and which evidence supports it. Preserve the retired record and its history when equipment is replaced; create a new identity for the new asset and link the relationship where useful instead of rewriting the old record as though it never existed.
Review data quality through targeted checks: duplicate IDs, missing locations, invalid categories, assets without responsibility, records without recent verification, and schedules that reference removed equipment. Sample physical assets against the register and register entries against the property. Protect confidential documents, access information and personal data with appropriate permissions. Exported spreadsheets should be controlled because copies can become outdated quickly.
Use the register during mobilisation, planned-maintenance review, monthly reporting and budget preparation so errors become visible through real work. Close the initial build only when outstanding gaps have owners and review dates, not when every cell has been filled. Friends Facilities Management can discuss the asset information needed for a Dubai maintenance or facility management proposal. Final scope, verification level, systems, responsibilities and deliverables must be confirmed in an accepted written agreement. This guide is general information and not financial, legal, regulatory, safety, certification or engineering advice.