K Chief 700

Kongsberg Functional Design Document
(KFDD)
Common System
Project: 99999
Product: K-Chief 700
Loctation:
Synopsis: This document describes the Common System
Document Number: Revision: A
Customer doc no. Document version: 2.0
Contract number: Number of pages: 122
A 01.12.12 AsBuilt AA BBB CCC
©Kongsberg Maritime Page 1 of 122
www.kongsberg.com
Document history
Revision Description of Change

A As Built
References
No Doc No Description
1 1122333 System Topology IAS
2 Alarm and Instrument List Machinery
3 Alarm and Instrument List Cargo
Copyright
The information contained in this document remains the sole property of Kongsberg Maritime AS. No
part of this document may be copied or reproduced in any form or by any means, and the information
contained within it is not to be communicated to a third party, without the prior written consent of
Kongsberg Maritime AS.
Disclaimer
Kongsberg Maritime AS endeavours to ensure that all information in this document is correct and fairly
stated, but does not accept liability for any errors or omissions.
www.kongsberg.com
Table of contents
1 Introduction ......................................................................................................... 13
1.1 Purpose .................................................................................................................. 13
2 Software package ................................................................................................. 14
3 System overview................................................................................................... 15
3.1 The Integrated Automation System ....................................................................... 15
4 Project Specific Configuration ........................................................................... 17

4.1 Configuration Set-up Operator Stations (OS) ....................................................... 17
4.1.1 Storage / Load Source of the RCU ................................................................... 19
4.1.2 Alarm Printers and Display Printers ................................................................. 19
4.2 Configuration Set-up Field Station (RCU) ............................................................ 21
4.3 Configuration Set-up Network Distribution Unit (NDU) ..................................... 23
Operator Panel ............................................................................................................ 24
5.1 IAS Main Tasks ..................................................................................................... 24
5.2 Configuration Set-up Users and Groups................................................................ 25
5.2.1 Login and access system ................................................................................... 25
5.3 Images & Command Groups ................................................................................. 29
5.4 Configuration Set-up OS and Command Groups .................................................. 30
5.5 System vs Watch Call / Command Group / Alarm Panel Group .......................... 34
5.5.1 Watch Call Groups ........................................................................................... 36
Master / Slave pairs:........................................................................................................ 37
5.6 PS description ........................................................................................................ 38
5.6.1 PS interface topology........................................................................................ 38
5.7 Event System ......................................................................................................... 39
5.8 Configuration History............................................................................................ 40
5.9 History Station ....................................................................................................... 41
5.10 Configuration Set-up Reports ................................................................................ 41
5.11 Configuration Set-up Trend ................................................................................... 42
5.12 Alarm extension system ........................................................................................ 43
5.13 Functional Description .......................................................................................... 46
5.13.1 Introduction ............................................................................................. 46
5.13.2 Panel Operation ....................................................................................... 48
Panel Overview ............................................................................................................... 50
5.14 Engine Patrol Man System .................................................................................... 55
www.kongsberg.com
6 Apendix 1 ). .......................................................................................................... 58
7 KM Standard colour definition .......................................................................... 58

Colour table..................................................................................................................... 58
8 K-Chief 700 .......................................................................................................... 58

8.1 AIM Environment ................................................................................................. 60
8.2 Distributed Control System ................................................................................... 60
8.2.1 FS – Field Station ............................................................................................. 61
8.2.2 OS – Operation Station ..................................................................................... 61
8.2.3 HS – History Station ......................................................................................... 62
8.2.4 Alarm/Event Printer .......................................................................................... 62
8.3 Communication ..................................................................................................... 62
8.4 Using K-Chief 700 ................................................................................................ 66
8.4.1 Starting and Stopping K-Chief 700 .................................................................. 66
8.4.2 Running K-Chief 700 ....................................................................................... 66
8.4.3 Users Guide/ F1 Help function. ........................................................................ 67
8.4.4 Analysis of K-Chief 700 ................................................................................... 67
9 Operator Stations ................................................................................................ 68

9.1 Main Features ........................................................................................................ 68
9.2 Logging On ............................................................................................................ 68
9.3 Images and Navigation .......................................................................................... 68
9.4 Access Control....................................................................................................... 68
9.5 Command Control ................................................................................................. 68
9.6 Process and Application Control ........................................................................... 68
9.7 Tag Mark Indication .............................................................................................. 69
9.8 Configuration Set-Up OS’s ................................................................................... 70
9.8.1 Storage / Load Source of the RCU ................................................................... 70
9.8.2 Alarm Kit .......................................................................................................... 70
9.9 Clock distribution system ...................................................................................... 70
10 History Station ..................................................................................................... 71

10.1 Main Features Rapid K-Chief-HS ......................................................................... 71
10.1.1 K-Chief-HS Description .......................................................................... 71
10.1.2 K-Chief-HS Configuration ...................................................................... 72
10.1.3 K-Chief-HS Storage ................................................................................ 73
10.1.4 K-Chief-HS Retrieve from OS in Trend ................................................. 73
10.1.5 Initializing of K-Chief-HS Databases ..................................................... 74
www.kongsberg.com
10.1.6 User Interface .......................................................................................... 74
11 Field Stations ........................................................................................................ 75

11.1 Main Features ........................................................................................................ 75
11.2 Modes of Operation ............................................................................................... 76
11.2.1 Normal Operation .................................................................................... 76
11.2.2 RCU Exceptional Modes ......................................................................... 76
11.3 Redundancy Pairs .................................................................................................. 76
11.4 IO System .............................................................................................................. 76
11.4.1 Concept IO System.................................................................................. 78
11.4.1.1 Overview ................................................................................................. 78
11.4.1.2 Serial Process Bus ................................................................................... 78
11.4.1.3 Profibus Standard .................................................................................... 78
11.5 Configuration Set-up ............................................................................................. 79
12 Network Distribution Units ................................................................................ 80

12.1 Main Features ........................................................................................................ 80
12.2 Topology................................................................................................................ 80
13 Images and Navigation ........................................................................................ 82

13.1 Main Features ........................................................................................................ 82
13.2 Image Types .......................................................................................................... 82
13.3 Image Window Types............................................................................................ 83
13.3.1 Primary Image Window .......................................................................... 84
13.3.2 Secondary Image Window ...................................................................... 84
13.3.3 Floating Image Window .......................................................................... 84
13.3.4 Navigation between Image Windows ..................................................... 85
13.4 Image Navigation .................................................................................................. 85
13.4.1 Navigator ................................................................................................. 86
13.4.2 History Navigator .................................................................................... 86
13.4.3 Hotspots ................................................................................................... 86
13.4.4 Operator Panel ......................................................................................... 86
14 Access Control System ........................................................................................ 87

14.1 Main Features ........................................................................................................ 87
14.2 User Rights ............................................................................................................ 88
14.3 Configuration Set-up Users ................................................................................... 90
www.kongsberg.com
15 Command Control System.................................................................................. 91
15.1 Main Features ........................................................................................................ 91
15.2 Command Groups .................................................................................................. 91
15.3 OS Groups ............................................................................................................. 91
15.3.1 OS Groups in Command of a Group ....................................................... 92
15.3.2 Privileges ................................................................................................. 92
15.3.3 Alarm Conditions .................................................................................... 92
15.4 Obtain, Lose and Transfer Command ................................................................... 92
15.5 Configuration Set-up OS and Command Groups .................................................. 93
16 Version Control System ...................................................................................... 94

16.1 Main Features ........................................................................................................ 94
16.2 Version Control System and Environment ............................................................ 94
16.3 Registration of Configuration Events .................................................................... 95
16.3.1 Event Logged in the Configuration Event DB(s) .................................... 95
16.4 Version Control Backup ........................................................................................ 97
16.5 Version Control Restore ........................................................................................ 98
16.6 Import of RCU Configuration Files ...................................................................... 98
16.7 User Interface ........................................................................................................ 99
16.7.1 Availability .............................................................................................. 99
16.7.2 Main Menu Commands and Dialog Boxes ............................................. 99
16.7.3 Context Menu .......................................................................................... 99
17 Event System ...................................................................................................... 100

17.1 Main Features ...................................................................................................... 100
17.2 Event Attributes ................................................................................................... 101
17.3 ‘Alarm State’ and ‘Acknowledge State’.............................................................. 101
17.4 Alarm Limits ....................................................................................................... 102
17.5 Alarm Changes .................................................................................................... 103
17.6 Alarm Priorities ................................................................................................... 104
17.7 Alarm Suppression .............................................................................................. 105
17.8 Alarm Acknowledgement .................................................................................... 105
17.8.1 Acknowledgement Authority ................................................................ 106
17.8.2 Acknowledge Methods .......................................................................... 106
17.8.3 Selection of Alarm for Acknowledgement............................................ 106
17.8.4 Shelving Alarms .................................................................................... 106
www.kongsberg.com
17.9 Alarm Groups ...................................................................................................... 107
17.9.1 Purpose .................................................................................................. 107
17.9.1.1 Terminology .......................................................................................... 107
17.9.1.2 Group types and intended use ............................................................... 107
17.9.1.3 First up................................................................................................... 107
17.9.1.4 Group ..................................................................................................... 108
17.9.1.5 Logical ................................................................................................... 108
17.9.1.6 Aggregated ............................................................................................ 108
17.9.1.7 The Verification Process ....................................................................... 108
18 Time Series System ............................................................................................ 111

18.1 Main Features ...................................................................................................... 111
18.2 Time Series .......................................................................................................... 111
18.3 Data Sources ........................................................................................................ 112
18.3.1 Input and Data Source ........................................................................... 112
18.3.2 RCU Resident Data Sources ................................................................. 113
18.3.3 External Data Sources ........................................................................... 113
18.4 Time Series Categories ........................................................................................ 114
18.4.1 RCU Primary Time Series..................................................................... 114
18.4.2 RCU Secondary Time Series................................................................. 114
18.4.3 HS Primary Time Series ........................................................................ 115
18.4.4 HS Secondary Time Series .................................................................... 115
18.5 Time Series Definition ........................................................................................ 116
19 Trend System ..................................................................................................... 117

19.1 Trends .................................................................................................................. 117
19.1.1 Trend Presentations ............................................................................... 117
19.1.2 Trend Types........................................................................................... 117
19.1.3 Trend Data Sources ............................................................................... 117
19.1.4 Dynamic and Static Modes ................................................................... 118
19.2 Configuration Set-up ........................................................................................... 118
20 Report System .................................................................................................... 119

20.1 Report Mechanism............................................................................................... 119
20.1.1 Overview ............................................................................................... 119
20.1.2 Prepared Reports and Generated Reports.............................................. 119
20.1.3 Triggering Report Generation ............................................................... 120
www.kongsberg.com
20.1.4 Report Management .............................................................................. 121
20.1.5 Displaying Reports ................................................................................ 121
20.1.6 Report Print-out ..................................................................................... 121
20.1.7 Report Storage ....................................................................................... 121
20.1.8 Report Types ......................................................................................... 121
20.2 Configuration Set-up ........................................................................................... 122
www.kongsberg.com
Definitions / Abbreviations
Function Module
The function module is the main building block of the control application residing on the RCU. A
function module is a self-contained software automation object. Function modules represent either:
Process devices, process control functions or system functions.
Function modules are connected to each other and to field signals to make up a software model of the
controlled process. Within a scan, function module algorithms are executed in a strict order.
Users can interact with function modules in many ways. The function module provides dialogs for
operation, parameterization and mode selection.
The environment for function module execution is the RCU on which the function module instance is
configured. However, both the RCU mode and the function module mode may affect the execution of a
function module.
Under normal processing, the function module algorithm is executed cyclically according to the RCU
scan task. Within a single scan, the function module (in sequence):
- Reads data from the input terminals

- Checks for input alarms
- Executes the algorithm
- Checks for output alarm
- Writes data to the output terminals
The function modules plcsm and plclg, referred to as flexi-modules, have no predefined algorithm but
provides advanced arithmetic functions and manipulation of analogue data which is possible to design for
the instance. It is rather a toolbox comprising a large number of analogue- and digital elements which can
be combined together to perform a complex logic function, which is specific for the instance.
A function module communicates with other function modules and the I/O system via input / output
terminals.
www.kongsberg.com
Control Function
A control function is a software cluster consisting of one or more function modules and designed to
represent part of- or a complete system. A control function communicates with other control functions
and the I/O system via input / output terminals.
Part of a system can be an analogue measurement, a valve, a motor starter, etc.
Systems can be two or three pumps in a duty / standby configuration, a complete diesel engine interface, a
complete VSD interface, etc.
Terminal
A terminal is the communication channels towards other function modules and the I/O system.
Terminals are used to transfer operational values between function modules and between the function
modules and the VMS environment.
The digital and analogue input and output terminals may be configured with alarm, numerical
value representation, bar graphs, as part of trend pages, reports, etc. The process terminals are a
“data highway” between function modules to exchange large amount of pre-defined sets of
operational values.
Each type of function modules has a set of terminals.
Terminal Connection
A terminal connection is two function modules, connected together, to enable exchange of data between
these function modules.
www.kongsberg.com
Scan Task
The scan task is a cyclic RCU task that runs the algorithms of a number of function modules in a defined
sequence. Two scan tasks are normally defined for control purposes:
- Scan task 1 (1Hz)

- Scan task 2 (10Hz)
Scan task 2 is used for the power management system, thruster control system and where servo loops are
within the ICMS. All other interfaces are normally configured as members of scan task 1.
Abbreviations
ACK Acknowledge
AI Analogue Input
AO Analogue Output
CCR Cargo Control Room
CTS Custody Transfer System
DB Database
DG Diesel Generator
DI Digital Input
DO Digital Output
ER Engine Room
EER Electrical Equipment Room
ECR Engine Control Room
ESD Emergency Shutdown
F&G Fire and Gas
FO Fuel oil
GCU Gas Combustion Unit
HD High Duty Compressor
HS History Station
HT High Temperature
www.kongsberg.com
HV High voltage (6.6 kV systems)
I/O Input / output
IAS Integrated Automation System
IG Inert Gas
IP Internet Protocol
KM Kongsberg Maritime
LAN Local Area Network
LD Low Duty Compressor
LNG Liquefied Natural Gas
LO Lubrication oil
LV Low Voltage (440V / 220 V systems)
MCC Motor Control Centre
MV Main Vaporizer
NDU Net Distribution Unit
OS Operator Station
PCU Process Control Unit
PMS Power Management System
PS Process Station, Process Control Cabinet
RCU Remote Control Unit
SG Steering Gear
SW Sea water
VDU Video Display Unit
www.kongsberg.com
1 Introduction
1.1 Purpose
This Kongsberg Functional Design Document describes the basic components and functionality of the
Kongsberg Maritime Integrated Control System ICS as to be delivered.
www.kongsberg.com
2 Software package
KONGSBERG vessel control system K-Chief 700 has the following software package installed:
 Microsoft Windows XP Professional

 Microsoft Windows XP service pack 3
 Kongsberg Maritime AIM-2000 Version 8.3.12
www.kongsberg.com
3 System overview
3.1 The Integrated Automation System

The system topology with all Field Stations, Operator Stations and auxiliary cabinets are shown in the
topology drawing “Reference [1]”.
The integrated automation system (IAS) communicates by means of redundant high speed network.
Compared to conventional stand alone controllers and alarm panels the Integrated Automation System
concept offers several advantages such as:
Increased safety due to
 Redundant communication network
 Stand-alone operator stations
 Distributed process control stations
 No main computer
 Modular fail-safe hardware
 On-line diagnostic functions
 Supervision of sensor interfaces
 Supervision of machinery operation
Cost effective due to
 Reduction of sensor cabling
 Reduction of interface problems
 Eliminates conventional hard-wired consoles / mimics and reduces control room area requirements
 On-line configuration reduces dead time during installation
 Reduction in spare part requirement
 One supplier providing service for the entire control system
 Fuel optimising by integration of dynamic positioning, thruster control and power management
systems
www.kongsberg.com
Simple operation due to
 Process oriented man-machine communication
 Purpose-built keyboard
 Uniform operator stations
Flexibility due to
 Easy expansion of existing system
 Built-in on-line configuration tool
 Process simulation
www.kongsberg.com
4 Project Specific Configuration
4.1 Configuration Set-up Operator Stations (OS)
Table showing operator stations details:
OS Name Location OS Type Flat Screen Extras

