Two ways to partner.
Instrument indexes and I/O lists are still built by hand, from drawings that keep changing. Some firms sell that work. Some companies build the software it happens inside. There is a path here for both, and neither one asks you to change what you deliver.
Which one are you
Engineering service firms
You already sell the instrument index, the I/O list, the line list and the cable schedule as deliverables. Your engineers read the drawing and build the register by hand, then build it again on the next revision. Partner pricing at volume, a workspace for every client project, and exports in whatever format your client asked for.
Software and automation partners
You build or sell the design, automation and asset software our customers already run. Engineering registers that come out of a drawing feed directly into that work. Integration with your product is set up with you, and our exports already land in the controls formats your users hand off to.
For engineering service firms
Your business is judgement, not typing. Knowing that a bubble on a vendor skid is not the client's tag, that a revision cloud changes the loop, that the I/O count drives the panel. Tagsight removes the hours before the judgement starts. The deliverable still goes out under your title block, still reviewed by your engineer, still billed at your rate.
- Volume pricing on the engine, with the cost of a drawing set knowable before you bid the job.
- A workspace for every client project, carrying the client, the project number, the plant and the area, with each client's tag convention held separately.
- Revision comparison against a held baseline, so a register you built last year stays useful this year.
- Exports in your client's format. Excel, CSV and JSON, plus TIA Portal, Studio 5000, PLCCreator and DEXPI. One drawing covers every format.
- A named technical contact, and a defect in your client's drawing convention treated as ours to fix.
- Unlimited supporting documents on every paid plan, so datasheets, schedules and indexes go in alongside the drawings.
For software and automation partners
Engineering registers are upstream of almost everything else a plant's software does. If your product consumes an instrument index, an I/O list or an equipment list, it currently consumes one somebody typed.
- Integration with your product, set up with you and documented for your team.
- Exports that already land where controls work happens, including TIA Portal and Studio 5000, plus DEXPI for engineering data exchange.
- Joint work on the listing and the integration story, and a technical contact who answers.
How a firm partnership starts
- 01A conversationWhere the drawing to register process actually breaks down for your team
- 02Your own drawingsA representative set, including the difficult ones, looked at together
- 03One live client projectA real job with a real deadline, before any agreement
- 04Terms and volumePriced from what the project actually used, not from a forecast
- 05Listed, if you want to beEvery word approved by you, and withdrawable at any time
Tagsight is independent. Software and format names on this page describe what our exports produce and what our customers run. They do not claim a partnership, an endorsement, or a registered vendor relationship with any of those companies.
Tell us which path fits
Say what you deliver today and who you deliver it for. Someone reads every one of these.
We run it on a real drawing first.
Whichever path fits, the useful first step is the same: a pilot on a real drawing set, with the scope agreed before it starts.