Asset Mgmt

Asset registry born at design and carried through; IoT streams feed predictive alerts; warranty tracked to asset.

What it is

Asset management is broken at the seams between project execution and facility operations. Asset registry compiled at handover is partial; warranties scatter; IoT streams from STP, lifts, DG, HVAC are captured but not used predictively. The module makes the asset registry born at design (M07 BIM), populated through execution (M17, M19), and handed over cleanly. IoT data feeds predictive alerts.

Inputs

Triggers

·Handover from M22 — asset register seeded
·Routine maintenance cycle
·Predictive maintenance alert (sensor or pattern)
·Customer-raised service request
·AMC renewal cycle
·Warranty claim window

Data reads

·BIM model with equipment locations (from M07)
·Equipment master from procurement (M14)
·Warranty terms from handover pack (M22)
·Maintenance history per asset
·Predictive maintenance sensor data (where instrumented)

Artefacts consumed

·Equipment commissioning records
·Warranty certificates
·OEM maintenance manuals
·Service request tickets
·Sensor data streams (where applicable)

Tools & Techniques

Methods

·Asset register tied to BIM model (location, type, specs)
·Routine maintenance scheduling per OEM and per regulatory
·Predictive maintenance using sensor patterns where instrumented
·AMC management with vendor performance tracking
·Warranty claim workflow against handover pack
·Spare-parts inventory linked to asset history

Policies

·asset management policy with maintenance cadence
·AMC policy with vendor performance criteria
·Warranty claim policy
·Predictive maintenance threshold policy (where instrumented)

Decision rules

·Routine maintenance auto-scheduled per OEM and regulatory cycle
·Predictive alert auto-routes to maintenance team
·Warranty claim mandatory before paid repair
·AMC vendor change requires service-history justification

Outputs

Artefacts produced

·Asset register per project (live)
·Maintenance log per asset
·AMC contract and performance record
·Warranty claim history
·Predictive maintenance alert log
·Spare-parts inventory register

Data writes

·Asset status updated continuously
·Maintenance history updated per service event
·AMC vendor performance updated on each cycle

Downstream triggers

·Service request status feeds resident services in M24
·AMC vendor performance feeds Vendor 360 in M13
·Predictive alert may trigger maintenance shutdown notice
·Warranty exhaustion triggers AMC scope refresh

Stakeholders

HPMOwns asset registry post-handover and maintenance
CMAsset registry handover from execution
Engineering teamPredictive maintenance and IoT
VendorsWarranty support and AMC

The flow

01Asset registry handover from CM to HPM (born at BIM)
02Testing and commissioning of MEP, lifts, fire systems
03IoT data streams captured from key equipment
04Predictive alerts on likely failures
05Scheduled preventive maintenance per asset
06Warranty tracking linked to asset

State change

Before

Asset registry compiled at handover, partial; predictive maintenance is reactive.

After

Asset registry born at design; IoT streams feed predictive alerts; warranty tracked.

Real-world example

Worli Tower 3 — 6,420 assets monitored. STP pump #3 IoT data shows pressure drift; predictive alert at 18% above baseline. HPM scheduled maintenance for 16 May. AC compressor unit on B-line shows efficiency degradation pattern — flagged for design review (3rd AC service request from B-line in past month).

Artefacts

·Asset registry
·T&C records
·IoT stream data
·Predictive alert log
·Maintenance schedule
·Warranty register

Pain today

Asset registry compiled at handover, often partial. Warranties scatter across vendor emails. IoT data captured but not used. Maintenance is reactive, not predictive.

Integrations

ACC (BIM source)IoT platforms (HPM-managed)