K-Chief-OS-31 CCR MP7900 23” Event printer: Yes
(172.23.101.31) Alarm kit: No
Keyboard: Yes
Sycon and Profibus: Yes
Version Contol: Yes
Dual Power: Yes
K-Chief-OS-32 CCR MP7900 23” Event printer: No
(172.23.101.32) Alarm kit: No
Keyboard: Yes
Sycon and Profibus: No
Version Contol: No
Dual Power: Yes
(172.23.101.33) Alarm kit: No
Keyboard: Yes
Version Contol: No
Dual Power: Yes
(172.23.101.34) Alarm kit: No
Keyboard: Yes
Version Contol: No
Dual Power: Yes
K-Chief-OS-35 CCR/CTS MP7900 23” Event printer: No
(172.23.101.35) Alarm kit: No
Keyboard: Yes
Version Contol: No
Dual Power: Yes
K-Chief-OS-98 EER “HS - Server” History Station with Rapid Db, SQL
(172.23.101.98) Server 2005 EventDb and
ConfigEventDb
www.kongsberg.com
OS Name Location OS Type Flat Screen Extras
K-Chief-OS-41 ECR MP7900 23” Event printer: No
(172.23.101.41) Alarm kit: No
Keyboard: Yes
Version Contol: No
Dual Power: Yes
(172.23.101.42) Alarm kit: No
Keyboard: Yes
Version Contol: No
Dual Power: Yes
CAN Bus: Yes
(172.23.101.43) Alarm kit: No
Keyboard: Yes
Version Contol: No
Dual Power: Yes
CAN Bus: Yes
K-Chief-OS-44 ECR MP7900 23” Event printer: Yes
(172.23.101.44) Alarm kit: No
Keyboard: Yes
Version Contol: No
Dual Power: Yes
K-Chief-OS-51 CBC MP7900 23” Event printer: No
(172.23.101.51) Alarm kit: No
Keyboard: Yes
Version Contol: No
Dual Power: Yes
Table 4-1 Operator Panel
www.kongsberg.com
4.1.1 Storage / Load Source of the RCU
Table showing operator stations configured to be RCU servers for PS/IO configuration files:
OS Name Serves RCU PS/IO Configurations files.

K-Chief-OS-31 All
K-Chief-OS-32 All
K-Chief-OS-41 All
K-Chief-OS-42 All
K-Chief-OS-51 All
Table 4-2 Storage
4.1.2 Alarm Printers and Display Printers

Local printers print alarms / Events continuously as they appear.
Printer type Location Station Filter Type
Matrix LX-300+II CCS OS31 Alarms
Matrix LX-300+II ECR OS44 Alarms
Table 4-3 Printer
Different filters are made, and can be configured, to print only selected items.
Printer Filter Made Selectable :
Printer Filter Name Command Group Description
AlarmPrinterECR Power, Machinery, FOTransf, Common, Print only Alarms.

System
AlarmPrinterCCR Ballast, Cargo, HDCompHeat, Navigation, Print only Alarms.

Fire&Gas, CTS, Common, System
Table 4-4 Printer
www.kongsberg.com
Net printers can prints all types of views on requests. Also screen dumps are possible.
Printer type Location Station with access to net printer
Hard copy printer CCR All operator stations. IP address 172.20.201.2
HP Color LaserJet
Enterprise CP4025dn.
Hard copy printer?? HP ECR All operator stations. IP address 172.20.201.4

HP Color LaserJet
Enterprise CP4025dn.
Table 4-5 Printer
www.kongsberg.com
4.2 Configuration Set-up Field Station (RCU)
This table defines the main lines in the distribution of signals in the different process cabinets.
Signal distribution.
Field Cabinet Type Location PCU: Distributed Systems:

Station
Name
FS-31 PS 400 – R1 EER PCU 31 - HD1 Comp Mtr, LD1 Comp Mtr, BowThr
/131 Mtr. 1C Tk N2 vlv and IS/IBS temp, 3C Tk
N2 vlv and IS/IBS temp, Deck Machinery,
IGG
FS-32 PS 400 – R1 EER PCU 32 - Ballast, FO, MDO,
/132
FS-33 PS 400 – R1 EER PCU 33 - Cargo, 2C Tk N2 vlv and IS/IBS temp, 4C Tk

/133 N2 vlv and IS/IBS
FS-34 PS 400 – R1 EER PCU 34 - HD2 Comp Mtr, LD2 Comp Mtr Cargo,
/134 Cargo Machinery
FS-35 PS 400 – R1 EER PCU - ESDS

35/135
FS-36 EER PCU 90 - CTS (KM Trondheim supply)

/190
FS-41 PS 400 – R1 ECR PCU 41 - No 2,3 and 4 Boiler W circ. PP

/141, 47, 48 - Machinery Misc.
- Patrol man sys.
- No1 & 2 Prop LO PP
- MGE 2 and 4 Pilot feed P/P,
- MGE 2 and 4 Priming LO P/P
- MGE 1 & 2
- DG 1 & 2, LV SWBD
- Propulsion
FS-42 PS 400 – R1 ECR PCU 42 - MSB2
/142, 49, 50 - Mach Valves
- MGE 3 & 4
- No2 & 4 Propulsion Alarms
- Machinery Misc
FS-43 PS 240C – R1 E/R 2nd Deck PCU 43 - HV SVBD, LV SVBD, Machinery Fans, Aux
/143 Boiler, Main Sea Water Cooling, FO Transfer
FS-44 PS 240C – R1 E/R 4th Deck PCU 44 - No 2,3 and 4 Boiler W circ. PP.DG 1 & 2,
/144 FO System, Main prop. winding temp.
www.kongsberg.com
Field Cabinet Type Location PCU: Distributed Systems:
Station
Name
FS-45 PS 240C – R1 E/R 4th Deck PCU 45 - DG 3 & 4, FO System

/145
FS-46 PS 240C – R1 E/R Floor Deck PCU 46 - Boiler circ pump,err bilge pump, sludge
/146 pump, No1 Main prop. winding temp.
FS-51 PS 120C – R1 PCU 51

- Gas Comp Control, Heater, vaporizer
FS-52 PS 120C – R1 PCU 52
- Gas Comp Control, Heater, vaporizer
FS-71 PS 400C – R1 E/R Floor Deck PCU - GCU (Hamworthy Supply)
71/171
Table 4-6 Field station
PS 400-R1: Cabinet for 400 number of IO, Redundant processor and power supply.
PS 240-R1: Cabinet for 240 number of IO, Redundant processor and power supply.
1. Spare I/O: RCU should run with a spare time of 45%+ and memory > 60%. RIO
modules/Field stations should have a spare IO-capacity of 20%.
2. Power: All power supplies are redundant.
3. 120 VAC: There are two 120 VAC sources of power running in redundant mode, with
alarms
4. CPU and I/O have the same Power supply. I/O is galvanic divided.
www.kongsberg.com
4.3 Configuration Set-up Network Distribution Unit
(NDU)
Table showing net distribution details:
NDU Name NDU Location Extra

NDU-A1 EER PDU1-1 (IP:172.21.200.1)
NDU-C1/B1 EER PDU2-2 (IP:172.20.200.1)(
IP:172.22.200.1)
NDU-B2 ECR PDU2-1 (IP:172.22.200.2)
NDU-A2 ECR PDU1-2 (IP:172.21.200.2)
Table 4-7 NDU
1. Max. network load should not exceed 40% under most extreme circumstances.
2. On operator stations in IAS there is a Net Status Page. The network is continuously monitored
and system alarms will come up in alarm line.
www.kongsberg.com
5 Configuration Set-up MIMIC (Image Tree)
Operator Panel
Definition of IAS keyboard layout.
Keyboard Layout:
HOME Steam Wartsila R.G

MACHINERY BILGE
Ballast Propulsion
PAGE System UCP Temp
POWER MGE1 MGE2 MGE3 MGE4 F.O Syst. F.O Syst.

Port Stbd
GAS N2
CARGO CTS IGG GCU ESD
MANAG .
FIRE Nav. PATROL

BALLAST & SYSTEM Prev . Next
System MAN
GAS
Table 7-8 Operator Panel
5.1 IAS Main Tasks
The main tasks of the IAS are as follows:
 Cargo control system

 Gas handling (compressors – heaters – vaporisers - GCU )
 Engine room alarm and monitoring
 Cargo system alarm and monitoring
 CTS system control and alarm
 ESDS control and alarm
 Alarm / event recording
 Alarm extension / patrol man system
 Power management system
 Auxiliary diesel engine control system
 Ballast control system
 Trend function
www.kongsberg.com
5.2 Configuration Set-up Users and Groups
5.2.1 Login and access system
When login into the K-Chief 700 operator stations a user name and password must be entered in order to
access the system. Each user is member of a user group, where access rights and user privilege is defined.
The following User Groups are configured:
User Group Description / Capability

Guests Members can only monitor the system.
Users Members can monitor and operate the system.
Power Users Members can monitor, operate and change parameters.
Administrators Members have full access to the system.
Table 7-9 Storage
The following users and user groups are defined:
User Password Member of user group
Guest Guest Guests
Operator Operator Users
Captain Power User
Chief Power User
Cryostar Override Cryostar Extended
System Administrators
Kongsberg Administrators
Table 7-10 Storage

Password is by default the same as user name, this can be changed by members of “Administrators”, and
additional users and user groups can be added (refer to the KM VC operator manual).
www.kongsberg.com
The following access rights and security levels are defined for the different user groups:
User Groups
Gate ID Permissions Description Guests Users Power Administrators

Users
Global_HS HS_Operation Enable HS operation. X X

Global_OS AlarmShelving_ProcessAlarms Permission to shelve or X X X
unshelve process alarms
AlarmShelving_SystemAlarms Permission to shelve or X X
unshelve system alarms
OSKCmdCtrlAcquire Users without this permission X X X
cannot have command control.
In the sense of Command
Control the OS is regarded as
dead.
OSKCmdCtr_ManuallyOverrideCommand X
Controll
OSKCmdCtrl_TakeForced Users without this permission X X X
cannot take command
controlled forced.
OSKEquipment_Configure In order to configure equipment X
system, the user must have this
permission and the OS must be
in configuration mode.
OSKOS_Configure Needed to be allowed to set the X X
OS in configure mode.
OSKOS_DisableLogOff Will disable the Logoff button in X
the Change User dialog
OSKOS_Exit Users without this permission X X X
cannot exit the OS.
OSKOS_Test Needed to be allowed to set the X
OS in test mode.
OSKTrend_UserDefined User without this permission X X X
cannot create and edit User
Defined Trend images
OskAccess_ConfigureGates Needed to add, modify and X
remove gates and which
permissions they control.
OskAccess_ConfigureOSes Needed to modify the local X
access control settings for each
OS.
OskAccess_ConfigurePermisions Needed to add, modify and X
remove permissions.
OskAccess_ConfigureUsergroups Needed to add, modify and X
remove usergroups and their
relationships to gates.
OskAccess_ConfigureUsers Needed to add, modify and X
remove users and their
relationships to usergroups.
OskAccess_ObserveConfiguration Needed to inspect the access X X
control configuration.
OSKEvent_AckProcessAlarm A user needs this permission in X X X
order to ack a process alarm.
OSKEvent_AckSystemAlarm A user needs this permission in X X X
order to ack a system alarm.
OSKEvent_ChangeFilter A user needs this permission in X X
order to change a filter.
OSKEvent_Configure A user needs this permission in X
order to configure the event
www.kongsberg.com
User Groups

Users
image grid.
OSKEvent_SelectFilter A user needs this permission in X X X
order to select a filter.
OSKEvent_UserLockFilter A user needs this permission in X
order to change a filter.
TS_Configure Create Time series with limited X X
life span.
TimeSystem_SetTime Needed to be allowed to change X X
system time.
TimeSystem_SetTimeZone Needed to be allowed to change X X X
time zone.
VersionControl_RestoreImportPCU Restore and import files from X
the PCU configuration archive.
VersionControl_ViewConfigurationEvents Permission to view configuration X X X
events dialog.
WatchCall_Configure Permission to change attributes X X
and qualifications of officers.
WatchCall_ManagePanels Permission to add and delete X
panels, and allocate panels to
officers.
WatchCall_Operate Permission to operate the watch X X X
call system
Global_PCU IO_BasicOperation Basic operations on IO system X
for loop checking purposes
IO_ExtendedOperation Extended operations on IO for X
parameter change purpose
IO_Operation Operations on IO system that X
do not affect process control.
IO_Service Service operations on IO X
system that may affect process
control.
PCU_Backup Permission to backup PCU. X X
PCU_SetPCUConfigurationMode Permission to set PCU X X
configuration mode.
PCU_TogglePCUModes Permission to toggle between X
the different exceptional modes
in the PCU Operation dialog.
Redundancy_OverruleObjects Permission to overrule error X X
objects.
Redundancy_SwitchMaster Permission to switch Master X X
PCU in the Redundant Stations
dialog.
ModuleGate000 AlarmLimits_EditAlarmConfig Edit access to the Alarm Limit X X

dialog.
AlarmLimits_ReadAlarmLimits Permission to view the Alarm X X
Limits dialog.
AlarmLimits_WriteAlarmLH Permission to change LH Alarm X X
Limits.
AlarmLimits_WriteAlarmLLHH Permission to change LLHH X X
Alarm Limits.
ModuleOperation_Operate Write access to Module X X X
Operation dialogs.
ModuleOperation_ReadParameterFree Read free parameters in module X X X
parameter view.
www.kongsberg.com
User Groups

Users
ModuleOperation_ReadParameterLimited Read limited parameters in X X X

module parameter view.
ModuleOperation_ReadParameterRestricted Read restricted parameters in X X X
ModuleOperation_ReadTerminalView Permission to view module X X X
terminal view dialog.
ModuleOperation_WriteParameterFree Write free parameters in module X X
parameter view.
ModuleOperation_WriteParameterLimited Write limited parameters in X X
ModuleOperation_WriteParameterRestricted Write restricted parameters in X X
ModuleOperation_WriteTerminalView Write terminal values in module X X
terminal view dialog.
ModuleOperation_ReadModuleMode Permission to view the Module X X X
Modes dialog.
ModuleOperation_WriteModuleMode Permission to write changes X X
from the Module Modes dialog.
OSKOS_Exit User without this permission X X
cannot exit the OS
OskEvent_SelectFilter A user needs this permission in X X
order to select a filter
Table 7-11 Storage

(*) “Set Time” function requires “OS configuration” mode enabled. When the master clock is
connected to the system, the “Set Time” and “SetTimeZone” functions will not be available.
(**) “TS Configure” enables creation of time series which “Expire on time” (i.e. limited life time).
Creation of permanent time series requires “RCU Configuration” mode enabled.
www.kongsberg.com
5.3 Images & Command Groups
Table shows relations between buttons / images / command groups.
Button label Image name Command Group
Ballast Ballast Ballast
Bilge Bilge ER Bilge
Cargo Cargo Plant Cargo
CTS CTS Main CTS
ESD ESD ESDS
Fire Gas Fire & Gas Fire&Gas
F.O. System Port Mach MGE FG Supply Port Machinery
F.O. System Stbd Mach MGE FG Supply Stbd Machinery
Gas Management Gas Management GasHandling
GCU Gas Combustion Unit GCU
IGG Mach IGG IGGenerator
Machinery Machinery Systems Machinery
MGE1-4 MGE1-4 Machinery
Nav. System Navigation Navigation
N2 Mach N2 Generator N2Generator
Patrol Man Patrol Man Common
Propulsion Propulsion Propulsion
Power Power Management Machinery
Steam System Mach Boiler Feed W Sys Machinery
System System Topology System
Wartsila UCP Wartsila UCP Status Alarm Machinery
N2 Gen N2 Gen N2 Gen
Table 7-12 Images & Command Groups
www.kongsberg.com
5.4 Configuration Set-up OS and Command Groups
The following Command Groups are configured:
Command Group No. Command Group Name

0 Common
1 Power
2 Propulsion
3 Machinery
4 Ballast
5 Cargo
6 Bilge
7 Fire&Gas
8 ESDS
9 System
10 FirePumps
11 CTS
12 N2 Generator
13 HDCompHeat
14 FO Transfer
15 GasHandling
16 IGGenerator
17 GCU
18 Navigation
Table 7-13 Commando Groups
* The Command Group Name must be in one word.
The operator stations will be defined in operator station groups. Several operator station groups can be
defined and these operator station groups will be set up with command control rights. This system will be
set up with the following operator station groups:
www.kongsberg.com
The following OS Groups are configured:
OS Group OS Member of OS Group

1. Bridge OS51
2. ECR OS41,OS42,OS43,OS44
3. CCR OS31,OS32,OS33,OS34,OS35
4. CTS OS35
5. Monitor NA
Table 7-14 OS Groups
Table showing operator stations in which operator station group:
OS HS/WCI Location Operator Station Group Display Remark
- Cargo Control Rm. CCR Single -

