Using Templates to Define Assets and Event Frames

The basic EIDI asset framework provides the capability to represent the refinery data in a hierarchical object-oriented schema. The Proclndustries' team needs to define asset templates and reuse them for similar types of equipment to achieve the greatest impact of the real-time data infrastructure. They also need to use event frames and combine the two EIDI capabilities.

Once refinery personnel started adopting and using the EIDI data, the team turned their attention to designing the hierarchical data model and defining the most commonly used asset templates. Peter assembled the group to determine how best to tackle this important issue, which would have lasting consequences for the refinery.

The team would use another capability of these object asset templates; they would be used in the context of defined production or refinery events. For example, if there were similar events that needed to be analyzed comparatively, the EIDI could segment and time-slice the continuously collected data so that Proclndustries personnel could compare and analyze similar events, such as producing gasoline using a specific type of crude oil or noting unit startups or shutdown events. Figure 3.5 shows an asset template with event frame context.

One of the most resourceful and productive methods of using these event frames is to dynamically create events, based on the process or operating status of the unit. This approach is used to create a "trouble" event when a unit is in an underperforming or a trouble operating mode.

This means that something caused the unit to run outside of acceptable conditions. Because the EIDI or operations personnel don't generally know when a unit enters a trouble mode, the EIDI can dynamically create such an event type during or after unit operation. When a metric or value deviates from normal conditions, the EIDI can trigger a start to the event. Consequently,

FIGURE 3.5

Asset template object components with the capability for event context.

if or when the unit returns to normal operation, the EIDI can trigger an end-of-event indicator. The EIDI even has the capability for people to mark these events after the production run has completed if it has been determined that there were problems. This last capability is powerful but should only be activated by people who are very familiar with the process and the equipment, until those people can determine how to automate the event triggers. Figures 3.6 illustrates this dynamic time-slicing capability.

FIGURE 3.6

Defining operating modes for a process unit.

FIGURE 3.7

Event frame template configuration and the event-framed data results.

Peter discussed the implications of these capabilities: "The time-event context stores the start and end times to calculate an asset's time-derived variables over a defined period of time. This will be key for analysis and optimization. As such, we can store totals and averages for selected attributes, calculated at the defined operating start and end times. This transforms the real-time and statistical data into operational intelligent information." Figure 3.7 shows how the event frame capability creates the resulting eventframed real-time data table. This information is analyzed directly through EIDI visualization tools or it can be exported to external products, such as Microsoft Excel or Power BI.

 
Source
< Prev   CONTENTS   Source   Next >