Cams

CENTUM CS 3000 & CENTUM VP ENGINEERING GUIDE
CAMS for HIS Engineering Guide
Introduction
This document explains the necessary engineering items on CENTUM system when CAMS for HIS function is
enabled. The following software revision of CENTUM system is supported in this document.
CS 3000 System ; CS 3000 R3.08.70 or later
CENTUM VP System ; CENTUM VP R4.01.60 or later
Note) The database structure of CAMS for HIS has changed significantly from R4.02, however, there are no
fundamental changes in the basic procedure for system design, alarm design and basic builder items.
Regarding R4.02 or later, please refer to both of this engineering guide and ESS-CDWG-S611-021503E.
Contents
1 Requirement Items for CAMS for HIS .................................................................................................... 3
1.1 Hardware Environment ..................................................................................................................... 3
1.2 Software Environment ...................................................................................................................... 3
1.3 Ordering CAMS for HIS Package ...................................................................................................... 3
2 Important Notes when CAMS for HIS is enabled .................................................................................... 4
3 Engineering Flow .................................................................................................................................... 8
4 System Basic Design ............................................................................................................................... 9
4.1 System Configuration ....................................................................................................................... 9
4.2 Plant Hierarchy .............................................................................................................................. 11
4.3 Security Policy............................................................................................................................... 12
4.4 Message Processing........................................................................................................................ 15
4.5 Other Engineering items on System Basic Design ............................................................................. 25
5 CAMS for HIS Alarm Design ................................................................................................................ 26
5.1 Alarm Attribute Design ................................................................................................................... 26
5.2 Alarm Group Design ...................................................................................................................... 29
5.3 Alarm Suppression Design .............................................................................................................. 29
5.4 Filter Design .................................................................................................................................. 32
5.5 Shelving Design ............................................................................................................................. 33
6 CAMS for HIS Message Monitor Design ............................................................................................... 36
6.1 Customizable items on CAMS for HIS Message monitor ................................................................... 36
6.2 Design CAMS for HIS Message Monitor ......................................................................................... 42
7 Capability of message notification processing of CAMS for HIS ........................................................... 43
7.1 Capability of message notification processing on R5.03.20 or later ..................................................... 43
7.2 Behavior at the time of alarm flooding ............................................................................................. 43
7.3 Elements which affect the capability of message notification processing ............................................. 44
7.4 Measured result .............................................................................................................................. 45
7.5 Conclusion (Engineering to ensure message notification processing) .................................................. 46
7.6 The behavior when messages are suppressed .................................................................................... 46
8 Engineering Tool................................................................................................................................... 48
8.1 Tool Launcher ................................................................................................................................ 48
8.2 Duplication Check Tool .................................................................................................................. 48
8.3 Deviation Check Tool ..................................................................................................................... 50
9 The Message from CENTUM XL and XL ........................................................................................... 52
9.1 Messages from the legacy stations supported by CAMS for HIS ........................................................ 52
9.2 View and Operate on CAMS for HIS Message Monitor ..................................................................... 52
Rev 7.0 ESS-CDWG-S611-021501E Page 1 of 84

9.3 Display on Historical Viewer of CAMS for HIS ................................................................................ 53

9.4 Action of Configurator of CAMS for HIS ........................................................................................ 53
9.5 Action of Alarm Generator .............................................................................................................. 53
9.6 HIS and CAMS for HIS Regarding Messages of Legacy Stations ....................................................... 53
10 Multiple Projects Connection ................................................................................................................ 54
10.1 Multiple Projects Connection before R4.02 ...................................................................................... 54
10.2 Multiple Projects Connection in R4.03 and later ............................................................................... 56
10.3 When upper project is R5.03.20 and lower project is before R5.03.00 ................................................. 59
11 Alarm messages received via OPC ........................................................................................................ 60
12 Upgrading CAMS for HIS .................................................................................................................... 63
12.1 Procedure of upgrading for Pattern 1 ................................................................................................ 64
Appendix1. How to define Guidance ...................................................................................................... 67
Appendix2. The operational differences between CAMS and NON-CAMS ................................................ 71
Appendix3. Sample User specification for Tokuchu DLL ........................................................................... 81
Revision History ........................................................................................................................................... 84

1 Requirement Items for CAMS for HIS
1.1 Hardware Environment

HIS to be installed CAMS for HIS shall comply with following hardware specifications.
[CS 3000 System]

* Refer to GS 33Q02N03-31E Model LHS4800 Consolidated Alarm Management Software CAMS for HIS.
CPU : Pentium 1.0GHz or higher (recommended Pentium4 2.8GHz or higher)
Main Memory : 256MB or more (recommended 512MB or more)
HDD : 24GB or more free disk space (recommended 40GB free disk space or more)
[CENTUM VP System]
* The CAMS for HIS requires the following environment. In fact, it complies with the LHS1100's environment.
Refer to GS 33K05D10-50E Model LHS1100 Standard Operation and Monitoring Function.
CPU : Core2 Duo 2.13HGz or higher, Xeon Dual Core 2.0GHz or higher
Main Memory : 2GB or more
HDD : 20GB free disk space or more (recommended: At least 40GB capacity)
(Minimum 1GB free disk space is required for Design Check function)
Note: Conditions above are not dependent on the operating system.
1.2 Software Environment

[CS 3000 System]
* Refer to GS 33Q02N03-31E Model LHS4800 Consolidated Alarm Management Software CAMS for HIS.
OS : The following OS system is supported.
Windows XP Professional SP2/SP3,
Windows Server 2003 Standard Edition SP1/SP2,
Windows Server 2003 Standard Edition R2/R2 SP2, Windows 2000 SP4
Microsoft Libraries: .Net Framework version 2.0,WSH version 5.6,MSXML version 6
[CENTUM VP System]
* It complies with the LHS1100's environment.
Refer to GS 33K05D10-50E Model LHS1100 Standard Operation and Monitoring Function.
1.3 Ordering CAMS for HIS Package

[CS 3000 System]
The CAMS for HIS is an optional package for HIS. Ordering is the same way as other option packages.
[CENTUM VP System]
The CAMS for HIS function is included into the Standard Operation and Monitoring Function (LHS1100 or
LHM1101). However, before R4.02, TOKUCHU is required for CAMS for HIS. In order to get the keycode
file for CAMS for HIS, specify the suffix code (/CAMS) of LHS1100 or LHM1101 on TOKUCHU SHEET.
If the suffix code is missing, the keycode file is not arranged.
If the CAMS for HIS is required after shipping, the project needs to submit TOKUCHU SHEET to request
the Keycode file to PMK department (This is not free.). From R4.02 or later, the CAMS for HIS becomes
available if only LHS1100 or LHM1101 is ordered. (TOKUCHU is not required.)

2 Important Notes when CAMS for HIS is enabled

Refer to the following IM and Appendix2 (The operational differences between CAMS and NON-CAMS) for the
details.
[CS3000]
IM 33S01B30-01E CS 1000/CS 3000 Reference Options, M13.10 Impact on the Standard Monitoring and
Operation Function (Especially M13.10.3 Differences between the HISs with and without CAMS for HIS is
important.)
[CENTUM VP]
IM 33K03H20-50E Consolidated Alarm Management Software Reference, A6. Relationship between CAMS for
HIS and HIS (Especially A6.4 Differences between HISs with CAMS for HIS Enabled and Those with CAMS for
HIS Disabled is important.)
This chapter explains the emphasizing items and additional notes to the IM.
Operation screen mode of CAMS for HIS Message monitor

For CS3000 system, only Window mode is available for CAMS for HIS Message monitor. The CAMS for HIS
Message monitor cannot be displayed as Full screen mode even though Full screen mode has been defined in
HIS Setup window. For CENTUM VP system, the CAMS for HIS Message monitor is displayed according to
the setting of HIS Setup window.
Process Value display of the process alarm message

In case the system does not enable CAMS for HIS (Non CAMS), it is possible to display process value in a
process alarm message displayed in the Process Alarm view. In case CAMS for HIS is enabled, the process
value cannot be displayed in a process alarm message. (From R5.04, displaying a current value is available by
adding alarm attributes of "PV(Current Value)" and "ALRM(Current Value)").
There is no function of this button on the

CAMS for HIS Message monitor.
Operation Guide Message

Engineering for Opeguide and Dialog messages generated from SEBOL function isn't available in
CAMS for HIS. If a project uses opeguide or dialog messages from SEBOL, it is recommended
not to integrate the Operation Guide message view into the CAMS for HIS Message monitor.
The whole message text is always shown in one line. A line break is ignored.
Example of a dialog message with line break:
A line break and specified color will be shown in

a dialogue window.

The color of message text cannot be changed. The specified color for Operator Guide messages will be
ignored. (Only tag mark is displayed with specified color.)
The Windows calling function from Operation Guide message in CAMS for HIS Message monitor is
not available. The definition in Operation Guide builder is ignored.
The Green color messages behave differently from the messages which are defined the color other
than Green. (Green color has a meaning of NR in CENTUM.) Be careful when using Green color
for Operation guide messages.
Ex)
"TEST500" is "Green" color message.
When generated, it starts blinking just
like other color messages.
The "Green" color message disappears

