Emerson Deltav batch Interface
OPC Alarm&Events Server as Data Source
Download 2.43 Mb.
|
- Navigate this page:
- Recipe Model vs. Equipment Model
OPC Alarm&Events Server as Data SourceOPCAE server is another component of the DeltaV Batch Execution System. Starting with version 10.3, OPCAE server provides batch events performed by the BES in real time. The use of OPCAE server is optional and is not required by the interface. Although, if it is used as an additional data source, it allows processing of batch data into the PI server in real time, not scan based. The OPCAE server can be specified only in conjunction with the DeltaV SQL server, which serves as backup source as well as the source for additional batch associated events. Recipe Model vs. Equipment ModelTwo distinct yet related models are used to describe batch processes. These are the Recipe Model and the Equipment Model. Diagrams depicting hierarchical structures, in particular those for the S88-compliant hierarchical structure, of these models are shown in Figures 5 and 6. The Equipment Model describes the physical equipment necessary to create a batch while the Recipe Model describes the procedures, which are performed during the execution of a recipe. There is no intrinsic or direct relationship between the levels of the Equipment Model and the Recipe Model. With the exception of Arbitration events, journal files contain only Recipe Model event information. It should be noted that within S88, the use of procedures and unit procedures is optional. A recipe may be defined consisting of only operations and phases. Figure 5. Recipe Model hierarchy 
Figure 6. Equipment Model hierarchy 
The Batch interface uses S88 terminology and hierarchy as framework to collate and store information in a structured manner within the PI Module and Batch databases. The Batch interface makes an assumption that a unit procedure maps directly to a PI UnitBatch. This assumption implies that only a single unit procedure can be active in a unit at any given time. This lays a fundamental restriction on the configuration of recipes that may be run by the BES, if the Batch interface is to be used to process the resultant data and populate the BDB in a meaningful manner. If there are overlapping Unit Procedures on the same unit, the interface closes the conflicting PI UnitBatches, although the data is still processed into closed PI UnitBatches. The actual end time for truncated UnitBatch is stored in its Product property. The actual Product is appended by the keyword “_TrueEndUTC=” which is followed by UTC seconds representing the actual End Time for specific unit batch. If the recipe is divided in multiple smaller unit procedures or operations, the DeltaV Batch interface should be run with merge startup command line parameter for entering that data into the PI server. Please refer to the Merging Multiple Source batches into a Single PIBatch section for more information on how the merge works. Directory: interfaces interfaces -> Pi interface for Siemens Spectrum Power tg (Linux) interfaces -> Interface to the pi system Version 37 and Greater interfaces -> Citect Interface interfaces -> Interface to the pi system interfaces -> How to Contact Us interfaces -> How to Contact Us Download 2.43 Mb. Share with your friends:
|