Inventory
A register of what is installed, with its provenance intact
Turn a field survey into an equipment register your team can revisit. Keep identities, available ratings, locations and source photographs together, with gaps stated clearly.
MEP equipment inventory software turns a field survey into a maintained register of the plant a building contains: each unit identified with the fields available from the survey, with an explicit record of which areas were surveyed and which were not.
The count has to be right
An inventory answers quantity questions — how many rooftop units are we responsible for, how much plant reaches end of life in five years. Duplicate rows distort those counts.
Repeat captures are the usual source: a unit photographed from several angles, or carrying both a unit plate and a compressor plate. Consolidating on identity evidence helps prevent repeat photos from inflating the register. Survey coverage still needs checking.
What a register needs to carry
01: Tag
02: Location
03: Identity
04: Age
05: Ratings
06: Condition
07: Status
| Column | Content | What it supports |
|---|---|---|
| Tag | As labeled on site, not as drawn | The key everything joins on |
| Location | Building, floor, room | Access planning and finding it again |
| Identity | Manufacturer, model, serial | Parts and replacement matching |
| Age | Printed date or supported serial lookup | Replacement sequencing |
| Ratings | Electrical and capacity, by type | Whether a like-for-like swap is possible |
| Condition | Rating plus who confirmed it | Prioritization, attributably |
| Status | Confirmed, or still unresolved | The register's own boundary, in the data |
State the boundary in the data
The most common failure in building equipment inventories is silent incompleteness. A locked switch room or a ceiling nobody opened leaves no trace in a normal spreadsheet, and a blank cell reads as absence to whoever inherits the file.
Keeping unresolved items as first-class entries fixes that. The register says what is confirmed, what is proposed and what is still open, so its coverage is legible without interviewing whoever compiled it.
Keeping it current
Registers decay. Equipment is replaced, spaces are re-fitted, tags are renumbered. A register that cannot be updated in place gets rebuilt from scratch every few years, which is how buildings end up with three conflicting inventories.
Review new captures before updating an existing unit or recording a replacement. For how the underlying survey runs, see MEP field survey software.
Keeping a register honest
What makes an equipment inventory trustworthy?
Knowing its boundary. An inventory that lists ninety units is useful; an inventory that lists ninety units and states which areas were not accessible is usable. Without the second part, a reader cannot tell the difference between a building with ninety units and a survey that stopped at ninety.
How is this different from a survey?
A survey is the act; an inventory is the artefact it leaves behind and the thing that has to stay current. The survey ends when you leave the building. The inventory carries on being read for years, by people who were never on site, which is why provenance and an explicit gap list matter more in the register than they did on the day.
Can it seed a maintenance system?
A reviewed equipment export can provide a starting point for a maintenance register. Check the required columns, identifiers and import format in the receiving system; direct integration is not implied.
What happens when equipment is replaced later?
Capture the replacement and review its identity against the existing record. A reused tag does not prove it is the same physical unit. Check the model, serial and location before merging or updating records.