Generate TAMP, PM (KDOT), IKE, and District reports

Do the full modeling activities for the 1R processes.

- See AECOM epmsHelpPart20220119100157200 for more information

Prepare the 1R candidate lists for initial review by the District Managers

Make the Frame Based data available to Planning for further utilization in 3R activities

Start the collection of the SKID data regarding the friction coefficients of the road surfaces under optimum dry conditions.

Work with the Planning WinCPMS system and the candidate lists from the previous year efforts for the current year scheduled work and track the current status of the work and update planning with the information

Modeling activity in which the Remaining Life of each 1/200th mile segment is calculated for the entire KHS Network.

Calculate the Performance Factors data and send that data to Planning

Determine if there are any changes tot he Network due to GIS mapping related problems.and/or changes.

Continue KHS data collection activities and load the data into the PMS data systems as it becomes available. - See Business Activities

Feb03-Run both vans on KTA

Apr04-Continue loading LCMS data

Apr05-Continue loading TCR data

Jun04-Continue loading LCMS data

Jun05-Continue loading TCR data

Jul01-Finish NOS collection / processing / reporting

Continue the SKID friction data testing and load the data as it is collected

See Task T08-05

Determine if there are any pavement type changes due to ongoing project work in each District

Determine if there are any changes to the District Alignments due to ongoing projects and GIS changes and record them in the PMS geometry data as well as the KHUB geometry data.

Generate an initial 1R project candidate list with respect to locations and scopes.

Clean the collected data by getting rid of bad data and normalizing any data as necessary.

Send project candidate lists out to the PPDC/Chief C&M/DC's

Acquire the non-State HPMS Samples from Planning and handle appropriately

Generate any Ad Hoc reports and data that might be needed to support the generation of the KDOT Annual Report, TAMP, GASB, ACFR, and Auditor activities - see similar tasks from July

Start the process of planning the activities and projects to be started at the beginning of the New Year.

Start the process of making data available to the KDOT Auditor division for evaluation.

Start the initial development of the Agency Central Financial Report (ACFR) for the State of Kansas

Start the initial development of the Transportation Asset Management Plan

Support the initial development of the Government Accounting Standards Boards reports

Work with Planning to determine if there are any non-internal issues from prior years data collection that need to be addressed at this time.

This stage determine if there are time windows and/or Planning windows that are available for activities.

A modeling stage in which the Pavement Condition States are calculated.

Determine if there are any necessary PCCP reports to be generated.and complete them during this stage of modeling.

This stage of modeling does a calculation of the Distress State Vector and the Performance Levels of the KHS.The historical method is defined but the method for the R-PMS system needs updated algorithmic definition.

This modeling step is used to verify that there is no missing data due to construction work and to convert that data into FILL values in the DB tables.

This is a modeling process in which segment data is used to generate segment based IRI, Rutting, Faulting, and TCR Indexes.

The purpose of this step is the preparation of the frame based HPMS data (State + HPMS) for Planning activities including Modeling activities in support of the 1R and 3R processes.

This task is to finish the NOS collection processes that was started earlier and get the data processed and reported as data files (CSV and XML)

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 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 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 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 step is needed to load the Transverse Cracking Data obtained from the LCMS Vans data collection activities

This stage involved the loading of the Van collected LCMS data from the portable HDD's into the PMS data system

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

In this task it is necessary to validate that the White Pavement Data Collection is working correctly.

This step works on data from the previous year to help fill in gaps that Planning is missing

This task is somewhat similar to the Mar03 task in that the PMS Operator takes the Mandli XML data files and extracts the measure of Transverse Cracking for each 1/200th of a mile segment. Then the PMS operator generates a TCM report/data files for use during modeling.

This particular activity is dependent upon the LCMS Data Collection Vans having finished the scan of the entire KHS 10,000+ miles of highways.  The LCMS data is then processed through the Pavemetrics and Mandli software to generate a series of "reports" that contain either CSV data files or else XML data files with metadata descriptions.

In this stage of the PMS work, it is necessary to verify that the data collection data analysis processes are progressing as expected and to handle any anomalies that might occur.

This activity does the following:

1)        Make changes to PMS Network based upon collection activities

2)        Make necessary changes to PMS Network based upon project completion status

3)        Make necessary changes to PMS Network based upon the Conflation between  the

            PMS Network and the KHS/NHS Networks

This activity represents the actions of the PMS Operators to start making necessary changes to the Logical Segment ID's based upon the actions that occurred in the previous year.

This activity is where the PMS Operations provide support and information to help generate reports for the Secretary and Legislature:

        Annual Report

        IKE Reports

        State Project Manager Reports

This activity provides direct support from the PMS personnel to work with the District representatives to develop the 1R Tours NCV, Data, and Maps

This activity is where the PMS Operations provide support and information to help the other KDOT reporting groups finish their annual reports for the prior year. Groups involved include:

        Federal Report Card

        Priority Formula

        1R Project Ranking Process

        Performance Measures

        DA400 Reporting

        AFR Reporting

        GASB 34 Reporting

        State Specific Performance Measures

        STIP

Operator gathers data from the KHUB systems, planning systems, maintenance systems, traffic, etc. that is to be used to help figure out the collection routes:

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

Start the collection of the FWD data regarding the friction coefficients of the road surfaces under optimum dry conditions.