Using RSLogix5000 (v16) Alarming Instructions with RSView SE/ME (v4.x)

Purpose of this Document: The alarming instructions, first made available in RSLogix 5000 v16, are designed to be used seamlessly with FactoryTalk View SE/ME (v5.0). They provide native compatibility with FactoryTalk View for SE v5.0, with FactoryTalk View ME supporting the instructions some time later. Because the timing of the releases of these different View products does not align with the release of RSLogix 5000 v16, there may be a need for projects that will be designed to take advantage of the benefits of FactoryTalk Alarms and Events, even though the visualization piece is not yet available This document outlines how to manually configure RSViewSE and RSViewME v4.x to utilize the alarming instructions introduced in RSLogix 5000 (v16.0). Its intent is to allow systems to be brought online and operational before the release of the visualization portion of FactoryTalk Alarms and Events is installed. The expectation being that when the upgrade to FactoryTalk Alarms and Events visualization occurs, the system changes to both the controller and HMI are minimized. This document will detail: • What features of FactoryTalk Alarms and Events can reasonably be implemented in RSView v4.x products. • How to configure RSView SE and ME alarms using the new RS Logix 5000 alarm instructions. • Using export (CSV) files to automate configuration. • Design considerations for RSLogix 5000 v16 projects when paired with RSView 4.x. • Design considerations for RSView v4.x to minimize impact when upgrading to FactoryTalkView v5.x. • Using the ALMA and ALMD faceplates.

The target audience is comprised of those engineers who want to utilize the new alarm instructions in RSLogix 5000 v16 but must design the HMI with RSView v4.x or RSView32. They may or may not opt to upgrade to FactoryTalkView 5.x. 1 What is alarming in FactoryTalk View v5.0? There are two new alarm instructions available in RSLogix 5000 v16: the ALMA instruction for analog alarms and the ALMD instruction for digital alarms. All alarm configuration information is part of the controller logic, such as limits, severity level, and alarm text. They can be acknowledged and suppressed by program logic, from View objects like a custom faceplate, or from the alarm banner or summary screens in FactoryTalk View SE v5.0. These alarms are displayed automatically on the FactoryTalk View SE v5.0 station. The benefits of controller-based alarming include:

• Alarms are reported to the HMI by exception, rather than burdening the network with constant polling • Single-point configuration and maintenance • Improved time stamp consistency for accurate first fault-finding in complex processes. • Better alarm coordination between stand-alone HMI Displays. • Single point of alarm acknowledgement and suppression • Leaves alarm control and status at the ultimate owner of the alarm, the controller

1.1 Can RSViewSE 4.x HMI stations view these alarms too? Yes! In View SE 4.x and earlier releases of View, alarms that are displayed on the HMI must be defined and configured in the HMI. So once the alarms are defined in the View project, some of the same functionality is possible in RSView SE 4.x as is available in FactoryTalk View SE. The following table outlines the features from the instruction based alarming system that can be implemented in a RSView SE 4.x project.

1.2 Alarm and Events HMI Functionality Matrix Using the ALMA and ALMD instructions, here is a functionality matrix comparing FactoryTalk View v5.x and RSView v4.x.

FactoryTalk View v5.x RSView v4.x

HMI Functionality FactoryTalk SE1

Alarm Viewer Faceplate RSView ME Alarm Viewer

RSView SE Alarm Viewer Faceplate

Alarm Notification by Exception (not Polling) ◦ ◦ Alarm Current Status 0 0 Multi-language alarm messages ◦ M A ◦ Alarm Buffering at Controller ◦ ◦ Automatic Update of additional or changed alarms from the controller at runtime Controller Maintained Alarm Status ◦ ◦ Associate other tags with alarm event?? ◦ 2 2 ◦ Tag-reference compiled alarm messages ◦ ◦

Time Stamp Alarm ◦ (< 1 sec)

(< 1 sec) ◦

