Classification Standard are represented in SAP Intelligent Asset Management in the Templates application by classes, subclasses, templates and associated Attributes and – if applicable – code lists.
A certain set of classification content is delivered with SAP IAM, i.e. classification content coming from ISO 14224 (version 2006), EN 15380 (version 2006). With SAP Asset Intelligent Network (SAP AIN) there is additionally the option to use eCl@ss classification content (version 10.1).
This blog first describes the general use of classification content in SAP IAM, and - in the second part - also introduces the use of eCl@ss classification content.
Classification Modeling is done using the Templates application in the SAP Intelligent Asset Management solution.
- Structural objects
- Classes and Subclasses
- Templates for Models, Equipment, Locations, Spare Parts, and Systems
- Attribute Groups, Attributes, Code Lists (associated with an attribute) – all are associated with a Class, a Subclass and/or a Template
Consumption of Classification objects is done in the Data Sheet section of a business object that has Subclass and/or Template assigned.
Classification objects are loaded as SAP IAM Template objects, i.e. classes, subclasses, attribute groups, attributes and - where applicable - templates. The templates can be differentiated by the object types that they can be used with, i.e. Model Template, Equipment Template, Location Template, System Template and Spare Part Template. To use an attribute in a business object it needs to be assigned to at least one attribute group which itself also needs to be assigned to at least one class, subclass, or Template.
In general, classes and subclasses are either delivered by SAP or a classification content provider. If the classification standard also contains attributes, these are also part of the delivered content. Delivered content can be re-used by customers, but it cannot be edited.
Customers (= organizations) can create own Template objects and own attribute groups, attributes and code lists. Here the organization owns its objects and can decide how they are being used, e.g. used only internally or get shared with selected connected partners (in SAP AIN).
In cases where customers create own template objects and share those with connected partners, they are also responsible for their content, e.g. if Template objects get created which are based on a classification standard not delivered by SAP, it needs to be ensured by the creator of the content that use respectively sharing in the network is allowed by the classification content owner.
Organizations want to classify by:
- A pre-delivered classification standard
- A pre-delivered classification standard and organization-owned templates*
- Multiple pre-delivered classification standards
- Multiple pre-delivered classification standards and organization-specific templates
- Organization-owned templates.
Note: Organization-owned can be company-specific objects, but also classification content from industry standards which are not pre-delivered by SAP and/or a classification standard provider (please refer to Note above).
Use Case Implementation
Example for a classification structure and the relationship to model and equipment
The following example explains how classification objects are delivered and get used:
1. Classes – delivered by SAP (based on an industry standard) or by a classification standard provider can be considered the top-node of the classification used in SAP Asset Intelligence Network, SAP Predictive Maintenance and Service cloud edition, SAP Predictive Maintenance and Service, on-premise edition or SAP Asset Strategy and Performance Management.
Note: A class does not have a parent object but can have multiple subclasses as child objects.
2. Subclasses – also delivered by SAP (based on an industry standard) or by a classification standard provider can be considered as 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 – usually 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.
4. Equipment Templates – usually either created by manufacturers for operators or directly 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.
Similar to the model template it is possible to have multiple equipment templates under the top-level equipment template. Each child equipment template will inherit attribute or attribute groups from its parent object, that is, equipment templates.
SAP Asset Intelligence Network and eCl@ss
eCl@ss is a cross-industry product-data standard for the classification and unique description of products and services. For more information on the company as well as the standard itself, please refer to the official eCl@ss Web pages (https://www.eclass.eu/en.html).
SAP Asset Intelligence Network (SAP AIN) and eCl@ss have a partnership, and eCl@ss acts as a Content Provider in SAP AIN. This means that eCl@ss is a participant in the network, and eCl@ss classification objects get created by eCl@ss in their account and will be shared by eCl@ss in the network as follows.
In SAP Test and Demo system
- A subset of eCl@ss classification content will be made available for trial use to all customers in the Test and Demo system.
- Trial use of this subset of eCl@ss classification content is free for all customers in the Test and Demo system.
- NO migration option from Test and Demo system to a later use in Production system.
In SAP Production system
Sequential upload of eCl@ss classification content based on customer requests.
eCl@ss will share their classification content with customers who have an eCl@ss license.
Note: eCl@ss licensing is handled directly by eCl@ss office (contact: email@example.com)