System 800xA training

Chapter 16 Alarm and Events

TABLE OF CONTENTS
Chapter 16 Alarm and Events........................................................................................................................................................ 1 16.1 General Information........................................................................................................................................................... 3 16.1.1 Objectives ................................................................................................................................................................... 3 16.1.2 Legend ........................................................................................................................................................................ 3 16.2 Alarm and Events .............................................................................................................................................................. 5 16.2.1 General........................................................................................................................................................................ 5 16.2.2 Data Flow.................................................................................................................................................................... 6 16.2.3 Storage ........................................................................................................................................................................ 7 16.3 Alarm and Event Presentation ........................................................................................................................................... 9 16.3.1 Alarm List................................................................................................................................................................... 9 16.3.2 Graphic Display ........................................................................................................................................................ 10 16.3.3 Faceplate ................................................................................................................................................................... 11 16.3.4 Alarm Band............................................................................................................................................................... 11 16.3.5 Alarm Sequence Bar ................................................................................................................................................. 12 16.3.6 Event List.................................................................................................................................................................. 12 16.4 Alarm Operations............................................................................................................................................................. 13 16.4.1 Navigation................................................................................................................................................................. 14 16.4.2 How to Acknowledge Alarms................................................................................................................................... 15 16.4.3 How to Silence Alarms ............................................................................................................................................. 15 16.4.4 Alarm Status Indications in Faceplates..................................................................................................................... 16 16.4.5 How to Add Comments ............................................................................................................................................ 16 16.5 Creating Alarms and Events in Control Logic................................................................................................................ 17 16.5.1 AlarmEventLib ......................................................................................................................................................... 17 16.5.2 AlarmCond and AlarmCondM ................................................................................................................................. 18 16.5.3 Transmission of Alarm Data..................................................................................................................................... 20 16.6 Alarm and Event Service Configuration.......................................................................................................................... 21 16.6.1 Alarm Manager Service ............................................................................................................................................ 22 16.6.2 How to Reduce the Alarm List ................................................................................................................................. 23 16.6.3 How to Setup the Event Collector Service................................................................................................................ 24 16.7 Name Uploader................................................................................................................................................................ 25 16.7.1 Problem Description ................................................................................................................................................. 25 16.7.2 Names and Description Texts ................................................................................................................................... 26 16.7.3 How to Run the Name Uploader............................................................................................................................... 27 16.8 Configuring Alarm and Event List Template .................................................................................................................. 28 16.8.1 Library Structure....................................................................................................................................................... 28 16.8.2 How to Create a New Template................................................................................................................................ 29 16.8.3 The Sort Tab ............................................................................................................................................................. 30 16.8.4 The Priorities Tab ..................................................................................................................................................... 31 16.8.5 The Column Tab ....................................................................................................................................................... 33 16.8.6 The Time/Date Tab................................................................................................................................................... 34 16.8.7 The Filter Tab ........................................................................................................................................................... 35 16.8.8 Event List Template Configuration........................................................................................................................... 36 16.9 Alarm and Event Lists ..................................................................................................................................................... 37 16.9.1 Alarm List Configuration.......................................................................................................................................... 37 16.10 External Alarms ............................................................................................................................................................. 39 16.10.1 External Alarm Configuration ................................................................................................................................ 39

1 / 44

T315-16 Alarm and Events - RevA

16.10.2 External Alarm Silence ........................................................................................................................................... 40 16.11 Hide Alarms ................................................................................................................................................................... 41 16.12 Alarm Logger (Printer) .................................................................................................................................................. 43 16.12.1 Alarm and Event Logger Configuration.................................................................................................................. 43 16.12.2 Alarm Logger Service ............................................................................................................................................. 44

2 / 44

System 800xA training

16.1 General Information 16.1.1 Objectives
On completion of this chapter you will be able to: • • • • • • Describe how alarms and events are distributed Handle alarms (operation) Create alarms in control logic Configure alarm and event lists Configure annunciation of alarms (external alarm) Set up an alarm logger (printer)