High Resolution Controller Time Stamp ◦ ◦ Custom Time stamp from External Source ◦ ◦ Alarm Class and Event Category ◦ ◦ View Command from Instruction A Alarm Acknowledge to controller M A Alarm Acknowledge from controller M M Alarm Suppress to controller Alarm Suppress from controller M Alarm Disable to controller Alarm Disable from controller Alarm History Storage MS SQL ◦ ◦

Alarm History Visualization FactoryTalk Log Viewer

◦ Alarm Status List Object

SE Alarm Log Viewer ◦

KEY: = available, = not available, ◦ = not applicable

A Feature must be implemented manually, but can be semi-automated via import/export (CSV) files. M Feature must be implemented manually, with manual configuration in RSView Studio. 0 Alarms configured in the traditional way, using the ALMA and ALMD parameters described in this document. 1 FactoryTalk Viewer for ME to be released at a later date. Until then, alarms must be configured in the traditional way. 2 Note that in RSView v4.x the ability to include the analog value in the alarm message is lost.

1.3 Summary of Functionality

• Individual traditional HMI digital alarms can be created and linked to ALMA and ALMD tag parameters. • In RSViewSE v4.x, though alarm collection is still based in the HMI, much of the FactoryTalk View v5.x Alarm and Event

functionality can be supported through both the Alarm Summary display object and faceplate. Some manual configuration is required, but tools can be used to make HMI alarm configuration easier and quicker.

• In RSViewME v4.x, alarm collection is still based in the HMI and only basic FactoryTalk View v5.x Alarm and Event functionality can be supported due to the ME architecture. Alarms must be configured in the traditional manual way. In applications that require more A&E functionality from the ME stations, the faceplates can be used.

• HMI alarm configuration can be made easier through the use of a conversion tool that will automatically generate RSView CSV files from RSLogix 5000 CSV files.

: 2

Table of Contents

1 WHAT IS ALARMING IN FACTORYTALK VIEW V5.0?.............................................................................................................1 1.1 CAN RSVIEWSE 4.X HMI STATIONS VIEW THESE ALARMS TOO? ................................................................................................1 1.2 ALARM AND EVENTS HMI FUNCTIONALITY MATRIX ..................................................................................................................2 1.3 SUMMARY OF FUNCTIONALITY .............................................................................................................................................2

2 THE ANATOMY OF THE RSLOGIX 5000 V16 ALARM INSTRUCTIONS ....................................................................................4 2.1 ALMD: DIGITAL ALARMS ....................................................................................................................................................4 2.2 ALMA: ANALOG ALARMS....................................................................................................................................................5 2.3 USING THE ALMA AND ALMD FACEPLATES ...........................................................................................................................6

3 CONFIGURE HMI ALARMS WITH INSTRUCTION PARAMETERS : RSVIEWSE V4.X ................................................................8 3.1 RSVIEWSE V4.X: ACKNOWLEDGEMENT AND SUPPRESSION FROM THE CONTROLLER ...................................................................10

4 CONFIGURE HMI ALARMS WITH INSTRUCTION PARAMETERS: RSVIEWME V4.X ..............................................................11

5 ALARM CONVERSION UTILITY – AUTOMATING ALARM CREATION ...................................................................................13

6 SYSTEM DESIGN ................................................................................................................................................................14 6.1 RSLOGIX 5000 DESIGN CONSIDERATIONS FOR HMI APPLICATIONS USING RSVIEW V4.X ...............................................................14 6.2 RSVIEW V4.X HMI APPLICATION DESIGN CONSIDERATIONS .....................................................................................................14 6.3 UPGRADING TO FACTORYTALK VIEW V5.X ...........................................................................................................................15

: 3

2 The anatomy of the RSLogix 5000 v16 Alarm Instructions

The instructions are defined in RSLogix 5000 as an alarm datatype and configured using property panels. All necessary alarm properties that previously had to be defined and maintained in the HMI, such as alarm limit and current status, are now defined and maintained in the controller as tag parameters. There are two instructions: 1. ALMA for analog alarms 2. ALMD for digital alarms

