- 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
Note:
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.
- 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).
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.
- 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.
Note: eCl@ss licensing is handled directly by eCl@ss office (contact: info@eclass.de)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
10 | |
7 | |
4 | |
3 | |
3 | |
2 | |
2 | |
2 | |
2 | |
2 |