Options are used in a Concurrent Design activity to model the identified promising solution directions for the design.
This section describes the management actions for these options.
Options are defined as:
representation of an option that is a potential design solution for the system-of-interest being developed in an Iteration of an EngineeringModel
[...] a design alternative that can be compared with one or more other design alternatives defined in other Options, for example to perform a trade analysis1
The notion of options is connected to a Concurrent Design activity. This has an implication for the use and availability of options in different model kinds of engineering models. In a Scratch, Template or Study Model, options can be defined and used without any restrictions. A Model Catalogue is intended to store design items that are reusable in multiple Concurrent Design activities. In this sense, these design items will be independent of the specific options in other engineering models as design solutions for different Concurrent Design activities and of the elaboration of these options in iterations. For this reason,
a catalogue may have only one iteration (represented by a combination of IterationSetup and Iteration), and one Option.2
Please note that also any information in state value sets for parameters that are state dependent in an engineering model will be discarded when copying an element definition into a Catalogue Model.
Design options allow the team of domain engineers to investigate different engineering solutions for an activity. In every newly created engineering model the standard option Default Option is created. This is the base option within a new engineering model at the start of a new engineering model for a CD activity, if not using a template model with predefined options, or copying from an existing engineering modelManage_EM. Whenever a different engineering solution is investigated within a CD activity it is possible to create a new option in the engineering model, see below for details. Options are handled below the level of iterations within an engineering model. The information related to these options and the option dependencies within the engineering model are stored within the iterations.
Open the Option browser by selecting the Options icon on the Model tab. This will show all the available options. It is possible to set one of the options as default option. This default option is given in bold font in the list of options.
To create a new option, select the Create Option icon or in the context menu select Create an Option.
On the Basic tab, provide the mandatory fields for Name and Short Name.
Optionally, a category can be applied to the option. To do this, provide the applicable category or categories by selecting these on the Categories tab. Given on this tab are only the categories that can be applied to options. This is done by including options in the list of permissible classes in managing the [categories][Cat].
The option modal dialogs further have the generic functionality on the Aliases, Definitions and HyperLinks tabs, described in the topic standard tabs.
For any new option that is added to an iteration of the engineering model, the relevant items are updated to include it. The element usages will be updated, where these will all be set to be included for the new option. Make sure to review the list of applicable element usages after creating a new option if this is required. See the description below on the inclusion or excluding of element usages in the option trees, or the explanation on the topic of managing element usages and element definitions). Further, the parameters that were set as having an option dependency will automatically be updated with a placeholder value for the new option.
To edit an option, select the Edit option icon or in the context menu select Edit. It is possible to edit the Name and the Short Name on the Basic tabs, the applicable categories on the Categories tab, as well as optional items on the other tabs for Aliases, Definitions, and Hyperlinks.
After making the required changes, click Ok.
On the Advanced tab, a Revision Number is given; see the description of [Revision Number][Rev_Num] for details.
The Advanced tab provides information that may be useful mostly to CDP™ database administrators. Given are the UniqueID and the [Revision Number][Rev_Num].
To delete an option, select the Delete Option icon or in the context menu select Delete.
When an option is deleted from the CDP™ database, it will actually be removed from the data that is stored in the CDP™ database from that point onwards.
Note that deleting an option will also delete all its related information. The option tree with all the nested elements as included element usages as well as the parameter values for that specific option for any parameter that is option dependent will be removed.
To export options, select the Export Option icon.
The options are used in the engineering model to allow a form of "configuration management" to express differences and explore variations in it. This is done by setting option dependencies on design items.
This option dependency can be used and applied at various levels:
For each Element Usage, an indication can be given for their option dependency.
This is used to indicate if the Element Usage as a whole is included or excluded from a specific option.
For each Parameter, an indication can be given for their option dependency.
If this is applied, a value set will be created for the parameter with a placeholder value for each option in the engineering model.
In the Element Definition Browser, an indication is given of the option dependency of element usages. If an element usage is included in all options, this is indicated with the green circles icon, if used in none of the options a blue list icon, and if not used in any of the options a red cross icon.
To edit the element usage for the option dependency, clicking on the icon will display a drop-down menu with the available options. Use the check box to include or exclude the element usage for each specific option.
To set the option-dependency of a parameter, see the description of managing parameters.
The option dependencies of Element Usages and Parameters are used to generate option-specific trees. To generate these option-specific trees, it is needed to set one Element Definition as Top Element. To set this, select the Element Definition, in the context menu select Edit. On the Edit Element Definition modal dialog, tick the check box Is Top Element. This top element will be the starting point for all the option-specific trees. Only the element usages that are indicated to belong to a specific option will be represented in the tree view. For the parameters, the general value from the element usage will be represented for parameters without option-dependency. For parameters with the option-dependency set, from the full value set of the parameter the specific value for the option will be represented in the option-specific tree.
Last modified 4 years ago.