Your starting point
- Accepted library
- Product revisions
- Incoming changes
Scope detail
The accepted library, affected product revisions and the changes you want monitored or handled.
Carry accepted updates into the library and the designs that depend on it.

Agree the work, the evidence and the people responsible before we begin.
The accepted library, affected product revisions and the changes you want monitored or handled.
The recurring assignments, available capacity, delivery and review owners, pricing and how additional work is handled.
The scoped design packages and accepted library updates, with a record of checks, decisions and remaining exclusions.
Time from change to accepted revision, missed dependencies and customer coordination effort.
A family agreement follows successful individual assignments. Automatic preparation is limited to configured work; engineering release stays with the named authority.
A request in an email can affect a drawing, a component and a check. Keep the reason connected to the work.
“Increase the duty.”
Change to assess“Use the replacement pump.”
Change to assess“Keep this access clear.”
Change to assessEngineer reviews the changes and unresolved questions.
Three sources. One design to keep in step.
Illustrated workflow, not a live engineering run. Automated updates depend on supported methods and agreed scope.
See a calculated plant example ↗A practical place to start
Show us the design, what needs to change and the delivery date. We’ll agree the work, files and price.
Bring us a change