Emerson Deltav batch Interface



Download 2.43 Mb.
Page8/37
Date09.06.2018
Size2.43 Mb.
#54070
1   ...   4   5   6   7   8   9   10   11   ...   37

PIModule Creation


The interface performs automated module and unit creation within the PI Server. PI Units (PIModules with the IsUnit flag set to true) are created if needed when they are first encountered in the data source. The following modules in DeltaV equipment hierarchy are maintained by the interface: Area, Process Cell, Unit and Phase Module. By default, the placement of these modules is at the root level of the Module DB. Although, the user can define an optional Starting Module Path by using the (/smp command line parameter) under which the equipment hierarchy will be created. The default structure of the PI module hierarchy utilized by the interface is depicted in Figure 9.

Figure 9. Interface PI Module DB Structure

The DeltaV Batch automatically references PI tags at the unit and phase PIModules through tag aliases if tag names contain unit and phase module names. If the tag name contains reference to the unit and not the phasemodule, then only Unit Alias is created for this tag.

If for any reason default equipment hierarchy is not feasible, then the interface allows creating custom equipment hierarchy through the use of Equipment Template (Table n). Equipment Template should be defined in INI file associated with specific interface instance.

Note, if SQL Alarm&Events SQL server is defined as one of the data source(s), the interface will use this Equipment template definition only down to [Unit] level. All underlying module names will be named exactly as it is provided by the data source.



Equipment Template definition

Template

Value

Allowed

Placeholders



Description

Equipment




[Area]

[ProcessCell]

[Unit]

[PhaseModule]



This template defines the ModuleDB structure which the interface creates automatically. The Module names should be delimited by the “\” character.

Restrictions:

The hierarchy order must be maintained in the following order:

[Area] (optional)

[ProcessCell] (optional)

[Unit] (required)

[PhaseModule] (optional)

Note: Any reoccurrence of already defined placeholder is treated as text.

Default: Equipment=[Area]\[ProcessCell]\[Unit]\[PhaseModule]

Example 1:

The Equipment Template is defined in INI file as follows:

Equipment = abc:[unit]\Phases\[unit]:[phasemodule],

Where the first [unit] placeholder is marked as PIUnit and the second [unit] placeholder serves as a prefix to a PhaseModule and which is marked as PhaseModule name.

Assume: that incoming event contains Unit=U101, and PhaseModule=Agitator, then resulting PIModuleDB hierarchy is shown in Fig. 10.

Figure 10. Equipment Hierarchy for Example 1.


Example 2:

The Equipment Template is defined in INI file as follows:

Equipment = Just_Testing\areas\abc:[area]\Cells\def:[processcell]\Units\ghk:[unit]\Phases\

orspr[unit]:[phasemodule]\miseleneous

Assume that the incoming event contains:

Area=BLOCK1

ProcessCell=DEP10

Unit=SW101

PhaseModule=HEAT

Then, the resulting PIModuleDB hierarchy is shown in Figure 11.

Figure 11. Equipment Hierarchy for Example 2.






Download 2.43 Mb.

Share with your friends:
1   ...   4   5   6   7   8   9   10   11   ...   37




The database is protected by copyright ©ininet.org 2024
send message

    Main page