AAM Manual Builder 2ed

AAM MANUAL BUILDER R100
AAM Builder
User Manual
IM 052006-A01 2ND EDITION ISSUE 22 MAY 2006 PAGE - 1

Copyright Notices
©2006 Yokogawa Electric Corporation
All Rights Reserved

All rights are reserved in this document, which is the property of Yokogawa Electric Corporation.
Information contained herein is the property of Yokogawa Electric Corporation.
Unless agreed in writing by Yokogawa Electric Corporation, the licensee shall not remove, release,
disclose, reveal, copy, extract all or part of the documentation.

Highlights
The Highlights section gives details of the changes made since the previous issue of this
document.
Summary of Changes
This is the 2nd Edition of this document.
Detail of Changes
The changes are as follows:
Chapter/Section/Page Changes
1st Edition Based on AAM Version 1.0
2nd Edition Updated based on AAM Version 2.0

AAM Document Set
The documents available for AAM are:
AAM Builder User Manual

(IM 052006-A01)
AAM Client User Manual

(IM 052006-B01)
AAM Statistical Report User

Manual (IM 052006-C01)
Functional Design
Specification-Alarm
Management System (NMR
601.21)

TABLE OF CONTENT
T1 INTRODUCTION ........................................................................................................ 6
T
1.1 Introduction .......................................................................................................................................................6
1.2 AAM Funcitons..................................................................................................................................................6
2 HOW TO USE THIS MANUAL................................................................................... 7
3 KEY CONCEPTS AND TERMINOLOGIES ............................................................... 9

3.1 Terms and Definitions .......................................................................................................................................9
3.2 Plant Hierarchy Concept ................................................................................................................................12
3.3 Operation by Area ...........................................................................................................................................13

3.3.1 Area and Plant Hierarchy...........................................................................................................................13
3.3.2 Area and AST ............................................................................................................................................14
3.3.3 Area and ExaOPC Server ..........................................................................................................................15
3.4 Security.............................................................................................................................................................16
3.4.1 Setting Security for the Administration Screens........................................................................................17
3.4.2 Setting Security for the Operation Screens................................................................................................18
3.4.3 Default User...............................................................................................................................................19
4 AAM BUILDER USER MANUAL ............................................................................. 20

4.1 Screen Layout for AAM Builder ....................................................................................................................20
4.1.1 General Layout ..........................................................................................................................................20
4.1.2 Screen Hierarchy .......................................................................................................................................21
4.2 Logon to AAM Builder....................................................................................................................................22
4.3 AAM-Common Module ..................................................................................................................................22

4.3.1 User Security .............................................................................................................................................23
4.3.2 System Configuration ................................................................................................................................29
4.3.3 Function Block ..........................................................................................................................................33
4.3.4 Uploading ..................................................................................................................................................36
4.3.5 Tag Hierarchy............................................................................................................................................41
4.4 AAM-Enforcer.................................................................................................................................................53
4.4.1 AST Builder...............................................................................................................................................53
4.4.2 Tag Monitor...............................................................................................................................................70
4.4.3 Shift/Enforcement PC................................................................................................................................75
4.4.4 Audit Trail Viewing...................................................................................................................................79
4.5 AAM Report.....................................................................................................................................................82

4.5.1 Configuration.............................................................................................................................................83
4.5.2 On-Demand Request..................................................................................................................................87

1 Introduction
This document describes the details of UI (User Interface) Screens and Software Structure of AAM
Builder Module for Advanced Alarm Manager (AAM) package. It will be used as the basis for the Client
operation.
This preliminary manual is based on the trial AAM software and shall be updated based on the final
version of AAM software.
1.1 Introduction
Yokogawa Advanced Alarm Management (AAM) system provides alarm documentation, alarm
enforcement on Yokogawa DCS, statistical reports on alarms, alarm enforcement and alarm
rationalization reports, and Sequence of Event reports.
AAM provides the capability of analyzing alarms and events and collecting and storing modifications to
alarm configuration data. All reports are viewed via the web, and only engineering and alarm database
enforcement functions are restricted to AAM client.
1.2 AAM Functions
Yokogawa AAM has been developed based on the following functional and operational considerations:
o Ability to retrieve alarm settings from the DCS to form the initial master alarm database. The
master alarm database also consists of alarm documentation which has to be manually
entered.
o Ability to modify the master alarm database and enforce the alarm settings in the master alarm
database into the DCS.
o Ability to view and store alarm data from PCS which includes Yokogawa DCS system and
Triconex ESD systems
o Ability to analyze the occurrence of alarms and various statistical reporting based on EEMUA
publication number 191.
o Ability to view modifications of alarm configuration data using web browser
o Ability to view alarm data.
Yokogawa AAM consists of three basic functions based on the above operational and operational
characteristics:
AAM Function Purpose

AAM Builder AAM Builder function is implemented to “build” the AAM with following
engineering practices:
Common: System-wide information such as plant hierarchy, data
source definition, modification of alarm documentation are performed
using a AAM Builder’s “Common” function.
Enforcer: DCS alarm settings are read from the ExaOPC servers and
entered into the alarm database. The initial master alarm database
may be generated using the initial upload of DCS alarm settings, and
rationalization or management of change performed on the master
alarm database. The AAM then enforces the alarm settings in the
master alarm database into the DCS.
Report: Alarm and event messages from the ExaOPC servers and
ESD OPC servers are collected and stored in the AAM database.
AAM Client AAM Client operation allows the AAM to interact with the plant workflow
processes and to be fully integrated with daily standard operating
practices.
Client operations allow client users to manage implemented alarm and
AST operation, referring to alarm adviser for assistance, and generate
AAM operational reports. Other functions including user switching, on-
demand enforcement can also be performed with AAM.
AAM Statistical AAM Statistical Report enables user to view, analyze, and manageall
Report the larm and event messages collected and stored in the AAM
database.
2 How to Use This Manual

Steps to use this manual:
Step 1: Logon to AAM
Please refer to Section 4 of this manual.
Step 2: Use of Individual AAM Functions
Yokogawa AAM user manual is based on the following functional hierarchy. Users may refer to the
respective manual for details:
AAM Builder
AAM Builder AAM Enforcer AST Builder
Tag Monitor
Shift/Enforce
ment PC
Audit Trail
Viewing
AAM Report Configuration
On-demand
Request
Common User Security
System
Configuration
Function
Block
Uploading
Tag Hierarchy

AAM Statistical Reporting
AAM Sys Configured Alarm

Statistical Configurati
Report- on Alarm Setting Change
Home Monthly KPI
KPI
Operation Cal Mode Listing
Statistics Digital Output Changes
Ope/Sys Time to Ack & Respond
Response
Mode Changes L T Alarm Rate
PID
Statistics SP Intervention Count Alarm Peaks
SP Intervention Range Frequent Alarms
MV Intervention Count Correlated Alarms

Alarm Floods Count
System
Statistics Alarm Floods Duration
Events and Events Viewer Chattering Alarm

Audits
Audits Viewer Stale Alarm Count
Stale Alarm Status

Suppressed Alarm Status
Suppressed Alarm Count
AAM Client
Implemented AST
AAM Client Daily
Operation
AST Operation
Alarm Advisor
Report
Actions Switch User
On-demand Enforcement

