- Documentation Home
- Introduction
- A Introduction
- B Concurrent Design Platform
- C Managing the CDP
- Application Layout
- Data Sources
- Engineering Models
- Log Information
- Notifications Feedback
- Refreshing Data
- Revision Number
- Session
- Site Directory
- Standard Tabs

- D Performing a CD Study
- E Special Topics
- Automate Computation Using Scripts
- Requirements

- F CDP4 Web API
- Glossary
- List of Acronyms

- Manage Finite States
- Introduction
- Possible Finite States
- Create Possible Finite State List
- Edit Possible Finite State List
- Inspect Possible Finite State List
- Delete Possible Finite State List
- Export Possible Finite State List
- Actual Finite States
- Create Actual Finite State List
- Edit Actual Finite State List
- Inspect Actual Finite State List
- Delete Actual Finite State List
- Export Actual Finite State List
- Notes on Using Finite State Lists
- Related Topics

**Plugin**:

The parametric design approach of the Concurrent Design methodology leads to a focus on the modelling of static behaviour. States have been introduced in the CDP™ to enable the modelling of dynamic behaviour.

States can be used to give a description of this dynamic behaviour, e.g. mission phases or system or equipment modes. The definition consists of the name of the list, with the associated states in that list.

This section describes the management actions for these states.

The usage of the states in the CDP™ is the following.
The definitions of each state list needs to be given in a *Possible Finite State List*.
Then combinations of *Possible Finite State Lists* can be made in *Actual Finite State Lists*.
The states in the actual finite state list are generated as all possible combinations from the finite states in the applicable Possible Finite State Lists.
Please note that for a single *Possible Finite State List*, this has to be created as an *Actual Finite State List* as well to be able to use it.

The *Actual Finite State Lists* can subsequently be assigned to parameters.
The parameter will thus be turned into a stateful parameter, with the automatic creation of a value for each combination as indicated in the actual finite state list.
Actual Finite states can only be applied to parameters within the scope of an engineering model, where these state lists are defined and stored in the iterations.
Over the iterations, changes can be made to the state lists, e.g. to reflect changes in the options that are under investigation.
The state dependency of parameters within an engineering model is not taken over if an element definition containing them is copied to other engineering models, e.g. to a *Model Catalogue* or another *Study Model*, see the description of *Model Kinds*.

To get an overview of the finite states open the **Finite State Browser** by selecting the *Finite States* icon in the *Finite States* group of the **Model** tab.
This browser gives an overview of the existing *Possible* and *Actual Finite State Lists* with *Name*, *Short Name* and *Owner*.
By expanding a Finite State List, the states are listed with *Name*, *Short Name* and *State Kind*, where this last column is only applicable to actual states.

Participants with a role that has the permission *Modify* on the *ClassKinds* *Actual* and *Possible Finite State List* are able to access the **Finite State Browser** and create, edit or delete possible or actual finite states.

A description of the available functionalities is given below.
Next to these it is possible to use the generic functionality using the *Search* and *Help* icons.
To make sure the latest data is shown in the browser, it is always possible to refresh it using the *Refresh* icon.
The possible and actual finite state list and state modal dialogs further have the generic functionality on the **Aliases**, **Definitions** and **HyperLinks** tabs, described in the topic standard tabs.

To create a new possible finite state list, select the *Create* icon or in the context menu select *Create a Possible Finite State List*.

On the **Basic** tab, provide the mandatory fields for *Name*, *Short Name* and *Owner*.

Furthermore, the *Possible Finite States* have to be added to the *Possible Finite State List*.
To do this, on the **Basic** tab, select the *Create a new PossibleFiniteState* icon and provide the *Name* and *Short Name*.
One specific *PossibleFiniteState* should be set to default.
To do this, select the *Set the selected PossibleFiniteState as the default state* icon.

On the **Category** tab, it is possible to select a *Category* that is applicable to the *Class* of *Possible Finite State List*.

The **Advanced** tab provides information that may be useful mostly to CDP™ database administrators.
Given are the *UniqueID* and the *Revision Number*, see the description of Revision Number for details.

To edit a possible finite state list or its possible finite states, select the *Edit Possible Finite State List* icon or in the context menu select *Edit*.
It is possible to edit the available fields on the **Basic** tab for the *Name*, *Short Name* and *Owner*, the applicable categories on the **Categories** tab as well as optional items on the other tabs for **Aliases**, **Definitions**, and **Hyperlinks**.
It is furthermore possible to edit the *Possible Finite States* on the **Basic** tab.
These can be edited for their *Name* and *Short Name*.
Additional possible finite states can be defined, or existing possible finite states can be deleted.
It is furthermore possible to change the relative ordering in the list.
To do this, select the *Move selected PossibleFiniteStateList Up* or *Down* icon.

After making the required changes, click *Ok*.

The browsers in the CDP™ Client of the user that performed the editing action will be updated immediately. Other CDP™ Clients will be updated with a refresh.

On the **Advanced** tab, a *Revision Number* is given; see the description of Revision Number for details.

