What work order information is used for ARP?
Asset Risk Predictor (ARP) doesn't use work order data; instead, its models are based on data payloads coming from the OT system/sensors.
What physically enables this service?
Enablement is completed by submitting data from a data source to the API endpoint. Our model is based on connecting an edge data collector, aggregating the data by the minute, and submitting every hour. However, there is no reason why data from an existing historian can't be connected as well using an integration service (like Boomi, SSIS or any other ETL system), so long as we get data submissions by the minute, submitted only once per hour. If you are interested in creating your own connector, this is an option as well, as a simple HTTP client in the language of your choice can submit data to ARP.
How is sensor data sent to ARP?
As mentioned in the previous answer, any system that can generate a JSON payload containing aggregated data of values can be used to send data to ARP. Data contained in a historian, db, data lake, and of course live data from OT sensors and PLC inputs can be used. For example, if you are collecting OEE and have that logged to a historian with live data, this value can be sent to ARP, and if the signature changes from the trained model we will see risk for that “sensor” input rise. We do not need to think about sensors as just inputs from a machine; they can be results from a calculation on a process as well. Any numeric value can be used as long as it can be read by the minute, has a "normal" pattern to it, and requires attention when it deviates from "normal".
Is my data secure when sent to the cloud?
Your data is secure during transmission and at rest. Data can only be sent with your valid token and is encrypted during transmission. We are HIPAA, PCI DSS, SOC 1, and SOC 2 Type 2 compliant for data governance.