Setup Customisation
Setup Customisation
Disclaimer
1.1 AVEVA does not warrant that the use of the AVEVA software will be uninterrupted, error-free or free from
viruses.
1.2 AVEVA shall not be liable for: loss of profits; loss of business; depletion of goodwill and/or similar losses; loss of
anticipated savings; loss of goods; loss of contract; loss of use; loss or corruption of data or information; any
special, indirect, consequential or pure economic loss, costs, damages, charges or expenses which may be
suffered by the user, including any loss suffered by the user resulting from the inaccuracy or invalidity of any data
created by the AVEVA software, irrespective of whether such losses are suffered directly or indirectly, or arise in
contract, tort (including negligence) or otherwise.
1.3 AVEVA's total liability in contract, tort (including negligence), or otherwise, arising in connection with the
performance of the AVEVA software shall be limited to 100% of the licence fees paid in the year in which the user's
claim is brought.
1.4 Clauses 1.1 to 1.3 shall apply to the fullest extent permissible at law.
1.5 In the event of any conflict between the above clauses and the analogous clauses in the software licence under
which the AVEVA software was purchased, the clauses in the software licence shall take precedence.
Copyright
Copyright and all other intellectual property rights in this manual and the associated software, and every part of it
(including source code, object code, any data contained in it, the manual and any other documentation supplied
with it) belongs to, or is validly licensed by, AVEVA Solutions Limited or its subsidiaries.
All rights are reserved to AVEVA Solutions Limited and its subsidiaries. The information contained in this document
is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval system, or transmitted without
the prior written permission of AVEVA Solutions Limited. Where such permission is granted, it expressly requires
that this copyright notice, and the above disclaimer, is prominently displayed at the beginning of every copy that is
made.
The manual and associated documentation may not be adapted, reproduced, or copied, in any material or
electronic form, without the prior written permission of AVEVA Solutions Limited. The user may not reverse
engineer, decompile, copy, or adapt the software. Neither the whole, nor part of the software described in this
publication may be incorporated into any third-party software, product, machine, or system without the prior written
permission of AVEVA Solutions Limited, save as permitted by law. Any such unauthorised action is strictly
prohibited, and may give rise to civil liabilities and criminal prosecution.
The AVEVA software described in this guide is to be installed and operated strictly in accordance with the terms
and conditions of the respective software licences, and in accordance with the relevant User Documentation.
Unauthorised or unlicensed use of the software is strictly prohibited.
Copyright 1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved. AVEVA shall not
be liable for any breach or infringement of a third party's intellectual property rights where such breach results from
a user's modification of the AVEVA software or associated documentation.
AVEVA Solutions Limited, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom.
Trademark
AVEVA and Tribon are registered trademarks of AVEVA Solutions Limited or its subsidiaries. Unauthorised use of
the AVEVA or Tribon trademarks is strictly forbidden.
AVEVA product/software names are trademarks or registered trademarks of AVEVA Solutions Limited or its
subsidiaries, registered in the UK, Europe and other countries (worldwide).
The copyright, trademark rights, or other intellectual property rights in any other product or software, its name or
logo belongs to its respective owner.
Hull Setup Customisation and Standards User Guide
Revision Sheet
Contents Page
Remark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:8
Flanges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Folded Flanges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
General about Flange Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2
Basic Flange End Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:3
Flange End Type 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:3
Flange End Type 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:4
Flange End Type 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:5
Flange End Type 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:5
Flange End Type 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:6
Flange End Type 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:7
Softening of Sharp Corners of Folded Flanges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:7
The Control File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:8
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:8
The FLA_TYPE Statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:8
The FLA_END Statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:9
Folded Flanges, Special Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:11
Basic Flange End 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:14
Basic Flange End 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:14
Concave (obtuse) Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:14
Convex Obtuse Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:15
Convex Acute Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:15
Basic Flange End 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:15
Concave (obtuse) Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:15
Convex Obtuse Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:16
Convex Acute Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:16
Basic Flange End 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:17
Concave (obtuse) Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:17
Convex Obtuse and Convex Acute Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:17
Basic Flange End 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:18
Concave (obtuse) Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:18
Convex Obtuse Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:18
Convex Acute Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:19
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1
Geometry of Cutout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1
Coordinate System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2
Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2
Cutout Macro Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2
Macro Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2
Input Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2
Output Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:3
Environment of Cutout Macros. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:4
Connecting a Cutout Macro to Hull . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5
Cutout Macro, an Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5
Testing of User Developed Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5
Test Running a Cutout Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:6
Brackets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Bracket Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Definition of Bracket Concept. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Type Standard Bracket, Overall Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . 1:3
Elements of the Bracket Set-up Facility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:3
Bracket Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:4
Bracket Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:4
Stiffening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:5
Connection to Surrounding Members. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:6
Shrinkage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Shrinkage Compensation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
General Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Local Shrinkage Compensation Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:3
Fully Automatic Local Shrinkage Compensation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:4
Local Shrinkage Compensation at Plate Edges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:7
Statistical Method for Shrinkage Compensation . . . . . . . . . . . . . . . . . . . . . . . . 1:8
Local Shrinkage at Butt-welded Profile Ends . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:8
User Control of Shrinkage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:9
Activation of Shrinkage Compensation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:9
Customer Set-up of Shrinkage Factors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:9
Input data for creation of shrinkage objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:10
SHRINKAGE Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:10
FILLET and BUTT Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:10
LONGITUDINAL Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:11
Alignment Marking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reference Planes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Definition of Planes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Statement Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Statement Qualifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2
Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:3
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:4
Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:4
Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Customer Set-up of Material Qualities . . . . . . . . . . . . . . . . . . . . . . . 1:1
Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Quality Set-up File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Default Density . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2
Quality File, Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2
Remark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2
Customising . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2
Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:3
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:6
General
1.1 Background
Parts (e.g. plates and stiffeners) are in the production identified by names which often are
painted or otherwise fixed onto the parts. The names may also be issued in drawings and
production lists of different kinds. These production oriented names are in AVEVA Marine
referred to as part names.
(The part names are not equal to and should not be confused with the names of parts used
within the data banks. There are several reasons for this. One is that also identical parts
must have unique names because they have individual occurrences and positions and e.g.
contribute in an individual way to the centre of gravity. On the other hand it may be
advantageous to let equal parts have the same part names because that may reduce the
handling/sorting in the workshop.)
This document describes how a customer can control the structure of part names.
1.2 General
A part name normally consists of a number of constituents that are combined to build up
the name, separated by delimiters. Examples of constituents are the project name, names
of assemblies, position (piece) numbers, etc. Delimiters can be any fixed strings but often
consist of a hyphen (-) or a slash (/).
However, it may not always be necessary to present the part name in its full (maximum)
size, but only a part of it. E.g. all parts in a drawing may belong to the same assembly and
therefore it is enough to present the position (piece) number to uniquely identify the part
within the drawing. Thus there is a need for a customer to set up rules for different levels of
the part name for one and the same part. Depending on the environment or context
alternative layouts can be chosen.
There may be different rules for the names of e.g. normal plates, brackets plates and
stiffeners. Therefore there is a need that part names should be controlled individually for
different types of parts.
The length of a part name is restricted to 48 characters. However, certain applications do
not accept a part name of that length. It is recommended to restrict the part name length to
24 characters, if possible.
1.3.1 General
The customer specification of the name rules is set up in a text file in a special format,
described in detail below. This definition file may be given an arbitrary name and can be
both created and interpreted in a function of the inithull facility. In order to make the part
name definition available to the application programs it should be compiled by inithull. If the
compilation is successful a part name control object will be stored in the structure data bank
(associated with SB_OGDB) by name __TB_PARTNAME_CTRL__.
The compilation will also result in a receipt list with input and errors, if any. If inithull has
been started via the Job Launcher this list can be accessed like all other files resulting from
a Job Launcher run. If inithull has been started outside the Job Launcher the receipt list will
be stored in print directory of the current project with the file extension. lst appended to the
name of the input file.
For backwards compatibility reasons it is currently necessary to assign the input file name
(without file extension) to the environment variable TB_PARTNAME_CTRL.
1.3.2 Layout
The name control file is an ordinary text file containing input in the general TIL format (TIL =
The Interpretive Language).
The input may contain a number of different statement types as specified below.
• LEVEL Statement
The LEVEL statement is used to specify the different levels a customer may want to use in
the naming of parts. The LEVEL statements must occur before the name definition
statements.
Syntax:
LEVEL, <level_name>;
Example:
LEVEL, ’FULL’;
LEVEL, ’SHORT’;
A maximum of 10 LEVEL statements may occur in the file.
• SYMMETRY Statement
The SYMMETRY statement is used to specify the strings to be used if an indication about
the symmetry status (or use) of a part should be included in the part name. It is relevant only
if the attribute /SYM is used in any of the name definition statements (Cf.below). It may
occur only once.
Syntax:
SYMMETRY,
[ /PS = <ps_id> ]
[ /SB = <sb_id> ]
[ /CL = <cl_id> ]
;
PS The string to be used for a PS specific part (or for a symmetric part,
used on PS).
Default is <ps_id>='P'.
SB Ditto for an SB specific part.
Default is <sbps_id>='S'.
CL The string to be used for a part lying in the centre line plane (or
symmetrically around this plane).
Default is <cl_id>='SP'.
• BUILT_PROFILE Statement
Certain profile types are "built" in the sense that the web and flange are welded together.
Such a built profile has normally a position number which is common to the profile as a
whole.
According to the practice of some yards such a built profile may actually be an assembly,
because the web and flange are fabricated to their final shape before being welded together.
Thus, they are temporarily treated as individual parts which need to have a unique part
name.
The BUILT_PROFILE statement is used to specify a constant string that should be used
when forming the part name of the web and flange, respectively, of a built profile to be
handled in this way (Cf. attribute /BUILT in the Name Definition statement below.)
Syntax:
BUILT_PROFILE,
[ /TOTAL= <tot_id> ]
[ /WEB= <web_id> ]
[ /FLANGE= <flange_id> ]
;
Syntax:
<part_type> [, <proftype>]
/LEVEL = <level_name>
<constituent> | <delimiter> (1 ... )
;
<part_type> is the type of part for which the current statement should be
valid. The following part types are currently supported.
• HGEN General (Hull)
• HPPL Plane Panel Plates (Hull)
• HSPL Shell Plates (Hull)
• HBPL Bracket Plates (Hull)
• HCPL Collar (Clip) Plates (Hull)
• HPPR Plane Panel Profiles (Hull)
• HSPR Shell Profiles (Hull)
• HBPR Bracket Profiles (Hull)
• HDOU Doubling Plate /(Hull)
HGEN is special in the case that it takes one parameter
which is a functional description (HGEN, <func_descr>)
where <func_descr> is an existing functional description
code. If a component has the code defined, then HGEN will
be the first priority rule.
<proftype> This is available for the profile part types (HPPR, HSPR and
HBPR). If given, the given profile type will get the name for
this rule instead of the given profile rule. The default rule will
be the rule where no <proftype> is give. <proftype> is one of
the Hull Standard Profile types and should be given as a
string.
LEVEL specifies the level (cf. above). A used level name must have
been specified in a LEVEL statement.
<constituent> specifies the part dependent item that should be used as a
"brick" in building up the part name. The following options
are available and any combination of them can be used.
/PROJ Use the project name.
/ASS= <ass_level number>
Note: that any combination of constituents and delimiters can be used. If two constituents
are given without any delimiter in between an empty delimiter will be created
automatically by the part name facility.
1.3.3 Remark
Note that there are no default rules for the forming of part names, i.e. a name definition file
must always be available, specifying name rules for all the types of parts for which the part
name facility will be used.
1.3.4 Example
The following input file creates names that in earlier versions of the Hull system were built-in
default rules.
Example:
LEVEL, 'FULL' ;
LEVEL, 'SHORT' ;
!
! "FULL" Part Names
!
HGEN, 603 /LEVEL='FULL' /BLOCK /DEL='-H-' /POS;
HPPL /LEVEL='FULL' /SBLOCK /DEL= '-' /POS ;
HSPL /LEVEL='FULL' /SBLOCK /DEL= '-' /POS ;
HBPL /LEVEL='FULL' /SBLOCK /DEL='-B' /POS ;
HCPL, /LEVEL='FULL' /SBLOCK /DEL= '-' /POS ;
HPPR, '31' /LEVEL='FULL' /BLOCK /DEL='-L-' /POS;
HPPR /LEVEL='FULL' /SBLOCK /DEL= '-' /POS ;
HSPR /LEVEL='FULL' /SBLOCK /DEL= '-' /POS ;
HBPR /LEVEL='FULL' /SBLOCK /DEL='-B' /BPOS /LPOS;
!
! "SHORT" Part Names
!
HPPL /LEVEL='SHORT' /POS ;
HSPL /LEVEL='SHORT' /POS ;
HBPL /LEVEL='SHORT' /DEL= 'B' /POS ;
HCPL, /LEVEL='SHORT' /POS ;
HPPR /LEVEL='SHORT' /POS ;
HSPR /LEVEL='SHORT' /POS ;
HBPL /LEVEL='SHORT' /DEL= 'B' /BPOS /LPOS;
Suppose that these rules are used for parts of a panel belonging to the block AA123.
Further suppose that all position numbers equal 1. Then the part names will be:
For the planar profile in the above example, the priority is that if a profile has a functional
description of 603 defined, then the HGEN rule will be used. If the profile is of type 31, but
no functional description of 603 is defined then the "HPPR, '31'" rule will be used. All other
cases for planar profiles will use the "HPPR /LEVEL" rule.
Shell plate: 1
Bracket plate: B1
Clip plate: 1
Shell profile: 1
1.4 Remarks
For backwards compatibility reasons a part name control file for hull parts should always
contain part naming rules for all types of hull parts to the extent illustrated in the example
above. It is recommended to use the level names of the example, i.e. FULL for full names,
SHORT for short names. However, other LEVEL names may be chosen if they are assigned
to the environment variables TB_PARTNAME_FULL and TB_PARTNAME_SHORT.
The Hull application always supposes that there should be a complete part name
specification on levels TB_PARTNAME_FULL (with default name FULL) and
TB_PARTNAME_SHORT (with default name SHORT). However, these names may be
different for different modules, see below.
Example:
PART_PLCM RULEA
PROFNEST, RULEB
etcetera.
This means that level RULEA will be used when creating partnames of plates in PLCM
sketches, RULEB in profnest.
The following module names are currently valid (default level is FULL unless otherwise
specified):
2.1 Background
Parts in the AVEVA Marine Product Information Model (sometimes referred to as PIM) are
identified by names and by different identification codes, used internally in AVEVA Marine.
The names may carry some information about the part. At least when it comes to part
names (the production oriented names) the name normally contains some information about
which assembly the part belongs to.
To support more explicit description of parts, AVEVA Hull also allows descriptive name
"tags" to be assigned to all parts. These tags are called functional descriptions and they are
strings that "follow" the parts throughout the development of the project. In this document
the term "Functional Description" is normally abbreviated to FD.
In addition to serving as pure name tags (which might be valuable in request functions like
Info/Model and in parts lists), the FD:s may also be used to control certain automatic
evaluations. An example of such a use is that the functional properties may control the
automatic calculation of weld sizes.
The purpose of this document is to give a complete description of the functional descriptions
in AVEVA Marine, i.e. regarding general principles, how they are set up and assigned to
parts.
2.3.1 General
The available functional descriptions are registered in an object in the data bank associated
with the environment variable SB_OGDB. This object has the fixed name
__FUNCTIONAL_PROPERTY__.
There are two ways in which the FD:s object can be updated.
1. The functional FD object is created or modified via an input text file in a specific format
described in detail below. This file is read and interpreted in a function of the hull utility
program inithull. As a result of the interpretation the file contents will be merged into the
FD object.
2. Modification of the FD object can also be done via a wizard in the FD function of inithull
without any input file.
The interpretation of the concept of "merge" in this context will be further discussed below.
• File Name
The name of the set-up file may be chosen arbitrarily and is given as input to the inithull
function for set-up of FD:s. However, the file extension should be .dat. A list file will be
produced during the process of interpretation of the input file. Inithull is normally run via the
Job Launcher and the list file will be stored as defined in the set-up for the Job Launcher.
Syntax:
DESCR, /VALUE='Panel';
20000
DESCR, 434 /VALUE='Panel at !X';
DESCR, 612 /VALUE='This will only be shown for stiffeners
in GUI';
DESCR, 735 /VALUE='This will only be shown for flanges in
GUI';
DESCR, 4442 /VALUE='Temp Functional Description';
Note that if some of these indices should already exist their description string will be
replaced by the one in the file (see Merging below)
2.3.4 Merging
Since the update of the FD object is always incremental (except if the object has been
deleted completely) the result of new input will always be merged into the current object.
Therefore it is important to keep the following in mind:
1. To delete a FD: Make the FD string an empty string, retaining the index.
2. Adding a new FD: Add a new index and a new FD string.
3. Changing a FD: Keep the index but change the FD string.
Please further observe the following:
• If you rerun an input file and change the index number (e.g. 20000 to 2000 in the
example file above (e.g. to correct a misprint)) a new FD with index 2000 will be added
but the old FD with index 20000 will still be retained (with the same string). To change
the FD with index 20000 to the new index 2000 the old FD it must be explicitly deleted
as described above.
• Likewise, if you change an index number in the list form after an activation of the
wizard, you will create a new FD entry but the old one will still be retained.
3.1 General
A number of special notes are used in drawings with different contents. The contents of the
notes are depending on both the type of the note and the component the note is made for.
The configurable note option in AVEVA Marine makes it possible to create notes with a high
degree of freedom regarding both the contents and the appearance. Each note type is given
an identifying string to appear in a selection list, and a set of characteristics described in
detail below.
The configuration is implemented as a Vitesse hook, meaning that a file with a specific
name is accessed from the AVEVA Marine functions. This file is written using the Vitesse
syntax and interfaces.
3.3.1 getNoteName
This method is supposed to have access to a list of note name strings. The input parameter
<NoteInd> is an integer index and should return the list value as a string if the index is within
the bounds of the list. If the index is outside the list bounds the nil object should be returned.
The string is supposed to be unique among the strings in the list, and must not be longer
than 80 characters.
The storing of the note names is free as long as they can be accessed as an indexed list
through the method getNoteName. The note names are used to present a list of
available notes to select from in the AVEVA Marine function that set configurable notes.
3.3.2 getNoteChar
This method is supposed to have access to a list of note characteristic records. It also takes
an integer index as parameter and should return a list of note characteristics for the
corresponding note. This list of note characteristic records should have the same number of
elements as the corresponding name list described above, i.e. there should be one entry for
each note type.
The characteristics record returned should contain the following items:
(<reference>,<placement>,<colour>,<layer>, <flip_angle>)
<reference> is a string defining the location of the reference point. The allowed values
are described below:
Value Description
cursor Use the pick point defined by the user as reference point
midpoint Use the midpoint of the longest geometry in the identified picture
element
COG Use the centre of the circumscribed rectangle of the identified picture
element
<placement> is a string defining the location of the note body in case no reference lines
are used. The placement is related to the reference point and the values refer to the
circumscribed rectangle of the note body.
<placement> is built up by two values, one for horizontal placement and one for vertical
placement that are concatenated without delimiters to form one string. The allowed values
are described below:
Origin refers to the point (0,0) in the local coordinate system used when building up the note
body further explained below. All combinations of these values are valid, e.g. LeftLower or
MidOrigin.
<colour> is a string giving the name of a colour selected from the standard set.
<layer> is either a string defining a named layer existing in the Layer Alias File (see
User's Guide Drafting), or an integer number giving the layer. The created note component
will then get this layer.
<flip_angle> is an integer number defining the angle in degrees where the note text
along a line changes from one side of the line to the other. The angle must be between 0
and 180 degrees.
3.3.3 getNoteFilter
This method is supposed to have access to a list of pick filters for each note. These filters
define the valid models/parts/subparts to be picked for note setting. The method takes two
integer arguments, the first is the note type index and the second is a filter index within this
note type. This means that each note can have many filters. All components matching any
of the filters can be picked.
The return value should be a list of three strings defining the model type, the part type and
the subpart type. The valid string value combinations are described in the table below:
flange -
pillar -
plate -
bracket stiffener
flange
seam -
hole -
notch -
cutout -
pipe "-
equipment "-
cable "-
struct "-
longitudinal - -
transversal - -
ventilation "-
accommodation "-
plate -
Irrelevant values should be set to empty strings. Note that it is not necessary to define the
filter all the way down even if it is possible. E.g. if a bracket as a whole should be picked the
subpart type should be empty, or if the whole panel should be picked, also the part type is
set empty.
Giving indices outside the list bounds should result in a nil object return.
3.3.4 getNoteData
This method is supposed to have access to a list of note definition records set by the
method setNoteData described below. It takes an integer item index and returns a note
definition record if the index is within the bounds of the note data list.
The records have the same basic layout, starting with six integer values followed by five
floats and ended by a string. They are interpreted differently depending on the first value.
Four different types exist, the reference symbol, the free symbol, the text in symbol, and the
free text. Irrelevant values should be set to nil values (0, 0.0 and "").
In the example below classes have been defined to encapsulate the record contents only
using relevant values for each type.
• Reference Symbol
The reference symbol is the symbol placed at the start point of the reference string-line
defined by the user, often an arrow. If the note is placed without a reference line, no
reference symbol will appear.
The reference symbol note definition record has the following contents:
(<type>,<font>,<number>,0,0,0.0,0.0,0.0,0.0,<height> "")
<font> is the symbol font number used to make up the name of the
symbol font according to d012sy<font>.sbs.
• Free Symbol
The free symbol is part of the note body. It can be placed freely and can be mixed with text
to form the note.
The free symbol note definition record has the following contents:
(<type>,<font>,<number>,<conn>,<mirr>,<hori>,<vert>,0.0,rotation>,<height>,"")
<font> is the symbol font number. For a description on symbol fonts see
User's Guide Drafting.
<mirr> is a mirror code where 1 means reflection in the u-axis and 2 means
reflection in the v-axis. 0 means no reflection.
<hori> is the horizontal position in mm. If set to 0.0 the symbol is left
padded.
• Text in Symbol
The text in symbol is placed using a predefined symbol text position with certain
characteristics. It is placed in the symbol preceding the text in symbol definition.
The text in symbol note definition record has the following contents:
(<type>,<font>,0,<conn>,0,0.0,0.0,<aspect>,<slant>, <height>,<text>)
<font> is the text font number. For a description of text fonts see User's
Guide Drafting.
• Free Text
The free text is freely placed and can be mixed with symbols to make up the note body.
The free text note definition record has the following contents:
(<type>,<font>,0,0,0,<hori>,<vert>,<aspect>,<slant>,<height>,<text>)
<hori> is the horizontal position in mm. If set to 0.0 the text is left padded.
3.3.5 setNoteData
The parameter list is:
setNoteData(<NoteNo>,<ModelType>,<Model>,<PartType>,<Part>
,<SubPartType>,<SubPart>)
This method takes an integer note number referring to the list of notes defined by
getNoteName. The first note has # 1 and so on. The following parameters are used to
specify a model object part that has been picked by the user. The method is called once for
each model part picked and is used to populate an internal list of note definition records to
be read by the method getNoteData.
The <ModelType>,<PartType> and <SubPartType> can have the values
described under getNoteFilter above. <Model> is the name of the model object while
<Part> is the component/part number and <SubPart> is the subordinate component/
part number. Empty strings for the types implies non-valid numbers.
The implementation of the setNoteData method is entirely up to the user. The suggestion is
to use Data Extraction to retrieve relevant data from the model and then transform it into
note definition records.
When adding note definition records certain rules about the order has to be fulfilled.
• The first record must define a reference symbol.
• Only one reference symbol record is allowed.
• Before a record defining a text in a symbol, a symbol record must have been added
(containing the used text position).
3.3.6 Example
The following example creates five different kind of notes. See TBhook_ConfigNote.txt.
4 Surface Setup
If the hull reference object exists, you will get some predefined values. In the example
above, the name of the hull reference object is DS4HULLREF and it is always located on
the data bank assigned to the environment variable SB_CGDB.
The value for "Name of the hull form" is the surface name. Make sure it is the correct name.
If not, then change it and press the button "Create Object".
If additional surfaces should be used, then press the "Additional Surfaces…" button and
make sure the names are correct:
To check that the surface set-up is ok, start e.g. Structural Design and cut some curves.
Preferably the hull reference object should be made available to the applications via the
environment variable SB_HREF.
If the default files have been copied from a previously used project, there might be some old
references to the hull reference object via default parameters. If so remove them.
1.1 Background
A ship is constructed by the assembly of parts to larger and larger units. In almost all
assembly operations parts or assemblies are welded together. Each weld combines two
parts and in at least one of the parts an edge of the part is involved. Edges to be welded
must in most cases be prepared in a special way to create proper conditions for the type of
welding that is selected. This is done by the application of bevel preparation along edges
according to a set of predefined bevel types.
AVEVA Marine has an advanced facility for the set-up, customisation and application of
bevels in the modelling and fabrication of parts. The purpose of this document is to give a
complete description of this facility.
Figure 1:1. A typical example of one butt joint and one fillet joint.
The shape of an edge involved in butt and fillet welding, respectively, may look the same but
they are always described using different bevel types as specified in detail in paragraphs to
follow.
Full details about various aspects of the AVEVA Marine support for the handling of fillet
bevels are given in paragraphs below.
1.3.1 Definitions
All standardized bevels are supposed to be an 'instance' of a number of basic bevel types
(or bevel types, for short).
Each bevel type is identified by a number, fixed by AVEVA, and has a number of parameters
associated with it. All the currently available bevel types are specified in detail in this
document.
The customer defines a bevel standard of his own as a number of instances of the basic
bevel types, each identified by a user selected number, called the user bevel code (or
bevel code, for short). Each bevel code is defined by either assigning fixed values to its
parameters or by making them depending on the connection angle between the elements
(fillet welding only!).
If two plates with different plate thicknesses are butt welded together, the difference might
call for a variant of the basic bevel type. The different variants are also described below.
Such a variant might include extra machining, resulting in a chamfer.
The thickness of the thinner plate in a butt joint is called the e-measure of the bevel on the
thicker plate.
Most bevel types have an opening angle in one or both of the sides of the plate. The
opening angle in the positive direction is denoted Alpha and in the negative direction Beta.
U-shaped bevels have a user controllable arc (radius) in their cross section geometry,
otherwise the bevel sections consist of straight lines.
Some bevels have got a nose or a sharp knee. The bevel definition may include a gap
between the centre of the joint and the edge of the plate after preparation (to be filled in
during the welding).
In the bevel definition a bevel has one side "up" and one side "down" related to the upper
and lower plate surfaces, respectively, in the figures below. In this document the upper side
is called the positive side of the bevel, the lower side is called the negative side.
When the positive side of a bevel is upwards in a drawing of a plate the bevel is said to be in
a normal position, when it is downwards it is said to be reflected.
These concepts are illustrated in the figure below.
Some bevel types may also have a second opening angle ( see figure below). The width
of the second opening angle on the edge of the plate, will be found in production data.
When evaluating the chamfer of a bevel there are two different options available.
The default situation is that the extension of the chamfer line will reach the level of the
abutting plate in the centre of the joint, see the figure below.
The second possibility is that the chamfer line reaches the level of the abutting plate in the
knuckle point of the bevel contour, see the figure below.
This will lead to a wider chamfer and is selected via assignment (of any value) to the
environment variable SBH_WIDE_CHAMFER.
Variant Description
• Bevel Type 10
Bevel type 10 means square butt welding.
• Bevel Type 11
Bevel type 11 means square butt welding with overlap.
Note: Please note that GAP should be defined as a negative value, i.e. the overlap.
• Bevel Type 20
This bevel type is a V-joint (without any nose)
.
• Bevel Type 30
This bevel type is an Y-joint, i.e. a V-joint with a nose (of fixed height)
• Bevel Type 31
This bevel type is an Y-joint with an angle defined for the nose.
• Bevel Type 33
This bevel type is a variant of the Y-joint (type 30) where the "V"-shaped opening is replaced
by a "U".
• Bevel Type 40
This bevel type is a "K" bevel, i.e. open in both directions with a nose. The bevel is
symmetric, i.e. the opening angles in both directions are equal and the nose is centred in the
middle of the plate (in variant 0)
• Bevel Type 41
This bevel is an asymmetric variant of the bevel type 40. The asymmetry means that the
opening angles on both sides of the bevel may be different and that the position of the nose
must be defined. This is done as the distance (H) to the lower edge of the nose from the
negative side, cf. the figure below. Apart from these differences the pictures for bevel type
40 are applicable
.
• Bevel Type 42
This bevel type is a variant of the asymmetric K-joint (bevel type 41) where the "V"-shaped
opening on both sides are replaced by "U"-shaped openings. The length of the nose and the
radius of the "U" may be defined on both sides.
• Bevel Type 43
This bevel type is a variant of the asymmetric K-joint (bevel type 41) where the "V"-shaped
opening on the positive side is replaced by a "U".
Relevant parameters are: α, β, NOSE, H, RAD, GAP.
Parameters as for bevel type 41. For RAD, see bevel type 33
• Bevel Type 50
This bevel type is an X-bevel, i.e. open in both directions with a sharp knee. The bevel is
symmetric, i.e. the opening angles in both directions are equal and the knee is centred in the
middle of the plate (in variant 0)
.
• Bevel Type 51
This bevel is an asymmetric variant of the bevel type 50. The asymmetry means that the
opening angles on both sides of the bevel may be different and that the position of the knee
must be defined. This is done as the distance H in the figure below. Apart from these
differences the pictures for bevel type 50 are applicable.
.
In the figures the mould plane has been indicated by a cross (X). The nominal limit curve is
in P.
Both figures show a plate edge supposed to have a square bevel.
In case A the nominal size need not be changed for the part. In case B the nominal size
must be reduced for the part so that the limit curve is moved from P to P1. This
displacement is not constant but may vary along the curve depending on the connection
angle.
All types of fixed bevels are affected by this change as illustrated in another figure below
.
In this case the part size is expanded, being moved from P to P1.
The facility to re-calculate the part geometry is activated by the environment variable name
SBH_BEVEL_ADJUST but also supposes that the option in product number 10517
(“Variable Bevelling in Plates and Profiles”) is available.
• Bevel Type 15
Bevel type 15 is a bevel type for square fillet, cf. the figure below. Only the basic variant is
available
.
• Bevel Type 25
This bevel type is similar to bevel type 20 but is used for fillet welding
.
• Bevel Type 35
This bevel type is similar to type 30 but is used for fillet welding
• Bevel Type 38
This bevel type is similar to type 33 but used for fillet welding
• Bevel Type 44
This bevel type is similar to bevel type 42 but used for fillet welding.
That bevel type is a variant of the asymmetric K-joint (bevel type 41) where the "V"-shaped
opening on both sides are replaced by "U"-shaped openings. The length of the nose and the
radius of the "U" may be defined on both sides.
• Bevel Type 45
This bevel type is similar to the symmetric bevel type 40 but used for fillet welding
.
• Bevel Type 46
This bevel type is similar to bevel type 41 but used for fillet welding
.
• Bevel Type 48
This bevel type is similar to bevel type 43 but used for fillet welding.
• Bevel Type 55
This bevel type is similar to the symmetric bevel type 50 but used for fillet welding
.
• Bevel Type 58
This bevel type has the same shape as type 51 but is used for fillet welding, i.e. it is an
asymmetric X-bevel (see the figure below)
1.6.2 Definitions
In order for the survey of bevel types with varying bevel angle to become sensible it is
necessary to define some concepts used in this context.
The automatic selection of bevel against other structures, e.g. in a plate edge against the
shell, is - for a certain production line - in principle dependant on two factors, namely the
thickness of plate and - primarily - on the angle between the plate and the surface against
which it is welded (=connection surface). This angle is here called the connection angle
and is in each point measured in a normal plane to the part contour. It is measured relative
to the normal of the mould plane of the part in the direction from where it is regarded. For a
plate part this is the direction of the positive w-axis of its local co-ordinate system, for a
profile (web) it is the mould line side, for a profile flange it is the top view direction. The
connection angle is said to be positive if it creates an open "wedge" in this direction,
negative otherwise, see the figures below. The connection angle is in this document
denoted CON
From the previous figure with a plane panel it might not be directly obvious how to define the
connection angle for a stiffener. Therefore the figure below shows two stiffeners with
different connection angle. The connection angle is, once again, denoted CON.
As can be seen, it is important in which direction the flange is pointing. The connection
angle is said to be negative, if the flange is pointing away from the surface. And positive
otherwise. (Of course, not every stiffener has a flange with a unique direction, but you can
always temporarily change to e.g. an L-bar).
In a bevel type with varying angles parts of the bevel section may be tightly connected to the
connection surface. However there is also a possibility that some angles are fixed, or that a
bevel angle is set equal to the connection angle with a certain angular offset. This offset is
below referred to as DIFF, see the figure below for an example
• Bevel Type 16
This is a completely tight joint with a full fitting (the figure shows a negative CON)
.
CON>0: The bevel should be turned so that the positive side is turned downwards.
CON<0: The positive side should be turned upwards, see the figures below.
• Bevel Type 17
This is a semi-tight bevel type where the lower part of the joint is parallel to the connection
surface and the upper part is vertical
.
| NOSE | <1 Means that NOSE is defined as factor to be multiplied by the actual
plate thickness to get the height of the nose.
NOSE > 0 Means that NOSE is the height of the vertical (upper) part of the
joint,
NOSE < 0 Means the height of the lower, tightly connected nose.
(e.g. NOSE=0.5 means that the "knee" of the bevel is in the middle
of the plate)
CON>0: The positive side of the bevel is upwards (as in the figure above).
• Bevel Type 26
This is a V-joint bevel type where the bevel angle varies. It is normally supposed to have a
certain angular offset relative to the connection surface
.
CON>0: The positive side of the bevel is normally supposed to be turned upwards
(as in the figure above).
• Bevel Type 36
Bevel type 36 is a Y-bevel where the opening angle is depending on the varying connection
angle in a similar way as described for bevel type 26 above
NOSE > 0 Means that the height of the actual toe (the vertical
(lower) part of the bevel contour),
(E.g. NOSE=0.5 means that the "knee" of the bevel is in the middle of the plate)
• Bevel Type 39
This bevel type is a Y-joint with a varying connection angle defined for the nose, that is, the
nose is supposed to be tightly connected.
• Bevel Type 47
This bevel type is a variant of the asymmetric K-joint (bevel type 41) where the bevel angles
in both directions may vary.
• Bevel Type 49
This bevel type is a variant of the asymmetric K-joint (bevel type 41) where the bevel angles
in both directions may vary. The bevel type has a tight connection on the nose.
• Bevel Type 37
Bevel type 37 is a Y-bevel with a tight connection (varying angle) of the lower part of the
bevel contour. Normally, the resulting edge will be X-shaped
NOSE > 0 Means that the height of the actual toe (the lower part
of the bevel contour),
(E.g. NOSE=0.5 means that the "knee" of the bevel is in the middle of the plate)
• Bevel Type 56
Bevel type 56 is an X-bevel type with one varying bevel angle. α is varying and β is fixed
• Bevel Type 57
Bevel type 57 is an X-bevel type where the bevel angle in both directions may vary
The AVEVA Marine bevel handling is activated by assignment of the environment variable
SBH_BEVEL_CTRL. Suppose that it has been assigned the following value:
n:\usr\projdir\bevel_def
Then the total file specification of the input file is formed by adding the file extension.dat, i.e.
n:\usr\projdir\bevel_def.dat
As the result of the compilation there will also be a receipt listing the name of which is
formed by adding the file extension .lst, i.e.
n:\usr\projdir\bevel_def.lst
In addition to a print-out of the input this list may contain error messages.
The extended bevel handling is activated by the existence of this object on the data bank.
1.8.1 Parameters
In the specification of the bevel definition quite a number of parameters are mentioned, all of
which are listed below. Some of them are given values in the definition file, others are
calculated from the given parameters and are referred to when defining texts.
Variant
Gap
Chamfer
Alpha (α) Opening angle on the upper side of a bevel with opening (e.g. V-
type bevels). For symmetric K- and X-joints, Alpha is valid also as
the opening angle on negative side.
Beta (β) Opening angle on negative side of K- and X-type bevels. For
symmetrical bevel types, Beta by definition is equal to Alpha and
should not be separately defined.
D_TS, D_OS The depth of the joint, measured from the positive side and the
negative side, respectively. In case of chamfer the depth is
measured from the point where the extended chamfer line
intersects the vertical edge line of the bevel, cf. the figure below.
These two parameters are calculated from other parameters.
Nose Height of nose in the basic bevel type (relevant for certain bevel
types only).
W_CHA Width of chamfer, measured from the vertical line through the edge
of the bevel (cf. the figure above). Calculated parameter.
OTH_TS Height of chamfer on the positive side and on the negative side,
OTH_OS respectively ("this side" and "other side"). Calculated parameters.
NOSE_ANGLE Fixed angle at the nose. Relevant for bevel type 31.
• CHAMFER Statement
The CHAMFER statement defines the normal chamfer angle for bevel variants with
chamfer.
Syntax
CHAMFER, <angle> ;
• VARIANT Statement
The VARIANT statement sets up the conditions for selection of bevel variants, e.g. for when
a bevel should be given a chamfer.
Syntax:
VARIANT [/TOL=<tol>]
[/LIM=<th_lim>]
[/OPEN=(<diff_lt>[,<diff_gt>])]
[/SQUARE=(<diff_lt>[,<diff_gt>] )]
;
Default value: 10 mm
Default values:
<diff_lt> = 3 mm
<diff_gt> = 5 mm
Example:
Suppose that the default values are used and that the
plate thicknesses are 12 and 16 mm. The difference is 4
mm. Since the thinner plate (12 mm) is thicker than the
limit (10 mm) comparison should be made to the greater
tolerance value (=5). Since 4 < 5, select a variant without
chamfer.
Changing the plate thicknesses to 9 and 13, i.e. keeping
the difference, would result in a variant with chamfer, since
comparison should be made with the tolerance for thinner
plates (=3).
• BASIC_TEXT Statement
The basic text is a numbered text, consisting of:
• a prefix,
• one parameter of the bevel converted into a string,
• a suffix.
Optionally, arbitrary texts may be defined as basic strings without reference to any bevel
parameter.
Syntax:
BASIC_TEXT,<no>
/PARAMETER=<parameter>
/AFFIX=(<prefix>[,<suffix>])
[/SKIP_BETA]
[/SKIP_ZERO_WELD]
[/DECIMALS=<no_dec>]
;
<no> is the customer defined number of the resulting text string (>0 or
<0).
<no>::= <integer>
The text number 0 is reserved and has a special sense (see
DRAW_TEXT Statement and NEST_TEXT Statement below).
<parameter>::=
ALPHA |
ALPHA2 |
BETA |
BETA2 |
D_TS |
D_OS |
E |
NOSE |
W_CHA |
ANGLE2_WTS |
ANGLE2_WOS |
OTH_TS |
OTH_OS |
WELD_SIZE |
ANY
ALPHA Alpha as described above will be converted into a string.
ANY Used to define an arbitrary basic text, not based on any bevel
parameter. It does not make sense to assign any suffix in this
case.
The character '%' (per cent) in any of these two strings will be replaced by the symbol for
degrees (i.e. a small circle) in the resulting string.
Default: 0.
Example:
2. Suppose that the thickness is 26 mm, the E-measure 20 mm and that the chamfer
angle is 14 degrees.
Example:
4. The following statements might establish almost all the basic texts required for a
customer to define his own bevel texts.
The numbers used here will be referred to in the examples of other statement types.
• DRAW_TEXT Statement
The DRAW_TEXT statement is used to define the texts to be set in the bevel notes in
drawings. The text is formed via references to basic texts, defined earlier in the input
scheme.
Each text definition is related to a basic bevel type, i.e. all instances (bevel codes) of one
basic type will have the same text definition. However, each variant of the bevel type has a
text definition of its own. (The resulting texts may, of course, be different because of
differences in the values of the parameters, referred to, even if the definition is identical).
Syntax:
DRAW_TEXT,<bevel_no>
[/<var_key> = (<b_text>[,<b_text> (2...10)]) (
0...5)
;
<bevel_no> is the basic bevel type for which the definition is valid.
It must be selected as one of the existing bevel types.
<var_key> is a keyword that defines the variant of the bevel type for which the
text should be valid.
<var_key>::= VAR_0 |
VAR_1 |
VAR_2 |
VAR_3 |
VAR_4 |
VAR_9
The digit indicates the variant number. (Not all combinations of
bevel type and variants are relevant, cf. the survey of bevel types
above).
The examples below use the basic texts, defined above in the BASIC_TEXT statement.
Example:
1. DRAW_TEXT,10
/VAR_1= 91
/VAR_2=(0, 91) ;
Example:
2. DRAW_TEXT, 30
/VAR_0= (10, 60)
/VAR_1= (10, 60, 91)
/VAR_2= (10, 60, 0, 91)
/VAR_4= (10, 60)
The statements below define a large part of the texts that may be required for a
customer to set up his texts to be used in drawings (however, with no examples for
variant 9).
DRAW_TEXT, 10
/VAR_1= 91
/VAR_2= (0, 91) ;
DRAW_TEXT, 20
/VAR_0= 10
/VAR_1= (10, 91)
/VAR_2= (10, 0, 91)
/VAR_4= (10, 60);
DRAW_TEXT, 30
/VAR_0= (10, 60)
/VAR_1= (10, 60, 91)
/VAR_2= (10, 60, 0, 91)
/VAR_4= (10, 60);
DRAW_TEXT, 40
/VAR_0= (10, 60)
/VAR_1= (10, 60, 91)
/VAR_2= (10, 60, 0, 91)
/VAR_3= (10, 60, 30)
/VAR_4= (10, 60, 30);
DRAW_TEXT, 50
/VAR_0= 10
/VAR_1= (10, 91)
/VAR_2= (10, 0, 91)
/VAR_3= (10, 30)
/VAR_4= (10, 30);
DRAW_TEXT, 51
/VAR_0= (10, 30, 0, 20)
/VAR_1= (10, 30, 91, 0, 20)
/VAR_2= (10, 30, 0, 20, 91)
/VAR_3= (10, 30, 0, 20)
/VAR_4= (10, 30, 0, 20);
• NEST_TEXT Statement
The NEST_TEXT statement is used to define texts to be set along the edges of parts in
burning sketches.
It is built up according to the same principles as the DRAW_TEXT Statement. However, the
parts may be oriented so that the bevel either has its positive side upwards or downwards.
Therefore, special keywords are used to define the texts in normal and mirrored cases. (For
drawing texts this is taken care of by moving the dashed reference line above or below the
solid line).
Syntax:
NEST_TEXT,<bevel_no>
[/<var_key>=<b_text>, (1...10)] (1...12)
;
<bevel_no> is the basic bevel type for which the definition is valid. It must be
selected as one of the existing basic bevel types.
<var_key> is a keyword that defines the variant and the side (normal/
reflected) of the bevel type for which the text should be valid.
<var_key>::=
NORM_0 |
NORM_1 |
NORM_2 |
NORM_3 |
NORM_4 |
REFL_0 |
REFL_1 |
REFL_2 |
REFL_3 |
REFL_4 |
REFL_9
<b_text> is the number of a previously defined basic text (cf. the
BASIC_TEXT Statement above). Up to 10 basic texts may be
concatenated into one text.
For certain bevel types and variants the texts may have to be
divided into two lines. Giving a basic text number 0 indicates the
end of the first text and the beginning of the second.
Example:
Supposing E= 20, plate thickness= 26 and chamfer angle= 14, this would result in the
following texts:
• variant 1, normal, and variant 2, mirrored: 'TS chmf. to 20.0 w. 24'
• variant 1, mirrored, and variant 2, normal: 'OS chmf. to 20.0 w. 24'
The following input statements define most of the nesting texts that might be required for a
certain customer in burning sketches (with the exception of variant 9). (Of course this is only
one way of doing the same thing. The partition into basic texts could have been done in a
different way and other parameters could have been used).
NEST_TEXT, 10/NORM_1=( 50, 70)
/NORM_2=(-50, 70)
/REFL_1=(-50, 70)
/REFL_2=( 50, 70) ;
NEST_TEXT, 20/NORM_0= 1
/NORM_1=(50, 70, 0, 11)
/NORM_2=(-50, 70, 0, 11)
/NORM_4=( 11, 60)
/REFL_0=-11
/REFL_1=(-50, 70, 0, -11)
/REFL_2=( 50, 70, 0, -11)
/REFL_4=(-11, 60) ;
NEST_TEXT, 30/NORM_0=( 11, 60)
/NORM_1=( 50, 70, 0, 11, 60)
/NORM_2=(-50, 70, 0, 11, 60)
/NORM_4=( 11, 60)
/REFL_0=(-11, 60)
/REFL_1=(-50, 70, 0,-11, 60)
/REFL_2=( 50, 70, 0,-11, 60)
/REFL_4=(-11, 60) ;
NEST_TEXT, 40/NORM_0=( 92, 10, 60)
/NORM_1=( 50, 70, 0, 92, 10, 60)
/NORM_2=(-50, 70, 0, 92, 10, 60)
/NORM_3=( 11, 30, 0,-11, 60)
/NORM_4=( 11, 30, 0,-11, 60)
/REFL_0=( 92, 10, 60)
/REFL_1=(-50, 70, 0, 92, 60)
/REFL_2=( 50, 70, 0, 92, 60)
/REFL_3=( 11,-30, 0,-11, 60)
/REFL_4=( 11,-30, 0,-11, 60) ;
NEST_TEXT, 50/NORM_0=( 92, 10)
/NORM_1=( 50, 70, 0, 92, 10)
/NORM_2=(-50, 70, 0, 92, 10)
/NORM_3=( 11, 30, 90,-11)
/NORM_4=( 11, 30, 90,-11)
/REFL_0=( 92, 10, 60)
/REFL_1=(-50, 70, 0, 92)
• BEFORE_SYMBOL_TEXT Statement
The texts in bevel notes are normally placed after the bevel symbol, supposing the bevel is
symmetric, i.e. there is only one "draw text". The BEFORE_SYMBOL_TEXT statement may
be used to define a text to the left of the symbol.
Syntax:
BEFORE_SYMBOL_TEXT, <bevel_no>
[/<var_key>=( <b_text>, (1...10))] (1...6)
;
<bevel_no> The basic bevel type for which the definition is valid.
<var_key> The attribute that defines the variant of the bevel type for which
the text should be valid.
<var_key>::= VAR_0 |
VAR_1 |
VAR_2 |
VAR_3 |
VAR_4 |
VAR_9
<b_text> The number of a previously defined basic text (cf. the
BASIC_TEXT Statement). Up to 10 basic texts may be combined.
The text may be split into two parts (above and below the
reference line) by reference to a (non-exiting) basic text 0.
Example:
BEFORE_SYMB_TEXT, 10,
/VAR_0 = (1, 2)
/VAR_1 = (3, 0, 4, 5)
/VAR_2 = (4, 5, 0, 3)
/VAR_9 = (4, 5, 0, 6, 7)
;
• WELD_PROCESS_TEXT Statement
This statement type defines texts that may be added at the "tail" of the bevel notes, mainly
intended to specify the welding process. Any number of weld texts may be defined and they
will all be presented for user selection when a bevel note is set. Note that these texts are
independent of the bevel type.
Syntax:
Here,,
Example:
• SYMBOL_COMBINATION Statement
Normally the symbols to be associated with a certain bevel type and to be presented in a
bevel note are supposed to be uniquely defined by the bevel type. However, AVEVA Marine
also allows that one from a set of predefined symbol combinations may be selected at the
time when the bevel note is set. They will be presented for interactive picking.
Each occurrence of this statement type creates one combination (set) of bevel and weld
symbols.
Syntax:
SYMBOL_COMBINATION, <symb_comb_no>
[/SYMBOL=( <symb>, ...)]
[/WELD_SYMBOL=( <symb>, ...)]
[/AFTER_TEXT_SYMBOL=( <symb>, ...)]
;
WELD_SYMBOL Ditto.
AFTER_TEXT_SYMBOL Ditto.
Syntax:
TYPE is the basic bevel type of which the current code is an instance.
BEV_NAME Is the string representation of the bevel code. This string may be
used instead of the code to refere to the bevel. If BEV_NAME is
defined, the system will if possible use that instead of the code
when bevels are presented.
GAP is the gap between the midpoint of the joint and the utmost part
of the bevel contour.
In butt welding (and when the bevel is symmetric) the total gap
will thus be 2*<gap>.
Set to 0 if undefined.
ALPHA The opening angle on the positive side of V-, Y-, K- and X-joints.
Moreover, the opening angle on the negative side of
symmetrical K- and X-joints. (Denoted a in the bevel figures
above.)
VAR_ALPHA Used for bevel types which have an opening angle in the
positive direction varying depending on the connection angle (cf.
the AUTO_SELECT Statement below). Must not be assigned
any value in the BEVEL statement.
VAR_BETA The opening angle on the negative side should be derived from
the connection angle as specified in the AUTO_SELECT
Statement (cf. below). Must not be assigned any value in the
BEVEL statement.
NOSE Height of nose for Y- and K-bevels (compulsory for these bevel
types).
h = max(<nose_pos>,<nose_pos_factor>*E)
AFTER_TEXT_SYM In some special cases there might occur an extra symbol after
BOL the text on the reference line. This attribute is used to select that
symbol.
The "after text" symbols are normally set above the reference
line. However, a negative value means that it should be set
below the reference line.
CHAMFER is the chamfer angle of the current bevel code. If not defined, the
default angle set in the CHAMFER Statement will be used.
SYMBOL_REFL Same as the ones without _REFL, but the reflected side
WELD_SYMBOL_RE
FL
NAME_REFL
AFTER_TEXT_SYM
BOL_REFL
Example:
1. BEVEL, 101
/TYPE=10
/SYMBOL=(61,-61)
/GAP=0.75
;
2. BEVEL, 301
/NAME=(3VD)
/NAME=REFL=(3VM)
/TYPE=30
/SYMBOL=(62,32)
/SYMBOL_REFL=(63,33)
/AFTER_TEXT_SYMBOL=45
/AFTER_TEXT_SYMBOL_REFL=44
/GAP=0.75
/ALPHA=25
/NOSE=2
;
3. BEVEL, 161
/TYPE=16
/VAR_ALPHA
/SYMBOL=63
;
• General
The handling of varying bevel types has a lot in common with the fixed bevel types but is in
general more complicated from different aspects, of course not least when it comes to
evaluation of the bevel and part geometries. Special is also that the final selection of the
bevel type to large extent is automatic.
Basis for the advanced AVEVA Marine handling of continuously varying bevel angles is the
set-up of the rules that should be applied in this context. The bevel definition language has a
number of statement types that deal exclusively with this matter (in addition to the
statements presented above which are used for continuously varying bevels as well). The
names of statements relevant only for varying bevel types all in AUTO_ and they are
specified in detail below, often combined with examples how the system would use the
information in different situations.
The definition of the connection angle in Definitions is supposed to be kept in mind when
studying the statements below.
• AUTO_SET Statement
One customer may have different rules for how the continuously varying bevel types should
be applied in different production lines. E.g. a panel line with special cutting equipment may
have different rules compared to single part cutting, special materials (like aluminium) may
require separate rules, etc. The collection of rules for one such separate type of production
is called a set. The rules for different sets are quite independent of each other (as
independent as if they were used in different companies!).
The AUTO_SET statements define the different sets that are used by a certain customer.
Syntax:
AUTO_SET, <set_No>
[/NAME=<set_name>]
[/CUTOUT=<number>]
[/BRIDGE=<number>]
;
• AUTO_RANGE Statement
Within each type of production line (identified by the "set" as defined above) there may be
different rules depending on the thickness of the plate. E.g. for a given connection angle a
thin plate may have a tight V-type of bevel, a thicker plate may (for the same connection
angle) require a semi-tight Y-bevel. The thickness intervals with separate rules within a
certain "set" are called ranges and are defined by the AUTO_RANGE statement.
Syntax:
<lim_i> Defines the upper limits of interval 1, 2, etc. They should be given
in order of increasing plate thickness. The interval limits will be
included in the lower interval.
The number of ranges within one set is restricted to 10.
SET Defines the set for which the range definition is made. It can be left
out if there is only one set.
The AUTO_RANGE statement must follow the AUTO_SET statement, if any, and can be left
out for a set with the same rules for all thicknesses.
• AUTO_SELECT Statement
In most cases the actual bevel type is selected automatically depending on the set, the
connection angle and the plate thickness. The rules for how this should be done are set up
in the AUTO_SELECT statement.
In general, bevel selection should be set up, covering the whole possible connection
angle interval (-90,+90) for all sets and all ranges Syntax
Syntax:
AUTO_SELECT,
[/SET=<set_No>]
[/RANGE=<range_No> (...)]
<gap_selection> | <angle_selection>
/BEVEL = <code>
[/CASE = <case_No>]
;
SET Defines the set for which the current definition is valid. Must
be given if there is more than one set.
RANGE Defines one or more thickness ranges within the current set
for which the current definition should be used. Must be
given if there is more than one range in the current set.
<angle_selection> Used when the gap condition has not been fulfilled (or not
defined).
The two selection modes are mutually exclusive in one AUTO_SELECT statement.
For more details about the selection criteria, see below.
"Gap selection":
Normally, the main criterion for selection of bevel is the connection angle. Suppose a
situation where a tight V-bevel would normally be selected based on the connection angle.
Further suppose that the angle is so small and/or the plate is so thin that the bevel wedge
becomes very narrow, ('g' in the figure below).
In such a situation it is possible to select the bevel type based on the width of the wedge gap
instead of on the angle. This is the interpretation of "gap selection". Thus, if the wedge gap
is smaller than a specified value, then the bevel type according to the "gap selection" should
be selected. The gap selection always takes over even if an "angle selection" has
been defined for the current angle interval and would have resulted in a different
bevel type.
This facility is mainly used to prevent unwanted bevel cutting when the bevel angle is very
small. The selected bevel type would then normally be a square bevel, e.g. of type 15.
<gap_selection>::= /GAP=<max_gap>
If the gap is smaller than <max_gap> irrespective of direction of the connection angle then
the specified bevel code should be selected.
Angle selection:
The angle selection defines the bevel type that would normally be selected for a given
angle interval. It has the following syntax.
<angle_selection>::=
/INTERVAL =(<low_lim>,<up_lim>)
[/VAR_ALPHA
[/DIFF=<angle_diff>]
[/MIN = <min_angle>]
[/MAX = <max_angle>] ]
[/VAR_BETA
[/DIFF=<angle_diff>]
[/MIN = <min_angle>]
[/MAX = <max_angle>] ]
INTERVAL Defines an interval of connection angles for which the current
definition should be valid.
For positive angles the upper limit will be included in the interval,
the lower limit for negative angles.
This may be used to set a "hard limit" for the bevel angle. Suppose
e.g. that CON varies between -0.5 and +15 degrees and that
normally a tight V-bevel is selected. It might not be possible to
divide the contour of this angle interval into different "segments"
(more details about this will be given in the AUTO_PRIORITY
Statement below). Thus, the tight V-bevel will be selected for this
whole contour. But a V-bevel must not have a negative opening
angle. By setting MIN=0 in this case the connection angle in the
interval [-0.5, 0] will be replaced by 0.
DIFF, MIN and MAX are position dependent, i.e. must follow
directly after VAR_ALPHA (and VAR_BETA, resp , see below).
VAR_BETA Ditto for the opening in the opposite direction, e.g. for X-type
bevels.
Basically the same rules are valid as for VAR_ALPHA (with DIFF,
MIN and MAX).
• AUTO_PRIORITY Statement
The AUTO_SELECT statement specifies the bevel types that should be selected within a
certain set and range as the connection angle varies. It might then happen that along one
contour the angle varies in such a way that the contour should be divided into intervals with
different bevel codes. Suppose that the following AUTO_SELECT statements have been
defined for one range within one set:
AUTO_SELECT /BEVEL=111/ INT=( 0,15), ....;
AUTO_SELECT /BEVEL=222/ INT=(15,30), ....;
AUTO_SELECT /BEVEL=333/ INT=(30,90), ....;
Further suppose that the connection angle varies between 0 and 45 degrees.
The contour should then have been divided into bevel intervals as indicated by the figure
below
However, currently AVEVA Marine has no support for automatic partition of an "unbroken"
contour into intervals with different bevels.
(If, on the other hand, the contour is "broken" into pieces by e.g. notches and cutouts, then
these pieces are treated as independent intervals. If, in the example above, the contour
would have been interrupted by notches the result might have become as shown in the
figure below
Another alternative is also to define different bevel intervals already in the initial bevel
definition in the modelling function.)
We now return to the initial situation in the first figure above. Since AVEVA Marine currently
does not divide the contour into intervals - which bevel code will then be selected? The
default rule for selection is that the bevel code will be selected which covers the largest
angle interval along the contour (however, if one of the bevel codes results from a gap
selection, this bevel code will never be selected).
(The result of the bevel selection may be that the connection angle in the whole interval may
exceed the allowed limits for the bevel code and that is where the MIN/MAX attributes of
the AUTO_SELECT statement will become useful.)
However, the customer may set up rules to control the selected bevel code, and that is done
by the AUTO_PRIORITY statement which is described below.
Syntax:
AUTO_PRIORITY=(<case_1>,<case_2>,....)
[/SET=<set_No>]
[/RANGE=(<range_No> (2...5) )]
;
SET and RANGE must be given if there is more than one of them.
The "cases" (<case_1>,<case_2>, etc.) are those, optionally defined in the
AUTO_SELECT statement. If a combination of cases according to the list in the statement
above has been found along one contour interval then the first of the given cases, i.e.
<case_1> will be used. The number of cases may vary in the range 2 to 5. For a certain
case to be selected there must be a "hit" on all cases in the same statement, otherwise the
default rule above will be applied. The order of the "cases" in the statement is arbitrary
(apart from the first one). Any number of AUTO_PRIORITY statements may be given,
covering all possible combinations of "cases".
/VAR_BETA /MIN=0
/BEVEL=-571;
AUTO_SELECT /SET=2 /RANGE=2 /INT=(-89,40) /VAR_BETA / BEVEL=-
171;
<variant> One of the variants as specified above (in the range 1-4, 9 -
normally relevant only for bevel types for butt welding).
<e-measure> The thickness of the plate on the other side of the joint (in mm).
Always two digits (if <10 then a leading 0 should be added).
The minus sign indicates that the bevel should be seen from the opposite side of the panel
or bracket (i.e. in the direction of the negative w-axis of its local coordinate system). For
stiffeners the bevel code is positive if its positive side is seen from the mould line side (web)
or top (flange), negative otherwise.
If bevel names are used and <variant> and <e-measure> should be given then the following
keywords are available:
Examples:
BEV = -101
BEV = 201107
BEV = 305120
As an alternative the bevel can be given as a name. In that case; variant, e-measure and
side are given with separate keyword.
Examples:
BEV = V50
Remarks:
1. Thus the user defined bevel must be either a 3-digit or a 6-digit number (actually,
decimals would be accepted in the e-measure). However, bevel codes < 100 are
accepted.
2. Along seams in panels the user normally specifies only the bevel code. From customer
defined rules the system will automatically evaluate the variant and the e-measure from
the relative positions of the involved plates.
However, if these parameters are defined directly by the user they will always override
the values that would otherwise have been derived based on the bevel definition file.
3. In other cases (bevel along outer contours, in brackets and in profiles) the variant and
the e-measure must be user supplied. If variant 0 is wanted, of course only the bevel
code need be given.
(An exception is if the keyword EQUAL has been used in the WELD statement. If so,
the variant will be evaluated automatically.)
between them implies chamfer, no chamfer will be shown in the view (unless explicitly
set by the designer).
These features are briefly described below.
• Detail Sketches
A true picture of the cross section of a joint between plates may be generated automatically
(this is done via the menu function Planar > View > Detail > Seam of Hull Modelling). The
detail sketch is evaluated in the position along a seam or outer contour, indicated by the
user. The sketch is shown at scale 1:1.
The figure below shows some typical examples
.
No text and no dimensions are set automatically in the picture. However, it may be the basis
for dimensioning, etc. like all other pictures in a drawing. In butt joints in/between panels
chamfer (if any) will be evaluated automatically. When such a detail view is recreated the
automatically evaluated chamfer between panels will currently be lost.
xbs Text before symbols (xbsu=upper text when split into text above and below
reference line, xbsl for lower), from BEFORE_SYMBOL_TEXT statement.
xbv Bevel text from DRAW_TEXT statement (xbvu and xbvl when split).
When, in case of an asymmetric butt joint, there is a need for individual texts/symbols, let
capital letters of the abbreviations above be used for information related to the side of the
joint, pointed at by the arrow.
Any of the constituents in the specification below may, of course, be empty.
In case of a symmetrical butt joint and in case of fillet joints the most complicated layout of a
bevel note may become as in the figure below
.
Figure 1:57. Bevel note for a symmetrical joint, most general care.
If none of the texts are split into upper and lower parts the note will become simplified as
shown by the next figure
.
Figure 1:58. Bevel note for symmetrical joint, no “under line” text.
The most complex layout of a bevel note for an asymmetric joint would have the following
layout
.
Some typical examples of bevel notes are shown in the pictures below. (However, none of
them contain any text below the reference line, any 'after text' symbol nor any 'weld
processing text'.)
Example:
Al 10 100 2
SOVS 20 100 3
etc.
The name of the table should be assigned to the environment variable SBH_BEVEL_TEXT.
When the bevel is defined in this way, the system may also examine if any of the involved
plate edges should be chamfered (see below). If so, a special chamfer text will be added
after the given text/ selected symbol. The chamfer text will be selected depending on the
side of the plate that should be chamfered.
The appearance and contents of the bevel and chamfer text are controlled by a number of
default parameters:
Note: The feature described is used only for drawing development, i.e. this bevel setting
will not affect the bevelling in plate parts extracted from the panel.
Figure 1:61. Contours required for bevel cutting, most general case.
Moreover, an envelope curve will be generated as the "union" of the other curves. This
curve indicates the area, affected by the complete cutting of the part and thus restricts an
area within which no other part may be nested. This curve is called the bump curve of the
part (in the figure above it is the union of curves C and D).
The figure above is showing two identical plate edges but with two different ways to
calculate the position of the required plate width because of the bevel angle on the lower
side of the plate.
By default, variants are taken care of when calculating the addition of material for the
different bevel types. This means that the upper material curve is positioned according to
point D in the lower view in the figure above.
In older versions of the system, the upper and lower material curves were calculated from
the plate thickness of the bounding plate, i.e. the e-measure of the current bevel. This
means that the upper material curve ends according to the point D in the upper view in the
figure above.
By assigning the value NO to the environment variable
SBH_ADJUST_FOR_BEVEL_VARIANT, the old way of calculating the material curves will
be activated and the upper material curve will be positioned according to the point D in the
upper view in the figure above.
of a bevel, e.g. as in the picture below (the parameter B is never stored, since it can always
be calculated from the other parameters)
.
Example:
2.1 General
AVEVA Marine has different means to compensate for the fact that parts when
manufactured cannot be cut to the nominal dimensions according to the design intent.
There are many reasons for this, e.g.
• Butt welding may require gaps between parts to ensure proper weld penetration. This is
considered in the AVEVA Marine bevel facility
• The fact that parts shrink during welding and other heating processes must be
compensated for. This is considered in the AVEVA Marine shrinkage compensation
facility
• In addition there may be bad fitting caused by accumulated errors in the fabrication and
assembly processes. The traditional way to get a good final fitting is to add extra
material that may be partially removed in the assembly process. This added material is
in AVEVA Marine called excess and compensation.
The two first types of modifications are normally made automatically by AVEVA Marine from
basic rules set up by the customer. In contrast excess and compensation should always be
explicitly given by the designer.
This document gives some notes on excess and compensation in AVEVA Hull. Excess may
be added to both plates and profiles. However, this document concentrates on excess in
plates.
Moreover, the excess type will be stored also in the plate parts so that appropriate actions
can be taken in later assembly stages.
A special symbol font should exist containing the symbols to be used for indication of the
excess types. Its number is 92.
It is the customer's responsibility to see to it that this font exists (if the Hull Modelling default
parameter DRAW_EXCESS>=2) and that it contains the symbols corresponding to the
symbol numbers referred to in the default file of Hull Modelling.
A customer may add new symbols to this font with arbitrary numbers, but these numbers
should be given in the default file of Hull Modelling.
Normally, each symbol should have one connection point which will "snap" to the closest
indicated contour.
If DRAW_EXCESS=3 then the symbol should have a text point as well. Its position is
outside the tail of the symbol.
If no text point has been defined, the text will be located to the right of the actual symbol.
3.1 General
This document describes the set-up and customisation of rules for automatic fillet weld
calculation (Weld Leg Length = WLL) in AVEVA Marine. The full implementation is made in
AVEVA Marine Weld Planning, however some of the functionality is also available when
using AVEVA Marine Planar Hull only.
The automatic calculation is activated when a fillet weld is detected between two steel
structures and no WLL values are given already in the modelling phase. All calculations are
made in two steps. First step is to calculate the weld factor and second step is to translate
this weld factor into a WLL. The rules for calculation of weld factors are stored in objects
called Execution Unit.
3.2.1 General
Execution Units (EU) are objects with rules for weld calculations, stored on a data bank
assigned to the environment variable SB_WELDDB. Rules for different class societies and
ship types are supposed to be stored in different physical data banks and an appropriate
one is to be selected at the project set-up.
3.2.3 Types of EU
EU:s can be of different types as specified below:
• A compartment by name
• A compartment by type
• A geographically given region (i.e. all structures between FR55 and FR60)
• A Reference Surface by name (ex. Main Deck, FR57, etc.). Stored in AVEVA Marine as
Reference Surface Objects (RSO)
• A panel by name
3.2.4 Selection of an EU
The selection of the EU object to be used can either be made automatically or manually.
The automatic selection depends on the geographical position of the two steel structures to
be joined (the abutted and the abutting structure). In the manual method a specific EU
object is selected that shall be used during a certain activity (i.e. when evaluating the welds
of an assembly in the Weld Planning application).
The selection criteria that are used during the automatic selection of an EU object should be
set up and customised by the customer. In this way it will be possible to define the search
order for EU objects (i.e. first compartment, second a reference surface, third
geographical…). The default search order is defined as below:
1. Panel
2. Reference Surface Object (RSO)
3. Compartment
4. Compartment type
5. Geographical
The search order can be changed by setting the environment variable SB_EU_ORDER to
the wanted search order, using the abbreviations P (panel), RSO, C (compartment), CT
(compartment type) and G (geographical) delimited by an underscore (_). The default
search order as shown above would be defined by the following assignment to the
environment variable:
P_RSO_C_CT_G
• The EU Statement
This statement is used to define an EU object. It is given with the name of the object as
argument.
The statement can have the following attributes, defining the type of EU:
· /COMP Compartment
· /GEO Geographical
· /PAN Panel
If the attribute GEO is used, then the attributes /MAX_X and /MIN_X can be used, both with
an X-coordinate as argument, delimiting the geographical region.
Note: Please note that the EU types COMP and COMP_TYPE are not yet supported by the
complete AVEVA Marine software and should therefore not be used for production
• RULE Statement
The RULE statement is used to define the weld factor to be used on a steel structure of a
certain type abutting another steel structure. The attributes /ABUTTED and /ABUTTING are
used, both with a functional description as argument. The weld factor is defined by using the
attribute /WELD_FACTOR with the wanted factor as argument.
A default rule for structures with undefined functional descriptions (non-existing or equal to
zero) is automatically created in all EU objects. This automatically created default rule will
get the weld factor set to one. The default rule can of course be over-ruled by an user-
defined statement (using functional description equal to 0 as the argument of the attributes /
ABUTTED and /ABUTTING).
• DEFAULT Statement
The DEFAULT statement is used to define default weld factors for different types of steel
components, to be used when no specific rule based on functional descriptions can be
found.
The statement can have the following attributes:
• FACTOR2WELD Statement
The FACTOR2WELD statement requires the following attributes:
/THICK
/WELD_FACTOR
/LEG_LENGTH
The /THICK attributes requires the thickness as argument, the /WELD_FACTOR attribute
requires a weld factor as argument and the /LEG_LENGTH attribute shall be given the
WLL as argument.
DEFAULT/STI_END=1/BRA=2/STI_TRACE=2/CLI=1/FLA=2;
EU,'GEO_2'/GEO/MIN_X=50000.1/MAX_X=100000.0;
RULE/ABUTTED=0/ABUTTING=0/WELD_FACTOR=1;
RULE/ABUTTED=15/ABUTTING=12/WELD_FACTOR=3;
RULE/ABUTTED=15/ABUTTING=101/WELD_FACTOR=2;
RULE/ABUTTED=14/ABUTTING=12/WELD_FACTOR=2;
RULE/ABUTTED=14/ABUTTING=9/WELD_FACTOR=1;
DEFAULT/STI_END=1/BRA=2/STI_TRACE=2/CLI=1/FLA=2;
FACTOR2WELD/WELD_FACTOR=1/THICK=5/LEG_LENGTH=2;
FACTOR2WELD/WELD_FACTOR=1/THICK=14/LEG_LENGTH=3;
FACTOR2WELD/WELD_FACTOR=1/THICK=40/LEG_LENGTH=4;
FACTOR2WELD/WELD_FACTOR=2/THICK=5/LEG_LENGTH=3;
FACTOR2WELD/WELD_FACTOR=2/THICK=14/LEG_LENGTH=4;
FACTOR2WELD/WELD_FACTOR=2/THICK=40/LEG_LENGTH=5;
FACTOR2WELD/WELD_FACTOR=3/THICK=5/LEG_LENGTH=5;
FACTOR2WELD/WELD_FACTOR=3/THICK=14/LEG_LENGTH=6;
FACTOR2WELD/WELD_FACTOR=3/THICK=40/LEG_LENGTH=7;
1.1 General
The Hull structure of a ship is built up by in principle two types of basic material, plates
(sheet material) and profiles (bars). Profiles are used to stiffen plates and for support, e.g.
pillars between decks.
However, plates may also be stiffened by "profiles" that are part of the plate itself, e.g. folded
flanges, swaging and corrugation (swaging is in AVEVA Marine the name of small, stiffener-
like corrugation).
It might therefore be meaningful to talk about stiffeners of two categories: those made of
profiles and those that are part of the plate. The partition into sheet material and bar material
is also made less clean by the fact that even if many profiles are fabricated from bars others
consist of assembled strips of plates.
The question about the actual profile standard used in AVEVA Marine is dealt with in a
document of its own. There are also documents describing other more specialised features
of the profile handling, e.g. how parts generated as profiles may be converted into and
manufactured as plate parts.
However, the focus of this document is on how profiles are handled from a modelling point
of view, i.e. how different types of stiffening can be generated in Hull.
From a modelling point of view profiles can be divided into shell profiles and plane panel
profiles.
automatically decide from which shell stiffeners data should be fetched, i.e. in the modelling
work there are never any references directly to shell stiffeners.
Thus, a longitudinal normally consists of a number of shell stiffeners along the same trace
curve or along different trace curves that must not overlap along the x-axis. Similarly,
transversals consist of shell stiffeners organised along frame curves (or other transversal
curves) on the condition that their extension does not overlap when following the curve from
the centre line towards the deck.
The trace curves of shell profiles may be planar or arbitrary hull curves with double
curvature. The actual profile may be planar or twisted (even if the trace curve is planar).
Currently a shell stiffener cannot be knuckled.
1.3.1 Stiffeners
Profiles welded to a plane plate surface are identified as stiffeners. Profiles that, from a
functional point of view, are flanges (see below) must also be generated as stiffeners if they
are not flat bars.
Stiffeners on type standard brackets are considered to be part of the bracket standards.
They cannot be generated separately as stiffeners but can be modified or deleted as part of
the bracket definition.
Stiffeners may be straight, curved or knuckled.
• Curved Stiffeners
By definition a curved stiffener has a trace curve that is not straight. On the other hand the
cross section perpendicular to the trace curve is always constant and equal to the nominal
dimension of the profile.
This means that a stiffener which is knuckled perpendicular to its trace is a curved stiffener,
not a knuckled stiffener, see the figure below
Curved stiffeners may be set parallel to limits, holes and arbitrary curves stored in the panel.
• Knuckled Stiffeners
Knuckled stiffeners have a diagonal knuckle line, either extending diagonally across the
stiffener or affecting only a part of the stiffener. The knuckle line must not intersect the trace
line of the stiffener. Therefore, the trace line of the knuckled stiffener must always be a
straight line. The figure below shows a couple of typical knuckled stiffeners
.
In such a case the need knuckling will be discovered automatically by the system. The
knuckle line will be diagonally across the stiffener and placed in such a way that the
knuckle line starts at the weld trace in the connection to the shell profile. The knuckle
angle will be calculated automatically.
2. The second case is that an (inclined) stiffener should end (or start) in a given plane,
see the figure below. (AVEVA Marine supports only that the stiffener is knuckled into
one of the principal planes).
The knuckle line will start at the trace at the indicated end of the stiffener and be
calculated so that the "triangular" bent piece of the stiffener is, located in the specified
plane.
The stiffener end and the location plane must be defined by the user.
3. The third case is that the position of the knuckle line is controlled explicitly by the user
as well as the bending angle, see the figure below for a possible case
1.3.2 Flanges
In the Hull application, two different component types are identified as flanges. They are:
• Flat bars - straight or curved - welded to a plate edge along the outer contour of a panel
in a hole or along the free edge of a bracket ("face plates").
A flange may be asymmetrically located relative to the plate.
• Folded (bent) flanges along the outer contour. When a folded flange is generated, the
shape of the plate is modified simultaneously. A folded flange has the function of a
profile, but it is of course no physical bar.
Flanges must be generated as stiffeners if they are not flat bars or if they are not
perpendicular to the plate surface.
Flanges on type standard brackets are considered to be part of the bracket standards.
1.3.3 Pillars
Any profile of any type can be generated as a pillar. However, normally a pillar is a "free"
profile, connected only at its ends. Pillars are typically used to carry decks in open areas,
e.g. on passenger ships.
Pillars, built up by plate parts, must be generated as panels.
1.6 Swaging
There is an additional way to stiffen a plate surface, e.g. to use small corrugations like
profiles. Such corrugations are, in Hull, called swages. From a functional point of view, they
act very much like stiffeners. In Hull Modelling, they are generated as a special type of
component with a statement type of their own, described in Hull / Planar Modelling / Design
Language of Hull Modelling / Swage Statement.
The characteristics of the swage are specified in a user defined external table, a swage
object.
Swages will modify the geometry of the part it is located on. This modification of the
geometry will take place in the splitting to parts. Therefore, the geometry of panels with
swages is according to nominal sizes.
2.1 General
The steel structure of a ship is built up by plates and profiles welded together. The plates are
bought in rectangular pieces and are available in an unrestricted variety of sizes and
thicknesses. As a contrast profiles are traditionally available only in certain shapes, e.g. flat
bars and L-bars (angles), i.e. there is a standard for profile types. For certain profiles types
there is additionally only a restricted set of allowable parameters values.
A rather recent trend in shipbuilding is to use aluminium for certain types of vessels instead
of - or as a complement to - steel. Since profiles in aluminium are fabricated by extrusion
new shapes can rather easily be fabricated. Because of the flexibility these profile may differ
considerably from traditional profile types and even combine the function of plate and
stiffener into one object.
The purpose of this document is to describe how the profile standard is implemented in
AVEVA Hull and how it can be used and controlled.
2.2 Definition
A profile in AVEVA Marine is a bar with constant cross-section along the whole bar - apart
form the treatment at the ends of the profile (in AVEVA Marine called endcutting). In
principle the endcuts may only reduce the cross-section, i.e. cut off material from the
constant cross-section bar. However, there are some exceptions to this. Certain endcut
types for flat bars may actually expand outside the specified size of the flat bar. However,
this is an exception and can be used only if the profile is converted to a plate part for
manufacture.
In addition to the profile types listed in the table there are some optional profile variants
available.
Flat bars:
In addition to the flat bars there is also a profile type 11 which has the same properties as a
profile type 10. The only exception for a profile type 11 is that this one can not be converted
into a plate part in the production programs.
Bulb bars:
Profile type 21 is a special Polish variant of the ordinary bulb bar. If used in combination with
any of the environment variables SBH_RUSSIAN_BULB, SBH_CHINESE_BULB or
SBH_JAPANESE_BULB this profile type may be used for the type of bulb bar used in
Russia, China or Japan.
Profile type 23 is the big type of welded bulb bar with a constant bulb size that is
manufactured by the INEXA steel mill and sold under the product name Jumbo Bulb Flat.
Additional U-bar:
In addition to the U-bar with type number 50 there is one additional type of U-bar available
with different thickness in web and flanges. The type number of this U-bar is 59. (However,
most probably it is not used in shipbuilding.)
Figure 2:1. Reference point and mould plane for profiles used as Stiffeners
The position of the reference point for some profile types used for pillars are illustrated in
relation with the specification of the pillar statement in Hull Planar Modelling, Design
Language of Hull Modelling, Pillar Statement.
3.1 Background
AVEVA Marine has a set of predefined and reserved profile types. Certain of these, namely
I- and U-bars, are picked by giving only nominal sizes (i.e. the nominal height and
sometimes - when several different profiles have equal height - the flange width). AVEVA
Marine has a number of built-in tables for these profile types dimensions according to DIN-
standards.
This appendix describes a facility that allows a customer to set up his own tables to replace
the defaults for these profile types, i.e. for the profile types 50 through 59. It is possible to
redefine any of the profile types and still use the defaults for others.
3.2.1 General
The definition of the profiles takes place via an ordinary text file, created and maintained in
the standard editor of the computer system.
The name of the file can be selected quite freely and its total name (path+name) should be
assigned to the environment variable SBH_I_U_BARS.
.
.
.
TYPE This statement indicates the start of a definition of a certain profile type.
<proftype> can be any type of 50, 51, 52, 53, 54, 55 and 59.
The text given as a comment after the TYPE statement is the customer
description of the profile type and is not used by AVEVA Marine.
ANGLE This statement sets the flange inclination of the lower inner surface of the
flange and will be valid for all following profiles until the next ANGLE- or
TYPE-statement. Default value after a TYPE-statement is 0. This
statement is optional and may be omitted as well as given once for every
line of profile data.
The parameter statements have no statement keyword but contain only the parameters
controlling the shape of the profile section.
<H> Height of the profile. This is the actual height of the profile and not the
nominal height (if different)
<B> Width of the profile
<Tw> Thickness of the web
<Tf> Thickness of the flanges
<R1> Radius between web and flange
<R2> Second radius (interpretation varies between profiles)
The parameter lines following the TYPE statement specify a number of occurrences of this
profile type. There are no restrictions as to the number of lines specifying profile
dimensions, i.e. any number of profiles may be defined. The measures may be given in
imperial units according to AVEVA Marine standards. The lines need not be sorted on
dimensions.
The types 50, 51 and 59 must have six parameters, while 52, 53, 54 and 55 have only five.
3.2.3 Example
Below you find an example of a profile definition file
Example:
Example:
4.1 Background
When generating profiles (shell stiffeners, stiffeners, flanges and pillars) in the AVEVA Hull
application the profile type and parameters are supposed to be in accordance with the
standards of AVEVA Marine. The facility described in this document is used to define the
subset of profile types and parameters that are used in a certain project. Those defined in
this way will become available for interactive picking in the modelling of profiles.
4.2.1 General
The selection of the active profiles takes place via an ordinary text file, created and
maintained in the standard editor of the computer system.
The name of this file can be selected quite freely and its total file specification should be
assigned to the environment variable SBH_PROF_CTRL.The file is normally supposed to
be stored in the default directory of the current project.
250, 120, 12
350, 150, 12
TYPE = 31 ’L-bar’
150, 90, 10, 12
200, 100, 10, 15
250, 120, 12, 20
350, 150, 12, 20
TYPE = 40 ’T-bar’
350, 150, 10, 12
450, 200, 12, 15
550, 200, 12, 20
TYPE = 43 ’T-bar’
350, 150, 10, 12
450, 200, 12, 15
550, 200, 12, 20
The keyword TYPE is the profile type as defined in the AVEVA Marine standard.
The text on the same line as the TYPE keyword is the customer description of the profile
type. This text will appear on a menu when creating stiffeners interactively.
The lines following the TYPE keyword select a number of dimensions for the current profile
type. The parameters should be given in the same order as they are entered in modelling
input. There is no restriction as to the number of lines selecting profile dimensions.
4.3 Remark
1. The hull utility program inithull may be used to check the profile control file.
2. The effect of this set-up is only that the specified profile types and parameters may be
picked interactively from list. The designer may, however, explicitly define arbitrary
occurrences of all profile types supported by AVEVA Marine, independently of the
profiles specified by this facility.
5.1 Background
When generating the hull model it is recommended to use topological references to as large
an extent as possible. This is valid also for profiles and a profile is often generated by
connection of the ends to another profile or to a surface.
The detailed nature of the end connection of profiles is controlled by two separate factors,
the connection code and the endcut code. (Moreover, the endcut code and the
connection code in combination control the selection of symbols at the ends of stiffeners in
drawings).
The endcut code with additional parameters controls the end treatment of the bar. An
excessive standards for endcuts can be found in Endcut Standards.
The connection code defines the position of the end of the profile relative to the
component it is connected to, e.g. butting/overlap/clearance and possibly offsets of the
mould lines of involved profiles. AVEVA Hull has an in-built standard set of connection codes
as documented below.
This guide describes how a customer can create a set of connection codes of his own, used
in parallel with, or overriding, the in-built standards.
5.2.1 General
The definition of connection codes takes place via an ordinary text file, created and
maintained in the standard editor of the computer system.
The name of a connection code file can be selected quite freely and its total file specification
should be assigned to the environment variable SBH_CONCODES.
<user code> is a number in the range 1-9999 that should be used by the designer. It
must be unique within the file but may very well be equal to one of the default codes. In that
case the standard code is redefined.
<type> defines the main type of connection. A picture of each type of connection is
enclosed below.
<type>=1 connect to the edge of another profile with the material (flange) in the same
direction as the current profile.
The table below shows the in-built connection codes of type 1 without any offset, sorted on
gap..
Dist Code
0 4
20 30
25 44
30 83
50 3
60 35
75 2
85 36
100 1
125 37
150 38
175 39
200 41
225 42
250 43
The table below shows the in-built connection codes of type 1 with tight connection (dist=0)
and offset, sorted on offset.
Offset Code
5 5
8 6
10 7
12 8
15 9
<type>=2 connect to profile edge, but with the material in different directions.
The table below shows those in-built connection codes of type 2 that overlap the profile they
are connected to (i.e. have a negative value of dist). They have no offset. They are sorted
on overlap.
Overlap Code
30 81
40 31
50 13
65 46
70 82
75 47
100 20
150 21
200 22
250 23
300 24
350 25
400 26
450 27
500 28
550 29
600 30
The table below shows the in-built connection codes of type 2 that do not overlap but has a
gap relative to the profile connected to, sorted on gap. They have no offset.
Dist Code
40 33
50 12
75 11
100 10
<type>=3 connect the end of one profile to the flat side of another profile (or possibly to
the outer contour of the panel).
The table below shows the in-built connection codes of type 3, sorted on gap.
Dist Code
0 15
10 85
15 86
20 87
30 88
40 19
45 25
50 14
75 16
85 49
100 17
150 18
150 38
175 39
200 41
225 42
250 43
<type>=4 connect the profile end to the end of another profile. The default code for this is
40 (tight connection).
<type>=5 connect the end of a profile to surface. The table below shows the in-built
connection codes of type 5, sorted on gap.
Dist Code
0 70
50 65
75 64
100 62
200 59
250 58
300 57
350 56
400 55
450 54
500 53
550 52
600 51
<dist> Distance between the profile end and the component it is connected to.
> 0 Gap (clearance)
= 0 Abutting
< 0 Overlap
<dist> is irrelevant for <type>=4.
<dist> <=0 for <type> >=3.
<offset> Offset of the planes of the profiles. Relevant only for <type>=1.
>0 Offset in the direction of the material (flange) of the profile to which
the connection takes place
<0 In the opposite direction.
5.2.3 Example
The input file below is an example of the input required to establish the default (= in-built)
connection standards in the above tables. As the in-built standard is very unstructured a
customer may create his own, better structured standard, e.g. 100, 125, 130, 150 etc. for
connection codes of type 1, etc.
1 1 100 0
2 1 75 0
3 1 50 0
4 1 0 0
5 1 0 5
6 1 0 8
7 1 0 10
8 1 0 12
9 1 0 15
10 2 100 0
11 2 75 0
12 2 50 0
13 2 -50 0
14 3 50 0
15 3 0 0
16 3 75 0
17 3 100 0
18 3 150 0
19 3 40 0
20 2 -100 0
21 2 -150 0
22 2 -200 0
23 2 -250 0
24 2 -300 0
25 2 -350 0
26 2 -400 0
27 2 -450 0
28 2 -500 0
29 2 -550 0
30 2 -600 0
31 2 -40 0
32 1 40 0
33 2 100 0
34 3 125 0
35 1 60 0
36 1 85 0
37 1 125 0
38 1 150 0
39 1 175 0
40 4 0 0
41 1 200 0
42 1 225 0
43 1 250 0
44 1 25 0
45 3 25 0
46 2 -65 0
47 2 -75 0
49 3 85 0
51 5 600 0
52 5 550 0
53 5 500 0
54 5 450 0
55 5 400 0
56 5 350 0
57 5 300 0
58 5 250 0
59 5 200 0
61 5 150 0
62 5 100 0
64 5 75 0
65 5 50 0
70 5 0 0
80 1 20 0
81 2 -30 0
82 2 -70 0
83 1 30 0
85 3 10 0
86 3 15 0
87 3 20 0
88 3 30 0
5.2.4 Remark
The utility program inithull may be used to check a newly established connection code for
correctness.
The connection codes established via this facility become available for interactive picking
when creating profiles in planar or curved hull modelling. The connection codes will be
presented in a list box. If there are no customer defined connection codes, no list box
appears. To become available in this way also the in-built connection codes will have to be
redefined by the connection file.
6.1 General
When a profile is manufactured, e.g. by cutting of a raw bar, the ends of it must normally be
prepared to get a suitable shape corresponding to its intended use. The shape of the end of
profiles is in AVEVA Marine called the endcut of the profile.
The total concept of profile endcut in AVEVA Marine is the subject of this guide. It describes
general principles and also how and to what extent the existing endcut standard can be
adapted to a certain customer's needs.
The shape of this and all other endcuts is controlled by three different types of data items.
1. The endcut type (in the example above the endcut type is 11).
2. A number of implicitly defined parameters with standard values. The parameters that
may have standard values are individual to a certain endcut type. These parameters
have a restricted number of values and each combination of them is identified by an
endcut code. The standardised parameters are either radii or fixed angles of the endcut
and they cannot be given explicitly by the designer but are selected via the endcut
code. In the figure above R1 and R2 are such parameters.
3. A number of additional parameters which may take any value and which are explicitly
given by the designer or automatically calculated by the system.
In the example above V is such a parameter. These parameters are given as explicit
complements to the endcut code.
Endcut type: 11
Code R1 R2
1100 0 0
1102 0 35
... ... ...
1110 35 0
1112 35 35
... ... ...
The standardised parameters of the endcut codes are set up in an endcut table, stored in
the data bank associated with SB_OGDB and created and maintained by the utility program
inithull.
The angle parameters always come last in the parameter list and are almost always
optional. If they are not given they will be calculated automatically by the system if the profile
end is connected. Otherwise they will by default be 90 degrees. If the designer explicitly
assigns the angles the given values will take over the automatically calculated ones.
The user given parameters are normally not changed. An exception is the a-measure of
certain endcuts.
• Selection Rows
In a selection row <type> is the endcut type (i.e. in the range 10-326). This means that there
is only one selection row for each endcut type. The number of parameters is fixed and must
be exactly 9 and the parameters are selection codes, valid for each of the resulting
parameters according to the list above in the given order, i.e. A, B, C, etc.
Note: In practice, the selection rows must always be set-up by AVEVA and should never be
changed by the customer.
• Parameter Rows
The parameter row specifies the in-built parameters associated with a certain endcut code,
typically notch radii and fixed angles. <type> is the endcut code. Thus there must be exactly
one parameter row for each endcut code.
When a customer wants to add a new endcut code, i.e. a new instance of an endcut type,
this is done by adding a new parameter row for the new endcut code. Most conveniently this
is done by copying one of the existing rows belonging to the current type and modifying the
relevant parameter(s).
The number of parameters may vary. Currently the maximum number is 4. (Traditionally, at
least three (3) parameters have been given and irrelevant parameters have been defined as
-1, but that is no longer necessary). The interpretation of each parameter is controlled by the
selection codes in the selection row of the endcut type of which the current endcut code is
an instance.
If the parameter defines a notch radius but the notch should be a sniped corner the size of
the snipe (KS notch) is indicated by a negative value.
The order between the records is in principle free, but the selection row should be given
before the parameter row belonging to the same type. There are two recommended options:
1. To give all selection rows first (sorted on type) and then all the parameter rows, sorted
on endcut code.
2. A selection row is immediately followed by its parameter rows.
It is a matter of taste which option is preferred.
• Selection Code
The selection code (SC) is an at most four-digit integer (=XYZW) which, depending on its
position in the selection row, is valid for a certain of the resulting geometry parameters. If the
selection code consists of several digits it must be interpreted from right to left, sometimes in
several steps. The parameters should also be evaluated in the order A, B, C, etc. since one
evaluated parameter may be used in the evaluation of a following one. Missing leading
digits in a positive selection code should be interpreted as zeroes, e.g. X=0, Y=0, Z=1 and
W=0 for selection code 10.
For parameters whose selection code is negative the corresponding parameter value will be
set to 0. Otherwise, the parameters will be initialised as follows:
• A is set = acut,
• B is set = bcut,
• C is set = ccut.
However, these values may be changed by the selection code as described below.
The significance of the different digits is:
W If the current parameter value is still zero after the initial setting and W>0, then
fetch the value from the parameter row of the current endcut code. Fetch it from the
column within this row indicated by W.
Z If Z>0 then fetch the value from acut (bcut, ccut), if Z = 1 (2, 3).
Y Has different significance for different parameters (when >0):
=1 V1: Set V1 = α1, if α1>0, otherwise V1 = 90.
=2 V2: Set V2 to the value indicated by W, if this value is less than 90,
otherwise set V2 = α2 (if α2>0, otherwise V2 = 90).
=3 There are conditions in two steps for the different angles.
V2,V3: If abs (ccut - bprof) < 0.1 then set V2 =V3 = 0.
C,V2,V3: If V2 + V3 = 180 and α2 + α3 >=180 then set parameter C =
bprof and V2 = V3 = 0.
6.5 Example
Below you will find the selection row for endcut type 22 followed by the parameter row for
endcut code 2211.
Type A B C R1 R2 V1 V2 V3 V4
601 22 9 10 1021 -1 1 -1 100 202 -1 -1
...
601 2211 2 35 30
...
Suppose that the stiffener end has been generated by the following input:
CUT = 2211, 150, 50, 80(*) (* Normally calculated automatically)
The result will be as illustrated by Figure 6:3.: Explicit parameters for creation of endcut type
22 below.
A (Selection code = 10, i.e. X=0, Y=0, Z=1, W=0). Since Z=1, set A = acut
(150)
B (Selection code = 1021). First set B = bcut (=50). Since B now has a value,
disregard the value indicated by W (and X). (If bcut had been zero, then B would
have been set equal to R1 (=35)).
V1 (Selection code = 100). Since Y=1 set V1 = α1 (=80). Since X=0 no further
change.
If a customer wants to change one of the standard values, he should proceed like this:
1. Identify the parameter you want to change (suppose e.g. that you want to change V2
from 30 to 45 degrees).
2. Examine the last digit of the selection code for that parameter (in this case 202). Look
up parameter 2 in the parameter row for endcut code 2211 and change 30 to 45.
7 Endcut Standards
7.1 General
The general principles of the handling of endcuts in AVEVA Marine have been described in
a separate document. As stated there a number of endcut types are built into AVEVA Marine
but for an endcut standard to become available for use instances of the endcut types must
be established. These instances (end cut codes) are stored in an endcut table. A definition
file for the creation of a standard endcut table is delivered along with the Hull application to
assist a customer in creating a first endcut standard. By making changes (and editing in
general) of this file a customer may adapt the default standard to his needs to the extent
described in the document referred to and in paragraphs below.
This document contains an overview of all the endcut types currently supported by AVEVA
Marine and documents also the characteristics of the endcut codes in the standard set-up of
AVEVA Marine.
Column 1 contains always the endcut code (i.e. an instance of the endcut type) with a list of
parameters that may be explicitly given. Parameters within brackets ( [… ] ) are optional
and need not be given.
As mentioned above parameters that are connection angles are normally calculated
automatically by the system (in case the profile end is connected to another part) and need
not be given. They are always optional even if not surrounded by brackets.
Columns 2, 3 etc. specify those of the endcut parameters that are set-up in the endcut table.
They can normally not be overridden by the end user with the exception of flange angles
angle 90 degrees in the endcut table.
E.g. specifying the input CUT=2100,0,75 means that α2 will be set to 75 instead of the
default 90 degrees.
Example:
Suppose that a customer needs an endcut type 11 with R1=40 and R2=0. He has then two
options:
1. Modify the definition of e.g. endcut code 1110 so that R1 is changed from 35 to 40.
2. Define a new endcut code, e.g. 1150, with R1=40 and R2=0.
Remark:
Currently the following rule should be adhered to when creating new endcut codes: For
endcut types 21, 22, 26, 27, 28, 31, 32, 35 and 36 endcut codes ending in 0 should always
have a default flange angle 90 degrees, those not ending in 0 should have a flange angle
with a different value.
Type 10:
Code, parameter
1000,a,b[,c,d]
Type 11:
Code, parameter R1 R2
1100[, α1] 0 0
1102[, α1] 0 35
1104[, α1] 0 50
1105[, α1] 0 60
1106[, α1] 0 75
1110[, α1] 35 0
1112[, α1] 35 35
1114[, α1] 35 50
1115[, α1] 35 60
1116[, α1] 35 75
1120[, α1] KS50 KS50
1122[, α1] 50 35
1124[, α1] 50 50
1125[, α1] 50 60
1126[, α1] 50 75
1130[, α1] 75 0
1132[, α1] 75 35
1134[, α1] 75 50
1135[, α1] 75 60
1136[, α1] 75 75
1140[, α1] 60 0
1142[, α1] 60 35
1144[, α1] 60 50
1145[, α1] 60 60
1146[, α1] 60 75
1190[, α1] KS10 0
Type 12:
Code, parameters R1
Type 13:
Code, parameters R1 α2
Type 14:
Remark:
If c is not given then c=(H-b)/2
Code, parameters α2
Type 15:
Code, parameter R1
1500, a 20
1510, a 35
LType 16:
Code, parameters R1
1600, a, b 20
1610, a, b 35
Type 17:
Code, parameters R1 α1
1700 20 18
1710 20 30
1720 35 18
1730 35 30
Type 18:
Remark:
If R1 = 0 then all parameters R1, a, b, c, will be set to half the profile height (H / 2).
If c = 0 or not given then c will be set to half the profile height (H / 2).
If b = 0 or not given then b will be set to the same value as a.
If a = 0 or not given then a will be set to the same value as the radius R1.
Code, parameters R1
1800[, a, b, c] 0
1810[, a, b, c] 35
1820[, a, b, c] 50
1830[, a, b, c] 100
Type 19:
Code, parameters α2
Type 61:
Code, parameters R1
Type 62:
Code, parameters R2
Type 63:
Code, parameters R1 α2
Type 64:
Code, parameters R1 α2
Type 65:
Remark:
R2 is calculated automatically from in-built rules.
Code, parameters R1 R2 α2
Type 66:
Code, parameters α2
Type 67:
Code, parameters α2
Type 68:
Code, parameters R1 R2 α2
Type 69:
Code, parameters R1 R2 α2
Type 76:
Code, parameters R1 R2
7610, [b,c,a1,a3] 15 300
7620, [b,c,a1,a3] 25 300
7630, [b,c,a1,a3] 50 300
Type 101:
Remarks:
1. If c=0 (not given) then c=(b -H)/2
2. NB! This endcut may only be used for flanges (face plates) to be fabricated as plate
parts.
Code parameters α2 α3
10100, a, b[, c ] 18 18
10110, a, b[, c ] 18 30
10120, a, b[, c ] 30 18
Type 102:
Remarks:
1. If b=0 (not given) then b=H
2. If c=0 (not given) then c= (H -b)/2
3. A negative value of c is allowed
4. NB! When c<0 this endcut may only be used for flanges (face plates) to be fabricated
as plate parts.
Code, parameters R1 R2 α2 α3
10200, a, b, c 30 30 18 18
10210, a, b, c 30 30 30 30
10220, a, b, c 50 50 45 45
Type 103:
Remark:
This is very similar to endcut type 14, the difference is that α2 and α3 may be different.
Code, parameters α2 α3
Type 104:
Remarks:
1. If c=0 or not given then c=(b -H)/2
2. If R1=0 then “upper” edge will be straight. Similarly for “lower” edge if R2=0 or not
given.
3. NB! This endcut may only be used for flanges (face plates) to be fabricated as plate
parts.
Code parameters
Type 105:
Remark:
If c = 0 or not given then c will be set to H - 2*b.
Code, parameters
Type 106:
Code, parameters R1 R2
Type 107
Code, parameters R1
Type 108
Code, parameters R1 R2
Type 112:
Remark:
If b=0 (or not given) then b = H -R2.
Code, parameters R1 R2
Type 113:
Remark:
b may be left out.
Code, parameters R1 R2 α2
11301[, b] 25 25 18
11302[, b 25 25 30
11303[, b] 25 25 45
Type 114:
Remark:
If c=0 (or not given) then c = ( H -b)/2
Code, parameters R1 α2
Type 115:
Remark:
The radius R is defined by the distance a and the angle α1.
Code, parameters
Type 116:
Remark:
If b < = 5 the KS10 notch will not be created.
Code, parameters R1 R2
Type 117:
Code, parameters R1
Type 118:
Remark:
R1 defines two identical arc segments.
Code, parameters R1
Type 20:
Code, parameters
2000, a, b[, c, d]
Type 21:
Code, parameters R1 α2
2111[, α1] 35 30
2120[, α1, α2] 50 90
2121[, α1] 50 30
2130[, α1] 75 90
2131[, α1] 75 30
2140[, α1, α2] 60 90
2141[, α1] 60 30
2190[, α1, α2] KS10 90
2191[, α1] KS10 30
Type 22:
Remarks:
1. If b=R1 then b need not be given
2. If b>H/2 then a1 should be given instead of a
Code, parameters R1 α2
Type 23:
Code, parameters R1 α2 α3
Type 24:
Code, parameters R1 α2
Type 25:
Code, parameters R1 α2 α3
Type 26:
Remark:
A given (or calculated) α2 will override the default value in case this is 90.
Code parameters R1 α2 R2
Type 27:
Remark:
A given (or calculated) α2 will override the default value in case this is 90.
Code, parameters R1 R2 α2
Type 28:
Remark:
A given (or calculated) α2 will override the default value in case this is 90.
Code, parameters R1 R2 α2
Type 29:
Code, parameters R1 α2
Type 60:
Remark:
A given (or calculated) α2 will override the default value in case this is 90.
Code, parameters R1 α2
6000, a, 20 90
6001, a, 20 30
6010, a, 35 90
6011, a, 35 30
Type 70:
Remark:
The radius R is defined by the distance a and the angle α1.
Code, parameters α2
Type 71:
Remark:
If c is not given (or =0), c will be set equal to the flange width α2 will become irrelevant.
Code, parameters R1 α2 α3
Type 72:
Remark:
If c is not given (or =0), c will be set equal to the flange width α2 will become irrelevant.
Code, parameters R1 R2 α2 α3
Type 73:
Remarks:
1. If c is not given (or =0), c will be set equal to the flange width α2 will become irrelevant.
Code, parameters R1 R2 α2 α3
Type 74:
Code, parameters R1 R2 α2 α3
Remark:
This endcut, which resembles endcut 23, is intended to be used mainly for bulb bars.
Type 75:
Code, parameter R1 a2 a3
7510, b 15 30 18
7520, b 15 90 18
7530, b 15 30 30
7540, b 15 90 30
Type 77:
This endcut type can be used only if two equal bulb bars are connected in a simple 90
degree connection.
Code, parameters R1
7700 0
7710 35
7720 KS10
Type 119:
Code, parameters R1 α2 α3
Type 120:
Code, parameters R1 R2 α2
Type 121:
Code, parameters R1 α3
12100, c[, α1, α2] 0 18
12101, c[ ,α1, α2] 0 30
12102, c[, α1, α2] 0 45
Code, parameters R1 α3
12110, c[, α1, α2] 35 18
12111, c[, α1, α2] 35 30
12112, c[, α1, α2] 35 45
12120, c[, α1, α2] 50 18
12121, c[, α1, α2] 50 30
12122, c[, α1, α2] 50 45
12130, c[, α1, α2] 60 18
12131, c[, α1, α2] 60 30
12132, c[, α1, α2] 60 45
12140, c[, α1, α2] 75 18
12141, c[, α1, α2] 75 30
12142, c[, α1, α2] 75 45
12190, c[, α1, α2] KS10 18
12191, c[, α1, α2] KS10 30
12192, c[, α1, α2] KS10 45
Remark:
If c is close to the web thickness or close to the flange width then use type 21.
Type 122:
Code, parameters R1 α2
Type 123:
Remark:
R1 defines two identical arc segments.
Code, parameters R1 α2
Type 124:
Code, parameters R1 R2 α2 α3
Type 125:
Remarks:
1. The small figure to the right shows how the geometry of this endcut may be controlled
when the endcut is drawn before the upper part of the web has been bent down.
Observe that R2 contains composed information in this case.
2. If c=0 the flange will have a straight cut and α2 becomes meaningless.
Code, parameters R1 R2 α2 α3
Type 126:
Code, parameters R1 α3
Remark:
If c is close to the web thickness or close to the flange width then use type 26.
Type 127:
Code, parameters R1 α2
Type 128:
Code, parameters R1 R2 α2
12800, a, b[, α1] 0 30 18
12810, a, b[, α1] KS10 30 18
12820, a, b[, α1] 10 30 18
Type129:
Code, parameters R1 α3
12900, a, b, c[, α1, α2] 0 18
12901, a, b, c[, α1, α2] 0 30
12902, a, b, c[, α1, α2] 0 45
12910, a, b, c[, α1, α2] 35 18
Remark:
If c is close to the web thickness or close to the flange width then use type 22.
Type 40:
Remarks:
1. This endcut type is intended for asymmetric T-bars (profile type 35) with a
comparatively small "overshoot" of the flange (less than half the flange width) on the
mould line side of the web
2. α 4 is by default 90 degrees. Any given value will override this default value.
Code, parameters R1 α2 α3
Type 41:
Remarks:
1. This endcut type is intended for asymmetric T-bars (profile type 35) with a
comparatively large "overshoot" of the flange (larger than half the flange width) on the
mould line side of the web.
2. α 4 is by default 90 degrees. Any given value will override this default value.
Code, parameters R1 α2 α3
Type 42:
Remarks:
1. This endcut type is intended for asymmetric T-bars (profile type 35) with a
comparatively small "overshoot" of the flange (less than half the flange width) on the
mould line side of the web
2. α 4 is by default 90 degrees. Any given value will override this default value.
Code, parameters R1 α2
Type 43:
Remarks:
1. This endcut type is intended for asymmetric T-bars (profile type 35) with a
comparatively large "overshoot" of the flange (larger than half the flange width) on the
mould line side of the web.
2. α 4 is by default 90 degrees. Any given value will override this default value
.
Code, parameters R1 α2
Type 132:
Remarks:
1. If c is not given (or =0), c will be set equal to the flange width α2 will become irrelevant
and the flange angle will be set to α4.
2. This endcut type is intended for asymmetric T-bars (profile type 35) with a
comparatively small "overshoot" of the flange (less than half the flange width) on the
mould line side of the web.
Code, parameters R1 α2
Type 133:
Remarks:
1. If c is not given (or =0), c will be set equal to the flange width α2 will become irrelevant
and the flange angle will be set to α4.
2. This endcut type is intended for asymmetric T-bars (profile type 35) with a
comparatively small "overshoot" of the flange (less than half the flange width) on the
mould line side of the web.
Code, parameters R1 α2
Type 134:
Remarks:
1. If c is not given (or =0), c will be set equal to the flange width α2 will become irrelevant
and the flange angle will be set to α4.
2. This endcut type is intended for asymmetric T-bars (profile type 35) with a
comparatively large "overshoot" of the flange (larger than half the flange width) on the
mould line side of the web.
Code, parameters R1 α2
Type 135:
Remarks:
1. If c is not given (or =0), c will be set equal to the flange width α2 will become irrelevant
and the flange angle will be set to α4.
2. This endcut type is intended for asymmetric T-bars (profile type 35) with a
comparatively large "overshoot" of the flange (larger than half the flange width) on the
mould line side of the web.
Code, parameters R1 α2
Type 136:
Remarks:
1. If c is not given (or =0), c will be set equal to the flange width α2 will become irrelevant
and the flange angle will be set to α4.
2. The small sketch to the right shows how a small notch may be defined below the end of
the flange
3. This endcut type is intended for asymmetric T-bars (profile type 35) with a
comparatively large "overshoot" of the flange (less than half the flange width) on the
mould line side of the web.
Code, parameters R1 R2 α2
Type 137:
Remarks:
1. If c is not given (or =0), c will be set equal to the flange width α2 will become irrelevant
and the flange angle will be set to α4.
2. The small sketch to the right shows how a small notch may be defined below the end of
the flange.
3. This endcut type is intended for asymmetric T-bars (profile type 35) with a
comparatively large "overshoot" of the flange (less than half the flange width) on the
mould line side of the web.
Code, designation R1 R2 α2
Type 138:
Remarks:
1. If c is not given (or =0), c will be set equal to the flange width α2 will become irrelevant
and the flange angle will be set to α4.
2. The small sketch to the right shows how a small notch may be defined below the end of
the flange.
3. This endcut type is intended for asymmetric T-bars (profile type 35) with a
comparatively small "overshoot" of the flange (less than half the flange width) on the
mould line side of the web.
Code, parameters R1 R2 α2
Type 139:
Remarks:
1. If c is not given (or =0), c will be set equal to the flange width α2 will become irrelevant
and the flange angle will be set to α4.
2. The small sketch to the right shows how a small notch may be defined below the end of
the flange.
3. This endcut type is intended for asymmetric T-bars (profile type 35) with a
comparatively small "overshoot" of the flange (less than half the flange width) on the
mould line side of the web.
Code, parameters R1 R2 α2
Type 153:
Remarks:
1. If c is not given (or =0), c will be set equal to the flange width α2 will become irrelevant
and the flange angle will be set to α4.
2. The small sketch to the left shows the parameters of the corner notch.
3. This endcut type is intended for asymmetric T-bars (profile type 35) with a
comparatively small "overshoot" of the flange (less than half the flange width) on the
mould line side of the web.
Code, parameters R1 R2 α2
Type 157:
Remarks:
1. If c is not given (or =0), c will be set equal to the flange width α2 will become irrelevant
and the flange angle will be set to α4.
2. The small sketch to the left shows the parameters of the corner notch.
3. This endcut type is intended for asymmetric T-bars (profile type 35) with a
comparatively large "overshoot" of the flange (more than half the flange width) on the
mould line side of the web.
Code, parameters R1 R2 α2
Type 160:
Remarks:
1. If c is not given (or =0), c will be set equal to the flange width α2 will become irrelevant
and the flange angle will be set to α4.
2. This endcut type is intended for asymmetric T-bars (profile type 35) with a
comparatively small "overshoot" of the flange (less than half the flange width) on the
mould line side of the web.
Code, parameters R1 R2 α2
Type 161:
Remarks:
1. If c is not given (or =0), c will be set equal to the flange width α2 will become irrelevant
and the flange angle will be set to α4.
2. The small sketch to the left shows the parameters of the corner notch.
3. This endcut type is intended for asymmetric T-bars (profile type 35) with a
comparatively small "overshoot" of the flange (less than half the flange width) on the
mould line side of the web.
Code, parameters R1 R2 α2
Type 162:
Remarks:
1. If c is not given (or =0), c will be set equal to the flange width α2 will become irrelevant
and the flange angle will be set to α4.
2. The small sketch to the left shows the parameters of the corner notch.
3. This endcut type is intended for asymmetric T-bars (profile type 35) with a
comparatively small "overshoot" of the flange (less than half the flange width) on the
mould line side of the web.
Code, parameters R1 R2 α2
Type 163:
Remarks:
1. If c is not given (or =0), c will be set equal to the flange width α2 will become irrelevant
and the flange angle will be set to α4.
2. This endcut type is intended for asymmetric T-bars (profile type 35) with a
comparatively large "overshoot" of the flange (more than half the flange width) on the
mould line side of the web.
Code, parameters R1 R2 α2
Type 164:
Remarks:
1. If c is not given (or =0), c will be set equal to the flange width α2 will become irrelevant
and the flange angle will be set to α4.
2. This endcut type is intended for asymmetric T-bars (profile type 35) with a
comparatively large "overshoot" of the flange (more than half the flange width) on the
mould line side of the web.
Code, parameters R1 R1 α2
Type 165:
Remarks:
1. If c is not given (or =0), c will be set equal to the flange width α2 will become irrelevant
and the flange angle will be set to α4.
2. The small sketch to the left shows the parameters of the corner notch.
3. This endcut type is intended for asymmetric T-bars (profile type 35) with a
comparatively large "overshoot" of the flange (more than half the flange width) on the
mould line side of the web.
Code, parameters R1 R2 α2
Type 167:
Remark:
If be equals the profile height aplha3 will be set to 90 deg.
Code, parameters R1 R2 α2 α3
Type 30:
Code, parameters
3000, a, b[, c, d, e, f]
Type 31:
Remarks:
1. A given (or calculated) α4 will override the default value for α2 and α3 in case this is
90.
2. Endcut codes with α2=α3=90 may be used for asymmetrical T-bars as well.
.
Code, parameters R1 α2 α3
Type 32:
Remarks:
1. For this endcut type α2 and α3 are always equal.
2. c is relevant only when α2=α3=90.
3. A given (or calculated) α4 will override the default value of α2/α3 in case this is 90.
4. Endcut codes with α2=α3=90 may be used for asymmetrical T-bars as well.
Code, parameters R1 α2
α3
Type 33:
Code, parameters α2 α3
Type 34:
Remark:
A given (or calculated) α4 will override the default value for α2 and α4 in case this is 90.
.
Code, parameters R2 α2 α3
Type 35:
Remarks:
1. For this endcut type α2 and α3 are always equal.
2. c is relevant only when α2=α3=90.
3. A given (or calculated) α4 will override the default value of α2/α3 in case this is 90.
4. Endcut codes with α2=α3=90 may be used for asymmetrical T-bars as well.
Code, parameters R1 α2
α3
Type 36:
Remarks:
1. For this endcut type α2 and α3 are always equal.
2. c is relevant only when α2=α3=90.
3. A given (or calculated) α4 will override the default value of α2/α3 in case this is 90.
4. Endcut codes with α2=α3=90 may be used for asymmetrical T-bars as well.
Code, parameters R1 α2
α3
Type 37:
Remark:
This endcut type may be used for asymmetric T-bars (profile type 35) as well.
Code, parameters R1 α2
Type 38:
Code, parameters R1 α2 α3
Type 39:
Remark:
If c = 0 or not given then c will be set to the flange width and α2 will become irrelevant. R2
contains encoded information according to the small sketch in the upper left corner. If R2 <
1000 then R2 will define an arc segment.
Code, parameters R1 R2 α2 α3
Type 44:
Remark:
If c = 0 or not given then c will be set to the flange width, α2 will become irrelevant and the
flange angle will be set to α4 (90 by default).
Code, parameters R1 α2
Remarks:
1. The difference between type 45 and type 47 is that type 45 has a temporary bridge, 40
mm wide.
2. These endcut types may be used for asymmetric T-bars as well.
Remarks:
1. The difference between type 46 and type 48 is that type 46 has a temporary bridge, 40
mm wide.
2. These endcut types may be used for asymmetric T-bars as well.
Type 49:
Remark:
If c = 0 or not given then c will be set to the flange width, a2 will become irrelevant and the
flange angle will be set to a4 ( 90 by default).
Endcut codes with a2=a3=90 may be used for asymmetrical T-bars as well.
Code, parameters R1 R2 α2 α3
Type 50:
Remarks:
1. This endcut has a temporary bridge, 40 mm wide.
2. Endcut type 50 may be used for asymmetric T-bars as well.
3. Type 50 is similar to type 46 but the flange extends outside the web in this case.
5060, a, b, c, 1/0,5
Type 81:
Remark:
If c is not given (or =0) then c will be set equal to the flange width and α2 becomes irrelevant
(=90).
Code, parameters R1 α2 α3
Type 82:
Remark:
If c is not given (or =0) then c will be set equal to the flange width and α2 becomes irrelevant
(=90).
Code, parameters R1 R2 α2 α3
Type 83:
Remarks:
1. If c is not given (or =0) then c will be set equal to the flange width and α2 becomes
irrelevant (=90).
2. R1 is calculated automatically depending on H.
Code, parameters R1 R2 α2 α3
Type 130:
Remark:
If c is not given (or =0) then c will be set equal to the flange width and α2 becomes
irrelevant.
Code, parameters R1 α2
Type 131:
Remark:
If c is not given (or =0) then c will be set equal to the flange width and α2 becomes
irrelevant.
Code, parameters R1 α2
Type 140:
Remarks:
1. If c is not given (or =0) then c will be set equal to the flange width and α2 becomes
irrelevant and the flange angle equal to α4 (90 by default).
2. The small sketch to the right shows how R2 controls the small notch at the end of the
flange. Note that R2 contains encoded information.
3. If R2<1000 then the notch will be placed in the upper corner of the web as shown in the
small figure below. Note that R2<0 in this case will produce a sniped corner.
Code, parameters R1 R2 α2
Type 141:
Remarks:
1. If c is not given (or =0) then c will be set equal to the flange width and α2 becomes
irrelevant and the flange angle equal to α4 (90 by default).
2. The small sketch to the right shows how R2 controls the small notch at the end of the
flange. Note that R2 contains encoded information.
3. If R2<1000 then the notch will be placed in the upper corner of the web as shown in the
small figure below. Note that R2<0 in this case will produce a sniped corner.
Code, parameters R1 R2 α2
Type 142:
Code, parameters R1 R2 α2
Remarks:
1. R1 defines two identical notches at the lower and upper corner of the web respectively.
Type 143:
Code, parameters R1 R2 α2
Type 144:
Code, parameters R1 R2 α2
Remarks:
1. R1 defines two identical notches at the lower and upper corner of the web respectively.
Type 145:
Remark:
If c = 0 or not given then c will be set to the flange width, α2 will become irrelevant and the
flange angle will be set to α4 (90 by default).
Code, parameters R1 α2 α3
Type 146:
Remark:
R1 defines two identical arc segments.
If c = 0 or not given then c will be set to the flange width, α2 will become irrelevant and the
flange angle will be set to α4 (90 by default).
Code, parameters R1 R2 α2
Type 147:
Remark:
If c = 0 or not given the c will be set to the flange width, α2 will become irrelevant and the
flange angle will be set to α4 (90 by default).
Code, parameters R1 R2 α2
Type 148:
Remark:
The value given for radius R1 and R2 has the following meaning:
• A negative value indicates a KS-notch.
• A positive value less than 1000 indicates a scallop radius.
• A positive value greater than 1000 indicates a fillet radius. The radius is received by
subtracting 1000.
Note that c contains encoded information. If c < 1000 then c will define an arc segment.
Code, parameters R1 R2 c
Type 158:
Remark:
If c is not given (or =0) then c will be set equal to the flange width and α2 becomes irrelevant
and the flange angle equal to α4 (90 by default).
Code, parameters R1 R2 α2
Type 166:
Remark:
If c is not given (or =0) then c will be set equal to the flange width and α2 becomes irrelevant
and the flange angle equal to α4 (90 by default).
Code, parameters R1 R2 α2
Type 167:
Remark:
If b equals the profile height alpha3 will be set to 90 degrees.
Code, parameters R1 R2 α2 α3
16700, a, b[,α1] 35 20010 18 30
Type 168:
Remark:
If c = 0 or not given then c will be set to the flange width and a2 will become irrelevant. R2
contains encoded information according to the small sketch in the upper left corner. If R2 <
1000 then R2 will define an arc segment.
Code, parameters R1 R2 α2 α3
The figures below associated with each endcut type show one web view and one flange
view of the I-bar.
Type 173:
Remark:
The value given for radius R1 has the following meaning:
• A negative value indicates a KS-notch.
• A positive value less than 1000 indicates a scallop radius.
• A positive value greater than 1000 indicates a fillet radius. The radius is received by
subtracting 1000.
Code, parameters R1 R2
Type 174:
Code, parameters R1 R2
Type 175:
Remark:
The value given for radius R1 has the following meaning:
• A negative value indicates a KS-notch.
• A positive value less than 1000 indicates a scallop radius.
• A positive value greater than 1000 indicates a fillet radius. The radius is received by
subtracting 1000.
R2 contains encoded information according to the sketch above. If R2 < 1000 then R2
defines an arc segment.
Code, parameters R1 R2
Type 176:
Remark:
The value given for radius R1 has the following meaning:
• A negative value indicates a KS-notch.
• A positive value less than 1000 indicates a scallop radius.
• A positive value greater than 1000 indicates a fillet radius. The radius is received by
subtracting 1000.
Code, parameters R1 R2
Type 177:
Remark:
The value given for radius R2 has the following meaning:
• A negative value indicates a KS-notch.
• A positive value less than 1000 indicates a scallop radius.
• A positive value greater than 1000 indicates a fillet radius. The radius is received by
subtracting 1000.
Code, parameters R1 R2
Type 178:
Code, parameters
Type 179:
Remarks:
1. b=0 (or not given) means that b=R2
Code, parameters R2 α2
Type 180:
Remarks:
1. b=0 (or not given) means that b=R1
2. α2=0 means that c becomes irrelevant
Code, parameters R1 α2
Type 181:
Remark:
If c = 0 or not given then c will be set to the value of b.
The value given for radius R1 has the following meaning:
• A negative value indicates a KS-notch.
• A positive value less than 1000 indicates a scallop radius.
• A positive value greater than 1000 indicates a fillet radius. The radius is received by
subtracting 1000.
R2 contains encoded information according to the sketch above. If R2 < 1000 then R2
defines an arc segment.
Code, parameters R1 R2
Type 182:
Remark:
If c = 0 or not given then c will be set to the value of b.
The value given for radius R1 has the following meaning:
• A negative value indicates a KS-notch.
• A positive value less than 1000 indicates a scallop radius.
• A positive value greater than 1000 indicates a fillet radius. The radius is received by
subtracting 1000.
R2 contains encoded information according to the sketch above. If R2 < 1000 then R2
defines an arc segment.
Code, parameters R1 R2
Type 183:
Remark:
The value given for radius R1 has the following meaning:
• A negative value indicates a KS-notch.
• A positive value less than 1000 indicates a scallop radius.
• A positive value greater than 1000 indicates a fillet radius. The radius is received by
subtracting 1000.
R2 contains encoded information according to sketch above. If R2 < 1000 the R2 defines an
arc segment.
Code, parameters R1 R2
Type 184:
Remark:
The value given for radius R1 has the following meaning:
• A negative value indicates a KS-notch.
• A positive value less than 1000 indicates a scallop radius.
• A positive value greater than 1000 indicates a fillet radius. The radius is received by
subtracting 1000.
R2 contains encoded information according to the sketch above. If R2 < 1000 then R2
defines an arc segment.
Code, parameters R1 R2
Type 186:
Code, parameters R1 R2
Type 187:
Code, parameters R2
Type 188:
Remark:
b=0 (or not given) means that b=R1.
Code, parameters R1
Type 191:
Remark:
• If R1 = 0 then notch will be omitted.
• If R1 < 0 then notch will be a KS notch
• If R1 > 0 and R1 < 1000 then notch will be a R notch
• If R1 > 0 and R1 > 1000 then notch will be a fillet notch, where radius = R1-1000
Code, parameters R2 α2
19100, a, [b, c, R1, α4] 60015 18
19110, a, [b, c, R1, α4] 40010 30
Type 192:
Remark:
• If R1 = 0 then notch will be omitted.
• If R1 < 0 then notch will be a KS notch
• If R1 > 0 and R1 < 1000 then notch will be a R notch
• If R1 > 0 and R1 > 1000 then notch will be a fillet notch, where radius = R1-1000
Code, parameters R2 α2
19200, a, [b, c, R1, α4] 20010 18
19210, a, [b, c, R1, α4] 30015 30
Type 193:
Remark:
• If R1 = 0 then notch will be omitted.
• If R1 < 0 then notch will be a KS notch
• If R1 > 0 and R1 < 1000 then notch will be a R notch
• If R1 > 0 and R1 > 1000 then notch will be a fillet notch, where radius = R1-1000
Code, parameters R2 α2
19300, a, [b, c, R1, α4] 16 18
19310, a, [b, c, R1, α4] 26 30
Type 194:
Remark:
• If R1 = 0 then notch will be omitted.
• If R1 < 0 then notch will be a KS notch
• If R1 > 0 and R1 < 1000 then notch will be a R notch
• If R1 > 0 and R1 > 1000 then notch will be a fillet notch, where radius = R1-1000
Code, parameters R2 α2 α3
19400, a, [b, c, R1, α4] 60015 18 40
19410, a, [b, c, R1, α4] 40010 30 60
Type 195:
Remark:
• If R1 = 0 then notch will be omitted.
• If R1 < 0 then notch will be a KS notch
• If R1 > 0 and R1 < 1000 then notch will be a R notch
• If R1 > 0 and R1 > 1000 then notch will be a fillet notch, where radius = R1-1000
• If R1 > 0 and R1 < 1000 then notch will be a R notch
Code, parameters R2
Type 196:
Remark:
• If R1 = 0 then notch will be omitted.
• If R1 < 0 then notch will be a KS notch
• If R1 > 0 then notch will be a R notch
Code, parameters R2 α2
19600, a, [b, c, R1, α4] 16 18
19610, a, [b, c, R1, α4] 26 30
Type 197:
Remark:
• If R2 = 0 then notch will be omitted.
• If R2 < 0 then notch will be a KS notch
• If R2 > 0 then notch will be a R notch
Code, parameters R2 α2 α3
19700, a, [c, α1, α4] 0 15 30
19710, a, [c, α1, α4] 30 25 45
19720, a, [c, α1, α4] -30 25 45
Type 198:
Remark:
• If R1 = 0 then notch will be omitted.
• If R1 < 0 then notch will be a KS notch
• If R1 > 0 then notch will be a R notch
Code, parameters R1 α2 α3
19800, a, [c, α4] 0 15 30
19810, a, [c, α4] 30 25 45
19820, a, [c, α4] -30 25 45
Type 199:
Remark:
• If R1 = 0 then notch will be omitted.
• If R1 < 0 then notch will be a KS notch
• If R1 > 0 and R1 < 1000 then notch will be a R notch
• If R1 > 0 and R1 > 1000 then notch will be a fillet notch, where radius = R1-1000
Code, parameters R2 α2 α3
19900, a, [b, c, R1,α4] 60015 85 40
19910, a, [b, c, R1, α4] 40010 30 60
Type 200:
Remark:
• If R1 = 0 then notch will be omitted.
• If R1 < 0 then notch will be a KS notch
• If R1 > 0 and R1 < 1000 then notch will be a R notch
• If R1 > 0 and R1 > 1000 then notch will be a fillet notch, where radius = R1-1000
Code, parameters R2 α2
20000, a, [b, c, R1,α4] 20010 18
20010, a, [b, c, R1, α4] 30015 30
Type 201:
Remark:
• If R1 = 0 then notch will be omitted.
• If R1 < 0 then notch will be a KS notch
• If R1 > 0 and R1 < 1000 then notch will be a R notch
• If R1 > 0 and R1 > 1000 then notch will be a fillet notch, where radius = R1-1000
Code, parameters R2 α2
20100, a, [b, c, R1,α4] 60015 18
20210, a, [b, c, R1, α4] 40010 30
Type 202:
Code, parameters α2 α3
20200, [c, α1,α4] 16 18
20210, [c, α1, α4] 18 30
Type 186:
Code, parameters R1 R2
Type 187:
Code, parameters R2
Type 188:
Remark:
b=0 (or not given) means that b=R1.
Code, parameters R1
Type 189:
Remarks:
1. b=0 (or not given) means that b=R2.
2. α2=0
3. means that c becomes irrelevant.
Code, parameters R1 α2
Type 190:
Remarks:
1. b=0 (or not given) means that b=R2.
2. α2=0 means that c becomes irrelevant.
Code, parameters R1 α2
8.1 Background
AVEVA Marine provides a large number of in-built endcut types. Most customers use only a
few of these.
This document describes how a customer may set up default endcuts depending on the
type of connection, i.e. endcuts that will be selected if not otherwise actively decided by the
designer. Only the endcuts defined in this way will be available for interactive picking.
The information is used when creating profiles in Hull Modelling and in Curved Hull
Modelling.
A way to inhibit the use of certain endcuts completely is to remove them from the endcut
table.
8.2.1 General
The definition of default endcuts takes place via an ordinary text file, created and maintained
in the standard editor of the computer system.
This file allows the user to define a subset of relevant endcuts from the total set of available
according to AVEVA Marine standards. It is also possible to define default endcuts to be
picked automatically depending on the type of connection. An endcut may in this way be
selected for a specific combination of profile type and connection code.
The name of a endcut file can be selected quite freely and its total file specification should
be assigned to environment variable SBH_ENDCUT_CTRL. The file is normally supposed
to be stored in the default directory of the current project.
The keyword TYPE is the endcut type as defined in the standards. This keyword starts a
"type group" and may occur any number of times.
The text given on the same line as the TYPE keyword is the customer description of the
endcut group.
The keyword PROF defines for what profiles types this endcut group is relevant. Any
number of profile types can be given but at least one.
The lines following the PROF keyword select a set of endcut codes. Each of these lines
starts with an endcut code according to AVEVA Marine standards. It is also possible to set
predefined values for the "free" parameters of the endcut (optional). With the keyword
"CON" it is possible to define a number of connection codes. Doing this means that the
endcut on the current line is the default for the profile type(s) in combination with the
connection code(s). Maximum number of connection codes following the "CON" keyword is
20. Use of the keyword "CON" is optional.
Note: that the same endcut may appear several times, e.g. with different parameters, to be
the default for different connections (cf. 1210 in the second "type group" in the
example).
The input example above should be interpreted in the following way: when generating a flat
bar and using any of the connection codes 5, 10 or 12 the default endcut type for that end is
1102. (However, the designer may select any other endcut at will.)
8.3 Remark
The utility found at: Initiate Hull Standards - Profiles and Flanges - Endcut selection, may be
used to check a definition of active endcuts.
This utility also updates settings drawing __SBH_ECUT_MENU__ with information used by
the Endcut Selection Dialog.
Further information can be found in Customising Dialogues .
9.1 General
The AVEVA Marine endcut standards consist of a number of built-in endcut types, which
may be customised via the endcut table. When the profile endcut is modelled, the desired
endcut geometry is defined by the endcut code and some endcut parameters. Sometimes,
however, a general rule for adjusting the geometry of an endcut type may be formulated.
Such a rule may override endcut parameters given by the user.
Currently, rules for the following definition purposes are supported:
• Endcut gap on flange of built T-bars depending on the profile height.
• Toe width of flange on T-bars considering web thickness.
• Knuckle angle and flange extension of tapered endcuts considering profile height and
endcut parameter "b".
• Endcuts adapted to curvature of parts connected to.
The rules are written in a project specific text file in a simple language based on the TIL
format. Before the rules may be used they must be interpreted by a function of the Hull
Initialisation program.
If the syntax in the text file is correct, an object __SBH_ADJUST_ENDCUT__ will be
created in OGDB. When this object is available, the geometry of the endcuts may be
adjusted according to the defined rules.
The customer can control the gap between the flange of a T-bar and a connected plate via a
file in TIL-format. For each relevant end cut type designed for T-bars, it is possible to specify
the size of the gap for different profile heights. Relevant end cut types are: 30, 31, 32, 33,
34, 42, 43, 44, 49, 83, 145.
The rule is composed of the CUT keyword, an endcut type and a number of pairs of /H-
attributes and /E-attributes.
Syntax
CUT, <endcut type> /H=<profile height> /E=< flange gap>……….;
Example of a text file defining the gap on the T-bar flange:
CUT, 42
/H=200 /E=40
/H=300 /E=50
/H=400 /E=60;
CUT, 43
/H=200 /E=40
/H=300 /E=50
/H=999 /E=38;
CUT, 145
/H=999 /E=38;
H=999 has a special meaning in that it defines all other profile heights, which have not been
defined for the endcut type. For example, the gap for endcut 145 is defined to 38 mm for all
profile heights, while for endcut type 43 the gap is 38 mm for all profile heights except
heights 200 and 300.
The customer can control the extension of the flange toe outside the web via a special file in
TIL-format. The rule should be written on the following format:
CUT, <endcut type> /D=< extension of the flange toe outside the web>;
The endcut type should be designed to be used for T-bars and have a toe on the flange
defined by a C-measure.
Example of a text file defining the extension of the flange toe outside the web:
CUT, 42 /D=8;
CUT, 43 /D=8;
CUT, 31 /D=10;
CUT, 32 /D=10;
When this facility is activated the value of 'c' in modelling is irrelevant and need not be given
at all except in certain cases as illustrated below ('old' input to the left, 'new' to the right).
CUT = 3101, 50, 85 -> CUT = 3101, 50, 85 ( or e.g. 3101, 0, 85)
The customer can control the knuckle angle and flange extension via a special file in TIL-
format.
The file consists of a number of statements, each consisting of the CUT keyword, an endcut
type and a number of triples of /HKN-attributes, /ANG-attributes and /EXT-attributes.
Example of a text file defining knuckle angle and flange extension of tapered endcuts:
CUT, 24
/HKN=25 /ANG=30 /EXT=6
/HKN=100 /ANG=18 /EXT=8;
CUT, 37
/HKN=50 /ANG=30 /EXT=6
/HKN=100 /ANG=18 /EXT=8;
Note: These rules are not valid for User Defined Endcuts.
The customer specifies that a specific endcut type may adapt to the curvature of connected
parts by setting up a rule in a file in a special TIL-format. The rule is written on the following
format:
CUT, <endcut type> /CUR;
10.1 General
In symbolic hull views (planar views and shell expansion views) stiffeners are drawn
symbolically in top views. (The term stiffener refers in this document to both plane panel
stiffeners and to shell stiffeners, i.e. longitudinal or transversal frames). In this type of views
a stiffener is represented by its mould line, by a material symbol and by a symbolic
representation of the endcuts.
The purpose of this document is to describe to some detail the principles of the currently
used symbols for endcuts. These symbols are supposed to give a fair idea of the shape of
the endcut and the connection at a stiffener end.
Remark:
Not all possible combinations are described below of the factors affecting the symbol
selection, only the most relevant or typical ones. Symbols for other combinations are
selected in analogy wherever reasonable. However, there might even be cases when the
available symbols are improper.
The figures below show a side view of the stiffener, a profile type symbol, the top view of the
stiffener and the symbol separately with its number.
Case 1:
No snipe and no offset of flange end (figure below).
Case 2:
Sniped flange ends, no flange end offset (figure below).
Case 3:
As case 2 but flange end offset (figure below)
Case 4:
Straight cut in web and flange, flange end offset (figure below).
Case 1:
Straight cut in both web and flange (figure below).
Case 2:
Same as case 1 but with sniped flange (figure below)
Case 3:
Both web and flange sniped (figure below).
Case 4:
Like case 3 but flange not sniped (figure below).
11.1 General
Profile endcuts are in AVEVA Marine specified via an endcut code that is a four or five digit
integer (e.g. 1302). They are all instances of a number of predefined endcut types with
numbers equal to the two or three leftmost digits of the endcut code (in the example above
the type is 13). In addition the endcut description is completed by a variable number of
parameters. Some of these parameters are normally connection angles, calculated and
added automatically by the system (e.g. the total endcut specification may be 1302, 100,
85.7 (where the last number is a calculated connection angle). This is all described in some
more detail in Profile Endcuts in AVEVA Marine .
Some yards have by tradition other ways to specify and present endcuts to production than
those used in AVEVA Marine. This document describes how one specific way of specifying
endcuts can be used in relation with AVEVA Marine in a situation where the system
internally still treats the endcuts in its traditional way.
• Ca45aR50 is a simple cutout of type 11 with an endcut angle that makes it extend 45
mm outside the nominal end point of the stiffener. The endcut has notch R50 in its
lower corner (similar to the right endcut in the figure in paragraph 9.5 below).
• D15bS0 corresponds to the endcut 1302, 15.
11.4 Restrictions
This implementation is subject to a number of restrictions:
• The main restriction is that there must be a one-to-one relation between a used endcut
string and the standards available in AVEVA Marine.
• In AVEVA Marine there is no correspondence to the feature of defining individual
endcuts for web and flange of built profiles. Thus, the previous condition excludes all
endcuts for built profiles.
• The same condition also excludes a considerable portion of the endcuts to be used for
flatbars and milled profiles where this feature otherwise may be applied.
To conclude: This feature offers an alternative way of using part of the existing endcut
standard for flat bars and milled profiles. It does not support the definition of any new endcut
types or standards.
Traditionally the endcut would in this case have been specified as CUT=1120 in both cases.
The result after generation will in the two cases be equal to CUT=1120, 60 and CUT=1120,
120, respectively.
The corresponding endcut string should be Cb173R50 and Ca173R50, respectively (here
173 is the result of the connection angle and the profile height). But beforehand the designer
may not know the connection angle and thus not whether it is <90, >90 or should happen to
be exactly 90 degrees. So the question is: How should he present his request for endcut to
the AVEVA Marine modelling function?
The following approach has been chosen as a general feature. The endcut should be
specified (in this case) as:
C$##aR50
Here:
## The distance (length of snipe) to be calculated from the connection angle and
the profile height.
Thus, when the designer gives an endcut string containing $ and ## he expects the system
to exchange these characters by appropriate values, evaluated from the result of the
modelling. These characters are allowed only immediately following the leading character
specifying the endcut type.
The mapping from endcut strings to AVEVA Marine endcuts are performed by the aid of a
translation file that is described in the next section.
Note: Any endcut string used by the designer must be registered in this file.
The input file consists of an unrestricted number of statements that may be organised in the
following way:
[<replace_stmt>] ( ....)
<profile_definition>
<translate_stmt>
<translate_stmt>
<translate_stmt>
....
<profile_definition>
<translate_stmt>
<translate_stmt>
....
<profile_definition>
<translate_stmt>
....
Syntax:
REPLACE, <prefix>
/ BY = <exch_str>
/ WHEN = <TB_type1> (1....10)
;
<prefix> The initial part of an endcut string that, if found, should be exchanged.
BY Specifies the string, by which to exchange.
WHEN This replacement should occur only when the corresponding AVEVA
Marine endcut type is <TB_type>. WHEN is the 2 or 3 digit endcut
type. Maximum 10 types can be given.
Examples:
REPLACE, Ca0 /BY = A / WHEN = (11, 21);
REPLACE, Ca0 /BY = B / WHEN = (12, 22);
Syntax:
<proftype> are valid profile types. Maximum 10 different profile types can be given in
one statement.
Examples:
PROFILE, 10;
PROFILE, 20, 21, 30, 31;
Syntax:
TYPE, <ec_string>
/TB_TYPE = <endcut_code>
[/PAR = <par1>,<par2>,...]
;
TYPE This is the endcut string that the designer specifies as input and that
normally will be picked from a list created based on this translation file.
Normally all parameters are fixed except some parts of the endcut
designation that may be depending on the connection angle (see above).
TB_TYPE AVEVA Marine endcut code. This code must exist in the current endcut
table.
PAR Explicit AVEVA Marine endcut parameters. They must match in numbers
those required by the endcut code.
Example:
REPLACE, Ca0 /BY = A /WHEN = (11, 21);
REPLACE, Ca0 /BY = B /WHEN = (12, 22);
PROFILE, 10;
TYPE, A /TB_TYPE=1100 /PAR = 90;
TYPE, AaC8 /TB_TYPE=1190 /PAR = 90;
TYPE, AaR50bR50 /TB_TYPE=1124 /PAR = 90;
12 Stiffener Connections
12.1 General
The automatic generation of panels in Structural Design is based on RSOs with defined
properties. One of the properties made use of in the modelling is standardized stiffener end
connections. These may be of type SNIPE, TIGHT or OVERLAP and will contain sets of
combinations of connection and endcut codes. Once the designer has selected any of
SNIPE, TIGHT or OVERLAP for a stiffener connection AVEVA Marine will automatically,
based on the profile type, pick a suitable endcut and connection code
When defining a profile end connection, both CON and CUT must be given in order to get
the profile end connection correct. The combination of CON and CUT are very often a
standard used by the yard. It is possible to define those standard connections as any
arbitrary name to be used in the continuing detailed design.
The underlying connection between these keywords and the profile endcuts and the
connection codes is defined in a standard object named __SBED_STIFF_ENDS__.
The standard object is created using a TIL input file and the interpretation of this file is made
in Inithull.
<type> is the connection type and could have any of the values 1, 3, 4 or 5.
Connection type 2 is covered within type 1 and is not needed to be
defined. <type> shall be given as an integer.
<code> is the connection code that shall be used for this type of definition. The
connection code shall be given as an integer. For available codes, see
Connection Code Definition.
<text> is a free descriptive text, currently not used by the system.
<ptype> is profile type identified by the AVEVA Marine code for the profile. Given
as integer.
<endcut> is a complete endcut description with code and parameters. Given as a
string.
<type> is the connection name to be used as a substitute for CON and CUT
when defining the stiffener end..
<code> is the connection code that shall be used for this type of definition. The
connection code shall be given as an integer. For available codes, see
Connection Code Definition.
<ptype> is profile type identified by the AVEVA Marine code for the profile. Given
as string.
<endcut> is a complete endcut description with code and parameters. Given as a
string.
13.1 General
In planar sections of the hull structure (symbolic hull views) stiffeners are represented in a
symbolic way by a line (mould line) and symbols for end treatment and material orientation.
For an example, see Hull Detailed Design/ Planar Modelling/ User's Guide/ Information on
Drawings and Information Structure/ Views/ Plane Panels/ Plane Views.
By default the mould line is represented by a dash-dotted line if the stiffener is located on
the side against you, by a dashed line if located on the side away from you. However, this
can be overridden by customer settings in the default files of involved programs. This is also
the case with the material symbol.
The conditions at the ends of stiffeners regarding end treatment and connection to adjoining
elements is indicated by symbols at the ends of the mould line. These symbols depend on
the combination of profile type, end cutting and connection (tight, gap, overlap).
The selection of a certain symbol is currently glued into the system and these rules cannot
be changed by the customer. However, a customer may modify the standard symbols
delivered by the system.
The tables below describe the symbols that are chosen in a special combination of profile
type, endcut type and connection.
13.1.1 Stiff 1
Flanges
1 Folded Flanges
1.1 Background
There are different ways in shipbuilding to stiffen free plate edges. One way of doing it is to
weld a flat bar ("face plate" - in Hull called (welded) flange) symmetrically or asymmetrically
to the edge. Another method is to weld a stiffener parallel to the edge at a certain distance.
A third method, often used especially in small parts, typically brackets, is to bend a part of
the actual plate to form a structure that looks and acts like a profile. This is in Hull called a
folded (or bent) flange.
A number of characteristics of folded flanges, e.g. the width of the area to be bent related to
the nominal height, the radius of the bending tool, the shapes of the ends of the flange, may
vary considerably between different yards. Therefore, a yard should be able to set up a
suitable flange standard of its own. AVEVA Marine has a facility with exactly this objective.
Based on a number of basic patterns it may establish any number of flange alternatives to
be used both in brackets and other plate parts. The flange definition facility is described in
this document.
flange ends types, each customer creates his own set of standardized flange ends. A folded
flange is not necessarily symmetric. The flange ends may be different, while - of course the
total height of the flange and the position of the marking line must be independent of the
flange ends. Normally, any combination of flange type and flange ends is allowed.
When generating a flange the user selects a certain flange type and also specifies the (user
defined) flange end types. If not specified the user defined default types will be used.
1.3 Definitions
In this document some terms will often be used. They are shortly described below
:
Base line The line to which the flange geometry will be added.
For brackets this line usually goes through the top of
the bracket toes.
Marking line A line on the flange indicating where the bending tool
should be placed while bending the flange.
W_KN The orthogonal distance between the base line and the
knuckle point.
MARK_D The orthogonal distance between the base line and the
marking line.
Characteristics:
• The radius (R1) must be defined in the definition file.
• The arc of the flange starts perpendicular to 'toe'.
• The arc ends at the intersection point with the base line.
Normally the contour has a knuckle here.
The radius as given will be recalculated before being used (R=R1/(sqrt(2)*sin(V))). This
means that R=R1 only when V=45.
Characteristics:
• The radius (R1) must be defined in the definition file.
• The arc starts perpendicular to 'toe' and ends perpendicular to the base line.
• Formula for W_KN has to be defined.
This type has the same characteristics as type 3, except that the arc starts parallel to the
base line and ends perpendicular to the base line.
TOE_L is optional and set to 0 if not defined.
The characteristics are the same as for type 3, but the arc starts as a continuation of the
'toe' and ends perpendicular to the base line.
This is a very special flange end type that usually occurs with a toe. However, even if
defined to be set at a toe it might be generated anywhere.
Special is that the base line passes through a point P (defined by DX_P, DY_P), and not
through the top of the toe. This means that the edge will not be set parallel to the 'original'
base line. The base line will thus be modified while setting the flange.
The shape of the toe is generated from two arcs (radius R1 (the larger one) and R2) and the
distance DIST from a certain line. This line passes through the given point P and a point on
the toe defined by TOE_H and TOE_L. All these parameters have to be set in the definition
file.
Furthermore, the distance from the base line to the knuckle point has to be defined as for
flange end types 3, 4 and 5.
1.5.1 General
The input file should be written in a syntax based on TIL (The Interpretative Language). In
this application the syntax is very simple with only two different statements, FLA_TYPE and
FLA_END.
The order of the statements is arbitrary. Note, however, that the default flange type and
flange end type will depend on the order if not otherwise specified. A flange definition file
must contain at least one flange type and one flange end type, but otherwise the customer
may define as many flange types and flange end types as he wishes.
The idea is to make it possible to let FLA_W and MARK_D be calculated according to the
following formulas, where the items above are 'variables' and the customer defines the
factors (constants) and R.
where H = a nominal value of the flange height (i.e. the size of the flange as given by the
user, not necessarily equal to the actual height of the flange)
/RADIUS = <radius>
[ /DEFAULT ]
/W_H_FACT = <fact>
[ /W_RAD_FACT = <fact> ]
[ /W_T_FACT = <fact> ]
[ /W_CONST = <const> ]
[ /M_H_FACT = <fact> ]
[ /M_RAD_FACT = <fact> ]
[ /M_T_FACT = <fact> ]
[ /M_CONST = <const> ] ;
<flatype_no> is an integer and the user's reference number for this flange type.
It must be a unique number (among flange types), and not
between 200 and 300.
/RADIUS Defines the bending radius.
/DEFAULT Attribute used if the flange type defined in this statement should be
the default type. Only one type may be default. If default is not
defined for any type, the first flange type in input will be the default.
/W_H_FACT These attributes define constants affecting FLA_W as described
/W_RAD_FACT above. If any of the attributes is omitted the corresponding value
/W_T_FACT will be set to 0.
/W_CONST
that W_H_FACT is mandatory.
/M_H_FACT These attributes define constants affecting MARK_D as described
/M_RAD_FACT above. If any of the attributes is omitted the corresponding value
/M_T_FACT will be set to 0.
/M_CONST
The figures in paragraph 1.4 show the basic types and their parameters.
For all basic types except type 1 and 2, the position of the knuckle point, W_KN, must be
defined. In analogy with the flange width, W_KN will be calculated according to the formula:
W_KN = KN_H_FACT*H + KN_RAD_FACT*R + KN_T_FACT*T + KN_CONST
where H, R and T have the same meaning as above.
The syntax of the FLA_END statement:
FLA_END, <fla_end_no>
/TYPE = <basic_type_no>
[ /DEFAULT ]
[ /KN_H_FACT = <fact> ]
[ /KN_RAD_FACT = <fact> ]
[ /KN_T_FACT = <fact> ]
[ /KN_CONST = <const> ]
[ /TOL = <tolerance> ]
[ /FLA_V = <angle> ]
[ /R1 = <radius> ]
[ /R2 = <radius> ]
[ /TOE_H = <distance> ]
[ /TOE_L = <distance> ]
[ /DX_P = <distance> ]
[ /DY_P = <distance> ]
[ /DIST = <distance> ]
[ /R_FILLET = <radius> ];
All the assigned values except <fla_end_no> and <basic_type_no> are real
numbers.
[ ] means that the attribute is optional.
T2 Tangent of the arc of the flange in point P. The following discussion will
concern how to choose T2 depending on B and T1.
A connection in the point P can be either concave or convex depending on V. Each of these
connection types can be divided into one obtuse and one acute case
.
Concave acute is an extreme case, where no folded flange can be used. Only the other
three cases will be regarded below.
When V0 < TOL then the flange will be replaced with type 1. TOL is the tolerance angle
which can be defined in the FLA_END statement.
When V0 > TOL the flange will remain a type 2 and T2 will be perpendicular to T1.
When V0 < TOL then the flange will be replaced with type 4, and T2 will be parallel with B.
(See the figure below.)
When V0 > TOL the flange will remain a type 3 and T2 will be perpendicular to T1.
The flange end will be replaced with type 4, and T2 will have the same direction as B.
The flange end will be replaced by a type 3 and T2 will have the same direction as T1.
The flange end will remain a type 4, and T2 will have the same direction as B.
The flange will be replaced with a type 3. T2 will have the same direction as T1.
This is the normal (and only possible) case for flange end type 5. T2 will have the same
direction as T1.
The flange end will be replaced with type 4, and T2 will have the same direction as B.
Note: that this flange end type will affect the position and direction of the base line.
1.6 Examples
Suppose that we want to calculate the width of the flange before bending, FLA_W. This
means that we want to calculate the length of the dashed line, which is the neutral line in
bending.
Make the following assumptions:
• H is the nominal height of the flange, as given by the user. Here it is supposed to be the
total height after bending.
• The neutral line is on the depth 1/3 of the material thickness.
Then FLA_W is calculated:
i.e.:
W_H_FACT = 1
W_RAD_FACT = (PI-2)/2 ~= 0.571
W_T_FACT = (PI-6)/6 ~= -0.476
W_CONST = 0
Now we want to calculate the position of the marking line, MARK_D. Make the following
assumptions:
• The bending should start at the base line of the flange.
M_H_FACT = 0
M_RAD_FACT = PI/4 ~= 0.785
M_T_FACT = PI/12 ~= 0.262
M_CONST = 0
Assume that the bending radius is 30, and we want to refer to the flange type as number 10.
Then our flange type could be defined with the statement:
FLA_TYPE, 10
/RADIUS =30
/W_H_FACT = 1
/W_RAD_FACT = 0.571
/W_T_FACT = -0.476
/M_RAD_FACT = 0.785
/M_T_FACT = 0.262;
KN_H_FACT = 0
KN_RAD_FACT = PI/2 ~= 1.571
KN_T_FACT = PI/6 ~= 0.523
KN_CONST = 15
Basic type 4 also requires the parameters R1 and FLA_V. If we set R1 to 30, FLA_V to 25,
and we want to refer to the flange end type as number 5, then our flange end will be defined
with the statement:
FLA_END, 5
/TYPE = 4
/KN_RAD_FACT = 1.571
/KN_T_FACT = 0.523
/KN_CONST = 15
/FLA_V = 25
/R1 = 30;
1.1 General
By definition closed contours in plate parts and profiles are in AVEVA Hull called holes.
Holes should normally bet set in the interior of panels and in the interior of the web of
profiles. In panels holes may very well be located across seams dividing the panel into plate
parts. In that case the hole will result in edge openings in the parts on both sides of the
seam. It is also possible to place a hole across the outer contour of a panel. The extracted
plate parts will then be correct but holes across panel boundaries may cause
inconveniences in 3D views of the hull model. A better solution in these cases is to replace
the hole by a notch.
A hole can be either a physical hole or a fictitious hole. A physical hole is always presented
in both symbolic views and 3D view as a free space. A fictitious hole is a hole that in the
parts generation will rather be treated as a marking of a hole that will at a later stage in the
production be cut out manually. This fictitious hole is by default not presented in 3D view. To
enable these holes in a 3D view, the environment variable SBH_INPM_FICT_HOLE has to
be defined (set to any arbitrary value). The hole is always presented in symbolic views.
It is possible to specify bevels to be applied around any hole. If the hole is created by
reference to a penetrating object the possibly varying bevel angle may be calculated and
applied for the selected bevel type ("dotori"). (Contrary to dotori along plate edges the bevel
type is not picked automatically).
<par_i> are parameters controlling the size of the hole. They can be given
arbitrary values as far as they produce a reasonable hole contour. The
number of parameters is different for different types of holes and may
also vary for a certain type of hole because certain parameters may
have default values.
Examples:
• D250 specifies a circular hole with diameter 250 mm
• HE250*125 specifies an elliptical hole with major axis 250 mm and a minor axis 125
mm
The menu below shows all existing standard hole types. They are described in detail in
paragraphs below.
In the specification of the different hole types below the figures show the shape of the holes,
their local co-ordinate system and thus their reference point. The figures also show how the
holes will be oriented if no turning angle is specified.
Designation: D <d>
Example: D250
Turning angle is irrelevant.
Example: HO600*400
Example: HOR600*200*100
Example: HE250*125
(x/a) ** e + (y/b) ** e = 1
Example: HSE1200*600*2.5
Example:¨ HER2100*950*1500*950
(This is an elliptical hole where rectangular “strips” have been inserted around the symmetry
axes).
Example: HR1480*680*40
Example: HRM2000*700*50*10
(If <d> is left out the corner arc passes through the sharp corner of the rectangle, i.e.
d=0).
Example: HT600*600*75
2.1 Background
In symbolic hull views different types of components are represented partly by symbols. E.g.
the end cut and connection types are indicated by symbols at the ends of the stiffener trace
line.
This document describes a facility that offers a customer a possibility to decide the symbols
to be used for a similar symbolic representation of holes and notches in symbolic views.
type The statement type can be either NOT for notches or HOL for holes.
Symb_No This is the number of the symbol in the symbol font No 94.
The designation does not have to be complete, e.g. HOL,HE,55; designates symbol 55 to all
elliptical holes, i.e. there is a kind of implicit "wild card" facility.
Additionally there is an option to define a default symbol for all notches or holes not
otherwise defined. This is done by giving an empty designation. Holes and notches must
have separate default specifications. If multiple default statements of the same kind exist,
only the last one is used.
Example:
NOT, ,100;
NOT, VU125*50, 1;
NOT, VU150*75, 2;
NOT, HKO150, 3;
.
.
.
HOL, , 250;
.
.
.
2.3.1 Remark
The definition of SBH_PENETR_SYMB_CTRL will activate the drawing of symbols for holes
both in symbolic hull views and in shell expansion views.
3 Notch Standards
3.1 General
"Notch" is the common denomination of the normally small openings in corners ("corner
notches") and along edges ("edge notches") of plates. In other contexts they may be called
"scallops" or "rat holes". Notches (only edge notches) may also be set along traces of
profiles but must not in this case be part of the end cut of the profile.
Some corner notches are supposed to be used only in brackets.
Examples:
• R50 specifies a circular arc with radius 50 mm
• HE250*125*100 specifies an elliptical notch ("edge hole") with major axis 250
mm and a minor axis 125 mm and with a 100 mm wide opening against the edge. The
toe height at the ends of the opening is by default 15 mm high.
The three menus below show:
1. Notches that may be used both in corners and along edges
The survey below gives all required details about each notch: how it should be selected,
controlled and used.
A standard notch is described in a co-ordinate system of its own. It is normally positioned
and orientated by reference to items in the model, e.g. corner or limits of the panel. A user
need normally not bother about how a standard notch is described in its own co-ordinate
system.
Certain types of standard notches (currently the types HKE, HKO, VUR, VDA, VDB, VOA,
VOB, KD, KE, KO, and KR) have toes with sharp corners.
An option has been implemented to soften these sharp corners by a fillet arc. The radius of
this arc is set by the environment variable SBH_NOTCH_TOER. Simultaneously, the built-in
toe height may be changed by another environment variable SBH_NOTCH_TOEH.
• Notch Type R
Picking:
Designation: R<rad>
Example: R50
Usage:
In brackets: In corners
• Notch Type RW
Picking:
Designation: RW<rad>
Example: RW50
Usage:
In brackets: No
Picking:
Designation: KEH<A>*<B>[*<C>[*<R>]]
Example: KEH250*125
Usage:
In brackets: No
Picking:
Designation: KUH<A>*<B>
Example: KUH250*70
Usage:
In brackets: No
• Notch Type KS
Picking:
Designation: KS<C>
Example: KS10
Usage:
In plates: In corners
In brackets: In corners
In profiles: No
Picking:
Designation: KSA<C1>*<C2>
Example: KSA15*10
Usage:
In plates: In corners.
In brackets: In corners.
In profiles: No.
Picking:
Designation: KSN<H>*<W>[*<KS>]
Example: KSN75*25*13
Default value: KS = 10
Usage:
In plates: In corners.
In brackets: In corners.
In profiles: No.
Picking:
Designation: HKE<A>*<B>*<C>
Example: HKE200*100*100
Usage:
In plates: In corners
In brackets: In corners
In profiles: No
Picking:
Example: HKO200*100
Usage:
In plates: In corners
In brackets: In corners
In profiles: No
• Notch Type VU
Picking:
Usage:
In plates: In corners
In brackets: In corners
In profiles: No
Picking:
Designation: VUA<X>[*<R>]
Default value of R=75
Examples: VUA100
Usage:
In plates: In corners
In brackets: In corners
In profiles: No
Picking:
Designation: VUF<C>*<B>*<R>
Example: VUF100*75*50
Usage:
In plates: In corners
In brackets: In corners
In profiles: No
Picking:
Designation: VUR<A>[*<B>[*<T>[*<R1>[*R2>]]]]
Default value B = 30
Usage:
In plates: In corners
In brackets: In corners
In profiles: No
Picking:
Designation: VDA<X>
Example: VDA75
Usage:
In plates: In corners
In brackets: In corners
In profiles: No
Picking:
Designation: VDB<X>
Example: VDB75
Usage:
In plates: In corners
In brackets: In corners
In profiles: No
Picking:
Designation: VOA<X>
Example: VOA75
Usage:
In plates: In corners
In brackets: In corners
In profiles: No
Picking:
Designation: VOB<C1>
Example: VOB75
Usage:
In plates: In corners
In brackets: In corners
In profiles: No
Picking:
Designation: BKU<A>*<R>[*<T>]
Example: BKU75*30
Usage:
In plates: No
In brackets: In corners
In profiles: No
• Notch Type BR
Picking:
Designation: BR<R>*[<T>[*<H>]]
Default value T = 15
Default value H = R
Example: BR30
Usage:
In plates: No
In brackets: In corners
In profiles: No
• Notch Type RF
Picking:
Designation: RF<R>
Example: RF50
Usage:
In plates: In corners
In brackets: In corners
In profiles: No
• Notch Type RN
Picking:
Designation: RN<R>[*<C>[*<H>]]
Default value H = 10
Example: RN50
Usage:
In plates: In corners
In brackets: In corners
In profiles: No
Picking:
Designation: VDC<A>*<B>[*<R1>[*<R2>[*<T>]]]
Default value R1 = B.
Example: VDC85*50
Usage:
In plates: In corners
In brackets: In corners
In profiles: No
Picking:
Designation: VUG<A>[*<B>[*<C>[*<T>[<R1>[*<R2>]]]]]
Default value C = B.
Example: VUG100
Usage:
In plates: In corners
In brackets: In corners
In profiles: No
• Notch Type RC
Picking:
Designation: RC<A>[*<B>[*<R1>[<R2>[*<T>[<V1>[*<V2>]]]]]]
Default value R1 = 30
Example: RC70.
Usage:
In plates: In corners.
In brackets: In corners.
In profiles: No.
Picking:
Designation: RKA<R>*<S>
Example: RKA50*20.
Usage:
In plates: In corners.
In brackets: In corners.
In profiles: No.
Picking:
Designation: RKB<R>*<S>
Example: RKB50*20.
Usage:
In plates: In corners.
In brackets: In corners.
In profiles: No.
• Notch Type KD
Picking:
Designation: KD<D>*<C>
Example: KD100*70
Usage:
In brackets: No
• Notch Type KE
Picking:
Designation: KE<A>*<B>*<C>
Example: KE250*125*100
Usage:
In brackets: No
• Notch Type KO
Picking:
Designation: KO<A>*<B>
Example: KO250*100
Usage:
In brackets: No
• Notch Type KR
Picking:
Example: KR1000*500*800*50
Usage:
In brackets: No
• Notch Type KU
Picking:
Designation: KU<A>*<B>
Example: KU150*50
Usage:
In brackets: No
Picking:
Designation: KUF<A>*<B>*<R>
Example: KUF200*100*50
Usage:
In brackets: No
Picking:
Designation: KDU<A>*<B>[*<C>[*<R1>[*<R2>]]]
Default value C = 150
Default value R1= 40
Default value R2 = 30
Example: KDU75*175
Usage:
In brackets: No
Picking:
Designation: KVU<A>*<B>[*<R>]
Example: KVU100*150
Usage:
In brackets: No
Picking:
Designation: KFS<D>
(A = D*sqrt(2) )
Example: KFS30
Usage:
In brackets: No
1.1 General
In shipbuilding it is most common that the stiffening of the main structural members
penetrate the plating of subordinate elements, e.g. so that longitudinal frames in the shell or
in the decks/bulkheads pass through webs and double floor bottoms. Such penetrations are
in AVEVA Marine called cutouts. (Cutouts need often be reinforced by small plate pieces, in
AVEVA Marine called clips or collars. The clips are defined in association with the cutouts
but they are described in separate documents.)
The cutouts are normally standardised regarding general shape, radii, clearances, etc. and
have well defined dependencies on profile types and sizes. Therefore they lend themselves
well to be generated by different types of parameterised macros.
The first part of this document describes the three options for generation of cutouts that
currently are available in the system. These options are:
1. AVEVA Marine contains a large number of cutouts which have been hard coded into
the programs. These cutouts with their design rules are specified in the Hull Standards.
2. The majority of cutouts used by a certain yard are common to all other yards in their
general principles. They may vary in details regarding e.g. clearances, radii, etc. but
the pattern is common. For this category of cutouts, AVEVA Marine has an "External
Cutout Definition Facility" which allows a customer easily to set up his own standards.
3. Very special and yard specific cutouts with an arbitrary geometry can be built up in
AVEVA Marine geometry macros which allows a customer to develop cutouts with any
shape.
These three options are described on an overall level in this specification. Details about
them can be found in separate documents.
Independently of the way they have been created all cutout types can be used both in plates
and profiles.
Cutouts are in AVEVA Marine normally identified and picked by a number that can be
selected quite arbitrarily by the customer when setting up the cutout standard. However, an
option to use “named” cutout is described in a separate document Named Cutouts.
(Many of the cutouts can be redefined to follow the same rules by use of External Cutout
Definition Facility, described in the next paragraph.)
• Cutout 1
• Cutouts, Survey
• Tight Cutout
Type 42 F = 60, G = 40
Ellipse:
A x B
A = H sin V + 25
B = 370/sin(V) + cos(V)(H + 55/sin(V))-120 sin(V)
1.3.1 General
When cutouts are made in plates or profiles for penetrating profiles the cutouts will
automatically adjust to the type, size and orientation of the penetrating profile. This means
e.g. that the cutout should consider the angle between the profile and the plane of the
penetrated plate / profile. Normal consequences are that the height of the profile and the
width of the flange in the section are bigger than the nominal values and that the angle
between the web and flange might be different from the normal 90 degrees.
This is to be taken into account when the geometry of the cutouts are generated. This is
done automatically by the External Cutout Definition facility but is the responsibility of the
customer when writing geometry macros for cutouts.
However, there is also another aspect that might have to be taken into consideration,
namely the thickness of the penetrated plate / profile. The options supported by AVEVA
Marine are described below.
3. The cutout contour is supposed to bevelled to create a tight connection against the
profile, see the figure below.
• Default Situation
The default situation is that no adjustment takes place. This happens when
SBH_CUTOUT_BEV is unassigned.
CUT_DRAW means that the cutout is adjusted also in views. Also in this case a warning
message will be issued in case of overlap.
Only the parts of a cutout directly connected (welded) to the profile are effected. No
additional environment variables are relevant in this situation.
A condition for this kind of change to function properly is that the part of a cutout between
two straight lines is supposed to be a fillet that should be translated together with the
surrounding lines without change of its size.
This method is normally supposed to be combined with bevel cutting of the part of the cutout
against the profile section, currently only using a simple V-bevel, the angle of which is
calculated automatically.
2.1 Introduction
The current document describes the AVEVA Marine option for External Definition of Profile
Cutouts as defined in the superior document mentioned in that document.
2.2.1 Definitions
The external cutout definition supposes that the customer cutouts are 'instances' of a
number of predefined basic cutout types which are described in this document.
Each such basic cutout type is called a main type and is identified by a type number. Thus
all the existing main types (with their numbers) must have been set up by AVEVA.
A customer may establish any number of instances of a main cutout type. Each instance is
identified by a number, the user type, selected freely by the customer. This number is used
when a cutout is picked in the modelling.
U-bars (profile type 50) are treated as L-bars (profile type 31) in all those profile types where
they are supported.
2.2.4 Clearances
The clearances between the segments of the cutout and the line segments of the profile
section are numbered like the radii, if not otherwise specified according to the figure below
Certain clearances may be irrelevant for certain cutout types, e.g. C3 for flat bars, bulbs and
L-bars when the cutout is quite open on the mould line side.
CUT, <number>
/TYPE=<base_type>
[/BULB_CLEARANCE
/PROF=(<type1>, <type2>,...) (1 ...)
<arc_definition> (1 ...9)
<gap_definition> (1 ...7)
;
Explanation:
Remark:
If an arc with a certain number is irrelevant for a certain cutout
it may be used to define gaps depending on profile heights,
see below.
<arc_definition>::=
/ARC=<arc_no> [,R_MIN=<rad>]
ARC Specifies the order number of the arc in the definition of the
cutout (see above). The relevant arc numbers are specific for
each basic type of cutout. If not given for a relevant arc this is
supposed to have radius 0.
Example:
/RAD= (-10, 40, 60)
/H_LIM = (100, 250)
will result in:
R=KS10 for profile height (H)<=100,
R=40 for 100<H<=250,
R=60 for H>250
/GAP=<gap_no>
[/DIST=<gap>]
[/REFERENCE=<arc_no>]
[/OPPOSITE]
[/FL_WIDTH]
[/SKIP_OVERSHOOT]
Example:
/REF=6 /DIST=-20 means that the clearance should be
equal to the radius of arc 6 minus 20.
By reference to an arc the clearance may be made dependent
on the profile height in the same way as the radius. Also arcs
not otherwise affecting the geometry of the cutout may be used
in this way.
OPPOSITE Relevant only for certain clearances, see below.
FL_WIDTH Relevant only for C1 and C7. For details, see below.
SKIP_OVERLAP Relevant only for T bars (normally only profile type 35) (C3)
and profile type 36 (C4). For details, see below.
Example of a Simple Cutout Definition contains a simple example of a CUTOUT set-up file.
R > 0 The connecting segment will be one (or maybe two, cf. below) arcs.
• Special Cases:
1. As a special case for R1 and R9 these radii may be set to xxx yyy rrr (one number,
where xxx, yyy and rrr are three-digit integers) creating a notch with the following
shape.
Example:
When xxx = yyy = 100 and rrr = 50 the radius should be given as 100100050.
2. For the "shoulder arcs" R4 and R6 the following special cases are supported in case of
non-elliptical and non-circular top of the cutout.
An ordinary fillet (default situation):
For the two “Mickey Mouse” variants C3 (C5) should be set as the distance between the
start of the arc and the profile. C3 will be set to C2 if not given.
3. For the shoulder arcs R4 and R6 in cutouts with an elliptical, see e.g. Paragraph 2.3.7
Main Type 6.
5. For cutouts with a lug on one side and quite open on the other, giving option
/FL_WIDTH means that these clearances are set to B -S +<xxx>. (Here, B is the width
of the flange and S the thickness of the web and <xxx> the given value).
This will normally result in a cutout with total width between the lug and the opposite
side equal to B+<xxx>. It is especially useful when T-bars should be inserted as
described in the figure below and should be used only for cutouts with lug one side.
This option is valid for C1 and C7.
6. Similarly, the option /OPPOSITE means that the distance <xxx> should be measured
from the opposite side of the web normally applicable for C1 and C7.
However, the same technique can be used to calculate C6 according to the figure
below, and C2 as in Figure 2:13.: Options for control of C2.
7. If C2 is defined for profile types where the flange is not extending into the mould line
side of the profile this inhibits the direct connection between R3 and R4 in main types
10, 11, 19, 20, 21 and 39.
The clearance between the starting point of R2 and the lower flange surface is
supposed to be C2 (with a possibility to calculate if from the upper surface by adding
option /OPPOSITE) as shown in the figure below.
R3/R4 (R6/R7) may overlap. In such a case the system treats the problem in the following
way..
R3 > 0: C2 is kept and R3 is adjusted to fit in, connected directly to R4. R6/R7
are treated in a similar way.
In a similar way R2/R3 (R7/R8) may overlap. Then the starting point of R3 will be moved to
have the same starting position in the x-direction as the ending point of R2. R2 will be
moved downwards if R3 and R4 are connected. Normally a knuckle will be introduced
between R2 and R3.
R7/R8 will be treated accordingly and R7 will be changed in case of conflict
If the cutout is open on both sides, C>0 gives a slope on the non-mould line side, C<0
on the mould line side.
2. Similarly, the distance from the mould plane of the profile to the free side of an open
cutout can be controlled by the parameter M1 in panel modelling, cf. the figure below.
The given measure will replace the clearance set in the cutout definition.
If the cutout is open on both sides, M1>0 defines the width on the non-mould line side,
M1<0 on the mould line side.
Note: that M1 defines the measure from the moulded side to the open side of the cutout.
Survey of Main Cutout Types
Below follows a survey of all the main cutout types, currently supported in this facility. The
general principles above are applicable if not otherwise stated.
Irrelevant radii: R2, R3, R5, R7, R8. In normal use, R1 and R9 are
irrelevant as well.
For the use of C1/C3 and C5/C7, respectively, see the general principles above.
Normally C3 and C5 would be defined, and C1 and C7 would be supposed to be calculated
from them. For other profile types than T:s, C1 is equal to C3. Therefore, if both C1 and C3
are given, C3 will be used only for the T-bars.
Clearances as for the previous cutout types. However, C4<0 means the distance from the
upper edge of the flange to the centre of the top arc.
Normally no radii should be defined (even if R1 and R9 may be).
All the normal profile types are supported. The general principles of clearances are
followed.
R2, R5, R7 and R8 are irrelevant.
C2 is normally irrelevant except for T-bars.
R3 and R4 will be directly connected to each other except for T-bars (and unless C2 is
explicitly defined)
The top circle of this cutout is handled and controlled in the same way as in main type 9.
C2 is normally irrelevant except for T-bars and C6 is irrelevant for flat bars.
The figure below defines the conditions for two cutouts that are very similar to each other.
The rules for both of them differ slightly when used for bulb bars and L-bars, respectively,
which means that separate definitions must be made for the two profile types. The definition
file is listed below the picture.
For L-bars: R1 = 40
/ARC=1 /RAD=-10
/ARC=3 /RAD=15
/ARC=4 /RAD=(30, 40)
/H_LIM=220
/ARC=6 /REF=4
/GAP=1 /DIST=1.5
/GAP=3 /REF=3 /DIST=1.5
/GAP=4 /DIST=40
/GAP=5 /DIST=25
;
!
! Type 308, L-bars
!
CUTOUT, 308
/TYPE=10
/PROF=(30,31)
/ARC=1 /RAD=-10
/ARC=3 /RAD=15
/ARC=4 /RAD=40
/ARC=6 /REF=4
/GAP=1 /DIST=1.5
/GAP=3 /REF=3 /DIST=1.5
/GAP=4 /DIST=40
/GAP=5 /DIST=25
;
!
! Type 309, bulb bars
!
CUTOUT, 309
/TYPE=10
/PROF=20
/ARC=1 /RAD=(50, 75)
/H_LIM=360
/ARC=3 /RAD=15
/ARC=4 /RAD=(30,40)
/H_LIM=220
/ARC=6 /REF=4
/GAP=1 /DIST=1.5
/GAP=3 /REF=3 /DIST=1.5
/GAP=4 /DIST=40
/GAP=5 /DIST=25
;
!
! Type 309, L-bars
!
CUTOUT, 309
/TYPE=10
/PROF=(30,31)
/ARC=1 /RAD=(50,75)
/H_LIM=360
/ARC=3 /RAD=15
/ARC=4 /RAD=40
/ARC=6 /REF=4
/GAP=1 /DIST=1.5
/GAP=3 /REF=3 /DIST=1.5
/GAP=4 /DIST=40
/GAP=5 /DIST=25
;
4.1 General
The general principles for handling of profile cutouts are described in a separate document.
The specific case that cutouts are created in geometry macros is described in the current
document. In doing so it covers the following topics:
• General assumptions about the coordinate system to be used for a cutout, supposed
orientation of the profile, etc.
• The environment in which the macros should be executed.
• The user interface (= the parameters) of the macro.
• Specification of how to make a customer written cutout macro available to AVEVA
Marine.
This specification also contains an example of an actual macro with the resulting cutout and
a macro that can be used in the testing of user developed macros.
4.2.2 Geometry
The geometry of the cutout should be oriented in the clockwise direction around the profile
section.
Make certain that the start and the end of the cutout contour extend well outside of the panel
boundary so that there are two intersections even in case of excess, etc.
NO_PROF_PARAMS INTEGER
PROF_TYPE INTEGER
PROF_PARAM1 DECIMAL
PROF_PARAM2 DECIMAL
PROF_PARAM3 DECIMAL
PROF_PARAM4 DECIMAL
PROF_PARAM5 DECIMAL
PROF_PARAM6 DECIMAL
V2 VECTOR_2D
V3 VECTOR_2D
WEB_FACTOR DECIMAL
FLANGE_FACTOR DECIMAL
PLATE_THICKNESS DECIMAL
R1 DECIMAL
R2 DECIMAL
M1 DECIMAL
M2 DECIMAL
M3 DECIMAL
M4 DECIMAL
CUTOUT_CONTOUR CONTOUR_2D
WELD_INFO STRING
After execution of the macro, the CUTOUT_CONTOUR should contain the contour
describing the cutout geometry.
WELD_INFO is a string with the order numbers of line segments that are welded against the
profile section. The first line segment along the contour has got number 1, the second
number 2, etc. (even if there should happen to be arc segments in between). The segment
numbers are separated by commas (In the figure above this string would be "1, 2" or
possibly "2" only). Currently, this parameter is not taken care of in AVEVA Marine.
> geomac
Present Geometry Macro:
(0) Exit
>
Observe that giving the name of the macro including the file extension .gml instructs the
geomac system to interpret this file instead of simply running an already pre-interpreted
macro.
If interpretation warnings are issued, these will be found in the file cutout_1.lst located in the
directory given by the definition of SBB_GEO_MACRO_LST. If the interpretation was
successful, the file cutout_1.glb will be present in the directory given by the definition of
SBB_GEO_MACRO_BIN.
See to it that any required auxiliary macros, called from this macro, are compiled in the
same way.
6 Named Cutouts
6.1 General
Traditionally in AVEVA Marine cutouts (and clips) are identified by integer numbers that are
selected by the customer when the standard is set up. These numbers must be used when
the designer picks/specifies a cutout to be generated.
This document describes an option to identify cutouts (including clips/collars) in the
modelling phase by "names" (strings) instead of (and in parallel with) numbers.
The syntax of one statement is as follows. The input file may consist of any number of such
statements.
CUTOUT, <name>
/CUT_NO = <cutout_number>
[/CLIP_1 = <clip_code_1>]
[/CLIP_2 = <clip_code_2>]
[/CLIP_3 = <clip_code_3>]
<name> The name the user wants to give the combination of the cutout number and
the clip arrangement. It may be a string or a number. (To use this option for a
cutout referred to by a number is a way to associate also numbered cutouts
with a clip arrangement).
CUT_NO Specifies the number of the cutout in the cutout standard available. (This is
the number to be used if this facility had not been available.)
CLIP_1 Specifies the number of a customer defined clip. This clip is valid for the
mould line side of the profile (or for a clip covering the whole cutout). (This is
number that should have been assigned to the keyword CT1 in panel input if
this facility had not been available.)
CLIP_2 Same as CLIP_1 but on the non-mould line side of the profile.
CLIP_3 Same as CLIP_1 but on the top of the profile.
Example:
The file below defines two named cutouts, with and without clip included.
CUTOUT, ABC
/ CUT_NO = 308
/ CLIP_1 = 22
;
CUTOUT, DEF
/ CUT_NO = 130
;
7.2 Background
When designing the internal structure in AVEVA Marine the cutouts for penetrating profiles
are supposed to be selected from a set of available cutout types. These are of two types:
those built into the system and those created by the customer. In both cases the cutout
types may be explicitly picked by the designer.
This document describes an alternative facility that lets the customer define default cutouts.
A cutout is default for a specific combination of a profile type and a panel data type. The
facility can be used to simplify the establishment of cutouts in the Planar Hull Modelling
module.
7.3.1 General
The definition of default cutouts takes place via an ordinary text file, created and maintained
in the standard editor of the computer system.
The name of the file can be selected quite freely and its total file specification should be
assigned to the environment variable SBH_CUTOUT_CTRL. This file is normally supposed
to be stored in the default directory of the current project.
...
• <proftype_i> is one of the normal profile types used in AVEVA Marine, e.g. 10, 20
and 30.
• <panel_dt> is the data type of the current panel. This data type together with the
profile type is the key to find the appropriate default cutout. <panel_dt> may contain
the wild card character % in one or several positions. Examples are "410", "%2%",
"%%%" and "%12". In this document <panel_dt> will also be referred to as a panel
data type mask.
One panel data type mask can be more specific than another. A panel data mask, A, is
less specific than another mask, B, if A contains more wild card characters than B.
Example: "12%" is less specific than "121".
The system does not check for multiple or overlapping panel data type masks. If two
masks overlap each other then the first one will be applied. Because of this the most
specific data type masks should appear first in the definition file.
• <defcut> is the cutout type to be applied to the current profile type if there is a match
of the data type of the current panel.
• <defclip> is the clip arrangement that should be applied. Zero indicates no clips.
If <defclip> is given with slashes (/), it indicates that the extended clip handling
should be used. All three CT's must always be given.
This shows, as in the example below, that CT1=190, CT2 is undefined and CT3 should
be 230.
Example:
TYPE = 10
410 38 011
41% 42 0
4%% 1 0
TYPE = 20
300 .. ..
TYPE = 43
325 5 190/0/230
7.3.3 Remark
The hull utility inithull may be used to check the cutout control file.
8.1 General
In shipbuilding it is most common that the stiffening of the main structural members
penetrate the plating of subordinate elements. Such penetrations are in AVEVA Marine call
cutouts. Normally the penetrated plate is connected to the penetrating plate, either for
strength reason or simply to tighten the penetration (or a combination of both). Often at least
a part of this connection is produced by the cutout itself; part of it may be welded to the
profile. However, very often the connection must be completed by extra plate pieces. The
parts used for fastening/sealing are always referred to as clips in AVEVA Marine, although it
sometimes would be more relevant to call them collars or lugs.
As can be seen in these examples the geometry of the clips depends on the profile section,
the geometry of the cutout, on rules for overlaps and clearances, etc. in a large variety of
ways.
But clips are also parts and may have common attributes with other types of parts,
especially plate parts, e.g. plate thickness and quality, part names and position numbers.
They may be bevelled and they are connected by welding which may have different
characteristics.
Clips further have a location, either on a selected side of the penetrated plate or even as
insert clips which are welded in the cutout without overlap.
The AVEVA Marine clip handling covers most of the aspects mentioned above and allows
the customer to specify most of these matters, often in such a way that the designer may
use the defined standards but also override it in the individual cases.
Clips have series of position numbers reserved for them (i.e. they will not be sorted together
with other plate parts and behave in this respect as e.g. brackets). It is also possible
(necessary) to set up special rules for the part names of clips. Clips are extracted to the
plate databank at the same time as all other parts in the ppanparts module and the nesting
system treats them also equally.
Note: this is the name of the part in the plate data bank and should not be confused with
the production oriented part name, created via the Part Name Control facility.
9.1 General
This document describes how to make clips via macros. It covers the following topics:
• general assumptions about the coordinate system of the clip, orientation of the profile
section, etc.
• the environment in which the clip macros are executed.
• the interface of the macros (= the parameters)
• how to make a customer defined clip macro and how to integrate it in the system.
The u-axis is perpendicular to the v-axis and always points in the direction of the flange. (In
case of a flat bar or a T-bar section it would be more correct to say that it points towards the
non-mould side of the profile section.)
9.2.2 Geometry
The clip contour delivered by the macro must be closed.
The clip contour should be defined in a counter clockwise direction, as seen from the w-axis
of the local clip coordinate system.
The macro itself must make allowance for the case when the profile penetration is not
perpendicular.
Input Parameters
<Name> <Description>
PROF_PARAM<1-6> (DECIMAL) For bulb bars the parameters are used in the
following way (both original parameter values and when
countered into a "similar" L-bar. (Values in a certain case
within apostrophes).
WEB_FACTOR (DECIMAL) Scale factor along the web (along the v-axis).
This factor will be different from 1.0 only when the profile
penetration is not perpendicular to the panel.
<Name> <Description>
• Input/Output Parameters
In general, output parameters need not be initialized in the geometry macro if they are not
relevant.
The four first parameters (CLIP_THICKNESS - EXCESS) are both input and output
parameters.
<Name> <Description>
CLIP_THICKNESS (DECIMAL) Thickness of the clip.
The clip thickness can be assigned in three ways:
1. By the clip macro parameter CLIP_THICKNESS.
2. In the input scheme, by the keyword "MAT" in the cutout
statement.
3. Default thickness: the thickness of the penetrated plate.
The above order is also the precedence between the rules,
i.e. the thickness given by the macro will always override
the thickness given in the input scheme.
SURFACE (STRING) Surface treatment of the clip.
QUALITY (STRING) The quality designation as a string. If the environment
variable SBH_CLIPQUAL_PLATE is set and no quality is given
in the scheme and no quality is given in the macro, the quality
from the plate that is closest to the clip will be chosen.
EXCESS (DECIMAL) Excess on edge abutting shell (or plate carrying the
profile).
If SURFACE, QUALITY and EXCESS are given as user input the given values will
override the values defined in the macro.
CLIP_CONTOUR (CONTOUR_2D) The geometry of the clip.
In the clip macro it is possible to define bevel/welding intervals. Paragraph Welding and
Bevel Information gives a detailed description.
BCLIP (DECIMAL) Bevel type when two clips are welded together.
BWEB (DECIMAL) Bevel type against the web of the profile section
BCWEB (DECIMAL) Bevel type against the web of the profile section where
coinciding with cutout contour.
BFLA (DECIMAL) Bevel type against the flange of the profile section.
BCFLA (DECIMAL) Bevel type against the flange of the profile section where
coinciding with cutout contour
BSHELL (DECIMAL) Bevel type against the plate that is carrying the profile.
BCSHELL (DECIMAL) Bevel type against the plate that is carrying the profile
where coinciding with panel contour. For an explanation of the bevel
types, see below:
The parameters WELD-BCSHELL should be regarded as default values for the clip. They
will be overridden if corresponding values are given as user input.
TCODE (INTEGER) Treatment code:
0 = standard part (i.e. stock material). This code implies that the clip will
not be stored as an individual plate part and it will not be assigned a
position number by the setposno program.
1 = will be treated a true "part" by the system.
DESIGNATION (STRING) Designation of the clip (of special interest when the clip
should not be position numbered but considered as stock material).
POS (INTEGER) Position number of the clip.
DESTINATION (STRING) Destination of clip.
INSERT_CODE (INTEGER) This flag can be used in the special case when a clip is
"inserted" into the cutout.
0 = Ordinary clip on panel surface. This is the normal situation.
1 = "Inserted" clip. It will be placed symmetrically "inside" the panel, see
below.
The connection angles of the clip edges against the web, the flange and the shell plate are
calculated automatically.
Example:
1.clip-code
|
| 2. macro-name
| |
| | 3. no_of_profile_types type1 type2, etc.
| | |
| | | 4. no_of_cutout_types,
| | | | type1, type2, etc.
| | | |
101 'clip1a' 3 30 31 32 2 505 506
101 'clip1b' 3 30 31 32 2 507 508
101 'clip1c' 1 10 2 505 506
102 'clip2' 1 10 3 101 102 103
103 'clip3' 3 10 20 30 1 100
A setup file contains a number of lines, normally one for each clip macro. One line may have
up to 500 characters. Each line contains the following information:
1. The clip code.
2. The name of the clip macro implementing this clip code.
3. A group of numbers selecting for what profile types this clip macro is valid.
4. A group of numbers selecting for what cutout types this clip macro is valid.
From the example file it can be seen that clip code 102 is valid for flat bars (profile type
10) and for cutout types 101-103.
The example also shows that the same clip code can be used more than once in the
setup file. Clip type 101 is implemented with different macros depending on the profile
type and the cutout type.
The hull utility inithull can be used to check if the file syntax is correct.
! ****************************************************************
! NAME:
!
! PURPOSE:
!
! This macro calculates the clip contour for:
!
! DECLARATION:
!
! Parameters:
! RESULT:
!
! Parameters:
! ______________________________________________________________
! The following parameters are optional in the sense that they need
! only be assigned a value if this is relevant.
! However they are always required in the macro head and should thus
! always be declared as output parameters.
! ______________________________________________________________
! DESTINATION Destination
! **************************************************************
MACRO, 'clip_1',
VERSION2,
PROF_TYPE,
PROF_PARAM1,
PROF_PARAM2,
PROF_PARAM3,
PROF_PARAM4,
PROF_PARAM5,
PROF_PARAM6,
V2,
V3,
V4,
WEB_FACTOR,
FLANGE_FACTOR,
PLATE_THICKNESS,
CLIP_LOC,
CUT_TYPE,
PARAM1,
PARAM2,
GAP_M,
GAP_N,
GAP_T,
C_MEAS,
CLIP_THICKNESS,
SURFACE,
QUALITY,
EXCESS,
CLIP_CONTOUR,
INTERVALS,
INTERVAL_TYPES,
WELD,
WCLIP,
WPROF,
WSHELL,
BCLIP,
BWEB,
BCWEB,
BFLA,
BCFLA,
BSHELL,
BCSHELL,
POS_CODE,
DESIGNATION,
POS,
DESTINATION,
INSERT_CODE,
ASSEMBLY,
RESULT,
MESSAGE;
!
DECLARE,VERSION2, INTEGER;
DECLARE, PROF_TYPE, INTEGER;
DECLARE, PROF_PARAM1, DECIMAL;
DECLARE, PROF_PARAM2, DECIMAL;
DECLARE, PROF_PARAM3, DECIMAL;
DECLARE, PROF_PARAM4, DECIMAL;
DECLARE, PROF_PARAM5, DECIMAL;
DECLARE, PROF_PARAM6, DECIMAL;
DECLARE, V2, VECTOR_2D;
DECLARE, V3, VECTOR_2D;
DECLARE, V4, VECTOR_2D;
DECLARE, WEB_FACTOR, DECIMAL;
DECLARE, FLANGE_FACTOR, DECIMAL;
DECLARE, DECIMAL;
PLATE_THICKNESS,
DECLARE, CLIP_LOC, INTEGER;
DECLARE, CUT_TYPE, INTEGER;
DECLARE, PARAM1, DECIMAL;
DECLARE, PARAM2, DECIMAL;
DECLARE, GAP_M, DECIMAL;
DECLARE, GAP_N, DECIMAL;
DECLARE, GAP_T, DECIMAL;
DECLARE, C_MEAS, DECIMAL;
DECLARE, CLIP_THICKNESS, DECIMAL;
DECLARE, SURFACE, STRING;
! Local declarations
! V2 is the normalized 2d vector along the flange
DECLARE, V2_X, DECIMAL;
DECLARE, V2_Y, DECIMAL;
! C0 - C5 define the node points of the clip contour.
!
! Some additional variables
DECLARE, DIST1, DECIMAL;
DECLARE, DIST2, DECIMAL;
DECLARE, DIST3, DECIMAL;
DECLARE, FIXED_R1, DECIMAL;
DECLARE, OVERLAP, DECIMAL;
DECLARE, Q0, POINT_2D;
DECLARE, RES, INTEGER;
DECLARE, V1, VECTOR_2D;
DECLARE, V2_NEG, VECTOR_2D;
DECLARE, WB1, POINT_2D;
DECLARE, WB2, POINT_2D;
DECLARE, X0, DECIMAL;
DECLARE, Y0, DECIMAL;
! **************************************************************
! **************************************************************
ASSIGN, POS_CODE, 1;
! DIST1 is the gap between the bottom side of the clip and the plate
! carrying the profile.
! DIST3 is the gap between the top side of the clip and the (top side)
! of the flange.
! V1 is a vector along the web of the profile cross section, i.e. along
! the V-axis of the local clip coordinate system.
! ---------------------------------------------------------------
! ---------------------------------------------------------------
IF, CLIP_LOC == 1;
! C2 C3 defines the starting and ending point on the upper arc segment
! with radius FIXED_R1.
CALL, 'fillet_radius_2d',
C1, V2_NEG, Q0, V1_NEG, FIXED_R1, C2, C3, RES;
! C4 C5 defines the starting and ending point on the lower arc segment
! with radius FIXED_R1
CALL, 'fillet_radius_2d',
C3, V1_NEG, C0, V2, FIXED_R1, C4, C5, RES;
! Calculate the start and the end point of the bevel/welding interval
! that overlaps the penetrated plate.
! ---------------------------------------------------------------
! ---------------------------------------------------------------
IF, CLIP_LOC == 2;
! Set DIST2
CALL, 'fillet_radius_2d',
C1, V2, Q0, V1, FIXED_R1, C2, C3, RES;
! C4 C5 defines the starting and ending point on the upper arc segment
! with radius FIXED_R1
CALL, 'fillet_radius_2d',
C3, V1, C0, V2_NEG, FIXED_R1, C4, C5, RES;
! Calculate the start and the end point of the bevel/welding interval
! that overlaps the penetrated plate.
CONTOUR, CLIP_CONTOUR, C0
/LINEEND = C1
/LINEEND = C2
/ARCRADIUS = ( C3, FIXED_R1)
/LINEEND = C4
/ARCRADIUS = ( C5, FIXED_R1)
/LINEEND = C0;
INTERVALLIST_2D, INTERVALS
/APPEND = ( C0, C1)
/APPEND = ( WB1, WB2);
These pictures show the resulting clip generated with the example macro "clip_1". In this
case the penetrating profile is perpendicular to the plate.
(The cutout is of main type 5, generated via the external cutout definition.)
The Hull application has a built-in facility for definition of simple clips with straight edges.
The geometry of these clips is so simple that they traditionally have been manufactured by
‘clipping’ rather than by burning. (This is actually the reason for the name ‘clips’ for this type
of parts in Aveva Marine.)
A cutout may be supplied with at most three clips of this type:
• One on the moulded side of the profile
• One on the non-moulded side
• One on top of the profile.
The clips are picked by a three-digit code (XYZ). The significance of the digits are:
X Specifies the location of the clip on the mould line side of the profile section
Y Specifies the location of the clip on the non mould line side of the profile section
If any of XYZ is zero this means that the corresponding clip is missing.
The table below shows how different values of XYZ control the position of the clips relative
to the profile section.
Clip 1
The constants below are examples that may be used by the system to control the position of
the clips. These values and rules that are used in generating the clips are glued into the
code and cannot be changed by the customer or end user.
From these built-in rules the system evaluates both the size and location of the clip.
However, the automatically evaluated size of the bracket (length/width/thickness) may be
overridden by user input when generating the cutout/clip. For details refer to Hull Detail
Design / Planar Modelling / Design Language of Hull Modelling / Cutout Statement.
Clip 2
For the exact positioning of clips, the following instances may occur:
F=0
F = 20 at drainage cut-outs measured from the top edge of the drainage cut-out
F = 40
G=0
Note: For welded angle profiles is GS = 20 first chosen for the positioning of clips and the
side opposite to the mould side. If by this the clip area will become insufficient,
choose G = 60 + I in stead
FT respectively GT = 0
FT respectively GT = 20
13 Cutout Settings
13.1 Background
In a project, many different types of cutouts are used for different types of profiles. In order
to get this organized, this tool makes it possible for the system manager to set up the cutout
standard to use in a project. The result of this tool is that after a profile section is indicated,
only those cutouts defined in the project that is available for the profile type will be presented
for selection.
The statements need not be in any particular order and there may be more than one
statement for the same cutout in one file.
Syntax:
<cutout> <profile>
<cutout> An integer number or a named cutout representing the
cutout.
<profile> The profile type that the cutout is valid for
If a named cutout is used, then also the clip arrangement will be presented.
1 10
1 20
1 30
1 31
1 33
1 40
1 43
2 10
2 30
2 31
2 40
2 43
The following is an example of the usage in Hull Modelling Create Statement for Cutouts. In
this example a profile type 31 has been indicated and available cutouts are presented for
selection.
Brackets
1 Bracket Types
1.1 General
"Bracket" is in shipbuilding the common denomination of plate parts used as connection
pieces between structural members of the steel structure, e.g. in connection plate-plate,
plate-profile or profile-profile. They are normally rather small, often "triangular" (with two
arms connected by a free side) but may also be comparatively large, have three arms, be
stiffened, etc. The picture below shows some typical bracket connections.
There is no sharp distinction between a bracket plate and an "ordinary" plate part - they may
look very much the same. It is more a matter of definition that is up to the individual yard to
make. The reason to identify a plate part as a bracket may be that they are handled
differently from other plate parts in production, e.g. have special production lines, be named
for production differently from other plate parts, etc.
• In the ship model a bracket must always belong to a panel, i.e. it can only be accessed
in the hull structure via the panel it belongs to.
Brackets are often standardised regarding their general shape, how they are stiffened and
not least how they are related to other elements that they connect or support. For this type
of standardised brackets the system has an advanced facility that allows a customer to set
up his own brackets standards. Moreover, a default standard bracket set-up goes along with
an installation of the Hull application. These brackets are called type standard brackets
(because they are identified by their type (name)).
Some brackets cannot be described as type standard brackets because they are so special
that they cannot easily be controlled by standard parameters. An example of such a bracket
can be found in the figure below.
Figure 1:2. A bracket that must be generated as a panel bracket or as a “contour bracket”.
3. The edge contour may be either a straight line or the true limit shape may be
approximated by one arc. The amplitude of this arc will automatically be calculated in
such a way that the bracket edge fits correctly in its end points and in the midpoint. The
fitting is in most cases satisfactory but may - in case the curvature of the limit is very
"irregular" - require that the bracket is generated as a panel bracket instead.
4. The basic toe types available are documented in Standardised Bracket Toes including
a specification of relevant parameters. Some of these parameters are normally derived
automatically from the surrounding structure, others defined in the set-up of a bracket,
whereas finally some may be set directly by the end user when generating the bracket.
5. The free side of the bracket may be associated with a folded flange which forms part of
the actual bracket geometry. The shape of this folded flange is under full customer
control.
6. Notches may be inserted in the corners of the bracket for the bracket individually
depending on the type of bracket and bracket toes. Most existing corner notches may
be used. It is possible to set up default rules for the notches to select.
Note: It is possible to use corner notches also in brackets with overlaps along one edge -
the notch geometry will automatically be adjusted to fit correctly. In the figure below a
simple standard circular notch (type R) has got its origin at the edge of the
overlapped profile. The notch contour has been extended perpendicular to the profile
edge. The figure also shows the result if the user specifies an unsymmetrical notch
(type VU) instead. (This way of using corner notches in relation with overlaps can
only be used in type standard brackets.)
1.4.3 Stiffening
The free edge of the bracket may be stiffened in three different ways:
1. By a folded flange (see above)
2. By a welded flange (face plate), either welded symmetrically (forming a symmetrical T
section) or asymmetrically (forming an asymmetric T section). This flange may either
be straight or curved depending on the shape of the free edge of the bracket.
3. By a stiffener, welded parallel to the free edge (or part thereof) at a specified distance.
This stiffener may be double, i.e. occur on both sides of the bracket.
In addition it is possible to specify at most four additional stiffeners in the interior of a
bracket, all set parallel to the free edge. Options are available to control the number of
stiffeners as a function of the size of the bracket and to control their position and
dimensions in a similar way.
When calculating the end points of a bracket stiffener the specified distance is by
default calculated between the edge and the closest point of the stiffener (=d1). By
adding the default parameter BKT_OLDPROF to the default file of Hull Modelling the
distance will be calculated to the closest end point on the mould line instead (=d2), see
the figure below.
As further developed below, the bracket definition file can be extended interactively via a
wizard in the inithull module.
In this way the file can be used as a starter (pattern) for a customer in defining his own
standards. Many of the brackets are very similar to each other (almost duplicates!) and a
customer is encouraged to remove those brackets which are of no interest in order to
reduce menu sizes in picking of brackets.
For a couple of brackets (types KL and K) following paragraphs contain the detailed
specification upon which the bracket definition has been made. The remaining brackets
have been created according to similar principles.
Type Standard Bracket KL contains a specification of the most simple of all brackets (type
KL) with the option of having at most one stiffener parallel to the free edge.
Type Standard Bracket K contains a specification of a big bracket (type K) which may have
a different number of stiffeners parallel to the free edge depending on the size (depth) of the
bracket.
This appendix contains the specification of the bracket KL. This specification is the basis for
the bracket set-up data in the definition file going along with a standard delivery of Hull.
The bracket is set-up based on the following conditions in addition to what can be
interpreted directly from the figure above.
1. The bracket is symmetric, i.e. the definition of arm B is equal to arm A.
2. If the length of the stiffener (L1) becomes larger than 700 mm the stiffener should
normally be set.
3. The size of the stiffener should be picked from the set of standard dimensions for
bracket profiles available for this and similar types of brackets. It should also have the
same quality (grade).
4. The profile size should be picked whose cross-section area is the closest smaller value
compared to 0.1*t*L (L in the figure above, t is the plate thickness).
5. Plate thickness and size (A, B) to be given by the designer if not calculated from
geometrical constraints.
6. This bracket may occur in many different types of connections.
7. If the bracket size is defined by a "gap connection" to an intersecting stiffener or to a
free edge the gaps/overlaps should be as in the figures below.
This appendix contains the specification of the bracket K and it is the basis for the bracket
set-up data in the definition file going along with a standard delivery of Hull. This bracket is
normally large and the number of stiffeners will vary with the size of the bracket.
The bracket is set-up based on the following conditions in addition to what can be
interpreted directly from the figure above.
5.1 General
This document specifies in detail a facility that is intended to be used to adapt the bracket
standard to the needs of a certain customer.
The final shape of a bracket is affected by a large number of factors, most of them possible
to set up rules for. These factors may be related to the shape of the bracket plate, rules for
how the bracket should be stiffened and for how it should be connected to the structure
surrounding it, etc.
Via Bracket Set Up Facility it is possible for customers to control many of the features of
brackets and set up their own standards. This is done by writing definition data in an
ordinary text file in a special language based on the Interpretative Language (TIL). The
format and the handling of the bracket definition file are described in detail in the current
document.
The inithull module has a function by which brackets in the setup file can be modified
interactively via a wizard. This module can also be used to create quite new brackets. The
result will be an updated bracket definition file that has to be compiled for the new/modified
brackets to become available for use.
Typically, the low level statement types define standard bracket toes, standard connections
of bracket toes and available profile types. - The very top level statement type is the one that
defines a bracket with reference to much of the information, created by the other
statements.
The statements must be given in a logical order, i.e. information that is referred to from one
statement must have been defined in another statement earlier in the input file.
• If there are several stiffeners on a bracket they are all supposed to be parallel.
Except for folded flanges the stiffening of a bracket means that profiles are welded to the
bracket. A set of profiles (types, dimensions) available for the bracket stiffeners can be
defined in a PROFILE statement. Many independent such sets may be defined, e.g. to be
used in different brackets.
The PATTERN statement specifies the location of the stiffeners on a bracket. Each pattern
is valid when a bracket has a certain number of stiffeners. For certain brackets the number
of required stiffeners may increase as the bracket size grows. This means that there must
be a number of patterns set up for such a bracket, each valid in case of a certain number of
stiffeners, e.g. one pattern when there is one stiffener, another when there are two, etc. The
position of bracket stiffeners in the interior are normally supposed to be depending on the
depth of the bracket.
In addition the PATTERN statement specifies how the profile dimensions should be selected
from the profiles available in a certain profile set, selected for the current bracket. Normally
the profile section is supposed to be compared to a tenth of the profile length times the
bracket thickness. Suppose that the profile length is L and the bracket thickness t. Let A =
L*t/10. Then the profile should be selected whose cross section area is comparable to A
(times a factor which is normally close to 1). Further details will be found in relation with the
PATTERN statement.
The STIFFENER statement specifies the stiffener pattern to select as a function of the
bracket size, specifies the profile set to be used and also the endcuts of the stiffeners (which
are all supposed to have the same endcut). The FACE_PLATE statement is used in a
similar way for welded flanges.
The different statement types will be specified in subsequent paragraphs of their own in this
document in the logical order, which is the order in which they are presented above.
Syntax:
<set_name> A name (string not longer than eight (8) characters) that
uniquely identifies a certain set of profile dimensions.
Can be left out if there is only one set.
DIM Specifies the profile type and dimensions. The profiles
should be sorted in increasing cross-section area.
Should be given in accordance with the standards.
The number of dimensions is unrestricted.
Syntax:
TOE, <user_name>
/ TYPE = <toe_type>
[ / TOE_H = < h > ]
[ / H_TOT = < h > ]
[ / O_LAP = < lap1 > [,< lap2 >, [ < lap3 >] ] ]
[ / O_LAP_LIM = < lim1 > [ ,< lim2 >] ]
[ / R_ANG = < r > ]
[ / TOE_L = < len1 > [,< len2 >, [ < len3 >] ] ]
[ / TOE_L_LIM = < lim1 > [ ,< lim2 >] ]
[ / RAD = < r >
[ / R_CORN = < r > ]
[ / R_LUG = < r > ]
[ / KNUCKLE_PT ]
;
H_TOT Total toe height. To be defined for toe types 13, 15.
Normally to be calculated by the application for toe types 31, 32,
33, 34, 35, 36, 131, 132, 133, 134, 135, 136.
Otherwise irrelevant.
O_LAP Overlap at (normally perpendicular to) the profile edge. The
overlap may be dependent on the bracket thickness (see
O_LAP_LIM below). At most three values can be given.
Compulsory for toe types 2, 4, 9, 31, 32, 33, 34, 35, 36, 102,
131, 132, 133, 134, 135, 136.
O_LAP = -1 has for the toe types 33 and 133 the meaning that
the overlap should be set equal to the profile height minus the
radius at the lug, cf. the figure below.
Irrelevant otherwise.
TOE_L Length of toe along edge. The toe length may be dependent on
length of the bracket arm (see TOE_L_LIM below). At most
three values can be given.
Must be given for toe types 3 and 4. (May be overridden by user
input). (Must be calculated by the application for toe types 12,
13, 14).
Irrelevant otherwise.
= -1 means that the toe length should be calculated by
projection of TOE_H (or H_TOT) of the opposite toe on the
current arm, e.g. when combined with a connection of type 7.
See figure below, showing a toe of type 3 the length of which is
calculated by projection of the other toe.
RAD (=R_TOE) Radius associated with certain toe types (8, 9, (11,)
12, 13, 14). This radius may often be changed or given directly
by the end user.
= -1 Means that the radius must be given via input at run time.
< -1 May in certain cases be relevant and used to indicate an
amplitude instead of a radius, e.g. in a situation like the one
below where two toes of type 8 are connected to form the free
edge of three-edged bracket (the left figure below). In a similar
situation a toe type 11 (which otherwise is not supposed to be
combined with a radius) can be assigned a radius, both in the
TOE statement and as user input in the generation phase (the
right figure below).
Syntax:
CON, <user_name>
/ TYPE = <con_type
/**** Next options only for con. type 1 (and partly type 2) ****/
[ / CL_TS = < s > ]
[ / CL_OS = < t > ]
[ / CL_FREE = < u > ]
/**** Next options only for con. type 2 ****/
[ / TIGHT_H = < h > ]
[ / FLAT_DX = < x > ]
[ / FLAT_DY = < y1 >, [<y2>] ]
[ / FLAT_LIM_A = < a > ]
[ / FLANGE_DX = < dx > ]
[ / FLANGE_DY = < dy > ]
/**** Next options only for con. type 3, 4, 5, 6 and an 7 ****/
[ / LAP = < f > ]
[ / PT_CTRL = < n > ,[ / PT_FACT = < pt_f > ] ]
[ /DIST = < d1 > [, <d2> / DIST_LIM_A = < a > ]
;
<user_name> is a unique user defined name of the connection type. Its length is
restricted to eight (8) characters.
TYPE= 0:
Default, free bracket end. The length of the bracket arm is normally supposed to be given by
the user. This connection has no options or additional parameters. For a typical case, see
figure below.
TYPE= 1:
Connection with gap to an intersecting profile (or to a free edge). In case of profile the
connection may take place with the bracket on the same or the opposite side compared to
the profile. Can be used together with toe types 1, 3, 8, 13 and 15. Even if defined it may not
be applicable in all connection cases, e.g. if defined for a bracket used in syntax 2 the
connection type is disregarded because in this syntax the bracket arm is always free and its
CL_TS
CL_OS See s, t and u, resp., in figure below.
CL_FREE t should be negative in the case illustrated below, i.e. when the
bracket passes the intersections stiffener.
TYPE= 2:
Tight connection to either side of a profile section (or to a surface in general). Is compulsory
for toe types 11, 12, 14 and 15. See the figures below.
CL_TS See 's' in the figure above. This toe type has a tight
connection to the intersecting member, but sometimes a
welding gap should be inserted. 's' is supposed to be a small
number.
TIGHT_H See 'h' in the figure above. The default height for connection
to an unrestricted surface. It can always be overridden by the
user.
All the keywords, starting in FLAT_ are relevant when connecting a toe to the flat side of a
profile section (as in the figure b above).
FLAT_DX 'x' in the figure above. Default is 0.
FLAT_DY 'y' in the figure above. The distance from the top of the profile
to the upper end of the bracket toe. One or two values may be
given. In case of two values the first is used if the angle is <
FLAT_LIM_A (v in the figure above), the second otherwise.
FLAT_LIM_A 'v' in the figure above. Default is 45 degrees.
All the keywords starting in FLANGE_ are relevant for connection to the side of a profile
section in which there is a flange (see fig. a above).
FLANGE_DX Normally the toe length is set equal to the free width of the
flange. Any change to this default should be given in this
option. >0 means addition to the default value, <0 means
subtraction.
Adding 10000 to the value (>0) means that a fixed toe length
should be given independently of the flange width.
FLANGE_DY 'dy' in fig. a above. Distance from the top of the profile to the
upper limit of the bracket toe. Normally this distance is
calculated from the lower edge of the flange (dy>0). If dy<0
then the distance will be calculated from the upper surface of
the flange. Adding 10000 to the value (>0) means that a fixed
toe height should be given independently of the profile height.
In calculating the flange thickness and flange widths of bulb
bars the following approximations have been made. FL_T is
the used flange thickness and FL_W is the used flange width.
This means that the connection will be evaluated as if they had been against an L-bar
of the size indicated by the dashed line in the figures above.
TYPE= 3:
Overlap of profile end without lug with one straight line in overlap edge. No fillet welding
along edge - see figure below. Relevant parameters described below the figure. Compulsory
for types 31, 32, 131, 132.
.
LAP See 'f' in the figure above. Specifies the overlap as a factor (that is
supposed to be multiplied by the profile height). If missing, 'f'=1.5 will
be used.
DIST See 'd' of the figure above. Distance from intersection point between
panel and profile trace to origin of bracket. Two values may be given
(d1 and d2), the first to be used when the connection angle is < 'a' (see
the figure above, = DIST_LIM_A), the second otherwise.
DIST_LIM_A Angle 'a' in figure above. Cf. also DIST.
TYPE= 4:
Similar but with lug of bracket welded against plate, see the figure below. Relevant
parameters described below the figure. Compulsory for toe types 33, 34, 133, 134.
TYPE= 5:
Similar to 4, but with a "free" lug of the overlap edge, see figure below. Relevant
parameters described below the figure. Compulsory for toe types 5, 36, 135, 136.
Common to connection types 3, 4 and 5 is that the position of the free side of the bracket
may be affected by an extra control point through which the free edge (or its extension) is
supposed to pass. The options PT_CTRL and PT_FACT can be used for this purpose, see
the figures below.
PT_CTRL Specifies a control point controlling the direction of the free side.
=1 The control point in located in the extension of the web endcut of
the overlapped profile, see figure a above.
=2 By a point perpendicular to the profile trace at a given distance, see
figure b above.
PT_FACT See 'pt_f' in the figures above. This is a factor used to calculate the
distance of the control point by multiplication with the profile height.
If, for a connection type 3, 4 or 5, PT_CTRL is undefined, then
PT_CTRL=1 is supposed to be valid.
If PT_FACT is undefined, then 'pt_f'=0.5 if PT_CTRL=1, else if
PT_CTRL=2 then 'pt_f'=2.0.
TYPE= 6:
Connection where bracket is attached along the edge of a profile. The bracket arm length is
defined as a factor times the profile height and an optional control point is used to control
the shape of the toe. Can be used together with a toe of type 1 (and possibly 2 and 102).
(Supported only in syntax 1.)
LAP 'f' in the figure above. Multiplied by the height ('H') of the 'profile along'
this is used to calculate the (default) length of the bracket arm (default
is 1.5).
PT_FACT See 'pt_f' in the figure above. When multiplied by the profile height the
resulting distance is used to position a point, controlling the direction of
the free side. Default value is 1.0.
TYPE= 7:
Simple free toe where the length of bracket arm is defined as a factor times the total height
('h') of the opposite bracket toe see figure below.
Connection types 6 and 7 are supported in syntaxes 1 and 7. However, when connection
type 6 is used in syntax 7 the length of the bracket arm (normally B) must be given explicitly
by the user. These connection types can be used only in combination with certain toe types,
both in the current bracket arm and in the opposite arm.
Connection types 3, 4 and 5 will be supported in syntaxes 5 and 6 but are not yet
implemented.
Syntax:
<set_name> A name (string shorter than eight (8) characters) that uniquely
identifies a certain notch selection rule.
NOTCH_TYPE Specifies the notch to be used. If the notch type/size should be
dependent on the length of the surrounding edges then < not1 >
will be used up to < L1 >, < not2 > up to < L2 >, etc. The
length of each notch definition is restricted to 24 characters.
No notch at all is indicated by assignment of an empty string (' ').
LIMIT_SIZE Specifies the length of the shortest of the two surrounding edges, up
to which the previously defined notch should be used. Should be
given in increasing sizes.
The LIMIT_SIZE attribute should follow after the NOTCH_TYPE
attribute.
If the number of notch types added to NOTCH_TYPE is N, then N-1
values must be assigned to LIMIT_SIZE.
Example:
NOTCH, NOT_KL
/ NOTCH_TYPE = (KS10, R30, R50)
/ LIMIT_SIZE = (250, 500)
;
Note: If the notch type contains a mathematical operator (e.g. an asterisk (*)) then it must
be surrounded by apostrophes (‘).
Syntax:
CUTOUT, <name>
< name> A name (string shorter than eight (8) characters) that uniquely identifies
a certain cutout selection rule. The same name may be used in several
statements provided the profile types occur only once in a rule with a
certain name. Thus one specific rule may be the result of several
CUTOUT statements.
CTYP The cutout type to be used
PROF The profile types for which CTYP should be valid in this cutout selection
rule.
The same cutout selection rule may be referred to from any number of brackets.
Example:
Example:
CUTOUT, CUT_BKTA
/CTYP = 31
/PROF = 10
;
CUTOUT, CUT_BKTA
/CTYP = 308
/PROF = (20,30,31)
;
CUTOUT, CUT_BKTB
/CTYP = 31
/PROF = 10
;
CUTOUT, CUT_BKTB
/CTYP = 305
/PROF = (20,30,31)
;
Syntax:
< pattern_name> A name (string not longer than eight (8) characters) that uniquely
identifies a certain stiffener pattern specification.
NO_STI Number of stiffener positions in this pattern. Should be 1 for face
plate.
This attribute must be given before any of those where the
number of arguments are depending on < N >.
DOUBLE Means that the first stiffener should be doubled, i.e. one stiffener
on each side. Both stiffeners should be equal and the given
factor should be shared half for each of them.
LOCATION Specifies the distance of the stiffeners from the free edge (or
possibly part of it, e.g. an arc, cf. below), with one specification
for each stiffener position. Should be 0 for a face plate.
Suppose that the depth of the bracket perpendicular to the free
side is Z. The position is always given as a distance from the
free edge (or a specified part of it).
<loc> >1 means that the distance is given explicitly,
<loc> <1 means that the distance is given as a factor.
<loc1> is used for stiffener position 1, <loc2> for stiffener
position 2, etc.
SIZE_FACTOR Specifies a factor that shall be used for the calculation of the
profile dimensions. <fact1> is used for the stiffener in position 1,
etc. One size factor shall be given for each of the stiffeners of
the given pattern. For more details, see below.
LENGTH_NO Specifies the length that shall be used in the evaluation of the
dimension of each of the profiles:
= 0 means L0,
= 1 means L1, etc.
Suppose that stiffener 2 shall be calculated and the following values have been assigned:
RULE =1
<loc2> =0.45
<fact2> =0.4
<No2> =0
Bracket thickness =1
Then stiffener number 2 will be located 0.45*Z from (and parallel to) the free edge.
Let A = L0*t/10. The profile size (among the available standard dimensions) will be selected
whose cross-section area is closest to 0.4*A.
Following example corresponds to the situation for a bracket that may have up to three
stiffeners. Three different patterns must be defined corresponding to the case that the
bracket has 1, 2 and 3 stiffeners, respectively.
Example:
PATTERN , PAT_A_1
/ NO_STI = 1
/ RULE = 1
/ LOCATION = 20
/ SIZE_FACTOR = 1.0
/ LENGTH_NO = 0;
The pattern definition for the same bracket when there are two stiffeners should be:
PATTERN , PAT_A_2
/ NO_STI = 2
/ RULE = 1
/ LOCATION = (20, 0.4)
/ SIZE_FACTOR = (0.6, 0.4)
/ LENGTH_NO = (0, 0);
PATTERN , PAT_A_3
/ NO_STI = 3
/ RULE = 1
/ LOCATION = (20, 0.28, 0.59)
/ SIZE_FACTOR = (0.6, 0.4, 1.0)
/ LENGTH_NO = (0, 0, 3);
Syntax:
<set_name> Is a name (string not longer than eight (8) characters) that
uniquely identifies a stiffener pattern in a bracket.
PROF_SET Specifies the name of a set of profile dimensions that shall be
used when picking the profile. This set must previously have
been defined in a PROFILE statement.
MIN_LENGTH Normally stiffeners shorter than MIN_LENGTH will not be
accepted (unless explicitly asked for by the user). Default
value is 700 mm.
END1_CUT Defines the endcut (type and parameters according to
standards) for end 1 of the stiffener (close to arm A of the
bracket).
If there is more than one stiffener they are all supposed to
have the same endcut.
END1_DIST Distance from end 1 of the stiffener (close to arm A of the
bracket) from the contour of the bracket (see the figure below).
Valid for all stiffeners on the bracket.
END2_CUT Ditto for end 2 of the stiffener (close to arm B).
END2_DIST
PATTERN Defines the name of the pattern that should be applied for the
bracket. The patterns referred to must have been defined
before in one or several PATTERN statements.
Several patterns can be defined to be selected depending on
the depth of the bracket (denoted Z, see the PATTERN
statement above). The first pattern (<pt1 >) will be used when
Z <= <size1>, etc.
If a certain pattern is set to an empty string (' ') this means that
in 4the corresponding size interval there should not be any
stiffener at all.
Syntax:
PATTERN Defines the name of the pattern that should be applied for the
flange. The patterns referred to must have been defined before
in a PATTERN statement.
Several patterns can be defined to be selected depending on
the depth of the bracket (denoted Z). The first pattern ( <pt1 >
) will be used when Z <= <size1 >, etc.
(This means e.g. that a given bracket may have no profile at all
up to certain size, then in the next size interval have a stiffener
set parallel to the free edge, and finally in another size interval
have a welded flange).
If a certain pattern is set to ' ' (an empty string) this means that in
the corresponding size interval there should not be any face
plate at all.
SIZE_LIM Cf. PATTERN. The values should always be given in increasing
order.
The SIZE_LIM attribute must come after the PATTERN
attribute in sequence.
If the number of values assigned to PATTERN is N, then the
number of values assigned to SIZE_LIM must be N-1.
OVER_SHOOT A face plate is normally placed symmetrically relative to the
plate surface of the bracket. The attribute OVER_SHOOT can be
used to control that the face plate should be placed
asymmetrically.
The distance given is the offset outside the mould plane of the
bracket in the direction opposite to the "positive profile side"
(defined by PSID in the generation).
A face plate with an offset will be stored as a stiffener, whereas
symmetrical face plates are stored as flanges.
Syntax:
<flange_set> A name (string) that uniquely identifies a certain set of heights and
calculation rules (<= 8 characters).
TYPE Number that specifies the flange type to be used in this set. Must be
selected from one of the types defined in the flange control facility .
If left out the default flange type will be used.
END1_FLANGE Number that specifies the flange end type to be used in end one of
the flange (close to arm A of the bracket). Must be selected from
one of the flange end types defined in the flange control facility.
If left out the default flange end type will be used.
END2_FLANGE Ditto end 2.
H Specifies allowable flange heights. The heights should be sorted in
increasing order.
RULE The flange height is selected based on the length of the free edge
(=L), divided by 10. I.e. the flange height should be picked from the
set of heights, assigned to H based on its relation to L/10.
= 1 Select closest height to L/10
= 2 Select closest to L/10 but smaller
= 3 Select closest to L/10 but larger
Creation of the actual geometry of the flange is controlled by the
normal flange control facility as described in the document referred
to above.
Syntax:
<name> Is the unique name of the bracket, used when the bracket is
generated. The name should start (and preferably end) in a letter
and be maximum 8 characters long.
Brackets defined in this facility are automatically activated, i.e.
will pop up in the menus of Component/Create/Brackets
without any separate action in accordance with the
specification of the attributes SYNTAX and SYMBOL below.
SYNTAX Specifies the connection cases (syntaxes) in which the bracket may
occur. The first of the given syntaxes is the default syntax, i.e. if not
explicitly specified by the user this syntax will be supposed in the
generation of the bracket. Syntax number 8 is the "free syntax"
when all bracket parameters will have to be supplied by the user.
SYMBOL Specifies the symbol number within the symbol font number 91
which is used in the interactive picking of the bracket type when
generating the bracket. If not given it is not possible to pick the
bracket by a symbol of it. It is the responsibility of the customer to
create an appropriate symbol for the bracket.
EDGE_3 Specifies that the bracket has three edges, i.e. two arms which are
connected by an "extra" connecting edge. If this option is left out the
bracket is supposed to have two arms connected directly to each
other.
TOE_A Selects a certain toe instance which must have been set up with a
unique name in a TOE statement and which shall be applied at the
end of bracket arm A. Two different toe selections can be assigned
in case of a tight connection (e.g. to a profile section). The first one
will be used for connection to a flat side, the second to the side of a
flanged side of a profile section (see the CONNECTION statement
above).
It should be noted that for brackets in syntaxes 1 and 5 bracket
arm A is always the bracket arm that is welded against the
plate surface.
CON_A Selects a certain toe connection instance with a unique name which
must have been set up in a CONNECTION statement and that shall
be used in the connection of bracket arm A to adjacent structural
members.
If not given, the bracket arm is supposed to be free.
It may happen that even if a connection has been defined that
connection is relevant only in certain connections and that in other
connections the bracket arm is free.
TOE_B Ditto for bracket arm B.
CON_B
STIFFENER Specifies the set of stiffening rules that should be applied for this
bracket. The referred stiffener set must have been defined with a
unique name in a previous STIFFENER statement. If not given, the
bracket will not get any stiffener. I.e. condition for a bracket to get
any stiffener at all is that the bracket has been set up with a stiffener
definition.
FACE_PLATE Specifies how a face plate should be positioned on the free edge of
the bracket. If not given, no face plate will be set.
This option and the FLANGE option (see below) are mutually
exclusive.
FLANGE Specifies the set of flange rules that should be applied for this
bracket. The referred flange set must have been defined with a
unique name in a previous FLANGE statement. If not given, the
bracket will not get any folded flange.
NOTCH Specifies a default notch selection set for use in the origin corner of
a bracket. The picked notch set must previously have been defined
with a unique name in a NOTCH statement.
If no NOTCH option has been given the bracket cannot have any
notch in this corner.
/ NOTCH=' ' (empty string) means that a notch may occur but
that no default notch exists.
NOA Ditto for notches at the end of arms A and B, respectively. May not
NOB be relevant for all toe types.
NOC Ditto for the notch at the start of arm A for a three-edge bracket
(only when the option EDGE_3 has been used).
The figure below specifies the corners where the notches may be
used.
5.4 Examples
Below you will find an example of a bracket definition file for the brackets are A, B and BK.
Bracket A is a big bracket that may have up to 3 stiffeners and whose toe lengths varies with
the bracket size.
Bracket B is a simple bracket with soft toes and maximum one stiffener.
Bracket BK is similar to B but is stiffened by a folded flange replacing the stiffener.
!
! Standard profile dimensions available for bracket stiffener.
! Used for all brackets.
PROFILE, STD_DIM
!
! Standard toe of basic type 11 (e.g. at arm A of A-bracket)
!
TOE, TA_A
/ TYPE = 11
;
!
! Tight connection of bracket A at toe A
!
CON, TIGHT
/ TYPE = 2
/ FLAT_DX = 0
/ FLAT_DY = (20, 0)
/ FLAT_LIM_A = 45
/ FLANGE_DY = 40
;
!
! Toe at arm B of A-bracket
!
TOE, TB_A
/ TYPE = 3
/ TOE_H = 15
/ TOE_L = ( 35, 100, 300)
/ TOE_L_LIM = ( 400, 800)
/ R_ANG = 10
;
!
! The patterns used for the A-bracket, see example in PATTERN
! statement
!
PATTERN, PAT_1_1
/ ......
;
!
! Stiffener definition for bracket type A (number of stiffener
! depending on size (depth=Z) of bracket)
!
STIFFENER, STI_A
/ PROF_SET = STD_DIM
/ MIN_LENGTH = 700
/ END1_CUT = ( 1302, 15)
/ END1_DIST = 50
/ END2_CUT = ( 1302, 15)
/ END2_DIST = 50
/ PATTERN = (PAT_A_1, PAT_A_2, PAT_A_3)
/ SIZE_LIM = ( 1100, 1850)
/ END_DIST_MOULD
;
!
! Definition of bracket A (arm B has no connection, is "free")
!
BRACKET, A
/ SYNTAX = (1.7)
/ SYMBOL = 10
/ TOE_A = TA_A
/ CON_A = TIGHT
/ TOE_B = STI_A
/ STIFFENER = ’’
/ NOTCH = ’’
/ NOA
;
!
! Soft toe (used e.g. for B-bracket)
!
TOE, T4
/ TYPE = 3
/ TOE_H = 15
/ TOE_L = 35
/ R_ANG = 0
;
!
! Connection with gap 50 mm (e.g. for brackets B and BK in syntax)
!
CON,GAP
/ TYPE = 1
/ CL_TS = 50
/ CL_OS = -50
/ CL_FREE = 20
;
!
! Standard stiffener "pattern" for brackets with one stiffener
! (e.g.B-bracket)
!
PATTERN, PAT-STD
/ NO_STI = 1
/ LOC = 20
/ LENGTH_NO = 0
/ RULE = 2
;
!
! Common stiffener definition for brackets with one stiffener
! (e.g.bracket B)
!
STIFFENER, STI_STD
/ PROF_SET = STD_DIM
/ MIN_LENGTH = 700
/ END1_CUT = ( 1302, 15)
/ END1_DIST = 50
/ END2_CUT = (1302, 15)
/ END2_DIST = 50
/ PATTERN = PAT_STD
/ END_DIST_MOULD
!
! Default notches for brackets B and BK
!
NOTCH, NOTCH_B
!
! Definition of bracket B (connection used only in syntax 1)
!
BRACKET, B
/ SYNTAX = (2, 1, 3, 4, 7, 8)
/ SYMBOL = 28
/ TOE_A = T4
/ CON_A = GAP
/ TOE_B = T4
/ STIFFENER = STI_STD
/ NOTCH = NOTCH_B
;
!
! Simple toe of type 1 with toe height 15 (used e.g. for BK-
! bracket)
!
TOE, T1_15
/ TYPE = 1
/ TOE_H = 15
;
!
! Standard flange definition for smaller flanged brackets (both a
! flange end type 2 with radius 75. Flange end type may have to
! be set up by flange control facility (SBH_FLANGE_CTRL)
!
FLANGE, FLA_STD
/ END1_FLANGE = 200
/ END2_FLANGE = 200
/ H = ( 100, 160, 220, 280 )
/ RULE = 1
;
!
! Definition of bracket BK
!
BRACKET, BK
/ SYNTAX = (2, 1, 3, 4, 7, 8)
/ SYMBOL = 29
/ TOE_A = T1_15
/ CON_A = GAP
/ TOE_B = T1_15
/ FLANGE = FLA_STD
/ NOTCH = NOTCH_B
;
Next follow two examples showing how two quite different brackets can be created using the
bracket definition language. The same profile standard is supposes as above.
First a bracket, called BMA, looking like the figure below. The height of the 'total toe height'
'h' is by default set to 150 by can be changed by used input.
TOE, TA_BMA
/ TYPE = 15
/ TOE_H = 15
/ H_TOT = 150
/ R_ANG = 30
;
CON, CONA_BMA
/ TYPE = 1
/ CL_TS = 25
/ CL_OS = -25
;
!
! Toe length of toe B calculated by projection of toe
! height A according to connection CONB_BMA
!
TOE, TB_BMA
/ TYPE = 3
/ TOE_H = 15
/ TOE_L = -1
/ R_ANG = 15
;
CON, CONB_BMA
/ TYPE = 7
/ LAP = 2
;
PATTERN, P_BMA
/ NO_STI = 1
/ RULE = 101
/ LOC = 20.0
/ SIZE_FACTORS = 0.14
/ LENGTH_NO = 1
;
STIFFENER, STI_BMA
/ PROF_SET = STD_DIM
/ END1_CUT = (1302, 15)
/ END1_DIST = 45
/ END2_CUT = (1302,15)
/ END2_DIST = 45
/ PATTERN = P_BMA
;
BRACKET, BMA
/ SYNTAX = 1
/ SYMBOL ??
/ CON_A = CONA_BMA
/ TOE_A = TA_BMA
/ CON_B = CONB_BMA
/ TOE_B = TB_BM
/ STIFFENER = STI_BMA
/ NOTCH = ’’
;
The next bracket is a similar bracket, however with different toes and connections at both
arms, see the figure below. The radius of the free side is by default set to 150 but may be
changed via input.
!
! Toe length of toe A calculated from connection type of
! arm B.
!
TOE, TA_BLA
/ TYPE = 13
/ TOE_H = 15
/ H_TOT = 150
/ R_ANG = 30
/ RAD = 150
;
!
! CONA_BLA same as CONA_BMA. Same definition could be
! used.
!
CON, CONA_BLA
/ TYPE = 1
/ CL_TS = 25
/ CL_OS = -25
;
TOE, TB_BLA
/ TYPE = 1
/ TOE_H = 15
;
CON, CONB_BLA
/ TYPE = 6
/ LAP = 1.5
/ PT_FACT = 1.0
;
PATTERN, BLA
/ NO_STI = 1
/ RULE = 301
/ LOC = 20.0
/ SIZE_FACTORS = 0.14
/ LENGTH_NO = 1
;
STIFFENER, STI_BLA
/ PROF_SET = STD_DIM
/ END1_CUT = (1302, 15)
/ END1_DIST = 45
/ END2_CUT = (1302, 15)
/ END2_DIST = 45
/ PATTERN = BLA
;
BRACKET, BLA
/ SYNTAX = 1
/ SYMBOL = ??
/ CON_A = CONA_BLB
/ TOE_A = TA_BLB
/ CON_B = CONB_BLB
/ TOE_B = TB_BLB
/ STIFF = STI_BLB
/ NOTCH = ’’
;
Finally a hint about the toe combinations that can be used to create some other typical
brackets, see the figures below. The indicated toe types are the basic types that should be
used for these brackets.
Figure 5:22. Bracket toes to be selected for some special bracket types.
6.1 Background
Brackets in general are normally small parts with two (sometimes three) arms at an angle to
each other. The ends of the arms are called the toes of the bracket. A bracket is often
generated by connecting two bracket arms by a "free" edge.
The extended bracket handling of specifically supposes that the shape of each of the two
free arms of a bracket may be defined by a length and a (generalized) toe with some
belonging parameters. The available toes are standardized to their general shape and to the
parameters controlling them.
This document specifies all the standardized bracket toes currently available in the Hull
system regarding general shape and parameters. Each toe type is identified by its number.
• Bracket Toe 1
Fixed: TOE_H
Given: LENGTH
• Bracket Toe 2
Given: LENGTH
2. The overlap may have several discrete values, e.g. depending on the
size of the bracket.
• Bracket Toe 3
There are three different cases for the evaluation of this toe:
1. The normal situation is that TOE_L is controlled via the bracket set-
up (or sometimes evaluated automatically by the modelling). Then
RAD is calculated from R_ANG and TOE_L.
3. All of R_ANG, TOE_L and RAD are given (in bracket set-up and/or by
the designer). Then the toe is over-determined. The following will
happen:
• R_ANG will be re-calculated. If the calculated angle is bigger
than the value from the bracket set-up the new value will be
accepted.
• If the calculated value is smaller (e.g. because the given RAD is
small in relation to TOE_L) then a line segment will be inserted
in the direction of the original value of R_ANG from the top of the
toe to the beginning of the arc. This case is illustrated by the
dashed contour above. In the other cases the result will be as in
the solid contour.
• Bracket Toe 4
Toe type 4 is similar to toe 3 but it has an overlap along the bracket arm.
The comments for toe type 3 are valid also for toe type 4 with the addition, that there is
another fixed parameter O_LAP. This parameter may have several discrete values as
defined in the bracket set-up.
• Bracket Toe 8
Remarks: 1. This toe type may only be used in a bracket, when the free edge of the
bracket consists of one arc. The toe it is connected to must be of a
similar type.
2. The radius of the arc segment connecting the bracket toes may be
calculated from the R_ANG parameter.
3. As an alternative the radius (RAD) may be given, and thus R_ANG will
be derived from this parameter.
• Bracket Toe 9
Toe type 9 is similar to toe 8 but it has an overlap along the bracket arm
Given: LENGTH.
Remarks: 1. This toe type may only be used in a bracket, when the free edge of the
bracket consists of one arc. The toe it is connected to must be of a
similar type.
2. The radius of the arc segment connecting the bracket toes may be
calculated from the R_ANG parameter.
3. As an alternative the radius (RAD) may be given, and thus R_ANG will
be derived from this parameter.
4. The overlap may have several discrete values, e.g. depending on the
size of the bracket.
• Bracket Toe 11
Fixed: [TOE_H]
Remarks: 1. This toe is normally used in a connection to (the flat side of) a profile
section or to a plate surface.
3. This toe may be used in combination with toe types 8 and 9 for
brackets with a one-arc free side.
• Bracket Toe 12
Fixed: [TOE_H]
Remarks: 1. This toe may be used to connect to a profile section when the
extension of the free side should intersect the bracket arm in a given
point. (This point will decide the value of TOE_L.)
• Bracket Toe 13
• Bracket Toe 14
Fixed: [TOE_H]
Remarks: 1. This toe may be used to connect to a profile section, especially if this
profile has a flange on the side to which the toe is connected (cf. toe
type 11).
2. This toe may be combined with a flange but then R_TOE must be
zero, because there is normally a separate radius definition as part of
the flange and set-up.
• Bracket Toe 15
Fixed: R_ANG.
3. Normally it is used so that the toe will look like a toe type 13, i.e. with
the free edge parallel to the bracket arm.
• Bracket Toe 31
• Bracket Toe 32
Remarks: 1 The angle (T_ANG) between the toe height and the profile is arbitrary.
. Normally it is chosen so that the toe height is parallel to the opposite
bracket arm.
• Bracket Toe 33
• Bracket Toe 34
The toe is almost like toe 33, except the parameter T_ANG
Remarks: 1. The angle (T_ANG) between the toe height and the profile is arbitrary.
Normally it is chosen so that the toe height is parallel to the opposite
bracket arm.
• Bracket Toe 35
A profile overlap similar to toe 33, but the lug has no radius and it is not welded to a panel
• Bracket Toe 36
The toe is almost like toe 35, except the parameter T_ANG
Remarks: 1. The angle (T_ANG) between the toe height and the profile is arbitrary.
Normally it is chosen so that the toe height is parallel to the opposite
bracket arm.
• Bracket Toe 37
Fixed: TOE_H.
Given: LENGTH.
2. The overlap may have several discrete values, e.g. depending on the
size of the bracket.
Remarks: 1. This variant is valid when R_CORN (see Bracket Toe 131, basic
variant) is 0, and is calculated as toe 31 supplied with a fillet in the toe
geometry.
2. The radius of the fillet (RAD) is derived from the toe geometry.
Remarks: 1. This variant is valid when R_CORN (see Bracket Toe 132, basic
variant) is 0, and is calculated as toe 32. The toe geometry is then
replaced with a fillet.
2. The radius of the fillet (RAD) is derived from the toe geometry.
Remarks: 1. This variant is valid when R_CORN (see Bracket Toe 133, basic
variant) is 0, and is calculated as toe 33 supplied with a fillet in the toe
geometry.
2. The radius of the fillet (RAD) is derived from the toe geometry.
Remarks: 1. This variant is valid when R_CORN (see Bracket Toe 134, basic
variant) is 0, and is calculated as toe 34 supplied with a fillet in the
toe geometry.
2. The radius of the fillet (RAD) is derived from the toe geometry.
Remarks: 1. This variant is valid when R_CORN (see Bracket Toe 135, basic
variant) is 0, and is calculated as toe 35 supplied with a fillet in the toe
geometry.
2. The radius of the fillet (RAD) is derived from the toe geometry.
Remarks: 1. This variant is valid when R_CORN (see Bracket Toe 136, basic
variant) is 0, and is calculated as toe 36 supplied with a fillet in the toe
geometry.
2. The radius of the fillet (RAD) is derived from the toe geometry.
7.1 General
The bracket set-up facility allows a customer to define a bracket standard of his own. In
doing that some parameters of the brackets are given specified values, e.g. toe heights, toe
lengths, etc. whereas other parameters are supposed to be evaluated or given by the user
when the bracket is used.
This paragraph specifies in detail a facility by which a customer may define default values
for some bracket parameters other than those that can be defined in the normal bracket set-
up file. Examples of such parameters are those defining the size and thickness of a bracket.
A set of bracket parameters for a certain bracket type is said to form an instance of the
bracket type.
Bracket instance definitions are created by writing definition data in an ordinary text file in a
special language based on The Interpretative Language (TIL). The format and the handling
of the bracket instance definition file are described in detail below.
Syntax:
BRACKET, <bracket_type>;
Syntax:
INSTANCE, <instance_name>
[/A=<A-measure>]
[/B=<B-measure>]
[/C=<C-measure>]
[/D=<D-measure>]
[/H=<H-measure>]
[/R=<radius>]
[/OFF=<offset>]
[/MAT=<thickness>]
[/QUA=<quality>]
[/BEV=(<bevel>[,<bevel>,<bevel>,<bevel>,<bevel>])]
[/NOTCH = < notch_name >]
[/NOA = < notch_name >]
[/NOB = < notch_name >]
[/NOC = < notch_name >]
[/COM=<comment>]
[/AS1=<general purpose string 1>]
[/AS2=<general purpose string 2>]
[/AS3=<general purpose string 3>]
[/AS4=<general purpose string 4>]
[/POS=<position number>]
;
Note: that it must start with the name of the bracket type
followed by digits or slash-characters (/). The bracket
instance name must be unique.
A A measure.
B B measure.
C C measure.
D D measure.
H Flange height.
R Radius of the free side.
OFF Distance the bracket is displaced from the profile plane.
MAT Bracket material thickness.
1.1 Background
Seams divide panels into plate pieces. When a seam passes an edge contour (that may be
panel boundaries, holes, notches or cutouts) an extra piece of material may be added to
allow for a good welding result. In AVEVA Marine such pieces are called "taps".
The designer has an option to define taps in the modelling phase. They will then be
converted in actual geometry when the plate parts are created in the automatic plate part
generation (ppanparts).
A customer may define his own standard for taps via a special set-up facility described
below. It consists of a file in a special format.
Note: Existing tap object, __SBH_TAP_CTRL__, will be replaced when the function is
used.
The statements need not be in any particular order and there may be more than one TAP
statement for the same standard type in one file. However, in that case the last statement for
a particular standard type will overwrite all previous taps of the same type. I.e. in the tap
object, one TAP type occurs only once.
Syntax:
Description:
FONT_NO and SYMBOL may be excluded. If excluded, the standard symbol number 105 in
symbol font 8 will be used.
FONT_NO and SYMBOL must, when given, always occur together, i.e. only FONT_NO or
only SYMBOL will not be accepted.
The black arrow is the connection point of the symbol with connection code 2.
The red arrow is the text position point with the text code 3.
When used in a hole the result will be as in the figure below:
Note that if some of these types should already exist in the tap object
(__SBH_TAP_CTRL__) they will be replaced by the ones in the file.
1.1 Background
The Hull application distinguishes basically between two different types of plate structures,
the planar structures in the internal of the ship and the curved structures in the shell.
The knuckled parts in the internal structure form a category of their own in between the
planar parts and the arbitrarily curved parts. However, the system treats them as a variant of
planar plate parts using basically the same tools as for the rest of the internal structure.
This document describes the general characteristics handling of knuckled plate parts and
panels.
The subpanels are described like normal panels, however, they must be given a tag, telling
that they are subpanels. The user must also indicate the edges of the subpanel along which
connection (knuckling) should take place.
Basically, the subpanels are generated as ordinary panels in a way similar to bracket
panels. Boundaries of subpanels to be connected need not coincide exactly - the system
will, whenever reasonable, adjust their geometry to fit. Thus, a certain gap or overlap will be
accepted. However, the planes of the subpanels will not be changed.
Once the subpanels have been generated the main panel is generated by reference to all
the subpanels by which it is built up.
In describing a knuckled panel there is some redundancy, because currently the plate
characteristics must be defined individually for each subpanel and the limits along the
knuckle line must be specified in both of the involved subpanels.
The given values must, of course, match for the two subpanels to be combined.
The position numbers of the combined plates will be fetched from the (first of the) subpanel
plate parts that are combined to the knuckled part.
Knuckled panels may contain stiffeners, holes, etc. like all other panels. These components
are supposed to be generated on the subpanels.
Holes, notches, cutouts and stiffeners across the knuckle lines are currently not supported.
The file is an ordinary ASCII text file and its full file specification must be assigned to the
environment variable SBH_KNUCKLE_CTRL.
The file is built up in the following way:
• It must always start with a TYPE statement defining the connection type code, e.g.
TYPE=45 (this is type of connection that is supposed to be defined in the boundaries of
subpanels along knuckle lines).
• Directly after the TYPE statement must follow a RADIUS statement defining the
bending tool radius, e.g. RADIUS=30.
• Then there must follow at least one so called thickness group. It starts with a
THICKNESS statement giving the maximum thickness up to which (and including) the
following parameters are valid, e.g. THICKNESS=10.
The parameters within a thickness group define stretch compensations as a function of the
knuckle angle (according to the experience of the individual yard). The values are given two
by two and define a knuckle angle up to which (and including) the following stretch
compensation should be applied for the current thickness. The number of pairs is not limited
but the knuckle angle must be ascending. The pair of parameters belonging to one
thickness group is interrupted by a new thickness group within the same connection type, by
a new connection type or by the end of the file. Thickness groups within one connection type
must be sorted in ascending thicknesses.
The compensation is used in the following way. The nominal size of the plate is considered
to be the length of the neutral line (plane) in the bending. This plane is supposed to be
located in the middle of the plate. The length of this line is calculated automatically taking
the bending radius into consideration and independent of the size of the subpanels when
generated (e.g. in case there happen to be gaps or overlaps). The compensation will add to
the nominal size of the plate if positive, reduce its size if negative. I.e. in a case where the
bending is found to cause a uniform stretching in the bend the plate will become too big
compared to the nominal length of the neutral plane and the compensation should be
negative.
Example:
For a customer using two different bending tools with the bending radius 30 and 40
millimetres, a control file could be defined like this:
TYPE=9999
RADIUS=40
THICKNESS=10
15 0.4
30 0.6
90 0.8
THICKNESS=20
15 0.5
30 0.7
90 0.9
THICKNESS=999
15 0.6
90 1.0
TYPE=33
RADIUS=30
THICKNESS=10
15 0.5
30 0.7
90 0.9
THICKNESS=20
15 0.6
30 0.8
90 1.0
THICKNESS=999
15 0.7
Example:
90 1.1
If the bending type is omitted when generating the boundaries of the subpanel the type will
be set to 9999, i.e. the default bending type is 9999. If there is only one type of bending the
connection type need never be given, it is enough to indicate a connection across that
bounding.
The file may be checked for correctness by a subfunction of the hull utility inithull. If it is not
correctly built up, the check will identify the line where the first error occurs. The file should
then be corrected and the check rerun until the file is found to be correct.
2.1 General
Plate surfaces in ships must normally be stiffened for reinforcement and to prevent buckling.
The normal way of doing this is to weld stiffeners to the plate. Other means of getting the
same result is to corrugate the plate surfaces. There are two principal types of corrugations:
large-size knuckling, often used in bulkheads in tanks on the one side, smaller, stiffener-like
corrugations, often used in super structures, on the other. The latter type is called swaging
and the general principles and the customer control of it are described in this chapter.
2.3.1 General
The characteristics of the swaging may be very different between different yards. A certain
yard may also use multiple types of swages simultaneously. Therefore it is necessary that
each customer should be allowed to control all characteristics of the type of swages used by
him. This paragraph contains details about how this control is done.
All the characteristics of a customer's swaging are kept in a so called swage object which
should be stored in the structure data bank (SB_OGDB). The name of this object can be
selected freely but it must be given as an ip or default parameter in modules where the
swaging is used, e.g. in Planar Hull Modelling, Automatic Plane Part Generation
(ppanparts), etc. The swage object can be created in a subfunction of the inithull module.
Remark: The height specified for a swage is a nominal height and need not
necessarily correspond to the actual height of the swage (H in last figure).
Back side: _____ _____ _____ _____ _____ _____ _____ _____ ___
A dash-dotted line on the facing side, a dashed line on the back side, also
optionally combined with a symbol.
= 102 A symbolic representation of the swage (supposing e.g. a swage with a section
as a trapezoid):
The following symbols can be used in combination with the line (see above).
Symbols:
Symbol No
0: No symbol
Example:
A line type 1 to be combined with symbol number 2 will result in the following representation
in a planar view.
The next figure shows a section view of a panel with swages (symbolic view). A 3D-view in
the direction of the swage will look the same.
SIZE A certain swage type may occur in several predefined sizes (nominal
heights). This statement type specifies a certain size and some data
related to that size.
• SWEDGE Statement
SWEDGE, <name>;
• PROFILE Statement
PROFILE, <type>
/VIEWING = <viewcode>
[/PLANE_SYMBOL = <symb_No>]
[/CROSS_SYMBOL = <symb_No>]
[MDIST=<distance>]
[MSIZE=<length>]
[MGAP=<length>]
;
• SIZE Statement
A certain swage type may occur in several (nominal) sizes. The "extra plate" required by the
swage is different for different sizes and may also differ with the plate thickness. The SIZE
statement is valid for the type of the last preceding PROFILE statement and may occur in
any number.
SIZE, <height>
/WIDTH = <width>
/UPPER_WIDTH = <width1>
/R1 = <rad1>
/R2 = <rad2>
/LOWER_LIM = <thickn>
( /UPPER_LIM= <thickn>
/COMP = <compensation> ) 1 ... 25
;
<height> This is one nominal height of the current swage type (roughly equal
to H in the figure above - in most cases there is only one size per
swage type).
WIDTH The nominal width of the swage (dimension D in Figure 2:1.: Height
and width of swage.)
UPPER_WIDTH The nominal width of the upper part of the swage (dimension D1 in
Figure 2:1.: Height and width of swage.).
R1 The radius between the mould plane of the panel and the swage
(R1 in Figure 2:1.: Height and width of swage.).
R2 The radius in the upper part of the swage (R2 in Figure 2:1.: Height
and width of swage.).
LOWER_LIM The compensation for the swage may vary with the plate thickness
and is supposed to be constant within a certain thickness interval.
This is the lower limit of the first interval.
UPPER_LIM Upper limit of a thickness interval (and lower limit of the next).
COMP The size of the expansion of the plate for this swage in the current
plate thickness interval.
• Example File
The file below is an example of a swage set-up file with only one type with one size.
Example:
SWEDGE, 'SWEDGE_OBJ';
/PLANE_SYMBOL=1
/CROSS_SYMBOL=1;
SIZE, 75 /WIDTH=90
/LOWER_LIM=5
/UPPER_LIM=7 /COMP=68.1
Example:
/UPPER_LIM=10 /COMP=68.9
/UPPER_LIM=12 /COMP=69.5;
Shrinkage
1 Shrinkage Compensation
1.1 Background
Each welding operation (and heating in general) in metal structures causes deformation
(shrinkage) of the structural elements involved. This means that if e.g. plate parts are
described to their nominal sizes they will in the fabrication and assembly process become
too small to fit. Thus when fabricating the parts they should already have been
compensated for the shrinkage so that the nominal dimensions are reached when the
assembly process is completed.
Hull has a facility for shrinkage compensation that allows a user to describe his model to
nominal dimensions but to extract parts which are expanded for the shrinkage. The purpose
of this chapter is to describe this facility, including how a yard's experience may be loaded
into a shrinkage compensation object for automatic or semi-automatic shrinkage
compensation.
The main characteristics of the two shrinkage evaluation methods are listed below in a
situation when they are operating in a fully automatic mode, i.e. when the user does not take
over any control.
1. The statistical method operates in the following way:
1. The most frequent stiffener direction (considering all the stiffeners in the panel) is
chosen as the shrinkage direction.
2. The most frequent partition (pitch) between the stiffeners in this direction is
evaluated and so is the partition between seams in this direction.
3. For each plate the following is done:
• Based on the plate thickness the amount of shrinkage for fillet welding is fetched
from a user defined shrinkage table. By dividing this with the pitch a scaling
factor is calculated by which the plate should be magnified perpendicularly to
the stiffeners.
• The same process is applied for the shrinkage caused by the butt welding along
the seams.
• These factors are combined to one which is used for scaling.
• Based on plate thickness and the pitch between stiffeners a shrinkage factor is
calculated by which the part will be scaled in the (longitudinal) direction of the
stiffeners.
This type of shrinkage compensation cannot be applied to shell plates.
Plane panel profiles are multiplied by the same scaling factor that has been used for
the plate (longitudinal scaling).
2. The method for local application of shrinkage has the following characteristics:
1. The total evaluation is on part level.
2. The evaluation of the shrinkage direction is done in a similar way as described
above, however all weld traces influence the evaluation, not only stiffener traces.
Moreover, depending on the trace pattern there may be two independent sets of
shrinkage directions. The corresponding compensations are applied independently
of each other.
3. Shrinkage compensation for butt welding is applied locally along plate edges which
are butt welded.
4. Shrinkage compensation for fillet welding is applied locally along the weld trace (the
outer geometry of the part is actually split, translated and then combined again).
However, before doing so an analysis is made of the length of the trace compared
to the size of the part. Shrinkage is applied only if certain conditions are fulfilled.
These conditions can be set-up and modified by the customer.
5. When the plate part has several different plate thicknesses (which may happen in
"assembly parts" for panel lines) the shrinkage compensation will consider the
thickness where the stiffener is located on the part.
6. The longitudinal shrinkage compensation is applied as a scaling factor as described
under 1) above. However, all weld traces are considered in the evaluation of the
pitch and of the scaling factor.
7. The shrinkage compensation is applied according to the same principles for both
plane panel plates and shell plates.
8. The longitudinal shrinkage in plane panel stiffeners is applied so that the change in
length of the profile is identical to that of its marking trace in the plate part(s), even if
the trace should pass several plate parts.
9. A special local shrinkage compensation may be applied at the ends of butt welded
profiles (including shell stiffeners).
The automatic evaluation as described above may be partly overridden by manual input.
Both methods use currently the same shrinkage table.
The most important advantages of the second method are:
• It makes a much more detailed analysis of the weld traces and, therefore, the result
should be more reliable.
• The customer can control the conditions for application of shrinkage to a larger extent.
• The shrinkage is applied locally whenever possible which is important, especially in
combination the use of the GSD option for alignment of parts for butt welding.
• The shrinkage compensation may be applied also for shell plates in the same way as
for plane panel plates.
• Using the statistical method also areas with no weld traces might be subject to
shrinkage compensation (since in this method it is always applied as a uniform
scaling). This will not occur with the second method, at least not to the same extent.
• The shape of parts (e.g. if they are (close to) rectangular or triangular) will affect the
way the shrinkage is evaluated.
A disadvantage may be that the second method requires much more process power.
However, since the evaluation is executed in a background process that is not so critical.
1. SBH_LOCAL_SHRINKAGE = EDGES_AND_FILLETS
By this assignment the system is told to apply the local shrinkage method automatically
and to the full extent as described in general terms above. The weld traces of all kinds
of connected components, profiles as well as panels (plates), and brackets are
considered. So are also the welds along edges, both fillet welds and butt welds.
Flanges welded along edges will contribute to the longitudinal shrinkage.
It is possible to some extent for the user to take manual control of the shrinkage
compensation (via input in panel generation) and then the system will automatically
switch to case 2, i.e. as if SBH_LOCAL_SHRINKAGE=EDGES. This means that the
user takes over the full responsibility for the shrinkage compensation in the interior of
plates. Thus, it is not possible to combine manual control and automatic evaluation in
this case.
2. SBH_LOCAL_SHRINKAGE = EDGES
The shrinkage compensation along plate edges will be applied locally while the
compensation in the interior of the plate will be done according to the "statistical
method" as described above (however, without the contribution from the seams). To be
compensated for shrinkage an edge must have been supplied with a bevel definition.
However, the type of bevel (butt welding or fillet welding) is irrelevant.
3. SBH_LOCAL_SHRINKAGE = EDGES_BUTTS
Similar to the previous case, butt shrinkage will be applied locally only along edges with
bevel types for butt welding, i.e. one of the basic types 10, 20, 30, 33, 40, 41, 43, 50 or
51.
If the user (in cases 2 and 3) has taken control via any of the parameters M5 or M6 in
generation input then there will be a complete switch to the statistical method.
Calculate the extension of the plate contour in the shrinkage direction. Let the result be
called LEN. Calculate the extension of the plate in the direction perpendicular to the
shrinkage direction and let the result be called BRE. The area of the surrounding rectangle
is then LEN*BRE (=RA).
Calculate the area (=PA) of the plate (skip holes). In case PA>RA*TOL_RECT_AREA the
plate is supposed to be rectangular, otherwise in case PA<RA*TOL_TRIA_AREA the part
is supposed to be triangular.
If the shape of the plate is not classified according to previous conditions, check the
distances from the 4 corners of the circumscribed rectangle to the plate contour. Calculate
also the length (=D) of the diagonal of the same rectangle. If any of the 4 calculated
distances is larger than TOL_RECT_DIAG*D then the part is considered as triangular.
If still not classified, check D against length of the shortest edge of the rectangle (any of BRE
or LEN, BRE is used in the formula). If D>TOL_RECT_EDGE*BRE then the part is
considered as triangular.
If still not classified, assume rectangular shape.
A number of default parameters, all starting in TOL_ and used in expressions below,
control whether a certain marking trace should be considered to contribute to the shrinkage
or not. They have all certain predefined values which can be changed by the customer. The
figure below shows a rectangular plate with a number of marking traces of different lengths.
Let LEN be the length of the two edges of the circumscribed rectangle parallel to the
shrinkage direction.
For rectangular plates check like this for all combined marking contours:
Project a trace on the shrinkage direction. Call the projected length PL<i>. Fictitious
marking traces will be skipped for perpendicular shrinkage. If PL<TOL_K1SFT*LEN then
the corresponding trace should not take part in the perpendicular shrinkage calculation,
otherwise it should. If PL<TOL_K1SFL*LEN then the marking line should not take part in
longitudinal shrinkage calculation, otherwise it should.
Calculate an average PL (=PLA) for the traces contributing to perpendicular shrinkage. If
PLA<TOL_K2SFT*LEN then skip the perpendicular shrinkage compensation altogether. If
PLA<TOL_K2SFL*LEN then skip longitudinal shrinkage compensation altogether.
For triangular plates the check is slightly modified.
Project traces as described above. Intersect the outer contour of the plate with a line parallel
to the shrinkage direction and through the midpoint of the current marking line. Calculate the
distance (=TOT<i>) between the utmost of these intersection points (normally there
should be two). If PL<TOL_K1SFT*TOT then the corresponding marking line should not
take part in the perpendicular shrinkage calculation, otherwise it should. If
PL<TOL_K1SFL*TOT then the marking line should not take part in longitudinal shrinkage
calculation, otherwise it should.
Calculate an average PL (=PLA) for those marking contours that will take part in the
perpendicular shrinkage and an average of all TOT<i>:s (=TOTA). If
PLA<TOL_K2SFT*TOTA then skip perpendicular shrinkage compensation altogether. If
PLA<TOL_K2SFL*TOTA then skip longitudinal shrinkage compensation altogether.
Fictitious marking lines for welding along plate edges are considered in the evaluation of the
longitudinal shrinkage. Accept them only if their direction deviates less than 45 degrees
from the shrinkage direction and if PL>TOL_K2SFL*LEN (LEN is replaced by TOT for
triangular plates).
The longitudinal shrinkage will be applied proportionally all over the plate as a scaling in the
shrinkage direction. Some calculations are made to decide if there will be any longitudinal
shrinkage compensation or not.
This evaluation is done in the following way:
• Project the midpoints of all accepted traces on a line perpendicular to the shrinkage
direction.
• Sort the points along this line.
• DIST<i> is the distance between two adjacent points.
• The distance between the extreme points is denoted TOT_EXT.
If any DIST<i> exceeds TOL_MAXPART_IND or if the average of the DIST<i>:s
exceeds TOL_MAXPART_AVE then skip the longitudinal shrinkage compensation
altogether. Do the same if (BRE -TOT_EXT) / 2 > TOL_MAXPART_IND, i.e. if there
are big regions of the plate without any traces (for BRE, see figure above).
As already pointed out the length of stiffeners are modified so that they get the same
change of length as the marking traces they have caused on plate parts (even if a certain
stiffener should be the origin of marking traces in several plates parts).
Figure 1:4. The effect of bevel gaps and shrinkage compensation at plate edge with GSD
2. The bevel code must be defined for the profile end and the basic bevel type must be
one of the main types for butt welding.
3. The values used for shrinkage compensation are fetched from table 2 of the shrinkage
object assigned to SBH_LOCAL_SHRINKAGE_PROF.
Statement Usage
SHRINKAGE Name of shrinkage object to be created
FILLET Statement for the creation of table 1 as explained above.
BUTT Statement for the creation of table 2 as explained above
LONGITUDINAL Statement for the creation of table 3 as explained above.
The input must start by a SHRINKAGE statement and may contain at most one occurrence
of each the other statement types in any order.
• SHRINKAGE Statement
Syntax:
SHRINKAGE, <name>;
Syntax:
<type>,
(/UPPER_LIM=<u_lim> /COMP=<comp>) (1 ... 25)
;
• LONGITUDINAL Statement
Syntax:
LONGITUDINAL,
( /PARTITION=<dist>
(/UPPER_LIM=<u_lim> /COMP=<comp>)(1 ... 25)) (1
... 25)
;
PARTITION The average partition between traces for which a certain table
should be used. Tables for at most 25 different partitions may be
created.
UPPER_LIM and COMP are used as in the FILLET/BUTT statement and are valid for
the table associated with the closest preceding PARTITION.
SHRINKAGE,'TEST_SHR';
FILLET/UPPER_LIM=12/COMP=3/UPPER_LIM=22/COMP=5;
BUTT/UPPER_LIM=12/COMP=2/UPPER_LIM=22/COMP=4;
LONGITUDINAL/PARTITION=500
/UPPER_LIM=10/COMP=3/ UPPER_LIM=20/COMP=4
/PARTITION=1500
/UPPER_LIM=10/COMP=4/UPPER_LIM=20/COMP=5;
SHRINKAGE_TOL_RECT_EDGE, <tol_rect-edge>,
Ditto for comparison with length of shortest edge of min-max rectangle. Default value is
0.85.
SHRINKAGE_TOL_K1SFT, <tol_k1sft>,
Factor for relative length of an individual marking trace to be accepted for perpendicular
shrinkage. Default value is 0.2.
SHRINKAGE_TOL_K2SFT, <tol_k2sft>,
Factor for average length of marking curves for perpendicular shrinkage. Default value is
0.4.
SHRINKAGE_TOL_K1SFL, <tol_k1sfl>,
Factor for relative length of an individual marking trace to be accepted for longitudinal
shrinkage. Default value is 0.4.
SHRINKAGE_TOL_K2SFL, <tol_k2sfl>,
Factor for average length of marking curves to be accepted for longitudinal shrinkage.
Default value is 0.4.
2.1 Background
The welding involved in the assembly of built profiles causes a deformation that need be
compensated for in one way or another. AVEVA Marine has an option to automatically
compensate for this deformation by modifying the web of built profiles before they are cut.
The compensation is controlled by a profile weld compensation object that is set-up and
maintained by the customer.
Alignment Marking
1 Reference Planes
1.1 General
Reference planes, arbitrary placed in the ship, can be defined to be marked on individual
plates (planar and curved) for assembly purposes. The planes should be defined in an early
stage of the project, selected in the modelling phase and finally result in marking lines on the
plate parts.
1.2.1 Syntax
The input file may contain two different types of statements, as described below.
CREATE_PLANE, <name_of_plane>
([/ARBITRARY =(X1, Y1, Z1, X2, Y2, Z2, X3, Y3,
[/PRINCIPAL Z3)] |
[/PLANE_NORM =('X' | 'Y' | 'Z', COORD)] |
=(X, Y, Z, N1, N2, N3)])
[/BOX =(X1, Y1, Z1, X2, Y2, Z2)]
[/SYM];
DELETE_PLANE, <name_of_plane>;
• Statement Parameter
<name_of_plane Arbitrary name given by the user. The resulting plane and curve
> will be given this name (for CREATE_PANEL) or a plane with this
name will be deleted (for DELETE_PLANE).
• Statement Qualifiers
Note that the qualifiers ARBITRARY, PRINCIPAL and PLANE_NORM are mutually
exclusive, i.e. only one of them can appear in the same CREATE_PLANE statement. The
BOX qualifier can, however, be given together with any of the other qualifiers. The SYM
qualifier can be given together with PRINCIPAL=('Y', COORD) qualifier. All coordinate
values for planes can be given as relative coordinate, i.e. co-ordinates referring to frames,
waterlines, etc. are allowed. Because of this, coordinates in the input file are handled as
strings and must be surrounded by apostrophes also when true numerical coordinates are
given.
There is no limit to the number of statements that can be given in one input file.
/ARBITRARY=(X1, Y1, Z1, X2, Y2, Z2, X3, Y3, Z3)
This qualifier is used when an arbitrary plane is defined by three points.
/PRINCIPAL=('X' | 'Y' | 'Z', COORD)
This qualifier can be used for the definition of a plane parallel to one of the principal planes
by specifying a coordinate along its normal axis.
/SYM;
This qualifier can be used together with /PRINCIPAL=('Y', COORD) qualifier and
means that two planes will be created, principal plane parallel by axis and its reflected
image in center line.
/PLANE_NORM=(X, Y, Z, N1, N2, N3)
By using this qualifier, a plane is defined by giving a point and a normal vector to the plane.
/BOX=(X1, Y1, Z1, X2, Y2, Z2);
This qualifier restricts the defined plane to be within the box formed by the given coordinate
limits.
Example:
CREATE_PLANE, 'PLANE1'
CREATE_PLANE, 'PLANE2'
/PRINCIPAL=('X', 'FR38-227.5');
CREATE_PLANE, 'PLANE4'
/PRINCIPAL=('Y', '4000')
/SYM;
CREATE_PLANE, 'PLANE3'
Example:
DELETE_PLANE, 'PLANE1';
1.3 Environment
The created data is placed on the data bank connected to the environment variable
SB_OGDB (the planes) and to SB_CGDB (the curves).
All messages and printouts will be displayed on the screen.
Reference planes are created by the use of the hull utility program inithull.
2.2 Environment
2.2.1 General
All GSD settings are defined in a file.
The name of this file shall be assigned to the environment variable SBH_GSD. A detailed
description of all available keywords in the default file is found in Control of GSD:s via a
Default File.
2.3.1 General
The GSD:s are first placed in their nominal position, i.e. in the position they should have had
if shrinkage could have been neglected entirely. The effect of the shrinkage compensation is
that the geometry will be enlarged so that the part after assembly will have its correct
geometry. The GSD:s will be affected by this geometry modification like all the rest of the
part.
Some consequences of the principle above:
• Along a seam for butt welding with gap the tip of triangles will be in the "gap zone", e.g.
the tip will be cut by the burner. See the figure below.
• The same is true for the end of a line marking. The end in the "gap zone" will be cut by
the burner. See the figure below.
• Similarly, triangular GSD:s can be used for positioning of two plates relative to each
other by checking the distance between them. The effect is also that this distance after
welding will be less due to the shrinkage.
• The outer geometry of the plate part will be in the nominal position after welding.
If there is excess in the panel the GSD will be placed as though there had not been any
excess, i.e. in the nominal position.
In general, marking traces are either entirely replaced by a number of GSD:s or the marking
traces may be supplemented with GSD:s.
The distance between adjacent GSD:s along a trace that has been replaced entirely by
GSD:s must not exceed the distance given by the default parameter MAXDIST. The "inner"
GSD:s will be equally spaced and triangular GSD:s is facing towards the centre of the
marking trace.
Short marking traces may be represented by both GSD:s at the ends and the actual trace
curve to avoid confusion. This will occur when the length of the marking is shorter than the
distance given by the default parameter TRACE_LIM. By setting a very large value to this
parameter one will get the result that all traces will be marked. If the trace is wanted there
will not be any "inner" GSD:s.
GSD:s are not added at all to marking traces with a length less than three times the value of
CORNER_DIST. The figure below shows complete marking information for a stiffener with
different parameter settings (triangular GSD:s used).
It should be noted that in some circumstances large parts of a GSD along an edge may be
removed (or even disappear entirely) e.g. in case of bevelling, especially if combined with
chamfer. In such a case the marking will have to be amended or added by the workshop.
See the figure below.
The following paragraphs describe the different positions where GSD:s are evaluated, in
most cases quite automatically.
The position of a GSD is affected differently by notches and cutouts in the corner depending
on the default USE_WELD_TRACE.
GSD:s will only be placed on boundaries defined by reference to the surrounding structure,
a hull curve, a stored plane or any edge where WELD is defined, i.e. free edges will not get
GSD:s. This can be overridden by the default GSD_AT_FREE. The figure below shows a
case where GSD:s have been set in all corners.
GSD:s will not be placed at plate corners where the boundaries intersect at 180 degrees.
At the intersection of the boundary or a seam with an internal plate seam, one GSD will be
placed on the seam only (i.e. at T-junctions). This can be overridden by the default
GSD_AT_T. The figure below shows the effect of this parameter.
GSD:s will not be placed on boundaries with flanges or where the geometry of the plate
edge does not allow it.
GSD:s will not be placed on boundaries defined by reference to a profile on another panel
(e.g. profile cross section).
GSD:s will not be set on inner seams for assembly parts (for the panel line).
Depending on the length of the trace and the size given by the parameter MAXDIST,
additional GSD:s may be added according to the general rule above. These "inner" GSD:s
will not have any corresponding marks on the stiffener.
There are no inner GSD:s on traces for stiffeners attached to assembly parts (for panel
lines).
If the position of the trace on the part is such that any GSD on the trace lies outside the part,
the marking of this trace is replaced with a solid line with end tags showing the position of
the end GSD:s. See the figure below.
Syntax:
MAR,LIM = <lim_no>;
LIM defines the limit along which reference marks are to be added
<lim_no>::=<integer>
The GSD:s are placed along panel limits and are oriented towards one of the three principal
axes.
The spacing between GSD:s in the direction of the y- and z- axes is defined by the variable
INTERVAL and the positions are calculated as even multiples, measured from the ship
centre line and base line, respectively. Reference marks in the direction of the x-axis are
placed at frame locations.
The evaluated GSD:s are displayed during modelling but will not be part of the drawing.
These marks are placed on both sides of the plate.
USE_WELD_TRACE=YES, otherwise from the profile end (cf. stiffeners in section Stiffener
Traces). The orientation of the GSD is perpendicular to the profile trace and triangular
GSD:s are facing away from the end.
Line "A" defines the moulded line of the attached panel. The line "B" defines the material
side (direction of line "B" = into material of panel). The corner between "A" and "B"
corresponds to the position of the associated GSD on the panel (see the figure below).
The length of "A" and "B" is controlled by the parameters FLA_A and FLA_B. The marking
will be placed at a distance (CORNER_DIST) from the nominal flange ends.
If, for some reason, the marking extends outside the raw profile edges, then line "A" and/or
"B" will be omitted from the marking geometry. If the flange marking from both ends of the
flange profile overlap, then measure "A" will be shortened accordingly.
The marking on the flange profile will be on the side that is welded to the plate edge. The
GSD on the plate will be on the side defined by SBH_MARKING_SIDE.
In case the flange extends outside the plate edge, the marking will be placed at a distance
(CORNER_DIST) from the plate corner. Notches in the plate geometry will be taken into
consideration if the keyword USE_WELD_TRACE=YES (see the figure below).
2.6.1 General
The environment variable SBH_MARKING_SIDE controls on which side of the plates the
GSD:s should be marked.
PL_LIM 0.0 This parameter affects all plate edges that cause a marking
trace. If the length of such an edge is shorter or equal to the
given limit value, then only one GSD will be presented
(corner GSD and GSD at marked trace). The GSD that is
presented is the one in the end closest to BOTTOM, AFT or
shell of SB side. This type of reduction cannot be used
together with the REDUCE_DIR keywords (see the figure
below).
USE_WELD_TRACE YES Allows the user to select if the weld trace or the
moulded trace shall be marked and be used in
positioning of GSD's. Possible values are YES
and NO (see the figure below).
1.1 General
FRP (Fibre Reinforced Plastics), sometimes also called GRP (Glass Fibre Reinforced
Plastics) is a technique to design and construct normally rather small vessels by replacing
the standard metal plates and profiles (made of steel or aluminium) by laminated plastics.
The plates consist of a relatively light and fragile core material that is reinforced by several
layers of fibre carpets glued together to form a tensile and endurable coating, normally on
both sides of the plates. Originally the carpets were made of glass fibres but an alternative
is to use coal fibres that are lighter and stronger.
There are several important differences compared to standard ships, e.g.:
• The thickness of plates is much larger that in a steel ship. This means that if the plate
thickness can be neglected in certain cases, it cannot for vessels built in FRP material
(e.g. in drawings, in calculating volumes, etc.).
• A consequence is that project settings must be made to consider plate thickness when
modelling planar panels and shell profiles.
• Other ships have uniform material qualities whereas densities vary between layers in a
FRP sandwich.
• The amount of stiffening is less than in steel or aluminium ships since the FRP plates
are very stiff in themselves and the stiffening that is there is of a partly different type.
• Where members of standard ships are fillet welded together FRP members are
connected in a different way, e.g. by a combination of beads and fibre tissue.
• In an FRP vessel there are fewer parts and not so many small details like notches,
clips/collars etc.
1.2.1 Modelling
Additional features of the planar hull modelling input language are described in detail in
User Guide Hull Detailed Design / Planar Modelling / Design Language of Hull Modelling /
Special FRP Additions. The component types affected by the FRP setting are plates,
stiffeners, holes and flanges. Moreover, beads are available as an additional component
type in an FRP project (accompanied by the corresponding BEAD statement in the input
language).
The Statement Wizard will adapt as well in an FRP project.
Laminate information may be set for shell plates and shell stiffeners, both interactively and
in the XML input files used in batch modelling of curved hull.
In both planar and curved hull, the concept of material quality refers to the core material in
an FRP project.
1.2.2 Views
Symbolic views generated in an FRP project differ to some extent from those in a steel
project.
• Panel sections
Sections of panel plates will show the thickness including the thickness of the lamination.
• Stiffeners
A top view of a stiffener contains two lines indicating the actual width of the profile (as
opposed to the single mould line in a steel project). The two lines will be dashed for a profile
placed on the upper side of the panel in the view and dash-dotted for a profile on the
opposite side. No material or endcut symbols of the profile are drawn.
In a section view of a stiffener, attached beads will be drawn as well.
• Holes
Lamination along the edge of a hole is indicated by a dashed contour parallel to and outside
the actual hole contour.
• Beads
A bead in the view plane will be indicated by a dashed line parallel to the boundary along
which it is defined.
In a section view, the actual cross-section shape of the bead will be drawn.
A bead is drawn in a 3D view as well.
The three statement types may occur in an arbitrary order in the input file. There may be a
maximum of 99 statements of each type.
• LAMINATE_PLANE Statement
Syntax:
LAMINATE_PLANE, <type_no_plane>
/ NAME = '<name>'
/ PERCENT_OF_FIBER = <fiber>
/ DESIGNATION = '<designation>' (1…11)
/ FABRIC_WEIGHT = <fiber_weight>
(1…11)
/ TOTAL_THICKNESS = <total_thickness>
/ TOTAL_WEIGHT = <total_weight>;
The number of DESIGNATION and FABRIC_WEIGHT attributes must be equal and the
values should match each other in order of appearance.
• LAMINATE_BEAD Statement
LAMINATE_BEAD ,<type_no_bead>
/ NAME = '<name>'
/ WEIGHT = <weight>;
• LAMINATE_FLANGE Statement
LAMINATE_FLANGE ,<type_no_flange>
/ NAME = '<name>'
/T_FL1 = <thickness>
/T_FL2 = <thickness>
/R = <radius>
/H_FL2 = <height>
/H_TAP = <height>
/DESIGNATION = <designation> (1….11)
/FABRIC_WEIGHT = <weight> (1….11)
/FABRIC_WIDTH = <width> (1…..11)
/RESIN = <resin name>
/RESIN_DENSITY_CURED = <density>
/TOTAL_WEIGHT = <weight>;
LAMINATE_PLANE, 42
/NAME='L42'
/PERCENT_OF_FIBER=51
/DESIGNATION='L450(C)'
/FABRIC_WEIGHT=0.409
/TOTAL_THICKNESS=0.45
/TOTAL_WEIGHT=0.8;
LAMINATE_PLANE, 92
/NAME='L92'
/PERCENT_OF_FIBER=51
/DESIGNATION='L450(C)'
/FABRIC_WEIGHT=0.409
/DESIGNATION='L450(C)'
/FABRIC_WEIGHT=0.409
/TOTAL_THICKNESS=0.90
/TOTAL_WEIGHT=1.6;
LAMINATE_PLANE, 93
/NAME='L93'
/PERCENT_OF_FIBER=51
/DESIGNATION='L450(C)'
/FABRIC_WEIGHT=0.409
/DESIGNATION='L450(C)'
/FABRIC_WEIGHT=0.409
/DESIGNATION='L450(C)'
/FABRIC_WEIGHT=0.409
/TOTAL_THICKNESS=1.35
/TOTAL_WEIGHT=2.4;
LAMINATE_PLANE, 52
/NAME='L52'
/PERCENT_OF_FIBER=56
/DESIGNATION='LT650(C)'
/FABRIC_WEIGHT=0.612
/TOTAL_THICKNESS=0.70
/TOTAL_WEIGHT=1.1;
LAMINATE_PLANE, 61
/NAME='L61'
/PERCENT_OF_FIBER=56
/DESIGNATION='DBL700(C)'
/FABRIC_WEIGHT=0.615
/TOTAL_THICKNESS=0.70
/TOTAL_WEIGHT=1.1;
LAMINATE_PLANE, 71
/NAME='L71'
/PERCENT_OF_FIBER=55
/DESIGNATION='L450(C)'
/FABRIC_WEIGHT=0.409
/DESIGNATION='DBT700(C)'
/FABRIC_WEIGHT=0.619
/DESIGNATION='L450(C)'
/FABRIC_WEIGHT=0.409
/TOTAL_THICKNESS=1.6
/TOTAL_WEIGHT=2.6;
LAMINATE_PLANE, 74
/NAME='L74'
/PERCENT_OF_FIBER=56
/DESIGNATION='LT650(C)'
/FABRIC_WEIGHT=0.612
/DESIGNATION='LT650(C)'
/FABRIC_WEIGHT=0.612
/DESIGNATION='DB450(C)'
/FABRIC_WEIGHT=0.410
/DESIGNATION='LT650(C)'
/FABRIC_WEIGHT=0.612
/TOTAL_THICKNESS=2.5
/TOTAL_WEIGHT=4.0;
LAMINATE_PLANE, 81
/NAME='L81'
/PERCENT_OF_FIBER=55
/DESIGNATION='DB450(C)'
/FABRIC_WEIGHT=0.410
/DESIGNATION='LT450(C)'
/FABRIC_WEIGHT=0.414
/TOTAL_THICKNESS=0.9
/TOTAL_WEIGHT=1.5;
LAMINATE_PLANE, 84
/NAME='L84'
/PERCENT_OF_FIBER=41
/DESIGNATION='DB450(C)'
/FABRIC_WEIGHT=0.410
/DESIGNATION='LT450(C)'
/FABRIC_WEIGHT=0.414
/TOTAL_THICKNESS=1.4
/TOTAL_WEIGHT=2.0;
LAMINATE_PLANE, 8
/NAME='L8'
/PERCENT_OF_FIBER=41
/DESIGNATION='DB450(C)'
/FABRIC_WEIGHT=0.410
/DESIGNATION='LT450(C)'
/FABRIC_WEIGHT=0.414
/TOTAL_THICKNESS=1.4
/TOTAL_WEIGHT=2.0;
LAMINATE_BEAD, 101
/NAME='FL1'
/WEIGHT=0.55;
LAMINATE_BEAD, 102
/NAME='FL2'
/WEIGHT=0.85;
LAMINATE_PLANE,1/NAME='TEST'
/PERCENT_OF_FIBER=40
/DESIGNATION='A'
/DESIGNATION='B'
/DESIGNATION='C'
/FABRIC_WEIGHT=0.45
/FABRIC_WEIGHT=1.8
/FABRIC_WEIGHT=0.45
/TOTAL_THICKNESS=4.3
/TOTAL_WEIGHT=4.3;
/T_FL1=20
/T_FL2=10
/R=15
/H_FL2=40
/H_TAP=60
/DESIGNATION='DB450-G10-2RVE-xxxxx'
/FABRIC_WEIGHT=0.410
/FIBER_WIDTH=140
/DESIGNATION='L450x-xxx-xxxx-xxx'
/FABRIC_WEIGHT=0.410
/FIBER_WIDTH=160
/DESIGNATION='DB450-G10-2RVE-xxx'
/FABRIC_WEIGHT=0.410
/FIBER_WIDTH=180
/RESIN='VE-XX2010-XXX-XX-XXX'
/RESIN_DENSITY_CURED=12.3
/TOTAL_WEIGHT=5;
1.1 General
This document describes an option to convert flat bars and built profiles into plate parts or
into plate parts and new profiles. If a built profile is split into other profiles these will always
be flat bars.
The selection of profiles to be converted is done via a decision table (see below). No other
input is necessary for the conversion.
The conversion of profiles takes place in the automatic parts extraction.
1.2 Result
For flat bars the name of the converted plate parts will be the same as the name of the
profile parts on the profile data bank. The data type (object code 1) of the converted parts
will be 87.
If the profile type is not a flat bar, a ´W´ for web and ´F´ for flange will be added to the name
of the profile part.
The naming for the new plate parts will in that case be as follows (supposing that the name
of the original profile part is ES123-1/S3):
PROFILE_TYPE
DIMENSION
QUAL_LENGTH
QUAL_LENGTH
.
.
DIMENSION
QUAL_LENGTH
.
.
DIMENSION
.
.
BEVEL
.
.
FLANGE
COMP
STRAIGHT
PROFILE_TYPE
..
• PROFILE_TYPE
Layout:
PROFILE_TYPE=<proftype>;
<proftype> is the profile type according to standard (any of 10, 35, 36, 37, 38, 43 is
allowed)
• DIMENSION
Layout:
DIMENSION=<dim_string>;
<dim_string> should contain the parameters in the order according to the standards,
separated by capital X. Any parameter may be replaced the “wildcard” symbol *. The
number of parameters must always be correct even when wildcards are used.
If there are several DIMENSION statements for one PROFILE_TYPE, the statements
should be given in order from specific to more general, e.g. from explicit dimensions to
dimensions selected via wildcard.
• QUAL_LENGTH
Layout:
QUAL_LENGTH=<qual>,<min_len>,<max_len>;
If there are several QUAL_LENGTH statements for one DIMENSION, the statements should
be given in order from specific to more general, e.g. from explicit qualities to qualities
selected via wildcard.
• BEVEL
Layout:
BEVEL=<bevel_from>,<bevel_to>;
<bevel_from> and <bevel_to> define an interval of allowable bevel codes for those
profiles that should be converted.
The BEVEL statement is optional and if missing the bevel code will not be considered.
• FLANGE
Layout:
FLANGE=PROFILE; (or FLANGE=PLATE;)
This statement is optional. For built profile the web will always be converted to a plate if the
conditions are fulfilled. The flange will also, by default, be converted to a plate but this may
be inhibited by FLANGE=PROFILE. (Thus, FLANGE=PLATE; is always redundant).
• COMP
Layout:
COMP=<YES/NO>;
This statement is optional and the default value is NO. If YES, then weld compensation will
be added to the web of the profile if such a compensation table is defined. The set-up of the
compensation table is described in Hull - Setup and Customisation - Shrinkage
Compensation - Weld Compensation for Built profiles.
• STRAIGHT
Layout:
STRAIGHT=<YES/NO>;
This statement is optional and the default value is NO. If YES, then the web of shell profiles
will be stored on the plate databank without curvature. Marking of the inverse bending lines
will be added to the plate parts.
1.4 Example
An example of a decision table is as follows
PROFIL_TYPE =43;
DIMENSION =400X12X125X15;
QUAL_LENGTH =*,10,16000;
DIMENSION =*X*X*X*;
QUAL_LENGTH =A,10,16000;
QUAL_LENGTH =*,10,2500;
BEVEL =0,310;
FLANGE
=PROFILE;
Note: When using '*' characters be sure to give the 'explicit' values first. As the dimension
cards are given in the example the program finds the profile 400X12X125X15 first.
This means that QUAL_LENGTH = *,10,16000 is only valid for that dimension. For all
other dimensions the QUAL_LENGTH = A,10,16000 or *,10,1500 is valid. I.e. the
first matching dimension is taken, then the first matching quality. All bevel cards may
come at the end.
2.1 Background
The generation of production data is an integrated part in the complete system, which may
affect the user already at the modelling stage.
This chapter describes the set-up of profiles with respect to the actual fabrication and the
production methods used at the customer site.
2.2.1 General
When a curved shell profile is manufactured in the workshop there is often a need for
excess material at the ends to be able to bend the profile. This document describes how this
bending excess can be automatically calculated and added to the profile using Profile
Nesting Utility and presented to the user with Profile Cutting Interface (PCI). All "keywords"
that are referred to below can be found in the restriction file described in Curvature Control
of Shell Stiffeners.
2.2.3 Method M1
This method is a customer specific implementation, with a number of customer specific
details, e.g. very complex rules for calculating bending excess, German printouts in the list
etc. No functional changes can be made that are not approved by this customer, but still it
could be valuable as an example for other customers. More general methods can be found
below.
Parameter <X>:
<X> is the maximum bending for which the line (row in the table) is valid:
If the profile is shorter than 2000 mm it is temporarily extended at each end in the direction
of the tangent because the curvature is examined at both ends independently.
Parameter <S> and <V>:
[+]<S> is the amount of bending excess to add to the profile. It is calculated and applied
differently depending on if [+] is given or not.
If [+] is given then <S> is an absolute amount of material to add to the profile either at the
endcut zero point or to the profile end point depending on the angle of the endcut.
If [+] is not given then the amount of bending excess is calculated as <S>*<profile height>
and applied to the point where the endcut geometry has y = 0.
The amount given by +<S> is called "stoss". This name is used in the generic file and in the
list for manual fabrication of profiles created by PCI. If <S>*<profile height> is used then
"stoss" is calculated and presented as if it was given via +<S>
.
[,<V>] is optional. It controls the amount of bending excess together with <S>. It is only valid
if [+] is NOT given and is always used as a factor of the profile height. It is calculated from
the profile end point. If both <S> and <V> are given then the one creating the largest
bending excess for that end is used.
Example of table
.
.
.
PROF_TYPE=20
.
.
.
BENDING_EXCESS_CONTROL_TAB1_30=+100
BENDING_EXCESS_CONTROL_TAB1_100=1
BENDING_EXCESS_CONTROL_TAB1_9999=1.5
BENDING_EXCESS_CONTROL_TAB2_100=0
BENDING_EXCESS_CONTROL_TAB2_9999=1.5,0.8
.
.
.
Notches are marked with a straight line with length L, perpendicular to the root edge of the
profile.
L is controlled via the keyword HOOK4 that shall be given for each profile type in the profile
restriction file. The default value is 50 mm.
The marking of macros is also indicated in the normal way, i.e. they have OPEN=10 or
OPEN=11 in the generic file. It is also visible in the plot of the nested profile where they are
dashed.
• Burner ID
A new burner ID, ROBOT_BENT_S, has been added and is used for S-schaubilders.
2.2.11 Method M2
The method M2 is activated by setting BENDING_TAB_METHOD=M2 in the general
section of the profile restriction file.
• General Definitions
For every bending curve on the profile set:
• Bending Excess
Bending excess is added to the profile if one or more of the following conditions are met:
1. Profile length is less than 3000 mm.
2. There is more than one bending curve.
3. If the formula above is satisfied for k=0 on the first bending curve and/or for k=n-1 on
the last bending curve.
The amount of bending excess is controlled by the keyword M2_BENDING_EXCESS that
shall be given for each profile type in the profile restriction file. The default value is 950 mm.
Bending excess is always applied at both ends of the profile at x1 on the first bending curve
and at xn-1 on the last bending curve.
2.3.1 Background
The Profile Nesting Utility allows the customer to specify the limits for a profile robot. If these
limitations have been set up, the profile nesting has a function to check if a profile nesting
contains parts that violate them. If so, this nesting is stored with a signal that it should be
fabricated manually.
However, it is possible to get information already in the modelling phase about the profiles
that do not comply with the restrictions set up by the customer. This document describes
how to activate this facility and the parameters of the restriction file that are relevant in this
context.
2.3.3 Profgen
Add the line CHECK_PROFGEN=YES to the restriction file to activate the feature. The
restrictions are only checked in this module if the user gives IP SPLITPROF.
For Profgen it is also possible to get the profile controlled against available stock material as
specified in the profile stock-number file (SBH_PROF_STOCKNO). This check is controlled
by the keyword CHECK_STOCKNO in the restriction file and replaces the one made against
the MAX_PROF parameter. Possible values for CHECK_STOCKNO are:
• IGNORE - no check is made
• WARNING - warning printed, profile stored on SB_OGDB and SBH_PROFDB.
• ERROR - warning printed, profile stored on SB_OGDB but NOT stored on
SBH_PROFDB
Note: that CHECK_STOCKNO has no effect if CHECK_PROFGEN=NO or not given.
All warning messages will be presented to the user in the dialogue area on the screen.
MIN_DIM<x> Minimum value for dimension <x> of the current profile type (x is the
order number of the parameter in dimension parameter list)
MAX_DIM<x> Maximum value for dimension <x> of the current profile type
TRUE_SCRAP The length of a scrap piece that shall be considered as true scrap.
This could be the basin width for scrap to fall down at the robot.
Note: Normally this keyword restricts the scrap piece between two
profiles but in this case it is checked against the scrap piece
created for each endcut.
BEVEL Bevel-type that can be treated by the robot. There may be more than
one BEVEL-keyword.
All these keywords are given for each profile type, that is a section within the restriction file
starting with the keyword PROF_TYPE defining "current profile type". The PROF_TYPE
keyword must exist for the treated profile.
Furthermore, specific endcut restrictions can be given. These restrictions, valid within the
current profile type are all given inside a section starting with the keyword ENDCUT, that
must exist for the current end of the treated profile:
Possible values given to these keywords are YES and NO. The default value for all of them
is YES.
2.4.1 Introduction
A curved shell profile is normally bent in the workshop before it is mounted in the ship. If the
profile is only slightly curved this step may not be necessary, the profile can be
manufactured as a straight one and will then "fall into place" when mounted in the ship. The
facility described here makes it possible for the yard to set up rules to decide if a shell
stiffener should be stored as curved or straight on the profile data bank, SBH_PROFDB. It is
applied in this storing process.
Syntax
Each statement in the text file has the syntax:
PROF
TYPE The profile type for which METHOD and CVAL are valid. If this keyword
is omitted then the values in this statement will be used as defaults for all
profile types not mentioned in other statements.
HEIGHT The biggest height for which METHOD and CVAL are valid.
METHOD The method used to evaluate if a shell profile is curved. Valid choices are
WHOLE_TRACE_INDEP_DIST and PER_1000_FACT. The two
methods are described below.
CVAL Described below for each METHOD.
2.5.1 General
The restriction file is used mainly by the Profile Nesting module and by the Profile Interface,
but to some extent also by modelling programs and other production programs. This is
explained further in the descriptions of the restriction keywords below.
Defaults and restrictions are defined by the user in a normal ASCII-file assigned to the
environment variable SBH_PROF_RESTRICT. The file is keyword oriented and can by
handled by any editor.
The contents of this file is divided into one general information part, valid for all types of
profiles and one part that is type dependent.
All profile types used should have it's corresponding section in this file (see PROF_TYPE
below).
MIN_DIST_RBENDS=<mm>
If greater than zero, the value is interpreted as the minimum distance from the first endcut
on the first profile and the last endcut on the last profile. Default value is -1.
If not greater than zero, the MIN_DIST value is used.
USE_ENDCUT=YES/NO
Information to the system whether the scrap material produced when cutting an endcut,
shall be possible to use for nesting. Default value is 0.
PRESENT_RIGHT=YES/NO
If yes, the result from the nesting will be presented from right to left on the raw bar. The
individual profiles will be pushed to the right end of the raw bar leaving scrap, if any in the
left end. Default value is NO.
BEFORE_BENDING=YES/NO
Measuring of holes along a shell profile is presented in the fabrication list of profiles.
Measuring can be done before (YES) bending or after (NO) bending. The default value is
NO.
LENGTH_IN_LIST=MOULDED/MOULDED_EXCESS/TOTAL
The length of a profile is presented in the fabrication list for profiles. The presented length is
presented either as the moulded length (MOULDED), the total length (TOTAL) or the
moulded length plus any excess values (MOULDED_EXCESS). Default value is
MOULDED.
Note: For curved profiles, MOULDED should be read as the moulded trace length of the
profile transferred to the neutral axis of profile.
MANSTIFF_ECUT=FULL/TYPE
The endcut is either presented with the code (FULL) or the type (TYPE) in the fabrication list
for profiles. Default value is TYPE.
MANSTIFF_WEIGHT=YES/NO
The approximate weight (not considering endcut and holes) can be presented in the
fabrication list for profiles. Default value is NO.
NEST_AS_SORTED=YES/NO
This keyword is to be used if nesting shall be done exactly in the same order as given in
input. Default is NO.
IDENT_STRING=<Customisation of IDENT STRING>
The following keywords in the generic file can be used in the IDENT_STRING:
All keywords are given within the signs < and > and they shall be given in capital letters. All
text outside these signs is not translated in any way, but simply transferred to the resulting
IDENT string of the generic format
The example below is illustrating the use of this option:
Example:
<ASSEMBLY_LOW>-<CUSTOMER_DATA_1>X<QUALITY>
This will result in the following IDENT string in the generic format:
U_A-BDXA00
when lowest assembly is U_A, first customer data is BD and quality is A00
IDENT_MAN=<number>
The standard fabrication list for profiles generated via the generic format contains a row for
each profile with lowest existing assembly. This is possible to change to a row with the
IDENT string instead. Assembly string is selected by giving the number 1 (default), the ident
string is selected by giving number 2 and by giving 0, no row at all will be printed.
The possibility to select assembly is kept for compatibility reasons, since the ident sting can
be customized to contain this.
IDENT_PLOT=<number>
The Nested Profile sketch program is marking the profiles in their left end with a text in case
the program is not setup with a drawing form containing $ rules. This text is by default either
customer specific or strings containing ship number, long part name, direction and side of
ship.
If <number> equals 0 then no text is presented. If <number> equals 1 (default) the default
text is used and if <number> equals 2 then the IDENT string is used.
PSKETCH= YES/NO
Keyword used to activitate the profile sketch function when running Profile Sketch and List.
PSKETCH_BEND_SIMPLE= YES/NO
The keyword can be used to activate the profile sketch function only for profiles with simple
bending curves (profiles with bending that can be described by feed and bend instructions).
Only needed in case the PSKETCH keyword has been set to NO. Default value is NO.
PSKETCH_BEND_COMPLEX= YES/NO
The keyword can be used to activate the profile sketch function only for profiles with
complex bending curves (profiles with bending that can’t be described by feed and bend
instructions). Only needed in case the PSKETCH keyword has been set to NO. Default
value is NO.
PGEN= YES/NO
When PGEN is set to NO generic files and mounting data will not be created by Profile
Sketch and List. When PGEN is set to YES generic files and mounting data will be created.
Default value is YES.
CGEN= YES/NO
When CGEN is set to NO generic files and mounting data will not be created by Profile
Cutting Interface. When CGEN is set to YES generic files and mounting data will be created.
Default value is YES.
CSKETCH= YES/NO
Keyword used to activate the profile sketch function when running Profile Cutting Interface.
Default value is NO.
CSKETCH_BEND_SIMPLE= YES/NO
The keyword can be used to activate the profile sketch function only for profiles with simple
bending curves (profiles with bending that can be described by feed and bend instructions).
Only needed in case the CSKETCH keyword has been set to NO. Used when running
Profile Cutting Interface. Default value is NO.
CSKETCH_BEND_COMPLEX= YES/NO
The keyword can be used to activate the profile sketch function only for profiles with
complex bending curves (profiles with bending that can't be described by feed and bend
instructions). Only needed in case the CSKETCH keyword has been set to NO. Used when
running Profile Cutting Interface. Default value is NO.
MANSTIFF=YES/ENG/ENGLISH/GER/GERMAN/NO
Keyword used to activate the manstiff list when using the Profile Interface or the Profile
Cutting Interface. The list can be presented in either English or German. Default is English.
Default value of the keyword is NO.
MANSTIFF_COMBINE=YES/ NO
If set to YES, then equal profiles (profiles with the same long partname) will be sorted
together and presented in one row in the manstiff list. Default value is NO. The keyword will
not have any effect when using the Profile Cutting Interface (using Nested Profiles as input).
MANSTIFF_ONE_LIST=DEFAULT/BLOCK/ASS
The absence of this keyword will result in individual Manstiff lists for each different profile
type and dimension. The file is named as the first selected profile of this type.
Using this keyword, will combine all Manstiff lists from a Profile List and Sketch session into
one list file. The naming of this file will be made according to the keyword value:
DEFAULT The list file is named according to one of the involved profiles (in the same
way as when not using this keyword.
BLOCK The list file will be named: Manstiff_<block name>. Block name is
fetched from one of the involved profiles
This keyword is not valid when presenting Manstiff lists for nested profiles (using the Profile
Cutting Interface). In this case each nested profile will generate a separate list file
TSK=<text>
Keyword used to define the text to be used on knuckle lines on bent profiles. The text will be
presented together with an angle value and will be used for knuckles on the non-moulded
side (as presented in the profile sketch). Default value is DSK.
OSK=<text>
Keyword used to define the text to be used on knuckle lines on bent profiles. The text will be
presented together with an angle value and will be used for knuckles on the moulded side
(as presented in the profile sketch). Default value is OSK.
TSR=<text>
Keyword used to define the text to be used on knuckle radius lines on bent profiles. The text
will be presented together with an radius value and will be used for rolling on the non-
moulded side (as presented in the profile sketch). Default value is DSW.
OSR=<text>
Keyword used to define the text to be used on knuckle radius lines on bent profiles. The text
will be presented together with a radius value and will be used for rolling on the moulded
side (as presented in the profile sketch). Default value is OSW.
RADIUS = <text>
Keyword used to define a prefix to the presented radius value when rolling on bent profiles.
Default value is R.
MARK_BEND_SIDE = BOTH/REFLECTED
Knuckle lines are by default marked on the bending side. This can be changed by using this
keyword.
LE1
LE2
LE3
Keywords used to set values used when creating hooks in holes as described by the figure
below. LE1 is used for all thicknesses below 10 mm, LE2 is used for thicknesses greater or
equal than 10 mm and below 26 mm and LE3 is used for all thicknesses greater or equal
than 26 mm. Default values are 10 mm for LE1, 20 mm for LE2 and 30 mm for LE3
DE1
DE2
DE3
Keywords used to set values used when creating hooks in holes as described by the figure
below. DE1 is used for all thicknesses below 10 mm, DE2 is used for thicknesses greater or
equal than 10 mm and below 26 mm and DE3 is used for all thicknesses greater or equal
than 26 mm. Default values are 0 mm for DE1, 0 mm for DE2 and 15 mm for DE3
RE1
RE2
RE3
Keywords used to define the safety radius when creating hooks in holes as described by the
figure below. RE1 is used for all thicknesses below 10 mm, RE2 is used for thicknesses
greater or equal than 10 mm and below 26 mm and RE3 is used for all thicknesses greater
or equal than 26 mm. Default values are 10 mm for RE1, 20 mm for RE2 and 50 mm for
RE3
BEV_COMP_ANG = YES/NO
The opening angles resulting from bevel definitions are presented by default (YES) as the
complementary angle. This can be changed by setting this keyword to NO.
BENDING_TAB_METHOD
Different customer specified methods are implemented and can be activated using this
keyword. The implementation is made only for the Profile Cutting Interface. Further
information can be found in Automatic Addition of Bending Excess to Curved Shell
Stiffeners.
MIRROR_BENDING = TRACE/TABLE
Keyword describing how to reflect a shell profile stored on the “other side” when calculating
the inverse bending information. Either the profile trace is mirrored or the contents of the
bending table is reflected. Default value is TRACE.
BENDING_TAB = <No. of>
Maximum number of bending tables. Default and maximum value is 10.
DIST_BEND_POINTS
Defines the distance between the reference points in the bending table(s) for the bending
sight line(s). Default value is 500. See also Hull / Manufacturing / Profile Manufacturing /
Production Output Profiles / Bending Information for Shell Profiles.
OVERLAP = <No. of Points>
When creating the bending lines, the overlapping number of reference points can be
controlled using this keyword. Default value is 1.
BEND_ON_TOTAL = YES/NO
Bending information can be calculated on moulded length or the total length. Default value
is NO (moulded).
SELECT_ONE_ASSEMBLY_LEVEL = YES/NO
This keyword applies to the Profile Nesting application when profiles to be nested are
selected by assembly input. If the keyword is set to YES then only profiles on the specified
assembly level are selected. Otherwise when set to NO (Default) profiles on the specified
level and all levels below are selected.
SKIPHOLE_DIST = <mm>
Distance in mm. Holes that are closer than SKIPHOLE_DIST to profile edge will not be
present in the production output files.
SKIPTWIST_DIST = <mm>
Distance in mm. If a frame intersects a twisted profile at a distance less than
SKIPTWIST_DIST, measured from the profile end at the top of the manufactured profile,
then twist data for this frame is disregarded in production output files.
Please also see the description of frame twist data in the profile generic file.
DOTORI_ANG_INT = <deg>
Dotori marking along profile trace is calculated at equal angle intervals. DOTORI_ANG_INT
specifies in degrees the angle interval for dotori presentation in all production output files.
DOTORI_ANG_TOL = <deg>
A tolerance used to calculate the angle intervals described above.
BEVEL_ON_SKETCH = YES/NO
A bevel code text can be optionally presented at the bevelled segment of an endcut. Also
bevel along the trace is presented if bevel presentation is on. Bevel trace code is placed in
the middle of the profile close to the trace. Bevel trace is not marked if Dotori.
YES (default) - bevelling information is placed on the sketch
NO - bevelling information only possible via $-value
BENDING_INSIDE_PROFILE = YES/NO
Bending information can now be set inside the profile picture.
For more information see separate section under Hull / Manufacturing / Profile
Manufacturing / Production Output Profiles.
BENDING_MARK_START
Label for start of bending. Default value is BS.
BENDING_MARK_END
Label for end of bending. Default value is BE.
PREFIX_RAD_TS
MIN_DIST
MIN_DIST_RBENDS
For a description of those keywords please see the previous section Set-Up for Profile
Fabrication.
All other keywords in the restriction file are only valid for the profile type below which they
are listed. A section like this is always started by the keyword:
PROF_TYPE=<No.>
The number used is according to the design standard, e.g. 10 for flat bars, 20 for HP bars,
etc. The section is ended by a new PROF_TYPE keyword or by end of file.
SHAPE_TRANSLATE=
This keyword is used to translate the default shapes (FB, HP, etc.) into a yard specific
translation. The translated shape will be used in fabrication lists.
MIN_RAW=<mm>
Minimum length in mm of raw material that can be handled by the robot used. Raw materials
below this length will be handled manually.
MAX_RAW=<mm>
Maximum length in mm of raw material that can be handled by the robot used.
MIN_PROF=<mm>
Minimum length in mm of profiles that can be handled by the robot used.
There is also a possibility to restrict the size of the endcuts and the size of the middle part of
the profile, possible to clamp. The definitions in the picture below is used in this document.
The two different ways to place text on profiles are selected by value TOP or BOTTOM.
TEXT_DIST_TOP=<mm>
Distance from top of text to top of profile. This keyword is used when TOP is selected above.
TEXT_MAX1=<mm>
Limit 1 used when positioning text from bottom.
TEXT_MAX2=<mm>
Limit 2 used when positioning text from bottom.
TEXT_HOR1=<mm>
TEXT_VER1=<mm>
TEXT_HOR2=<mm>
TEXT_VER2=<mm>
TEXT_HOR3=<mm>
TEXT_VER3=<mm>
When BOTTOM is selected, the text position is depending of the profile height. The text
position is calculated as a horizontal and a vertical distance from the profile bottom line and
from the profile left edge to the lower and left edge of the text. The following rules are used:
Use HOR1 and VER1 if profile height is less equal than TEXT_MAX1.
Use HOR2 and VER2 if profile height is less equal than TEXT_MAX2.
Use HOR3 and VER3 if profile height is greater than TEXT_MAX2.
Hooks are automatically inserted in holes. The keywords below defines the size of such
hooks.
HOOK_<thickness>=<radius in mm>
The system automatically selects the hook valid for the current profile thickness. If this one
is not defined in this restriction file, it tries to find a hook radius for a thinner profile.
<thickness> above can have values between 1 and 50.
SIDE_UP = MOULD/NON_MOULD/MOST_MARKINGS
Profile sketch looking direction. Default value is MOULD side.
Endcuts allowed by the robot used shall be defined with the keyword below:
ENDCUT=<No.>
The keyword can be used any number of times. The value of the keyword must be
according to the Design Standard.
Each ENDCUT-keyword can be followed by three new keywords, with information valid for
this keyword:
BEVEL_FLANGE=YES/NO
BEVEL_WEB=YES/NO
EXCESS=YES/NO
These keywords are restricting the robot used, but are also used when formatting output
data in the Profile Cutting Interface, i.e. when no bevel on web, the bevel code is normally
presented with a zero (0), but with the corresponding keyword set, it will be presented with a
dash (-).
EXTRA_DIST=<endcut type>_<distance in mm>
For example means 20_100_21=11 that the tuning time for profiles of type 20 with height
100 and endcut of type 21 is 11 seconds.
The time calculations are performed in the Profile Cutting Interface and is described in the
documentation of this product.
ADDDISTBULB_<profile_height>=<mm>
An extra distance between profiles with a bulb or flange can be defined if needed for some
reason. Profile height can have the values 150 and 200 to 500 with steps of 5.
The keywords below shall be used if there are restrictions on the length of the last profile
nested on the raw material. If these keywords are set and fulfilled, then the first profile is
moved to be last and the last profile on the raw material is moved to be first.
LM_MIN_<height>=<mm>
See definition on LM above (below MIN_PROF). If the last profile nested is below this limit.
LM_MIN_REST_<height>=<mm>
REST_LIMIT_<height>=<mm>
Miscellaneous
1.1 Background
Hull allows the user to specify the material quality (grade) of all parts when they are
modelled. The assigned material qualities must all have been registered on beforehand via
a user defined text file that is described in this document.
File layout:
Remarks:
1. The densities can be changed at any moment. The new value will come into operation
the next time the material is accessed.
2. <paint i> can be changed at any moment. The new string will come into operation the
next time the paint information is accessed.
3. New qualities can be added at any moment.
4. For a material quality with the default density the density need not be given explicitly
but may be replaced by an asterisk (*).
5. The quality with <int_code>=0 will be output as the default quality, i.e. the quality you
get if not explicitly defined.
1.3 Remark
The hull utility inithull can be used to check a newly established quality file for correctness.
If only numbers are to be used in the quality name it is necessary to give the same numbers
in the code.
e.g.
14571 14571 *
2 Destination Definition
2.1 Description
Hull allows the user to specify the destination in the workshop of parts such as plates,
brackets, stiffeners, flanges and pillars. The valid destinations must be defined by the
customer, see the specification below. The intention is to define the workshop station where
the different parts will be assembled. However, the user is free to use it as he likes.
The user has the possibility to pick the destination in the different hull modelling modules. A
given value will be accepted only if it has been registered in a special set-up file otherwise
an error message will be returned.
The selected destination of plates and brackets will be transferred to the parts after parts
extraction. Destinations are available e.g. via Data Extraction.
For plane panel profiles, as well as for shell profiles, the destination will be transferred to the
split profile parts (if necessary assignments are made).
3.1 Description
Hull allows the user to specify surface treatment of different types of parts such as plates,
brackets, stiffeners, flanges and pillars. The values given must be registered by the
customer on beforehand as specified below. The intention is to define the type of treatment
of the parts before the production phase. However, the user is free to use it as he likes.
The user has the possibility to set surface treatment in different hull modelling modules. A
given value will be accepted only if it has been registered in a set-up file otherwise an error
message will be returned.
For plate parts in general the surface treatment will be transferred to the plate parts after
parts extraction. The surface treatment can be accessed e.g. via Data Extraction.
For plane panel profiles, as well as for shell profiles, the surface treatment will be
transferred to the split profile parts (if necessary assignments are made).
4.1 Description
Hull allows the user to specify the Data type and Geometry type of a plane panel. These
numbers offers the user a way of classifying panels in a way that he finds suitable. When
using Create statement for the panel statements the data and geometry types that are
available can be controlled in files associated with the environment variables
SBH_PANEL_DT and SBH_PANEL_GT, that is, ordinary text files containing the valid
numbers to use (one number on each row). In the Panel statement form only those numbers
available in the files are presented. The numbers are presented in the same order as in the
files. Reserved numbers (957, 958 and 959 (Bracket Panels, Knuckled Sub-panels and
Outfitting Steel Panels)) will not be valid even if present in the files.
If a file is missing, the default number ‘101’ will be used.
1 Customising Dialogues
1.1 General
Graphical menus used in dialogues (e.g. hole type selection) are controlled and customised
by updating a specific drawing and the corresponding picture object attributes connected to
these drawings. The drawings all have fixed names and are stored on SB_SETTINGS_DB,
which is accessible from the Drafting application.
The Template project, delivered together with the product, contains examples of the
drawings that are used for the dialogues.
1.2 Drawings
The dialogues are controlled and customised by updates of normal drawings where each
view represents an entry point within the dialogues. The updating is made using standard
Drafting functions in general and specifically the function Tools->Inspect Drawing-
>Attributes to change the attribute information
The following drawings (existing in the Template project) are currently used:
1.2.1 Customising
Customising is normally made by manual changes to the drawings used for dialogue
creation. However, in some cases this is made by the functions automatically as specified
below:
1.2.2 Attributes
To control the dialogue, picture attributes are added on view level. The following general
attributes should be used:
9962
9961
Hole dialogue:
0 - Standard hole.
1 - Penetration for a pipe or a ventilation duct.
2 - Penetration for a pillar.
3 - Hole from curve.
If the variable I2 does not exist then a standard hole is
assumed.
Notch dialogue:
0 - Standard notch.
1 - Notch from curve.
If the variable I2 does not exist then a standard notch is
assumed.
Endcut dialogue:
Endcut type.
9960
General
PLPL (Planar Plate)
PLPR (Planar Profile)
SHPL (Shell Plate)
SHPR (Shell Profile)
STPL (Structure Plate)
STPR (Structure Profile)
NDIS (Not Displayed)
Bracket specific:
SYN1
SYN2
SYN3
SYN4
SYN5
SYN6
SYN7
SYN8
SYNV
Cutout Specific:
10
20
21
.
.
.
43
For the classification shapes in drawing
__SBH_REST_PLATES__ the contents of this attribute is
defined differently as specified below:
S1-Sn T
The names of classification shape arguments.
Totally 7 can be defined. The exact number is
defined by I2 below.
I1
Shape type
I2
Number of arguments
R1-Rh
Optional default values for each shape argument.
Endcut Specific:
9959
Only the drawings on the top level are having fixed names,
defined by the system. Drawings on lower levels are
named by the user, all referenced drawings must start with
two underscores ("__")
1.2.3 Example
The picture below shows the drawing __SBH_HOLE_MENU__ that is used for the hole
dialogue implementation:
1.1 General
This document describes the set-up and customisation of line types and colours in Symbolic
Planar Hull Views. The set-up is generated as a control object (named LT below) on the data
bank from an input file written by the user using the syntax described below. The LT object is
created in Inithull (Other standard set-up) and it is activated via a default in the standard
default file used by Marine Drafting.
The customisation can be made on individual hull components. The components that are
not customised will be drawn with default line type and colour.
/LIST A list of the LT object is generated. The list includes both settings made by the
user and the default values. The result file can be used as an input file with
small modifications.
• OVERRIDE_COLOUR_P Statement
The statement is used if this customisation shall override any modelled colour on a
Production Panel.
• OVERRIDE_COLOUR_D Statement
The statement is used if this customisation shall override any modelled colour on a Design
Panel.
• Component Statements
All component statements can have attributes to control the line type or the colour. The
attributes are listed below:
/LT='value' The attribute controls which line type to use for a specific
component. The line type value is given as a string.
CLIP_TS Used to control a clip plate in a planar view. The clip plate is
on this side of the plate it is attached to.
CLIP_OS Used to control a clip plate in a planar view. The clip plate is
on the other side of the plate it is attached to.
1.1.3 Colours
Colour names that can be used are specified in Marine Drafting / User Guide / Appendices.