by acknowledgement operation.
Blinking stops in other color messages.
Manual reset operation is required to delete the messages whose color is other than Green.
The green mark at the head of message starts blinking by Manual operation. The messages
disappear by acknowledgement operation. (When enabling "Auto Clear", only a manual reset
operation is enough to delete a message.
Mode Select Key Switch on Operation Keyboard

In R4.02 and later CAMS for HIS, the security of login user can be temporarily changed to the higher access
level (S1 -> S2,S3, S2 -> S3) by changing the key position.
Before R4.02, the security of CAMS for HIS depends on the HIS user who is logged in the HIS.
The position (OFF/ON/ENG) of the Mode Select Key Switch cannot change the access level to message
displayed on CAMS for HIS Message monitor.
To change the operation permissions for CAMS for HIS, log in again via the HISs User Login dialog box as a
different user with appropriate permissions.
(e.g)
Some of the system alarm messages cannot be deleted by S1 privilege (like OFF User).
In case of NON-CAMS, it is possible to delete these messages by changing the key position without User
Login.
In case CAMS for HIS before R4.02 is enabled, changing the key position is not available and a User
having more than S2 privilege needs to be logged in.
Alarm Status Display under Alarm inhibition

The following methods are available in CAMS for HIS to suppress alarm messages.
Enable Suppression to the message
Disable the Detection attribute of the message by CAMS for HIS
Change the alarm priority of the message to Logging/Reference priority by CAMS for HIS
In CAMS for HIS before R4.02, when a process alarm occurred in FCS, if this alarm message is suppressed,
the alarm status is not displayed on HIS operation and monitoring window. (NR is displayed as alarm status.)

(e.g.)
In case Lo alarm of TAG-A, which is set as Logging priority by CAMS for HIS Configurator, is generated,
LO alarm status is ON in FCS (Logics like ST16 can detect the alarm status.) but HIS displays the alarm
status on the faceplate of TAG-A as NR.
(Note)
There is a solution with project responsibility. Please refer to CAMS for HIS Trouble Shooting & FAQ,
2.2 When a TAG is defined as logging alarm or an alarm source of the TAG is under suppression, the TAG
keeps the NR status even though the alarm is detected in FCS.
In R4.02 and later CAMS for HIS, it is possible to display FCS alarm status on the faceplate, tuning view, etc.
even if the alarm is suppressed. Whether it displays or not is defined on the CAMS for HIS tab of the
Project Properties. Basically, this is the same behavior as NON-CAMS, however, there is a difference in the
priority of a display of alarm status.
When CAMS for HIS is enabled:

The display priority of alarm status depends on AlarmPriority which is defined in CAMS for HIS
Alarm builder.
When CAMS for HIS is disabled:

The display priority of alarm status depends on the following system-fixed order.
OOP > IOP > IOP- > HH > LL > HI > LO > DV+ > DV- > VEL+ > VEL- > MHI > MLO > CNF
(e.g.)
When enabling CAMS for HIS and defining "High" for TAG-A.HH and "Critical" for TAG-A.HI as
AlarmPriority, "HI" will be displayed on the faceplate during generating both of "HI" and "HH". When
disabling CAMS for HIS, HH will be displayed.
(Note)
In R4.02 and later CAMS for HIS, if the method described in the above-mentioned engineering guide
(CAMS for HIS Trouble Shooting & FAQ, Section 2.2) is executed, the display priority of alarm status
will be the system-fixed order.
Alarm Priority and Acknowledgement of Process Alarm message

In R4.02 and later CAMS for HIS, Lock type, Non-lock type or Self-acknowledge type is available if
CENTUM Original is selected for the alarm action on Project Properties.
In CAMS for HIS before R4.02, the alarm messages behave with the same action (equivalent action of Lock
type) regardless of the alarm priority.
(e.g.)
Even though specifying LOW alarm that the alarm flashing action is Non-Lock type by FCS drawing
builder, the alarm flashing action in CAMS becomes Lock type.
Please refer to 4.4.1.1 Alarm priority and Alarm processing table for the details.
.

Extent of the impact by acknowledgement of System alarm and Operator Guidance

messages
In case of NON-CAMS, the acknowledgment status of all HISs in an operation group will be equalized.
The same can be said for CAMS for HIS in R4.02 and later.
Before R4.02, if CAMS for HIS is enabled, the acknowledgment status of all HISs in an equalization scope will
be equalized. This version of CAMS for HIS doesn't have the conception of operation group.
Suppression of repeated alarm messages

The CAMS for HIS has a function to suppress the repeated messages automatically after displaying the first 10
messages (5 pairs of alarm/recover).
Message control
A message control in Graphic view doesnt support CAMS for HIS. Therefore, it displays maximum 200
messages even if more than 200 messages are generated. Also, the definition on CAMS for HIS Alarm builder
isnt reflected on a message control.
Display on a message control
Definition on CAMS for HIS Alarm builder
Displayed with original color.
Display on CAMS for HIS Message monitor

3 Engineering Flow
Start
Scope of this document
System Basic Design

System Configuration
Plant Hierarchy
Security Policy
Message Processing
CAMS for HIS Alarm Design
Alarm Attribute Design
Alarm Group Design
DCS/SCS Detail Design Alarm Suppression Design
FCS Functional Spec Filter Design
SCS Functional Spec Shelving Design
CAMS for HIS Message monitor Design

Generation Message Monitor Design
Creation of Function blocks

Creation of Annouciator
Creation of Operator Guides

Import Tag database

(In the case before R4.02)
CAMS Function Configuration

Functions Unit Test
Import Project DB
Control Function
Attribute Definition for each alarm
Graphic
Group Definition
Report
Shelving Definition
Etc.
Filter Definition
Download
Integration Test
Proceed to FAT

4 System Basic Design

This chapter describes the some design points to be considered in the Basic Design phase when introducing
CAMS for HIS into the CENTUM system.
Example definitions are shown in each definition items and then it may help engineers to easily understand the
design points.
4.1 System Configuration

When designing System Configuration, it needs to consider following system requirements.
It is necessary for all HISs to enable CAMS for HIS function. If some of HISs does not enable the CAMS
for HIS function in a project, the alarm status is displayed differently within HISs.
Number of HIS: Maximum 100 HIS / Project
Creating multiple equalization scopes in a project is possible. However, define one equalization scope per
a project basically. (Refer to 4.4.4.)
Number of alarms stored: Maximum 2000. (can be increased to 10000 by Tokuchu from R4.03)
From R4.03, CAMS for HIS has supported Multiple projects connection. Therefore, there are following
problems if Multiple projects connection is used for previous version CAMS for HIS.
Alarm states and/or Acknowledgement states are propagated within an equalization scope of HISs in
a same project. Different alarm states will be found among the different projects. e.g. When more
than 2 alarms are blinking on a TAG and then an alarm blinking stops by Ack operation in one
project, the alarm blinking doesnt stop in other project.
Alarm engineering should be done each project. Therefore, the same maintenance of CAMS DB
should be done each project. (e.g. When changing the alarm details of F001.HH alarm in PJT01.HH,
the same maintenance needs to be done on PJT02.
Message from CENTUM-XL and/or XL via BCV-H/-L can be displayed.
Since CENTUM-V is out of guaranty, please do not use CAMS for HIS to the system integrated
CENTUM V system.
For more detail, please refer to 8. The Message from CENTUM XL and XL.
Ethernet or Vnet/IP Bus 2 Open is mandatory for the equalizing message status and the configuration files.
Ethernet TCP/IP Setting in HIS property should be specified correctly. It is used for the equalization of
data among the HISs.
Only one HIS shall be configured as the download master HIS for maintenance and/or downloading
several kinds of configuration files per each equalization scope. And also any HIS within a CAMS
Equalization Scope can be the download master HIS. CAMS for HIS Configurator can be exclusively run
at download master HIS.
In case of CS3000 system, CAMS for HIS earlier than R3.08.50 cannot be integrated to the system using
R3.08.50 or later. When the data equalization from CAMS of the upper version to CAMS of the lower
version is executed, the lower version of CAMS suddenly stops. For more details, please refer to IM
CS3000 Installation - Cautionary Notes for Upgrading the CS 3000

The following is a sample system overview and operation requirements in this document.
Project Name: CAMSDEMO
Operation and Maintenance Group Maintence Group for a project

for a project
Engineers Group Maintenance Group

HIS0164
Operation Group Operation Group

for AREA01and Utility for AREA02 and Utility
HIS0161 HIS0162 HIS0163 HIS0150 HIS0151
FCS FCS FCS FCS FCS

0101 0102 0103 0104 0105
AREA 01 Utility AREA 02
Plant 011 Plant 012 Plant 021
Unit 11A Unit 11B Unit12A Unit UT Unit 21A Unit21B
AREA01 Supervisors Group AREA02 Operator Group
AREA01 Operator Group AREA02 Operator Group

4.2 Plant Hierarchy

A plant hierarchy refers to the various equipments used to operate the plant such as, factories, departments,
lines, unit instruments, and devices that are organized into layered architectures according to the ISA S88.01
physical model.
The plant hierarchy allows you to organize the entire plant into a layered structure (hierarchy), and thus
achieving efficient engineering, operation and monitoring.
In CAMS for HIS operation, Plant Hierarchy can be used for the alarm filtering, and also alarm segregation
(Security).
Note; The engineering of the plant hierarchy is designed in the same way as NON-CAMS. Please refer to IM
(CS3000: IM 33S01B30-01E CS 1000/CS 3000 Reference Human Interface Station, E10.Plant Hierarchy,
CENTUM VP: IM 33K03F22-50E Human Interface Stations Reference Vol.2, 3. Plant Hierarchy) for more
detail.
<<Sample Project>>
Site Area Process Cell Unit Equipment Element
CAMSDEMO
AREA01
PLANT011
UNIT011A TAG-A (PID)
UNIT011B TAG-B (PID)
PLANT012 UNIT012A TAG-C (PID)
UTILITY UNIT_UT TAG-D (PID)
AREA02
PLANT021
UNIT021A TAG-E (PID)
UNIT021B TAG-F (PID)
Plant Hierarchy Name can be used for Alarm Filtering of CAMS for HIS.

4.3 Security Policy

The HIS Security Policy and User Security Policy are utilized for the alarm segregation based on the HIS or
Login User. For example, the alarms under the operation scope of User-A appears on only the HIS of User-A
logged-in, and wont be shown on the HIS of other users.
The properly configured security policy allows operators to be released from the alarm flood.
The Security Policy of CENTUM system consists of the following three layers.
The following diagram shows an image of these security layers.
HIS Security Policy

User Security Policy
CAMS for HIS Security Policy
Alarm Display
CAMS for HIS Security Policy Process Message receiving scope of Users
Filtering by User Security based (CAMS for HIS Alarm builder ( CAMS
on alarm source for HIS Configurator in previous
version))
User Security Policy Process Message receiving scope of Users

Filtering by User Security based (System View)
on TAGs, Plant Hierarchy
HIS Security Policy Process Message receiving scope of HIS

Filtering by HIS Station based (System View)
on Plant Hierarchy, FCS
Alarm An Alarm occurs with Plant

TAG
Hierarchy name
Alarm Status

4.3.1 HIS Security
HIS security policy stipulates the scope of operation and monitoring allowed on the HIS. Regardless of the
logon users, the operation performed to a device or to a function block data item may be restricted. HIS receives
alarm messages from Plant Hierarchy or Tags within the operation and monitoring scope of the HIS.
HIS Security may be defined by the purpose of HIS or the operation and monitoring scope of the regular users.
HIS Security is used for the case the HIS needs to be limited to access regardless of log-on User and/or the case
the system doesnt use User Security policy.
If supervisory users or maintenance/engineering users use the HIS and they need to access all of plant area, HIS
security may not be used and access control may be carried out by users operation & monitoring scope (User
Security).
<<Sample Project>>
In this project, the access control is achieved by User Security policy. Therefore HIS security in the
System view shall be configured to allow assessing to all of plant.
< Security Tab of HIS Constants builder >
HIS Name Description Operation & Monitoring Process Alarm Acknowledgement

Range Receiving
HIS0150 HIS for AREA02. Operation range ALL ALL ALL
HIS0151 is limited by user security.
HIS0161 HIS for AREA01. Operation range ALL ALL ALL
HIS0162 is limited by user security.
HIS0163
HIS0164 HIS for Engineers ALL ALL ALL
4.3.2 User Security
User security policy stipulates the scope of operation and monitoring for users. Each user is restricted to operate
or monitor a certain scope of devices and function block data items. HIS receives alarm messages from Plant
Hierarchy or Tags within the operation and monitoring scope of the Login User.
User Security Definition consists of two layers, User Group Definition and User Definition. Create User Groups
and define the operation and monitoring scope based on responsibility of plant area, and make each user belong
to the appropriate user group.
<<Sample Project>>
The Plant is operated by plant area.
Users belonging to Operator Group have all privileges for own plant area operation.
Users belonging to Supervisor Group have all privileges for all plant area operation without
acknowlagment on plant area out of his scope.
Users belonging to Engineering Group and Maintenance Group have all privileges for all plant area
operation without acknowledgement on all plant area.

< User Security Builder in System View >

User Group Definition
User Group User Group Operation & Monitoring Process Alarm Receiving Acknowledgement
Name Description Range
AR01OPGR AREA01_Operators AREA01, UTILITY AREA01, UTILITY AREA01, UTILITY
AR01SVGR AREA01_Supervisors AREA01,AREA02, UTILITY AREA01,AREA02, UTILITY AREA01, UTILITY
AR02OPGR AREA02_Operators AREA02, UTILITY AREA02, UTILITY AREA02, UTILITY
AR02SVGR AREA02_Supervisors AREA01,AREA02, UTILITY AREA01,AREA02, UTILITY AREA02, UTILITY
ENGGR Engineer ALL ALL None
MNTGR Maintenance ALL ALL None
User Definition
User Name User Group Name

AR01OP001 AR01OPGR
AR01OP002 AR01OPGR
AR01SV001 AR01SVGR
AR02OP001 AR02OPGR
AR02OP002 AR02OPGR
AR02SV001 AR02SVGR
ENG001 ENGGR
MNT001 MNTGR
4.3.3 CAMS for HIS Security
Each individual alarm source like TAG-A.HH, TAG-A.LL can be assigned to users or user groups.
By these settings, a logon user can receive only alarm messages within the scope.
Monitoring Denied User or User Group is set to the individual alarm on CAMS for HIS Alarm builder (Alarm
List Tab or Alarm Group Tab of CAMS for HIS Configurator in previous version).
In case the Monitoring Denied User and/or User Group for individual alarm is not defined in CAMS for HIS
Alarm builder (Default setting), the logon user can see and acknowledge alarms according to the plant hierarchy
which is permitted by HIS and User Security Policy.
<<Sample Project>>
The followings are CAMS for HIS Security Policy on this project.
User has to monitor and acknowledge all alarm status generated from his/her responsible plant area.
Users belonging to Maintenance group can see alarm messages related to process signal (IOP/OOP)
only.
< CAMS for HIS Alarm builder (Alarm List Tab in CAMS for HIS Configurator in previous version) >
Alarm Source Monitoring Monitoring Acknowledgement Acknowledgement Denied
Denied User Denied User Group Denied User User Group
TAG-A.IOP (Blank) (Blank) (Blank) (Blank)
TAG-A.OOP (Blank) (Blank) (Blank) (Blank)
TAG-A.HH (Blank) MNTGR (Blank) MNTGR
TAG-A.LL (Blank) MNTGR (Blank) MNTGR
: : : : :

4.4 Message Processing

This section describes the necessary engineering items for message processing function when CAMS for HIS
function is enabled. The message processing notifies the changes of process and the system status to operators
by pre-defined messages.
Messages are classified as listed below depending on their origins and contents.
System Messages: System messages notify operator of system status and operation.
System alarm message is in this category.
Process Messages: Process messages notify operator of process status and operation.
Process alarm message, annunciator message, operator guide message, print message, sequence
message request, and signal event message are in this category.
Operation related messages excluding the messages mentioned above.
Messages from supervisory computers and help message are in this category.
In case CAMS for HIS is enabled, it is necessary for engineers to design Process alarm message, annouciator
message, operation guide message and system alarm message.
4.4.1 Process alarm message and Annouciator message
Messages behave in accordance with the definition on a function block or an annunciator (engineering in source
of message) unless doing engineering on CAMS for HIS Alarm builder.
There are some differences on message behavior between CAMS and NON-CAMS. Therefore please study the
differences and then design messages correctly.
4.4.1.1 Alarm priority and Alarm processing table
[Engineering in the source of messages]

Alarm processing level is defined by the same way of conventional engineering, which the alarm behavior of
each alarm priority is defined by the alarm priority builder and alarm color and priority is defined by alarm
processing table.
By setting the alarm processing level to a function block or an annouciator which is message generator, alarm
behavior from the Tag or the annouciator is determined.

For CENTUM System Basic Design, the following items need to be defined as the same way of conventional
engineering.
Display in HIS / Buzzer sound / Printing / Output to files / Repeated warning
<Alarm priority builder Defaults>
Alarm priority of Tag Display Buzzer sound Printing Output to files Alarm flashing action Repeated NR Message
or Annouciator in HIS (Note 1) Note 2 warning
High Y High alarm Y Y Lock type Yes On Alarm Dependent type
Medium Y Medium alarm Y Y Lock type -- --

Low Y Medium alarm Y Y Non-Lock type -- --
Logging N N Y Y Self-acknowledge type -- --
Reference N N N N Self-acknowledge type -- --
Note 1 Buzzer sound is set on HIS Setup window Buzzer tab.

Buzzer sound for High alarm :Tone number 24Default
Buzzer sound for Medium alarm :Tone number 30Default
Note 2 In case CAMS for HIS is enabled and Consolidated is selected for alarm action, messages behave with
Lock type regardless of alarm priority.
Alarm color and Alarm priority on each alarm source

<Alarm processing table builder>
Bit Alarm source Alarm Alarm Alarm Alarm Alarm Alarm
(PID) processing level 1 processing level 2 processing level 3 processing level 4 processing level 5 processing level 6
Color priority Color priority Color priority Color priority Color priority Color priority
7 AOF Blue High Blue Medium Blue Low Blue Logging Blue High Blue Medium
8 CAL Cyan High Cyan Medium Cyan Low Cyan Logging Cyan High Cyan Medium
9 NR Green High Green Medium Green Low Green Logging Green High Green Medium
10 OOP Red High Red Medium Red Low Red Logging Red High Red Medium
11 IOP Red High Red Medium Red Low Red Logging Red High Red Medium
12 IOP- Red High Red Medium Red Low Red Logging Red High Red Medium
13 HH Red High Red Medium Red Low Red Logging Red High Red Medium
14 LL Red High Red Medium Red Low Red Logging Red High Red Medium
15 Red High Red Medium Red Low Red Logging Red High Red Medium
16 Red High Red Medium Red Low Red Logging Red High Red Medium
17 HI Red High Red Medium Red Low Red Logging Red Medium Red Low
18 LO Red High Red Medium Red Low Red Logging Red Medium Red Low
19 Red High Red Medium Red Low Red Logging Red Medium Red Low
20 Red High Red Medium Red Low Red Logging Red Medium Red Low
21 DV+ Yellow High Yellow Medium Yellow Low Yellow Logging Yellow Medium Yellow Low
22 DV- Yellow High Yellow Medium Yellow Low Yellow Logging Yellow Medium Yellow Low
: : : : : : : : : : : : : :
Regarding Alarm priority builder and Alarm processing builder, refer to IM (CS3000: IM 33S01B30-01E CS
1000/CS 3000 Reference Function Block Details, C5.15 Classification of Alarm Actions Based on Alarm
Priority and C5.16 Alarm Processing Levels CENTUM VP: IM 33K03E21-50E Function Blocks
Overview, 5.15 Classification of Alarm Actions Based on Alarm Priority and 5.16 Alarm Processing
Levels ) for more detail.
<<Sample Project>>
Use the default setting of Alarm priority builder.
Add two alarm processing tables (5 and 6) as user customization.
Alarm processing table 5: IOP/OOP/HH/LL are High alarm, the lower than HI/LO are Medium.
Alarm processing table 6: IOP/OOP/HH/LL are Medium alarm, the lower than HI/LO are Low.

[CAMS for HIS Engineering]

Particular alarm priority in CAMS can be defined to an alarm source by CAMS for HIS Alarm builder (CAMS
for HIS Configurator in previous version). CAMS priority is used for filtering function, sorting function and
shelving function of CAMS for HIS Message monitor and then it helps operators to monitor alarms efficiently.
Alarm priority in CAMS: Critical/High/Medium/Low/Logging/Reference/(None)
Even though CAMS alarm priority is set, the definition on Alarm priority builder depends on the alarm
level defined on a function block or annunciator (except the messages defined Logging/Reference by
CAMS). In other word, since the alarm blinking action, the repeated warning and so on are followed the alarm
level of TAG and annouciator, the conventional engineering is required.
In CAMS for HIS before R4.02, the alarm blinking behavior is always Lock type regardless of alarm
processing level. An alarm source defined as the Logging alarm priority in CAMS behaves Logging alarm
priority regardless alarm level of TAG and Annunciator.
In R4.02 and later CAMS for HIS, Lock type, Non-lock type or Self-acknowledge type is available depending
on the alarm level of TAG and Annunciator if CENTUM Original is selected for the alarm action on Project
Properties.
The following table shows alarm processing behavior in CAMS for HIS.
- Before R4.02
CAMS Priority Display Buzzer sound Printing Output to file Repeated Alarm flashing
in HIS warning behavior
Critical * * * * * Lock type
High * * * * * Lock type
Medium * * * * * Lock type
Low * * * * * Lock type
Logging N N Y Y N N
(None) * * * * * Lock type
*: Alarm action depends on alarm level of TAG or annunciator.

e.g. 1 Condition 1: Alarm processing level of LL alarm of TAG-B in control drawing builder: High
Condition 2: Repeated warning for High alarm: Yes
Condition 3: Alarm priority of TAG-B.LL in CAMS Configurator: Low
When LL alarm of TAG-B is generated;
Action 1: Display/ Sound/ Printing/ File: High alarm action defined in alarm priority builder
Action 2: Repeated warning: LL alarm is re-generated after predefined minutes
Action 3: Alarm flashing behavior: Lock type
e.g. 2 Condition 1: Alarm priority of LO alarm of TAG-C in control drawing builder: Low (User alarm level)
Condition 2: Alarm priority of TAG-C.LO in CAMS Configurator: Critical
When LO alarm of TAG-C is generated;
Action 1: Display/ Sound/ Printing/ File: Low alarm action defined in alarm priority builder
Action 2: Alarm flashing behavior: Lock type
e.g. 3 Condition 1: Alarm processing level of TAG-D in control drawing builder: Medium
Condition 2: Alarm priority of TAG-D.LO in CAMS Configurator: Logging
When LO alarm of TAG-D is generated;
Action 1: Display/ Sound/ Printing/ File: No Display/ No Sound/ Yes/ Yes
Action 2: Alarm flashing behavior: No
- R4.02 and later
CAMS Priority Display Buzzer sound Printing Output to file Repeated Alarm flashing
in HIS warning behavior
Critical * High Priority * * * *(Lock type in the case of
Consolidated)
High * High Priority * * * *(Lock type in the case of
Consolidated)
Medium * Medium Priority * * * *(Lock type in the case of
Consolidated)
Low * Medium Priority * * * *(Lock type in the case of
Consolidated)
Logging N N Y Y N N
Reference N N N N N N
(None) * * * * * *(Lock type in the case of
Consolidated)
*: Alarm action depends on alarm level of TAG or annunciator.
From R4.02, the buzzer sound (Yes/No, tone) depends on the alarm priority defined by CAMS for HIS.

<<Sample Project>>
The following table shows the policy of alarm priority and alarm processing table in this project.
Priority of Priority in Assignment philosophy Display Buzzer Printing Output Repeated Alarm
Tag or ANN CAMS in HIS Sound to file warning flashing
High Critical Alarms which need immediate Y Y Y Y Y Lock
operator action, huge consequence
will be given if operator does not
respond. Critical priority shall be
defined to the specific alarm by
CAMS configuration.
High Tags which need immediate operator Y Y Y Y Y Lock

action.
Medium Medium All other DCS tags which do not Y Y Y Y N Lock

need immediate operator action.
Low Low To be defined by user for giving Y Y Y Y N Lock

Information to operator.
Logging Logging To be defined by user for logging N N Y Y N N

Reference N N
Priority of Tag is defined by the Tag detail builder of the control drawing builder.
Priority of ANN is defined by the Annouciator builder
Priority in CAMS is defined by CAMS for HIS Alarm builder (Alarm Detail tab or Alarm List tab in
CAMS for HIS Configurator in previous version).
Buzzer sound setting is as follows.
Buzzer sound for High alarm :Tone number 24Default
Buzzer sound for Medium alarm :Tone number 30Default

4.4.1.2 Recover Message
If it is NON-CAMS or CENTUM Original is selected for CAMS for HIS with R4.02 and later, the recover
message of process alarm is generated according to alarm flashing action defined in the alarm priority builder.
Lock type:
When an acknowledged alarm is recovered, a recover message of the alarm is not generated.
When a non-acknowledged alarm is recovered, a recover message of the alarm is generated.
Non-Lock type:
When an alarm is recovered, a recover message of the alarm is not generated regardless
acknowledgement status.
Self-acknowledge type
When an alarm is recovered, a recover message of the alarm is not generated because the alarm is
always acknowledged.
When previous version CAMS for HIS has been enabled or "Consolidated" has been selected for CAMS for
HIS with R4.02 and later, a recover message of alarm is generated regardless of alarm flashing action defined.
The recover message appears with blinking and then acknowledgement to the recover message is required. If
an operator doesnt like to acknowledge the recover message to acknowledged alarm, define AUTO
CLEAR alarm attribute of the alarm in CAMS for HIS Alarm builder (CAMS for HIS Configurator in
previous version). This setting makes the alarm to do the same behavior of Lock type in NON-CAMS.
<<Sample Project>>
AUTO Clear alarm attribute is enabled to all alarm sources.
<CAMS for HIS Alarm builder (CAMS for HIS Configurator Alarm List in previous version)>
Alarm Source Priority Auto Clear
TAG-A.IOP High Enable
TAG-A.HH Critical Enable
: : :
4.4.1.3 NR Message
When the statuses of all alarms in one function block return to normal (NR), flashing starts to notify the
operator of the status change. The actions can be designated only for high priority alarms. The actions when
alarm recovers to normal include two types, On Alarm Dependent type and Notification at Return type.
This setting is done by Alarm Priority Builder.
In case CAMS for HIS is enabled and Notification at Return type is selected, NR message is displayed even
though the alarm is suppressed. The reason why CAMS for HIS cannot handle the NR message correctly
because the NR message is generated based on TAG not an alarm source.
(e.g.1) The alarm is not displayed under suppression condition, but NR message of the TAG appears.
(e.g.2) When an alarm source is shelved into Continuous Shelf, the alarm including the recover message is
automatically shelved into the shelf, but NR message of the TAG is displayed.
Therefore, in case CAMS for HIS is enabled, select On Alarm Dependent type for NR message action. In
this case, NR message is not displayed under any condition.
<<Sample Project>>
NR message action is On Alarm Dependent type in this project.

4.4.2 Operator Guide Message
4.4.2.1 Integration of Operator Guide view
The CAMS for HIS Message monitor supersedes the standard HIS windows (Process alarm view, System alarm
view and Operator Guide view).
It is selectable to integrate Operator Guide view with CAMS for HIS Message monitor. We recommend not
integrating Operator Guide with CAMS for HIS Message monitor in case of Batch system because CAMS for
HIS Message monitor does not support Batch ID filtering (it has been supported from R4.03) and
opeguide/dialogue message from SEBOL. The setting for not integrating Operator Guide with CAMS for HIS
Message monitor can be done on HIS Utility window. (All Opeguide messages are displayed on the
conventional Opeguide view.)
<<Sample Project>>
This project isnt for Batch plant and also doesnt use dialogue message from SEBOL. Therefore
Operator Guide view is integrated into CAMS for HIS Message monitor.
4.4.2.2 Alarm Priority
Alarm priority for an operation guide message can be set as well as one of a process alarm message by CAMS
for HIS Alarm builder (CAMS for HIS Configurator in previous version). In case of an operation guide
message, there is no need to consider the alarm processing table.
Setting alarm priority helps for operator to manage the messages efficiently by the filtering function and/or
shelving function.
Please note that the color setting to an operation guide message in the operation guide builder is affected to the
TAG mark but not message contents.
<<Sample Project>>
The table below shows engineering policy for Operation Guide Message.
Category of Operation Guide Message Alarm Priority Color

Messages which need immediate operator action, huge Critical Red
consequence will be given if operator does not respond.
Critical priority shall be defined to the specific messages
by CAMS configuration.
Important message High Pink
Messages other than category above. Medium Blue
Buzzer Sound is as follows.
Operator Guide Buzzer sound :Tone number 18Default

4.4.3 System Alarm Message
The system without CAMS for HIS does not have priority level for system alarms. All system alarms and
messages are displayed in the system alarm window with the same priority level.
However, CAMS for HIS enables to assign different alarm priority level for each system alarm. If necessary,
review system alarms and assign alarm priority to system alarms.
Please be noted the following important points
Since the system alarm regards the message number as a key (source), the engineering of the alarm
definition of each output source station cannot be done.
The alarm source is a message number but not alarm message contents
There is the same message number but the different sentence.
e.g. 0303 FCSxxxx Fail (FCS number is depend on the failed station.)
0891 {Text message from option packages}
The system alarms whose default priority is "HIGH" can be assigned an alarm priority. The table
below shows system messages having HIGH priority as default. If an alarm priority is defined for
the system alarms whose default priority is LOW or "Logging, these settings are ignored. (To
overwrite "Low" by "Logging" or "Reference" not to display messages is possible.)
Message No Message Description Alarm Priority Buzzer Sound Severity

00XX Odd FCS Error Generation and Recovery High System Alarm 900
Even Messages Low None
01XX Odd Control Station Messages of Other High System Alarm 900
Even Systems (not CS FCS) Low None
02XX Odd HIS System Status Messages High System Alarm 900
Even Low None
03XX Odd Communication Related Messages High System Alarm 900
Even (Control bus status information) Low None
04XX * Control Station Status Change Related Logging None 200
Messages
05XX Odd Operation Command and Operation Low Operator Guide 300
Even Record Messages Logging None
06XX * Logging None 200
07XX Odd FCS Related Messages High System Alarm 900
Even Low None
08XX Odd HIS Peripherals Messages High System Alarm 900
Even Low None
4XXX Odd Control Station Related Messages High System Alarm 900
Even (CS 1000/ CS 3000) Low None
Buzzer sound setting can be done in HIS Setup window.
System Alarm :Tone Number 36Default
In case of System Alarm, the following engineering information is not reflected.
Do not write in these attribute boxes in CAMS for HIS Alarm builder (CAMS for HIS Configurator in previous
version).
Alarm group, Monitoring Denied User/User group, Acknowledgement Denied User/User group,
Manual Reset Permitted User/User group, Manual Reset Denied User/User group, Auto Clear, Tag
mark color
<<Sample Project>>
There is no change to system alarm messages in this project.

4.4.4 Equalization Scope
In case CAMS for HIS is enabled, the following information is equalized with in HISs belonging to the
equalization scope by the CAMS for HIS special function.
Alarm & event message though OPC A&E function
Alarm acknowledgement
Suppressed Alarm status (Suppression, Shelving)
When restarting HIS, the following information is equalized from another HIS in the same equalization scope.
CAMS Database
Historical data
Messages on CAMS for HIS Message monitor
The equalization scope is determined by selecting HISs being in the same scope at [Detailed Setting] in
CAMS for HIS tab of HIS Utility window.
3) Acknowledgement of HI is
2) Acknowledge HIat HIS #3
equalized to HIS #1 & #2 4) Acknowledgement of HI is NOT
equalized to other equalization groups.
HIS #1 HIS #2 HIS #3 HIS #4 HIS #5

