NAPA Online Manuals 2011.2: Emergency Response (ER)

NAPA Online Manuals 2011.
2
Emergency Response (ER)
© 1992-2011 Napa Ltd. All rights reserved.

NAPA Online Manuals 2011.2
Table of Contents
1 General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1 What is NAPA ER?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 What is needed in the NAPA models to run NAPA ER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3 Starting NAPA ER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2 Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.1 Startup checks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.2 Menus and toolbars. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.3 Defining a new scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.4 Save and Save As. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.5 Scenario settings - Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.5.1 Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.5.2 Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.5.3 LD Arguments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.5.4 Reference System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.5.5 Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.5.6 Toolbar – Save. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3 Graphics Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1 General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.2 Zooming in graphics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.3 Using graphics to check coordinates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4 Condition Tree and Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4.1 Scenario, sequence and conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.2 Definition of new conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.3 Expanding and collapsing the condition tree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.4 Working with conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.4.1 Renaming a condition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.4.2 Adding a condition to a scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.4.3 Copying a condition within the scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.4.4 Deleting a condition from a scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.4.5 Save a condition as a normal loading condition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.4.6 Apply changes to the condition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.5 Supported functionality / actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5 Table Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.1 Compartment loading (Comps). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.1.1 Sub-selection of compartments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.2 Mass loading (Masses). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.3 Recorded changes to the condition (Actions) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.3.1 What are actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.3.2 Action areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.4 Damaged compartments (Dam Comps). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.5 Longitudinal strength (Strength). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.6 Stability curve (Stability). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.7 Criteria check (Criteria). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.8 Opening list (Openings). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.9 Tide calculation (Tide) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
6 Working with NAPA ER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

6.1 Loading the ship. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

NAPA Online Manuals 2011.2
6.1.1 Loading compartments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

6.1.2 Loading masses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
6.1.3 Draught Survey functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
6.2 Compartment properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.2.1 Compartment permeability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.2.2 Pressures in compartments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
6.3 Defining damages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
6.3.1 Compartments open to sea (unlimited damage). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
6.3.2 Definition of breaches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
6.3.2.1 Modifying a breach. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.3.2.2 Deleting a breach. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.4 Definition of grounding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.4.1 Tide definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.4.2 Varying the water depth without tide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.5 Condition notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.6 General note. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
7 Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
7.1 Results tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
7.1.1 Condition comparison. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
7.2 Outflow of cargo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
7.2.1 Outflow calculation mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
7.2.2 Selecting outflow components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
7.3 Longitudinal strength. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
7.3.1 Strength mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
7.4 Stability curve (GZ). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
7.5 Stability criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
7.5.1 Selecting active criteria group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
7.5.2 Switching between intact / damage criteria. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.6 Tidal calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.6.1 Calculating required tide change to refloat the ship. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.6.2 Redrawing the graphics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
8 Output (Printing). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
9 Customising NAPA ER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
9.1 Setting the columns shown in tables and the quantities in the Results tab. . . . . . . . . . . . . . . . . . . . . . 33
9.2 Printing system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
9.2.1 How to modify an existing / make a new print macro. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
9.2.2 Adding new macros to / modifying the VARDEF* table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
9.2.3 Modifying the printing system macro. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

NAPA Online Manuals 2011.2 1 (35)
1 General
1.1 What is NAPA ER?

NAPA ER has been developed to meet the demands for easy loading and damage analysis, and to allow fast
technical support for ships in operation. A land based technical support team is already required for tankers
sailing in US waters (OPA 90) and the demand for support is expected to widen even further.
NAPA ER is a part of the powerful NAPA system. It combines several different parts of NAPA in one powerful
graphical user interface. NAPA ER is a separately licensed feature in the NAPA package.
1.2 What is needed in the NAPA models to run NAPA ER

Due to the possibility of a large variety of level of detail in NAPA models, NAPA ER is designed to make use of
almost any existing database. Still there are some basic requirements that need to be met in order for NAPA
ER to make use of the model.
NAPA model must include the following
■ A HULL, a STABHULL and a DAMHULL, or equivalent geometric objects to base the calculations on. If
the names differ from the defaults, they need to be correctly updated in the reference system.
■ A SHIP MODEL arrangement defined in the SM task.
■ A LIGHTWEIGHT definition to use in loading conditions.
The following is not required, but still recommended to have in the NAPA model
■ A LIGHTWEIGHT DISTRIBUTION definition for strength calculation.
■ Predefined loading conditions to base scenarios on
■ Draught mark curves* (useful when giving the floating position for draught survey and grounding
calculations)
■ Bending moment and shear force limiting curve group(s) for global longitudinal strength calculations
■ Opening arrangement*
■ Stability criteria group(s) (some are included in NAPA)
* Draught mark curves and opening arrangement can be created using, for example, the Verify Manager.
1.3 Starting NAPA ER

NAPA ER is started by selecting Emergency Response under the TASK menu in the NAPA main window.

Note: NAPA ER only works in the LD task. Entering a subtask of LD and using NAPA ER will present a
request to return to the LD task. Leaving the LD task (to TASK level) will cause NAPA ER to close down
and any information not previously saved is lost.
2 Administration
The core of NAPA ER is based on the scenario description. Information regarding the location of the initial
loading condition and scenario tree is stored within this description. The core structure of NAPA ER is based
on a set of naming rules, and it is not recommended that the specially named objects are manually modified
outside NAPA ER. The most important named objects are:
The scenario descriptions prefix ER*

The initial loading condition prefix ER#
The scenario process table prefix TAB*ER#
2.1 Startup checks

When the NAPA ER window is opened, the application looks for a specially named macro. If a macro named
DATA*ER.CHECK_START is found, it is executed when the window is built. The purpose of this is to allow the
checking of the database when the application is started. Currently the macro verifies that the purpose FLOOD
exists in the PAR*STD table, as this is required in order to handle the oil outflow calculation properly.
When a scenario is opened, another macro is searched for. If a macro named DATA*ER.CHECK_OPEN is
found, it is executed each time an ER scenario is opened. This allows for checking the specific scenario
immediately after it has been opened. Currently there is no ER.CHECK_OPEN macro shipped with NAPA.
2.2 Menus and toolbars

The menus and the main toolbar reside at the top left corner of the application window. From the drop-down
lists one can access almost all functions available, all grouped according to subject.

The different menus are:
File Scenario handling and printing (create new, open,

save and close scenario, print and printer settings)
View Graphics area related functions, currently only
drawing area selection
Condition tree Tools for the condition tree, the same functions as in
the condition tree toolbar
Load Functions for loading and damaging the ship
(condition tools)
Tools Accessing separate tools and dialogs
Help Standard help menu
The toolbar provides quicker access to functions in menus. Components, listed from left to right, are:
New New scenario