31
32 - Cargo Control Rm. CCR Single -
35 Cargo Control Rm. CTS Single -
41 Engine Control Rm. ECR Single -
42 WCI Engine Control Rm. ECR Single -
43 WCI Engine Control Rm. ECR Single -
44 Engine Control Rm. ECR Single -
51 - Wheelhouse Bridge Single -
91 - Cabin OS Monitor Single Cabin OS (Laptop)
98 HS Electric Equipment Room - Single Database for historical data storage.

No operation possibilities.
No screen connected.
Table 7-15 OS Groups

www.kongsberg.com
Table showing relations between OS Groups and Command Groups:
OS GROUPS Bridge CCR ECR CTS

Command Id Shared D T A D T A D T A D T A
Groups
Common 0 True X X X X X X X X X X X X
Power 1 False - - - - - - X X X - - -
Propulsion 2 False - - X - - - X X X - - -
Machinery 3 False - - - - - - X X X - -
Ballast 4 False - - - X X X - - X - - -
Cargo 5 False - - - X X X - - - - - X
Bilge 6 False - - - X X X - - X - - -
Fire & Gas 7 False X X X - - X - - - - - -
ESDS 8 False X X X - - X - - X - - -
SYSTEM 9 False X X X X X X X X X X X X
FirePumps 10 True X X X X X X X X X X X X
CTS 11 False - - - - - X - - - X X X
N2 Generator 12 False - - - X X X - - X - - -
HDCompHeat 13 False - - - X X X - - X - - -
FO Transfer 14 False - - - - - X X X X - - -
GasHandling 15 False - - X X X X - - X - X X
IG Generator 16 False - - - X X X - - X - - -
GCU 17 False - - - - - X X X X - - -
Navigation 18 False X X X X X
Table 7-16 OS Group privileges
 Commando Groups must be typed in one word in the SvcSysConf database.

Some definition must be clarified before the command group set-up is specified:
Explanation to the table above:
D – Default: An OS group will automatically try to take a default command group at start up, that is,
when the first OS in an OS group starts.
T – Take: An OS group can take the command over a command group, which is not under command of
any other OS groups. The command group must be acquirable.
A – Acquirable: The OS group must have this privilege for the command group in order to obtain the
command of it.
O – Display Command Groups: The Command Group will be displayed in the command control
overview dialog box.
www.kongsberg.com
Id: Identifier for the Command Groups, only for internal usage.
Shared: The Command Group can be under command of several OS groups simultaneously.
When a command transfer is done, this will be indicated on all operator stations in the ‘Message
Manager’ box.
www.kongsberg.com
5.5 System vs Watch Call / Command Group /
Alarm Panel Group
Table showing the System versus Watch Call, Command Group and Alarm Panel Group:
System WC Command Group Alarm Panel Group
Gas Handling GCU GasHandling Gas Management
Cargo Cargo Cargo Cargo
Bilge Machinery Machinery Bilge
CTS Cargo Cargo CTS
Navigation Navigation Navigation Nav.
1LVCSB Cargo Power Power
ESDS ESDS ESDS Cargo
CargoCompr Cargo GasHandling Gas Management
CargoMisc Cargo Cargo Cargo
2LVCSB Cargo Power Power
EM’CY DG Machinery Power Power
Power Machinery Power Power
Prop1 Machinery Machinery Machinery
Prop2 Machinery Machinery Machinery
MGE1 Machinery Power Power
1HVMSB Machinery Power Power
2HVMSB Machinery Power Power
1LVMSB Machinery Power Power
2LVMSB Machinery Power Power
www.kongsberg.com
System WC Command Group Alarm Panel Group
Cargo Cargo Cargo Cargo
CargoTank1 Cargo Cargo Cargo
CargoMachin Cargo Cargo Cargo
N2Gen Machinery N2Generator Machinery
Hamworthy GCU GasHandling Gas Management
Kyma Machinery Machinery Machinery
InertGas Cargo GasHandling Gas Management
SeaWater Machinery Machinery Machinery
Fire Fire & Gas Fire & Gas Fire & Gas
FreshWater Machinery Machinery Machinery
Machinery Machinery Machinery Machinery
Fans Machinery Machinery Machinery
CompAir Machinery Machinery Machinery
StGear Machinery Machinery Machinery
Fuel Oil Machinery Machinery Machinery
Cryo1 Machinery GasHandling Gas Management
Cryo2 Machinery GasHandling Gas Management
Ballast Cargo Ballast Cargo
System Machinery Machinery Machinery
Table 7-17 Command Group and Alarm Panel
www.kongsberg.com
5.5.1 Watch Call Groups
Extension panel alarm indicator Panel text
1 Machinery alarm *(1,16)
2 Cargo alarm *(2,8)
3 Navigation alarm *(3)
4 Fire&Gas *(4)
5 System *(5,100,110)
6 Dead man alarm *(6,7)
7 Repeat alarm
8 Unit Fail
Table 7-18 Watch Call groups

Software configuration WC group:
*1= Machinery
*2= Cargo
*3= Navigation
*4= Fire&Gas
*5= System (OS power fail, Earth fail,CPM fail)
*6= Dead man alarm
*7= Bridge watch alarm
*8= ESDS
*16= GCU
*100= System Error
*110= OS Alarm (Panel alarm)
www.kongsberg.com
Master / Slave pairs:
Process Station Master PCU Slave PCU
FS 31 31 131
FS 32 32 132
FS 33 33 133
FS 34 34 134
FS 35 35 135
FS 41 41 141
FS 42 42 142
FS 43 43 143
FS 44 44 144
FS 45 45 145
FS 46 46 146
FS 41 47 Single
FS 41 48 Single
FS 42 49 Single
FS 42 50 Single
FS 51 51 Single
FS 52 52 Single
FS 71 71 171
Table 7-19 Master/Slave
www.kongsberg.com
5.6 PS description
5.6.1 PS interface topology
The figure below show connection between KM - ABB switchboard, KM - ABB propulsion motor and
KM - Wärtsilä generator engine.
IAS Net B
IAS Net A
FS41 FS42 FS43

FS44 FS45
PMS2 PMS1
ProfiBus ProfiBus
HW HW
ABB ABB
PM 1 PM 2
HW HW
WECS WECS
(MGE1) Wärtsila¨ Wärtsila¨ (MGE3)
UCP 1 TCP TCP UCP 3
PLC PLC
HW HW
WECS WECS
(MGE2) Wärtsila¨ Wärtsila¨ (MGE4)
TCP TCP
UCP 2 UCP 4
PLC PLC
LV 1 RIO LV 1 RIO
SBBus SBBus
FS42-2(LM2) FS43-2(LM1)
HV 1 RIO SBBus HV 1 RIO

SBBus
FS42-1(HM2) FS43-1(HM1)
Table 7-20 PS interface
www.kongsberg.com
5.7 Event System
An event will be recorded if an alarm is triggered, a software component is operated or change of

component status is detected. All recorded events will be stored in the event database, or databases. The
operator station, or operator stations, set up with an event database will function as an event server. Other
operator stations will function as event viewers. The operator stations functioning as event viewers are
possible to set differently regarding which event server to access when requiring stored information. For
the event viewers ODBC protocol is used for accessing information stored on an event server. The IAS
network will be used for the data transmission.
Two of the operator stations will be set up as event servers: OS-34 and OS-41.
The other operator stations will be set up as viewers, refer the table.
OS Servers OS Viewers
HS-98 OS-42, OS-43, OS-44, OS-31, OS-32, OS-33, OS-34 and OS-35
Table 7-21 Event Server
www.kongsberg.com
5.8 Configuration History
Changes and configuration in module parameters will be stored in a database at operator station set up to
run the “Configuration Store” application. Configuration history can however be retrieved from any OS.
All save and backup of the RCU-files will be saved with a revision number. Old versions of the RCU-file
can be retrieved or checked towards an older or newer version.
Database Location Comment
OS-31 OS-31 is setup with the MS Visual Source Safe software for version
control of the RCU-files.
HS-98 And with the “Configuration Store” application.
All recorded config events will be stored in the config event

database. The operator station, or operator stations, set up with
an configevent database will function as an event server. Other
operator stations will function as event viewers. The operator
stations functioning as event viewers are possible to set
differently regarding which configevent server to access when
requiring stored information. For the configevent viewers
ODBC protocol is used for accessing information stored on a
configevent server. The IAS network will be used for the data
transmission.
Table 7-22 Config HS
www.kongsberg.com
5.9 History Station
History station is integrated in HS-98.
Reports:
The report system has possibilities for the following types of reports:
Daily report
This report uses dynamic process variables from the process station. It can be printed either cyclic or on
request.
Historic reports
This report uses data from history station. By specifying a certain time window data from time series can
be called and several mathematics functions can be used.
Mathematics functions available are:
- Period sum
- Period middle
- Period min
- Period max
Hour count reports.
This report is used to show running hours on equipment. It accumulates the running hours.
Following Measurements included:
- Pumps controlled from IAS

- Generators
5.10 Configuration Set-up Reports

The following reports will be made:
Report Name Report Type

Diesel Generators Interactive Report
Running Hours on all Main motors. Hour Count Report
Ballast Tanks Interactive Report
Potable Water Tanks Interactive Report
Fuel Oil Tanks Interactive Report
Suppressed/blocked Alarms Interactive Report
Table 7-23 Reports overview
www.kongsberg.com
OS Name Location Report Name Report Type
KM-OS All Locations. All Cyclic and Interactive reports
Table 7-24 Report Responsibility
5.11 Configuration Set-up Trend

The following reports will be made:
Trend Name Trend Type

PID Trend Trend for each PID Controller. Meas, Setpoint and
CmdOut
< Project Trend > “To be defined by owner. Or setup during
commissioning”
Table 7-25 Trend
www.kongsberg.com
5.12 Alarm extension system
The Alarm Extension system will alarm the engineer on duty in case of any monitored parameter exceeds
its set value, as monitored by the alarm & monitoring system. There are eight categories of alarms:
For each category the alarms will be routed to the engineer on duty.
I.e. cargo alarms will be routed to the cargo engineer on duty when the alarm extension system
for cargo is activated.
www.kongsberg.com
19 watch call panels are provided in the following locations:
Panel Panel Type Location Watch Call Qualification

no. Group no.
1 Main panel Bridge All
2 On Duty panel C/E’s Cabin (505), As Qualification Engine

Ext. Buzzer in Bed RM
3 On Duty panel 2/E’s Cabin (513) , Ext.Buzzer As Qualification Engine

in Bed RM
4 On Duty panel ETO’s Cabin (502), As Qualification Engine
5 On Duty panel Cargo Eng’s Cabin (517) As Qualification Cargo

Ext.Buzzer in Bed RM
6 On Duty panel Junior Eng (403), Ext.Buzzer in As Qualification Engine

Bed RM
7 On Duty panel C/O’s Cabin (512), As Qualification Multiple C/N

Ext. Buzzer in Bed RM
8 On Duty panel Captain’s Cabin (510) Ext. As Qualification Navigation

Buzzer in Bed RM
9 On Duty panel General Office (410) As Qualification Navigation
10 On Duty panel 2/O’s Cabin (411) As Qualification Navigation
11 On Duty panel 3/E’s Cabin (404) As Qualification Engine
12 On Duty panel 3/E’s Cabin (405) As Qualification Engine
13 On Duty panel V.M.T(A) Office (406), Master As Qualification Engine
14 On Duty panel V.M.T(B) Office (407), Chief As Qualification Engine

Eng
15 Public Conference Room (408) All
16 Public Gymnasium (328) All
17 Public Duty Mess Room (217) All
18 Public Officer’s Mess Room (212) All
19 Public Officer’s Receration Room (208) All
www.kongsberg.com
Table 7-26 Watch call Panel
www.kongsberg.com
All duty/cabin panels can be selected in one of the following duties and will receive alarms in accordance
with duty selection:
1. Engine
2. Cargo
3. Multiple (Engine/Cargo)
4. Navigation
6. Multiple (Cargo/Navigation)
5.13 Functional Description

5.13.1 Introduction
The ‘Alarm Extension’ system is basically an extension of the Event system for the IAS system and this
system has two main functions:
1. Alarm Extension – This is a group alarm status and on-duty officer indication facility with built-in
on-duty acceptance, fault indication and test facilities.
2. Officer Call – This is an individual and general calling facility for officers that can be
activated from selected vessel control locations.
The ‘Alarm Extension system comprises two kinds of panels:
1. Watch Bridge Unit (WBU)

2. Watch Cabin Unit (WCU)
The WBU and the WCU are units required by the classification society to run a vessel with unmanned
engine room.
The main functions of the WBU are to indicate engine room alarms on the bridge, to indicate and accept
the transfer of machine watch responsibility to and from the bridge.
The main functions of the WCU are to indicate alarms with buzzer and light in the cabins and the public
quarters of the engineer on duty while in bridge control.
www.kongsberg.com
The ‘Watch Call’ system is communicating with the operator stations located in ECR by a CAN Bus
Interface. Two operator stations are required and will work in a master/slave configuration, i.e. the
‘Watch Call’ system will be operating with only one operator station up running at the time. The ‘Watch
Call’ system can be managed from two different managing groups:
1. ECR Manager
2. CCR Manager
From the operator stations in ECR, duty engineer can be selected for ECR and the watch responsibility
can be requested transferred to and from bridge. From the operator stations in CCR duty officer for CCR
can be selected. Selecting/Changing duty officer must be done when watch responsibility is in ECR.
The ‘Alarm Extension panels’ will be set up to belong to a unit group. Three different main unit groups
are available:
1. Bridge Group
2. Officer Group
3. Public Group
For the officer group several groups can be defined, i.e. ‘OfficerGroup1’, ‘OfficerGroup2,
‘OfficerGroup3, and up to ‘OfficerGroup8’. The panels belonging to officer groups are defined as duty
panels while panels belonging to the public group are defined for installation in public quarters.
The officer groups will be set up with a ‘Duty Officer Qualification’, which defines the type of alarms the
panel will subscribe to. Two different types of ‘Duty Officer Qualification’ are available:
1. Machinery
2. Cargo
3. Navigation
The alarm groups defined in the system will be set up to belong to either machinery or cargo. When an
alarm is triggered in the system the ‘Alarm Extension Panel Interface’ application will read the alarm
group, check which group it is belonging to (engine or cargo) and then route the alarm to the correct duty
panel(s), to all public panels and the bridge panel if in bridge watch.
www.kongsberg.com
5.13.2 Panel Operation
1. Alarm acknowledge during wheelhouse watch mode
 Initially alarm will sound on bridge panel, on duty engineer panel and on public panels.
 Pressing the “Sound Off” button on a public panel will turn off the sound only on the panel
operated. Alarm indicator will continue to flicker until alarm is acknowledged, and then change to
a steady light. Indicator will be turned off when alarm condition is no longer present.
 Pressing the “Sound Off” button on the bridge panel will turn off the sound only on bridge panel.
Alarm indicator will continue to flicker until alarm is acknowledged, and then change to a steady
light. Indicator will be turned off when alarm condition is no longer present.
 Pressing the “Sound Off” button on the duty engineer panel will turn off the sound on duty panel
and public panels (Bridge panel must be silenced separately). Alarm indicator will continue to
flicker until alarm is acknowledged, and then change to a steady light. Indicator will be turned off
when alarm condition is no longer present.
 Operating the “Ack” function on OS in ECR (for machinery alarms) or the OS in CCR (for cargo
alarms), will silence all panels and give a steady alarm indication. Indicators will be turned off
when alarm condition is no longer present.
2. Alarm acknowledge during ECR/CCR watch mode
 Extension panels will only show alarm status. No sound device will be set off. For cabin panels
and bridge panel, it is selectable whether alarm status should be shown or not when no people are
on duty. This must be selected from the watch call interface on the operator station.
3. Duty engineer/officer selection
 To transfer machinery responsibility to bridge (bridge watch mode), the operator must first select
a duty engineer on duty from software panel on VDU. The duty lamp is activated on all panels.
Then the “Bridge watch” button is selected and buzzer/lamp is activated at bridge panel. Pressing
the “Bridge watch” button on bridge panel will accept the watch transfer and a lamp indicator will
indicate bridge watch mode. A transfer from bridge to ECR must be initiated from ECR;
buzzer/lamp is activated at bridge panel. Upon acceptance from bridge, watch responsibility is
transferred to ECR.
 If a duty engineer is selected from software panel on VDU, without transferring the watch
responsibility to the bridge (Harbour mode), alarms will be routed to duty engineer panel as well
as public panels. Repeat alarms and Personal alarms will be activated as normal during this
condition.
4. Engineer/Officer call from ECR/CCR
 Two types of call functions are supported, “Call Duty” or “Call all”.
 The “Call Duty” operation will activate buzzer/lamps on the designated duty engineer panel and
