So1077 b Training and Evalu

8/13/2019 So1077 b Training and Evalu

1/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03

TEC Instructor's Manual for Neptune

TRAINING AND EVALUATION

CONTROL (TEC)

INSTRUCTORS MANUAL

For Neptune

Department/Author: Approved by:

Hkon Dyrvik (s) Harald Kluken (s)

2003 KONGSBERG MARITIME SHIP SYSTEMS ASAll rights reserved

No part of this work covered by the copyrighthereon may be reproduced or otherwise copied

without prior permission fromKONGSBERG MARITIME SHIP SYSTEMS AS


2/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03

TEC Instructor's Manual for Neptune i

DOCUMENT STATUS

Issue No. Date/Year Inc. by Issue No. Date/Year Inc. by

SO-1077-A 11-Feb-03 HK/bebaSO-1077-B 4-Mar-03 HK/beba

CHANGES IN DOCUMENT

Issue ECO Paragraph Paragraph Heading/No. No. No. Description of Change

B MP 8 Event Based Action added.


3/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03

TEC Instructor's Manual for Neptune ii

TABLE OF CONTENTSSection Page

1 GENERAL....................................................................... 11.1 Terms and expressions................................................... 2

2 TO START THE SIMULATION ................................................ 42.1 To load an exercise........................................................ 5

2.2 To save an exercise........................................................ 62.3 To stop the simulation.................................................... 7

2.4 Instructor Monitor Unit ................................................... 82.4.1 TEC Instructor displays................................................... 82.4.2 Pages .........................................................................11

2.5 Screen Layout and Operations ........................................12

2.5.1 Heading Bars ...............................................................122.6 Keyboard Function Keys.................................................132.7 The mouse ..................................................................14

2.8 Template.....................................................................14

3 THE OPERATING CONDITION DISPLAY ................................. 15

3.1 Operating Condition Display............................................153.2 Access : Instructor, Operator 3, Operator 2, Operator 1 ......16

3.2.1 Access Control .............................................................173.3 Fixed Process : Air, Steam, Level / Temp, Ship Speed.........193.4 Inhibit : Alarm Horn, AC Buzzer, ECR Bell, Keyboard Buzzer.19

3.5 Dynamic Response : Levels, Process Dynamics, Ship Dynamics20

4 INITIAL CONDITION DISPLAY ........................................... 23

4.1 The Initial Condition display............................................234.2 Initial Condition Directory Display....................................23

4.3 Exercise 1 ...................................................................27

5 RUN&FREEZE.............................................................. 28

5.1 Run............................................................................28 5.2 Freeze ........................................................................285.3 Exercise 1 ...................................................................29

6 SCENARIOS.................................................................. 306.1 Scenario Display...........................................................30

6.2 Exercise 2 ...................................................................35

7 MALFUNCTION EDITOR.................................................... 36

7.1 Malfunction Editor Display..............................................377.1.1 My first Scenario where Time based Malfunction is included..37

7.1.2 Testing the result of the Time Based Malfunction................407.1.3 My First Scenario where Event based Malfuntion is included .417.1.4 Testing the result of the Event Based Malfunction...............42

8 ACTION EDITOR............................................................ 44


4/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03

TEC Instructor's Manual for Neptune iii

8.1 Action Editor Display .....................................................45

8.1.1 Create an Action...........................................................458.1.2 My First Scenario where Time based Action is included........46

8.1.3 Testing the result of the Time Based Action.......................48

8.2 Event Based Action .......................................................508.2.1 Testing the result of the Event Based Action......................52

8.3 Exercise 3 ...................................................................54

9 THETIME EDITOR.......................................................... 56

9.1 The Time Editor Display.................................................569.2 Time Editor Procedures..................................................58

9.2.1 How to control scenario progression.................................58

10 THE EVENT EDITOR........................................................ 59

10.1 What is the Event Editor? ...............................................5910.2 Event Editor Display......................................................5910.3 Event Editor Procedures.................................................61

10.3.1 How to change event specification...................................61

11 THE EVALUATION EDITOR................................................ 62

11.1 What is the Evaluation Editor..........................................6211.2 How is the Evaluation Editor operated?.............................62

11.3 The Evaluation Editor Display..........................................6311.4 Evaluation Editor Procedures...........................................6511.4.1 How to create an Evaluation ...........................................65

11.4.2 How to rename an Evaluation .........................................6511.4.3 How to copy an Evaluation .............................................66

11.4.4 How to delete an Evaluation ...........................................6611.4.5 How to start an Evaluation .............................................67

11.4.6 Description of the Weighting Factor..................................6711.5 Exercise 4 ...................................................................68

11.6 Exercise 5 ...................................................................7011.7 Exercise 6 ...................................................................72

12 SNAPSHOTS ................................................................. 75

12.1 What are Snapshots?.....................................................7512.2 How to take snapshots ..................................................75

12.3 Snapshot Directory Display.............................................7612.4 Hints related to Snapshots:............................................78

13 ALPHANUMERIC PAGES ................................................... 7913.1 Malfunction Pages.........................................................79

13.1.1 Content of the Malfunction Pages.....................................8013.2 Variable Pages .............................................................8113.3 Alarm Pages ................................................................81

14 REPLAY &BACKTRACK.................................................... 82

14.1 Backtrack ....................................................................82


5/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03

TEC Instructor's Manual for Neptune iv

14.2 Replay........................................................................82

14.3 Procedures ..................................................................8214.3.1 How to run a Replay......................................................82

14.3.2 How to do a Backtrack...................................................82

15 INSTRUCTOR MMIFUNCTIONS ....... ERROR!BOOKMARK NOT DEFINED.15.1 The Print Hard Copy Function. Error! Bookmark not defined.

15.1.1 What are Hard Copies........... Error! Bookmark not defined.15.1.2 How is a Hard Copy created.. Error! Bookmark not defined.

15.2 The Print Administrator......... Error! Bookmark not defined.15.2.1 What is the Print AdministratorError! Bookmark not defined.

15.2.2 How is the Print Administrator usedError! Bookmark not defined.15.3 The Disk Administrator ......... Error! Bookmark not defined.15.3.1 What is the Disk AdministratorError! Bookmark not defined.

15.3.2 How is the Disk Administrator usedError! Bookmark not defined.15.4 The Hpterm ........................ Error! Bookmark not defined.

15.4.1 What is the Hpterm.............. Error! Bookmark not defined.15.4.2 How is the Hpterm used........ Error! Bookmark not defined.

15.5 The DAT Administrator.......... Error! Bookmark not defined.15.5.1 What is the DAT AdministratorError! Bookmark not defined.

15.5.2 How is the DAT Administrator usedError! Bookmark not defined.

16 APPENDIX A:DELETE /CHANGE PASSWORDSERROR!BOOKMARK NOT DEFINED.

17 APPENDIX B:MAP UNIX DISK FROM A PCERROR!BOOKMARK NOT DEFINED.

17.1 Map Unix disk from a PC....... Error! Bookmark not defined.17.2 Printouts to file ................... Error! Bookmark not defined.

17.3 Trouble Shooting ................. Error! Bookmark not defined.

18 APPENDIX C:CHANGING DATA ACCESS LEVELERROR!BOOKMARK NOT DEFINED.


6/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03

TEC Instructor's Manual for Neptune 1

1 GENERALDepending on content of the contract each student and instructor station will have one or

two monitors. The TEC (Training, Evaluation and Control) instructor system is anexcellent tool for the instructor to efficiently prepare, control and evaluate students on a

predefined task. The Instructor system is built up by scenarios, and all scenarios can bemodified on-line, i.e. while the simulator is running, or created off-line. The on-line facilityis normally used during an ongoing exercise, when the student progress need to be

adjusted.

As a result of feed back from many of our customers, in combination with internaldevelopment projects, our various Engine Room and Cargo Handling Simulators(ERS/CHS) can offer our customers an efficient tool for instructors when organising and

