A yearly safety check for your robot cells
Robot cells can change after startup. Fixtures move, guards get adjusted, and safety zones get edited.
Once a year, we check the safeguards on each KUKA, FANUC, and ABB cell and give you a written report of what we found.
- Cells
- KUKA, FANUC, ABB
- How often
- Once a year
- You get
- A written report
Illustrative model
- Safety zonesAgainst the cell as it stands
- Light curtainsA stop test on each one
- InterlocksGate switches and door locks
- Robot safety controllerIts configuration and checksum
- A written reportWhat we checked and what we found
What we check
- Safety zones: the zones and limits configured on the robot, against the cell as it stands
- Light curtains: a stop test on each one, against what the cell documentation says it should do
- Interlocks: gate switches, door locks, and the safety signals between the robot and the cell PLC
- The robot safety controller: where the cell has KUKA SafeOperation, FANUC DCS, or ABB SafeMove, its configuration, and its checksum against the one on record if the plant keeps one
What you get
- A written report for each cell: what we checked and what we found
- The findings in priority order, so you know what to fix first
- A dated record to compare against next year’s check
We can fix what we find, quoted separately. Any change to a safety configuration goes through your plant’s safety review and re-validation.
What it is not
The safety check does not replace your plant’s risk assessment or any validation your standards require. It is not a certification or an assessment against a standard, and a report with no findings does not mean a cell meets one. It is a yearly check of each cell’s safeguards against the cell’s documentation, written down so you can act on it.
How the check runs
- We agree the cells, the dates, and who from your team works with us.
- We review the cell documentation and the safety configuration on each robot controller.
- We test the safeguards at the cell, under your plant’s safety rules and with your people present.
- You get the written report, and we agree the date of next year’s check.
See also: Robot programming, Training days
Straight answers.
Does this replace our risk assessment?
No. The check does not replace your plant’s risk assessment or any validation your standards require, and it is not a certification or an assessment against a standard. It tells you, in writing, what we found on each cell.
Will you change our safety settings?
Not without your OK. The check reports what we find. Any change to a safety configuration goes through your plant’s safety review and re-validation.
How often is the check?
Yearly, on a date agreed in writing. A cell that has been rebuilt or moved can be checked between visits.
Do we need to stop production?
The cell being checked needs to be available for testing. We plan the dates around your shifts and outage windows.
What should we send?
The plant, the cells, the robot make and model in each, the safety options on each controller, and the cell documentation and checksum records you keep.
Schedule your yearly robot safety check.
Tell us the plant, how many cells, the robots in each and their safety options, and the cell documentation you keep.
What to send
- STEP 5: the whole project folder, zipped (the program file ends in ST.S5D, plus the other S5D files beside it).
- STEP 7 V5.x: a SIMATIC Manager archive (.zip), from File > Archive.
- TIA Portal: a project archive (.zapNN) from Project > Archive, and the TIA Portal version and update level.
- RSLogix 5 and 500: the program file (.RSP or .RSS), saved from the software or uploaded from the PLC first.
- Studio 5000: the project (.ACD) or an .L5X export, and the controller firmware revision.
- Robot backups: a full KUKA archive, a FANUC “All of above” backup or an ABB controller backup.
Office: (877) 524-6674, Mon–Fri 9:00am–5:00pm ET
Email: sales@ts-controls.com
Mailing address: 6650 Rivers Ave Ste. 105, N. Charleston, SC 29406