---
title: "AUVY for machine building: spec changes into production"
description: "AUVY catches customer changes after order release, shows their effect on engineering, parts and delivery, and tracks supplier dates through to acceptance."
url: https://www.auvy.ai/use-cases/machine-building
lang: en
site: AUVY
brief: https://www.auvy.ai/llms.txt
---

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

A customer change after design release tends to reach production late, and then the extra cost stays with you. AUVY follows each order from release to acceptance, shows what a changed specification or a late supplier means for design, purchasing and delivery, and drafts the change request for the project manager to sign off.

[← Use cases](https://www.auvy.ai/use-cases) For: Owners, project managers, design and production engineering, purchasing, service

Machine building & engineer-to-order

## A week on a customer order.

After release, the customer asks sales by mail for a different conveyor height. A supplier confirms a drive two weeks late in a PDF that nobody links to the assembly date.

Use cases

## What comes in, and what AUVY does with it.

1. When
### The customer asks for a different conveyor height after release.
AUVY
Marks the change against the order specification and names the drawings, parts and dates it touches.
You get
A change request for the customer to approve by link, with the price and date effect for you to fill in, and tasks for design and purchasing.
Reads Mail · Order specification · Part list export
2. When
### A supplier confirms a later delivery date.
AUVY
Compares the confirmation 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
3. When
### Engineering releases a new revision of an assembly.
AUVY
Names what changed since the last revision and whether production is still working from the old one.
You get
Production informed with the source attached, before the wrong part is made.
Reads Revision exports · Production plan
4. When
### The customer's acceptance test is next week.
AUVY
Lists every change agreed since the order, with its status and sources.
You get
An acceptance where every deviation is explained.
Reads Change requests · Specification · 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 The workshop date is still open.

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

**Offer v3.docx** Source 2 · section 4, lines 12 to 14

1. 4 Scope, phase 2
2. 4.1 Munich is added as a third site,
3. as requested by the client on 12 March.
4. 4.2 One workshop and two site visits.
5. 4.3 Dates follow the revised plan.

Example project, synthetic data.

Meetings

## Order kick-off, design reviews, acceptance.

Meetings Before After

Order kick-off The specification as sold, open points from sales and the dates promised to the customer. Agreements logged against the specification, with tasks for design, purchasing and production.

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

Factory and site acceptance Every agreed deviation with its sources. Remaining items as tasks with owners and dates, and the protocol filed with the order.

Rules

## How AUVY fits the way your trade works.

Your ERP stays the system of record

AUVY reads the exports and documents you give the project and writes nothing 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, and the answer is recorded with the order.

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](https://eur-lex.europa.eu/eli/reg/2016/679/oj) , German text binding.

Checked

30 September 2026

Questions

### Does AUVY connect to our ERP?

Not directly. It reads the exports, part lists and documents you give the project, and 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 the supplier confirmations you give the project, compares them with what you ordered and shows which steps depend on each date.

Also read

- [System integrators & automation Revision D replaces revision C. AUVY shows what that means before commissioning. ](https://www.auvy.ai/use-cases/system-integrators)
- [Contractors & building services The schedule moves. AUVY makes sure your crews and your claims move with it. ](https://www.auvy.ai/use-cases/construction)
- [Change requests Every change you catch is a change you can price. ](https://www.auvy.ai/use-cases/change-requests)
[All use cases →](https://www.auvy.ai/use-cases)

## See it on one of your own projects.

[Book a walkthrough](https://www.auvy.ai/walkthrough) [Sign in](https://www.auvy.ai/os/)