conducting training on the simulators.

KMSS designed an instructor system focused on the following requirements:

* No need of previous computer knowledge

* Graphical screen communication

* Few strokes to execute a command

* All training based on scenarios

* All training can be evaluated on- line

* On-line stretching or compressing of the scenario, due to different student trainingprogress

* Each operator group can be trained and retrained by exactly the same scenario.

TheInstructorControlstheScenarioParameters

TEC

raining and Evaluation Control

Operator/StudentAction

EvaluationoftheOperator/StudentActions

INSTRUCTOR OPERATOR/STUDENT

SIMULATOR


7/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


1.1 Terms and expressionsExplanation of words and expressions used in this manual:

Expression ExplanationBacktrack Means to load a Snapshot and thus retrieve a previous

state of the simulation models. The simulation may thencontinue as normal from the retrieved state. (See also:

REPLAY.)

Button Is a defined function area within a display or page. It isdrawn in a 3D style. The function connected to the

button is activate/deactivate by pointing and clickingwith the mouse.

Column Is used in this manual when referring to a column (orbutton) in one of the screen displays.

Display Is the window covering the entire screen such as the

Scenario, Action and Malfunction Editors.

Field Means a defined data area within a display or within a

page. It contains alphanumeric information such asnumeric output, variable name, etc.

Initial Condition A state of the simulator which one may start a session

from. Initial conditions are stored as text files on thehard disk.

Instructor Action An action performed by the instructor, e.g., typing anumber or selecting something using the mouse.

Key Is one of the two physical keys on the mouse.

Page Refers to the information presented in the pop-upwindow overlaying the display currently presented.

Pop-up window Refers to the area (window) that appears (pops-up) onthe current display when a page is presented. The termused in this manual for this is PAGE.


8/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


Expression ExplanationReplay Is to repeat a simulation session partially or in whole.

This is done by loading a snapshot (backtrack) and then

all the instructor and operator commands/actions to thesimulation model are automatically repeated in the same

sequence as the original session.

Scenario Means instructor actions automatically executed atindividually specified times or as a result of an event. A

scenario may contain instructor initiated actions, such asstart/stop pumps, change ambient air temp., set/reset

malfunctions.

Select Refers to the action of using the mouse to position themarker in a specific area in a display or page and then

pressing the middle button on the mouse. i.e., pointingand clicking.

Snapshot Snapshots are stored and used as starting conditions forthe Replay feature. It should be noted that all snapshotsare deleted upon completion of a simulation session or

loading a new initial condition.

Variable Name A unique symbolic name that identifies a variable within

the simulation model.


9/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


2 TO START THE SIMULATION

When the various simulation applications have been installed into the PC (normally carriedout by KMSS) and the PC has been turned on, the Desktop will display the icon of thesimulator application(s) installed. The simulation model is available shortly after having

clicked twice on the icon. The program appears with the Picture directory of the simulationmodel.


10/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


2.1 To load an exercise(Click once in the Picture Directory to assure a blue coloured Top frame.)

1) Press F5 (Oper. Condition) on the keyboard.2) Select Init. Condition from the upper right corner (or Shift+F6 directly).

3) Select an Init Condition, and

4) Press function key F1 (Run)5) Press Home-key to get Picture Directory and select a Process Display to proceed in

order to reach training objectives of the exercise.


11/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


2.2 To save an exercise1.

To save the present situation for later use, Press F2 on the keyboard.2. Press F5 (Oper. Condition) on the keyboard.

3. Select Init. Condition from the upper right corner (or Shift+F6 directly).

4. At the lower left corner of the Init Condition there are three buttons.

5. Press Create, and a message appears next to Create

6. Click on the box next to I20, and type the name of the exercise, for example Crude OilWashing, press Enter, and in seconds you have saved an exercise for later use.


12/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


2.3 To stop the simulation1

To exit the simulation exercise, press F3 on the keyboard. At the lower left corner ofthe current display you are watching, a message appears.

2 type y or Y and press Enter.3 The simulation acknowledges the command by replying

4 The PC returns to the Desk top window, or to other application that may be runningsimultaneously.


13/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


2.4 Instructor Monitor UnitThe instructor has one or two colour graphic monitors for TEC Instructor displays and

Process displays. These are used when the instructor prepares, supervises or evaluates thetraining sessions.

Example of a TEC Instructor display Example of a Process display

2.4.1 TEC Instructor displaysAttached exists an overview of current TEC Instructor displays: Detailed description offunctionality is found in separate sections.

Operating Condition

Initial Condition Directory


14/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


Scenario Directory

Malfunction Editor

Action Editor

Time Editor

Event Editor


15/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


Evaluation Editor

Snapshot Directory

Facilities for moving from one system display to another are provided both by usingbuttons (soft-buttons) in the view section of the displays and access through function keysat the keyboard.

Soft-buttons for easy access between the TEC displays


16/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


2.4.2 PagesInformation is also presented in pop-up windows overlaying the current display. Thecontent of such windows is referred to as a page. The pages are organised depending on

their content:

- Variable Pages

- Alarm Pages- Malfunction Pages

These pages can be selected either by using the Function keys on the keyboard or themouse by selecting the 3D-buttons on the current display, The selected pages can be

moved around within the display, and will remain even if a new display is acquired.

Example of an Alarm and Malfunction Page shown in a Process display


17/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


Example of a Variable Page shown in a Process display

2.5 Screen Layout and OperationsDisplays and pages include some fixed basic information fields and buttons located insections as detailed below.

2.5.1

Heading BarsI n Displays

TIME Field displaying simulator time and status (Run/Freeze).PICTURE Field displaying the display number (ex. Picture DIR 00).

NAME Field displaying the display name (ex. Picture Directory).

On Pages

TYPE Field displaying page type. (ex. al0000)

PICTURE Field displaying the page number (ex. PAGE 0000).NAME Field displaying the page name. (ex. ALARM PAGE DIRECTORY)DOWN Select this down arrow to display the next page in a sequence of pages.

UP Select this up arrow to display the previous page in a sequence of pages.EXIT Select this button to remove the page


18/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


2.6 Keyboard Function KeysThe functions are grouped according to function type and assigned to keys with the

purpose of achieving the best user friendliness. The keyboard has some keys, which arealready marked with an appropriate text: Home, Page Up and Page Down.

Present Windows layout:

Keyboard Key TEC Function

F1 Run simulation

F2 Freeze simulation

F3 Stop, end simulation

F4 Snapshot

F5 Operating Condition

F6 ScenarioF7 Recall picture

F8 Alarm Log

F9 Malfunction page directory

F10 Variable page directory

F11 Alarm List

F12 Alarm silence

Home Picture directory

Page Down Next picture

Page Up Previous picture

Shift + F4 Replay/snapshot dir.

Shift + F6 Initial Condition

Shift + F7 Mark picture

Shift + F8 Alarm log acknowledge

Shift + F12 Toggle window decorations

Shift Home Picture number (mdxx)

To access functions listed in the left column in the attached table, please follow the quick

reference in the right column:


19/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


2.7 The mouseThe mouse is equipped with two buttons. The left button is used to open valves, start

pumps etc. In addition you may activate 3D buttons (soft keys) or controllers in the variousdisplays.The rightbutton is used to close or stop.

As a result of a point and select fieldaction, the instructor will often be prompted for analphanumeric input requesting a text string or new values.

2.8 TemplateTogether with the simulator a template is also supplied to cover the function keys on thekeyboard.


20/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


3 THE OPERATING CONDITION DISPLAYThe Operating Condition display features possibilities to define the operating conditions

for the simulator. The display layout varies from model to model, but in general the pictureis divided into 8 windows. In each window there are various selectable operating

conditions. The alternatives are normally Access, Fixed Process, Inhibit, DynamicsResponse (Levels, Process Dynamics and Ship Dynamics), Snapshots and Logging

