K-Chief 600 Presentation

You might also like

Download as pdf or txt
Download as pdf or txt
You are on page 1of 52

K-Chief 600

KONGSBERG PROPRIETARY: This document contains KONGSBERG information which is proprietary and confidential. Any disclosure, copying, distribution or use is prohibited if not otherwise explicitly agreed with KONGSBERG in writing. Any authorised reproduction in whole or in part, must include this legend. © 2015 KONGSBERG – All rights reserved.
Chapter 1
K-Chief 600 functional description(standard
alarm and monitoring system)

• Alarm detection: analogue, digital, on/off with line


check.
• Alarm inhibition
• Alarm and monitoring display
• Alarm events
• Watch calling system
• Access and control transfer
• User interface
• System Architecture, LAN and CAN
Chapter 1
K-Chief 600 functional description(standard
alarm and monitoring system)

• Alarm detection:
Instrument failure, Low-Low, Low, High, High-High, filters on signal,
time delay on alarm and return status, line broken, line short. Alarm state
indication.
• Alarm Inhibition:
inhibit source, time delay for inhibition situation.
• Alarm and monitoring display:
Alarm pages: alarm group, active alarms, alarm history.
Monitoring pages: group display, tag details, custom view.
Chapter 1
K-Chief 600 functional description(standard
alarm and monitoring system)

• Alarm events:
Parameters enter an alarm state. Handling of events.
Watch Calling System:
Extend the alarm information to accommodation area where the duty
engineer is.
Set duty engineer/officer
Transfer duty watch to bridge.
• Access and control transfer:
Equipment control must be only available from one location at a time.
• User interface:
Topbar, alarm side bar, Navigation line, operator dialogues , tabular
views, process views, custom views, trend views.
Chapter 1
K-Chief 600 functional description(standard
alarm and monitoring system)
Chapter 1
K-Chief 600 functional description(standard
alarm and monitoring system)

System Architecture, LAN and CAN


Watch calling system architecture .

Lan: Ethernet, TCP/IP,KM standard


interface program ,communicate
between Oses and PC based
equipment.

CAN: control area network, highly


reliable process bus used for
communication between the DPUs
Chapter 2
K-Chief 600 system configuration

The control system is used in a wide range of KM


applications:

• K-Gauge tank management


• Machinery Instrumentation for Engine Protection
• Vessel Performance System
• AutoChief®C20 ,600 propulsion control system
• Thruster Control system
• Kongsberg Ship@Web system
• K-Remote and K-Loading
Chapter 3
K-Chief 600 system main hardware components

• SCU
• DGU
• RAi-16xe,RAi-10tcxe,
• RAo-8xe,
• RDi-32xe,RDi-32Axe,
• RDo-16xe
Chapter 3
K-Chief 600 system main hardware components

• SCU:
• Functions
Features
• Responsible for routing data, both • Standard Fast Ethernet, 100Base-X
real-time and service-data. Fast Ethernet.
• Alarm system including local • Industrial Ethernet, POWERLINK,
timestamp. is CANopen over Ethernet with
real-time capabilities (optional).
• Programmable Logical Controller
• CANopen maritime (CiA 307).
• (KM Flexi modules). • Communication line redundancy.
• Pre-programmed logic • No serviceable parts inside module
and remote control of ship • All connections are plugable.
• auxilliary equipment and power • Easy hardware replacement:
Software and configuration
management.
download to DPU’s on local CAN
Chapter 3
K-Chief 600 system main hardware components
Chapter 3
K-Chief 600 system main hardware components

• The DGU contains four CAN-buses and two RS422/485


serial lines. Each port is galvanically isolated.
Chapter 3
K-Chief 600 system main hardware components

• RAi-16xe
Chapter 3
K-Chief 600 system main hardware components
K-Chief 600
Alarm Philosophy
Alarm Priorities, Colours and
Buttons
Emergency alarm – requires immediate action
Alarm – requires action
Warning – requires attention
Info (caution ) – requires attention (lowest priority)
Inhibit – alarm is blocked by process.
Offscan – alarm is blocked by operator
Invalid - alarm cannot be presented due missing
communication to the DPU.

Alarm acknowledge Alarm sound off


The top bar
The two most recent unacknowledged alarms are always shown
in the top bar. A single click in the top bar provides an extended
list of unacknowledged alarms in the system.

The top bar and alarm lines will always be accessible. Hence it is not
possible to cover the top bar by for example dialogues.
Alarm side bar Dock
Alarm groups can be docked and undocked to show group information

The alarm group information is shown as


an expandable menu on the left side of
the screen. An extended menu will appear
when moving the cursor to the left side of
the alarm group bar. This menu contains
buttons with the name of the alarm
groups together with the number of active
alarms.

Alarm group pop-up window


When clicking an alarm group, the list of
active alarms will pop-up in a dedicated
secondary window.
Show all tags in group
The context menu is accessible by right–clicking
on an alarm group in the expanded alarm view.

Selecting Show all tags in group will


open the Tag summary view for the
alarms in this group.
Acknowledge Alarms
An alarm is acknowledged by single-clicking the alarm cell
of the tabular view. When the alarm is acknowledged, the
content of the cell is changed; The button disappears, the
coloured area is made smaller, and a check mark appears.

When Acknowledge
Alarms in Tabular
view - Active Alarms,
all visible Alarms will
be Acknowledged
Active Alarms