16.1.2 Legend
<> | Bold “ “ Indicates a key name. Indicates when you go from one menu to a sub-menu. Indicates a menu name or an option in a menu, or file structures Indicates dialog box buttons, tabs, instructions etc. Indicates start/explanation of student activity

3 / 44

T315-16 Alarm and Events - RevA

4 / 44

g. it causes a change in the alarm condition.g. Object events e. Object alarms e. The alarm condition also changes if any of the following actions are carried out locally on an alarm: • • • acknowledgement disabling enabling 5 / 44 . When such a signal changes value. PID-controller set point was changed.2. level too high in a tank. pressure in the reactor back to normal. • • • Process alarms e. In general an event is the transition of a Boolean variable from one state to another (False to True or True to False). the operator is able to monitor status changes of a certain signal. In an alarm condition. motor temperature too high.g. etc. etc.2 Alarm and Events 16. pressure too high in a reactor.g. motor was set to manual mode. • • • • Process events e. etc.1 General Alarms and events are used to inform the operator of the status of processes and systems. valve opened.System 800xA training 16. Alarms are also presented in the Event List The Event List is the log book that indicates what happened in the plant Alarms They are a subset of events that alert you to an abnormal process or system state. Events They give information regarding changes in the process state and other operational occurrences in the plant. Alarms need to be acknowledged NOTE! All alarms are events. but not all events are alarms. etc.

A message is sent from the controller.RevA 16. The alarm indicates a problem and the purpose is to direct the operator’s attention towards plant conditions.2 Data Flow An Alarm system is an important element in almost all modern operator interfaces to industrial plants.2. 3. some form of visual indication. See later in this section for how to create alarms in control logic.T315-16 Alarm and Events . via the OPC server (Connectivity Server). so he can correct potentially dangerous situations in time. The alarm is displayed on the Operator Workplace. to the alarm (Aspect) server in the operator station. Alarms are signals announced to the operator by an audible sound. 6 / 44 . 2. Beep! Aspect Server Beep! Workplaces (clients) Client/server Network 3 Connectivity Server Control Network Controllers 2 Field bus 1 Field devices 1. and/or with a message of some kind. An alarm limit in the process is exceeded.

By clicking the “Edit” button in the Alarm Storage area you can configure the alarm storage. You can set the maximum number of alarms which can be stored in the Alarm Manager.3 Storage Alarms All alarms are stored. The Alarm Server is capable to save the 10000 (default) most recent alarms in a “circular” file but the size can be changed. 7 / 44 . by default.2. in the main storage.System 800xA training 16.

or make sure the system messages do not overflow the disc. connected systems.RevA Events / System Messages The System Message server handles messages from the server. NOTE! Please refer to the manual for more detailed information.T315-16 Alarm and Events . and workplace clients. The two reasons to change the default values for the system message configuration are to increase/decrease the number of stored messages. Normally you do not need to alter the defaults of the System Message Server. 8 / 44 .