possibilities.

3.1 Operating Condition DisplayIn the following, each section of the Operating Condition display is explained in moredetail.

Figure 3-1 Operating Condition Display


21/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


3.2 Access : Instructor, Operator 3, Operator 2,Operator 1

(Not yet ful ly implemented on Neptune applications ! )There are four different levels of the information presented in the Model Drawings (MDs):

Instructor mode, Operator 1, Operator 2 and Operator 3

The Instructor has superior access to the system. In Instructor mode, the user has access to

all information available, i.e., all instructor pages like Init Condition, Operating Conditionand Scenarios. Furthermore, this level gives the user status of possible malfunctions

activated. All variables are presented in the Process Diagrams such as temperature T, flowG, pressure P, power E. Additionally, all alarm points are displayed.

The operators 3, 2 and 1 all have restricted access to the system, but the amount of access

depends on which mode you have been given.

The operator 3 has access to all the operator functions. In addition, the operator 3 haspartial access to some instructor functions. Operator 3 may access the Scenario Directory

and load a new scenario.

Operator 2 has access to all the variables as the instructor has on the process mimicdiagrams. When Operator 2 is selected, the user is disabled from getting access to theInstructor pages. Also status of active malfunctions are removed. However, the full range

of variables are presented in the same way as in Instructor mode.

Operator 1 has access only to the variables normally found in the control system at the realplant. Operator 1 is similar to operator 2, except that only variables comprising alarmpoints are displayed on the MDs.


22/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


Function How to access

Operator 1 provides the student with least information in

the simulator. Only Alarm points are displayed in theProcess displays and limited access to TEC instructorDisplays.Operator 3 shows all information in the Process displays,

and gives limited access to TEC instructor Displays.Instructor Access have all rights.

Default Access mode is Instructor.

1) Click to Operator 3,2 or 1 to change access, and for

example press the Home-key (Picture Directory appears)To get Instructor Access:

2) Press F5,Operating Condition, a window appearsasking for a password: Type it, press Enter, and againyou have Instructor access.

3.2.1 Access ControlThe Access Control picture can only be displayed by selecting ACCESS CONTROL from

the Operating Condition picture menu.

From the Access Control picture, it is possible to configure station level, which is required

to execute certain simulator functions. It is also possible to modify the required stationlevel to display some instructor pictures.

The system provides Operator1 with least information, while Instructor access applies toall information available.

Access Level Access by:

Number Operator 1 Operator 2 Operator 3 Instructor

1 x x x x

2 - x x x

3 - - x x

4 - - - x


23/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03



Access Control At the bottom of the Operation Condition display, there

is a button called Access Control. This display showswhich access level Operator 1, 2, 3 and the Instructorhave.4 refers to Instructor

3 refers to Operator 32 refers to Operator 2

1 refers to Operator 1

To modify current setting, carry out required changes and

click on the Save Access button located at the bottom ofthe display. Access Control has been changed

accordingly.


24/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


3.3 Fixed Process : Air, Steam, Level / Temp, ShipSpeed


Fixed process allows the user to maintain certainvalues unchanged. This function is useful for

student familiarisation or when the user wants torun parts of the simulation without being forced

to line up all relevant subsystems.AIR: Air bottles are pressurised at all times

independent of air consumption.

Steam: A steady steam pressure is available and

steady independent of consumptionLevel/Temp: Level and temperature remain

unchanged to normal valued independentof impact from user

Ship Speed: Is set to a fixed value.

3.4 Inhibit : Alarm Horn, AC Buzzer, ECR Bell,Keyboard Buzzer


Inhibit is used in connection with Operational

simulator models to disable various sounds frombells and alarm buzzers.

The sound of alarms are disabled when thecorresponding button is activated.


25/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


3.5 Dynamic Response : Levels, Process Dynamics,Ship Dynamics


Levels in tanks can be adjusted to steady (nochange), or have a fast response for instanceduring refilling of tanks, or have a slow

response. Fast response on levels implies forexample higher consumption of fuel oil. This is

achieved by simulating a reduced diameter ontanks.


Dynamic Response enables the instructor to

define three different levels on the processdynamic response.

Normal process dynamic response is equal to

real time response.Fast and very fast process dynamic response

speeds op the process even faster.In general this is valid particular for slow

processes like heating of Settling tanks.


By Ship Dynamics the system gives theInstructor possibilities to alter the ships

reaction.Normalis equal to the response of a real ship.

Fast and Very Fast: A quicker ship responsecan be obtained by using Fast or Very Fastas the ships block coefficient is modified

accordingly.


26/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03



Determines which events or alarms shall be

logged on which printer. All six buttons can beactivated simultaneously.Alarm: Printout of all alarmsEvents: Printout of events as changes in

status of valves, pumps, etc havetaken place

Datachief: Printout of all alarms on Datachief(Operational simulators only)

Malfunctions:Printout when malfunctions have

been reset or attempts of resettinghave been carried out.

Instructor: Printout of all instructor actions.Select: Printout of tags with text.


Snapshot: A snapshot is an instant condition

of the present simulation. All data of thesimulation is saved to the disk.

The Snapshot Table displays a list of the

twenty latest snapshots taken. They areidentified by the time they were taken. The

complete list of Snapshots are available inthe Snapshot Directory.

As soon as a new initial Condition isloaded into memory, the previousSnapshots are deleted.

Using a Snapshot: If the user has carried out afatal error, and it seems that the whole

exercise has failed, this can be repaired byloading a snapshot taken prior to the

accident.1 Press Freeze (F2)2 Click the correct Snapshot twice, for

example 033 Press Run (F1). Snapshots newer than the

chosen one are deleted as new snapshots

will be related to actions based on newintructor inputs after the Snapshot was

loaded into memory.


27/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03



User Name: This section contains information of

the User Name and given name of thePersonal Computer. In addition it tellswhich Scenario is in use as well as whichInitial Condition is attached to the

Scenario.


Simulation Speed Ratio: The lower part of thesame section as above, shows which

simulation speed is currently used. TheSimulation Speed Ratio can only bechanged while in Freeze.

Snapshot interval: 00:01:00 means that everyminute there will be taken a Snapshot. The

instructor can alter the Snapshot in eitherFreeze or Run .

Snapshot Cycles: The number indicates how

many snapshots the system takes care ofbefore the first one is being replaced with

the upcoming snapshot.


28/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


4 INITIAL CONDITION DISPLAY4.1 The Initial Condition displayAn initial Condition comprises all necessary information to run a simulation. An initialcondition is a description of a specific situation. Loading an initial condition (exercise)implies that you together with the model itself, also load a set of parameters that describe

the starting point of your simulation.Among thousands of variables, the simulation describes for instance the current value of:Sea Water Temp

Wind SpeedShip Speed

Trim and Heel

An Initial Condition is the mean to permanently store a defined simulator situation.

To reach a specific training objective, the instructor normally needs to modify an Initial

Condition included in the originally delivery.

If you change the value of one of the above mentioned variables and store it, you have in

fact created a new Initial Condition.

An Initial condition must be chosen prior to starting the simulation.

Even Snapshots can be converted to initial conditions.

4.2 Initial Condition Directory DisplayIn the following, each section of the Initial Condition display is explained in more detail.


29/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


Initial Condition display (example)


Private/Common initial Conditions: TheInitial Condition Display directorycontains 50private(blue coloured buttons)

and 10 commonInitial Conditions Buttonsrepresented by a grey shaded colour. Each

Initial Condition is identified by numbercombined with a descriptive text.Anybody can save an init as private init,

but the only one to delete them is the

author him/herself.


30/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03



Initial Condition: To connect an initial

Condition to the simulation model:1 Ensure that the simulator is in Freeze (F2).2 Click on the desired soft button, for

instance I03. Seconds later the button is

depressed and the text colour has changedto yellow.