Equalization Scope A Equalization Scope B
1) Process alarm TAG001.HI and HH arise
FCS
Please be noted the followings.

In previous version CAMS for HIS (before R4.02), the acknowledgement and deletion to Operation
Guide message & System alarm message is equalized to all HISs within the same equalization scope.
Therefore Operation Group ID is ignored.
Basically, one project has one equalization scope. It is possible to divide more than two equalization scopes but
please be noted the followings.
The Download Master station is required every equalization scope. It means that the engineering on
CAMS for HIS Configurator is required for each equalization scope.
Acknowledgement to a process alarm is equalized within an equalization scope.
(e.g.) TAG-A is monitored from the equalization scope A & B (ES-A, ES-B), and then both HH alarm
and HI alarm of TAG-A are generated and flashing on HIS.
When HH alarm is acknowledged by HIS in ES-A, HH alarm flashing action stops on HIS in ES-A.
However the acknowledgement is NOT equalized to ES-B, so HH alarm on HIS in ES-B is continued
flashing. After acknowledged HI alarm by HIS in ES-A, all alarms of the TAG are acknowledged, so
CAMS for HIS function of HIS in ES-A sends the acknowledgement message to the TAG in FCS. The
result of the message sending, HIS in ES-B knows the acknowledgement status of the TAG and forces
to stop flashing of the alarms.
Before R4.02, Acknowledgement and Deletion to Operation Guide message & System alarm message
is equalized to all HISs within the same equalization scope. This is similar to the conventional
Operation Group ID function.
In addition, the Buzzer Ack ID is not related to CAMS for HIS. Buzzer ACK ID can be used as it is.

The definition of the equalization scope is required for every HIS in the project. Please confirm the Detail
Setting on CAMS for HIS tab in HIS Utility for every HIS when a HIS is added or removed
(Note)
After R5.03.20, an ExaOPC server station (R3.72.00 or later) can be included into a equalization scope. By this,
messages received by CAMS for HIS will be transferred to an upper computer accurately and quickly.
<<Sample Project>>
All HISs are in the same equalization scope.

4.5 Other Engineering items on System Basic Design
4.5.1 Download master HIS
Decide the Download Master HIS for alarm configuration. Only one Download Master should be set within the
Equalization Scope.
On a download master HIS, check a box of Set this HIS as Download Master on CAMS for HIS tab of HIS
Utility. On the other HISs, uncheck the checkbox of it.
Only the download master can start the CAMS for HIS Configurator.
A download master is responsible for competitive management among HISs when something has changed in
CAMS for HIS Message monitor. The downloading from CAMS builders in SystemView isn't related to the
existence of download master.
<<Sample project>>
ENGHIS is Download Master HIS.
4.5.2 Maximum size of alarm buffer
Define the maximum number of alarms to be held in CAMS for HIS. A desired number can be set as a multiple
of 100, between 100 and 2000. The default is 2000. From R4.03, this number can be increased up to 10000 by
Tokuchu.
There is the configuration area in CAMS for HIS tab of HIS Utility function on each HIS.
Be sure to set the same number for all HISs in the same equalization scope.
Messages suppressed by CAMS for HIS aren't counted. Please refer to section 7.6 for the details.
<<Sample project>>
Use default value: 2000
4.5.3 The action of ACK Key on Operation Keyboard
Decide the action of ACK key on the operation keyboard for acknowledgement of message shown in CAMS for
HIS Message monitor.
There is the configuration area in CAMS for HIS tab of HIS Utility function on all HISs.
ACK key acknowledges the selected A&E message:
If you want to acknowledge only the selected A&E messages, click this radio button on.
ACK key acknowledges all the displayed A&E messages:
If you want to acknowledge all the shown A&E messages at once, click this radio button on.
<<Sample Project>>
ACK key acknowledges the selected A&E message