3 Key Concepts and Terminologies
3.1 Terms and Definitions
This section serves as the ‘dictionary’ for the many AAM-related phrases and words used unsparingly in
upcoming sections and chapters to describe AAM Enforcer.
Terms Descriptions/Definitions
AAM Advanced Alarm Management
AAM Enforcer To enforce alarm settings in the master alarm database into the DCS.
DCS setting are read from the OPC servers and entered into the alarm
database. The initial master alarm database may be generated using
the initial upload of DCS alarm settings, and rationalization or
management of change performed on the master alarm database.
Additional Tag info “Additional Tag Info” refers to the following informational items
attached to each AST tag:
o Tag Comment;
o SH;
o SL
o ENGUNIT
o Alarm Priority
o Safety Critical
o Equipment ID
o Source Doc
o MOC#
o Highest Computed Priority
Alarm acknowledgement Time for operator to acknowledge alarm after the alarm is activated.
threshold
Alarm Advisory Messages “Alarm Advisory Messages” refers to the informational items attached
to each AST tag on a per alarm-limit-parameter basis for advisory
purpose. The alarm advisory message may include:
1) Purpose
Purpose of this alarm (the hazard or process condition that the alarm
intended to detect)
2) Consequence
Consequence of this alarm.
3) Actions to Verify
Actions the operator should take to verify the process condition.
4) Actions to Correct
Actions the operator should take to correct the process condition.
5) Severity
Severity of the consequences in safety, environmental, and economic
terms associated with the alarm. Possible values are ‘High
Consequence’, ‘Medium Consequence’, ‘Low Consequence’.
6) Response Speed
Time required for the corrective actions to be performed and to have
the desired effect in response to the alarm. Possible values are ‘<15
minutes’, ’15-45 minutes’, ‘>45 minutes’.
7) Computed Priority
Priority of Alarm computed based on selections of “Severity” and
“Response Speed”. The Priority Computation table is as illustrated
below:
Severity
High Medium Low
Response

< 15 mins 1 1 2
15 – 45 mins 1 2 3
> 45 mins 2 2 3
Alarm limits Refers to the alarm threshold parameters of an AST/DCS tag. For
AAM software, the followings are supported:
HH : High High alarm limit
PH : Process High alarm limit
PL : Process Low alarm limit
LL : Low Low alarm limit
DL : Deviation Limit
VL : Velocity Limit
Alarm priority Alarm Priority value (‘1. High’, ‘2.Medium’, ‘3.Low’)
Alarm rate Total alarms counted over a specified period

Alarm response speed Refer to “Alarm Advisory Messages”
Alarm return threshold Time for operator to return alarm to normal operation condition after
alarm is activated.
Alarm setting Refers to the alarm limits (including “HH”, “PH”, “PL”, “LL”, “DL”, “VL”
threshold parameters) and AOFS setting of an AST/DCS tag.
Alarm setting template Refer to” AST”

Alarm suppression An alarm is suppressed when logical criteria are applied to determine
that the alarm should not occur, even though the base alarm
conditions (eg. Alarm setting exceeded) is present.
AOFS Alarm On/Off Status setting. Refers to the “AOFS” parameter of an
AST/DCS tag. An alarm can be disabled by setting “AOFS” to “AOF”
value, or enabled by setting “AOFS” to “AON”.
Applying AST “Applying AST” means sending the “Alarm Setting” for all selected tags
in the selected AST, to the DCS.
AST Alarm Settings Template. An “AST” refers to the complete information

comprising the followings:
o One “AST Header”

o One set of “Full Alarm Setting” for one or more AST tag(s)
There are 2 types of AST:
1) Master AST type (one for each area in plant hierarchy; each
AST contains all the tags covered by the area). Master ASTs are auto-
built by AAM software, and cannot be removed.
2) User-defined AST type (each AST can be configured to have

one or more tags). Since a user-defined AST contains alarm limits
and AOFS setting for a tag (or a group of related tags), it is equivalent
to saying that it is an “operation mode” for the tag(s), as some other
AAM software might have named it so.
AST Builder An AAM software function to

AST DB “AST DB” refers to the single DB comprising both the “Master AST
DB” and “User-defined AST DB”.
AST Header “AST Header” refers to the information comprising the followings:
o AST Name
o Description
o Author Name
o Unit Name
AUT Auto mode

CAS Cascade mode
Change DCS PH/PL “Change DCS PH/PL” means changing the PH/PL limit values of one
selected tag in DCS to their new values. This action is not considered
as AST-related action, and AAM does not record their changes into
Implemented Alarm DB.
Computed alarm priority Refer to “Alarm Advisory Messages”
Daily alarm rate Total alarms counted daily

DB Refers to “database”
Disable DCS Alarm(s) “Disable DCS Alarm(s)” means changing all AOFS to AOF (Alarm
OFF). This action is not considered as AST-related action, and AAM
does not record their changes into Implemented Alarm DB.
Enable DCS Alarm(s) “Enable DCS Alarm(s)” means changing the AOFS values of all
selected tags in DCS to AON (Alarm ON). This action is not
considered as AST-related action, and AAM does not record their
changes into Implemented Alarm DB.
ENGUNIT Engineering Unit
Equipment ID Equipment ID assignment
Frequent alarms Alarms frequently occurred during operation

Full alarm setting Refers to “Alarm Setting”, plus the alarm advisory messages attached
to each alarm limit of each AST tag, and the additional tag info (“SH”,
“SL”, “ENGUNIT”, etc) for each AST/DCS tag.
Plant operation experts shall provide/supply other necessary

information (alarm advisory messages) to form the “Full Alarm
Settings”.
Highest computed priority Highest Computed Priority for the AST tag
IAD Implemented Alarm DB
Implemented Alarm DB Current implemented alarm setting database.
“Implemented Alarm DB” (IAD) starts off the same as the MAD. When
a user starts to apply any user-defined AST to DCS, Implemented
Alarm DB will be updated, and will no longer be the same as MAD.
KPI Key performance index

MAD Master AST DB
Maint record Link to maintenance record--Date last checked
MAN Manual mode

Master Alarm DB Refer to “Mater AST DB”
Master AST Refer to “AST”
Master AST DB Entire set of “Master ASTs” for the AAM software is referred to as the
“Master AST DB” (MAD). From technical viewpoint, we can also use
the term “Master Alarm DB” in place of “Master AST DB”.
MOC# Management Of Change reference number
Plant Hierarchy “Plant Hierarchy” refers to the ‘tree-structure’ layout of the plant
hierarchy comprising of one plant, many areas, and many units.
Safety Critical Designation of whether alarm instrument is safety critical
SH Scale High value for process value
SL Scale Low value for process value
Source Doc Path information to source document
Suspending Tag’s Alarm Every tag in Implemented Alarm DB has two attached parameters:
Setting Enforcement “SuspendFrom” and “SuspendTo”. By default, these parameters are
empty; which means that the tag is subjected to alarm setting

enforcement at shift-change, periodic, or in on-demand enforcement
request.
“Suspending Tag’s Alarm Setting Enforcement” means providing AAM

software with a time frame, during which this tag will NOT be checked
for inclusion in the exception tag list for alarm setting enforcement.
Tag comment Tag Description, or Annunciator Message
Tag Hierarchy “Tag Hierarchy” refers to the ‘where-about’ information of an AST tag
in plant hierarchy. The where-about information includes the
followings:
o Plant Name
o Area Name
o Unit Name
User-defined AST “User-defined AST” refers to the AST formed by using AST Builder,
based on user’s selection of tags, and other details.
Also refer to “AST”
UAD User-defined AST DB
User-defined AST DB Refers to entire set of “User-defined ASTs” for the AAM software.
UAST Refer to “User-defined AST”
3.2 Plant Hierarchy Concept
When using the AAM software, references to elements of plant hierarchy is prevalent.
The figure below illustrates the plant hierarchy as applied to Riyard Refinery. There is a single plant
(named “Riyadh Refinery”), eight areas (named “Area D”, ”Area E”, “Area G”, “Area H&I”, “Area J”,
“Area Util”, “Area WTP”, “Ccr FCS”), and there is one unit for each area.

3.3 Operation by Area
One of the key screen operation concepts in AAM software is “Area-of-responsibility”.
When a user logs in to the AAM client, the software will first determine his areas-of-responsibility. As an
example, if this operator is responsible for operating “OPC1” area, then he will be allowed to apply
alarm settings found in ASTs for “OPC1”.
3.3.1 Area and Plant Hierarchy
The figure below illustrates the relationship between “Area” and “Plant Hierarchy”:
AAM software
Plant “Riyadh Refinery”
Area Area
Area “OPC5”
“OPC1” “OPC3”
Area
Area Area
“OPC6”
“OPC2” “OPC4”
Note the following important points:
1) Areas must not overlap. This means that a DCS tag assigned to “OPC1” area cannot be
attached to another area at the same time.
2) Area name must be unique within a plant. However, this version of AAM software supports
only a single plant; so the possibility of seeing “OPC1” area in another plant other than
“Refinery” is not present.

