The Functional Use of CRM

There are different functional properties and definitions that are needed to get the model in a state where it can be used in the design process. Depending on discipline and usage, these properties can vary and, in some cases, become contradictory. The CRM is therefore kept clean from all sorts of functional properties and this information is instead applied to a functional model layer, the Functional Arrangements as described in this document.

From a user perspective, this is made transparent by specialized application functions. Consider for example a marine structural designer that needs to subdivide the project with decks and bulkheads or modelling design seams in positions where a thickness change is needed. While doing this modelling, two design entities are created, a surface or a curve in CRM representing the geometry, but also a functional entity that can host the properties of the decks and bulkheads or seams. Later, more functional entities will be created referencing the same surfaces, for example when creating fire zone limits or subdividing into different compartments or design areas.

When the same marine structural designer is creating steel on one of the earlier created decks, the properties can be picked up from any of the related functional entities, but the actual reference stored with the created steel entity will be to the surface in the CRM.

When changing the project breakdown, for example moving decks or bulkheads in a ship, the design change is made in one place affecting the CRM entity. All other functional and physical entities can then easily be recreated to get the correct updated geometry