The Incidents application lists all the incidents that have been generated by the machines in the environment. Incidents are generated based on the Monitors  which watch specified machine events and to trigger incidents because of machine events, and by scheduled Preventative Maintenance tasks. This article explains the function and use of the Incidents application and the information it provides.

Article Topics

This article covers the following topics.

• Accessing the Incidents Application
  • From the Health Applications Menu
  • From the All Machines Page
  • From the Machine Overview Page
• Incidents Application Layout and Functions
  • Page View Functions
    • Application / Page View
    • Filtering the Incident View
    • Setting the Date Range
    • Searching for Incidents
    • Exporting Incidents
  • Incident Information
  • Individual Incident Information Page
• Resolving an Incident
  • Using the Incidents Ellipse Menu
  • Using the Resolve Incident Button
• Reassigning an Incident
• Viewing an Incident in the Diagnostic Timeline

Accessing the Incidents Application

You can access the Incidents application from the following locations in MachineMetrics:

• Health applications menu
• All Machines page
• Overview page for an individual machine

The following sections explain how to access the Incidents application for a machine from each of these locations, assuming you are already logged in to MachineMetrics.

From the Health Applications Menu

To access the Incidents application from the Health applications menu, do the following:

1. Hover over Health in the main navigation and select Incidents as highlighted below.
   
   
   
   
2. The Incidents application page will display listing all incidents that have occurred for all machines for the selected date range as shown in the example below. If no incidents have occurred, the page will display "No open incidents found in range". 

From the All Machines Page

To access the Incidents application from the All Machines page, do the following:

1. From the Current Shift Dashboard page, click Machines from the main application menu to open the All Machines page.
   
   
   
   
2. Click the "ellipse" menu (---) associated with the machine you want to view, and select Incidents as highlighted below. 
   
   

From the Machine Overview Page

To access the Incidents application from an individual machine page, do the following:

1. Open the All Machines page as described in the preceding section.
2. Click on the desired machine to view the Overview page for that machine.
3. From the Overview page, click the application menu and select Incidents as highlighted below.
   
   

Incidents Application Layout and Functions

The figure below highlights the functions and information provided in the Incidents application page. The following sections describe the information provided and the purpose and use of each function.

Page View Functions

The following figure highlights the functions for modifying the Incidents application page view.

Application / Page View

Clicking the application menu allows you to access a different Health application. The All page view shows all incidents that meet the selected incident filter, date and search criteria. 

Filtering the Incident View

You can filter the incidents displayed in the Incidents application page by the following criteria:

• Assignee: The Assignee filter allows you to display all incidents for all users or only the incidents assigned to a selected MachineMetrics user. 
• Type: Incidents can be triggered by Monitors or by Preventative Maintenance tasks that have been scheduled. The Type filter allows you to display only the incidents of the selected Type, which include: 
  
  • Alarm: Incidents triggered by an Alarm monitor.
  • Anomaly: Incidents triggered by an Anomaly monitor.
  • Downtime: Incidents triggered by a Machine reports inactive monitor.
  • Annotation: Incidents triggered by a Current downtime period categorized monitor.
  • Maintenance: Incidents triggered by a scheduled Preventative Maintenance task.

See the Monitors article for more information on the above monitors, and the Preventative Maintenance article for more information on scheduling preventative maintenance tasks.

• Status: The Status filter allows you to display incidents based on their Status (Open, Closed, or Both).
• Machine: The Machine filter allows you to display incidents for all machines or only the incidents of a selected machine.

Setting the Date Range

To set the date range and from/to time for the incidents you want to view, do the following:

1. Click the date/time menu field to the right of the Machine filter menu to open the calendar tool.
2. In the Start and End fields, enter the times that will be the start time on the start date and end time on the end date.
3. On the calendar, click on the end date and start date that represent the date range. The selected dates will be highlighted in green. Use the <-- and --> arrow buttons to browse by month.
4. Click the Apply button to apply the selected date/time range to the Incidents application page view.
   
   Example
   The following figure shows the date/time range selected as 10:00 AM on November 1 2019 to 11:00 AM on November 11 2019. Note that the date/time fields at the top will not change until the Apply button is clicked. 

