link R-PMS System Use Cases : Model . R-PMS System - EPMS/KANPAV : System
Use Case - KANPAV-01 Calculate Road Families link
| Properties |
| Name | Value | ||||||||||
| Description |
Use to enabling Actor to calculate the Condition of a Road based upon a variety of input elements and constraints. This stage involves shifting to the modeling activities and to take the Historical Data and any new data from WinCPMS, and use this data to determine the Road Categories of each 1/200th mile segment. Once determined then the Road Category allows modeling activities to properly predict the degradation of the surface of the road segment analytically and/or through statistical processes. |
||||||||||
| Transit From |
|
||||||||||
| Id | UC28 | ||||||||||
| Abstract | false | ||||||||||
| Leaf | false | ||||||||||
| Root | false | ||||||||||
| Stereotypes | UseCase, Modeling | ||||||||||
| Justification | A critical part of the AECOM modeling activities includes the normalization of the data into Road Families | ||||||||||
| Business Model | false | ||||||||||
| Primary Actors | Actor - KDOT PMS Operator | ||||||||||
| Status | Identify | ||||||||||
| Rank | Unspecified | ||||||||||
| Relationships Summary |
| Name | Begin | End | |||
|
|
|
|
|||
| Use Case Note |
| ■ Inputs or Prior Activities | |||
| • Time Specific Data Lock (DL(date)) | |||
| • Segment List | |||
| ♦ Location | |||
| ♦ Scheduled Work by Segment | |||
| ♦ Traffic data by Segment | |||
| ■ Actions | |||
| • Group PMS IDs in GEOM based on surface mix and year and continuity (even across county lines)... | |||
| • Apply scheduled treatments to segments to derive Current Segment Condition | |||
| • Convert Mandli/Pavemetrics continuous data per segment into a Discrete Condition State | |||
| ♦ Normalize Mandli/Pavementric data across entire segment | |||
| ♦ Calculate the "Average" segment condition | |||
| ♦ Convert the average segment condition into a Discrete Condition State (Good, Fair, Poor) | |||
| • Merge the Current Segment Condition and the Discrete Condition State into a Segment Condition | |||
| ■ Outputs | |||
| • Inputs into Segment State Vector for Current Segment Condition | |||
| Actions |
| Steps | |||
1.  Actor - KDOT PMS Modeler identifies the date of the data for locking and the segments to be processed |
|||
| 2. SYSTEM Convert Mandli/Pavemetrics continuous data per segment into a Discrete Condition Bins | |||
| 2.1. Normalize Mandli/Pavementric data across entire segment | |||
| 2.2. Calculate the "Average" segment condition | |||
| 2.3. Convert the average segment condition into a Discrete Condition State (Good, Fair, Poor) | |||
| 3. SYSTEM Include Calculate Distress State per segment Use Case | |||
| 4. SYSTEM Include Calculate Remaining Life per segment Use Case | |||
| 5. SYSTEM Merge the Results of Discrete Condition, Distress State, and Remaining Life into Segment State Vector | |||
| Details |
| Name | Value | ||
| Level | Subfunction | ||
| Complexity | High | ||
| Use Case Status | Initial | ||
| Implementation Status | Scheduled | ||
| Preconditions | |||
| Post-conditions | |||
| Author | Rick Miller and Jerry W. Manweiler, Ph.D. | ||
| Assumptions | |||
| Tagged Values |
| Name | Type | Value | |||
| Level | Ad Hoc Enumeration | ||||
| Complexity | Ad Hoc Enumeration | ||||
| Use Case Status | Ad Hoc Enumeration | ||||
| Implementation Status | Ad Hoc Enumeration | ||||
| Preconditions | Multi-line Text | ||||
| Post-conditions | Multi-line Text | ||||
| Author | Text | ||||
| Assumptions | Multi-line Text | ||||
| References |
| File Name | Description | ||
|
|
|||
|
|
|||
| Relationships Detail |
| Name | Value | ||||||||||
| Name | |||||||||||
| From |
|
||||||||||
| To |
|
||||||||||
| Transit From |
|
||||||||||
| Visibility | Unspecified | ||||||||||
| Stereotypes | Extend | ||||||||||
| Appears In |
| Diagram | |||
|
|
|||