System Navigation

Depending on your account privileges – which will be set by your system administrator – you will see different functions available to you when you first login. There are, however, a couple of core system pages that will be available to you regardless of your account privileges. This section details some of the basic facets of these pages.

1. To navigate to each page of the Metrix system, use the section header located at the top of the application. Regardless of where you are within the system, this section header will always be available. The section header will generally look like the following:

2. Review the Dashboard Page - The dashboard provides a quick and easy overview of some core statistics about your assets within the system. This can be useful for extracting charts and graphs for generating your Asset Management Plans and Policies. It is also handy for gaining a high-level snapshot of your asset performance.

3. Review the Assets Page - The assets page is the main engine room of the system. This is where users can view their asset portfolio through an intuitive map interface, fetch information, as well as perform edits on that information.

4. Review the Capital Page (permissions dependant) - The capital page is where you can manage your capital works projects. This includes the ability to create, edit, and track the progress of projects, as well as view associated costs and timelines. Additionally, you can manage settings such as the current financial year and the like.

5. Review the Operations Page (permissions dependant) - The operations page is where you can manage your operational activities. This includes the ability to create, edit, and track the progress of operational tasks. These can include maintenance activities, inspections, and other operational tasks related to your assets.

6. Review the Reports Page - The report generation page is full of predefined report templates to help you extract the information you need about your assets. Additionally, you can access previously generated reports from within this page.

7. Review the System Menu - In the top right-hand corner of the application, you will see a menu drop-down labelled with your organisation’s Site ID. This contains all site configuration options (if your account has the rights to see such settings). It is also where you can access and manage your Profile information and sign out of the application.

Initialising a Metrix Account

Before you can use your Metrix Asset Management System, you must have a valid Metrix account with which you can login with. To gain access to such an account, your organisation’s system administrator needs to generate an invitation for you to register. If you have not received an invitation, please consult your organisation’s system administrator.

Once invited, you will receive an email with your username details as well as a temporary password that you need to change immediately. Follow the ‘Sign In’ button from this email to perform the password change.

Your new password must meet the following requirements:

• Minimum length of 8 characters
• No spaces
• At least one uppercase letter
• At least one lowercase letter
• At least one number
• At least one special characters (excluding + and -)

Once you set and confirm your new password, you can safely delete the invitation email. Please note that the invitation email will expire after 7 days. At which time, a new invitation will need to be generated.

Logging in to Metrix

To log in to your Metrix Asset Management System environment, you will need to know your organisation’s Site ID and have a valid username and password for that environment. Your organisation’s Site ID is used within the web URL of your system.

Once you enter your organisation’s web URL, you will be presented with a login page. This page is requesting your username – which is your email address – and the password that you have defined when initialising your Metrix account (see Initialising a Metrix account for details on this).

Resetting your Password

If at any time, you forget your password for the Metrix Asset Management System, you can request a password reset from the main login page. To do this, complete the following steps.

1. Click on “Forgot Password” below the “Sign In” button and you will be redirected to the password reset page.

2. Enter your username – which is your email address – and click “Reset Password”.

3. At this point, you will be redirected to a password reset verification stage. A verification code will be emailed to your email address.

4. Once you have received your email, enter the verification code along with a new password. The new password must also meet the password requirements stipulated above (see Initialising a Metrix account for details on this).

Map View Tools

This page covers some of the basic navigation options available within the core ‘Assets’ page in the Metrix Asset Management system including:

• Pan / Tilt / Zoom the map window
• Info Tool
• Search

Map Window Pan / Tilt / Zoom

The built-in map window inside the main ‘Assets’ page supports various computer mouse gestures to interact with the map location and view. These are detailed below:

Pan:

Panning a map means to shift the map image relative to the display window without changing the viewing scale.

To pan the map window, hold down the ’left’ (main) mouse button and drag your cursor. The map will follow until you release the mouse button.

Zoom-In:

‘Zooming in’ refers to the action of adjusting the view of the map to make a specific area appear larger and closer.

To zoom in, scroll the mouse wheel up.

Zoom-Out:

‘Zooming out’ refers to the action of adjusting the view to make the image or area ot he map appear smaller and farther away.

To zoom out, scroll the mouse wheel down.

Rotate:

‘Map rotation’ is a way of viewing the map window from a different orientation.

To rotate the map view, hold down the ‘right’ mouse button and drag your cursor to the left of the map window. The map will continue to rotate in a clockwise direction until you release the mouse button.

Note: to rotate counter-clockwise, drag the cursor to the right.

Tilt:

‘Map tilt’ refers to the angle at which the map is being viewed from. By default, the tilt is ‘flat’ and being viewed from directly above. When ’tilted’, the map view is angled so that the user feels they are looking ‘along’ the map.

To tilt the map view, hold down the ‘right’ mouse button and drag your cursor up to the top of the map window. The map will continue to tilt until you release the mouse button.

Note: to reverse the tilt, drag the cursor down.

Info Tool

In order to interrogate an asset via the main ‘Assets’ page map window, pan & zoom the map window to the asset location and single click (left-click) on the asset’s spatial feature.

The info panel will appear/populate on the right hand side of the map window when one or more valid features have been interrogated by a click.

Search

In addition to basic pan and click operations, the Metrix Asset Management system contains a free text search tool that can navigate and select chosen results for you. To start a search, simply click inside the search pill at the top of the page, and begin typing your criteria. The following asset/component fields are included in the search index:

• Asset Description
• Asset ID
• Component Description
• Component ID

The search tool will begin looking for results immediately and render them in a box below the search pill. By default, ‘All Results’ will be shown. Users can however, refine their results to the following result levels:

• Assets
• Components
• Programmes

Info Panels

This section details the info panels available within the core ‘Assets’ page in the Metrix Asset Management system including:

• Component Info Panel
• Intervention Info Panel
• Transactions Info Panel
• Programming Info Panel
• Parent Asset Info Panel

Info Panel Tools

In addition to the above panel structures, various tools built into these information panels are also detailed, including:

• Actions Menu
• Map Zoom Options
• Expand/Collapse Content
• Information Shortcuts
• Collections Interfacing
• Managing Pending Edits
• Component Group Selection
• Copying Field Values

Basemaps & Focus Mode

The Metrix Asset Management system provides built-in access to publicly accessible aerial photography imagery as well as basemaps as backdrops to your asset portfolio. These layers provide users with helpful context on the area they are viewing in the map window. To further assist with seeing asset content in association with these layers, Metrix also contains some tools to modify which backdrop you are seeing, as well as the colour intensity of the backdrop in comparison to your asset portfolio.

Focus Mode

For nearly all users, there exists a colour combination that is hard to decipher between and thus difficult to read when displayed in a map window. To cater for this, the Metrix Asset Management map tools provide users with the ability to put the map backdrop into ‘Focus Mode’. This will binarise (to make black-and-white) the backdrop so that the colours of your asset portfolio are easier to distinguish.

View Aerial Imagery as Backdrop

To view the aerial imagery as a backdrop to your asset portfolio, simply click on the ‘Imagery’ button in the top-left hand corner of the map window. This will swap out the underlying view to the aerial photograph imagery configured for your environment. The screenshot below shows a map window with aerial imagery as the backdrop, split between focus mode and standard.

View Basemap as Backdrop

To view the basemap as a backdrop to your asset portfolio, simply click on the ‘Base’ button in the top-left hand corner of the map window. This will swap out the underlying view to the basemap configured for your environment. The screenshot below shows a map window with basemap as the backdrop, split between focus mode and standard.

Custom Filters

The Metrix Asset Management system is equipped with a built-in data filtering tool that works across a variety of pages and functions within the system. This allows users to create and manage subsets of their entire asset portfolio for viewing, reporting, as well as sharing with other users of the system. Additionally, the data filtering tools can aid in highlighting asset management targets within your asset portfolio - filters can be combined to create multiple restrictions on included components.

Saving & Sharing Filters

Once a filter has been configured, users can choose to save that filter for later reuse. Saved filters can also be shared so that all users of the system can leverage that filter set.

Filters across the System

In addition to the core ‘Assets’ page map window, the filter tool works across the Metrix Asset Management system in areas such as:

• Dashboards,
• Report Exports, and
• Capital Budgeting

This means that users can define a filter once, and then, view dashboard widgets as they pertain to that reduced data set only. Further more, users can create a filter and then export the results of that filter to a CSV report by choosing the filter in the reports page.

Filter Options

The following options are filterable in the Metrix Asset Management System:

• Asset Classification
• Component Group
• Status Code
• Reporting Category
• Condition
• Useful Life
• Residual Life
• Next Intervention Year
• Metric Values (area, length, diameter, height, length, volume, and width)
• Component ID list

Map Themes (Visualisation)

The Metrix Asset Management system is equipped with a built-in map theming tool that works automatically with your data and attributes. This allows users to visualise breakdowns of their entire asset portfolio, assisting in better and faster decision making. Additionally, these visualisation tools can aid in highlighting asset management targets within your asset portfolio.

Available Map Themes/Visualisations

There are a number of built-in map theme visualisations that are ready to work immediately for you. These cover a range of areas from lifecycle theming, to report category visualisations. The following details some of the available themes. This is not an exhaustive list, but provided for context on the types of themes provided.

General Map Themes

These map themes switch around the asset classification and status.

• Asset Class

This is the default visualisation theme for the system. Each component is coloured according to its Asset Class (the first level of the asset classification structure).

• Component Group

This theme colours according to the Component Group level of the classification structure. This offers far more granularity than the Asset Class theme.

Users should be aware of potential stacked geometry issues when using this theme.

• Status

The status theme colours each component geometry according to its current status code.

Intervention Map Themes

These map themes aim to highlight the lifecycle metrics associated with your asset portfolio.

• Condition

The condition theme displays components on a colour gradient from green (1 - excellent) to red (5 - really poor).

• Residual Life

This theme converts a component’s residual life to a percentage of its overall useful life. The result is then displayed on a colour gradient from green (100% remaining life) to red (0% remaining life).

• Construction Year

This displays components in a accordance with their recorded original construction date. This is a useful data audit tool as it will highlight anomaly records (in comparison to the surrounding asset components).

Report Categories

The system takes each of your configured report category configurations and automatically creates a map theme to render each component in accordance with their assigned option within that category (including missing or no assignments).

The map theme switcher will render an option for each configured report category.

Metric Attributes

The custom attribute form specifications contain several restricted attribute names that relate to component metrics such as width, length, height, etc. If any of these fields are implemented within your component custom attribute definitions, the map theme generator can style your geometries based on these numeric results.

Custom Attributes

Any custom attribute definition that is controlled by an option list will be available within the map theme switcher for render.

Collection Sets

The concept behind collections within the Metrix Asset Management system is to allow users to choose various components from a map or list, and build an actionable group from them. A collection, in other words, is a selection set that users can use in system actions.

Once a collection set has been constructed, users can use that collection to:

• Perform bulk data updates
• Schedule inspections
• Generate reports
• Create custom filters using the entities in the filter

When a component is included in a collection set, the spatial feature will be rendered with a halo, highlighting it to the user.

As mentioned in the above list, collections can be converted into permanent custom filters. User can also start a collection from the components resulting from an existing custom filter. There is a two-way interoperability at play here.