The instructions are each a single data type with many read/write parameters Starting with FactoryTalk View SE v5.0, the HMI requires little or no configuration to display these alarms. The information is available directly from the controller by means of FactoryTalk Alarm and Events. For RSView v4.x and until FactoryTalk View v5.x is available, the tag parameters can be used to configure traditional HMI digital alarms. The following tables list the primary tags necessary to implement RSLogix 5000 v16 alarm instructions in RSView v4.x. 2.1 ALMD: Digital Alarms

In Alarm Status Parameter: Read Only Read Write Parameter Name Read Parameter Write Parameter

General Status – In Alarm . InAlarm ◦

Acknowledgement by Operator Parameter: Read and Write Read Write Parameter Name Read Parameter Write Parameter

General Status – Acknowledge .Acked .OperAck

Suppression by Operator Parameters: Read and Write Read Write Parameter Name Read Parameter Write Parameter

Alarm Suppression (by Operator) .Suppressed .OperSuppress Alarm Unsuppression (by Operator) ◦ .OperUnsuppress

Disable by Operator Parameters: Read and Write

Read Write Parameter Name Read Parameter Write Parameter Alarm Disable (by Operator) .Disabled .OperDisable

Alarm Enable (by Operator) ◦ .OperEnable The alarm message text is NOT exposed to the controller as a tag, but can be accessed from an RSLogix 5000 export (CSV) file. Sample from RSLogix 5000 CSV file:

Text Messages TYPE NAME DESCRIPTION SPECIFIER ALMMSG:en-us ALMD Tag Name Alarm text for operator in English AM ALMMSG:de-ch ALMD Tag Name Mitteilung für den Operator auf Deutsch AM

: 4

2.2 ALMA: Analog Alarms Six analog alarm conditions may be configured, with one general overall condition. The following parameters are useful for RSView alarm configuration:

In Alarm Status Parameters: Read Only Read Write Parameter Name Read Parameter Write Parameter

General Status – Any condition In Alarm .InAlarm ◦ High Condition – In Alarm .HInAlarm ◦ High High Condition – In Alarm .HHInAlarm ◦ Low Condition – In Alarm .LInAlarm ◦ Low Low Condition – In Alarm .LLInAlarm ◦ Rate of Change Increase – In Alarm .ROCPosInAlarm ◦ Rate of Change Decrease – In Alarm .ROCNegInAlarm ◦

Acknowledgement by Operator Parameters: Read and Write

Read Write Parameter Name Read Parameter Write Parameter General Status – Acknowledge (.AnyInAlarmUnack) .OperAckAll High Condition – Acknowledge .HAcked .HOperAck High High Condition – Acknowledge .HHAcked .HHOperAck Low Condition – Acknowledge .LAcked .LOperAck Low Low Condition – Acknowledge .LLAcked .LLOperAck Rate of Change Increase – Acknowledge .ROCPosAcked .ROCPosOperAck Rate of Change Decrease – Acknowledge .ROCNegAcked .ROCNegOperAck

Suppression by Operator Parameters: Read and Write

Read Write Parameter Name Read Parameter Write Parameter Alarm Suppression (by Operator) .Suppressed .OperSuppress

Alarm Unsuppression (by Operator) ◦ .OperUnsuppress

Disable by Operator Parameters: Read and Write Read Write Parameter Name Read Parameter Write Parameter

Alarm Disable (by Operator) .Disabled .OperDisable Alarm Enable (by Operator) ◦ .OperEnable

Just as for digital alarms the alarm message text is NOT exposed to the controller as a tag, but can be accessed from an RSLogix 5000 export (CSV) file, with additional lines for each translated message. . Sample from RSLogix 5000 CSV file:

Text Messages TYPE NAME DESCRIPTION SPECIFIER ALMMSG:en-us ALMA Logix Tag Name HH alarm text for operator in English HH ALMMSG:en-us ALMA Logix Tag Name H alarm text for operator in English H ALMMSG:en-us ALMA Logix Tag Name L alarm text for operator in English L ALMMSG:en-us ALMA Logix Tag Name LL alarm text for operator in English LL ALMMSG:en-us ALMA Logix Tag Name ROC positive alarm text for operator POS ALMMSG:en-us ALMA Logix Tag Name ROC negative alarm text for operator NEG ALMMSG:de-ch ALMA Logix Tag Name HH Mitteilung für den Operator auf Deutsch HH ALMMSG:de-ch ALMA Logix Tag Name H Mitteilung für den Operator auf Deutsch H

