The insights within Servitly used, for example, to provide useful information about the operation of connected products are based on the concept of Standard System Status, which represents the operational status of a machine, but using standard status codes on which computational logic can then be applied.
Standard Status Codes:
- OFFLINE: the product is offline (Connection Status != 1)
- DOWN_UNPLANNED: the product is in FAILURE and so not able to work.
- DOWN_PLANNED: the product is not able to work due to a planned reason, for instance, a cleaning session is running.
- IDLE: the product is not working (e.g. standby, warm-up, startup).
- WORKING: the product is working.
By entering the Catalog / Thing Definitions page, and then in a Thing Definition, it is possible to specify which metric provides the machine status, and for each Standard Status code, you can map multiple machine codes (e.g. HEATING is mapped to WORKING).
A comma-separated list of machine codes can be specified for each Standard Status. If the metric already provides standard codes, the states mapping can be ignored.
The Standard Status codes you have to map are: Down Planned, Down Unplanned, Working, Idle.
The OFFLINE status does not require to be mapped, because it is implicitly managed through the Connection Status metric.
The Algorithm's computation engine uses this mapping to convert the machine status codes, and pass the dataset containing the standard status codes to the algorithm being computed.
Daily Minimum Online Time
Optionally, you can specify the minimum time in hours the machine must be online each day in order to correctly computes insight metrics.
For example, if the machine remains offline for the whole day, the Uptime insight cannot be calculated because the actual state of the machine is not known.
Comments
0 comments
Please sign in to leave a comment.