Incidents (risk events)

<< Prev   Next >>

Incident is an event which has influenced or can influence the company goal achievement. Sometimes an event happens because another event did not take place. We can also consider an event without consequences as an incident. For example, a dangerous or almost dangerous event, an event that almost occurred, a situation where an event occurred but the consequences were accidentally avoided.

In the "Risk management" subsystem (the Risk management section), use the Incident document to register incidents. It is assumed that you will carry out certain activities concerning the incident. In this regard, you can specify the current document state by simply setting an attribute with the same name. Or, you can manage the document using the approval process. To assess the damage, use the following amount attributes related to the possible damage cause:

• Maximum possible damage. Such damage can occur in the worst case when you do not carry out any activities.
• Projected damage. The most likely damage. It can occur even when you carried out or planned the activities.
• Recognized damage. The damage amount recorded in accounting.

The difference between the maximum possible and projected damage indicates the expected effectiveness of reaction activities to an uncovered incident. The difference between the maximum possible and recognized damage indicates the actual effectiveness of the carried out activities for a closed incident (or about the successful loss avoidance).

When you register an incident in the "Risk management" subsystem (the Risk management section), specify the following:

• Incident name in the Incident field.
• Number. The number is assigned automatically after saving the document.
• Date
• Preceding incident cause from the incident catalog.
• Risk to which the incident relates.
• Company where the incident has occurred.
• Financial responsibility center
• Project
• Context type
• Context
• Risk source
• Incident description. Specify the relevant incident characteristics in text form.

Then, when you register an incident, specify the Projected damage assessment ranging from "Maximum possible" to "Recognized". Also, automatically calculate the Planned costs limit as a multiplication of predictive assessment and Cost percentage.

Describe the damage which you cannot assess in amounts in text form in the Damage description field.

The Incident document date is a date of the event (or no expected event) considered as an incident.

The Context type attribute is a list of system object types. You can define a catalog or the current infobase document for the basis type. In this case, in the Context attribute, you can select only the object of the specified type.

You can use the Context attribute to link the incident to any catalog item or any system document.

You can fill the Company, Project, and Center for Financial Responsibility attributes to link an incident to the corresponding object.

You can find the Context type, Context, Target, Company, Project, Center for Financial Responsibility attributes both in the Incident document and in the Risks catalog item. Even if the Incident is linked to "Risk", the values of these attributes in two objects might differ. It helps you to enter a more detailed value in "Incident". For example, in "Risk", you can specify a high-level Financial responsibility center, and in "Incident", you can specify a subordinate Financial responsibility center.

In the Responsible person attribute, specify a system user responsible for the incident. It is assumed that this employee has the authority to organize reaction activities and is responsible for the final incident consequences.

In the "Incident" form, you can view, open, add new, or delete the existing list of related reaction activities.

On the Reactions to risk tab, the user accesses the Activities catalog. There, they can select the required Activity or create a new one.

<< Prev   Next >>