3.3.2 Area and AST
The figure below illustrates the relationship between “Area” and “AST”:
AAM software
Area “OPC1”
AST “MAST_OPC1”
AST
“LN Mode” AST
“HN Mode”
AST
“CDU2”
AST
“AST1”
1) Every area will be automatically configured by AAM software with an “un-removable” Master
AST (named as “MAST_<areaname>”) to include all tags under <areaname> area. In above
example, “MAST_OPC1” is an AST containing all tags assigned to “OPC1” area. The tags
which are viewable in “Implemented Alarm Screen” are selected by area (the list of areas is
derived from the areas-of-responsibility of the logon user), and are therefore the same tags as
“MAST_<areaname>” AST for the selected area.
2) AST cannot cross areas. For example, it will NOT be possible to build an AST containing one
tag in “OPC1” and another from “OPC2” area. The current version of AAM software will NOT
allow user-defined AST to cross units too.

3.3.3 Area and ExaOPC Server
The figure below illustrates the relationship between “Area” and “ExaOPC”:
AAM software
ExaOPC “Server1” ExaOPC “Server2” ExaOPC “Server3”
Area Area Area

“OPC1” “OPC3” “OPC5”
(Default) (Default) (Default)
Area Area Area

“OPC2” “OPC4” “OPC6”
1) AAM software exchanges data with DCS systems using one or more ExaOPC servers.
2) Each ExaOPC server will handle tags in one or more areas.
3) Each ExaOPC server has a temporary area to serve as its “Default Area” (or “Upload Area”).
New tags defined in DCS system (yet-to-assign to plant hierarchy) shall arrive at the
default/upload area.

3.4 Security
This section covers built-in users, functions (permissive), and default security settings.
The table below summarizes the built-in users and their default security settings in the AAM software:
Screen Type Permissive AAMadmin Engineer

Administration Create AST ; ;
Edit/Save AST ; ;
Delete AST ; ;
Copy AST ; ;
Edit/Save Plant Hierarchy ; ;
Edit/Save Tag Hierarchy ; ;
Access System Audits ; ;
Edit/Save Operation Parameters ; ;
Edit/Save System Parameters ; ;
Edit/Save SECURITY Settings ;
Access Tag Monitor ; ;
Upload Tag Info ; ;
Operation Access AST ; ;
Apply AST ; ;
Apply Master AST ; ;
Access Alarm Advisor ; ;
Enable DCS Alarm ; ;
Disable DCS Alarm ; ;
Suspend Enforcement ; ;
Resume Enforcement ; ;
Change DCS PH/PL ; ;
Access Operation Reports ; ;
Change Own Password ; ;
Execute On-demand Enforcement ; ;
Areas of Responsibility * *
; Permitted Not permitted * All areas
In the above table, “AAMadmin” is the system-defined (not removable) user with full permission (not
configurable). “Engineer” is also system-defined, but his permission can be configured.

3.4.1 Setting Security for the Administration Screens
The details of “Permissive” items for Administration screen type are described as below:
Permissive Description
Specifying permission to “create AST” provides the user with the
Create AST
authority to generate new AST.
Specifying permission to “edit/save AST” provides the user with
Edit/Save AST
the authority to change contents of AST.
Specifying permission to “delete AST” provides the user with the
Delete AST
authority to remove AST.
Specifying permission to “copy AST” provides the user with the
Copy AST
authority to generate a new AST from an existing one.
Specifying permission to “edit/save plant hierarchy” provides the
Edit/Save Plant Hierarchy
user with the authority to change the plant hierarchy tree.
Specifying permission to “edit/save tag hierarchy” provides the
Edit/Save Tag Hierarchy user with the authority to assign tags to a plant hierarchy
location.
Specifying permission to “access system/admin audits” provides
Access System Audits
the user with the authority to read system audit trails.
Specifying permission to “edit/save operation parameters”
Edit/Save Operation Parameters provides the user with the authority to configure operation
parameters such as shifts and enforcement.
Specifying permission to “edit/save system parameters” provides
the user with the authority to configure system parameters such
Edit/Save System Parameters
as ExaOPC server’s details and Oracle DB housekeeping
configurations.
Specifying permission to “edit/save security settings” provides
Edit/Save Security Settings the user with the authority to add/remove user and configure his
permissions.
Specifying permission to “Access Tag Monitor” will allow the
Access Tag Monitor user to be notified when a new tag has been detected by the
system
Specifying permission to “Upload Tag Info” provides the user
Upload Tag Info with the authority to upload a new tag into the list of available
tags in the system.

3.4.2 Setting Security for the Operation Screens
The details of “Permissive” items for Operation screen type are described as below:
Permissive Description
Specifying permission to “access AST” provides the user with
Access AST
the authority to access AST listing and AST details.
Specifying permission to “apply AST” provides the user with the
Apply AST
authority to send alarm settings of UAST tags to DCS.
Specifying permission to “apply AST” provides the user with the
Apply Master AST
authority to send alarm settings of Master AST tags to DCS.
Specifying permission to “access alarm advisor” provides the
Access Alarm Advisor user with the authority to search for tags to display their full
alarm settings.
Specifying permission to “enable DCS alarm” provides the user
Enable DCS Alarm
with the authority to send AON requests to DCS tags.
Specifying permission to “disable DCS alarm” provides the user
Disable DCS Alarm
with the authority to send AOF requests to DCS tags.
Specifying permission to “suspend enforcement” provides the
Suspend Enforcement user with the authority to specify date/time range for suspension
of alarm setting enforcement for selected tags.
Specifying permission to “resume enforcement” provides the
Resume Enforcement user with the authority to specify removal of alarm setting
enforcement suspension for selected tags.
Specifying permission to “change DCS PH/PL” provides the user
Change DCS PH/PL
with the authority to send PH/PL change requests to DCS.
Specifying permission to “access operation reports” provides the
Access Operation Reports
user with the authority to view and print reports
Specifying permission to “execute on-demand enforcement”
Execute On-demand Enforcement provides the user with the authority to perform an on-demand
enforcement
Specifying permission to “change own password” provides the
Change Own Password
user with the authority to change his/her own password
Specifying the areas of responsibility provides the user with the
authority to access ASTs and tags covered by the areas. The “*”
Areas of Responsibility string is used to specify all areas. For operator in general, this
string can be “OPC1”, or “OPC1,OPC2”, etc. where multiple
areas are separated by comma.

3.4.3 Default User
A default user can be defined on each client PC. If a default user is defined, the login screen will be
skipped when the AAM Client Application is started. The AAM Client Application will be launched
immediately with the default user as the login user. This default user must be defined in the AAM
database as well as the Windows Registry. The required entries in the Window Registry are as follows:
Registry location: HKEY_LOCAL_MACHINE Æ Software Æ yokogawa Æ AAM

Registry entries: AAMDefaultUserName
AAMDefaultUserPassword
AAMTimeOutMins
The AAMDefaultUserName defines the user name to log in by default.
The AAMDefaultUserPassword is the password for the default user. Any change of password for this
user must be updated here.
The AAMTimeOutMins defines the number of minutes allowed for other users to use the AAM on this
PC.

4 AAM Builder User Manual

4.1 Screen Layout for AAM Builder
4.1.1 General Layout
The figure below illustrates the general layout of the AAM Builder:
In general, you need to use either “pull-down main menu”, “tool bar”, or “side bar” to display the
AAM builder function in the “main display area” to start using the AAM builder.

4.1.2 Screen Hierarchy
The figure below illustrates the screen hierarchy or screen organization of the AAM Builder:
AAM Builder
Common
User Security
System Configuration
Function Block
Uploading
Tag Hierarchy
AAM-Enforcer
AST Builder
Tag Monitor
Shift / Enforcement PC
Audit Trail Viewing
AAM-Report
Configuration
On-Demand Request

