TM-2122 AVEVA Marine (12.1) Project Administration (Hull) Rev 4.0

94  26  Download (0)

Full text

(1)

www.aveva.com

AVEVA Marine

(12.1)

Project Administration (Hull)

(2)
(3)

AVEVA Marine (12.1) Project Administration (Hull) (TM-2122)

www.aveva.com

Revision Log

Date Revision Description of Revision Author Reviewed Approved

11/10/11 0.1 Updated to 12.1.1 JP

20/10/11 0.2 Reviewed JP JS

21/10/11 1.0 Approved for training for 12.1.1 JP JS SK

02/12/11 2.0 Issued with latest copyright footer CF CF

29/03/12 2.1 Issued for review 12.1.SP2 JP

03/04/12 2.2 Reviewed JP SK

03/04/12 3.0 Approved for training 12.1.SP2 JP SK SK

16/05/12 3.1 Clip macro information added JP JP

09/11/12 4.0 Approved for training 12.1.SP3 JP SK SK

Updates

All headings containing updated or new material will be highlighted.

Suggestion / Problems

If you have a suggestion about this manual or the system to which it refers please report it to AVEVA EDS - Training and Product Support at tps@aveva.com

This manual provides documentation relating to products to which you may not have access or which may not be licensed to you. For further information on which products are licensed to you please refer to your licence conditions.

Visit our website at http://www.aveva.com

Disclaimer

1.1 AVEVA does not warrant that the use of the AVEVA software will be uninterrupted, error-free or free from viruses.

1.2 AVEVA shall not be liable for: loss of profits; loss of business; depletion of goodwill and/or similar losses; loss of anticipated savings; loss of goods; loss of contract; loss of use; loss or corruption of data or information; any special, indirect, consequential or pure economic loss, costs, damages, charges or expenses which may be suffered by the user, including any loss suffered by the user resulting from the inaccuracy or invalidity of any data created by the AVEVA software, irrespective of whether such losses are suffered directly or indirectly, or arise in contract, tort (including negligence) or otherwise.

1.3 AVEVA's total liability in contract, tort (including negligence), or otherwise, arising in connection with the performance of the AVEVA software shall be limited to 100% of the licence fees paid in the year

1.4 Clauses 1.1 to 1.3 shall apply to the fullest extent permissible at law.

1.5 In the event of any conflict between the above clauses and the analogous clauses in the software licence under which the AVEVA software was purchased, the clauses in the software licence shall take precedence.

(4)

www.aveva.com

Trademarks

AVEVA and Tribon are registered trademarks of AVEVA Solutions Limited or its subsidiaries. Unauthorised use of the AVEVA or Tribon trademarks is strictly forbidden.

AVEVA product/software names are trademarks or registered trademarks of AVEVA Solutions Limited or its subsidiaries, registered in the UK, Europe and other countries (worldwide).

The copyright, trade mark rights, or other intellectual property rights in any other product or software, its name or logo belongs to its respective owner.

Copyright

Copyright and all other intellectual property rights in this manual and the associated software, and every part of it (including source code, object code, any data contained in it, the manual and any other documentation supplied with it) belongs to, or is validly licensed by, AVEVA Solutions Limited or its subsidiaries.

All rights are reserved to AVEVA Solutions Limited and its subsidiaries. The information contained in this document is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval system, or transmitted without the prior written permission of AVEVA Solutions Limited. Where such permission is granted, it expressly requires that this copyright notice, and the above disclaimer, is prominently displayed at the beginning of every copy that is made.

The manual and associated documentation may not be adapted, reproduced, or copied, in any material or electronic form, without the prior written permission of AVEVA Solutions Limited. The user may not reverse engineer, decompile, copy, or adapt the software. Neither the whole, nor part of the software described in this publication may be incorporated into any third-party software, product, machine, or system without the prior written permission of AVEVA Solutions Limited, save as permitted by law. Any such unauthorised action is strictly prohibited, and may give rise to civil liabilities and criminal prosecution.

The AVEVA software described in this guide is to be installed and operated strictly in accordance with the terms and conditions of the respective software licences, and in accordance with the relevant User Documentation. Unauthorised or unlicensed use of the software is strictly prohibited.

Copyright 1994 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved. AVEVA shall not

(5)

Contents

www.aveva.com

1 Introduction ... 7 1.1 Aim... 7 1.2 Objectives ... 7 1.3 Prerequisites ... 7 1.4 Course Structure ... 7

1.5 Using this guide ... 7

2 Hull Top Level Elements ... 9

3 Initiate Hull Standards ... 11

3.1 Initialising the Form data bank (SB_CGDB) ... 11

3.1.1 Creating a Hull Reference Object ... 12

3.2 Initiating the Structure data bank (SB_OGDB) ... 14

3.2.1 Creating a Structure Reference & Hull Structure Object... 14

3.3 Defining Frame / Longitudinal positions ... 15

3.3.1 Frame numbering in AVEVA Marine ... 15

3.3.2 Longitudinal position numbering in AVEVA Marine ... 15

3.3.3 Creating the SBH GENTAB object ... 16

3.3.4 The contents of the TIL file ... 17

3.4 Creating a Block Object ... 18

3.5 Deleting Blocks ... 20

4 Releasing the Surface to Dabacon ... 21

5 Hull program defaults ... 23

5.1 Planar Hull Modelling (sj001) ... 23

5.1.1 Excess ... 24

5.1.2 Excluding blocks... 24

5.2 Curved Hull Modelling (sh700) ... 24

5.3 Hull Structural Design (sj700) ... 25

5.4 Plate Nesting (se001) ... 25

5.5 Generic Post Processor (sf001) ... 26

6 Hull Drawings ... 27

6.1 Drawing Databases ... 27

6.2 Drawing Registry ... 28

6.3 Production sketches naming rules ... 28

6.4 Shell Expansion Drawing ... 29

6.5 Settings Drawings ... 30

7 Hull PPI Programs ... 31

7.1 Plane Part Generation (sf416d) ... 31

7.2 Parts Lists (sf101d) ... 31

7.3 Profile Sketch and List (sf628d) ... 32

7.4 Weight and Centre of Gravity (sf102d)... 33

7.5 Curved Plate Generation (sf831d) ... 33

7.6 Bending Templates (sf820d) ... 34 7.7 Jig Pillars (sf824d) ... 35 7.8 Plate Jigs (sf821d)... 36 7.9 Profile Nesting (sf605d) ... 37 7.10 Paint Areas (sf812d)... 38 7.11 Hull Marks ... 38 8 Customising a project ... 39

8.1 Panel Data and Geometry Type ... 39

8.2 Cutouts and Clips ... 39

8.2.1 Cutouts ... 39

8.2.2 AVEVA Marine External Cutout Definition Facility ... 40

8.2.3 Cutout Setting set up file. ... 41

8.2.4 Cutouts via Macros... 42

8.2.5 Automatic setting of Cutouts ... 42

8.2.6 Named Cutouts ... 43

8.2.7 Clips ... 44

8.2.8 Clips via Macros ... 45

(6)

www.aveva.com

