Deep dive one: consequential executions

With more complex assets, you are likely to require some form of aftercare when a certain type of maintenance has taken place. A typical example would be the readjustment of components some time after their first installation as a result of running in. If this is the case, you could add a schedule item in your request body with an additional ‘after‘ field in the interval object.

In practice, this could look somewhat like:

{
    "id": "ADJUSTMENT",
    "name":"Post overhaul adjustment"
    "interval":
        {
            units: 100,
            orDays: 10,
            after:"OVERHAUL"
        }
}

In the above example, by adding the after field, the schedule item will no longer be executed every 100 units, but only the first 100 units after the execution of another schedule item with the id “OVERHAUL”. Every future execution of the “OVERHAUL” item will also trigger the execution of the “ADJUSTMENT” item. Besides referencing just one item, it is also possible to reference multiple item id’s when separated by commas.