The content of this article is deprecated, and will be removed in the future
detectedAnomaly
detectedAnomaly messages are sent when an asset has stopped and the reason is identified.
less than a minute
This is part of our recommended workflow to create machine states. The data sent here will not be stored in the database automatically, as it will be required to be converted into a state. In the future, there will be a microservice, which converts these automatically.
Topic
ia/<customerID>/<location>/<AssetID>/detectedAnomaly
ia.<customerID>.<location>.<AssetID>.detectedAnomaly
Usage
A message is sent here each time a stop reason has been identified automatically or by input from the machine operator.
Content
| key | data type | description |
|---|---|---|
timestamp_ms | int | Unix timestamp of message creation |
detectedAnomaly | string | reason for the production stop of the asset |
JSON
Examples
The anomaly of the asset has been identified as maintenance:
{
"timestamp_ms":1588879689394,
"detectedAnomaly":"maintenance",
}
Producers
- Typically Node-RED
Consumers
- Typically Node-RED
Last modified November 12, 2024: Merge pull request #308 from united-manufacturing-hub/fix/xxx/correct-opc-ua-simulator-get-started (56093f1)