An Operations and Maintenance Information Open System Alliance

OIIE Use Case 9 - Incident Management/Accountability

Background

With the increasing emphasis on risk management topics including Operational Risks and Health, Safety and Environmental risks, better incident management methods must be established. While traditional incident management systems relied on somewhat arbitrary (and frequently manual) methods to declare, capture, escalate and respond to various categories of incidents, a more systemic approach enables a substantially improved approach to risk management. Post mortem analysis shows that in many cases, a catastrophic event is proceeded by a series of improperly captured and escalated incidents. When the catastrophe occurs, management often responds by indicating they were unaware of the situation in spite of prior related incidents. In response, regulatory agencies such as OSHA are communicating their intent to hold management increasingly accountable (including criminal prosecution) for future catastrophes with ignorance to not be an excuse. In order to enable management to be properly aware of these incidents (in addition to the other risk indicators flowing in association with OIIE Use Case 8), industry must make sure that critical information is captured and escalated along the lines of accountability. An automated approach offers the greatest assurance of such a flow by eliminating unnecessary gaps in the process. This will also properly support the forthcoming requirements to capture, track and report near-miss incidents.

Scenarios

  • Scenario 21 - Pull Significant ORM Events from ORM to ERP, ERM, PORT, OPM
  • Scenario 22 - Publish Significant ORM Events from MMS to ERP, ERM, PORT, MES, OPM
  • Scenario 29 - Pull Current Operating Data and Events from CMS to CONTROL, ORM, OPM
  • Scenario 30 - Publish Current Operating Data and Events from CMS to CONTROL, ORM, OPM
  • Scenario 31 - Pull Historical Operating Data and Events from HIST to ORM, OPM