About

This section contains basic information about classification configurations in the Metrix Asset Management system.

Subsections of About

Component Flags

Component flags are simple ways to toggle the expected requirements of a component group. Such flags include:

Conditioned:

The conditioned flag indicates if components assigned to the relative component group will typically require condition assessments to be conducted. Setting this flag to ‘off’ will mean that any assigned components do not contribute to any ‘missing condition’ counts or filters.

Depreciable:

The depreciable flag indicates if components assigned to the relative component group will typically require periodic depreciation charged against its carrying value. This can be useful for report generation as well as tracking the state of the organisations depreciation runs.

Carries value:

The carries value flag indicates if components assigned to the relative component group will typically be posted against in the financial transaction ledger. This would be set to ‘off’ for non-valued assets that are included for reference or other reasons.

Smart Attributes

Smart attributes can be defined to link an asset components attribute to the underlying spatial feature, and setting its value to the length or area of said geometry. Once an attribute has been defined as a smart attribute for a given classification, its value can no longer be set by end users. Rather, any changes to the underlying spatial feature will trigger an update of the fields value.

In order to be defined as a smart attribute, the form field must be marked as required.

Info

The definition of a smart attribute, like cost unit formulas, must be done via the classification screen. This is because form definitions can be shared across multiple classifications, and it may not be correct for an attribute to be ‘smart’ for all of the classifications that rely upon it.

Cost Unit Formulas

Cost unit formulas can be defined to calculate an asset components cost unit value according to a user defined algorithm based on the underlying attribute form and/or any defined smart attributes. When a cost unit formula is defined and in force, end users will be unable to manually set the ‘Cost Units’ value for asset components within that component group.

Example

Consider the Surface component of a Local Road asset. The Intervention Treatment assigned to the component may have a Unit Rate that is based in square metres. Therefore, the units of measure for the component Cost Units would also need to be in square metres. This Cost Unit value can be set automatically by a Cost Unit Formula result.

Firstly, the organisation would need to define an attribute form with at least the following two (2) fields:

  • Length: as a required, numeric field (possibly a smart attribute linked to a line length)
  • Width: as a required, numeric field

With the attribute form assigned to the Road Surface component group, the organisation would then define the following Cost Unit Formula:

[Length] x [Width]

Assigning this formula as the component group’s Cost Unit Formula would then cause any assigned components to have an automatically calculated Cost Unit field that will react to changes to the Length and/or Width attributes.

Classification Resources

In addition to linking resources for use throughout an asset portfolio, the classification configuration screen allows you to set other properties that control the behaviour of assets and their components throughout the Metrix Asset Management system.

This includes setting resources for both:

  • Asset level classifications, and
  • Component group level classifications.

All classification linked resources can be managed from the classification configuration screen (in addition to the link portals on the resource management page). This includes the following resource types:

Asset Level Resources

Component Level Resources