Run reactive FM service after handover
Handle a fault the way a building operator should: log the reactive request against the asset, work it with the warranty and O&M data to hand, and close it out with a verification check.
How it works, step by step
3 steps across the platform - what you do at each one, and why it matters.
Log the reactive request
ServiceRaise the service request against the specific asset that failed, with the fault, the location and the priority, so it is tracked from report to fix instead of sitting in an inbox. Set the response target.
Why: A fault that is not logged against the asset is one nobody can trend or prove was fixed. Tying it to the asset from the first call is what later tells you which units keep failing and whether the response target was met.
Open the asset and its data
AssetsOpen the asset record to see its make and model, its location and, crucially, whether it is still in warranty and what the O&M manual says. Pull the spare part or the procedure from there.
Why: Fixing a unit that is still under warranty out of your own pocket is money straight out the door. The asset record is what tells the engineer, before they start, who pays and how the maker says to fix it.
Close out with a verification check
InspectionsBefore you mark the job done, run a short verification inspection that the fault is actually cleared and the asset is back to spec, and capture it with a photo. Only then close the request.
Why: A job closed on trust alone is the one that reopens next week. A quick verified check is what makes closed mean fixed, and gives the operator a clean maintenance history on the asset.