8.3.2 U and I bar set-up... 47

8.4 Connection codes ... 48

8.5 Endcut set-up ... 50

8.5.1 Endcut table ... 50

8.5.2 Endcut selection ... 52

8.6 Profile restriction file ... 52

8.6.1 General information section ... 53

8.6.2 Type specific section ... 53

8.6.3 Shell stiffener curvature ... 55

8.6.4 Raw profiles ... 56

8.7 Brackets ... 57

8.7.1 Bracket Wizard ... 58

8.7.2 Bracket Instance Object, Create ... 61

8.8 Tap Pieces ... 63

8.9 Genauigkeit (GSD Marking Triangles) ... 63

8.10 Bevel ... 63

8.11 Weld Planning Setup ... 64

8.11.1 Weld Positions ... 64

8.11.2 Weld Leg Length ... 64

8.11.3 Weld Defaults ... 65

8.12 Shrinkage ... 66

8.13 Swedging ... 67

8.14 Knuckled panel bending control ... 69

8.15 Folded flanges ... 69

8.16 Material Qualities ... 71

8.16.1 Defining Qualities ... 71

8.16.2 Quality exchange... 72

8.17 Customising Dialogues in AVEVA Marine Hull ... 73

8.18 Nesting ... 76

8.18.1 Creating parent plates ... 76

8.18.2 Create Rest Plate ... 76

8.18.3 Parts Menu Display ... 77

8.18.4 Burning Sketches ... 77

8.18.5 Defining a new nesting drawing form ... 78

8.18.6 Modifying an existing nesting drawing form ... 78

8.18.7 Deleting a drawing form ... 78

8.18.8 Defining a new hook ... 78

8.18.9 Modifying an existing hook ... 79

8.19 Automatic position numbers ... 79

8.20 Part name control... 80

8.20.1 Part name level ... 82

8.21 Functional Properties ... 83

8.22 Functional Structure (Hull Structural Design) ... 84

9 Manufacturing Packages ... 85

9.1 Manufacturing packages from template ... 85

9.2 Manufacturing packages from macro ... 86

9.3 Manufacturing folder created interactively. ... 87

10 Marine Copy Assistant ... 89

10.1 Export ... 89

10.2 Import ... 91

(7)

www.aveva.com

CHAPTER 1

1

Introduction

AVEVA Marine Hull Manager covers the project environment, settings & defaults required to run the Hull applications

1.1

Aim

To allow the user to define and configure the project environment and default standards.

1.2

Objectives

Create the Hull Top Level Elements. Edit and Initiate the hull standards. Set frame tables.

Release the project surfaces.

1.3

Prerequisites

An understanding of the AVEVA Marine Hull Applications.

1.4

Course Structure

Training will consist of oral and visual presentations, demonstrations and set exercises. Each workstation will have a training project. This will be used by the trainees to practice their methods, and complete the set exercises.

1.5

Using this guide

Certain text styles are used to indicate special situations throughout this document, here is a summary; Menu pull downs and button press actions are indicated by bold dark turquoise text.

Information the user has to Key-in will be in bold, red text. Annotation for trainees benefit:

Additional information

System prompts should be bold and italic in inverted commas i.e. 'Choose function'

(8)
(9)

www.aveva.com

CHAPTER 2

2

Hull Top Level Elements

After creating the project structure DB and editing the d065 file, it is now necessary to run the dbprompt utility to create the hull top level elements

example that follows a MDB named HADMIN has been created which includes all of the the hull top level elements will be stored.

Open the Log Viewer, Start > All Programs > AVEVA Marine > Design > Marine 12.1 > Hull Log Viewer, click Admin > DBPrompt.

The CredentialsForm will be displayed, input the required login information.

(Password=HADMIN)

The following form is displayed:

To add hull top level elements to a DB, select the DB and right click to display the available options, these will differ depending on the type of DB selected (DESI or MANU).

DESI DB options:

MANU DB options:

Click on the element type you wish to create, the following input box is displayed, key in the name of the element, then press Return/Enter on the keyboard

The hull top level elements will be added to the DB, the + sign indicates additional contents within the DB, selecting the + sign will expand the tree. Selecting sign will close the node.

(10)

www.aveva.com

To delete an element, select the element and right click Delete.

To rename an element, select the element and right click Rename, then key in a new name and press Return/Enter on the keyboard. The delete option will be disabled if the element contains hull references e.g. if panels have been added to a block.

When all top level elements have been created select File > Save. The top level element structure can be exported ( ) to a csv file which can be edited using Excel, the file can then be imported ( ) to update the structure.

An extract of the exported file for the MTP project is shown below:

The following top level elements should be defined in their own DESI database, those marked * should exist only once in each project. There are also rules governing the use of others: RSOWLD*, COMWLD*, SSOWLD, HCMWLD, MOGWLD, STDWLD, MWLWLD*, GRDWLD*.

NSEQ and HMKWLD.

The above are only part of the project recommendations; please see the User Guide - Hull in Dabacon, Marine Databases and World Elements,

Databases and World Elements Used in Hull.

The Options menu contains Non-unique naming mode MANU. Selecting this option will allow non uniquely named elements to be created, and the following warning is displayed.

The top level manufacturing elements may only exist once in any working MDB, to exit the system and log back into another MDB to create the same top level manufacturing elements would be laborious. To In this way all quality elements may be made in one operation.

Additional functionality can also be found regarding the generation of BLOCK top level elements using an extended version of the file used to define the block volumes. If reference to frame and longitudinal positions are to be used then the frame table should be generated before generating the blocks.

(11)

www.aveva.com

CHAPTER 3

3

Initiate Hull Standards

After defining the hull top level elements it is then necessary to initialise the Form data bank (SB_CGDB) and the Structure data bank (SB_OGDB). This involves the creation of various objects and tables in both the SB_CGDB and SB_OGDB. These objects and tables will inform the AVEVA Marine system which hull form to use, what the frame spacing is, what the prefix for the naming of seams and butts should be if

SBH_FREE_SEAMPROF_NAMES is not set.

This object and table is created using the AVEVA Marine Initiate Hull Standards utility. Ensure no AVEVA Marine applications are running.

S tart the utility by clicking on Start > All Programs > AVEVA Marine > Design > Marine 12.1 > Hull Log Viewer, click Admin > DBPrompt.

Select Hull > Hull Init

The CredentialsForm will be displayed, input the required login information.

(Password=HADMIN)

The user should have write access to t Hull top level elements e.g.

GRIDWLD for the storage of the frame tables, BLOCK references for the storage of hull block

definitions should also exist. Note: The use of HBLWLD is not necessary, the block references can be made directly in the relevant db using DBPrompt.

In the tree structure on the left-hand side of the resulting application expand the Initiate Hull Model node and the following nodes will be displayed.

Hullref, create: Creates a Hull Reference Object in the SB_CGDB

Structref, create: Creates a Structure Reference Object in the SB_OGDB

Blocks, manipulate: Creates Block objects in the SB_OGDB

Frame/long positions, create: Creates an __SBH_GENTAB__ object in the SB_OGDB

