We're working through a few early issues. Your drawings, extractions, and credits are safe while we resolve them.
Practitioner-written guides on the documents that show up on every controls project.
Drop a P&ID, instrument index, or schedule. Tagsight reads it to the tag and opens a workspace you keep when you sign in.
PDF · DWG · DXF · TIFF · PNG · XLSX
The DCS vendor needs a signal count before they will price the hardware. The integrator needs tag-class breakdowns before they will size the panel. The project manager needs both before the FEED report closes. The I/O list is what everyone is waiting on, and the drawings are the only place the data exists.
A Dutch HVAC set uses NEN 2778 symbols and area-unit-instrument tag structure. A North Sea platform set uses NORSOK I-005 and KKS. A Texas refinery set uses ISA 5.1 with a house convention the original EPC wrote in 1989. Reading all three as the same grammar produces an output none of the three operators can use. The standard in the drawing dictates the standard in the output.
An MOC package built against a drawing that has not been updated since 2009 is not a management of change document. It is a record of what the drawing said. When that difference surfaces during a HAZOP or a regulator audit, the project team has to reconstruct twelve years of undocumented modifications from field markups, commissioning reports, and memory. That reconstruction is the brownfield documentation problem, and it starts with the drawings.
4200 tags. Three controllers. Six months to cutover. The first document the integration contractor asks for is the I/O inventory, broken down by signal class and system. The first delay is usually tracing where that inventory comes from, because the existing DCS documentation and the current P&IDs have been drifting apart for fifteen years.
FT-2201 starts as a line item on a requisition, becomes a tagged row in the instrument index at FEED, gets a datasheet during detailed design, is assigned a loop number and a P&ID reference, receives a calibration certificate at factory acceptance, and is checked against the loop diagram on the day it is commissioned in the field. That chain of custody across a multi-year project is what the instrument index is for.