For both analog and digital alarm instructions, messages are denoted by language using ISO language codes, as seen in the TYPE column. Text for the operator is in the DESCRIPTION column. The SPECIFIER denotes for which alarm it is. Although multi-language alarms are not officially supported by RSView v4.x, they can still be configured. See end of note for more information.

: 5

2.3 Using the ALMA and ALMD faceplates Faceplates are direct-referenced HMI interfaces to the alarm instructions. They can be viewed on the screens, independent of the alarm summary screen, to show individual alarm status, limit settings, and commands. The faceplates for the ALMA and ALMD instructions are a bit more advanced since in RSView v4.x as some commands for the alarm instructions are only available from the faceplate. In RSViewSE v4.x, the faceplate display can be configured to appear when an operator “identifies” a single alarm from the alarm summary display. This action is the equivalent of the “FactoryTalk Command Execution” available within the FactoryTalk ViewSE v5.x viewer. For consistency and better operator retention, the faceplates use the same icons as are used in the FactoryTalk ViewSE v5.x viewer.

Operator icons Alarm Status icons

Enable Alarm Alarm is active; Not acknowledged

Disable Alarm

Alarm is active; acknowledged

Unsuppress Alarm Alarm is normal; Not acknowledged

Suppress Alarm Alarm is normal

Acknowledge Alarm condition Alarm is disabled

Acknowledge All Alarm conditions (ALMA)

Alarm is suppressed 2.3.1 ALMA Faceplates for SE and ME The ALMA faceplate consists of 3 screens: ALMA indication, ALMA configuration, and ALMA fault status.

Main faceplate: ALMA indication

ALMA Fault Status popup

ALMA Configuration popup

In RSViewSE, if an event file is not configured to link suppression and acknowledgement with HMI suppression and acknowledgement, the faceplate is the only place where an alarm can be acknowledged at the controller level by the operator. See section 3.1 for more information. In RSViewME, alarm suppression and acknowledgement at the controller level are only available from the faceplate. For both RSView ME and SE, Alarm enable/disable are only available from the faceplate.

: 6

2.3.2 ALMA Extended Faceplate for ME

Extended faceplate: ALMA indication, status, and configuration

Because RSViewME cannot support multi-layer dynamic referencing using parameter files (i.e., a parameter-linked screen calling a popup using the same parameters), the extended ALMA faceplate can be used to provide full faceplate functionality with minimal screen navigation. This faceplate will be available on the Rockwell Automation Sample Code Library website: http://samplecode.rockwellautomation.com

2.3.3 ALMD Faceplate for SE and ME

Just as with the ALMA faceplate… In RSViewSE, if an event file is not configured to link suppression and acknowledgement with HMI suppression and acknowledgement, then the faceplate is the only place where an alarm can be acknowledged at the controller level by the operator. In RSViewME, alarm suppression and acknowledgement at the controller level are only available from the faceplate. For both RSView ME and SE, enabling and disabling of alarms is only available from the faceplate.

: 7

3 Configure HMI Alarms with Instruction Parameters : RSViewSE v4.x When configuring RSView v4.x to display alarms from the ALMA and ALMD instructions, the most effective way is to create a digital HMI tag for each desired alarm condition and then configure its respective alarm information. This tag is linked to the .xxInAlarm property of the ALMA (where xx is HH, H, LL, L, etc.) or the .InAlarm property of the ALMD instruction. Additionally, for each desired alarm condition that requires acknowledgement, to coordinate the acknowledgement between the HMI and controller, an additional digital HMI tag is created that is linked to the .OperAck property of the ALMA or ALMD instruction. Digital HMI Tag Creations

1 User-defined tagname: A good rule of thumb is to make the HMI tagname similar to the RSLogix 5000 tagname.

Step 1. HMI Alarm Tag

1