3 Press Run (F1) to start simulation.

4 The heading of the Initial Conditiondisplay shows the name of the selected

init.

5 Press Run (F1) to start simulation. StartSimulation command is displayed at the

lower left corner

6 In addition, Running is displayed inupper right corner, and the simulation time

starts.


Create: To create the present situation forlater use (as an initial condition) :

1 Press Freeze (F2)2 Click on Create.3 Move the cursor to a vacant location ,

and type name of the exercise,terminate by Enter. Text

4 Example: Select I19 and type:Ready to Discharge. Shortly after,relevant values are saved.

5Press Run (F1) to continue, quit or load adifferent initial condition .


31/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03



Rename:Not yet implemented on Windows

simulation models.

Delete:The initial conditions delivered withthe simulator cannot be deleted. To delete

any other initial Condition:1 Press Freeze (F2)

2 Select the Delete button. This turnsyellow, and the system asks you to

click on the desired init to be deleted.As an example I19 will be deleted.

As soon as you have made your selection,the init condition disappears from the Init

Condition Directory.

Deleting Initial Conditions should be donewith great care. Once the action has taken

place there is no way of restoring the Initial

Condition deleted. If a mistake is made, thedeleted condition can only be restored from

a backup file/CD


Right hand side of Initial Condition

display: The remaining part of theInitial Condition display contains thesame information as described under

the Operation Condition display.


32/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


4.3 Exercise 1-Start up your workstation, and load a simulator application-Go to the Initial Condition Directory.

-Select the initial condition Cold Ship or Virgin/Fuel added.Start the simulation and start up one or more subsystems.Put the simulator in Freeze.

Save the current situation as a new Initial Condition named with your username.


33/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


5 RUN &FREEZE5.1 RunTo set the simulator in Run mode, press the Run pushbutton on the INSTRUCTORkeypad.

A green light in the Run pushbutton indicates that the simulator is in Run mode and themode indication in the header bar changes from Freeze toRunning.

The simulated time displayed in the header bar of the display starts incrementing.

5.2 FreezeTo set the simulator in Freeze mode, press the Freeze pushbutton on the Instructor keypad.

A yellow light indicates that the simulator is in freeze mode and the mode indication in the

header bar changes from RunningtoFreeze.

The simulated time displayed in the header bar of the display stops incrementing.

Note:

1) The instructor is prevented from putting the simulator in run while loading aninitial condition or while loading a snapshot.

2) It is not permitted to change simulation speed while the simulator is in run mode.


34/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


5.3 Exercise 1-Start up your workstation, and log in to the simulator.

-In the Start picture, select a simulator and start it.

-When the simulator is loaded, observe which Mode the simulator is in.

-Try to change between Instructor Mode and Operator Mode and observe the

difference in access on the Instructor panel.

-Put the simulator in Instructor Mode and go to the Operating Condition Access

Control page. Change the Access Level for the different facilities, save, and observe the

changes on the Instructor Panel.

-Go to the Initial Condition Directory. Start the initial condition Cold Ship. Put thesimulator in Running and start up one or more subsystems. Put the simulator in

Freeze, and save your work in a new Initial Condition named with your loginusername.


35/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


6 SCENARIOSA scenario is a set of pre-programmed instructor actions executed at specified times or

events during a simulator session. Scenarios are used to store sequences of instructoractions often used during training sessions. A scenario can comprise time controlled

malfunctions, event controlled malfunctions, time actions or event actions. A scenario mayalso be connected to a specific initial condition. A scenario can be used over and overagain as it is stored on the Harddisk.

6.1 Scenario DisplayIn the following, each section of the Scenario Display is explained in more detail.

Figure 6-1 Scenario Display, seen as Instructor


36/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


Figure 6-1 Scenario Display, seen as Student

There are two types of Scenarios:Private Scenarios: These scenarios have blue colour, are readable by the owner only.

Common Scenarios: These scenarios have grey shaded colour, and are available on allworkstations running the same simulator model. These can only be

deleted by the owner.

The initial setup gives the instructor access to 40 various

scenarios. Scenarios S21 through S40 appear when usingthe scroll bar. The last five ones, S36 through S40, are

accessible for all users.

This function is very handy during distribution ofscenarios to the students prior to start of a lesson. As the

students have limited access to instructor information,they are disabled from knowledge of which malfunctions

or actions are included in training session.


37/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03



Load a Scenario Ensure that the simulation is in Freeze mode (function

key F2). Select the Scenario from the keyboard(function key F6) Scenario Display appears.

Move the cursor to one of the existing scenarios and loadit by clicking on the descriptive text, in this case

Malfunction on ME. That scenario turns to yellow. Tostart simulation, press Run on the keyboard (function key

F1)

There is normally attached one specific initial condition

to each scenario. In this case it is I05 Full Ahead Loaded.

Create a Scenario In this example we will create a scenario location S18,and Init condition I04 Dead Slow ahead will be used.

Ensure that the simulation is in Freeze (F2). Click atCreate at the bottom of the Scenario Display. The textSelect description button to be created. We will select

S18:Type a name that identifies the purpose of the Scenario

for example: Malfunctions in Steam system. In this casewe just type Creating a Scenario. Press Enter.

In the green field you shall type the reference to the

Initial Condition you will use as a basis for this scenario.We can use any of the existing initial conditions as long

as they contribute to reach learning objectives. In our testwe will use Initial Condition no.4 Slow ahead Loaded.Type: I04and press Enter.

Now we have gene rated a Scenario in location S18, andInitial Condition is used as a starting point for theexercise. We will later learn how to attach Time

Malfunctions, Event Malfunctions, Time Actions andEvent Actions. First we will learn how to Rename, Copy

and Delete a Scenario.


38/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


Rename, Copy andDelete a scenario

First we will learn how to Rename, Copy and Delete aScenario. We will practice on S18

Rename: Scenario called creating a scenario, S18, shall be

renamed to Renaming a scenario Select the Renamebutton

Click on the title of the scenario located on S18. Thecolour changes to green. Delete Creating and type

Renaming press Enter. If you want to use Initialcondition I04 as the basis for the exercise, accept by

pressing Enter. If not, select any existing initialcondition reference and press Enter.

The name of the Scenario has been updated.

Copy: We want to make a copy of the renamed scenario in S18,

and locate the new scenario in position S20

Select Copy. You are asked to Select description buttonto be copied. Click on the text to the right of S18. A

new text appears, asking for Select destinationdescription button.

Clickon 3D-button to the right of S20.

A new scenario identical to the one in S18 is available in

S20. However, there are no links between the two.

Delete: Now and then it is necessary to delete useless or oldscenarios. In this example we will delete the scenariolocated in S20 Renaming a scenario

Select the Delete button. The system responds with:

Select description button to be deleted:Move the cursor next to S20 and click on Renaming a

scenario.


39/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


A successful operation has removed the scenario.

In the nest chapter we are going to include malfunctions and actions into a scenario by

taking advantage of the following editors:

Malfunction Editor permits malfunctions to be set up for activation in a scenario.Action Editor permits actions to be set up for activation in a scenario.Time Editor permits control of the scenario progression.

Event Editor permits control of the events that trig actions andmalfunctions.


40/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


6.2 Exercise 2

- Go to the Scenario page, and create a scenario named after your username.- Connect the scenario to the Initial Condition Full Ahead Ballast.- Copy the scenario to the Common area, and observe how all workstations in the

network can access the scenario.

- Try to delete the scenarios in the Common area.- Rename your Private scenario to My first scenario.


41/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


7 MALFUNCTION EDITORThe Malfunction Editor is used to pre-program a single fault, several faults or sequence of

faults. Most malfunctions can be introduced in a range of 0-100%, while others are ofon/off type.

The malfunctions may be activated at specified times, Time Based Malfunctions , or as aresult of an event Event Based Malfunctions .

Furthermore, malfunctions may be ramped from one value to another defined value.

All malfunctions located in the Malfunction Editor must be linked to a Scenario.

Figure 7-1 Malfunction Editor Display


42/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


7.1 Malfunction Editor DisplayIn the following, each section of the Malfunction Ed itor Display is explained in more

detail. As this manual is common for various simulator models, the examples givendescribe in general how to access various functions

7.1.1 My first Scenario where Time based Malfunction isincluded


Create a Malfunction As described all Time or Event controlled Malfunctionsmust be linked to a Scenario. Therefore we will create a

Scenario called My first Scenario.

Ensure that the simulation is in Freeze mode (function

key F2). Select the Scenario from the keyboard(function key F6). Scenario Display appears. Followdescription in previous chapter Scenario and create a

scenario called My First Scenario, using Init ConditionI05 as basis.

Click on Ed Malf (Edit Malfunctions), in upper rightcorner. The Malfunction Editor appears. The upper half

of the Malfunction Editor shows 10 various Time BasedMalfunctions (out of 40) which can be linked to onescenario,

while the lower part displays Event Based Malfunctions

linked to the same Scenario. These are numbered fromM41 through M80.


43/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03



Time based

Malfunction

In this example we will introduce a malfunction M0111

from Malfunction Page ma0100 Sea Water System,called Low Suction Sea Chest Filter Dirty whichintensity will increase from 0 to 50% during a period of 4min., and start effecting the system 1 min. after start of

the Scenario (Run). By selecting Malfunction Page(F9), we can from the Directory select the Malfunction

M0111 Low Suction Sea Chest Filter Dirty (valid forMC90 model).

Select Create at the bottom of the Malfunction Editor,

click on the Button to the right of M01, and type LowSea Chest dirty, press Enter.

Next to the Malfunction description Low sea chest dirty,you are requested to enter the Tag Name. You type the

reference number of the Malfunction, in addition tounderscore S (= _S ).In this example: M0111_S

Type 50 and press Enter for the Active rading. Type 0and press Enter for the Passive input, and press enter

once more.

The result should show as follow:


44/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03



In the example, only On, Off

Period, Ramp and Duration is ofinterest.

On tells the system that we want tointroduce a malfunction that will

remain on when first activatedOff Period indicates the time whenthe malfunction will start effecting the

system after start of the Scenario.Ramp has to be chosen when a

malfunction shall increase smoothlyfrom one value to anotherDuration is the specified time given

to the system to go from the Passivevalue to the final value (Active value)

When entering new time values, both :

and .are accepted by the systemFor the Off Period: enter 1 minFor the Duration: enter 4 min

Click on : OnClick on Ramp

The final setting should look asdisplayed:


45/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


7.1.2 Testing the result of the Time Based MalfunctionTesting the result of the Time Based

Malfunction

How to access

Ensure that the simulation is in Freezemode (function key F2).

Select the Scenario from the keyboard(function key F6).Click on My First Scenario until the the

text My First Scenario turns yellow.Select Sea Chest filter Dirty in the TimeBased Malfunction.

Press Run (function key F1) and

monitor the impact of your result.

The expected result is shown below asabnormal differential pressure across

the lower sea chest filter.Furthermore you will realize increased

temperature in the Fresh Water System


46/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


7.1.3 My First Scenario where Event based Malfunction isincluded


Event based Malfunction In this example the Event BasedMalfunction will introduce a

malfunction M1311 from MalfunctionPage ma1100 ME Fuel Oil System

(1), called FO Visco Contr. Unstableat the point in time when the Bridgereduces ME Speed from 74 to below 60

rpm. The malfunction will effect thesystem 30 seconds after 60 RPM has

been reached.Note the variable number of thePropeller speed N03761 at Variable

Page (F9) 5600 indicates 74 rpm

Enter the Scenario Display (F6)

Ensure the simulation is in Freeze(F2) Select My First Scenario.

Click on EDITOR below Event

Malfunctions and Malfunction EditorDisplay appears

Click on the Create button.

Select location M41 and type:FO Visco contr unst.(able)In the next field type the reference of

the malfunction to be activatedM1311_S. Acknowledge by pressing

Enter


47/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


Type the intensity of the malfunctionwhen Active, here 100

The Passive value to be set to 0

Unit can be left blank, or %Enter the variable that will trigger the

Malfunction in this example the MESpeed, N03761. Actual value is 74 rpm.

When its value exceeds 75 or 65 rpm,the malfunction will be activated.

In this example there has beenintroduced a delay of 10 sec from the

time the rpm exceedes the limits untilexecution of the malfunction

When completed, the setup for the

Event Based Malfunction has thefollowing view.

7.1.4 Testing the result of the Event Based MalfunctionTesting the result of the Event Based

Malfunction

How to access

Ensure that the simulation is in Freeze

mode (function key F2).Select the Scenario from the keyboard

(function key F6).Click on My First Scenario until the thetext My First Scenario turns yellow.

Select FO Visco contr unst. from theEvent Based Malfunction.

Press Run (function key F1). Let thesystem run for a period of time andreduce the ME speed to 58 rpm from

Main Engine Bridge Control DisplayMD110 and monitor the impact of your

result.


48/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


The expected result is activation of themalfunction FO visco controller

unstable as the rpm decreases 65 rpm.

The impact is abnormal behaviour ofthe controller which can be monitoredon the FO slave controller in MD11 FOSystem.

Furthermore you will notify an alarmrelated to the viscosity inlet Main

Engine.


49/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


8 ACTION EDITORThe Action Editor is used to pre-program a single, multiple or sequence of actions. Most

malfunctions can be introduced in a range of 0-100%, while others are of on/off type..

The actions may be activated at specified times , Time Based Actions , or as a result ofother events, Event Based Actions .

Any variable with input access within the simulation models may be controlled by thescenario via the Action Editor.

Furthermore, an action may be ramped from one value to another defined value. They mayalso be repeatedly changed from one value to the other.

All actions located in the Action Editor must be linked to a Scenario.

The maximum number of actions attached to one Scenario is 40 Time Based and 40 EventBased Actions.

Figure 8-1 Action Editor Display


50/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


8.1 Action Editor DisplayIn the following, each section of the Action Editor Display is explained in more detail. As

this manual is common for various simulator models, the examples given describe ingeneral how to access various functions based on one of our low speed engine roomsimulators.

8.1.1 Create an ActionFunction How to access

Create an Action As previously described all Time orEvent controlled Actions must be linked

to a Scenario. As we already have one

scenario called My first Scenario, wewill continue to expand that one.

Ensure that the simulation is in Freezemode (function key F2).

Select the Scenario from the keyboard(function key F6). Scenario Display

appears.Select the scenario called My FirstScenario.

The selected field turns yellow.

At the right hand side of the Scenario,

Time Actions are listed.At the bottom of the column, EDITORis listed.

Click on Editor

In this location any variable from thevariable pages (F10) can be entered

into the system.


51/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


These buttons can be used as earlierdescribed to:

-Create a new action

-Rename an existing action-Copy one action to a vacant location,or-Delete an existing action

8.1.2 My First Scenario where Time based Action is includedFunction How to access

Time Based Action In this example the Time Based Action

will introduce a change in the weathercondition (waves) from calm sea tohurricane. The impact from Beaufort

ramps from 0 to 10 during a period of 5minutes, 1 minute after the simulation

has started. The variable Z00770Weather Condition is located atVariable Page 9202. The initial value is

0 Beauf

Enter the Scenario Display (F6)

Ensure the simulation is in Freeze

(F2) Select My First Scenario.Click on EDITOR below Time Based

Actions.Action Editor Display appears

Click on Create at the bottom.

Select A01 and type:Weather ConditionPress Enter

The cursor moves to Tag NameType Z00770

The result is as shown.Press Enter

The cursor asks for the Active andPassive value.Type 10, Press Enter

Type 0. Press Enter twice.The result is as shown


52/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


Click on the On 3D-button.Press Enter

Change the Off period to 1 min

Press Enter, and Enter once more.Change the Duration to 5 min.Activate the Ramp function.The result is displayed.

The final layout should be as follow:


53/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


8.1.3 Testing the result of the Time Based ActionTesting the result of the Time Based Action How to access

Ensure that the simulation is in Freeze

mode (function key F2).Select the Scenario from the keyboard

(function key F6).Click on My First Scenario until the thetext My First Scenario turns yellow.

Select Weather Condition. from theTime Based Actions.Press Run (function key F1).

The weather condition will start to

impact the simulation after 1 min andwill increase over a period of 5 minutes.

One expected result is increased

activity on the ME speed controller as ittries to compensate for increased ship

movementFurthermore several false Level alarmsappears on the Alarm Log Display

(F8).Both Shaft. and Turbo generator will be

disconnected from Main switchboard..Boiler will trip and in the end ME shutsdown.


54/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


EXAMPLE

We will use the Action Editor to specify the action of entering shallow water going from100 meters to 30 meters sea water depths. We specify the action as an ON/OFF action with

a duration on 3 minutes and a ramp duration of 1 minute.

Figure 8-2 Entering shallow water

Figure 8-3 Specifying Time-based Actions


55/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


8.2 Event Based ActionLet us assume that a ship is approaching a pier to discharge its cargo at 4,5 knots. There is

also another ship coming in from starboard. The captain put all his energy to avoid acollision and gives Full Astern Command. Ship Speed reduces. The impact of strong windgets less attention and the ship hits the pier and stops as the Ship hits the rocks 2 minutes

After Captain has given Full Astern CommandWhen testing Event based Action, prepare an Initial Condition called Loaded at 4,5knots where:

-Responsibility Transfer is in Bridge Control-Ship speed is 4-5 knots. Throttle approximately Dead Slow Ahead (= 17-18 % command

on MC90 simulation model)-Weather Condition is 4 Baufort.-Wind Direction 90 degrees

Demonstration of Event based Action Based on Initial condition Loaded at 4,5knots


Event Based Action In this example the Event based Action

Stop the ship will hit the Rocks of thepier and stop 2 minutes after the captainhas given Full Astern Command. We

will use the tag Lever Position at Main

Engine Bridge Control display, andtwo minutes later the ship will stop dueto activation of Stop Ship Commandfound in the Variable Page Sim Control

(this may vary from one simulationmodel to the other) For this purpose

there has been created a Scenario calledMy second Scenario where a link tothe above mentioned Initial Condition

Loaded at 4,5 knots has beenestablished at location I16 in the Initial

Condition Display.


56/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


Enter the Scenario Display (F6)Ensure the simulation is in Freeze

(F2) Select My Second Scenario.

Click on EDITOR below Event Actionsat the lower right hand side.Action Editor Display appears

Click on Create at the bottom.

Select A41 and type:Emergency Crash StopPress Enter

The cursor moves to Tag NameType X07005, Stop Ship action

variable for this paricual simulator(Ship speed turns to 0).The result of the entry is shown.

Press Enter

The cursor asks for the Active andPassive value.

Type 1 for (impact: The ship stops)Press EnterType 0. Press Enter twice.

The result is as shown


57/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


Event Tag name variable that willdecide whether the ship will crash or

not ( i.e ship speed set to zero) The

current value is 17,5%. If the readingexceeds 100% or -95% ( i.e. FullAstern) The Stop Ship variable X07005will turn active (=1).

Enter value of High Limit: 100Press Enter

Enter value of low Limit: -95Press Enter

However, The stop ship action can be

delayed if desired. In this example wewant a delay of 2 minutes.Type 2:00 ( :and , are both accepted)

Press Enter

Disregard Duration and Ramp functionin this example and press Enterfinished

The result is displayed.

The final layout should be as follow:

8.2.1 Testing the result of the Event Based ActionTesting the result of the Time Based Action How to access

Ensure that the simulation is in Freezemode (function key F2).Select the Scenario from the keyboard

(function key F6).Click on My Second Scenario. The text

My Second Scenario turns yellow.


58/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


Select Emergency Crash stop. fromthe Event Actions.

Press Run (function key F1).

At the time when the Captain gives Full

Astern Command, the ship will crash(or stop) 2 minutes later and ship speed

will indicate 0 knots


59/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


8.3 Exercise 3- Load the scenario My first scenario.- Implement five malfunctions into the scenario. The malfunctions we will insert are four

time-based malfunctions and one event-based malfunction. The following malfunctionwill be inserted:

Time-based: TG LO Filter Dirty

Low temperature fresh water pump no. 1 wearEarly fuel injection on cylinder no. 1Late fuel injection on cylinder no. 5

Event -based: Low suction sea water filter dirty.

Time Malf TG LO Filter 1 Dirty M01

Time Action Ent. Shallow Waters A01

Event Malf Dirty SW Filter M41

Time Malf LTFW Pump 1 Wear M02

Time Malf Cyl. 1 Early Injection M03Time Malf Cyl. 5 Late Injection M04

The M01 malfunction (TG LO Filter 1 Dirty) is specified to turn active after 1 minute of

simulated time. The LO filter will then start to be gradually dirty during 1 minute that isthe time we specify under Ramp Duration. Activation of the ON button means that themalfunction will be active until the student repairs the filter and reset the malfunction by

finding the right malfunction from the Malfunction Page and reset it by means of thetracker ball or mouse and its right button. The student will get a message if he tries torepair an active component or if he attempts to reset a passive malfunction.

The M02 malfunction (LTFW Pump 1 Wear) will activate after 9 minutes of simulated

time. We specify this malfunction as and ON/OFF malfunction that goes from active topassive after 1 minute. The specified Ramp Duration that is set to 1 minute, refers to bothgoing from passive to active and from active to passive.


60/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


Figure 8-4 Specifying Time-based Malfunctions

In our scenario we will also include one Event-based malfunction that goes activedepending on a specified event that occurs in the process. This event-based malfunction

can be the low suction sea water filter that starts to go dirty when the sea depth is less than50 meters. In the chapter describing the Action Editor in the TEC instructor system, wewill see how the sea water depth can be changed as an action in our scenario. In the section

for Event-based malfunctions in the Malfunction Editor, we specify the filter to go 80%dirty when the malfunction goes active, and 10% dirty when in returns to passive. We put awatch on the sea water depth by typing in this variables tag name that we find in the

alphanumeric Variable Pages. The Event-based malfunction will go active if the watchedvariable is higher or lower than the given limits. For the sea water depth the high limit is

set to infinity (1000m) and the low limit is set to 50 meters. If the variable toggles aroundthe limits, we can put a delay time before the malfunction is triggered.

Figure 8-5 Triggering of Event-based Malfunction

Figure 8-6 Specifying Event Based Malfunctions


61/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


9 THE TIME EDITOR9.1 The Time Editor DisplayThe Time Editor is used to adjust the scenario progression during a training session.

Entries from the action and malfunction editors are presented in a Gannt like diagram. The

diagram shows when, in simulated time, the automatically scheduled events will occur.

The instructor can easily delay or advance the progression of any automatic action and

malfunction in the current scenario. However, the auto repeat malfunctions and actions arenot adjusted by the Time Editor.

Figure 9-1 The Time Editor Display


62/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


Malfunctions / Actions Section

Name Content/Function

Reference Column for reference number definitions, i.e.,

which malfunction or action is currentlydisplayed

Status Column for malfunction status indicators.Status conditions:

a) The outer circle will light up (light grey)when the malfunction button is activated.

b) The inner circle will light up (yellow) when

the scenario malfunction is active.

Malfunction/Action

Buttons for activating/ deactivating themalfunctions or actions.

Scroll Scrolls malfunctions UP/DOWN

