This section describes the steps involved in developing a Template.

Templates represent the specification of repeatable patterns of XML that is to be instantiated. Template can be reused, and Templates can constructed form other Templates. An example is the template: SerialisedAsset used to represent an asset that has a serial number. The is template compromises of the following templates:

RealizedPart

StockItem

Part

ViewDefinitionContext

This is illustrated in Figure 1.

Consequently, when designing a Template consideration should be given to what or what level in an information hierarchy the Template is.

At the top level, the Template corresponds to a business objects.

Other templates are intended to be reusable patterns used from within Business objects. If the template is generic and likely to be used in a number of different contexts, then it should be considered an OASIS template and developed as such.

If the template simply defines a mapping to a single PLCS PSM block, then the template probably should not be developed since this would be replicating capability presently in the PSM.