How do machine builders answer a customer specification?
An enquiry for a special-purpose machine rarely arrives as one document. The customer sends a requirement specification that describes the task: the product, the process steps, the output wanted and the space available. Many customers call it a user requirement specification, or URS. German-speaking customers call it a Lastenheft. Alongside it come the plant's own factory standards and the commercial terms.
The builder replies with a quotation and a functional specification, which in German practice is the Pflichtenheft. It describes the concept offered: stations, sequence, controls, guarding, interfaces and what is excluded. Once both sides sign it, the functional specification is normally the document the machine is accepted against. A requirement that was in the URS and never reached the functional specification is where most later arguments start.
| Document | Written by | What it fixes |
|---|---|---|
| Requirement specification (URS or Lastenheft) | Customer | The task: product range, process, output, changeover, footprint, utilities and the acceptance wanted |
| Factory standards | Customer's plant or group engineering | Approved component brands, the control platform, software structure, electrical and pneumatic practice, colours, labelling and documentation format |
| Functional specification (Pflichtenheft) | Builder | The machine offered: concept, stations, sequence, safety concept, interfaces, exclusions and assumptions |
| Performance and acceptance criteria | Both, agreed in the contract | Cycle time, output, availability or OEE, capability figures, and how, where and for how long each is measured |
| Deviation list | Builder | Each point where the offer differs from the requirement specification or a factory standard, with the reason |
- Split the requirement specification and every factory standard into single requirements, each with its section number.
- Mark each one against the functional specification: complies, deviates, needs clarification or not addressed.
- Check the performance figures separately. Write down the product, the operator count and the measuring period each figure assumes.
- Collect the open points into a deviation list and a list of questions, and send both with the quotation.
- After the customer replies, carry the agreed deviations into the signed functional specification so that one document governs acceptance.
The row-by-row record is a compliance matrix. A ready layout for a URS reply is on the URS response matrix template page.
Which rules and standards come up in a machine specification?
A requirement specification usually names the law of the country where the machine will run and then a short list of safety standards. The table gives the ones a builder meets most often, at name level only. It is our own summary and it is not legal advice. Work from the texts and editions your contract names.
| Rule or standard | What it is | What to look for in the specification |
|---|---|---|
| Machinery Directive 2006/42/EC | The EU law that machinery placed on the EU market must meet today. It sets essential health and safety requirements and asks for a risk assessment, a technical file, a declaration and CE marking | Whether you supply a complete machine with a declaration of conformity or partly completed machinery with a declaration of incorporation |
| Machinery Regulation (EU) 2023/1230 | The regulation that replaces the Directive. The Commission states that it applies from 20 January 2027 | The date the machine will be placed on the market. A long project can start under one text and deliver under the other. See the Machinery Directive and Regulation page |
| EN ISO 12100 | The general standard for risk assessment and risk reduction in machine design | Whether the customer wants to see the risk assessment, and at which design review |
| EN 60204-1 | The standard for the electrical equipment of machines | Conflicts between it and the plant's own electrical standard, and which one governs |
| Supply of Machinery (Safety) Regulations 2008 and UKCA | The Great Britain rules for new machinery. Government guidance says CE marking continues to be recognised there | Which marking the customer asks for, and instructions in English |
| OSHA rules and NFPA 79 | For US buyers: federal workplace rules on machine guarding, and the NFPA electrical standard for industrial machinery | That CE marking is not a US requirement. The specification should say which US standards the buyer expects the machine to meet |
| The customer's factory standards | Private documents that sit on top of the law | The order of precedence if a factory standard and a named safety standard disagree |
Machines with a safety-related control system often also name a functional safety standard. Where a specification asks for a safety integrity level, the overview on IEC 61508 and IEC 61511 explains the terms. A machine that contains pressure equipment may also fall under the Pressure Equipment Directive.
What goes in a machine builder's deviation list?
On a machine project the costly deviations are seldom about the process. They are about the parts the customer's maintenance team wants to see when it opens the cabinet, and about how performance is proved. These are the areas to read first.
| Area | What to check before you sign the functional specification |
|---|---|
| Brand and component lists | Named makes for PLC, drives, pneumatics, sensors, robots and safety devices. Check whether an alternative needs written approval and who pays if the listed part has a long lead time |
| Cycle time and output | The product variant, the infeed quality, the operator count and whether the figure is gross or net of stoppages caused by the customer's material |
| OEE or availability guarantees | The formula the customer uses, the length of the acceptance run, which stoppages count against the builder and what happens if the figure is missed |
| Capability figures | Which characteristics are measured, the sample size, who supplies the parts and the gauges, and whether the figure is proved at FAT, at SAT or both |
| Controls standards | PLC platform and firmware level, software structure and naming rules, HMI layout, network and data interfaces to the plant systems, and remote access |
| Safety concept | Guard types, access and operating modes the customer wants. A plant standard may ask for more than your risk assessment needs, or for something it does not support |
| Documentation language and format | The languages for instructions, HMI texts and drawings, the file formats, the plant's numbering scheme and the number of paper sets |
| Acceptance and handover | Whether FAT and SAT are both required, who supplies test product, and which documents must be complete before each test |
| Training and spare parts | Days of training included, the spare and wear parts list wanted with the offer, and any stock the builder must hold |
Put the test conditions next to every guaranteed figure
A cycle time or OEE figure with no stated product, duration and stoppage rules cannot be passed or failed. If the requirement specification gives a number and nothing else, raise a clarification and write your assumptions into the functional specification.
Which documents follow after the order?
After the order the customer's document list turns into dated submissions. Some are contract documents the customer approves. Others are legal documents the builder owes under the machinery rules whether the customer asks or not. The contract and the law that applies decide the list. A machine builder should expect these.
| Document | What the customer looks for |
|---|---|
| Design review records | Minutes of each layout, mechanical and controls review, with the actions agreed and who closes them |
| FAT protocol | The test steps, the acceptance figure for each, the product used and the requirement each step proves. See the machine FAT protocol template |
| FAT report | Signed results, the list of open points with owners and dates, and the release to ship |
| SAT protocol and report | Tests repeated or added after installation, run with the plant's utilities and product. See site acceptance test |
| Declaration of conformity | For a complete machine: the builder's signed statement that it meets the machinery rules, issued with the machine |
| Declaration of incorporation | For partly completed machinery: the statement of which requirements are met, supplied with assembly instructions |
| Instructions | Operating and maintenance instructions in the language of the country of use, matching the machine as built |
| Technical file | Kept by the builder for the authorities. The contract says which parts of it, if any, the customer receives |
| Spare and wear parts list | Part numbers, makes and recommended quantities, in the plant's format |
| As-built drawings, schematics and software backup | The revision that matches the machine after SAT changes |
The handover set is close to what process industries call a turnover package. The difference between the two acceptance tests is explained under FAT vs SAT, and the factory acceptance test checklist covers what to have ready before the customer travels.
How does OdysseyGPT help?
OdysseyGPT reads the documents you upload and sets them against the customer's written requirements. Every finding shows the passage it rests on in both documents, so an engineer can check it in seconds. Document Review takes the requirement specification and factory standards as the base and your functional specification and quotation as the documents to check. It also works in reverse, listing statements in your documents that the customer's text does not cover. The other tools each read a narrower set.
| Your document | Tool | What it reports |
|---|---|---|
| Requirement specification, factory standards and your functional specification | Document Review | A status and a pair of quotes for each customer requirement, plus assumptions and exclusions in your text that the customer has not answered |
| Requirement specification and factory standards on their own | Customer Specification Review (beta) | A register with one line per requirement, grouped as technical, quality, documentation, test or commercial, with unclear items flagged |
| The customer's machine data sheet and your filled copy | Datasheet Comparison (beta) | Matched fields and each difference in value, with the cell or line it came from |
| Deviation list and the customer's replies | Deviation Register (beta) | One running record of each deviation through the clarification rounds to the customer's decision |
| The contract's list of documents to submit | VDRL/MDR Tracker (beta) | A register of each required document with its due date, revision and status |
| Your inspection and test plan and the customer's quality clauses | ITP Validator (beta) | Stages the customer asks for that the plan leaves out, and witness points that do not match |
| FAT protocol with the test plan, calibration evidence and open-points list | FAT Readiness Check (beta) | Whether the documents the test depends on are in place, with blockers listed apart from review items |
| FAT measurement records and gauge certificates | Calibration Validity Check (beta) | Each instrument named in a record matched to a certificate valid on the test date |
| The documentation folder and the customer's index | MRB Readiness Check (beta) and MRB Compiler (beta) | Documents that are missing, unapproved or at the wrong revision, and a manifest in the customer's index order |
The tools are grouped by project stage: tender, inspection and handover. The manufacturing page shows how they fit together. There is no tool for the site acceptance test itself.
What does a result look like?
The table below is an invented example. The customer, the machine, the section numbers, the builder's documents and every figure are made up to show how a result is laid out. Nothing in it comes from a real project, a real builder or a standard.
| Customer requirement (quoted) | Builder's document (quoted) | Status | Note |
|---|---|---|---|
| "The cell shall assemble housing variants A, B and C without tool change." (URS 3.1) | "Variants A, B and C are processed on common nests. No change parts are required." (Functional specification 2.2) | Complies | Same three variants and the same no-change statement in both documents. |
| "Cycle time shall not exceed 12 seconds per part, measured over an eight-hour production shift." (URS 4.2) | "Technical cycle time: 12 s per part in automatic mode with parts supplied to drawing." (Functional specification 5.1) | Clarification | The figure matches. The builder states no measuring period and adds a condition on part quality. |
| "All PLC and drive components shall be taken from the approved list in Factory Standard FS-07." (URS 6.1) | "Servo drives: builder's standard make, as listed in the component schedule." (Quotation Q-1182, item 14) | Deviates | The drive make offered is not on the customer's list. Declare it or price the listed make. |
| "Overall equipment effectiveness of at least 85 % shall be demonstrated during a three-shift acceptance run at site." (URS 4.5) | "Availability of 95 % is demonstrated at FAT over a four-hour run." (Functional specification 9.3) | Deviates | A different measure, a shorter run and a different place. This needs a decision before the order. |
| "HMI texts and operating instructions shall be supplied in English and Polish." (URS 8.3) | "Documentation language: English." (Quotation Q-1182, item 22) | Deviates | The second language is not offered. |
| "The supplier shall provide the risk assessment for review at the design freeze meeting." (URS 7.2) | No matching statement found in the documents supplied. | Not addressed | The builder's documents do not say whether the risk assessment is shared. Answer it in the offer. |
| "Machine capability shall be proven on 50 consecutive parts for the press-in force." (URS 4.7) | "Capability study on 50 parts for press-in force and press-in depth at FAT." (FAT plan FP-03, step 11) | Complies | The builder's study covers the characteristic asked for and one more. |
| "A recommended spare parts list with prices shall be submitted with the offer." (URS 9.1) | "A spare and wear parts list is supplied with the final documentation." (Functional specification 11.4) | Deviates | The list is offered later than the customer asks, and prices are not mentioned. |
A project engineer opens the two quotes on each row and confirms or changes the status. Rows left as deviates or clarification go to the deviation list and the question list. Rows marked not addressed show where the functional specification needs another paragraph.
Where OdysseyGPT falls short
- It does no risk assessment. It does not identify hazards, choose protective measures or judge whether a safety concept is adequate.
- It does no CE or UKCA conformity assessment and it does not tell you which legislation or which standards apply to your machine.
- It does not write the technical file, the declaration of conformity, the declaration of incorporation or the instructions.
- It does not read layout drawings, mechanical drawings, electrical or pneumatic schematics, or PLC and robot programs. A requirement that is answered only on a drawing or in code is not checked.
- It cannot tell you whether a cycle time, an OEE figure or a capability figure is achievable. It shows what each document says. Your engineers judge the design.
- It holds no standards and no factory standards. A rule that sits only inside a named document is checked only if you upload that document as readable text.
- It can pair a requirement with the wrong passage or miss one, most often where a requirement specification repeats the same wording for several stations. The quotes are shown so a person can catch this.
- It does not run a FAT or a SAT, record measurements or connect to the machine.
- Tools carrying a beta marker on this page are available on request, and we set each team up ourselves.
Talk through your tender review
See how OdysseyGPT reviews a tender
Tell us how your team reviews tenders today. We can walk through an example together.