To inspect a possible finite state list, select the *Inspect Possible Finite State List* icon or in the context menu select *Inspect*.
In the **Inspect** modal dialog, all the details can be seen on the **Basic** or content-specific tabs, as well as optional tabs for **Aliases**, **Definitions**, and **Hyperlinks**.
Additionally the status of the Parameter Type is given by the check box for *Deprecated*, see the description of *Delete* below.

The **Advanced** tab provides information that may be useful mostly to CDP™ database administrators.
Given are the *UniqueID* and the *Revision Number*, see the description of Revision Number for details.

To delete a Possible Finite State List, select the *Delete Possible Finite State List* icon or in the context menu select *Delete*.
Possible Finite States can be deleted by editing the Possible Finite State List, or select *Delete* in the context menu on a specific Possible Finite State.

TBD for implementation of not allowing deletion of possible list if used in actual list

Possible Finite State Lists and Possible Finite States will be deleted from the CDP™.

To export possible finite state list, select the *Export Possible Finite State List* icon.

To create a new actual finite state list, select the *Create* icon or in the context menu select *Create an Actual Finite State List*.

On the **Basic** tab, provide the field for *Owner*.
Next select the applicable *Possible Finite State List(s)* that should be used for the *Actual Finite State List*.
The *Name* and *Short Name* for the *Actual Finite State List* will be derived using the names of the selected *Possible Finite State List(s)*.

The *Actual Finite States* are derived as all combinations of the *Possible Finite States* in the *Possible Finite State List(s)*.

In the *Create Actual Finite State List* modal dialog, select a domain as the *Owner* of the *Actual Finite State List*.
Select the *Add Possible Finite State List* icon to a row with possible finite state lists.
All available *Possible Finite State Lists* will become available in the drop-down menu for each row, with the exception of any *Possible Finite State List* that has already been selected in any of the other rows.
It is possible to add as many rows as there are *Possible Finite State Lists*.
To delete a row again, select the row by clicking the box at the front of the row; this box should show a triangle icon.
Select the *Remove a Possible Finite State List* icon to discard a row.

It is possible to change the relative ordering of the lists themselves.
To do this, select the *Move Up a Possible Finite State List* or *Move Down* icon.
This will have an impact on the ordering of the states in the actual finite state list, where the top row will come first, followed by second row etc.

On the **Options** tab, it is possible for each *Actual Finite State List*, together with the specific settings for its *State Kind* for the *States* to select to which option it is applicable.

The **Advanced** tab provides information that may be useful mostly to CDP™ database administrators.
Given are the *UniqueID* and the *Revision Number*, see the description of Revision Number for details.

To edit an actual finite state list or its possible finite states, select the *Edit Actual Finite State List* icon or in the context menu select *Edit*.
It is possible to edit the available fields on the **Basic** tab for the *Owner*, the applicable options on the **Options** tab as well as optional items on the other tabs for **Aliases**, **Definitions**, and **Hyperlinks**.
It is furthermore possible to edit the *Actual Finite States* on the **Basic** tab.
These can be edited for their *State Kind*, which can be set to either *MANDATORY* or *FORBIDDEN*.
The *Name* and *Short Name* cannot be edited, as these are derived from the *Possible State List(s)*.

It is also not possible to change the relative ordering of the states within the list; this is given by the ordering that was given when the *Actual Finite State List* was created.

On the **Options** tab, it is possible for each *Actual Finite State List*, together with the specific settings for its *State Kind* for the *States* to select to which option it is applicable.

After making the required changes, click *Ok*.

The browsers in the CDP™ Client of the user that performed the editing action will be updated immediately. Other CDP™ Clients will be updated with a refresh.

On the **Advanced** tab, a *Revision Number* is given.

To inspect a parameter type, select the *Inspect Actual Finite State List* icon or in the context menu select *Inspect*.
In the **Inspect** modal dialog, all the details can be seen on the **Basic** and *Options* tabs.

The **Advanced** tab provides information that may be useful mostly to CDP™ database administrators.
Given are the *UniqueID* and the *Revision Number*.

To delete an actual finite state list, select the *Delete Actual Finite State List* icon or in the context menu select *Delete*.
Actual finite states can be deleted by editing the actual finite state list, or select *Delete* in the context menu on a specific actual finite state.

*Actual finite state lists and actual finite states will be deleted from the CDP™. Please note that this will delete all corresponding values of parameters that were depending on the actual finite state list.

To export actual finite state list, select the *Export Actual Finite State List* icon.

Actual finite state lists can be applied to parameters of all parameter types, including e.g. compound and array parameter types. It is also possible to apply an actual finite state list together with setting an option-dependency for a parameter.

Care should be taken in applying an actual finite state list to a parameter, due to the fast multiplication of values for parameters to which it is applied. Please take care to keep the finite state lists manageable and usable, by using not too many states in a single possible finite state list and not using too many possible finite state lists in creating an actual finite state list. Please beware of too deeply nested resulting value sets for parameters when using the finite state lists combined option dependency on parameters, for which it may not be clear anymore what their precise meaning is in the modelling.

Last modified 3 years ago.