The main design activities in a Concurrent Design study are performed by the design team within the frame of an Engineering Model. This section describes typical use of the different possible combinations of Model Kinds and Study Phases for engineering models.
More information is given in the related topics of managing engineering model setups on the high level administrative actions, and the setup of engineering models on creating and updating the actual design data model in the engineering model.
For a Scratch and Study Model, depending on the setting of the Study Phase, full functionality is available to e.g.
A Template Model can only contain one Iteration, as mentioned in the description of Model Kinds. If a scatch or study_ engineering model with multiple iterations is turned into a template model, only the active iteration will be kept.
Apart from the possibility to use iterations, all other functionality is available to e.g.:
A Model Catalogue is intended to allow reuse of element definitions. A model catalogue can only contain one Iteration, and only one Option within this iteration, as mentioned in the description of Model Kinds.
A Scratch Model could typically be used to setup and prepare engineering models, very likely outside the scope of an actual [Concurrent Design Activity][CD_A]. If this type of model is used in a [Concurrent Design Activity][CD_A], since no suitable study Model or Template Model is available to start from, it may well be that a Scratch Model is initially used for the preparations, with the Study Phase indeed set to Preparation Phase. It is advisable however to not use a Scratch Model too long within the scope of an actual Concurrent Design activity, but to turn this into a Study Model as soon as possible; in any case when starting the Design Sessions Phase. Please note that outside the scope of an actual Concurrent Design activity, it may make good sense to use the other Study Phase indications as well, e.g. for testing purposes, especially since different phases have differences in possible functionalities.
Setting up and updating a set of template models can be used to facilitate a successful start of new Concurrent Design studies supporting different types of projects (e.g. development of hardware vs. more software oriented projects), application fields (e.g. develop a business case, develop proposals, support planning activities, create a design) or complying to other phases (e.g. in a preliminary/ conceptual design phase or a subsequent detailed engineering phase). Other types of projects or applications may lead to (very) different sets of parameters that need to be exchanged between disciplines. There may also be a need to follow other or different (industry or organizational) standards or approaches. As an example, specific sets of parameter types can be created in the model RDL of two or more template models. Any engineering model that is created based on any of these templates will have the possibility to use that particular set to create parameters, as it is in the chain of RDLs, while not having access to the sets in the other template model RDLs. The use of a template model therefore provides a possibility to define and use specific sets for different types of projects, without cluttering the set of parameters for other (types of) projects that have no use for these parameter sets.
For a Catalogue Model,
When a new [engineering model is being created][Create_EM], the Model Kind is by default preselected as a Study Model in Preparation Phase. This would be a typical situation for new engineering models that are being created for new Concurrent Design studies, that are based on an already available engineering models, most likely a Template Model, another Study Model or a suitable Scratch Model.
These source engineering models will have to be available on the CDP™4 Database for the hosting organization(s). If no (suitable) source models are available yet, these will have to be created.
In this case, it will be possible to create a Study Model, but a preferred approach can be to create a Scratch Model to be used to prepare and setup a suitable engineering model first. It is up to the organization to choose if it is preferred to do this within the scope of an existing Concurrent Design study, or as a separate tasks in managing a Concurrent Design centre. In any case, having an engineering model as a Scratch Model can be used to provide a clear indication that the engineering model is (still) 'under construction'. When the quality and level of detail of a Scratch Model is sufficient to be used, it can then be edited to become e.g. a Study Model or it can be turned into a Template Model to serve as a basis for multiple new engineering models that benefit from the available setup.
It is in principle likewise possible to directly create a Catalogue or Template Model that is empty and to build this up gradually in the engineering model itself. For the reasons given here above about a clearer indication of the status, it is advisable however to always first create these models as Scratch Model as well, before turning them into the desired Model Kind. This would give users a better idea of which engineering models may be more useable, complete and useful for their tasks.
It has to be understood however that engineering models in general are never "finished" and will be continuously updated, upgraded and improved. Minor updates can usually be done within an existing Catalogue Model or Template Model. For major changes it may be advisable to turn the Template Model into a Scratch Model. This will allow making and testing the changes and adaptations, before changing back to a full Catalogue or Template. It is up to organizations and/or individual users managing various engineering models to define a more fixed or more open approach to handle management of engineering models.
Last modified 1 year ago.