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 pavement csv report data link

Properties
Name Value
Description

The solution is desired to develop an interface or data conversion process to allow users of the system to access to formatted csv "reports" like those created by Mandli RVW [this is just the means to get LCMS and profile data from the collection system into the PMS]. For each year (2013-2022) this would include about 15 data elements. Reports are run at three different aggregations, so a frames report would have about 2.5 million records. A tenths report would have about 120,000 records, and a segments report would have about 12,000 records. For the non-State HPMS, frames reports would be about 80,000 records with 15 fields, 4,000 and 15 for tenths, and about 300 and 15 for HPMS segments.

Transit To
Name
 T06-01 Create Historical Data and Load New from Planning : Task
Id R-PMS 8.1.2
Stereotypes Pavement Condition Data Req

Attributes
Name Type Value
Text Text
ID Text R-PMS 8.1.2
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