Your starting point
- Reference designs
- Approved parts
- Company rules
Scope detail
A recurring product family, reference designs, house rules and the first assignment to complete.
Solutions / Reusable design knowledge
Your design knowledge.
Useful on the next job.
Capture the parts, dependencies and rules needed to deliver a first audit or variant.
A clear start.
A defined handoff.
Agree the work, the evidence and the people responsible before we begin.
Our agreement
- Library boundary
- Source rights
- Acceptance owner
Scope detail
The library scope, source rights, acceptance criteria and a named engineer to accept each entry.
Your delivery
- Versioned library
- Rules & evidence
- First audit or variant
Scope detail
A versioned component and rule library plus the agreed audit or variant that proves it is useful.
What we measure
- Repeated interpretation
- First assignment
- Repeat assignment
Scope detail
Repeated interpretation avoided and time to acceptance on the first and second assignments.
Codification is scoped with a useful first assignment. Coverage grows through accepted work, rather than an open-ended data-cleaning exercise.
The brief changes.
Keep the design together.
A request in an email can affect a drawing, a component and a check. Keep the reason connected to the work.
Customer email
“Increase the duty.”
Change to assessSupplier update
“Use the replacement pump.”
Change to assessSite discussion
“Keep this access clear.”
Change to assessOne connected design
Prepared for reviewOne revision.
One revision.
With its reasons.
DrawingsReference
Parts listReference
ChecksReference
Engineer 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
Start with one assignment.
Show us the design, what needs to change and the delivery date. We’ll agree the work, files and price.
Bring us a change