Pavement Condition is for storing the annual pavement condition survey results and their locations, such as IRI, Rutting, Faulting, Cracking, etc. Out of the box, the table is named PMS_AUTOMATED_CONDITION_SURVEY, and the corresponding window is located under Pavement Analyst > Asset Performance > Automated Condition Survey > Automated Condition Survey Data menu.
PMS_AUTOMATED_CONDITION_SURVEY is also a strictly Location-referenced data table i.e., the data is identified strictly by a location in the LRS network (route with "from" and "to" point boundaries). The main difference between Pavement Condition data and Roadway Inventory data is that condition data has an EFF_YEAR column, to record data from each data year, and some additional out-of-the-box pavement condition columns.
Out of the box, PMS_AUTOMATED_CONDITION_SURVEY table has these 9 columns:
| COLUMN_NAME | DATA_TYPE | DATA_LENGTH | NULLABLE | COMMENTS |
|---|---|---|---|---|
LOC_IDENT | NUMBER | 22 | N | Location # used in SETUP_LOC_IDENT table to store the record’s location in the LRS. This is a system column. |
EFF_YEAR | NUMBER | 22 | Y | Data year. |
WC_ID | NUMBER | 22 | Y | Pavement type |
PMS_IRI_VALUE | NUMBER | (22,2) | Y | International Roughness Index |
PMS_RUTTING_VALUE | NUMBER | (22,2) | Y | Pavement rutting value |
PMS_FAULTING_VALUE | NUMBER | (22,2) | Y | Pavement faulting value |
PMS_PCT_CRACKING | NUMBER | (22,2) | Y | Pavement percent cracking |
DATE_UPDATE | DATE | 7 | Y | Last update date of the record |
USER_UPDATE | VARCHAR2 | 400 | Y | Last update user of the record |
COMMENT_STR | VARCHAR2 | 4000 | Y | Comment of the record |
Table and Window Configuration
The configuration of this dataset starts by expanding the PMS_AUTOMATED_CONDITION_SURVEY table structure to include customer-specific pavement condition data collected in the survey, such as block cracking, cracking extent and/or severity from different zones, bleeding, etc.
Similar to Roadway Inventory data, when adding columns to the table, pay special attention to the type of data to be added: Is it “List” or “simple value”. Then, follow the instruction detailed in “Create and Import Lookup Values” and “Add Columns to a Table” Chapter in “AgileAssets System Foundation Configuration Guide” and add them into the PMS_ROADWAY_INVENTORY table.
After all the columns have been added to the table, follow the instruction detailed in “Add Columns to a Data Window” section in “AgileAssets System Foundation Configuration Guide” to add those columns to the window.
At this point, the system will have an empty PMS_AUTOMATED_CONDITION_SURVEY table and the window will display an empty dataset.
Import Data
The next step is to create an Import Configuration, and load the data into the table. Follow the instruction detailed in “Load Data into Tables” chapter in “AgileAssets System Foundation Configuration Guide” to create the import on pavement condition table.
Out of the box, a standard import using csv file has been configured that matches the PMS_AUTOMATED_CONDITION_SURVEY table configuration. It uses a csv file with the following specification:
| Column Header | Data Type | Description |
|---|---|---|
EFF_YEAR | Number | Effective year of the traffic data |
ROUTE_NAME | String | Route Identifier in the LRS network |
LANE_DIR | Number | 1 for Ascending (Cardinal or Primary) direction. 2 for Descending (Non-cardinal or Reverse or Non-Primary) direction. 0 for both directions. |
LANE_ID | Number | 0 for all lanes. Otherwise the specific lane number (1,2,3, etc.) |
OFFSET_FROM | Number | Start Measure of the location |
OFFSET_TO | Number | End Measure of the location |
PAVEMENT_TYPE | String | Pavement type - corresponding to records in Pavement Analyst > Setup > Inventory Setup > Pavement Type window |
PMS_IRI_VALUE | Number | IRI value |
PMS_RUTTING_VALUE | Number | Rutting value |
PMS_PCT_CRACKING | Number | Percent Cracking |
PMS_FAULTING_VALUE | Number | Faulting value |
If there is client-specific configuration to PMS_AUTOMATED_CONDITION_SURVEY to track additional pavement condition data element, the template can be expanded to include those fields. In addition, the following objects needs to be updated to reflect those changes to ensure all the steps in the import are running correctly:
- PMS_AUTOMATED_CONDITION_SURVEY table and window
- Import configuration into the PMS_AUTOMATED_CONDITION_SURVEY table
The guideline for updating or creating additional import configuration is similar to roadway inventory data. One difference is that most of the time, when updating roadway inventory data, you would “replace” the entire dataset because roadway inventory is not differentiated by year, whereas for condition data, you will only import (or replace) the data with a specific year (or latest year), and leave the historical data untouched. This can be achieved by specifying a “Replace Where Clause” in the import Configuration, for example:
EFF_YEAR=2019
After running the import, the system will have a populated PMS_AUTOMATED_CONDITION_SURVEY table and the window will display the corresponding data.