on public panels. The “Call Duty” button will not work unless a duty engineer is selected.
 Acknowledging the call on the designated duty engineer panel will silence all panels.
 Acknowledging the call on a public panel will silence that specific panel only. Indicator lamps
will continue to flicker on all panels.
 The “Call all” function is more of an emergency operation. Pressing the “Call all” button will
activate buzzer/lamp on all panels. Acknowledging the call on one engineer/officer panel will
silence that specific panel only. Acknowledging the call on a public panel will silence that
specific panel only.
www.kongsberg.com
5. Duty Engineer/Officer call from Wheelhouse
 Operating the “Call Duty” from bridge panel will activate buzzer/lamp on the selected duty
engineer panel and on public panels. Again, the “Call Duty” function requires that an
engineer/officer actually has been set on duty.
 Acknowledge functions are the same as calls initiated fro ECR/CCR.
6. Repeat Alarm
 Repeat alarm will be triggered when an active watch call group alarm has not been acknowledged
from an operator station within a predefined time. This predefined time is normally set to three
minutes (LIMIT 1 - adjustable). Repeat alarm one will be given at bridge panel, duty
engineer/officer panel and at public panels. If again, the engineer on duty fails to acknowledge
the alarm within “Repeat Alarm two limit”, normally three minutes(LIMIT 2 – adjustable) all
engineers with the qualification will be announced at bridge panel, duty engineer/officer panel
and at public panels.
7. Patrol Man alarm

 When a “Patrol Man Alarm” is activated all officers with machinery qualification are called. The
public area panels will also call these officers.
 Likewise, for cargo, when a “Patrol Man Alarm” is activated, for cargo, all officers with cargo
qualification are called. The public area panels will also call these officers.
www.kongsberg.com
Panel Overview
Watch Bridge Unit:
Unit Location: Bridge

Number of Units: 1
A1 – Chief/eng
A2 – 2st./Eng
A3 – 3rd1-2/Junior./Eng
A4 – ETO
A5 – Captain
A6 – Chief/off
A7 – 2nd./Off
A8 – Cargo Eng ok
B1 – Mach.
B2 – Cargo
B3 – Nav.
B4 – Fire & Gas
B5 – System
B6 – Patrol Man
www.kongsberg.com
Watch Cabin Unit for ECR:
Unit Location: Refer table above.

Number of Units: 12
A1 – Chief/eng
A2 – 2st./Eng
A4 – ETO
A5 – Captain
A6 – Chief/off
A7 – 2nd./Off
A8 – Cargo Eng
B1 – Mach.
B2 – Cargo
B3 – Nav.
B4 – Fire & Gas
B5 – System
B6 – Patrol Man
www.kongsberg.com
Watch Cabin Unit for CCR:

Number of Units: 2
A1 – Chief/eng
A2 – 2st./Eng
A4 – ETO
A5 – Captain
A6 – Chief/off
A7 – 2nd./Off
A8 – Cargo Eng
B1 – Mach.
B2 – Cargo
B3 – Nav.
B4 – Fire & Gas
B5 – System
B6 – Patrol Man
www.kongsberg.com
Watch Cabin Unit for Navigation:

Number of Units: 4
A1 – Chief/eng
A2 – 2st./Eng
A4 – ETO
A5 – Captain
A6 – Chief/off
A7 – 2nd./Off
A8 – Cargo Eng
B1 – Mach.
B2 – Cargo
B3 – Nav.
B4 – Fire & Gas
B5 – System
B6 – Patrol Man
www.kongsberg.com
Watch Cabin Unit for Public:

Number of Units: 6
A1 – Chief/eng
A2 – 2st./Eng
A4 – ETO
A5 – Captain
A6 – Chief/off
A7 – 2nd./Off
A8 – Cargo Eng
B1 – Mach.
B2 – Cargo
B3 – Nav.
B4 – Fire & Gas
B5 – System
B6 – Patrol Man
www.kongsberg.com
5.14 Engine Patrol Man System
The system can be activated from one of the activation panels located in entrance to the engine room or
automatically from the alarm extension system when a machinery alarm is activated.
The reset interval period is set to 15 minutes. Pre warning alarm will be activated 3 minutes before dead
man alarm is set.
See the flowchart below for more details:
www.kongsberg.com
Machinery
Alarm when
System ON
Bridge Watch
ON
Start reset timer
YES Reset button

activated?
NO
NO
Timer>15 min?
YES
Set warning light

in machinery area
YES Reset button

activated?
NO
NO
Timer>18 min?
YES
Activate Patrol
Man alarm
Activate Extention
Alarm system
Table 7-27 Patrol man flowchart
www.kongsberg.com
If the system is switched off before the pre-warning or patrolman alarm is initiated, the sequence will
terminate and switch off the system on lamp.
Keeping the on/reset button for more than 10 seconds can perform lamp test.
Following panels are provided:
 2.ea activation panels
 Reset buttons / system on light (included in the engine alarm columns).
Reset can also be performed from one of the engine control room operator stations by using the dedicated
push button on the Patrol Man mimic.
www.kongsberg.com
6 (Appendix 1 ).
7 KM Standard colour definition
Colour table
Table 7-1 Colour Definition
8 K-Chief 700
K-Chief 700 is the control and monitoring system by Kongsberg Maritime. The system has a large range
of applications within the fields of offshore industry, on-shore chemical industry, safety systems and
vessel control systems.
A good comprehension of the basic principles in AIM makes it easier to use the system efficiently. The
intention of this section is to provide this background. It starts with a description of the AIM environment
and continues with a closer look at the role of each station type and the way they communicate.
Compared to conventional stand alone controllers and alarm panels the Kongsberg ICMS concept offers
several advantages such as:
www.kongsberg.com
Increased safety due to
 Redundant communication network

 Stand-alone operator stations
 Distributed process control stations
 No main computer
 Modular fail-safe hardware
 On-line diagnostic functions
 Supervision of sensor interfaces
 Supervision of machinery operation.
Cost effective due to
 Reduction of sensor cabling

 Reduction of interface problems
 Eliminates conventional hard-wired consoles / mimics and reduces control room area
requirements
 On-line configuration reduces dead time during installation
 Reduction in spare part requirement
 One supplier providing service for the entire control system
 Fuel optimising by integration of dynamic positioning, thruster control and power
management systems.
Simple operation due to
 Process oriented human-machine communication

 Purpose-built keyboard
 Uniform operator stations.
Flexibility due to
 Easy expansion of existing system

 Built-in on-line configuration tool
 Process simulation.
www.kongsberg.com
8.1 AIM Environment
The plant
AIM 2000
User Interface
Historical data
Process Logic
Data import / export
Field Interface
Other
systems
Process 1 Process 2 Process 3
The field
Table 8-1 AIM Environment

One or several processes, running on the plant, are controlled by means of AIM.
The collection of equipment, instruments and actuators that make the processes, is designated 'the field'.
The signal interface between the field devices and AIM is designated the field interface, which is part of
the AIM system. Beside the field interface, data can be exchanged with other systems that comply with
certain data access standards.
The process logic handles signals from both the field interface and the user interface. It processes the
information according to the configured logic and provides response to either interface. The process logic
is a configuration of standard AIM function modules that build up the required functionality for the plant.
The user interface allows the user to operate and configure the process logic.
AIM is capable of logging historical data. The historical data can be used for trending, reports or data
analysis.
8.2 Distributed Control System

AIM is a distributed control system (DCS). Its architecture is based on a local data network that
interconnects the stations required to control the plant. There are several station types. Each of them has a
specific role and can be configured to match the operational requirements of the plant. Due to this
architecture, AIM systems are scalable: New stations can be connected in the network to control
additional process areas or extend functionality.
As the AIM network is crucial for all communication between the stations, it is made dual redundant.
In addition to the AIM network, OSs and HSs may be connected to an administrative data network,
providing a connection interface for other systems and devices.
www.kongsberg.com
AIM 2000 – Simplified block diagram
Event External Network

printer systems printer
Adm. Network
(Network C)
OS OS OS HS
AIM Network
(Networks A and B)
FS FS FS
RCU RCU RCU
RIO400 RIO400 RIO400

units units units
TBSS RS485 TBSS
Serial lines Profibus DP Serial lines
The field The field The field
Table 8-2 Distributed Control System
8.2.1 FS – Field Station

The FS is a combined processing and field interface unit. It can comprise a single Processing Controlling
Unit (PCU) or a pair of redundant PCUs. The PCUs will from here be referred to as the Remote
Controlling Units - RCUs. The RCU keeps the process logic for a specific process area, while the RIO400
units provide signal connection between the field devices and the AIM system. A FS communicates with
the field devices it controls by means of discrete IO signals and serial lines.
AIM has a distributed database: Each RCU keeps the program, configuration and data that are associated
with the process area it controls. Both the program and the configuration that run on a RCU are to be
backed up to an OS for permanent storage.
8.2.2 OS – Operation Station

The OS provides the interface between the user and the process plant.
More specifically the OS provides:
 A graphic user interface towards the AIM image types

 Facilities for navigation in defined images
www.kongsberg.com
 Storage of RCU program files and configuration data.
The OS platform consists of:
 At least one colour monitor for presentation

 At least one operator panel for data and command entry (buttons in AIM panels can be
combined indicators and controls)
 A pointing device such as a trackball or mouse.
In principle the entire process can be controlled from any OS in an AIM system. However, AIM provides
several mechanisms to limit control. Three levels are distinguished:
 Network setup can limit which RCU are visible for the OS
 Membership in OS groups controls which process areas can be controlled from the OS
 Access control controls which functionality is available for the user. (See Ch. 7)
8.2.3 HS – History Station

The HS stores time series that can be used in historical trends and reports. The HS is only HS and does
not have functionality as OS. The station is then referred to as HS99 and is configured with Rapid
8.2.4 Alarm/Event Printer

The Alarm/Event printer is dedicated to print events as they occur. The printer is connected to a parallel
port on the OS. For redundant printing a printer is connected to at least two operator stations. Even if one
network is down Alarms/Event printer will print out Alarms/Events as they occur. See Ch. 6 for
configuration.
8.3 Communication
A common approach to AIM communication is to distinguish the following areas:
 Field communication between AIM and the field devices

 Internal communication between AIM stations
 Communication with administrative systems for data import and export.
Internal Communication
Internally, AIM communicates via the AIM network.
The AIM network is an Ethernet based LAN providing data communication between all connected
stations. The AIM network is dual redundant. That means that every station is connected in two identical
networks, net A and net B. The communication path is intact as long as at least one of the networks is
operational.
As any LAN, the AIM network can be designed and implemented in many ways. Normally the AIM
applies a network topology with hubs. A possible topology is shown on the next page.
www.kongsberg.com
Adm. Network
(Network C)
Note: The C-Net is normally located inside the NDUs
OS OS OS HS OS OS for Network B.
AIM Network
(Networks A and B)
FS
NDU NDU NDU NDU NDU NDU
A1 B1/ A2 B2 A3 B3 / RCU
C1 C3
AIM Network
(Networks A and B)
FS FS FS FS FS FS FS FS
RCU RCU RCU RCU RCU RCU RCU RCU
Table 8-3 AIM Network - Simplified Block Diagram
The basic considerations for segregating traffic in the AIM network are:
 Fault isolation
 Network load control.
Field Communication
The RCU communicate with the field devices via:
 Discrete AIM IO
 Serial lines
 Industrial standard compatible field bus.
Discrete IO provides separate channels assigned to signals through AIM IO configuration. Dependent on
the signal type, analogue, digital or pulse train, appropriate RIO400 cards are used to implement the
interface. Basically two types of RIO400 units are used:
 RDIOR420 .. .. 16 HSD digital inputs and 16 relay outputs

 RMP420 .. .. 32 HSD digital input/output and analogue input/output where
two channels can be used for pulse train.
The RIO420 units provide:
www.kongsberg.com
 Galvanic isolation between the instrument loop and the IO channel
 Facilities for signal loop powering from either within the AIM system or the field
 Grounding.
The RIO420 units provide conversion between data signal, on the RCU process bus side, and instrument
signal, on the field side.
AIM discrete IO
Signal loop
BUS
RCU
HUB
* Field device
1A
1A
Field device
RIO420
Field device
X2 Red.
Update
R-Bus
BUS *
RCU HUB
1B 1B
RIO420 Field device
* = Each BUS HUB provides 4 galvanically isolated BUD segments.

RIO may be located in main FS cabinet or sub-cabinets.
Distance for each segment = max. 200 meters. Aditional HUB units
may be used as amplifiers / extenders for additional 200 meter
range
Table 8-4 RCU, RIO and IO

Serial lines are connected to the serial port of the RCU via a serial line terminal board. Adapters are
inserted on the termination board to adapt the serial line format.
AIM Serial line interface
TBSS Field device Field device Field device

Serial
RCU
Flat line I/F
cable card
Field device Field device Field device
Table 8-5 RCU and Serial Line Interface
Profibus is an industrial standard field bus. Profibus and Profibus DP slaves are fully AIM compatible.
The Profibus transmission line is connected to the Profibus communication port of the RCU via a RS-485
splitter card or a DP/DP-Coupler. The RCU acts as Profibus
www.kongsberg.com
master.
AIM Profibus interface
RS-485
RCU Splitter Field device
Drop
cable card Slave 3
RS-485
RCU Splitter Field device Field device Field device
Drop
cable card Slave 3 Slave 4 Slave n
OLM
DP/DP- Optic
RCU
Drop Coupler Drop Link Field device Field device Field device
cable cable Slave 3 Slave 4 Slave n
Module
Table 8-6 RCU and Profibus Interface

Communication with External Devices
The C-Network network is on all OS and HS Stations. On C-Network are all kind printers connected. The
C-Network can also be connected to a Router and firewall so a connection to the “vessel own” network
can be established.
Data Import and Export
AIM uses several industry standard interfaces for export and import of data:
 ODBC is used for export of historical time series and event data. Specific ODBC drivers and
DSN are included in the OSK installation that is part of the AIM system installation. ODBC
exported data are used by the AIM Report System.
 TCP/IP can be used to export ASCII streams of time series data directly from the HS as they
are received from the RCU. This mechanism is used in customer adapted applications for
post-processing of AIM data.
www.kongsberg.com
8.4 Using K-Chief 700
8.4.1 Starting and Stopping K-Chief 700
The way an AIM system is started depends on the situation. The most extensive situation is start up after
Cold Start. Less drastic situations are the start up and stopping of single stations. There is no general
procedure for starting up an AIM system. The exact way an AIM system deploys is a matter of
configuration. However, the main principles are reflected in the following.
After Cold Start, at least one OS which serves the RCUs configuration files must be started and all RCUs
booted. If at least one of the serving OSs are running, the RCUs start loading their program and
configuration files. Normally, several OSs are set to serve the RCU´s program and configuration files,
making the order of start-up less significant. You can observe the deployment of the system from the
Equipment image on an OS. It should not take more than 30 min(Normally less than 15 min) before all
OS and RCU are on-line.
Should the serving OS malfunction, while an RCU is loading, the RCU will reboot and find another
server, until it has succeeded.
Stopping the system is done by turning off the power to RCU and exiting AIM from each OS/removing
both power supplies from OS.
Start up sequence in steps from the point power supply to RCU, NDUs and OS has been established:
 Operator Stations starts AIM automatically. Logged on as Operator (default)

 Control of command groups are distributed as defined (ref ch. 7.4).
 RCUs get IP-address from Hosts-file from any OS online (AIM must be running and at least A or
B network).
 RCUs ask for process- and IO-files from any of the defined servers. If none of defined servers are
running, RCU will keep rebooting until this is the case (ref 6.1.1).
 System is back to normal mode when all RCUs are rebooted.
8.4.2 Running K-Chief 700

In order to access AIM, a login name and password is required. All AIM users are organized in user
groups. The functionality available to the members of a group is determined by the security objects
associated with each user group.
As several users can be logged on simultaneously, there is a possibility of concurrent operation.

Preventing concurrent operation is a matter of command control. In order to get control of a function
module, you must operate the OS that is in command of the command group to which the object belongs -
typically a function module that runs on a RCU.
Dependent on the user group they belong to, users can enter special configuration modes. The intention of
the configuration mode is to prevent the user from accidentally changing a configuration; therefore a
configuration mode must be entered before changing a configuration.
www.kongsberg.com
8.4.3 Users Guide/ F1 Help function.
The User Guide for the Advanced Integrated Multifunction (AIM) system is the essential
reference for personnel involved in operation and configuration of the AIM system. It is
presumed that the reader has participated in the AIM training program.
By Typing F1 the AIM Users Guide appears on the OS.
Structure:
As a general rule, the information in each section is organized in three main parts:
1. Description - general overview of technical concept concentrated in the User Guide