Spatial Features

An elemental facet of the Metrix Asset Management system is spatial representation of asset components. At a basal level, this is enforced by the mandatory requirement that every component maintained in the system MUST reference a valid spatial feature. The system has been built around the existence of spatial features, and several tools exist to make this both beneficial, and easy for end users, including:

• Feature sharing across asset components.
• Built-in geometry editing tools,
• Integration with 3rd party GIS editing platforms such as QGIS,
• Attribute updates tied to relative spatial properties, and
• Performing asset operations using spatial techniques (line split),

Shared Component Geometries

Each spatial feature in the system is its own record. That is, the geometry is not ‘just’ another attribute of the asset component. Instead, by maintaining spatial features as distinct entities, we are able to ’link’ a single geometry to more than one component. This means, you can have the same line feature representing the earthworks, base, and surface of your road asset. Editing the line once, will update the representation for all.

It should be noted, however, that this sharing feature is not mandatory. Within an asset, each component could have their own distinct spatial representation. YOu could even maintain a hybrid approach, with two components sharing a geometry, whilst a third maintains a distinct feature.

The only caveat is that geometries cannot be shared across components with different asset parents. The relationship must stay within a single asset.

Managing Spatial Features

The system come with built-in spatial editing tools for basic geometry creation and updates. These tools are simple to use and support all simple geometry types; points, lines, and polygons. In the case that your geometric construction requirements are more advanced that those offered in system, the Metrix Asset Management system has published a free to access QGIS plugin that can connect to your cloud environment (using your Metrix account details), view your geometry data, as well as make edits and save changes back to the system.

Asset Operations with Spatial Tools (the line splitting tool)

With such a strong relationship to underlying spatial features, the Metrix Asset Management system is able to leverage geometric principles in offering advanced asset management operations, in an easy to use and understand package. Such an operation is the ability for users to SPLIT assets or components at a given point with the system handling all the financial apportionment of capital value for them. This is great for recording partial renewals, re-segmenting your network assets to cater for additional installations.

Smart Attributes

Another added benefit of mandating spatial features is the ability to leverage spatial properties as attribute information. See smart attributes for more information.

Residual Life Calculations

In simple terms, the Residual Life is the number of years that a Component has left/remaining before a capital intervention is required. The Residual Life is calculated as the difference between its useful life and the Component’s age plus any residual life offsets (see below) recorded against the Component.

As a Component goes through it’s life, it is expected that it will degrade/age over the years. How any particular Component experiences this ageing process however, will be in accordance with some very local factors relevant to that Component only. This means that any one Component could under-shoot or exceed it’s expected useful life - it also exemplifies how a Component’s useful life is just an averaged expectation, rather than a hard-and-fast rule.

To cater for such variations to lifecycle patterns, the system allows for the Residual Life to be ‘set’ by the user at any point throughout the Component’s life cycle. That is, the user does not modify the useful life of each Component, but rather, can set the residual life to the value they see fit.

This translates to a residual life offset being inferred upon the Component. This residual life offset takes effect upon the calculated residual life by being added to the calculated residual life.

It is for the reasons stated above, that the formula for Residual Life in the Metrix Asset Management system is:

Inputs to Residual Life

The following provides additional details on the inputs to the residual life formula discussed above.

Residual Life Offset

A component’s residual life offset is an offset applied to the calculated ‘residual life’, to either increase or decrease the resulting value. The residual life offset is calculated by the Metrix Asset Management system as the difference between the calculated ‘residual life’ and the subjectively assessed remaining life. That is:

There is NO requirement of a user to consider the concept of residual life offset when altering the residual life of a component. In fact, a user can be safely ignorant of the concepts of residual life offset. All the user needs to supply (going by the above example) is that the residual life of the component should be 6, not 5. The system will take that value and calculate the +1 years offset in the backend.

If the user were to state that the residual life was actually 8, then the system would calculate an offset of +3 years.

As the residual life offset is applied to the residual life value after the initial basic residual life calculation takes place, the reported residual life will continue to decrease as time passes. The user does not need to do anything for this, the system will handle it all.

Capital Anniversary Dates

A Capital Anniversary date is a pre-ordained time of the fiscal year when a capital asset undergoes an ageing event. By default, Metrix environments are configured for annual (once per year) capitalisation. - however, this can be adjusted to suit the needs of the organisation to frequencies such as quarterly, monthly, or the like.

When a Component is first built, or renewed, it will receive a construction date and/or a last intervention date. The Capital Anniversary event relevant to this date is:

• the Initial Capital Anniversary. This is the date in which the Component will BEGIN ageing.

Throughout the Component’s life, two other Capital Anniversary events are continuously relevant to the Component - the Most Recent Capital Anniversary and the Next Capital Anniversary:

• the Most Recent Capital Anniversary is the most recent date in which the Component underwent an ageing event, and
• the Next Capital Anniversary is the next date in which the Component is scheduled to undergo a capitalisation event.

All of the above Capital Anniversary dates are listed in the ‘Intervention Summary’ section of the Component info panel.

Age

A component’s age is calculated as the difference between the first ‘capital anniversary’ that occurred after the component’s intervention date, and the most recent ‘capital anniversary’ to have passed.

Reports generated from the system support returning the age of a component at a date other than the current date. A report generated at a date of 2 years in the past, will return the age of the component at that date - not today.

Last Intervention Date

The last intervention date refers to the date in which a component last underwent capital intervention works relating to it’s treatment. This includes:

• the original_construction_date of the component,
• the date of major renewal works on the component, or
• the date of substantial upgrade works on the component.

The original_construction_date will NOT change following an intervention (i.e. a reseal for a road surface). Only the last intervention date will change over the course of a component’s lifetime.

Component Quantity/Size

The quantity/size of a component in the Metrix Asset Management system is stored within the ‘Cost Units’ value, in the ‘Intervention’ info panel. Given that component shapes and measurement techniques differ from type to type, and the method of ascribing a cost to that shape/technique is variable, the cost units value of a component is not restricted to a specific component metric such as length, area, volume, etc. Rather, the cost units number field is free to represent whatever quantity that is required to satisfy the assigned intervention treatment.

Metrix also supports the implementation of cost unit formulas to automatically calculate these values based off the value of certain metric fields. This is covered in another section pertaining to Smart Attributes and Cost Unit Formulas.

Component Treatments & Next Treatment

Intervention Treatments in the Metrix Asset Management System provide the ability for users to store and manage unit rates and default useful lives for a variety of component interventions. When assigned to a component group, treatment definitions are able to be used to define the current and/or next intervention method for given components.

Component Treatment

The current component treatment informs a component ‘Unit Rate’ (for current cost calculations), the ‘Default Useful Life’, as well as an indicator to the material and/or methodology used in it’s original construction. The later of these depends on the naming conventions used in defining intervention treatments.

Next Treatment

A component’s next treatment definition allows for users to record their ‘best guess’ how a component’s upcoming intervention treatment will be conducted. Such definitions can be based on:

• Estimated Cost: for works that may be based around an externally quoted price.
• Treatment with Override Unit of Measure: for works that will be conducted in accordance with a chosen treatment definition - but for a specific quantity of cost units.
• Treatment with Percentage of Component: for works that will be conducted in accordance with a chosen treatment definition - but for a percentage share of the component’s current cost units.

Financial Movements

The financial transactions ledger within the Metrix Asset Management system tracks the financial consumption and restoration of asset components over their lifetime. This data is then collated in a number of system reports that satisfy the financial reporting obligations of user organisations. The following outlines a number of terms used throughout the system, and how they tie into the financial frameworks in force.

Gross Value

The replacement cost of a component at the time of valuation (or revaluation). Gross value can increase or decrease over the life of a component through intervention actions such as additions or upgrades to the asset component. Another way that gross value increases or decreases is through indexation – this is essentially increasing the value of a component by a percentage amount, typically in line with CPI.

Accumulated Depreciation Value

The accumulated depreciation of a component is the sum of all depreciation transactions logged against it over its life time.

The formula for accumulated depreciation is:

In the Metrix Asset Management system, the accumulated depreciation is posted as a NEGATIVE NUMBER to reflect the fact that it is a ‘consuming’ factor.

Carrying Value

The carrying value of a component is the net worth of the component to the entity in adjusted terms. Carrying value is a calculated value that deducts the accumulated depreciation from the gross value. Given that the depreciation figure is already stored within the Metrix Asset Management system as a negative figure however, the formula for carrying value is:

Renewals and Depreciation

In the Metrix Asset Management system, a renewal expenditure is typically posted as a POSITIVE movement against the components accumulated depreciation. This is to recognise the fact that the action has ‘undone’ the financial consumptions of the past. In turn, the components carrying value (assuming renewal costs equal gross value and a fully depreciated component) is restored to its original gross value as expected.

Making a Selection

This guide provides an overview on how to make asset component selections from a map view withing the Metrix Asset Management system, including:

Selecting from the Map

1. When you wish to get information about an asset and/or component in your current map view, simply click on the spatial feature.

2. On the right-hand side of the window, an info panel will appear. If the area you clicked on contains more than one (1) valid asset component, you will be presented with the option to refine your selection down to the target component you want information about.

3. As seen above, each asset (falling in the range of your click location) will be grouped and the sub-components displayed for your choice. Click on the asset/component you wish to view.

4. The component info panel will then render for your chosen component.

   Info

   If the location of your mouse click only intersected one (1) component, you will be taken straight to this panel.

Changing Component Groups within an Asset

1. When viewing information about a selected component, you can switch to another component on the same asset using the ‘Components’ switcher on the left-hand side of the info panel.

2. Each available component group (on the asset classification configuration) will be rendered in this side panel. If the asset has one or more component entries against a particular component group, a component ID and status tag will be shown. Otherwise, it will state, ‘None’.

3. To view the information about one of the listed components in this list, simply click on that entry in this panel.

Changing Info Panel Display

1. To view different information about the selected component, users can simply switch between the tabs across the top of the info panel.
   Info

   The ‘Parent Asset’ tab contains asset level information and is therefore identical no matter what component within the asset you are viewing.

Using Custom Filters

This document provides an overview on how to filter your asset portfolio using the built-in custom filter tools, including:

Filtering Data

1. To get started using custom filters, navigate to the main ‘Assets’ map in the Metrix Asset Management system.

2. On the left hand side of the page, make sure the ‘Filter Data’ tab is activated.

3. Here, you will see a number of categories that can be used to filter the visible asset components in the map view.

   Note: If there is a current filter applied, clear it by following these steps.

4. Choose any category to begin your filter by clicking on the ‘filter pod’ for that category. For example: Click on ‘Condition’.

5. A menu fly-out will appear where you can then further define how you wish to apply the filter using the chosen category. These will typically be represented by checkboxes for restrictions to apply to your portfolio. For example: For condition, you may tick ‘Excellent’. This would restrict the visible asset portfolio to components with a Condition value of ‘Excellent’.

6. Filter conditions can be chained together. Click on another ‘filter pod’ and set some additional restrictions. For example: Click on ‘Residual Life Years’. The fly-out requests that you input two (2) values:

   a. The operator (<, >, =), and

   b. The value relative to the operator.

   Inputting > 6 would restrict the visible components to those with more than 6 years of residual life remaining.

