In this task it is necessary to start the White Pavement Data Collection activities

This is a continuation of the Mar03 Activities and is here for reference only

This stage is dedicated to loading the LCMS Van scanned and interpreted Join Distress Data for the KHS.

This is a continuation of the Mar04 Activities and is here only for reference

This task involved the querying of the existing/historical PMS data set to create a collection of historical data

This step then involves load any newly created data from Planning (WinCPMS) and also load new Traffic estimated data coefficients, Pavement Surface Type definitions (and specifications) as well as any available Shoulder data.

This Use Case is a primary Use Case in that it formulates the overall actions of the PMS modeling activities but in general utilizes included Use Cases to do the actual work

This stage involves shifting to the modeling activities and to take the Historical Data and any new data from WinCPMS, and use this data to determine the Road Categories of each 1/200th mile segment. Once determined then the Road Category allows modeling activities to properly predict the degradation of the surface of the road segment analytically and/or through statistical processes.

This step is a continuation of the step Apr04 as the LCMS data is multiTerabyte in size and takes a very long period of time to load into the PMS data tables.

This step involves the loading of the 1/200th mile segment data aggregate / metadata regarding IRI, rutting, faulting, and TCR indices

This again is a continuation activity as the TCR data requires a significant amount of processing time to extra the TCR values from the Mandli XML data files.

This action is also a continuation action from the Apr01 action by helping to support Planning activities on the non-Interstate related data issues.