2. Procedures - relates to the use of the commands and their functionalities
3. Reference - providing dialog box and command specific information.
Information retrieval:
This User Guide provides several ways to locate the information you are looking for.
The most usual way is to use the search tab to find the topic you need, and then use the Locate button to
find its place in the contents structure.
Context-sensitive help is available for all dialog boxes. Use the F1 button on the keyboard to
display help for the active dialog box.
Terms and abbreviations are explained in the glossary section of the User Guide. In addition,
these terms and abbreviations are identified in the text and appear in the same way as hyperlinks.
Pointing to the link for an explained term invokes the following ToolTip: Click the term for a
definition of the term in a pop-up window.
No Help screens for help screens identifying permissives, trips, sequences of operation, faults
and other information.
8.4.4 Analysis of K-Chief 700

K-Chief has a number of functionality for troubleshooting and fault-finding. For network faults refer to
the net-status page on the equipment view. For faults on IO-level/serial lines check IO-manager and
station explorer. Alarms will be issued as a system alarm if an abnormality in relation to K-Chief 700
system occurs. For information how to use the tools of K-Chief 700 to troubleshoot see the operator
manual.
www.kongsberg.com
9 Operator Stations
9.1 Main Features
The OS provides an operator interface to the plant, including process animation, alarm lists, trends, report
system etc. It is a user interface provider for the communication between the user and the RCUs and HSs.
It also provides the user interface to the access control system and the command control system.
The OS provides a storage/load source of the RCU system- and configuration files and user interface to
access to the entire AIM configuration.
The OS user interface provides functionality for normal operation and configuration of your application.
To achieve this, the OS provides several mechanisms.
Refer to Operator Manual how to operate Operator Stations.
9.2 Logging On
When logging on to the K-CHIEF Operator Stations, a user name and password must be entered in order
to access the system. Each user is member of a user group, where access rights and user privileges are
defined. For details about Users, User Groups and the Access System, refer to section 14 Access Control
System. After power up, Operator will be logged on as default.
9.3 Images and Navigation

K-CHIEF images are displayed in the main view areas of the primary and secondary windows. Normally,
however, the image windows will be of 'normal' size, and will be displayed either on large screens or on
multiple screens OSs. For details about the images and navigation refer to section 13 Images and
Navigation.
9.4 Access Control

User groups are configured to give each user access to the functionality the user needs to perform the
work tasks. For details about the Access Control refer to section 14 Access Control System.
9.5 Command Control

To avoid concurrent operation of the same command groups, and to restrict user access to specific
command groups, the OS is equipped with a command control mechanism. For details about the
Command Control refer to section 15 Command Control System.
9.6 Process and Application Control

Commands are provided on the main menu and the toolbar, and also on image/mode sensitive context
menus.
The OS may also have an operator panel connected, which is based on a standard keyboard and then tailor
made to the operator.
www.kongsberg.com
9.7 Tag Mark Indication
The purpose with the “tag mark” is to give the operator a clear indication of the mode status of the AIM
software function module controlling the different field devices. The “tag mark” will also be used for
alarm indication in case a ‘Failure’ signal is included for the controlled device. Also timeout and
inconsistency alarm will be indicated by the “tag mark” (typically for pumps and valves). Below you will
see the different “tag mark” indications, the meaning of them and typically software function modules
they will appear together with. “Tag mark” indications used two times will be with different colours.
Table 9-1 Tag mark

Number Tag Mark Meaning Used by Colour
1 ““ Detached PID, motor, valve, cb Cyan
2 “L” Local Motor, valve, cb Cyan
3 “!” Not OK Motor, valve, cb Red
4 “s” Shutdown / Trip Motor, valve etc. Magenta
5 “o” Override PID, motor, valve etc Cyan
6 “i” SD/ Inhibit PID, motor, valve etc Cyan
7 “!” Override / Interlock PID, motor, valve etc Cyan
8 “I” Interlock Motor, valve, cb etc. Cyan
9 “f” Follow & Freeze PID Cyan
10 “e” External PID Green
11 “m” Manual PID, motor, valve etc Cyan
12 “a” Auto Motor, valve etc. Green
13 “i” No definition - -
14 ““ Not Mark - -
Table 9-2 Tag Mark Indication

www.kongsberg.com
9.8 Configuration Set-Up OS’s
Refer to chapter 4.1 Configuration Set-up Operator Stations (OS) for Project specific configuration.
9.8.1 Storage / Load Source of the RCU

The OS provides a storage/load source of the RCU system- and configuration files. When a RCU is
powered up or reset, a set of system files and configuration files will be downloaded from the operator
stations. System files will be downloaded from any operator station while configuration files will be
downloaded from operator stations configured to be RCU servers.
Refer to chapter 6.1 Table 4-5 Printer

Configuration Set-up Field Station (RCU) for Project specific configuration.
9.8.2 Alarm Kit

Two Operator Stations will have installed a relay kit used for activation of alarm columns. These
Operator Stations are normally located in CCR. The relays will be triggered in parallel with the panel
alarm buzzers. Electrically the relays will be interfaced to the nearest field station as digital inputs on a
RIO400 unit. These inputs will be, in the software, used to set digital outputs which again are interfaced
to the alarm columns. Alarm columns in other areas will be connected to the nearest field station.
9.9 Clock distribution system

All Operator Stations and Process Stations (RCU) will operate on same synched clock-system. The clock
synchronization will come from the “System Master Clock”.
The “System Master Clock” time will either be set by the Captain and Kongsberg user or be updated from
an external clock – GPS. Then one of the RCU will take the “lead and roll” as “System Master Clock”.
All RCU will be synchronized from this “System Master Clock”.
www.kongsberg.com
10 History Station
There is one history stations onboard, one Rapid database (K-Chief-HS99) for long term storage.
10.1 Main Features Rapid K-Chief-HS

The Rapid-History Station provides facilities for storage of time series. SQL Server 2005 is used for
Alarms and Events. The HS is for Trending and Event List (Operational use).
10.1.1 K-Chief-HS Description

The K-Chief-HS consists of two databases:
 Time series database, Rapid database.

1 Primary time series, which are process values as they are logged from the RCU
2 Secondary time series, which are processed primary series, for example mean
values for a process value for a given period of time.
 Alarms and Events database, SQL Server 2005 database.
The illustration below shows HS Rapid database and its interfaces.
HS98
Time series data
from function Time series
modules database
configured on
PCUs
Alarms and Event

database
Usage of stored data
- Trends
- Reports
- Event images
- ODBC clients
Alarms and Events from alarm

and event server
The Time series database receives time series data from the function modules that are configured on the
RCUs. The time series that come from the RCUs are primary or secondary time series. The stored time
series are utilized by other AIM applications like Trend images and reports. The time series database has
an Open Database Connectivity (ODBC) interface. A separate export function is also incorporated in the
HS.
www.kongsberg.com
The Alarm and Event database receives event data from the event server. Alarms and events are
generated by the function modules running on the RCUs, or by the surrounding system. These alarms and
events are stored in the database and are subsequently utilized by Event images, where they are displayed
as alarms and messages. The alarms and events database also has an ODBC interface.
AIM 2000, K-Chief-HS39 and Data Logger– Simplified block diagram
Data
Logger
DMZ
OPC DA/AE
client
Router
Adm. Network (Network C)

Rapid Time Series
HS40 HS39
DP Logger DB
OPC DA/ for
OS OPC DA/
AE Produ SQL Event/Alarms
AE Server
Server ction and Config Events
DB
AIM Network
(Networks A and B)
FS FS FS
Note! Programmers note: History station to be configured for automatic

startup.
10.1.2 K-Chief-HS Configuration

The HS configuration messages, sent from the RCU to the HS-Application (HS-APPL), are transferred to
the Rapid database and the Storage Server. The Rapid has a Configuration interface. Both the Rapid
Data Abstraction Layer (DAL) and the Configuration interface may be accessed.
www.kongsberg.com
10.1.3 K-Chief-HS Storage
The Time series data, sent from the RCU to the HS-APPL for storage, are transferred to the Rapid
database by the Storage Server.
The Rapid database has two possible interfaces:
 Data Logger
 Data Abstraction Layer.
AIM 2000, K-Chief-HS39 – Storage
Adm. Network
(Network C)
Rapid
Data Logger
HS39/ 3000 Storage
(OPC DA client)
Server
AAI
(Archive Interface)
Data Abstraction
HS-APPL Layer
(Message parsing)
DB
(objectivity)
AIM Network
(Networks A and B)
FS FS FS
Time series data is stored in bursts, 100 values once every 10 seconds for 10 Hz data. (configurable). Data
that occurs during a store is queued and stored immediately.
The HS is able to receive these amounts of data from the AIM system and transfers them to the Rapid
Database without data loss. This happens when the only applications running are the Rapid Server and
the HS, when both the RCUs and the Rapid system are set up with zero hysteresis.
This project has included storage of all System I/O into the Rapid Database for Trending and Reports.
10.1.4 K-Chief-HS Retrieve from OS in Trend

The HS retrieve messages, sent from the OS to the HS-APPL, handled by the Retrieve client. The
interface to choose is dependent on design details, about how to handle aggregations. The HS-APPL will
return the data using the existing HS message format or ODBC. All time series send to the Rapid
database, both raw and calculated, can be trended on the OS.
www.kongsberg.com
AIM 2000 K-Chief-HS39 – Retrieve
Adm. Network
(Network C)
Rapid
HS39/ 3000 Retrieve Data Abstraction

client Layer
AAI
(Archive Interface)
HS-APPL
(Message parsing)
OS
Trend
DB
(objectivity)
ODBC
AIM Network
(Networks A and B)
Note! The Rapid database is used for storage of Time series only. The alarms
and events are stored in a separate database(SQL Server 2005)
10.1.5 Initializing of K-Chief-HS Databases

The databases of a HS can be re-initialized by Kongsberg personnel. When doing so, all data currently
contained in the database on the selected HS is deleted.
10.1.6 User Interface

The HS operation user interface is provided by a command on the main menu on OS and associated
dialog boxes, which are available in all views. Refer to the operator manual for more information.
www.kongsberg.com
11 Field Stations
11.1 Main Features
The Field Stations houses Remote Controlling Units (RCUs) and the Remote I/O units (RIOs). The RCUs
are performing the control of the instrumentation field. The communication with the field is performed by
the RIO400 system, which is a distributed part of the RCU system.
OS OS HS
NtPS
RCU Servers RCU Servers
AIM Network
(Networks A and B)
RCU RCU RCU
RCU RCU FS
FS FS
The field
Table 11-1 RCU Simplified Functionality
The RCUs themselves provide no permanent storage of programs and data. On a specific RCU start-up,
all its programs and data are loaded from its RCU servers. These servers are configured on one or more
OSs. The OS may be housed in an operator console, or it may be a stand-alone PC.
Note! RCUs controlling machinery used for DP purpose will be with flash
memory and hence can be started up without loading their program from
and configuration from the OSs.
The NtPS’, which are simulated RCUs with limited functionality, are also configured on OSs.
Time series, which essentially are time-stamped process variable values, are generated on RCUs (and
other external sources). Provided that a time series is configured to be stored permanently, it is stored in
the HS time series database only.
www.kongsberg.com
11.2 Modes of Operation
RCUs can operate in different modes:
11.2.1 Normal Operation

The RCU is fully operational and performing plant monitoring and control. The function modules are
processed by cyclically repeating the following steps for each function module:
1. Updating all input terminal values from IO drivers or connected terminals

2. Checking for alarms on all input terminal values
3. Running the module algorithm
4. Checking for alarms on all output terminal values
5. Transferring output terminal values and computing / updating terminal output values.
11.2.2 RCU Exceptional Modes

Users with the appropriate rights may switch the RCU into one or more exceptional modes of operation.
Mode Description
Passive The RCU is in standby mode where the configured modules don't take active part
in the process control.
Simulation The RCU is running in simulation mode. The function modules are isolated from
algorithm the IO system, but input data will be obtained from an alternative source to allow
simulation.
Alternative The function module input terminal values are taken from module output
terminal input terminals instead of from the IO terminals (provided that both types’ connections
exist).
Table 11-2 RCU Exceptional Modes
11.3 Redundancy Pairs

All RCUs are Redundant. Switching between master and slave is an automatic operation which will occur
when there is power loss or error on master RCU. It can also be performed manually if necessary from
operator dialogue. Switching is bumpless and will not disturb the process in any way.
11.4 IO System
The AIM IO system provides the communication interface for exchange of IO signals between the field
devices and the RCU. The AIM supports several IO solutions.
The AIM IO system supports the following IO solutions; SP-Bus with Kongsberg proprietary
communication protocol and a serial bus solution; Profibus standard.
www.kongsberg.com
AIM discrete IO
Signal loop
BUS
RCU
HUB
* Field device
1A
1A
Field device
RIO420
Field device
X2 Red.
Update
R-Bus
BUS *
RCU HUB
1B 1B
RIO420 Field device
* = Each BUS HUB provides 4 galvanically isolated BUD segments.

RIO may be located in main FS cabinet or sub-cabinets.
Distance for each segment = max. 200 meters. Aditional HUB units
may be used as amplifiers / extenders for additional 200 meter
range
AIM Serial line interface / AIM Profibus interface

Drop
RCU cable RSER
Drop
cable
RS-485
Splitter Field device Field device Field device
card Slave 3 Slave 4 Slave n
Table 11-3 A simplified functional block diagram illustrates the general principles of the
IO system.
The common blocks in the IO system functional block diagram are:
www.kongsberg.com
AIM
IO block IO driver
module
Table 11-4 IO system functional block diagram

AIM function modules: Software residing on the RCU and representing field devices, read and write
signal values in order to perform control. The IO signals are connected to the terminals of the AIM
function modules.
IO block: Provide connection and conditioning of the IO signals. The IO block is responsible for
conversion between IO raw value on the driver side and the engineering value on the module side.
IO drivers: Responsible for the communication with the field device. The IO driver provides conversion
between field value and IO raw value.
11.4.1 Concept IO System

11.4.1.1 Overview
The IO system, interfacing one or more processes on the plant, is used to configure and control the input
and output devices in the field.
The AIM IO system supports two IO solutions:
 Serial Process Bus (SP-Bus) with Kongsberg proprietary communication protocol

 Profibus standard.
11.4.1.2 Serial Process Bus

On the AIM side, the RIO400 units are connected to the RCU via a SP-Bus cable. The SP-Bus is a high
speed communication bus, serial line to a dedicated RIO400 unit which can be located inside the FS or
distributed inside third party cabinets. On the field instrumentation side, the RIO400 unit types provide a
various number of discrete IO channels.
The RCU with Kongsberg proprietary software is used for control and management of the field devices
via discrete IO and serial lines. Discrete IO provides separate channels assigned to signals through AIM
IO configuration. Dependent on the signal type, analogue, digital or pulse train, appropriate RIO400 units
are used to implement the interface.
Using the AIM SP-Bus system makes it easy for the user to configure and to control the input and output
process devices and signals of the plant.
11.4.1.3 Profibus Standard

Profibus is a widely accepted international networking standard for automation in manufacturing and
process control and can handle large amounts of data at high speed and serve the needs of large
installations.
www.kongsberg.com
Its great speed, covering distance and data handling capabilities make it ideal for many process control
and data intensive applications. Profibus is a polling network, meaning that its assigned master,
periodically requests the status of each node. This ensures that each device on the network is updated
consistently and reliable.
11.5 Configuration Set-up

Refer to document ‘IO Specification RIO400 Distribution List’ for details about the RIO distribution.
Table showing types of field station delivered:
FS Type Explanation
FS-400C-R1 Cabinet for approximately 400 IO signals. Contains double remote controller
units (RCU) that provides redundancy in computer processing and bus
communication with the remote I/O devices and may house up to 12 RIO400
units, each up to 32 IO channels.
FS-240C Cabinet for approximately 240 IO signals. Contains a single remote controller
unit (RCU) and may house up to 8 RIO400 units, each up to 32 IO channels.
FS-240-R1 Cabinet for approximately 240 IO signals. May house up to 8 RIO400 units, each
up to 32 IO channels.
Table 11-5 Delivered Field Station Types

