Skip to content
Equipment Specification and Acceptance | Part 2 of 6

User Requirement Specification: Requirements That Can Be Tested

How to collect requirements with the users and write a URS in which every line has a criterion, a method and a verification stage.

You can only accept what you have specified. The user requirement specification, in short URS, is the document in which the buyer says what the equipment must achieve and how that will be proven. It is the cheapest place to get a machine right.

Collect with the people who will live with it

A specification written by one engineer contains what one engineer knows. For the assembly cell AC7 the project lead ran three sessions of three hours with eight people:

  • Product and process: manufacturing engineering and quality bring variants, tolerances, monitored values and test methods.
  • Use: the supervisor, operators and maintenance walk through a shift, a changeover, a fault and a repair.
  • Site: safety, controls, facilities and purchasing bring layout, media, interfaces, documents and the commercial frame.

The sessions produced 97 notes. After merging doubles and turning solutions into requirements, 64 remained in eight categories.

Five rules for every line

  1. One requirement per line. One number, one sentence with shall, one test.
  2. What, not how. Describe the result. The solution belongs to the supplier, unless a plant standard applies.
  3. A number and a unit. Seconds, percent, millimeters. Words such as fast, robust or easy are not requirements.
  4. A condition. For which variant, with whose operators, over which duration.
  5. Must or want. A must excludes a quotation that fails it. A want earns points in the comparison.

A note from the session said that changeover should be easy. The requirement says: changeover between variants shall take at most 10 minutes from the last good unit to the first good unit. A note said that the screw station must be reliable. The requirement says: screw torque shall reach a machine capability index of at least 1.67 on 50 consecutive units.

Must and want

Of the 64 requirements of AC7, 42 are a must and 22 are a want. The test for a must is one question: would we reject the best quotation because of it? If the answer is no, it is a want.

Criterion, method and stage

Each requirement gets three more entries. The acceptance criterion says what is measured, with sample size or duration. The method is a document review, an inspection, a test or a measurement. The stage says where the proof takes place.

Stage Where and when Requirements
Design review On paper, before parts are ordered 9
Factory acceptance test At the supplier, before shipment 31
Site acceptance test In the plant, after assembly 20
Performance run In the plant, in production 4

These three entries turn the requirement list into the acceptance plan. The protocol for the factory test of AC7 was simply the 31 lines with the stage factory acceptance test, each with its criterion.

The document around the list

The requirement list is the core. Around it, a few pages give the supplier what a serious quotation needs: scope and interfaces, product and volume with the four performance data, the site with layout and media, the acceptance stages with the classes of open points, the project milestones and the form of the quotation.

Three things do not belong in it. Solutions that fix the design without a reason. Pasted pages of standards: name the rule that applies and attach it. And contract wording: terms, liability and warranty belong in the order documents and are reviewed by purchasing and legal counsel. Safety and conformity requirements are listed as test points, and your safety specialist checks which rules apply.

Release before the inquiry

Production, maintenance, quality and safety sign the specification. A signature means: my requirements are in it, and I will take part in the tests. Only then does the inquiry go out.

The effort for AC7 was 112 hours: the three sessions and 40 hours of writing. The last cell cost EUR 86,000 in retrofits.

Newsletter

One Lean idea.
Every two weeks.