Revision D replaces revision C. AUVY shows what that means before commissioning.
Extra signals get built because start-up can't wait, and they rarely reach an invoice. AUVY compares every IO list and specification revision the customer sends, names the panels and checklists it touches and drafts a change request while there is still time to bill it, for the project lead to sign off.
← Use casesFor: Owners, project leads, PLC and panel engineers, commissioning teams
System integrators & automation
A week in integration.
The customer uploads IO list rev D with 14 new signals, three renamed and two on a panel already built. The commissioning checklist still reads rev C, and the site team finds out at the machine.
Use cases
What comes in, and what AUVY does with it.
- When
The customer uploads IO list rev D.
AUVYNames the added and renamed signals since rev C and finds the panels and checklists that still rely on rev C.
You getTasks for PLC and panel build with owners and dates, and a change request for the extra signals.
Reads IO list rev C ↔ D · Checklist v5
- When
The specification changes after the order.
AUVYMarks the changed requirements against the version you quoted on and names the parts of the design they touch.
You getA change request with its sources, for the customer to approve by link.
Reads Specification versions · Offer
- When
The FAT produces a punch list.
AUVYLinks each item to the requirement it refers to and separates defects from new wishes.
You getDefects as tasks and new wishes as change requests.
Reads FAT notes · Specification
- When
On site, the commissioning engineer asks which parameter set is valid.
AUVYAnswers from the project's documents with the version and page it read.
You getAn answer with its source, on a phone at the machine.
Reads Parameter lists · Mails
Sources
Every answer shows its work.
Before a partner puts an answer in front of a client, they want to know where it came from. In AUVY that takes one click.
What did we agree about the Munich site?
The client added Munich as a third site on 12 March.1 It is covered in the revised offer, section 4.2
2 of 3 sentences have a sourceNo source: “The workshop date is still open.”
- 4 Scope, phase 2
- 4.1 Munich is added as a third site,
- as requested by the client on 12 March.
- 4.2 One workshop and two site visits.
- 4.3 Dates follow the revised plan.
Meetings
Kick-off, FAT, site commissioning meetings.
Rules
How AUVY fits the way your trade works.
- Quoted version as the baseline
- Every change is checked against the specification and IO list you quoted on, so extra work is visible before it's done.
- Revision control
- Every version of every list and document is kept, and AUVY names which revision was valid when.
- Your code stays yours
- AUVY reads the documents you give the project. It doesn't touch your PLC projects or controllers.
At a glance
- Walkthrough
- 40 minutes on one of your own projects, free.
- Price
- €59 per person a month, billed yearly, with every project, team and bot included.
- Your data
- Stored on our own servers in Helsinki, never used to train AI, and deleted within 30 days after the contract ends.
- Contract
- Every order includes the data processing agreement under Art. 28 GDPR, German text binding.
- Checked
Questions
Can AUVY compare IO lists and Excel files?
Yes. Give the project each revision, and AUVY names what was added, removed and renamed, with the file and row as the source.
Does AUVY connect to PLCs or SCADA?
No. It reads the documents, lists and mails you give the project, and your engineering tools stay as they are.
Can subcontractors join a project?
Yes. A panel builder or other partner is invited into one project and sees only that project.
Also read
- Machine building & engineer-to-orderThe customer changes the order after release. AUVY carries it into engineering and production.
- IT services & implementation partnersScope moves in the steering committee. AUVY checks it against the statement of work.
- Change requestsEvery change you catch is a change you can price.
