Greater Denver & the Front RangeDenver & Front Range(720) 340-1539
1st Key Technology Group — One Integrator, Every System
PLANNING

What belongs in a system inventory?

A useful inventory helps owners plan maintenance, takeovers and replacements.

A man is working on an electrical panel
BY MIKE MARSHEDITORIAL DATE UPDATED

Editorial dates are assigned for this collection; they do not represent original publication or author approval dates. The update date records this site revision.

Connect device to location

Record each camera, opening, panel, switch or sensor by a stable identifier, physical position and head-end connection. Software labels should match drawings and field tags.

Capture ownership and dependencies

Add manufacturer, model, firmware or support status where available, license owner, power and network path, administrator and service contact. Mark unknowns rather than guessing.

Keep the record current

Update the inventory after moves, repairs and tenant changes. The most valuable sheet is the one the next technician can use to find the installed asset.

Working example: The scenario below is illustrative. It describes a practical design and review method, not a completed customer project or a guaranteed result.

A working scenario

The facilities spreadsheet lists 70 cameras, while the recorder shows 62 and the latest drawings show 65. Each source describes a different moment in the site's history.

The decision to make before buying

Assign stable IDs and record device location, model, serial where appropriate, software, power, network, owner, status and confidence in each entry. Flag inaccessible equipment.

A useful acceptance test

Compare a field sample to the recorder, switch and drawings; resolve duplicates and mark unknowns rather than guessing. Reconcile additions after every project phase.

What the owner should receive

Store a dated inventory, location map, credential and license ownership, linked test records and a process to approve updates.

Questions owners ask

Which fields belong in an asset register?

At minimum, use a stable ID, physical location, system and device type, model or version where available, power and network association, owner, observed status and date verified. Add credential or license ownership without publishing secrets in the general register. Link each item to relevant test and service records.

How do you handle conflicting records?

Mark source and confidence: “field verified,” “reported by platform,” or “drawing only.” Investigate discrepancies at critical locations first. Keep a dated exception rather than making an undocumented guess; an uncertain camera count is less dangerous than treating a nonexistent view as proof of coverage.

← All insightsTalk with us
COLORADO FACILITIES

Let’s talk about your building.

Have a building in Colorado? 1st Key stands ready and able to help. Tell us the location and what needs attention; we will confirm service availability and scope.

Request Service
Request Service