KDOT PMS Replacement Project

R-PMS System Use Cases : Model . R-PMS System - EPMS/KANPAV : System

Use Case - KANPAV-04 Lock Data per Date link

Properties
Name Value
Description

This use case creates a "Snapshot" of the State of the KHS for a specified Actor supplied date

Transit From
Name
 M01 Pavement Modeling : Use Case
 T11-01 Clean up data collection continued : Use Case
 M01 Pavement Modeling : Use Case
 M01 Pavement Modeling : Use Case
 T01-07 Closing out Previous Years FWD and SKID data : Use Case
 T07-05 Calculate Distress States & Performance Levels : Use Case
 T06-02 Calculate Road Categories : Task
Id UC32
Abstract false
Leaf false
Root false
Stereotypes UseCase, Modeling
Justification In order to model the degradation of the pavement for the KHS it is necessary to lock the existing and historical scanned data and PMS data systems so that no changes are allowed
Business Model false
Primary Actors Actor - KDOT PMS Modeler
Status Identify
Rank Unspecified

Relationships Summary
Name Begin End
  : Association
 Actor - KDOT PMS Modeler : Actor
 KANPAV-04 Lock Data per Date : Use Case
  : Include
 KANPAV-00 1R PMS Prediction System : Use Case
 KANPAV-04 Lock Data per Date : Use Case

Use Case Note
■ Inputs or Prior Activities
    • KHS Network Segments Data
        ♦ FDIST
        ♦ FWDGEOM
        ♦ GEOM
        ♦ LMA
        ♦ LOGPROJ
        ♦ PAVEMENT
        ♦ RDIST
        ♦ REHAB
        ♦ REMLIFE
        ♦ ROUGH
        ♦ TRAFFIC
■ Actions
    • Using the Actor supplied Date, Road Category Scenario, Default Design Life, Distress Scenario, Treatment Scenario, Pavement Type(s), etc...
        ♦ Lock the KHS Data as of the specified date, i.e. no data is used that has been entered after the specified date
■ Output
    • The beginnings of a Segment State Vector although missing elements that are added later such as:
        ♦ Current Segment Condition
        ♦ Distress State Vector per segment
        ♦ Remaining Life per segment

Actions
Steps
1. Actor - KDOT PMS ModelerUsing the Actor supplied Requirement Data
    1.1. Lock KHS Data as of <Date>
2. SYSTEM Generate the beginnings of a Segment State Vector for each Segment include:
    2.1. Location: (MP begin, MP end)
    2.2. Distress State <Historical>
    2.3. Road Category <input variables>
    2.4. Auxiliary Data <Fatigue Cracking, Deflectometer, ...>
    2.5. Past Action List
    2.6. Scheduled Treatments List
    2.7. Traffic Estimation/Prediction Analysis per pavement type (ESALs)
        2.7.1. Truck %
        2.7.2. Car %

Details
Name Value
Level Subfunction
Complexity Low
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
 Actor - KDOT PMS Modeler : Actor

Relationships Detail
Name Value
Name
From
Name Value
Role
Element
 Actor - KDOT PMS Modeler : Actor
Multiplicity Unspecified
Aggregation Kind None
Navigable true
To
Name Value
Role
Element
 KANPAV-04 Lock Data per Date : Use Case
Multiplicity Unspecified
Aggregation Kind None
Navigable true
Transit From
Name
 T07-05 Calculate Distress States & Performance Levels : Use Case
 T06-02 Calculate Road Categories : Task
Abstract false
Final Specialization false
Leaf false
Visibility Unspecified
Derived false

Name Value
Name
From
 KANPAV-00 1R PMS Prediction System : Use Case
To
 KANPAV-04 Lock Data per Date : Use Case
Transit From
Name
 T07-05 Calculate Distress States & Performance Levels : Use Case
 T06-02 Calculate Road Categories : Task
Visibility Unspecified
Stereotypes Include

Appears In
Diagram
 R-PMS Use Cases - EPMS - KANPAV Modeling : Use Case Diagram
KDOT PMS Replacement Project