Building a brownfield OT asset inventory without stopping production

You cannot secure, modernize, or integrate an industrial network you cannot describe. Brownfield plants rarely have one accurate asset list: drawings are out of date, vendor laptops appear only during a fault, and the same controller may be called three different names by maintenance, engineering, and IT.

Start with passive evidence

Collect existing drawings, controller backups, switch exports, maintenance records, network flows, and operator knowledge. Passive discovery is usually safer than active scanning on fragile or safety-critical networks. Record what was observed, when, from which source, and how confident the identification is.

An inventory record should include asset identity, location, function, owner, manufacturer, model, firmware, network address, protocol, connected peers, lifecycle status, and criticality. Add safety relevance, remote-access path, backup status, and known vulnerabilities only when the evidence supports them. “Unknown” is better than a confident guess.

Join technical and operational views

A device’s business criticality is not always obvious from its model. A small unmanaged switch may isolate a whole line; a redundant historian may be low consequence. Ask what stops if the asset fails, what can run manually, what the safe state is, and how long recovery can take.

Normalize names so the inventory can link to a cell, line, and process area. Keep aliases from drawings and vendor tools as searchable fields. This is where a simple asset hierarchy pays for itself before any AI or digital twin project starts.

Make the inventory a maintained operational record, not a one-time spreadsheet. Add a last-seen date, evidence source, confidence, owner, and next review. When a new panel or temporary laptop appears, capture it during normal work and route it through the same change process. A list that cannot explain what changed since the last survey will drift back into fiction.

Turn the list into action

Prioritize unknown remote access, unsupported firmware, flat network paths, missing backups, and assets with no owner. Do not remediate everything at once. Create a change-controlled backlog with a safe test window, rollback plan, and evidence of completion.

The OT zones and conduits guide shows how an inventory becomes a segmentation design. The industrial DMZ glossary entry covers one common boundary. For a broader map of plant systems, Understanding the Shop Floor is a practical companion ebook.