7. To remove a specific filter definition, simply uncheck the restriction within that category. For value based filter settings, there is a ‘Reset’ option within the menu fly-out.

Clear the Filter

1. To clear an active filter, simply click the ‘return’ icon at the top of the filter panel. This will remove all of your configured filter settings.

   

   Note: This does not affect the settings of ‘Saved’ filters, but will clear the filter from being active.

Saving/Sharing a Filter Definition

1. The system supports the saving and sharing of filters. To do so, define your filter following the steps above.

2. Once you have finished configuring the filter properties, simply click on the ‘Save’ option at the top of the filter panel.

   

3. A fly-out menu will appear prompting you for a name for the new filter. Input a name for the filter (this is how you will find it later).

4. To opt to allow other system users to see the filter you have defined, toggle the ‘Shared’ control. By default, filters are private and NOT shared.

5. When you are done, click ‘Save’. The filter is now saved under that name. If you shared the filter, other users will see it in the ‘Filter Drop-Down’ at the top of the panel.

Using Save Filters

1. To use a predefined filter that you have saved, or another user has saved and shared, simply expand the drop-down menu at the top of the filter panel.

   

2. Here you will find a list of filters that can be applied. If you already have a saved filter applied, it will be highlighted in this menu.

3. To stop using the filter, either clear it, or select ‘No Filter’ from the ‘Filter Drop-Down’.

   Info

   The ‘Filter Drop-Down’ menu also contains a section for filters that were defined using a collection set. These can be accessed from the ‘Collection’ tab of the menu. More information on saving collection sets as filters can be found here.

Deleting a Saved Filter Definition

1. At any time, the user who created a custom filter, can delete that custom filter definition. This includes shared filters.

2. To delete a saved filter, click on the ‘Settings’ cog in the ‘Filter Drop-Down’ menu.

3. A dialog detailing each saved filter available to the user will then be displayed. Next to each of the filters in the table, is a button to ‘Delete’ the filter from the system. Click this button to delete the filter.

   Info

   If the ‘Delete’ button is not visible, or deactivated, it means that you do not own the filter.

Filter Actions

1. The ‘Filter’ panel also contains short-cuts to a few reports that can be generated using the current filter definition as a filter.

2. To use these action short-cuts, simply click on the ‘Filter actions’ menu at the top of the filter panel.

3. From the menu, choose which report you would like to generate.

   Info

   The filter does NOT have to be saved in order to generate a report in this fashion.

Using Map Themes (Visualisations)

This document provides an overview on how to use the built-in custom map themes in the Metrix Asset Management system.

1. To get started, navigate to the main ‘Assets’ map in the Metrix Asset Management system.

2. On the left hand side of the page, make sure the ‘Visualise By’ tab is activated. .

3. Initially, you will see a map legend for the currently applied map theme. By default, this is set to colour switch on ‘Asset Class’. To change the map theme to a different pre-configured visualisation, simply click ‘Switch Map Theme’ at the top of the panel.

4. This will now display all of the available built-in map themes in a range of contextual categories. .

5. To apply a specific visualisation, simply click on the tile in this view.

6. The theme will apply, and you will be returned to the ‘Legend View’ as it pertains to your chosen theme.

7. Repeat this process to go to another theme.

   Info

   Remember, the default map theme is called ‘Asset Class’. Choosing this theme will essentially reset your visualisations to system standard.

Component Change History

This document provides an overview on how to use the Component Change History Viewing tool in the Metrix Asset Management system.

1. To get started, navigate to the main ‘Assets’ map in the Metrix Asset Management system and select an asset record to bring up it’s Info Panel.

2. Ensure you have either the ‘Info’ or ‘Intervention’ panel tab open, and look for the ‘History’ icon along the right-hand side edge of the panel. A ‘History’ icon is available at the top of each ‘section’ of Info Panel content. .

3. A slide-out drawer will appear, initially with the Component’s current information listed. Only sections where history is tracked, are shown.

4. At the bottom of the slide-out drawer, you will see some navigation buttons. These allow you to move backwards and forwards through the change history of the active component. Additionally, around these navigation buttons, you will see the date and time of the change, as well as the name of user who made the change. .

5. Any differences that exist between the record version you are CURRENTLY VIEWING and the LIVE VERSION of the component record will be highlighted in red. In the example below, the current (live) value of the component’s length is 966.8467, whereas the historic value of this field value is 1150.6717. .

6. Additional indicators exist on each tab to guide users towards areas where changes exist on the current component version. These indicators are shown as a red dot next to the tab label. In the example below, the ‘Info’ and the ‘Intervention’ tabs contain changes, whereas the ‘Spatial’ tab does not. .

Building Collection Sets

This document provides an overview on how to use the collection set concept in the Metrix Asset Management system, including:

Defining a Collection Set

1. To get started, navigate to the main ‘Assets’ map in the Metrix Asset Management system.

2. On the left hand side of the page, make sure the ‘Collection’ tab is activated.

3. To start building your collection set, click the ‘Add with select tool’ option at the top of the panel. This will place you in ‘Selection’ mode where any clicked assets in the map view will add those asset components to your collection set.

   Info

   The selection tool will add ALL components from a clicked asset. It does, however, respect any applied custom filters that may be excluding some component types. That is, if you filter out road base and road earthworks (leaving just surface), and click on a road segment, only the surface will be added to your collection. Without a filter, all three (3) component groups will be added.

4. Once you have added some asset components to your collection, the ‘Remove with select tool’ option will activate as an optional mode. Using this mode will mean that every asset clicked on will REMOVE its components from your collection set (if they were a part of it).

5. Also, you have the option of simply adding ALL components from your current custom filter definition to your collection set. That is, if you have a filter that results in 15 components, then those 15 components would be added to your collection set.

6. Once you have finished defining your collection set, click the ‘End selection’ option which will be hovering at the top of the map window.

Collection Set Actions

1. Once you have a defined collection set, you can then perform actions on it including bulk data updates and generating reports.

2. To generate a report from the current collection set, simply click ‘Generate Report’ from the ‘Collection Panel’ and choose the report you would like to create. The results of the report will be filtered down to your current collection set.

   Info

   Other available collection actions are subject to their own instructions.

Saving Collection Set as Filter

1. Once you have finished building the collection, simply click on the ‘Save as filter’ option in the ‘Collection Panel’.

2. A fly-out menu will appear prompting you for a name for the new filter. Input a name for the filter (this is how you will find it later).

3. To opt to allow other system users to see the filter you have defined, toggle the ‘Shared’ control. By default, filters are private and NOT shared.

4. When you are done, click ‘Save’. The filter is now saved under that name. If you shared the filter, other users will see it in the ‘Filter Drop-Down’ at the top of the panel.

   Info

   Filters created from Collections will be listed under the ‘Collection’ tab of the ‘Filter Drop-Down’ list.

Staged Changes

Making edits to your asset information in the Metrix Asset Management system is a two-phased process. First, you make the alterations. Then, you save those changes (or discard them). Prior to this second step, the changes are considered to be STAGED, and awaiting final SAVE.

Users can make many edits in a single sessions before opting to save or discard the staged changes.

After your first alteration, you will notice that the ‘Save or Discard Edits’ button in the top-right hand corner of the page is now activated. Additionally, there is an orange marker line surrounding the info panel for the asset/component that the changes occurred on.

Prior to saving changes, users are provided the chance to review their work via a summary of the changes panel.

Basic Data Edits

With appropriate user rights, editing your asset information in the Metrix Asset Management system has been tailored to be super simple, and safe. To get started with editing your asset information, follow these steps:

1. Navigate to the main ‘Assets’ page and make a selection from the map screen.

2. Your asset and component data is displayed inside the info panel on the right-hand side of the page. This is where you will also edit the data.

3. To edit a field, simply click the information content - if the field is editable, and you have the appropriate privileges, the content will transform into an editable control. Depending on the field, users will be presented with one of the following controls:

   Instructions on how to use each of the above controls are discussed below.

Text Input Box

1. For alpha-numeric free text fields, the control that renders when you set it to edit mode will be a standard input box.

2. To edit content in an input box, simply locate your cursor and begin typing.

3. Once you have finished making your edits, click anywhere outside of the box to release the control.

4. The edits you made are now STAGED and ready to save.

Number Input Box

1. For numeric data fields, the control that renders when you set it to edit mode will be a standard number input/picker box.

2. To edit content in an input box, simply locate your cursor and begin typing.

3. Another option you have is to click the increase/decrease toggles on the right-hand side of the input box.

4. Once you have finished making your edits, click anywhere outside of the box to release the control.

5. The edits you made are now STAGED and ready to save.

Option Row

1. For list based data fields that have fewer than 5 options, the control that renders when you set it to edit mode will be an option row.

2. To alter or set the active choice in the option row, simply click that option.

3. The edits you made are now STAGED and ready to save.

Drop Down List

1. For list based data fields that have more than 5 options, the control that renders when you set it to edit mode will be an drop-down list.

2. To alter or set the active choice in the option row, simply choose that option from the list.

3. The drop down list control also supports filtering of the visible list items. To do this, simply type your filtering letters into the search box at the top of the list.

4. The edits you made are now STAGED and ready to save.

Calendar Picker

1. For date based data fields, the control that renders when you set it to edit mode will be a dynamic calendar control.

2. To edit content in a calendar control, simply choose the date value from the displayed calendar widget.

3. The calendar is month based. Users can change the visible month and year using the drop down options at the top of the control.

4. Some calendar controls are also pre-configured with ‘quick-dates’ allowing you to set the value to date such as ‘1 week ago’.

5. The edits you made are now STAGED and ready to save.

Save or Discard Changes

Making edits to your asset information in the Metrix Asset Management system is a two-phased process. First, you make the alterations. Then, you save those changes (or discard them). The following outlines how you can do this.

This document provides guidance on saving changes, as well as some other options around saving or discarding your changes, including.

For each of the following sections, we assume you have one or more pending changes to your asset information. If not, make some edits to your asset and/or component information.

After your first alteration, you will notice that the ‘Save or Discard Edits’ button in the top-right hand corner of the page is now activated. Additionally, there is an orange marker line surrounding the info panel for the asset/component that the changes occurred on.

Saving Changes

1. Start by reviewing your change(s), click on the ‘Save or Discard Edits’ button. A dialog will appear with a summary of the changes you have made to your asset and/or component data. Alterations are broken down by type, and summarised into affected record counts.

2. To commit the changes, provide a short comment about the alteration, and then click ‘Commit Changes’.

3. The data will then be permanently saved to your Metrix Asset Management system.

Saving Changes at a Specific Date

The Metrix Asset Management system maintains a full audit history of changes users make in the system. This audit history is available through the ‘Report’ generators - allowing a user to backdate certain reports, to get asset/component information as it was at a specific point in time.

To extend upon this capacity, the system also supports backdating the ‘Effective Date’ of an alteration so that it can be visible in specific reporting ranges.

1. Start by reviewing your change(s) - click on the ‘Save or Discard Edits’ button. A dialog will appear with a summary of the changes you have made to your asset and/or component data. Alterations are broken down by type, and summarised into affected record counts.

