Safety Application Requirements

IEC 61508 requires you to perform various proof tests of the equipment that is used in the system. Proof tests are performed at user-defined times. For example, proof tests can be once a year, once every 15 years, or whatever time frame is appropriate. The controllers have a useful life of 20 years, and no proof test is required. Other components of the system, such as safety I/O devices, sensors, and actuators can have different useful life times.
IMPORTANT: Your specific applications determine the time frame for the useful life.

Controller Specifications and Certifications

For specifications and the agency certifications for the products, see the following:
  • ControlLogix and GuardLogix Controllers Technical Data, publication 1756-TD001
  • Agency certifications on the product labels
  • Declarations of conformity, certificates, and certification details at rok.auto/certifications

System Reaction Time

The system reaction time is the worst-case time from a safety-related event as input to the system or as a fault within the system, until the time that the system is in the safe state.
This worst-case definition includes the effects of asynchronous communications and multiple potential faults within the system.
For high demand applications, the system reaction time includes safety function muting time.
Actual reaction times are typically faster.
System Reaction Time
System Reaction Time
Each of the reaction times is dependent on factors such as the type of I/O device and instructions that are used in the program.
For more information about reaction time calculations, see Reaction Times.

Contact Information if Device Failure Occurs

If you experience a failure with any device, contact Rockwell Automation Technical Support: rok.auto/knowledgebase
Your local Rockwell Automation sales office or Allen-Bradley distributor can also initiate the following actions:
  • Return the device to us so the failure is logged for the affected catalog number and a record is made of the failure.
  • Request a failure analysis to try to determine the cause of the failure.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal