The Maintenance Manager features an enhanced workflow for tracking the life cycle of a simple transportation asset from installation date to0 retirement date. In addition to modeling how the asset condition will deteriorate over time, decision trees can now be used to set the ideal thresholds, in terms of age or condition, at which the agency can intervene, with key maintenance activities/treatments, to improve or maintain the asset's condition and extend its life. Optimization Analysis can also now be used for multi-year planning of the asset maintenance program, including the planning for replacement campaigns at the expected end of life for a group of assets.
The Standard Pavement Express module support for Lifecycle Analysis on various network types or asset classes (namely Pavement Segments and Parking Lots) most closely resembles the functionality. Still, MMS has a simplified version of this. It supports only Signs asset types for now, but adding support for other simple asset types should be straightforward.
To open the Optimization Analysis window, follow the steps below:
In this window, scenarios can be configured and executed, but a general configuration must be done first in order for it to operate. This is described in the next sections.
MS_OPT_TABLE_NAMES table lists important names of tables and columns used during network optimization and performance analysis.
Agile Standard has a record for module 3 (MMS), which contains the main tables and column names used in the optimization analysis. It should not require any changes for adding new asset types.
MMS_NETWORK_MASTER is a network master table in the MMS module. It contains the main asset attributes (id, name, installation year, expected life, condition (5-0), etc.) used in the optimization analysis.
To populate the MMS_NETWORK_MASTER table - run a System Job called "Update MMS Network Master" which accepts one required argument - Effective Year, and one optional argument, Asset Type. If Asset Type is not set - System Job will populate data for all assets that support optimization analysis in MMS. The Job uses Asset Lifecycle Parameters and Asset Inventory data to populate the Network Master table.
Asset LifeCycle parameters and data are stored in 3 tables.
This defines default Replacement Cost and Expected Life on the asset class code level
Column Name | Data Type | COMMENT |
|---|---|---|
| default_asset_attribute_id | bigint | PK |
| asset_type_id | bigint | FK to the setup_asset_type table. |
| class_code_id | bigint | FK to the ident_class_code table. |
| replacement_cost | integer | |
| expected_life | integer | |
| comment_str | varchar(4000) | |
| user_update | varchar(400) | |
| date_update | date |
Record for Signs in the DB
default_class_code_attribute_id | asset_type_id | class_code_id | replacement_cost | expected_life | comment_str | user_update | date_update |
|---|---|---|---|---|---|---|---|
| 1 | 2038 | 253128 | 150 | 7 | SYSTEM | 2022-08-09 |
This allows overriding default Replacement Cost and Expected Life values for any asset
Column Name | Data Type | COMMENT |
|---|---|---|
| asset_attribute_id | bigint | PK |
| inv_elem_id | bigint | FK to the ident_inv_element table. |
| replacement_cost | integer | |
| expected_life | integer | |
| comment_str | varchar(4000) | |
| user_update | varchar(400) | |
| date_update | date |
For Signs - these values can be defined in the Combined Asset Inventory window using right-click menu.
This defines Installation Date and Primary Key column names in the asset inventory table since it usually varies
Column Name | Data Type | COMMENT |
|---|---|---|
| asset_column_id | bigint | PK |
| asset_type_id | bigint | FK to the setup_asset_type table. |
| installation_date_column_name | varchar(100) | FK to the setup_column_id table. |
| primary_key_column_name | varchar(100) | FK to the setup_column_id table. |
| comment_str | varchar(4000) | |
| user_update | varchar(400) | |
| date_update | date |
Record for Signs in the DB
asset_column_id | asset_type_id | installation_date_column_name | primary_key_column_name | comment_str | user_update | date_update |
|---|---|---|---|---|---|---|
| 1 | 2038 | ORIGIN | SIGN_ID | SYSTEM | 2022-08-09 |
Contains only Signs asset type note but can contain others.
Defines treatments based on asset attributes. Signs use Asset Condition and Asset Age as decision tree arguments.
There is currently only one performance model, which uses a 7-year deterioration model.
There will be additional nodes for other asset types and expected life years (Linear Condition from 100 to 0 in N Years) when N is a possible expected asset life value. Note the Performance Model list can be viewed in the Performance Model List.
A configuration where we can specify which columns are used as a Decision Tree/Performance Model variable, as a constraint in the analysis setup, as an analysis scope variable, etc. Most likely won't need to be updated for other assets.
Asset condition can be updated by creating and completing Regular inspection in Inspection window.
When inspection is completed, groovy script which is used to calculate overall condition of Sign analyzes Asset Inspection Answers, and populates asset condition using following schema:
| Overall Rating | Criteria for using this rating |
|---|---|
| 1 - Replace |
|
| 2 - Poor |
|
| 3 - Fair |
|
| 4 - Good |
|
| 5 - Excellent |
|
| 0 - N/A |
|
Asset condition could be also updated by system by generating Maintenance inspections, for that new work order should be created.
In creation wizard it should have Asset Type field populated with asset type that currently supports LCCA, in Activity field should be selected activity that has corresponding
treatment mapping in ACTIVITY_TREATMENT table otherwise work order would not be processed by system and inspection records would not be created.
When there are work orders that have activity with corresponding treatment, they will be processed by system job called 'MMS: Update Asset Condition After Maintenance'
this job will be executed automatically once a day and will process all completed work orders since last time job was executed, in case that job was never executed all work orders would be processed.
New Maintenance inspections would be created for inventory elements of processed work orders and 'Update Target Table' will be executed for these inventory elements.
When work order was processed by system job and after that uncompleted then next time system job will be executed it will delete all Maintenance inspections that were created from this work order.
If inspection will be completed again it will be processed by job next time it will be executed.
An Asset Life Cycle JasperServer report is embedded in the Combined Asset Inventory window and can be opened by selecting Show Asset Life Cycle Report in the right-click menu.
