After the order, many buyers wait for the machine. The next time they see it is at the supplier, fully built, a few days before shipment. Every finding at that point costs steel, software and weeks. The cheap moment for changes is earlier: when the machine exists on paper and as a model.
Two documents, two authors
The user requirement specification is written by the buyer and says what the equipment must achieve. The functional specification is written by the supplier after the order and says how each requirement will be fulfilled: stations, sequence, controls, interfaces.
For the assembly cell AC7, supplier B delivered a functional specification of 58 pages in week 5 after the order. The project lead did one thing with it before anyone discussed details: a trace.
The trace
Every requirement of the specification is linked to the section of the functional specification that answers it. Three results are possible. The requirement is answered as specified. It is answered with a deviation. Or it is not answered at all, which is the most frequent and the most dangerous case.
On AC7, 58 of 64 requirements were answered as specified. Six want requirements had deviations that were known from the quotation, for example seven purchased components outside the preferred list of the plant. Each deviation was agreed in writing with an adapted criterion, so that it could still be tested later.
The design review
In week 6 the team spent one day at the supplier with the layout, the 3D model and the sequence diagram. The team was the same one that had written the requirements, with operators and maintenance technicians.
The review follows five questions:
- Operation: where does the operator stand, reach, look and walk during one cycle, a refill and a changeover?
- Faults: what happens at each station when a part is missing, wrong or jammed, and who can clear it how fast?
- Maintenance: how is each wear part reached and exchanged, and which components are not on the plant list?
- Quality: how is each monitored value measured, stored and checked with a reference unit?
- Site: do footprint, media, transport path and interfaces match the layout?
Nine requirements of AC7 had the design review as their verification stage, among them the access to all maintenance points, the controls hardware, the footprint and the risk assessment of the supplier, which was presented and reviewed with the safety specialist.
What the review found
| Result | Example | Findings |
|---|---|---|
| Design changed | Feeders filled from outside the guard, second door at the screw station | 11 |
| Clarified in the functional specification | Content of the 14 traceability fields | 27 |
| Accepted as designed | Position of the control cabinet | 8 |
Forty-six findings in one day. Eleven of them changed the design, and none of them changed the price, because each could be traced to a requirement in the specification.
The design release
The review ends with a document. All findings are closed or have an owner and a date, and both sides sign the design release. Only then does the supplier order long lead time parts. For AC7 this was week 8.
Changes after the release
Two kinds of changes come up in every project, and they must not be mixed.
A change inside the specification is the task of the supplier. If the cell cannot reach 25.0 seconds with the released design, the supplier changes the design.
A new wish of the plant is a change request. It gets a written description, a price, an effect on the date and a decision by the one person on each side who may agree changes. Most disputes about equipment start with a promise made at the machine by someone without a mandate.
Keep one list of all change requests. Every one of them is a requirement that was missing, and the best input for the next specification.