Fluor.
Instrument density, pipe-spec labelling, and tag format shift with every Fluor client and sector. The document structure underneath stays constant across mining, petrochemicals, and advanced facilities.
Primary standard: Client-driven plus Fluor internal practice
- Project I/O list against the client-specified tagging convention
- Master instrument index with tag uniqueness across the full project drawing set
- Equipment list keyed to vessels, pumps, compressors, and packaged skids
- Line list per the client line-numbering family
- Valve list with fail position and actuator type for the EI&T scope
- SIS register per IEC 61511 separated from BPCS
- Revision comparison reports for IFC-to-IFD-to-AFC progression
- Operator-specific tagging conventions come through alongside ISA 5.1
- Multi-page drawing sets process page-by-page so review starts on early pages while later pages are still processing
- BPCS, SIS, FGS segmentation onto distinct Excel sheets
- Revision comparison produces the IFC-to-AFC change records project document control needs
- Direct exports to TIA Portal, Studio 5000, PLCCreator, DEXPI
- Image-based ingestion covers brownfield revamp scope where prior as-builts are scanned
Fluor is referenced descriptively. Tagsight has no affiliation with Fluor Corporation.