Refer to chapter 0 Table 4-5 Printer
Configuration Set-up Field Station (RCU) for Project specific configuration.
www.kongsberg.com
12 Network Distribution Units
12.1 Main Features
Internally, AIM communicates via the AIM network.
The AIM network is an Ethernet based LAN providing data communication between all connected
stations. The AIM network is dual redundant. That means that every station is connected in two identical
networks, net A and net B. The communication path is intact as long as at least one of the networks is
operational.
12.2 Topology
As any LAN, the AIM network can be designed and implemented in many ways. Normally the AIM
applies a network topology with hubs. A possible topology is shown below.

Adm. Network
(Network C)
Note: The C-Net is normally located inside the NDUs
OS OS OS HS OS OS for Network B.
AIM Network
(Networks A and B)
FS
NDU NDU NDU NDU NDU NDU
A1 B1/ A2 B2 A3 B3 / RCU
C1 C3
AIM Network
(Networks A and B)
FS FS FS FS FS FS FS FS
RCU RCU RCU RCU RCU RCU RCU RCU
Table 12-1 AIM Network

The basic considerations for segregating traffic in the AIM network are:
 Fault isolation
 Network load control.
www.kongsberg.com
Table showing types of net distribution units delivered:
NDU Type Explanation

SF16 The NDU comprises the following equipment in different combinations and
numbers: STP Hubs (multiport repeaters) having 12 or 24 ports with RJ-45
connectors, fiber optic Hubs (multiport repeaters) each having 6 or 12 ports with
ST connectors, patch panels (RJ-45) for STP cables, fiber optic patch panel (ST)
for connection of external cables, STP switches having 16 or 24 ports with RJ-45
connectors, converters and Hub backplanes that interconnects two or more Hubs.
SF24 The NDU comprises the following equipment in different combinations and
numbers: Switch/switches having 24 ports with RJ-45 connectors, converters for
converting STP to fiber optic, patch panels (RJ-45) for STP cables and fiber optic
patch panel (ST) for connection of external cables.
Table 12-2 NDU types

Refer to chapter 4.3 Configuration Set-up Network Distribution Unit (NDU) for Project specific
configuration.
www.kongsberg.com
13 Images and Navigation
13.1 Main Features
Information and user interaction means are presented to the user via images. An image has a name and
contents. An image belongs to any of the image types defined in the system, for details about image types
refer to section 13.2 Image Types.
Images may be stand-alone objects that are configured to be displayed in the navigator and/or be targets
of hotspots. Images may also be configured as image decorations, which are contained in other images of
Process, Flow or Generic types.
In OS Configuration mode, existing images may be deleted and new images may be created (this doesn't
apply to the PBUS IO image).
Note! Except for the PBUS IO image, no image comprises any module- or IO
configuration. Thus, editing, deleting or saving of images doesn't affect
these types of configurations.
13.2 Image Types

AIM supports the following image types:
Image Type Description

Flow A graphical image type displaying the modules as they are configured in the AIM
world space. Flow images are primarily used to configure the modules and
connections, but can also be used to operate the modules.
Can hold hotspot: Yes
Can hold decoration: Yes
Exist as decoration: Yes
Process A graphical image type providing enhanced graphics and functionality for
operation of the modules. The graphics provides a real life vision of the modules
and site arrangements, with the arrangement of the modules as designed in each
image, and not as defined in the AIM world space.
Process images use configured Flow images as basis.
Trend A graphical image type showing trends for module variable states.
Can hold hotspot: No
Can hold decoration: No
Event A list type image showing alarms and events.
www.kongsberg.com
Image Type Description
System Status A list type image showing status of the stations in the system.
Exist as decoration: No
PBUS IO A persistent image showing the IO racks configuration and -setup for a selected
RCU.
Generic This image type supports hotspots and decorations.
Web An image type that displays web sites/pages.
Table 13-1 Image types
13.3 Image Window Types

AIM provides three image window types:
 A primary image window (one off per OS)

 Secondary image windows (unlimited number per OS)
 Floating image windows (unlimited number per OS).
One primary image window and an applicable number of secondary image windows may be configured
on a large screen, or in multiple screen OS solutions. It is also possible, however not recommended, to
configure several primary and secondary windows on one standard OS display screen.
www.kongsberg.com
13.3.1 Primary Image Window
The primary image window is mandatory in any application. Some basic functionality is only available in
this window. These are:
 System menu operations

 Alarm line in the event system
 Module Editor
 Message Manager
 Report manager
 Command control
 PCU operation
 HS operation
 Log off and exit.
Applications running on one screen will normally have the primary image window only, in addition to
floating image windows.
13.3.2 Secondary Image Window

Applications running on multiple screen solutions or on a large screen will normally have a number of
optional secondary image windows in addition to the primary image window. The functionality of a
secondary window differs from that of the primary window as listed above.
13.3.3 Floating Image Window

A floating image window is a resizable and movable image window that is contained in either the primary
or a secondary image window. It has the same functionality as secondary image windows.
To avoid recurrence, a floating image window cannot contain any other floating image windows.
Restrictions
Floating image windows, popups or dialog boxes cannot be moved outside its image window.
www.kongsberg.com
13.3.4 Navigation between Image Windows
 Moving your cursor to another image window shifts the focus to that image window.
 The Navigator provides a context menu for the selected image, which lets you select the
image window that you want the image to be displayed in.
 In Flow, Process and Generic images, you can configure hotspots, which display images and
popups in other image windows.
13.4 Image Navigation

The OS provides various means for navigation between the images. These means are the following:
Navigator Means Description

Navigator The navigator lets you select the name of the image that is to be displayed in the
main view area.
Hotspots and Hotspots provide links to other images
command buttons Command buttons configured directly on the background of certain types of
images provide links to other images
History Navigator Provides the historical sequence of the images that have been displayed in the
main view area.
History navigator When clicked, they navigate you back and forth in the displayed image history.
arrow buttons
Tag-based image For a selected tag, two related methods are provided:
navigation Navigation via context menu
Best image navigation. A system algorithm selects the best image of the image
type that has been selected by the user.
Operator panel and Keyboard with pointing device can be used for image navigation during both
keyboard normal operation and configuration. If your OS is configured with an operator
panel and alarm panel, you can navigate between images using buttons on these
panels.
Table 13-2 Means of Image Navigation
www.kongsberg.com
13.4.1 Navigator
Root Image - Legend
Parent Image - Symbol for Process Image
Symbol for Trend Image

Child Images
Parent Image -
Child Images
Parent Image -
Child Images
Parent Image -
Child Images
Parent Image - User Rights
Child Images
Table 13-3 Image Navigator
13.4.2 History Navigator

The number of images contained in the historical list can be re-defined by users with OS configuration
privileges. The set up is 10 numbers of images in the historical list.
13.4.3 Hotspots
Images of Generic, Flow and Process types may contain hotspots. In general, when a hotspot is clicked, a
function is executed. However, in most cases, the function will display a specific image. Thus, usually the
hotspot provides a shortcut to another image.
13.4.4 Operator Panel

OSs configured with an operator panel provides an easy navigation between images using buttons on
these panels. For details about button layout refer to MIMIC KFDD document.
www.kongsberg.com
14 Access Control System
14.1 Main Features

The access system provides a security mechanism to control:
 User accounts: I.e. whether a user can log on the application

 User rights: I.e. what kind of functionality is available for each user.
The concept builds on a few principles:
 A user account is identified by a user name and password combination

 Every user account belongs to a user group
 A specific set of user rights that represent a distinct functionality, is associated with each user
group.
The access system provides the built-in user account 'Administrator' that is member of the built-in user
group 'System'. Neither can be deleted.
All users use the access system as they log on and off.
All configuration tasks, such as adding, editing or deleting user accounts and user groups are the
responsibility of the system administrator.
Flow Chart
Log On
Log on to user account with correct
password
User G User J User M
Identification Not ok
User H User K User N
Ok
User Group
User I User L User O Link the user to the user group which it
belongs to
User group P User group Q User group R

User Rights
Link the user to table with user rights
User Rights according to configured for the user
group
The user can now operate the system

according to its configured user rights
Table 14-1 Users and User Groups
www.kongsberg.com
14.2 User Rights
A security object controls the access to specific functions. A user group is associated with a number of
user rights. The table below lists all the user rights that are available in AIM and the capability of each of
the user rights is defined.
Security Object Description / Capability

AlarmLimits_EditAlarmConfig Edit access to the alarm Limit Dialog
AlarmLimits_ReadAlarmLimits Permission to view alarm limits dialog
AlarmLimits_WriteAlarmLH Permission to change LH alarm limits.
AlarmLimits_WriteAlarmLLH Permission to change LlHH alarm limits.
H
AlarmShelving_ProcessAlarms Permission to shelve or unshelve process alarms.
AlarmShelving_SystemAlarms Permission to shelve or unshelve system alarms.
HS_Operation Enable HS operation.
IO_BasicOperation Basic operations on IO system for loop checking purpose.
IO_ExtendedOperation Extended operations on IO system for parameter change purpose.
IO_Operations Operations on IO system that do not affect process control.
IO_Service Service operations on IO system that may affect process control.
ModuleOperation_Operate Write access to module operation dialogs
ModuleOperaton_ReadParamet Read free parameters in module parameter view.
erFree
ModuleOperaton_ReadParamet Read limited parameters in module parameter view.
erLimited
ModuleOperaton_ReadParamet Read restricted parameters in module parameter view.
erRestricted
ModuleOperaton_ReadTermina Permission to view module terminal view dialog.
lView
ModuleOperaton_WriteParamet Write free parameters in module parameter view
erFree
ModuleOperaton_WriteParamet Write limited parameters in module parameter view.
erLimited
ModuleOperaton_WriteParamet Write restricted parameters in module parameter view.
erRestricted
ModuleOperaton_WriteTermin Write terminal values in module terminal view dialog.
alView
Module_ReadModuleMode Permission to view module modes dialog.
Module_WriteModuleMode Permission to write changes from the module modes dialog.
OSKCmdCtrl_Acquire Users without this permission cannot have command control. In the
sense of Command Control the OS is regarded as dead.
OSKCmdCtrl_ManuallyOverri Users with this permission may override Command Control.
dCommand
OSKCmdCtrl_TakeForced Users without this permission cannot take command control forced.
OSKEquipment_Configure In order to configure equipment system, the user must have this
permission and the OS must be in configuration mode.
www.kongsberg.com
Security Object Description / Capability
OSKOS_Configure Needed to be allowed to set the OS in configure mode.
OSKOS_DisableLogOff Will disable the logoff button in the change user dialog.
OSKOS_Exit User without this permission cannot exit the OS.
OSKOS_Test Needed to be allowed to set the OS in test mode.
OSKTrend_UserDefined Users without this permission cannot create and edit User Defined
Trend images.
OskAccess_ConfigureGates Needed to add, modify and remove gates and witch permissions the
control.
OskAccess_ConfigureOSes Needed to modify the local access control setting for each OS.
OskAccess_ConfigurePermissi Needed to add, modify and remove permissions.
ons
OskAccess_ConfigureUsergrou Needed to add, modify and remove usergroups and their relationships
ps to gates.
OskAccess_ConfigureUsers Needed to add, modify and remove users and their relationships to
usergroups.
OskAccess_ObserveConfigurati Needed to inspect the access control configuration.
on
OskEvent_AckProcessAlarm A user needs this permission in order to ack a process alarm.
OskEvent_AckSystemAlarm A user needs this permission in order to ack a system alarm.
OskEvent_ChangeFilter A user needs this permission in order to change an Alarm filter.
OskEvent_Configure A user needs this permission in order to configure the event mage
grid.
OskEvent_SelectFilter A user needs this permission in order to select a filter.
OskEvent_UserLockFilter A user needs this permission in order to change a filter.
PCU_Backup Permission to backup PCU
PCU_SetPCUConfigurationMo Permission to set PCU configuration mode
de
PCU_TogglePCUModes Permission to toggle between the different exceptional modes in the
PCU Operation dialog.
Redundancy_OverruleObjects Permission to overrule error objects.
Redundancy_SwitchMaster Permission to switch master PCU in the Redundant Stations dialog.
TS_Configure Create timeseries with limited life span
TimeSystem_SetTime Needed to be allowed to change system time.
TimeSystem_SetTimeZone Needed to be allowed to change timezone.
VersionControl_RestoreImport Restore and import files from PCU configuration archive
PCU
VersionControl_ViewConfigur Permission to view configuration events dialog.
ationEvents
Table 14-2 User Rights
www.kongsberg.com
14.3 Configuration Set-up Users
Refer to chapter 5.2 Configuration Set-up Users and Groups for Project specific configuration.
Passwords are by default the same as the User name. This can be changed by members of
“Administrators”, Additional Users and User Groups can be added (refer to the K-CHIEF operator
manual).
Numbers like PIN codes are recommended as passwords, to avoid the use of regular keyboards for login.
With a number the normal operator panels can be used.
www.kongsberg.com
15 Command Control System
15.1 Main Features
The command control system provides mechanisms to manage and distribute responsibility between OS'
on a plant. If concurrent operations are forbidden, command control ensures that concurrent operations
don't take place.
Using command control assumes that the following are defined clearly:
 The fields of responsibility (the command groups)

 The actors (OS groups) that can claim, or be given, the responsibility over the command
groups.
Command Command Command
group P group Q group R
OS OS OS OS OS OS OS OS
OS group M OS group N OS group O
Table 15-1 Command Control System
Consequently, the command control system is provided with mechanisms that:
1. Grant or deny the responsibility over a command group to an OS group

2. Allow transfer of responsibility between OS groups.
15.2 Command Groups

A command group represents a set of objects. Usually, an object is an AIM function module.
A command group may be exclusive or shared:
 An exclusive command group can only be under command of one OS group at a time
 A shared command group can be under command of several OS groups simultaneously.
15.3 OS Groups
Each OS group contains one or more OSs, whereas each OS can only be member of a single OS group.
www.kongsberg.com
15.3.1 OS Groups in Command of a Group
An OS group can be in command of a command group, this means:
 The OS group can operate objects in the command group

 The OS group is responsible for the command group
 The OS group receives events and alarms from objects in the command group, which events
and alarms an OS receives depend on the event filter settings.
15.3.2 Privileges
For each command group, an OS group can have the following privileges:
 The command group is acquirable. The OS group must have this privilege for the command
group in order to obtain the command of it
 In addition the command group can be in default. This means that the OS group tries to
obtain command at start up.
If the command group is exclusive, the OS group may have the privilege to take the command forced.
This means that the OS group can obtain command without any accept from the OS group, which
currently is in command of the command group.
If access control is enabled, the user who currently is logged on must also have sufficient user rights.
15.3.3 Alarm Conditions

When all OS' in an OS group are dead, the OS group is regarded as dead. This will cause an alarm to
arise.
15.4 Obtain, Lose and Transfer Command

An OS Group can obtain command and lose command over a command group in various ways. For an
exclusive command group the command can be transferred from one OS group to another. This means
that the second OS group will obtain the command of the command group, and the first OS group will
lose it.
The table below describes the various ways the command control can be obtained, lost and transferred:
Command Description
Control
Take at start- An OS group will automatically try to take a default command group at start up, that is, when the
up first OS in an OS group starts.
Take An OS group can take the command over a command group, which is not under command of any
other OS groups. The command group must be acquirable.
Take shared An OS group can always take the command over a shared command group, if it is acquirable.
Request An OS group can request the command over an exclusive command group, if it is acquirable. The
command is transferred, if the OS group currently in command accepts the request.
www.kongsberg.com
Command Description
Control
Take forced Instead of waiting for a request to be accepted, the requesting OS group can take the command
forced. To take command forced, the OS group needs the corresponding privilege.
Give An OS group in command over a command group can give the command to another OS group,
which can acquire it. The command is transferred, if the receiving OS group accepts to receive.
Give up to An OS group can give up the command over a command group to none only if there is as least one
none other OS group in command.
Auto receive When the last OS in an OS group stops, and if it is the only OS group in command of a command
group, all other OS groups, which can acquire the command group, will automatically receive the
command. The first OS group, which accepts to receive, will obtain the command.
Table 15-2 Command Control
15.5 Configuration Set-up OS and Command

Groups
Refer to chapter 5.4 Configuration Set-up OS and Command Groups for Project specific configuration.
www.kongsberg.com
16 Version Control System
16.1 Main Features

The Version control system logs all RCU configuration changes that are made to all the function
modules/tags of the configuration. All backups of the RCU configuration changes (files) are stored in a
dedicated archive, allowing restore of any of the previously made backups.
This is normally installed in the Master Configuration OS located in ECR, CCR or Bridge.
16.2 Version Control System and Environment