Searching for Incidents

In the search field to the right of the date/time range fields, you can enter text that will filter the incidents to display based on whether the text is contained in any of the following:

• Message: The incident name or message associated with the incident. 
• Machine: The name of the machine that experienced the incident.
• Assignee: The name of the MachineMetrics user assigned to the incident.

The incidents are filtered instantly as text is entered. You only need to enter part of the intended incident search target as shown in the following search example, where "sub" is entered to display incidents generated by the "Sub Collet" alarm type.

Exporting Incidents

Click the Export button to the right of the search field to export all incidents into a comma-separated value (CSV) file that contains the following incident data:

• Triggered At: Date and time each incident was triggered.
• Resolved At: Date and time each incident was resolved.
• Asset: Machine that experienced each incident.
• Message: Message associated with each incident (Alarm/Anomaly name, maintenance task, and so on).
• Priority: Priority assigned to each incident (Low/Medium/High).
• Assigned To: MachineMetrics user assigned to each incident.
• Assigned At: Date and time each incident was assigned to the assignee.
• Trigger Type: Type of each incident.

Once exported, the CSV file data can be viewed in an application like Excel or imported into a database for use in a separate system such as an Enterprise Resource Management (ERP) system or other company system.

Incident Information

The following figure highlights the "incident information" area of the Incidents / All page.

The incident information area of the Incidents / All page provides the following information:

• Time and date that the incident was triggered
• Incident message/name
• Name of the machine that experienced the incident
• Incident Priority (Low, Medium, High)
• Incident Status (Unassigned, Assigned, Resolved)
• Assignee name (or Unassigned if not assigned

The ellipse menu on the right of each incident allows you to resolve the incident or view the incident on the Diagnostic Timeline.

Individual Incident Information Page

Clicking on an incident entry in the incident information area will open the information page for that incident as shown in the following example for a "Sub Collet 2" incident.

The incident information page provides the following information and functionality:

• Incident Name/Message: Displays the name or message assigned to the incident.
• Machine Information: Displays the machine name, make, model, and status.
• Incident Details: Displays the incident Priority and name of the MachineMetrics user assigned to the incident (or Unassigned if not assigned).
• Incident Log: Provides the log of changes to the incident status, including when the incident was Triggered, Assigned, and Resolved.
• Resolve Incident (Button): Clicking this button resolves (closes) the incident.
• Reassign Incident (Button): Reassigns the incident to a different MachineMetrics user. Button only becomes active when the currently assigned user is changed.

Resolving an Incident

Alarm incidents can be configured to automatically resolve when the alarm condition is cleared on the machine, or require manual resolution as described in this section. All other incident types remain open until they are resolved manually. MachineMetrics users can resolve incidents manually using either of the methods described in the following sections.

Using the Incidents Ellipse Menu

On the Incidents application page, click the ellipse menu associated with the incident you want to resolve and select Resolve from the menu:

Using the Resolve Incident Button

On the individual incident information page, click the Resolve Incident button:

Reassigning an Incident

To reassign an incident to a different MachineMetrics user, do the following:

1. On the Incidents application page, click on the incident you want to reassign. This will open the individual incident information page.
2. In the Incident Details section, click the Assign to pull-down menu and select the user you want to assign the incident.
   
   
   
   
3. Click the Reassign button to assign the incident to the selected user.

Viewing an Incident in the Diagnostic Timeline

 The Diagnostic Timeline application is a powerful analytical tool that enables users to view, analyze and troubleshoot machine performance based on any diagnostic metrics available on the machine. It may be useful in certain cases to view the Diagnostic Timeline and analyze machine behavior at the time an incident occurred. To do this, on the Incidents application page, click the ellipse menu associated with the incident you want to analyze and select View In Timeline from the menu:

The following figure shows an example of the Diagnostic Timeline. See the Diagnostic Timeline article for more information on this application.