The purpose and use of the above four functions are explained in the following chapters. (Some of these objects can also be controlled / created using Hull Design and are covered in the Hull Design course).

3.1

Initialising the Form data bank (SB_CGDB)

The form databank contains information related to the surfaces of the ship i.e. the ship surface itself and curve information derived from the surfaces. Additionally, there are some tables that keep a record of the names of objects in this data bank and of the objects stored there.

(12)

www.aveva.com

3.1.1 Creating a Hull Reference Object

The hull reference object is a small table containing information about names and name rules of objects in the form databank (SB_CGDB). The AVEVA Marine modules access the name of this object via the AVEVA Marine environment variable SB_HREF.

The hull reference object is created or modified by the Hullref, create option. Clicking on this option will result in the following form being displayed:

Name of Databank (SB_CGDB) and (SB_HREF) will be automatically filled in by the system assuming the relevant variable is set in the current project.

Name of HULLREF object:

An arbitrary string, but usually a combination of the project identification, (ship letters) and the word HULLREF. This field will also be automatically filled in with the current value of

SB_HREF. This allows either the modification of this existing object or the creation of a new hull reference object.

Multiple hull reference objects can exist in one project but only the one currently assigned to SB_HREF will be read by the system.

Allow free naming of shell profiles and seams:

If this is selected free naming can be given. (Set only once in a project and should not be changed.)

X co-ordinate of the

perpendiculars: The relevant X co-ordinate for the Aft and Fore

Perpendiculars (given in mm)

The Half breadth of the ship: The half breadth of the ship (given in mm)

Name of the hull form: If using AVEVA Marine Initial Design software to produce the hull form this name should match the name of the main hull surface released from the Lines or Surface application. It should be left empty if registering the surfaces through the Structural Design application.

Suffix: Curves created in these additional surfaces are named according to the same rules as curves in the main surfaces. To separate them from the main surface curves the group names of these additional

surfaces have an additional "suffix" by which the group name will be extended. Example of Composed Names of Objects in Multiple Surfaces:

In order to allow the same numbers to be used for objects in different surfaces, it is necessary to specify a surface specific extension of the group names. This surface suffix consists normally of one letter.

Example; suppose that there is a seam with number 123 in an additional surface with surface suffix C and that the group name for seams is AAS. Then the name of that seam will be AASC123.

(13)

AVEVA Marine (12.1) Project Administration (Hull) (TM-2122)

www.aveva.com

Plate thickness option: Allows for plate thickness to be disregard. Panel against surface, where panels allow for shell plate compensation. Shell profiles only, where shell profiles only allow for compensation.

Both panels & shell profiles, where both panels and profiles allow for shell thickness compensation.

Co-ordinate table name: The name of the co-ordinate tables for frame, waterline and buttock curves. These tables contain the X, Y and Z co-ordinate of the plane in which the curve with a given number is located.

Group name: The group names of frame, waterlines and buttocks. The names of these main curves are composed by a "group name" concatenated with a curve number (e.g. a frame number). These group names are defined in this object.

Name of deck form: If using AVEVA Marine Initial Design software to produce the deck form this name should match the name of the deck surface released from the Surface application. If no deck form is present in this particular project, the field should be left blank.

Seams and butts:

Table of co-ordinate limits on X-axis/ Z-axis: The names of the limit tables along the X and Z axes for seams. One of these tables contains the minimum and maximum co-ordinates along the X axis of all seams, the other the same information for the Z axis.

Group name: Defines prefix to be given to Seams and Butts in the tables above. (These naming rules do not need to be used if SBH_FREE_SEAMPROF_NAMES is set YES).

Additional Surfaces: Opens the dialog box shown opposite, where the user can add up to 100 additional surfaces.

Name: If using AVEVA Marine Initial Design software to produce the additional surface this name should match the name of the surface released from the Surface application.

Suffix: Curves created in these additional surfaces are named according to the same rules as curves in the main surfaces. To separate them from the main surface curves the group names of these additional surfaces have an additional "suffix" by which the group name will be extended.

Plate thickness option: Allows for plate thickness to be disregard. Panel against surface, where panels allow for shell plate compensation. Shell profiles only, where shell profiles only allow for compensation.

Both panels & shell profiles, where both panels and profiles allow for shell thickness compensation.

Surface type: Select either Shell or Deck

Add: After completing the 3 fields above use this button to submit the additional surface information.

Delete: Highlight an existing additional surface in the list displayed and use this button to delete it.

OK: Use this button to exit the function after Adding/Deleting the desired surfaces.

Extract data from DB: The system will refresh the current form with the latest data from the SB_CGDB.

Create Object: After completing all the required fields use this button to create/update the hull reference object in the SB_CGDB.

For Additional surfaces to be available in the modelling applications i.e. when creating symbolic views, a reference should be added to the modelling default files (sj001.sbd, sj700.sbd and sh700.sbd).

SURFACES = 1,2,3,-4 Where positive values reference additional shell surfaces and negative values reference additional deck surfaces.

(14)

www.aveva.com

3.2

Initiating the Structure data bank (SB_OGDB)

The structure databank contains model information about the internal structure of the ship. The model information in the structure information is stored according to nominal dimensions and the adjustments for production are made when parts are extracted for production. Examples of such adjustments are shrinkage compensation, excess, shell plate development, development of knuckled pieces, changes for (varying) bevels angles and bevel gaps.

Additionally the structure data bank contains some table information and objects that describe miscellaneous types of hull standards, set up by the customer.

3.2.1 Creating a Structure Reference & Hull Structure Object

The structure reference object is a small table containing information about names and name rules of objects in the structure databank. The AVEVA Marine application modules access the name of this object via the AVEVA Marine environment variable SB_SREF.

The structure reference object is created or modified by the Structref, create option. Clicking on this option will result in the following form being displayed:

Name of Databank (SB_OGDB)

and (SB_SREF) will be automatically filled in by the system assuming the relevant variable is set in the current project.

Ship Letters: It is suggested that the names of all hull objects of a certain project should start with the same one or two letters. Check all of the Link boxes and the letters keyed into this field will be automatically added to the default names for the other objects in this menu.

Name of Structure Reference Object: STRUCTREF

Name of Hull Structure Object: HULLSTRUCT. The Hull Structure object is the object that serves as the entry to the hull model via the design structure. It does not contain any relevant information except the references to all the blocks. The Hull Structure object is automatically updated each time a block object is created, modified or deleted. The designer never really gets in direct contact with the Hull Structure object.

Name of Longitudinal Limit Table: The name of the extension table for longitudinals along the X axis (min-max co-ordinate values). The names of limit tables for the extension along the Y and Z axes are formed by adding 'Y' and 'Z', respectively, to this name.

Longitudinal Group Name: The group names of longitudinals. The name for one of these objects is created by a "group name" plus a number added in Curved Hull or Basic Design, typically the longitudinal position multiplied by 10. (These naming rules do not need to be used if SBH_FREE_SEAMPROF_NAMES is set).

Name of Transversal Limit Table: The name of the extension table for transversal frames along the X axis (min-max co-ordinate values). The names of limit tables for the extension along the Y and Z axes are formed by adding 'Y' and 'Z', respectively, to this name.