2. To set a specific ‘Effective Date’ for the alterations summarised, expand the panel below the current date (which is rendered at the top of this dialog).

3. The expanded panel provides options to override the ‘Effective Date’ with shortcut values, or a custom date entry. Make your selection for ‘when’ the change(s) should be applied.

4. The data will then be permanently saved to your Metrix Asset Management system, effective from the date you specify.

Discarding ALL Changes

1. Start by reviewing your change(s), click on the ‘Save or Discard Edits’ button. A dialog will appear with a summary of the changes you have made to your asset and/or component data. Alterations are broken down by type, and summarised into affected record counts.

2. On the bottom left-hand side of the dialog portal, a collapse panel is rendered offering you the option to ‘Undo all Changes’. Click on this panel.

3. The panel will expand, revealing an option to ‘Rollback Changes’. To continue with undoing any alterations you have made since your last save, click this button.

4. Any alterations you have made will be reverted, and your session restored.

Discarding Specific Component Alterations

1. At any time during an editing session, users can review what information has changed on a specific asset or component from right within the info panel. In the top right-hand corner of the info panel is an ‘Edits Indicator’ that appears when the active asset/component has pending edits against it.

2. Click on this indicator to see a brief summary of the changes.

3. To rollback all changes recorded against the active component, click on the ‘Rollback’ button inside this preview.

   Note

   This option only relates to COMPONENT data edits. It cannot be used to revert alterations made on the parent asset info panel.

Task Types

This guide provides an overview on how to create or edit task records in the Metrix Asset Management system. The areas covered include:

Viewing Task Records

1. Any task records that have been captured, will be displayed in the parent asset info panel (for records logged at an asset level), or the component info panel (for records logged against a specific component). To see the records, scroll to the bottom of the respective info panel, to the section titled ‘Task Data’.

2. The most recent entry will be displayed in a form layout. In the top right-hand corner of the form is an indicator (titled ‘More’) regarding how many records of that task type exist against the asset or component. Click this label to see more records.

3. The form view will expand at this point to a form view per task record, stacked and ordered by record date. Scroll this view to see the details of each entry.

Enter a New Task Record

1. To capture a new task data record, navigate to the relevant info panel. That is, to capture a record against the asset, go to the parent asset info panel. To capture a record against a specific asset component, go to that component info panel.

2. Scroll to the bottom of the info panel to where the task records are rendered.

   Info

   If no task types are assigned to the appropriate classification level, this section will simply state ‘No task types configured’.

   If more than one task type is assigned, they will each be listed in this section.

3. For the relevant task type definition, click on the ‘New’ button.

4. A fly-out panel will appear with the task form rendered in edit mode. Complete this form.

5. When you are finished, simply click ‘OK’ at the bottom of the form. To cancel, click the ‘X’ in the top right-hand corner of the form.

6. The new task record entry is now STAGED and ready to save.

Edit a Task Record

1. To edit an existing task data record, simply navigate to the record in the appropriate info panel. That is, for a record logged against an asset, go to the parent asset info panel. For a record logged against specific asset component, go to that component info panel.

2. Scroll to the bottom of the info panel to where the task records are rendered.

3. For the task type you are altering, click the ‘More’ option to expand the entries.

4. Each record entry rendered for the task definition will have an ‘Edit’ button at the top of it. Click this button.

5. A fly-out panel will appear with the task form rendered in edit mode. Update this form.

6. When you are finished, simply click ‘OK’ at the bottom of the form. To cancel, click the ‘X’ in the top right-hand corner of the form.

7. The modified task record entry is now STAGED and ready to save.

Delete a Task Record

1. To delete an existing task data record, simply navigate to the record in the appropriate info panel. That is, for a record logged against an asset, go to the parent asset info panel. For a record logged against specific asset component, go to that component info panel.

2. Scroll to the bottom of the info panel to where the task data records are rendered.

3. For the task type you are altering, click the ‘More’ option to expand the entries.

4. Each record entry rendered for the task type definition will have an ‘Actions’ button at the top of it. Click this button.

5. In the menu that flies out from this button, there will be a ‘Delete’ option. Click this option.

6. The task record entry is now STAGED for deletion. Simply save your changes for this to take effect.

Reshape/Replace Component Geometry

This section provides an overview on how to manage your spatial features within the Metrix Asset Management system. The context covered includes:

Reshaping an existing Component Spatial Feature

1. To alter the spatial feature of a component, select the asset and navigate to the appropriate component info panel.

2. Within the component info panel, is a section titled ‘Spatial’. To modify the current geometry without changing the geometry type (point, line, polygon), click ‘Reshape/Move’.

3. The info panel will hide itself and you will be immersed into the geometry editing view.

4. Make the desired edits to your geometry, according to its type of point or line/polygon.

5. When finished, click ‘End Editing’ on the panel at the top of the map window.

6. The updated geometry is now STAGED and ready to save.

Replacing an existing Component Spatial Feature

1. To replace the spatial feature of a component, select the asset and navigate to the appropriate component info panel.

2. Within the component info panel, is a section titled ‘Spatial’. To replace the current geometry by changing the geometry type (point, line, polygon), click the ‘Replace With’ menu.

3. From the menu list, choose the desired geometry type for the new spatial feature - point, line, or polygon.

4. The info panel will hide itself and you will be immersed into the geometry editing view.

5. Create the desired geometry type as either a point or line/polygon.

6. When finished, click ‘End Editing’ on the panel at the top of the map window.

7. The replaced geometry is now STAGED and ready to save.

For more information, see the helpful tutorial video below.

Confirming Shared Spatial Features

1. To confirm whether or not an active component spatial feature is shared with other components on the asset record, navigate to the parent asset info panel.

2. Within the parent asset info panel is a section titled ‘Component Spatial Breakdown’. This displays a table view specifying each asset component alongside the geometry number* that the component is using.

   

   In the above screenshot, the asset has four (4) components, and three (3) unique spatial features. The first and last component (in the table view) are using ‘Shape 1’* and the middle two components reference their own shape. We therefore know that ‘Shape 1’ is shared across those two components.

   * this number is dynamically generated and simply serves to inform whether a shape feature is used on more than one component.

Modifying Point Features

Point features support relocation.

Moving Points To move a point, simply:

1. Click once on its current location (it will change color to bright green).
2. Click-and-drag the feature from where it currently is, to where you wish it to be located.
3. Release to finish relocating.

When finished, click ‘End Editing’.

Modifying Lines & Polygons

Line/Polygon features support both relocation and reshaping.

Moving Lines/Polygons To move a line or polygon, simply:

1. Click once on any of the line/perimeter segments.
2. Click-and-drag (from that segment). The entire shape will begin to follow your cursor across the map.
3. Release to finish relocating.

Reshaping Lines/Polygons

To reshape a line or polygon, simply:

1. Click once on any of the line/perimeter vertex nodes (it will change color to bright green).
2. Click-and-drag (from that vertex node) from where it currently is, to where you wish it to be located.
3. Release to finish relocating the node.
4. Repeat the above for other vertex nodes that need moving.
5. To ADD a new vertex node, click once on one of the segment center marker (white dot).
6. A new vertex node will be created, click-and-drag it to the desired location.
7. Release to finish relocating.

Creating Point Features

To create a new point feature:

1. Simply click on the map window where you want the point to be located.
2. To alter this location after initial placement, follow the instructions to relocate a point

Creating Line & Polygons

To create a new line or polygon feature:

1. Click on the map window where you want the first vertex node to be located.
2. Then, continue to click map locations for each subsequent vertex node location.
3. Double-click to finish drawing new vertex nodes.
4. To alter the location of a vertex node after initial placement, follow the instructions to relocate a line/polygon

Assign/Unassign Report Categories (Tags)

This document provides an overview on how to assign and unassign specific report category tags from asset components in the Metrix Asset Management system. Please note that in order to use a report category, it must be first defined in the system configuration.

Assign Report Categories

To assign a report category (tag) against a component:

1. Navigate to the component info panel for the asset component.

2. Within the first ‘Identification’ section of the panel is a sub-section called ‘Report Categories’.

3. To add a new report category tag, click on the ‘+’ drop down list. The remaining available (not currently assigned to the active component) report categories will render inside this menu.

   Info

   If the ‘+’ button is disabled, it means there are no available report categories, or, all report categories have already been assigned to the active component.

4. For each report category, the menu will render a sub-menu so that you can choose the tag to apply. Choose the desired combination you wish to apply.

5. The category assignment is now STAGED and ready to save.

Unassign Report Categories

To unassign a report category (tag) from a component:

1. Navigate to the component info panel for the asset component.

2. Within the first ‘Identification’ section of the panel is a sub-section called ‘Report Categories’.

3. Current assignments will display in this section. On the right-hand side of each rendered category tag, there is a ‘-’ (remove) icon. To unassign the category tag, simply click this icon.

4. The category un-assignment is now STAGED and ready to save.

Update Condition

This document provides an overview on how to set or update the condition score of an asset component in the Metrix Asset Management system. Please note that in order to use CUSTOM condition assessments, one must be first defined and assigned to the relevant component group in the system configuration. Otherwise, the default condition assessment form will be used.

To set/update the condition for a component:

1. Navigate to the desired asset component and select the intervention info panel.

2. At the top of the intervention info panel, the current condition is summarised. If this part of the info panel is not currently expanded, click on ‘Show More’ to expand it.

3. Click on ‘Update Condition’

4. A fly-out panel will then appear with the condition form rendered in edit mode. Fill out this form.

5. When finished, click ‘Update Condition’ at the bottom of the form.

6. The new condition entry is now STAGED and ready to save.

Update Treatment

This document provides an overview on how to set, update, or remove an intervention treatment of an asset component in the Metrix Asset Management system. Please note that in order to use an intervention treatment definition, it must be first defined and assigned to the relevant component group in the system configuration.

To set/update the intervention treatment for a component:

1. Navigate to the desired asset component and select the intervention info panel.

2. Within the intervention info panel, the current treatment details are summarised. If this part of the info panel is not currently expanded, click on ‘Show More’ to expand it.

3. Click on ‘Update Treatment’

4. A fly-out panel will then appear with a list of assigned intervention treatments as well as other intervention related settings.

5. For your first step, choose the appropriate treatment from the list of treatments by clicking on it. Alternatively, to completely clear the component’s treatment definition, select ‘Unassign Treatment from Component’ at the bottom of the table.

6. At the bottom of the panel, a brief summary of the change is rendered. Additionally, there is a checkbox asking if you wish to change any associated details along with the treatment. To update the:

   • Last Intervention Date,
   • Useful Life, and
   • Residual Life, toggle the checkbox. Doing so will set the intervention date to today, the useful life to the treatment definition’s default useful life, and the residual life to be equal with useful life.

7. For the above associated lifecycle metrics, users are able to overwrite the default values generated by the system. Simply input any adjustments to the Last Intervention Date, Useful Life, and/or Residual Life as deemed fit.

   Info

   Be aware that the useful life cannot be exceeded by the residual life. Also, when setting a value for the residual life, please be aware that the default effective date for the residual life offset is today. See Residual Life Calculations

