Problem
What this replaces on site
Most sites keep assets in a spreadsheet that cannot talk to tickets, AMCs, or meters. When a chiller fails, someone hunts warranty paper while production or tenants wait.
Who uses it
The people on this module
-
Facility and plant engineers
Own the tree — what the site has, where it sits, how critical it is.
-
Technicians
Update condition when they close work.
-
Procurement / stores
See AMC windows, vendors, and the last spare against the same asset.
-
Managers
Watch risk, not a list of nameplates.
How to use
Three steps to start
-
Step 01
Put the asset on the tree
Location, nameplate, and criticality — one object, not five folders.
-
Step 02
Attach AMC, PM, and signals
Contracts, planned work, meter readings, and (when present) Nova’s sensors sit on that object.
-
Step 03
Open work from health, not from panic
Atlas surfaces risk. Orbit can open the job before the complaint arrives.
Different from an Excel register
Health score from age, failures, PM, and sensors — not a static asset list that nobody updates after commissioning.
Atlas is the memory of the facility. Nameplate, contract, last failure, last spare — one object. Predictive cues here are history plus sensors, not a black-box promise.
