Classes

Classes group similar design and technical information. They are always owned by a standard and are the primary sorting function within Asset Design. A process design system has related classes created for pumps, motors, pipes, heat exchangers, tanks and cables, among others. Similarly, electrical, instrumentation and piping design systems will have their own set of classes. Each class contains similar technical information, guides permissible relations and display properties, and controls the functionality and behavior of Asset Design:

Most of the important design object settings occur on a per design object class basis, as defined in Asset Design/Class Basic Data pages, for example:

Engineering part settings occur on per part class basis as defined in PDM/Basic Data/Part Classes page, for example:

Design Object Class Components

Each design object class is comprised of (and/or influenced by) the following:

Engineering Part Components

Each design object class is comprised of (and/or influenced by) the following:

Creating Design Object Classes

The most important considerations for the creation of a class are:

Class Naming and Sorting Conventions

The following conventions are used when naming and configuring classes:

Design Object Class Considerations

Design object classes are created before adding the member objects. Often the class name (or an abbreviated version of it) will be part of the object ID. It is easier to create the unique object IDs if the class designation already exists.

When setting up object class names, the object's technical data and ID designations should be considered as follows:

Part Class Considerations

Part classes are created after their corresponding design object classes have been created, and they will usually be given the same names as the design object classes. For example, the design object class, PUMP, and the part class, PUMP.

Class Identifier

A class identifier, which is a mandatory designation for each class, is used to give the class a common name when different sites use local language names for the class. For example, a class identifier could be set to the English-language Pressure Vessel. For a site in Sweden, the class name Tryckkärl would be used and a site in Germany would use the class name Druckbehälter. However, both sites would use the English-language class identifier Pressure Vessel as a common class name. The Class Identifier becomes invaluable when comparing, importing and exporting data between IFS/Asset Design sites in different countries.

Default Design Object Class

A default class structure exists to enable the creation of design objects without defining a specific class. The default class is particularly valuable during the early stages of the design when the Asset Design database is being populated with design objects. The default class structure also has a validation function that assigns an object to the correct class based on the given parent object ID. 

This default class has the following characteristics:

Setting and Clearing Entity-Type Design Object Class Definitions

A class that is set as a design object class in the Class page and then cleared of this definition, no longer allows the registration of objects to it. A class for which the entity-type definition has been cleared does not appear within Lists of Values and cannot take part in a class change. Design objects belonging to a class for which the entity-type definition has been cleared are still visible within Design Object Explorer, but further registration to that class is prohibited.

Changing Design Object Class 

A design object class can be changed from all object pages using a command button option. A dialog box opens showing the current class. The new class is then selected from a pull-down list containing available classes. The available classes are determined by Parent Class.

The following rules apply to object class changes:

Parent Class

The parent class is defined on the design object class level. The parent class structure determines if a design object class change is allowed and to which classes the design object class may be changed. A design object class without a designated parent class is not allowed a class change. 

Parent classes are defined with general class information. For example, Pump Misc would have a general class configuration applicable to centrifugal and diaphragm pumps as well as controlled volume and hydraulic pumps. This is important to avoid conflicts and loss of information, such as technical data, class relations, and class properties when the object's class is changed.

A temporary class structure can be created to group objects by their probable class inclusion. Such a structure is created by defining a parent class for multiple object classes. For example, a generic pump object could be temporarily assigned to the class, Pump Misc. Later, it can be assigned to the Pump Centrifugal class, which would be required to have a parent class of Pump Misc.

An object's class with a designated parent class may be changed to the following accordingly: