KDOT PMS Replacement Project

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

Group - KDOT - KHUB, Planning, and Other Database Systems link

Properties
Name Value
Transit From
Name
 Active Directory Integration : Requirement
 AD Configuration : Requirement
 GPS Data : Requirement
 Interface or ingest historic pavement surface friction expanded data : Requirement
 Interface or ingest historic pavement TSD data : Requirement
 Interface or ingest historic rigid pavement surface condition data : Requirement
 Interface with KDOT implementation of Roads and Highways called K-Hub : Requirement
 Interface with KDOT project management systems : Requirement
 Interstate data collected in one calendar year must be passed to Planning before April 15 of the following year : Requirement
 KDOT GIS Systems Integration : Requirement
 KDOT Highway Inventory Systems Integration : Requirement
 Non-Interstate data collected in one calendar year must be passed to Planning before June 15 of the following year : Requirement
 Non-State-maintained data collected in one calendar year must be passed to Planning before June 15 of the following year : Requirement
 Provide Data or Interface to Feed the Priority Formula : Requirement
 Use K-Hub Interface to push PMS pavement condition data : Requirement
 Use K-Hub Interface to update PMS highway network and LRS : Requirement
Id BP221.BP46

Children
Name Description
 KHUB.LRS_Deltas : Data Store
 KHUB.Traffice(Volume) : Data Store
 KHUB.NHS : Data Store
 KHUB.Maintenance : Data Store
 KHUB.Class : Data Store
 WinCPMS : Data Store
 GIS-BaseMap : Data Store
 KHUB.Shoulder : Data Store

References
File Name Description
N/A

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