5 CAMS for HIS Alarm Design

This chapter describes the engineering points on the alarm design to the CAMS for HIS function.
Example definitions are shown in each definition items and then it may help engineers to easily understand the
design points.
5.1 Alarm Attribute Design

Use of the alarm attribute helps operator to manage alarms efficiency and to reduce operators load.
The followings are sample usages of alarm attributes.
Make it easier to recognize the contents of alarm message by the alarm attribute
Sort the alarm list on A&E Message monitor by the alarm attribute.
Use the alarm attribute for the filter condition.
Use the alarm attribute for the shelving condition.
The alarm attribute can be set on CAMS for HIS Alarm builder (Alarm Detail tab or Alarm List tab of
CAMS for HIS Configurator in previous version).
Each alarm handled by CAMS for HIS has various types of system pre-defined attributes and their values (e.g.
Time stamp, Plant hierarchy name) are set according to the system built-in rule.
If the pre-defined attributes are not enough to the required specification, it is possible to define extra attributes
and those values.
5.1.1 Default attribute of alarm message
The CAMS for HIS provides the useful attributes as the system default for the alarm management.
E.g. AlarmPriority, Consequence (the scale of impact on the system if no appropriate step is taken for the alarm)
and so on.
Additional information to IM is described in this section.
Detection
Alarm source selected Disable in this item is not displayed even though the alarm is detected on FCS.
When Blank is set to this item, it is taken as Enable.
AlarmPriority
Alarm priority except Logging is handled as comment in effect and does not override alarm processing level
of the function block or annouciator in FCS. (See 4.4.1.1 Alarm priority and Alarm processing table for more
details)
Alarm priority can be used for sorting condition or filter condition of A&E Message monitor.
User
User information being set in this item is handled as comment.
It doesnt mean that only User defined in this item has a right to monitor the alarm source.
Auto Clear
Auto Clear Enable setting is to automatically clear both the acknowledged alarm and the recover message
when the alarm is recovered.
In case of Disable setting (or blank), an acknowledgement operation is required to acknowledge the recover
message because the recover message is generated with flashing when the alarm is recovered.
If the project requires the acknowledge operation same as the conventional operation, please set Enable into
this item.

In R4.02 and later CAMS for HIS, this setting for process alarm is available only when the Consolidated is
selected for the alarm action.
The following table shows the relation between the Auto Clear setting and its action.
Setting
Alarm Type Project Properties: CAMS Alarm builder: Auto Clear Action
Alarm Action Auto Clear Setting
(Setting disabled) Comply with the definition on the
CENTUM Original:
alarm priority builder.
Enable Automatic clear
Process Alarm
Consolidated or Disable No automatic clear
before R4.02 (NONE) No automatic clear (Alterable by
Tokuchu)
Enable Automatic clear
Disable No automatic clear
Operator Guide Message (Setting disabled)
(NONE) No automatic clear (Alterable by
Tokuchu)
Manual Reset Permitted User (User Group) and Manual Reset Denied User (User Group)
The manual reset is the function that deletes the acknowledged messages not having a recovery message
(operator guide messages or some of system alarms). The user more than S2 is usually allowed to do manual
reset. If the S1 user is defined in Manual Reset Permitted User, the manual reset can be done by the S1 user.
The definition in Manual Reset Denied User (User Group) is prior to one in Manual Reset Permitted User (User
Group).
(e.g.) When Group1 is defined as Manual Reset Permitted User Group and User A in Group1 is defined as
Manual Reset Denied User, Users in Group1 except User A can reset manually.
Alarm Group
Only one alarm group defined in Alarm Group builder can be set to each alarm source.
In other words, an alarm source cannot belong to multiple alarm groups. Alarm Group can be used for Alarm
Suppression.
Guidance
Define the contents to be displayed in Detail pain of CAMS for HIS Message monitor. The content is normally
the causes and actions for each alarm source. You can also provide a separate file describing the causes and
actions and specify that file.
According to Style definition in Tool menu of CAMS for HIS Configurator, the effectiveness of the definition
in this item is decided.
Guidance : Character string typed in Guidance column, Link Address, The contents of text
file name typed in Guidance column Note 1
Specify Alarm Attribute : Character string typed in Guidance column
All Alarm Attributes : Character string typed in Guidance column

(Note 1) Text files are stored into [CENTUM install folder]CAMSdatabasehttppost folder by clicking
[File] in the menu bar - [Import] - [External File]. After importing external files into CAMS for HIS
Configurator, download them to HISs by Download operation. When Editable is selected in Style setting,
the contents of the text file can be edited from CAMS for HIS Message monitor.
Refer to Appendix1 for the procedure of defining the Guidance.
Invalid attribute
In CAMS for HIS before R4.02, the following attributes in CAMS for HIS Configurator are invalid. Dont
specify the value.
Monitoring Permitted User / User Group
Acknowledgement Permitted User / User Group
Alarm Sub-State Change Permitted User / User Group
Alarm Sub-State Change Denied User / User Group
5.1.2 User attribute of alarm message
A user can add attributes on CAMS for HIS Alarm builder (Alarm list of CAMS for HIS Configurator by right
clicking the mouse in previous version).
User attributes are displayed in A&E Message pane, and are used for a condition of filter and so on.
The notes on User attribute are;
The number of User attribute : less than 50 (This is the limitation from R4.02)
Name of User attribute : uppercase and lowercase alphabets, period (.) and numbers.
The first character must be an alphabet.
Length is less than 50 characters. (This is the limitation from R4.02)
<<Sample Project>>
The alarm attributes in the table below are shown in A&E Message pane.
Customer needs to decide the detail value of each attribute for alarm except Time Stamp and
Message.
Display Column name Meaning Description In charge

order
1 TimeStamp Message timestamp Example: 2008/07/14 10:00:05 Auto
2 Message Message Text Example: Auto
NZPID1 Tag Comment PV = 0.0 LO
3 AlarmPriority Alarm Priority Critical/High/Medium/Low/Logging Customer
*Logging message isnt displayed.
4 Purpose Purpose of the A&E message Safety/Environment/Financial Customer
5 Consequence Predicted consequence in case the A&E Very Large/Large/Medium/Small Customer
message is ignored
6 Time-to-respond Reaction for the alarm Urgent/Quick/Routine Customer
7 Guidance Cause and solution regarding String text or Text file Customer
the A&E message *File name is alarm source name.txt
8 Start-up (User attribute) Alarm to be out of scope at Start-up : 1 Customer
Out of scope for Monitor at Start-up
9 Shutdown (User attribute) Alarm to be out of scope at Shutdown : 1 Customer
Out of scope for Monitor at Shutdown

5.2 Alarm Group Design

By grouping alarm sources, Suppression function (suppress unnecessary A&E message) by a group can be
executed. And it is also possible to acknowledge or reset all messages in a same alarm group when an
operator acknowledges or resets an alarm message in it. (Apply to All)
Monitoring Permitted User (User group) can be defined to the alarm group instead of each alarm source.
(Note)
- When using Apply to All, it may affect the performance of CAMS for HIS because CAMS server
receives a lot of ACK at the same timing, etc. The number of alarm groups and the number of messages in
an alarm group should be kept to a minimum.
- The default value of Apply to All is;
Before R5.03.20: Enable
After R5.03.20: Disable
<<Sample Project>>
Alarm Suppression function is executed by Unit operation.
Acknowledgement and Reset operation is done for alarm source.
Monitoring Denied User is set by alarm source. (See CAMS Security section
Users can start the Alarm Suppression function for Units that they are monitoring.
< CAMS for HIS Alarm builder (CAMS for HIS Configurator Alarm Group Definition tab in previous version)>
Alarm Group Apply to Monitoring Monitoring Alarm Group Sub-State Alarm Group Sub-State
Name All Denied User Denied User Change Permitted User Change Permitted User Group
Group
UNIT011A Disable None None None AREA01OPGR,AREA01SVGR,ENGGR
UNIT011B Disable None None None AREA01OPGR,AREA01SVGR,ENGGR
UNIT_UT Disable None None None AREA01OPGR,AREA01SVGR
AREA02OPGR,AREA02SVGR,ENGGR
UNIT021B Disable None None None AREA02OPGR,AREA02SVGR,ENGGR
5.3 Alarm Suppression Design

The CAMS for HIS provides Alarm Suppression function which can eliminate designated alarms (Alarm
Group) temporarily. The alarm suppression by CAMS for HIS shall be used for area, process cell level or unit
level suppression. (E.g. Alarm suppression from out-of-service plant)
Alarm Suppression Start/Stop operation can be done by Function key, Graphic, Preset Menu function or %RQ..
Start Command:CENTUM Install folderProgram BKHCAMS_SON.exe [GroupName]
Stop Command:CENTUM Install folderProgram BKHCAMS_SOF.exe [GroupName]
It is recommended that equipment or control module level suppression (i.e. over current alarm of motor) is
realized by logic in the FCS.
The following is an example to define the suppression of alarm group group_1 on the graphic push button.

The each groups users who are allowed to do Suppression operation are defined on CAMS for HIS Alarm
Group builder. (Alarm Group Sub-State Change Permitted User) In default, all users are able to stop the
suppression, but start operation is not allowed by all users.
Define which alarm is belonging to which group on CAMS for HIS Alarm builder.
The suppression of the alarms which are belonging to group_1 starts by pushing the button on the graphic
window. If any alarm groups are suppressed, the information is displayed in the Suppression dialog box.

The behavior of Suppression has changed from R5.03.20.
Before R5.03.20:
When starting suppression, the suppressed alarm messages are recovered compulsorily and the recover
messages are output as following if these havent been acknowledged. When messages have been
acknowledged, these will be deleted without a recover message. The recover message cannot be suppressed.
When canceling suppression, the suppressed alarm messages (both of the message which occurred before
Suppression and the message which occurred after Suppression) are displayed with the timestamp of this timing
as following.
After R5.03.20:
Suppression is the same function as AOF, and a compulsory recovery does not take place when starting
suppression. The message on a monitor remains on the monitor as it is. If a displayed alarm recovered, it will be
deleted from a monitor.
When canceling suppression, the alarm messages which have arisen during suppression are displayed with the
timestamp of this timing as following. These messages remain on the monitor even if these are suppressed
again.
Canceling AOF
Canceling Suppression
After R6.01.10:
Selecting Do not generate recovery message when Suppression is started on CAMS for HIS tab of Project
Properties becomes available. If this option isn't selected, a recover message will be generated like the previous
behavior (before R5.03.20).
<<Sample Project>>
Alarm Suppression is executed by Alarm group (every Unit).
Start/Stop operation is done by Push button operation on a dedicated graphic.

5.4 Filter Design

Filtering is an operation to select A&E messages that serve your purpose. The function displays alarm messages
which are met to a filter condition and then can reduce the number of A&E messages displayed in A&E
Message pane.
User who has a permission to create a filter can also edit or delete filters by right clicking the mouse. (The same
operation can be done from edit menu.) The permission is set by CAMS for HIS Message monitor definition
builder (Message monitor tab of CAMS for HIS Configurator in previous version).
In case the system administrator want to create Filters without giving the permission of the filter creation to
Users, the system administrator needs to create the filters as system default filters by Configuration Mode of
CAMS for HIS Configurator. (In addition, the system administrator can give a permission to modify the filter
name / filter icon / filter description to Users. This permission is set by CAMS for HIS Message monitor
definition builder (CAMS for HIS Configurator in previous version).)
Load Shedding can restrict the messages and only displays the messages of the designated category
(pre-defined filter) when too many alarms are generated from the system in short time.
Load Shedding is defined at the Filter tab of the option window in CAMS for HIS Message monitor.
Only one filter can be assigned as Load shedding condition.
The CAMS for HIS provides the following default filters for linking with HIS. Be careful not to modify or
delete the default filters.
SIS: Displays all A&E messages sent from ProSafe-RS SCS (Safety Control Station)
SIS/System: Displays system alarm messages sent from ProSafe-RS SCS
SIS/Process: Displays process alarm messages sent from ProSafe-RS SCS
System: Displays system alarm messages
Process: Displays process alarm messages
Operator Guide: Displays operation guide messages and dialog messages
(Reference)
A customer may not want SIS filter when Prosafe-RS isnt connected. Or, a customer may not want Opegauide
filter when opeguide view is excluded from message monitor. In that case, these filters can be deleted by the
following procedure. Be careful not to delete necessary filters.
1. Start CAMS for HIS Configurator and select Message Monitor Configuration, and start Message monitor
with Configuration mode by SYSTEM user.
2. Select an unnecessary filter and open Properties using a click of the mouse to display the menu.
3. Change the filter name (any name is OK) and click [OK].
4. Select the same filter again and select Delete using a click of the mouse to display the menu.
5. Execute Commit Changes..
<<Sample Project>>
All Users can create/edit/delete filters..
System default filters are shown in the table below; (User cannot change the filter attribute.)
Filter for Critical/High alarm priority
Filter for each Unit
Use Load Shedding. User cannot change Load Shedding setting.
Condition and filter name for Load Shedding is shown below.

System Common Filters

Filter Name Description Icon Filter Condition Object Users
Critical_Alarm Critical & High alarm AlarmPriority=Critical or All Users
AlarmPriority=High
Unit11A Unit11A alarm Source.Plant="CAMSDEMO Users belonging to AR01OPGR,
AREA01 PLANT011 UNIT011A" AR01SVGR,ENGGR
Unit11B Unit11B alarm Source.Plant="CAMSDEMO Users belonging to AR01OPGR,
AREA01 PLANT011 UNIT011B" AR01SVGR, ENGGR
AREA01 PLANT012 UNIT012A" AR01SVGR, ENGGR
AREA02 PLANT021 UNIT021A" AR02SVGR, ENGGR
Unit21B Unit21B alarm Source.Plant="CAMSDEMO Users belonging to AR02OPGR,
AREA02 PLANT021 UNIT021B" AR02SVGR, ENGGR
UnitUT UnitUT alarm Source.Plant="CAMSDEMO Users belonging to AR01OPGR,
UTILITY UNIT_UT" AR01SVGR, AR02OPGR,
AR02SVGR, ENGGR
Definition of Load Shedding

Pre-defined filter name for Load Shedding Critical Alarm
Load Shedding Condition 15 alarms occurs per 1 minutes
5.5 Shelving Design

A Shelf is used for temporary hiding undesired alarms from the A&E message pane.
By reducing the number of displayed message, operator can immediately act to important alarm messages.
The difference between Shelving and Alarm Suppression is that the shelved alarms can be restored into A&E
message pane. On the other hand, the suppressed alarms are not recognized by CAMS for HIS so those alarms
can not be restored into the A&E message pane as long as the suppression is enabled. In this step, select the
extent of impact of the shelves, and define the function type and duration time for each shelf.
5.5.1 Shelving Function Type
There are three types of Shelf.

Continuous Shelving
A&E messages identical to each A&E message specified for shelving are shelved continuously
(including the recover message associated with these messages). Once the specified time elapses,
CAMS for HIS notifies that A&E messages remain
One-Shot Shelving
Only the A&E message specified for shelving is shelved. Once the specified time elapses, CAMS for
HIS notifies that the A&E message remains shelved.
Auto-Shelving
Applicable alarms are shelved continuously in accordance with the filter conditions set for these alarms
specified for shelving. Once the specified time elapses, CAMS for HIS notifies that A&E messages
remain shelved.
Auto-Shelf can be created only one in the project.

(Note)
Before R5.03.20, if a message in a continuous shelf is recovered, it disappears from the shelf and it cannot be
reset. After R5.03.20, a recovered message in a continuous shelf can be reset from a shelf by using the
continuous shelf reset individual message dialogue.
Reset Individual Messages in Continuous Shelf dialogue
5.5.2 Extent of Impact on Shelving Operation
There are two types of Extent of Impact, SYSTEM and USERS. The selected type must be the same within
an equalization scope.
SYSTEM
Shelving applies to the entire system. Shelved A&E messages are also shelved in all Message Monitor
of CAMS for HISs within the same system.
USER
Shelving applies to the Message Monitor of CAMS for HIS associated with the same HIS logon user.
Shelved A&E messages are also shelved in all Message Monitor of CAMS for HIS associated with the
same HIS logon user.
In CAMS for HIS before R4.02, the extent can be specified by the radio button on the upper part of the builder.
(See below.)
In R4.02 and later CAMS for HIS, the extent can be set in the location below. It cannot be specified for each
shelf, but the extent specified for the top shelf applies to all shelves.
If the extent is set to System, only system filters can be moved to Auto Shelf. (A filter created by a user is
specific to that user, so that filter cannot be moved if the extent is set to System.)

5.5.3 Type of Shelving Duration Time
It is possible to define a timing to inform operators that alarms are left in the shelf.
Duration
The CAMS for HIS notifies the remaining alarms in the shelf if the alarms have been left in the shelf
longer than specified duration.
Specific time
The CAMS for HIS notifies the remaining alarms in the shelf at the specified time, such as shift change
timing, etc.
<<Sample Project>>
Extent of Impact : System
Common shelves are defined as follows.
Shelf Name Description (Auto shelving Icon Function Type of Permissible Time
condition) Type Time
OneShotShelf One Shot Shelf One-shot Elapsed Time 10 minutes
NoTimeCriticic Time to respond >= 60min Auto Elapsed Time 60 minutes

The CAMS puts alarms which has
longer time to respond automatically.
1stShift Alarm Shelf for the shift operators. Continuous Specific time 15:30
CAMS notifies the remaining alarms
30 minutes before shift change
2ndShift ditto Continuous Specific time 23:30
3rdShift ditto Continuous Specific time 7:30

6 CAMS for HIS Message Monitor Design

The CAMS for HIS Message monitor is customizable on Font, color, whether or not to display each pane, and
so on.
It is possible to design the monitor for all users as a common or the different monitor for each user.
This section describes the customization of the CAMS for HIS Message monitor.
6.1 Customizable items on CAMS for HIS Message monitor

Window Layout
It is possible to change the layout of A&E Browser pane to the wide layout.
The layout can be switched by Change Window Layout button or set on the Window tab of Option
window.
Wide Layout
Standard Layout
Change Window Layout button
Window Color
It is possible to change the text color & the background color to be applied to the title name of each pane in the
CAMS for HIS Message monitor.
The change can be set on the Window tab of Option window.
The background color of the window title The background color of the window title (Selected)
The text color of the window title The text color of the window title (Selected)

Menu Bar/ Toolbar Show

It is possible to hide the Menu bar and Tool bar on CAMS for HIS Message monitor.
The change is set on CAMS for HIS Message monitor definition builder (CAMS for HIS Configurator in
previous version)..
Menu bar and Tool bar Menu bar is hidden
Tool bar is hidden
Shelves Pane Show

It is possible to hide the Shelves pane or to set the Show/Hide switching type.
In case of switching type, the Shelves pane can be shown or hidden by Show Shelves Pane button.
previous version).
Show Shelves Pane button

