Model and Event Creation Overview
The integrated components of a Manufacturing Execution System can be aligned horizontally from the continuous data flow of control systems to the transaction data processing of business-based systems. Plant Applications’ primary role in a plant information system is to bridge the gap between continuous time-based data and the manufacturing and business transaction-based data that is found throughout the plant.
Plant Applications has powerful tools that segment the continuous data by the discrete events in order to make decisions concerning grade performance and process optimization. These tools perform this critical function by detecting the important events in the plant, reconciling continuous and event-based data, setting the context of the data through business rules and definitions, and summarizing key variables for long-term performance analysis.
Plant Applications models are used to capture events such as reel turn-ups, batch starts/stops, product changes, consumption of product on a production line, and so on. The Event Manager Service watches for different types of data to change and creates events based on that data. Events are created based on specific models, which describe what data to watch, and how to interpret that data to produce an event. For example, an event model may call for the event management service to watch a set of tags in the historian to capture when a batch was started or completed, capture or create the batch ID, and capture or create the product code of the batch.
A library of event models ship with each Proficy Server. Inside the Plant Applications Administrator, you may browse through available models to determine which model applies to your current situation. If no standard models apply, it is recommended to derive a site-specific model using a generic model as a base. Certain types of event models may be restricted by the licenses purchased.
See Also