KDOT PMS Replacement Project

R-PMS System Use Cases : Model . KDOT PMS Process and Data Flow Overview : Pool

Choreography Sub-Process - PMS Modeling Processes link

Properties
Name Value
Description

The PMS Modeling process business activity is responsible for utilizing all of the data input from the Scanning activities as well as a variety of database elements that have been generated in the past from the modeling and/or data elements that have been generated from other KDOT activities such as the Priority Formula, 3R processes, HPMS Processes, Performance Measures Processes, Project Management activities and many others.

Transit From
Name
 Allow for condition deterioration model flexibility : Requirement
 Allow for pavement condition flexibility : Requirement
 Allow for work type constraint flexibility : Requirement
 Allow for pavement deterioration model definition set naming : Requirement
 Allow for action feasibility and cost flexibility : Requirement
 Allow for economic assumption flexibility : Requirement
 3R PPS - Analysis : Requirement
 Allow for pavement condition flexibility : Requirement
 Allow for pavement condition definition set naming : Requirement
 Allow for work type constraint flexibility : Requirement
 Allow for constraint set naming : Requirement
 Allow for condition deterioration model flexibility : Requirement
 Allow for pavement deterioration model definition set naming : Requirement
 Allow for action feasibility and cost flexibility : Requirement
 Allow for economic assumption flexibility : Requirement
 Allow for pavement action set naming : Requirement
 KDOT and Federal Pavement Performance Monitoring Processes : Requirement
 flow and track pavement condition data for KDOT Performance Measures Dashboard submittals : Requirement
 flow and track predicted pavement condition data for KDOT Performance Measures Dashboard submittals : Requirement
 run analyses to determine predicted pavement performance measure : Requirement
 Flow and Track HPMS (pavement) data for submittals : Requirement
 compile pavement condition data following HPMS requirements and pass to KDOT Transportation Planning : Requirement
 Conflation to Planning Network/LRS : Requirement
 Interstate data collected in one calendar year must be passed to Planning before April 15 of the following year : Requirement
 Comprehensive process from collection through analysis : Requirement
 Workflow : Requirement
 Workflow Functionality : Requirement
 Pavement Related Asset Management Processes : Requirement
 flow and track TAMP (pavement) data for submittals : Requirement
 Allow for pavement condition flexibility : Requirement
 Allow for pavement condition definition set naming : Requirement
 Allow for condition deterioration model flexibility : Requirement
 Allow for pavement deterioration model definition set naming : Requirement
 Allow for action feasibility and cost flexibility : Requirement
 Allow for pavement action set naming : Requirement
 Allow for work type constraint flexibility : Requirement
 Allow for constraint set naming : Requirement
 Allow for economic assumption flexibility : Requirement
 Run Analyses to Determine related Pavement Performance, Work Types, and Funding for the TAMP : Requirement
 Security Requirements : Requirement
 User Timeout : Requirement
 Security Authentication and Authorization : Requirement
 Logging Security Violations : Requirement
 Denial of Service : Requirement
 Data Encryption : Requirement
 Data Privacy : Requirement
 Data Segregation : Requirement
 History Tracking : Requirement
 State Security Policy : Requirement
 AD Authentication : Requirement
 Active Directory Integration : Requirement
 AD Configuration : Requirement
 Multiple Users : Requirement
 Single Sign on : Requirement
 Accessibility--1 : Requirement
 Accessibility--2 : Requirement
 Automated User Access List updates : Requirement
 Authorization level : Requirement
 Multiple User Groups : Requirement
 Member of User Groups : Requirement
 User Group Security Access : Requirement
 Default User Group : Requirement
 Group Configuration : Requirement
 Restrict Access : Requirement
 General System Requirements : Requirement
 Compliance : Requirement
 Least Privilege : Requirement
 Default Local Accounts : Requirement
 Session Management : Requirement
 Session Termination-Inactivity Log out : Requirement
Transit To
Name
 Construct PMS State Vector : Action
 Prediction Modeling : Activity
 AECOM : Activity Partition
 Query Current Constraints Matrix : Action
 Output 1R Recommendation List : Activity
 Output 3R Comparative Recommendation List : Activity
 Start Modeling : Initial Node
 Acquire Snapshot Analysis User Parameters : Action
 KANPAV-02 Calculate Federal Distress State Vector : Use Case
 KANPAV-00 1R PMS Prediction System : Use Case
Id BP221.BP145