2 The tag description becomes the text displayed on the HMI alarm banner/summary screen. This corresponds to the ALMMSG:en-US message seen in the RSLogix exported CSV file.

2

3 The tag datasource is the desired .InAlarm property of the RSLogix ALMA or ALMD tag. The address is in the following format: [RSLinx_Topic]RSLogix_Tag.InAlarm where .InAlm is one of the In Alarm Status Parameters listed in the previous section of this document.

3

If the controller and HMI are online, it is also possible to find the correct parameter using the online tag browser.

Step 2. HMI Alarm Configuration: Alarm States

4 Alarm Type: On This will trigger an alarm to be displayed when the digital input is true. The following HMI alarm parameters should be configured as desired and are not directly related to the ALMA or ALMD instructions: Alarm Label Severity1

Alarm Messages2: In Alarm Alarm Messages2: Out-of-Alarm Alarm Messages2: Acknowledgement

4

1 Alarm severity is a parameter of the ALMA and ALMD instructions, but the range is 1-1000, where RSView severities are limited to 1-9. 2 Alarm messages are sent to the alarm log file and/or the printer when the tag goes into alarm.

: 8

Step 3. HMI Alarm Configuration: Advanced

5 (Optional) Alarm Identification Configure a command to display a popup containing the ALMA or ALMD faceplate. This command or macro runs when an operator highlights the alarm in the alarm summary and clicks the Identify button or, clicks a button in the display that issues the Identify command. Command used in example: Display popALMA /T[CLXv16]ALMATag01

5

6

6 If alarm acknowledgment is required for this particular alarm, enter an HMI tag that is linked to the appropriate Acknowledgement by Operator parameter. See Step 4. HMI Acknowledgement

Step 4. HMI Acknowledgement Tag

7 7 User-defined tagname: A good rule of thumb is to make the HMI tagname similar to the RSLogix tagname.

8 The tag datasource is the desired .OperAck property of the RSLogix ALMA or ALMD tag. The address is in the following format: [RSLinx_Topic]RSLogix_Tag.OperAck where .OperAck is one of the Acknowledgement by Operator Parameters listed in the previous section of this document.

8

All additional alarm settings can be left at the default setting or modified as desired. For more information about configuring alarms in RSViewSE, see the RSView Supervisory Edition User’s Guide Volume 1. . TIP These steps also apply when configuring HMI alarms in RSView32.

TIP While it is also possible to configure an HMI analog alarm with the same properties as an ALMA instruction, doing so makes the

ALMA faceplate useless and forces RSView to process the alarm conditions, instead of simply reflecting the controller’s condition in a digital state.

TIP In RSViewSE, all steps pertaining to HMI tag creation and alarm configuration can be done in CSV files and imported into the

application.

: 9

3.1 RSViewSE v4.x: Acknowledgement and Suppression from the Controller Configuring HMI Alarms in RSViewSE v4.x using ALMA and ALMD instructions means that Alarm Acknowledgement and Alarm Suppression occur at two levels: the controller level (using instruction parameters) and the HMI level (using HMI commands).

Faceplate

communicates at the ControlLogix Level.

RSView Alarm Summary Object

communicates at the RSView HMI Level.

Therefore, when the operator uses the ALMA or ALMD faceplate to acknowledge or suppress an alarm, by default that status is not reflected in the Alarm Summary. To link the two, an event file can be created in SE to watch for the controller acknowledge or suppression status. When the alarm acknowledge or suppression status is active, the event configuration forces SE to execute the respective HMI command for that particular alarm tag, thus updating the alarm at the HMI level. SE Event Setup example:

1

2

1 Suppression The expression field contains a link to the ALMA or ALMD .Suppressed property. The action performed is the HMI SuppressOn command for the respective HMI Alarm tag. The NOT-condition of the .Suppressed property performs the HMI SuppressOff command.

Acknowledge The expression field contains a link to the ALMA .xxAcked property (where xx is HH, H, LL, L, etc.) or ALMD .Acked property. The action performed is the HMI Acknowledge command for the respective HMI Alarm tag.

2

