Assets and inspections
Every asset carries its own history.
Nameplate, documents, service history, inspections, and cost in one record per asset, so the same failure next year starts from evidence, not memory.
Import the list you have. Fill the gaps during the first inspections.
Registry
One hierarchy, from portfolio to part.
Organization, site, building, system, asset. Every work order, inspection, and reading lands on the right node.
Inspections
Scheduled against the asset, run from the field.
Checklists, photos, and readings come back on a phone. A finding can open a work order, which a reviewer approves before it is dispatched.
Lifecycle
From service history to repair-or-replace.
Repeat failures, rising repair cost, and verified results accumulate on the record and flow into the capital plan.
Illustrative product views with fictional data.
For K‑12 and higher education
Running a school district?
The same registry, written for maintenance and operations teams: district-wide hierarchy, campus inspections, and bond-cycle planning.
Questions
Asset management FAQ
What does an asset record hold?
Nameplate details (make, model, serial, install year), location in the organization → site → building → system hierarchy, documents and manuals, the complete service history with labor, parts, and cost, scheduled inspections, and the repair-or-replace outlook that history produces.
How do inspections work?
Inspections are scheduled against the asset and appear in the same queue as work orders. Technicians follow the checklist on a phone or tablet, attach photos and readings, and findings can open a work order that a reviewer approves before dispatch.
How does the registry feed capital planning?
Repeat failures, rising repair cost, and age are tracked per asset, so repair-or-replace calls start from the record rather than from memory. Verified savings and failure history flow into multi-year capital priorities.
Can we import the asset list we already have?
Yes. Spreadsheets, exports from an existing CMMS, and nameplate photos are the usual starting points. Edviro maps them into the hierarchy and flags gaps to fill during the first inspections.
Do we have to replace our CMMS to use Edviro for assets?
No. Edviro can be the asset system or read from and write to the one you keep. Integration scope is confirmed system by system, and the choice can change later.
See what Edviro finds in your buildings.
Connect your sites. Find the problems. Close the loop.