Templates

A template is a format created by SAP Asset Strategy and Performance Management organization (for example, manufacturer, operator, or service provider) to maintain metadata, that is, attributes and attribute groups, related to a model, equipment, location, system, or spare part. A template inherits metadata from its parent objects, for example, parent subclass templates or other parent templates, and can have additional attribute groups and attributes.

Example:

A model template inherits the structure from a parent model template, a parent subclass template, other related parent subclasses, and the parent class.

A template in SAP Asset Strategy and Performance Management is identified by a unique name and comprises of attribute groups and attributes. An attribute group is a logical grouping of related attributes of the equipment, model and location, and an attribute is a qualifier to define the equipment.

Example for a classification structure and the relationship to model and equipment

The following example explains how classification objects delivered by SAP Asset Strategy and Performance Management, classification objects that can be created by customers, and type and instance information also created by customers relate.

  1. The class level – delivered by SAP Asset Strategy and Performance Management based on an industry standard – can be considered the top-node of the classification used in SAP Asset Strategy and Performance Management.

    A class does not have a parent object, but can have multiple subclasses as child objects.

  2. Subclasses – also delivered by SAP Asset Strategy and Performance Management based on an industry standard – are the child objects of a class. It is possible to model multiple subclasses under the top-level subclass. Each child subclass will inherit attributes or attribute groups from its parent objects, that is, class and subclasses.

    In the example:

    • • Subclass 1 (Power transformer) would inherit from Class (Transformer)

    • Subclass 2 (Dry-type transformer) would inherit from Subclass 1 (Power transformer) and Class (Transformer)

  3. Model Templates – created by manufacturers – can be child objects of a subclass, or be used without a parent object. It is possible to have multiple model templates under the top-level model template. Each child model template will inherit attribute or attribute groups from its parent objects, that is, class and subclasses and model templates.

    When creating a model, you do this with reference to a model template.

    In the example:

    • Model Template 1 (SDT) would inherit from Subclass 2 (Dry-type transformer), Subclass 1 (Power transformer), and Class (Transformer)

    • Model Template 2 (SDT-100x) would inherit from Model Template 1 (SDT), Subclass 2 (Dry-type transformer), Subclass 1 (Power transformer), and Class (Transformer)

    • Model would be created with reference to Model Template 2 (SDT-100x), and therefore the Model would have all attributes or attribute groups coming from the model template itself as well as the ones inherited.

  4. Equipment Templates – created by operators – are used to provide equipment-specific attributes or attribute groups. You can use equipment templates as only reference for an equipment or in combination with the templates coming via a model.
    In the example:

    • Equipment was created in reference to Model, and therefore this equipment would have all attributes /attribute groups associated with the model, that is, inherit from Model Template 2 (SDT-100x), Model Template 1 (SDT), Subclass 2 (Dry-type transformer), Subclass 1 (Power transformer), and Class (Transformer)

    • Since Equipment was also created in reference to Equipment Template, this equipment would additionally have all attributes or attribute groups associated with the equipment template.