Blocks

• Block groups
  • Naming rules and limitations for block groups
  • Block numbers and names
• Block area and description
• Logistical database

When creating building blocks, each block must assigned to a block group, such as Hull, Foundation, or any other predefined block group that is made available. See Block groups for information on how to make block groups available for users.

The area of each block must be set when creating the block. The area settings can be changed later. It is possible to add a description to the block, if so desired.

The project manager can modify the block definitions in the System Management application with the Projects > Building Block Overview function. See Building Block Overview for more information.

The Tools > Information > Building Block Overview function in the 2D-Contek, 3D-Contek, Shell, and HiLTop applications gives users an overview of all the block groups and blocks with their descriptions (if any), and area definitions and default grids. Users cannot modify the block definitions unless the project manager has allowed it in System Management > Extra > Customize > Miscellaneous, by setting Building Block Overview - Modify to In All Applications.

Block groups

Before blocks are created, the available block groups must be defined in System Management with the Projects > Block Groups function. If no group names have been defined, a block will be assigned to group Hull.

Naming rules and limitations for block groups

The following rules and limitations apply to block group names.

• A block group name must be an alpha numeric string without spaces.
• A block group name cannot be a number, and texts All and Cancel are not allowed.
• A block group name is case insensitive.

Block numbers and names

A block name can be number based or name based from Hull V6.0 onwards. Block names defined in Hull V5.3 and earlier versions were always number based. The number must be a positive integer, and it may start with leading zeros, as in 00101. Whether block names are number or name based is defined when creating the project in Hull. See Project/Block.

Number based block naming

The name can contain alpha numeric characters, but the numeric part must be unique for each block in the project. The maximum block name length is 16 characters, and the maximum number of digits in the numeric part is 9. Examples:

• Names such as DoubleBottom100 and 123456789deck are valid number based block names.

• Names such as 100SB and 100PS are not valid number based block names because the numeric parts are identical.

Note: Blocks named as 99999 and 12346 can only be opened in the 2D-Contek application.

Name based block naming

The name can contain alpha numeric characters, and the numeric part does not have to be unique. Only the combination of the numeric and character parts must be unique. For example, 100SB and 100PS are allowed in the same project. The maximum block name length depends on how many characters are use in the name, as follows.

Limitations on using alphanumeric block naming

Hull always uses numeric block naming internally. Alpha characters in block names are converted to numeric characters so that A is converted to 11, B to 12, and so on. For example, block name 1111P will be converted to 111126 (because 26 represents character P). Likewise, ABC will be converted to 111213.

This means that it is possible that you try to use a block name that already exists. For example, if you have a block named 2212P, you cannot use block name LBP, because both will be converted to 221226. If such cases the system will display a "Block name already exists" error.

Block area and description

The block area is checked in specific occasions to make sure the items in the construction database are still inside the defined area. The actual construction area is compared to the (new) block area when changing from one block to another, when creating a new block, or when switching from one application to another, for example. In distributed projects, the changes are applied at other sites only when the block is saved and downloaded after replication.

The check is done, for example, when updating a construction within a drawing with Update and Update All. The blocks which are set to solid or dashed are checked for their area, to determine if the block area is (partly) inside the drawing area. If a block is inside the drawing area, it is updated. Block areas are also used when copying parts, and a good block area definition will improve copy performance. The principle is the same as when presenting parts.

If the construction area is larger than the newly defined block area in any direction, a dialog showing the original and new values opens. The user can keep the original values, accept the new values, or modify and then accept the new values. If the user closes the dialog, the change is canceled.

If the user accepts the new values, the changes are applied at other sites after the block has been saved.

The comparison between the block area and construction area is not done when the block has been opened in browser mode.

Logistical database

For a detailed description on how to define the logistical database layout see Defining the logistical database layout in the Managing Production Information Administrator's Guide.