M3 Outfit Manager SP4

Tribon Outfit
Manager
Training Guide • Training Guide • Training Guide

Revision Log
Date Page(s) Revision Description of Revision Release
19/10/2004 Various 01 Updated to M3SP2 M3SP2

12/05/2005 Various 02 Updated to M3SP3 M3SP3
06/08/2005 - 03 Checked against M3SP4 M3SP4
Updates
Updates to this manual will be issued as replacement pages and a new Update History Sheet complete with instructions
on which pages to remove and destroy, and where to insert the new sheets. Please ensure that you have received all
the updates shown on the History Sheet.
All updates are highlighted by a revision code marker, which appears to the left of new material.
Suggestion/Problems
If you have a suggestion about this manual or the system to which it refers please report it to the training department at
Fax +44 (0)1223 556669

Email training.uk@aveva.com
Copyright © 2004 Aveva Solutions Ltd
All rights reserved. No part of this publication may be reproduced or used in any form or by any means (graphic,
electronic, mechanical, photocopying, recording, taping, or otherwise) without written permission of the publisher.
Printed by Aveva Solutions Ltd on 04 October 2005

Contents
1 Outfit Set-up & Customisation .......................................................................................................... 5

1.1 Using Frame Numbers in the Outfitting Systems ..................................................................... 5
1.2 Define Model Co-ordinates, sx001 ............................................................................................. 6
1.2.1 Environment.......................................................................................................................... 7
1.2.2 Types of Planes .................................................................................................................... 7
1.2.3 Input File syntax.................................................................................................................... 7
1.2.4 The IDENT Statement........................................................................................................... 7
1.2.5 The REFERENCE Statement................................................................................................ 7
Worked Example, Define Model Co-ordinates ...................................................................................... 8
1.3 Pipe & Ventilation ....................................................................................................................... 9
1.3.1 Flange Offset Tables............................................................................................................. 9
1.3.2 Nominal Diameter Tables.................................................................................................... 11
1.3.3 Boss Types......................................................................................................................... 12
1.3.4 Pipe Object Types............................................................................................................... 14
1.3.5 Naming Conventions for Tribon Pipe Objects ...................................................................... 14
1.4 Migration of Specifications and Diagrams from TB5 & M1v4 to M3. ...................................... 14
1.4.1 Pipe Specifications.............................................................................................................. 14
1.4.2 Pipe Diagrams .................................................................................................................... 15
1.4.3 Cable Diagrams .................................................................................................................. 15
1.4.4 Using the valves/pipes from imported Diagram lists in M3 Pipe Modelling (sp303) ............... 15
1.5 Cable ......................................................................................................................................... 16
1.5.1 Dimensioning Table SBC_TAB1.......................................................................................... 16
1.5.2 Default Files........................................................................................................................ 16
1.6 Structure ................................................................................................................................... 17
1.6.1 Components in TRIBON Structure....................................................................................... 17
1.6.2 True Components ............................................................................................................... 17
1.6.3 Structure Object Types........................................................................................................ 18
1.7 Equipment import utility........................................................................................................... 19
1.7.1 Template for importing equipments ..................................................................................... 19
1.7.2 Running the import.............................................................................................................. 20
1.8 Data Extraction introduction.................................................................................................... 21
1.8.1 Running Data Extraction ..................................................................................................... 21
1.8.2 Using sx711 ........................................................................................................................ 21
2 Creation of Modules and Systems .................................................................................................. 23

2.1 Description ............................................................................................................................... 23
2.2 Creating a new Module............................................................................................................. 23
2.3 Creating a new Pipe System .................................................................................................... 24
2.4 Deleting Modules and Systems ............................................................................................... 24
3 Piping Machine Objects................................................................................................................... 25

3.1 Pipe component Bending code................................................................................................ 25
3.2 Bending Machine...................................................................................................................... 26
3.2.1 Bending Dimension Data..................................................................................................... 27
3.2.2 Deleting Bending Dimension Data....................................................................................... 28
3.2.3 Bending Machine Data........................................................................................................ 28
3.2.4 Bending machine planes, Worked example......................................................................... 31
3.2.5 Spring-back data................................................................................................................. 36
3.2.6 Delete Bending Machine ..................................................................................................... 37
3.2.7 Making Lists........................................................................................................................ 37
3.2.8 Multiple Bending Machine Objects....................................................................................... 38
3.3 Flange Welding Machine .......................................................................................................... 38
3.3.1 Min/Max values................................................................................................................... 39
3.3.2 Add flange group................................................................................................................. 39
3.3.3 Delete flange group............................................................................................................. 39
3.3.4 List welding machine data ................................................................................................... 40
3.4 Boss extrusion machine .......................................................................................................... 41
3.4.1 Boss Machine dimension data............................................................................................. 41
3.4.2 Boss Machine distance data................................................................................................ 42
3.4.3 Delete machine dimension data .......................................................................................... 42
3
3.4.4 List machine dimension data ............................................................................................... 43
3.5 Machine Object Set-up in TTP Project..................................................................................... 43
4 Standard Handling ........................................................................................................................... 45

4.1 Symbols .................................................................................................................................... 45
4.1.1 Symbol Creation ................................................................................................................. 46
4.1.2 Symbol Connections ........................................................................................................... 46
4.1.3 Text Positions ..................................................................................................................... 47
4.1.4 Automatic Positioning of a Symbol ...................................................................................... 47
4.1.5 Removing Symbols from a Symbol Font.............................................................................. 47
4.1.6 sb021 - Symbol Font Utility Program ................................................................................... 47
4.1.7 Font Naming and Location .................................................................................................. 48
4.1.8 The Font Head Viewer Form ............................................................................................... 48
4.1.9 Worked Example, Symbol Creation ..................................................................................... 48
4.1.10 Symbol font Migration Programs ......................................................................................... 50
4.1.11 Symbol Fonts Reserved by the System ............................................................................... 51
4.2 Drawing Forms ......................................................................................................................... 52
4.2.1 Normal Forms ..................................................................................................................... 52
4.2.2 Modelling Forms ................................................................................................................. 58
4.3 Sb029 Print symbol font drawing(s) ........................................................................................ 60
4.4 Create a standard hatch pattern .............................................................................................. 61
4.5 Standard Details ....................................................................................................................... 63
4.5.1 sb028 - Handle Standard Objects........................................................................................ 63
4.5.2 Worked Example, Save Standard Detail.............................................................................. 65
4.6 Standard Units.......................................................................................................................... 67
4.6.1 Saving a Unit ...................................................................................................................... 67
4.7 Standard Structures ................................................................................................................. 68
4.7.1 Environment variables......................................................................................................... 68
4.7.2 Default parameters in SBD_DEF1. ...................................................................................... 68
4.8 Component Naming.................................................................................................................. 68
4.8.1 Delivered Components........................................................................................................ 68
4.8.2 Structured Naming .............................................................................................................. 69
4.9 Components, use of text file .................................................................................................... 70
4.9.1 Input File............................................................................................................................. 70
4.9.2 Components to file (su015) ................................................................................................. 71
4.9.3 Components from file (su016) ............................................................................................. 72
5 Tribon.com ....................................................................................................................................... 75
5.1 User Interface ........................................................................................................................... 76
5.2 Getting Started ......................................................................................................................... 77
5.3 Logging in................................................................................................................................. 77
5.4 Information ............................................................................................................................... 78
5.5 Local Language Support.......................................................................................................... 78
5.6 Menu Bar................................................................................................................................... 79
5.7 Utilities ...................................................................................................................................... 79
5.7.1 Software Download ............................................................................................................. 79
5.8 Logging off ............................................................................................................................... 81
5.9 Settings..................................................................................................................................... 82
5.10 General...................................................................................................................................... 83
5.11 Company................................................................................................................................... 83
5.11.1 Presentation........................................................................................................................ 83
5.11.2 Configuration Page ............................................................................................................. 83
5.12 Preferred Suppliers List ........................................................................................................... 86
5.12.1 Viewing the available lists ................................................................................................... 86
5.12.2 Creating new preferred supplier lists ................................................................................... 87
5.12.3 Use of preferred supplier lists.............................................................................................. 88
5.13 Project....................................................................................................................................... 89
5.14 User........................................................................................................................................... 89
5.15 User Administration ................................................................................................................. 90
Appendix 1, Bending Machine Set-up .................................................................................................... 91
4
Chapter 1
1 Outfit Set-up & Customisation

This Chapter deals with some of the important steps required in order to customise the set-up of a project from an
Outfitting perspective. We will look at each discipline in turn starting with two general applications.
1.1 Using Frame Numbers in the Outfitting Systems

Typically the Hull users create a frame table at the start of each project. The values are stored in an object with the
name __SBH_GENTAB__ in the SB_OGDB database
It is normal that the frame table values are written in a file as below which becomes input to the Initiate Hull Standards
application: -
 See the Hull Manager Training Guide for full details of the input file.
5
This creates table objects in two databanks: -

 SB_OGDB to be used by the Hull System __SBH_GENTAB__

 SB_REFDB to be used by Outfitting systems <PROJ>=GENTAB==
1.2 Define Model Co-ordinates, sx001

The purpose of this program is to define co-
ordinates and planes that later can be
referred to in the Tribon Outfit modelling
systems. So, for example, one can then refer
to waterlines, decks etc instead of always
using absolute co-ordinates (distances from
the ships origin where x=0,y=0,z=0).
6
1.2.1 Environment
SB_OGDB SB_REFDB
SX001 LIST
INPUT
1.2.2 Types of Planes

The planes can be of the following kinds: -

 Named Co-ordinates

 Frame Planes

 Waterline Planes

 Buttock Planes

 Hull Planes
Co-ordinates can be defined directly via input to the program. While the other planes are fetched from the Hull system.
1.2.3 Input File syntax

There are two statement keywords: -

 IDENT

 REFERENCE
1.2.4 The IDENT Statement

This statement contains information valid for the whole program. The given project name will be used to define the
names of the created objects, when stored in SB_REFDB.
[,<id>] User identification string (maximum 26 characters). This string is optional.
/PROJECT=<projid> <projid> Project identification string (maximum 26 characters).
Example: IDENT,’Joe Bloggs’/PROJECT=’TTP’;
1.2.5 The REFERENCE Statement

This statement is used to define all coordinate references to the TRIBON Hull data bank and to create new planes and
coordinates.
[,<refid>] String maximum 26 characters long. It defines the name of the coordinate. It must always be given
except when a coordinate table is defined.
[/XTAB=<hull table name>] Define a x-coordinate table to be fetched from TRIBON Hull.
[/YTAB=<hull table name>] Define a y-coordinate table to be fetched from TRIBON Hull.
[/ZTAB=<hull table name>] Define a z-coordinate table to be fetched from TRIBON Hull.
<hull table name> Name of object in TRIBON Hull containing coordinate tables
.Example: REF/ZTAB=’TTPZTAB’;
[/X=<coordinate>] Define an x-value with the name <refid>.

[/Y=<coordinate>] Define an y-value with the name <refid>.
[/Z=<coordinate>] Define a z-value with the name <refid>.
<coordinate> Coordinate value.
7
Example: REF,’FPS’/X=103600;
[/PANEL=<panel name>] Defines a panel to be used as a coordinate reference plane. The reference name
will be <refid>.
<panel name> Name of hull panel (string maximum 26 characters long).
Example: REF,’BHDA’/PANEL=’SB512-3’;
1.2.5.1 Example input file

IDENT,’JB’/PROJECT=’TTP’;
REF, 'TANKTOP'/PANEL='BLOCK1-TTF';
REF, 'UPPERDECK'/Z=20000;
REF/XTAB='TTPXTAB';
REF/YTAB='TTPYTAB';
1.2.5.2 Result
The coordinate references are stored in the SB_REFDB. A result list, MODCOORD.lst, is created showing the input
statements and messages from the program.
Worked Example, Define Model Co-ordinates


 Open a DOS window and go to the M3 bin directory. Then run SX001: -

 Check the result file: -

 Then using the Tribon M3 DB utility, check the objects in the Reference database: -
 The default COORD_TRANS in the drafting

default file SBD_DEF1 can be varied so as a
3D co-ordinate dimension can display these
references.
 Refer to the Drafting User Guide for

full details
8
1.3 Pipe & Ventilation
1.3.1 Flange Offset Tables

The amount that a pipe flange is offset from the end of the pipe is referred to as the flange offset. In the normal case, the
pipe material will be reduced by this ‘building length’. In the case of a backing ring flange (type code 2206) the pipe is
extended beyond the flange and therefore excess material is added to the pipe to allow for flanging of the pipe material.
In either case, it is important that the offsets produced agree with the shipyards internal production processes in order to
produce the correct cutting lengths on the pipe sketch.
Figure 1.3.1, showing on the left a normal slip-on flange and on the right a backing ring flange
The pipe system can calculate this offset using either: -

 Internal, default values

 A customisable flange offset file, SBP_FLG_OFFSET
1.3.1.1 Internal default values

The default values are 10 mm if wall thickness is greater than 7.1 mm, otherwise 6 mm. For ventilation there is no
default value for offset, so it has to be defined in the flange offset file. The default excess values are based on the
following formula: -
<excess> = ( <collar dia> - DY ) * 0.5
where DY is the outer diameter of the pipe, and collar diameter is fetched from the table below.
DY Collar diameter
< 65 88
< 80 108
< 100 124
< 125 144
< 150 169
< 200 199
>= 200 254
 Note that the default excess values are calculated only up to and including ND 200,.if greater values are required
then the customisable file SBP_FLG_OFFSET will need to be used.
9
1.3.1.2 Flange Offset File
In order for the system to use this method for calculating the offsets the following criteria must be met: -
1. The variable, SBP_FLG_OFFSET must be set in the d065 project file

2. The file, SBP_FLG_OFFSET must exist
3. The file must contain relevant data for the particular interval
In the d065<project>.sbd file: -
SBP_FLG_OFFSET C:\Projects\TTP\def\sbp_flg_offset.def
If the assignment does not exist, or if the file does not contain any valid interval, the default values will automatically be
used.
Record format
The offset may be defined within the flange-offset file via the following data types: -

 Flange Group

 DN

 DY

 Wall Thickness
The offset file contains a number of record types each one associated with certain data types: -
Record types Data
1 <version no.>
a user identification to handle multiple versions.
2 <table type>
1 = The table values are upper limits for the offset.
The limit is not included in the interval.
3 Description string
4 <Offset> <DN> <DY> <Wallthickness>
5 <Offset> <DN> <DY> <Wallthickness> <Flange group>
6 <Offset> <Height or Diameter> <Width or Not used>

< Wallthickness>
7 <Offset> <Height or Diameter> <Width or Not used>

<Wallthickness> <Flange group>
10 <Excess> <DY>
The modelling programs first check if the flange group name exists (in record 5) and then DN or DY or wall thickness to
get the offset which matches the checked record data.
Example 1, using DN Ranges
If a pipe has a nominal diameter of 250, the offset will be 7 mm. If a pipe has a nominal diameter of 300, the offset will
be 11 mm.
10
Example 2, Using DY, Flange Groups and Ventilation
If a pipe has an outer diameter of 244.5 mm, the offset will be 7 mm. If a flange group exists, the offset will be 4 mm. If a
pipe has an outer diameter of 273 mm, the offset will be 11 mm. If a flange group exists, the offset will be 3 mm. If a pipe
has an outer diameter of 76.1 mm, the collar excess will be 17 mm. If a ventilation duct has a height that is less than 251
mm, the offset will be 4 mm, unless it is included in the group ABC, in which case it will be 5 mm.
Example 3, Using Wall Thickness
If a pipe has a wall thickness of 2.95 mm, the offset will be 4.4 mm.
1.3.2 Nominal Diameter Tables

The system often has to determine the nominal diameter, DN of a pipe based on its outer diameter, DY. Applications
where this translation is used are: -
- Components
- Specifications
- General diagrams
- Data extraction
- Batch pipe modelling
- Interactive pipe modelling
- Statistics
- Insulation
The system can determine the DN in the following two ways: -

 From internal, hard coded tables

 From a user defined file, SBP_CMP_DATA_DEF
1.3.2.1 Internal Tables
 See the tables given in the Component User guide, Tribon M3 Outfitting > Components > Standard
Pipe Components
11
1.3.2.2 User Defined DN Tables
A variable SBP_CMP_DATA_DEF has to be assigned, pointing to an existing file containing the DN tables: -
In the d065<project>.sbd file: -
SBP_CMP_DATA_DEF C:\Projects\TTP\def\sbp_cmp_data.def
Record format
Record Data Description
Type
1 <version number> a user id to handle multiple versions

2 <table type> 1 = DN/DY-table (only 1 is valid)
3 <material type> 1 = Steel (material code 1-3,7-10)
2 = Copper (material code 4-6)
(Only 1 and 4 is valid)
4 <description string> maximum number of records = 10
5 <DN> <DY> the record can be repeated as many time as
needed
Example, showing DN10-DN50 for various material codes
1.3.3 Boss Types

Some of the main connection types for boss/branches are shown below.
EXTRUSION is not relevant unless you have an extrusion machine in the pipe shop. It is much more common in
shipbuilding to use a SADDLE type boss connection. The pipe training shows how the boss connection type may be
changed locally on the current pipe. Here we will deal with how to set-up the system to automatically choose SADDLE
instead of EXTRUDE.
BOSS_DEFAULT=NO (default) ON_SURFACE or INSERT or EXTRUDE or SADDLE in the SBP_MODEL_DEF file

