1 of 1 people found this helpful
Lots of good questions for a relatively complex and powerful interface.
I posted this a few years back on a different account:
Attribute Templates: When the Batch Interface is configured to create Event Frames these become static values that are PI AF attributes of Event Frames with no data reference. When using the PI Batch Database the property template defines the properties of a PI Batch.
Tag Templates: In general, tag templates allows for the storage of data in PI tags and should be used for time series information such as multiple values per Event Frame or the ability to trend data. It makes sense to use a property if there is just one value to be stored per Event Frames using an Attribute/Property Template.
Recipe Templates allow for customization of the Event Frame or PI Batch objects themselves. For example, we can give the Event Frames or PI Batch objects a custom name, descriptor (AF only), Product (both Batch and AF) and more per the manual. The index for recipe templates refer to the level in the recipe. That means level 1 refers to the procedure level and two is the unit procedure level.
A sample INI file here that you could experiment with.
2) If the tags you want to add already exist, that is an excellent case for a recipe template. Recipe templates should point to AF Event Frame templates that take advantage of the reference elements. Basically, put the tags on the elements and refer to these tags from the event frame template.
3) If the source does not match, it will try to create the elements. There are some switches to control the element hierarchy creation if needed.
4). Property templates are for EF attributes that do not have PI Point data references. For example, the operating, the type if ingredient, or the PH sample time.
This is a rather complicate topic. Hope I helped!