Classification Configuration

The Classification Hierarchy is typically configured as part of your Maintenance Connection implementation. Following are some general guidelines for configuration:

• Configure the hierarchy to allow for optimum reporting.

  Reports can be configured to include information on designated nodes and/or all classifications below that node.

• The hierarchy should be based on logical groupings of classifications, rather than being component-based.

  This means the classifications under a given node (children) should be types of classifications for that node, not components of the node. This is in contrast to the Asset Hierarchy, in which it is common to structure the hierarchy on a component-basis.

Here is an example of a well-configured classification hierarchy:

• Vehicle

  • Car

  • Flatbed

The values car and flatbed are appropriate children to the vehicle parent/node as they are types of vehicles.

In contrast, values like batter and engine would not be properly configured as children since they are components of the parent, rather than types of classifications associated with the parent. This type of configuration will not support logical report groupings of similar assets.