4.2 Logon to AAM Builder
To execute AAM Builder function, logon on as user with “AAM Builder” access privilege. User
without “AAM Builder” access privilege will be denied access to AAM Builder.
Step 1: Enter user name and password.
Note: The logon user shall have AAM Builder access rights to logon. Otherwise the access
request will be denied.
Step 2: Press button to logon.
For more on details on the user security setting, go to “User Security” for details.
4.3 AAM-Common Module
The AAM Builder software has the following functions for AAM-Common module:
1. User Security
• Manage user security configuration
2. System Configuration:
• Configure (i.e. add/edit/delete) an ExaOPC server, and manage database
housekeeping configuration
3. Function Block:
• Manage function block types registration
4. Uploading:
• Upload (read and update) alarm configuration database
5. Tag Hierarchy:
• Build plant and tag hierarchy

4.3.1 User Security
The figure below summarizes the screen flow and key functionalities of Security Configuration
Screen:
User security setting can be configured with AAM Common function, assigning respective
permissive items or rights for each type of user account.
4.3.1.1 View Individual User Security Setting
There are two default users, namely “AAMadmin” and “Engineer”, created by AAM which can not
be deleted from the system. Additional users can be created using “Add a new user” function.
Access rights are displayed in the right pane of the screen for each selected user, as illustrated
below.

Please refer to “Add a new user” to how to create a new user account.
4.3.1.2 Add a new user
This is to create a new user account. Below is the illustration of creating a new user account.
Step 1: Click Add button , a “Add User” window pop-up as below:

Note: This function is only accessible to logon user with “Change Own Password” OR
“Edit/Save SECURITY Setting” access rights.
Step 2: Enter the new user name as illustrated above.
Step 3: User description can be added.
Note: The Description field can be left blank.
Step 4: Enter password for the newly created user.
Step 5: Confirm password.
Step 6: Check to grant this new user access rights as below. Uncheck to deny access rights.
Step 7: Assign Areas of Responsibility. Click the “Area of Responsibility” dropdown list as
below. Select the Area for the newly created user and click the Area Add button.
Note1: “*” means all areas.

Note2: A comma separated string of areas will be formed if more than one area is
selected.
Note3: Click “Clear” button to remove all areas.
Step 8: Click “OK” to save user configuration.
4.3.1.3 Edit user security setting
User security setting can be edited using “Edit” insert “edit button” function, depending on the
access privileges assigned to the logon user. General steps are described as below:
Step 1: Select the name of the user for which security setting needs to be edited. A “Edit User”
window will pop-up.

Step 2: User Name and Description can be edited if needed.
Step 3: New set of password can also be created, if the user has the privilege of “Change Own
Password” OR “Edit/Save SECURITY Settings”.
Step 4: Check or Uncheck each permissive item to edit security setting.
Step 5: Click “Areas of Responsibility” dropdown list to edit the area of responsibility.
Note: To delist area(s) the user is responsible for, press “clear” button to empty
the selected area field first before selecting new Areas of Responsibility.
Note: To assign more Area of Responsibility to the user, selected the areas from the
droplist and click button to confirm.
PAGE - 27
ND
IM 052006-A01 2 EDITION ISSUE 22 MAY 2006
Step 6: Click “OK” if Edit User is completed.
4.3.1.4 Copy user
AAM also allows a new user account to be created using “Copy” function. General steps are
described as below:
Step 1: Select the User Name that will be copied.
Step 2: Press copy button.
Step 3: A dialog box will popup.
Click “Ok” to proceed, or press “Cancel” button to abort.
Step 4: A new account will be created, with the SAME security setting as the original user
selected.
Step 5: If any security setting for the newly created user need to be edited, refer to step “Edit user
security setting” for details.

4.3.1.5 Delete user
A user can be removed from the currently system user list, using “Delete” function. General steps
are as below:
Step 1: Select the user that needs to be removed.
Step 2: Press “Delete” button .
Step 3: A dialog box will pop up. Press Ok to proceed to delete the selected user, or
press “Cancel” to cancel deleting user.
Step 4: The user will be deleted if OK is pressed.
4.3.2 System Configuration
Two functions can be achieved with System Configuration under AAM Builder:
• OPC Server configuration;
• Database Housekeeping configuration.
Please refer to the below for details.
To access System Configuration, logon to AAM Builder using user account with “AAM Builder”
access rights. Screen and key functionalities of “System Configuration” will be as below:

4.3.2.1 OPC Server configuration
4.3.2.1.1 Add a new OPC Server
Step 1: Press Add button , to popup the “Add OPC Server” dialogue box.
Step 2: Enter “Server Name” and “XX PROGID” information for new OPC server. Click “OK” to
confirm.
Step 3: A new OPC Server has been added.
4.3.2.1.2 Delete a OPC Server
Step 1: Select an OPC Server, by clicking on one of the selection boxes at the left side of “OPC
Server” data grid.

Step 2: Use “Delete” button to delete the selected OPC Server. A dialogue box will appear.
Note: If no OPC server has been selected, the following dialog box will be displayed.
Step 3: Confirm deletion by pressing “OK” button.
Step 4: Selected OPC server will be deleted.
4.3.2.1.3 Edit a OPC Server
Step 1: Select a OPC Server to be edited.
Step 2: Press “Edit” button to pop-up the “Edit OPC Server” dialog box.

Note: Only one server can be selected at one time for editing. If no server or more than
one server has been selected, pressing “Edit” will pop up a dialogue box as below.
Step 3: Update “Server Name” and “XX PROGID” information, and click “OK” to confirm.
Step 4: OPC Server configuration editing is completed.
4.3.2.1.4 Refresh OPC Server List
Using “Refresh” to refresh the OPC Server list.
Below a OPC Server list before being refreshed, for example.
Below a OPC Server list after being refreshed.
4.3.2.2 Database Housekeeping Configuration
This function is only accessible to a logon user with “Edit/Save System Parameters” access right.
Below is the window frame of Database Housekeeping Configuration:

4.3.2.2.1 Edit Database Housekeeping Configuration
Step 1: Press Edit button to pop up a dialogue box as below:
Step 2: Enter the number of days to keep data for the respective tables, and click OK to confirm
the editing.
4.3.3 Function Block
The screen below summarizes the screen flow and key functionalities of “Function Block” tab of
AAM Builder.

4.3.3.1 Add more function block types
To add more function block types to registered list, follow the guiding steps below:
Step 1: Use “Add” Button to pop-up the “Add Function Blocks” dialog box as below:

Step 2: Use the check box next to Function Block column in data grid to individually select function
block types for registration with AAM Historian.
Step 3: Use “Selection String” textbox together with “select” and “unselect” buttons for “Bulk select”
or “Bulk unselect” function.
Step 4: Press OK to complete the function block registration.
4.3.3.2 Delete function block types
To delete function block types, follow the guiding steps as below:
Step 1: Select the function block type to be deleted.
Step 2: Press delete button to pop-up a dialogue box as below:

Step 3: Press “OK” button to proceed with deleting the function block. Press “Cancel” button to
terminate deleting the function block.
4.3.4 Uploading
The figure below shows the “Uploading” tab of AAM Builder.
Key operations for “Uploading” tab are summarized as follows:
4.3.4.1 Connect to a OPC server by following the guiding steps below:
Step 1: Select an OPC server (together with its PROGID) using the dropdown list box for the “OPC
Server” input field.
“DA PROGID” information is automatically retrieved with the selected “OPC Server” based on
configuration already done in “Configure” tab.
Step 2: Enter “Number of Retries” parameter for handling unsuccessful requests to OPC Server.

Step 3: Enter “Delay between Requests” parameter for slowing down of continuous stream of
requests to OPC Server.
Step 4: Click on the “Connect” button.
Upon successful connection, status bar will displayed “<station> connected” message. The
“Disconnect” button will be enabled, to allow you to cut the connection to ExaOPC server.
Upon unsuccessful OPC server connection, an error message box will appear as below:
4.3.4.2 Disconnect to a OPC server

