News Opus Suite v2023.0

Release 2023.0 includes many exciting new capabilities, together with enhancements to existing features.

Task Results 
This version of SIMLOX adds fine-grained results for tasks completed during a simulation. These results offer a whole new level of insight into the workload on the support organization, giving additional understanding and analytical capabilities. It also facilitates the understanding and verification of an input model.  

Task results are available per combination of task, event, material and time interval. New reports are added and can be configured to provide details, or aggregated results, across all these dimensions.  

To enable the collection of task results, the format for the output file (.sxo) has been updated. A consequence of this is that the size of the file has typically increased for smaller cases but decreased for larger cases. Task results are obtained as default, but if desired, it is possible to switch off the collection of these results to reduce the need of memory and decrease the size of the output file.

Robbing 
An enhanced way of modeling robbing has been reintroduced in SIMLOX. Robbing is an alternative way of trying to reduce system down time in case of item shortage. A missing item can be robbed (taken) from another system that is in-operable due to waiting for other replacement items. Replacements through robbing can only be performed between systems at the same base and unit.

An important aspect is that robbing only occurs if it speeds up the process of getting the robber system ready while simultaneously not delaying the victim.

In the default setting, robbing is not allowed. To enable robbing, the potential victims are given specific tasks used for the robbing replacement. The robbing activities are modeled as separate tasks which gives a lot of flexibility since they then may have different duration and resource requirements compared to the standard replacement task.


Backorder criticality factor
This is a feature that has been reintroduced in OPUS10. The factor specifies the probability that a certain item is required for the system to be able to perform its duties. The default value is 1, meaning that no value is given, all items are always assumed to be required for the system to be operational.

The backorder criticality factor affects the optimization and the stock results. The algorithm takes into account that if an item is only required for a part of the operation, it is “less important” to have spares of that part.  

Previous releases:

Opus Suite v2021.1 
Opus Suite v2021.2
Opus Suite v2022.0
Opus Suite v2022.1
Opus Suite v2022.2