Skip to main content

Create a Treatment

Define an asset treatment and its effects

When managing Treatments, select Create Treatment in the bottom-left corner to start creating a new one. If the button is dimmed out, select in the top-right corner to close the current Treatment first.

A Treatment represents a physical procedure to improve an asset's condition. Fill in the form to describe this procedure, the Asset Groups it applies to, the associated costs, and the effect it has on specific Condition Parameters. Fields marked with an asterisk * require a value to continue.

When you're finished, select Create at the top to create the new Treatment.

Note

Treatments use the following features, so make sure they're set up correctly for your organisation before getting started:

Details

The Details section of an example Treatment

Configure the Treatment's priority, length constraints and subsection merging method:

  • Name * - enter a distinct name that clearly identifies the Treatment.

  • Colour * - choose a colour for the Treatment. This helps to identify the Treatment in Layers and Reports.

  • Feature Code * - choose the type of asset that the Treatment applies to, e.g. Carriageway (CW), Footway (FW). This filters the Asset Groups and Condition Parameters that can be picked in later sections.

  • Critical - if enabled, the Treatment will always be selected for subsections that trigger it, subject to budget. In asset sweating scenarios (where Treatments are deferred to prolong asset lifespan), the Treatment will always be flagged as Last Chance and therefore guaranteed to be selected.

  • Major - enabled by default. The Treatment won't be selected on any triggering subsections that have planned works (as defined by the Works Layer of a Treatment Set). If disabled, the Treatment is considered Minor, and will only be excluded if a subsection has planned work in the current year.

  • Treatment length min * - specify a minimum length in metres, e.g. the length required for the Treatment to be cost-effective. It must be greater than or equal to the Subsection Length in a Treatment Set's Details. If the length of a subsection - or a scheme of merged subsections - is shorter than this, the Treatment won't be triggered.

  • Treatment length max * - specify a maximum length in metres, e.g. the length of road that can be closed to the public at any one time. Subsections will not be merged if their combined length exceeds this, even if the Merge when setting is fulfilled. However, this setting is ignored when Whole section merge is enabled in a Treatment Set's Details.

    Note

    If you set the min and max length to the same value, this will result in fixed-length Treatments that are never merged (unless they cover 99%+ of the Section).

  • Merge when * - to create realistic schemes that fit within the Treatment length range, Horizons merges adjacent triggered subsections into single uninterrupted lengths. It will also merge separate subsections using the chosen method:

    • Efficiency - used by default. If the triggered subsections would comprise over X percent of the potential Treatment scheme after merging, then merge them. In the example below, 60 m of the 100 m length is defective. Therefore, an efficiency of 60% or higher would include the entire 100 m in the merged Treatment scheme.

    • Proximity - if triggered subsections are within X metres of each other, merge them. In the example below, each defective subsection is less than 40 m from the next. Therefore, a proximity of 40 m would include the entire 100 m in the merged Treatment scheme.

    By default, merging is only performed along the length of an individual XSP (e.g. road lane). For other settings that affect merging, see Treatment Set Details.

    Example illustration
    Merging rules

    During the merge process, the following rules are observed:

    1. Any Treatment can be merged across a blank subsection that doesn't trigger any Treatments.
    2. A parent Treatment can be merged across a child Treatment.
    3. A child Treatment cannot be merged across a parent Treatment.
    4. The merged Treatment scheme must be valid for all the Asset Groups it spans.

    For the example below, imagine a Treatment Set where Treatment A is the parent of Treatment B.

    The first two B Treatments can merge across the blank subsection (rule i). However, they cannot merge with the third B Treatment because they cannot overwrite the parent A Treatment (rule iii). The final two A Treatments can merge across the child B Treatment (rule ii).

    In all cases, a subsection can only be overwritten if its Asset Group is valid for the merged Treatment (rule iv). It may be that A and B are bituminous Treatments and the blank subsection is concrete. In that case, the blank subsection cannot be overwritten with Treatment B.

    A diagram showing how subsections can be overwritten when merging
    Note

    In asset sweating scenarios, if any merged subsections are flagged as Last Chance, the entire merged scheme will be flagged as such.

  • Applies to * - select one or more Asset Groups that the Treatment can apply to. Select Add Asset Group, make your selection and then select Save. To remove an added Asset Group, select its button.

    In some situations, you might want to move assets into another group after the Treatment has been applied to them, e.g. their material composition has changed. Select an Asset Group's Change field and choose a destination Asset Group from the list.

    Two Asset Groups added to the list

Costing

Define fixed and unit costs for the Treatment over multiple financial years, along with expected emissions:

  • Cost type * - choose whether the Treatment's costs are Linear (per m) or Area (per m2).

  • Costs * - specify Treatment costs for one or more financial years. Select Add Cost, make your selection and then select Save. To remove an added year, select its button.

    For each added year, you can specify a combined fixed cost estimation (e.g. equipment, traffic management) and a combined unit cost estimation (e.g. materials, labour, fuel).

    If a financial year isn't specified, the costs of the previous specified year are used. If the unspecified year occurs before the first specified year, the first year's costs are used. Financial years occurring after the final specified year are calculated using the Inflation rate.

    In the example below, FY25 will use the same costs as FY26. FY28 and FY29 will use the same costs as FY27. FY30 onwards will be adjusted for inflation.

    3 years with fixed and unit costs specified
  • Inflation rate * - enter an average inflation rate for calculating future financial years.

  • BCR scale factor * - Horizons calculates a benefit-cost ratio (BCR) score for every Treatment. If Alternative treatments is enabled in a Treatment Set, a Treatment with a higher BCR may be chosen instead of the triggering Treatment. To inflate or deflate this Treatment's BCR score, enter a decimal scaling factor (1.0 = no adjustment). To learn more, see Treatment Set Details.

  • CO2 Emission / NOx Emission - to model emissions caused by the Treatment, enter a value in kg per m/m2 (depending on the Cost type). If you have emission targets, you can define them in a Strategy that can influence a Works Plan.

Effects

Describe how the Treatment will affect the assets being treated.

The status of each asset Section is tracked using Condition Parameters that are initially populated with survey data. When generating a Works Plan, Horizons intelligently deteriorates these conditions for subsequent years. If any Condition Parameters for a subsection cross a threshold, it triggers the need for treatment to restore them to desirable levels.

Select one or more Condition Parameters that the Treatment will affect. Select Select Condition Parameters, make your selection and then select Save. To remove an added parameter, select its button.

For each added parameter, choose the Adjustment type and enter an Amount. The options differ depending on whether the parameter has ascending severity (lower values are better) or descending severity (higher values are better).

Ascending severity
  • Reset to - overwrite the parameter value with the amount.

  • Scale by - multiply the parameter value by the amount (between 0 and 1).

  • Reduce by - subtract the amount from the parameter value.

Descending severity
  • Reset to - overwrite the parameter value with the amount.

  • Scale by - multiply the parameter value by the amount (1 or higher).

  • Increase by - add the amount to the parameter value.

Multiple example Condition Parameters
Note

Don't forget to save your changes using the top green button!