(15)

AVEVA Marine (12.1) Project Administration (Hull) (TM-2122)

www.aveva.com

Transversal Group Name: The group names of transversal frames. The name for one of these objects is created by a "group name" plus a number, typically the relevant frame number. These naming rules are not used if SBH_FREE_SEAMPROF_NAMES is set.

Project Name: The project name of the current project. This name may be used as a part the production oriented part names (and may thus be considered as an "external" correspondence to the ship letters that are for internal use).

Multi View Project: Enables design and production views with in the project.

Get data from Object: The system will refresh the current form with the latest data from the SB_OGDB.

Create Object: After completing all the required fields use this button to create/update the structure reference object in the SB_OGDB.

3.3

Defining Frame / Longitudinal positions

Within AVEVA Marine it is possible to define an object that contains the entire frame and longitudinal position information for the current project. Within this object it is possible to define both horizontal longitudinal grid positions i.e. distances from the centreline and also vertical longitudinal positions i.e. distances from the baseline.

The object will be named __SBH_GENTAB__ and will be stored in the structural database (SB_OGDB). The object is very important within an AVEVA Marine project as many of the applications use this object to calculate the position of model objects that are located using frame or longitudinal position references. Before discussing the creation of the object a few AVEVA Marine numbering rules should be considered.

3.3.1 Frame numbering in AVEVA Marine

The frames must be integers i.e. they must not contain any letters, however they may be negative. The number of the frames should be in the range [-899,2276]

The maximum number of frames is currently restricted to 500, unless the frames are consecutively numbered. In the latter case the frames may have numbers in the range [-99,500], i.e. 600 in total.

The relation between frame number and frame position may be quite arbitrary, e.g. they may be increasing with increasing x-co-ordinates, decreasing with increasing x-co-ordinate or set without any specific order with relation to the frame position.

The distance between frames may vary arbitrarily.

It is common within shipbuilding to locate frame number 0 at the aft perpendicular and to let the frames in the aft peak be identified by letters; A, B, C, etc. The rules above do not allow this denomination.

It is recommended that the letters be replaced by negative numbers (A -1, B -2, etc.).

In some regions of the world it is customary to have numbered frames only at web frames and to identify intermediate frames by adding letters to the main frame number, e.g. 56, 56A, 56B ...., 57, 57A, 57B, ... . It is recommended that the letters in the example are replaced as follows; 56, 561, 562,...., 57, 571, 572, ... (or to 560, 561, 562, ...., 570, 571, 572, ... ).

3.3.2 Longitudinal position numbering in AVEVA Marine

Frame positions are in most cases defined at those locations along the ship where there are transversal hull members, either frames or webs, etc. In a similar way there are in most ships characteristic distances from the Centre Line (CL) and above the Base Line (BL) where hull members are located. E.g. longitudinals in the bottom and in the side in the midship section are located at positions which normally also define the position of stiffeners in decks, platforms, bulkheads, etc, and the position of girders. By referring to these positions one may define locations along the Y and Z axes as simple as e.g. Y=LP10 +100 and Z=LP35 -100. (LP10 +100 means 100mm in portside direction from Longitudinal Position number 10 in the bottom, LP35 -100 means 100 mm below Longitudinal Position 35 in the side).

From a practical point of view it is recommended to let the longitudinal positions and their numbers coincide with the numbers and positions of actual longitudinals in the midship section. However, it should be noted that the longitudinal positions form a grid that need not have any direct relation with the physical longitudinal frames. E.g. if some longitudinals are replaced by girders there are "holes" in the numbering of longitudinals.

(16)

www.aveva.com

However, the longitudinal positions should include all the positions, also those where there are no

longitudinal frames. The figure below shows schematically a typical midship frame with suggested longitudinal positions.

The point at the cross in the figure above may be located by Y=LP6, Z=LP26.5

The following rules should be considered:

The positions and the numbers should be related to those of actual longitudinal frames, if possible.

The longitudinal numbers should be in the interval [0,999]

The numbers for

horizontal positions (along the Y axis) and vertical positions (along the Z axis) should not be the same.

It is quite possible to define a longitudinal position in the CL plane, i.e. where Y=0. This position may have number 0.

The relation between increasing/decreasing numbers and increasing/decreasing distances is arbitrary similar to what is stated for frames. This should be decided by the rules for longitudinal numbering, used by the yard.

There is no direct connection between the longitudinal position numbers and the generated physical longitudinal frames.

Longitudinal positions in the bottom are normally only defined on portside. Reference to the corresponding positions on the starboard side is done by negating the longitudinal number, e.g. Y=LP-20+100.

3.3.3 Creating the SBH GENTAB object

The __SBH_GENTAB__ object is created or modified by the Frame/long positions, create option.

Clicking on this option will result in the following form being displayed:

The __SBH_GENTAB__ object is created by the system reading a suitable TIL file.

(17)

AVEVA Marine (12.1) Project Administration (Hull) (TM-2122)

www.aveva.com

If an input file already exists then use the Browse button in the Generate object field to locate the file.

If no file exists then use the Generate TIL button in the Generate TIL File field to create a new file. The system will prompt for a name for the file and it should then be saved before exiting the editor. After creating the file use the Browse button in the Generate object field to locate the file.

When the file has been located successfully in the Generate object field, use the Edit TIL File button to open the file with the default Windows editor and this allows editing to suit.

After the successful editing of the file close and save it. Click the Create object button and the system will generate the __SBH_GENTAB__ object.

3.3.4 The contents of the TIL file

The input file is organised in "record types" with layout as described below. The format is free but it is recommended to have one record per line. The line width is limited to 80 characters. The number of records is unrestricted.

Record Type 0

This record must specify the name of the current structure reference object. E.g. STRUCTREF

The line should consist of the digit zero followed by a blank space, then a single apostrophe followed immediately by another single apostrophe then a blank space followed by the name of the structref object. Record Type 2

This record has no parameters. If it is included in the input file the system will produce an output file containing all of the frame and longitudinal positions generated along with their corresponding co-ordinate value. It is recommended that this record type is always included.

Record Type 20

This record type informs the system of the desired frame number and position.

The records must be given such that the co-ordinates are in strictly ascending or descending order. E.g. 20 START STEP END COORD COORDSTEP

START The first frame number for which to add or change a co-ordinate STEP The difference in frame numbers for the current record

END The last frame number for which to add or change a co-ordinate COORD The co-ordinate for the frame START

COORDSTEP The distance between each frame in the range START END

Record Type 30

positions relative to the centreline. The records must be given such that the co-ordinates are in strictly ascending or descending order.

E.g. 30 START STEP END COORD COORDSTEP

START The first longitudinal for which to add or change a co-ordinate STEP The difference in longitudinal numbers for the current record

END The last longitudinal number for which to add or change a co-ordinate COORD The co-ordinate for the longitudinal START

COORDSTEP The distance between each longitudinal in the range START END

The longitudinal numbers should not be multiplied by 10 and they have to be equal to or greater than 0.

Record Type 40