8. When finished, click ‘Apply Condition’ at the bottom of the form.

9. The new treatment and any associated changes are now STAGED and ready to save.

Update Next Treatment

This document provides an overview on how to set or update the next treatment specifications of an asset component in the Metrix Asset Management system. Please note that in order to use particular treatment definitions, they must first be defined and assigned to the relevant component group in the system configuration.

To set/update the next treatment specification for a component:

1. Navigate to the desired asset component and select the intervention info panel.

2. Within the intervention info panel, the current definition for the next treatment is summarised. If this part of the info panel is not currently expanded, click on ‘Show More’ to expand it.

3. Click on ‘Update Next Treatment’

4. A fly-out panel will then appear with the options for setting the next treatment specification.

5. The first part of the panel requires users to choose the manner in which the component next treatment is being specified. This is either:

   • Estimated Cost: If choosing this method, enter the estimated cost of the next treatment into the input box below the radio button.
   • Treatment with Override Unit of Measure: if choosing this method, pick a treatment from the drop-down list, and also set an override value for the component cost units.
   • Treatment with Percentage of Component: if choosing this method, pick a treatment from the drop-down list, and also set an override percentage share for the component cost units.

   Set one of these options.

6. Next, set the estimated date for the next intervention treatment. This is an optional field.

7. Lastly, enter a description and reason for the next intervention treatment.

8. When finished, click ‘Apply Next Treatment’ at the bottom of the form.

9. The new treatment specification is now STAGED and ready to save.

Bulk Updates

This document provides an overview on how to perform bulk updates across many asset components in the Metrix Asset Management system. To use this feature, the components must be a part of an active collection set.

To perform bulk updates:

1. Navigate to the main ‘Assets’ map in the Metrix Asset Management system.

2. Build a collection containing the asset components you want to update.

3. When the collection is ready, click ‘Bulk Data Updates’ in the collection actions area. This will launch the ‘Bulk Data Update’ panel where assets and components within your collection are batched into their respective classification configuration.

Data Updates

4. To perform data updates, ensure you are using the ‘Data’ tab of the bulk panel and then locate the specific asset classification or component group on the left-hand side navigation tree.

5. On the right-hand side of the panel, a form will render showing you the possible data updates that you can make.

   Info

   At the top of this form, the number of assets or components (from your collection set) that are associated with the selected asset classification or component group will be rendered.

   Remember, any changes you make on this panel will be played out across all of those records.

Report Category Updates

6. To perform report category updates, switch to the ‘Assign/Unassign Report Categories’ tab of the bulk panel. Each report category defined in the system will be listed.

7. Click to expand the desired report category.

8. Each category has two options to choose from:

   • Bulk assign your collection set to a single report category option.
   • Bulk unassign your collection from one or more report category options. Choose options from the left or right-hand side controls based on your desired outcome.

9. When finished, click ‘Stage Changes’.

10. The updates are now STAGED and ready to save.

    Warning

    Bulk updating information is more prone to errors as the program cannot perform much of the validation until the save step of the process.

Component Finance Settings

This document provides an overview on how to set or update the financial settings for an asset component in the Metrix Asset Management system. These settings relate to how the component is going to be depreciated over it’s lifetime, including any residual value, and the rate at which it is consumed.

To set/update the finance settings for a component:

1. Navigate to the desired asset component and select the transactions info panel.

2. Within the transactions info panel is a section title ‘Financial Settings’. It is here that users can record such information.

Depreciable Value

3. To set or update the ‘Depreciable Value’, click on the current field value (it may be set to ‘Not Set’).

4. First, choose whether the ‘Depreciable Value’ is to be a fixed dollar value, or a percentage figure based on the component’s gross value. To completely remove the ‘Depreciable Value’ setting for the active component, choose ‘Not Set’ and skip the next step.

5. Set the numeric value that corresponds with the option you set in the previous step. For percentage figures, the value must be between 0 & 100.

Period Depreciation Value

6. To set or update the ‘Period Depreciation’ value, click on the current field value (it may be set to ‘Not Set’).

7. First, choose whether the ‘Period Depreciation’ value is to be a fixed dollar value, or a percentage figure based on the component’s gross value. To completely remove the ‘Period Depreciation’ value setting for the active component, choose ‘Not Set’ and skip the next step.

8. Set the numeric value that corresponds with the option you set in the previous step. For percentage figures, the value must be between 0 & 100.

9. The updated finance settings are now STAGED and ready to save.

Posting Component Transactions

This document provides an overview on how to create a new posting to the financial transactions ledger for an asset component in the Metrix Asset Management system. These transactions form the basis of a component’s capital valuation and an organisation’s end of period financial statements.

To post a new financial transactions ledger entry for an asset component:

1. Navigate to the desired asset component and select the transactions info panel.

2. Within the transactions info panel is a section title ‘Transaction History’. It is here that users can see past recorded movements, as well as post new ones.

3. To post a new financial transactions ledger entry, click ‘New Transaction’ at the top of the history summary table.

   Info

   If the summary table and/or the ‘New Transaction’ button is not displayed for your active component, it typically means that the asset component does not currently contain the prerequisite information for carrying capital value.

   This typically means that the underlying component is not Active.

   Users may also be presented with warnings about missing construction/intervention dates or useful life values - these are warnings that do not prevent transaction creation, but should be considered.

   A fly-out panel with a transaction generation form will appear.

   

4. Set the posting ‘Date’ for the new transaction. This is the date that the transactions value will be recognised by the system. The date cannot extend beyond the end of the current financial period (typically the end of the financial year).

5. Select the ‘Effect’ that the posting will have on the asset component. That is, will the posting affect the component’s gross value, or its accumulated depreciation value.

6. From the transaction ‘Type’ drop-down list, choose the desired transaction type for the new posting.

   Info

   Each transaction type in the list is tagged with the required polarity of the transaction ‘Value’ according to the chosen transaction type ‘Effect’. This will be either:

   • Positive: value must be greater than zero
   • Negative: value must be less than zero
   • Any: no restriction

7. Enter a transaction ‘Value’ with consideration for the polarity restriction for your chosen transaction type.

   Info

   For the ‘Depreciation’ transaction type, an ‘Estimated Annual Depreciation Amount’ figure will be displayed above the ‘Value’ input box for information purposes.

8. If the component does not currently carry any capital value, the ‘Finance Category’ will need to be defined next. Choose a valid finance category from the drop-down list. If your component already carries value, this drop-down will be disabled.

9. Lastly, enter a comment for the transaction.

10. When finished, click the button below the comment input box that contains a summary of the transaction.

11. The transaction has been generated and is now STAGED and ready to save.

Deleting Component Transactions

This document provides an overview on how to delete existing postings to the financial transactions ledger for an asset component in the Metrix Asset Management system.

To delete an existing financial transactions ledger entry for an asset component:

1. Navigate to the desired asset component and select the transactions info panel.

2. Within the transactions info panel is a section title ‘Transaction History’. It is here that users can see past recorded movements, and delete them.

3. In the transaction history table, each entry contains a ‘Delete’ option (rendered as a trash-can) on the far right-hand side of the row. To delete a transaction entry, click this button.

   Info

   When processing the deletion of one or more transactions, the system considers the following:

   • Following removal of the transactions, the component must not be left with a negative carrying value.
   • Transactions from previous financial periods cannot be removed.

   These restrictions do not apply to transactions that have not yet been saved/committed to the system.

4. Repeat the above step for each transaction that you may need to remove.

5. The transaction(s) have been STAGED for removal and are ready to save.

Editing Barcode Values

This document provides an overview on how to set or remove a barcode value of an asset or asset component in the Metrix Asset Management system. Please note that in order to modify barcode values, the user must have the appropriate permissions set.

To set the barcode value for an asset or component:

1. Navigate to the desired asset or component and select the basic info panel.

2. Within the info panel ‘Identification’ section, details pertaining to any current barcode value assignment is shown. If no value has been assigned, this will be empty.

   Hovering over the barcode value will render a preview of the barcode

3. To assign a barcode value (where one has not previously been assigned), click ‘Add Barcode Link’.

   Note: If the asset or component has a previously assigned barcode value, this will need to be removed/unlinked first.

4. A panel will slide out asking for the value of the barcode to link to the active asset or component. Enter the value within this text entry.

5. The panel will validate the supplied barcode value. If the value is NOT valid, the ‘Save (Immediatley)’ button will be disabled - follow the prompts to ‘repair’ the entered value.

6. To save the new barcode value, click ‘Save (Immediately)’. Note; this change (as inferred) does NOT go via the staged changes process. Rather, the link will occur immediatley.

To remove the barcode value for an asset or component:

1. Navigate to the desired asset or component and select the basic info panel.

2. Within the info panel ‘Identification’ section, details pertaining to any current barcode value assignment is shown.

3. To remove the currently assigned barcode link for an asset or component, simply click the ‘Trash’ icon next to the barcode value.

4. A dialog will appear asking for confirmation. Confirm the deltion.

The Bare Minimum

The Metrix Asset Management system supports a wide scope of asset related data. When it comes to creating new records within your system, more information is always encouraged. As a minimum however, the following record types are required:

• Each asset must contain at least one (1) asset component record.

Additionally, the following resources or fields are MANDATORY:

• A valid asset classification and component group definition,
• A short Asset description and Component description,
• A valid Component status
• A valid Spatial Feature Definition

Creating Assets

Creating a new asset record in the Metrix Asset Management system is a simple process that involves choosing an asset classification, defining a spatial feature, and then populating the asset and component data fields.

To create a new asset record:

1. Navigate to the main ‘Assets’ page.

2. Above the map window, is a button titled ‘Create Asset’. Click this button.

3. A fly-out ‘Create New Asset’ panel will show at the bottom of the map window. Firstly, it will render a list of available asset classes configured in your system.

   Info

   The asset class is the ‘first level’ of the asset classification structure.

   Choose an asset class for your new asset.

4. The panel will then render the the list of asset classifications relative to your chosen asset class. Choose an asset classification for your new asset.

5. On the right-hand side of the panel, you will then be presented with options for creating the asset components. Firstly, confirm which component group(s) you wish to include as components for your new asset.

   Info

   For each component group that remains checked, the system will generate one (1) component.

6. Next, choose the initial status from the status drop-down list. The default status is ‘Proposed’. Each of the components, defined in step 5, will be assigned this status.

7. Then set the effective date for the new asset components via the calendar input control. Each of the components created, defined in step 5, will be generated as at this date.

8. The last step involved in creating a new asset is to define the spatial feature that will be assigned to ALL of the asset components, defined in step 5. Click on either

   • New Point,
   • New Line, or
   • New Polygon and digitise the spatial feature as per these instructions for points ↗ or these instructions for lines/polygons ↗.
   Info

   To finish digitising lines and polygons, simply double-click the map.

9. When you have finished digitising the spatial feature, click ‘Finish & Create’ at the bottom of the panel. Assets will be created immediately upon clicking ‘Finish & Create’. They do NOT go via the staged changes process.

10. The asset, once created, will then be selected and ready for you to update the attributes, intervention details, and condition as necessary.

Appending Components to Assets

