The Treatments window provides the following panes: Treatments, Improvements, and Other Improvements. The Improvements pane is for attributes that vary according to a performance model (that is, performance index values such as IRI or roughness) and the Other Improvements pane is for attributes that do not vary according to a performance model (such as traffic or pavement age).
For example, a treatment could be to apply a 2" overlay. The resulting improvements from this treatment could then be to improve the IRI value, reset the pavement age to zero, and reduce bridge clearances by 2". The Improvements pane would show how the IRI value changes and the Other Improvements pane would change the pavement age and bridge clearances.
The Treatments pane lists all treatments used for long-term projects and the costs associated with each. It includes the following columns:
After the treatment selected in the Treatments pane is applied, the condition attributes (also called performance indices) listed in the Improvements pane will change according to the rules configured in this pane. The condition attributes not listed in this pane are unaffected by the treatment and will not change.
The Improvement pane contains the following columns:
Condition Improvement Script: Only provided for those implementations that use the Optimization Analysis window. In these implementations, this column shows the name of the Groovy script that determines the "condition improvement" estimate. The script is selected from a drop-down list, the contents of which are configured in the Groovy Scripts window under the Condition Improvement type of Groovy script.
Note: Rather than editing a script in the Groovy scripts window, you can instead modify a script by clicking the name, which then displays the Description of the Groovy Script Dialog Box. |
Increases Index RSL by N Years: For the condition attribute, after treatment and improvement, the deterioration is set based upon the model selected using the Default Model Structure window's decision tree, but the model's coefficients will be automatically adjusted to extend the life of the road section by N years (based upon the RSL threshold as defined in the Performance Models window). This life extension is over and above the life extension due to the improvement itself. (The value of N is either set directly in the Effective for Years column or results from the Groovy script specified in the Groovy Script for Number of Years column.)
Improvement Deteriorates in N Years: For the condition attribute, after treatment and improvement, the deterioration is set to return to the "before treatment" model after N years after which the "before treatment" model is used. (The value of N is either set directly in the Effective for Years column or results from the Groovy script specified in the Groovy Script for Number of Years column.)
Note: For those treatments with a future deterioration type of either Improvement Deteriorates in N Years or Increases Index RSL by N Years (as set in the Future Detr Type column in the Improvements pane), the value in this column indicates how long the improvement in condition should last until the condition returns to that experienced by the pavement section (according to its underlying performance model). The graph below shows how these years are applied to a maintenance treatment:![]() |
New PC Model: A new deterioration model for the condition attribute that deteriorates is applied based upon the model selected using the Default Model Structure window's decision tree.
Section Model If Exists, Otherwise New PC Model: If there is a model for the section, then, after treatment, it will be used; otherwise, the model selected using the Default Model Structure window's decision tree will be used. Note: Section models are always used during the first years of analysis prior to treatment. The same section model will continue to be used after treatment if you select this option.
Groovy Script for Number of Years: Specifies how the N value for the two future deterioration types Increases Index RSL by N Years and Improvement Deteriorates in N Years is determined. When a script is selected in this column, the system uses it to calculate the N value (and ignores the Effective for … Years column).
Condition Improvement Script: This column is provided for those implementations that use the Optimization Analysis window. In these implementations, this column shows the name of the Groovy script that determines the "condition improvement" estimate. The script is selected from a drop-down list, the contents of which are configured in the Groovy Scripts window under the Condition Improvement type of Groovy script.
Note: Rather than editing a script in the Groovy scripts window, you can instead modify a script by clicking the name, which then displays the Groovy Script Dialog Box. |
After the treatment selected in the Treatments pane is applied, the non-PI-based attributes listed in the Other Improvements pane will change according to the rules configured in this pane. When multiple records appear in this pane, the order in which the attributes are updated is set by the value in the Update Order column of the Setup PMS Analysis Columns window.
The Other Improvement pane contains the following columns:
Changing Attributes: Provides a drop-down list that contains all non-PI-based attributes (that is, attributes that don't change according to a performance model, such as pavement age or traffic). These attributes are columns in the Network Master file and have the Restart with Treatment check box selected in the Setup PMS Analysis Columns window.
Condition Improvement Script Other: Shows the name of the Groovy script that determines the "condition improvement" estimate. The script is selected from a drop-down list, the contents of which are configured in the Groovy Scripts window under the Condition Improvement type of Groovy script.
Note: Rather than editing a script in the Groovy scripts window, you can instead modify a script by clicking the name, which then displays the Groovy Script Dialog Box. |