Processes and Corresponding Workflows

Incident lifecycle

WS00500001

The incident lifecycle process supports you from the initial recording of an incident to the time when you close the incident data record.

Incident Recording

Dispatcher

WS00500006

This workflow is the central point for determining the additional tasks to trigger, for example, notification via e-mail about a fatality.

Inquiries

WS00500002

You can send inquiries to the people and organizations involved in an incident to collect more information. The process starts when you send the selected forms to the desired recipient.

The system handles generating the form, sending it, and extracting the data from a returned form. You receive a task to evaluate the returned data in comparison to existing data. Your decision to keep or reject the returned data causes the system to automatically transfer the data into the data record or delete it, respectively.

Inquiries

Notifications

WS00500004

WS00500036 for PM

WS00500037 for CS

WS00500038 for QM

You can notify people about work that they need to perform in the Plant Maintenance (PM), Quality Management (QM), or Customer Service (CS) components, or notify people when an incident fulfills certain conditions.

You explicitly start the notification process when you choose the Start Process button for a notification to an integrated component, such as the Plant Maintenance component.

The system also automatically starts the notification process when the incident fulfills specified conditions, for example, an involved person was fatally injured.

Adding Actions and Notifications

Notify Involved Person about Cost Collectors

WS00800022

You can notify stakeholders that a cost collector has been added to an incident. The system sends an e-mail with incident information, the internal order, and the request to invoice and enter all income and expenses related to this incident to the mentioned internal order.

You manually start the notification process. The notification process ends once the assigned work is complete and approved, or once the notified person confirms that the notification has been read.

Financial Tracking

Incident investigation

WS00500031 (investigation process)

WS00500032 (investigation step)

You can start an investigation to find out the root causes for an incident. The investigation contains steps that each represent their own processes. You can assign steps to other people and execute the steps assigned to you directly in the application. You explicitly start the investigation process or step when you choose the Start Investigation or Start Step pushbutton on the Investigation tab. The process ends once the investigation steps have been canceled or carried out, and you explicitly close or cancel the investigation.

Investigation

For more information about the workflow for evaluating controls during an investigation, see the description in Processes and Corresponding Workflows for risk assessment.

Report generation

WS00500051

You can manually add a report to an incident data record. The system checks the incident data record and suggests a corresponding reporting form, for example, for an injury/illness. When you add a form, the process starts. In the data record, you can confirm that reporting is required and generate the report.

If you do not manually add a report that is required for reporting, the system can also add the form automatically and sends a task to the incident manager to determine if the report is required. The process ends once the form has been successfully generated or you have determined that the form is not required for reporting.

Incident Reporting

Reporting

WS00500034 (shipment)

WS00500003 (approval)

When you are ready to send a generated report, you can choose the Send pushbutton on the Reports/Documents tab in incident management. This starts the report shipment process. If approval of the report is required before you send it, the system waits until the report has been approved. The approval process also supports you if the report is rejected and must be regenerated. The reporting process ends once the report has been successfully sent.

Incident Reporting

Action

Action ‑ Change Request

WS00500005

WS00600080

You can add an action to an incident data record on the Tasks tab. You explicitly start the action process when you choose the Start Process button for an action. The system uses this workflow to communicate tasks to the responsible implementer and approver, if necessary. The action process ends once the assigned work is complete and approved.

You can also add a change request to an incident data record on the Tasks tab to communicate a requested change to SAP Management of Change.

Adding Actions and Notifications

Absence was maintained in HR

WS00500039

You can add absences to an incident record that were maintained in the HR component. The system starts the process when a scheduled job returns an HR absence. The process ends when you assign the absence to an incident record, or decide to ignore the absence.

HR Integration for Absence Assignment

Absence notification to HR

WS00500040

You can notify the HR responsible of an absence entered in an incident record. You start the process when you explicitly choose the Create HR Absence pushbutton. The process ends when a scheduled job determines that the absence was entered in the HR system.

HR Integration for Absence Assignment

Communication of operational incident information to GRC

WS00800036

You can communicate incident information to the SAP BusinessObjects Risk Management component of GRC solutions, for example, to provide data about losses and loss reductions associated with incidents on a corporate level. The system checks and determines the relevance of the incident data based on settings in the Customizing activity Specify Selection Criteria for Data Transfer. The workflow then reports the relevant incident data to GRC using the BAdI Transfer of Incident Data to GRC (BADI_EHHSS_INC_GRC_INT).