Incidents application

Edit online

You use the Incidents application to report incidents, including any secondary events, that have a health, safety, or environmental impact. After an incident occurs, you can follow up with the persons who are affected to ensure that the appropriate corrective actions were implemented.

Watch this video to learn how to create incidents in the Incident application.

In the Incidents application, you can do the following activities:
  • Starting in 9.2, use artificial intelligence (AI) to automatically categorize incidents based on the incident summary and details in the Tickets application. The multi-class classifier (MCC) model provides suggestions for incident type and incident category fields to help you classify incidents more consistently and efficiently.

  • Starting in 9.2, assign inspections to specific individuals or groups to reduce unnecessary downloads of unassigned inspections to mobile devices. New fields in the inspection results identify the assigned owner and owner group for each inspection. The application uses this information to route inspections to the appropriate person. For more information, see Assigning inspections.

  • Starting in 9.1, perform the following actions to manage emissions and for regulatory compliance.
    • Search incident records by incident event type, event category, emission type, emission category, or emission impact by using the More search fields option.
    • Mark an incident as Recordable when you create an incident for compliance reporting.
    • Specify emission details such as event category, emission type, emission category, and emission impact when you select an blow down, environmental, leakage, purge, or spills event type.
    • Select an Inspection Form that is associated with an asset or location and select Inspection Results for an incident.
  • Create one or more incident events for each incident.
  • Classify incidents as global, regional, local, or master.
  • Associate risk assessments and risk rankings with incidents.
  • Associate losses and impacts with incidents.
  • Specify the details of high-context incidents.
  • Specify whether incidents can be reported, recorded, and whether an investigation is essential.
  • Add information about the persons who are impacted by an incident, including their roles.
  • Record the severity of an injury or an illness, the type of injury, and the result of the injury or illness. In the Incidents application, specify the person who was impacted by the incident, and select Injured/Ill in the Person Role field. This feature is enabled by using the Controls the injury and illness details section signature option for the Incidents application in the Security Groups application. You must have administrator privileges to enable signature options.
  • Record multiple illnesses or injuries per person, and for each injury or illness, record one or more outcomes. This feature is enabled by using the Enable multiple injuries and illnesses on incident records signature option for the Incidents application in the Security Groups application.
  • Record multiple outcomes for each injury or illness.
  • Create activities to specify and initiate the work processes that are essential for completion of the activities in the incident record or in associated records.
  • Specify the type of follow-up action to be taken by the person who is responsible for the action, and any associated procedure or standard action group.
  • Specify and describe the actions that were taken after an incident occurred.
  • Associate existing solutions with incidents.
  • Create draft solutions.
  • Associate hazards with incidents.
  • Specify the potential and actual consequence of the hazard.
  • Specify the potential severity and actual severity of the hazard that is associated with an incident.
  • Add the sequence of events that occurred, and information about witnesses to the events.
  • In support of fulfilling OSHA 300, 300A, and 301 reporting requirements, you can add details about the persons that were impacted by an incident that resulted in an injury or an illness. Additionally, you can generate a BIRT report that contains the same fields that are needed to fulfill the OSHA requirements.
If an incident requires follow-up tickets or work orders, you can generate the following types of records from this application:
  • Action
  • Communication
  • Improvement
  • Incident
  • Investigation
  • Management of change
  • Management of change request
  • Release
  • Risk Assessment
  • Service request
  • Solution
  • Work order