By Halcyon Machinery · Published and reviewed
What should a roll forming machine control handover include?
Agree a named inventory of PLC files, HMI files, recipes, drive parameters and access rights before placing the order. For each item, identify the target device, software version, file revision, included data and permitted use. A folder called “backup” does not establish that you can restore the accepted machine or edit its engineering project.
This guide is for buyers comparing roll forming machine quotations and maintenance arrangements. Halcyon Machinery reviews equipment requirements with our factory team; the proposed controller, deliverables and verification must be confirmed for the specific line.
Separate the deliverables instead of asking for one backup
| Deliverable | What to ask the supplier | What it does not establish |
|---|---|---|
| PLC engineering project | Required engineering software, version, libraries, editable scope and agreed rights | That every protected or third-party block is editable |
| PLC recovery backup | Compatible device and firmware, included data, restoration conditions and verification record | That the file is an editable source project |
| HMI project or recovery file | Panel identification, software version, screen files and connection settings included | That the PLC program is included |
| Profile recipes | Units, revision, permitted settings and relationship to approved profiles | That mechanical guides, spacers or tooling positions are recorded |
| Drive parameters | Drive identification, parameter revision, supported export and restoration method | That a replacement drive is compatible without review |
The Siemens S7-1200 documentation distinguishes backup options with different contents and editability. Its complete CPU backup is a restore point rather than an editable project. This is a system-specific example; it does not identify the controller supplied on your proposed machine.
Match the files to the machine you accept
Ask for a device register covering the PLC, operator panel and drives, with relevant hardware, firmware and engineering software versions. Link each file to that register and the final acceptance configuration. A file date alone cannot prove that the delivered project matches the program used during the trial.
Schneider Electric’s Control Expert guidance includes checking equality between the project application and the PLC application before providing an archive. Ask your supplier to document the appropriate matching method for the actual controller. A screenshot from a different machine is not evidence for yours.
For US and UK quotations, make software versions and units explicit rather than relying on the local meaning of “standard backup.” Identify whether trial lengths and recipe entries use millimetres or inches, and retain the approved drawing revision. An English-language offer does not establish local support, stock or a particular controller brand.
Agree maintenance rights, editing rights and support
Separate permission to restore operation, access for maintenance and permission to change the program. Ask which software licences, libraries and authorised access are required, who holds them, and which assistance is included in the quotation. If a block or software component belongs to another party, identify the restriction and support route before purchase.
Record the person responsible for access and the secure handover channel. Do not put passwords in a public worksheet or inquiry form. Buying the machine does not by itself define every software right; the written supply agreement must state the deliverables and limitations.
What evidence should accompany the handover?
- A file inventory with revision, target device, included and excluded contents.
- A documented match to the configuration accepted during the machine trial.
- An agreed verification by the supplier and a competent technician under suitable conditions, with the outcome and limitations recorded.
- Checks of the finished profiles, lengths and punching operations included in the agreed trial after the relevant recovery verification.
- Open items, a named owner and the agreed acceptance decision.
This is a procurement checklist, not instructions for loading a program onto a running line. Recovery verification must follow the actual equipment documentation and commissioning plan. Restoring software does not replace finished-part acceptance or the required review of control and safety functions.
A useful question when the folder looks complete
Consider a hypothetical handover folder containing an HMI recovery file and a recipe list. Those files may cover part of the system, but they do not demonstrate that the PLC project, drive parameters or manual mechanical setup records are included. Ask the supplier to complete the register or identify the exclusions in the offer. This is an example for comparing quotations, not a reported Halcyon customer incident.
Download the blank control handover comparison record. Record deliverables and verification outcomes; do not enter passwords or credentials.
Frequently asked questions
Is a PLC backup the same as editable source code?
Not necessarily. Contents, format and editability depend on the controller and backup method. Specify recovery and editable project deliverables separately when both are required.
Will saved recipes reproduce a complete profile changeover?
Recipes alone may omit manual tooling, guide or spacer settings. Keep the mechanical setup record and verify the first part against the approved drawing.
Can a different replacement PLC use the same files?
Do not assume compatibility. Have the supplier review the exact hardware, firmware, software and agreed recovery scope before approving a replacement.
Related purchasing checks and inquiry
Use the line setup documentation guide for mechanical settings and first-piece records, and the spare tooling and parts documentation guide for identifiable replacement items. Compare the purlin equipment selection guide when your schedule includes C/Z sections.
Send the section drawing, material, thickness range, punching layout and required output. Add your required control-file deliverables and maintenance arrangements. Halcyon will use these requirements to discuss the proposed scope with our factory team; do not send passwords or confidential programs through the public form.
Discuss drawings and control handover requirements
Sources above describe specific control systems. The procurement checklist is Halcyon’s editorial synthesis, not evidence of a supplied configuration or completed recovery trial. Reviewed 3 October 2026.