Creating a new component record against an existing asset in the Metrix Asset Management system is a simple process that involves selecting the parent asset, choosing the target component group, confirming or defining a spatial feature, and then populating your new component data fields.

To create a new component record against an existing asset:

1. Navigate to the main ‘Assets’ page and make a selection from the map screen.

2. On the left-hand side of the info panel (right side of the page) the ‘Components’ switcher lists each component group (from the asset classification configuration) available to the asset. At the bottom of this listing, there is a button labelled ‘Add New’ and titled ‘Component’. Click this button.

3. A fly-out ‘Create New Component’ panel will show at the bottom of the map window rendering your component creation options. Firstly, confirm which component group(s) you wish to generate and append to the parent asset.

   Info

   For each component group that remains checked, the system will generate one (1) component.

4. Next, choose the initial status from the status drop-down list. The default status is ‘Proposed’. Each of the components, defined in step 3, will be assigned this status.

5. Then set the effective date for the new components via the calendar input control. Each of the components created, defined in step 3, will be generated as at this date.

6. The last step involved in appending components for an asset is to define the spatial feature that will be assigned to the new components, defined in step 5. Click on either

   • New Point,
   • New Line,
   • New Polygon, or
   • Create with / Choose from Current Asset Geometry

   New Spatial Feature

   If defining a new spatial feature, digitise the geometry as per these instructions for points ↗ or these instructions for lines/polygons ↗.

   Info

   To finish digitising lines and polygons, simply double-click the map.

   When you have finished generating or confirmting the spatial feature, click ‘Finish & Create’ at the bottom of the panel. To finish, click ‘Finish & Create’.

   Using Existing Spatial Features

   If you choose to inhertit the spatial feature from an existing component on the parent asset, one of two workflows will occur:

   • If the components of the parent asset rely on a single spatial feature, the fourth button option will be labelled ‘Create with Current Asset Geometry’. Clicking this option will complete the process and your new components will be appended to the parent asset and share the one spatial feature.

   • If the components of the parent asset rely on multiple spatial features, the fourth button option will be labelled ‘Choose from Current Asset Geometries’. Clicking this option will present another panel requiring you to choose which spatial feature to inherit.

     As you hover on each option row (representing a distinct spatial feature), the corresponding feature will be highlighted in the map window.

     Click a spatial feature row to choose your geometry. Then click ‘Create Component’.

   Components will be created immediately - they do NOT go via the staged changes process.

7. The components, once created, will then be selected and ready for you to update the attributes, intervention details, and condition as necessary.

Splitting Assets

The ability to split an Asset is vitally important in keeping the Organisation’s financial reporting, engineering concepts, and asset management data policies in sync. The core concept involves splitting a linear geometry (representing one or more Components associated with an Asset) at any given coordinate, at an effective date.

The returned feature set represents the two (or more in certain cases) new Assets, each containing a distinct copy of the original Components, with each new Component being proportionately associated with one of the two (or more) resultant geometries. The original Asset and Components are deprecated (see section on deprecation).

The following concepts are covered in this article:

Note: This article is specifically addressing Asset Split operations where the goal is to generate two (or more) distinct new Assets with their own Components (mirroring the original). Users may also be interested in reading about splitting asset components whereby the parent Asset is maintained, but a sub-selection of Components are split and duplicated within said parent Asset.

How a Split Works

The basic mechanics of the Asset Split operation is that a user submits a request to the system for a split to occur. The system will respond (assuming no errors occur) with the required Asset, Component, and Resource inserts and updates that need to occur. Accepting this response will process the Split operation. This process is summarised below:

1. User submits request for a split operation
2. System assesses the request and responds with a detailed summary of the inserts and updates required to achieve the split
3. User accepts the response, and the split occurs.

Requesting a Split

To request a split, the following information is required:

• The Split Level (split_level) which must be set to ‘asset’ for an Asset Split.
• The Asset Record ID (asset_uid) of the Asset being split
• The Splitting Blade definition (intersection_wkt) defined in Well Known Text.
• An optional Posting Date (posting_date) for when transactions associated with the split operation should occur. This field will default to the current date/time if empty.
• An optional Effective Date (effective_date) for when the split should occur. This field will default to the current date/time if empty.
• Optional Split Flags (flags) that can control facets of what will be copied across to the new Assets and Components. See ‘Advanced Splitting: Resource Exclusions’ for more information.

System Assesses the Request and Response

Upon receiving a split request, the system will review the prohibitions detailed in the section, ‘When a Split can Occur’. It will then commence building a response that (if accepted by the user) instructs the system on how to:

• Deprecate the Old (split) Asset and Components
• Create the new Asset and Components
• Append the appropriate valuations and resources to the new Assets and Components.

User Accepts the Response and the Split Occurs

After reviewing the response - where the user can investigate in detail what will and wont be created - the user can accept the response and the relative Split Operation will occur.

How the Split Works at a Geometry Level

In order to perform the split, the user must provide a splitting blade - a linear geometry that cuts across the Component geometry/geometries at the desired split coordinate. See screenshot below:

In the above screenshot, the Asset (Twynam Avenue) is highlighted in yellow and the user provided splitting blade is located about 25% along it’s overall length. For the purpose of this example, we will assume that Twynam Avenue has three (3) Components - earthworks, base, and seal - all sharing the same linear geometry running from Governors Parade to Barr Street.

Prior to the split, the Twynam Avenue Asset Components could be represented by the following (basic) attribute data set:

With the ID of the Asset and the definition of the splitting blade supplied, the system first derives the NEW Component Geometries that would result from the split operation. See screenshot below:

In the above screenshot, the split has occurred and the first of the resultant two geometries is highlighted in yellow. The remaining portion of Twynam Avenue is associated with the second of the resultant two geometries.

Following the split, Twynam Avenue is now two (2) distinct Assets whose Components could be represented by the following attribute data set:

Asset 1 (highlighted in yellow)

NOTE: the proportion of length between ‘Asset 1’ and the original Asset is assumed to be 25% - the System has returned the new Cost Unit values based on this geometric truth.

Asset 2 (not highlighted)

NOTE: the returned data for ‘Asset 2’ represents 75% of the original Cost Unit values. All Components have been duplicated to the second Asset and can be managed in isolation of Asset 1 from now on.

When a Split can Occur

The following restrictions are enforced by the system when a user attempts to perform an Asset Split operation:

• The splitting blade MUST pass through the subject Geometry/Geometries at some point.
• The construction/Intervention dates of the Components cannot be after the effective date.
• The status effect of the Components must be active.
• The Component must have no Transaction postings that occur after the posting date.
• The posting date must not conflict with a Locked Financial Year.
• Only linear Geometries can be split.

Resources Assigned to the New Assets

Following an Asset Split, the following resources are copied across to the new Assets. They are discussed in detail below.

• Original Attribution
• Transaction Summary
• Condition History
• Report Categories
• Task Records

Original Attribution

Each new Asset or Component record that is created will inherit it’s attribution from the original Asset or relevant Component. Attributes are copied to the new Assets and Components unchanged - The ONLY EXCEPTION to this is the cost units value, which is modified by the Component’s relative proportionality.

Transaction Summary

Each new Component record that is created will inherit a proportionate baseline value from the original relevant Component and the original Component’s Value is written-off. This means there is ZERO change in overall value in the system. Consider the following 50/50 split of a single Component into two (2) new Components.

The original transaction schedule would look something like this, with the carrying value displayed at the bottom.

As a part of the Asset Split operation, the following transaction schedule would be generated and applied. Note: transaction schedule simplified to years for the example.

By the end of the process, the valuation summary for ALL Components would be:

Condition History

For each newly created Component, the relevant Condition History is copied to across in a split operation. The term ‘relevant’ refers to whether or not the Condition record concerned the spatial bounds associated with the new Component (see section: Advanced Splitting: Multiple Geometry Features), as well as whether or not the Condition record existed at the ‘Effective Date’ for the split operation.

The following table details this concept of ‘relevant’ Condition history for an Effective Date of 12/10/2000. Note, each row represents a Condition record that lasts from the Assessment Date until the Assessment Date of the subsequent row. That is, the above Component was considered to be in Condition 1 from January 1993 to February 1997.

Note: this condition record is carried over, however the Assessment Date is set to the Effective Date (October 2000) and a comment is added to reflect the original Assessment Date.

Report Categories

For each newly created Component, the LATEST (as at the Effective Date) relevant Report Categories are copied across in a split operation. That is, if a Component held a Special Schedule 7 Category of ‘Roads’ at the Effective Date, each new Component would inherit this Report Category.

Task Records

For each newly created Component, the relevant Task Records are copied across in a split operation. This occurs at both the Asset and Component Register level. Please note, the same rules of ‘relevancy’ that apply to the Condition History, apply to Task Records.

What happens to the Original Asset and Components

Following an Asset Split operation, the original Asset and ALL of it’s Components are marked with a status code of ‘Deprecated’. This is a special system status code (that users cannot access) which marks the record as ‘superseded by another record or records’. Deprecated records remain in the system, but they are excluded from the default map view, tables, filters, dashboards, and reports.

Information associated with a Deprecated Asset record can be fetched via the NEW Asset record(s). Each new record maintains a ‘Deprecated Parent’ linkage back to the original Asset.

Note: In the case of an Asset Split operation, only the Asset records receive a Deprecated Parent link back to the original Asset. The Component’s do not receive such a linkage in this case as the operation was at the Asset level.

Advanced Splitting: Multiple Geometry Features

In certain situations, an Asset’s Components may not all be represented by the same Geometry record. See the cross-section view below:

In the above example, the Asset (Twynam Avenue) is associated with five (5) Components. An earthworks Components, represented by a single Geometry running from Governors Place to Barr Street. Two (2) base Components running from Governors Place to Matthews Street and then from Matthews Street to Barr Street. And Two (2) seal Components running from Governors Place to Matthews Street and then from Matthews Street to Barr Street (identical to the base).

Given the above scenario, if Poate Street was to be extended such that it now crosses Twynam Avenue, the Asset Management and Engineering principles may require Twynam Avenue to be now represented as two (2) Assets, split by it’s intersection with Poate Street. In this case, the splitting blade would look like the following:

In the above, the Twynam Avenue Asset is to be split by its new full intersection with Poate Street. For the purpose of the example, we will assume the split blade is 75% along the original Asset’s length.

The resultant Assets and Components of such a split are shown below. The original Seal 1 and Base 1 features are not altered by proportionality, they are simply copied and associated with the new, shorter, Twynam Avenue Asset. The Seal 2, Base 2, and Earthworks Components however, are split between the two new Twynam Avenue Assets.

In the above, the Twynam Avenue Asset is to be split by its new full intersection with Poate Street. For the purpose of the example, we will assume the split blade is 75% along the original Asset’s length.

The association and proportion share of the new Assets and Components can be represented in the following table. As can be seen, Base 1 and Seal 1 features are copied and wholly associated with the first Asset (Governors Pde to Matthews Street). However, the Earthworks, Base 2, and Seal 2 are copied and distributed across the splitting blade.

Splitting Asset Components

The ability to split a Component is vitally important in keeping the Organisation’s financial reporting, engineering concepts, and asset management data policies in sync. The core concept involves splitting a linear geometry ( representing one or more Components) at any given coordinate, at an effective date.

