A development project for an electrical control system rarely fails in week one. It usually fails late: commissioning slips because nobody defined what "complete" means, or a line is accepted and then blamed on the integrator for problems the buyer could have caught in review. For procurement teams, the practical answer is to treat the deliverable list as part of the purchase specification, agreed and signed off before the first panel is built.
The list below is written from a buyer's point of view, not a controls engineer's. Each item is something you can hold in a meeting, and each one answers a question you will otherwise ask on site with a contractor waiting.
Before the build: documents that set the boundary
1. User Requirement Specification (URS) and its functional description
The URS states what the machine or line must do, not how. Ask for mode definitions (manual, semi-automatic, automatic, maintenance), the machine states each mode allows, the interlocks and why each one exists, alarms and the response each one expects, and a power-loss and recovery description. If your plant changes recipes, has shift patterns, or runs utilities that fail in a known way, those conditions belong here.
A useful test: hand the URS to your maintenance supervisor. If they cannot describe how a fault is found and cleared from it, the document is not finished.
2. Functional Design Specification (FDS) and a signed design review record
The FDS translates the requirements into an approach: the control architecture, the PLC and drive platform, the network layout, HMI structure and screen list, the I/O strategy, and how the system talks to upper-level systems such as MES or SCADA. Request the design review as a dated record with an action list, owners and close-out dates — not a photo of a whiteboard.
This is also where you settle standards before they get expensive: naming convention for tags, components and programs; drawing format; language of labels and screens; which cable and gland types your plant accepts. A single page of standards agreed now prevents three rounds of rework on drawings later.
3. Bill of materials with models, brands and alternatives
A BOM that says "servo drive, 1.5 kW" cannot be compared between suppliers and cannot be serviced in three years. Ask for manufacturer and model per line, plus an approved substitute for key items such as the PLC CPU, drives, safety relays and HMI. State the obsolescence rule in writing: if a component is discontinued during the project, the supplier proposes the replacement and re-tests the affected function instead of silently swapping it.
4. Method statements for welding, crimping, torque and post-weld inspection
Ask how the panel is actually built: the crimp tool and terminal range, torque values for busbar and power connections and how they are marked, conductor marking rules, segregation of power and signal wiring, minimum bend radius, and who inspects after welding and against which checklist. This is the cheapest quality lever in the whole project — a fabrication standard agreed at quotation stage costs nothing, while loose connections found in commissioning cost line downtime.
During the build: evidence you can check remotely
5. Panel layout and electrical drawings, at issue-for-manufacture status
Request schematic, terminal and layout drawings, plus the bill of materials cross-referenced to component designators. Confirm the drawings are issued, not "current working", and that every revision carries a number, a date and a reason for change. A drawing set with no revision history is a maintenance liability the day the machine reaches your plant.
6. Wiring, continuity, and dielectric test records
Ask for the completed check sheets from the supplier's own test bench: continuity against the circuit, point-to-point I/O verification, insulation or dielectric test with the test voltage and duration used, and the earth continuity result. The values and the instrument used should appear on the record. If a supplier cannot produce test records before shipment, plan your factory acceptance test to cover every one of those checks yourself.
7. A FAT protocol with a pass/fail line for every test case
Do not accept a FAT that is a demonstration. Write the protocol before the build: each test case numbered, with the expected result, the actual result and a signature column. Cover power-up and recovery, every interlock and safety function, manual and automatic operation, alarm behaviour, recipe or product changeover, and the interface with your upstream or downstream equipment. Agree in advance what counts as a show-stopper and what can be closed after shipment, and put the deferred list in the shipping document.
8. Software delivered as a working project, not a locked binary
Ask for the editable PLC program, the operator and maintenance HMI project and any vision, motion or safety configuration, with a documented tag list and a change log. Agree the versioning rule and who signs off each release. If an integrator refuses to hand over source, negotiate that at contract stage — the alternative is that every future modification has to go back to one supplier.
9. A written I/O list and interface list with neighbouring systems
The I/O list names every signal: tag, device, direction, signal type and terminal. The interface list does the same for boundaries you do not own: the plant air and water supply, the upstream conveyor, the MES tag exchange, the 24 V supply load. Interface disagreements cause most on-site arguments, and a signed list settles them before anyone arrives.
At handover: what the supplier must leave behind
10. As-built drawings that match the machine you received
Make as-built documentation a release condition for the final payment. Compare at least a sample — one panel, one circuit, one safety loop — against the drawings before you sign. A redline marked "as-built" is acceptable only with a date and an author; an unmarked set is not as-built.
11. Safety documentation and CE marking technical file
For equipment sold into the European market, expect the technical file, the risk assessment with the residual risks listed, the standards applied, the Declaration of Conformity, and the safety function validation record showing the measured response of each safety function, such as a light curtain stop or a safety door interlock. For machinery that also carries automated production line solutions content, check which parts of the safety argument belong to the line supplier and which to the machine builder.
12. A performance and reliability run you can verify yourself
Agree the run rate, the product or material used, the number of consecutive cycles or hours, and how a stop is counted — including minor stops under a set duration, which are the ones that quietly consume capacity. Take the counters from the machine itself rather than from a stopwatch, and keep the run log with the acceptance certificate.
13. Training records and an operator troubleshooting guide
Ask for a training plan with the attendee list, the topics covered and the person who delivered it. Separately request the troubleshooting guide that maps each alarm code to what it means, what your operator may do, and when to call for support. This document decides whether a fault costs ten minutes or a flight and a two-day wait.
14. Spare parts list split into wearable and critical spares
Two lists, not one. Wearable parts with a replacement interval, and critical spares whose failure stops the line, each with model number and a lead time. For anything with a lead time measured in weeks, ask whether the supplier holds stock and at what price.
15. A defect list with owners, dates and a retention trigger
Close the project on a document, not a handshake. Every open item gets a severity, an owner and a due date. Retention is released against that list, and the warranty period start date is written down — a warranty that starts at shipment rather than after your commissioning window is a common and expensive surprise.
How to turn this into a contract that holds
Take the fifteen items and map each one to a payment milestone. Documents reviewed and accepted, panel built and tested, FAT passed, site commissioning, performance run, final documentation. That mapping is what makes the list enforceable; a deliverable with no milestone attached is a wish.
Then compare suppliers on the same page. Two quotations for the same machine can differ by a wide margin simply because one includes an editable program, an as-built drawing set and a validated safety loop, and the other prices them as extras discovered later.
Where development capacity enters the picture
If the control system is being developed rather than copied from a proven design — a new machine, an unusual process, or a line where the automation concept has not been built before — ask the supplier to show how the controls work is staffed and reviewed alongside the mechanical design. Product R&D accelerator support is worth asking about in that situation, together with hardware test capability, because the cheapest place to find a controls fault is on a bench, not on your production floor. Shenzhen PowerDe Automation Precision Equipment positions its engineering work across equipment R&D, hardware testing and line integration, so it is a supplier to put on the shortlist when the deliverable list above has to be built from a first design rather than a standard catalog machine.
The short version for your next RFQ
Attach the deliverable list to the enquiry and require each bidder to state, line by line, whether it is included, excluded or optional. The exercise usually removes more ambiguity than any technical clarification round. Buyers who do this rarely argue about documentation at handover — and the ones who skip it almost always do.
Send the fifteen deliverables to your current controls supplier and ask for a line-by-line confirmation against your open project. If the answers come back vague, that is the time to reopen the specification — before the panel is built.
