Drawings against lists
Line lists, valve lists, instrument indexes and equipment lists, checked against the P&IDs.
P&ID checks
Check every drawing against every list, before you issue.
Verno reads the drawing set and the documents that are supposed to agree with it, then shows you every place they do not. It changes nothing while it checks.
Consistency checks eat the week before issue.
The same valve appears on a P&ID, in the valve list, in the instrument index and on a datasheet. Checking that they all agree is a line-by-line job, usually done the week before a package goes out.
It is exactly the kind of work that gets rushed, and exactly where expensive mistakes come from.
How Verno handles it
Across disciplines
Tie-in schedules and electrical and I&C drawings checked against the P&IDs.
Every mismatch shown
Each finding points at the drawing, the row and the value that disagree.
Package checks
Right revision, right date, right stamp on every drawing before issue.
Read-only by default
Checking changes nothing. Fixes are proposed separately and accepted by an engineer.
Your standards
Checks follow your project's conventions, not a generic rule set.
Ask it
What engineers say to Verno.
“Audit the valve list against the P&IDs. Show me every row that does not match.”
“Check the tie-in schedule and the electrical and I&C drawings against the P&IDs.”
“Every drawing in this package: right revision, right date, right stamp. Before I issue.”
Common questions
What does a P&ID consistency check cover?
Whether the tags, line numbers, sizes and specs on the P&IDs match the project's lists and registers, and whether related drawings and schedules agree with them.
Does Verno fix the mismatches it finds?
It can propose the fix, with its reasoning. Nothing is changed until an engineer accepts it.
Can it check documents in our own formats?
Yes. Verno reads your lists in your own Excel templates and your drawings as they are.