# Scenario Sequence Types

You must have administrator rights to access this feature.

This feature may not be available in every package. Not sure if you have this feature or you want to learn more about it? Send us a message at support@cartegraph.com.

## Projected Date

The date that an asset qualifies for a particular activity. The earliest Projected Date is the highest priority.

### Sort Specifics

• Activities are first sorted by Projected Date, soonest to farthest away.
• When a tie exists when more than one activity with the same projected date, a series of sub-sorts are applied until the tie is broken.
• Subsorts for Asset Criticality (Descending), Install/Replace Date (Ascending), Asset ID (Ascending), Activity (Ascending), Protocol (Ascending)

Example

There are three Pavement segments: Pavement A, Pavement B, and Pavement C. Each Pavement segment qualifies for two activities.

• Pavement A (Criticality: 10) - Patch, Projected 2/1/18 = Wins because soonest date
• Pavement C (Criticality: 20) - Patch, Projected 3/1/18 = Wins because next soonest date and asset has the highest criticality
• Pavement B (Criticality: 10) - Patch, Projected 3/1/18
• Pavement A (Criticality: 10) - Rehab, Projected 6/1/18 = Wins because next soonest date, Criticalities the same, Install Date the same, then asset ID ascending
• Pavement B (Criticality: 10) - Seal, Projected 6/1/18
• Pavement C (Criticality: 20) - Seal, Projected 12/1/18

## Asset Criticality

Asset Criticality is based on assets' Criticality Factor, a field on the asset record. The number is used to compare and prioritize different assets of the same type, a higher number indicating higher priority.

### Sort Specifics

• Activities are first sorted based on their asset's Criticality Factor, highest to lowest number. Null values are treated as a value lower than zero, giving them the lowest priority.
• When a tie exists when more than one activity with the same projected date, a series of sub-sorts are applied until the tie is broken.
• Subsorts - Install/Replace (Ascending), Asset ID (Ascending), Projected Date (Ascending), Activity (Ascending), Protocol (Ascending)

Example

There are five Pavement segments, each segment qualifies for two activities.

Asset ID

Criticality Factor

Projected Date

Activity

Pavement B*

10

2/1/18

Patch

Pavement B#

10

11/1/18

Seal

Pavement A^

8

1/1/18

Patch

Pavement A

8

5/1/18

Seal

Pavement C+

8

6/1/18

Patch

Pavement C

8

6/1/18

Seal

Pavement H**

0

5/1/18

Patch

Pavement H

0

12/1/18

Seal

Pavement D

(null)

1/1/18

Patch

Pavement D

(null)

10/1/18

Seal

* Wins because it has the highest criticality factor and then based on the projected date.

# All activities for the asset with the highest criticality are prioritized above any activities for assets with lower criticality.

^ Wins criticality tie over pavement C because of asset ID.

+ Wins over other activities for pavement C because of alphabetical activity name.

** Wins over pavement D because a nonnull value of 0 is prioritized higher than a null value.

## Asset Criticality and Lowest Estimated OCI

This type of prioritization is commonly referred to as Do Worst First where high-risk assets (highly critical assets that are in poor condition) are given top priority. Asset Criticality is based on assets' Criticality Factor, a field on the asset record. Estimated OCI is based on assets' estimated OCI at the beginning of a plan year. Assets with the highest criticality and lowest estimated OCI is the top priority. The user-specified Asset Criticality Weight and Estimated OCI Weight are factored into the priority. A weight of zero can be assigned to Asset Criticality to have the prioritization based strictly on Estimated OCI. On the Activity List results, the Priority Ranking value represents the calculated priority. See the Priority Ranking help topic for details on how this value is calculated including how weighting is applied.

### Sort Specifics

• Activities are sorted based on the calculated Priority Ranking, highest to lowest number.
• When a tie exists, when more than one activity with the same priority ranking, a series of sub-sorts are applied until the tie is broken.
• The secondary sort differs based on the defined Asset Criticality Weight and Estimated OCI Weight.
• If Asset Criticality Weight is higher than Estimated OCI Weight, the activities are sorted based on the asset's Criticality Factor, highest to lowest.
• If Estimated OCI weight is greater than or equal to Asset Criticality Weight, the activities are sorted based on Estimated OCI at the beginning of the plan year, lowest to highest.
• If a tie still exists between activities, the asset with the earliest install date or replace date take priority the oldest asset.
• Finally all ties are resolved by ordering by asset ID then protocol.

Example

There are four Pavement segments: Pavement A, Pavement B, Pavement C, and Pavement D. Each Pavement segment qualifies for activities. The activities sort like this:

Asset ID

Install Date

Beginning of Plan Year OCI

Esti-mated OCI Weight

Criti-cality Factor

Max Criti-cality Factor for Asset

Criti-cality Weight

Priority Ranking

Pavement C*

1/1/2000

35

2

20

100

1

150

Pavement B

1/1/2000

50

2

50

100

1

150

Pavement D

1/1/2000

80

2

50

100

1

90

Pavement A

1/1/2000

80

2

20

100

1

60

*Activity occurs first due to having the highest priority ranking, and the lower estimated OCI and estimated OCI are weighted higher than asset criticality.

## Asset Criticality and Highest Estimated OCI

This type of prioritization is commonly referred to as Do Best First where assets in the best condition receive maintenance priority. Asset Criticality is based on assets' Criticality Factor, a field on the asset record. Estimated OCI is based on assets' estimated OCI at the beginning of a plan year. Assets with the highest criticality and highest estimated OCI is the top priority. The user specified Asset Criticality Weight and Estimated OCI Weight are factored into this prioritization. A weight of zero can be assigned to Asset Criticality to have the prioritization based strictly on Estimated OCI. On the Activity List results, the Priority Ranking value represents the calculated priority. See the Priority Ranking help topic for details on how this value is calculated including how weighting is applied.

### Sort Specifics

• Activities are sorted based on the calculated Priority Ranking, highest to lowest number.
• When a tie exists, when more than one activity with the same priority ranking, a series of subsorts are applied until the tie is broken.
• The secondary sort differs based on the defined Asset Criticality Weight and Estimated OCI Weight.
• If Asset Criticality Weight is higher than Estimated OCI Weight, the activities are sorted based on the asset's Criticality Factor, highest to lowest.
• If Estimated OCI weight is greater than or equal to Asset Criticality Weight, the activities are sorted based on Estimated OCI at the beginning of the plan year, highest to lowest.
• If a tie still exists between activities, the asset with the earliest install date or replace date takes priority (oldest asset).
• Finally all ties are resolved by ordering by asset ID then protocol.

Example

There are four pavement segments: Pavement A, Pavement B, Pavement C, and Pavement D, Pavement E. Each Pavement segment qualifies for activities.

Asset ID

Install Date

Beginning of Plan Year OCI

Esti-mated OCI Weight

Criticality Factor

Max Criticality Factor for Asset

Criticality Weight

Priority Ranking

Pavement B*

1/1/2000

60

1

50

100

2

160

Pavement D#

1/1/1990

60

1

30

100

2

120

Pavement A

1/1/2000

80

1

20

100

2

120

Pavement C

1/1/2000

35

1

20

100

2

75

Pavement E^

1/1/2010

35

1

20

100

2

75

* Activity for Pavement B occurs first due to it having the highest calculated priority ranking.

# Activity for Pavement D follows having the second highest priority ranking and a higher criticality factor when compared with Pavement A; asset criticality is weighted higher than estimated OCI.

^ Activity for Pavement E occurs last as it has the lowest priority ranking and is more recently installed than Pavement C.