Create a simulation model
- Last UpdatedMay 26, 2025
- 6 minute read
The first step towards simulation is creating a scenario from an existing FMECA system. Once a scenario has been created, it can be modeled in the Simulation module, where it is called a Simulation model. A scenario can be created based on one of the following FMECA objects:
-
Serial System
-
Parallel System
-
Part
At that moment Risk-based Maintenance will create a copy of that FMECA model which will exist independently afterwards. This means that changes made to the FMECA model after creating the scenario, will not be reflected on the scenario and vice versa.
Initially, the simulation model will inherit the name of the FMECA model. The name can be changed afterwards, which can help identify the simulation among other similar simulation models.
Creating a scenario
To create a scenario, perform the following steps:
-
Right-click one of the object types described above in the FMECA tree
-
Choose New > Scenario
-
Fill in the Properties screen for the scenario and define the simulation parameters (for details see below)
-
Press OK to save and close;
The scenario has been created.
In the Properties screen, if you select Apply, the changes are saved and the windows will remain open. You can select Cancel to cancel the creation of a new scenario.
-
To make the scenario visible, click the bar called Scenario on the bottom right of the screen.
This will collapse the Property Grid and display the scenario window.
The scenario, which is linked to the active object in the FMECA tree, is now visible in the scenario window
-
Navigate to the simulation module by double clicking the scenario.
This will display the individual scenario. Alternatively, you may right click the scenario and choose Edit Scenarios. As a third option, you can open the simulation module from the main menu bar, Simulation > Simulation models which will display all simulation modules:
This will open the simulation module showing the created scenario.
Properties of a simulation model
|
FIELD |
DESCRIPTION |
|
Name |
This is a free-text field. You are free to choose any name By default this field copies the name of the part or system the scenario was copied from |
|
Description |
This is a free-text field. You are free to choose any description |
|
Sim. Period |
Here, you can choose from Hours, Weeks, Months, and Years |
|
Model start date |
This is an offset date, indicating to Risk-based Maintenance that reporting of simulation data earlier than this date should be skipped. It is an absolute date field, which can be filled or left empty. If left empty, Risk-based Maintenance will assume the day of today each time the scenario is run, while all start dates entered in other fields will be compared to the day of today (i.e. the day the simulation is run). If filled, the chosen date should always be later than "today". Note: The Model start date must always be later than the date of "today". This means, that when revisiting a scenario that was run some years ago, it may well be that meanwhile, the Model start date is now in the past. Rerunning the simulation in this situation may result in undefined data, or in a complete stop of Risk-based Maintenance in some cases. Note: There is also a relationship between the Model start date and the chosen Begin date of objects in the model. The Begin date must be in the past compared to the Model start date. Note: If a simulation has been run, the Model start date field can still be changed. However, changing the date will not trigger new calculations, which means the existing results no longer reflect the initial situation where the Model start date was left unchanged. |
|
No.of Periods |
The number of weeks, months or years that the simulation must cover |
|
Max. Calc. Time (min) |
The maximum duration of the simulation in minutes. Since on starting the simulation it is not always possible to predict how long it will last, you can set a maximum computing time here. When this computing time has elapsed, the simulation is terminated. You must, however, be aware that in such a case you will probably not achieve results with the specified reliability. This action will only take place if the option End by time was set |
|
Max. No. of Runs |
The maximum number of runs performed. During a run, the model is simulated once. So if you specify a 10-year simulation period, there is only one run cycle of 10 years. If you specify multiple runs, the simulation period will be run multiple times, and the final results will be an average of these runs. This action will only take place if the option End by runs was set |
|
Reliability |
Here, you can specify the reliability percentage within which the results must be. If this percentage has not yet been reached, additional runs will be performed. This will continue until either the specified reliability has been achieved, or the maximum number of runs has been performed, or the maximum computing time has elapsed. If it is set to <none> (0%) the simulation will not stop prematurely because the reliability percentage is reached. In this case, the simulation reports will show "Not available" for the reliability level. This action will only take place if the option End by Reliability was set |
The Simulation Models window now contains a new model. This model can be further changed or extended by copying and pasting objects from the FMECA Systems window. Objects that can be copied into a model include:
Serial Systems
Parallel Systems
Parts
Components
Failure causes
Maintenance Actions (FBM, UBM, CBM, CBM Follow-Up)