relative to the base line. The records must be given so that the co-ordinates are in strictly ascending or descending order.

(18)

www.aveva.com

E.g. 40 START STEP END COORD COORDSTEP

START The first longitudinal number for which to add or change a co-ordinate STEP The difference in longitudinal numbers for the current record

END The last longitudinal number for which to add or change a co-ordinate COORD The co-ordinate for the longitudinal START

COORDSTEP The distance between each longitudinal in the range START END

The longitudinal numbers should not be multiplied by 10 and the first number should be greater than the final horizontal position number defined in record type 30

Example of input

Resulting frame positions:

FR-4 is at X=-3200, frame numbers then increase in steps of 1 until FR222 is reached with each frame being 800mm from the previous one.

Resulting horizontal longitudinal positions:

LP0 is at Y=0 and the longitudinal position numbers then increase in steps of 1 until LP2 is reached with each longitudinal position being 600mm from the previous one. LP3 is at 2000 and the longitudinal position numbers then increase in steps of 1 until LP15 is reached with each longitudinal position being 800mm from the previous one.

Resulting vertical longitudinal positions:

LP19 is at Z=0 and the longitudinal position numbers then increase in steps of 1 until LP21 is reached with each longitudinal position being 750mm from the previous one.

LP22 is at Z=2200mm and the longitudinal position numbers then increase in steps of 1 until LP30 is reached with each longitudinal position being 700mm from the previous one.

LP31 is at Z=8550mm and the longitudinal position numbers then increase in steps of 1 until LP40 is reached with each longitudinal position being 750mm from the previous one.

LP41 is at Z=16060mm and the longitudinal position numbers then increase in steps of 1 until LP45 is reached with each longitudinal position being 760mm from the previous one.

LP46 is at Z=19755mm and the longitudinal position numbers then increase in steps of 1 until LP47 is reached with each longitudinal position being 655mm from the previous one.

LP48 is at Z=21240mm and the longitudinal position numbers then increase in steps of 1 until LP52 is reached with each longitudinal position being 830mm from the previous one.

Additional increments may be added as required.

From the Structural Design interface up to four additional frame tables may be defined for different geographical areas of the ship.

3.4

Creating a Block Object

Like the hull structure object the block objects do not carry any actual model information, only the location of its surrounding box in space. It should primarily be considered a geographically constrained container of panels, referred to from the Hull Structure object.

The designer never really interacts with the block objects except when they are created. However, the block may be used as the "handle" by which information from the hull model is extracted in various situations. The same block may include panels both on portside and on starboard. If a block is restricted to a side section (e.g. a side tank) its limits should be restricted to its limit on portside. Panels valid for the starboard side (and even those modelled and stored on starboard) may nevertheless belong to this block. Thus a block can always contain panels within its explicitly defined block but also panels within the box when mirrored in the centreline plane.

(19)

AVEVA Marine (12.1) Project Administration (Hull) (TM-2122)

www.aveva.com

A Block is created or modified by the Blocks, create option. Clicking on this option will result in the following form being displayed:

The block objects are created by the system reading a suitable csv file.

Blocks can also be created from a file or interactively using the Structural Design interface.

Use Browse to locate the csv file to be used to define the block. Example of a block csv file shown below:

Column A Type of block: D=Design, P=Production Column B Name of the block.

Column C,D,E,F,G,H Nominal position of Aft, Starboard, Bottom, Forward, Port and Top block limits. Coulmn I Enclosing Design Block to which the Production blocks will belong.

Column J,K,L,M,N,O Offset (overlap) from Aft, Starboard, Bottom, Forward, Port and Top block limits. Column P,Q,R,S,T,U Named limit of the block if defined by RSO, plane or surface.

Column V Sym: Should the block be symmetrical (P&S).

Column W System colour highlighting the block limits when displayed. Column X Enclosing envelope.

A block definition in AVEVA Marine does not need to reflect the building blocks used for construction. The use of the Assembly Planning Tool allows the actual build sequence to be completely redefined, regardless of the block definition in AVEVA Marine.

It is also possible to define BLOCK top level elements by adding the database names in an additional column Y, this csv file should be input through the DBPrompt utility before executing through the block create program otherwise the block limits will be stored in the first writeable DESI type db and not under there top level elements.

In the example shown opposite in the file named MTP_BLOCKS_1.csv (columns C to X have been hidden) top level BLOCK elements named A101, A102 etc. will be created in the PHULLAFT/P_A101 db,

(20)

www.aveva.com

To execute in batch start the AVEVA Marine command prompt, (this sets the installation and project paths) and should be used when executing any batch processes from a command prompt.

All Programs > AVEVA Marine > Design > Marine 12.1 > AVEVA Command Prompt

Then execute the input file using the following syntax (example shown in MTP project using file MID_BLOCKS_1.csv defined on previous page):

dbprompt proj=MAR user=SYSTEM pass=XXXXXX mdb=/DBPROMPT blk=MTP_BLOCKS.csv

Top level BLOCK elements should be created before running the block file in Init Hull or through the Structural Design interface.

It is possible, using PML function to create a block in a specific DB within the application. The function returns the DBREF to the newly created block element if successful.

The DB needs to be accessable from the MDB used to log in. Eg.

This statement will create the block MYBLOCK in the DB MYTEAM/MYDB

3.5

Deleting Blocks

After defining a block, the block may be deleted using the Structural Design module or by running the block creation file through Hull Init from the Log Viewer and preceding the block to be deleted with the text

DELETE.

(21)

www.aveva.com

CHAPTER 4

4

Releasing the Surface to Dabacon

When a new project is started, no surface definition exists. The empty folder structure is created and the references to the folders are defined in the D065 file generated by the Project Creation Wizard. The definition of the surface can now be carried out by creating a Project group and starting a new surface definition.

If a surface has already been created in Stand-alone mode then the files can be copied to the folder referenced by the variable SB_NAVARCH.

From the Start Menu select All Programs > AVEVA Marine > Engineer > Initial Design 12.1 > Project Tool the following form is displayed showing the current projects:

Right click on Projects and select New > Project.

The following form is displayed:

Key in the Project Name, then browse to the Project Folder containing the surface files.

Ensure Register Designs is checked to register the design with the current project.

The Design Defaults form is now displayed, simply click Cancel if you are opening an existing project. The new project name is now displayed, it is not yet current. To make the new project current, right click on the project name and click Select, the project is now displayed in red and is current.

(22)

www.aveva.com

The Display Registered Designs Only box is checked and the surface file displayed for the selected

project.

To associate the Initial Design project with the dabacon project right click on the project name and click

Associate.

The following form will be displayed:

Check the Associate AMA with Dabacon project check box and key in the Dabacon Project name and Preferred mdb. Click OK.

The surface file can be opened from the Surface and Compartment application and design elements .

If the elements have already been marked for release then the project can be released from the Initial Design Project Tool, right click on the surface file and click Release as shown below:

Check the option Dabacon project AMA then click Yes.

As the surface is being referenced directly from the database it cessary to release the files to the Initial Design project.

Lines files can be associated and released in the same way.

