Automation Canada Machine Safety Issue May 2021 - 14

If you are designing soſtware level B in soſtware level C, these tools do
not exist. So you have to be very meticulous to document everything
and inherently you're going to end up with some errors. It is also a lot
more burden on the developers and programmers to ensure that the
application is complying with the relevant safety standards.
So far, these are all obvious things for compliance, but you have to
look a little bit beyond the standards because there is also an
expectation that most A-level soſtware from reputable manufacturers
will meet a lot of these requirements.
So, how else can you differentiate similar soſtware to decide which
one is right for you?
ADDITIONAL SAFETY SOFTWARE REQUIREMENTS
Usability
Since you will be using this a lot it is worthwhile to demo the soſtware
and determine how easy it is to use, how comfortable, and how fast it
is. Some things to look for:
* Can you have multiple screens?
* Can you configure the windows and which functions show up first?
* Is it easy to change from one type of device to another? For example
from a desktop computer to a tablet?
Reliability
How reliable is it? Are there any tools to reduce errors and improve
commissioning efficiency?
Security & Intellectual Property
Security and intellectual property protection are not required but they
are a huge part of the development of your machine. The safety
soſtware you choose must address this.
For example, some security controls allow you to limit, through
passwords, access to the controller, the logic, and what changes a user
can and cannot make. This enables both the safe and efficient operation
of the machine without necessarily compromising its reliability by
having unauthorized access by somebody that might not be qualified.
CANADIAN AUTOMATION
Martin Lalonde
Application Engineer & Technical Team Leader Wieland Electric
Martin Lalonde is a professional engineer with 20 years of experience
in the manufacturing sector and over 15 years of that time dedicated to
machine functional safety. Martin is also a Certified Electrical Safety
Engineer (CESE) by TUV-Saar. He is the Application Engineering and
Technical Team Lead at Wieland Electric, supporting clients with
product configurations, training, and custom projects.
VOLUME 3, ISSUE 3
14
Next, you should consider tools to protect your intellectual property.
Is your device protected against cyber tampering? By connecting to
your controller remotely, you could be exposing yourself to possible
cyber tampering. Tools such as code keys make it so that changes and
downloads of the soſtware can only happen with a USB that carries that
code.
There are also tools to prevent program duplication. Can you lock the
project to a specific station or controller? Alternatively, can you lock that
controller to a specific logic project? This further prevents unauthorized
changes to your machine.
Download the Samos® Plan safety soſtware here:
https://www.wieland-safety.com/programming-soſtware/
**This is a transcript of a live presentation.
To watch the full presentation on-demand, please go here:
https://attendee.gotowebinar.com/register/583253906422881870
4 **
About the Author:
https://www.wieland-safety.com/programming-soſtware/ https://attendee.gotowebinar.com/register/583253906422881870 https://www.wieland-safety.com/
Automation Canada Machine Safety Issue May 2021

Table of Contents for the Digital Edition of Automation Canada Machine Safety Issue May 2021