To disconnect AAM from OPC server, follow the steps below:
Step 1: Select the OPC Server name.
Step 2: Press “Disconnect” button.
Upon successful disconnection, status bar will displayed “<station> disconnected” message. The
“Connect” button will be enabled, to allow you to make the connection to ExaOPC server.
4.3.4.3 Read from OPC Server and Update AAM
AAM enable user to read tag and update alarm configuration from OPC server in three optional
ways:
• From all FCS stations, or
• From one specific FCS station, or
• From selected tags.
4.3.4.3.1 Read tag and update alarm configuration from ALL OPC Server and Update AAM
To read from ALL connected OPC Server and Update AAM, follow the steps as below:
Step 1: Click on the “All Stations” radio button. Then click on “Read” button

You will be asked to confirm your choice of uploading from all FCSs covered by the
connected OPC server, as illustrated by the figure below:
Step 2: Click on the “OK” button.
Upon completion of uploading, status bar will display “Successfully uploaded

<number> tags” message. The above “Completion of Upload” dialog box will be
displayed for user acknowledgement. Click on “OK” to acknowledge upload
completion.
Step 3: Click on the “Update AAM” button to update configuration database.
4.3.4.3.2 Read tag & alarm configurations for one FCS.
To read tag and alarm configuration from on FCS, follow the guiding steps as below:
Step 1: Click on the “One Station” radio button. Then Select a FCS using the dropdownlist
box for the “FCS Station Name” input field.
Step 2: Click on the “Read” button.


completion.
4.3.4.3.3 Read tag & alarm configurations for selected tags.
To read tag and alarm configuration for selected tags, follow the uiding steps as elow:
Step 1: Click on the “Tags Selected by User” radio button. Then Select a FCS using the
dropdownlist box for the “FCS Station Name” input field.
Step 2: Click on the “Browse” button.
Step 3: Click on checkboxes next to tag name individually, or use text selection string
together with “Select”/”Unselect” buttons. End selection with “OK” button.

Step 4: Click on the “Read” button.

completion.

4.3.5 Tag Hierarchy
All plant tags can be organized based on a tag hierarchy using AAM Tag Hierarchy function.
Illustrated below is the window frame of the Tag Hierarchy:
4.3.5.1 Edit Plant/Area
4.3.5.1.1 Edit Plant

To edit plant information, follow the guiding steps as below:
Step 1: Select the plant to be edited
Step 2: Press Edit button and a dialogue box will display as below:
Step 3: Edit Plant Name and Description.
Step 4: Complete Plant Editing by pressing “OK” button. Press “Cancel” to terminate Plant editing.
4.3.5.1.2 Add, Edit and Delete Area
Plant Area can be added, edited or deleted by AAM Builder, following the guiding steps below:
• Add Area
Select or highlight the plant name

Press Add button to pop-up “Add Area” dialogue box as below:
Enter Area Name, Description (can not be blank), and OPC Server. Press “OK” to
proceed or Press “Cancel” to terminate the Add Area function.
A new Area has been successfully created.

• Edit Area
Select Area to be edited.
Press Edit button to pop-up Edit Area dialogue box as below:

Update Area Name, Description, etc if required.
Press “OK” to proceed editing or “Cancel” to terminate the editing.
Area is successfully edited.

• Delete Area
Select Area to be deleted.
Press delete button to pop-up Remove Area dialogue box as below:
Press “OK” to proceed or “Cancel” to terminate the area removing.

Area is successfully removed.
Note: If the area to be removed is attached with Units, it can not removed and an
error message will be displayed as below:
4.3.5.1.3 Add, Edit and Delete Unit
• Add Unit
Select the Area where unit is to be added.

Press “Add” button to pop-up Add Unit dialogue box.
Enter Unit Name and Description. Press “OK” to proceed or “Cancel” to cancel
adding a new unit.
A new unit will be created.

• Edit Unit
Select the Unit to be edited.
Press Edit button to pop-up a Edit Unit dialogue box as below:

Update the Unit Name or Description information.
Press “OK” to proceed or “Cancel” to terminate the editing.

Unit editing completed.
• Delete a Unit

Select the Unit to be deleted
Press Delete button to pop-up the Remove Unit dialogue box.
Press “OK” to proceed if the selected unit is confirmed to be removed. Or Press

“Cancel” deleting the unit.
Unit will be deleted.

4.3.5.1.4 Tag Hierarchy Builder
The figure below summarizes the screen flow and key functionalities of Tag Hierarchy Builder pop-
up screen:
Key operations for Tag Hierarchy Builder are summarized as below:
■ Select a unit in Plant\Area hierarchy window. Area and unit information will appear on top
of the tag download area.
Area and unit information will appear on top of the tag download area.
■ Select the FCS station name. Information of all tags from the selected FCS station will be
displayed as below.

Note: If “*” instead of a specific FCS station has been selected, all tags assigned to the
Unit will be displayed.
■ Users can use tag movement buttons as below to move tags between tag upload area
where all available tags for building tag hierarchy are listed and tag download area for tag
hierarchy configuration.
Note: when move tags from “Available tags for building tag hierarchy” area to tag hierarchy
building area or download area, the tag will be automatically assigned to the specific FCS
stations.
■ To remove unwanted tags from the Upload Area, follow the steps as below:
o Select the tag(s) to be deleted from tag upload area.

o Press Delete button to pop-up a “Delete Tags” dialogue box as below:
o Click “OK” to proceed.
4.4 AAM-Enforcer
AAM Builder software has the following operational functions for AAM Enforcer module:
• AST Builder
• Tag Monitor
• Shift/Enforcement PC
• Audit Trail Viewing
4.4.1 AST Builder
The figure below summarizes the screen flow and key functionalities of AST Builder by using
tab, from menu bar, or press the “AST Builder” icon

.

Key operations for AST Builder are details as below.
4.4.1.1 Select an AST

Select an AST by using the “Area” dropdown list to choose the area of interest.
A master AST for this specific area and other user-defined ASTs will be displayed as below. Select
the specific AST and all tags under the specific AST will be displayed as below.

4.4.1.2 Create a user-defined AST (UAST)
To create a new user-defined AST, follow the steps below:
Step 1: Click “Add” button to pop up a “Add AST” dialogue box as below. Enter information in
the areas of AST Name, Author, and Description.
Note 1: All areas MUST be filled and can not be left blank.
Note 2: Default name of “Author” is the logon user with “Access Builder” rights. Entered
name of the use must have same User Security level.

Step 2: Select Unit name from “Unit” area dropdown list.
Note: All tags for the newly created AST MUST from same unit in AAM Enforcer function.
Step 3: Select tags from “Available tags” area to be added to the newly created AST, as shown
above.
Note: User can also use a tag selection filter and click “Show selected one” to
select/unselect tags.
Step 4: Use following buttons to Add, Add All, Remove, Remove All tags between “AST Tag list”
and “Available Tag” list:
Step 5: Press “OK” to proceed and a new AST is created.
4.4.1.3 Edit a user-defined AST (UAST)
AAM Builder allows user to edit user-defined AST following the steps below, with “Edit” function
tool:
Step 1: Select the user defined AST to be edited.

Step 2: Click “Edit” button to pop up the “Edit AST” dialogue box. Update all AST necessary
information.
Note: Master AST is system-defined and not editable. If Master AST is selected and click
“Edit” button, an error message will display as below:
Note: To update Tag information, please refer to the section Create a User-Defined AST
for details.
Step 3: Click “OK” to proceed and the selected AST editing is completed.

4.4.1.4 Copy a user-defined AST (UAST)
To create a new user-defined AST, AAM Builder also allow users to use “Copy” function as
described below:
Step 1: Select the AST to be copied.
Step 2: Click “Copy” button to pop up a “Copy AST” dialogue box as below. Enter reasons in
“Reason” area.
Note: “Reason” area must be filled and can not be left blank.
Note: Master AST can not be copied. If Master AST has been selected and click a “Copy”
button , an error message will be prompted as below:

