Revision D replaces revision C. AUVY shows what that means before commissioning.

For system integrators and automation firms, AUVY compares every IO list and specification revision the customer sends and tells you what it touches: signals, panels, checklists. Extra signals go into a change request with the evidence while there is still time to bill them. The project lead signs 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, replaces rev C”, and 14 signals are new, three renamed, two on a panel already built.
The commissioning checklist still reads rev C; the site team finds out at the machine.
The extra signals get done because the start-up can't wait, and never make it onto an invoice.

Use cases

What comes in, and what AUVY does with it.

When
The customer uploads IO list rev D.
AUVY
Compares rev C with rev D, names added and renamed signals, and finds the panels and checklists that still rely on rev C.
You get
Tasks 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.
AUVY
Marks the changed requirements against the version you quoted on, and names the parts of the design they touch.
You get
A change request with the evidence, for the customer to approve by link.
Reads Specification versions · Offer
When
The FAT with the customer produces a punch list.
AUVY
Turns the list you add into items linked to the requirement each one refers to, and separates defects from new wishes.
You get
Defects as tasks, new wishes as change requests, nothing mixed up.
Reads FAT notes · Specification
When
The commissioning engineer asks on site which parameter set is valid.
AUVY
Answers from the project's documents with the version and page it read.
You get
An answer with its source, from a phone at the machine.
Reads Parameter lists · Mails
When
A panel builder works on your project as a subcontractor.
AUVY
Invites them into this one project, where they see its documents and threads and nothing else.
You get
One place to coordinate, without opening your workspace.
Reads The project
When
You want the same way of handling every revision.
AUVY
Turns your revision check into a repeatable workflow the team runs on each new IO list or spec, with review.
You get
The same check every time, whoever is on shift.
Reads Your procedure

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.¹ It is covered in the revised offer, section 4.² The workshop date is still open.

2 of 3 sentences have a sourceNo source: “The workshop date is still open.”

Offer v3.docxSource 2 · section 4, lines 12–14

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.

Example project, synthetic data.

Numbered sources: Every statement in an answer carries a small number. The number points to the file, the version AUVY read and the lines it used.
One click to the passage: Click the number and the file opens beside the conversation, scrolled to the passage and marked in the text. A deck turns to the slide; a spreadsheet selects the cited cells.
It checks itself: AUVY shows how much of an answer is backed by a source and names the sentences that are not, so you know what to verify before it goes out.
Every version kept: Files change during a project. Every version stays, so you can see the text an answer was based on and what has changed since.

Meetings

Kick-off, FAT, site commissioning meetings.

AUVY prepares from the project documents and follows up from the notes and minutes you add.

MeetingsBeforeAfter

Kick-off and design reviewThe specification as quoted, open questions, and assumptions still unconfirmed by the customer.Answers logged against the requirement they settle; changes marked against the quoted version.

Factory acceptance testWhat changed since the design review and which tests it affects.Punch list split into defects and wishes, tasks and change requests drafted.

Daily commissioning meetingYesterday's open items and today's documents, current version only.Items updated with owners; the report to the customer drafted for review.

How AUVY fits

How AUVY fits the way you have to work.

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; AUVY names which revision was valid when.
Customer approval by link: The customer approves a change request from a link, without an account; the answer is recorded in the project.
Your code stays yours: AUVY reads the documents you give the project. It doesn't touch your PLC projects or controllers.

For every project

The same ground rules, whatever you deliver.

Only what you give it: Each project reads only the sources you give it: a folder, a mail thread, the Outlook, Teams and SharePoint places you connect.
One project, one room: Project content stays in its project. Personal notes stay yours. An outside partner is invited into one project, never into the workspace, and a read-only link shows one view and nothing else.
A person decides: AUVY prepares; a person accepts, edits or rejects. Nothing leaves until someone accepts it. When a step needs a person, AUVY stops and asks them by name.
Everything on record: Every answer cites the document and the exact version it read, and shows the sentences that have no source. Every version is kept, and a client's answer by link is recorded in the project.
Data in the EU, no training: Workspace and account data is stored in the EU (Helsinki); AI runs through approved providers in EU regions. Customer data is never used or designated for model training. Every subprocessor is listed in the trust center.
No one is scored: AUVY senses the project, not the people: no per-person performance views, no employee scoring. The AVV under Art. 28 GDPR is part of every order.

Questions

Can AUVY compare IO lists and Excel files?

Yes. Give the project each revision; AUVY compares them and 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. Your engineering tools stay as they are.

How do extra signals get billed?

AUVY marks them against the quoted revision and drafts a change request with the evidence, for the customer to approve by link before or while the work is done.

Can subcontractors join a project?

Yes. A partner is invited into one project and sees only that project.

See it on one of your own projects.

Book a walkthrough Sign in

Revision D replaces revision C. AUVY shows what that means before commissioning.

A week in integration.

What comes in, and what AUVY does with it.

The customer uploads IO list rev D.

The specification changes after the order.

The FAT with the customer produces a punch list.

The commissioning engineer asks on site which parameter set is valid.

A panel builder works on your project as a subcontractor.

You want the same way of handling every revision.