Laserfiche WebLink
Since the segment analysis requires more detailed information than the network analysis, it will <br />be referenced in this chapter much more than the network analysis. Where there are differences <br />between the two modes, they will be specified. <br />Collect and Validate Data <br />When the segment analysis is called by the user (by pressing the "Analyze and Report" button, <br />with the "Street Segment Level" option selected) the first step is to collect the required data, <br />either from the pavement management data previously imported, or from the user -override data <br />entered after the PMS data was last imported. The data required are as follows. <br />Pavement Structure <br />Surface type / material, and thickness <br />Base type / material, and thickness <br />Subbase type / material, and thickness <br />Subgrade R-Value <br />Standard expected pavement design life <br />Segment width and length <br />Traffic <br />Original design ESALs <br />Traffic volumes <br />Average Daily Traffic, or ADT <br />Option: Heavy Commercial Average Daily Traffic (HCADT) or Percent Trucks, or both <br />Predicted traffic growth rate <br />Pavement Condition <br />Last three pavement condition index values <br />Dates of the last three pavement condition surveys <br />Construction and Cost <br />Year the pavement structure was last reconstructed <br />Cost per inch of bituminous overlay <br />Cost of total reconstruction <br />Minimum overlay thickness desired <br />Increment of overlay thickness design <br />Additional Heavv Vehicles <br />Vehicle type <br />Number of each vehicle type <br />Time interval for vehicle numbers (per day, week, month, etc.) <br />Loading status for each vehicle type (full, 1/2-full, or empty) <br />Each input from the list above, whether collected from the PMS database or altered by the user, <br />is validated to ensure it is within reasonable limits and that the type of data is what is expected. <br />15 <br />