I would like to hear how other UR integrators handle requests from customers who want full access to the robot after SAT.
In our case, this may include:
UR program files, installation files and scripts
Access to Manual Mode
The safety password
Administrator password
We understand why customers want full access to equipment they have purchased. However, our concern is that PolyScope 5 does not provide a reliable audit trail showing who accessed the robot or what changes were made.
If the cell later stops, we cannot immediately know whether the fault is related to our original software or to a change made by the customer. Before troubleshooting the actual fault, we may therefore need to obtain the current backup/support file, compare them with our approved SAT version and possibly restore the original version. This can significantly increase the time required to get the cell running again.
We are considering the following procedure:
Save a complete, clearly versioned backup as the official SAT release.
Hand over the requested program files and relevant passwords securely to an authorised person at the customer.
Inform the customer that access and subsequent modifications may result in longer troubleshooting and recovery times.
Ask the customer to document all changes made after SAT.
Base warranty and support on the most recently approved software version.
Charge for troubleshooting, comparison and restoration work if the issue is related to changes made by the customer or a third party.
Require a new risk assessment and safety validation if safety-related parameters or functions are changed.
How do other integrators handle this?
Do you provide all program files and passwords as standard, or only when specifically requested? Or not at all?
Do you also provide the safety password?
How do you determine whether the customer has modified the program?
How do you handle warranty and support when the customer has programming access?
Do you ask the customer to sign or acknowledge any specific terms before handing over the files and passwords?
Have you found a practical way to maintain traceability on PolyScope 5?
I would appreciate hearing about you procedures and experiences.
Thank you!
We also hand over everything if the customer requests so, which they are in their right to do.
We have had cases before, where they have managed to mess up the program, but it has never been up for discussion what was the cause of the problem. We have the original program backed up, and it isn’t too difficult comparing a program in the offline simulator with the robot program.
We do not hand over the safety password, though. And no documents are signed or anything.
Alright thank you @efn. I agree that they are in their right to do so - i just fear bad scenarios where we cannot determine who is at fault.
So if you were to compare the possibly modified program, you would check line-by-line together with the original-program in URSIM?
You could do line by line comparison, or you can use a diff checker and compare the .script files. We have a liability waiver that we have customers sign before handing over the safety password, as well as backing up and documenting the safety signature.
I really just look visually in the programs. If we do end up comparing two programs, it’s usually because something is not working. So that’s a good place to start.
We are the customer side. We would not buy from integrators who are not sharing the full access to the UR. We learned from the past. It is within our project specifications that the sharing is mandetory. However, this is mere a fallback as the integrators we worked with so far did hand over the programs and access by default. After SAT ensuring that the application runs safely is not up to the integrator but to the customer who runs the application. With signing SAT it is ensured that there was a safe running state in addition to CE which documents how the Safe running was proven.
If your customer wants your support, you obviously need the latest version of the programm. We document that by datestemping the files. If security measures are changed, then a new Risk assesment has to be done, but that is up to the customer then. Which I mostly see relevent in Human Robot interactions, in which a mail or note in the SAT would do the deed of written proof that the customer knows of the responsabilities.