The customer changes the order after release. AUVY carries it into engineering and production.

For machine builders and engineer-to-order manufacturers, AUVY follows a customer order from release to acceptance. When the customer changes the specification or a supplier moves a date, it shows what that means for design, purchasing and delivery, and drafts the change request. The project manager signs off.

← Use casesFor: Owners, project managers, design and production engineering, purchasing, service

Machine building & engineer-to-order

A week on a customer order.

The customer wants a different conveyor height after the design is released, in a mail to sales.
A supplier confirms a drive two weeks later than ordered, in a PDF nobody links to the assembly date.
The change reaches production late, and the extra cost stays with you.

Use cases

What comes in, and what AUVY does with it.

When
The customer asks for a different conveyor height after release.
AUVY
Marks the change against the specification of the order, and names the drawings, parts and dates it touches from the documents you gave the project.
You get
A change request with price and date effect to be filled in, for the customer to approve by link, and tasks for design and purchasing.
Reads Mail · Order specification · Part list export
When
A supplier confirms a later delivery date.
AUVY
Reads the confirmation, compares it with the date you ordered, and shows which assembly step and customer date depend on it.
You get
The risk visible early, with a task and a note to the customer drafted.
Reads Supplier confirmation · Order · Plan
When
Engineering releases a new revision of an assembly.
AUVY
Compares it with the previous revision and names what changed and whether production is working from the old one.
You get
Production informed with the source attached, before the wrong part is made.
Reads Revision exports · Production plan
When
The customer's acceptance test is next week.
AUVY
Lists every agreed change since order, its status, and the evidence behind it.
You get
An acceptance where every deviation is explained and on record.
Reads Change requests · Specification · Mails
When
Service gets a call about a machine delivered last year.
AUVY
Answers from the order's record: what was agreed, which changes were made, which revision was built.
You get
Service knows the machine as delivered, not as first quoted.
Reads The whole order
When
You want one view of open changes across orders.
AUVY
Builds a small tracker in the project from your description, fed from the change requests, edited together.
You get
Open changes, their status and owners in one place.
Reads Change requests · Your request

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

Order kick-off, design reviews, acceptance.

Prepared from the order's documents; followed up from the minutes and notes you add.

MeetingsBeforeAfter

Order kick-offThe specification as sold, open points from sales, and the customer's promised dates.Agreements logged against the specification; tasks set across design, purchasing and production.

Design review with the customerChanges since order, their status, and decisions the customer still owes.New wishes marked as change requests; confirmations drafted for review.

Factory and site acceptanceEvery agreed deviation with its evidence.Remaining items as tasks with owners and dates; the protocol filed with the order.

How AUVY fits

How AUVY fits the way you have to work.

Your ERP stays the system of record: AUVY reads the exports and documents you give the project. It doesn't write to your ERP or PLM.
The order as sold is the baseline: Changes are checked against the specification you gave the project, so every deviation is priced or given away on purpose.
Customer approval by link: The customer approves a change request from a link, without an account; the answer is recorded with the order.
A person decides: Nothing goes to the customer or a supplier until someone accepts it.

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

Does AUVY connect to our ERP?

Not directly. It reads the exports, part lists and documents you give the project; your ERP remains the system of record.

What counts as a change?

A relevant change in the sources you connected: a new requirement, a moved date, a changed quantity or revision. AUVY marks it where it arrived and shows what it affects.

Can AUVY track supplier delivery dates?

It reads supplier confirmations you give the project, compares them with what you ordered, and shows which steps depend on the date.

Where does our data live?

Workspace and account data is stored in the EU (Helsinki). Customer data is not used for model training.

See it on one of your own projects.

Book a walkthrough Sign in

The customer changes the order after release. AUVY carries it into engineering and production.

A week on a customer order.

What comes in, and what AUVY does with it.

The customer asks for a different conveyor height after release.

A supplier confirms a later delivery date.

Engineering releases a new revision of an assembly.

The customer's acceptance test is next week.

Service gets a call about a machine delivered last year.

You want one view of open changes across orders.