Overlap example

A slightly more complex situation can also occur, in which one maintenance action is already in progress, while a second action is started. The following figure describes such a scenario:

The figure shows that the two maintenance actions have an overlap in time of one hour. One purpose of the simulation core of Asset Strategy Optimization is to record downtime caused by maintenance actions. If the actions shown above are related to two parts of the same system, then the system as a whole will be down as long as any of the parts is down. This means that the simulation core of Asset Strategy Optimization must make sure that for overlapping maintenance actions downtime is only recorded once, while total maintenance time of both actions are added together. In the example above, the separate actions would record downtimes of two and four hours, respectively. Should Asset Strategy Optimization count them separately, a total of six hours of downtime would be recorded. In reality, because of one hour overlap, the system will have a downtime of only five hours. Total maintenance time, however, takes up a total of 6 hours. How the simulation core of Asset Strategy Optimization can take overlap into account (by applying a scoring mechanism) is discussed next.