Step 3: Click “OK” to proceed and a new AST has been created which is copied from an existing
AST with identical Tag list.
Step 4: To edit the newly created AST by using “Copy” tool, refer to section “Edit a user-
defined AST” described before.
4.4.1.5 Delete a user-defined AST (UAST)
To delete a user-defined AST (USAT), following the steps below:
Step 1: Select the USAT to be deleted.
Step 2: Click “Delete” button and a “Delete AST” dialogue box will appear as below. Enter
reason for the deletion in “Reason” Area.
Note: “Reason” area must be filled and can not be left blank.
Note: Master AST can not be deleted. If Master AST has been selected and click “Delete”
button, an error message will be displayed as below:

Step 3: Click “OK” to proceed with the deletion of selected AST. The selected AST is deleted.
4.4.1.6 Show/Edit Tag Alarm Settings
With AAM Enforcer, each tag alarm setting can be viewed and edited. Guiding steps are details
below:
4.4.1.6.1 Show Tag Alarm Settings
To view tag alarm setting of a specific AST:
Step 1: Under “AST Builder”, select Area using “AST Selector”, and AST from the AST list. All tags
assigned to the AST (including both master AST and user-defined AST) will be displayed in the
AST Viewer Area.

Step 2: Check the “Check/Uncheck” box to select tags, or use “Unit” or “Tag” filter as
below to select tags to view alarm settings.
Step 3: Click “Show Alarm Settings” button and “Alarm Setting Display”
window will display as below and contains information including:
• Area;
• Unit;
• Equipment ID;
• Source Doc;
• Tag Name;
• Tag Comment;
• Safety Critical Classifications;
• Maintenance Record;
• Alarms limits including SH, SL, HH, LL, PH, PL, DL, VL;
• Additional alarm message including Engineering unit, Alarm priority, highest
computed priority, MOC#, Alarm inhibition status;
• Other advisory messages including Purpose of the limit setting, severity of the
consequences associated with the alarm, response speed required for corrective
action to be performed and to have desired effect, etc.

Please refer to Key Concepts and Terminologies for details on the above information used
in this document.
Note: Alarm setting is not editable with “Show Alarm Settings” function.
Note: If more than one (1) tag have been selected to view alarm setting, user can click
“Pre” or “Next” to view the alarm setting of previous or next tag.
4.4.1.6.2 Edit Tag Alarm Settings
To Edit tag alarm setting of a specific AST:
Step 1: Under “AST Builder”, select Area using “AST Selector”, and AST from the AST list. All tags
assigned to the AST (including both master AST and user-defined AST) will be displayed in the
AST Viewer Area.
Step 2: Check the “Check/Uncheck” box to select tags, or use “Unit” or “Tag” filter to select tags to
view alarm settings.
Step 3: Click “Edit Alarm Settings” button and “Alarm Setting Editor” window
will display as below with same information as displayed by “Show Alarm Settings”.
Note: If more than one (1) tag have been selected to view alarm setting, user can click
“Pre” or “Next” to view the alarm setting of previous or next tag.

Note: The information field displayed by “Alarm Setting Editor” window may have two
types of backgrounds, light green colored or white colored.
Light green colored fields are not editable.
White colored fields are editable.
Step 4: Update alarm settings.
Update alarm setting if required. However, not all fields are editable. Below is a list for
editing reference
• Area: Not editable.

• AST name: Not editable.
• Unit: Not editable.
• Equipment ID: Editable. Optional.
• Source Doc: Editable. Optional.
• Tag Name: Not editable.
• Tag Comments: Not editable.
• Safety Critical: Editable
• Maint Record: Editable. Optional
• SH: Not Editable.
• SL: Not Editable.
• Engunit: Not Editable.
• Alarm Priority: Not Editable.
• Highest Computed Priority: Not Editable.
• Alarm on/off Setting: Editable.
• HH: Editable.
• PH: Editable.
• PL: Editable.
• LL: Editable
• DL: Editable
• VL: Editable.
• MOC#: Not Editable.
For each limit setting:

• Modified: Not Editable. Most recent modification time displayed.

• Computed priority: Not editable. Computed based on severity and response speed
factors.
Computed priority of the alarm is determined by Severity and Response Speed as

below:
Computed Priority of Alarm
Response Speed
>45 mins 15-45 mins <15 mins
Severity Low 3 (low) 3 (low) 2 (medium)
Medium 2 (medium) 2 (medium) 1 (high)
High 2 (medium) 1 (high) 1 (high)
Note: After selecting Severity and Response Speed from respective dropdown list
as below, Computed Priority will automatically determined by AAM based on the
above table “Computed Priority of Alarm”.
• Severity: Editable. To select from dropdown list.

• Response speed: Editable. To select from drop down list.
• Purpose: Editable. Optional
• Consequence: Editable. Optional.
• Actions to verify: Editable. Optional.
• Actions to correct: Editable. Optional.
• Reserved. : Reserved field. Not for use.
Please refer to Key Concepts and Terminologies for details on the above information used
in this document.
Note: To view alarm setting editing history, go to Builder\AAM Enforcer\Audit Trail Viewing.
Step 5: Click “Close” button if all tag alarm setting have been updated. “Undo” and
“Save” button will appear on the right-bottom corner of the “Alarm Setting Editor”.

Note: To ignore the edited alarm setting, click “Undo” button to exit.
Step 5: Click “Save” button to proceed. A “Save Alarm Setting” dialogue box will appear. Enter
“MOC Ref” and “Reason” for this editing.
Step 6: Click “OK” button to proceed to save the updated alarm setting. Or click “Cancel” to exit.
The updated Tag alarm setting is reflected in the “AST Viewer” area as below.

Step 7: Enable/Disable “MOC#” and “Reason” memory feature
AAM allows user to Remember Last MOC# Used and Remember Last Reason Given when
executing “Save Alarm Setting” as mentioned in Step 5 above.
This feature will automatically display the last MOC# used and Reason Given in the respective
“MOC #” area and “Reason” area.
AAM Builder user can either enable or disable these two settings.
Step 8: Action feature
AAM allows user to take following Actions for all tags assigned to a specific user-defined AST,
including:
• Set All Tags to “Alarm Enabled”: This is to enable ALL AST tags “Alarm on/off Setting” to
“Alarm Enabled” mode. Steps are as below:
o Click “Set All Tags to “Alarm Enabled” “ tab, a “Save Alarm Setting” dialogue box
will popup as below:

o Enter the “MOC Ref” and “Reason” in respective areas.

o Click “OK” to proceed, or “Cancel” to abort this setting.
Note: The new settings only apply to all tags assigned to the selected AST.
• Set All Tags to “Alarm Disabled”: This is to enable ALL AST tags “Alarm on/off Setting” to
“Alarm Disabled” mode. Steps are as below:
o Click “Select All Tags to “Alarm Disabled” to pop up a “Save Alarm Setting”
dialogue box.
o Enter the “MOC Ref” and “Reason” in respective areas.

o Click “OK” to proceed, or “Cancel” to abort this setting.
Note: The new settings only apply to all tags assigned to the selected AST.
• Import Advisory Messages: This is to allow Advisory Messages in CSV format to be

imported to AAM alarm data base, instead of using “Editing Alarm Setting” function for
Advisory Message editing. Steps are as below:
o Click “Import Advisory Messages” to pop up a “Import Advisory Messages”
dialogue box.
o Specify the CSV file name and location.

o Click “Open” to proceed, or “Cancel” to abort this setting.
• Import Alarm Settings: This is to allow Alarm setting in CSV format to be imported to AAM
alarm data base, instead of using “Editing Alarm Setting” function for Alarm Setting editing.
Steps are as below:
o Click “Import Alarm Setting” to pop up a “Import Alarm Settings” dialogue box.


• Export Advisory Messages: This is to allow Advisory Messages in CSV format to be

