KDOT PMS Replacement Project

R-PMS Requirements : Package . KDOT Historic Pavement Condition Data Integration : Requirement . Interface or ingest historic pavement condition data : Requirement

Requirement - Interface or ingest historic rigid pavement surface condition data link

Properties
Name Value
Description

The solution must interface or incorporate a data conversion process for historic rigid pavement surface condition data (date collected, faulting, joint distress, ...) [this data currently resides in an Oracle database table]. For each year (1986-2022) this would include about 23 data elements. This is nominally 1 mile segment data with typical yearly record counts around 1,500.

Transit To
Name
 White Pavement Study (Concrete) : Task
 T04-02 Validate White Pavement Data Collection process : Task
 KDOT - KHUB, Planning, and Other Database Systems : Group
Id R-PMS 8.1.7
Stereotypes Pavement Condition Data Req

Attributes
Name Type Value
Text Text
ID Text R-PMS 8.1.7
Source Text
Kind Ad Hoc Enumeration Functional
Model Model Element
Risk Ad Hoc Enumeration High
Verify Method Ad Hoc Enumeration Test
ReqType Ad Hoc Enumeration M-Mandatory

Appears In
Diagram
 R-PMS System - Master Requirements for KDOT Replacement PMS System : Requirement Diagram
KDOT PMS Replacement Project