For most applications, an event execution time of one second should be acceptable.

: 10

4 Configure HMI Alarms with Instruction Parameters: RSViewME v4.x Alarms in RSViewME are configured through the Alarm Setup panels in RSView Studio. The alarm configuration can be made using ControlLogix tags or HMI tags. In the example below, ControlLogix tags will be used. TIP These steps also apply to FactoryTalk ViewME v5.x.

Step 1. Add Tag to Alarm Setup Triggers

1 2

3

The following fields are important:

Select Trigger For ALMA instructions, the trigger should be the .xxInAlarm property of the ALMA tagname, where xx is the alarm condition such as HH, H, LL, L, ROCPos, ROCNeg. For ALMD instructions, the trigger should be the .InAlarm property of the ALMD tagname. Using the RSLInx Enterprise tag browser is possible and recommended.

Trigger Type Value

Ack For ALMA instructions, the trigger should be the .xxOperAck property of the ALMA tagname. For ALMD instructions, the trigger should be the .OperAck property of the ALMD tagname.

Remote Ack For ALMA instructions, the trigger should be the .xxAcked property of the ALMA tagname. For ALMD instructions, the trigger should be the .Acked property of the ALMD tagname.

1

2

3

: 11

Step 2. Configure Alarm Messages

4 5 6

Trigger Select a trigger name from the pulldown menu. The triggers available should be all the tags defined in the Triggers tab.

Trigger Value Since the instruction properties are digital, the Trigger Value should always be 1.

Message Type an appropriate message for the operator.

4

5

6

All other alarm settings can be left at the default setting or modified as desired. For more information about configuring alarms in RSViewME, see the RSView Machine Edition User’s Guide Volume 1. TIP Trigger names and messages can be copied from Excel and pasted to the Alarm Messages table in RSView Studio.

: 12

5 Alarm Conversion Utility – Automating alarm creation An alarm conversion utility was created to simplify CSV file creation by automatically generating an HMI tag and alarm for each ALMA or ALMD instruction found in an RSLogix 5000 project.

Alarm Conversion Utility: Make RSView Alarms v1.0

The following alarm properties are taken directly from the RSLogix 5000 project:

• Alarm Tag Name • Alarm Text (without embedded variables) • Alarm Address (ControlLogix tag name) • Severity* • Identify Action* (A command to execute when the operator selects the alarm) • Multi-language alarms* (if multiple languages are configured, a separate digital alarm tag can be created for each message text)

*Optional. If not selected during conversion, RSView defaults will be used instead. Once the RSView tag and alarm CSV files are created, they can be modified or imported to the desired RSView project as-is. The RSLogix 5000 CSV file is not altered during conversion. For more information on configuring alarms in RSViewSE, see the RSView Supervisory Edition User’s Guide Volume 1. This utility will be posted in the Rockwell Automation Knowledgebase, Answer ID 38147.

: 13

6 System Design 6.1 RSLogix 5000 design considerations for HMI applications using RSView v4.x ALMA and ALMD instructions allow for variable-embedded alarm messages. These messages can’t be reflected in RSView v4.x since the HMI alarm text is the HMI tag description. If variable-embedded alarm messages are used in anticipation of upgrading to FactoryTalk View v5.0, then the user must manually modify the alarm message for use in RSView v4.x.

• If desired, ALMA and ALMD instructions can be configured to not require operator acknowledgement. All RSView v4.x alarms

require acknowledgment, but this affects only HMI display, not the controller logic.

• ALMA and ALMD severities can be defined in RSLogix 5000 with a range of 1-1000. RSView alarm severities are between 1-9.

• New ALMA and ALMD instructions are not automatically added to the HMI. 6.2 RSView v4.x HMI application design considerations

• RSLogix “FactoryTalk View Command” is the equivalent to “RSView Alarm Identification” Command

• Because RSView v4.x alarms will only display 1 message per tag, multi-language alarms cannot be supported by design. However, two (or more) languages can be configured by creating 2 separate alarm tags pointing to the same ControlLogix address. Each tag description would be the alarm text in one of the languages.

