Every tag. One truth.
One controlled source for your plant's engineering data
UnaPlant keeps the P&ID, the engineering lists, components and documents in one register, from first design to the part that arrives on site. A change is approved once and shows up everywhere, marked up, before it reaches procurement.
Errors in engineering data surface where they cost the most.
Tag data lives in P&IDs, Excel lists and datasheets that drift apart. The mismatch shows up in procurement, construction and commissioning, and much of the data never reaches the operator.
- ≈10×
A change after design freeze costs about ten times more in each later project phase.
Source: Kerzner, Project Management, 14th ed.
- 27 %
Median engineering slip when detailed design starts before the P&IDs are issued and the heat and material balances are closed.
Source: Merrow, Contract Strategies for Major Projects (IPA data, 1,148 industrial projects)
- 8.5 %
of more than 16,000 projects met both their cost and their schedule targets.
Source: Flyvbjerg & Gardner, How Big Things Get Done
- 2–4 %
of project cost is what owners spend recreating operations and maintenance information after handover.
A controlled register, not another layer over loose files
Drawings and spreadsheets drift apart because each holds its own copy of the data. UnaPlant keeps one, and everything else is generated from it.
- One register, not copies
- The P&ID, the lists and the datasheets are generated from and linked to the same tags. Nothing is synchronised, because nothing is kept twice.
- Checks that give the same answer twice
- Ratings, completeness and consistency are checked by fixed rules. A finding names the tag, the rule and the values, and it is the same finding every time you run it.
- Approval is a record, not a click
- A change to released data needs a reason and a second person. UnaPlant shows what it touches before anyone approves, and keeps the record.
- AI proposes, the register decides
- AI does the tedious reading and drafting. What it proposes is marked as proposed until a person approves it, and it never writes to released data on its own.
What lives in UnaPlant
The P&ID and the four engineering lists are maintained in UnaPlant itself. Click any tag, in any drawing or list, to see the item with its component and documents.
Deliverables
P&ID editor
Upload an existing P&ID once, as a vector PDF. UnaPlant proposes the symbols, lines and tags, you review them, and from then on you edit the P&ID in UnaPlant, where every symbol is linked to its tag.
Engineering lists
The main equipment, valve and filter, instrument and signal lists are generated from the register and issued as controlled deliverables with revisions.
Components and documents
Component database
Specific variants, such as a ball valve series in DN 50, PN 16. Place the component on the P&ID, then pick its variant in the list.
Document database
Datasheets, certificates, manuals and drawings, stored once and linked to every component they cover. One datasheet for DN 15–100 is one document.
Change control
Change requests
Released data changes only through a request with a reason and an approval. Before anyone signs off, they see the items, documents and checks the change affects.
Revision markup
Every new revision of a released P&ID or list marks what changed: clouds on the drawing, highlighted cells in the lists. Nobody has to compare two PDFs by eye.
Procurement
Requisition to delivery
Track each purchase item from requisition to delivery on site, with need dates, supplier dates and vendor documents in one place.
Spec changed after PO
When engineering changes a component that is already on a purchase order, procurement sees it on that item straight away.
Checks and AI
Rule checks
Findings come before the purchase orders, in plain words: HV-101: rated PS 10 bar g at 180 °C is below line PS 16 bar g (EN 1092-1, group 10E0).
AI proposes, people approve
AI proposes tags from drawings, mappings for Excel lists and ratings from datasheets, each with its source. Nothing reaches released data without a person's approval.
How a change goes through
The same change as in the drawing above, from request to issue.
Request
An engineer raises CR-261101-01 on XV-1203. Why: the design pressure of its line went up.
Review the impact
UnaPlant shows what the change touches: the P&ID, the valve and filter list, the datasheet, the open purchase order and the checks that now fail.
Approve
The lead engineer approves. Whoever raised a request can't approve it, and operations can be a required reviewer.
Issue
Revision C of the P&ID and the list marks the change, and procurement sees "Spec changed after PO" on the ordered valve.
Built for skid builders and EPC firms
UnaPlant is made for the companies that design and build process plants, and for everyone on the project who works from the same data.
- Process, piping and I&C engineers
- Enter and change tag data without retyping it from drawings and lists.
- Lead engineers
- Control what gets released and see a change's impact before approving it.
- Project engineers
- Know the status of the data, open changes and open design issues at any time.
- Procurement and expediting
- Order from current lists and see what is late against the need date.
- QA and inspection
- Record FAT and inspection results and release items for shipping.
- Operations reviewers
- Review operability and maintainability before the scope is frozen.
Your data stays yours
Customer projects are confidential. UnaPlant is built around that from the start.
- Hosted in the EU
- Your data, including backups, stays in EU data centres.
- Separated by design
- Each company is its own tenant, and each customer's projects sit in their own data space. The database enforces the separation, not just the app.
- Your own sign-in
- Single sign-on with your company's identity provider, and multi-factor authentication.
- A complete audit trail
- Every change to released data is recorded with who made it, when and why.
- AI under control
- AI is off until you switch it on. Calls go only to approved providers, through one gateway that logs every call. AI output stays marked as proposed until a person approves it.
See UnaPlant on a project like yours
UnaPlant is in development, and we set up each company ourselves. Tell us about your projects and we'll walk you through a demo.