exported for other usage, eg, message editing. Steps are as below:
o Click “Export Advisory Messages” to pop up a “Export Advisory Messages”
dialogue box.


• Export Alarm Settings: This is to allow Alarm setting in CSV format to be exported for other
usages, et, alarm setting editing. Steps are as below:
o Click “Export Alarm Settings” to pop up a “Export Alarm Setting” dialogue box.

4.4.2 Tag Monitor
Tag Monitor function allows AAM Builder user to monitor additional tags or changes made to tags,
take necessary steps to update AAM alarm data base.
The figure below summarizes the screen flow and key functionalities of Tag Monitor by using tab
from menu bar, or press the “Tag Monitor” icon. The tag monitor screen is illustrated as below:
The screen consists of two parts, one is “New Tag” Window in the left column, and the right colun
is for “Changed Tags”.
4.4.2.1 “New Tags” Window Frame
1. Use “OPC Server” selector to view new tag(s) from specific OPC Server, as illustrated
below:
2. Read a new tag by following the steps below:

Select a new tag, by clicking on one of the selection boxes at the left side of “New
Tags” data grid.
Click on “Read” button to pop-up the “New Tag” dialog box showing the actual tag
information read from DCS. If the AAM is not able to read the values of the changed
tag, it is probably deleted.
If no tag, or more than one tag, is selected when “Read” button is clicked, the following
dialog box will be displayed:

3. Upload a new tag by following the steps below:
Tags” data grid.
Click on “Upload” button to pop-up the “Uploading New Tag” dialog box showing the
actual tag information read from DCS, and pausing for a confirmation.
Click on “Confirm” button to proceed to upload this tag into “Upload Area” of the
selected OPC Server. An uploaded tag will appear in the “Upload Area” in “Tag
Hierarchy” screen.
If no tag, or more than one tag, is selected when “Upload” button is clicked, the
following dialog box will be displayed:
4. Ignore a new tag by following the steps below:
Tags” data grid.
Click on “Ignore” button to pop-up the “Delete One Tag” dialog box showing the actual
tag information read from DCS, and pausing for a confirmation.
Click on “Confirm” button to proceed to delete this tag from “Tags to be confirmed”
data grid. The deleted tag and its subsequent events will not be displayed.

4.4.2.2 “Changed Tags” Window Frame
1. Read a changed tag by following the steps below:
Select a to-be-confirmed tag, by clicking on one of the selection boxes at the left side
of “Tags to be confirmed” data grid.
Click on “Read” button to pop-up the “Tag Changed” dialog box showing the actual tag
information read from DCS. If the AAM is not able to read the values of the changed
tag, it is probably deleted.
If no tag, or more than one tag, is selected when “Read” button is clicked, the following
dialog box will be displayed:

2. Update a changed tag by following the steps below:
Click on “Update” button to pop-up the “Changed Tag” dialog box showing the actual
Click on “Update Value” button to proceed to update this tag information into the
database.
3. Ignore a changed tag by following the steps below:
Click on “Ignore” button to pop-up the “Delete One Tag” dialog box showing the actual
Click on “Confirm” button to proceed to delete this tag from “Tags to be confirmed”
data grid. The deleted tag and its subsequent events will not be displayed.

4.4.3 Shift/Enforcement PC
Enforcement Application by AAM software is to enforce alarm settings from implemented alarm
database to DCS settings. This configuration is on a per AAM Client PC basis (each of which can
have an area of responsibility based on plant hierarchy) and the enforcement can be made at a
pre-set time or shift.
Below is a Shift/Enforcement PC window:
4.4.3.1 Shift Configuration
Shift can be configured based on the actual plant operation. To edit, follow the steps below:
• In Shift Configuration window below,
click “Edit” button . A “Shift Configurator” dialogue box will display as below:

Note: Default time of Start Time is the current time.
• Update shift information as requested. Click “OK” to proceed with shift configuration, or
click “Cancel” to abort the configuration.
• Upon clicking “OK” button, the shift details will be updated as below:
4.4.3.2 Enforcement Configuration
With AAM, alarm setting can be enforced in a pre-configured arrangement. Below is a

“Enforcement Configuration” window, which is only accessible to users with AAM Builder access
rights.
AAM allows enforcement configuration to be edited, created, and deleted. These buttons can be
found in the Enforcement Configuration window area.
These key functionalities are described as below.
• Add Enforcement PC
A new enforcement client PC can be created following steps below:

o Click “Add” button . A “Add Enforcement PC” dialogue box will display as below:

o Enter the information below:

Client PC Name: The client PC to be used for alarm setting enforcement;
Area of Enforcement: select from a dropdown list to assign an area of
responsibility to the client PC;
Enforcement Mode: select from a dropdown list, manual or full.
Note: In Full-Enforcement mode, the Enforcement Application enforces

alarm settings from Implemented Alarm DB at shift-change, and at
configurable periods, without seeking prior consents from the operator-in-
charge. For example, at these scheduled timings, a client PC covering an
area will automatically pick up alarm settings of exception tags in the
covered area, and make write requests for these settings to DCS system.
An exception tag is one in which its DCS alarm setting is different from its
setting in Implemented Alarm DB.
In manual-enforcement mode, the “enforcement application” screen will

pop up at scheduled timings if there are exception tags at that time. This
same screen will also be displayed when “on-demand” enforcement is
activated from the AAM Client Application.
Countdown Timer: The countdown timer mechanism will allow enforcement

will be aborted if countdown expires. This does not apply to Full-enforcement
mode.
Enable Shift Enforcement: check or uncheck to select enable/disable shift

enforcement.
Enable Periodic Enforcement: check or uncheck to select enable/disable

periodic enforcement.
Starting time and Intervals: If Enable Periodic Enforcement is checked, user

can specify the enforcement starting time and intervals.
Click “OK” button to proceed. Click “Cancel” button to abort the addition of an
enforcement PC.
o An Enforcement PC is added if “OK” is clicked in the previous step.

• Edit Existing Enforcement PC
Existing enforcement PC can be re-configured using Edit function. Following the steps below
to edit the enforcement PC:
o Select the enforcement PC to be edited.
o Click “Edit” button . A “Edit Enforcement PC” window will display as below.
Update information as required.
o Click “OK” button to proceed with editing, or click “Cancel” to cancel editing.
o Editing completed if “OK” is clicked. The edited information will be updated in the
“Enforcement Configuration” window as below:

• Delete An Enforcement PC
Enforcement PC can be deleted following the steps below:
o Select a PC to be deleted.
o Click “Delete” button . A “Delete Enforcement PC” will be displayed as below:
o Click “OK” to proceed, or click “Cancel” to abort deletion of the selected PC.
o The selected enforcement PC will be deleted if “OK” is clicked in the previous step.
The “Enforcement Configuration” window will be updated as below:
4.4.4 Audit Trail Viewing
Audit Trail Viewing function allows AAM Builder user to view audit and trial all modifications made
to alarm documentation.
The figure below summarizes the key functionalities of Audit Trail Viewing.

Steps are listed below to operate Audit Trail Viewing:
Step 1: Logon to AAM Builder as user with AAM Builder access rights. AAM Enforce\Audit Trail
Viewing window can be displayed by using Audit Trail Viewing panel toolbar as below
or by clicking action bar in side bar area, or by clicking “Audit Trail Viewing” icon
.
A “AAM Enforcer\Audit Trail Viewing” window will display as below:

Step 2: Use “Audit Report Selector” to select reports to be audited.
Selections can be performed based on the following selecting criteria:

• Area: Default setting “*”, which means all areas;
• Category: 4 categories can be selected, ie. IAD, AST, Enforcement, and
Hierarchy. Default setting is “*”, which means all categories.
• Period “From” and “To”: in days. Default setting is current time.
o Upon clicking “From”, a calendar will appear for user to choose a date.
o Upon clicking “To”, a calendar will appear for user to choose a date.
Step 3: Click “Go” button and a report will be generated as below.

