Databases and World Elements Used in Assembly Planning
- Last UpdatedNov 30, 2023
- 1 minute read
The table below shows the databases and world elements used in Assembly Planning.
|
Database type |
World element type |
Description |
Contents |
Assembly Planning user access |
Hull & Design user access |
Project setup recommendations. Single location. |
Project setup recommendations. Collaboration project. Multiple locations |
|
DESI |
ASWLD |
Assembly World |
Assembly hierarchy with assembly nodes |
Write access for those working with Assembly Planning |
Read access for anyone who wants to access Assembly data (for example, Hull design users, Weld Planning users, ….) |
Assembly worlds should be in one or more separate databases, dedicated for assemblies.. Case 1: The ship is divided into zones. One team is working within one zone, doing both Hull design and Assembly Planning. One assembly world/one assembly database per zone. Case 2: One assembly database/one assembly world for the whole ship. |
Same as single location |
|
CATA |
General part (GPART), which can be used in Assembly Planning. |
Read access for Assembly Planning users. |
|||||
|
DESI |
LINKWL |
Link World |
Link Assembly to their associated output that means, Drawings and Parts Lists |
Write access for those working with Assembly Drawings |
One data\-base dedicated for assembly links. |
||
|
PADD |
Assembly Drawings |
Write access for those working with Assembly Drawings. |
for further information, see Drafting database setup. |
||||
|
NSEQ |
SEQWOR |
Name Sequence World |
Name sequences for Assembly Drawings |
Write access for those who create assembly drawings No access required for other users |
It is recommended to have one Name Sequence database for all Named Sequences within a project. |
One Name Sequence datafbase per location. Note that each location needs to have its own predefined unique sequence interval. |