The Active alarms view is used to display the following alarms:


• Active acknowledged alarms
• Active unacknowledged alarms
• Unacknowledged alarms returned to normal
This is the main view for evaluation and acknowledging of incoming alarms. As soon as a
new alarm is generated, the information in this view is dynamically updated.
Alarm History

The Alarm history view is used to display the following alarms:


• Active acknowledged alarms
• Active unacknowledged alarms
• Acknowledged alarms returned to normal
• Unacknowledged alarms returned to normal
• Local time change events
Event History

The Event history view is used to report the following events:


• All alarm events.
• Tag state changes (inhibit, offscan , alarm )
• Change of user access log-in and command control. Only successful command transfers are
logged.
• Changes of tag parameters.
• All process events (for example start/stop, open/close, connect/disconnect).
• Change of time zone.
Alarm test button

Choose Menu – Alarms – Alarm test

This is a SW function to test/activate the


Alarm functionality as sound, light and
horn
K-Chief 600
Trends Reports & Custom view
Trend views
A trend view is used to display recorded and present data for
selected alarm parameters.

• Tools and options


area
• View area
• Tag details area
Backward Trend setup

Choose Select on the tools menu

Max backward trend 7 days. Long trend 5


years when integrated to Ship@Web.
Trend from Object menu – Tag details

Live trend from tag details, max 12 minutes span


Custom View setup

Chose custom view 1 and click


Add tags.

Filter by Alarm groups, Tag or


description.

Double click selected tag to


add in Custom view.

Add tag is also an option.


Custom view presentation

Selected tags will default show as list.


Under convert you have options for other views of all tags or
just some selected tags
Custom view layout
Opens “Convert” menu

Gauge view Bargraph view


K-Chief 600
Tag Details
Tag details view

Show Tag details by Use the pin to open multiple Tag


expanding the operating menu details view for comparison
Tag Summary tab

Tag summary tab gives you general info


such as signal type, DPU and channel
number.
Trend tab
This tab contains live trend with a maximum span of 12 minutes.
Freeze and zoom is possible, but not save or backward trending.
Control tag trends contains all referenced tags.
Alarm parameters
Change or add alarm limits. In This shows you which alarm
this case only High and Low are group the tag belongs to.
enabled.
Parameters tab
It is possible to adjust some of tags parameters (requires
Power user logon ).
K-Chief 600
Access Control
The purpose of command control
The purpose of command control is to transfer command right.
In some cases also alarm acknowledge rights can be transfered.
Command control structure
Alarm groups are groupped in Control groups.
All operator stations are grouped
Each control group must have one default control position.
Other control positions can have different priveledges to each control
group.
OS command control dialogue
Command Controls
Command Control
Control Groups
How to request Command
Highlight Control Group

Click Take button


Override function can be use in case of emergency (requires Poweruser
logon)
Emergency override activation
Override is used when control is needed in case of emergency
1. Log on as poweruser (Chief)
2. Click Override single group or Override all groups
3. Enter your poweruser (Chief) password again to confirm override.
Emergency override deactivation
To deactivate override:
Select the overriden group and click Return button.

After 1 minute of user inactivity a dialogue will


be displayed counting 1 minute to automatic
command return to default control position ( if
not confirmed by “Continue override” )
Top bar command button status
K-Chief 600
Ship@Web
Background

• Since DataChief 2000 the FleetMaster has given the officers


and the owners the possibilities to monitor the system from
any location on board the vessel
• The FleetMaster used on DC2000, DataChief C20 and K-Chief
500 is based on old technology that requires time consuming
installations and specific computers for runtime
• To continue delivering services outside the process network of
K-Chief 600, the Ship@Web project was started
Login page
Login page
Illustration only and gives an idea about how
Ship@Web could be used in the future
Home/Portal page

Ship@Web applications:
• Viewer
• Trend
• Report Designer
• Report Generator

• Logged in as an administrator, you can


control user accounts, upload images and
adjust different settings.

• Which applications available is project


dependent
• Access to applications are controlled by
user rights
Viewer - Overview
• Primary functions are:
– The user can access the Ship@Web by using a web
browser on any PC on the ship network
– Display process mimics from the K-Chief 600
– Display Alarm groups
– Display alarms, tag values and history through list views
such as Active Alarms, Alarm History, Tag summary, Event
History, Inhibit tags, Overriden tags, Counters, Tank list etc.

• Simple navigation similar to K-Chief 600

• Choose between day or night color palettes


• Filter and sort functionality in all table views makes it easier to find
the correct information
• Views are refreshed automatically dependent of bandwidth
settings for each user
• Warning messages is not only given on the K-Chief OS, but also to
the web page so that the user knows if the tags in the view can be
trusted or not. (Network problem / missing tag updates)
• Can also be used on shore if the ship owner has a fast and
affordable broadband connection to the ship (Not KM delivery)
Trend - Overview
• Each user can define a unlimited number of Trend views
• Each view can be named after own wish
• A preferred view can be defined for each user
• Adjustable x and y scale. Auto, default or manually
• Static- / Live view
• one month high resolution history
• Up to five years of compressed history
• Different views for analog and digital tags
• Highlight tags and include alarm limits

• Export of trend data as .csv


• Easy to use tag manager
• Free text search
• Sort by alarm group
• Sort alphabetically
• Hide tags temporarily without deleting them from the view
• Change graph colors
kongsberg.com

You might also like