A guide to clearly defining test, file and training handover between the machine manufacturer, automation team and end user.
Accepting a machine’s automation involves more than seeing the PLC run or the operator screen open. The manufacturer and automation team should agree at the outset on functions to test, on-site checks and files to hand over. This provides a shared technical scope for delivering the machine to its end user.
Handover criteria follow the operating sequence
Documenting automatic cycles, manual commands, settings and process transitions also defines the test scope. State which operation is expected under which conditions rather than simply “the machine will run”. Behaviour observed during testing can then be compared against an agreed description.
If a machine works with other equipment, include the signals exchanged between them. Define the direction and meaning of signals such as ready, running, fault or process complete. The same document can clearly allocate responsibilities for mechanical manufacture, field connections and automation software.
Workshop and site tests may have different scopes
Not all actual field equipment may be connected during workshop panel and software checks. Functions checked with simulated signals are recorded with the test conditions used. Seeing an input in software and verifying that the real sensor operates in the correct position on the machine are separate checks.
At the customer site, checks use actual operating conditions once mechanical installation, connections and peripheral equipment are complete. Separating workshop checks from items to finish on site avoids treating an incomplete site test as complete. Decide in advance who will accept test results.
What headings can an acceptance checklist include?
The checklist is prepared for the machine. A row with the function, initial conditions, expected result and actual result provides a workable structure. Mechanical and electrical safety requirements are assessed within their own project scopes, rather than being left unclear under software function tests.
| Check group | Example scope |
|---|---|
| Field signals | Sensor and equipment information shown under the correct names |
| Operating modes | Manual commands and automatic cycle transitions |
| Operator screen | Correspondence of commands, statuses, settings and user permissions |
| Alarms | Defined events, descriptions and restart conditions |
| Records and connections | Reports and peripheral equipment information included in the scope |
Which software and documents should be handed over?
PLC and HMI projects, electrical drawings, device lists and operating instructions should clearly identify their machine. Delivered backups should include the final commissioning changes. A clear arrangement can be agreed for file names, versions and handover dates.
An editable project file and device backup may contain different information. At the quotation stage, the manufacturer should clarify which files will be supplied, the software versions needed to open them and usage conditions. Matching files to the relevant machine and version is part of handover as well as providing the files.
Operator and maintenance training can have separate scopes
Operating the machine, using production settings and reading alarm descriptions are daily operator tasks. The maintenance team may need different device definitions, drawings and fault investigation information. Training defines which information goes to each group.
If the end user needs screens or documents in another language, state this during manufacture. Training location, attendees and site readiness are also included in the handover plan. This establishes in advance what will be demonstrated and which documents will be left at the end of commissioning.
How is the scope between Enopan and the manufacturer prepared?
At Enopan, we address suitable PLC software, HMI screens, electrical control panels and on-site commissioning together for each machine. PLC/HMI program backups, electrical drawings, an operating manual and operator training are part of our standard handover. Project-specific tests and connections are defined separately.
For the first discussion, share the machine’s function, operating sequence, equipment list and end-user expectations. Also state which team will handle panels, field connections, workshop tests and customer-site commissioning. The quotation and handover list can be prepared around this division of responsibilities.
Define your machine automation and handover scope with us
Share the operating sequence, equipment list and tests expected at the customer site. We can assess software, panels, commissioning and handover files within one plan.
