Main differences between COS and HDX

• Hull can now be run as stand-alone, without running any other processes. The COS server and an HCA are only needed when the data needs to be distributed.

• Data is not automatically transferred to/from COS. Hull engineers now decide when work in a given block has advanced enough for the data to be saved into COS and distributed to other sites.

• The permissions for accessing applications and functions are not as detailed in the COS setup. Across sites, access is handled by COS with checkouts/checkins. Within sites, access is managed by a file-based locking mechanism.

• In System Management, two users can define the same settings at the same time. The changes saved last will then be applied. However, there are some exceptions:

  • Logistical Database Layout/Logistical Fields Options: These settings can only be modified when all blocks and general project data (Hull project general) are checked out, and no users are present in any of the blocks.

  • Activate Database/Update Database: In distributed projects shapes can be updated and saved if the Hull Shape is checked out..

  • The following functions require the general project data (Hull Project General) to be checked out besides the logistical functions mentioned above:

    • Grid Manager

    • Flexi Weight

    • Setting custom attributes

    • Send settings to Outfitting

    • Setting object number

    • Setting Reversed Frame

  • For all block management-related functions, the appropriate blocks need to be checked out.

• System Management password protection

• Outfitting integration:

  • The Send to Outfitting function no longer exists. For Hull data, the integration with CADMATIC Outfitting is handled via the Check out and check in operations dialog.

  • The Outfitting user always owns the holes; only the Outfitting user has full control over the shape and size of the holes.