These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Facility Maintenance Mgmt
- Features
- Assets & Condition
Assets & Condition
Keep the equipment register and threshold readings tied to the work they trigger.
OverviewAssets In Service×
Facility Maintenance Mgmt · Assets & Condition
New
Assets In Service
Assets
| Asset tag | Name | Location | Status | |
|---|---|---|---|---|
| AT-630 | Asset 114 | X-9 | Active | |
| AT-836 | Asset 940 | S-11 | Active | |
| AT-956 | Asset 247 | X-22 | Active | |
| AT-663 | Asset 483 | F-13 | Active | |
| AT-700 | Asset 407 | Y-14 | Active |
6 of 6 records
AT-630Assets · ASS-18500
ActiveNameAsset 114
LocationX-9
What you can do
Keep the equipment identity steady
The asset record gives maintenance work a stable point of reference. Name, tag, location, manufacturer, serial number and commissioning date help the team distinguish similar equipment. Its state identifies equipment that is Active, under maintenance, out of service or retired. Maintenance Manager should use those states consistently so the service queue reflects the equipment people can use today.
How the work is organized
- Identify. Admin and Maintenance Manager agree the asset name, tag and physical location.
- Observe. A condition reading ties a metric, value, unit and action limit to the asset at a recorded date.
- Respond. A reading that reaches its action limit flags the asset for maintenance and gives the manager a reason to review work.
What to agree during setup
Choose naming and tag rules before importing equipment. Where machines have similar names, the tag and serial number should settle which physical asset a technician visits. Agree the metric units and action limits for each type of reading. A number without its unit is hard to interpret beside another reading. The team should also decide who checks the condition queue and creates the appropriate work request after an asset is flagged.
Condition monitoring records do not replace the work order. The reading action stores the measured value and can change the asset state; planning and authorization still proceed through the order and its permit. Maintenance Manager should keep the observation and later repair connected by selecting the same asset in both places.
Check the handoff on an actual case
A vibration reading is entered for a rooftop fan. The operator records the metric, value, unit, date and limit. The value reaches the action limit, so the fan is marked Maintenance. Maintenance Manager checks the reading and opens a Corrective work order for that fan. The planner then handles the permit and assignment before the technician begins. After accepted repair, the manager checks that service history shows the completed outcome and that the asset is returned to Active.
This rehearsal tests the full chain from observation to service. The condition reading stays as the original measurement. Later readings can show whether the value changed, while the asset and service records explain what the team did in response.
What your team sees
- Assets In Service — The in-service equipment list lets the team verify tags and locations.
- Condition Reading Register — Measurements show the value, unit and action limit beside each asset.
Follow the work through
Follow the first handoff and the next decision. Rehearse the sequence with a representative asset before opening it to the full team.
What it keeps track of
Data model- Assets
- Machine and equipment registry
- Condition readings
- Condition monitoring measurements per asset
- Work orders
- Maintenance work orders through their lifecycle
- Preventive schedules
- Preventive maintenance intervals per asset
- Service history
- Completed maintenance history per asset
Who uses it
Permissions- Maintenance Manager
- , Maintenance Planner, Technician.
- Each uses the same asset and order references for handoff.
Set up Facility Maintenance Mgmt your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.