Template modeling examples

The following information describes two template modeling examples:

Example 1

This example describes the model of a process that contains thee types of tanks. The types are determined from device requirements. To optimize engineering development, a common derived template called $Tank that utilizes an object wizard is developed from the $UserDefined base template. The contains all device requirements and multiple configurations of tanks can be built from the template by selecting different object wizard options. If some tank configurations cannot be easily accommodated by the $Tank template, additional templates can be derived from it.

The following figure illustrates how these templates can be developed:

A base tank template contains the fields and settings common to all tanks within the facility. A new template is then derived from the base template for category of tank and contains settings that are specific to that type.

Object instances are then derived from the applicable template to represent the actual tanks.

Example 2

This example describes a common, complex relationship called Reactor. Reactor is based upon an interaction of five field devices. Multiple instances of this relationship are used within the plant model.

The relationship can easily be developed using containment.

Create a derived template called $Reactor from the $Tank_Mixing template shown in the previous example.

Then, create template instances representing each of the five field devices from a derived template (again, based on the $UserDefined template). The complex relationship can now be developed (using scripting) in the container object ($Reactor) using the hierarchical names given to each field device. When instances of $Reactor are created as field devices, each has two names: the containment name (hierarchical name); and the physical name.

The following figure illustrates this practice: