pcs 7 in-practice alarmhiding sp

Applikationen & Tools

Answers for industry.

Deckblatt

PCS 7 in Practice - Smart Alarm Hiding SIMATIC PCS 7 V7.0 and higher

Application Example November 2009

2 Smart Alarm Hiding

2.0, Beitrags-ID: 39134774

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Industry Automation and Drives Technologies Service & Support Portal This article is taken from the Service Portal of Siemens AG, Industry Automation and Drives Technologies. The following link takes you directly to the download page of this document. http://support.automation.siemens.com/WW/view/en/39134774 If you have any questions concerning this document please e-mail us to the following address: [email protected]

http://support.automation.siemens.com/WW/view/en/39134774�

mailto:[email protected]�

Smart Alarm Hiding 2.0, Beitrags-ID: 39134774 3

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

s

SIMATIC Smart Alarm Hiding SIMATIC PCS 7

Alarm management in V6.1

1 Smart Alarm Hiding in V7.0 / V7.1

2

Glossar 3

Related Literature 4

History 5

Warranty and Liability


2.0, Beitrags-ID: 39134774

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Warranty and Liability Note The Application Examples are not binding and do not claim to be complete

regarding the circuits shown, equipping and any eventuality. The Application Examples do not represent customer-specific solutions. They are only intended to provide support for typical applications. You are responsible for ensuring that the described products are used correctly. These application examples do not relieve you of the responsibility to use safe practices in application, installation, operation and maintenance. When using these Application Examples, you recognize that we cannot be made liable for any damage/claims beyond the liability clause described. We reserve the right to make changes to these Application Examples at any time without prior notice. If there are any deviations between the recommendations provided in these application examples and other Siemens publications – e.g. Catalogs – the contents of the other documents have priority.

We do not accept any liability for the information contained in this document.

Any claims against us – based on whatever legal reason – resulting from the use of the examples, information, programs, engineering and performance data etc., described in this Application Example shall be excluded. Such an exclusion shall not apply in the case of mandatory liability, e.g. under the German Product Liability Act (“Produkthaftungsgesetz”), in case of intent, gross negligence, or injury of life, body or health, guarantee for the quality of a product, fraudulent concealment of a deficiency or breach of a condition which goes to the root of the contract (“wesentliche Vertragspflichten”). The damages for a breach of a substantial contractual obligation are, however, limited to the foreseeable damage, typical for the type of contract, except in the event of intent or gross negligence or injury to life, body or health. The above provisions do not imply a change of the burden of proof to your detriment. Any form of duplication or distribution of these Application Examples or excerpts hereof is prohibited without the expressed consent of Siemens Industry Sector.

Table of Contents


Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Table of Contents Warranty and Liability ................................................................................................. 4 1 Alarm management in V6.1............................................................................... 6

1.1 Focussing on the most important alarms ............................................. 6 1.2 Suppressing alarms.............................................................................. 7 1.3 Messages triggered by acknowledgement........................................... 8 1.4 Filtering alarms..................................................................................... 8 1.5 Alarm analysis ...................................................................................... 9

2 Smart Alarm Hiding in V7.0 / V7.1 .................................................................. 11 2.1 Automatic alarm hiding....................................................................... 13 2.1.1 Configuring the operating states ........................................................ 13 2.1.2 Configuring the status block............................................................... 14 2.1.3 Configuring the block group ............................................................... 17 2.1.4 Configuring the hiding matrix ............................................................. 19 2.1.5 OS compilation ................................................................................... 20 2.1.6 Behaviour in OS Runtime................................................................... 23

Alarm hiding in OS Runtime............................................................... 23 List of messages to be hidden ........................................................... 25 Alarm view in the faceplate (SP1) ...................................................... 27 Status of hidden alarms...................................................................... 27

2.1.7 The principle of automatic alarm hiding ............................................. 29 2.2 Manual alarm hiding........................................................................... 30 2.2.1 Configuring automatic alarm hiding.................................................... 30 2.2.2 Behaviour in OS Runtime................................................................... 31 2.3 Alarm hiding versus alarm suppression ............................................. 32

3 Glossar ............................................................................................................. 33 4 Related Literature ............................................................................................ 34

4.1 Related Literature............................................................................... 34 4.2 Internet Link Specifications ................................................................ 34

5 History............................................................................................................... 35

Alarm management in V6.1 1.1 Focussing on the most important alarms


2.0, Beitrags-ID: 39134774

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Alarm management in V6.1 1 In the following chapter we will give a short summary of the alarm management functions already incorporated in PCS 7 V6.1.

1.1 Focussing on the most important alarms

• alarm line in the overview area (displaying the alarm with the highest priority) • preconfigured alarm views, fully customizable alarm views • group displays in the overview areas and as part of the block icon • loop-in-alarm highlighting the faulted measuring point • horn

Figure 1-1 PCS 7 OS - alarm display

Alarm management in V6.11.2 Suppressing alarms


Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Figure 1-2 Horn configuration

1.2 Suppressing alarms

Alarms could be suppressed based on the following: • Suppressing alarms directly at the technological blocks via the M_SUP_xy

inputs to block alarms of a block depending on the program logic. • Blocking alarms of an individual measuring point or sublevel of the hierarchy

via OS operation.

Alarm management in V6.1 1.3 Messages triggered by acknowledgement


2.0, Beitrags-ID: 39134774

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Figure 1-3 Locking alarms for specific areas or measuring points

1.3 Messages triggered by acknowledgement

To reduce the number of alarms generated in a plant, the PCS 7 alarm blocks ALARM_8 and ALARM_8P allow messages to be triggered by acknowledgement. After an incoming message has been generated for a signal (signal changes from 0 to 1), no additional messages are created for that signal until acknowledged on the OS.

1.4 Filtering alarms

The alarm filters in the alarm lists can be customized for each user. The filter criteria are the properties of a message (date, time, message class, message text, etc.).

Alarm management in V6.11.5 Alarm analysis


Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Figure 1-4 Filtering and sorting alarms in the alarm journal

1.5 Alarm analysis

The hit list displays statistical calculations on the archived messages in the message window. The following statistical calculations are available for messages: • The frequency of a message number. The frequency is only increased if a

message in the archive has the status “came in”. • The accumulated duration of a message number in seconds for the status