Open Open a previously saved scenario
Save Save the current scenario
Quick-open field Type the name of the ER* scenario and open it right
away
Print Open the Print dialog
Calc ON Suspend calculation*
Update intermediate results If a condition contains a breach defined previously
in the tree, outflow calculation might be dependent
on the history of the condition. The icon shows a
red exclamation mark if calculation results might be
outdated. Click to update intermediate results and
get more accurate outflow calculation.
* WARNING: suspending calculation will not suspend ALL calculations, but it might still cause problems if
changes to the condition definition are done while the suspend button is clicked. Use this only to quicker build
up the tree structure and if you want to save some time as the system will not do any updates. Remember
to turn the calculation ON again before changing any definitions in the condition.
2.3 Defining a new scenario

A new scenario is defined either by clicking the New button in the upper left corner of the ER window or by
selecting New from the File menu.

Creating a new scenario

In the dialog, the new scenario can be based either on an existing loading condition in the project, a loading
condition received from the Onboard-NAPA loading computer or on an empty loading condition using only a
predefined lightweight condition. With the button all existing loading cases can be browsed and the drop-
down list for 'Empty, lightweight' shows all lightweights defined in the project.
Note: an existing scenario cannot be overwritten when a new scenario is defined.
When a new scenario is made, the system will automatically set some of the arguments for the loading condition:
■ YREF is set to OFF if it is ON
■ FRSM is set to ‘ALL REAL’
■ MODE is set to REAL SRED ISTR
■ The HEEL range is automatically set to (-70 -30 10) (-25 -10 5) (-7 -1 2) 0 (1 7 2) (10 25 5) (30 70 10)
unless the default HEEL range in LD goes higher than 55 degrees, in which case the default HEEL range
from LD is used. The reason for using symmetric heel angles to both sides is that the opening tab will
show the immersion angles (IMMA) for the openings on both sides and the criteria are listed for both
sides separately. The heel range can be manually set to one side or something else in the Preferences
dialog.
■ All compartments are given RPERM 100% * unless anything else is given in a column RPERM in the ship
model arrangement table.
* RPERM is an added permeability that takes into account the steel reduction. The volume available for flooding
water with RPERM = 100% is therefore equal to the volume available for loading the compartment (with steel
reduction taken into account). If a compartment has an RPERM defined in LD, that value is used instead of
the PERM given in e.g. the Ship Model arrangement.
Creating a new scenario will also open the Preferences dialog so that criteria groups, opening arrangement
etc. can be selected right at the start.
2.4 Save and Save As

The scenario is saved either by clicking the Save button or by selecting Save in the File menu.
Selecting Save As will save the scenario with a new name. An existing scenario can be overwritten, but you
are first asked for a confirmation that the existing one can be overwritten.
2.5 Scenario settings - Preferences

Selecting Preferences from the Tools menu will open a window where scenario specific settings can be set.
Some of the settings are stored in the loading condition and some in the scenario description. This window
offers possibilities to change e.g. the behavior of the graphics and set the arguments in the loading condition.
For the Tools menu to be activated, a scenario has to open. The functionality of the different tabs is described
below.

2.5.1 Calculation
Preferences window
Global Arguments
The calculation tab divides the settings into five different areas: global arguments, local arguments, damage
calculation mode, strength mode and strength plot. The global arguments offer the possibility to set an opening
arrangement and to select the intact and damage stability criteria groups. These arguments (of the loading
condition subsystem) are global in the sense that they affect all the results regardless of where in the scenario
you are, and they are stored with the scenario.
All openings in NAPA ER are handled in opening arrangement tables (prefix OPE*). If your project does not
contain an arrangement, existing opening definitions can easily be converted to one e.g. by using the VERIFY
Manager. Just make sure the openings are marked as relevant in the damage subsystem when running VERIFY
Manager.
Criteria groups can be selected for intact and damage stability checks, and hence they need to be defined prior
to selecting them. Please keep in mind that intact criteria can be used in damaged conditions, but damage
criteria cannot be used in an intact condition.
For more information regarding these arguments, please refer to the loading condition manuals or explanation
texts.
Local Arguments
As opposed to the global arguments that affect all the results in the scenario, the local arguments are condition
dependent. This means that when these arguments are changed, they will also be added to the change track
records (actions) if you choose to apply them.
For more information regarding these arguments, please refer to the loading condition manuals or explanation
texts.
Damage Mode

NAPA ER offers three alternative ways of calculating the damage results. The first one (Mode 1) is the default
way in NAPA, i.e. the floating position found is based on the GZ curve calculated at the given heeling angles.
The second one (Mode 2) makes NAPA first find the equilibrium and then include this heeling angle in the GZ
curve, making it possibly slightly more accurate at the cost of calculating an additional point. The third (Mode
3) is the same as the second mode, but NAPA freezes the amounts of liquids in breached tanks when the
GZ curve is calculated.
The biggest difference in the ways of calculating is seen in the outflow calculations for breached conditions.
The first one (Mode 1, default) is that the amount of liquid cargo lost is the amount of cargo that would escape
at the worst heeling angle between the initial condition and the equilibrium. As this is a conservative approach,
some might consider this pessimistic and prefer the other modes. Mode 2 and Mode 3 calculate the amount of
outflown cargo at the equilibrium angle instead. Mode 3 only differs from Mode 2 when analysing the outflow
at different heel angles other than the equilibrium.
Strength Mode
The strength mode options concern the results when a strength limit group has been selected. This option
changes the way the relative strength values are related to the limits. Normally (Mode 1, default) the relative
values are zero when the actual shear force or bending moment is zero. Mode 2, on the other hand, sets the
zero relative value in the middle between the limits (normally used when both the minimum and maximum limit
is either positive or negative and a zero shear force or bending moment would reside outside the limits).
Delayed GZ curve calculation
Improvements to NAPA ER regarding performance have emerged in a new option to delay or prevent the GZ
curve calculation when not needed. Skipping the GZ calculation will improve the performance of NAPA ER as
calculation time is saved. The input is in seconds, where zero means immediate calculation of the GZ (like
before) and anything greater than zero means that the GZ curve is calculated after some time, when NAPA
ER has been idle. As a special option, a delay of -1 seconds will prevent the GZ curve from being calculated
unless the Stability, Criteria or Opening tab is open / entered (GZ data is required here).
Note: when the GZ information is missing, GZ related values in the results list are not available (like GMACT
for a damaged ship).

2.5.2 Environment
Currently, the Environment tab does not have any other function than storing general information regarding
the scenario. This information will in the future be used to generate a general report page describing the
environmental conditions at the site of the emergency. The information is stored with the scenario description.
2.5.3 LD Arguments

The LD Arguments tab offers a view of all arguments in the LD subsystem. If the top item (the initial condition) in
the hierarchy tree is chosen, this tab will also allow access to all the arguments; otherwise, it is set to read-only.
2.5.4 Reference System
The Reference System tab offers a view of the parameters set in the reference system. It does not give access
to change these parameters, as they could have an effect on basically everything in the model. Still it is of
importance that you can view all reference parameters of the model.

2.5.5 Graphics
The Graphics tab controls the settings of the graphics areas. The three areas are represented by the numbered
fields on the top, to make it easier to see where each setting affects.
Drawing Area 1
In the first drawing area, there is the option to draw the frame scale and alternatively change the setup to one
previously stored in the database.
Drawing Area 2
In the second drawing area, there is also the option to draw the frame scale and alternatively change the setup
to one previously stored in the database.
Drawing Area 3
In the third drawing area, there is the option to draw the section inclined according to the floating position
instead of having the waterline inclined. There is also an option to draw draught values at the side of the section,
indicating the draught to the keel and the draught to the deepest part of the section.
2.5.6 Toolbar – Save