Timephase Section


Current Time Bar Bar representing current time, black.

Edit Time Bar Bar representing the current edit time, yellow.

ChangeTimephase

Button to permit use of the dedicated buttons onthe TEC keypad to advance or postpone theoccurrence of scheduled events to alter thescenario progression.

Active Value Column displaying the active value for this

variable, i.e., the value to be used when thisvariable is activated.

Current Value Column displaying current value of thisvariable.

Passive Value Column displaying the passive value for thisvariable, i.e., the value this variable is given

when this malfunction or action is deactivated.

Unit Column displaying engineering units used.


63/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


Timephase Section cont:

Scroll Axis Left Button for moving the scroll axis.

Scroll Left Button for scrolling scenario to the left -advance scenario events.

Scroll Axis Right Button for moving the scroll axis.

Scroll Right Button for scrolling scenario to the right - delayscenario events.

9.2 Time Editor Procedures9.2.1 How to control scenario progressionThe transitions from ON to OFF and vice versa, the ON/OFF times, are indicated in theGannt diagram as colour changes. White indicates that this event is not activated, i.e. set to

the value displayed in the passive column. Black indicates when the event is activated.

1) Select the Edit Times button to enter the change time-phase mode. When activated,the yellow Scroll Axis will be presented. The Scroll Axis will always be positionedat a scenario ON/OFF time.

2) The Scroll Axis can now be moved to the next or previous ON/OFF transition time

for scheduled events using the Move Scroll Axis buttons.

3) Events scheduled after the selected position of the Scroll Axis (to the right) can now

be moved in time using the Scenario Timer Scrollbar.


64/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


10 THE EVENT EDITOR10.1 What is the Event Editor?The Event Editor is used to supervise and possibly adjust the events and event

conditions (high/low limit and delay). The data is presented graphically in a manner,which makes it easy to spot any events or nearly events.

10.2 Event Editor DisplayEdi tor My Fi rst ScenarioEvent

MALFUNCTIONS

Scenario:

VALUES EVENTS VIEW

00:09:15

Freeze

Picture

1206

MalfPage

VariablePage

AlarmPage

Ed Eval

InitialCondition

Operating

Condition

EdTime

Ed Malf

Scenarios

EdAct

Low High DelayActive Passive UnitsREADING

M41

M42

M43

M44

M45

M46

M47

M48

M49

M50

A41

A42

A43

A44

A45

A46

A47

A48

A49

A50

Scenario: .. .:

Initial Condition: ..:

My First Scenario

Simulation

Speedr atio


65/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


Malfunctions / Actions Section


Reference Column for reference number definitions, i.e.,

which malfunction or action currently displayed

Status Column for malfunction status indicators.Status conditions:

a) The outer circle will light up (light grey)when the malfunction button is activated.

b) The inner circle will light up (yellow) when

the scenario malfunction is active.

Malfunction /Action

Buttons for activating/ deactivating themalfunctions or actions.

Scroll Scroll malfunctions UP/DOWN

Value Section


Active Column for display/ input of active value.

Reading Column displaying current value/ status.

Passive Column for display/ input of passive value.

Unit

Event Section


Low Limit Column displaying the low limit for the event.

Event Barograph Barograph displaying the event variable valuerelative to the high/ low limits.

High Limit Column displaying the high limit for the event.

Delay Timer Graphical presentation of the delay countdown.Presented as a clock counting down to zero.

Delay Value Column, which display the delays in minute:second format.


66/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


10.3 Event Editor Procedures10.3.1 How to change event specificationEvents are specified by the High / Low limits and the Delay. These values may be changed

by activating the wanted input fields and type the wanted value.

1) Point at the wanted field and select (middle button).2) Type wanted value (abort input sequence with ESC).

3) Enter.


67/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


11 THE EVALUATION EDITOR11.1 What is the Evaluation EditorThe Evaluation Editor is an aid to the instructor when evaluating the trainees

performance. It allows for monitoring of key variables in the simulated plant, thusgiving an indication of how well the plant is managed/controlled.

The evaluation is performed by monitoring selected values (variables in the plant) in theaction/malfunction editors in a scenario to see if the operator(s), trainees, manages to keep

these selected values within its specified ranges. If the monitored variables exceed belowor above the specified range as a result of an active malfunction, the absolute deviation will

be integrated in time and multiplied by an weighting factor. The sum will then be a resultof the deviation and how long the deviation has been in time.

All releases after 3.7 inc ludes an additional page in the variable list called "Scenario-FreeTags". These can be used for activating of evaluation during procedural training where

preset malfunctions and/or actions not are a part of the exercise. The free tags can be set toa value between 0-100.By means of the free tags we can make "dummy actions" to activate the evaluations.

Figure 11-1 Evaluation Principle

The evaluation is performed continuously during the training session. The instructor mayinspect the evaluation results at any time during the training session.

11.2 How is the Evaluation Editor operated?The Evaluation Editor is selected from the View Area of the displays or the ED EVAL

pushbutton on the Instructor Section of the TEC keyboard.

The evaluation criteria are edited in the Evaluation Editor.

The result of the evaluation can be monitored directly in the Evaluation Editor.


68/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


11.3 The Evaluation Editor Display

Figure 11-2 The Evaluation Editor Display

Evaluation Area


Reference Column for reference numbers.

Evaluation Buttons for name definition and activation.

Variable Name Column for evaluation variable namedefinitions.


69/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


Evaluation Data Area


Reading Column for current value of variable.

Low Limit Column for the low limit value specified.

High Limit Column for the high limit value specified.

Absolute

Deviation

Column displaying deviation when value is

outside limits.

Weighting Factor Select field to insert a weight factor for each of

the evaluation criterions. See separatedescription.

WeightedDeviation

Column displaying the result of the deviationfield multiplied by the weight factor.

Trigger Identifier

Field

Specifies which action or malfunction used to

trigger the evaluation, i.e., M01-M40 and A01-A40. Ref. column 1 in the Malfunction andAction Editors.

Trigger Status The status of the trigger action/ malfunction.

Ref. column 2 in the Malfunction and ActionEditors.

Evaluation Sum Field displaying the result of the specifiedevaluation criteria. This sum is the result of the

integrated weighted deviation.

Total Evaluation

Sum

The resulting sum of all evaluation sum fields.

Create Sets up a new evaluation criteria.

Rename Renames an already existing evaluation criteria.

Copy Copies an already existing evaluation criteria.

Delete Deletes an already existing evaluation criteria.


70/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


11.4 Evaluation Editor Procedures11.4.1

How to create an Evaluation

1 Select the CREATE button. When activated; the colour changes and the text Select

descriptive button to be createdis presented.

2 Select the scenario EVALUATION button to be created. When activated; the colour

changes and the green input line appears in this button.

3 Type in the wanted descriptive text for this button. Terminate with the ENTER key.The green input line then moves to the VARIABLE NAME column.

4 Type in the variable name. Terminate with the ENTER key. If the variable name is a

legal one, the green input line then appears in the LOW LIMIT column.

NOTEThe system response to illegal values/names is always that the green input line does not

disappear or jump to the next column.

5 Type in the low limit value. Terminate with the ENTER key. The green input linethen appears in the HIGH LIMIT column.

6 Type in the high limit value. Terminate with the ENTER key. The green input line

then appears in the WEIGHTING FACTOR column.

7 Type in the weighting factor for this variable. Terminate with the ENTER key. Thegreen input line then appears in the TRIGGER REFERENCE column.

8 Type the action / malfunction reference. Terminate with the ENTER key.

11.4.2 How to rename an Evaluation1 Select the RENAME button. When activated; the colour changes and the text Select

descriptive button to be renamedis presented.

2 Select the EVALUATION button to be renamed. When activated; the colour changes

and the green input line appears in this button.

If the EVALUATION button selected is not defined, the text Can't renamenonexisting evaluationis displayed.

