Planned UnifyOS module · Operating & maintenance intelligence
Most operating teams inherit an asset they cannot see clearly: incomplete asset registers, warranties nobody can find, maintenance regimes built from guesswork, and no link back to how the building was designed or delivered.
The planned facilities-management module takes the verified handover record forward into operations, so maintenance, compliance and lifecycle decisions rest on structured asset data rather than reconstruction.
In design — shaped with operators and landlord facilities teams
These modules are roadmap positions within UnifyOS. They are in design or scoping, are not available today, and no delivery dates are committed. They are published so clients can see the direction of the platform and shape it — not to imply released functionality.
The problem
The intent
Data it would work from
Capabilities
Worked through with delivery teams running live completions, so the design starts from how handover actually behaves.
The verified asset and system register produced at completion becomes the operating record directly — no post-occupation survey, no re-keying, and every asset still linked to the certificate, warranty and drawing it came with.
Inspection, testing and certification duties are held against each installed system with their frequency and responsible party, so lapses are visible before the certificate expires rather than at audit.
Maintenance regimes are derived from the specified and installed equipment rather than a generic template, so the tasks, intervals and spares match what is actually in the building.
Warranty scope, duration, expiry and the responsible contractor or supplier are held per asset, so a failure is dealt with as a warranty claim while the entitlement still stands.
Recurring faults are traced back through the handover and review record to their design, specification or installation cause, so the same defect stops being solved repeatedly at operating cost.
Compliance position, outstanding statutory items, condition and maintenance performance report consistently across assets, giving owners a comparable operating view.
What it produces
Live asset and system register
What is installed, where, to what specification, with its evidence attached.
Statutory compliance position
Inspections and certificates due, completed and overdue per asset and system.
Maintenance regime pack
Planned tasks, intervals and spares structured against the installed equipment.
Warranty register
Coverage, expiry dates and the responsible party for every warranted asset.
Recurring defect report
Repeat failures with their traced design, specification or delivery cause.
Operating performance view
Compliance, condition and maintenance performance compared across the portfolio.
Who it is for
Facilities and operations managers
Run the asset from a register that matches the building instead of rebuilding knowledge after handover.
Landlords and asset owners
See operating compliance and condition without commissioning a separate survey each cycle.
Compliance and HSE teams
Evidence statutory inspection and testing duties with the certificate behind each entry.
Commercial and contract teams
Pursue warranty and defect liability while the entitlement is still live.
Where the line sits
The boundaries matter as much as the capability.
Roadmap position · Next
Sequencing is driven by dependencies, not by marketing convenience. Nothing here is available today and no delivery date is committed.
Depends on
Already in place
Still needed — In design
See where this sits against every other module on the UnifyOS roadmap.
Inside UnifyOS
Every module shares the same governance, evidence and audit standards, so intelligence carries forward instead of being rebuilt.
The completion record becomes the operating baseline with no re-entry of data.
Operating and condition data feeds lifecycle and capital planning.
Connects to the CAFM, ERP or property-management platform already in use.
Client systems connect through IntelliBridge™, so this module would read from and write back to the platforms you already run.
Requirements from live portfolios shape what gets built first — and what gets built at all.
