What are Incidents, Warnings, and Alerts?

Monitor incidents, warnings, and alerts to learn about issues that might delay or interrupt your production process. Define rules to trigger these events based on the nature of the production issues and the actions required to resolve them.

Monitor the list of incidents to learn about those production issues that require a maintenance technician to repair or tune a machine to get resolved. Incidents have a priority and a status that you can use to manage and track the resolution of the production issue. You can view incidents from the web application and from the mobile application. See View Incidents and View and Update Incidents in the Mobile App.

View the list of warnings to diagnose production issues or to learn details about the performance of your factories and machines. Warnings do not require a human to resolve them, they get resolved once the value you are monitoring goes back to normal. Typically warnings get resolved on their own, multiple warnings for the same issue or a warning that’s been active for a long time might indicate a problem with the affected machines. See View Warnings.

Alerts do not appear in the user interface because they are used to integrate with other business systems, or from REST clients. The way you view and monitor alerts depends on the business system integration or REST client you are using.

When to Create an Incident?

Define rules to create incidents for issues that need human interaction to get resolved. Incidents provide a structured life cycle that you can use to track the status and resolution of the production issue. Incidents also appear in the mobile application so that maintenance technicians can access and update the incident while they are working on the field.

For example, if a machine breaks down, you can create an incident to inform the maintenance technicians that the machine needs to be repaired. This incident also allows you to track the status of the service request.

For information on how to create incidents, see Define Rules to Trigger Incidents.

When to Create a Warning?

Define rules to create warnings for temporary issues that might resolve on their own. Warnings let you keep track of these issues so that you can use them to asses the status of a machine, or to diagnose a production issue.

For example, you can create a warning when the temperature goes above 70 F. If the temperature goes back to normal in the next reading, the warning will get automatically resolved.

For information on how to create warnings, see Define Rules to Trigger Warnings.

When to Create an Alert?

Define rules to create alerts for issues that require you to trigger actions in another system or in a REST API client.

Alerts do not appear in the Oracle IoT Production Monitoring Cloud Service user interface. You can access alerts using REST APIs or the Oracle Internet of Things Intelligent Applications Cloud Management Console.