• Summary of operator events and how they effect alarm status, both for the HMI display and at the instruction level.

RSView v4.x

HMI Functionality RSView ME Alarm Viewer

RSView SE Alarm Viewer Faceplate

Alarm Acknowledge to controller Alarm Acknowledge from controller Alarm Suppress to controller Alarm Suppress from controller Alarm Disable to controller Alarm Disable from controller

• As described in Section 3, it is possible to configure the alarm to display the ALMA or ALMD faceplate when the operator

chooses to “identify” it from the Alarm Summary screen. If the operator needs access to ALMA or ALMD faceplates for alarms that are not active, individual display buttons can be added to operator screens as desired

: 14

6.3 Upgrading to FactoryTalk View v5.x In addition to the following the guidelines to configure device-based alarming in RSView v4.x, the following considerations should be taken into account when upgrading an RSView v4.x application to FactoryTalk View v5.x. 6.3.1 RSLogix 5000 Application code changes: There should be no major code changes required, and the following features are no longer restricted:

• Alarm messages can contain embedded variables. • Multi-language alarms are supported; no need for multiple alarm definitions. • Online changes of ALMA and ALMD instructions will be reflected automatically. • Alarm Class designation now has relevance. • Controller time stamp resolution greatly improves.

Users may have added extra logic to coordinate v16 alarm command and status tag elements with the available RSView 4.x alarm features – this will have to be removed or disabled. 6.3.2 HMI Application code changes: The transition is straightforward.

• Remove HMI alarm tags that reflect ALMA and ALMD instructions, and modify any existing references to these HMI tags, such as screen animation.

• Convert other HMI alarm tags to Tag-based Alarms & Events. (Optional, see TIP below) • Configure FactoryTalk Alarm Summary and Banner colors and display preferences. • Replace Alarm Summary objects on screens with FactoryTalk Alarm objects. • Remove “Alarming” from the HMI Application startup. • Alarm History database schema changes; RSView Alarm Logging is no longer used.

TIP The traditional RSView Alarm Summary object and new FactoryTalk Alarm Summary object can both be displayed on a single

screen for applications that have both types of alarms.

: 15

Important User Information In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment. The examples and diagrams in this document are included solely for illustrative purposes. Because of the many variables and requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on the examples and diagrams. No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software described in this document.

www.rockwellautomation.com Corporate Headquarters Rockwell Automation, 777 East Wisconsin Avenue, Suite 1400, Milwaukee, WI, 53202-5302 USA, Tel: (1) 414.212.5200, Fax: (1) 414.212.5201 Headquarters for Allen-Bradley Products, Rockwell SoFactoryTalkware Products and Global Manufacturing Solutions Americas: Rockwell Automation, 1201 South Second Street, Milwaukee, WI 53204-2496 USA, Tel: (1) 414.382.2000, Fax: (1) 414.382.4444 Europe/Middle East/Africa: Rockwell Automation SA/NV, Vorstlaan/Boulevard du Souverain 36, 1170 Brussels, Belgium, Tel: (32) 2 663 0600, Fax: (32) 2 663 0640 Asia Pacific: Rockwell Automation, 27/F Citicorp Centre, 18 Whitfield Road, Causeway Bay, Hong Kong, Tel: (852) 2887 4788, Fax: (852) 2508 1846 Headquarters for Dodge and Reliance Electric Products Americas: Rockwell Automation, 6040 Ponders Court, Greenville, SC 29615-4617 USA, Tel: (1) 864.297.4800, Fax: (1) 864.281.2433 Europe/Middle East/Africa: Rockwell Automation, Brühlstraße 22, D-74834 Elztal-Dallau, Germany, Tel: (49) 6261 9410, Fax: (49) 6261 17741 Asia Pacific: Rockwell Automation, 55 Newton Road, #11-01/02 Revenue House, Singapore 307987, Tel: (65) 6356-9077, Fax: (65) 6356-9011 Publication 000-0000-0000 – March 2, 2007 Copyright © 2007 Rockwell Automation, Inc. All rights reserved. Printed in USA. V9SMB

: 16