Shelves pane
Shelf Icon
Shelves Pane Blinking action

When an alarm moved into a shelf is blinking, the Shelf icon of the shelf is also blinking. This action can be
stopped by setting.
The change can be set on the Shelves tab of Option window.
Shelves Pane Displayed Number of Alarms/ Unread Alarm Style/ Font/ Color
It is possible to hide several alarm information (Number of Active Alarms/ Number of Unacknowledged
Alarms/ Total Number of Alarms/ Number of Ignored Alarms). And also it is possible to disable emphases when
there are unread messages in a shelf. Also it is possible to change Font and color settings.
The changes are set on the Shelves tab of Option window.

Number of Active Alarms

Number of Unacknowledged Alarms
Color of Font, text Total Number of Alarms
Number of Ignored Alarms
Emphases on unread message
Background color
Background color (Selected)
Text Color (Selected)
Filter Pane Show/ Create Filter

It is possible to hide the Filter pane or to set the Show/Hide switching type.
In case of switching type, the Filter pane can be shown or hidden by Show Filter Pane button.
The change is set on CAMS for HIS Configurator.
Also, it is possible to give the permission to create a new filter to Users. (User cannot create a filter by default.)
previous version).
Filter Icon
Show Filter Pane button
Filter pane
Filter created by User

User can create/ edit/ delete filters by
Edit menu of CAMS Message monitor if
the user have a permission.
Filter Pane Blinking action

When an alarm meeting the filter condition is blinking, the filter icon of the filter is also blinking. This action
can be stopped by setting.
The change can be set on the Filter tab of Option window.
Filter Pane Displayed Number of Alarms/ Unread Alarm Style / Font / Color
It is possible to hide several alarm information (Number of Active Alarms/ Number of Unacknowledged
Alarms/ Total Number of Alarms). And also it is possible to disable emphases when there are unread messages
meeting the filter condition. Also it is possible to change Font and color settings.
The changes are set on the Filter tab of Option window.

Number of Active Alarms

Color of Font, TextNote 1
Number of Unacknowledged Alarms
Total Number of Alarms
Emphases on unread message
Background color (Note 1)
Background color (Selected)
Text color (Selected)
(Note 1) The setting can be set on General tab of Option window
A&E Browser Pane Show

It is possible to hide the A&E Browser pane or to set the Show/Hide switching type.
In case of switching type, the A&E Browser pane can be shown or hidden by Show A&E Browser Pane
button. The change is set on CAMS for HIS Message monitor definition builder (CAMS for HIS Configurator
in previous version).
Show A&E Browser pane A&E Browser pane
A&E Message Pane
A&E Browser Pane Background Pattern / Color/ Font

It is possible to make the background of A&E Browser pane to the Zebra pattern. Also it is possible to change
the Text color and the Font color.
Changing to the Zebra pattern, the color of text and font is set on A&E Browser pane tab of Option
window.
Text color 1 Background color 1 Text color 2 Background color 2
Background color 2 (Selected) Text color 2 (Selected)

A&E Browser Pane Blinking action

It is possible to stop an icon (or TAG mark) blinking of A&E message.
In case of stopping icon blinking, the icon (or TAG mark) never blink even though the A&E message is
generated initially.
This setting is not related to the blinking action of A&E message displayed in A&E Message pane.
The change is set on A&E Browser pane of Option window.
A&E Browser Pane Line Spacing

It is possible to change the Line spacing.
By making the line spacing wide, it helps for operator to read messages easily.
The change is set on A&E Browser pane tab of Option window.
A&E Browser Pane Display Column

It is possible to add columns displayed on A&E Browser pane.
The time stamp and message contents are displayed as default setting.
Customized columns by CAMS for HIS Message monitor definition builder (CAMS for HIS Configurator in
previous version) can be added as well as the standard columns (AlarmPriority, Consequence and so on)
prepared by CAMS for HIS function.
The change is set on A&E Browser pane tab of Option window.
A&E Browser Pane Column Width

It is possible to make users to be able to change a column width of A&E Browser pane.
In case of using the default setting, user cannot change the column width, so user cannot read the message
content at A&E Browser Pane if the message is long.
previous version)..
A&E Browser Pane Display Position of New Alarm

It is possible to show new message at the bottom of A&E Browser pane.
previous version)..
A&E Messages Pane Background Pattern / Color/ Font

Same as A&E Browser Pane Background Pattern / Color/ Font.
A&E Messages Pane Blinking action

Same as A&E Browser Pane Blink action.
A&E Messages Pane Line Spacing

Same as A&E Browser Pane Line spacing.
A&E Messages Pane Display Column

Same as A&E Browser Pane Display Column.
Need to set for both Filter selected and Shelf selected.
A&E Messages Pane Display Position of New Alarm

Same as A&E Browser Pane Display Position of New Alarm.

Details Pane Show

It is possible to show the Detail pane always or to hide it. Default setting is the switching type and then the
Detail pane can be shown or hidden by Show Detail Pane button.
previous version).
Detail pane
Show Detail pane button
After R5.03.20, the detail pane has been divided into 2 tabs, "Alarm attribute" and "Guidance". Both of alarm
attribute and guidance will be displayed even if a guidance has been prepared as a text file.
Dynamic Filter Pane Show

It is possible to hide the Dynamic Filter pane.
Default setting shows the pane automatically when the cursor is over around the bottom of CAMS for HIS
Message monitor.
previous version).
Dynamic Filter pane
Status Bar Show

It is possible to hide the Status bar.
previous version).
Status bar

6.2 Design CAMS for HIS Message Monitor

Design the engineering items mentioned in the previous section and also describe whether or not users have the
permission to change these items.
When users can change items on CAMS for HIS Message monitor, the permission to change each item should
be given to users. Its defined on CAMS for HIS Message monitor definition builder (Message Monitor tab of
CAMS for HIS Configurator in previous version.).
When not giving the permission to users, the default value of each item can be changed by CAMS for HIS
Configuration Mode.
<<Sample Project>>
Engineering items Definition Permission to Users
General Layout Standard Deny
Color Default color for all items Deny
Menu bar/ Tool bar Show Show Show
Shelves Pane Show Show Deny
Blinking action Blinking Deny
Displayed Number of Alarms All items are displayed Deny
Unread Alarm Style Bold Deny
Font Default font Deny
Color Default color Deny
Filter Pane Show Show Show always
Create filter Allow users to create filters Allow
Blinking action Blinking Deny
Displayed Number of Alarms All items are displayed Deny
Unread Alarm Style Bold Deny
Font Default font both all filters and favorite filters Deny
Color Default color both all filters and favorite filters Deny
Change the system common User cannot change System common filter (Name/ Icon/ Deny
filter settings. Description) and Load Shedding definition.
A&E Browser Pane Show Show Show always
Background pattern/ color Standard pattern/ default color Deny
Blink action Blinking Deny
Line spacing Default value Deny
Display column Refer to Alarm attribute Deny
Column width Allow users to change the column width Allow
Display Position of New Alarm Defaults Top
A&E Message Pane Background pattern/ color Standard pattern/ default color Deny
Blink action Blinking Deny
Line spacing Default value Deny
Unread Message Style Bold Deny
Display column Refer to Alarm attribute Deny
Column width Allow users to change the column width Allow
Display Position of New Alarm Defaults Top
Detail Pane Show Switching type Switch Show/Hide
Dynamic Filter Pane Show Automatic display Show
Status Bar Show Show Show always

7 Capability of message notification processing of CAMS for HIS
7.1 Capability of message notification processing on R5.03.20 or later

A capability of message notification processing of CAMS for HIS has been significantly improved from
R5.03.20. The capability of message notification processing is an index in deciding whether messages are
displayed on CAMS message monitor within 1 second after HIS receives them. It is expressed by a maximum
number of messages per second.
The capability of message notification processing depends on a PC's display performance and the following
definitions on CAMS message monitor (Refer to the section 7.3 for the details). Therefore, showing a unique
value is impossible. Regarding the actual capability of message notification processing, refer to the measured
result in the section 7.4.
- The maximum size of alarm buffer (It can be extended up to 10000 by Tokuchu.).
- The number of columns (attributes) and filters on CAMS message monitor.
- The number of characters defined as a Guidance or User-defined attribute on CAMS message monitor.
7.2 Behavior at the time of alarm flooding

If all instruments are stopped because of power failure, etc., messages will be generated beyond the speed of
CAMS's ability. The following problems will occur if continuing this situation.
- Messages are not displayed on the SMB or CAMS message monitor, or it takes time before displaying.
- The number more than the maximum size of alarm buffer will be displayed on SMB.
- ACK operation is not available. Messages cannot be deleted.
The above-mentioned phenomena occur when the Notification FIFO buffer in CAMS server is filled with
messages or messages are overflowing from it.

The time that elapses before overflowing of the Notification FIFO buffer can be calculated roughly by a rate of
message generation (number of messages / sec) in case of power outage which is estimated by the total number
of function blocks.
According to the measured value in the section 7.4, the capability of message notification processing of DELL
HIS with 10000 buffer size is 110 messages / sec. If the estimated rate of message generation in case of power
outage is 200 messages / sec, 90 messages per sec are not notified soon and are accumulated in the Notification
FIFO buffer temporary. The size of the Notification FIFO buffer is 20000 when the maximum size of alarm
buffer is 10000. Therefore, messages will be overflowed from the Notification FIFO buffer in 220 seconds
(20000 / 90).
The period when messages are accumulated in the Notification FIFO buffer.
Message display may be delayed, however, messages will be displayed on CAMS message
monitor correctly. (Delay is up to 182 seconds (20000/110 =182).)
Messages are overflowing from the Notification FIFO buffer and