Procedure
Steps
1. Lock the existing PMS Highway Network
2. Query the data elements based upon a specific lock date (called a Snapshot by the AECom system).
3. Calculate the current state of the system using the query data (snapshot)
3.1. Define the segment for the modeling
3.1.1. AECom utilizes 1 mile segments
3.1.2. Alternative processes can utilize 1/200th mile segments
3.2. Define the Organization level (normalization level)
3.2.1. AECom utilizes the Road Category
3.2.2. Alternative methods can utilize individual road segments
4. Normalize query data into comparatives and aggregate values such as:
4.1. Road Categories
4.2. Distress States
5. Estimate the remaining life of each segment
6. Model the road surface conditions for future years
6.1. AECom procedures
6.1.1. Create an eventual "Steady State" final condition as a target
6.1.2. Transition optimization procedures based upon goals
6.1.2.1. Maximize Benefit within specific cost cap
6.1.2.2. Minimize Costs with constrained by Road Categories
6.1.3. Use the Optimization results to create an Action plan
6.1.4. Rank the Action plan
6.1.5. Identify Candidate Projects
6.1.6. Match the Candidate Projects to Segments
6.1.7. Generate Candidate Project Scopes
6.2. ML/AI postulated procedures (1/200 mile segment)
6.2.1. Utilize the historical scan data segment
6.2.2. Determine historical wear patterns per segment
6.2.3. Acquire modeled future Traffic conditions
6.2.4. Acquire modeled future weather conditions
6.2.5. Acquire modeled future resource availabilities
6.2.6. Acquire modeled future Economic conditions
6.2.7. Blend it all together utilizing industry standard ML/AI procedures such as:
6.2.7.1. Trained Neural Nets using Historical Scan Data
6.2.7.2. Deep Learning Neural Nets
6.2.7.3. Multivariate Regression Analysis
6.2.7.4. Dimensionality Reduction e.g. Primary Component Analysis
6.2.7.5. Genetic Algorithms
6.2.7.6. Statistical Algorithms
6.2.7.7. etc.
6.2.8. Generate Action Plans on aggregated segments (Projects)
6.2.9. Rank Action Plans
6.2.10. Generate Candidate Lists
6.2.11. Match Candidate Lists to Segments
6.2.12. Generate Candidate Project Scopes

Relationships Summary
Name Begin End
 1R Candidate Project LIst : Generic Connector
 PMS Modeling Processes : Choreography Sub-Process
 1R Processes : Choreography Task
 3R Comparative Candidate List : Generic Connector
 PMS Modeling Processes : Choreography Sub-Process
 Priority Formula Processes : Choreography Task
  : Association
 PMS Modeling Processes : Choreography Sub-Process
 Annotation3 : Text Annotation
  : Sequence Flow
 Update PMS Oracle Databases : Task
 PMS Modeling Processes : Choreography Sub-Process
  : Generic Connector
 PMS Database (Oracle) : Group
 PMS Modeling Processes : Choreography Sub-Process

Relationships Detail
Name Value
Name 1R Candidate Project LIst
From
 PMS Modeling Processes : Choreography Sub-Process
To
 1R Processes : Choreography Task

Name Value
Name 3R Comparative Candidate List
From
 PMS Modeling Processes : Choreography Sub-Process
To
 Priority Formula Processes : Choreography Task
Transit From
Name
 3R PPS - Analysis : Requirement

Name Value
Name
From
 PMS Modeling Processes : Choreography Sub-Process
To
 Annotation3 : Text Annotation
Id BP221.BP188
Direction None

Name Value
Name
From
 Update PMS Oracle Databases : Task
To
 PMS Modeling Processes : Choreography Sub-Process
Id BP221.BP146
Condition Type None
Immediate Unspecified
Quantity 1
Timeout 0

Name Value
Name
From
 PMS Database (Oracle) : Group
To
 PMS Modeling Processes : Choreography Sub-Process

Sub Diagrams
Name Description
 R-PMS System - PMS Modeling Processes Activity Diagram : Activity Diagram

Details of the Proposed PMS optimization modeling activities showing data products and activity/action states.

References
File Name Description
 Modeling for 1R-3R 2-12year horizon : Rectangle
N/A
N/A
N/A
N/A
N/A
 Model Inputs : Package
 Model Outputs : Package
 EPMS-Modeling : Subsystem
 EPMS-Modeling : Package

Appears In
Diagram
 R-PMS System - KDOT PMS Data Flow Process Overview : Business Process Diagram
KDOT PMS Replacement Project