by mbm - 2011/10/25 20:15

The purpose of this checklist is to provide general guidelines to check a module. Some of the checks are on-going, some of should be performed once a week or when the module is finished and PI is ready to be started.

1. Check section specifications and ploo heights

- Use “Utilities > Lists”- function to select elements

2. Check positions

- Use “Utilities > Reports”- function to select elements

- Position of SITE/ZONE/STRU has to be 0,0,0 WRT WORLD

3. Add all surrounding structures by discipline

- Add all volumes within 1000 mm box for visual check

4. Delete empty elements

- Use “Utilities > Lists”- function to select elements STRU/FRMW/SBFR/PANE/PLOO without members

5. Update connections

- Use “Position > Align Secondary Nodes”- function in Site- level

6. Set material references

- Use “Utilities > Lists”- function to select elements FRMW/SCTN/PANE or

“Modify > Material”- function

7. Check sections without SPREF or length less than 100 mm

- Use “Utilities > Lists”- function to select elements

8. Check section end connections

- Use “Query > End Connections”- function

9. Make section ends perpendicular in bracing (KBR)

- Use “Utilities > Lists”- function to select elements

10. Tidy Model

- Use “Delete > Tidy Joints” and “Delete > Tidy Nodes”- functions


- For term explanations, see “PDMS Terms”

- For query commands, see “PDMS Query Commands”

- For detailed instructions how to use lists, see “PDMS Lists”

- For detailed instructions how to use reports, see “PDMS Reports”

Article written by Marko Ervonmaa


PDMS to Tribon modeling comparison

by mbm - 2011/10/16 21:15

1. Scope

The scope of this document is a simplified model comparison based on PDMS Structural Design and TRIBON Hull Design.

2. Purpose

The purpose of this document is to give an overview of two 3D- modeling systems and underline the differences between them.

3. General

PDMS provides powerful interactive functions, for example, Lists for model manipulation, whereas Tribon still heavily relies on manipulating of the schemes and batch modeling.

ConceptHierarchy (picture 1)Panel (scheme)
TopologyReference to element (picture 2) (Pline/Ppoint/Snode/Sjoint)Reference to name (Sur/Pln/Pan/Pan Part/Pnt)
Coordinate SystemAbsolute (X/Y/Z)Relative (FR/LP/LP)
StandardsCatalogue DatabaseStandards Database
PositioningPline/Ppoint > JustificationMould line > Material side
EditingElement (command window)Panel (scheme)
Model UpdatesAlign Snodes (picture 3)Recreate panel (scheme)
Model ChecksLists & ReportsPanels (schemes) & Utilities
View Types3D- view2D- & 3D- views
Object StatusClaimed/UnclaimedLocked/Unlocked
Build StrategyHierarchy within Design applicationWOP (separate application)
End ConnectionsSnodesEnd connection table
End CutsSjointsEnd cut table

Table 1, Model Comparison

Unknown Object

Picture 1, PDMS Structural Database Hierarchy

Picture 2, Plines for I-beam

Picture 3, Connection of sections


- Section 2 is connected to section 1.

- Justification (based on pline) is NA for section 1 and TOS for section 2.

- Position of section 2 is determined by justifications of sections 1 and 2,

see picture 2 above for possible justifications for I-beam.

- Snode (asterisk in picture 3) determines the end connection (length) for section 2 and is

based on pline rule when connecting sections.

- SJoint (arrow line in picture 3) has the connection reference (CREF) pointing to section 2

and determines the end cut, which in turn is based on specification reference (SPREF).

- Plines correspond topology points in Tribon in a sense of referring to an existing

profile, but elements modeled using plines do not get updated, but only initially positioned.

- For additional information, refer to “PDMS Terms”, “PDMS Query Commands”,

“PDMS Lists” or “PDMS Reports”.

Article written by Marko Ervonmaa

MBM Project migration 2017

by mbm - 2017/01/05 17:46

Today 5 January 2017 MBM Project starts migration to purposely build web site & blog platform based on MS ASP .NET & C# . Some of the old pages with obsolete information will be dropped. Some will be kept for reference. During the migration due to different platforms the information in the old articles might be partially lost or with changed formatting. Users' comments will not be transferred to the new site.