Rockwell Automation FactoryTalk View Site Edition Users Guide - Manual (Page 271)

12 • S ETTING UP F ACTORY T ALK ALARMS
12–15
•
•
•
• •
12
•
Pla
ceho
lde
r
FactoryTalk Diagnostics routes audit messages to the Local Log (and to the
FactoryTalk Audit Log, if you have the FactoryTalk AssetCentre software installed).
You can look at audit messages logged the Local Log in the Diagnostics Viewer.
 Diagnostic messages inform operators of system activity, in the form of
information, error, and warning messages.
FactoryTalk Diagnostics routes these messages to a Diagnostics Local Log, the
Diagnostics List, and to a central ODBC log, if one is available. You can look at
diagnostic messages in the Diagnostics Viewer.
 Historical alarm and event messages record all the alarm activity that occurs at
an alarm server at run time.
The Alarm and Event Historian manages connections between alarm servers and
databases, and logs data from each alarm server to an alarm history database.
You can look at historical alarm information in the Alarm and Event Log Viewer.
For information about FactoryTalk Diagnostics, see the FactoryTalk Help. For more
information about historical alarm and event logging, see page 12-31.
Summary of basic steps for setting up FactoryTalk alarms
To set up FactoryTalk alarm monitoring, plan the design of the FactoryTalk View SE
application first, and decide which processes you want to monitor for alarms.
Then, in FactoryTalk View Studio, create the application and set up the FactoryTalk
Alarms and Events components you need. Following are the basic tasks involved:
1. Set up system-wide alarm and event policies for the application.
For information, see “Setting up system-wide alarm and event policies” on
page 12-16.
2. If the application is to use device-based alarms, in RSLogix 5000, program alarm
instructions into Logix5000 controllers that support built-in alarm detection.
For information, see the RSLogix 5000 documentation.
3. To let run-time clients receive device-based alarm data, add one or more Rockwell
Automation Device Servers (RSLinx Enterprise) to the application, and set up the
servers to support FactoryTalk Alarms and Events.
The Alarm and Event Historian is installed with the FactoryTalk Alarms and Events software.
To log alarm and event data, you must also install Microsoft SQL Server separately, on the
computers where data will be stored. For details, see the FactoryTalk Alarms and Events Help.