The solution is desired to interface or incorporate a data conversion process with historic pavement core data (location, date, bound thickness by layer with approximate unbound lengths, condition by layer). Currently KDOT does not have this data in electronic form, but an effort may be made by KDOT to back populate a table with this data and then include it in the solution.