In the example above the project AMA has been created, and references are made to the AMA surfaces and project structure, this reference should be replaced with your project name.

(23)

www.aveva.com

CHAPTER 5

5

Hull program defaults

After the installation of the software and the selection of a project, any of the hull programs can be started. It should be noted that default files control the appearance/behaviour of the majority of the applications. These files reside in the directory associated with the project variable SB_SHIP.

Unless you are doing AVEVA Marine work for various clients it is envisaged these default files will be set up once to suit your standards/requirements and are added to your project template. If you are doing work for various clients that demand different standards/requirements then each client could be allocated a project template in which all the program defaults are set to suit that particular client.

Note that for the general functions common to all interactive AVEVA Marine Hull applications a default file named SBD_DEF1 exists, this file is described in the User Guides AVEVA Marine; 2D Drawing; Marine es; Appendices; Drafting Default File Keywords.

It is recommended to set a true type font through the Admin module (see TM-2120 System Administration (Basic), and set this as the default value for the drafting default setting TEXT_FONT.

5.1

Planar Hull Modelling (sj001)

The default file for Planar Hull Modelling is called sj001.sbd and resides in the SB_SHIP directory. The file is an ordinary text file and can be created and maintained with a standard editor. The file may contain a number of different parameters, in some cases with assigned values. If a parameter is given in the file, this means that the default action controlled by the parameter or the default value associated with the parameter is superseded. Inversely, if the parameter is not given in the default file, the default action or default value of the system is valid.

The following rules must be followed when parameters are specified in the file: Values assigned to parameters must be preceded by an equal sign (=). Commas separate multiple values.

Parameters and their assigned values are separated by a carriage return. The order of parameters is irrelevant.

An extract from a sj001.sbd file is shown below: STORE_FR

DRAW_PAN = DEFINED SCH_CREATE

STORE_FR:When a frame number defines a value along the X-axis, the value is translated to a pure number before storing it. This means that if the frame table is then changed, the value will translate back to another frame number. To avoid this, STORE_FR can be used to actually store the frame number. This will make the panel definition follow changes in the frame table.

DRAW_PAN=DEFINED:This parameter controls the drawing of panels in a view. When set toDEFINED seams, cut-outs and notches are drawn as components. When using symbolic view > create in Planar Hull Modelling the setting here will appear as the default in the menus.

SCH_CREATE:When given, and the function "Panel Store" is used, the input scheme will be created from the panel

For a full list of all possible parameters and an explanation for each, please refer to User Guides Modelling, Parameters, General Purpose.

When creating views in Planar Hull, information regarding what is displayed in the views can be modified using the View Properties dialogue box. These properties can be set within the sj001.sbd to automatically remove unwanted markings.

For further information seeUser Guides AVEVA Marine; Hull Detail Design; Planar Modelling; fault File of Planar Hull Modelling; Parameters; Picture Derivation

(24)

www.aveva.com

5.1.1 Excess

The symbols displayed in drawings where excess has been defined, and the names listed when selecting the excess types are controlled via the Planar Hull Modeling default file (sj001). Up to 5 different excess types can be defined.

EXC_TYPE_1 = panel, 80 EXC_TYPE_2 = assembly, 83 EXC_TYPE_3 = erection, 84

In the example shown above, the names displayed when selecting the excess types would be PANEL, ASSEMBLY or ERECTION. The symbols displayed would be symbol 80, 83, and 84 respectively, these symbols all belong to font 92.

5.1.2 Excluding blocks

When creating views in Hull Modelling and extracting marking information for plates, AVEVA Marine searches all blocks for panels to be included in the view. A facility exists to exclude panels at block level (these may be construction aids or supports that should not be included in drawing or marking outputs, a separate block should be created to define these items, to allow the use of this facility).

The environmental variable SBH_EXCLUDE_BLOCKS should be assigned to a file which contains the names of the blocks (one block name per row). These items will now be excluded from hull views and outputs using ppanparts and cpanparts.

5.2

Curved Hull Modelling (sh700)

The default file for Curved Hull Modelling is called sh700.sbd and resides in the SB_SHIP directory. The file is an ordinary text file and can be created and maintained with a standard editor. The file may contain a number of different parameters, in some cases with assigned values. If a parameter is given in the file, this means that the default action controlled by the parameter or the default value associated with the parameter is superseded. Inversely, if the parameter is not given in the default file, the default action or default value of the system is valid.

The following rules must be followed when parameters are specified in the file: Values assigned to parameters must be preceded by an equal sign (=). Commas separate multiple values.

Parameters and their assigned values are separated from other parameters by carriage return. The order of parameters is irrelevant.

An extract from a sh700.sbd file is shown below: BEV_LINE_SYMBOL

LP_TERM_OUT=0 SHX_PARTITION=4000

BEV_LINE_SYMBOL: When given, bevel symbols will be drawn in symbolic views in the same way as in separate generation, even if the extended bevel handling is used.

LP_TERM_OUT=0: Y and Z-co-ordinates can be described as LP-terms in system generated output. The value 0 indicates LP-terms with a possible offset will be used.

SHX_PARTITION=4000: The shell expansion view is created by development along frame curves. The density of the development curves can be controlled. The magnitude of the partition between curves is controlled via the default value (the exact positions of the development curves are selected from certain criteria within the program). If not given, 5000 is used.

For a full list of all possible parameters and an explanation for each, please refer to the User Guides of Curved Hull; Parameters; General Purpose.

(25)

AVEVA Marine (12.1) Project Administration (Hull) (TM-2122)

www.aveva.com

5.3

Hull Structural Design (sj700)

The default file for Hull Structural Design is called sj700.sbd and resides in the SB_SHIP directory. The contents of this file is restricted by the same rules previously explained for Planar and Curved Hull Modelling. For a list of all available parameters please refer to the previously mentioned chapters of the Planar and Curved Hull s.

5.4

Plate Nesting (se001)

The default information is stored as one assignment statement per row in the default file. An assignment statement consists of a keyword identifying the variable followed by an equal sign, followed by the default value. Since the default information is identified by a keyword, the order of the default information in the default file is irrelevant.

The default system is divided into two levels with a default file for each. The higher, superior level (the system manager level) consists of global default variables that may not be changed by the operator. The inferior level consists of default variables that may be interactively changed by the operator while in the Nesting application.

The superior default file must be assigned to the logical variable SBH_NEST_DEF1 and the inferior default file to the logical variable SBH_NEST_DEF2.

Where multiple burning machines are used with different default values, the SBH_BURNER_DATA file is used to allocate the correct defaults to the selected burning machine, additional defaults can also be defined for different plate thickness ranges using one burning machine, these level 1 and level 2 default files can be freely named and should be stored in the SB_SHIP directory.

An extract from a SBH_NEST_DEF1 file is shown below: DIRECTION_DEF=1234567 DIRECTION_NAME1=TOP DIRECTION_NAME2=BOTTOM DIRECTION_NAME3=FORE DIRECTION_NAME4=AFT DIRECTION_NAME5=CL DIRECTION_NAME6=PS DIRECTION_NAME7=SB

DIRECTION_DEF: The default parameter DIRECTION_DEF indicates the directions that should be

available when directions are inserted into the burning sketch. To get all directions the parameter shall have the value

1234567. If only TOP, AFT, CL and SB are to be shown then the value should be 1457. The order in which numbers are given is irrelevant.

DIRECTION_NAME1 TOP DIRECTION_NAME2 BOTTOM DIRECTION_NAME3 FORE

DIRECTION_NAME4 AFT Text associated with each direction. DIRECTION_NAME5 CL

DIRECTION_NAME6 PS DIRECTION_NAME7 SB

For a full list of all possible parameters and an explanation for each, please refer to the User Guides AVEVA Marine; Hull Detailed Design; Manufacturing; Nesting; Hull Plate Nesting; Initialisations for Nesting; Defaults.

As well as the controlling default files mentioned above, a file has to be set up to define the burning machine data. Any number of burning machines can be handled. The complete file name should be assigned to the environment variable SBH_BURNER_DATA.

(26)

www.aveva.com

For a full list of all possible parameters and an explanation for each, please refer to the User Guides AVEVA Marine; Hull Detailed Design; Manufacturing; Nesting; Hull Plate Nesting; Initialisations for Nesting; The Burner Machine Data.

5.5

Generic Post Processor (sf001)

The Generic Post Processor (GPP) [sf001.exe] reads data files in the generic file format. These generic file are generated by the AVEVA Hull Nesting application. The GPP is controlled by user-defined machine configuration data file(s), and produces output files containing NC machine instructions (ESSI or EIA format) to drive a variety of 2-axis burning machines.

To run the GPP the user must have a default data file specified and optionally a kerf data file specified. Default data file

The Default data file contains parameters specifying the machine controller and variant, burner type, format of output, machine restrictions and fixed speeds. This file is tailored by the user to suit the particular

requirements of the machine controller.

The file must appear in the directory assigned to SB_SHIP and the default file extension must be .def. The parameter GPP_CTRL_FILE (in the nesting default file SBH_NEST_DEF1 or SBH_NEST_DEF2) must also point to this file. This time only the file name and extension should be given in single apostrophes the system will automatically look in the SB_SHIP directory for this file. If this parameter is not set then the Generic Post Processor cannot be ran interactively from within the Nesting application.

Where multiple burning machines are used with different default values, the SBH_BURNER_DATA file is used to allocate the correct defaults to the selected burning machine, the GPP_CTRL_FILE referenced in these additional default files should also exist in the SB_SHIP directory.

Kerf Data File

For certain combinations of controller and variant a Kerf data file is required to determine various values (e.g. Kerf pre-select offset values and burning speeds) for a given plate thickness and bevel side, angle and depth. The value(s) are retrieved from the file and in some cases interpolated from values in the file. The user, from experience, normally creates the Kerf data file. The expected format is decided by the assignments to CONTROLLER and VARIANT in the default data file.

This file, if defined, should be assigned to SBH_GPP_KERF.

The default directory is SB_SHIP and the default file extension is def.

For a full explanation of the make-up of these files, please refer to the User Guides AVEVA Marine; Hull Detailed Design; Manufacturing, Post Processors, Generic Postprocessor.

(27)

www.aveva.com

CHAPTER 6

6

Hull Drawings

6.1

Drawing Databases

Generally hull drawings will be saved to the first writeable PADD database, the default being SB_PDB, in department General and registry MarDwg in the example shown below.

Departmen

allow the dept;regi elements to be defined in the correct PADD. When saving drawings the system will look in the current mdb

For hull production programs to store drawings in individual database locations can be assigned for each type of output. Variables defined in the D065 file control where the different drawing types will be saved, an example is shown below, the variable given for the db location is fixed, however the department and registry can be freely named.

Hull drawings.

SB_PDB SB_PDB Fixed system name.

SB_PDB_PADD General;MarDwg Dept;Regi can be freely named. Additional drawing storage area for design drawings.

SB_PDB001_PADD EarlyDesign;ClassDwg Assembly drawings produced using the hull interface.

SB_ASSPDB SB_ASSPDB

SB_ASSPDB_PADD Assembly;AssemblyDwg Nested plate drawings.

SB_NPL_DWG SB_NPL_DWG SB_NPL_DWG_PADD NestPlt;NplDwg Bending template drawings.

SBH_BENDTEMPL_DWG SBH_BENDTEMPL_DWG

SBH_BENDTEMPL_DWG_PADD BendTemp;BendDwg Curved plate drawings.

SBH_CPART_DWG SBH_CPART_DWG

SBH_CPART_DWG_PADD Cpart;CpartDwg Hull Markings drawings.

SBH_MARK_PICT SBH_MARK_PICT SBH_MARK_PICT_PADD HullMark;HullMarkDwg Profile nesting sketches.

SBH_NSKETCH_DWG SBH_NSKETCH_DWG

SBH_NSKETCH_DWG_PADD ProfNest;ProfNestSk Part list drawings.

SBH_PARTLIST_DWG SBH_PARTLIST_DWG SBH_PARTLIST_DWG_PADD PartList;PListDwg Pinjig drawings.

SBH_PINJIG_DWG SBH_PINJIG_DWG

(28)

www.aveva.com

Plate jig drawings.

SBH_PLJIG_DWG SBH_PLJIG_DWG

SBH_PLJIG_DWG_PADD PlateJig;PlJigDwg Planar panel parts drawings.

SBH_PPART_DWG SBH_PPART_DWG

SBH_PPART_DWG_PADD PPart;PPartDwg Profile sketch drawings.

SBH_PSKETCH_DWG SBH_PSKETCH_DWG

SBH_PSKETCH_DWG_PADD ProfSketch;ProfSk Weight and centre of gravity drawings.

SBH_WCOG_DWG SBH_WCOG_DWG

SBH_WCOG_DWG_PADD WeightCoG;WCoGDwg 3 Axis nesting sketches.

SBH_3AX_SKETCHDB SBH_3AX_SKETCHDB SBH_3AX_SKETCHDB_PADD 3AxNest;3AxNestDwg

6.2

Drawing Registry

It is recommended that the maximum number of drawings in a single REGI should not exceed 1000, this can be controlled by the setting of MAX_DWGS_IN_REGI :1000 in the drafting default file (the default value is 1000). The new REGI s will have the same name as the original one but with a number suffix. Following the

Hull drawings example where the REGI for General d:

MarDwg_001, MarDwg_002, MarDwg_003 etc.

6.3

Production sketches naming rules

Drawings generated by the production programs are automatically named. Naming rules are created by system administrator and controlled via file assigned to SBH_DWGNAME_RULES.

Naming rules are defined individually for a number of applications. Each rule consists of a keyword identifying the application, followed by a number of attributes defining how the name is built up. The following keywords identify the applications for which rules may be defined:

PPAN Plane panel parts generation CPAN Curved panel parts generation PART_PLATE Plate parts list

PART_PROFILE Profile parts list

WCOG Weight and centre of gravity report

PROF_SKETCH Profile sketches when one profile is drawn on each form COMB_PSKETCH Combined profile sketches

PROF_NEST Profile nesting receipt sketches

BENDTPL Bending templates

CROSS_BENDTPL Cross bending templates JIGPILLAR Jig pillar sketches PLATEJIG Plate jig sketches NEST3AX Nesting 3-axis sketches

The naming rule attributes define how a sketch name should be generated. The rule attributes are applied in the order they are given in the rule. Only rule attributes valid for the application may be given. Resulting values of each rule attribute are concatenated.

(29)

AVEVA Marine (12.1) Project Administration (Hull) (TM-2122)

www.aveva.com

A rule attribute consists of a slash (/) and a keyword in some cases followed by an equal sign (=) and a

string or a number. The last rule attribute of a rule is followed by a semicolon (;). Rule attributes and resulting value:

/AUTO_SEQNO=<length> Next drawing sequence number of the running application. Formatted with leading zeros in order to form a string of <length> characters. See also (Link to 5.3.11 Setup for automatic naming of production sketches)

/BLOCK_NAME Block name.

/COMPUTER=<no> The <no> last characters of the name of the executing computer.

/COMPUTER The whole computer name.

/COUNTNO Value of counter incremented by running application. Any text.

/FULL_PARTNAME Full part name.

/JOBNO The job number of the started batch job.

/OBJECT_NAME Name of the object being handled by the application.

/PAGENO For sketches consisting of 2 or more pages the result of this attribute will be <current page no>(<total number of pages>).

As previous but result will be <current page no>[<total number of pages>]. /SHORT_PARTNAME Short part name.

There are restrictions on how naming rules may be composed. Some attributes may be used only in a few types of rules while other may be used in almost all types of rules.

/COUNTNO is allowed only for PROF_SKETCH, COMB_PSKETCH and BENDTPL.

/FULL_PARTNAME, /SHORT_PARTNAME and /OBJECT_NAME may be used only for CPAN, PROF_SKETCH and NEST3AX. However only one of the attributes may be used in the same rule. /BLOCK_NAME may be used in CPAN, WCOG, PART_PLATE, PART_PROFILE, PROF_SKETCH, COMB_PSKETCH and NEST3AX rules.

/COMPUTER and /JOBNO may be used in all rules but PROF_SKETCH and COMB_PSKETCH rules. /PAGENO may not be used in PPAN, PROF_NEST and CROSS_BENDTPL rules.

/AUTO_SEQNO and /DELIMITER may be used in all rules.

If a naming rule has not been defined for an application then a default rule will be applied. The following default rules are automatically defined:

CPAN /OBJECT_NAME /DELIM='_' /PAGENO;

PART_PLATE /DELIM='PL_' /AUTO_SEQNO=6 /DELIM='_' /PAGENO; PART_PROFILE /DELIM='PR_' /AUTO_SEQNO=6 /DELIM='_' /PAGENO; WCOG /DELIM='WCOG_' /AUTO_SEQNO=6 /DELIM='_' /PAGENO;

PROF_SKETCH /OBJECT_NAME /DELIMITER='_' /COUNTNO /DELIM='_' /PAGENO; COMB_PSKETCH /BLOCK_NAME /DELIM='_' /AUTO_SEQNO=6 /DELIM='_' /PAGENO;

/PAGENO;

CROSS_BENDTPL /OBJECT_

NEST3AX /OBJECT_NAME /DELIM='_' /PAGENO;

6.4

Shell Expansion Drawing

The Shell Expansion drawing image produced from symbolic view, can be controlled using these defaults: SHX_DRAW_PLATES SHX_SHOW_POSNO and SHX_SHOW_MATQ

(30)

www.aveva.com

6.5

Settings Drawings

Settings drawings are a special case and are stored in the STDWLD which is in a DESI type db, unlike the other drawings which are stored in a PADD type db. The variable setting for this is as shown below.

SB_SETTINGS_DB SB_SETTINGS_DB

Sequential database files (.sbd) can be transferred to dabacon using the utility SA004, using the AVEVA command prompt.

Open the AVEVA command prompt, ensure the current folder is: C:\AVEVA\Marine\OH12.1.1.

Execute SA004 giving the project name, mdb, user and password as shown below. Then follow the prompts displayed in the command window. An example is shown where the .sdb file __SBH_PROF_TYPES__ is being copied from folder C:\Temp\SETT\ into the SB_SETTINGS_DB of the MAR project. Where input appears empty below, just press enter/return to move to the next line.

Note: the DESI db containing the STDWLD should be included in the mdb which is accessed when executing SA004 from the AVEVA

/HADMIN in the example below.

Once the drawings have been imported they can be opened from the Settings drawings db by selecting the

Drawing type: Settings drawing, then clicking List. Select the required drawing then click Open

(31)

www.aveva.com

CHAPTER 7

7

Hull PPI Programs

7.1

Plane Part Generation (sf416d)

The default file for Plane Part Generation is called ppanparts.ip and resides in the SB_SHIP directory. This program splits plane panels into their individual plate and profile parts. The plate and profile parts will also be supplied with marking in this function, all automatically evaluated from the model.

Parameters for this program are given in an ordinary ASCII file. An extract from a ppanparts.ip file is shown below:

SHRINKAGE, SBSHRINK, SPLIT_BEVEL_INFO, SPLIT_EXCESS_INFO, HULLMARKINGS,

SHRINKAGE, SBSHRINK,With this parameter given, this program will handle the compensation for shrinkage. In this example SBSHRINK is the name of the object containing data for shrinkage compensation.

An empty string should be given if no object exists.

SPLIT_BEVEL_INFO, Bevel information (normally defined for each limit of a plate, if any defined) will be split into more accurate intervals, taking the geometry of cutouts, holes, etc. into consideration.

SPLIT_BEVEL_INFO must be given if the bevel information function should work properly in the Nesting system.

SPLIT_EXCESS_INFO,Excess information (normally defined for a whole limit) will be split into more accurate intervals, taking the geometry of cutouts, holes, etc. into consideration.

HULLMARKINGS,For hull marking information to be presented on planar plate parts

For a full list of all possible parameters and an explanation for each, please refer to the User Guides AVEVA Marine; Hull Detailed Design; Manufacturing, Manufacturing of Plane Panel Parts; Plane Panel Parts; Set-up of Program; Set-up of the IP file

7.2

Parts Lists (sf101d)

There is no designated parameter file to control the Parts List program. However a number of steps, AVEVA Marine objects, drawing forms, etc must be in place to allow the functioning of the program.

Before running the Parts List program ensure:

The parts to be listed have been processed through the Plane Parts Generation program. If the planar panels have not been split then nothing will appear in the parts list.

The object __TB_PARTNAME_CTRL__ exists in the SB_OGDB. This object dictates the make-up of the resulting part names.

Note: if the__TB_PARTNAME_CTRL__object is using positions numbers in the final part name then ensure position numbers have been allocated to the relevant parts.

As well as producing CSV lists, the system also creates a drawing for the resulting plate parts and a drawing for the resulting profile parts. For the system to produce these drawings the necessary drawing forms must exist in the SBD_STD

Figure

Updating...

References

Updating...