Background

As owner/operators attempt to move from a purely reactive world to a world where they optimize overall operations, all of the various systems must be able to provide each other with some degree of early notifications about impending situations which will require an optimal decision to be made. If optimal operations are to be achieved, a fully informed dialog needs to take place between all of the participating systems and personnel as they make optimization decisions in support of a previously agreed upon definition of optimum for a particular organization, which may be established using tools such as balanced scorecards.

This use case contemplates the situation where an Operational Performance Modeling & Optimization (OPM) system is receiving early warning notifications from a variety of systems which are contributing inputs to the overall optimization effort. The objective is to avoid the “collisions” that routinely occur in planning and scheduling meetings. While this use case focuses on the maintenance and reliability-oriented systems, equal attention must be placed on all of the operational planning and scheduling systems. The OPM can then be used to generate a unified O&M schedule that is optimized according to agreed upon metrics and that should be the basis for any discussion about further optimization (or deviations).

Scenarios

  • Scenario 17 – Pull Maintenance KPIs from MMS to ERP, ERM, PORT, MES, OPM
  • Scenario 18 – Publish Maintenance KPIs from MMS to ERP, ERM, PORT, MES, OPM
  • Scenario 19 – Pull Performance KPIs from ORM to ERP, ERM, PORT, OPM
  • Scenario 20 – Publish Performance KPIs from ORM to ERP, ERM, PORT, OPM
  • 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 23 – Pull OPM KPIs from OPM to ERP, ERM, PORT, MES
  • Scenario 24 – Publish OPM KPIs from OPM to ERP, ERM, PORT, MES
  • 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