The settings stored with the scenario can also be stored as project defaults (DB1), or system defaults (DB1
and DB2) which are applied when a new scenario is created.

3 Graphics Area
3.1 General
Graphics in NAPA ER are shown in two different places. One is in the Criteria tab (explained in the criteria part
of the table area), and it is dedicated to showing criteria results, while the other, main graphics area, is always
visible in the upper right part of the user interface.
The main graphic area is divided into parts of which three are normally visible and used. The figure below
shows the orientation of the drawing areas referenced to by numbers from here on.
The drawing area 1 (DA1) is used for displaying the profile view of the ship and it provides by default two
orange coloured selector bars for generating the section coordinates in the two other views (DA2 and DA3).
Unless a setup is selected, the application will use the PROF setup as default (Y=0.01). Using the default setup
is recommended.
Note: if a profile curve has been generated in the project, and the name has been set in the REFERENCE
system PROF parameter, this curve will also be plotted in the drawing area 1. This allows the rest of the
vessel, including e.g. cranes etc., to be seen in projects where the arrangement used only contains the
compartments below the main deck.
Drawing area 2 is mainly used to show water line sections (Z-sections) of the arrangement and drawing area
3 is used for frame sections (X-sections). If both selector bars are visible in the DA1, input fields for entering
coordinates directly are also available in area 2 and area 3. These are connected to the selector bars, so
changing one will affect the other (input field – selector bar).
Note: all sections chosen by coordinates or with the selectors are generated directly from the model. To
use predefined setups (available in DA1 and DA2), select them in the Preferences dialog found in the Tools
menu.
In the middle of the graphics area there are lines separating the fields, and in the middle of them (where they
meet) is a small button that can be pressed to realign the lines. Dragging one of the lines is also possible and
it resizes one or several drawing areas depending on the line dragged. This allows the areas to be modified
according to one's desire. The setting of the drawing areas is however not stored when the application is closed.

3.2 Zooming in graphics

In all three drawing areas the key press based zoom has been introduced. It is activated by right-clicking in the
graphics and selecting Zoom mode. The zoom now “listens to" the up-arrow and down-arrow keys zooming
in or out. When activated, two buttons also appear at the bottom left of the active drawing area, offering the
Exit zoom mode and Fit to window options. Click the Exit zoom mode or select the Zoom mode again from
the right-click menu to deactivate the zoom.
For using the zoom more effectively, it is suggested to bind the up-arrow to the mouse wheel roll-up movement
on the mouse and down-arrow to the mouse wheel roll-down movement. This will speed up working with the
zoom in NAPA ER and it is useful elsewhere in NAPA as well. To assign the mouse roll-movement, do as
follows:
■ Open the Exceed Configuration (right-click the Exceed icon in the task bar and choose Tools /
Configuration)
■ Open the Keyboard Input settings, switch to the Mouse Input tab and choose Wheel movement invokes
macro
■ Create the macros by clicking the Macro bindings button, click on the ‘…’ button next to the Wheel Up
field and click the Add button
■ Record a macro containing one up-arrow press, save it and record one for the down-arrow press as well
■ Select the correct macro for the Wheel Up and Wheel Down movement
■ Click OK and save the settings
Note: when the zoom mode is activated in the DA1, the selector bars are hidden as the coordinates used
and what the selector bars show are not synchronized. After turning the zoom mode off, they appear again.
The graphical area in the Criteria tab uses the normal zoom menu.
3.3 Using graphics to check coordinates

Whenever the mouse clicks in the graphics with the left or the middle button, the coordinates from the current
point in the graphics are displayed in the status bar at the bottom of the NAPA ER window. Using the left mouse
button will select objects from the graphics as well, while the middle button is dedicated for the coordinates
alone (so far).
4 Condition Tree and Architecture
4.1 Scenario, sequence and conditions

In the NAPA ER window you can build a scenario of conditions which on the uppermost level refers to an initial
loading condition. The initial loading condition is the starting point for all further modifications and definitions.
The link / connection to the initial loading condition selected (at the creation of the scenario) will not remain; a
new copy is made for the current scenario. In other words, if the loading condition initially referred to is later
changed, the defined scenario will not be affected.
Below the initial loading condition you can add any number of conditions. Each condition inherits all the
properties of the condition above in the hierarchy. Many parallel (alternative) studies can be defined as new

conditions can be added as either 'daughters' or 'sisters' to the selected condition. This can best be illustrated
with the scenario in the following figure.
The scenario CASE1 has been defined by referring to a loading condition called ERTEST4. All the properties
of ERTEST4 are copied to this scenario, but the link to ERTEST4 is not maintained. Two parallel conditions
N1 and N2 are added as 'daughters' to the top condition. N2 has three 'daughters' N3, N4 and N5. Further,
N4 has three 'daughters' N6, N7 and N8 etc.
When a change is made to a condition anywhere in the scenario tree, all conditions that are below in the
hierarchy will be affected i.e. the changes are inherited downwards in the scenario. If e.g. a change in the tank
loads of N4 is made, the following conditions will be updated accordingly: N6, N7, N8, N9 and N10.
The dependencies are highlighted in the tree when a condition is selected. In the figure above the selected
condition N10 depends on the conditions N7, N4, N2 and the initial loading condition (top condition). All these
conditions have their icons drawn in orange colour. The conditions that have no effect on N10 are shown in grey.
4.2 Definition of new conditions

The tree structure and the number of conditions are totally up to you to create. A single condition can contain any
number of actions, i.e. changes of load components, masses, grounding definitions, breaches and damages
etc. It is, however, not very practical to define a large number of actions in a single condition. While working
it is probably of more interest to create several sequences of 'what if' scenarios where the different conditions
could contain e.g.
■ grounding
■ breach and damage definitions
■ relocation of cargo from a tank to another
■ ballasting
■ etc.
In this way each condition is a well-defined action or a set of actions which gives a better overview of the
development of an emergency response case.

4.3 Expanding and collapsing the condition tree

When selecting a condition, there is difference when pointing at the name of the condition or pointing at the
icon of a folder.
Note: a folder is identified by the small "-" (expanded) or "+" (collapsed) sign in the icon. When clicking on
the icon, the condition is selected AND the folder will either be expanded or collapsed depending on the
current status of the folder. When pointing at the name of the condition, the condition is selected but the
tree is not changed.
In the figure above you can see condition icons with a "+" sign meaning that there are sub-conditions under
the collapsed folder. If there is a "–" sign, the folder is fully expanded, and pointing at the condition icon will
collapse the tree below that condition.
Note: when opening an existing scenario, the tree is automatically fully expanded.
4.4 Working with conditions

Internally each condition gets an identifier (Nx, where x is a running number) which will occasionally show up
in some printouts and reports, but in the hierarchy tree one can name the different conditions separately.
To work with the scenario tree, there is a set of buttons and menus to use. The buttons can be found above
the condition tree. The menu is called Condition tree and the same tools can also be found by opening the
right-click menu in the tree.
4.4.1 Renaming a condition
Renaming a condition will change the text displayed