The illustration below shows the version control system and its environment. OS numbering is just for the
illustration.
RCU
configuration
archive Configuration
event
database(s)
Version
OS31 OS32 OS33
control
system
AIM network
RCU31
Table 16-1 Version Control System and Environment
The version control system is installed on one OS of the configuration.
All operator stations (OSs) can, however, utilize functionality provided by the version control system as
follows:
 OSs with enabled version control system can initiate both backup and restore of the RCU
configurations
www.kongsberg.com
 OSs with no enabled version control system can only initiate backup.
The RCU configuration archive contains all previous backups of the RCU configuration files (.ps, .io
etc.). The RCU servers, which are housed in the OSs, contain only the last backup of the RCU
configuration files.
The RCUs contain information on the events concerning the RCU configuration changes. These events
are also copied to the configuration event database (DB) as they occur, and can be viewed by the user.
The import function lets you import RCU configuration files from external sources.
16.3 Registration of Configuration Events

The version control system is an integrated part of both the OSs and the RCUs. It works in close
conjunction with the RCU backup and -restore system.
16.3.1 Event Logged in the Configuration Event DB(s)

Whenever a user performs a RCU configuration change/backup/restore, information on this event is
stored in the configuration event database.
In the table below, all events, which are registered by the version control system, is defined in the column
to the left. For each type of event, the logged legal actions are defined in the column to the right.
In addition, users can add a comment prior to starting the backup.
Event Actions
Add and remove Function module created
function module Function module removed
Change in module Scan task changed
general data Scan multiplicity changed
Trig module changed
Command group changed
Alarm panel group changed
Tag name changed
Visibility level changed
Position changed
Change in function Disable alarm mode changed
module status Disable input mode changed
Disable output mode changed
Passive mode changed
Simulation Algorithm mode changed
Alternative Terminal Input mode changed
Change in specific Parameter changed
parameter values
www.kongsberg.com
Event Actions
Time-series Time-series created
configuration Time-series deleted
Time-series changed
Alarm Alarm created
configuration Alarm deleted
Alarm changed
Connection Connection created
configuration Connection deleted
Connection changed
IO configuration Slot changed
Address changed
Task changed
Card deleted
IO interface IO connection created
(Profibus) IO connection deleted
Change of RCU RCU mode changed
mode
Backup of RCU Backup succeeded
Distribution succeeded
Restore of RCU RCU configuration files restored
Boot of RCU Started
Table 16-2 Event Logged in the Configuration Event DB(s)

In addition, users can add a comment prior to starting the backup.
www.kongsberg.com
16.4 Version Control Backup
The version control system stores all backups of the RCU configuration files in the RCU configuration
archive. When the version control system is not enabled, only the last backup is saved (on the RCUs
fileservers).
RCU
configuration
archive Configuration
event
database(s)
Version
OS31 OS32 OS33
control
system
AIM network
RCU31
Table 16-3 Version Control Backup

Refer to the figure above. The version controlled backup is performed as described in the following:
1. One of the OSs initiates a backup of the RCU31 configuration files. A comment may be
added, to be used in step (5).
2. The system tells the OS31, which runs the version control, the names of the OSs that are
fileservers for the RCU31.
3. OS31 then distributes the RCU31 configuration files to these fileservers in sequence, thus
storing the RCU configuration changes on a permanent basis. (Existing RCU
configuration information is overwritten.)
4. All distributed RCU configuration files are also stored in the RCU configuration archive
under a new label (version id) and with the additional comment inserted by the operator
in step (1).
5. Information on the backup event is sent to the configuration event database and can be
viewed by the user.
On a later point of time the user can restore the appropriate version from the RCU configuration archive.
www.kongsberg.com
16.5 Version Control Restore
A backup of the RCU configuration files, which is stored in the RCU configuration archive, can be
restored to the appropriate RCU. The restore must be initiated by an OS with enabled version control
system.
RCU Configuration
configuration event
archive database(s)
OS32 OS33
Manual
restart of
RCU by
operator
Version
OS31 RCU31
control
system
Table 16-4 Version Control Restore
Refer to the figure above. The restore of the version controlled RCU configuration files is performed as
described in the following:
1. OS31 initiates a restore by selecting a version of a given RCU (in this case RCU31) by
getting the information from the RCU configuration archive.
2. OS31 distributes the RCU configuration files to the OSs that are fileservers for RCU31.
While doing this, messages are sent to the RCU containing the progress value.
3. An operator message is broadcasted to all OSs of the configuration telling that RCU31 is
restored with version X, and needs to be restarted.
4. RCU31 is then manually restarted by the user. During the boot-process RCU31 reads the
restored RCU configuration files from one of its fileservers.
16.6 Import of RCU Configuration Files

The version control system incorporates functionality, which allows you to import RCU configuration
files from external sources. The importing is only possible to perform on an OS that has enabled the
version control system.
www.kongsberg.com
16.7 User Interface
16.7.1 Availability
The Version control function is available in all image types.
16.7.2 Main Menu Commands and Dialog Boxes

The Version control user interface comprises of a command on the main menu and various dialog boxes.
Refer to the Reference information section for more information.
16.7.3 Context Menu

Right clicking in the Configuration Events dialog box displays the context menu displayed below.

Configuration Store and History
www.kongsberg.com
17 Event System
The event system handles the notification of system and process alarms as well as messages.
17.1 Main Features

An event is a notification to the operator of some condition in the system or the controlled process that
may need attention. Which events are to be notified to the operator, depends on which list is displayed
and which filter is selected.
Events are classified as illustrated:
Events
Alarms
System
Process
Messages
System
Process
Operator
Configuration
Table 17-1 Events
The Event Server in AIM maintains lists of the newest alarms while the state of all alarms in the system is
kept by the RCU. In the different event views both dynamic and static presentations can be
generated. Furthermore, the user can control the selection of what is displayed in the event views by
means of 'filters'. System defined filters are associated with each list, but you can specify filters that suit
specific needs. There is one list for each client connected to the event server.
The event system provides several notifications and presentation alternatives:
 Alarm line
 Event image
 Event popup
 Event decoration
 Audible alarm - a summary alarm indication
www.kongsberg.com
 Alarm indication by means of colour coding and flashing effect in the graphic presentation of
modules in flow and process images.
17.2 Event Attributes

Systematic handling and notification and presentation of events require all events to be specified by
means of a set of attributes. The text representation of these attributes is used in the alarm line and in the
different views. Relevant event attributes are:
Event Type Categorizing of events according to their cause

Time of origin The time (local and UTC time) at which the reported condition occurred.
Originating station Identification of the station that issued the event.
Priority Each event is associated with a 'priority' level. The four priority levels are
denoted, in increasing order, by the numbers 0 through 3
Event text Description of the event or state that caused the event (reason).
Tag, terminal Tag and Terminal denote the source of process events. The fields are used in case
of system events too
Description Optional attribute. The module description associated with the tag
Descriptive text A description of the issuing module that can be understood by the operator. e.g.
"pump", "generator" etc.
Value Optional attribute. A value related to the event
Acknowledge state Applicable for alarms only. The acknowledge state for alarms is 'Acknowledged'
or 'Unacknowledged'
Alarm state Applicable for alarms only. High, HighHigh, etc.
Command group Optional attribute, applicable for alarms only. An identification of the command
group related to the alarm.
Redundancy state Possible values are: RP (redundant passive), RA (redundant active) or empty (no
redundancy).
Origin Area where the event occurred.
Table 17-2 Event Attributes

The exact event type names, used in event and alarm lists, are not necessarily identical to those used in
the table above. The name associated with each event type is set in the system configuration database in
section: Global/Event System/EventImage configuration parameter group 'Type Names'.
17.3 ‘Alarm State’ and ‘Acknowledge State’

Alarms report the state of a condition. Three states are distinguished:
www.kongsberg.com
State of Condition Description
Void Indicating that the alarm condition does not exist, only shown in historical lists.
Active Indicating that the alarm condition is present.
Normal Indicating that the alarm condition is no longer present.
Table 17-3 ‘Alarm State’ and ‘Acknowledge State’

Furthermore, alarms in the 'active' or 'normal' state can be 'acknowledged' or 'unacknowledged'.
The combination of 'alarm state' and 'acknowledge state' determines the legal transitions from one state to
another:
Active and
un-ack’ed
Normal and Active and

un-ack’ed ack’ed
Normal and
ack’ed or void
Table 17-4 ‘Alarm State’ and ‘Acknowledge State’ Transitions
17.4 Alarm Limits

Digital alarms are either active or not (VOID and NORMAL). For alarms on analogue terminals,
however, the active state is further refined by means of alarm limits as illustrated below:
www.kongsberg.com
High process values As long as the terminal value is at
least equal to the limit but does not
High Scale
High Scale limit reach the next limit, the
HighHigh corresponding alarm state is active.
HighHigh limit
High
E.g. On a scale from 0 to 100, the
Alarm limits
High limit
Low limit is set to 15 and the
Normal / Void
Low limit
LowLow limit is set to 5. A Low
Low alarm is activated as 15  terminal
LowLow limit value > 5.
LowLow
Low Scale limit
Low Scale
Low process values
Table 17-5 Alarm Limits
 An analogue alarm is in 'normal' or 'void' state as long as the terminal value remains within
the High and Low alarm limits. In other words, the alarm is not active.
 The alarm becomes active when the terminal has reached the High or Low alarm limits but is
within the HighHigh or LowLow alarm limits.
 When the terminal value has reached the HighHigh or LowLow alarm limits but is within the
HighScale or Low Scale, a new limit is passed.
 The highest alarm limit is reached when the terminal value equals or exceeds the Scale High
or ScaleLow limits.
17.5 Alarm Changes

Alarm changes are classified as 'major', 'minor' or 'value' changes.
Major changes are alarm state changes defined by the following rules:
S/N Description
1 The alarm state changes from void to active.
2 The state of an acknowledged alarm increases to a worse alarm state.
3 The state of an unacknowledged alarm increases to a worse alarm state than
reported earlier since the alarm became unacknowledged (only relevant for
analogue alarms).
4 The state of an acknowledged alarm changes polarity, for example from High to
Low.
5 An unacknowledged alarm changes from suppressed to not suppress.
Table 17-6 Alarm Changes

Values changes are changes in acknowledge state or suppression defined according to the following rules:
www.kongsberg.com
1. An acknowledged alarm changes its suppression state
2. An un-acknowledged alarm becomes acknowledged.
All other changes are minor changes.
The rules are illustrated below. The arrows indicate major changes and the number refers to which of the
above rules is applied. Other crossings of the process value with an alarm limit, illustrate points of minor
changes. The acknowledging of the alarm is a value change.
Changes to the acknowledge state, and other changes to the alarm state, are minor changes.
These rules are illustrated in the figure:
Process values
High Scale 3
HighHigh 3 2
High 1
Time
Low 4
LowLow
Low Scale
Unacknowledged Acknowledged
Table 17-7 Values changes
All changes are reported, but major changes imply that the alarm timestamp is updated. Consequently, the
alarm is moved to the top of the alarm list, thus calling for more attention from the operator.
17.6 Alarm Priorities

The alarm system supports three priority levels, which are indicated with different colours. The alarm
priority / colour coding is:
1. Low priority alarms  Yellow colour

2. High priority alarms  Red colour
3. Critical priority alarms  Magenta colour
Low Priority Alarms High Priority Alarms Critical Priority Alarms

Number  1 2 3
Colour  Yellow Red Magenta
www.kongsberg.com
Low Priority Alarms High Priority Alarms Critical Priority Alarms
Normally Alarms for auxiliary and Alarms that will lead to Fire and Gas alarms and
used for  machinery systems which shutdown of main ESD.
will not lead to shutdown machinery systems and System alarms.
of main machinery other alarms of high
systems. severity.
System alarms. System alarms.
Table 17-8 Alarm Priorities
4. Fire & Gas Alarms  Emergency Priority

5. Digital Shutdown and Trip Alarms  High Priority
6. All Other Digital Alarms  Low Priority
7. Analog Alarms  HH=High Priority
 LL=High Priority
 L=Low Priority
 H=Low Priority
NB: The alarm philosophy should be specified by the Customer!
17.7 Alarm Suppression

Alarm systems offer a feature called 'alarm suppression'. The intention of this feature is to reduce operator
stress by holding back alarms that in some temporary system state are more or less unwanted. The alarm
property 'suppressed' indicates that the alarm is normally not intended for operator attention. Some
systems allow the operator to explicitly suppress unwanted alarms. Alarms suppressed by the operator are
called 'disabled alarms'. Alarms can also be suppressed by the means of SW-configurations. E.g. when a
pump is NOT running it should suppress the pump discharge pressure module to not give an alarm.
17.8 Alarm Acknowledgement

Whether an alarm needs acknowledgement depends on its priority level. The priority level that marks the
limit is set in the Global/Event System configuration parameter: 'AckLimit'. All events with a priority
level at or above the 'AckLimit' need to be acknowledged. There is one exception: At OS start-up, the
‘station availability’ alarms caused by missing response from some station do not require
acknowledgement.
Acknowledgeable alarms must be acknowledged explicitly by the operator. Acknowledgeable alarms

become unacknowledged upon major alarm changes.
The possible acknowledge states are 'Acknowledged' and 'Unacknowledged'.
www.kongsberg.com
17.8.1 Acknowledgement Authority
The authority to acknowledge alarms is built on commando control and access system configuration:
 An OS can only acknowledge those process alarms that are originated by the function
modules controlled by that OS. This authority is exclusive: Process alarm cannot be
acknowledged from an OS that does not control the source function module (Which command
group the module belongs to).
 An OS can acknowledge system alarms originated by itself or by controlled RCU. A RCU is
controlled by the OS when it contains a function module under a command group that is
controlled by the OS in question.
 An OS can acknowledge system alarms for not-controlled RCU (if the Global/Event
System/Privileges configuration parameter 'Ack Extended' is set to 'TRUE' in the system
configuration database).
17.8.2 Acknowledge Methods

Alarms can be acknowledged:
 Using the ACK option in the context menu of the dynamic and static alarm list and the last
alarm line.
 Using the ACK button in the event image or event dialog toolbar.
 Using the ACK key on dedicated AIM operator panels.
17.8.3 Selection of Alarm for Acknowledgement

The authority to acknowledge alarms from the OS in question, is indicated in the left most column of the
list.
The effect of these actions depends on whether unacknowledged alarms are selected:
 When one or several unacknowledged alarms are selected, the acknowledge action applies to
selected alarms only.
 When no selection is made, the acknowledge action depends on the settings of the SysConf
Global/Event System/EventView parameter 'AckAllVisibleIfNoneSelected':
 If 'AckAllVisibleIfNoneSelected' is ‘TRUE’, all unacknowledged alarms in the current
alarm page are acknowledged.
 If 'AckAllVisibleIfNoneSelected' is ‘FALSE’, none of the unacknowledged alarms are
acknowledged.
17.8.4 Shelving Alarms

In the Alarm system the operator can shelve alarms. E.g. if one transmitter have alarm because of fault
and we do not have time to change/repair it now, then we can shelve it and repair the transmitter at a later
time.
We can also set a time limit when shelving the alarm. After the time limit, the alarm will appear on the
alarm list again.
www.kongsberg.com
As opposed to disabling alarms which only disables alarm for 10 minutes, shelving alarms can be done
for a longer timespan. Will also be reset if alarm condition is reset.
17.9 Alarm Groups
17.9.1 Purpose
This document is a guideline for offline configuration of alarm groups in the K-Chief 700 system. The
purpose of alarm group definitions is to suppress alarms based on defined conditions.
17.9.1.1 Terminology
In this document alarm suppression will have the following features in K-Chief 700:
 Annunciation is turned off (no sound and no entrance in alarm list with default filter)
 A suppressed alarm will enter the log with acknowledged state
 In the Process view presentation, the alarm is shown as suppressed (Suppress colour, normally
Cyan)
 Only process alarms can be suppressed. System alarm must be handled by other means, when
possible (e.g. IO alarms can be suppressed in certain cases by settings in the IO drivers)
17.9.1.2 Group types and intended use

There are four types of groups in the AIM alarm group system. These are
 First up
 Group
 Logical
 Aggregated