the display on CAMS message monitor becomes incorrect.
- The number more than the maximum size of alarm buffer
is displayed on SMB
- - Messages cannot be deleted by ACK.
Overflowing - - It takes time before displaying messages..
of notification
FIFO buffer
Please do logon (User-in) again to restore if the display of CAMS message monitor becomes incorrect
after overflowing the Notification FIFO buffer (if the number more than the maximum size of alarm
buffer is displayed on SMB). After that, the Notification FIFO buffer will be reset and messages on CAMS
message monitor will be cleared. The messages can be confirmed in historical viewer even if these have been
cleared from CAMS message monitor.
Furthermore, if a lot of messages continue occurring for a long time, messages will be overflowed from the
forwarded packet FIFO buffer and a part of messages will be not recorded in a historical file. Doing logon
again restores the incorrect situation of CAMS message monitor, however, there is no way to confirm
overflowed messages.
7.3 Elements which affect the capability of message notification processing

The following definitions regarding the display on CAMS message monitor affect the capability of message
notification processing. Especially, the size of alarm buffer largely affects it. The number of columns, filters
and characters don't affect the performance so much, however, reducing the number results in the efficiency of
capability of message notification.
(1) Size of Alarm buffer

When the size of alarm buffer is large, the number of messages displayed on CAMS message monitor will
increase and it will affect the display performance. The display performance will get worse when the
number of unacknowledged messages and not recovering messages increase and exceed the alarm buffer
size, because CAMS server needs to delete low priority messages and display new messages on CAMS
message monitor.

(2) The number of displayed columns (attributes) and filters on CAMS message monitor
If displaying the columns other than the default 2 columns (Date and message), the display performance
will get worse according to the number of displayed columns.
In the case of filter, if the number of messages which are matched to the filter conditions increases, it affects
the display performance. (Putting messages into the appropriate filters in accordance with the filter
conditions affects the load of CAMS server.)
(3) Amount of character data to display on CAMS message monitor

The number of alarm sources doesn't affect the display performance. If the number of characters for
guidance, the number of user-defined attributes and the amount of characters defined for a user-defined
attribute increase, the display performance will get worse.
7.4 Measured result

The following is the measured result by R&D. (For reference). One of the 10 displayed columns is guidance
display with 250 characters. Messages will be displayed on SMB or CAMS message monitor within 1 second,
after a HIS receives them, even if messages continue arising within the following capability of the message
notification processing for a long time. (Messages are not accumulated in the buffer.)
DELL HIS (T3500, CPU 3.60GHz(2CPU), Memory 8.00GB):

Alarm Engineering database Monitor definition Capability of CPU
buffer Alarm Guidance User-defined Number of Number of message notification
sources attribute displayed columns filters processing
2000 400000 250 char. 1 8 56 210/sec 35%
4000 400000 250 char. 1 8 56 160/sec 35%
10000 400000 250 char. 1 8 56 110/sec 35%
HITACHI HIS (HF-W7500 model30, CPU 2.00GHz(4CPU), Memory 7.99GB):

Alarm Engineering database Monitor definition Capability of CPU
buffer Alarm Guidance User-defined Number of Number of message notification
sources attribute displayed columns filters processing
2000 400000 250 char. 1 8 56 90/sec 80%
4000 400000 250 char. 1 8 56 70/sec 83%
10000 400000 250 char. 1 8 56 40/sec 70%
According to above data, the capability of message notification processing of HITACHI HIS is 90 messages /
sec when the maximum size of alarm buffer is 2000. It means that HITACHI HIS does not meet the official
capability of CAMS (130 messages / sec). However, as described in the section 7.2 and the following graph, as
long as the situation of receiving messages exceeding the capability does not continue for a long time, all
messages that should be notified are displayed on CAMS message monitor.

Capability of message notification processing when messages arise continuously with the speed of 130
messages / sec. (Measured value of HITACHI HIS with buffer size 2000)
The number of processed messages 90000
80000
No problem till 300 seconds.
70000 This graph shows that there are messages
never notified after 300 seconds.
60000
50000
40000
30000
Messages which occurred actually
20000
Messages which were notified
10000
0
0 60 120 180 240 300 360 420 480 540 600
Time
Actual capability of message notification processing of HITACHI HIS is 90 messages / sec. If messages arise at
the speed of 130 messages / sec, 40 messages / sec will be accumulated in the Notification FIFO buffer. The
size of the Notification FIFO buffer is 12000 if the maximum size of alarm buffer is 2000. Therefore, for at
least 300 seconds (12000 / 40 = 300), all messages that should be notified are displayed on CAMS message
monitor and are recorded in Historical file without problems.
7.5 Conclusion (Engineering to ensure message notification processing)

Suppressing unnecessary messages is considered most important, however, the following points should also be
paid heed.
1. Keep the size of alarm buffer to a minimum when the size is expanded by Tokuchu.
2. Keep the number of columns which are displayed on CAMS message monitor to a minimum.(around 10)
3. Keep the number of filters which are displayed on CAMS message monitor and conditions for each filter to
a minimum.
4. Reduce the number of characters for Guidance as much as possible when Guidance is required.
5. Keep the number of user-defined attributes to a minimum.
7.6 The behavior when messages are suppressed

Practically, the Alarm buffer (Alarm Data table) described in the following figure maintains the messages until
the number defined by "Maximum size of alarm buffer".

The messages suppressed by the following methods aren't included in the

Alarm buffer. It means that suppressing the unnecessary messages by the
following methods contributes to the efficiency of capability of message
notification.
(All of OPC A&E messages are included in the Alarm buffer because those
messages are not able to be suppressed one by one.)
- Suppression
- Detection = Disable
- Priority = Logging
- Priority = Reference
- AOF
The details are described in the following table.

x: Not included o: Included
The sort of suppression Alarm buffer Suppression Historical file
Alarm buffer
CAMS Suppression x o *1 o
CAMS Disable x x x *2
CAMS Priority = Logging x x o
CAMS Priority = Reference x x x *2
AOF x o *1 o
*1: After cancelling Suppression or AOF, the alarm messages during occurrence moves to the Alarm buffer.
*2: Those are not displayed on the Historical view but recorded in HISHIST.

8 Engineering Tool
If there is the wrong records in CAMS DB, CAMS of HIS doesnt work properly.
CAMS Database Consistency Check tools have been released from R3.08.70 & R4.01.60. These tools are for
internal use only.
Duplication Check Tool : Checks the duplicate alarm source in CAMS DB.
Deviation Check Tool : Checks the difference of alarm source between CENTUM DB and CAMS DB.
From R5.01, the following engineering tools have been prepared. Refer to the engineering guide CAMS for HIS
Trouble Shooting & FAQ for the details.
Redundancy ring check tool: Checks whether CAMS Equalization Ring works correctly.
Historical file dump command: Converts the historical files to text data.
CAMS Server restart command (R5.03.20 or later): Restarting CAMS server by specifying a equalization
source HIS is possible..
8.1 Tool Launcher

After closing CAMS Configuration, double click the following exe file from Windows Explore.
[CENTUM install folder]histool CAMSDatabaseChecker.exe
You can launch a tool you want to use from the Tool Launcher.
8.2 Duplication Check Tool

The tool retrieves all alarm definition file (*.csv) from a search object folder, and checks whether an alarm
source defined in a definition file is duplicated in other definition files.
When the tool finds the duplicate alarm sources, it shows the duplicate alarm source name, the plant hierarchy
name, the location of the definition file and the file update information (date & time).
How to start
Select Duplication Check Tool on Launcher screen, then press Start button. Main window is displayed.

Search function
By pressing Search button, the search function starts.
In upper area, shows the result of search for the duplication in Active CAMS DB that was downloaded to HIS.
In lower area, shows the results of search for the duplication in Work CAMS DB that is before downloading.
Result of search
When there is no duplication, the following dialog appears.
When there is duplication, the following dialog appears and the duplicate alarm sources are shown.
Example
PID001.HH and PID001.HI were defined for PLANT 1 at 2006/10/21.
(PID001 was created in FCS0201DR0001 and PLANT 1 was assigned in the upper plant name of PID001, and
then PID001 was imported into CAMS DB.)
After that, the same alarm sources were defined for FCS0201DR0001 at 2006/10/21.
(The upper plant name definition of PID001 was deleted, and then imported into CAMS DB.)
Therefore the duplicate alarm sources were created.
Required action
Delete unnecessary alarm sources from CAMS DB and then download new DB.

8.3 Deviation Check Tool

The tool consists of the following function.
Pre-import: the tool copies three information (Alarm source, User, User Group) from
Project DB to the work directory for checking.
Deviation detection: the tool compares alarm source between CAMS DB and information above.
The Deviation detection function compares the data itself but not the attribute of the data. For example
For example, the tool checks whether or not there is a user, but it doesn't compare the security setting of the
user.
How to start
Select Deviation Check Tool on Launcher screen, then press Start button. Main window is displayed.
Search function
By pressing Search button, the search function starts.
In upper area, shows the alarm sources that exist in CENTUM DB but not in CAMS DB.
In lower area, shows the alarm sources that exist in CAMS DB but not in CENTUM DB.
Result of search
When there is no deviation, the following dialog appears.
When there is deviation, the following dialog appears.

Example 1 Alarm source deviation: Function block type of TAG001 was changed from SIO block to PID block.
Example 2 User Group deviation: User Group name was changed from Group1 to Group2
Required action
Delete unnecessary alarm source or data from CAMS DB and then download new DB.

9 The Message from CENTUM XL and XL
9.1 Messages from the legacy stations supported by CAMS for HIS
R3.08.70 & R4.01.60 or later, CAMS for HIS can handle the A&E messages of CENTUM-XL and XL
stations (hereinafter referred to as the legacy stations) connected on the network through bus converter
(BCV-H/L). Since CENTUM V is not supported, do not use CAMS for HIS for the system.
CAMS for HIS Message Display
BCV-H/-L Message frame conversion
CENTUM-XL, XL Message generates
9.2 View and Operate on CAMS for HIS Message Monitor

The displays of the process alarm messages of the legacy stations (not including the annunciator) on Message
Monitor of CAMS for HIS are different from the CS 3000 process alarm messages.
The main differences between the process alarm messages of the legacy stations and the process alarm
messages of CS3000 are as follows:
The number of messages from legacy stations is limited to 20 per each tag.
(For displaying annunciator messages, up to 10 messages per each tag can be displayed. The actions are
the same regardless if the CAMS for HIS is enabled or disabled.)
The alarm tree view (or eclipsing) is only grouped per each tag.
Continuous Shelving is processed per each tag.
Acknowledge operation is performed per each tag.
For multiple alarm messages of one tag, the recovery messages not paired with all the alarm messages,
there is only one recovery message for the tag.
This feature is the same regardless if the CAMS for HIS is enabled or disabled.
The message text does not contain the process data.
The message with alarm status of [NR], the messages with status of [CAL] and the message with status of
[AOF] may also be displayed.
(Note 1) Display of Simultaneously Occurred Messages:
When multiple messages occurred simultaneously, only the message with the highest alarm priority will be
displayed, and displayed as an unacknowledged message. This action of the simultaneously occurred
messages including the messages occurred at the timing of occurring or recovering of a process alarm,
releasing CAL (NCL) and AOF (AON) statuses.
(Note 2) Message with Alarm Status of [NR]:

When a message with the alarm status of [NR] is received, CAMS for HIS will delete the other acknowledged
messages of the same tag. If all the messages of the same tag are all acknowledged, all the messages of the
tag including the message with status of [NR] will be deleted. If there is one or more than one messages of
the tag is not yet acknowledged, the message with alarm status of status to [NR] will be displayed as
unacknowledged.

(Note 3) Message with Data Status of [CAL] or [AOF]:

The message may be displayed as an unacknowledged when an alarm status in [CAL] or [AOF] of a function
blocks changes.
9.3 Display on Historical Viewer of CAMS for HIS

When displaying the process alarm message (not including the annunciator) of legacy stations on Historical
Viewer of CAMS for HIS, the message may be displayed twice. One is displayed with the process data while
the other is displayed without process data. The previous one is for printout and the later one is for display on
screen. Moreover, on Historical Message Report window, only the messages with process data which are
originally for printout are displayed.
9.4 Action of Configurator of CAMS for HIS

When importing the CS 3000 engineering data to the Configurator of CAMS for HIS, the alarm definitions
regarding the tags of the legacy stations cannot be imported.
Moreover, it is not possible add new definitions for the A&E messages of the legacy stations on the Alarm List
tab, the attributes cannot be defined either.
9.5 Action of Alarm Generator

The Alarm Generator cannot simulate the alarms of the legacy stations.
9.6 HIS and CAMS for HIS Regarding Messages of Legacy Stations
On HIS operation and monitoring window, the process alarm messages of legacy stations will be displayed
regardless the alarm inhibition settings on CAMS for HIS.
Alarm message
of Legacy station
Alarm message of
not Legacy station

10 Multiple Projects Connection
10.1 Multiple Projects Connection before R4.02

Before R4.02, CAMS for HIS doesnt fully support the multiple-project connection function. An alarm message of
another project can be displayed in the CAMS for HIS Message monitor by importing these messages into
OtherProject (see below) but the acknowledgement operation or shelving operation for these alarm messages
cannot be shared by the other project. Furthermore, the alarm configuration must be performed independently for
each project, so there is a problem with cumbersome duplicate definitions.
The following describes the procedure to import the alarm source of another project to CAMS for HIS Alarm
builder.
To import the alarm source of another project, use OtherProject in CAMS for HIS Alarm builder. Import to
OtherProject a CSV file that was exported in CAMS for HIS Alarm builder of another project.
CAMS Alarm builder in other project
Import Export
CSV file
To import the alarm source of another project, an attribute called ProjectID is required. This is an attribute available
in CAMS for HIS Alarm builder by default and is used to recognize another project. To import to OtherProject a
CSV file that was exported in CAMS for HIS Alarm builder of another project, the inputting of the project ID is
required.

<Procedure to import a CSV file to OtherProject>

(1) Select OtherProject in CAMS for HIS Alarm builder.
(2) Select External File Import from the File

menu.
(3) In the Import window, set the CSV file that was exported in CAMS for HIS
Alarm builder of another project, then select the item and perform mapping.
(4) Click Import to display the Import (OtherProject) window.
(5) Define the project ID

and click OK.
Turning on the Add
ProjectID to the tag
name checkbox adds
@{ProjectID} to the
tag name when
importing.
(6) The following window appears. Click OK.
(7) The alarm source of another project is imported.

10.2 Multiple Projects Connection in R4.03 and later

After R4.03, CAMS for HIS has supported multiple-project connection officially. The ACK, Manual reset,
Suppression, Shelving(excepting AUTO) and edited memo in Detail pane are equalized among HISs in multiple
projects. However, it is necessary to define the same name for all alarm groups on every project for Suppression.
Also, it is necessary to define the same Shelf name", "Shelf type and Extent of Shelving for all shelves on
every projects for Shelving. The followings show the result of shelving. The result depends on the definition of
"Extent of Shelving".
<Extent of Shelving: SYSTEM>
<Extent of Shelving: USER>
The ACK and Manual reset operation of System alarm messages and opeguide messages are equalized in the same
Operation group.

