Book PDF

NAPA Online Manuals 2011.
2
Container Loading (CL)
© 1992-2011 Napa Ltd. All rights reserved.

NAPA Online Manuals 2011.2
Table of Contents
1 Container loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1 Overview of functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Connection to other subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.4 Handling container loads under loading conditions (LD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.5 Steps involved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.6 History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2 General principles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1 Basic concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2 Parts of a container arrangement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.3 Properties of stacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.4 Properties of blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.5 Properties of container types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.6 Numbering of container positions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.7 Management of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.8 Usage of alignment points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.9 Mixed loading of long and short containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.9.1 Long and short containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.9.2 General requirements for mixed loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.10 List of quantities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3 Defining container arrangements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3.1 Defining a block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.1.1 The BLOCK command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.1.2 Block defined for mixed loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.1.3 Defining the coordinates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.1.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.1.5 Adding vertical gaps with the ZCORR command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.1.6 Removing locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.1.7 SYM and REFLECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.1.8 Defining stack specific exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.1.9 Auxiliary commands under block definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.1.10 Finishing the block definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.2 Defining combined arrangements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.3 Defining stacks under table calculation (pilot). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.4 Designating subsets of bays, rows and tiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.5 Defining arbitrary subsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4 Auxiliary definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.1 Definitions related to the owner numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.1.1 Defining the numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.1.2 Defining the formal owner numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.1.3 Owner numbering range separating containers in hold/on deck . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.1.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.1.5 Copying the owner numbering system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.2 Various parameters (subtask ADM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.2.1 Bay numbering convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.2.2 Source of container types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.2.3 Defining additional quantities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.2.4 Check mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.2.5 Criterion for separating long and short containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

4.2.6 Criterion for accepting differing container dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

4.2.7 Height tolerance for long containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.2.8 Interpretation of real/formal bay numbers in loading commands . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.2.9 Exit from block definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.3 Default template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.4 Default substance for LCA NEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.5 Defining container types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.6 Templates for controlling texts inside containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5 Loading functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.1 Role of the container arrangement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.2 The container type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.3 Administrative commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.4 Definition of loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.4.1 Creating a new container load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.4.2 The ADD, REDUCT and CHG commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.4.3 The ADD command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.4.4 Specifying container properties in the ADD command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.4.5 General subset selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.4.6 Summary of the ADD command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.4.7 The REDUCT command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.4.8 The CHG command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.4.9 Changing the alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.4.10 Loading containers occupying double bays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.5 Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.5.1 Checks done when loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.5.2 Separate checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.5.3 The UNDO command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.6 Defining container loads under table calculation (pilot) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.7 Graphic information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.8 Description of a container load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.9 Listing data about a load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.10 Variables related to the current load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.11 Adaptation to changed arrangement and types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.12 Generating the lateral profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.13 Connection to loading conditions (LD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.13.1 Adding a container load to a loading condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.13.2 Changing a container load directly under LD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.13.3 Listing container data under LD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.13.4 Plotting under LD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.13.5 Entering container loading from the LOAD task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
6 Drawing functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
6.1 Ways of drawing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
6.1.1 General projections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
6.1.2 Orthogonal projections, real geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.1.3 Orthogonal projections, modified geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.2 Drawing commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.3 The PLOT command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.4 Command PO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.5 The plot options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.6 Plotting individual containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.6.1 Selecting fill colour (FILL option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.6.2 Using figures to represent containers (FIG option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.6.3 Adding text information inside containers (MI option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

6.6.4 Combining information for long and short containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

6.7 Adding text information at the sides of a plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
6.7.1 Selecting the quantities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
6.7.2 Formatting the texts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.7.3 Position control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
6.7.4 Adding headers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
6.7.5 Adding frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
6.8 The NG option (non-geometric) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
6.9 The PART option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
6.10 Controlling the drawing order for hidden lines effect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
6.11 Drawing into the SETUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
6.12 The general drawing functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
6.13 Drawing during block definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
6.14 Additional drawing examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
6.14.1 Example 1 - arrangement plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
6.14.2 Example 2 - not involving containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
6.14.3 Example 3 - checking visibililty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
7 Output functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
7.1 General basis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
7.2 Listing commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
7.3 Listing by container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
7.4 Listing by line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
7.5 Listing by stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
7.6 Listing by layer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
7.7 Listing by container type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
7.8 Transfer of data to table calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
7.9 Auxiliary listing functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
7.9.1 The bare LIST command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
7.9.2 Listing data for arrangements (INFO command) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
7.9.3 Listing data from container type definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
7.9.4 LIST .id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
7.10 Accessing container data in macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
7.10.1 Variables maintained . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
7.10.2 Calculator function CLINFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
7.10.3 Using the table calculation connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
8 Command specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
8.1 Commands on the main level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
8.1.1 Definitions related to containers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
8.1.2 Output functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
8.1.3 Defining container loads. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
8.1.4 Various functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
8.2 Commands in subtask BLOCK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
8.3 Commands under ADM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

NAPA Online Manuals 2011.2 1 (72)
1 Container loading
The container loading subsystem contains functions supporting the design of container arrangements and
creating container loads for use as such or as parts of loading conditions.
The potential locations of containers are defined as so-called container arrangements. Their role is analogous
with that of a compartment arrangement in ordinary loading, and forms the basis for the loading of containers.
The container arrangement has a function in its own right, for assisting the design of the ship. From the
container arrangement, the container capacity can be calculated and drawings can be prepared for showing
the location of containers. In generating the container arrangement, one can take advantage of the geometry
of ship structures.
The functions of container loading can be applied to other cases of objects loaded at predefined positions in
a more or less regular pattern, for example cars on a car deck.
1.1 Overview of functions

The central functions related to container loading are
■ definition of container arrangements
■ drawing container arrangements as such or in arrangement plans
■ output of container counts and other properties
■ definition of container loads
■ output data for container loads in table or graphic form
■ adding container loads to loading conditions
1.2 Connection to other subsystems

Geometry (definitions):
Objects in the ship can be used for providing locations and for eliminating non-available positions in a container
block.
Geometry (drawing):
Container arrangements and container loads can be drawn into arrangement plans or combined with ship
geometry in other ways.
Loading conditions:
A container load can be added as a component in a loading condition. Some output functions of CL are available
directly under the main task of LD. For more details, see below.
Stability criteria:
A modified lateral wind profile can be generated from a container load.
1.3 Installation
Defining container arrangements can be considered part of the description of the ship, and belongs therefore
to the ship model, while loading containers belongs to loading conditions. However, from the practical point of
view, defining arrangements and loading them have much more mutual connections than with the main tasks
mentioned, and have therefore been collected into an single subtask CL. In order to account for the two aspects

above, this subtask has been installed both under SM (ship model) and under LOAD (loading conditions). The
following map is shows how the CL subtask is accessed
Installation of container loading

The map also shows the direct access to the drawing task, without leaving container loading.
A few commands belonging to container loading are available directly in the loading condition task: AC (add
containers), RC (remove containers) and CLA (container load administration).
1.4 Handling container loads under loading conditions (LD)

Containers cannot be added directly to load cases (except as ordinary mass loads), but are collected into
container loads, added as a whole. Defining a container load can be a fairly complicated process, and this
task can be managed more easily when done independently of loading conditions, and the result can be used
repeatedly by combining it with different 'ordinary' load components or with different other container loads. This
principle is also dictated by the need to minimize the interdependence between the two large subsystems, LD
and CL.
In order to provide some shortcuts when working under LD, the following functions are provided:
■ the main container loading commands are available (add, remove containers)
■ a loading condition can have an 'own' container load that is read and stored automatically with the load
case
■ some administrative functions of CL are available under LD
The listing and drawing functions of CL are available under LD.
1.5 Steps involved

This paragraph gives a short overview of the steps involved in analyses including container loading.
1. Defining container types
This function is not necessarily ship dependent and standard type definitions can be prepared.
2. Defining the owner numbering system
To some extent, a numbering system can be standardized, but there is likely to be ship specific
exceptions requiring adaptations.
3. Defining container arrangements
The potential container locations are defined, beginning with the basic components, which can be
combined into larger sets.
4. Defining container loads
Different ways of using the container positions are defined.
5. Independent analyses of container loads
Calculations and graphic presentations of the container loads can be prepared independently of other
subsystems.
6. Analyzing loading conditions containing container loads

The behaviour of the ship as a whole is studied, when loaded with containers. This includes the effect on
the wind area in stability criteria.
Normally, the general ship geometry has been defined when container loading is done, but it becomes strictly
necessary only when loading conditions are involved.
1.6 History
Container loading was first introduced to NAPA in 1990. As demands on the system increased and a better
understanding on how it should work developed, the need to revise some basic solutions was recognized. In
1994, this revisions was made and the first official release to include the revised system was 95.1.
The data structures are to a large extent incompatible, and for the transfer from pre 95.1 versions to the present
one, see CL.2, chapter Conversion.
2 General principles
2.1 Basic concepts

The central concepts in the subsystem are container arrangements and container loads.
A container-arrangement means a definition of the possible container positions. Its role in the loading process
is similar with the compartments in ordinary loading. This function is installed as subtask CL, which can be
entered from the ship model (SM) task or the loading condition task (LOAD).
A container load is formed by a set of stacks. meaning a vertical set of containers loaded one upon the
other. A container arrangement describes the places where such stacks can be loaded. In connection with an
arrangement, the word 'stack' refers to such a place. As a way of defining many stacks at a time, there is the
concept of block as described in the next paragraph.
Defining a container load means placing containers into a container arrangement.
Container loads can be added as load components into a load case. The weight, center of gravity and weight
distribution are taken into account. Containers on deck are taken into account in criteria involving the profile.
Container loads are handled under task LOAD with the MASS command.
2.2 Parts of a container arrangement

Logically, a container arrangement is considered formed by a three dimensional matrix of spaces, oriented
as the ship coordinate system. The transversal layers are called bays, the longitudinal layers rows and the
horizontal layers tiers. These layers are numbered, and a container position can be designated by the bay,
row and tier number.
Bay, row, tier and stack

A set of containers with the same bay and row number and physically connected, i.e. standing on each other, is
called a stack. This is the basic component from which the container arrangement is formed. A stack is always
vertical, having a fixed location in x and y. When containers of different dimensions are loaded, the alignment
point controls the relative position in x and y so that the alignment point of a container is made coincide with
that of the container below or that of the stack. There may be several stacks in the same bay and row, normally
one under deck and one above deck. These are distinguished by their starting tier number. In most cases,
the word 'stack' refers to a physical stack as presented. A logical stack is the total set of containers with the
same bay and row number.
Except for the stacks, the bays, rows and tiers of a container arrangement need not be geometrically aligned,
i.e. a fixed coordinate being associated with a given bay, row or tier number. However, there are usually subsets
with this property, and for taking advantage of this in the definitions, the block concept is available. A block
is formed by a three-dimensional matrix of spaces with fixed x-, y- and z-coordinates in each transversal,
longitudinal and vertical layer, but not necessarily with uniform spacing. Within the matrix, there may be
positions not corresponding to possible container locations, which are specified in the block definition, and
taken into account when loading.
Example of a basic block
Example of a block with positions removed and non-uniform spacing

A set of stacks can also be defined directly, so that the relevant properties are defined directly for each stack
(pilot level only).
A block or a set of directly defined stacks can be used as such as arrangements. However, in most cases it is
useful to collect the arrangement from separately defined parts as a combined arrangement.
The following figure illustrates a combined container arrangement
Example of combined container arrangement

In order to give a preliminary idea of the definitions, the definition of the arrangement is presented below:
BLOCK IN-HOLD C1
X, 10, 6, 1, 6, 1, 6; Y 1.5 4; Z 0.3 5
REDUCT Y>HULL -0.4; SYMMETRIC
BLOCK ON-DECK C1, B1=4 T1=6
X, 22, 12; Y 0 4; Z 11.5 6; SYMMETRIC
COMBINE C-ARR1 IN-HOLD ON-DECK
2.3 Properties of stacks

The following properties are relevant for stacks. The symbols given below are the names of the quantities
representing the properties.
■ container type (CTP)
The container type provides the basis for the spacing and the default for container loads. The type can be
changed when containers are loaded. Capacities referring to the arrangement as such are calculated as if
the places are occupied with containers of the default type.
■ double size container type (CT2)
If the stack is such that it can be loaded in combination with its neighbouring stack by double sized
containers, a default container type is needed for this purpose.
■ position in x, y and z (REFX, REFY,REFZ)
This information is stored as the location of the alignment point the default of which is the lower x-, y- and
z-coordinate.
■ numbering, bay, row and tier (BAY, ROW, T1)
The bay and row numbers are fixed for the stack, while the tier number means the lowest tier in the stack.
■ number of containers that can be loaded
The nominal capacity of the stack is expressed by the number of containers of the default type that can
be loaded or indirectly by the highest tier number (TN). This implies a maximum height, which is the
actual limitation used.
■ maximum height (ZMAX)
This places a limit on how many containers can be loaded. It is inferred from the container positions
defined, as presented above, but can also be defined directly.
■ size, length in x, y and z (LENX, LENY, LENZ)
The size refers to the space reserved for the individual containers and is obtained from the default
container type.
■ on deck/in hold (DH)
It is recorded whether the stack is on deck or in hold. Unless explicitly defined, the default is based on the
tier number.
■ maximum stack weight (WSTMAX)
The maximum allowed stack weight places another limitation on the container load that the stack can
have and is used for check purposes.
■ alignment point (LXAL, LYAL, LZAL)
The alignment point is measured from the lower x- and y- limits and defines a reference point that is
made to coincide with that of the container. By default, the alignment point is derived from properties of
the default container type.
■ orientation, longitudinal/transversal (ORNT)
Containers are normally loaded as defined, i.e. with the x-dimensions longitudinally. By defining a stack to
be transversal, the containers are turned 90 degrees so that x and y change place.
The height of the associated container type decides the vertical spacing, i.e. the height of the tiers. These
heights will be modified if the stack is loaded with containers of differing height.

2.4 Properties of blocks

A block is fast way of generating a set of stacks forming a regular matrix. The basic information on which the
block is dependent is a set of x-, y and z- coordinates defining the locations of the bays, rows and tiers. By
separate instructions, stack specific deviations can be defined. The numbering is always such that consecutive
layers have consecutive numbers in the internal numbering system.
Other stack properties are either derived from the default container type or common instructions in the block
definition. However, individual maximum stack weights can be defined.
Comment. Presently, the only way to more directly define individual stacks is by way of a table, which is provided
as a pilot level feature.
2.5 Properties of container types

The main properties of containers are handled by defining container types. The definition of a container type
gives some fixed properties and some properties that are only defaults and can be changed in connection with
loading. In addition to the standard properties described below, the user can add own properties which can
be used in output functions.
The role of the standard properties is the following.
■ physical dimensions of the container
Since the system is not concerned with the detailed properties of the containers, these are presently
not used, but reserved for future functions, for instance in drawing. The physical container is assumed
centered inside the logical one.
■ logical dimensions of the container (LENX, LENY, LENZ)
These dimensions define the total space occupied by the container. It means the minimal distance
between consecutive containers, and decides the spacing of blocks and height of stacks. All local
distances are measured within the logical dimensions.
■ local center of gravity (LXCG, LYCG, LZCG)
The local center of gravity means the (default) center of gravity of the container, measured from the lower
limits of the logical container.
■ weight (W)
The weight defined for a container type provides the default when loading containers. In a given loaded
container it can be changed.
■ minimum, maximum weight (WMIN, WMAX)
The minimum and maximum weights define the interpretation of relative weights, so that 0%=minimum
and 100%=maximum. These are also used for error checks.
■ fill colour (FCODE, LFCODE)
The fill colour can be used when containers are drawn so that types are distinguished by colouring The
colouring can be defined as colour or pattern indices (FCODE) or logical fill codes (LFCODE).
■ alignment point (LXAL, LYAL, LZAL)
The alignment point is used for controlling the position of the upper container with respect to the lower.
The lowest container in a stack obeys the alignment point of the stack. The alignment point is defined
with respect to the lower limit of the logical container.
■ descriptive text (DES)
The descriptive text is used for documentary purposes.

Illustration of some container properties

Other properties can be defined as needed. These will have no function in the calculations, but are available
for output purposes or for doing selections. A list of such properties are maintained in order to allow the system
do some error checking (command QNT under ADM).
The dimensions related to the container are presented using quantities referring to x-, y- and z, according to the
normal orientation of the loaded container. However, it is possible to load a container transversally, in which
case the x- and y-dimensions change place.
The properties of the container types are taken into account when generating the geometry of blocks. If the
dimensions are changed, the definitions of the blocks have to be repeated.
2.6 Numbering of container positions

Container positions are designated by bay, row and tier numbers. The numbering system is global, i.e. it
concerns the total set of containers. Each part of the arrangement must therefore be placed into the global
numbering system.
In the internal processing, a numbering system is used that reflects spatial relations between the bays, rows
and tiers. Within this system, containers are numbered as follows:
■ bays are numbered 1,2,3..., in the order the bays are encountered when moving from the bow to the
stern. The numbering order can be be reversed by defining a different convention in the installation
parameters or configuration parameters (see task ADM). The numbering range actually used need not
start from 1.
■ rows are numbered so that the center row has number 0, if any, with numbers 1,2,...on the port side and
-1, -2 ... on the starboard side. If a left-handed coordinate system is used, the numbering is reversed.
■ tiers are numbered 1,2,3... from below up.
It is not necessary that all internal numbers in a given range are occupied in a given arrangement.
The numbering system used in commands and output. the so-called owner numbering. is defined
separately. From the system's point of view, this numbering system can be arbitrary, and works more like labels.
However, there are the functions presented below where the numbering system is used for distinguishing bays
with long and short containers. The owner numbering is defined by associating each internal number with an
owner number. This is the only place where the internal numbering is visible to the user.

The numbering systems
The owner numbering system has a very central role in both input and output functions, and should be
carefully designed and complete before starting with the main definitions.
The bay numbering convention (aft or forward) must also be fixed in advance.
2.7 Management of changes

The following categories of data are involved in the system:
■ the numbering system
■ container types
■ primary arrangement parts
■ combined arrangements
■ loads
This paragraph gives an overview of how the dependence between these categories are handled.
The numbering system is assumed to be fixed. At least to some extent an installation level standard should
be useful. There is no support for changes in the numbering system when the container definitions have been
made. However, in many cases a change of numbering may have no other adverse effects than that the output
of the DES command is incorrect.
The geometric properties of container arrangements are decided when the arrangements are defined, and
generated according to the container dimensions valid at that time. Changes in the container dimensions can
only be taken into account by repeating the definitions. Other dependencies of the container types are dynamic,
i.e. applied as valid when the system is run.
The dependence of combined arrangements on the parts is also handled dynamically.
A container load is stored in a way that tells what type of container is placed in a given position, expressed by
bay, row and tier numbers. If the arrangement is changed, the positions may disappear or change place and
these changes will be taken into account when the load is used. A load belonging to a nonexistent position

is removed. Changes of container types are also taken into account automatically. Note also that a container
weight given as a relative one is converted to an absolute weight and recorded this way.
If the container load has been affected by any of these changes, a message is given when reading it, telling
the resulting change in weight and container count.
2.8 Usage of alignment points

The purpose of the alignment points is to allow the system to load correctly containers of differing length, for
example a 40 foot one on top of a 45 foot one. The location of the upper container is adjusted so that the
alignment points coincide. The lowermost container obeys the alignment point of the stack.
This logic assumes that the alignment points on the bottom and the top of the container are the same. In other
cases, the difference must be declared in the loading command (quantities XCORR, YCORR).
This facility is primarily intended for the longitudinal direction, but for symmetry, the alignment logic is provided
in the y- and z-direction also. Alignment in the y- and z- directions is considered pilot level.
The alignment point is always measured from the lower coordinate in the current direction. There is no logic
for, for example, taking into account reflections of containers.
The following figure illustrates the alignment logic:
In the example, the two lowest containers are loaded normally. For the third container, a change of alignment
is given. This will automatically be inherited by the upper containers.
2.9 Mixed loading of long and short containers

In general, a stack is loaded by piling containers on top of each other, without affecting the neighbouring
stacks. Under the conditions presented below, it is possible to load a container so that it occupies two adjacent
bays. Most frequently, this occurs when loading 40 foot containers over two 20 foot bays. This following figure
illustrates an arrangement loaded with short and long containers:

Long and short containers
2.9.1 Long and short containers

For the purpose of mixed loading, a 'short' container means here one that occupies one stack, while a 'long'
one occupies two adjacent stacks. However, there may also be stacks designated for a single length. In order
to control the effect of loading commands in these cases, container types are also classified as long or short
using a length limit defined in the configuration parameters (see LCR/ADM). A stack is designated as long or
short depending on the default container type.
2.9.2 General requirements for mixed loading

In the arrangement, locations intended to be loaded by either one long or two short containers are defined as
two bays of the short type. These must be defined in the same arrangement part - such pairs are not checked
for between different parts of a combined arrangement. The two short bays form the physical definition of the
arrangement, for example, stack weights are relevant for these only. The long containers are treated as forming
formal bays. in contrast to the 'real' bays defined in the arrangement.
The arrangement part (block) concerned must have two alternative default container types defined. The longer
type should have (approximately) the double length of the shorter one, while the other dimensions are the same.
There must be a numbering system defined for the formal bays. For each formal bay, this numbering system
tells the bay number of the corresponding partial bays (command ON FORMAL). The figure above illustrates
the formal bay numbering.
Finally, the two short bays must be geometrically feasible:
■ same y
■ same z, after taking into account possible lower containers
■ the x-distance is small enough so that both ends of the long container are supported.
Whether a loading command gives rise to long or short containers is controlled by either
■ giving an explicit container type
■ giving a bay number belonging to the real or formal number set
The logic related to real/formal bay numbers in a loading command can be switched off (parameter RFMODE
under ADM).

The rules for this are explained in more detail in connection with loading.
2.10 List of quantities

The quantities used in the system are registered in the quantity standard and partially shared by other
subsystems. The following list gives an overview of the quantities used.
Available quantities
QUANTITY EXPLANATION
BAY bay number
ROW row number
TIER tier number
B1 start bay number
R1 start row number
T1 start tier number
BN last bay
RN last row number
TN last tier number
REFX,REFY,REFZ location of alignment point
CTP container type
CTP2 the alternative container type
FCODE fill colour (colour index)
LFCODE fill colour (logical fill code)
W container weight
WMIN container weight, minimum
WMAX container weight, maximum
WREL container weight, fraction
DH in hold (IH) or on deck (OD)
LXCG x-coord. of center of gravity, local
LYCG y-coord. of center of gravity, local
LZCG z-coord. of center of gravity, local
LXAL, LYAL, LZAL location of alignment point inside container
XCORR ... ZCORR correction to container position
XMIN...ZMAX extreme coordinates
WSTMAX allowed stack weight
DES descriptive text
NR number of container positions
NL number of containers loaded
PART name of arrangement containing a container
MASS loaded weight (note that W=weight of container)

XM, YM, ZM center of gravity of the load

VOLM volume of containers
CGX, CGY, CGZ center of gravity of the volume
These are the quantities relevant for the calculations. Other quantities can be added to container type definitions
and load definitions. These are available for output purposes and for doing selections. They must be declared
in the configuration parameters (command QNT/ADM).
3 Defining container arrangements

This chapter describes the definition of the components of container arrangements. At the end of the chapter,
some generally used syntaxes are presented, that also concern loading and output functions.
3.1 Defining a block

A block definition starts with command BLOCK, which is followed by a varying number of additional commands.
The definition is finished by command OK and optionally by a command not in the context (see command
BLEXIT/ADM). In addition to the definition commands, there are listing and plotting commands by which the
partial results can be checked, and the definition can therefore be done as an interactive process.
The shortest possible definition of a block contains the following information:
BLOCK name container-type
X x0 nx
Y y0 ny
Z z0 nz
The BLOCK command can contain options for specifying descriptive text and other properties, and records
ADD, REDUCT, SYM and REFLECT can be added with the effect described below.
The parts of the definition are described in more detail in the following paragraphs.
3.1.1 The BLOCK command

The BLOCK command starts the definition of a block.
The following parameters must always be given:
BLOCK name container-type
where
name:
in the name of block. In the data base, prefix CNTA* is added.
container-type:
The container type decides the geometric properties of the block and the default for loading. See also option
T (transversal).
If the block is intended for loading of both short and long containers, an alternative container type is needed
as presented below.
The block can be placed in the bay/row/tier numbering system by giving the start numbers in the BLOCK
command. All three numbers can be given by the syntax .
(b,r,t): start bay row and tier

or separately by the options
B1=i: bay number of the first bay

R1=i: row number of the first row.
T1=i: tier number of the first tier
(As always, numbers given in commands are owner numbers). If not given, defaults are set so that bay=1,
row=1 or 0 and tier=1 in the internal numbering system.
In addition to these parameters, the following optional parameters can be given:
T: transversal, apply the container dimensions so that x and y change place.

IH: defines the block to be in hold
OD: defines the block to be on deck default=from tier number
WST=w: maximum allowed stack weight, default=none
DES=text: the descriptive text
For the effect on row numbering by commands REFLECT and SYM, see below.
3.1.2 Block defined for mixed loading

If the block is intended to be used by both long and short containers, an alternative container type must be
supplied:
BLOCK name short-type/long-type
for example
BLOCK B1 D20/D40
The long container type should be approximately twice the length of the short one (normally 20 feet/40 feet). This
type provides the default when loading long containers and its existence signals that pairs of adjacent stacks
should be checked for in order to give the potential locations of long containers. These pairs are determined
according to the formal owner numbering system (see ON FORMAL) with the additional requirement that the
parts of the pair should be geometrically compatible. For the parameters controlling this, see command PTOL
in subtask ADM. The block can contain stacks not belonging to any pair.
If the latter container type is shorter than the first one in the BLOCK command, their roles are reversed.
Mixed loading is not supported for transversal containers.
3.1.3 Defining the coordinates

The location of the block and the spacings are defined by commands X, Y and Z, each having the same form,
here represented by x:
X x0 nx
This form defines that the starting x coordinate is x0, and then follow nx intervals of the length implied by the
given container type, taking a possible option T into account.
x0 is at the start of the first bay, and the steps following are added in the direction of increasing bay
numbers. Thus, if the bay numbering is from fore to aft, x0 is at the upper x-limit of the block.
Additional spaces can be inserted the following way:

X x0 nx1 d1 nx2 d2 ...

where d1, d2 are additional steps in the x-direction and nx1, nx2 etc the number of container lengths between.
nx1 can be entered negative, meaning that the lower limit of the block is -nx1 container lengths behind x0.
The other coordinates are entered analogically. For y, there is the option C instead of y0, placing the first
container centered at the center line, for example:
Y C 4
This command places 4 containers so that the first one is centered at the center line.
In the z-direction there are no fixed locations except for the lowest one, because the height of a container is
obtained by adding the heights of those below, which need not have the default height. The locations given
define the nominal capacity and imply the total height of the stack, unless modified by option DH in the MODIFY
command presented below. Containers cannot be loaded over the total height defined this way (concerns also
containers on deck). The spacings that can be given between tiers represent gaps that are maintained for each
tier regardless of the actual height of the loaded container. See also command ZCORR below.
No other parts of the definition can be entered before the coordinates are defined. The coordinates can be
changed by re-entering the corresponding command, provided that none of the additional commands have
been used.
The general syntaxes for referring to surfaces can be used, for example
Z #DECK1 4
However, there is no administration for handling possible subsequent changes, and updating of the block must
be made at the user's initiative.
If there is a repeated pattern in the container spacings, the following syntax can be used in the X and Y
commands:
X ... m*(n1,d1,n2,d2,...) ...
This notation means that the syntax within parentheses is repeated m times. Note that the first item is a number
of steps, not an additional spacing d.
In the last repetition, the last spacing d is not used. If the definition continues, it must begin with a spacing.
Example:
X 10.5 3*(2,0.5) 0.8 2*(3,0.4)
giving the same as
X 10.5 2,0.5 2,0.5,2 0.8 3,0.4,3
3.1.4 Example
3.1.5 Adding vertical gaps with the ZCORR command

As an alternative to adding spacings to the Z command, gaps between tiers can be defined with the ZCORR
command:
ZCORR d0,tier1,d1,tier2,...
Where d0,d1 etc are the spacings and tier1,tier2 etc define the places where the spacing changes. d0 is applied
from the start of the stack until tier1, below which the gap is d1 and so on. The following example illustrates
ZCORR and the equivalent Z command for a simple case:

BLOCK B1 D40 T1=1

...
Z 0 4
ZCORR 0 2 0.1 3 0.2
or
Z 0 2*(1,0.1) 0.2 2*(1,0.2)
giving
Simple block with spacings between tiers

If the block is loaded with lower containers than those defined in the BLOCK command, the number of tiers
may be larger than originally defined. The spacing defined for the highest tier is applied for the additional ones.
3.1.6 Removing locations

Removing locations means marking part of the spaces within the initial matrix as not used.
Removing locations can be done by directly specifying bay, row and tier numbers, or by a geometric instruction,
where a forbidden area is designated with the aid of a surface.
Removing locations by explicit numbers is done by a command of the following form:
REDUCT bay-range row-range tier-range
Each range can be defined either by
n: a single value
n1...n2: numbers n1 to n2 inclusive
* the whole range
Examples:
REDUCT 1 1 1
Remove the position in the lower left corner
REDUCT 1...2 * 1
Remove the transversal lines at tier 1, bays 1 to 2.
For a more complete description of how to designate container positions, including graphic input, see below.
The geometric reduction is done in the form
REDUCT Y>surface
This means that container positions wholly or partly on the specified side of the surface shall be removed.
Analogically, one can use Y<, Z> or Z<. (Y and Z designate coordinate axes, while '<' and '>' mean remove
containers at lower or higher coordinates respectively).
In order to be interpreted correctly, the surface should have the orientation according to the axis used (see
quantity ORNT in the output of INFO under DEF). The section of the surface must contain one branch only

and this is forced by connecting possible multiple branches. At places where no intersection is obtained, the
reduction is not done.
A translation of the surface at right angles to the normal of the x-section can be added in the form
REDUCT Y>surface d
where the sign of d tells whether the translation is in the direction of the positive or negative half axis (negative
in the example below).
Example of geometric reduct

The reduction is done by making x-sections at the lower and upper end of each bay. If one wants to see what
happens, the option CHECK gives a graphic check, for example:
RED Y>HULL -0.5 CHECK
The graphic check shows the containers before and after the operation in combination with the sections used,
as in the figure above. This check is made separately for each bay.
When using the CHECK option, the projection is changed to X if not initially set. If the drawing has not been
scaled in advance, it is scaled according to the current block. If the graphic output is directed to the intermediate
file, the result of the check operation is organized as an independent drawing, where each bay is shown as a
subdrawing. Note that any previous graphic settings are replaced.
The geometric reduction is implemented in order to save manual work in the definition, but a permanent
dependence on the surface is not handled automatically. If the surface is changed in a way that affects the
block, the definition must be repeated.
The ADD command is analogical with the REDUCT command, but only explicit index ranges can be given. It
can be used to restore positions removed by REDUCT, but not to extend the initial range. It can be used if
the geometrical reduct removes undesired positions, or it can be practical to reduct a whole layer, and then
add the positions intended to remain.
The figure below shows a block definition using the geometric reduct:
3.1.7 SYM and REFLECT

With the aid of commands SYM and REFLECT, the symmetry usually occurring about the center plane can be
exploited. The row numbering presented below concerns the internal numbering.
Command SYM makes the block symmetric by adding the reflected part about the center plane. Before entering
the SYM command, the block must either be entirely on the positive y side, or the first row may be centered at
y=0. In the latter case, this row will obtain number 0, otherwise the rows nearest the center plane get numbers
-1 and 1. Correspondingly, the initial starting row number must be 1 or 0.
The REFLECT command reflects the block about the center plane. The numbering is also 'reflected', i.e. the
first and last row numbers are interchanged and sign reversed.
These commands operate on the block as defined when the command is given, and the block can be
subsequently modified and, for instance, unsymmetric changes done. The following example shows two
symmetric blocks, one of which is transversal:

3.1.8 Defining stack specific exceptions

The stack weight, the location and the maximum height can be adjusted separately for given stacks, if the
common value is not useful. This is done with command MODIFY:
MODIFY bay-range row-range * symb=value,...
The range specification is done with the standard notation and specifies the stacks to be changed. The asterisk
designates the tier range which is irrelevant but included in the standard notation.
'symb' designates the quantity and 'value' its value. The following alternatives are available:
WST=w: allowed stack weight

REFX=x: new position in the x-direction. The symbol may be abbrieved to X.
Similarly REFY, REFZ.
DX=dx: change in the x-position. Similarly DY, DZ.
DH=dh: additional height above the highest container.
The height of the stack is by default calculated from the number of
containers. The option dh specifies an additional height that may be
available if the stack is loaded with containers of differing height.
3.1.9 Auxiliary commands under block definition

Information about the current block definition can be obtained with the following commands:
DES: same command DES on the main level. Without parameters, the current
block definition, as far as entered, is displayed.
LIST: lists data using the same LIST command as on the main level.
PLOT: same as the plot command on the main level. Commands SIZE, FILL
COLOUR and PROJECTION are available to support the PLOT command.
Command PO is also available, including option AUTO.
In the LIST and PLOT commands, the logic of plotting container loads is borrowed for separating places in the
initial matrix from those removed by REDUCT, so that places actually remaining are treated as loaded.
Using the standard LIST and PLOT commands as auxiliary output functions under BLOCK is a convenient
way of making a large set of output functions accessible, but it is not guaranteed that all options produce
useful results.
3.1.10 Finishing the block definition

The block definition can be finished explicitly with command OK. Command SKIP finishes the definition and
abandons the result. Optionally, the block definition is finished when a command not known in the context is
entered (see parameter BLEXIT/ADM). Before the minimum block definition has been entered (commands X,
Y and Z), it can be finished with SKIP only.
3.2 Defining combined arrangements

Arrangements can be combined into larger sets with the COMBINE command:
COMBINE name part1 part2 ... DES=text

where 'name' is the name of the arrangement created

'part1', 'part2' etc are the names of the parts, which can be blocks or combinations of blocks.
'DES=text' is optional, and gives text used for documentary purposes.
Arrangements can be combined on several levels (i.e. the parts may also be combined). When read for use,
the arrangements are decomposed into the basic parts, and the intermediate levels will not be visible.
The blocks in the example ship and some combinations

The parts must not overlap each other, neither geometrically nor in the numbering. This is checked when a
combined arrangement is read for use and a warning is given telling the bay, row and tier numbers of the first
place a violation of this rule is encountered. The arrangement is accepted even if there are overlaps, but stacks
containing common numbers with a preceding one are removed.
3.3 Defining stacks under table calculation (pilot)

A container arrangement is internally treated as a set of stacks. This set of stacks can be presented as a table
and treated under table calculation. This possibility can be used as a pure output function, and it can also be
used as a way of defining container arrangements. In the latter possibility is presently implemented on pilot
level only.
The table defining a container arrangement contains the following quantities, some of which are optional.
Quantities available for container arrangement
BAY bay number
ROW row number
T1 start tier number
TN highest tier number
CTP default container type
CL2 default long container type, default=empty
REFX x-coordinate of reference point
REFY y-coordinate of reference point
REFZ z-coordinate of reference point
ORNT orientation (L or T, default=L)
LXAL location of longitudinal alignment point measured
from the lower limit (default 0)
LYAL,LZAL similarly for y, z

XMIN x-coordinate of lower limit (default=calculated)

XMAX...ZMAZ similarly for the other limits
Bay row and tier numbers are given as owner numbers. If the columns XMIN...ZMAX are present all values
within the columns must be given.
When used for defining arrangements, note the following:
The name rule is the same as for arrangements defined by other means, i.e. CNTA*name. Thus, the catalog
will not show directly what arrangements are defined under table calculation and what are defined otherwise.
Arrangements defined as tables can be separated by adding the selection criterion TYPE=19000.
An arrangement not defined as a table cannot be read directly under table calculation. However, in the main
task of CL, the command CNTA name; reads the given arrangement, converts it to a table and enters table
calculation. If the original definition was not as a table, the name is modified by appending .T.
3.4 Designating subsets of bays, rows and tiers

In various definition, loading and output functions, there is the need to specify ranges of bays, rows and tiers,
for which the following alternatives are provided.
When doing the specification numerically, the form is
(bay-range row-range tier-range)
where each one of the ranges can be specified in one of the forms:
n: single index
n1...n2: range from n1 to n2 (inclusive)
* the whole range
The numbers represent owner numbers. A range is interpreted so that the containers corresponding to the
upper and lower limit are taken and all between them in the internal numbering.
The parentheses belong to the syntax. They are optional in commands specifically designed for use with the
range selection (ADD, RED, MOD under block definition, ADD, RED and CHG commands of loading), but
needed when used as options in subset selections.
The ranges can also be given graphically, if there is a suitable drawing available. The drawing must be made
in an orthogonal projection, and the projection, scaling or plot options must be the same as when the drawing
was made.
The bay, row or tier range is shown by pointing at the lower left and upper right containers in the range selected.
In the viewing direction, one cannot show the range, and it has to be entered numerically as the first item, using
the syntaxes above. It can be omitted if the whole range is selected.
Example: In an ADD command, a range of bays and tiers is shown in a side view, selecting rows 1...4
numerically. The following is entered from the keyboard (note the colon):
ADD 1...4 :
then the lower left and upper right corners of the range are shown on the screen.
The ordinary data echo will show the graphic input as the coordinates pointed at, and an additional data echo
will be produced showing the input as interpreted to bay row and tier numbers.
The following unofficial service is available for arrangement plans if the name of the part used in the input
has the form
BAY nr or BAY n1-n2

and similarly for ROW or TIER. When using such a plan part for graphic input, the range implied by the plan
name is used in the result.
Formal owner numbers can be used for designating ranges, which will include both partial bays corresponding
to the formal number. In loading commands, additional interpretations may be done as presented later.
3.5 Defining arbitrary subsets

The most general subset selection is formed by the a combination of the following components:
brt-range special-options location quantity-criterion
The partial criteria are formed as follows:
brt-range: the syntax presented above, including parentheses.
special-options:
IH: only containers in hold

OD: only containers on deck
L: only loaded container positions
U: only unloaded container positions
A: both loaded and unloaded positions type (the name of a container type)
only containers of the given type
PART=name: containers in a given partial arrangement
location:
A location is given in the form axis=q or axis=(q1,q2), and selects the containers at least partly inside the given
range. Examples:
Y=0
X=(0,20)
quantity-criterion:
Quantity-criterion means a selection criterion formed using the available quantities and the general selection
syntax (see !EXPL SEL/GEN). The standard quantities are always available, in addition there may be own
additional ones (see command QNT in subtask ADM).
TYPE=T1
W=0...2
the quantities BAY, ROW and TIER are also available and provide an alternative way of selecting number
ranges. However, the effect may be different than using the range syntax. The difference can best be
understood by taking into account that this criterion is in all respects similar with a criterion involving, for
instance, the container weight.
As an example of several criteria combined, the following syntax selects all loaded but empty containers
between bay 20 and 32:
(20...32 * *) L WREL=0
The dummy command SEL in the main task gives access to the explanation of the selection syntax (use !
EXPL SEL).

Interpreting the general selection syntax is an own function. This is the reason for the need to separate this
syntax from others, for example in the PLOT command, where the distinction with respect to the plot options
may feel unnatural. In commands the keyword SEL is used for separating the selection syntax.
Examples of selections used with the DRW command
4 Auxiliary definitions
This chapter presents the auxiliary definitions, i.e. container types, owner numbering and other definitions not
producing container objects.
4.1 Definitions related to the owner numbering

The following subjects are related to the owner numbering:
■ the actual numbering, i.e. the set of owner numbers
■ numbering rule for real/formal bays
■ number range of containers in hold/on deck
Command ON defines handles all definitions concerning the owner numbering, including some administrative
functions.
4.1.1 Defining the numbering

The main part, the actual owner numbering, is defined separately for the three axes in the form:
ON axis i0 n1, n2, n3 ...
where
axis: X, Y or Z; defines the direction concerned
i0: first index defined (bay if axis=x etc)
n1,n2... owner number for index i0, i0+1, ....
If owner numbers are evenly spaced, the normal series syntax can be used.
Example:
ON X 1 3 6 (8 24 4) 26
defining owner numbers 3,6,8,12,16,20,24 and 26 for bays 1 to 8.

With option LIST, a list of corresponding user and owner numbers is printed for a given axis, for example ON
X LIST. For the example above, the result would be
X 1 2 3 4 5 6 7 8
ON 3 6 8 12 16 20 24 26
Make sure that owner numbers are defined for the whole range to be used.
Unused ranges in the internal numbering have no effect on other functions than plotting with the NG option,
where the internal numbering decides the coordinates plotted.
Without a complete owner numbering system, only some administrative functions are available.
4.1.2 Defining the formal owner numbers

For mixed loading of long and short containers, the formal owner numbering system controlling the location of
long containers is defined by the ON FORMAL command:
ON FORMAL p11/f1/p12 p21/f2/p22 ...
or
ON FORMAL ISO
The first form defines explicitly the relation between the real and formal bay numbers. Each triple
p1/f/p2
specifies that the pair of bays p1 and p2 together forms the formal bay f. p1 and p2 must be two consecutive
bays.
The second form specifies the ISO mode numbering, which is equivalent with
ON FORMAL 3/4/5 7/8/9 11/12/13 ...
within the range of covered by the owner numbering system.
This definition cannot be entered until the bay numbering has been defined. When entering the definition, it
is checked that it is consistent with the bay numbering. This check is not repeated if the bay numbering is
subsequently changed.
4.1.3 Owner numbering range separating containers in hold/on deck

For deciding whether containers (or more precisely stacks) are on deck or in hold, a default can be defined
via the owner numbering system. The command
ON INHOLD t1 t2
defines a tier range such that tier numbers from t1 to t2 (inclusively) are considered being in hold, while others
are on deck.
4.1.4 Example
4.1.5 Copying the owner numbering system

The owner numbering can be copied from another project or version in the form

ON FROM A (copy from version A) or

ON FROM A/P1234 (copy from version A in project P1234)
The current owner numbering in the system can be stored in the system data base by the command
ON SAVE
It can copied for use in the current project by the command:
ON FROM SYSDB
If no owner numbering system has been stored in the project, the one in the system data base is used.
4.2 Various parameters (subtask ADM)

A number of properties of the system can be adapted to the local needs. The definitions are collected as
subtask ADM and the result is stored in a description named CL*CONTROL. When entering container loading,
this description is read from the project data base if available, else from the system data base. If none is found,
built-in defaults are used.
Some of the parameters presented here belong to functions that will be presented in more detail in their
respective contexts.
4.2.1 Bay numbering convention

Whether the bay numbering goes from fore to aft of or vice versa can be defined in the configuration parameters.
The default is fetched from the installation parameters (see document MN.2). The possibility to use the
reference system (task REF) is still available but is considered redundant and replaced by the own facilities
of CL.
The bay numbering is defined by the command
BAYNR FORE bay numbering forward (lower numbers in the aftbody)

BAYNR AFT bay numbering aft (higher numbers in the aftbody)
Objects defined with a different bay numbering convention than the one currently valid will work incorrectly.
4.2.2 Source of container types

The name of the table providing the properties of container types is by default STD. Another name can be
defined by command CT.
4.2.3 Defining additional quantities

An overview of the standard quantities used in the system is presented in chapter 1 and more closely in
their respective contexts. These quantities are automatically available in the functions they are intended for.
Additional quantities can be introduced as properties of containers. Their values can be given via the container
type definitions or in the container loading commands.
In order to make the management of quantities easier and to allow for error checks, the additional quantities
must be declared with the QNT command:
QNT symb1 symb2 ...
where symb1, symb2 ... are the symbols used in the quantity standard.

4.2.4 Check mode

When loading containers, various checks can be done regarding matching container dimensions, correct
loading of the container below etc. By default, the checks are done with each loading command and a violating
loading command is not carried out. The options are to suppress the checks or to make the messages only,
and these are set with the command ERM.
The mode is expressed by a combination of the following characters:
R: report error directly when loading (default)

N: do not report errors directly
S: no not carry out a loading causing the error (default)
A: accept a container in spite of the error
4.2.5 Criterion for separating long and short containers

By default, lengths under 9m (appr. 30 feet) are considered short and lengths over 9 m long. This limit value
can be changed by command LCR.
When executing loading commands, long container places are (without error message) disregarded when
loading short containers and vice versa.
4.2.6 Criterion for accepting differing container dimensions

When it is checked whether a container matches the dimensions of the location designated, two factors are
used:
If the container is shorter (in the x- or y-directions) by a factor LT1 it is considered too short. If the container
is longer by a factor LT2, it is considered too long.
Note the difference with respect to the preceding parameter, which is used for interpreting the intention of a
loading command.
4.2.7 Height tolerance for long containers

When loading a long container, it is checked that the containers below are at the same height by a tolerance
ZTOL. The built-in default is 0.1 m.
4.2.8 Interpretation of real/formal bay numbers in loading commands

As presented in connection with mixed loading of long and short containers, the way the bay number is given
(real or formal) may affect the interpretation of a loading command. If one prefers to control this aspect by
using explicit container types only, the real/formal interpretation can be switched off with command RFMODE.
If RFMODE=OFF, bay numbers affect the range only. The built-in default is ON.
4.2.9 Exit from block definitions

It is possible to select whether a block definition is considered finished when a command not belonging to
the context is entered, or whether an explicit OK or SKIP command is needed. The selection is done with the
command BLEXIT, with parameter AUTO or MANUAL. The built-in default is MANUAL.

4.3 Default template

When using the plot option MI (mark inside), a template can be used for controlling the layout instead of the built-
in logic. A default template can be given with the command TEMPL. The built-in default is to use no template.
4.4 Default substance for LCA NEW

In the main task of loading conditions (LD), a new container load can be created and added to the loading
condition with command LCA NEW. The substance recorded for the load (quantity LOAD) is by default CONT,
i.e. the equivalent MASS command is
MASS CONT name
This default can be changed with the command SUBS.
4.5 Defining container types

Container types are defined under table calculation as tables where each line defines a container type. The
tables have the prefix CNTT*. The standard columns are listed below, and others can be added as needed. All
table calculation facilities are available, and for example, combined tables can be used for collecting data from
several sources. Command CNTT enters table calculation with subject (=table prefix) set to CNTT.
Commands for container type definition
CT identification of container type (key)
DES descriptive text (default=empty)
W default weight
WMIN minimum weight(default=0)
WMAX maximum weight(default=W)
CTLENX spacing in x
LENY spacing in y
LENZ spacing in z
LXCG local center of gravity (default LENX/2)
LYCG local center of gravity (default LENY/2)
LZCG local center of gravity (default LENZ/2)
LXAL length from aft end to alignment point (default 0)
LYAL length from -yend to alignment point (default 0)
LZAL length from bottom to alignment point (default 0)
FCODE fill code (integer)
LFCODE logical fill code, alternative to FCODE
FIG figure (for plot option FILL=CT)
The columns having a default can be omitted. FCODE, LFCODE and FIG can be omitted if the corresponding
services are not used (see plot options FIG and FILL). Other quantities can be added as desired. These are
available in various output functions, but are not taken into account in the calculations.

A model table named CNTT*MODEL is delivered with the system, providing the table structure and sample
definitions.
When running the system, there is a single table of type definitions used. The built-default for the name of it
is STD, but it can be changed under task ADM.
When starting container loading, CL makes an own copy of the container type table. If the table is changed,
this copy must be updated, either by returning to task level or by using the command RESET !, which will
return container loading to its initial state. Any container objects in the run time memory will be removed.
4.6 Templates for controlling texts inside containers

When plotting containers, information in text form can be written inside the containers (plot option MI, mark
inside). The layout of these texts can be controlled with templates giving the position and text height relative
to the container contour.
A template is defined as a macro, where the relevant information is expressed by drawing commands as in
the task DR, and a template can be used as drawing macro for showing the result. The name of the macro is
given as parameter to the plot option TMI.
A template contains the following parts:
■ a contour defined with the POL / (u1,v1) (u2,v2); command defining the borders of the template.
■ a number of TEXT commands of the form
TEXT text (u,v) t (ii)
where t and (ii) are optional. From this, the location (u,v), the inclination t and the optional alignment specification
(ii) are extracted.
■ TH th; commands by which the text height is controlled.
Any other commands are ignored, and can be added for the purpose of making the macro more useful for
drawing.
Depending on the number of quantities given in the MI option, a different number of texts is produced and
consequently the need for different layouts. For handling this, a single template can contain many sets of text
fields. In the order they appear, the texts represent the following items:
1: the result of MI=qnt

2,3: the result of MI=(qnt1,qnt2) (text nr 2 represents qnt1 and nr 3 qnt2)
4,5,6: the result of MI=(qnt1,qnt2,qnt3) and similarly for larger sets
When combining information for a long container and its parts into a common layout, the usage of the template
is different, as presented below.
A text item can be suppressed by placing the field below the template more than the height of the template
i.e. v<v1 -(v2-v1).
Example:
NEW CL-TEMPLATE
size -1 2-1 2
th 0.22
pol / (0 0) (2 1)
text t1 1 0.5 (22)
th 0.18
text t21 0 1(04)
text t22 2 0(40)

th 0.15
text t31 0 0.7 (01)
text t32 0 0.4 (01)
text t33 0 0.1 (01)
The following figure shows the result when the template is used with different MI options:
The template itself is added by the option TMI=CL-TEMPLATE. (This template is delivered with the system).
A single macro can define many templates by repeating the POL command and the subsequent texts. For a
specific container, the template that best matches the proportions of the current contour is used.
When combining data for a long container and its parts into a common layout, every quantity needs three fields,
and a template designed for this purpose must have fields as follows:
1,2,3: the result of MI=qnt

1=the long container
2,3=the short containers
4...9: the result of MI=(qnt1,qnt2)
4,5: the long container
6,7: the short container to the left
8,9: the short container to the right
5 Loading functions
This chapter describes definition of container loads. A container load is formed by a container arrangement
where it is defined what positions are occupied and with what type of containers. Handling of container loads is
mainly done under the container loading subtask (CL), and the result as a whole is added as load components
to a loading condition. In addition to this, the main loading commands and some administrative functions are
available directly in the loading condition subtask.
5.1 Role of the container arrangement

The role of the container arrangement is similar with the compartments in ordinary loading, and there is
no restriction regarding the set of container arrangements occurring in a single loading condition. One can
therefore use different container arrangements as it serves the purpose. For instance, in order to define a
container load that is wholly under deck, a container arrangement containing only such blocks automatically
restricts the scope of loading commands accordingly.
5.2 The container type

In the simplest case, a container load is defined by only selecting the loaded/unloaded positions. These will
then be loaded according to the properties defined for the default container type. For more specific loading,
the container type can be changed or properties of the containers can be given directly. From the calculation
point of view, the most important property is the weight of the container.
The height of the container loaded decides the height at which the next container in the stack is placed.
5.3 Administrative commands

The administrative commands for creating and storing container loads are the usual commands NEW, GET,
RENAME, SAVE, REPLACE and UNSAVE. In addition there is the command TREAT which makes a load
current from the run time memory. In contrast to this, GET always reads from the data base.

The object of the loading operations is the load made current by command NEW, GET or TREAT. When a new
load is made current, the preceding one remains in the run time memory and can be made current again with
command TREAT. The current load is also the default object for commands LIST, DRW and PLOT.
Command WHERE tells the name of the current load and those in the run time memory. In addition, it tells
whether the loads have been changed but not stored in the data base.
Command RESET ! initializes CL and removes any container loads in memory.
Definition of container arrangements (commands BLOCK, COMBINE) will also cause any loads in the run
time memory to be removed. If the current one has been changed but not stored, it is saved so that it can
be rescued with command GET *.
Command CAT L gives a list of stored container loads.
5.4 Definition of loads

The following paragraphs describe the functions by which container loads are created and modified.
A graphical tool for container loading is added in Loading Conditions Window, please see Container loading
GUI for more detailed information.
5.4.1 Creating a new container load

A new container load is created with command NEW. The arrangement to which a container load belongs is
defined in the NEW command, either as a separate item or as part of the name, for example
NEW L1 CA1
NEW CA1.L1
both creating a container load into arrangement CA1, the first one named L1, the second one CA1.L1.
A descriptive text to be used in listings can be added with command TEXT.
5.4.2 The ADD, REDUCT and CHG commands

The main loading commands are ADD and REDUCT, for loading or unloading containers into specified positions
and optionally change parameters such as the container weight. In addition, there is the command CHG which
only changes parameters of containers.
These commands are otherwise similar, except that
■ ADD makes the positions in the given set loaded and optionally changes container properties
■ REDUCT makes the positions in the given set unloaded
■ CHG changes container properties but keeps the status of being loaded or unloaded
As a short indication of the effect of a loading command, the container count and weight are listed as valid
before and after carrying out the command.
Initially, the container type defined in the arrangement provides the default for the properties of the container
loaded into given positions. These properties may be modified or extended in the loading commands.
If a container position is made unloaded, the current container properties (e.g. container type, weight) remain
and if the position is made loaded again, the previous values are still valid.

5.4.3 The ADD command

The simplest form of the ADD command is
ADD bay-range row-range tier-range
where the general syntaxes for expressing the ranges are used, including the possibility to use graphic input.
Examples:
ADD * * 1 load the whole tier 1

ADD 1...5 * 4 load bays 1 to 5 in tier 4
In this form all container positions in the given range will be loaded. Any other properties such as container
type or weight will have the values they had when the positions were last loaded, or if the positions had not
been loaded before, the values of the default container type.
For the effect of using real or formal bay numbers, see paragraph on mixed loading.
In the following, the notation 'ranges' refers to the bay/row/tier ranges as presented above.
The more general forms include possibilities to change the container type or other properties and to use more
general options for designating the locations concerned.
5.4.4 Specifying container properties in the ADD command

The container type is changed by adding the new type as the first (note) parameter:
ADD type ranges
Example:
ADD T40A * * 3
Containers of type T40A are loaded into the whole tier 3.
The container type is set to default by the command
ADD STD ...
All properties of the container type will automatically be transferred to the loaded container. Values differing
from the standard ones or parameters not related to the type can be defined in the ADD command. These
values are given before the bay/row/tier range in the form qnt=value, where 'qnt' is the standard symbol of
the quantity.
ADD qnt=value ... ranges
Several quantities can be given at a time. The most important case is changing the weight, for example
ADD W=2.5 * * * (absolut e weight)

ADD WREL=0.5 * * * (rela tive weight)
For the relative weight, a shorter form is available:

ADD 50% * * *
A change of type can be combined with assigning other properties provided that the type is entered first.
Note: any properties given explicitly keep their values when the container type is changed. An explicitly assigned
value can be cancelled by assigning value=0 (or empty for string items). All values of a given quantity can be
reset to standard values by the command
RESET qnt

5.4.5 General subset selections

In addition to the bay/row/tier range, all possibilities of the general subset syntax are available for designating
the set of container positions concerned by the the ADD command:
ADD 'ranges' SEL subset-specification
Any part of the criterion can be omitted, but they must be entered in the given order. The keyword SEL is
necessary only when the part 'ranges' is omitted.
For the parts of the selection criterion, see separate paragraph. Note specially that the name of a container
type can be used as a selection criterion, selecting containers of the given type.
Examples:
ADD C40A * * * U
Load all presently unloaded positions with containers of type C40A.
ADD W=10 SEL OD W>10
Change the weight to 10 in all positions on deck presently loaded with more than 10 tons.
Note the difference between the following commands:
ADD W=0.5 1 * *
ADD 1 * * W=0.5
In the first case, W=0.5 defines a property, in the latter case it belongs to the selection criterion.
5.4.6 Summary of the ADD command

With all options presented at a time, the syntax of the ADD command is
ADD type properties ranges SEL subset-spec !
type: the container typet

properties: e.g. weight
ranges: bay, row, tier range
SEL subset: general subset selection
!: force the command to be carried out even if some loading rule is violated

Examples of ADD commands
5.4.7 The REDUCT command

The REDUCT command is otherwise equivalent with the ADD command, but the positions in the range are
made unloaded and container properties cannot be changed. Thus, the syntax of the REDUCT command is
REDUCT ranges SEL subset-spec !
5.4.8 The CHG command

The CHG command is otherwise similar with ADD, but the status of being loaded or unloaded is not affected.
Thus, the only effect is to change some properties of the containers. The syntax of the CHG command is
identical with that of ADD:
CHG type properties ranges SEL subset-spec
By default, the CHG command concerns loaded positions only.
The similarity with ADD makes the CHG command somewhat unnatural in some simple cases. For example,
to change all containers of type C1 to C2, the command is
CHG C2 SEL C1
5.4.9 Changing the alignment

By default, the alignment point of the container is made coincide with that of the lower container or that of the
stack. This can be changed by assigning the quantity XCORR, YCORR or ZCORR. The effect is to move the
container the given distance in the given coordinate direction. The following figure illustrates this:

Effect of change in alignment

The value of the correction is entered using the normal syntax. For example, changing the location of the
container at bay=12, row=1 and tier=7 is done by the command
CHG XCORR=0.5 12 1 7
Note carefully: the containers above the one corrected this way will also obey the correction - their alignment
is done the normal way with respect to the lower container. Thus, changes in alignment in several tiers will
be cumulative.
5.4.10 Loading containers occupying double bays

This paragraph describes the special questions related to loading a container that occupies two positions in
the arrangement. The most frequent case is loading a 40 foot container into two 20 foot positions. A container
corresponding to a single position is here referred to as 'short' and one occupying two positions as 'long'.
The general requirements for this are presented in connection with properties of container arrangements:
alternative container type defined with the arrangement, numbering system for formal bays, geometric
compatibility between the stacks concerned.
By default, containers are loaded according to the arrangement definition, which in this case means the short
type. Loading a long type can be defined explicitly in the loading command. In this case, the way the bay range
is expressed is not relevant.
If no container type is specified, the owner numbering system is applied. If the given bay number belongs to
the set of short bays, it implies the current short type, if any, else the default short type. If the given bay number
belongs to the set of long bays, it implies the current long type, if any, else the default long type. Note: when
giving a bay range, the way the lower limit is given decides the interpretation. The interpretations related to
real/formal numbers in a loading command can be switched off with parameter RFMODE under ADM.
When the whole range is designated (syntax *) or graphic input is used, a change of container type must be
done explicitly.
Note that this logic may cause an implied type change, . causing the weight and other container parameters to
be . reset to standard values. In the following, a precise specification is made for the action in different loading
commands.
■ no container type given in the command
■ no long/short set implied (whole range, graphic input, or the given bay belongs to a non-shared bay,
RFMODE=OFF).
■ loaded contained position: same type as before
■ no alternative type in the arrangement definition: loaded with the single default type
■ alternative types in the arrangement definition: loaded with the short type.
■ bay number belonging to the short set
■ no alternative type in the arrangement definition: Loaded if the position is classified as short according
to the length criterion (parameter LCR/ADM).

■ alternative types in the arrangement definition: loaded with the short type.

■ bay number belonging to the long set

Analogically with the preceding case
■ container type given in the command
■ the new type is classified as long
■ no alternative type in the arrangement definition: Loaded with the given type if the stack is classified as
long, else not affected

■ alternative types in the arrangement definition: loaded with the long type.
■ the new type is classified as short
Analogically with the case above.

The following simple example illustrates the basic principle for loading 20/40 ft containers. The block in question
is defined as follows
BLOCK B1 C20/C40 B1=3
X 40, 6
Y 0, 3
Z 10, 2
The load of the example

The load is defined by
NEW B1.L
ADD 13...9 2 10
ADD, 12 2 20
ADD, 3 2 *
5.5 Checks
5.5.1 Checks done when loading

The following checks are made or can be made when carrying out a loading command:
■ the location exists. Bay, row and tier ranges are truncated to the actual range. In the z-direction, the
maximum height of the stack is checked. When loading a long container, it is checked that both halves
exist. All checks of this group are done silently, i.e. the effect of the loading command is restricted without
error messages. The warning 4937, 'no change done', means that the set of applicable positions was
reduced to zero.
■ the container below is loaded. In the case of a short container,it is also checked that it is not loaded with a
long one.
■ the container dimensions match those of the stack.The acceptance criteria can be modified by
commands LT1 and LT2 under ADM.
■ in the case of a long container, it is checked that the parts below are at the same height. The tolerance
can be adjusted with command ZTOL under ADM.

Illustration of ZTOL
■ if the container weight is given, it is checked with respect to the maximum and minimum weight of the
given container type.
■ the total stack weight is checked with respect to the allowed stack weight.
Whether to do these checks or not and whether to do the loading in spite of an error can be controlled by the
command ERM under ADM. The stack weight check is done after the loading and in case of a a violation, a
warning is given.
By adding the option ! as the last parameter of the loading command, it can be forced to be carried out even
if it violates some of the conditions above.
5.5.2 Separate checking

With command CHECK, an existing container load can be checked. Some of the errors listed below are unlikely
because of the direct checks, but even if the immediate check mode is on (the default, see ERMODE/ADM),
a loading operation can have indirect effects that are not covered by the direct checks. The separate check
also includes some aspects not covered by the direct ones (extension of the container, position of the center
of gravity).
The CHECK command has the following parameters
CHECK options SEL subset
The options are
ADJ: (adjust) correct some loading errors:

- lower containers to fill a gap
- correct weights and centers of gravity out of range
AS: (adjust silently) do the adjustments without reporting errors
CODES: special function: make a list of the errorcodes used for the quantity STAT
in LIST ST.
For each stack, a given error is reported only once, even if it occurs in several containers.
The error checks can also be included in the result of LIST ST by adding the quantity STAT, for example
LQ CLS BAY ROW MASS WSTMAX STAT
The value returned in the STAT column is composed by a set of letters, one for each error found in the stack:
D: container dimension in conflict with stack

E: container position below is empty
M: maximum stack weight exceeded
O: container extends outside stack
W: container weight not within limits
C: center of gravity not within limits
L: short container loaded over long one

Z: heights under long container differ
This list is obtained by command CHECK CODES.

The criterion for error O is that the container extends outside the limits of the stack by the factor given by the
parameter LT2 (same as used for testing too long containers).
5.5.3 The UNDO command

Command UNDO cancels the last change of a container load. Repeating UNDO has no further effect.
5.6 Defining container loads under table calculation (pilot)

As presented under output functions, there is the possibility to create a table presenting container loads in
various ways.
The reverse function, creating a load as a table is implemented on pilot level. Such a table is likely to be large
and inconvenient to handle, but offers the ultimate solution when a container load has to be treated in great
detail or received from an external source. 'Pilot level' means among other things that there are no support
functions under table calculation such as error checking and it has not been tested that all possible cases can
be handled.
A table representing a container load has prefix CNTL* and must contain at least the following columns:
BAY, ROW and TIER: locati on of the load

CTP: type of container loaded
As an alternative to the columns BAY, ROW and TIER, the column ID can be used, containing the location as
a single item Cbbrrtt. By assigning this as the key column, there is automatic check for duplicates.
Optionally, any other property that can be defined for loaded containers can be added, for example the weight
W.
For easier change of status from unloaded to loaded and vice versa, the column NL can be added. A container
having NL=0 is considered not loaded while >0 means that it is loaded.
The arrangement to which the load belongs must be defined separately by the command
QNT ARR name
where 'name' is the name of the arrangement.
For handling tables representing container loads, table calculation is entered with the command CNTL. With
option *, the current load is transferred to the work area of table calculation. Creating a load from scratch is
easiest this way (otherwise all potential container positions would have to be entered manually). The CNTL *
command has an option composed of one or two of the following letters:
K: create an ID column rather than BAY, ROW and TIER

U: add also unloaded positions and the column NL
The tables are named according to the name rule of container loads i.e. CNTL*name. The differ in the
description type, which is 1970 for tables instead of 4201 as used by CL.
A load created as a table can be used as any other load. It can be modified with the normal loading commands,
but if replaced it will be stored in the standard format, not as a table.
The container load currently in the work area of table calculation can be made active with the command CNTL
LOAD.

There is only one work area of table calculation at a given time and this is shared by the commands TAB,
CNTT, CNTA and CNTL. Command TREAT (of table calculation) can be used for restoring a work area
no longer active.
5.7 Graphic information

The possibilities for showing a load graphically are presented in connection with drawing of containers in
general. In summary, the following possibilities are available:
■ separating loaded positions from others by dashing or filling (option LB)
■ adding information about container counts, weights etc inside the container boxes or at the sides of the
plan.
■ showing the container type by text or fill colour.
When a container load is made current with command NEW or GET, it becomes the default object of plotting
- the PLOT and DRW will plot the current load unless a different object is given explicitly.
With option AUTO, automatic drawing of changed loads is set. In order to set a drawing mode that actually
shows the loads, option AUTO also causes options LB and NL to be set, i.e. both loaded and unloaded positions
are shown, and the number of loaded positions is written. (PO AUTO, NL=OFF; is needed for AUTO without
NL). If filling is done (command FILL or plot option FILL), the loaded positions are separated from the unloaded
ones by the filling, otherwise by changing line type.
The following figures are examples of graphic display of loads:
Load shown in a horizontal section, with number of loaded positions marked and colouring according to load
type, corresponding to options: PO Z=5 FILL=CT NL LB N
Load shown in 3d (options FILL=CT LB)

The following figure shows the definition of a load and its presentation as a section at y=0.

Example: plot options in output
5.8 Description of a container load

Producing an alphanumeric description of a container load (command DES) poses the problem that the load
definition can be the result of an interactive process, where part of the commands may cancel each other.
However, reconstructing a set of commands which would do the same thing in a shorter way has been
considered far too complicated to be done in a way generally useful, especially in the presence of varying
container properties. Therefore, the DES command will produce whole definition history of the load. Command
RESET is provided as a way of emptying a load and restoring standard parameters, which will also empty the
set of stored commands.
Command DES without parameters presents the current load. Other loads can be presented by the command
DES L load-name
Command EDIT functions analogically. However, EDIT without parameters simply enters the editor, and the
syntax * is available for designating the current load.
5.9 Listing data about a load

The listing possibilities are presented in more detail in the chapter about output, here only a short summary is
given. The following list options are relevant for loads:
LIST (no specification) a very short summary

LIST B/R/T list data for every bay, row or tier
LIST CLX/CLY/CLZ list data for lines
LIST ST list data for the physical stacks
LIST CLC list data for individual containers
LIST CT list data by container type
The current load is the default object for the LIST command.

(The only form of the LIST command not relevant for loads is LIST CTP, list data from the definition of container
types).
5.10 Variables related to the current load

When a container load is made current with command GET or NEW, the following variables are assigned:
CLLOAD name of the container load

CLARR name of the arrangement containing the load
CLTEXT description of the load (from TEXT command)
CLATEXT description of the arrangement
When using the LIST command, these variables are temporarily changed if needed, so that when used in table
output options, the correct values are obtained.
5.11 Adaptation to changed arrangement and types

When a container load is read from the data base, it is checked whether the arrangement it belongs to has
been changed since the load was stored. If here has been changes, the load is adapted as presented below.
In the data base, a container load is stored in a form telling what container is loaded in given positions, which are
expressed in the internal numbering. The basic principle is that positions keep their load a far as the positions
still exist in the arrangement. The same adaptation is made if a load is read into a different arrangement.
If the weight or center of gravity of container types have been changed, the load is changed accordingly, unless
these values have been given in the load definition. Note that container weights are recorded as absolute
weights, even if originally given as relative ones.
In order to give a fast indication of the changes involved, the total weight before and after the correction is
displayed.
5.12 Generating the lateral profile

Unless separately inhibited, the containers are added to the wind profile when calculating stability criteria for a
load case involving containers. For direct access to the profile of the container load, there is the command PRF:
PRF name bare-profile
where 'name' is the name of the resulting curve and 'bare-profile' is the name of a curve giving the profile
without containers. This command generates and optionally draws a curve representing the wind profile. If the
latter parameter is omitted, a curve containing the container profile only is generated.
In this function, containers in hold are disregarded. The possibility that there could be air below a container is
not taken into account. The lower limit of the distribution curve is supposed to disappear when the container
profile is merged with that of the ship.
The profile is stored as a space curve located in y=0. It can be drawn (under DR) with the PLOT command. If
the current projection is Y, the result of the PRF command is drawn automatically.
The area and center of gravity of the profile curve are listed as calculated for the part over the design water
line. Areas and centers of gravities can also be accessed with the calculator functions AREA and CGA, e.g. !
CALC AREA('PROF-CONT').
If the original profile contains one branch only, the contour of the containers is merged geometrically with the
profile, otherwise only a logical combination is made.

5.13 Connection to loading conditions (LD)

The following paragraphs describe the functions available under the main task of the loading conditions
subsystem (LD), related to handling of container loads in connection with loading cases.
A graphical tool for container loading is added in Loading Conditions Window, please see Container loading
GUI for more detailed information.
5.13.1 Adding a container load to a loading condition

A container load is added to a load condition with the MASS command:
MASS type load-name
'type' has the same function as otherwise in the MASS command, for providing the 'substance' in the form
of a name defined under PD (purpose definitions) in SM. The physical type associated with the substance
must be defined as 'container', represented by symbol C. For example, the following purpose definition can
be given under PD:
DEF CONT 'containers' TYPE=C
where a substance named CONT is defined, the description of which is 'containers'.
Using the substance defined above, an example of adding a container load is given by
MASS CONT IN-HOLD.L1
The parameters defined for the substance, for example, the description, ('containers' in the example), have
their usual function. The container load name will be stored as the formal location of the mass load, while a
possible description associated with the container arrangement is used in the place of the room description.
It is possible to load several container loads into the same load case. There is no check that they form a
reasonable combination, but this should not be needed in the cases where this possibility is likely to be useful,
for instance in adding containers on deck and containers in hold independently.
Removing a container load is done with command DELETE, for example:
DELETE IN-HOLD.L1
5.13.2 Changing a container load directly under LD

Some of the basic services of CL are available directly under LD. These services include container loading
commands, some administrative functions and listing functions.
Because of conflicts with other commands under LD, the loading commands are named AC (ADD) and RC
(RED). As under CL, these commands operate on the current container load, and changes must be stored
separately in the data base. Selecting the current load and storing it in the data base can be done manually
or automatically.
A container load that has been added to a load case with same name is treated as belonging to that load case.
This means that the container load is automatically made current when getting the loading condition and will
be automatically stored when writing the loading condition to the data base. A single container load named this
way makes the containers in practice integrated with the loading condition, and no additional administrative
commands are needed. This does not prevent the container load to be treated independently or added to other
load cases. Note: a rename or delete of the load case does not affect the container load.
In other cases, these operations must be done manually, either under CL (commands GET, SAVE, REPLACE)
or directly under LD using command CLA.
Command CLA (container load administration), allows the following functions to be done directly under LD:
■ inquire the current container load

■ create a new load

■ change the current load
■ replace the current load in the data base
Plot options set under CL work under LD also, including option AUTO.
The following figure illustrates the management of container loads under LD.
Example of container loading under LD

The left route uses the CLA command for handling the whole operation under LD while the right one creates
the container load independently.
5.13.3 Listing container data under LD

The LIST functions of CL are described in the next chapter. They are available directly under LD by adding
the keyword CL:
LIST CL <CL-list parameters>
where the parameters after the keyword CL are the same as under CL (see !EXPL LIST/CL2).
The list alternatives B, R, T and CT can be used without the CL keyword.
When an object is given, the list command works as under CL. When no object is given, the current load case
is searched for container loads, and the listing is done for the total load. When combining the loads, warnings
are obtained for multiply loaded locations. The check does not cover multiply defined stacks. The listing obeys
commands LQ and TOO, but the commands can be given under CL only.
5.13.4 Plotting under LD

The drawing functions of CL are presented in an own chapter. They can be used directly under LD by adding
the keyword CL:
PLOT CL <cl-parameters>
DRW CL <cl-parameters>

where <cl-parameters> are the same as would be given under CL. When no object is given the current loading
condition is searched for container loads.
5.13.5 Entering container loading from the LOAD task

With the exception of the commands presented above, any container operations must be done under the
container loading subtask. When returning to LD from CL, the current load case is updated taking into account
changes made under CL.
If there is an active load case when entering the container loading subtask, container arrangements (commands
BLOCK and COMBINE) cannot be redefined or created. Command SKIP (under LD) cancels the current load
case.
6 Drawing functions
This chapter presents the drawing functions for showing information about container arrangements or container
loads in graphic form. In addition to drawing the geometric shapes, there is a number of functions for adding data
about counts, weights etc. For adding other graphic components, the general drawing task can be accessed
without leaving the CL subtask.
6.1 Ways of drawing

Drawings can be made for the purpose of visualizing the containers or as the basis for showing information
on weights, container counts, container types and similar. This paragraph gives an overview of the drawing
alternatives and their usefulness for different purposes.
Containers can be drawn as plane sections or as projections of three dimensional objects, and these again in
orthogonal or general projections. Lastly there is the possibility to make schematic drawings that do not show
the real geometry.
The following figures illustrate the basic alternatives.
Perspective view of container block
The same block shown as orthogonal projection (unfilled) and section near the end (filled)
6.1.1 General projections

For visualizing a container arrangement or a container load, general parallel or perspective projections can be
used. This type of drawing is not available for presenting numerical information. However, there is the possibility
to use colouring for distinguishing containers of different types, weight or other properties.

The order of drawing is selected to get a hidden lines effect if filling is on. However, a completely reliable result
is not possible with this method. The plot option SRP (see below) may provide some help.
6.1.2 Orthogonal projections, real geometry

By default, drawing in an orthogonal projection is made according to the real geometry of the object, i.e. the
drawing attempts to show how the object in question looks like. In contrast to this, there are the drawing
modes presented in the next paragraph which are more oriented towards presenting numerical information in
connection with the graphics.
When drawing real geometry, every container is drawn individually. However, for better performance coinciding
container contours and containers completely hidden by another one are removed. Thus, every contour drawn
belongs to an identified container, and container specific information can be added by texts or colouring. It is
possible to add information regarding whole lines (e.g. container count) which will be added to any container
having the same bay/row/tier number as the line in question.
Sections are always drawn as real geometry.
6.1.3 Orthogonal projections, modified geometry

In order to add information regarding layers (bays, rows or tiers) or lines (given bay/row/tier combinations),
the real geometry may create the difficulty that there is no unique position where to write a given piece of
information. For this purpose, two special drawing modes are provided:
non-geometric
nominal
In the non-geometric mode, no attempt is made to show the actual geometry of the objects, instead internal
bay, row and tier numbers, multiplied by specified lengths, are used as coordinates.
The nominal mode is an intermediate between the real and nongeometric modes. The geometry is as far as
possible adapted to the real object but lines or layers are forced to be aligned. In the weaker nominal mode
(default), all containers in a given line in the viewing direction are given a common position, in the stronger
mode every layer (bay,row or tier) is forced to have a common position.
There is no sophisticated logic for deciding the nominal coordinates, but the first representative of each
argument will provide the position. The only way to influence this is to define the arrangement so that more
representative parts come first.
When adding numeric information at the borders of a plan, nominal coordinates are always used. These are
also returned by the calculator function CLINFO (quantities X, Y and Z).
Example. In the following example, the effect of the NOM option is emphasized by using a container load where
irregularities are introduced by both varying length and height and where the position of some stacks have
been modified.
The example in a perspective projection

The example in the y-projection, drawn as real geometry
The example in the y-projection, using the NOMINAL option

In all cases the plot options
PO FILL=CTP MI=ID ID=BB-TT
were used. In the last one the following options were added:
PO + TMI=CL-TEMPLATE2 MR=N MB=(N N-L) NOM
6.2 Drawing commands

The main command by which container arrangements are drawn is PLOT.
For controlling the drawing, the standard commands PROJECTION, SIZE, COLOUR, THICKNESS, FILL,
DASH, FONT and TCOL are available directly in the CL subtask. Under CL, a name given in command SIZE
(e.g. SIZE BLOCK1) is first checked for possible interpretation as container arrangement component. SIZE *
refers to the arrangement behind the current load.
Commands TRANSLATE, SCALE and WINDOW, available under task DR, also affect the result of the PLOT
command.
Various drawing options can be specified in the PLOT command. Options needed repeatedly and options
controlling automatic drawing of changed loads can be stored permanently with command PO (plot options).
Containers can also be drawn into an arrangement drawing created with the SETUP command. The DRW
command is used for this purpose.
6.3 The PLOT command

The PLOT command in task CL has the following form:
PLOT object SEL subset PO plot-options
'object' is the name of a container arrangement or container load, and defines what object to draw. If it is
omitted, the object defined under plot options is used, if any, else the current load.

The containers to be drawn can be restricted to a specified subset if needed. If no subset is given, the keyword
is also omitted. For historical reasons, some of the functionality of the subset facility is duplicated within the
plot options.
In contrast to listings, the subset specification does not influence the calculation of totals to be marked as
text in the drawing.
Plot options can be given directly in the PLOT command, either modifying or replacing the permanent options
given by command PO. The keyword PO or RO must be given as separator before the plot options. RO (replace
options) means that any permanent options are disregarded while PO means modifications to these. The
options are described in more detail in the next paragraph.
6.4 Command PO
Command PO (plot options) was primarily added in order to support automatic drawing when doing load
definitions, but it can be used whenever there are options one wants to use repeatedly.
The options given in the PO command will be used when drawing with PLOT or DRW. An option given in the
PLOT command overrides an option possibly given under PO. Note specially the parameter OFF, by which
single options can be cancelled.
In addition to the options presented in the next paragraph, there is the option AUTO, that turns on automatic
drawing of changed loads. The AUTO option also sets options LB and NL (see below) and if these are not
wanted, they must be turned off separately (i.e. NL=OFF or LB=OFF).
The object and intersection plane can also be given as permanent options, for instance PO NAME=BLOCK1
or PO X=12.
When entering the PO command, any previous options are cancelled unless the first parameter is +.
When the PO command is given without parameters, the currently valid options are displayed. Command PO
EDIT transfers the current plot options to the editor work area.
Plot options of permanent value can be stored in the data base, either the project data base or the system data
base. When fetching options, the project data base is checked first. The commands related to stored options are
PO SAVE name save in the project data base under the given name
PO SAVE name SYSDB save in the system data base (requires full professional mode)
PO GET name get options
PO UNSAVE name delete stored options
PO CAT catalog of stored options
6.5 The plot options

This paragraph gives an overview of the options. Part of these refer to functions that will be presented in more
detail in own paragraphs below.
Most options affect orthogonal projections only, and are ignored when drawing perspective drawings. The
following options are valid in all cases:
LB: add unloaded positions and draw them in a way that differs from the
loaded ones. If filling is used, unloaded ones are separated by removing
the filling, otherwise by setting dashed lines.

BAY=nr: restrict the drawing to the given bay or bay range (e.g. BAY=2...5). Options
ROW, TIER work similarly.
FILL=qnt: controls colour filling. All properties of individual containers can be uses
as basis for fill, e.g. FILL=CTP for colouring according to container type.
See command FST for controlling the colouring. A fixed filling is set by
command FILL.
PART=part: restrict the drawing to a specified part of a combined arrangement. For the
purpose of this option, see below.
CT=type: restricts the drawing to containers of the specified type.
ST: draw stacks only. Stacks are represented as boxes corresponding to their
extreme coordinates.
The following options are valid in orthogonal projections only.

The following options affect the drawing in general:
NG: set non-geometric mode. The associated dimensions can be given as

parameters: NG=(lx,ly,lz)
NOM: set the nominal mode. NOM=B gives the stronger form. See also option
XCC.
The following set adds information at the side of the drawing or controls the effect:
N: add bay, row or tier numbers at the sides. Equivalent with MB=N, ML=N.
C: adds coordinates at bay/row/tier limits. Equivalent with MB=C, ML=C.
TH=h: selects the text height (meters full scale)
HDP: position of headers from HMA, HMB, alternatives L,R,B
Options ML,MR,MB,MA,HML,HMR,HMB,HMA,PML,PMR,PMB,PMA,FML,FMR,FMB,FMA,FRA,HDP control

the writing of information at the sides of the plan, see separate paragraph.
The following options write information into the boxes or control the effect:
NR: mark number of container positions in the viewing direction. Equivalent

with MI=NR
NL: as NR, but marking the number of loaded positions.
BRT: mark the bay, row or tier number pair corresponding to the current
projection. Equivalent with MI=BRT.
BLN: mark the block name (same as MI=PART)
MCT: mark the container type as text (same as MI=CTP)
FIG=name: draw a figure into each one of the positions. The figure is drawn in addition
to the container contour unless option ONLY is added
FIG=CTP: as above, but making the figure dependent on the container type
CP: (container proportions) affects the drawing of figures so that the
proportions of the figure are adapted to the container
MI: (mark inside): draw information as text inside the container boxes, see
paragraph below. Options NR...MCT are special cases, retained for
historical reasons.
TMI: template for MI

THMI: text height for the result of option MI.

XCC: affects the result of MI as presented below
ID: template for the ID quantity
Option ONLY has the effect that the additional information only is written, not the container contours.
6.6 Plotting individual containers

In the drawings, a container is represented as a box according to the dimensions defined for the container type
in question or possibly modified by the NOMINAL or NG options. This paragraph describes the functions by
which the drawing of of the box can be modified or by which additional information can be added to it.
Filling is available for all projections, the other services are available in orthogonal projections only.
6.6.1 Selecting fill colour (FILL option)

Any quantity available for a container is also available as basis for colour filling. Filling is obtained by the plot
option
FILL=qnt
where 'qnt' is the symbol of the quantity, for example CTP=container type, W=weight.
The fill colours must be defined by a filling standard as created in the subtask FCD under SM. In general,
different quantities need different fill standards. However, the only necessary requirement is that a numeric
quantity is used with at fill standard having a numeric key while a character quantity needs a character key.
A special case is formed by FILL=CTP. If given, a fill standard is used as for the other quantities, otherwise the
filling defined as a container property in the type definitions is used (quantity FCODE or LFCODE).
The following examples illustrate fill standards. It is recalled that colour standards are defined as tables using
the normal commands of table calculation and accessed with command FCD under SM. The example illustrates
a colour standard defined for a character quantity, the property DH (on deck/in hold).
NEW COLOUR*DH
COLUMN DH
COLUMN FCODE
DH FCODE
------------
OD -3
IH -4

Negative numbers mean pure colours while positive numbers mean raster patterns. Containers on deck are
coloured with colour 3 (green) and those in hold 4 (blue). The colouring is activated by the commands
FST DH
PO FILL=DH
(It is not necessary that the tables are named as the key quantity.)
The second example illustrates a fill standard for a numeric quantity, the container weight.
NEW COLOUR*W
COLUMN W
COLUMN FCODE
W FCODE
------------
0 -29
1 -27
2 -25
5 -23
10 -21
20 -99
999 -99

Containers with weight between 0 and 1 will be coloured 29, between 1 and 2 with 27 etc. In the standard colour
maps delivered (CMAP*LARGE), the result is shades of red, with darker shades for larger weights. Weights
over 20 will be coloured black (99).
6.6.2 Using figures to represent containers (FIG option)

Normally, a container is represented as a rectangle in the drawings. With the FIG option, figures can be used
instead or in addition to it. The option
FIG=name
makes all containers represented by the given figure. The option
FIG=CTP
gives a figure dependent on the container type. The names of these figures must be stored as the quantity
FIG in the container type definition. It is possible to use different figures for different projections. These figures
must be named by adding .X, .Y or .Z to the name given in the table as in the example below. If there is no
projection specific figure, a figure without the suffix if looked for.
Example of figures defined for a container type
Example of the figures in use

The figures are scaled so that they fit into the container they represent and centered. With the option CP
(container proportions) breadth/length ratio the figure is adapted to that of the container (as drawn).
The figures can contain text fields. Unless a template has been given, these will be used when drawing texts
resulting from the MI option.
By default, the figure is drawn in addition to the normal container contour. With the option ONLY, the figure
only is drawn.
6.6.3 Adding text information inside containers (MI option)

Information in text form can be added inside the container contours by the option MI (mark inside). One or
several quantities can be given:
MI=qnt
MI=(qnt1,qnt2 ...)
where the normal symbols of the quantities are used.
The following quantities represent sums along the line with the same bay/row/tier numbers as the container:
NL: number of loaded containers

NR: total number of container positions
MASS: total weight of the loaded containers
XM,YM,ZM: center of gravity of the weight
VOLM: volume of the loaded containers
CGX,CGY,CGZ: center of gravity of the volume
All other quantities represent properties of the specific container shown. Note specially that W=weight of the
single container.
The options NL, NR and BRT are abbreviations for MI=NL, MI=NR and MI=BRT. BRT represents the relevant
combination of bay, row and tier.
A special service is provided for the quantity ID, which presents the bay/row/tier numbers as a single item. The
option ID defines a template for how to combine the numbers, where the components BB, RR and TT will be
replaced by the current bay, row or tier numbers. For example,
ID=BB-TT
shows the bay and tier, giving for instance 03-21.
The text positions can be controlled by giving a template with the TMI option. The definition of templates is
described in connection with definitions in general. If a figure has been used having text fields, these will be
used for controlling the text positions. As default, there are predefined positions covering up to three quantities.
The text height can be adjusted by the THMI=th option. When more than three quantities are be used a template
must be given defining enough text positions.
A template to be used as default can be defined under ADM.
The option to use no template is then TMI=NONE (TMI=OFF means no TMI option, i.e. the default).
When long and short containers are combined as presented in the next paragraph, the templates must be
modified.

6.6.4 Combining information for long and short containers

By default, every container is drawn individually. This concerns orthogonal projections also, with the exception
that containers covered by another one are omitted. If the MI (mark inside) option has been given, the texts
are drawn separately for each container. This is normally not useful when there are lines occupied partly by
long containers (two stacks loaded in combination) and partly by short containers. This paragraph presents
the principle by which data belonging to long containers are drawn in combination with data from the parts it
shares. This principle is used when the NOM (nominal) or NG (nongeometric) option have been given - in other
cases the drawing is done as presented for real geometry. The individual mode can be set with option XCC.
When a given line is partly loaded with long and partly with short containers, a single contour is drawn
representing the containers in that line and the parts. The long container provides the geometry for the
combination, while a dashed line in the middle marks the division into the two parts.
If the MI option has been given, the quantities asked for are written for the whole and for the halves separately,
totally three times the number of quantities given. These texts are placed according to the given template or
the default locations as presented above.
The different texts are placed in the following order:
the texts for the whole (1, 4,5)
the texts for the left part (2, 6,7)
the texts for the right part (3, 8,9)
The numbers to the right represent the indices resulting when the number of quantities is 1 or 2. These indices
control the usage of the text fields in the template. The text fields are used analogically with the normal case,
except that the number of fields is three times larger. The template should be designed for the proportions of
the long container type.
Example of combining data for long containers and its parts. (rightmost figure)
6.7 Adding text information at the sides of a plan

Information regarding numbering, container counts, weights and centers of gravity can be written in connection
with a container plan as text at the sides, concerning sums over the layers seen in the plan (e.g. bay and tiers
in a side view). Regarding the texts, there are options concerning headers, positions, formatting and addition
of frames. The basic options are ML,MR, MB and MA as presented below. The related options are named by
adding a letter in front of these symbols, e.g. HML for the header belonging to ML.
There is quite a number of degrees of freedom regarding contents and layout and many of these have been
made accessible in the form of options, making this function appear quite complicated. However, there are
defaults for all properties except for the selection of quantities.
6.7.1 Selecting the quantities

For writing information at the sides, options ML, MR, MB and MA are used, standing for 'mark at left', 'mark
at right', 'mark below' and 'mark above' respectively. This symbol is followed by one or several of the symbols
below, telling what quantities to draw:
N: bay, row or tier number

C: coordinate
NL: number of loaded position in the layer
MASS: total weight of the containers
XM,YM,ZM: center of gravity of the mass in the direction specified
CGX,CGY,CGZ: center of gravity of the volume in the direction specified
When several alternatives are given, they must be enclosed within parentheses. The order in which the
quantities are given determines the placement so that the first one given is drawn closest to the plan.
When there are both real and formal bays, the output is done so that by default, a number is written for each real
bay. If there are long containers sharing a bay, half of the containers is attributed to this bay. In container counts,
the container is counted in both halves. Other alternatives are available by modifying the quantity symbols:
xx-L: quantity xx summed over the long containers only

xx-S: quantity xx summed over the short containers only
Subset selections do not influence the totals.

Examples:
ML=N MB=N
Write bay, row or tier numbers to the left and below (same effect as with option N).
ML=(MASS N) MR=(N NL)
Assuming a side view: mark total weight (to the left) and number of containers loaded (to the right) for the tiers,
adding the tier number at both sides.
MB=(BAY, BAY-L) MA=(NL-S, NL-L)
Below the plan, bay numbers are written separately for the real and formal bays. Above the plan, the same
separation is done for the container counts.
Examples of text information in a plan
6.7.2 Formatting the texts

The numbers are drawn obeying the unit and format defined in the quantity standard (see command !FORM).
For numbers at the sides, the field length and a fixed number of decimals are used, while the numbers below
and above are drawn with dynamic format, where only the number of decimals is used (as upper limit).

6.7.3 Position control

The figure below shows the dimensions relevant when placing the texts:
Dimensions controlling the layout

The figure shows the texts corresponding to the MA (mark above) and MR (mark right) options. The texts
belonging to ML and MB are handled symmetrically using the same dimensions.
In the figure 'TEXT' represents the value of a quantity. The texts are placed within visible or imagined fields
(see the frame options). Above and below the plan, the height (h) of these fields can be adjusted, and at the
sides, the width (b). Above and below, the text height (th) can be changed, at the sides the location within the
field (d). The dimension d is the distance from the left side of the field to the start of the text (also for ML). In
both directions a margin (m) can be added. For use below in the description of the frame options, the lines
separating the fields are numbered 1...4.
In the absence of other specifications, the dimensions are selected as follows:
At the sides:
m (the margin): zero

th (the text height): from TH option, else 0.3 m
b (the field breadth): (n+2)*th, where n=the field length associated with the
quantity in question (see !FORM)
d (distance from field start): selected so that the text is centered assuming
character width=character height
the whole field (according to !FORM) is centered.
Above and below:
m (the margin): zero, except when HML or HMR options are given in which
case space is reserved above the plan
h (field height) 1.8*th (text height as above)
th (the text height): h/1.8
These defaults are also used for any dimension assigned zero in Pxx option.

These dimensions can be modified by options PML, PMR, PMB and PMA. For PML and PMR the parameters
are
Pxx=(m,b1,d1,b2,d2,...)
and for the PMA and PMB options
Pxx=(m,h1,th1,h2,th2,...)
The indices 1, 2, ... refer to the text fields as counted from the plan outwards. These dimensions can be given
far as needed - missing ones are assigned default values while additional ones are ignored.
Illustration of the position options (the dashed lines do not belong to the output of PLOT)
6.7.4 Adding headers

For adding header texts identifying the quantities, the options HML, HMR, HMB and HMA are provided, referring
to the texts added by the corresponding ML, MR, MB or MA option. If no parameter is attached to the option,
the same symbols by which the quantity is selected are used as headers. Other headers can be specified as
parameters to the option. Thus, the following pairs are equivalent:
ML=(MASS,NL) HDL
ML=(MASS,NL) HDL=(MASS,NL)
Headers belonging to texts at the sides of the plan are written above the numbers while headers belonging
to texts above or below the plan are written to the left and/or to the right. Whether texts from HMA and HMB
are written to the left or right is decided taking into account the space created by the options ML and MR. The
decision can be done explicitly with the option HDP (header position):
HDP=L add the headers at the left side

HDP=R add the headers at the right side
HDP=B add the headers at both sides
6.7.5 Adding frames

The text information can be accompanied by vertical and horizontal lines for improving the visual appearance.
A default set of lines is obtained with option FRAMES. This set includes a lines surrounding the whole plan
and lines separating the text part from the containers. If filling is not set, the lines are drawn dashed in order to
distinguish them from the container contours, otherwise, the lines are drawn solid.

For more control, the options FML, FMR, FMB and FMA are provided, concerning lines in connection with the
texts from ML, MR, MB and MA respectively. With these options, the addition or properties of the individual
frames can be controlled independently of the FRAMES options.
The parameter to the FML ...FMA options is a string containing a letter for each (potential) line concerned:
N: no line
L: solid line of the current thickness
D: dashed line
T: solid line, thicker line
The first letter concerns the line directly attached to the plan. The second letter concerns the line at the given
margin from the plan (even if the margin is zero). The remaining letters follow the order in which the quantities
are given.
The FRAMES option can also have the same parameter. This parameter is applied for all partial frames having
no own specification.
Plan with frames
6.8 The NG option (non-geometric)

Option NG sets 'nongeometric mode' on. In this mode, the actual locations of the containers are ignored, and
replaced by multiples of the bay, row and tier numbers. The length units are by default 2 m in the transversal
and vertical directions and 3 m in the length direction. These dimensions can be changed by adding them as
parameters to the NG option, for example
NG=(4,2,2.5)
for setting the lengths to 4 (x), 2 (y) and 2.5 (z). In the nongeometric mode, a possible intersection plane
is ignored, but a selection in the form SEL X=50 can be made. Whether to show horizontal, longitudinal or
transversal views is decided the normal way with PROJECTION, while SIZE is used for scaling. Thus, drawing in
nongeometric mode is otherwise almost identical with other ways of drawing orthogonal projections, especially
if the length units are close to the actual container dimensions. If the NG option is valid when the SIZE *
command is given (scaling according to the current object), the result takes into account this option.
If the bay numbering if from forward aft, the x-coordinates are selected so that bay 0 (in the internal numbering)
is at LREF.

Transverse section in non-geometric mode

The dashed lines in the figure mark positions in the internal numbering that are not in use in the current section.
6.9 The PART option

The PART option restricts the drawing of a combined arrangement to a given part:
PART=name
where 'name' is the name of arrangement representing the part.
It has been added in order to give more possibilities to handle layout problems that may arise when drawing
complicated arrangements. For bare arrangements it is simpler to draw the parts directly, but this is not possible
if one wants to mark properties belonging to a load, e.g. container counts of the whole load. When the PART
option is given, the nominal coordinates are determined for the part separately and each part has its own texts
at the sides.
The following example shows a typical case where the PART option can be used. When marking row numbers,
the positions will be selected according to the lower parts, if done for the whole arrangement. By drawing the
upper and lower parts separately, a better result can be obtained.

Example of usage of the PART option
6.10 Controlling the drawing order for hidden lines effect

When drawing containers in general projections with filling, the containers are sorted according to distance in
order to produce a hidden lines effect. As a method, this is not adequate and may fail occasionally, especially
when there are long and short containers mixed.
By default, the basis for sorting is the distance to the center. In a given case, the result may be better if another
reference point is used, and therefore the option SRP (sorting reference point) is provided:
SRP=xyz
where x=reference point in the x direction, either
L=lower limit
C=center
U=upper limit
and similarly for y and z. Thus, the default corresponds to
SRP=CCC
while
SRP=LUU
selects the corner with lower x, upper y and upper z.
A special case is formed by
SRP=N
which controls the drawing order according to the numbering.
6.11 Drawing into the SETUP

If an arrangement drawing has been created with the SETUP command, container data can be drawn into the
setup with the DRW command:
DRW i1,i2 ...
Except for the parameters i1,i2, the parameters are the same as in the PLOT command. The parameters i1,i2
are optional, and restrict the drawing to parts i1...i2 of the setup. i2 can be omitted if it is the same as i1.

The container drawing functions are not implemented for sections with surfaces or varying section coordinates,
for which an average coordinate is selected. Thus, the setup should be done with normal plane sections. All
drawing into the setup is done as sections, except for the profile (y=0), which is drawn as a projection. In order
to get a section, Y=0.02 can be used.
Note carefully: the DRW command under container loading is not identical with the general one - it differs
from the DRW command under DR exactly as the PLOT command does. Therefore, any of the standard DRW
functions must be used under DR except for DRW ALL.
For each part in the setup, the section plane is set accordingly. Thus, note the difference between
SET n; PLOT ...
DRW n ...
Both draw into the n:th part of the setup, but DRW sets the section plane as specified for that part, while the SET
n; command simply sets the position and projection according to the part in question, and PLOT works as usual.
Outside the CL task, container arrangements and container loads can be drawn into a setup by adding the
keyword CL as presented below.
6.12 The general drawing functions

The full range of drawing commands can be accessed by entering the drawing task with command DR. Note
that in this context, a name given in the PLOT command is interpreted as that of a geometric object.
Return from the drawing task can be done with command CL. The same commands that in the normal
DRAW task lead to the definition environment, now lead back to the container loading subtask. Some of these
commands (e.g. DES) are defined in this context (with their own meaning) while others (e.g. CURVE) are
unknown.
For drawing of container objects outside the CL task, the general drawing commands PLOT and DRW can be
used by adding the keyword CL:
PLOT CL cl-parameters
DRW CL cl-parameters
where 'cl-parameters' mean any parameters of the PLOT command of CL. Outside CL, there is not default for
the object which must be given in the command. Plot options given under CL will be used unless overridden
by options given directly in the command. (Note option RO for completely ignoring any predefined options).
6.13 Drawing during block definition

In the subtask started by command BLOCK, the block being defined can be displayed graphically. This is done
with the same PLOT command as under the main task of container loading, with the difference that the default
object is the block being defined. Plot options set outside remain valid but options set under BLOCK are used
in the subtask only. Commands PROJECTION, SIZE, FILL and COLOUR are available.
The logic related to plotting loads is borrowed for separating positions in the initial blocks from those removed
by REDUCT. Positions remaining after REDUCT are plotted as loaded, while the initial block is treated as the
bare arrangement. Thus, option LB will show both categories but separated by the way of drawing.
6.14 Additional drawing examples

The following examples illustrate some possibilities offered by the drawing functions.

6.14.1 Example 1 - arrangement plan

The following example shows the container arrangement presented in an arrangement plan.
NEW ALL.L; ADD * * *
DRAW CL-ARRANGEMENT
SET PROFILE, (BAY9, BAY7, BAY5, BAY3, BAY1),
(BAY19 BAY17, BAY15, BAY13, BAY11)
DRW ALL @@ draw the geometry
FONT HW7; FILL=#5
DRW @@ draw the containers
DRW 1 PO MA=N TH=0.9 ONLY
@@ bay numbers in the profile (part 1)
DR; DRW ID; END @@ plan names
The x-plans used in the setup are defined according to the following model:
PLAN, BAY1, X=#107; IDENT 'Bay 1'
Showing the container arrangement in a plan
6.14.2 Example 2 - not involving containers

This example illustrates the FIG option, and at the same time, usage of container loading functions for other
purposes than containers. In the example, a car deck is divided into car positions by the following definition:
BLOCK CARDECK CAR
X 20.5 20; Y 0 5; Z 2.3 1
REDUCT Y>HULL -0.5; SYM
The drawing is made by the commands
PLOT CARDECK FIG=CAR ONLY
DR
PLOT HULL/Z=2.3
PLOT HULL/Z=4.8

6.14.3 Example 3 - checking visibililty

The following example shows a check of the visibility from the bridge. In order to have something to look at,
an island with a lighthouse is defined by boxes.
From the side, the situation looks like this:
and from the bridge:
When drawing perspective drawings, one should avoid objects close to the viewer, since their images approach
infinity. The same applies to the coordinates given in a SIZE command. In this case, the nearest containers
are omitted by giving a bay number range. The drawing is made by the following commands:
DR * (assuming initial environment CL)
DRAWING SIGHT
PROJECTION (22 0 25) (203 2 13)
** location of viewer, point looked at (lighthouse in this case)
SIZE 50 212.00 -32.00 32.00 -15.00 32.50
FILL WH; PLO LIGHTHOUSE O;
FILL RED; PLO LIGHTHOUSE2 O
CL ** return to CL subtask
GET SIGHTDEMO.L1 ** get container load
FILL #66
PLO SIGHTDEMO.L1 PO BAY=3...16 TIER=4...9
The container arrangement example in paragraph 'Parts of a container arrangement' is drawn with the following
data:
DR
DRAWING CONT-ARR
PROJECTION -51 21
SIZE *S
CL; FILL #15; PLOT ON-DECK
DR; PLOT MDECK3; PLOT BHC3

CL; FILL 9; PLOT IN-HOLD PO BAY=13...20

DR; FILL #68; PLOT BHC2
DR; FILL #68; PLOT BHC1
7 Output functions
This chapter presents the functions for output of container data in numerical form, while drawing functions are
presented separately.
7.1 General basis

The object of listing can be a container arrangement or a container load.
The main output functions are based on the possibility to extract selected data as function of the following
arguments:
■ single container
■ line
■ stack
■ physical
■ logical
■ transversal line
■ longitudinal line
■ layer
■ row
■ tier
■ container type
Any quantity available (see list in chapter 1), including own additions can be output for single containers. The
other alternatives represent totals within a subset, and for these, the following quantities are available:
NR: number of positions (loaded + empty ones)

NL: number of loaded containers
MASS: total weight of loaded containers
XM,YM,ZM: center of gravity of the mass
VOLM: volume of the loaded containers
CGX,CGY,CGZ: center of gravity of the volume
XMIN...ZMAX: extension of the given set
The possibility to load one container over two positions and to extend a stack over the nominal capacity causes
the definition of the quantity NR (number of positions) to be ill defined.
For physical stacks, a number of additional quantities are available:
STAT: status code for loading errors

WSTMAX: maximum container weight
BAY,ROW: bay, row

T1,T2: tier range

CTP,CT2: default container types
PART: arrangement the stack belongs to
REFX,REFY,REFZ: location of alignment point (absolute)
LXAL,LYAL,LZAL: location of alignment point (local)
For expressing the argument, bay, row and tier numbers are available. In addition, the quantity ID can be used:
Cbbrrtt: single container

Lbbtt: line (transversal)
Xbbrr: line (longitudinal)
Ibbrr or Obbrr: stack (physical)
Sbbrr: stack (logical)
BAYbb: bay
ROWrr: row
TIERtt: tier
where bb, rr and tt represent bay, row and tier numbers with two digits.
The general subset facility (see 4.5 Defining arbitrary subsets) can be used for restricting the listing according
to various criteria:
■ bay/row/tier range
■ special options (in hold, loaded, container type)
■ location
■ quantity selection
A subset concerns the whole operation, including the generation of totals.
Regarding the quantity selection: note that a criterion involving bays, rows or tiers influences the calculation
only, not the selection of arguments, while the range syntax will also restrict the arguments.
In addition to the main listing commands, there is the command INFO for presenting general characteristics
about arrangement parts and LIST CTP for listing data about container types.
In the listing examples below, the following load is used:

Example load
7.2 Listing commands

The main listing commands obey the following general syntax:
LIST list object SEL subset TOO
table-output-options
where
list: list type as described below. It may be followed by type specific options
object: object of listing, either arrangement or load, default=the current load.
subset: restricting containers to the given subset, expressed with the general
selection syntax. If the subset is not given, the keyword SEL is also
omitted.
table-output-options: standard table output options. If no table output options are given, the
keyword TOO is also omitted.
The listings obey the LQ and TOO commands.

The following table gives an overview of the main listing functions, which will be presented in more detail below.
Overview of listing functions
Argument Select quantities Table output options Start output with
command
container LQ CLC TOO CLC LIS CLC
line LQ CLL TOO CLL LIS CLX LIS CLY LIS
CLZ
stack LQ CLS TOO CLS LIS ST
layer LQ CLB TOO CLB LIS B LIS R LIS T
container type LQ CT TOO CT LIS CT
7.3 Listing by container

LIST CLC This list has the type CLC and subject CLC, i.e. the relevant commands are

TOO CLC ...

LQ CLC ...
LIST CLC ...
This list, as the next one, implements in list form the basic function of collecting data for individual containers
or various subsets. The main use of this function is expected to be transfer of data to table calculation rather
than listing directly. Note however that the table output options make it possible to use this list type in a variety
of ways. The following example shows how to make a list grouped according to weights.
LQ CLC ID(WEIGHT)/'FMT(W,1,4)', MASS XM YM ZM (W)
LIST CLC TOO HD=(S,UL) GROUP=ID SUBT=ONLY TOT
WEIGHT MASS XM YM ZM
--------------------------------------
15.0 810.0 35.30 0.00 5.70
20.0 520.0 38.99 0.05 11.57
28.0 28.0 62.84 -1.28 2.26
--------------------------------------
TOTAL 1358.0 37.28 -0.01 7.88
The container weight is converted to a character quantity (ID borrowed for the purpose) in order to serve as
the grouping criterion.
The quantity W is the weight of the container, which has a value even if the container is not loaded, while
MASS is zero for unloaded positions and equal to W for loaded ones.
7.4 Listing by line

The list by line contains one line of output for one line of containers. The list type is either
CLX longitudinal lines
CLY transversal lines
CLZ stacks (logical)
The listing is controlled by a common LQ and TOO with subject CLL (L for lines). In the LQ, the quantity BRT
is available and will be replaced by the relevant combination of bay, row and tier, depending on the list type.
Each line of containers is presented on an own line of output. In order to obtain a two-argument listing of lines,
the special options related to LIST B/R/T must be used.
The special questions related to the bay argument are handled in the same way as for LIST B/R/T (options
SO, LO and H).
The option L, e.g.
LIST CLY L LOAD1
restricts the listing to loaded lines only.
In the following example, the listing is restricted to the two lowest tiers for shortness:
LQ CLL, BRT, NL, MASS
TOO CLL, HD=(S, UL), TOT
LIST CLX SEL (* * 2...4)

ROW TIER NL MASS

---------------------------
4 2 4 60.0
4 4 4 60.0
2 2 5 88.0
2 4 4 60.0
0 2 0 0.0
0 4 0 0.0
1 2 5 80.0
1 4 4 60.0
3 2 4 60.0
3 4 4 60.0
---------------------------
34 528.0
7.5 Listing by stack

Command LIST ST gives a list by stacks. This list is similar with LIST CLZ, but instead of logical stacks (same
bay and row), physical stacks are listed.
It has an own LQ with subject=CLS, containing a few additional quantities with respect to CLZ:
T1: lowest tier

TN: highest tier
WSTMAX: maximum stack weight
STAT: error status
CTP: container type on which the stack is based
CT2: alternative (long) container type
REFX,REFY,REFZ: location of the alignment point (in space)
LXAL,LYAL,LZAL: location of the alignment point (local, measured from lower limit)
PART: name of arrangement part
The error status contains in a compressed form information about loading errors in the stack. For the symbols
used, see checking of loads (command CHECK CODES; gives a list).
Subset selections affect the selection of stacks only - not the selection of containers inside the stacks. The
criteria are tested for the first container in the stack.
The arguments are always the real bays and long containers are always distributed over the halves (see option
H for LIST B).
Example:
LQ CLS, BAY, ROW, ' ', PART, NR, MASS
TOO CLS, HD=(S, UL), TOT
LIS ST SEL (3...5 * *)
BAY ROW PART NR MASS

-------------------------------------

5 1 HOLD1 3 0.0
3 1 HOLD1 3 0.0
5 3 HOLD1 3 0.0
3 3 HOLD1 2 0.0
5 2 HOLD1 3 14.0
3 2 HOLD1 3 14.0
5 4 HOLD1 3 0.0
3 4 HOLD1 2 0.0
5 0 DECK2 2 10.0
3 0 DECK2 2 10.0
5 1 DECK2 2 10.0
3 1 DECK2 2 10.0
5 3 DECK2 2 10.0
3 3 DECK2 2 10.0
5 2 DECK2 2 10.0
3 2 DECK2 2 10.0
5 4 DECK2 2 10.0
3 4 DECK2 2 10.0
-------------------------------------
42 124.0
7.6 Listing by layer

Listing by layer
The listing by layer has the list types
B: by bays
R: by rows
T: by tiers
These lists are controlled by a common LQ and TOO with subject CLB. This is the default subject (need not be
given in the LQ and TOO commands). Among the available quantities, the quantity BRT stands for bay, row
or tier number, and is at output changed to the current argument.
By default, bays are listed for formal and real bays separately. This can be changed by the following options:
SO (short only) list real bays only (includes independent bays)

LO (long only) list formal bays only
H: (halves) use real bays as argument, but add formal bays distributed over
the two halves
Option L restricts the output so that completely unloaded arguments are omitted.
Examples:
LQ BRT NL MASS XM YM ZM
TOO HD=(S,UL) TOTAL
Basic case (no options), showing all bays:
LIST B
BAY NL MASS XM YM ZM

----------------------------------------
1 0 0.0 0.00 0.00 0.00
3 0 0.0 0.00 0.00 0.00
4 6 128.0 63.00 -0.28 9.01
5 0 0.0 0.00 0.00 0.00
7 8 120.0 53.31 0.00 3.71
8 5 100.0 50.75 0.00 10.90
9 12 180.0 47.21 0.00 4.70
11 0 0.0 0.00 0.00 0.00
13 5 75.0 38.52 0.00 10.90
14 6 120.0 35.53 0.21 11.63
15 5 75.0 32.42 0.00 10.90
17 12 180.0 26.33 0.00 4.70
18 10 200.0 23.17 0.00 12.20
19 12 180.0 20.23 0.00 4.70
----------------------------------------
81 1358.0 37.28 -0.01 7.88
Showing formal bays (=long containers) only:

LIS B LO
----------------------------------------
1 0 0.0 0.00 0.00 0.00
4 6 128.0 63.00 -0.28 9.01
8 5 100.0 50.75 0.00 10.90
11 0 0.0 0.00 0.00 0.00
14 6 120.0 35.53 0.21 11.63
18 10 200.0 23.17 0.00 12.20
----------------------------------------
27 548.0 40.21 -0.02 11.09
Showing real bays only:

LIST B SO
----------------------------------------
1 0 0.0 0.00 0.00 0.00
3 0 0.0 0.00 0.00 0.00
5 0 0.0 0.00 0.00 0.00
7 8 120.0 53.31 0.00 3.71
9 12 180.0 47.21 0.00 4.70
11 0 0.0 0.00 0.00 0.00
13 5 75.0 38.52 0.00 10.90
15 5 75.0 32.42 0.00 10.90
17 12 180.0 26.33 0.00 4.70
19 12 180.0 20.23 0.00 4.70
----------------------------------------
54 810.0 35.30 0.00 5.70

By adding the corresponding symbol (B, R or T) as qualifier in the quantity selection, it is possible to list a given
quantity as a function of two arguments, where the values are sums over the third direction. For example, if
the basic list is by bay (LIST B ...), the qualifier R, e.g. NL/R, makes the quantity listed for each bay and row,
i.e. by stacks.
When defining headers in the TOO command, a quantity to be expanded is treated as a single item although
it will give rise to several columns. The special symbol O (owner numbers) will be replaced by the numbers
corresponding to the added argument.
The following example shows the quantity NL listed as totals/bay (as above) and separately for each bay/tier:
TOO HD=((- ' Containers loaded/tier'), ('Bay', 'Total' O 'Weight')), UL, TOTAL
LQ BRT, NL, NL/T, MASS
LIST B
Containers loaded/tier
Bay Total 2 4 6 82 84 Weight
--------------------------------------------------------
1 0 0 0 0 0 0 0.0
3 0 0 0 0 0 0 0.0
4 6 1 0 0 5 0 128.0
5 0 0 0 0 0 0 0.0
7 8 4 4 0 0 0 120.0
8 5 0 0 0 5 0 100.0
9 12 4 4 4 0 0 180.0
11 0 0 0 0 0 0 0.0
13 5 0 0 0 5 0 75.0
14 6 1 0 0 0 5 120.0
15 5 0 0 0 5 0 75.0
17 12 4 4 4 0 0 180.0
18 10 0 0 0 5 5 200.0
19 12 4 4 4 0 0 180.0
--------------------------------------------------------
81 18 16 12 25 10 1358.0
Note the header component O in the second header line, giving the tier numbers 2,4 ... 84.
7.7 Listing by container type

The list type CT lists the container load as function of the container type The listing can be controlled by
commands LQ CT and TOO CT.
Example:
LQ CT CTP W NL MASS
TOO CT HD=(S, UL) TOTAL
CTP W NL MASS
-----------------------------
D20N 15.0 46 690.0
D40N 20.0 25 500.0
D20H 15.0 8 120.0

D40H 20.0 2 48.0

-----------------------------
TOTAL 70.0 81 1358.0
The available quantities include both properties of the load and properties of the container type. In the
example above, W is the standard weight defined for the container type while MASS is the total weight
loaded.
7.8 Transfer of data to table calculation

For purposes where the normal listing options are not enough, or when data about containers have to be
transferred to other functions, table calculation is available.
For transferring data to a table, the listing functions presented above can be used by adding the table output
option TABLE. As a shortcut, the TAB command can be used directly:
TAB type object SEL subset
The parameters of the command are the same as in the LIST command. The columns of the table are
generated according to the LQ of the corresponding list concerned. However, only directly calculated columns
are available - not columns generated by formulas.
As a result, table calculation is entered with a table named TABLE being current, containing the data selected.
7.9 Auxiliary listing functions

The following listing functions are mainly intended for assistance when working with the system.
7.9.1 The bare LIST command

The LIST command without other parameters than possibly the name of the object gives a very short summary,
telling capacity and actual load in terms of weight and numbers of containers.
7.9.2 Listing data for arrangements (INFO command)

Command INFO gives data about arrangements as a whole, in a similar manner as the INFO command of
geometry definitions gives data about geometric objects.
The objects to be listed are given as arguments in the command, and an asterisk has its usual function of
including the parts (in this case the blocks of a combined arrangement). The result can be controlled by
commands LQ and TOO. The subject identifier CL must be included - the default subject is CLB.
The available quantities include:
■ geometric extent: extreme coordinates in all directions
■ 'numeric' extent: bay, row and tier range covered
■ number of container positions: this can be obtained for containers on deck or in hold separately
■ volume and center of gravity
■ type and dimensions of container
Example of listing with command INFO:
Quantity selection STD, (=the default), giving extreme coordinates and index ranges:
NAME XMIN XMAX YMIN YMAX ZMIN ZMAX B1 BN R1 RN T1

M M M M M M
ARR1 3.00 32.40 -9.60 9.60 1.40 16.50 1 7 -4 4 1
BLOCK1 3.00 32.40 -9.60 9.60 1.40 9.80 1 7 -4 4 1
BLOCK2 7.00 32.20 -7.70 7.70 10.20 16.50 2 7 -3 3 6
Quantity selection CAP, (LQ CL CAP), giving capacity in terms of container counts and volumes:
NAME CT NR IH OD VOLM CGX CGY CGZ

M3 M M M
ARR1 C1 272 146 126 5277.9 20.37 0.00 9.52
BLOCK1 C1 146 146 0 2833.0 21.04 0.00 6.22
BLOCK2 C1 126 0 126 2444.9 19.60 0.00 13.35
7.9.3 Listing data from container type definitions

The command LIST-CTP lists data from the container type definitions. The same information could by obtained
by entering table calculation (command CNTT), but this list option is provided for convenience. The list is
controlled by LQ CTP and TOO CTP.
7.9.4 LIST .id

The standard facility for creating own list functions by macros is available. With command
LIST .id
a macro named LISTCL.id is started.
7.10 Accessing container data in macros
7.10.1 Variables maintained

The identification of the current container components are available in the following variables:
CLARR: current arrangement

CLATEXT: descriptive text of the arrangement
CLLOAD: the current container load
CLTEXT: descriptive text of the current container load
7.10.2 Calculator function CLINFO

Information about containers or container loads can be obtained with the calculator function CLINFO.
The general form of the function call is:
!CALC CLINFO(name,quantity,arr,arr2)
'name' tells the given load or arrangement, and 'quantity' the information required. 'arr' is an array needed for
receiving the result of those functions returning many values, otherwise the result is returned as the function
value. 'arr2' is used as option for quantities X, Y and Z. The arrays must be created before the call by the ARR
function, for example
BAY=ARR(1) (array of integers)

XX=ARR(2) (array of reals)
The alternatives for 'quantity' are:
NL: number of containers loaded

NR: number of container positions
MASS: weight of load
XM,YM,ZM: center of gravity. The results are returned as the function value.
LIM: returns in 'arr' the limiting coordinates in the order
xmin,xmax,ymin,ymax,zmin,zmax.
NI: (numbering info) returns in 'arr' the limits as owner numbers in the order
B1,BN,R1,RN,T1,TN
BAYS: returns in 'arr' a list of all bays in the given object. The function value gives
the number.
ROWS: analogically for rows
TIERS: analogically for tiers
X: x-coordinates of bays
Y: y-coordinates of rows
Z: z-coordinates of tiers
The coordinates X, Y and Z are generated in the same way as the coordinates used by the nominal mode in
plotting. When 'arr2' is given the lower and upper coordinates are returned separately in 'arr' and 'arr2', while
the midpoint is given when 'arr' is the only receiver. Examples:
■ @CLINFO('LOAD1','MASS')
return the total weight loaded
■ @LIMITS=ARR(2)
array of numbers (2=reals, note)
■ @CLINFO('ARR1','LIM',LIMITS)
store the extension in array LIMITS
■ @RANGES=ARR(1)
array of numbers (1=integers, note)
■ @CLINFO('ARR1','NI',RANGES)
store the bay/row/tier range in array RANGES
@BAYS=ARR(1)
@CLINFO('ARR1','BAYS',BAYS)
The typical use of the last alternative is in a macro such as the following one, plotting each row separately:
@ROW=ARR(1)
@NROWS=CLINFO('ARR1','ROWS',ROWS)
@FOR I=1,NROWS
PLOT ARR1 PO ROW=@ROWS(I)
TEXT 'Row=@ROW' 0 -2
TRANSLATE 0 25
@NEXT
A special case of the function returns a list of bays, rows or tiers, as defined in the owner numbering system:
CLINFO('ON','X',arr)
CLINFO('ON','Y',arr)

CLINFO('ON','Z',arr)
As a result, the owner numbers is the given direction are stored in the given array and the size of the array
is returned as the function value. The purpose of this service is to make it easier to write macros that need
the sequence of consecutive layers.
7.10.3 Using the table calculation connection

More complex sets of data can be generated as tables, which then can be used as source for macros. The
basic functionality is provided by the listing functions as presented above. With the TAB command, the result
is without listing generated as a table after which control is transferred to table calculation.
In order to simply create a table, the table output option TABLE can be used. The table itself can be accessed
with the calculator function DB, while columns are accessed with the REC function.
The following macros show simple examples of extracting information via the table form. The first one answers
the question how many containers of a given type there are in given load.
@@ Demo macro 1, inquire number of containers of a given type
@LOAD=.... name of container load
@TYPE=.... container type
LQ CT CTP NL
LIST CT @LOAD TOO TABLE=ONLY
@TAB=DB('TAB*TABLE')
@TREC=REC(TAB,'CTP')
@NREC=REC(TAB,'NL')
@I=LOCS(TREC,TYPE)
@IF I=0 THEN
TYPE No containers of type @TYPE
@ELSE
TYPE @NREC(I) containers of type @TYPE
@ENDIF
@@ end of macro
The second macro answers the question what is the weight and type of a given container.
@@ Demo macro 2, inquire weight and type of the
@@ container at the position given by bay, row and tier
@LOAD=.... name of the container load
@BAY=... bay number
@ROW=... row number
@TIER=... tier number
LQ CLC ID CTP MASS
LIST CLC @LOAD SEL A TOO TABLE=ONLY
@TAB=DB('TAB*TABLE')
@IDREC=REC(TAB,'ID')
@TREC=REC(TAB,'CTP')
@MREC=REC(TAB,'MASS')
@@ combine bay, row, tier to the container ID
@ID=CNC('C',SBS(FMT((1000000+10000*BAY+100*ROW+TIER)),2,7))
@I=LOCS(IDREC,ID)
@IF I=0 THEN
TYPE No such location
@ELSEIF 0=MASS(I) THEN
TYPE The location is not loaded
@ELSE
TYPE The location is loaded by
type=@TREC(I), weight=@MREC(I)

@ENDIF
@@ end of macro
The default in LIST CLC is to list loaded locations only and the subset selection SEL A gives all locations, also
the unloaded ones. In the example, this is added in order to be able to make the distinction between the first
and second answer.
8 Command specifications
8.1 Commands on the main level

The following commands are available directly in the subtask CL.
8.1.1 Definitions related to containers
8.1.2 Output functions
8.1.3 Defining container loads
8.1.4 Various functions
8.2 Commands in subtask BLOCK
8.3 Commands under ADM

Book PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Book PDF

Hochgeladen von

Copyright:

Verfügbare Formate

NAPA Online Manuals 2011.

© 1992-2011 Napa Ltd. All rights reserved.

3 Defining container arrangements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

© 1992-2011 Napa Ltd. All rights reserved.

4.2.6 Criterion for accepting differing container dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

© 1992-2011 Napa Ltd. All rights reserved.

6.6.4 Combining information for long and short containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

© 1992-2011 Napa Ltd. All rights reserved.

1.1 Overview of functions

1.2 Connection to other subsystems

© 1992-2011 Napa Ltd. All rights reserved.

Installation of container loading

1.4 Handling container loads under loading conditions (LD)

1.5 Steps involved

© 1992-2011 Napa Ltd. All rights reserved.

2.1 Basic concepts

2.2 Parts of a container arrangement

Bay, row, tier and stack

© 1992-2011 Napa Ltd. All rights reserved.

Example of a basic block

Example of a block with positions removed and non-uniform spacing

Example of combined container arrangement

© 1992-2011 Napa Ltd. All rights reserved.

2.3 Properties of stacks

© 1992-2011 Napa Ltd. All rights reserved.

2.4 Properties of blocks

2.5 Properties of container types

© 1992-2011 Napa Ltd. All rights reserved.

Illustration of some container properties

2.6 Numbering of container positions

© 1992-2011 Napa Ltd. All rights reserved.

The numbering systems

2.7 Management of changes

© 1992-2011 Napa Ltd. All rights reserved.

2.8 Usage of alignment points

2.9 Mixed loading of long and short containers

© 1992-2011 Napa Ltd. All rights reserved.

Long and short containers

2.9.1 Long and short containers

2.9.2 General requirements for mixed loading

© 1992-2011 Napa Ltd. All rights reserved.

2.10 List of quantities

© 1992-2011 Napa Ltd. All rights reserved.

XM, YM, ZM center of gravity of the load

3 Defining container arrangements

3.1 Defining a block

3.1.1 The BLOCK command

(b,r,t): start bay row and tier

© 1992-2011 Napa Ltd. All rights reserved.

or separately by the options

B1=i: bay number of the first bay

T: transversal, apply the container dimensions so that x and y change place.

3.1.2 Block defined for mixed loading

3.1.3 Defining the coordinates

Additional spaces can be inserted the following way:

© 1992-2011 Napa Ltd. All rights reserved.

X x0 nx1 d1 nx2 d2 ...

3.1.5 Adding vertical gaps with the ZCORR command

© 1992-2011 Napa Ltd. All rights reserved.

BLOCK B1 D40 T1=1

Simple block with spacings between tiers

3.1.6 Removing locations

© 1992-2011 Napa Ltd. All rights reserved.