“came in/went out” (+/-), the status “came in/initial acknowledgement” (+/*1) or the status “came in/second acknowledgement” (+/*2).

• The average duration of a message number in seconds for the status “came in/went out” (+/-), the status “came in/initial acknowledgement” (+/*1) or the status “came in/second acknowledgement” (+/*2).

Only the states “acknowledgement”, “system acknowledgement” and “emergency acknowledgement” are used for the statistical calculation of the acknowledgement times.

Alarm management in V6.1 1.5 Alarm analysis


2.0, Beitrags-ID: 39134774

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Figure 1-5 Analysis of the alarm frequency in the hit list and configuration in Alarm Control

Figure 1-6 Analysis of the alarm frequency in the hit list and configuration in Alarm Control

Smart Alarm Hiding in V7.0 / V7.11.5 Alarm analysis


Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Smart Alarm Hiding in V7.0 / V7.1 2 As an additional function to the alarm management of PCS 7, "Smart Alarm Hiding“ is available since V7.0. This function offers you to hide alarms for the reduction of the number of messages in the process. „Smart Alarm Hiding” provides two possibilities: • manual hiding and unhiding of alarms • automatic hiding and unhiding of alarms Basically the automatic Alarm Hiding is actuated by status blocks in the AS, which in conjunction with a hiding matrix alarms hide or unhide dependent on state. The allocation of the technological (messaging) blocks to a status block is managed via the new block property "block group".

Figure 2-7 Overview “Functionality of automatic alarm hiding”

Smart Alarm Hiding in V7.0 / V7.1 1.5 Alarm analysis


2.0, Beitrags-ID: 39134774

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

The behaviour of the “smart alarm hiding” in process operation is implemented as follows: • The messages are hidden in the following alarm lists: incoming alarm list,

outgoing list, acknowledged alarm list and one line (except alarm journal, process alarm list, operation list) and the group displays.

• During process operation you can manually hide the following lists: – incoming alarm list – outgoing alarm list – acknowledged alarm list

• Currently pending messages which are hidden are displayed in the “list of hidden messages” (except: gone messages).

• The “messages to be hidden” list contains all messages to be hidden upon arrival.

• Hidden messages can be made to reappear in the incoming alarm list or outgoing alarm list via the “list of hidden messages”.

• Hidden messages are archived. • If operator stations are redundant, the message archive is updated. • The acoustic signalling (horn) of hidden messages is suppressed

/acknowledged. • The status of hidden messages is not displayed in the group displays of the

process pictures and faceplates. • Manually hidden alarms are redisplayed after a defined time. • Manually hidden alarms are acknowledged automatically. • Manual alarm hiding is OS server specific. • An operator message is generated when the operator hides and shows alarms

manually. • When hiding and showing a message, a message with the status show or hide

is generated.

Smart Alarm Hiding in V7.0 / V7.12.1 Automatic alarm hiding


Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

2.1 Automatic alarm hiding

The configuration of the automatic alarm hiding comprises five basic steps: Figure 2-8 Flowchart of alarm hiding engineering

2.1.1 Configuring the operating states

The target is to hide alarms caused by certain process or plant conditions so that the operator sees only the relevant alarms. These plant conditions are defined in the first step. The definition is done using enumerations which are defined in the global declarations in SIMATIC Manager’s component view. To this end, an enumeration with the name “Operating State” is configured. Values from 1 to 32 can now be defined as plant conditions in this enumeration. The value “0” is the preset for “normal” operating condition. In this state the plant is within normal operating limits and no alarms are hidden. You can now assign any plant conditions to the values 1 to 32 (Figure 2-9). In multiprojects consisting of several subprojects, the operating states are created in the global declarations in the master data library and then updated in the multiprojects (Figure 2-10).

STEP 1: Engineering of operating states

STEP 2: Insert StateRep block + connections

STEP 3: Engineering of block groups

STEP 3a: Compile CFC

STEP 3b: Download AS

STEP 4: Engineering of „Hiding“ matrix

STEP 5: OS Compile

STEP 5a: Download OS

STEP 5b: Restart OS

Smart Alarm Hiding in V7.0 / V7.1 2.1 Automatic alarm hiding


2.0, Beitrags-ID: 39134774

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Figure 2-9 Defining plant conditions as enumeration value

Figure 2-10 Comparing the operating states in the multiproject

2.1.2 Configuring the status block

In the second configuration step, insert the technological block “StateRep” from the PCS 7 V7.0 Library. This technological block converts Boolean input signals into the corresponding operating states. The “StateRep” block features 32 “StateX” Boolean inputs. These inputs correspond to the values of the enumerations you have created in the first configuration step (Figure 2-11). If, for instance, the value 3 is equivalent to the operating state “emergency stop“, this is the input “State3” at the “StateRep” block. If now a “1” is received at the input “State3”, this corresponds to the operating state “emergency stop“, which is output to “QState” of the “StateRep” block (Figure 2-13). It is thus possible to generate different operating states controlled by the program. The attribute “S7_enum_Operating State“ links the output “QState“ to the values of the enumeration “Operating State”. The values/states configured in “Operating State” are thus assigned to and processed by the inputs of the “StateRep” block (Figure 2-12).



Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Figure 2-11 Diagram of “StateRep“ status block

SR blockQSTATEINT

BOOL QERR

STATE1 BOOL

S7_m_c = trueS7_enum = OperationState

S7_m_c = trueS7_state_rep = trueS7_block_group= <block group name>

STATE2 BOOLSTATE3STATE4

STATE32

STATE5

BOOLBOOLBOOL

BOOL

Figure 2-12 Assigning the output “QSTATE” to the enumeration “Operating State“

If no signal is received at any input of the “StateRep” block, the plant is in normal operating state and the output “QSTATE” is 0. No alarms are hidden in this case. If two inputs are “1“ simultaneously, “QERR“ is set to “1” and “QSTATE” to “0” since a plant can not assume two different states at the same time. A block group is now defined in the properties dialog of the “StateRep” block. In the next step, you can define the technological area to which the “StateRep” block forwards the operating state. This means that a “StateRep” block is permanently assigned to a block group (Figure 2-14).



2.0, Beitrags-ID: 39134774

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

It is thus possible to hide alarms of specific block groups for certain operating states.

Figure 2-13 Technological block “StateRep”

Figure 2-14 Assignment of “StateRep” block to the equivalent block group



Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

2.1.3 Configuring the block group

One technological area is composed of several technological blocks that can generate alarms. To hide alarms for subplants, we must combine all technological blocks of a subplant in one block group. This allows us to hide all alarms generated by blocks of the same block group for certain operating states. There are two ways how technological blocks can be assigned to a block group. The first way is to enter the block group directly into the properties dialog of the technological block (Figure 2-15). The “block group” attribute is also available in the Import/Export Assistant (Figure 2-16, Figure 2-17).

Note The “block group” attribute is an ES (CFC) attribute. When migrating your own block libraries to PCS 7 V7.0, this attribute is automatically added into the library’s technological blocks.

Figure 2-15 Defining the block group at the technological block



2.0, Beitrags-ID: 39134774

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Figure 2-16 Block group attribute for Import/Export File

Figure 2-17 Block group attribute in the IEA File Editor

The second method is to assign the block groups to the corresponding technological block in the process object view (Figure 2-18).



Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Figure 2-18 Defining the block group in the process object view

After the charts and technological blocks (module assignment, StateRep configuration) have been configured, you must compile the CFC charts and download the AS.

Note AS change compilation and change downloading is possible.

2.1.4 Configuring the hiding matrix

In the previous three sections of the configuration you have established the basis on which to configure the alarm hiding matrix in the process object view (Figure 2-19). In the process object view you can define which alarms of the group’s message-capable blocks to hide based on the operating condition of the corresponding block group. Only 10 columns of the operating states are displayed by default in the process object view. You can show additional columns via “Simatic Manager -> Options-> Columns-> Process object view-> Messages -> Visible columns-> Status “ Besides configuration in the process object view, you can also export the data to CSV, edit (e.g. in Excel) and re-import them.

Note Make sure that the data format of the exported file will not be changed when editing this file with spreadsheet tool. (e.g. if the chart is named with 001, that the 00 are not cut away)



2.0, Beitrags-ID: 39134774

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Procedure: 1. Open the “Messages” tab and select “Block group” in the “Filter by column”

dropdown list box and enter the name of the block group in the “Display” box. 2. Configure the hiding matrix for the selected block group.

Figure 2-19 Message matrix in the process object view

After you have completed all configuration steps in the ES, compiled the CFC charts and downloaded the AS, you must compile and download the OS.

Note Delta loading is possible for changes made to the hiding matrix of an existing block. When adding a new message-capable block with a configured hiding matrix, the alarm hiding functionality won’t be active after delta loading. To activate this functionality you have to restart the OS server.

You also have to restart the OS server after delta downloading changes of the block group assignment.

2.1.5 OS compilation

Based on the “message matrix” from the process object view, a hiding matrix is generated automatically during OS compilation in the Alarm Logging as an additional attribute (Figure 2-20). You can use this matrix later in OS-RT to hide alarms in the alarm lists. Furthermore, the corresponding block group is entered automatically as an attribute for each message. A user-specific alarm group is generated for each block group which contains all alarms of the blocks for the block group. The status tag of



Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

the “StateRep” block belonging to the block group is available in the alarm group properties (Figure 2-21). A “QState” tag is created for each “StateRep” block in the WinCC Tag Management during compilation. The value corresponds to the current operating state (Figure 2-22). Additionally, there are internal tags of the type text reference that contain the configured operating status in plain text (Figure 2-23).

Figure 2-20 Hiding matrix OS alarm logging



2.0, Beitrags-ID: 39134774

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Figure 2-21 Integrating block groups, user-defined message classes, message class properties

Figure 2-22 “QSTATE” tag in the OS Tag Management



Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Figure 2-23 Text reference tag for configured operating state

2.1.6 Behaviour in OS Runtime

Alarm hiding in OS Runtime No alarms are hidden in “normal” operating state. The following pictures show the behavior of Alarm Hiding in OS Runtime. You can see the alarms in the group displays of the overview area (Figure 2-24), in the message line of the overview area and in the “incoming alarm list”. The “list of hidden alarms” is therefore empty (Figure 2-25).

Figure 2-24 New list in “normal” operating state

Figure 2-25 Hidden list in “normal” operating state

In “Maintenance” operating state, several alarms of the plant area “SAH_Engineering“ are hidden as configured (Figure 2-26).



2.0, Beitrags-ID: 39134774

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

No alarms are displayed in the group displays of the overview area for the associated plant sections “SAH_Engineering“. And no alarms of these subareas are displayed in the message line of the overview area and the new list (Figure 2-27). Alarms of these area are filtered and moved to the “list of hidden messages” (Figure 2-28).

Figure 2-26 List of hidden messages in “maintenance” operating state

Figure 2-27 New list in “maintenance” operating state

Figure 2-28 List of hidden alarms in “maintenance” operating state



Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

The runtime model represents the alarm behaviour and the display of alarms during process operation with alarm hiding activated and deactivated. Points 1-5 show that with alarm hiding active the messages generated in the AS are processed in the OS alarm server and thus archived. But they do not appear in the alarm views and in the process pictures. In points 4-6 an alarm is pending. The alarm hiding is deactivated in point 5 and the incoming alarm is immediately displayed in the message views and process pictures. In points 5-8 alarm hiding is disabled. Incoming alarms are displayed in the alarm views and process pictures. In points 8-12 alarm hiding is reactivated. The alarm still pending at point 8 remains in the OS alarm server as coming in, but it is immediately hidden in the alarm views and process pictures. Figure 2-29 Runtime model of automatic alarm hiding

Alarm hiding active

Alarm in control server (AS)

Alarm in alarm views

1 2 3 4 5 6 7 8 9 10 11 12

Activate alarm hiding

Deactivate alarm hiding

Activate alarm (coming)

Deactivate alarm (going)

Alarm in alarm server (OS)

List of messages to be hidden With the new Version of PCS 7 an additional alarm list has been added to the existing lists. This new list called “List of messages to be hidden” shows all the messages which will be hidden in the current plant status. To open the “List of messages to be hidden” in the button bar a new button is available.



2.0, Beitrags-ID: 39134774

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Figure 2-30 Configuration of the “list of messages to be hidden”

In the Alarm Control you can activate the button that displays the “list of messages to be hidden” (Figure 2-31). This list contains all alarms which are hidden for a certain operating state.

Figure 2-31 Configuration of the “list of messages to be hidden”



Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Alarm view in the faceplate (SP1) Automatically hidden alarms are still displayed in the alarm list of the associated faceplates (Figure 2-32). This allows you to see whether alarms are present for a measuring point although automatic alarm hiding is active. Manually hidden alarms are not displayed in the alarm list of the faceplate.

Figure 2-32 Alarm view of a faceplate with active alarm hiding

Status of hidden alarms Besides the standard message states such as “coming“ or “going“, the process alarm list and the alarm journal also show the status “show” or “hide”. Both the alarm journal and the process alarm list will thus register if a message status changes from show to hide.

Figure 2-33 Message status show/hide in the alarm journal



2.0, Beitrags-ID: 39134774

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Figure 2-34 Message status show/hide in the process alarm list



Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

2.1.7 The principle of automatic alarm hiding

Figure 2-35 The principle of automatic alarm hiding

Block group 1

„StateRep“ State of block group 2 IN - BOOL 1-32 OUT - INTEGER

STOP

Emergency Stop

„StateRep“ State of block group 1 IN - BOOL 1-32 OUT - INTEGER

Operating State 0-32

(Enumeration)

Message block

Block group 2

Message block

„Hiding matrix“ Selection which messages of technological blocks will be hidden for a predefined operating state. The hiding matrix will be configured in the PO and mapped into the OS. SQL filters of the alarm lists put the related messages into the list “Hidden Messages”

Smart Alarm Hiding in V7.0 / V7.1 2.2 Manual alarm hiding


2.0, Beitrags-ID: 39134774

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

2.2 Manual alarm hiding

By hiding alarms manually, the operator can put those alarms out of sight which are irrelevant for the present operating state. Manual alarm hiding is OS server specific. If an alarm is hidden manually on an OS client, this alarm will not be visible on any client accessing the associated server.

2.2.1 Configuring automatic alarm hiding

Select the “Message display” tab in the OS Project Editor to configure the settings for smart alarm hiding (Figure 2-36). Here, you can activate the button for manually hiding alarms in the PCS 7 alarm lists and set the duration on the server after which a manually hidden alarm is displayed again.

Figure 2-36 Configuration for manual alarm hiding in OS Project Editor

Note Delta loading is possible for changes made to the hiding duration and the display of the button for manual hiding.

Smart Alarm Hiding in V7.0 / V7.12.2 Manual alarm hiding


Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

2.2.2 Behaviour in OS Runtime

An additional button is displayed in the alarm lists (Figure 2-37). This button allows you to manually hide selected alarms and move them to the “list of hidden alarms“. Manually hidden alarms in the incoming alarm list are acknowledged automatically, because they were acknowledged when manually hidden. When the configured hiding duration has expired, the alarms are shown again. They can also be manually re-displayed. Alarms which were manually hidden will appear after deactivating the hiding in the acknowledged alarm list unless they have recurred.

Figure 2-37 Additional button for manual alarm hiding

Figure 2-38 Runtime model of manual alarm hiding

Manual alarm hiding timeout active



1 2 3 4 6

Activate alarm hiding automatically



Alarm hiding active


Alarm in control server (AS)

Activate alarm hiding manually


5 7

Smart Alarm Hiding in V7.0 / V7.1 2.3 Alarm hiding versus alarm suppression


2.0, Beitrags-ID: 39134774

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

2.3 Alarm hiding versus alarm suppression

When an alarm is suppressed or locked, the alarm is already blocked at the measuring point. This means that messages of a measuring point will not enter the alarm system of the PCS 7 OS and are therefore not displayed and archived on the OS. When hiding alarms, the alarms of the measuring point are processed in the alarm system of the OS and archived. But, depending on the operating state, they are filtered for the operator and hidden if necessary. Alarm suppression is on a higher level than alarm hiding. If, then, alarm hiding is enabled for a measuring point while alarm suppression is active, alarm suppression will be predominant because it prevents all alarms from entering the OS alarm system so there is nothing to hide in the first place.

Figure 2-39 Runtime model of alarm hiding and alarm suppression

Alarm hiding active



1 2 3 4 5 6

Activate alarm hiding



Activate alarm suppression

Deactivate alarm suppression

Alarm suppression active


Alarm in control system (AS)

Glossar2.3 Alarm hiding versus alarm suppression


Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Glossar 3

Term NAMUR International user association of automation technology in process industries EEMUA Engineering Equipment & Materials Users Association

Related Literature 4.1 Related Literature


2.0, Beitrags-ID: 39134774

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Related Literature 44.1 Related Literature

1. “Alarm Systems – A Guide to Design, Management and Procurement”, EEMUA, 1999

2. “NA 102 – Alarm Management”, NAMUR, Version 15.21.2005 3. “Institutionalizing Alarm Management”, Matrikon Inc., 01.2004 4. “Alarm Management White Paper”, Matrikon Inc., D.Shook 5. „Alarm Management“, EXIDA, 2006

4.2 Internet Link Specifications

This list is not complete and only represents a selection of relevant information. Table 4-1 Internet Links

Topic Li Link

\1\ Reference to the entry

http://support.automation.siemens.com/WW/view/en/39134774

\2\ Siemens I IA/DT Customer Support

http://support.automation.siemens.com

\3\

http://support.automation.siemens.com/WW/view/en/39134774�

http://support.automation.siemens.com/�

History4.2 Internet Link Specifications


Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

History 5 Table 5-2 History

Version Date Modifications

V1.0 12.01.2007 First version on the DVD PCS 7 V7.0 V2.0 05.11.2009 Layout adjustent for the publishing in the Service & Support

Portal under “Applications & Tools” (see link in Table 4-1).

pcs 7 in-practice alarmhiding sp

Documents

application examples

practice smart alarm

copyright siemens ag

alarm management

table of contents smart

siemens publications

service portal of siemens

liability clause