Hull objects

Hull Block List

The hull block list is represented by a single COS object, Hull Block List. This object stores the projectinfo.xml file as application data. In each project, there is only one Hull Block List object, which contains the block numbers belonging to it.

Note: Only the list of blocks in their respective block groups and the index are saved as an object. All the other data is saved as attributes in the Hull Block object.

Hull Block

Data belonging to a hull block is stored in the following object types: Hull Block, Hull Construction Part, Weld, and Model Group. The construction database is stored as an attachment.

A single COS object, Hull Block, exists for each block. This object stores the block metadata as attributes and all block data as attachments. The attributes of the block do not change but the attachments are updated when saving data to COS.

Hull Construction Part

There are individual Hull Construction Part objects for each logistical construction part in the block. Therefore, plates split by a seam will result in two separate Hull Construction Part objects, whereas two plates connected by a knuckle will result in one object. Because only physical objects are stored, all types of holes are excluded. Lugs only appear if the associated CGF files exist.

When saving a block, the .cgfx files are read by HCA and the data is extracted and stored in COS with the corresponding Hull Construction Part.

The construction parts are stored as a flat list without a hierarchy, that is, each part has its block as the parent.

Each custom attribute will be added to each construction part when saving the block.

Weld

Each individual weld in each individual construction part in the block is represented by a single COS object, Weld, which is also used by Plant Modeller. Welds reference two construction parts, but only welds referencing the primary part are created.

The welds are stored as a flat list with each weld being a parent to the block, not the construction part. The weld data contains the COS identifiers of both the main and secondary parts. If a weld references a secondary part from another block and the other block has not been saved to COS when saving the weld, a null identifier will be saved. The identifier is corrected when saving the weld again, if the other block has then been saved.

In addition to the Weld object, a single Model Group object representing the weld group is stored for each block. The object is of type Weld Group and contains a list of all the welds belonging to the block.

Work Breakdown Structure

The work breakdown structure in COS is a tree structure identical to the one shown in Hull Viewer. The structure is stored in the database by adding a Model Group object for each node in the tree, including the root representing the block. The leafs represented by the Hull Construction Part objects are not represented here. Each node in the tree apart from the root (since it has no parent), contains the identifier of its parent in the record structure.

Apart from the construction part level, each level in the tree is associated with a custom attribute with a value and type originating from the logistical database. For example, a node on the third level has the user-defined attribute defined in the work breakdown configuration file for that specific level. The user-defined attributes are registered to the COS database in System Management with the Projects > Outfitting > Hull Structure > Send Settings function.

Hull Plantek

Data belonging to a Hull Plantek is contained within the HullPlantek class.

Each Hull Plantek in a Hull project is represented by a single Hull Plantek COS object, which stores its attachments but contains no attributes. Only the Plantek models are stored; references to models are part of the block data.

Hull Line Range Subset

Each hull line range subset is represented by a single COS object, Hull Line Range Subset. Therefore, if there are two hull line range subsets, there are also two COS objects in the COS database.

A Hull Line Range Subset object stores information (name, description and subset identifier) about the hull line range subset as attributes. The hull line ranges of the subset are stored as text in the data part of the COS object.

Each Hull Line COS object also stores a reference to the corresponding Hull Line Range Subset object. This creates a relation/link between the hull line and the parent subset, and allows retrieving all hull lines belonging to that subset.

Hull Line

In general, hull lines can be seams, butts, dimension lines, or hull boundary lines. Each hull line is represented by a single COS object, Hull Line. This object stores the hull line metadata as attributes and the data as an attachment.

Each Hull Line object also stores a reference (identifier) to the Hull Line Range Subset object corresponding to the parent subset. This creates a relation/link between the hull line and the parent subset, and allows retrieving all hull lines belonging to that subset.

Hull Basic Data

There are three types of Hull Basic Data objects: Hull Norms, Hull Shape and Hull Project General. Each COS object type has a distinct database schema and at most one entry in the COS database. Each object type may contain one or more attachments.

The Hull Norms object contains the project norms. Norms contain project settings, and each project can contain multiple norm sets. Each block group uses one of the existing norm sets (the user can choose which one).

The Hull Shape object contains the active hull shape database.

The Hull Project General object contains high level project settings not stored in the norms (the name of the ship, for example).

Hole Request

Plant Modeller users create hole requests to notify Hull that holes need to be added in the construction data. The Hole Request objects indicate these requests.

Hole Request Response

Hull users create hole request responses to indicate the status of the holes requested by Plant Modeller users. The Hole Request Response objects indicate the progress on hole requests. Each Hole Request Response object refers to the corresponding Hole Request object.

Hull Document

The Hull Document object is a placeholder for different revisions of a single document. The Hull Document object is referenced from the Document Publication objects.

Document Publication

All the data needed when publishing a document to eShare is combined into a Document Publication object:

The document itself as a PDF file
Document meta data including a list of key values defining the (user-defined) properties of the document
Document link data consisting of a list of areas (boxes) on the document and a reference to one or multiple parts in the 3D model

A Document Publication object is created for each revision of a document.

The Document Publication object stores a reference to the Hull Document object.