The engineering record for the energy transition.
A hydrogen unit drawn last month and a gas plant drawn in 1988 are documented the same way. Tagsight reads the drawings into the instrument index, I/O list and equipment register a project runs on, for the plants being built now and the plants being rebuilt around them.
Every plant runs on the same record. The plants being started now are transition projects.
Whatever a plant processes, it is documented as a P&ID set, an instrument index, an I/O list, equipment, line and valve lists, datasheets, cable and junction-box schedules and a cause-and-effect matrix. A carbon capture unit is an amine system. An electrolyzer plant is compression, storage, gas detection and a lot of water treatment. A battery plant is a one-line, HVAC, fire suppression and a thermal-management P&ID. A fuels plant is hydrotreating and fractionation.
The tags are ISA, KKS, IEC 81346 or the owner’s own house rule. The documents are the same documents, and the work of building the registers from them is the same work. It is still done by hand, one sheet at a time, on every revision.
Three places the register is built on a transition project.
- 01GreenfieldA new hydrogen, capture, ammonia or storage plant builds every register from nothing, from an IFC set that keeps changing, against a disbursement clock.
- 02RetrofitElectrification, a capture tie-in or hydrogen blending starts with the current-state register of an existing unit, read from legacy drawings that are often scanned.
- 03Handover and evidenceCommissioning packages, MOC records and as-built registers are what milestone reviews consume, and they consume them faster than an engineer can retype them.
Where the drawings are now.
Read as drawn, in the convention of the package.
An electrolyzer supplier, a capture EPC, a European renewables developer and a North American utility each tag their sheets differently, and one project carries all of them. Every tag is read as its sheet prints it and keeps that sheet as its reference. Your engineer confirms each read before it exports.
- AT-EC-201Electrolyzer stack outlet analyzer
- AT-ABS-1102CO2 at the absorber outlet, the capture rate
- LSHH-TK-2101Refrigerated ammonia tank high-high trip
- OGD-ENC-07Off-gas detector, battery enclosure 7
- TT-RX-1201-B3Hydrotreater bed 3 temperature
- 52-B1-01Bay 1 breaker, ANSI device 52
- 10LAC01CT001Feedwater temperature, KKS
- PT-RO-HP-6201RO high-pressure pump discharge
What it delivers on these projects.
- Instrument index and I/O list reconciled across the supplier and EPC packages, every row traceable to its sheet
- Equipment, line and valve lists with the service and spec the drawing prints, so hydrogen, CO2 and low-temperature subsets filter out on their own columns
- The SIS subset for gas detection, trips and shutdown scope the safety file references
- Revision change reports from IFC through mechanical completion, and through a retrofit as the MOC record
- Exports to Excel, CSV, JSON, DEXPI and the control-system formats the build imports
Built in Calgary, inside the projects.
Tagsight is built in Alberta, alongside the capture, hydrogen and retrofit projects that run through one of the densest process-plant clusters in the world. Engineers use it on greenfield sets and on drawing archives that predate the engineers reading them. The company keeps its industrial identity: refineries, gas plants, petrochemicals, pharma, food and mining remain the industries it serves, and the transition runs through them.
Our own footprint, and the size of our claim.
Tagsight is software. It does not capture carbon, make hydrogen or store power, and it does not reduce anyone’s emissions. The projects that do those things run on the records it builds, and on a retrofit they cannot start until the current-state record of the unit exists. That is the whole of our climate claim, and we keep it that size on purpose.
Our own footprint is small and we treat it as real. There is no office and no fleet; the footprint is cloud compute, and that compute runs in a region our provider designates low-carbon. We read our provider’s carbon report for our account and will publish the figure once a year. Drawings are deleted on request and can be set to delete after export, so we hold no more than the work needs.
Common questions
Does the software do anything different on a hydrogen or carbon capture plant?
Where does a retrofit start?
Does Tagsight reduce emissions or model the process?
Which conventions are read on transition projects?
Are the registers usable as commissioning evidence?
Does this replace the oil and gas, refining and petrochemical work?
Start with one drawing.
Upload a P&ID from the project, see the instruments, equipment and lines it reads, and export the register in the format the build already imports.