User can also use the filter provided as below to make report filtration.
User name and/or Details can be entered in “User” area or “Details” area. Click button to
retrieve audit report and a report window will display as below:
4.5 AAM Report
AAM Builder software has the following functions for AAM Report module:
• Configuration:
o System Default Parameters
o AAM Priority
o KPI Target
• On-demand Request

4.5.1 Configuration
AAM Report Configuration allows AAM Builder user to manage system default parameters, AAM
priority, and KPI target. Key functions are summarized as below:
4.5.1.1 System Defaul Parameters
Below is the list of system default parameter and respective values, units, and descriptions.
As shown above, the System Default Parameters consist of the following:
• 10_MIN_RATE_THERESHOLD: Default 10 minute slice alarm rate threshold;

• ACK_LIMIT: default interval threshold for ACK event
• CHATTER_INTERVAL: default chatter interval;
• CHATTER_THRESHOLD: default chatter alarm count threshold;
• CORRELATED_INTERVAL: default correlated alarm interval;
• CORRELATED_THRESHOL_C_REPEAT: default child repeat count threshold
• CORRELATED_THRESHOLD_RATIO: default percentage ratio of chile-repeat
over parent-repeat threshold;
• DAILY_RATE_THRESHOLD: default daily (24 hours) alarm rate threshold;
• DATE_STR_FORMAT: default format for displaying date on report;
• DEFAULT_SEARCH_PERIOD: default search period for Suppressed Alarm status
and Calibration Mode report
• FLOOD_INTERNAL: default flood interval;
• FLOOD_THRESHOLD_X: default alarm count for Flood condition threshold X;

• FLOOD_THRESHOLD_Y: default alarm count for Flood condition threshold Y;

• MAX_ROWS: default max rows returned by data base to web applicaton;
• PEAK_TIME_SLICE: default timeslice for peak alarm report;
• RTN_LIMIT: default interval threshold for RTN event
• STALE_ALARM_SEARCH_LIMIT: default search alarm for stale alarm status
report;
• STALE_INTERVAL: default stale interval;
• TOP_N_LIMIT: default top N ranking for Frequent alarm report.
The values entered as shown above will serve as default parameters for generating the Monthly
KPI Report. They will also be used when no value or inappropriate values are entered by the user
on the web interfaces.
The system default parameters can also be edited if necessary. To edit, select the parameters to
be edited, click “Edit” button . A “System Default Parameters” window will be displayed as
below:
Default value will be shown with blue background. To change, enter the new value in “Value” area.
Click “Ok” button to proceed with the value change. Or click “Cancel” to abort the editing.
The Default System Parameter will be updated as below:
4.5.1.2 AAM Priority
DCS Tag Priority can be mapped to user defined AHR Alarm Priority. A DCS Tag Priority\AHR
Alarm window is displayed as below:
To edit the Alarm Priority Mapping, select the Priority to be edited. Click “Edit” button and a
Alarm Priority Mapping window will display as below:
Enter new AAM Alarm Priority level to be assigned the corresponding DCS Tag Priority, click “OK”
button to proceed. Or click “Cancel” to terminating the priority editing.
Upon clicking “OK” button, the new AHR Alarm Priority setting will be updated and displayed as
below.
4.5.1.3 KPI Target
KPI Target can be set and edited with AAM Report, as shown below:

AAM consists of 5 KPIs and the details are listed below:
• 10_MIN_ALARM_RATE: number of 10 minutes slices where alarm count exceeded “X”

alarms.
• CHATTER_ALARM: total number of chattering alarms based on Tag condition_name.
• DAILY_ALARM_RATE: number of days where daily total alarms exceeded “X” alarms per
day.
• STALE_ALARM: total number of stale alarms based on Tag condition_name.
• SUPPRESSED_ALARM: Total number of AOF events.
The value entered above will be displayed as KPI targets on the Monthly KPI Report.
To edit KPI Target value, select the KPI to be edited, click “Edit” button . A KPI Target window
will display as below:
Default value will be shown with blue background. To change, enter the new value in “Value” area.
Click “Ok” button to proceed with the value change. Or click “Cancel” to abort the editing.
Upon clicking “OK” button, the new KPI Target setting will be updated and displayed as below.

4.5.2 On-Demand Request
On-demand request allows user to manage on-demand/manual A&E (based on DA reads) for
AOFs, “alarm state changes” and “PID mode changes”.
Operational steps are as below:
Click “on-demand request” from side bar (function tree) or from main menu. A “AAM Builder”
dialogue box will be displayed as below:
As shown in the dialogue box, on-demand request can take a lot of minutes to process.
Click “cancel” to abort this request. Or click “Ok” to proceed, a “On-demand request” dialogue box
will be displayed as below:
Select OPC Server name from OPC server field dropdown list, and enter “delay per tag” value.
Click “cancel” to abort the request, or proceed with the request by clicking “OK”. AAM start to
reach data from DCS.


This page is blank.

AAM Manual Builder 2ed

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

AAM Manual Builder 2ed

Încărcat de

Drepturi de autor:

Formate disponibile

AAM MANUAL BUILDER R100

IM 052006-A01 2ND EDITION ISSUE 22 MAY 2006 PAGE - 1

All Rights Reserved

IM 052006-A01 2ND EDITION ISSUE 22 MAY 2006 PAGE - 2

This is the 2nd Edition of this document.

IM 052006-A01 2ND EDITION ISSUE 22 MAY 2006 PAGE - 3

AAM Document Set

The documents available for AAM are:

AAM Builder User Manual

AAM Client User Manual

AAM Statistical Report User

IM 052006-A01 2ND EDITION ISSUE 22 MAY 2006 PAGE - 4

1.1 Introduction .......................................................................................................................................................6

1.2 AAM Funcitons..................................................................................................................................................6

2 HOW TO USE THIS MANUAL................................................................................... 7

3 KEY CONCEPTS AND TERMINOLOGIES ............................................................... 9

3.2 Plant Hierarchy Concept ................................................................................................................................12

3.3 Operation by Area ...........................................................................................................................................13

4 AAM BUILDER USER MANUAL ............................................................................. 20

4.2 Logon to AAM Builder....................................................................................................................................22

4.3 AAM-Common Module ..................................................................................................................................22

4.5 AAM Report.....................................................................................................................................................82

IM 052006-A01 2ND EDITION ISSUE 22 MAY 2006 PAGE - 5

1.2 AAM Functions

AAM Function Purpose

2 How to Use This Manual

Step 1: Logon to AAM

Please refer to Section 4 of this manual.

Step 2: Use of Individual AAM Functions

AAM Builder AAM Enforcer AST Builder

AAM Report Configuration

Common User Security

IM 052006-A01 2ND EDITION ISSUE 22 MAY 2006 PAGE - 7

AAM Statistical Reporting

AAM Sys Configured Alarm

SP Intervention Range Frequent Alarms

MV Intervention Count Correlated Alarms

Events and Events Viewer Chattering Alarm

Stale Alarm Status

Suppressed Alarm Count

Actions Switch User

IM 052006-A01 2ND EDITION ISSUE 22 MAY 2006 PAGE - 8

3 Key Concepts and Terminologies

3.1 Terms and Definitions

IM 052006-A01 2ND EDITION ISSUE 22 MAY 2006 PAGE - 9

Alarm priority Alarm Priority value (‘1. High’, ‘2.Medium’, ‘3.Low’)

Alarm rate Total alarms counted over a specified period

Alarm setting template Refer to” AST”

AST Alarm Settings Template. An “AST” refers to the complete information

o One “AST Header”

There are 2 types of AST:

2) User-defined AST type (each AST can be configured to have

AST Builder An AAM software function to

AUT Auto mode

Computed alarm priority Refer to “Alarm Advisory Messages”

Daily alarm rate Total alarms counted daily

ENGUNIT Engineering Unit

Equipment ID Equipment ID assignment

Frequent alarms Alarms frequently occurred during operation

Plant operation experts shall provide/supply other necessary

KPI Key performance index

Maint record Link to maintenance record--Date last checked

MAN Manual mode