Colaborative Robots - Introduction
•
1 like•507 views
Ebook about colaborative robots and its standards
Recommended
More Related Content
Similar to Colaborative Robots - Introduction
Similar to Colaborative Robots - Introduction (20)
More from マルセロ 白井
More from マルセロ 白井 (20)
Recently uploaded
Recently uploaded (20)
Colaborative Robots - Introduction
- 9. ISO/TS 15066 Explained Standards vs. Technical Specifications Note that ISO/TS 15066 is not a standard, it's a technical specification. The difference is important. The ISO sometimes develops technical specifications prior to releasing final, formal standards. This is a recognition of the fact that the state of the art is “in flux” and will be evolving over time, explains Björn Matthias, Senior Principal Scientist – Robotic Automation, at ABB. “The technical specifications format is intended to record a snap shot of what the state of the art is here right now, and to make that available to the community to work with, knowing full well that there will be additions and changes in the future,” says Matthias. Technical specifications like ISO/TS 15066 are intended to mature the material, says Fryman. “Technical specifications are reserved for information that is ultimately intended to appear in an ISO standard, but is considered not fully developed and needs to be tested. A technical specification is what we really think the final standard will be, but you need to give us feedback.” Universal Robots’ Kieffer sees technical specifications as documents that provide guidance for the industry to test. “It's a way of trying out the requirements. If we were extremely certain about the content, then we could have made this a standard. But we chose not to,” says Kieffer. Meanwhile, Roberta Nelson Shea, Convenor of the ISO Industrial Robot Safety Working Group (ISO/TC 299/WG 3) and global marketing manager for Rockwell Automation views a technical specification document as one that is “not quite ready” to lay out formal requirements. “A technical specification document tells you that the technology needs a little more gel time and that the industry needs some experience with it in order to be able to make very definitive statements. At this point in time for collaborative robot applications, we are still learning.” You may well be asking yourself “If ISO/TS 15066 isn't a full ISO standard yet, why do I need to pay attention to it?” Firstly, it's never too early to get started on safety. Not only does ISO/TS 15066 build on the requirements in ISO 102181 and 102182, it constitutes best practice for the industry today. Secondly, if you want to be able to legitimately claim that you have properly safeguarded your collaborative robot system and provided a safe work environment for workers, ISO/TS 15066 is the document to read. Page 9 robotiq.com
- 12. ISO/TS 15066 Explained Integrators ISO/TS 15066 eliminates a lot of guesswork by providing the information integrators need when performing a risk assessment on collaborative robot applications. “It provides a lot of guidance that the integrator needs to think of when he's installing the robot,” says Universal Robots’ Kieffer. “If you are an integrator that is quite new in the field and you don't have that much experience, then ISO/TS 15066 is very good because it provides the input you need to do a good risk assessment.” “The purpose of 15066 is to make the job of the integrator easier and if there is anything in it that they cannot use, then let us know about that,” adds Kieffer, who expects ISO/TS 15066 to be “a big help” to Universal Robot integrators. ISO/TS 15066 will help Honda Canada's integrators better understand their requirements and obligations, says Smith. “Now there are some good hard numbers that integrators can go by to make sure that we don't injure somebody. When people understand the specific guidance of the technical specifications, it's also going to be easier for us to show compliance to the ISO 10218 standard.” Under Ontario law, there is a requirement for a prestart health and safety review of robotics systems. “We need an independent engineer to come in and to make sure that we've followed all the standards. ISO/TS 15066 is going to give them more information on how to apply those requirements properly,” adds Smith. Production Managers and Automation Engineers Production managers need to know that their people are working according to the state of the art, says ABB's Matthias. “The production manager needs to care about ISO/TS 15066 because it will give him the confidence that he is using the present state of the art, best possible information available today.” Automation engineers understand the application and its requirements, says Matthias. They also understand a bit about robotics and its capabilities and a bit about collaboration. But they may not have huge levels of experience in realizing collaborative applications. “When the automation engineer builds collaborative applications, he will have the objective of using the best possible information. This objective is fulfilled by ISO/TS 15066 in the best possible way. The Page 12 robotiq.com
- 13. ISO/TS 15066 Explained benefit of ISO/TS 15066 for automation engineers is the specific guidance it provides on what to look out for when putting together collaborative applications.” Confidence is a theme running through our expert's responses to this question. Well executed risk assessments inspire confidence. Adoption of best practices inspire confidence. Providing a safe environment for workers inspires confidence. But the benefits of ISO/TS 15066 go beyond generating feelings of confidence. “It also mitigates risk if you follow the document and you are more certain that you do things right,” says Kieffer. “There can also be benefits from stating that products comply with a safety document. Sometimes this has a commercial value or a value in terms of allowing you to show that you performed your risk assessment correctly.” ISO/TS 15066 provides production engineers with the information they need to understand all the capabilities and possibilities of collaborative robotics, says Smith. “I think the more they understand about collaborative robots, the better. They understand automation and manufacturing, so once they understand these new tools and how to implement them, and all the different requirements, they can come up with a lot of different technical solutions.” Factory Floor Workers Knowing that the specifications laid out in ISO/TS 15066 have been followed will generate confidence among factory workers, says ABB's Matthias. “The factory worker can be confident that his colleagues responsible for creating the application (the production manager and the application engineer) have worked according to the best present knowledge of the state of the art. This should give him a degree of confidence in his workplace.” Fryman agrees. “As a user, to know that there is a set of technical specifications that the integrator is designing to should give workers some comfort in the knowledge that someone is not just winging it and that the system has been designed within acceptable parameters,” says Fryman. “This should make factory workers more comfortable with the concept. The worker comes to work in the morning healthy, he's entitled to go home at night safely.” Factory floor workers will benefit from having collaborative applications properly defined with proper procedures, risk assessments, and warnings, says Pilz's Dominguez. Page 13 robotiq.com