3 Type in the new descriptive text wanted in this button. Terminate with the ENTERkey. The green input line then appears in the VARIABLE NAME column.

4 Type in the variable name. Terminate with the ENTER key. The green input linethen appears in the LOW LIMIT column.


71/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


NOTEThe system response to illegal values/names is always that the green input line does not

disappear or jump to the next column.

5. Type in the low limit value. Terminate with the ENTER key. The green input linethen appears in the HIGH LIMIT column.

NOTE

If the current value displayed in the in the green input line is to be kept, confirmed this byterminating with the ENTER key.

6 Type in the high limit value. Terminate with the ENTER key. The green input linethen appears in the WEIGHTING FACTOR column.

7 Type in the weighting factor for this variable. Terminate with the ENTER key. The

green input line then appears in the TRIGGER REFERENCE column.

8 Type the action / malfunction reference. Terminate with the ENTER key.

11.4.3 How to copy an Evaluation1 Select the COPY button. When activated; the colour changes and the text Select

descriptive button to be copiedis presented.

2 Select the EVALUATION button to be copied. When activated; the colour changes

and the text Select Evaluation destinationis presented.

If the EVALUATION button selected is not defined, the text Can't copy nonexistingevaluationis displayed.

3 Select the destination EVALUATION button. The scenario is now copied from thesource to this new destination.

4 Use the RENAME feature to insert new name in the destination button.

11.4.4 How to delete an Evaluation1 Select the DELETE button. When activated; the colour changes and the text Select

descriptive button to be deletedis presented.

2 Select the EVALUATION button to be deleted. The EVALUATION selected is thenautomatically deleted and the descriptive text removed.

If the EVALUATION button selected is not defined, the text Can't delete nonexistingevaluationis displayed.

Take care when using the delete feature as when a scenario is deleted it can not be

restored!


72/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


11.4.5 How to start an EvaluationThe evaluation starts when the Evaluation Button is activated. The evaluation sumaccumulates while the Trigger Status is active (the corresponding malfunction / action is

activated).

11.4.6 Description of the Weighting FactorThe Evaluation Editor may be used to create until 20 evaluation criteria. Each criterion isrepresented by one variable. The value of this variable is checked against its high and lowlimits and the following takes place:

If the value of the variable is outside its legal range, as defined by its high and low limits,

the deviation is calculated. The result is called Absolute Deviation.

Absolute Deviation = variable value - exceeded limit

The Absolute Deviation is multiplied with the Weighting Factor. The result is called the

Weighted Deviation.

Weighted Deviation = Absolute Deviation * Weighting Factor

The Weighted Deviation is integrated, making the Evaluation Sumas a function of both

the magnitude and duration of the deviation.

Evaluation Sum= (Weighting Factor * (tag value - exceeded limit))

Note:

The integration is executed only when the Evaluation Button is activated and theassociated malfunction/action is active. This because the Evaluation Editor is supposedto be used to evaluate the students response to introduced malfunctions or actions. In

other words, the integration will not start until the malfunction/action has been turnedon.

The purpose of the weighting factor is to enable scaling of the deviation. A deviation of1000 kilograms can be scaled to give the same evaluation as a deviation of 1 ton.

The integration unit is 1/sec., which means that a constant weighted deviation of 1.0 will

increase the evaluation sum with 1.0 pr. sec. Thus the evaluation report may be used tomeasure for how long a valve has been open/closed, or a pump has been on/off.


73/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


11.5 Exercise 4We will prepare an evaluation of how the trainees perform when the malfunctions DirtyDO Filter DG1, M01, and Dirty SW Filter that we prepared in the Malfunction Editor,

turn active.

For the malfunction dirty diesel oil filter on diesel generator no. 1, we will have an increase

in the differential pressure over the diesel oil filter. In the Evaluation Editor we will put awatch on this differential pressure and specify limits that the pressure shall stay in between

for normal operation. When the malfunction turns active and the pressure increases abovethe upper limit, the absolute deviation from the limit, will be integrated in time until the

pressure falls under the upper limit again. We can put on a weighting factor on the

deviation depending of how critical the parameter is that we put a watch on.


74/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


The faster the trainee realises the problem and solves it, the less the figure will be and thiscan be used to compare the performance of trainees.

For the malfunction of the dirty sea water filter, we put a watch on the differential pressureover the filter.

When the exercise is completed we will have relative figures of how the trainee performed

faced with problem on the diesel oil filter and sea water filter. The two figures will also be

summed up, giving and overall figure of performance.

NOTE: The deviation will only be integrated in time when the malfunction is active.

Some values to be entered into the Evaluations:

Evaluations Tag name Low limit High limit Weight

factor

Counting if

active

Diff. Pres. DO DG1 P03066 0,4000 0,7500 5,00 M01

Low suct. SW filter P00630 0,0000 2,0000 2,00 M41


75/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


11.6 Exercise 5We want to check that there is voltage on the EG (excitation ON and voltage adjusted) at

the time the student carries out a connect attempt of the EG to emergency busbar:

Go to Action Editor, event based actions (to make a dummy action):

A41 (EG connect attempt)Tag name: X93001

Active: 50 (or another value)Event Tag name: X06134High/Low Limit: 1/-1

Delay: When necessary

Ramp: When necessary

The evaluation counter will be activated at the students connect attempt.


76/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


Go to Evaluation Editor:E01 (voltage on EG?)

Tag Name: V06136

Low Limit: 430High Limit: 450Weighing Factor: To be consideredCounting if Active: A41

The student will be given penalty points if voltage is not present at the time of connect

attempt.


77/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


11.7 Exercise 6NOTE:This example is taken from the MAN B&W 5L90MC-VLCC model. The tags can

be different on other models.

Preparing of ME. Here the trainee have to prepare all the sub. system as LTFW, HTFW,

HFO, starting air and LO system before the student can blow the ME by air and start. Thetemperature, pressure and flows have to be normal.

Following tags can be used: (Only for example, it is possible to put in more dummy tagsand other events)

Go to Action Editor, event based actions (to make a dummy action) :

See enclosed picture.


78/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


Go to Evaluation Editor:

The student will be given penalty points if different flows, pressures, temperatures and

levels is not present at the time of starting the ME. See enclosed pictures.


79/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


More the trainee remember to start and check before he start the ME, less the figure will beand this can be used to compare the performance of trainees.

When the exercise is completed we will have relative figures of how the trainee performedwith preparing and starting the ME. All the figures will be summed up, and give a overall

figure of performance.


80/88

KMSS

Doc.no.: SO-1077-B / 3-Mar-03


12 SNAPSHOTS12.1 What are Snapshots?A snapshot is a copy of all the variables and parameters needed to describe the state

of the simulator. A snapshot consists of one or more binary files stored on the systemhard disc and can be seen as a "picture" of the simulated plant state at a given time.

Snapshots will only exist during a training session and cannot be transferred to orused in later training sessions unless they are converted into initial conditions. Asnapshot is marked with the simulated time when it was taken and is identified by

this time mark.

Snapshots saved using the auto snapshot facility are most often used for this purpose. Up to100 snapshots may be saved and are thus accessible from the snapshot directory during atraining session.

Snapshots are used for three purposes:

1 Creating initial conditions

2 Performing a replay

3 Do a backtrack

12.2 How to take snapshotsThere are two ways to take snapshots, automatically or manually.

Automatic snapshots

Snapshots are taken automatically when setting the 'snapshot interval'. Default snapshotinterval at simulation start-up is 00:00, i.e. no snapshots taken automatically. However,

setting the 'snapshot interval' to 00:10 will cause snapshots to be taken at 10 minutesintervals.

Manual snapshots

To force a snapshot to be taken independently of the set snapshot frequency, press the

Snapshot pushbutton on the Inst

So1077 b Training and Evalu

Documents

Transcript of So1077 b Training and Evalu