Get started

The following steps provide a high-level overview of setting up
FactoryTalk Alarms and Events
 as part of a network distributed application.
Use the following steps to walk through the initial configuration of alarms and events for your system. For more details, refer to
FactoryTalk Alarms and Events
 System Configuration Guide.
  1. Plan system, install and activate software
    Set up
    FactoryTalk Alarms and Events
     as part of a network distributed application, held within a
    FactoryTalk
     Network Directory, and distributed across an automation system running on multiple computers.
  2. Set up device-based alarm monitoring
    Set up device-based alarm monitoring to obtain alarms from
    Studio 5000
     controllers using built-in alarms or alarm instructions. With device-based alarm monitoring that are available with the Studio 5000 Logix Designer application, pre-built alarms or alarm instructions are configured and then downloaded into a
    Studio 5000
     controller. The controller detects alarm conditions and notifies alarms and events services of alarm states. Software components publish this information to a device server. From the device server, the information can be logged to a database and monitored from FactoryTalk View graphic displays.
  3. Set up server tag-based alarm monitoring
    Set up server tag-based alarm monitoring to obtain alarms from a data server. Software-based Tag Alarm and Event Servers monitor controller tags for alarm conditions through data servers and publish event information for display and logging. Tag-based alarm monitoring is used for
    Studio 5000
     controllers, PLC-5, and SLC 500 devices communicating through
    Rockwell Automation
     Device Servers (
    FactoryTalk Linx
    ), or for third-party controllers communicating through OPC data servers.
  4. Set up OPC UA alarm monitoring
    Set up OPC UA alarm monitoring to obtain alarms from a third-party OPC UA server. The alarm data from the third-party devices is routed first to the OPC UA server, then to
    FactoryTalk Linx
     OPC UA Connector, and last to
    FactoryTalk Alarms and Events
    . The alarm information can be logged to a database and monitored from FactoryTalk View graphic displays.
  5. Set up graphic displays
    Monitor and interact with device-based, server tag-based, and OPC UA alarms during runtime using alarm and event objects, embedded in
    FactoryTalk View
     graphic displays. The alarm and event objects include the Alarm and Event Banner, Alarm and Event Summary, Alarm Status Explorer, Alarm and Event Log Viewer, and Automatic Diagnostic Event Summary. Once they are added to
    FactoryTalk View
     graphic displays, operators and users can use them to interact with alarms and events at runtime.
  6. Monitor alarms during runtime
    Monitor and interact with alarms and events during runtime with the
    FactoryTalk View
     SE Client. Monitor the graphic displays that host the Alarm and Event objects.
  7. Set up alarm history logging
    Use the Alarm and Event Historian with
    SQL Server
     installed on your network to log alarm history information to a database. An appropriate version of
    SQL Server
     is provided with both
    FactoryTalk View
     and
    FactoryTalk Linx
    .
  8. (optional) Set up redundant alarms and events
    Redundancy provides operational resilience in the case of hardware or power failure. Device-based, server tag-based, and OPC UA alarms require different setup procedures.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal