Adding a part, replacing a tool or changing a program can affect several devices in a cell. The study starts with a survey of the installed equipment. It should describe the proposed change, its dependencies and the conditions for returning to service.
Establish the baseline
Record the references of the robot, controller, PLC, drives, vision and relevant safety equipment. Record software versions, options, drawings and available programs. Compare older documentation with the installation before using it as a quotation baseline.
Identify which access rights are available and who holds them. Missing passwords, licences, source projects or manufacturer support may limit the work. These gaps become actions to resolve or explicit quotation limits.
Record differences between drawings and wiring, and changes already observed. Distinguish inspected items from areas that remain inaccessible.
Prepare usable backups
Define what each device requires in its backup, using its manufacturer procedure. Robot programs, installation data, recipes, vision settings and PLC source projects may be separate items. A log export does not establish the ability to restore the complete cell.
The Universal Robots documentation consulted distinguishes support files from data backups. It also warns that incorrect file handling can damage the file system. These procedures are product and version specific; the ESTUN method must be confirmed for the installed controller.
Define the effects of the change
Compare the installed and proposed states device by device. A new mass may affect load configuration. A longer tool may change clearances. A new sequence may introduce access or recovery cases that were not previously considered.
Suva addresses safety from equipment purchasing and risk assessment across the life cycle. For a retrofit, assess applicable requirements and responsibilities against the actual change. The word retrofit alone cannot determine the regulatory status of the work.
Plan intervention and rollback
Agree the shutdown window, contacts, isolation arrangements and access conditions with the operator. Preparation identifies work requiring a robot, process or safety specialist. Site intervention authorisations remain applicable.
The rollback plan describes the target state, required files, compatibility and checks after restoration. It also states physical rollback limits, for example after wiring or fixture changes. Possessing a backup alone does not establish this plan.
Revalidate affected functions
A matrix connects each change with the necessary tests. Include affected formats, transitions, machine exchanges and recovery cases. Affected protective functions require verification by competent participants within the agreed scope.
Fault tests are prepared with the site under controlled conditions and with required protection. Record what was verified, what remains reserved and the conditions for proceeding. A successful normal cycle does not complete recovery testing.
Hand over the delivered configuration
The final file contains the change list, versions, backups, tests and reservations. Update affected drawings and instructions within the agreed scope. Identify who retains the files, who may change them and who decides the return to production.
Future maintenance should be able to identify this reference state. Assess further changes against the file and define their own tests.
Common questions
Points to clarify.
Can a retrofit be quoted without source projects?
An initial assessment can identify missing information. Execution scope remains conditional on the necessary access, sources and compatibility.
Does a backup guarantee recovery?
No. Check its contents, compatibility and restoration procedure, followed by the necessary physical and functional checks.
Does a change require every test to be repeated?
The impact assessment defines affected functions and tests. Scope depends on the change and identified risks.