The upper project must be R4.03 or later if Multiple projects connection is used on CAMS for HIS. Also, the alarm
action must be same among all projects.
If all projects are R4.03 or later, the following setting is available to equalize engineering data among multiple
projects. (Project Properties CAMS for HIS tab) Be careful not to set it when a project before R4.03 is
connected. (The downloading of project common section is required after setting it.)
Use the OtherProject node described in 9.1 for Alarm engineering in the following cases.
- Alarm engineering is configured on the upper project.
- A project before R4.03 is connected.
Import the Alarm source of lower project (CSV file) to the OtherProject node.
- In the case that the CAMS for HIS alarm builder exists in the lower project;
Use the CSV file exported from CAMS for HIS Alarm builder.
- In the case that there is no CAMS for HIS Alarm builder in the lower project;
Create CSV file nanually.
AlarmSource must be defined on A1. Define each alarm source after
A2 column.
OtherProject Node
When creating CSV file (Alarm source list file of a project which doesnt have CAMS for HIS Alarm builder)
manually, execute CENTUM VP Database Convert of the Tool menu of Configurator of CAMS for HIS and use
the output alarm source list files for each hierarchy.
Those files are output in CENTUMVP\CAMS\configurator\work\database\Client\Config.
Alarm source list files for each hierarchy
Note)
An alarm list source file is created based on a tag list in the HIS which executed "CENTUM VP Database Convert".
The alarm list source file isn't output if that HIS doesn't include a tag list of lower project.

Unify the alarm source list files of lower project. Delete the rows except "Source". And change the column name of
Source to "AlarmSource" and import it to OtherProject node.
Delete
Delete
If the lower project is before R4.03, the User-defined alarm character string and Plant hierarchy of the lower
project must be acquired by the upper project. (This procedure is required whenever these have been changed in
lower project.)
1. Execute CENTUM VP Database Convert in the upper project. (Configurator of CAMS for HIS Tools
CENTUM VP Database Convert)
The following files are created under
C:/CENTUMVP/CAMS/configurator/work/database/Client/Config
AlarmStatus.csv
PlantClass.csv
2. Copy AlarmStatus.csv and PlantClass.csv to

The upper project name)/Common/CAMS_for_HIS/CAMSAlm~EDF.
3. Open the User-defined Status Character String builder and Plant hierarchy builder, save them, and then
download them.

10.3 When upper project is R5.03.20 and lower project is before R5.03.00
After R5.03.20, the database style of CAMS for HIS has changed. Therefore, R5.03.20 HIS cannot read the
engineering information downloaded from an ENGHIS (CAMS for HIS Alarm builder) in a previous revision
project.
To avoid this problem, use OtherProject node of CAMS for HIS Alarm builder in upper R5.03.20 project.
<Detailed procedure>
1. Import the definition of CAMS for HIS Alarm builder of previous revision (R4.03.00 in this case) by
OtherProject node of CAMS for HIS Alarm builder in R5.03.20 upper project.
2. Tick a box of Equalize the alarm & event data and CAMS engineering data with connected projects on CAMS
for HIS tab in Project Properties of upper R5.03.20 ENGHIS..
3. Tick a box of Equalize the alarm & event data and CAMS engineering data with connected projects on
CAMS for HIS tab in Project Properties of lower rev ENGHIS.
4. Download Project common section from both of upper project and lower project.

11 Alarm messages received via OPC

The CAMS for HIS enables alarm and event messages to be received directly from OPC A&E servers. (Only the
connections to PRM and Stardom are guaranteed officially.) The OPC A&E through SIOS is an arbitrary
character-string of sequence message Text massage and CAMS for HIS cannot receive it.
When connecting OPC A&E, set up the connection between CAMS for HIS and the OPC A&E server in the OPC
A&E Server Connection dialog box opened from the HIS Utility dialog box. Messages are received by a HIS with
the following definition, and these messages are equalized among other HISs within the same equalization scope.
Connecting two or more HISs to OPC A&E server for safety purpose is possible, however, it requires the process of
deleting duplicative messages and it affects the performance of CAMS for HIS.
The computer name of the HIS is displayed.
Type the computer name of

the OPC A&E server.
Type the program ID of

the OPC A&E server.
The registered OPC A&E servers are listed here.
After defining above-mentioned settings on HIS utility, messages from OPC A&E will be displayed on CAMS
message monitor. By registering OPC A&E server program ID in OPC hierarchy of CAMS alarm builder,
engineering on CAMS for HIS alarm builder becomes available. (The program ID for PRM and STARDOM is
prepared by default.)

To normalize messages (to make messages into the same style as CENTUM) is required for displaying messages
from OPC A&E on the CAMS message monitor. The PRM and STARDOM have the mechanism of this
normalization, therefore they are guaranteed to connect CAMS for HIS officially.
As has been explained above, engineering on CAMS alarm builder becomes available by registering OPC A&E
server program ID in OPC hierarchy of CAMS alarm builder, however, it means to overwrite the result of
normalization.
Example of engineering of STARDOM messages on CAMS alarm builder
In the case of STARDOM, the source of system alarm messages is IP address like the above-mentioned image
(172.32.1.100 IP address of FCN/FCJ). Therefore, the definition for each system alarm message on CAMS alarm
builder is not allowed. A source of process alarm message and application alarm message is one of the followings
and a definition for each source is possible on CAMS alarm builder.
- A tag name of SIOS instrument and an alarm name are connected by "." (e.g. FIC001.OOP)
- A POU instance name and an alarm name are connected by . (e.g. Main.NPAS_PID_1.OOP)
The tag mark of messages from OPC A&E is the following shapes.
Recover
Alarm
Acknowledged
(Note)
After R5.03.20, Tokuchu is available to normalize OPC A&E messages from other than PRM and STARDOM.
(Create a DLL for normalization by Tokuchu.)

The Tokuchu DLL normalizes the data from OPC A&E server and put them into a alarm data structure member
corresponding to a column of CAMS message monitor. Only the following members and columns are available.
(User-defined attribute is not available.)
Refer to Appendix3 for the sample user specification for Tokuchu DLL.
Column name Data type Member of alarm data structure Description

Timestamp double stNattr.dTimestamp Time stamp
Timestamp.server double stNattr.dTimestampServer Time stamp (CAMS)
Source char [512] stNattr.szSource Alarm source (main)
Source.Plant char [136] stNattr.szSourcePlant Alarm source (sub)
TagName char [16] stNattr.szSourceEclipseGroup Tag name
AlarmPriority CAMS_UINT16 stNattr.stSeverity Alarm priority
CAMS_UINT16 stNattr.szSourceEclipseLevel
Message char [256] stNattr.szMessage Alarm message
<icon> char [16] stNattr.szMessageMark Tag mark
<sound> CAMS_BYTE stNattr.szMessageBuzzer Alarm buzzer
TypeOfAlarm CAMS_BYTE stSattr.stTypeOfAlarm Type of alarm
<alarm condition> char [24] stNattr.szCondition Condition attribute
(EVENT, ALARM,
RECOVER)

12 Upgrading CAMS for HIS

The upgrading procedure depends on the version before upgrade. The database structure was changed at R3.08.50,
R4.02 and R5.01. The following actions are required when getting over these versions.
Pattern 1
Pattern 2
Pattern 3
- Shutdown all the HISs - Convert the CAMS DB by - Create index files for the historical search
before upgrading. CAMS for HIS Migration Tool.(*1) by Index file generation tool. (*3)
- Start an old Configurator of - When upgrading from CS3000,

CAMS for HIS by running copy the folders/files under
the following command on CS3000/CAMS to the same position of CENTUMVP/CAMS.
Command Prompt, and (Backing up and Restoring CS3000 Package Data)
download from it. It is necessary to disable CAMS for HIS once. (*2)
CENTUMVP/CAMS/CAMSConfigurator.exe O
(*1) Regarding CAMS for HIS Migration Tool, refer to the IM 33K03H20-50E Consolidated Alarm
Management Software Reference, B3.1.1 Migration Tool.
(*2) Regarding this procedure, refer to the IM 33K01C10-50E CENTUM VP Installation,

C6.1.2 Backing up and Restoring CS 3000 Package Data.
(*3) Regarding Index File Generation Tool, refer to the IM 33K01C10-50E CENTUM VP Installation,
C11.6 Upgrading to R5.01.00 .
The outline of upgrading of each pattern is described from next page. Refer to the IM 33K01C10-50E CENTUM VP
Installation for the detailed procedure.

12.1 Procedure of upgrading for Pattern 1

The following is a procedure when a PC is ENGHIS and Download master.
1. Save PJT DB.
2. Disable CAMS for HIS and save all data under CS3000/CAMS (CS3000 package data).
3. Shutdown all the HISs within the equalization scope, and start Download master (ENGHIS).
4. Perform installation upgrading to R5.
5. Restore CS3000 Package Data to the same position under CENTUMVP/CAMS. After that, enable
CAMS for HIS and reboot PC.
6. Download from the old Configurator of CAMS for HIS. After that, execute Back-up of Configurator
(Run CENTUMVP/CAMS/CAMSConfigurator.exe O on Command Prompt and download from it.)
7. Open a project on SystemView. (Convert PJT DB.)
8. Convert the back-up of Configurator of CAMS for HIS (saved at 6) by CAMS for HIS Migration Tool.
9. Download Project Common section.
10. Just to make sure, confirm the settings on HIS Utility - CAMS for HIS tab.
(It has been restored by 5.)
11. Run Index file generation tool


1. Execute Back-up of Configurator of CAMS for HIS and save PJT DB.
2. If the original PJT is CS3000, disable CAMS for HIS and save all data under CS3000/CAMS
(CS3000 package data).
3. Perform installation upgrading to R5..
4. If the original PJT is CS3000, restore CS3000 Package Data to the same position under
CENTUMVP/CAMS. After that, enable CAMS for HIS and reboot PC.
5. Open a project on SystemView. (Convert PJT DB.)
6. Convert the back-up of Configurator of CAMS for HIS by CAMS for HIS Migration Tool.
8. If the original PJT is CS3000, just to make sure, confirm the settings on HIS Utility - CAMS for HIS
tab. (It has been restored by 4.)
9. Run Index file generation tool.
Both of the back-up of Configurator of CAMS for HIS (saved at 1) and the back-up of all files under CAMS folder
(saved at 2) are available for CAMS for HIS Migration tool. The relation between them is as follows.
Files to be needed for CAMS for HIS Migration tool

the back-up of Configurator of CAMS for HIS
the back-up of all files under CAMS folder
Actually, CAMS for HIS Migration tool requires the following 2 folders.
- database
- configurator


1. Perform installation upgrading to R5..
2. Open a project on SystemView (Convert PJT DB).
4. Run Index file generation tool.
If a PC is replaced, move the PJT DB, the back-up of Configurator of CAMS for HIS and CAMS historical data
(CAMS/hist) to the same place in a new PC.
Before connecting a new PC to the network, start it up with the same conditions as the engineering HIS of the
previous revision (Install R5 -> Restore PJT DB -> Restore Historical data -> Convert PJT to R5 -> Download PJT
Common -> Enable CAMS, Define Equalization scope). After that, shutdown both of new PC and existing PC, and
exchange them, and restart a new PC. After starting HIS, restore the back-up of Configurator of CAMS for HIS and
download it. Finally, run Index file generation tool.
Regarding other HISs, start it up with the same conditions as the existing PC and exchange the old one for new one
after doing shutdown of both of them.
New HIS0164 New HIS0163 New HIS0162
Old HIS0164 Old HIS0163 Old HIS0162
CAMS
PJT DB Configurator DB
CAMS
Historical CAMS
CAMS
Historical Historical

Appendix1. How to define Guidance

Cause and solution regarding the A&E message can be defined in the Guidance column on CAMS for HIS Alarm
builder. The guidance messages can be typed in the column directly. It is also possible to define the guidance
messages on the separately prepared files or web pages.
Select Guidance on the "Style Settings dialog" of Configurator of CAMS for HIS and download when only the
information defined in the Guidance column is displayed on the Details pane.
(Before R5.03.20, this setting is applied to all messages. So, in the case of the sources without defining the
guidance, nothing will be displayed in the Details pane.)

When the guidance messages are typed in the Guidance column directly
The information typed in the Guidance column is displayed in the Details pane.
When the guidance messages are described in the text file

If the file name of separately prepared text file is defined in Guidance column, the data of the text file is displayed in
the Details pane. The text file should be saved with UTF-8 or UTF-16. Download the text file as external file
directly from the Configurator of CAMS for HIS. Specify the following as the download destination.
(CENTUM VP Installation Folder)/CAMS/database/httppost
The data of the text file is displayed in the Details pane.

When Editable (Text File Only) option is selected on the "Style Settings dialog" of the Configurator of CAMS for
HIS, it becomes possible to directly edit the text displayed in the Detail pane.
Note) There is not a limit on the number of text file.

Note) The maximum size of a file is 10KB.
When the guidance messages are described on the WEB page

If URL is defined in Guidance column, the hyperlink to the URL is displayed in the Details pane. WEB page is
displayed by clicking the hyperlink.

When the guidance messages are described in the file other than text file
If the file path is defined in Guidance column like following, the hyperlink to the address is displayed in the Details
pane. The data of the file(Word, Excel, Pdf, etc.) is displayed by clicking the hyperlink.
Ex) When the file (wordmemo.doc) is under C: temp wordmemo.doc
file: C: temp wordmemo.doc
Files other than the text file arent equalized among the HISs in the same equalization scope. Even if the files are put
into httppost, they arent equalized.
Click the hyper link then the content of file is displayed. It is the same also in Excel and PDF, etc.

Appendix2. The operational differences between CAMS and NON-CAMS
HIS without CAMS for HIS HIS with CAMS for HIS
Definition for Acknowledgement Action (Acknowledge and Acknowledge All)
Define the Acknowledgement Action on Alarm tab of HIS Setup window. The definitions on Alarm tab of HIS Setup window are disabled.
("Group Acknowledgement" or "Individual Acknowledgement") (Excluding the setting for "System Message Banner")
One of them can be selected. Both of [Acknowledge] button and [Acknowledge All] button can be displayed on
the Message monitor of CAMS for HIS. (Customization for each user is available.)
The action of the Acknowledgement key on the operator keyboard also complies with
this setting. The action of the Acknowledgement key on the operator keyboard is defined on
CAMS for HIS tab of HIS Utility.

Acknowledgement and Deleting of System Alarm Messages