The returned feature set represents the two or more new Components, each containing a distinct copy of the original Components, with each new Component being proportionately associated with one of the two (or more) resultant geometries. The original Components are deprecated (see section on deprecation) and the new Components are inherited by the original Asset.

The following concepts are covered in this article:

Note: This article is specifically addressing Component Split operations where the goal is to maintain the single Asset parent. Users may also be interested in reading about asset splitting whereby the parent Asset is also deprecated and the result is two (or more in certain cases) new Assets with all new associated Components.

How a Split Works

The basic mechanics of the Component Split operation is that a user submits a request to the system for a split to occur. The system will respond (assuming no errors occur) with the required Component/Resource inserts and updates that need to occur. Accepting this response will process the Split operation. This process is summarised below:

1. User submits request for a split operation
2. System assesses the request and responds with a detailed summary of the inserts and updates required to achieve the split
3. User accepts the response, and the split occurs.

Requesting a Split

To request a split, the following information is required:

• The Split Level (split_level) which must be set to ‘component’ for a Component Split.
• The Asset Record ID (asset_uid) of the Asset that ‘owns’ the Component(s) being split.
• The Component Record IDs (component_uids) of the Component(s) that are being split.
• The Splitting Blade definition (intersection_wkt) defined in Well Known Text.
• An optional Effective Date (effective_date) for when the split should occur. This field will default to the current date/time if empty.
• Optional Split Flags (flags) that can control facets of what will be copied across to the new Components. See ' Advanced Splitting: Resource Exclusions’ for more information.

System Assesses the Request and Response

Upon receiving a split request, the system will review the prohibitions detailed in the section, ‘When a Split can Occur’. It will then commence building a response that (if accepted by the user) instructs the system on how to:

• Deprecate the Old (split) Components
• Create the new Components against the original Asset
• Append the appropriate valuations and resources to the new Components.

User Accepts the Response and the Split Occurs

After reviewing the response - where the user can investigate in detail what will and wont be created - the user can accept the response and the relative Split Operation will occur.

How the Split Works at a Geometry Level

In order to perform the split, the user must provide a splitting blade - a linear geometry that cuts across the Component geometry/geometries at the desired split coordinate. See screenshot below:

*In the above screenshot, the Asset (Twynam Avenue) is highlighted in yellow and the user provided splitting blade is
located about 25% along it’s overall length. For the purpose of this example, we will assume that Twynam Avenue has
three (3) Components - earthworks, base, and seal - all sharing the same linear geometry running from Governors Parade
to Barr Street.*

Prior to the split, the Twynam Avenue Components could be represented by the following (basic) attribute data set:

Assuming the user only wants to split the Base and Surface Components (leaving the Earthworks untouched), they would supply the Asset Record ID, and the two (2) Component ID’s relating to the Surface and Base. The system then derives the NEW Component Geometries that would result from the split operation. See screenshot below:

*In the above screenshot, the split has occurred and the first of the resultant two geometries is highlighted in
yellow - a portion of the base and seal will be associated with this geometry. The remaining portion of base and seal
Components are associated with the second of the resultant two geometries. The earthworks are still associated with the
original geometry record.*

Following the split, Twynam Avenue is still one distinct Asset, however, instead of having three (3) Components, it now has five (5). The new Component Structure (ignoring deprecated Components) would look like this:

NOTE: the proportion of length between the smaller geometry and the original Asset is assumed to be 25% - the System has returned the new Cost Unit values based on this geometric truth.

When a Split can Occur

The following restrictions are enforced by the system when a user attempts to perform an Asset Split operation:

• The splitting blade MUST pass through the subject Geometry/Geometries at some point.
• The construction/Intervention dates of the Components cannot be after the effective date.
• The status effect of the Components must be active.
• The Component must have no Transaction postings that occur after the effective date.
• The effective date must not conflict with a Locked Financial Year.
• Only linear Geometries can be split.

Resources Assigned to the New Components

Following a Component Split, the following resources are copied across to the new Components. They are discussed in detail below.

• Original Attribution
• Transaction Summary
• Condition History
• Report Categories
• Task Records

Original Attribution

Each new Component record that is created will inherit it’s attribution from the original relevant Component. Attributes are copied to the new Components unchanged - The ONLY EXCEPTION to this is the cost units value, which is modified by the Component’s relative proportionality.

Transaction Summary

Each new Component record that is created will inherit a proportionate baseline value from the original relevant Component and the original Component’s Value is written-off. This means there is ZERO change in overall value in the system. Consider the following 50/50 split of a single Component into two (2) new Components.

The original transaction schedule would look something like this, with the carrying value displayed at the bottom.

As a part of the Component Split operation, the following transaction schedule would be generated and applied. Note: transaction schedule simplified to years for the example.

By the end of the process, the valuation summary for ALL Components would be:

Condition History

For each newly created Component, the relevant Condition History is copied to across in a split operation. The term ' relevant’ refers to whether or not the Condition record concerned the spatial bounds associated with the new Component ( see section: Advanced Splitting: Multiple Geometry Features), as well as whether or not the Condition record existed at the ‘Effective Date’ for the split operation.

The following table details this concept of ‘relevant’ Condition history for an Effective Date of 12/10/2000. Note, each row represents a Condition record that lasts from the Assessment Date until the Assessment Date of the subsequent row. That is, the above Component was considered to be in Condition 1 from January 1993 to February 1997.

Note: this condition record is carried over, however the Assessment Date is set to the Effective Date (October 2000) and a comment is added to reflect the original Assessment Date.

Report Categories

For each newly created Component, the LATEST (as at the Effective Date) relevant Report Categories are copied across in a split operation. That is, if a Component held a Special Schedule 7 Category of ‘Roads’ at the Effective Date, each new Component would inherit this Report Category.

Task Records

For each newly created Component, the relevant Auxiliary Data Records are copied across in a split operation. Please note, the same rules of ‘relevancy’ that apply to the Condition History, apply to Task Records.

What happens to the Original Components

Following a Component Split operation, the original Components are marked with a status code of ‘Deprecated’. This is a special system status code (that users cannot access) which marks the record as ‘superseded by another record or records’. Deprecated records remain in the system, but they are excluded from the default map view, tables, filters, dashboards, and reports.

Information associated with a Deprecated Component record can be fetched via the NEW Component record(s). Each new record maintains a ‘Deprecated Parent’ linkage back to the original Component.

Advanced Splitting: Resource Exclusions

When requesting a Component Split operation, a user can supply some optional flags that will alter what resources the newly created Components will receive. The flags currently available in the system are:

• Apportion Cost Units (apportion_cost_units - true/false): If not supplied, this defaults to TRUE. This flag indicates that the user wishes for the Cost Unit values of each new Component to be proportionately set based on its ' share’ of the original Component. If set to FALSE, each new Component will receive a Cost Units value equal to that of it’s parent Component.
• Copy Condition History (copy_condition_history - string): If not supplied, this defaults to all. This flag indicates what sort of Condition History the user would like to translate to the new Components. The following options are available:
  • all (default): All relevant Condition history will be copied.
  • latest: Only the most recent Condition record (relative to Effective Date) will be copied.
  • none: No Condition records will be copied.
• Copy Report Categories (copy_report_categories - true/false): If not supplied, this defaults to TRUE. This flag indicates that the user wishes for the relevant Report Categories to be copied to the new Components.
• Copy Task Records (copy_auxiliary_data - string): If not supplied, this defaults to all. This flag indicates what sort of Task Record History the user would like to translate to the new Components. The following options are available:
  • all (default): All relevant Records will be copied.
  • latest: Only the most recent Record (relative to Effective Date) will be copied.
  • none: No Records will be copied.

Advanced Splitting: Multiple Geometry Features

In certain situations, an Asset’s Components may not all be represented by the same Geometry record. See the cross-section view below:

*In the above example, the Asset (Twynam Avenue) is associated with five (5) Components. An earthworks Components,
represented by a single Geometry running from Governors Place to Barr Street. Two (2) base Components running from
Governors Place to Matthews Street and then from Matthews Street to Barr Street. And Two (2) seal Components running
from Governors Place to Matthews Street and then from Matthews Street to Barr Street (identical to the base).*

Given the above scenario, if Poate Street was to be extended such that it now crosses Twynam Avenue, the Asset Management and Engineering principles may require the Component’s of Twynam Street to reflect this new extent. In this case, the splitting blade would look like the following:

*In the above, the Twynam Avenue Components are to be split by its new full intersection with Poate Street. For the
purpose of the example, we will assume the split blade is 75% along the original Asset’s length.*

The resultant Components of such a split are shown below. The original Seal 1 and Base 1 features are not altered by proportionality, they are therefore UNMODIFIED by the split operation. The Seal 2, Base 2, and Earthworks Components however, are split by the intersection blade.

*In the above, the Twynam Avenue Components are to be split by its new full intersection with Poate Street. For the
purpose of the example, we will assume the split blade is 75% along the original Asset’s length.*

The association and proportion share of the new Components can be represented in the following table. As can be seen, Base 1 and Seal 1 features are left UNMODIFIED. However, the Earthworks, Base 2, and Seal 2 are copied and distributed across the splitting blade.

Deprecated Records

Following an action that results in assets or components being regenerated into a new entity, the original records will be marked as ‘deprecated’. This is a special system status code (that users cannot access) which marks the record as ‘superseded by another record or records’. Deprecated records remain in the system, but they are excluded from the default map view, tables, filters, dashboards, and reports.

Information associated with a Deprecated records can be fetched via the NEW (replacing) record(s). Each new record maintains a ‘Deprecated Parent’ linkage back to the original record. This can be accessed via the Actions menu at the top of the info panel.

Finance Re-Categorisation

A component’s finance category is defined by the first entry into the financial transactions ledger posted against that component. Following that, all transactions against that component will utilise that same finance category. To change a component’s finance category, the adjustment must be recorded through the financial transactions ledger as a movement off the original category, and then on to the new category.

Below is a summary of the involved movements posted during a financial re-categorisation from ‘Roads’ to ‘Footpaths’.

Note: In the above example, the gross value is $200, and the accumulated depreciation is -$150

In the above schedule, the process involves:

1. Writing off the accumulated depreciation value from the old category
2. Writing off the gross value from the old category
3. Writing on the gross value for the new category
4. Writing on the accumulated depreciation value for the new category

Importantly, the net change in carrying value for the component is zero.

Merging Assets

The ability to merge an Asset is vitally important in keeping the Organisation’s financial reporting, engineering concepts, and asset management data policies in sync. The core concept involves merging/combining two or more spatial features (representing one or more Assets), at an effective date.

The returned feature represents a new combined Asset, containing a distinct copy of the original Asset and Component’s data, with each being associated with parent Assets/Components. The original Assets and Components are deprecated (see section on deprecation).

The following concepts are covered in this article:

Note: This article is specifically addressing Asset Merge operations where the goal is to generate one new Asset with its own Component(s) from two or more Assets. At the date of publication of this guide, the ability to merge Components within an Asset is not supported by this tool.

How a Merge Works

