R-PMS Requirements : Package . KDOT Historic Pavement Condition Data Integration : Requirement . Interface or ingest historic pavement condition data : Requirement
Requirement - Interface or ingest historic flexible pavement surface condition data link
Properties |
Name | Value | ||||||||||
Description |
The solution must interface or incorporate a data conversion process for historic flexible pavement surface condition data (date collected, rutting, transverse cracking, fatigue cracking, block cracking, ...) [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 10,000. In addition to the summary data in the tables described above, there are specific tables for transverse cracking. These tables contain about 1.5 million records per year with 21 columns for 2013 to 2022 years coverage. A summary statistic table for segments has 12000 records per year and 8 columns also for the period 2013 to 2022. |
||||||||||
Transit To |
|
||||||||||
Id | R-PMS 8.1.6 | ||||||||||
Stereotypes | Pavement Condition Data Req |
Attributes |
Name | Type | Value | |||
Text | Text | ||||
ID | Text | R-PMS 8.1.6 | |||
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 | |||
|