display shortcuts) or through aspects selectable from a workplace. 16.1 Alarm List An alarm list only includes the alarms that an operator needs to pay attention to. You can access the alarm functionality as part of the configuration (Application Bar. normally: • • unacknowledged still active alarms This is the most familiar presentation. alarms end events are presented in a list format with one line for each alarm: 9 / 44 . Status Bar.3 Alarm and Event Presentation There are many indications of an alarm in the operator workplace.3.System 800xA training 16.

3. 10 / 44 . Alarm Line The indications in the application bar are the most important because the only alarms visible in a graphic will be the set of tag objects in that graphic. and there is an Alarm Line in the application bar at the top of the screen.RevA 16. but it is always on the screen and it only has the latest three alarms in it. The designers of the system can filter this alarm list so that only a selection of the alarms for the system show up if they want to. Alarm Line Red blinking The figure shows that there are alarm indications in the graphic display.T315-16 Alarm and Events . It is very similar to any other alarm list.2 Graphic Display Process and object alarms are normally also indicated on the process graphic displays by red blinking.

3. Alarm indication 16.System 800xA training 16. Click on the Alarm Band (button) to call up the associated Alarm List. 11 / 44 . The color of the button indicates the highest priority alarm that is active in that list. at least one alarm is not acknowledged. The number within the button represents the number of unacknowledged alarms.3 Faceplate Faceplates have by default an alarm indication and the alarm can be acknowledged.4 Alarm Band The Alarm Band Aspect is usually configured to appear in the Application Bar of the workplace. each button represents one alarm list.3. It appears as a group of buttons. If the button is flashing.

T315-16 Alarm and Events .RevA 16.6 Event List The Event List is the log book that indicates what happened in the plant.3. The bar is usually sized and arranged horizontally across a screen.3. 12 / 44 .5 Alarm Sequence Bar Here each alarm is represented by a single button. 16.

Each time the lists are called up again they will come up as the default order they are configured with.Z). Repeat this action to reverse the sorting. Sorting Columns To sort a column double click on the column header. Sorting a second time will cause the sorting to be reversed (Z. For example.System 800xA training 16. These changes are not remembered... sorting Source Name once may cause the items in the list to be sorted in alphabetical order (A. Tool bar Use the “Page Down” button to show the next 500 alarms in the list.4 Alarm Operations The picture below displays a typical view of an Alarm and Event List aspect.. You can also return to this order by clicking the Rest button on the toolbar.. 13 / 44 .A). The information presented in each list is organized in a way defined by its configuration (what columns show up in what order and how the list is sorted).

most common a faceplate. Context Menu You can right-click on an alarm line in the alarm list to bring up the context menu.1 Navigation If you double-click on an alarm line in the alarm list the default aspect for the process object/alarm will appear. silence the audible alarm or add a note.4.T315-16 Alarm and Events . 16.RevA Stop/Start Alarm and Event Updates You can stop or restart list updates using the “Stop” button. 14 / 44 . By using the context menu you can perform some actions on this alarm line for example acknowledge the selected alarm.

then click on the Acknowledge verb in the context menu. The following figure shows these options: 16. 15 / 44 . click on the “Silence” button or select “Silence” in the context menu.press the “Acknowledge” button (green check mark) Right click on an object in.4. Click on the alarm status button in a faceplate NOTE! To be allowed to acknowledge an alarm you need to be granted permission for this operation.4. This is a one shot type action that silences the current audible alarm. for example. Select a group of individual alarms and then. • • • Alarms can also be acknowledged in a process graphic display or a faceplate.2 How to Acknowledge Alarms You can acknowledge alarms for an Aspect Object in the following ways: • Click on the “Ack State” box for the alarm in the list to acknowledge the one alarm.select “Acknowledge Selected” in the context menu or . If a new audible alarm then occurs. If not logged on as operator blink behavior around check box will not occur.3 How to Silence Alarms To silence an audible alarm.System 800xA training 16. a process display or process graphic. . that alarm must be silenced again. NOTE! To silence an alarm does not mean that the alarm is acknowledged.

16. The Message Comment dialog box is displayed and you can type a message. 2. 3. Right-click on the alarm to which you want to add a comment.4 Alarm Status Indications in Faceplates Faceplates provide a set of symbols for alarm status. Select “Comment” from the context menu. deviation alarm.4. low alarm. 16 / 44 .T315-16 Alarm and Events .4. etc.RevA 16.5 How to Add Comments To add a comment for an alarm do as follows: 1. The operator would normally take a closer look to see whether it is a high alarm. Of course this is only an indication that the object is in alarm or not.

For example the ValveUniM is defined with an Alarm handling module within it. in order for time stamps to be reliable when trying to analyze a sequence of events. It can be used to generate an event on the rising edge of a boolean input. These are placed in the application within the objects that require alarm monitoring.5. 16. Alarm text is configured here along with severity (priority). Time stamping is done to a resolution of 1 ms. Settings for severity and class are provided. The SimpleEventDetector function block type is also located in the AlarmEventLib.1 AlarmEventLib Process alarms are generated by functions blocks or control modules which are defined in AlarmEventLib. These modules will generate an alarm to the OPC server on the rising edge of a boolean input. 17 / 44 .System 800xA training 16.5 Creating Alarms and Events in Control Logic Alarms and events are generated in three ways: • • • by using objects based on library types containing alarm and event functions by using objects especially made for alarm and event handling (based on the types in the Alarm and Event library) by hardware units throughout the system (system alarms) NOTE! All alarms and events follow the OPC Alarm and Event specification. When an alarm is generated it is time stamped in the controller in which the detector is executing. The user may create alarms by using alarm detectors/generators in a similar manner. Alarm and event handling also requires time synchronization.

2 AlarmCond and AlarmCondM The two basic types for creating alarm conditions are the function block type AlarmCond and the control module type AlarmCondM.RevA 16. The following figure is an example on how to configure an alarm using function in a controller.T315-16 Alarm and Events . The principle behind the two is the same. 18 / 44 .5. The CondState parameter indicates the status of the alarm.

and 1000 is the most severe level. for example. Severity Indicates the degree of severity. AckRule Determines which acknowledgement rule is used. for example. “Level_High“. The acknowledgement rule decides the behavior of the alarm condition when an alarm has been created. Name of the source has to be unique together with the condition name. The condition name is normally the name of the alarm condition function block or control module instance. Message Can be used to add a textual description of the alarm condition. “Motor101”. • AckRule = 1 “normal handling”. CondName Identifies the alarm condition. “temperature low”. for example. SrcName Identifies the alarm source. alarms must be acknowledged and inactive before the “normal” state is resumed AckRule = 2 alarms need no acknowledgement AckRule = 3 alarms return to “normal” state on acknowledgement AckRule = 5 alarms return to “normal” state when a sum system alarm is acknowledged and returns to its normal state • • • 19 / 44 . The parameter Inverted can be used to invert the in signal.System 800xA training The following parameters are the most important ones: Signal Internal monitored Signal. This parameter is very useful when filtering alarms and events. where 1 is the least severe.

operator acknowledgement must be transmitted back down from the client to the controller. in the Alarm and Event Tab: 20 / 44 .T315-16 Alarm and Events . NOTE! Thus alarm handling involves two way data exchange. a simplified diagram is shown below: The first link in the chain is the MMS Server. it handles the subscription to alarms in one or more controllers on the control network. Client Application: Alarm List Alarm and Event Server OPC Server MMS Server Controller 1 Controller 2 Controller n The OPC Server is connected to the MMS Server.5.RevA 16.3 Transmission of Alarm Data The data associated with an alarm must be transmitted up to the 800xA System and then on to the clients for inclusion in alarm lists etc. Similarly. Considering the transmission of an alarm up to the client. It is configured in the OPC Panel.

21 / 44 . The services for Alarm and Event are found in the Service Structure.System 800xA training 16.6 Alarm and Event Service Configuration Prior to configuring the Alarm and Event List display. the user must setup the service provider and service group definition.

A second Service Group called SoftAlarms is also created.T315-16 Alarm and Events . This also has a service provider.1 Alarm Manager Service The services are arranged into ‘Service Groups’ and within any group there may be one or more ‘Service Providers’. The Configuration Tab of the Service Group Definition aspect points to the Service Provider (The Alarm and Event Server running as part of the 800xA system). Soft Alarms are those generated in the 800xA Server rather than the controllers. The service provider is the program that provides the service to the group as a whole.6.RevA 16. Each Service Provider has a Definition which gives it its name and also sets its running status. The Service Group object points to this provider in its own Service Group Definition. During installation a Service Group (called Basic) and a Service Provider (called Alarm_Manager_Basic <PCName> object is created. 22 / 44 . There may be one or more service providers in a group.

System 800xA training 16. The setting for this is located at the Special Configuration tab on the Alarm Manager Service. 23 / 44 .6. each inactive to active state change will result in a new alarm. NOTE! For reducing your alarm list please disable this setting.2 How to Reduce the Alarm List If one alarm occurs several times you can reduce your alarm list so that this alarm is presented only once. If the check box Make new alarm entry each time a condition gets active is marked.

Select the OPC Server that is your collector (supplier of alarm and event information) under “Alarm Server”. 4.T315-16 Alarm and Events . 2. 6. Service and select Basic. Open the Service Structure in the Engineering Workplace and expand Services. You do this as follows: 1.3 How to Setup the Event Collector Service You have to connect to an OPC Alarm Server (collector) before you can get any alarms and events. Select Service Group Definition in the aspect list. 3. Select the “Special Configuration” tab in the preview area. Click “Apply”. Open Event Collector.RevA 16.6. Service Group. 5. 24 / 44 .

The second is the Name aspect.7. which contains the corresponding aspect object name in Plant Explorer. Control Builder Libraries Engineering Workplace Object Type Structure Valve Valve Tank Tank Valve1 (type “Valve”) Valve1 Relative name Control Builder Applications myTank Tank Valve1 Valve Name Name In the example above. 25 / 44 . When the instance is created it must be given a name such as Valve1.g.7 Name Uploader There are two different name aspects in Plant Explorer for representing a control object name.System 800xA training 16. only the top-level of the type is assigned a new and unique name. The first is the Control Builder Name (CBName) aspect. the tank contains one or more valves created from other control module object types. NOTE! If there are no unique names. the object name in an alarm list will be presented with a GUID number! 16. When the Tank control module object type is instantiated several times in the application it will also be possible to name the instance e. Name uploading can be used to secure unique names for control objects that are embedded in type solutions. myTank but the valve will still have the same name! NOTE! The valve can therefore not be identified by a unique name and have its own faceplate. which always is synchronized with the present name in Project Explorer.1 Problem Description When a function block type or control module type is used to create an object. and therefore always follows IEC 61131-3 naming conventions.

The solution is entering appropriate strings for the name and description variables on the Control Modules.7. 16.RevA The Name Uploader tool solves this problem by going through all objects further down in the Control Structure. all objects must have a Name and a Description parameter. The Name Uploader then fetches the names via the OPC server so that each object has a system-unique name. NOTE! For the Name Uploader to work.2 Names and Description Texts If there is more than one instance of the Tank type. 26 / 44 . Control Builder Applications Engineering Workplace Control Structure myTank Tank Valve1 Valve Variables Name = V047 Description = Text Variables Name = P01 Description = Text Control Structure after Name Upload Control Structure before Name Upload After running the Name Uploader this will result in unique name and description in the name aspect on the Control Structure instances.T315-16 Alarm and Events . it will result in equal faceplates for the valves below these instances. looking for Name properties.

Click “Start Upload”. Verify the name changes in the Control Structure. 2.System 800xA training 16. 27 / 44 .7. NOTE! The Name Uploader aspect is by default placed on all control networks and on all applications. select your application and click on the Name Uploader aspect. 3.3 How to Run the Name Uploader To start a Name Upload for an application: 1. In the Control Structure.

It is never a very good idea to modify system default objects because in a future revision upgrade our customization could be overwritten.8. The main philosophy is that all configuration templates shall be in the Library Structure and from there be instantiated to objects. the instantiated aspects will change or update at the same time as the aspect in the Library structure. If so.1 Library Structure The appearance of an Alarm and Event List is controlled by an Alarm and Event List Configuration aspect. This is always defined in the Library Structure of the Engineering Workplace: There are default Alarm and Trend Configurations delivered with the system and they are used if no other configuration is defined. We can also create our own objects by adding a new object from the list as we have done previously.T315-16 Alarm and Events . This reduces the cost of maintenance and secure that all aspects will be updated or changed.8 Configuring Alarm and Event List Template 16.RevA 16. The actual Alarm and Event List aspect is then set up to use a particular configuration. 28 / 44 . NOTE! Copying the defaults to new objects or inserting new templates is the most preferable option. or we can copy an existing object and modify it.

Add a new object to create a group for all your project specific templates. 29 / 44 . This will now be a new group besides the Default Configurations. which you can use now for your Alarm & Event List aspects.2 How to Create a New Template You can make your own set of default Alarm and Event Lists in the Library structure.System 800xA training 16. To this new group add a new object. 2. Go to the Library Structure.8. Select the Alarm & Event Configurations folder and open it. Do as described below: 1. 3. Now you created your own default plant Alarm and Event template. for use in your plant. Alarm & Event List Configuration Group. 4.

For configuration select your project Alarm & Event List Template object in the Library Structure. it is pretty common to sort by event time with the newest events at the top of the list. In fact multiple criteria can be used (max. three). but this is not rigidly defined. we sort alphabetically by name and so on. and so on. we will configure it in the same way.8. select the blank area in the Sort Criteria area. 30 / 44 .RevA Whether we use the ‘default’ templates or we use the newly created object on the in the Library Structure. For example. NOTE! To remove an item from the list. Then. The default is to sort first by event time newest events at the top. in case of two events with the same time.3 The Sort Tab We can select how the alarms will be sorted in the list. If you select the Alarm and Event List Configuration aspect of this object then you have access to five different tab cards in the “Config View”: • • • • • Sort Priorities Column Time/date Filter 16.T315-16 Alarm and Events . We could sort by priority or alphabetically by name.

For this reason. 938-1000 maps to Priority 1.4 The Priorities Tab 800xA system supports 1000 different priority levels. the sixteen priorities are mapped to the one thousand 800xA priorities in the following figure. 31 / 44 . and steady when acknowledged. but the colors under the heading ‘Unack Text /AckBox Bg’ are blinking. Notice that we can assign background color to each priority. It is not obvious from above figure. The text will be in red and the background will be in black. Of course we can change any of the colors and also change whether they blink or not.8. Of course we don’t have to use that many priorities. NOTE! Three or four levels are very common. It will be blinking when unacknowledged. The top priority row. but we only use 16 priority levels for simple discussion. then these are the colors that will show up in the alarm list.System 800xA training 16. and we can also assign a background color to the entire list. This will be the color where there are no alarms. perhaps for readability. If we select that level in our tag for some condition such as the active state of high alarm.

it is important to do one of two things if this form of annunciation will be used: • One is to keep a dedicated alarm screen with this alarm list up all the time. You also want to be able to change these colors in one operation for all occurrences. A logical color is defined once. They do not send the tone to the sound card unless the display is on the screen.WAV file. Many plants do have one screen that always has the alarm list on it anyway so this is a good plan for them. • 32 / 44 . Setting Sound Click on the Sound column to preview or associate an individual . For this reason.RevA Some colors need to be the same in all places. to give the system a user friendly look (for example the background colors).T315-16 Alarm and Events . and the user of the color refers to it by its name. with each priority and set the duration of the sound: • • • OFF = no sound Momentary = one sound when a new alarm gets active Continuous = a constant sound as long as the alarm is unacknowledged One important thing to know about this is that these sounds are part of the Alarm List Display. Logical color is the concept used in System 800xA to be able to fulfill these needs. The other thing is to enable the annunciation from the Alarm Line. We will see in the next section that this is a special Alarm List that stays in one place on the screen all the time.

Of course scroll bars allow us to have access to more than a screen of data. There are a few configurable options on this tab such as font and blink and whether to make the column and row headings visible. An edit box will appear. but it is preferable that an operator sees what is most important at a glance. 33 / 44 .5 The Column Tab It provides the means to define exactly what fields show up what order for an alarm in the list. 1 to 500. Setting Order of Columns Move a column either by selecting the Message Field and using the positioning arrows to move the column up (left) or down (right) or drag and drop the column to the proper position within the Message Layout area. Changing Column Header Names Select the row to be changed and then click on the column header name.System 800xA training 16. Viewable Messages Enter a number. Changing Column Size Select the row to be changed and then click on the column with. to set how many messages that shall appear in the list. There are many more details about a tag and about the alarm condition than will fit on the screen at one time. An edit box will appear where you can change the name. in which you can change the size. The customized name appears in the column heading. Another way to change the name is to select the row to be changed and then press F2.8. It is also possible to change the width by dragging the columns to the right size in the Message Layout area.

Regional differences in the format that people are used to seeing are important because the operators need to react quickly to this information. 34 / 44 . the space left for other information is reduced.6 The Time/Date Tab There is not much that needs to be said about the Time/Date tab once you look at it. NOTE! If the time shown is a long format. Use the same time separator as defined in Windows Regional Options.T315-16 Alarm and Events .RevA 16. It is self explanatory. to be able to copy data to other applications such as Excel.8.

8.System 800xA training 16. These options provide a lot of flexibility. Many users have a strong preference for one or the other of these options and there is no one way that works best for all situations. The first selection. or vice versa. Please note that if you change the Message Type from Process Alarms to Events. these are the choices: • • • Process Alarms Events everything coming from the OPC AE server This tab allows the list to have a defined start and end time or to be simply oldest to newest. It allows a selection of which priority levels to include in the list so that we could define separate lists for different levels. If you pull down the selection.7 The Filter Tab Be aware that there are many options that may not be shown when the tab is first called up. categories must be selected. NOTE! The options ‘Process Section’ apply to AC400 Connect. Message Type is the main difference between an alarm list and an event list. The Filter tab provides a means to select what events to display in the list. the alarm disappears or to include acknowledged alarms so that they remain until they are both inactive and acknowledged. It allows us to have only active and unacknowledged alarms so that when we acknowledge. 35 / 44 . Some choices will simply not be visible if the window is too small.

Used to store messages that haven't been defined in the system yet. Used to log administrate actions in the system. be that an aspect system is loaded to the system. To filter Event Categories.8. This can. The event list is simply a record of what is happening. Used to log operator interaction. select each category to be included in the Event List (shown with blue line). 36 / 44 .T315-16 Alarm and Events . Used by the Service Manager and Services. Used for simple process events (does not include any state or condition of the object). and it grays out choices for active or inactive and enabled or disabled since these choices apply to alarms.8 Event List Template Configuration An Event List uses the same configuration object with a couple of different options. Used for Security tracking events. Used to log annotations that have been made by a user. the message type is set to ‘Events’. Example of Categories (Storage Class) AE Condition Event Description Used for condition process events (the event carries information about a condition of the process object. the condition PVLEVEL and the subcondition can be HI_HI). There are also many types of system messages. Used to log status events regarding hardware.RevA 16. This can be an annotation associated with a process alarm. for example. Some of the additional message types are audit trail types such as configuration and operator actions. Many users never bother with an event list because they are only interested in responding to abnormal conditions. There are also some differences on the Column tab since we do not need some of the ones that apply to alarms such as the acknowledgement related fields. Used for acknowledgement of alarms and other kinds of tracking events. if you look at the default lists. is that on the filter tab. The major difference between the alarm and event lists. This adds many more categories of messages to the selection list. Used for important events that are not directly related to a process object. for example. AE Simple Event AE Tracking Event Audit Event Default Class/Storage Network Messages Operation Services System Administration System Status User Annotation The Priorities tab has all events in a single color because there are no priority levels for events. Events are not considered to have an abnormal condition as alarms have. A selection can be deselected by another click.

you can place the aspect in the Control Structure as well. In this way it is easy to have as many alarm lists as you like. Object and descendents Show the alarms and events related to the object the Alarm List aspect belongs to and to all its descendents independent of structure.9 Alarm and Event Lists Alarm and Event list aspects may be placed in any structure and configured to list the Alarms for that object or else that object and its children. Only in this structure you can use the filter options in an efficient way. Object Alarms Show the alarms and events related to the object the Alarm List aspect belongs to. The option Local will allow you to set all the template settings locally at your Alarm / Event aspect.9. Define an alarm filter in the Alarm filter area: • • • All alarms Allow this aspect to display alarms and events for all objects. Typically an Alarm / Event aspect is placed in the Functional Structure. Use the Config View to set up the association of the list to a selected configuration aspect and what elements are to be displayed on the list. 16.the Main View and the Config View. and to arrange for the alarms in each list to be organized. Anyway.System 800xA training 16. The Alarm and Event list aspect base on a template used in the Library Structure. Object and descendents in structure Show the alarms and events related to the object the Alarm List aspect belongs to and to all its descendents in the selected structure.1 Alarm List Configuration The Alarm and Event List aspect have two views . NOTE! Using this option increases CPU load. • 37 / 44 . Alarms and Events may be passed up the hierarchy to a ‘collector’ list near the top.

• 38 / 44 . • • List Title The list title name is displayed in the Alarm Band of the operator workplace.RevA Additional Settings The Config View of an Alarm / Event aspects offers some additional settings.T315-16 Alarm and Events . This sound is defined in the alarm template Show Tool Bar Enables the tool bar in the Main View of the Alarm / Event aspect. Play Alarm Sounds For getting knowledge about new alarms by a sound.

In the External Alarm Configuration dialog box.System 800xA training 16. When alarms fulfilling the filtering criteria are received by the external alarm function the destination output is set. 2. The syntax for the destination is: <Object:Aspect:Property>. 16. 1. You also configure the path to the destination output. 4. 5. Silence can be done for all configured alarms or for one explicit external alarm.10. The operator can silence the external alarm through the silence view. select the alarm list in the Alarm List drop-down menu. Click “Apply”. 39 / 44 . Select the object you want to add an External Alarm Configuration aspect to. Write the destination output to be used in the Destination text field. Add a new aspect from the context menu and select the “External Alarm Configuration”. 3.1 External Alarm Configuration In the External Alarm Configuration View you select the Alarm List and which filter criteria the external alarm uses to subscribe alarms. For example a horn can sound if a new alarm gets active in the alarm list.10 External Alarms The External Alarm function makes it possible to setting a digital output when a specific alarm list gets an active alarm. NOTE! This aspect needs to be added to the same object as the Alarm List aspect where the alarms will appear. The destination can be an alterable OPC property.

It provides an interface in the Engineering Workplace as shown below where we can do that.10.RevA 16. But since it is an aspect.2 External Alarm Silence The other aspect we need to define is the External Silence aspect. NOTE! A default aspect is provided in the Library Structure.T315-16 Alarm and Events . This simply provides a button to silence any one or all of the external alarms we have configured. 40 / 44 . it can be called up with an Aspect Link in a graphic also.

41 / 44 . For example. it is possible to hide non-important alarms. The Hiding alarm function will help the operator to get the alarm lists clearer from irrelevant alarms. which can be process conditions or logical expressions. during start-up or a shut-down of a process or plant. An alarm is irrelevant if it doesn't require an action from the operator. All the hiding rules are kept in the Hiding Mask Manager. refer to the Instruction Manual for more information. it is common that alarms. The hiding of alarms is initiated by hiding rules.11 Hide Alarms Hiding is a way of avoiding alarm situations where numerous alarms make it hard to determine what is the problems root cause. By using the hiding function in 800xA.System 800xA training 16. Hiding affects the presentation of the alarm list. If an alarm is irrelevant it should not be shown in an alarm list. NOTE! To configure the Hiding Mask Manager. are totally irrelevant. which are relevant during a normal operation.

RevA 42 / 44 .T315-16 Alarm and Events .

since the alarms print out as they occur. colors and sounds are not supported. The printer has to be connected as a local printer to the node in Windows. Any device that can be configured as a Windows printer device will work. but since the alarms print out one at a time as they occur. 43 / 44 .System 800xA training 16. just as with alarm and event lists. it is very similar to an alarm list because it is a special case of an alarm list. 16.12. it is recommended that the print device be a line printer rather than an Ink-Jet or Laser-Jet. In fact. Also on the priorities tab. This is one of the default objects there along with the Alarm and Event Lists. There are just several things that are not supported on the printer that are supported in an alarm list. there is no need to sort them so no sort options are supported.12 Alarm Logger (Printer) An Alarm Logger is an alarm printer. The line printer used has to be added to a Windows node on which you run the System.1 Alarm and Event Logger Configuration The first is to configure the Alarm & Event Logger Configuration object in the Library Structure. You can create a new one or use the default. For example. called Common Logger Config.

if you expand the Alarm Logger Service. In the Service Structure. This is where a printer is assigned.2 Alarm Logger Service The next thing that needs to be done is to configure the Alarm Logger Service.12. 44 / 44 .T315-16 Alarm and Events . on the Basic Service Group’s Special Configuration tab. The next thing is to select the Special Configuration tab of the Service Provider inside the Basic Group. First. there is a basic group.RevA 16. we specify which Alarm & Event Logger Configuration object from the Library Structure to use. In the group there will be at least one node.

Sign up to vote on this title
UsefulNot useful