in the scenario tree. The name does not need to be
unique and longer names can also be used but short
names are recommended; to input more information
to a condition use the Notes field (tab) in the lower
left part of NAPA ER.

4.4.2 Adding a condition to a scenario
Adding a condition to a scenario will create a new

child to the selected condition. The system will ask
you to name the new condition when it is created.
4.4.3 Copying a condition within the scenario
Copying a condition will create a new condition as

a child to the parent of the current condition, i.e. a
parallel alternative condition is made. All actions
within the condition copied are also copied, but the
children are not. The new condition will be named
Copy of the current condition.
4.4.4 Deleting a condition from a scenario
Deleting a condition will erase all information within

it (notes, actions etc.) and remove it from the tree.
Deleting a condition will also affect all children, as the
actions within the deleted condition disappear, the
children will inherit this change as well.
4.4.5 Save a condition as a normal loading condition
Any condition in the scenario can be saved as an

independent loading condition for treating it outside
NAPA ER. This function will save the selected
condition as an independent loading condition
including all information concerning deadweight,
grounding, breaches, damages, permeability etc.
4.4.6 Apply changes to the condition
After changes have been made (actions) they have

to be added to the condition. This works as a sort
of an undo function, and if the changes have not
been applied, the system will ask for it when another
condition is selected in the tree or the SAVE button is
clicked.
This function is quite useful if the scenario grows very large, and you would like to define a new scenario based
on a selected condition.
4.5 Supported functionality / actions

As mentioned above, each condition can contain a number of different actions. The normal actions supported
in NAPA ER are:
■ Compartment Loading: any compartment can be loaded with any load defined in the PD (Purpose
Definition) of SM.
■ Mass Loading: mass loads can be added, modified or deleted.

■ Damage: any compartment can be damaged / repaired, i.e. the tank is flagged to be 'open to sea' without
additional information on the extent of the damage. If the tank contained liquid load prior to the damage,
all load is lost.
■ Breach: damage with defined extension. All tanks that are fully or partly within the extent of the breach
are damaged, and the outflow of liquid is calculated based on the intersection of the breach and the
compartment.
■ Air-pressure: a constant air-pressure (positive or negative) can be applied to all tanks that are damaged.
The outflow of liquid is calculated taking into account the pressure and the breach. For damaged
compartments without breach definition (open to sea), the air pressure will only have an effect on the
amount of inflown water, in this case it is assumed that the damage/opening is at the bottom of the
compartment.
■ Ground: a grounded condition can be calculated as a 1-point or, 2-point condition either given as a
floating position or explicitly giving the point of contact. Alternatively, a shelf grounding condition can be
defined.
■ Tide: in combination with a grounding condition the tide can be defined. The floating position and
longitudinal strength is then calculated as a function of time.
In addition, a draught survey can be done to correct the current condition if the floating position and loads
reported do not match, resulting in an unknown deadweight component added to the current condition as a
mass load.
5 Table Area
The area under the graphics (lower right) is dedicated mainly for tables providing interaction with definitions or
calculation results. The different tables are chosen using the tabs for opening up different pages (tabs). This
area also operates the graphics in some cases based on the tab selection.
Note: it is important to be aware of the active tab, as e.g. the selection of compartments remains when
switching tabs until another selection is made. This can cause unwanted loading operations to occur if
operations not belonging to the active tab are used.
More information regarding how to use the different tabs and what they provide can be found in chapter Working
With NAPA ER and chapter Results.
5.1 Compartment loading (Comps)

The compartment tab shows all intact compartments available for loading (damaged compartments are filtered
away and will appear in the damaged compartments tab, Dam Comps). The table provides a direct link to the
loading condition definition while also providing calculation results. The compartments can be selected from
the graphics or from the table (both highlighting the compartment(s) in the other). All loading commands in the
graphical user interface are applied on the selected tanks (if possible). The compartment table contains the
following columns by default:
Name The name column contains the name of the compartment as it is defined in
the database. Names cannot be modified in NAPA ER.
Description The description is the descriptive text as defined in the ship model (SM).

Load The load tells what the compartment is or will be loaded with. Clicking the
value twice provides a drop-down list to choose from purposes defined in
the PAR*STD or PAR*PRO tables.
The density of the load, automatically taken from the load, but can also be
Density modified
Capacity The capacity is the space available in a compartment that can be loaded
Vrel Relative volume loaded, tells the relative filling of the compartment by the
load
VLoad Volume loaded, tells the volume that has been loaded into the
compartment
Mass Mass of loaded substance, equal to Density * VLoad
CGX Center of gravity in X-direction for the compartment
CGY Center of gravity in Y-direction for the compartment
CGZ Center of gravity in Z-direction for the compartment
Free-surface moment, the free-surface effect the load has (only for liquids)
Frsm
LTyp Type of load (e.g. L = liquid, gives free surface moment)
5.1.1 Sub-selection of compartments

Using the drop-down list located to the right of the tab selection buttons (to the right of the screen, under the
graphic area) it is possible to filter the visible compartments in the table according to load. The sub-selection
list is automatically updated when new loads are added or removed.
5.2 Mass loading (Masses)

The Masses tab shows all mass loads defined in the current condition. New masses can be added and existing
ones can be modified or deleted. Mass loads should not be modified in other tabs, except for when performing
a draught survey.
Name Name of the mass load (formal location)

Load Load (substance) of the mass load
Weight The actual mass loaded
LCG Longitudinal center of gravity of the mass load (x axis)
TCG Transverse center of gravity of the mass load (y axis)
VCG Vertical center of gravity of the mass load (z axis)
Length Length of the weight distribution
Xmin Minimum x-coordinate for the weight distribution
Xmax Maximum x-coordinate for the weight distribution

5.3 Recorded changes to the condition (Actions)
5.3.1 What are actions

One of NAPA ER’s strengths is that it clearly shows what changes to the condition (actions) have been made
compared to the previous condition one step higher in the condition tree. These actions are listed, after applying
them, into the Actions tab.
To apply actions, simply right-click in the graphics and choose Apply actions, select Apply actions from the
Condition tree menu or, if the Actions tab is open, click the Apply button to the far right under the graphics area.
5.3.2 Action areas

The Actions tab area is divided into three parts, each of them dedicated for different types of actions.
The larger one on the left side shows all compartment related actions (loading, air pressure, damage etc.). The
one on the top on the right shows mass related actions (adding, deleting and modifying), and the third one,
lower right shows other actions (e.g. breach, grounding or argument changes).
5.4 Damaged compartments (Dam Comps)

The damaged compartment tab (Dam Comps) shows all damaged compartments along with more damage
related information. This tab is used to change damage related properties to compartments and to view
calculated results.
5.5 Longitudinal strength (Strength)

In the Strength tab, the results from the longitudinal strength calculations are presented. Switching to this tab
will change the graphics to use only one drawing area, showing a strength plot with the ship profile below. In
the table area the information shown in the plot is presented in numeric form in two different lists. The first
one (left) is a regular strength list for a set of x-locations, and the second (right) is a strength summary list. A
possible strength limit curve selection is also displayed at the top of the tab (STLIM).
Note: aside of the normal NAPA standard, NAPA ER shows the relative strength values also with a negative
sign, depending on the load value (above or below 0%). This is done in the Strength tab and the results
area, but not in the Tide tab.

5.6 Stability curve (Stability)

The GZ curve is presented in the Stability tab, both graphically and in table format.
5.7 Criteria check (Criteria)

The Criteria tab provides information regarding the currently selected criteria group. The group displayed
depends on the environment selected in the listbox at the top. Each criteria in the group is listed together with
its status, and clicking on one of them will plot the selected criteria in the graphics area next to them. If the
HEEL range covers both sides (PS + SB), the criteria will also be listed for both sides separately; otherwise,
the side used in the calculation is shown between the name and the REQ value.
To have a better idea of which openings are critical for the criteria a special tab is provided behind the graphics
area, listing only the openings inside the HEEL range to the side of calculation. For the criteria plot, the number
of openings shown can also be limited with the # of openings drop-down list.
Note: intact criteria calculation in NAPA does not have the same logic in setting openings irrelevant as
damage criteria calculation has. This means that to avoid limiting the range used by the intact criteria due to
internal openings, these should be set irrelevant. To do this, simply select the Exclude internal openings
option. This option does also have an effect on damage criteria, but it is not needed due to the logic built
in for them.
Note: the selection of excluding internal openings and the environment is saved with each condition although
it is not visible in the Actions tab. Also note that a damaged environment cannot be activated if the ship is
not damaged or grounded.

Select the active criteria by clicking in the list, highlighting the criteria line in yellow and updating the plot.
5.8 Opening list (Openings)

If an opening arrangement has been selected for the current scenario, a list of openings with calculation results
is presented in the Openings tab. The list is sorted according to the IMMR value (range to immersion).
5.9 Tide calculation (Tide)

Calculate liftoff
What probably is of interest in a grounded situation is how much the water needs to rise before the ship will float
freely. To help in estimating this, a Calculate liftoff function is offered. Note that no tide information is needed
for using this. To activate this, merely click the Calculate liftoff button and the result is shown in the field next
to the button. The accuracy of this interpolation is 2 cm.
Tide calculation
Provided that the ship is aground and a tide definition has been defined, the tide tab provides tide related
calculation results both graphically and numerically. To perform a tide calculation, enter the desired time (clock)
from when the calculation should start, set the time span (hours) to calculate and the step in minutes. Clicking
Update will start the calculation.
For each time step values will be calculated and listed in the table. The values in the table are then plotted
in the graphics.

Note: switching away and back to the Tide tab after a tide diagram has been drawn will make the graphics
look distorted. This is easily resolved by clicking the Re-draw button on the right under the graphics area.
This will update only the graphics without having to recalculate the results. Without calculated results, the
diagram cannot be drawn.
6 Working with NAPA ER

This chapter explains the different tools and tabs used in the definition of conditions. It gives a deeper look
into the options and tools available, and it is based on the information given in the general presentation of the
tabs in chapter Table Area.
6.1 Loading the ship

NAPA ER provides the normal tools for loading a ship in the same way as it can be done in the normal Loading
Condition user interface in the NAPA system. In the first release of NAPA ER there are still some limitations:
■ Container loading is not yet supported. It could work theoretically, but there are no tools for modifying the
container loading provided.
■ Grain loading is not supported. No tools for loading grain or for defining the special arrangements related
to grain are provided in NAPA ER.
Calculation for container and grain loading should in theory still work normally, but it has not been verified in
the ER user interface. You can try to use it at your own risk.

6.1.1 Loading compartments

Compartments are selected by clicking on them in the graphics or selecting them in the compartment table.
Note: damaged compartments and compartments not in the current subselection are filtered away and
they are not selectable while the compartment tab is active. Select the 'Dam comps' tab to pick damaged
compartments.
A compartment is by default loaded with the load defined by its purpose. The load is shown in the load column
in the compartment table. Clicking twice on the value in the load column provides a drop-down list with the
purposes that are defined in the PAR*STD table or in the PAR*PRO table.
The amount of substance (load) loaded into each compartment is normally controlled by the compartment table,
right-click menus and the Load menu. Editing the Vrel, VLoad or Mass values in the table will also change
the amount loaded in the compartment. Alternatively right clicking in the table or in the graphics also provides
options for loading the selected compartments (empty, full or to a fixed relative value).
Loading tool
From the Tools menu or by right-clicking in the graphics, a Loading Tool can be opened. It appears in the lower
right corner of the graphics area and provides input fields and a scrollbar to load one or several compartments
(depending on the selection).
For trying out a certain filling percentage the scrollbar can prove useful.
The tool is closed the same way it was opened.
Balance
In some cases a condition might need to have the loading condition corrected *) in order to properly represent
the actual condition or perhaps one would like to experiment in finding alternative corrective actions to a
condition. Then the balance tool, opened from the Tools menu, could come in handy.
*) * The loading condition can also be corrected using the Draught Survey functionality, calculating an unknown
deadweight mass load instead of editing e.g. the ballast water tanks, which might provide a different free-
surface moment.

This tool uses the Autoload function in NAPA, using optimization algorithms to find a solution for the given
problem (to change the condition according to a given criteria). Set the target values and give the limitations,
click Preview, and when a acceptable solution have been found, click Apply to load the ship according to
the results.
Move
In some cases it is necessary to move cargo from one compartment to another on the ship. In order to have
control of how much cargo can be transferred and to make sure that the same amount reduced from one
compartment is added to the other, the move tool can be used. First select the compartment to move cargo
from, open the move dialog from the Load menu, and select the target(s). The tool is limited to compartments
with the same load or empty compartments, as NAPA does not know how cargoes are mixed (and if they are
mixed).

6.1.2 Loading masses

Mass loads are only added, modified and deleted while the Masses tab is open. For editing and deleting, the
desired mass load can be selected from the graphics or from the table.
Adding a new mass load
A new mass load is added by selecting the Add massload from the Load menu or by right clicking in the
graphics. This will open up a new dialog (Add New Mass Load Component) asking for the load and name
(formal location) for the mass load.
Note: in order to highlight masses, the formal location should be given a name (without parentheses). By
default the system will give the load in parentheses as the name, but this is not sufficient for the highlighting.
Accepting the addition and clicking the Add button will open up the Load Mass Load dialog (see Editing a
mass load below).
Editing a mass load
Editing of mass loads is done either in the table directly or by using the Load Mass Load dialog. In the table the
new values can be entered directly into the columns (Weight, LCG, TCG and VCG), while the dialog provides
fields for each value to be filled in.

