Community Tip - Learn all about PTC Community Badges. Engage with PTC and see how many you can earn! X
Events are automatic analysis jobs which are submitted based on a pre-defined condition.
In this step, we'll configure an Analysis Event which will execute automatically whenever there is a datachange in our simulated engine.
Map the Properties of AMQS_Thing, to the fields required to evoke an Analysis Job.
Map goalName to goalField in the same manner.
Now that we've done the mapping from Foundation to Analytics, let's confirm that everything is correct.
If so, we'll then Enable the Analysis Event so that it can automatically generate and process Analysis Jobs.
Now that you have enabled the Analysis Event, whenever AMQS_Thing's InfoTable Property changes, the new data will be submitted to Analytics Manager.
An Analysis Job will automatically run, with a predictive score sent back and stored in AMQS_Thing's Result_low_grease (Boolean) and Result_low_grease_mo (Number) Properties.
In this step, we'll confirm that the automatic analysis of information coming from remote devices is operational.
NOTE: You will see true or false, just as when you manually tested the Model, so you know that Analytics Manager is now automatically submitting and completing jobs with a resulting prediction.
Follow these steps to confirm that the results are being sent back to ThingWorx Foundation in a way in an actionable way.
Using this technology, you could create a paid customer service, where you offered to monitor remote engines, in return for automatically shutting them down before they experience catastrophic engine failure.
For that example implementation, you would utilize the AMQS_Thing.Result_low_grease BOOLEAN Property to trigger other actions.
For instance, you could create an Alert Event which would be triggered on a true reading.
You could then have a Subscription which paid attention to that Alert Event, and performed an action, such as sending an automatic shutdown command to the engine when it was experiencing a likely low grease event.
NOTE: We recommend that you return to the ThingWorx Composer Analytics > ANALYTICS MANAGER > Analysis Events tab and Disable the Event prior to continuing. Since the simulator generates an Event every ~10 seconds, this can create a large number of Events, which can fill up your log.
Congratulations. You've completed the Operationalize an Analytics Model guide.
In this guide you learned how to:
This is the last guide in the Design and Implement Data Models to Enable Predictive Analytics learning path.
We recommend the following resources to continue your learning experience:
Capability | Guide |
Build | Implement Services, Events, and Subscriptions Guide |
If you have questions, issues, or need additional information, refer to:
Resource | Link |
Community | Developer Community Forum |
Support | Analytics Manager Help Center |