Blog.

Notes on P&ID instrument extraction, ISA 5.1 classification, line-list parsing, and the engineering workflows.

CFIHOS, Explained. What Instrumentation Engineers Actually Hand Over

CFIHOS, JIP36 defines the data an owner-operator receives at handover. Tag classes, ISDD properties, document links, and as-built reconciliation.

Read article

June 2026

Reading Owner-Operator Instrument Tags Built on ISA 5.1Owner-operators layer company-specific tag rules on the ISA 5.1 base. How the functional identifier reads, how to confirm the deviations against the drawing legend, and how to build a clean instrument index, worked through the publicly documented Saudi Aramco SAES-J-004 standard.ISA 5.1Owner-Operator StandardsDialects

May 2026

CFIHOS and ISO 15926. A Working Reference on Engineering Data HandoverHow CFIHOS and ISO 15926 structure process-plant data handover. The lifecycle data model, the reference data library, why the instrument index has to conform, and why the handover register has to stay current after the plant starts up.Data HandoverCFIHOSStandards
Brownfield I/O Reconciliation. Keep, Remove, ReplaceOn a revamp the drawings, the field, and the control system rarely agree. Reconciliation is the pass that makes the I/O list defensible.BrownfieldI/O ListMOC
Building an I/O List From P&IDsA step-by-step build of a controller-ready I/O list from a P&ID set. Extract, classify, dedup, assign, freeze. With worked examples and what stays off the list.I/O ListP&IDReference
IEC 61511 for the I&C Engineer Building the SIS I/O ListThe working subset of IEC 61511 an I&C engineer needs, from reading the LOPA output through documenting proof-test intervals on the SIS I/O list.IEC 61511SISFunctional Safety
I/O List Columns Explained. What Each One Is ForA column-by-column guide to the instrument I/O list. What each field contains, who reads it downstream, where the data comes from, and the common mistakes.I/O ListReference
I/O List to Wiring. Termination and MarshallingThe I/O list says which channel. The termination schedule says which wire. This walks the chain from field instrument to PLC card terminal.I/O ListWiringCommissioning
PLC Tag Naming Conventions. P&ID to DCSThe P&ID tag, the PLC variable name, and the asset-management ID are related but not the same string. The naming convention is what keeps them in sync.PLCTag NamingI/O List
Redundant I/O. How 1oo2, 2oo3, and 2oo4 Voting Show Up on the I/O ListHow to represent voted sensor sets and redundant final elements on the SIS I/O list. One row per physical device, suffixed tags, shared SIF identifier.I/O ListSISReliability
AI, AO, DI, DO Signal Classes ExplainedHow to assign the correct signal class, AI, AO, DI, and DO, to every bubble on a P&ID. ISA letter rules, fixed overrides, dialects, and one-channel-per-bubble.I/O ListISA 5.1Signal Class
Soft Tags vs Hard I/O. What Belongs on the I/O ListA hard I/O point is a wire on a card. A soft tag is a value the controller computes or reads over a bus. Only hard channels belong on the I/O list.I/O ListDCSReference

Page 1 of 4Older posts

Run it on your drawings.

The articles describe how Tagsight reads P&IDs and produces the engineering documents.

Start a workspace Pricing