GDS Technology — Built, Wired and Secured podcast banner
Watch on YouTube →
Blog Built

Best OT Asset Inventory Methods for Buildings

A controller that nobody can identify is not a minor documentation problem. It is an operational risk sitting behind a ceiling, inside a telecom room, or on a building network with authority over air handling, access, cameras, power monitoring, or life-safety-adjacent processes. The best OT asset inventory methods create a defensible record of what is connected, what it does, who owns it, and what fails when it goes offline.

For commercial properties and enterprise facilities, the inventory cannot be a spreadsheet assembled during a project closeout and ignored afterward. Operational technology changes constantly. Contractors replace controllers. Service providers add remote gateways. Facilities teams connect temporary devices that become permanent. Network changes expose equipment that was never meant to be routed. Without a controlled process, the inventory becomes a partial story, and partial stories lead to delayed recovery when an incident occurs.

Best OT Asset Inventory Methods Start With Scope

An OT inventory should not begin with a network scan. It should begin with a clear definition of the environment being governed. Building automation, physical access, video systems, elevator interfaces, power and environmental monitoring, industrial controls, telecom-room equipment, and their supporting network infrastructure may all be in scope. The exact boundary depends on the property, the operating model, and who carries responsibility for each system.

That boundary needs to include supporting assets, not only field devices. A facilities director may know every major piece of equipment in a mechanical room but have no record of the workstation, virtual server, cellular gateway, network switch, power supply, or remote-access appliance required to manage it. Those supporting components often determine whether the system can be restored after a failure.

Assign an accountable owner to every asset class before discovery begins. “Facilities” and “IT” are not ownership assignments. An accountable owner needs the authority to approve access, authorize changes, verify operating status, and escalate unsupported or unapproved equipment. Shared environments can have multiple contributors, but they still need one decision path.

Use Four Evidence Sources, Not One

No single discovery method provides a complete OT inventory. Passive network monitoring can reveal communication patterns but may not identify a device hidden behind a serial converter. A physical walkdown can confirm equipment labels and locations but cannot show every dependency or remote connection. Project documentation may identify intended equipment but not the device that was substituted in the field.

The most reliable approach reconciles four sources of evidence:

  • Physical verification in mechanical rooms, telecom rooms, risers, roofs, loading areas, and other equipment locations.
  • Network and configuration data from switches, firewalls, wireless infrastructure, address assignments, and management platforms.
  • System documentation, including closeout records, control drawings, cabinet schedules, and maintenance records.
  • Interviews with facilities, IT, security, property management, and service personnel who understand how the system actually operates.

Each source exposes a different type of gap. A controller seen during a walkdown may be absent from network records because it sits on an isolated segment. A device in switch records may have no documented business purpose. A listed server may no longer exist, while a replacement has been installed with no formal turnover. Reconciliation is where inventory work becomes operational governance rather than data collection.

Passive Discovery Comes First on Live OT Networks

Passive discovery is usually the safest technical starting point for a live OT environment. It observes traffic and identifies devices, addresses, communications, and likely roles without sending probes that could interrupt fragile systems. This is especially useful when equipment age, firmware condition, or vendor support status is uncertain.

Passive methods have limits. A quiet device may not communicate during the observation period. Segmented networks may require collection points in more than one location. Traffic analysis can also produce incomplete or ambiguous device identification. Treat passive discovery as evidence, not final truth.

Active scanning has a role, but it should be planned and authorized. Some older controllers and embedded devices react poorly to aggressive scanning, unexpected authentication attempts, or malformed traffic. The right approach is to define approved ranges, maintenance windows, scan profiles, rollback actions, and responsible contacts before testing begins. A scan that creates a building-system outage is not a successful inventory exercise.

Physical Walkdowns Validate What the Network Cannot See

A walkdown is where teams find the assets that diagrams miss: unmanaged switches mounted in panels, undocumented power injectors, abandoned gateways, cellular devices, loose patching, and locally connected engineering laptops. It also verifies asset location, cabinet or room identification, power source, environmental exposure, and physical access conditions.

The walkdown should be performed with a standard capture process. Photograph labels where permitted, record serial numbers and controller identifiers, and confirm whether each device is powered, connected, and actively serving a function. Do not assume an unlabeled device is obsolete. Trace it, ask the operating team, and document the result before removal or isolation.

Physical verification also reveals whether the asset can be supported during an incident. If the only workstation used to manage a system sits in a locked office with no documented credentials or backup, that is a resilience issue. The inventory should record it as such.

Build Records That Support Decisions

An inventory that only lists device names and addresses will not help much during an outage. Every record should answer practical questions: What is this asset? Where is it? Who owns it? What process does it support? How is it connected? Can it be safely changed? What happens if it fails?

At a minimum, capture the asset type, manufacturer and model, serial number where available, location, network identifier, software or firmware version, support status, accountable owner, and lifecycle status. Add the system dependency and criticality rating. For example, a network switch should not simply be classified as a switch. The record should show whether it supports a floor of access-control panels, a mechanical control network, a security operations workstation, or a noncritical tenant service.

Relationships matter as much as individual records. Document upstream network dependencies, power dependencies, management platforms, remote access paths, and any shared services such as time synchronization, identity services, or backup storage. A failed controller is one problem. A failed shared component that disables twenty controllers is a different class of problem.

Use a consistent criticality model across the portfolio. The model should reflect safety exposure, business interruption, tenant impact, regulatory obligations, recovery complexity, and the availability of manual operation. Avoid calling everything critical. If every asset has the highest designation, the designation has no operating value.

Make the Inventory a Control, Not a Project Deliverable

The inventory begins to decay the day it is completed unless changes are governed. Every construction turnover, service visit, equipment replacement, network modification, and remote-access request should trigger an inventory review. This does not need to create bureaucracy. It requires a simple operating rule: no asset enters production, changes function, or leaves service without the record being updated and accepted.

This is where fragmented responsibility creates avoidable failure. A contractor may install the equipment, a service company may configure it, IT may assign network access, and facilities may operate it. If none of those parties owns final acceptance of the documentation, the organization receives a working system with no verified operational record.

Build inventory validation into turnover. Before acceptance, verify device counts, locations, network settings, administrative access, backup configurations, support contacts, and recovery documentation. Confirm that unused accounts and temporary remote connections are removed. Test that the record matches the installed environment rather than accepting a closeout package at face value.

For existing buildings, establish a review cadence based on risk. High-impact systems and remote-access pathways may require frequent review. Lower-risk devices can be reviewed on a scheduled basis or when related work occurs. The point is not to create activity for its own sake. The point is to detect drift before a failure turns undocumented change into extended downtime.

Measure Inventory Quality by Recovery Readiness

A useful inventory is tested by the questions an incident commander would ask at 2:00 a.m. Can the team identify the failed asset? Can they find it? Do they know who can authorize access and changes? Can they see which systems and occupants are affected? Is there a supported recovery path, a current backup, and a documented fallback?

Run tabletop exercises around realistic failures: loss of a telecom room, expiration of a device certificate, a failed controller power supply, an unavailable remote connection, or a network change that isolates a building system. These exercises expose missing dependencies and unclear ownership faster than an annual documentation review.

The goal is not a larger database. It is one standard for knowing what is in the environment and one accountable process for keeping that knowledge current. When a building system stops responding, the organization should not begin by asking what is connected. It should begin with a verified record and a clear path to recovery.