The basic mechanics of the Asset Merge operation is that a user submits a request to the system for a merge to occur. The system will respond (assuming no errors occur) with the required Asset, Component, and Resource inserts and updates that need to occur. Accepting this response will process the Merge operation. This process is summarised below:

1. User submits request for a merge operation
2. System assesses the request and responds with a detailed summary of the inserts and updates required to achieve the merge
3. User resolves any merge conflicts identified by the system (such as conflicting attribute values)
4. User accepts the response, and the merge occurs.

For Components within each Asset, they will be merged in accordance with their Component Group classification. For example, when merging two road Assets, all child Surface Components will be merged together, all child base Components will be merged together, and all child earthwork Components will be merged together.

Requesting a Merge

To request a merge, the following information is required:

• The Asset Record IDs (asset_uid) of the Assets being merged
• A Posting Date (posting_date) for when any transactions associated with the merge operation should occur. This field will default to the current date/time if empty.

System Assesses the Request and Response

Upon receiving a merge request, the system will review the prohibitions detailed in the section, ‘When a Merge can Occur’. It will then commence building a response that (if accepted by the user) instructs the system on how to:

• Deprecate the Old (merged) Assets and Components
• Create the new Asset and Components
• Append the appropriate valuations and resources to the new Asset and Components.

During this process, the system analyses the Asset and Component attribution from all records being merged. Any conflicting values will be flagged to the user for resolution.

User Resolves any Merge Conflicts Identified by the System

The system will return a summary of merge request. This summary will include details regarding any conflicts that need to be resolved before continuing. Along with each conflict, the system will return some suggested values that might resolve the conflict. Where appropriate (for numeric values) the suggested values may include sums, averages, min and/or max values of the input Components for the Component Group in question.

Examples of conflicts, system suggestions, and possible ways to resolve them, include:

• Mismatch Cost Units: This is expected as each Component being merged will likely have a different value for Cost Units, reflecting their individual size/quantity. The system will return the sum of all Cost Units for that Component Group, as well as the average, the min, and the max value across the Component Group. Users may wish to elect the SUM value, reflecting the fact that the new Components size will be an aggregate of each input Components size.
• Mismatch Custom Text Attribute: This can occur from time to time and will typically not be accompanied by any ‘smart’ sugestions (sum, average, etc.). Users will be asked to choose one of the values from the input Components for the Component Group.

In all of the above examples, and during any merge operation, users do NOT have to settle for any of the suggested values (smart or otherwise). In all cases, a manual override is available for conflicting attributes.

User Accepts the Response and the Merge Occurs

After reviewing the response and resolving all merge conflicts - where the user can investigate in detail what will and wont be created - the user can accept the response and the relative Merge Operation will occur.

How the Merge Works at a Component by Component Level

In order to perform the merge, the user must provide two or more valid Asset Records.

Prior to the merge, the Twynam Avenue Asset Components could be represented by the following (basic) attribute data set:

Asset 1

Asset 2

NOTE: each Surface Component have differing values for ‘Treatment’. This will be a merge conflict that user must resolve in order to complete the merge. Additionally, each of the Cost Unit value conflicts (per Component Group) will need to be resolved.

The system, upon reviewing the merge request, will return a merge preview response highlighting any merge conflicts. For the above example (and for the information supplied), the following merge conflicts are likely:

For the above merge conflict, the resolution may be the following:

Following the merge, Twynam Avenue is now one (1) distinct Asset whose Components could be represented by the following attribute data set:

When a Merge can Occur

The following restrictions are enforced by the system when a user attempts to perform an Asset Merge operation:

• At least two (2) Assets must be submitted for merge.
• All Assets within the merge operation must share the same Asset Classification.
• The construction/Intervention dates of the Components cannot be after the posting date.
• The status effect of the Components must be active.
• The Component must have no Transaction postings that occur after the posting date.
• The posting date must not conflict with a Locked Financial Year.
• For each Component Group, the Finance Category for associated Capital Value must be the same.
• The Asset Components must not have any outstanding WIP transactions (from a Capital Budget process).
• The Assets or Components must not have any outstanding Programming Tasks.

Resources Assigned to the New Asset

Following an Asset Merge, the following resources are migrated to the new Asset. They are discussed in detail below.

• Original Attribution (with consideration for any merge conflict instruction)
• Transaction Summary
• Condition (with consideration for any merge conflict instruction)
• Report Categories (with consideration for any merge conflict instruction)

Original Attribution

The Asset/Component record that is created will inherit it’s attribution from the original Assets or relevant Components. Attributes are copied to the new Assets and Components unchanged (excepting any merge conflict instrucitons).

Transaction Summary

Each new Component record that is created will inherit a combined baseline value from the original relevant Components and the original Componens Value is written-off. This means there is ZERO change in overall value in the system. Consider the following merge of two (2) Components into one (1) new Component.

The original transaction schedule would look something like this, with the carrying value displayed at the bottom. For Component 1,

For Component 2,

As a part of the Asset Merge operation, the following transaction schedule would be generated and applied. Note: transaction schedule simplified to years for the example.

By the end of the process, the valuation summary for ALL Components would be:

Condition

For the newly created Component, the relevant Condition is copied across in a merge operation. On conflict, the user will be asked to choose which Condition value should be applied.

Report Categories

For the newly created Components, the LATEST (as at the Effective Date) relevant Report Categories are copied across in a merge operation. That is, if a Component held a Special Schedule 7 Category of ‘Roads’ at the Effective Date, each new Component would inherit this Report Category. This is, of course, subject to any merge conflict instructions.

What happens to the Original Assets and Components

Following an Asset Merge operation, the original Assets and ALL of their Components are marked with a status code of ‘Deprecated’. This is a special system status code (that users cannot access) which marks the record as ‘superseded by another record or records’. Deprecated records remain in the system, but they are excluded from the default map view, tables, filters, dashboards, and reports.

Information associated with a Deprecated Asset record can be fetched via the NEW Asset record(s). Each new record maintains a ‘Deprecated Parent’ linkage back to the original Asset.

Financial Re-Categorisation

To perform a financial re-categorisation, firstly, ensure that you understand the purpose and implications of such a process. Then, simply follow these steps.

1. Navigate to the main ‘Assets’ page and make a selection from the map screen.

   Ensure the correct asset component is your active selection.

2. Within the transactions info panel is a section title ‘Transaction History’. It is here that users can see past recorded movements, as well as perform financial re-categorisations.

3. At the top of the ‘Transaction History’ section, click on the ‘Reclassify’ button.

   Info

   If the summary table and/or the ‘Reclassify’ button is not displayed for your active component, it typically means that the asset component does not have any transactions posted against it. This therefore indicates that re-categorisation is NOT necessary.

4. A fly-out panel will display, requiring the target finance category and posting date for the change to occur.

5. Enter the posting date for the financial re-categorisation to occur using the calendar input.

6. Select the target finance category from the drop-down list.

7. Provide an optional comment.

8. Click ‘Reclassify’ when ready.

9. This operation does NOT proceed via staged changes, and occurs immediately. You have successfully re-categorised your component.

Splitting Assets or Components

The ability to split an Asset is vitally important in keeping the Organisation’s financial reporting, engineering concepts, and asset management data policies in sync. This section provides an overview on two different methods supported by the Metrix Asset Management system to perform spatial, linear bisections of your assets or asset components.

• Split Asset
• Split Asset Components
• Explode Multi-Geometry features

For a basic overview of how splitting works, please see the video below:

Reclassification

From time to time, an organisation’s asset infrastructure will undergo different purposes - or data management practices may adjust. In these cases, it can become necessary to reclassify assets and/or components to different asset classifications (or component groups). This section provides an overview on two different methods supported by the Metrix Asset Management system to perform reclassification of assets (including the asset components) or components.

• Reclassify Asset
• Reclassify Component within Asset Classification

For a basic overview of how reclassification works, please see the video below:

Set Component Status

This section provides an overview on how to alter a component’s status code in the Metrix Asset Management system:

1. Navigate to the main ‘Assets’ page and make a selection from the map screen.

   Info

   Make sure you have the correct component selected - the one you wish to update the status for

2. The component’s status is referenced toward the top of the ‘Info’ tab in the component information panel. To the right of this label, exists an option to ‘Update Status’ for the active component. Click this drop down list and choose the desired status from the options presented.

   Alternatively, setting the status in an option in the Info Panel ‘Actions’ menu. From the ‘Actions’ menu, choose ‘Set Component Status’ and then, from the sub-menu, choose the target component status that you wish to set.

   

3. A fly-out panel will appear seeking confirmation for the status change. If the target status effect is ‘inactive’, the system will also generate the required financial transactions ledger postings required to successfully set the status.

   These transactions are designed to ensure that ‘inactive’ components (i.e. disposed) do not carry any value or have any gross value. If you proceed, the transactions will be posted to your ledger.

4. Once satisfied with the proposed change, click the confirmation button at the bottom of the panel.

5. This operation does NOT proceed via staged changes, and occurs immediately. You have successfully updated the status on your component.

Deleting Assets & Components

From time to time, you may create a new asset or asset component and that eventuates to being a mistake. For these scenarios, the Metrix Asset Management system has support for users deleting assets or asset components.

Delete Assets

To delete an asset record and its asset components:

1. Navigate to the main ‘Assets’ page and make a selection from the map screen.

2. At the top of the info panel, click the ‘Actions’ menu.

3. From the ‘Actions’ menu options, hover or select ‘Parent Asset Actions’ and then choose ‘Delete Asset’.

4. The asset deletion has been STAGED and is ready to save.

Delete Component

To delete an asset component from a parent asset:

1. Navigate to the main ‘Assets’ page and make a selection from the map screen.

   Info

   Make sure you have the correct component selected - the one you wish to delete.

2. At the top of the info panel, click the ‘Actions’ menu.

3. From the ‘Actions’ menu options, choose ‘Delete Component’.

4. The component deletion has been STAGED and is ready to save.

Merging Assets

From time to time, your network of assets may become too bifurcated. For these scenarios, the Metrix Asset Management system has support for users merging assets.

Merge Assets

To merge two or more asset records:

1. Navigate to the main ‘Assets’ page and make a collection from the map screen. This will represent the assets you wish to merge together as one.

2. From the Collections side-bar options, choose ‘Perform Merge within Collection’.

3. Confirm the Asset Classification of the Assets that you wish to merge. This step is provided to prevent accidental merge of adjacent assets/components.

4. Confirm the selected records (within the Assset Classification) that will be merged. This is essentially a preview of what you have selected, once again to prevent accidental merge of adjacent assets/components. Click ‘Continue’.

5. Supply a Posting Date, if required. If the underlying Asset(s) have any capital value, you will be prompted for a Posting Date value. Enter a Posting Date if required. Then click ‘Generate Merge Preview’.

6. The system will analyse the request and return a preview of the merge operation, along with any merge conflicts discovered.

7. Navigate through the tabs of ‘Asset Data’, and ‘Component Group Data’. At the top of each tabbed section, a highlight will detail any merge conflicts within the tab that MUST be resolved. Review the data in each tab, resolve any merge conflicts, and generally review the data that will be created on the new merged record(s).

8. Once on the ‘Finalise and Review’ tab, you can click ‘Complete Merge’. This will commit the merge operation.