When the keyword is set to a specific boss connection type this type will be used for all boss connections. If the keyword
is set to NO the built-in rules of the system will be used to choose a suitable connection type.
12
1.3.3.1 Pipe Component Extrusion Code
The pipe (tubing) components should be created with an EXTRUSION CODE=2 (extrusion of bosses not allowed: -
Extrusion code:
1 = extrusion of bosses allowed
2 = extrusion of bosses not allowed
1.3.3.2 Boss Machine Object

Of course if the customer does not use extrusion at all then the object $MACH$BOSS should not exist in the component
database, SBE_GENCMPDB.
1.3.3.3 Default Values

In the default file SBP_MODEL_DEF the values BOSS_EXCESS and MITRE_EXCESS can be defined.
If BOSS_EXECSS is not given the system default 50 will be used for saddle connection
If MITRE_EXCESS is not given the system default 100 will be used for external excess
For mitre also the internal excess is calculated according to the dia and mitre angle.
Other system defaults for internal excess are: -

* 17 for insert when pipedia<32 and 29 otherwise
* 0.26663*pipedia + 6.6440 for thread
* collar excess from SBP_FLG_OFFSET or
fladm = 88 if pipedia <65
" = 108 " <80
" = 124 " <100
" = 144 " <125
" = 169 " <150
" = 199 " <200
" = 254 otherwise
and excess = (fladm - pipedia) * 0.5
1.3.3.4 Rules for choosing type

Below you can find an extract from the logic that is built into the pipe modelling program. These are the rules that are
used to decide the type of boss connection. The logic is ”hard coded”, but if you find it is not quite suitable then you can
request that it should be changed via a CSR or by contacting FLS.
1. if typecode for boss comp is NOT between 7000 and 7999 (that is the boss is no pipe) AND
boss comp connection code is 1 then on surface is chosen
2. if pipe is straight pipe or straight frame AND
bossdia <= pipedia - 2*pipewallthi & bossdia< 33.7+dm_tol(0.04999) AND
abs(cos_angle) <= pipewallthi/(2*bossdia) then drill is chosen
3. if pipe is straight pipe or straight frame AND
bossdia <= pipedia - 2*pipewallthi AND
abs(cos_angle) <= pipewallthi/(2*bossdia) AND
pipedia/2 * (1-sqrt(1-(bossdia/pipedia)**2)) + 0.5 <= pipewallthi/2 then burn is chosen
4. if pipe comp extrude code is 1 AND pipedia<=bossdia AND
pipedia < 650 AND pipewallthi < 10
bossdia < 368 AND bosswallthi < 17.2 AND
"the boss is not sloping too much" then extrude is chosen
5. if pipe is steel AND boss is pipe material
then saddle is chosen
6. if pipe is non-steel AND boss is pipe material AND
bossdia > 133 then saddle non-steel is chosen.
7. otherwise saddle is chosen and warning message is given
13
1.3.4 Pipe Object Types
The different object types are named according to the table below: -
Object Type Name Location Example

Position object <proj>=POS SB_PSDB TTP=POS
Module object <proj>=<module>= SB_PSDB TTP=101A=
Function object <proj>=FUN SB_PSDB TTP=FUN
Pipe line object <proj>==<pipe line> SB_PSDB TTP==XX018
Pipe line within module <proj>=<module>=<pipe line> SB_PSDB TTP=101=XX018
object
Auxiliary reference object <proj>=AUX SB_PSDB TTP=AUX
Diagram list object <system>_DIAGRAM SB_VDIAGDB XX_DIAGRAM
Pipe Specification object <proj>==SPEC=<system> SB_SPECDB TTP===XX
Pipe Surface Treatment <proj>=SUR SB_PSDB TTP=SUR
1.3.5 Naming Conventions for Tribon Pipe Objects

The object names in Tribon Pipe are made up using
constituents and delimiters. A constituent can be the
name of the project, the name of the module, the name
of the system etc. A delimiter can be '-', '+', '=' etc,
depending on the type of object. For all Pipe object
names, as well as for different kinds of constituents,
length regulations apply. The diagram below displays the
maximum number of characters, that is handled by the
Tribon Pipe system, for each of these object names and
constituents.
 See Pipe User Guide, Tribon M3 Outfitting

> Pipe > Concepts > Organization,
Identifications, etc. in the PSDB for full
details of the Object types
1.4 Migration of Specifications and Diagrams from TB5 & M1v4 to M3.
1.4.1 Pipe Specifications.

TB5&M1v4 Pipe specifications can be merged to M3. In TB5&M1v4 Pipe Specifications are stored as files in the DB
directory.
The file name format is:

<PROJECT NAME>_<SPEC>_<NAME OF SPEC>_.DAT
e.g. ES_SPEC_WW_.DAT.
1. Copy the TB5/M1v4 Pipe Specification files from the TB5/M1v4 environment to the M3 environment, use
normal file ftp/copy procedures.
2. Select M3 project
3. From a command prompt window, run the M3 program TbSpecConversion.exe. This program converts the TB5
Pipe Specification file to a normal text file that can be imported by the M3 Pipe Specification program.
14
Use the following command:
TbSpecConversion [<path>]<infile> [<path>]<outfile>.
If path is not given, then SB_PIPEDATA will be used as default for infiles and the current directory for outfiles.
e.g.
TbSpecConversion ES_SPEC_WW_.DAT ww.txt
Start the M3 Pipe Specification program and Import the text file, ww.txt.
Use the function File > Import.
Save the imported Pipe Specification. File > Save
1.4.2 Pipe Diagrams
1.4.2.1 Diagram Drawing

TB5&M1v4 Pipe Diagrams can be merged by Project Copy to M3.
The merged Diagram has no Intelligence in M3 (no connection to the Diagram List object). They will be ordinary
drawings and can be edited with Drafting or any other Tribon interactive application.
1.4.2.2 Diagram List

TB5/M1v4 Pipe Diagram List objects can be merged to M3 by Project Copy.
Use the new Diagram List program (sp902.exe) to update and maintain the Diagram List object in M3.
1.4.3 Cable Diagrams
1.4.3.1 Cable Diagram Drawing

TB5/M1v4 Cable Diagrams can be merged by Project Copy to M3. The merged Diagram has no Intelligence in M3 (no
connection to Cable objects). Use Drafting to edit the Diagrams.
1.4.3.2 Cable Diagram List

TB5/M1v4 Cable objects can be merged to M3 by Project Copy.
Use Cable Modelling (sm001) and the function Cable > Change Data to maintain the Cable objects in M3.
1.4.4 Using the valves/pipes from imported Diagram lists in M3 Pipe

Modelling (sp303)
In sp303 the forms for Functions “New Pipe, Insert Part and Add Part”are changed to be able to read Valves from the old
Diagram List objects (Merged to M3). Gaskets and Flanges should be selected using M3 functionality.
Note! The new Resize/Respec functionality in M3 Pipe Modelling is dependant on new Specification functionality and will
not work fully for Valves selected from the old Diagram List object in the described way. The reason is that old data does
not have Specification information stored on part level. This is of course also true for already modelled objects.
In Interactive Pipe Modelling (sp303.exe)
1- Update default file (SBP_MODEL_DEF) with keywords:

DIAGRAMS=GENERAL
MAIN_FITTING_FROM_DIAGRAM=ON (new keyword)
2- In Interactive Pipe Modelling (sp303.exe)
a. Create a new Pipe by selecting the Pipe number as in Diagram List, the main Component is then
picked up from the Diagram List object.
b. Insert part by selecting ":D#V<no>" in the function combo box for a Pipe belonging a given Pipe
System.
15
1.5 Cable
1.5.1 Dimensioning Table SBC_TAB1

The tables used in the function "cable dimension" are to be defined in advance. The table definition is an ordinary text
file that should be attached to the logical name SBC_TAB1. The table has to have a specific layout as follows:
NOTABLES <integer> Statement telling how many tables to be used.

MAX_NOVAL <integer> Maximum number of values within any table.
TABLE_NO <integer> Table number that is to be filled in.
TABLE_DESCR <string> User defined string for table separation.
A/C <real> Area and maximum allowed current for this area.
1.5.1.1 Example of a Cable dimensioning table

NO_TABLES 2
MAX_NOVAL 5
TABLE_NO 1
TABLE_DESCR 'FREE, 20DEG'
A/C .75 5
A/C 1.00 10
A/C 2.5 12  These statements define three tables,
A/C 4 14 each with 5 values.
A/C 10 20
TABLE_NO 2
TABLE_DESCR 'FREE 60DEG'
A/C .75 7.5
A/C 1.00 10
A/C 2.5 12
1.5.1.2 Cable Object Types

The Cable System produces the following object types: -
Type Name OC1 Example

Cable <projnr>+<system>+<cable> 3000 TTP+WW+01
Cableway <proj>=<cway> 3001 TTP==CWXX1
Penetrations <proj>==PNTR 3002 TTP==PNTR
Workorder <proj>&<workorder> 3003 TTP&WO1
Route <proj>==N==<name> 3004 TTP==N==2011
Route dist <proj>==D==<name> 3005 TTP==D==2011
Route index <proj>==I==<name> 3006 TTP==I==2011
Route path <proj>==P==<name> 3007 TTP==P==2011
Cableway modulereference <proj>===$MOD$ 3010 TTP===$MOD$
Cableway module <proj>===MOD 3011 TTP===101
1.5.2 Default Files

A default file contains information of some parameters and constants that are used in the programs. In TRIBON Cable,
there are two levels of default files. Firstly, there is one default file with the logical name SBC_DEF, which is valid for all
TRIBON Cable programs. Secondly, each program can have its own default file containing parameters that are different
from those in the common default file. These program specific default files have the logical names SBC_DEF1,
SBC_DEF5 etc.
Logical name Usage

SBC_DEF Common default file
SBC_DEF1 Default file for SM005 (Update Cable Background)
SBC_DEF5 Default file for SM001 (Cable modelling)
SBC_DEF6 Default file for SM016 (List Cable Background)
16
1.6 Structure
1.6.1 Components in TRIBON Structure

In TRIBON Structure the parts are made up of components of three classes:
1. General component
2. Bar component
3. Plate component
In giving the component name two ways exist in the TRIBON Structure, giving true components and pseudo
components.
1.6.2 True Components

The true components are stored in the General Component data bank. When adding a component to the data bank a
name is given along with all dimensions and other properties. This name is then used in Tribon Structure to refer to the
component when creating parts. The naming of the component is up to the customer.
Plate and bar components are recognized by the system, and thus the outer contour of a plate and the length of a bar
must be specified together with the position in space. However any component can be positioned by Tribon Structure.
This is useful for elements like shock absorbers and bolts for example.
1.6.2.1 Pseudo Components

The second component type used in the Tribon Structure does not require a component data bank. They are called
pseudo components and all the dimensions are specified in the "component" name according to the syntax below.
Plates, holes in plates and bars can be created with pseudo components.
If three parameters are given for any bar component excluding the flat bar, the system uses the value of <s> also for <t>
If only two parameters are given for the same bar component, the system uses the value of <height> also for <width>.
To get on line help in Structure Design give #? on the component name prompt.
All the dimensions are specified in the "component" name according to the syntax.
17
1.6.2.2 True components versus Pseudo components
The advantage of using pseudo components is that the user can start building structures without having a component
data bank.
The disadvantage of not having a component data bank becomes obvious for example when extracting production
information. For example for the weight calculation steel density is always assumed. Further no material, buying or stock
information is connected to a pseudo component.
True components and pseudo components can be mixed in a structure object.
1.6.2.3 Production Information
This Split function is used to transfer a completed structure object to the production preparation environment. The plate
parts of the structure object are copied to the plate data bank (SB_PLDB), and the profiles to the profile data bank
(SBH_PROFDB). They can then be treated by the Hull Nesting applications.
General components are currently not treated. The plate parts get a name according to <object name>-<id>C and
the profile parts according to <object name>\<id>C where id is an internal unique number within the structure object.
1.6.3 Structure Object Types

The TRIBON Structure model object hierarchy can be expressed as:

 Module reference object

 Module object(s)

 Structure object(s)

 Part(s)

 Belonging part(s)
On top of the hierarchy is the module reference object that is created at the start of a project. The module reference
object name consists of the project name together with a fixed part specific for structure objects according to <project
name>::$MOD$.
The next level is the module object that is used to group the structure objects in any way chosen by the user. All module
objects are noted in the module reference object. The module object names are built up by a user given arbitrarily part
and the project name according to <project name>::<module name>.
Object Type Name Example

Module reference object <project>::$MOD$ TTP::$MOD$
Module object(s) < project >::<module> TTP::101
Structure object(s) <structure> FOUNDATION1
Part(s) -
Belonging part(s) -
Under the modules the structure objects reside, which are the entities handled in the Tribon Structure system against the
data bank in operations such as store, delete and input. Also the structure object names are user defined and arbitrarily.
The structure objects in turn contain parts such as profiles, plates and general components. In some cases also parts
have subordinate parts for example a plate with holes.
The structure objects and parts are handled in the Tribon Structure system. However a module reference object and at
least one module object must exist within the current project.
18
1.7 Equipment import utility
The normal method of creating equipment in Tribon M3 is via the interactive methods, either in tbequip or in the
graphical applications. An alternative is to create an input file, in csv format, containing the equipment details and to
import the equipment using the function Import in tbequip.
1.7.1 Template for importing equipments

In the outman folder you will find a template for the import: Equipment Import Template.xls

 Open the file using Excel: -
 Mandatory inputs are coloured blue. Note also that the

modules referenced must exist (see next section)
 Note that the Action can be CREATE, REPLACE, or

DELETE

 Select save as (*.csv): -
19
1.7.2 Running the import  Open drawing EQUIP_IMPORT and insert the models

 Then in tbequip, select File > Import…

 You should see that the 6 equipments have been imported to the equipment databank: -
20
1.8 Data Extraction introduction
Data in the Tribon data banks are accessible via the Data Extraction facilities. It is possible to retrieve specific
information from one or several Tribon objects by specifying the type and name of the model object and the wanted item
within the object
1.8.1 Running Data Extraction
Using a command prompt window from

Tribon > M3 > Bin > sx700, it is
possible to ask for specific terms and
get the answer at the terminal
 See Tribon M3 Documentation, Tribon M3 Developers Toolkit, Data Extraction for full details of how
to run Data Extraction and the options available
1.8.2 Using sx711

This is the normal method for executing data extraction. In Tribon M3 there is also the possibility to use sx711, which
can be found in Tribon M3 > Documentation > SX711.zip
21
SX711 is a sample MFC application that illustrates the usage of the Data Extraction component from C++.
22
Chapter 2
2 Creation of Modules and Systems
2.1 Description
Prior to outfit modelling, the system requires that the following objects are created in the outfitting model databanks: -

 Module

 System (valid only for Pipe)
Each model object must belong to a project, module (and system), therefore these ‘high-level’ objects must be set up
prior to modelling. In Tribon M3. the creation of these objects is done via the Design Manager application. The program
is started as below: -

 Select New from the menu

 Open up the TTP project and select sub-project outman

 Open up the project node TTP so as the Design and Production nodes appear as above
2.2 Creating a new Module

 Open up the Design node as above, then right-click the cursor on the
Outfitting modules node and choose New Module

 Key-in ‘200’ and select OK. The module ‘200’ is created in all the
relevant Outfitting databanks (pipe, ventilation, cable, structure,
equipment).

 Outfitting objects may now be modelled belonging to this module.
23
2.3 Creating a new Pipe System

 Select the node Pipe systems and right-click. Choose New System
 See the Pipe Designer Training Guide for details of the

‘Surface Preparation Code’.
 In this case the surface preparation code 20 will become default for
the whole HW system (all pipes)
 Note if want to changethe surface preperation code or the system

description needs to be modiifed, right click on the system and select
Properties the following dialogue box will appear, Select Edit.

 Key-in the values as above and select OK

 The system HW is created and is now available for modelling pipes.
2.4 Deleting Modules and Systems

To delete a module or a pipe system simply right-click on it and choose Delete.
Note that if objects have been modelled belonging to the module or system then
the system will not allow you to delete it: -
In this case, the model objects would first have to be moved to a different
system or deleted from the databank before it is possible to delete the system
object.
24
Chapter 3
3 Piping Machine Objects
The machine objects describe capacities, critical measures and other characteristics for certain machines in the pipe
manufacturing shop
The three types of machine object are: -

 Bending machine(s) $MACH$BEND  The objects are stored in the component

 Automatic flange welder $MACH$WELD databank SBE_GENCMPDB

 Boss extrusion machine $MACH$BOSS
3.1 Pipe component Bending code

The relevant pipe (tubing) components should be created with an BENDING CODE=1 (automatic bending allowed): -
Bending Code
1 = automatic bending allowed
2 = bending not allowed
3.=manual bending can be made
25
3.2 Bending Machine
The system stores a model of the customers bending machine(s). The model contains a simple
3D representation of the bending machine and any surrounding obstructions using planes, as
well as dimensional values required for the successful automatic bending of each relevant pipe
component.
G = Shortest straight pipe between two bends (grip

length)
L1 = Minimum length of straight pipe to the first bend of

a pipe without flange
L2 = Minimum length of straight pipe to the last bend of

a pipe with flange. If the possibility to bend a pipe with a flange does
not exist in the current machine the value 100 000 should be given
To add or Update
To Delete Bending Bending Data
Data
Current Bending
Machine Object (there
can be 100)
To List Bending
Data
26
The system stores 6 main types of Bending Data: -

 Bending Dimension Data

 Bending Collision Planes

 Turning Collision Planes

 Stretch Factors

 Springback data

 Maximum Pipe Lengths
3.2.1 Bending Dimension Data

Dimension data is data associated with each pipe component and its relevant dimensions. The user is prompted for the
following: -

 Machine No

 Outer Diameter

 Wall Thickness (optional)

 G measure

 L1 measure
 The Bending Machine
 L2 measure
 Number (each object
 FC measure (customer specific)
can have up to 10)

 Bending Radius
Enter the data as below: -
Click Finish to save the data
To enter further dimension data simply repeat

the process with a new pipe size.
27
3.2.2 Deleting Bending Dimension Data

 Click on Delete

 Click Next

 Key in the Dy and Wall Thickness (optional)

 Click Finish
3.2.3 Bending Machine Data

Bending Machine data is data associated with the bending machine itself such as: -

 Collision Planes

 Maximum length of pipe the machine can bend

 Stretch factors
28
3.2.3.1 Collision Planes General  Open drawing TURNING_COLL1
Collision planes are defined representing the geometry of the machine and any necessary surrounding obstructions
(such as the shop floor). There are two main categories: -

 Bending Collision Planes – planes that can be struck by the pipe during a bending operation

 Turning Collision Planes – planes that can be struck by the pipe during a rotating operation
Turn
 Note that some planes can be struck during
bending or turning. These planes have to be
defined twice; once as a bending plane, and
once again as a turning plane
The plane of the floor can be struck when the pipe is

being turned in the bending machine
Turn
Bend
This plane of the wall can be struck during turning operations (left), and during bending operations (right).
 Open drawings TURNING_COLL2 and BENDING_COLL1 respectively
29
3.2.3.2 Bending Collision plane
The position of the planes are measured from an origin point (where X=0, Y=0, Z=0. This origin is always considered to
be the centre of the bending die. The co-ordinate system is as shown below.
 Bending collision planes can only lie at normal to the X or Y axis The GUI will limit you to these choices
3.2.3.3 Define Bending Collision plane
Return to the Add/Update screen.

 Click in the Bending Collision plane box

 Fill in the values as to the left

 Click Finish to save the data
As stated on the previous page, this plane also can be considered a turning plane.
30
3.2.3.4 Turning Collision plane
The workshop floor is an example of a plane that can only be hit during a turning operation. Therefore it need only be
defined once.
 Turning collision planes can only lie at normal to the X or Z axis The GUI will limit you to these choices
3.2.3.5 Define Turning Collision plane

 Click in the Turning Collision Plane box

 Enter data as on the left


 As before repeat the process for further Turning Collision Planes
3.2.4 Bending machine planes, Worked example

There now follows an example of how typically planes may be defined for a bending machine and surrounding workshop
area.
In this example, the planes on the machine itself

that are considered are as below: -

 Top of machine

 Side of machine

 Front of machine
31
 Open drawing PIPESHOP_PLANES
3000 2000 5000 3000
Z Z
125
3000
X Y
1200
1075
3400 2000 2600
2
1 5
3000
400 400
400
Y
Z
X X 3 7
4 Y
1600
8000
800
= BENDING PLANE
6
= TURNING PLANE
5000
BENDING PLANE:
Plane Xmin Xmax Ymin Ymax Zmin Zmax COMMENT

1 2000 2000 -5000 3000 -1200 1800 WALL X
2 -3000 2000 3000 3000 -1200 1800 WALL Y
3 400 400 -1200 -125 -1600 400 SIDE OF MC
4 -400 400 400 400 -1200 -125 FRONT OF MC
TURNING PLANE:
Plane Xmin Xmax Ymin Ymax Zmin Zmax COMMENT

5 2000 2000 -1200 1800 -5000 3000 WALL X
6 -3000 2000 -5000 3000 -1200 -1200 FLOOR
7 400 400 -1600 400 -1200 -125 SIDE OF MC
8 -400 400 -1600 400 -125 -125 TOP OF MC
32
3.2.4.1 Define max feed length of pipe
This defines the maximum feed allowed in one operation for each bending machine.

3.2.4.2 Define stretch factors

Definition - A coefficient defining the stretching of pipe material that occurs during the bending process. Two stretch
factors are given; one constant (C), and one proportional (P). The values for these factors can be altered slightly to give
the desired results. The following formula defines the stretching: -
AL = (C-P*ALPHA/2)*BL
AL is arc length after bending.

BL is arc length before bending.
ALPHA is the bending angle.

 Click in the Stretch Factor box

 Enter data as above

33
3.2.4.3 Setting how Stretch is calculated
In the modelling default file SBP_MODEL_DEF the variable STRETCH=<options> is used to control the method for
determining how the stretch value is calculated. This also influences how the Machine objects set-up program responds.
The options are: -
STRETCH=NOSTRETCH C=1.0, P=0.0

STRETCH=SYSTEM_DEFAULTS C=0.977, P=0.01528
STRETCH=MACHINE C and P according to each bending machine (default in this project)
STRETCH=MATERIAL C and P are Outer Diameter, Wall Thickness and Material Code dependant.

 Example – set the value STRETCH=MATERIAL in the modelling default file.

 You will see that when using option Springback Data that the stretch factors are now asked for, on each pipe size
 Material code 1 = steel
34
3.2.4.4 Delete bending machine data

 Choose Delete

 Click Next

 Type in the Plane that
you wish to delete
(To see how to identify the

correct plane, see next
section)

 Click Finish
 This function deletes both bending collision planes and turning collision planes. The plane numbers are changed
for the remaining planes when an existing plane is deleted.
35
3.2.5 Spring-back data
Spring-back data is used to control the accuracy of bending. When a pipe is bent it is normal that pipe springs back to
something less than the actual bend. E.g. when an actual bend of 90 degrees is made the pipe may spring back to (say)
89 degrees. Therefore to achieve a resultant bend of 90 degrees you may have to make an actual bend of 91 degrees
on the machine. The spring-back is adjusted by allowing the user to key in two values: -

 The resultant angle at 20 degrees

 The resultant angle at 120 degrees
The system can then determine the ‘over-bend’ that is required for any bend angle based on these values.
3.2.5.1 Add / Update spring-back data


 Enter data for the pipe size
 Material code 1 = steel
3.2.5.2 Delete spring-back dat


 Return to the Delete window

 Enter data for pipe size
36
3.2.6 Delete Bending Machine
This function deletes a bending machine. All data associated with the particular machine is removed from the Bending
machine object (collision planes, stretch factors, max feed length and dimension data).

 Click on Bending Machine to delete the bending machine
3.2.7 Making Lists

It is possible to list any of the bending data using this function. The resulting lists are stored in the SB_SHIPPRINT
directory (lst) and have the following name formats: -
MacObj_<type>.lst
Where <type> = ‘dim’, ‘bend’, ‘weld’ etc depending on the

type of list.

 Return to previous window and select List then Next >
Click for the type of list

you want
Use this button to browse

to a new location for the
lists
Use this button to view

the list (once it has been
made)
Use Finish to create the

list
37
3.2.8 Multiple Bending Machine Objects
This feature makes it possible to define up to 100 bending objects, each one with a maximum of 10 (ten) bending
machines, numbered 1 to 10. Thus, the total number of bending machines possible to define is 1000.
If the BMOBJECT_ID keyword is present in the SBP_MODEL_DEF default file there will be an option to enable work on
a specific bending machine object. There will always be an ‘active' bending machine object. The bending machine
number will be picked up from the object. The object can be the general-purpose bending machine object
($MACH$BEND, equivalent to BMOBJECT_ID=0) or another object specified by the user.
Pipe tube material with the same data (Outer Diameter and Wall Thickness) can be placed in different bending machine
objects.
To disable use of the multiple bending machine objects the keyword BMOBJECT_ID has to be removed from the
SBP_MODEL_DEF default file.
3.3 Flange Welding Machine
The system stores a model of the flange-welding

machine. The user can input the following values: -

 Minimum and maximum DY values

 Minimum and maximum lengths of pipe

 Flange Group names (Components)
MAX and MIN L
Flange Groups
MAX & MIN DY

 Select Add/Update

 Click Next
38
3.3.1 Min/Max values
3.3.2 Add flange group
3.3.3 Delete flange group
39
3.3.4 List welding machine data

 Return to previous window as below
The Options are the

same as the Bending
Machine lists

 Example of Welding machine list -
40
3.4 Boss extrusion machine
3.4.1 Boss Machine dimension data



 Click Next
41
3.4.2 Boss Machine distance data
This page contains function to add or update boss
distance data of the pipe.
The boss distance is the distance from the sealing

surface of the branch piece to the centre line of the
main pipe. It is not used for boss made from pipe
material.
Note that boss distance data should be used with

great care as the distance value will be applied for all
bosses with given dy, irrespective of the component
type.
Boss Dy Boss diameter.

Main Pipe Dy Main pipe diameter.
New Distance Value Boss distance value, valid for specified combination of pipe diameter and boss diameter


 Click Next

 Enter values as below and select Finish
3.4.3 Delete machine dimension data
42
3.4.4 List machine dimension data
The Options are the

same as the Bending
Machine lists

 Example of Boss machine extrusion table -
3.5 Machine Object Set-up in TTP Project

 See Appendix 1 of this guide for full examples of how the machine objects for the main TTP project
are set-up. If there is time then reproduce this set-up in the outman sub-project.
43
44
Chapter 4
4 Standard Handling
This chapter deals with some of the most common methods for handling standards within the TRIBON outfitting
systems. It is normal that the customer will, over time, develop a comprehensive library of standards for day-to-day use
in the system.
In this chapter we will discuss and explain some concepts regarding: -

 Symbols

 Drawing Forms

 Standard Details

 Standard Units

 Standard Structures

 Component Naming conventions
Although this guide is aimed at Outfitting users, many of these concepts are also applicable in Hull.
4.1 Symbols
In many applications a considerable part of the information on drawings and diagrams consists of schematic pictures of
different items. These are referred to as symbols. Symbols can be created once and then easily placed on drawings.
WW-1
WW-2
WW-31
I1
H I2
TI
P1
10 L
11
WW-42
WW-5 WW-5 WW-8

V3 V4
WW-3 WW-7
V8
WW-43 WW-13
WW-6
WW-4
V1 V2
WW-28 WW-25
WW-10
WW-9
V11
WW-17
WW-14
WW-16
WW-22
V5 V6
V7 WW-26 WW-27
WW-39
WW-21
WW-15
I3 LI
WW-11
WW-19 WW-18
WW-38
WW-23
WW-24
WW-20
V12
WW-29
V13
WW-40
WW-34
WW-33
WW-37
WW-36
V9
WW-41
V10
WW9003 WW9004 WW9005 WW9001
WW9002 WW9006
WW-32
WW-35
WW-30
SYSTEM: WW
REV. DATE REF. DESC
TITLE
From SERVO System SHT. DRAWN BY
Hydraulic System for
Windlass & Mooring OF
Winches DATE DEPT. SIZE SCALE
To SERVO System
SHIP NO. CHKD. APPR.
BARREL TO BE PLACED IN
HYDRAULIC ROOM FOR WINCHES solutions DWG. NAME
AT DECK NO 4 Training Department
email: training@tribon.com PIPEDES.EX2
Related symbols are grouped together in a symbol font. Each font is identified by a unique font number (1-999). Each
symbol within a certain font is identified by a unique symbol number (1-32767). There are a number of symbol fonts
delivered with TRIBON that are used by the system. These can be used in drawings but must not be modified. A list of
system defined reserved symbol fonts can be found in section 1.5 of this chapter.
Drafting handles the creation and maintenance of individual symbols and the symbol font utility program – sb021
handles the equivalent functions for symbol fonts.
45
4.1.1 Symbol Creation
It is usual to create the symbol in an area of 511mm x 511mm at a scale of 1:1. For convenience there is a drawing form
provided in the training project called NEWSYMBOL shown below: -
511
 A similar form is automatically created when an

CREATE SYMBOL existing symbol is fetched for updating.
FORM
CONNECTION TYPES
1=pipe connection
2=electric connection  Tip - the easiest way to create a new symbol is to

3=ventilation connection
update an existing symbol, modify it, and save as
a new symbol.
CONNECTION CODES
0 NO RULE CONNECTION
511
1 PARALLEL AND AT A DEFAULT

DISTANCE FROM THE GEOMETRY.
The first thing is to decide where to store the symbol. If
2 PARALLEL TO THE GEOMETRY
a symbol has been fetched for update, the original font
3 AT THE GEOMETRY
4 AT THE CLOSEST END POINT and symbol number will be proposed by the system. If
OF THE GEOMETRY.
5 PARALLEL AND AT THE CLOSEST

this proposal is rejected by the user, or if the symbol
has been created from scratch, the font and symbol
END POINT OF THE GEOMETRY.
6 PARALLEL AND AT THE GEOMETRY
number must be explicitly given by the user. Note that

solutions
the given symbol font must exist and that the symbol
Training Department
email: training@tribon.com
number must not exceed the current limit for this font.
(0,0)
 the limit can be changed, using the Symbol Font Utility program sb021
The normal Insert functions are used to create the symbol (line, arc etc). Hatching for example can also be input to the
symbol as can 2D primitives, existing symbols and so on.
 Note that any drawing structure (sub-picture

levels etc) will be lost when the geometry is
converted to a symbol. Also any colours used will
be lost.
 Note if the shape is too complicated, the user will

receive an error message and the creation will be
aborted. The size of the symbol can be reduced
by chaining geometry together.
4.1.2 Symbol Connections

It is normal to add connection points to the symbol. This is requested when the symbol is to be saved. Connections
already belonging to an existing symbol will be highlighted and the system will ask the user if it is OK to keep these
connections. It is also possible to delete old connections. The updating of connections is terminated by Operation
Complete.
New connections may be added in true interaction. The system keeps track of the next free connection number and
allows the user to supply all necessary information, namely: -

 the connection point

 the connection vector

 the connection code
Operation Complete terminates the adding of new connections.
46
4.1.3 Text Positions
The text positions are treated in the same was as the connections, except when supplying necessary information,
namely: -

 the text position

 the text vector

 the text position code

 the maximum height and width
Operation Complete terminates the updating as well as the adding of new text positions.
4.1.4 Automatic Positioning of a Symbol

A symbol can be positioned on any geometry (line, arc or contour). The following criteria have to be fulfilled in this case:

 Automatic positioning must be on.

 The symbol must have been defined with connection point no. 1.

 The connection code is interpreted by the system to give the following results: -
0. No adjust
1. Parallel and at a default distance from the geometry
2. Parallel to the geometry
3. At the geometry
4. At the closest end point of the geometry
5. Parallel and at the closest end point of the geometry
6. Parallel to and at the geometry
The distance between the closest geometry and the given position (connection point no 1) must be less than the default
value (SYMB_AUT_DIST in the default file).
 Connection point 1 is the main connection and will determine how the symbol is positioned
 Note that the Connection numbers, vectors and connection codes

are displayed in the Drafting Message Window when updating an
existing connection on a symbol. Try updating some existing symbols
to see how they are constructed.
4.1.5 Removing Symbols from a Symbol Font

To delete a symbol - select Tools > Symbol > Remove in Drafting. When removing a symbol, the symbol font number
is requested and the symbol to delete is selected from the symbol font menu displayed on the screen. You need to be
careful here - when a symbol is used in a drawing, only the reference to the symbol font and the specific symbol is
stored. By deleting a symbol, old drawings may be affected.
4.1.6 sb021 - Symbol Font Utility Program

The program is used to maintain symbol fonts and performs the following tasks: -

 Viewing and updating of font header characteristics

 Creation of new symbol fonts

 Copying of symbol fonts

 Deletion of symbol fonts
The program interacts with the user via the Main Activity form and its sub forms which are:-

 the Font Head Viewer form

 the Font Copy Utility form

 the Font Delete Utility form
 For full details of the Symbol Font Utility Program see the Drafting User Guide, Utilities
47
4.1.7 Font Naming and Location
A symbol font is identified by a number between 1 and 999.The corresponding font file is named d012sy<xxx>.sbd
where xxx stands for the identification. The directory where the font files reside is initially project dependant
(SBB_SYMBDIR) but can be changed to whatever desired inside the program.
4.1.8 The Font Head Viewer Form

This form is used to view, update or create symbol fonts. The source symbol font is specified in the 'Directory' and
'Identification' fields respectively. The font header characteristics are shown in the section labelled 'Characteristics' and
contains the following: -
 A ‘slot’ is a space in the symbol font which can be occupied by a symbol

 The total number of slots available

 The highest slot number in use
 
 The used slot size, in words
 The size of a slot, in words (complexity)

 The symbol origin (reference point)

 The revision number of the font (not used at present, always=1)

 The text code (not used, always =0)
4.1.9 Worked Example, Symbol Creation


 Run the Symbol Font Utility program sb021

 First we will create a new symbol font into which new
symbols may be stored. We will create a new symbol
font 33.

 Choose View from the Main activities menu

 The Symbol Font Head Viewer form appears as
below

 Key in ‘999’ in the identification box

 Select Create

 The new (empty) symbol font 99 is created on the
directory assigned to the variable SBB_SYMBDIR

 Next we will create a typical symbol and store it in the
new font

 Start up Drafting. Open a new drawing and use
drawing form NEWSYMBOL
48

 Create geometry as below using lines, arcs and hatching

 Select Tools > Symbol > Save..

 The system then asks the user to define connection point 1; first the location, then the direction vector and then
the connection code

 Select Intersection from the 2D point toolbar to locate the connection point

 Indicate intersection …Choose Offset Current … Key in ’50 R’ for the vector

 Then key in connection code ‘6’
(Parallel to and at the geometry).

 Complete the connection points as shown left

 Choose Operation Complete when asked for Text position
point (not relevant for this type of symbol)
49

 The symbol is now stored and can
be accessed in Drafting with Insert
> Symbol

 The Connection Code 6 was defined on the first connection. This
means that the symbol can snap to the nearest point on existing
geometry (provided Auto Positioning for symbols is turned on). The
connection vector will also be parallel to the geometry

 This type of symbol might be used to represent a type of valve

 This is a description of the
symbol used by the system
when creating position
numbers.
4.1.10 Symbol font Migration Programs

To move a symbol font file from hardware platform A to platform B: -

 Convert the binary file to stream format, using SB022, on platform A.

 Transfer the stream file to platform B.

 Convert the stream file back to binary format, using SB023, on platform B. A binary file has the extension 'sbd' while
the stream file has the extension 'port'.
 See the Drafting User Guide, Utilities for more details
50
4.1.11 Symbol Fonts Reserved by the System
The symbols fonts reserved by the system are all located in the range 1-99, but there are also user fonts located in this
area. In the range 100-999 only user fonts are allowed.
FontDescription
1 User font: Arbrit FontDescription
2 System and user font: Nesting 51 System font: Not in use
3 System font: Facit printer text font 0 52 System font: Not in use
4 System font: Facit printer symbol font 53 System font: Not in use
5 User font: SDS 54 System font: Not in use
6 System font: 55 System font: Hull modelling
7 System font: Diagram 56 System font: Not in use
8 System and user font: SDS 57 System font: Not in use
9 User font: PSE 58 System font: Not in use
10 System font: PSE 59 System font: Not in use
11 User font: Diagram 60 System font: Not in use
21 System font: SBD 70 System font: Not in use
22 System font: SBD 71 User font: SBD
23 System font: SBD, system menu font 72 User font: SBD
24 System font: Not in use 73 User font: SBD
29 System font: Cable diagram 78 User font: SBD
30 System and user font: Cable diagram 79 User font: SBD
31 System font: Tablet menu symbols 80 System font: SBD, IGES font 1 symbols
32 User font: General diagram 81 System font: SBD, IGES font 1001 symbols
33 User font: General diagram 82 System font: SBD, IGES font 1002 symbols
34 User font: General diagram 83 System font: SBA, Accommodation menu symbols
35 User font: General diagram 84 System font: Not in use
37 System font: Not in use 86 System font: Not in use
41 System font: Alternative font for Note 90 System font: HULL, Bevel symbols
and Position Number symbols 91 System font: HULL, Interactive bracket symbols
42 System font: Not in use 92 System font: HULL, Excess symbols
43 System font: Not in use 93 System font: HULL, End cut symbols
50 System font: Not in use
51
4.2 Drawing Forms
There are two kinds of drawing forms used in TRIBON:

 "Normal" forms

 Modelling forms
4.2.1 Normal Forms

Normal drawing forms are used as a background for a drawing and can contain e.g. a frame, some fixed text and some
dynamic text. The dynamic text is created by using rules, where e.g. the rule $2000 will automatically be replaced by the
drawing name.
Field Rule number In the File menu, click Properties. The function uses a SBFS
Drawing no $2000 form dialog when interacting with the user. This form contains
Drawing no in top left corner $2113 a number of fields corresponding to certain information
connected to the drawing e.g. drawing name, date, author,
Title $2101 scale etc. Each field in the SBFS form has a specific rule
Title, another language $2114 number connected to it. The information in such a field will be
Title, second row $2115 inserted in the drawing, according the corresponding rule
Drawn by $2102 number in the drawing form (if it exists).
Dep. $2103 When this function is entered, it tries to read the information
Date $2104 (if there is any) in the current drawing and when the SBFS
Tsc $2105 form appears this info will be shown in the appropriate fields.
If no information is found for a certain field, this field will be
Secy cl. $2107
empty.
Scale $2108
Size $2109 The function can handle three slightly different SBFS forms
Doc. Type $2110 as described below. The SBFS form to use is controlled by
the Default Keyword UPDATE_DRAW_INFO_FORM. The
Tot.sheet.no $2111
fields on the left are taken from the form SBFS #1.
Rev. $2112
Prj.c $2106 The last eight rule numbers (@600 - @607) are preceded by
Check $2116 the @ sign. These are rule numbers of type table. There can
be a total of ten rows for each such rule.
Appr. $2117
Appr. $2118 The procedure is to create a drawing framework according to
Signature $2119 the size of drawing form you wish to create. It is
Rev. @600 recommended to work at a scale of 1:1. The origin (point
where U=0 & V=0) should be at the bottom left hand corner
D @601 of the form.
P @602
Date @603 The easiest way to create a new drawing form is to take an
existing form and modify it. You can also start from scratch by
Rev. reason @604
opening a new drawing (without a drawing form) and
Zone ref @605 constructing the geometry of the form something like as
Apprv. @606 below: -
Desc. of rev. @607
52
 You can also insert sub-pictures to the form.
One example of this might be adding the
company logo in the title block. When the
drawing is converted to a drawing form any
sub-picture structure is lost.

 Use the Insert > Text function to add the rule text as shown below: -

 Select Tools > Drawing form > Save…

 The system will ask for the name of the reference form. A reference form is not needed by the system, it just makes
things easier for the user. If a reference form has been supplied, the system will ask if the rule parameters in the
form you are about to save should be defined automatically, via the reference form. In this case we will define from
scratch by choosing OK

 The system will step through each rule one-at-a-time, highlighting the current rule, and asking for the following
information: -
 Text Adjustment
 Max number of characters
 Max number of lines (applicable for table rules only)
 Interline space factor (applicable for table rules only)
53

 In this form always use 1 Flushed left for the Text Adjustment. The text will start at the rule text at the ‘$’ symbol
and then the text contents will appear to the right. The height of the final text will be the same as that of the rule text.

 When all of the rule parameters have been defined, the system will allow you to update any of the existing rules by
picking from the defined rules list: -

 Select OK. The form is stored on the database assigned to SBD_STD

 Open a new drawing and use the drawing form A3_TEST

 Select File > Properties and fill in the form as below: -
54

 Select OK and see the values appear on the drawing as below: -
 This type of drawing form is used throughout the system, and although many of them may seem
much more complex than this example, they are simply “more of the same”. Some examples are;
pipe sketches, assembly drawings, nesting drawings. For details of the rules available for each case
see the relevant User Guide for the application
55
4.2.1.1 Pipe Sketch Form  Open the drawing PIPE_SKETCH_FORM
One of the most commonly changed forms is the pipe sketch form. This is really just a more complex version of the
previous drawing form. The drawings that use this form are created by the pipe splitting program.
A sample for the rule texts available for the pipe splitting program is shown below.
:
Management data:
sketch name $100

project $101
block name $102
:
Automatic welding:
position 1 @300
position 2 @301
rotation angle @302
:
 See the “Pipe Users Guide, Background Jobs, Routines for creating Pipe Sketch Forms” for a full
listing of the available rule texts
Add the text as shown below and choose Tools > Drawing Form > Save…
The form is based on the main pipe sketch form in this project PSKETCHFORM_TBS

 Then update the rules 100, 300, 301, 302 as below.
56

 When finished select OK and Operation complete

 Try splitting some pipes using this form
57
4.2.2 Modelling Forms
Modelling drawing forms are forms that include a layout of projections that can be used in modelling applications, one
example of these is the CV4 form that is included in the TTP training environment: -
4.2.2.1 Create Modelling Drawing Form

Start a new drawing without a drawing form and construct the geometry of the form as below. The bottom left hand
corner should be at u-0, v=0. Use “Key-in” to ensure this is the case.

 Once the geometry is complete, use the function Tools
> Drawing form > Save

 Key in a name for the form and press OK

 The system then prompts for the view definitions. Choose Intersection.

 Then indicate the bottom left corner (1) followed by the top right corner
(2) of the lower left area.
58

 Choose the projection and Key in a name for the view

 Continue this process until each of the views is defined as
shown on the left

 Then select (Operation Complete)

 Check the result by starting a new drawing using this form
and Insert model as on the right
4.2.2.2 Updating a Modelling Drawing Form

To update the form select Tools > Drawing form > Open and choose the form you wish to update.
You may wish to add symbols to each view describing the projections.
When complete use Tools > Drawing Form > Save to save the
form as before
During this operation you will be asked whether you wish to keep
the projections and/or whether you require additional views.
59
4.3 Sb029 Print symbol font drawing(s)
This program sb029 is used to create drawing(s) of symbols; the symbol drawing will be drawn on a predefined drawing
form, which has 12 symbol fonts per page. The main purpose of this utility is to create a symbol font book to stop the
duplication of symbols.

 From the Tribon > M3 > Bin directory double click on the sb029.exe file

 The following screen will appear

 Enter 1 to create drawing(s) of symbols

 Enter the Font number required for this example we will use font 11

 Enter the First symbol number in this case we will enter 1

 Enter the Last symbol number in this case we will enter 12 (the symbol font drawing form only allows 12 symbols
per page)

 The symbol number from 1 to 12 inclusive have been found and a drawing SB029_DWG1 has been created

 Enter 0 to Exit program
60
The symbol font drawing can now be opened
 Open drawing STD_SUBPICTURE
4.4 Create a standard hatch pattern  Open drawing HATCH_PATTERN

Normally, a hatch pattern consists of lines at certain angles and distances. These patterns are supported by the system
and angles and distances can be changed in the default file. User-defined hatch patterns can, however also be created
and used. This is done by the 2D drafting functions in the system. Before it is saved, it must belong to the same level 3
subpicture. The function. A standard book is used for this purpose. When a pattern shall be updated, the pattern is
added to the current drawing as a level 3 subpicture with the function Tools-Insert Std hatch pattern.

 Select Subpicture > Save as Std Hatch Pattern
from the Tools menu.

 Indicate the Subpicture and then select Yes from the dialogue box
61

 The Save in Hatch pattern Book dialogue box appears, select OK

 A new dialogue box now appears; select a detail description that requires replacing with the new hatch pattern or a
detail that is not yet defined, then select OK

 Key in the description for the new hatch pattern, and then select OK

 Select (Operation complete) to exit from function. The pattern can then be used for hatching: -

 Try drawing some other types of hatch pattern and using them on the closed contour.
62
4.5 Standard Details
Any sub-picture can be stored as a standard detail in the standards databank, SB_STD. This can later be retrieved and
re-used in other drawings.
Standard Details are stored in a Standard Book where (in this example) ‘2’ represents the page number and associated
with the page is a description: ‘INSTRUMENT MASTS’. The creation and maintenance of the individual sub-pictures are
handled by the Drafting application. The program SB028 handles the maintenance of the standard books.
The example on the left is a standard detail

representing a VLCC radar mast. It can be found in
Drafting using the function Insert > Standard Detail
and choosing 2 Instrument Masts
4.5.1 sb028 - Handle Standard Objects

The program sb028 is used to administrate the standard books in TRIBON: -
4.5.1.1 TRIBON Environment Variables

SBD_STD Standard data bank containing the standard books.
SBLIST1 The name of the list file for page descriptions. Default name is sb028.lst.
4.5.1.2 Description of the Different Tasks

The book to handle is selected from the main menu. To quit, select Exit program. Once the book is selected, the specific
task to perform is selected from the task menu. To return to the main menu, select Return to main menu. Below, the
different tasks are described. If not otherwise stated, <CR> means go back one step in the sequence of user input.
63
4.5.1.3 List All Page Descriptions
This function will add to the list file all page descriptions defined in the current book. The same information will also be
displayed on the screen.
4.5.1.4 Move Whole Page

This function moves a whole page within the current book. User supplies the source page, followed by the target page.
4.5.1.5 Move Standard

This function moves a standard from one page to another within the current book.
First, the source page and standard within the page are supplied (the numbers of existing standards within the page are
listed). Secondly, the target page and standard within that page are supplied. Overwriting is not allowed, so the target
standard must not exist (the numbers of non-existing standards within the page are listed).
4.5.1.6 Change Page Description

This function allows the user to change the description of a certain page. By giving the page number, the old description
is displayed, whereafter the new description is supplied by user.
NOTE! <CR> means step back, while one or more spaces makes the description empty.
64
4.5.1.7 Change Standard Description
This function allows the user to change the description of a certain standard. By giving the page number, the existing
standards within that page are listed. By giving the desired standard number, the old description is displayed, then the
new description is supplied by user.
NOTE! <CR> means step back, while one or more spaces makes the description empty.
4.5.2 Worked Example, Save Standard Detail  Open drawing STD_SUBPICTURE

 Select Tools > Subpicture > Save as Std Detail (Indicate the Mast and choose level 2)
65

 Select INSTRUMENT MASTS 
 Select 1

 The Sub-picture is now stored as a Standard Detail named ‘RADAR MAST’

 The standard sub-picture can be inserted into
arrangement drawings in the early design phase

 The scale of the subpicture will vary with the scale of the
level 1 sub-picture (owner).
 Sub-pictures can also be used to represent

components as an alternative to displaying the
3D volume. See the M3 Outfit Drafting training
guide.
66
4.6 Standard Units
A Standard Unit, as it is referred to here, is a collection of Model Objects which together may represent a standard
assembly that the shipyard may use many times across multiple projects.
It can, for example, be comprised of some equipment, pipes and

some supporting framework. The concept here is that the
production info is created once and then ‘looked up’ each time
the unit is required.
The Create Unit function converts the original collection of model

objects into a single (un-placed) volume. The volume may then
placed in the ship model either as equipment or as a placed
volume as and when required.
If placed as equipment then the following info can be lodged in

the component: -

 Material Number

 Weight

 Standard ID

 Connection points e.t.c.
4.6.1 Saving a Unit  Open drawing STD_UNIT

 Select Tools > Volume > Create Unit

 Key-in a name for the unit – ‘WINCH_MODULE’

 Indicate the sub-picture and choose level 1: -
 Level 2 can also be used here to collect individual objects

 Select Operation Complete – the system calculates the
combined weight of the selected objects.

 The unit is stored on the db assigned to SBD_VOLUME. It
can now be used to represent a component (equipment)
or placed as a volume.
67
4.7 Standard Structures
Any structure that is re-used across multiple projects or many times on one project can be stored as a Standard
Structure.
4.7.1 Environment variables.

SBF_DB_FSTRU Structure data bank.
SBF_DB_FSTD Standard Structure data bank.
4.7.2 Default parameters in SBD_DEF1.

STRUCT_KEEP_INSERT_OBJ = YES or NO
This keyword controls whether the original inserted structure object should be deleted or
not. If the original inserted structure has a standard reference it cannot be deleted.
STRUCT_KEEP_STAND_REF = YES or NO
A new Structure created from a Standard Structure could keep a reference to the
corresponding Standard Structure. This keyword controls if the reference should be kept or
not.
By using the STANDARD function it is possible to create a standard structure from a structure object in the current
model. The structure is actually copied to the Standard Structure Data Bank (SBF_DB_FSTD). Inversely a standard
structure can be copied to the current model. In both cases, the name and the module of the new structure is given by
the user. A new structure created from a standard structure could keep a reference to the corresponding standard
structure. This is controlled by the keyword STRUCT_KEEP_STAND_REF in the default file SBD_DEF1.
When a structure is copied to the Standard Structure Data Bank it will get this standard reference according to the same
keyword. As long as this reference exists, it cannot be modified, it can however be moved and copied, not mirrored. To
be able to modify it, the reference to the standard structure has to be removed.
Note that whenever replacing a structure object, its assembly references will be removed. Also referenced assemblies
will loose their belonging structure objects.
 See the Structure User Guide and the Structure Training Guide for full details of the concepts
regarding Standard Structure
4.8 Component Naming

In the 3D Drafting Training guide Chapter 7 there is some information regarding Component naming. Here we will try to
point out some of the practical considerations regarding the naming of components.
It is normal that the customer develops his or her own component database. The main reason for this is that the
component database contains: -

 The customers stock materials (tubing, cable trays, profiles etc)

 The customers directly purchased materials (equipment, fittings, valves etc)

 References to internal shipyard standards

 References to national and international standards

 Material numbers from the customers materials systems

 Information representing the customers production methods / standards e.t.c.
4.8.1 Delivered Components

Aveva Solutions Ltd deliver a component database in the Training environment (and also in the Template project).
Hopefully this contains examples of most types of components. It is a useful reference when the customer creates his
own database. The database contains a number of naming conventions. There is also a possibility to download
rd
components from www.tribon.com or from 3 party suppliers (see next chapter).
68
4.8.2 Structured Naming
There is no absolute need to arrive at a structured naming convention. The customer might choose for instance to name
all components for the material number or standard id or similar. However in these cases it is more difficult for the user
to find the right component without constantly searching the database. Also, as these fields are already contained in the
component information, why duplicate them?
The following naming structure is only one suggestion that allows the user to quickly narrow the search. After a while
you can expect the modellers to automatically key-in the correct component names without having to search the
database.
4.8.2.1 Building up the name

In normal use the interesting fields might be considered as: -
1. Main type of component; Pipe, Electrical etc

2. Sub-type of component; Valve, Cable etc
3. Type of Material; Steel, Plastic etc
4. Standard; Pressure, Power etc
5. Size of component; Nominal Diameter, Number of Cores, HxWxT etc
It is natural and desirable to organise components into Groups wherever possible.
Fields 1 to 4 will make up the Group Name and the Item Number is given by the Size. Therefore we might arrive at a
naming convention as below where the group name is divided up by ‘.’ and the item number is pre-fixed by ‘-‘: -
AA . BB . CC . DD – EE
Where: -
AA = Main class of component Group Name
BB = Sub Class of component
CC = Material type of Component
DD = Standard Item Number
EE = Size
4.8.2.2 Examples
PF.SO.01.16-100
Pipe Flange . Slip-on . Steel Ordinary . 16 Bar – 100 Nominal Diameter
PV.SDNRG.02.10-400
Pipe Valve . Screw Down Non-Return Globe . Cast Iron . 10 bar – 400 Nominal diameter
EL.CM.09.240-08
Electrical . Cable Multicore . Other Materials. 240 volts – 8 cores
SL.EQ.01.01-10012
Structure L Bar . Equal . Steel.Standard – 100x100x12
General components used for equipment could also be handled in a similar way: -
EP.CO. 01.500.450
Equipment Pump . Cargo oil . Steel . 500m3/hr – 450 DN
 Please note that this is not an attempt to arrive at the optimum naming solution. That solution will probably differ for
each customer depending on his or her requirements. We are merely trying to explain some of the fundamentals.
69
4.9 Components, use of text file
It’s possible to use a text file format to output and create components. This may be useful when sending data to sub-
contractors, or for making large-scale changes to existing components. The two methods are: -

 Components to file (su015)

 Components from file (su016)
Editor
su015
Text File
su016
SBE_GENCMPDB Tribon Component Repository

SB_DATA Name of input data file to interpret. If not assigned, the program will ask for the name of the file.
The file is an ordinary ASCII-file.
SBE_LIST1 Resulting list with information about the components. The default name of the file is COMP.LST
and it will be placed at current directory.
PRINTER0 Log file containing a list of the input file together with possible error messages. If not assigned,
the program will ask for the log file name. The file will be put in the current directory.
SBP_CMP_DATA_DEFDefault file for pipe component data. For further information see User Defined Nominal Diameter
Tables .
 This is the same method that Tribon.com uses when downloading components (see next Chapter)
4.9.1 Input File

The input file can contain individual component names or partial names and a wildcard (*) as in the example below.
70
4.9.2 Components to file (su015)
Two files are produced comp_result.lst, indicating whether the components have been handled, and comp_syntax.dat,
which contains the components in text form. This format is referred to as TIL (Tribon Interpretive Language).
Comp_result.lst
%COMP-I-MSG3, Component PFSODIN2501PN10-200 handled.

Comp_syntax.dat
COMPONENT, 'PFSODIN2501PN10','RF.PN10-200',2201,200
;
GENERAL
/KIND_OF_COMP = 'P'
/MAT_CODE = 1
/WEIGHT = 1.000000E-001
/MANUFACTURER = ( 1, 'Non Specific Suppl' )
/SUPPLIER = ( 1, 'SUPP' , 'Non Supplier Speci' )
/AQUISITION = ( 1, '0' )
/DESCR = ( 1, 'Slip-on flange - raised face, DIN 2501 PN10, nominal diameter 20' )
/DESCR = ( 1, '0' )
/TECH_SPECIFICATION = ( 1, 1, 'Flange acc. DIN 2501, PN10' )
;
PIPE_PROPERTY
/CONNECTION_CODE = 4
;
PIPE_CONNECTION
,1
/CONNECTION_VECTOR = ( 1,-1.000000E+000 )
/CONNECTION_VECTOR = ( 2,0.000000E+000 )
/CONNECTION_VECTOR = ( 3,0.000000E+000 )
/DIAMETER = 2.191000E+002
/FLANGE_CODE = 2
/TOTAL_LENGTH = 2.400000E+001
/TOTAL_OUTER_DIAMETER = 3.400000E+002
;
71
4.9.3 Components from file (su016)
Two files are produced: comp.lst indicating whether the import has worked, and comp.log which gives the details.
Comp.lst
%COMP-I-MSG6, Component PFSAPN10-200 has been stored

Comp.log
Aveva Solutions Ltd AB Components
Page 1
SU016 2004-04-29 16:58:43
1 COMPONENT, 'PFSAPN10','RF.PN10-200',2201,200
2 ;
3
4 GENERAL
5 /KIND_OF_COMP = 'P'
6 /MAT_CODE = 1
7 /WEIGHT = 1.000000E-001
8 /MANUFACTURER = ( 1, 'Non Specific Suppl' )
9 /SUPPLIER = ( 1, 'SUPP' , 'Non Supplier Speci' )
10 /AQUISITION = ( 1, '0' )
11 /DESCR = ( 1, 'Slip-on flange - raised face, DIN 2501 PN10, nominal diameter 20' )
12 /DESCR = ( 1, '0' )
13 /TECH_SPECIFICATION = ( 1, 1, 'Flange acc. DIN 2501, PN10' )
14 ;
15
16 PIPE_PROPERTY
17 /CONNECTION_CODE = 4
18 ;
19
20 PIPE_CONNECTION
21 ,1
22 /CONNECTION_VECTOR = ( 1,-1.000000E+000 )
23 /CONNECTION_VECTOR = ( 2,0.000000E+000 )
25 /DIAMETER = 2.191000E+002
72
26 /FLANGE_CODE = 2
27 /TOTAL_LENGTH = 2.400000E+001
28 /TOTAL_OUTER_DIAMETER = 3.400000E+002
29 ;
30
31 PIPE_CONNECTION
32 ,2
33 /BH_CIRCLE_DIAMETER = 2.950000E+002
34 /BH_DIAMETER = 2.200000E+001
35 /BH_LENGTH = 2.100000E+001
39 /N_BOLTHOLE = 8
40 /SKETCH_SEPARATING = 'Y'
41 ;
42
43 SYMBOL
44 ,1
45 /FONT_NUMBER = 0
46 /SCALE_FACTOR = 1.000000E+000
47 /SYMBOL_NUMBER = 2012
48 /USAGE_CODE = 4
49 /PARAMETERS = ( 1,2.191000E+002 )
50 /PARAMETERS = ( 2,3.400000E+002 )
51 /PARAMETERS = ( 3,2.191000E+002 )
52 /PARAMETERS = ( 4,3.400000E+002 )
53 /PARAMETERS = ( 5,2.400000E+001 )
Aveva Solutions Ltd AB Components

Page 2
SU016 2004-04-29 16:58:43
54 ;
55
56 USER_DEFINED
57 /USER_DEFINED_NINT = 10
58 /USER_DEFINED_NREA = 10
59 /USER_DEFINED_NSTR = 12
60 /USER_DEFINED_STR = (11,'3E4DD62E931243C791114337B6')
61 /USER_DEFINED_STR = (12,'330486')
62 ;
63 COMPONENT, 'PFSAPN10','RF.PN10-250',2201,250
64 ;
The components are stored in the Component Repository, ready for use in modelling: -
73
74
Chapter 5
5 Tribon.com
Tribon.com is a powerful web based application designed to support the integration of Supplier Information into the
customers Design Systems, and assist in the Procurement phase in Shipbuilding.
It allows the user to search the Global Database (GCDB) for suppliers and products that match desired technical
requirements and then download selected components into the local component database (LCDB). The components can
then be used directly in the Tribon Product Information Model (PIM).
E-Commerce functionality is provided to enable the user to request information and quotations from suppliers, initiate
reverse auctions and create purchase orders.
Shipyards Suppliers
Design Purchase
Department Department
Component E-commerce
Tribon Catalogue & functionality
Supplier Info
PIM
Tribon.com
Ship
Database
Supplier
Info
* For Tribon M1/M2 the supplier info is stored in user

given folder locations in there original state (autocad
drawing, word document, etc.) Tribon M3 stores the
supplier info as COM objects on Tribon databases.
Welcome to Tribon.com!
75
5.1 User Interface
Each part of the Tribon.com interface has its own unique purpose and so will appear differently.
Some selections appear below: -
Product Search
76
Preferred Suppliers
5.2 Getting Started
5.3 Logging in
In your web browser enter the address http://www.tribon.com

Type the username and password provided by Aveva Solutions Ltd and click Log in to Tribon.com
Please note that you have now entered the Tribon.com site. You can now see the Welcome Page.
77
5.4 Information
This page gives access to: -

 Search for Products

 List Suppliers

 Release Notes

 Training Guide
 Feedback Form
5.5 Local Language Support

Tribon.com supports local languages. At the time of release of Tribon.com 9.0, English and Korean are the languages
that are supported.

 To change the language pull down the Choose Language
window and select Korean

 The web page will refresh and all text, menus, etc., will
appear in Korean
 If the user exits the

website then the
language that is set
will be the default
when they log back
into Tribon.com
78
5.6 Menu Bar
On the right hand side you can see the Menu Bar. You may use this to navigate through the major Tribon.com functions
which are grouped into five categories.

 Tribon.com

 Products and Suppliers

 Settings

 Utilities
Click on the text to go

to the function
5.7 Utilities
Before we can use the website effectively, we must ensure that certain platform and software requirements are met on
the PC that is to be used.
5.7.1 Software Download

 Click on Support & Downloads from the Utilities menu
The page below will be displayed which contains information and links to the software
downloads.
79
5.7.1.1 Platform Requirements and Software Downloads for tribon.com
This page describes the requirements for using the market place as a customer (e.g. shipyard or designer).
5.7.1.2 Basic requirements


 Microsoft Windows 2000, XP

 Microsoft Internet Explorer 6.0 SP1

 Internet connection - broadband or fast internet connection is preferred

 Tribon installation present in a local environment to import the downloaded products to

 Tribon Project environment available and selected
5.7.1.3 Internet Explorer Settings


 Cookies - Using Tribon.com requires cookies to be enabled. Cookies are used to facilitate log-in and store session
information. For more information please click here to view Tribon.com Privacy and Cookies policy.

 Active X - Some functions of Tribon.com require ActiveX controls. In order to use these functions downloading of
signed ActiveX controls has to be enabled.

 Firewalls - Some firewall and internet traffic balancing solutions can change the IP addresses for outgoing traffic,
which can cause Tribon.com to log you out automatically. Please contact Tribon front line support at
tribonsupport@aveva.com in case you experience similar problems.

 Caching of pages - Please set your internet explorer to check for newer versions of page on "every visit to the
page". This option can be accessed trough "Internet Options..." menu, "General" tab, "Temporary Internet Files"
section, "Settings..." button, then radio control "Every visit to the page". If in doubt please contact Tribon front line
support at tribonsupport@aveva.com.

 Usage of “Pop-up blockers” - Some plug-ins for Internet Explorer offers the possibility to block pop-ups. Please turn
blocking of pop-ups off while using Tribon.com. Tribon.com uses pop-ups to enhance user experience and they are
Important part of its functionality. In case you need more information on how to turn the blocking of pop-ups off,
please refer to your plug-in documentation or contact Tribon front line support at tribonsupport@aveva.com.
5.7.1.4 Import Utilities Download

For a proper import of the technical and volumnal description of the product in local Tribon component repository, please
make sure you have downloaded the latest import utilities.
Notes:
- The dates within the square braces indicate the last time the file was updated.
- In case "File Not Found!" message is shown, for required file please contact tribonsupport@aveva.com.
- After importing of product information in local Tribon installation, it is referred to as component.
5.7.1.5 Software Downloads

All the software for editing and viewing technical information is using Microsoft ActiveX technology and is downloaded
automatically on request from the browser, the first time a viewing (editing) is requested.
Links to software information and downloads:
Download FREE HOOPS 3D Part Viewer for ACIS - The link opens in new window. The viewer can be used for viewing
3D SAT files.
80
5.7.1.6 Support
Please do not hesitate to contact Tribon front line support at tribonsupport@aveva.com in case you experience problems
with Tribon.com.
5.8 Logging off

To exit Tribon.com, carry out any one of the following steps.

 Click on the Logout text in the Tribon.com menu as below.

 Use the option File > Close in your browser – the browser will be closed

 Click the Home button on your browser – you will exit Tribon.com and return to your preset home page

 Enter any desired web page address in your browser – you will exit Tribon.com and go to your desired web page.
81
5.9 Settings
Via the settings menu it is possible to create and maintain the following: -

 Company Settings

 Preferred Suppliers Lists

 Project Settings

 User Settings

 User Administration
The extent of what you are allowed to do depends on what category of user you
are logged on as.
Level Name
40 Main Administrator
30 Administrator
20 Project Owner
10 E-Commerce User
5 Designer 2 (Download)
3 Designer 3 (Read-Only)
0 Not Active User
Application functions 40 30 20 10 5 3
View browser tree 1 1 1 1 1 1
Search and view components 1 1 1 1 1 1
Send technical enquiry 1 1 1 1 0 0
View supplier dir and company pages 1 1 1 1 1 1
Request info 1 1 1 1 1 1
Download 1 1 1 1 1 0
Use component printer page 1 1 1 1 1 1
View own company page 1 1 1 1 1 1
Configure company page 1 1 0 0 0 0
Administrate users 1 1 0 0 0 0
Change user data 1 1 1 1 1 0
Administrate projects 1 1 1 0 0 0
Choose project 1 1 1 1 1 0
Use requisition workflow 1 1 1 1 0 0
Use Message centre 1 1 1 1 1 0
Various "Super user" functions 1 1 0 0 0 0
82
5.10 General
Company: Here you can see general information regarding the company
Preferred Suppliers Lists: View and edit suppliers list, used to point out and prioritize certain
suppliers when searching.
Project: View and edit of project information. Here you can see information from the shipyards’
perspective where a project is equal to a ship. Users are connected to active projects here.
User: View and edit your user information.
User Administration: This is the administrative function where the main administrator work with
user information
5.11 Company
5.11.1 Presentation

 Contains information about the shipyard, including contact details and Company logo
etc.

 The first set of information that you see is the Company Header information. This is
maintained by Aveva Solutions Ltd.
5.11.2 Configuration Page


 Allows the user to update and configure the Shipyard information.

 As stated previously, Aveva Solutions Ltd must update the Company Header
information.

 The customised attributes may be updated by the Shipyard Administrator.
83
We will now show a small worked example of how to create a Customised Attribute.

 To create a new Customised Attribute choose

 Choose Template 1
 Click on the View and

choose template text
to see and choose
other template formats

 Type in Header and
Context texts.

 To add an image file
click the Browse button.
84

 Browse to the required image file on your PC. Click the file and choose Open

 Click
The system should tell you that ‘the attribute was successfully saved!’

 Navigate to the Presentation page and the result should look something like above. Using these methods you can
build up a complex Company Presentation.
85
Header
Image Context
5.12 Preferred Suppliers List

Lists of Preferred Suppliers can be created and are used in the presentation of search results. Lists can be created by
users for their own usage or by an administrator for all users within the company.
5.12.1 Viewing the available lists

 Choose All to see all the available preferred supplier lists.

 Choose User to see the current user preferred supplier lists etc
86
5.12.2 Creating new preferred supplier lists

 To create a new list click on Add

 Choose the List type, Name, Project and Description

 Then select Add list. You are then directed to the Search for supplier’s page.
In this example we will choose: -
Product Area: Valves

Country: United Kingdom

 Tick the suppliers that are preferred and then choose Add to list
87
You can add some notes to the supplier list if you wish.
At any time the Preferred supplier lists may be updated by choosing
5.12.3 Use of preferred supplier lists

Preferred suppliers indicated by a star in product search result: -
Preferred Supplier sorted first and indicated by an asterisk in the list-of-values dialog: -
To see the preferred supplier indication in the Product Search result list or
the Product Search supplier list the user setting ‘Use preferred suppliers’
should be ticked
88
5.13 Project
The Project option allows you to list and update the existing projects. The user may also
create new Projects and attach users to the projects.
The project can be selected from the

Choose Project pull down window
5.14 User
The User function shows the current user details and allows updates to be made to the
current user.
Alert and Broadcast

mails from the Message
centre will be sent to this
e-mail address
The list of Preferred

Suppliers will be
active for the User
89
5.15 User Administration
The User Administration function allows the creation and modifications of users plus
associated details.
Alert and Broadcast

mails from the Message
centre will be sent to this
e-mail address
90
Appendix
Appendix 1, Bending Machine Set-up

The following tables show the set-up for the bending and flange welding machines contained within the main TTP
project. For the “outman” sub-project these objects are empty, so part of a possible exercise would be to recreate these
objects as below.
(1) BENDING MACHINE DIMENSION TABLE
 In the above table the Wall-thicknesses are all set at 0.0. This means that all thicknesses for these Outer-diameters
will be handled.
(2) BENDING MACHINE BENDING TABLE
91
(3) BENDING MACHINE SPRINGBACK TABLE / STRETCH-FACTOR TABLE
(4) FLANGE WELDING MACHINE WELDING TABLE
92

M3 Outfit Manager SP4

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

M3 Outfit Manager SP4

Caricato da

Copyright:

Formati disponibili

Tribon Outfit

Training Guide • Training Guide • Training Guide

Date Page(s) Revision Description of Revision Release

19/10/2004 Various 01 Updated to M3SP2 M3SP2

Fax +44 (0)1223 556669

Copyright © 2004 Aveva Solutions Ltd

Printed by Aveva Solutions Ltd on 04 October 2005

1 Outfit Set-up & Customisation .......................................................................................................... 5

2 Creation of Modules and Systems .................................................................................................. 23

3 Piping Machine Objects................................................................................................................... 25

4 Standard Handling ........................................................................................................................... 45

Appendix 1, Bending Machine Set-up .................................................................................................... 91

1 Outfit Set-up & Customisation

1.1 Using Frame Numbers in the Outfitting Systems

1.2 Define Model Co-ordinates, sx001

1.2.2 Types of Planes

1.2.3 Input File syntax

1.2.4 The IDENT Statement

[,<id>] User identification string (maximum 26 characters). This string is optional.

/PROJECT=<projid> <projid> Project identification string (maximum 26 characters).

Example: IDENT,’Joe Bloggs’/PROJECT=’TTP’;

1.2.5 The REFERENCE Statement

[/X=<coordinate>] Define an x-value with the name <refid>.

<panel name> Name of hull panel (string maximum 26 characters long).

1.2.5.1 Example input file

Worked Example, Define Model Co-ordinates

 The default COORD_TRANS in the drafting

 Refer to the Drafting User Guide for

1.3.1 Flange Offset Tables

The pipe system can calculate this offset using either: -

1.3.1.1 Internal default values

<excess> = ( <collar dia> - DY ) * 0.5

1. The variable, SBP_FLG_OFFSET must be set in the d065 project file

In the d065<project>.sbd file: -

Record types Data

4 <Offset> <DN> <DY> <Wallthickness>

5 <Offset> <DN> <DY> <Wallthickness> <Flange group>

6 <Offset> <Height or Diameter> <Width or Not used>

7 <Offset> <Height or Diameter> <Width or Not used>

Example 1, using DN Ranges

Example 3, Using Wall Thickness

1.3.2 Nominal Diameter Tables

The system can determine the DN in the following two ways: -

1.3.2.1 Internal Tables

1 <version number> a user id to handle multiple versions

Example, showing DN10-DN50 for various material codes

1.3.3 Boss Types

BOSS_DEFAULT=NO (default) ON_SURFACE or INSERT or EXTRUDE or SADDLE in the SBP_MODEL_DEF file

1.3.3.2 Boss Machine Object

1.3.3.3 Default Values

Other system defaults for internal excess are: -

1.3.3.4 Rules for choosing type

Object Type Name Location Example

1.3.5 Naming Conventions for Tribon Pipe Objects

 See Pipe User Guide, Tribon M3 Outfitting

1.4.1 Pipe Specifications.

The file name format is:

TbSpecConversion ES_SPEC_WW_.DAT ww.txt

Use the function File > Import.

Save the imported Pipe Specification. File > Save

1.4.2 Pipe Diagrams

1.4.2.1 Diagram Drawing

1.4.2.2 Diagram List

1.4.3 Cable Diagrams