* Deleting of a message without a recover message. * Deleting of a message without a recover message.
Blink stops by [Ack] button. The reset messages are never deleted by [Ack] button. Only the recovered messages are deleted by [Ack] button.
All acknowledged messages (including the messages without a reset message) are Blink of the messages without a reset message stops by [Ack] button.
deleted by [Delete] button.
Messages without a reset message
Messages without a reset message Reset the alarm messages by [Manual Reset] button and delete them by [Ack] button.
Deleting after Acknowledgement

Manual Reset
Ack


* The behavior in the case of Individual Acknowledgement * The behavior in the case of Individual Acknowledgement
An alarm message and its reset message must be deleted individually. Both of an alarm message and its reset message are deleted when one of them has been deleted.
(There is no relation between them.) (There is a relation between them.)
Ex When "FCS Fail/Recover" messages arise twice from FCS0101 and FCS0102; Ex When "FCS Fail/Recover" messages arise twice from FCS0101 and FCS0102;
After acknowledging all messages, Select "0303 10/19 16:41:26 FCS0101 Fail" and acknowledge it.
select "0303 10/19 17:15:55 FCS0101 Fail" and [Delete] it. Then, another "0303 10/19 16:40:57 FCS0101 Fail" is deleted simultaneously.
Then, another "0303 10/19 17:13:47 FCS0101 Fail" is deleted simultaneously. Also, its reset message (0304) is deleted at the same time.
(The message with the same number of FCS0102 isn't deleted.) (The message with the same number of FCS0102 isn't deleted.)
Select one of them and acknowledge it.
Select one of them and delete it.
"0304 FCS0101 Recover" is also deleted.

"0304 FCS0101 Recover" isn't deleted.


* The privilege required for deleting messages * The privilege required for deleting messages
[Ack] is available for every user. [Delete] is available for the user with more than S2. [Ack] is available for every user. [Manual Reset] is available for the user with more than S2.
The user with S1 can't operate [Delete]. The user with S1 can't operate [Manual Reset].
Acknowledgement of Process Alarm Messages
Alarms of each tag can be acknowledged. Alarm messages are acknowledged individually.
All alarm messages from the same tag are acknowledged after one of them Even if the messages are from the same tag, each message needs to be acknowledged
has been acknowledged. (Individual Acknowledgement) one by one. ( If these messages are in the same Alarm group and "Apply to All"
is defined for this group, all of them are acknowledged at the same time.)

Manual reset of Process Alarm Messages
An process alarm can't be reset manually. An process alarm can be reset manually.
(There is no [Delete] button in the process alarm view.) The setting to permit users or user groups [Manual Reset] operation is required
on CAMS for HIS Alarm builder.
Open the "Message monitor of CAMS for HIS" by a "Manual reset permitted user" and
select a relevant alarm. Then, [Manual Reset] button becomes active.
Delete an alarm by [Ack] button after resetting it by [Manual Reset].

NR message of Process Alarm Messages

(In the case of Lock-type, NR message without buzzer sound is output regardless of (NR message without buzzer sound is never output.)
the alarm priority when all alarms from the same tag are reset before acknowledging them.)
* In the case of "High-priority" and "Notifivation at Return Type" * In the case of "High-priority" and "Notifivation at Return Type"
1.Blink stops by [Ack] button. 1.Blink stops by [Ack] button.
2. Only NR is displayed when all alarms have been reset.

(both of "Lock type" and "Non lock type".)
"In the case of CENTUM Original"
2. Only NR is displayed when all alarms have been reset.
(both of "Lock type" and "Non lock type".)
NR message with buzzer sound.
"In the case of Consolidated"
3. Example in which all alarms are reset without the acknowledgement. 3. Example in which all alarms are reset without the acknowledgement.
All messages are deleted by the acknowledgement for one. Only the selected message is deleted by [Ack] button.
(the pair of alarm/reset is reset at the same time)

NR message of Process Alarm Messages

* In the case of "High-priority" and "On Alarm Dependent Type" * In the case of "High-priority" and "On Alarm Dependent Type"
1.Blink stops by [Ack] button. 1.Blink stops by [Ack] button.
2. All messages are deleted when all alarms from the same tag have been reset.
2. All messages are deleted when all alarms from the same tag have been reset.
NR message isn't displayed.
3. Example in which all alarms are reset without the acknowledgement.

Only the selected message is deleted by [Ack] button.
3. Example in which all alarms are reset without the acknowledgement. (the pair of alarm/reset is reset at the same time)
All messages are deleted by the acknowledgement for one.
NR message without buzzer sound.

CAMS for HIS cannot handle the NR message because the NR message is generated
based on TAG, not alarm source.
Therefore, it is recommended that "Notification at Return Type" isn't defined.

The behavior when acknowledged Process Alarm Messages recover
The messages are deleted automatically when these alarm messages have been In the case of "CENTUM Original", the messages are deleted automatically
acknowledged and recovered. when these messages have been acknowledged and recovered.
(NR is output when "Notification at Return Type" has been defined.) In the case of "Consolidated", the messages are not deleted automatically.
In the case of "Consolidated" and "Auto Clear" is defined for each alarm source,
the acknowledged messages are deleted automatically when they have been recovered.
Auto Clear can be defined on

CAMS for HIS Alarm builder
Alarms recover 1. Blink stops by [Ack] button.
2. Only the alarm messages by which "Auto Clear" has been defined are deleted
automatically after the acknowledgement.
Process Value Display of Process Alarm Messages
"Display" or "Not display" of process value can be switched. There is no switching button. Process value is always displayed.

Operations to expand from a tag or a message
The Process Alarm view displays the result of filtered messages by the tag name. The function to filter the messages by the tag name is not available.
Only the alarm messages of selected tag are displayed.

Ordinary Message monitor of CAMS for HIS is displayed.
The menu is displayed by clicking the right mouse button after selecting a message. The menu is displayed by clicking the right mouse button after selecting a message.
The menu is editable. The menu is not editable.

Acknowledgement and Deleting of Operation Guide Messages
Blink stops by [Ack] button. Blink stops by [Ack] button.

All acknowledged messages are deleted by [Delete] button.
Reset manually by [Manual Reset] button and delete it by [Ack] button.

The messages are deleted by clicking only [Manual Reset] button if "Auto Clear"
has been defined for these messages.
[Delete] after [Ack]
Manual Reset
Manual Reset
Ack (with Auto Clear)
Suppression for chattering messages
All unnecessary chattering messages are displayed. Suppresses the repeated A&E messages after displaying the first 10 messages.

Appendix3. Sample User specification for Tokuchu DLL
------------------------------------------------------------------------------------------------- ------------------------------------------
User Requirement Specification for;
CAMS for HIS OPC A&E Message Integration Library for
xxx A&E Server
Rev Issue Date Description DR. CHK. APP.
1. General
This document describes user requirement specification for the Tokuchu Library which is to
integrate xxx OPC A&E server and CAMS for HIS.
2. Alarm & Events to be integrated

The CAMS for HIS receives all categories of alarms & events from xxx OPC A&E server.
Refer table 2 for the classification of the alarms & events.
3. Alarm Appearance
Alarms from xxx OPC A&E Server appear in CAMS for HIS with following format.
3.1 Tag Mark and Color

Table 1 Tag Mark and Color
Tag Mark Color Status
Red
Alarm occurrence
(blinking)
Red (static) Acknowledge
Green Reset (Recover)
3.2 Alarm Condition Transition
The condition of CAMS alarm shall follow to the status of xxx OPC alarms & events.
Table 2 Alarm Condition convention

OPC A&E Status CAMS Alarm Status CAMS Alarm Priority
Inactive & Enabled RECOVER Low
Active & Enabled ALARM Depends on the severity (Refer to Table 3)
Disabled (No display) Reference
** CAMS does not care of Acknowledge state of OPC A&E. Acknowledge state will be
managed independently between Yokogawa HIS and other system.

4. CAMS Alarm Attributions

The table below describes correspondence between Source information (Attributions in xxx OPC
A&E) and Attributions of CAMS for HIS.
Table 3 CAMS Alarm Attributions

CAMS Alarm Source of Value Remarks
Attribution
TimeStamp [Time] (xxx OPC A&E)
Message [Message] (xxx OPC A&E)
Message.Buzzer If the CAMS Alarm Status is RECOVER, the parameter Buzzer number
Message.Buzzer is always set to 0. If the CAMS Alarm Status is assignment shall
ALARM, the following definitions apply. be configurable.
AlarmPriority (CAMS) Message.Buzzer (CAMS)

Critical 4 (Process Alarm High Priority)
High 4 (Process Alarm High Priority)
Medium 5 (Process Alarm Medium Priority)
Low 6 (Process Alarm Low Priority)
Reference 0 (No Buzzer)
MessageNo (Null)
TypeOfAlarm Type (xxx OPC A&E) TypeOfAlarm (CAMS) .
System Alarm (ALARM_TYPEOFALARM_SYSTEM)
Process Alarm (ALARM_TYPEOFALARM_PROCESS)
Source Source is a key

attribute to
identify an alarm
source.
A pair of
ALARM and
RECOVER for the
same source is
available.
Source.Plant
TagName Should be
limited to the last
16 characters of
the field, if it is
longer as 16
characters.
AlarmPriority [Severity] (xxx OPC A&E) AlarmPriority (CAMS) Severity
801-1000 Critical (ALARM_PRIORITY_CRITICAL) assignment shall
601-800 High (ALARM_PRIORITY_HIGH) be configurable.
401-600 Medium (ALARM_PRIORITY_MEDIUM)
1-400 Low (ALARM_PRIORITY_LOW)
- Reference (ALARM_PRIORITY_REFERENCE)

5. Restrictions
The CAMS (OPC A&E client) cannot set filter criteria for the OPCEventSubscription object,
which means that the CAMS receives all alarms and events from xxx OPC A&E.
(A filtering function on the CAMS message monitor is available after the CAMS receives
messages.)
The CAMS isnt able to transfer the status of acknowledgement to xxx OPC A&E.
6. Non-Functional Requirement
Performance: Processing time per one message shall be less than 1.0 [ms].
Do not use asynchronous processing or multi-threading within DLL.
Do not allocate more than 1 [MB] memory.
7. Others
The Subscription parameters of CAMS OPC Client are fixed as follows;
Buffer Time (msec): 0

Max Size: 1
If necessary, changing these values is available by Tokuchu.
-----------------------------------------------------------------------------------------------------------------------------------------

Revision History
Rev Issued Date Description
0 2009/10/19 First issue
1 2010/04/23 Second edition
P1 Contents page revised.
P2 Description of Ordering CAMS for HIS Package revised.
P3 Notes added.
P4 Description added.
P20 Description of Equalization scope added.
P23 Description added.
P25~26 Description of Alarm Suppression Design and Filter Design added.
P36~38 Pictures replaced.
P42~45 Appendix1 added.
2 2010/06/30 3rd edition
P45 Files other than the text file arent equalized added
3 2013/06/28 4th edition
Thoroughly revised, Section9,10,11 and Appendix2 added.
4 2014/04/25 5th edition
Corresponding to R5.03.20 P4 ~7, P9,P23,P24,P29, P31,P34,P43~47, P57~60 Description
added
5 2014/10/15 6th edition
P58 Illustration replaced.
P60 Reference page for sample URS for Tokuchu DLL added.
P79~81 Appendix3 added.
6 2015/02/25 7th edition
P23 Correction of erroneous description: inhabitation -> suppression & shelving
The information which is equalized when restarting HIS added.
P56~57 "How to create Alarm source list file (CSV) manually by using CENTUM VP
Database Convert function" added.
2015/05/22 8th edition
P4 The behavior on and after R5.04 has been added to "Process Value display of the process
alarm message".
P31 The behavior on and after R6.01.10 has been added.
P43~46 Name change
Notification buffer Notification FIFO buffer
Forwarded Packet buffer Forwarded Packet FIFO buffer
P47 Section 7.6 added.

Cams

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cams

Uploaded by

Copyright:

Available Formats

CENTUM CS 3000 & CENTUM VP ENGINEERING GUIDE

CAMS for HIS Engineering Guide

Rev 7.0 ESS-CDWG-S611-021501E Page 1 of 84

9.3 Display on Historical Viewer of CAMS for HIS ................................................................................ 53

Rev 7.0 ESS-CDWG-S611-021501E Page 2 of 84

1 Requirement Items for CAMS for HIS

1.1 Hardware Environment

[CS 3000 System]

1.2 Software Environment

1.3 Ordering CAMS for HIS Package

Rev 7.0 ESS-CDWG-S611-021501E Page 3 of 84

2 Important Notes when CAMS for HIS is enabled

Operation screen mode of CAMS for HIS Message monitor

Process Value display of the process alarm message

There is no function of this button on the

Operation Guide Message

A line break and specified color will be shown in

Rev 7.0 ESS-CDWG-S611-021501E Page 4 of 84

The "Green" color message disappears

Mode Select Key Switch on Operation Keyboard

Alarm Status Display under Alarm inhibition

Rev 7.0 ESS-CDWG-S611-021501E Page 5 of 84

When CAMS for HIS is enabled:

When CAMS for HIS is disabled:

Alarm Priority and Acknowledgement of Process Alarm message

Rev 7.0 ESS-CDWG-S611-021501E Page 6 of 84

Extent of the impact by acknowledgement of System alarm and Operator Guidance

Suppression of repeated alarm messages

Definition on CAMS for HIS Alarm builder

Displayed with original color.

Display on CAMS for HIS Message monitor

Rev 7.0 ESS-CDWG-S611-021501E Page 7 of 84

System Basic Design

CAMS for HIS Message monitor Design

Creation of Function blocks

Import Tag database

CAMS Function Configuration

Rev 7.0 ESS-CDWG-S611-021501E Page 8 of 84

4 System Basic Design

4.1 System Configuration

Rev 7.0 ESS-CDWG-S611-021501E Page 9 of 84

Project Name: CAMSDEMO

Operation and Maintenance Group Maintence Group for a project

Engineers Group Maintenance Group

Operation Group Operation Group

HIS0161 HIS0162 HIS0163 HIS0150 HIS0151

FCS FCS FCS FCS FCS

AREA 01 Utility AREA 02

Plant 011 Plant 012 Plant 021

Unit 11A Unit 11B Unit12A Unit UT Unit 21A Unit21B

AREA01 Supervisors Group AREA02 Operator Group

AREA01 Operator Group AREA02 Operator Group

Rev 7.0 ESS-CDWG-S611-021501E Page 10 of 84

4.2 Plant Hierarchy

Site Area Process Cell Unit Equipment Element

UNIT011A TAG-A (PID)

UNIT011B TAG-B (PID)

PLANT012 UNIT012A TAG-C (PID)

UTILITY UNIT_UT TAG-D (PID)

UNIT021A TAG-E (PID)

UNIT021B TAG-F (PID)

Rev 7.0 ESS-CDWG-S611-021501E Page 11 of 84

4.3 Security Policy

HIS Security Policy