Note: if mass loads are modified using the dialog, the load and name (formal location should be visible in
the top of the dialog; otherwise, you have to select a mass load to modify.
In the dialog, fill in the values and click Close. Selecting New will open the Add New Mass Load Component
dialog and Remove will delete the mass load.
Deleting a mass load
To delete a mass load, simply select the one to delete and choose Delete Massload from the Load menu or
the right-click menu in the table or in the graphics.
6.1.3 Draught Survey functionality

Since the model of the ship and the real ship might slightly differ, the loading condition might give different
draughts from what is reported. The same applies if the reported deadweight or damage extension are not
correct. To resolve this, a more thorough investigation is needed. To get around the differences quickly, NAPA
offers the Draught Survey functionality. It is based on the difference in the floating position of the modeled
situation and what is reported from the ship. To use this tool, open the Draught Survey window from the Tools
menu.
Note: the draught survey is only available if the ship is not grounded.
Draughts at marks
The easiest way to compare and correct the draughts is by using the values obtained from the draught marks
on the ship. This of course assumes that they have been modeled into the NAPA model as well. If draught
marks exist in the model, the input fields at the marks appear in the window and you can type in the correct
values as reported from the ship.

As soon as sufficient input has been given, NAPA displays the new calculated unknown deadweight. This can
then be applied by clicking the Load New button. What will happen is that a mass load, called unknown_dwt
is added to the loading condition compensating for the differences in the draught readings.
Draughts or ullages at arbitrary points
If no draught marks have been defined or reading them on the ship is difficult, you can also use custom ullage
or draught values located anywhere on the ship. To do this you need to open the Waterline Distances window
by clicking the Custom draughts… button.
When filling in these fields, you need to remember not to put all readings in 'a straight line', as NAPA needs
three points in space to fit the water-plane taking into account also the heel. Clicking OK will transfer the input
to the main Draught Survey window and the unknown deadweight can be applied.
6.2 Compartment properties
6.2.1 Compartment permeability

A permeability quantity called RPERM was introduced in NAPA Release 2005.1. This quantity is an additional
reduction of volume in damaged condition. This means that a RPERM value of 100% will allow the compartment

to fill to the same amount as it would in a loading condition (steel reduction is taken into account). This RPERM
overrides the normal PERM values given in the ship model. The RPERM value is stored in each loading
condition separately, and it can therefore differ between loading conditions.
Note: NAPA ER automatically sets the RPERM for all compartments in the arrangement to 100% when a
new scenario is made.
The RPERM values can be modified in the Dam Comps tab using the Perm column.
WARNING! Currently setting RPERM to 0% turns it off and makes NAPA use the normal PERM values
from the Ship Model instead. Set RPERM to 0.1% or something greater than zero even if no flood water is
desired in the compartment to avoid this feature.
6.2.2 Pressures in compartments

Pressurising (over or under pressure) of compartments is also supported in NAPA ER. This is done by entering
the amount of over/under pressure in kPa (1 Bar = 101.3 kPa) into the AIRP column in the Dam Comps tab.
This affects the amount of oil lost in a breached compartment, or adjusts the height of flood water in a broken
compartment (OTS). For a broken compartment (OTS) the damage is assumed to be at the bottom of the
compartment for the flood water calculations if the pressure is modified.
6.3 Defining damages

Damaged compartments in NAPA ER show up hatched in the graphics and with a light-blue filling representing
the amount of flood water in the compartment. All damaged compartments are automatically moved from the
Comps tab to the Dam Comps tab.
6.3.1 Compartments open to sea (unlimited damage)

A compartment considered ‘open to sea’ in NAPA basically has connections in all directions with the outside
of the ship, regardless if it would be surrounded by other compartments or not. This means that all liquid loads
are lost and replaced with sea water. This is the faster way to define damages in NAPA ER, and is done by
selecting the compartment(s) and choosing the Break / Repair option in the right-click menu (in the table or
graphics) or from the Load menu.
6.3.2 Definition of breaches

A breach is a damage with a physical extent. In NAPA, all compartments overlapping the same space as the
defined breach will be damaged. To define a breach in NAPA ER, select the Define Breach / Box Shaped
option in the right click menu in the graphics. This initiates the breach definition, and the extent is defined by
dragging in the profile (Y-) or waterline (Z-) projection (DA1 or DA2) a box representing the breach. The box
will appear also in the other views when the mouse button is released and now the penetration depth has to
be adjusted in the other view (Y or Z, depending on where it was defined), which is done by dragging the end
of the box representing the penetration line to the desired position, and finally one has to right-click in the other
view to end the breach definition.
Note: the system will be frozen until the right-click is done, indicating the end of the definition.
When the breach has been defined, the Edit Breach dialog is automatically opened (see Modifying a breach
below) allowing a more accurate definition using coordinates given manually. Please note that there can be

more than one breach defined, but if several breaches are defined for one compartment, the combined global
extent of the breaches will be used for the outflow calculation (as if there was only one breach).
6.3.2.1 Modifying a breach

Editing a breach is done by selecting it and choosing Define Breach / Edit Breach… from the right-click menu
in the graphics. This opens up a dialog that provides the breach definition as well as some outflow calculation
results.
The definition of the breach is modified by typing in the new values into the coordinates in the table or by
changing the value in the coordinate field. To apply the new definition click Calculate and OK to close the
window.
6.3.2.2 Deleting a breach

A breach is deleted by selecting it and choosing Define Breach / Delete Breach from the right-click menu in
the graphics, or by first choosing Define Breach / Delete Breach from the right-click menu in the graphics and
then selecting the breach by clicking on it from the graphics.
Deleting a breach in the same condition as where it was created or in sub-conditions will load the compartment
with the original cargo unless 'update intermediate results' has been activated. If 'update intermediate results'
has been activated in a sub-condition of where the breach was defined, the amount loaded in the compartment
has changed to reflect the loss of cargo (outflow). Repairing a breach in such a situation will result in that the
cargo remaining and the flood water in the compartment will be mixed (density and load name will change).
Note: deleting a breach in a node where it was not created will try to mix the flood water with the remaining
cargo (for compartments loaded with liquids) in the compartment. This means that the density will be the
weighted average of the two mixed liquids.

6.4 Definition of grounding

The grounding window is opened either by selecting Grounding from the Tools menu or by right-clicking in
the graphics and selecting Grounding. In the grounding window there are two alternative ways to define the
ground: either based on the point of contact or by the floating position of the ship. The selection will have an
affect on what calculations can be done and the results obtained.
Floating position
The floating position definition is probably the first method used in a grounding situation to estimate the location
of the ground contact, as it takes time to get divers under the ship to assess the damages and locate the
ground(s). To enter a floating position, draught mark curves can be utilized or you can give custom drafts as
draught trim heel or using measurements from the ship. If a two-point definition is selected, you must also
estimate where the aft and forward longitudinal (X) locations of the ground are; otherwise, the system will not
have sufficient input to perform the calculation.
Note: a ground definition set as a floating position will try to maintain the floating position entered also during
reloading of the ship. This means that the ground point will move around to stabilize the ship if the loading
condition is changed. Tide calculations are prevented if the ground is set as a floating position, as the ground
would also move with the tide.
Point of contact
When detailed information is available for the ground, the point of contact can be entered. This means that the
exact location of the ground is entered along with distribution length etc. Point of contact also supports one
or two point definition along with a shelf ground definition. Please also note that there are two different depth
values: one at the current time and water level, and one at zero tide (tide offset = zero). If a tide is activated,
the depth values will use the tide offset to correct one of the two accordingly.
Penetration is the z-distance from the baseline for the point. Changing this (>0) will allow the ship to sink deeper
over the ground, reducing the ground force (changing in the opposite direction will increase the ground force).
For ships with an uneven baseline or at the ends of a ship, the ground plot will appear at the baseline even
though the hull might be much higher up. Still a ground force is applied to the ship.
Note: to change from a floating position to a point of contact, merely apply the ground as floating first and
then change the mode to point of contact and reapply the ground definition. In some cases the grounding

point calculated from the floating position can give another floating position that also satisfies the same
point of contact.
6.4.1 Tide definition

Tide definition is done in the Tide dialog. The base of the definition is that the normal water level is assumed
to be zero, and the height of the tide is inserted as the amplitude in both directions and at what time it occurs.
The definition of the tide is automatically saved into the database and it is set for the whole scenario.
Tide can be input in two ways
One is as a maximum and minimum level (High/Low) and the rest is extrapolated based on that using a sinus
curve.
The other is to input the water levels at different times using a table. In this case, the tide values are interpolated
and extrapolated linearly assuming the input represents a complete cycle for the tide.
6.4.2 Varying the water depth without tide

When tide information is not available, it can still be of interest to investigate 'what if' scenarios with tide. In this
case the tide can be changed manually using the Tide offset tool between the condition tree and the results
and notes area. You can manually feed a tide offset value to the condition. This is stored as a change in the
grounding definition and will thus be registered as an action.
6.5 Condition notes

Next to the Results tab, in the lower left corner there is also a Notes tab. This tab offers space to write down
notes which are then automatically saved. There is one note for each condition in the hierarchical tree. These
notes can then later be printed with the condition or with the chosen sequence.

6.6 General note

A general note tab is introduced in Release 2006.1. This note remains static throughout the whole scenario
and it can be used e.g. to write general information like telephone numbers etc. for easy and fast access.
7 Results
7.1 Results tab

In the lower left corner there is tab for the immediate results, showing selected quantities like e.g. the floating
position of the ship. These quantities are automatically updated after each change to the loading condition and
the Current results move over to the Prev. side for comparison.
To select the quantities shown in the Results tab, select Results Quantities from the Tools menu. The default
ones used are stored in the DATA*ER.TABQNTS in the NAPADB. Here NAPA ER offers some additional
quantities not available for normal loading conditions or damage cases.
7.1.1 Condition comparison

To compare different conditions with each other, there is a tool called Condition Comparison in the Tools
menu. This opens a dialog where the results listed in the result tab for the currently selected condition can be
collected next to each other. By changing to other conditions they can be listed next to the previously added
results for comparison. The table displayed is available for printing, but it is emptied as soon as the dialog is
reopened after it has been closed.
Note: the results for the listed conditions are not updated automatically. This means that if something is
changed that will effect the results, each condition listed must be updated manually.
7.2 Outflow of cargo
7.2.1 Outflow calculation mode

When calculating the outflow of liquids in case of compartments damaged by a breach, there are two different
methods available in NAPA ER. This option is set in the Preferences window, found in the Tools menu.
“Mode 1” (default) calculates the largest theoretical outflow at the worst heeling angle from upright to the angle
of equilibrium. E.g. if the equilibrium heeling angle is 17 degrees, but the outflow is largest at an heeling angle
of 3 degrees, the outflow at 3 degrees is calculated and shown in the graphics and in the list output.
“Mode 2” calculates the theoretical outflow at the equilibrium heeling angle. E.g. if the equilibrium heeling
angle is 17 degrees, the outflow is calculated at that heeling and shown in the graphics and in the list output.
“Mode 3” calculates the same way as Mode 2, but keeps the amount of liquids in the breached compartments
frozen during the GZ calculation. This means that the outflow results will match Mode 2 at the equilibrium angle,
but might be slightly different for the other heeling angles.

7.2.2 Selecting outflow components

Selecting Loads for Outflow Calc from the Tools menu opens up a window listing all the currently (or previously
if it has been saved) used loads. The dialog sets the different loads to be included or not in the outflow listing.
The selection can then be saved for later use; otherwise, it will be reset the next time NAPA ER is started. The
selection is saved into a VARDEF* table called VARDEF*ER#OFLLOADS and it is project-specific. The default
loads selected are all liquid loads with a density of less than 1 t/m3.
7.3 Longitudinal strength

Longitudinal strength can be analyzed by viewing the shear force and bending moment. This is done in the
Strength tab, and the graphics is set to one window showing a graphical representation of the loads on top
of the profile view of the ship. The numerical values from the diagram are listed in the table to the left at the
definition points of the strength limits (if any). On the right side there is a summary list of the extreme values
for shear force and bending moment.
7.3.1 Strength mode

“Mode 1”, (default) calculates the relative values of bending moments and shear force related to zero, i.e.
relative to BM=0 and SF=0. If e.g. the maximum allowed BM is 1000 tm and the absolute BM is 500 tm, the
relative value is 50 %.
“Mode 2” works in such a way that the relative values are zero at the mean value of the maximum and minimum
allowable values. This mode is normally useful when the allowable limiting curves are not symmetric around
zero or when both limits reside on the same side of the zero axis. Especially for passenger vessels the allowable
bending moments limiting curves (min & max) can both be on the positive side (constant hogging condition).
If e.g. the minimum allowed BM is +500 tm and the maximum allowed BM is +1000 tm, a BM of +750 tm will
give a relative bending moment of 0 % i.e. it is on the “neutral axis” between the two limiting curves.
The mode is set in the Preferences window, opened from the Tools menu.
7.4 Stability curve (GZ)

In the Stability tab the GZ curve is plotted and listed numerically.
7.5 Stability criteria
Note: using criteria to determine the severity of a situation can be misleading. The criteria should only be
used to give an indication of the stability, but will never tell the whole truth.
The selected criteria (intact or damage) are viewed in the Criteria tab. This area is automatically updated when
the loading condition changes and it tells whether the criteria are met or not. Each criterion can also be plotted
in the additional graphics area by clicking on the desired criterion line.
7.5.1 Selecting active criteria group

Criteria selection can be made using the Preferences window, found under the Tools menu, or if no selection
has been made, the program will use the default values from the criteria subsystem. If no default criteria have
been defined in the CR subsystem, the program will set the relevant criteria group to “A749-3.1”, an intact
criteria group found in the NAPADB.

7.5.2 Switching between intact / damage criteria

If the ship is in a damaged condition, also damage criteria can be used to determine the severity of the situation.
This is done by selecting INTACT or DAMAGE from the drop-down list at the top of the Criteria tab.
7.6 Tidal calculation

Tidal calculation can be done if the ship is grounded and the tide has been defined. The calculation is done
by selecting the time when the study starts (in relation to the tide definition), the number of steps which should
be calculated and the time that will pass between each calculated step. Then just click the Update button and
the table and graphics will be updated.
7.6.1 Calculating required tide change to refloat the ship

In order to find out the required change in tide before the ship will float freely there is also an Calculate liftoff
button. Clicking this will, by using iteration, try to find the change in tide with 10cm accuracy which will refloat
the ship.
7.6.2 Redrawing the graphics

Switching away and back to the Tide tab after a tide diagram has been drawn will make the graphics look
distorted. This is a known issue and it is easily resolved by clicking the Re-draw button on the right under the
graphics area. This will update only the graphics without having to recalculate the results. Without calculated
results, the diagram cannot be drawn though.
8 Output (Printing)
The printing system in NAPA ER is based on a table and macros, and it is fully customizable by an advanced
NAPA user (see chapter Customising NAPA ER for more information). The Print button opens up a Print dialog
where a set of reports (in reality macros) is selected, and then they are executed and the results are collected
into one DOC code that is sent to the printer through the Document Formatter. The Print dialog also offers
some settings for the output and a selection can also be made based on the source of reports desired.

9 Customising NAPA ER
Although NAPA ER is built with ease of use in mind, the solutions made will not always suit every user.
Therefore, there are some parts that have been designed to give you possibility to change the visualisation
or functionality of the application.
9.1 Setting the columns shown in tables and the quantities in the Results tab
The column selection for all tables in the table area of NAPA ER is predefined in a text object called
DATA*ER.TABQNTS. Each row has a five character identifier and a colon that must not be modified. As of yet,
the identifier is not used and the order of the rows must not change. After the six characters at the beginning of
the row, the actual selections appear, so here anyone can change the order of, or add/remove quantities as well.
The original file looks like this:

9.2 Printing system

As almost everyone has their own view on how to organize information and the way they want to present it to
others, the printing system in NAPA ER is made very flexible. The Print dialog is built around a VARDEF* table
that is fully user-definable. The dialog runs an advanced macro generating DOC code based on the selection
made in the table, calling other macros to generate figures and lists that are inserted into the DOC code. Each
macro used can be modified to change the information shown.
WARNING! All macros should work within the LD task, or in subtasks from LD. Exiting the LD task will cause
NAPA ER to close the current scenario and all information not previously saved is lost.
A set of predefined macros is provided with the release. These should cover most of the reports needed, but
future releases will likely bring more possibilities.
9.2.1 How to modify an existing / make a new print macro
CAUTION! Some of the provided macros are advanced and access information from within the NAPA ER
application. Unless you know how this is done, it is not recommended to modify these macros.
Naming rule
The printing macros provided all follow the naming rule DATA*ER.PRINT_type_part, where type is the report
type (Condition = LD, Calculation = CAL and Sequence=SEQ) and part indicates what the report contains.
New printing macros can be freely named, but it is recommended to stick to some sort of naming rule. Using
the same naming rule as the included examples is a good idea; just do not use the exact same names unless
you want to replace existing macros.
IMPORTANT! Unless modification to the core printing macro is made, the name of the result (i.e. the LIST*
or DRAW*) must be exactly the same as the name of the macro. See existing macros for examples.
Contents
The current printing machinery only recognises figures (prefix DRAW*) and lists (prefix LIST*) to be printed.
Each macro therefore should produce a figure, a list or both. They will then be added to the DOC source, if
found, the figure first and then the list. Use normal lists, commands and plots to produce the desired result.
Prior to running the macros and generating the DOC source, the printing system will destroy all previous lists
and plots from the database, making sure the results printed are current and up-to-date.

9.2.2 Adding new macros to / modifying the VARDEF* table

The VARDEF* table used is called VARDEF*ER.PRINT. The only particular thing about this table is that it
contains an additional column called MACRO. In this column the name of the macro to be executed (without
prefix) is stored, and the name of the macro must be the same as the result for the system to work. Also note
that each macro to be executed must have the VALUE set to ‘1’ in order to be run. This is easily done using a
TOGGLEBUTTON as the CLASS for the VARDEF component. Otherwise, the VARDEF* table can be modified
like any other normal VARDEF table (see the Monitor manual).
Note: adding print options to the VARDEF table requires modifying the print system macro.
9.2.3 Modifying the printing system macro
WARNING! Even though the NAPA ER print system macro is available for modification, we do not
recommend it. Support from our Customer Service regarding modification of this macro might be limited
as well.
General
The macro running the result macros based on the VARDEF* table is called DATA*ER.PRINT. It reads the
VARDEF table to see whether a report item has been selected or not. It deletes all previous results and then
executes the selected macros and generates the DOC source code.

NAPA Online Manuals 2011.2: Emergency Response (ER)

Uploaded by

Copyright:

Available Formats

You might also like

NAPA Online Manuals 2011.2: Emergency Response (ER)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NAPA Online Manuals 2011.2: Emergency Response (ER)

Uploaded by

Copyright:

Available Formats

NAPA Online Manuals 2011.

© 1992-2011 Napa Ltd. All rights reserved.

4 Condition Tree and Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

6 Working with NAPA ER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

© 1992-2011 Napa Ltd. All rights reserved.

6.1.1 Loading compartments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

© 1992-2011 Napa Ltd. All rights reserved.

1.1 What is NAPA ER?

1.2 What is needed in the NAPA models to run NAPA ER

1.3 Starting NAPA ER

© 1992-2011 Napa Ltd. All rights reserved.

The scenario descriptions prefix ER*

2.1 Startup checks

2.2 Menus and toolbars

© 1992-2011 Napa Ltd. All rights reserved.

The different menus are:

File Scenario handling and printing (create new, open,

New New scenario

2.3 Defining a new scenario

© 1992-2011 Napa Ltd. All rights reserved.

Creating a new scenario

Note: an existing scenario cannot be overwritten when a new scenario is defined.

2.4 Save and Save As

2.5 Scenario settings - Preferences

© 1992-2011 Napa Ltd. All rights reserved.

© 1992-2011 Napa Ltd. All rights reserved.

© 1992-2011 Napa Ltd. All rights reserved.

© 1992-2011 Napa Ltd. All rights reserved.

2.5.4 Reference System

© 1992-2011 Napa Ltd. All rights reserved.

2.5.6 Toolbar – Save

© 1992-2011 Napa Ltd. All rights reserved.

© 1992-2011 Napa Ltd. All rights reserved.

3.2 Zooming in graphics

3.3 Using graphics to check coordinates

4 Condition Tree and Architecture

4.1 Scenario, sequence and conditions

© 1992-2011 Napa Ltd. All rights reserved.

4.2 Definition of new conditions

© 1992-2011 Napa Ltd. All rights reserved.

4.3 Expanding and collapsing the condition tree

4.4 Working with conditions

4.4.1 Renaming a condition

Renaming a condition will change the text displayed

© 1992-2011 Napa Ltd. All rights reserved.

4.4.2 Adding a condition to a scenario

Adding a condition to a scenario will create a new

4.4.3 Copying a condition within the scenario

Copying a condition will create a new condition as

4.4.4 Deleting a condition from a scenario

Deleting a condition will erase all information within

4.4.5 Save a condition as a normal loading condition

Any condition in the scenario can be saved as an

4.4.6 Apply changes to the condition

After changes have been made (actions) they have

4.5 Supported functionality / actions

© 1992-2011 Napa Ltd. All rights reserved.

5.1 Compartment loading (Comps)