The platform contains the automation layer allowing to rise an abstraction level from a level of models and elementary device components to a business process level. The current layer concept is based on the idea of any process representation in the form of a logical diagram that contains states and transitions between them, according to the final state machine principle.
The state characterizes the time period during that no changes in the business process properties occurred. In other words, every property displays in the form of a separate state in the scenario. For instance, in dependence on which object is bound to the scenario of automation, new states may be added to it: turned on, turned off, remains at rest, moves, if it is about a car, the state of hijacking can be fixed, etc.
The transitions can happen between the states that characterize the state of the system. They are initialized by events and by changes happening in the system. In the transition should be written a condition that determines the commission of one or another change. When this condition is fulfilled, the transition realizes between the states. For example, in the condition, it can be said that the transition may be only committed if the specified value was exceeded by a numerical indicator of a sensor. If it is fixed that the value of the current indicator exceeded the norm, indeed, then the transition between the system states initializes. It is worth noting that the transition always must lead from one state to another and, besides that, the branch condition should be specified. If the transition is instant, it is considered executed automatically.
In this way automation script is built and the object logic is determined. When starting the scenario, there is no need to monitor and control the current object state constantly and, accordingly, to execute any actions, send commands based on received data regularly. All these operations are executed when the final state machine is started, which allows automating the object management.