The next subsections contain a brief description of the functionality for the different groups.
The groups normally used are Logical or First up. For a Logical group, a condition for alarm suppression
must be specified. This condition can be a logical expression based on a set of terminal states and io
signal states, see further description in the following sections.
17.9.1.3 First up
In a first up group, only the first member entering active state will be alarmed to the operator, and all
other alarms entering active state will be suppressed. The suppression is active as long as there are active
alarms in the group. If the first alarm goes to normal state and it is acknowledged, the next active alarm
will be shown. This will continue until all alarms are in normal state and acknowledged.
First up group are intended to be used in situations where a set of alarms will cause the same action. This
is typically used for shutdown levels and equipment protection trips.
www.kongsberg.com
17.9.1.4 Group
All members in a group alarm are suppressed. When a member in the group is entering active state a
common alarm is raised. When all alarms are in normal state, the common group alarm is also in normal
state.
The group alarm is typically used where the operator shall be warned about a situation that has occurred,
but does not need any details. The reason for the individual alarms is for presentation in detailed pictures,
for fault finding and/or maintenance purpose.
17.9.1.5 Logical
Logical alarm groups will suppress the member alarms in the group as long as the logical expression is
true (reset when false). Using several such groups for the same set of alarms is used to form context based
suppression, e.g. different logical expressions may suppress the same set of alarms.
The logical groups are normally used for process/utility systems which have different contexts (e.g.
stopped, running, shut down, maintenance etc.)
Since all alarm members in the group are suppressed, it is important that there are other unsuppressed
alarms to inform the operator of the situation.
17.9.1.6 Aggregated
Aggregated alarm group is the only group that does not suppress any alarms; it generates a new alarm
when all member alarms in the group are in active state. The alarm goes to normal state when at least one
of the member alarms is back in normal state.
This type of alarm group is used when the state of a number of basic alarms together describe the state of
a process system or sub-system more precisely than a single alarm.
17.9.1.7 The Verification Process

When a proposal for alarm suppression is received from the yard, KM will run a verification process on
the received specification (Excel file format expected)
This process will:
 Check syntax of groups, group expressions and alarm members.

 Check that conditions are based on existing tags & terminals.
 Check that suppressed alarms exist in the system.
 Check that the setup is with the system limitations.
 Alarm generated by tags not found in the yard io-list may be added.
Diagnostic messages will be transmitted to the yard for correction.
The verification of the final result will be done by KM, first in a test environment.
www.kongsberg.com
For a final test, the alarm suppression setup must be included in the onboard system, and sufficient test
cases prepared.
The main items of the proposed process are described in a simple flowchart below.
www.kongsberg.com
KM Yard/Owner
responsibility responsibility
Prepare Prepare alarm

initial Alarm list suppression
alarm list group list
System
configuration
Alarm
group list
Verify
alarm Correction Update alarm
group list proposals suppression
group list
Updated
Alarm
group list
Verification completed
Onboard
test
Final alarm
suppression
test report
Flow of activities proposed for preparing an alarm suppression configuration.
www.kongsberg.com
18 Time Series System
The time series system allows you to define and retrieve historical time series of logged process values
for use in reports and Trend images.
18.1 Main Features

In short, a time series is a log of time-stamped values. It extracts data from a single variable as input,
performs a mathematical transformation and stores resulting values according to the selected time series
attributes.
 The time series system provides the functionality to:

 Select input variable
 Define, modify and delete time series definitions
 Store and distribute time series definitions.
 Data to be trended at not less than the sample rate booth for short-term and long term.
Beside time series definition, data storage is an important aspect of the time series system: While short-
term time series can be stored on the RCU, long-term time series require the storage capacity of a HS.
It is possible to define both permanent and temporary time series.
Data stored in time series are in turn input for trends and reports.
The time series system description covers the following main topics:
 Time series
 Transformations
18.2 Time Series

A time series is a log of status- and time-stamped values: It receives data, manipulates them, and stores
the results. Logically, a time series consists of a definition part and a data storage part. In the illustration
below, the white boxes represent the data parts while the text without boxes represents the definition part.
TS definition
TS definition
Primary Secondary
Data source
time-series time-series
Table 18-1 Time Series Types

The life span of time series can be defined as follows:
www.kongsberg.com
 Permanent time series: In principle, a permanent time series is not limited in time, but the
number of data elements it can contain is limited. That means that new data elements are
added and old ones are purged as time progresses.
time
Data element
Time-series
Series length
Table 18-2 Time Series Length

 Temporary time series: Optionally, an absolute expiration date and time can be set,
cancelling the data collection and deleting the time series definition automatically at
expiration time. Defining temporary time series does not require RCU configuration
privileges.
The obvious data source for time series is an AIM module variable - i.e. a terminal or a 'logable'
parameter. However, time series can take input from other data sources too. The data source determines
whether the time series definition is stored on the RCU or on a HS.
According to the data manipulation they perform, time series are classified as:
 Primary time series storing raw data: i.e. they fetch data and store them without further
manipulation. Only one primary time series per variable can exist on a single station (RCU or
HS).
 Secondary time series applying mathematical transformations to a set of data elements stored
in another time series. The secondary time series contains the result of the transformation.
Short term time series, covering minutes or hours, can be stored on the RCU that owns the module
providing the data input.
18.3 Data Sources

18.3.1 Input and Data Source
It is important to understand the difference between 'input' and 'data source': A time series takes input
either from a data source or from another time series. Input from other time series is not a 'data source'.
The data source refers always to the origin of the data. Consequently, a secondary time series takes input
from another time series, but the data source for both is either an analogue or digital data source.
Among the data sources two main categories are distinguished:
 RCU resident data sources

 External data sources.
The data source determines where the time series definition is stored.
www.kongsberg.com
18.3.2 RCU Resident Data Sources
The most obvious data source for time series is a RCU resident module variable. Any module terminal
and those module parameters that are exported for logging - i.e. module parameters of the data type
LOGVAR can act as input for primary time series on the RCU.
The definition of time series that take input from a module variable are always stored on the RCU.
18.3.3 External Data Sources

Using the ODBC interface, external applications may act as data source for time series on the HS. The
definition of the time series that take input from an external source is always stored on the HS.
www.kongsberg.com
18.4 Time Series Categories
RCU HS
TS definition
TS definition
TS definition
TS definition
Module Primary Secondary Primary Secondary

variable time-series time-series time-series time-series
TS definition
TS definition
Primary Secondary
time-series time-series
TS definition TS definition
External
APA
application
ODBC
External Primary Secondary

application time-series time-series
OPC
External
application
Table 18-3 Time Series Categories

The following time series categories are distinguished, based on the data source, the data manipulation
they perform and the type of station where they are stored:
18.4.1 RCU Primary Time Series

The data source is a module variable that belongs to a tag owned by the RCU in question. The input data
are not manipulated. The sampling rate for the time series is defined by the configured task. The time
series definition is stored on the RCU in question. The time series data are stored on the RCU.
A RCU primary time series can be the parent of:
 RCU secondary time series

 HS primary time series.
18.4.2 RCU Secondary Time Series

Takes input from a primary or secondary time series on the same RCU. Input data are transformed
according to a transformation template resident on the OS. The time series definition and data are stored
on the RCU in question.
A RCU secondary time series can be the parent of:
 RCU secondary time series
www.kongsberg.com
 HS primary time series.
Note! Secondary time series are created through continuous calculation. This
makes it possible to create a 24 hours average based on a primary time
series which is far shorter than 24 hours. The required length of the
primary series is 15 second.
18.4.3 HS Primary Time Series

HS primary time series can take input from either a RCU time series or an external data source.
Data Source Transformation TS Definition TS Data Storage

RCU None On RCU On HS
External source None On HS On HS
Table 18-4 HS Primary Time Series
A HS primary time series can be parent for HS secondary time series.
18.4.4 HS Secondary Time Series

Takes input from a primary or secondary time series on the HS. Again, the data source for the original
variable, determines where the time series is stored.
Data Source Transformation TS Definition TS Data Storage

RCU Calculated on PCU On RCU On HS
External source Calculated on HS On HS On HS
Table 18-5 HS Secondary Time Series

A HS secondary time series can be parent for other HS secondary time series.
www.kongsberg.com
18.5 Time Series Definition
A user's possibility to look up, create and manipulate time series definitions is determined by the
combination of the following conditions:
 Whether the actual OS is in command of the command group to which the module belongs
 Whether the user is a member of a user group that includes the TSConfigure security object
 Whether the OS runs in PCU configuration mode.
Time Series Command Control TSConfigure Security PCU Configuration

Definition Object Mode
Lock-up Does not matter Does not matter Does not matter
Create new, modify Required Required Not required for
or delete temporary time series
that expire on time.
Required for permanent
time series.
Table 18-6 Time Series Definition
www.kongsberg.com
19 Trend System
The Trend system is used for presentation of trends. It uses split window mechanisms to create and
present one or several trends as separate panes in a trend image. Each trend may contain one or several
trend curves.
The AIM Trend System contains functions for controlling the displaying, creation and appearance of
trends.
19.1 Trends
A trend is a presentation of one or several trend curves in a scaled axis system. You can both configure
the trend with its contents and operate on the displayed trend by using a dedicated trend context menu.
This context menu applies to the trend from which it was launched (this is significant when two or more
trends are displayed simultaneously).
19.1.1 Trend Presentations

There are two different types of trend presentation:
 Trend Image, which fills the main view area and may comprise several trends contained in
separate panes. You can add, split or merge trend panes by using splitter window techniques.
 Trend Popup, which comprise a single trend in a re-sizeable popup window. The popup
remains displayed irrespective of the view selected and can be positioned anywhere within the
main view area.
Both trend presentations have a context menu that you can use to control their appearance.
19.1.2 Trend Types

There are two trend types:
 Time Trend, which shows the development of single process values with the progress of time.
 XY Trend, which shows the correlation between two process values within a defined time
span.
19.1.3 Trend Data Sources

There are three types of data sources for trends:
 Current value subscription, which is a subscription of a process variable, i.e. the current
value of module terminal or a 'logable' parameter.
 RCU time series, which is a time series stored on a RCU.
 HS time series, which is a time series stored on a HS.
Trend curves with a current value subscription as the only data source will initially be empty.
A trend curve will normally display data merged from several sources simultaneously. The part of the
curve read from the HS will be displayed as a dashed line until the reading is complete.
www.kongsberg.com
19.1.4 Dynamic and Static Modes
There are two types of trend presentation modes:
 Dynamic mode. When a trend is launched, it is by default displayed in dynamic mode. The
process value history is read from a RCU or a HS (if time series has been defined) and new
values are automatically appended to the trend curves as they are produced.
 Static mode. The operator may choose to enter the static mode to be able to inspect the
process value history more carefully. In this mode, new values will not be appended to the
curves and the display will be frozen. If all curves in the trend have support from time series
stored on a HS, the operator may now inspect the process value history by navigating along
the time axis.

Following trend images are made:
See Setup : 5.11 Configuration Set-up Trend
More trends can be added by user with access right to configure time series and making trend image
views.
www.kongsberg.com
20 Report System
The report system lets you design and generate reports. It provides report management, including report
scheduling, storage, printing and mailing.
This section contains the conceptual description of the report system. To fully understand all of the report
system, you should have a good understanding of:
 Time-series
 Event system
20.1 Report Mechanism

20.1.1 Overview
Operator
Clock
Event
Monitor
AIM Time- ODBC Generated Report Printer

series
Export
Version
control
system
AIM Event ODBC Prepared Report
database Report
archive
Customer
specific ODBC
data source
Time limits
Table 20-1 Report Mechanism
The main purpose of the AIM report system is to generate reports where the data is:
 fetched from the AIM system through ODBC

 presented according to a suitable layout
20.1.2 Prepared Reports and Generated Reports

The basis for an AIM report is a 'prepared report' which is a description of the data source, conditional
data selection and output format for a report. The prepared report does not contain data. Prepared reports
www.kongsberg.com
must be stored under the base path for prepared reports, defined in the Configure Report Manager dialog
box.
Prepared reports run on the OS, may prompt the user for a time span, adapting the report definition
accordingly, before producing a 'generated report': i.e. a report that contains data.
Generated reports can be displayed, printed and stored in a file in different formats. The path for storage
of generated reports is defined in the Configure Report Manager dialog box.
A prepared report is created online from one of the report templates that follow with the report system.
When applying a template, it is sufficient to assign appropriate values to the report parameters in the
prepared report.
Report templates are designed offline using the Crystal Report Designer, a commercial third party
product. The result of a report designed using the Crystal Reports system, is an .rpt file. Moving the .rpt
files to the appropriate path in the OS file structure, makes them available as report template. The base
path for storage of report templates is defined in the Configure Report Manager dialog box.
20.1.3 Triggering Report Generation

Report generation can be initiated in different ways:
 Interactively by the user: I.e. you select a prepared report and run it. The result is a 'generated'
report containing data fetched from the data source, and presented in a separate window on
the OS.
 Scheduled by the OS according to the schedule parameter settings of a report job. I.e. the
system clock triggers a prepared report to be run. A scheduled report is stored in the report
archive, but not displayed, automatically.
 Process event-triggered reports: A configured AIM function module trig_rep can trigger a
defined report job. The generated report is not displayed automatically.
www.kongsberg.com
20.1.4 Report Management
Prepared Report: Output alternatives:
Interactively Displayed report
Report archive
Printed report
Scheduled
Report jobs Exported report
By event
Table 20-2 Report Management
Depending on how the report generation was initiated, reports can be stored, displayed, printed, exported
or mailed.
20.1.5 Displaying Reports

AIM displays reports in popup windows. The specific report popup window includes appropriate controls
to browse, scroll, scale, print and store and mail the report. Each report is presented in a single window
that pops up on top of the AIM OS application. Interactive reports are displayed automatically as they are
run while historic reports are displayed upon request. Scheduled reports, generated according to the
specifications of a report job are not displayed automatically.
20.1.6 Report Print-out

Generated reports can be printed on any printer available to the OS.
Printing of displayed reports can be initiated from the appropriate control in the report window.
Scheduled report may be configured to print the report upon generation.
20.1.7 Report Storage

Reports can be converted to a large range of formats and stored in any destination that can be reached
from the OS. Storage of displayed reports can be initiated from the appropriate control in the report
window while scheduled reports may be configured to store the report upon generation.
20.1.8 Report Types

The report system has possibilities for the following types of reports:
 Daily Reports
www.kongsberg.com
 This report uses data from the history station. By specifying a certain time window data
from time series can be called and several mathematics functions can be used.
 Hour Count Report
 This report is used to show the accumulated running hours on rotating equipment.
 Interactive Reports
 This report uses dynamic process variables from the RCUs. It can be printed either cyclic
or on request.

Report station.
Note! All OSs have all reports.
www.kongsberg.com

K Chief 700

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

K Chief 700

Încărcat de

Drepturi de autor:

Formate disponibile

Kongsberg Functional Design Document

Product: K-Chief 700

Synopsis: This document describes the Common System

Document Number: Revision: A

Customer doc no. Document version: 2.0

Contract number: Number of pages: 122

A 01.12.12 AsBuilt AA BBB CCC

©Kongsberg Maritime Page 1 of 122

Revision Description of Change

©Kongsberg Maritime Page 2 of 122

2 Software package ................................................................................................. 14

4 Project Specific Configuration ........................................................................... 17

7 KM Standard colour definition .......................................................................... 58

8 K-Chief 700 .......................................................................................................... 58

9 Operator Stations ................................................................................................ 68

10 History Station ..................................................................................................... 71

11 Field Stations ........................................................................................................ 75

12 Network Distribution Units ................................................................................ 80

13 Images and Navigation ........................................................................................ 82

14 Access Control System ........................................................................................ 87

©Kongsberg Maritime Page 5 of 122

16 Version Control System ...................................................................................... 94

17 Event System ...................................................................................................... 100

©Kongsberg Maritime Page 6 of 122

18 Time Series System ............................................................................................ 111

19 Trend System ..................................................................................................... 117

20 Report System .................................................................................................... 119

©Kongsberg Maritime Page 7 of 122

©Kongsberg Maritime Page 8 of 122

- Reads data from the input terminals

©Kongsberg Maritime Page 9 of 122

Part of a system can be an analogue measurement, a valve, a motor starter, etc.

©Kongsberg Maritime Page 10 of 122

- Scan task 1 (1Hz)

CCR Cargo Control Room

CTS Custody Transfer System

EER Electrical Equipment Room

ECR Engine Control Room

ESD Emergency Shutdown

F&G Fire and Gas

GCU Gas Combustion Unit

HD High Duty Compressor

©Kongsberg Maritime Page 11 of 122

I/O Input / output

IAS Integrated Automation System

LAN Local Area Network

LD Low Duty Compressor

LNG Liquefied Natural Gas

LV Low Voltage (440V / 220 V systems)

MCC Motor Control Centre

NDU Net Distribution Unit

PCU Process Control Unit

PMS Power Management System

PS Process Station, Process Control Cabinet

RCU Remote Control Unit

VDU Video Display Unit

©Kongsberg Maritime Page 12 of 122

©Kongsberg Maritime Page 13 of 122

 Microsoft Windows XP Professional

©Kongsberg Maritime Page 14 of 122

3.1 The Integrated Automation System

Increased safety due to

 Redundant communication network