The "HPMS Workflow Articles" page is the culmination of all articles in the HPMS Workflow category. This page eliminates the need to click between articles.

Workflow

The workflow is the steps taken in the HPMS Manager application for actions-based processes. These steps help the user understand the progression of the application, essential tasks, and covered actions on the software. There are seven steps in the HPMS Manager workflow. It is very common for this workflow, or its particular steps, to be executed many times during the submittal process for any given year.

Build a Data Table -- HPMS Manager combines and segments all necessary data into a single table with direction from the user for processing validations, edits, and reporting.
Populate Report -- This report allows users to identify issues with the source data used in the Data Table creation prior to use in other systems and processes.
Validations -- This functionality allows the user to validate data in a Data Table according to very specific and detailed FHWA requirements.
Edit Data -- This functionality allows the user to address and correct data issues found as a result of Validations.
Sample Adequacy -- HPMS Manager’s Sample Adequacy module allows the user to verify that the data is adequately sampled and to address issues of over or under sampling.
Standard Reports -- This functionality allows the user to verify and report certified public road mileage through preconfigured reports.
Submittals and Summaries -- This functionality allows the user to create submittal and summary files to submit to the FHWA.

The LADOTD workflow portion of the Help Guide has a section dedicated to each step above. However, the Populate Report step will be combined with the Build a Data Table step due to their close association; articles for both steps will be located under the "Build a Data Table" section.

Build a Data Table

Data Source Configuration

In order to begin the first step in the workflow-- Build a Data Table-- the user must initiate a Data Source Configuration. The Data Source Configuration interface allows the user to tackle three actions: adding new data sources, editing previously created data sources, and deleting data sources that no longer exist or are no longer relevant. To initialize the Data Source Configuration, the user can follow these general steps.

First, open the Data Source Configuration interface by selecting the Data Sources menu item in the System Administration tab.

Next, select the "Add New" button. This will trigger the picklist beneath the button to become available for selection.

Then, select a data source type in the Data Source Type picklist. The user can choose between File, Database (SQL Server or Oracle), Map Service, and Access Database here. The content in the connection parameters section, or the information underneath this picklist, is dependent upon the selected data source type.

Finally, fill out the connection parameters.

As indicated above, each Data Source Type has different connection parameters. The breakdown of these parameters and the specific steps toward Data Source Configuration is outlined in other articles which are identifiable by the Data Source Type (File, Database (SQL Server or Oracle), Map Service, and Access Database).

Managing Data Sources

File Data Sources

All information found here occurs in the Data Sources interface on the System Administration tab.

When a user is trying to initiate a Data Source Configuration, they can select the “File” option from the Data Source Type picklist. This selection will cause the interface to resemble the image below if files exist in the system; if not, the table containing the Delete, File Name, Type, Separation Chart, and Load/Reload columns will be empty.

To load files into the data source, follow these steps:

Click the “Show/Add Files” button to open up the “Files Found” interface. If the desired files already exist in the file share, skip steps 2-4.
Click the “Choose Files” button. A file manager will open prompting the user to add files from the local computer.
Select one or more files to add. Hold down the control (Ctrl) key while clicking on a file to select multiple files.
After selecting all the desired files, click the “Open” button. HPMS Manager will then add the selected files to the application’s file share.
To finish uploading the files to the data source, check the checkbox to the left of the file and click the “Add Files to Source” button.
For files that require separating characters, such as CSV files or pipe delimited files, edit the Separating Characters column by clicking into the cell to change the value to ensure proper file parsing and loading. Skip this step if the file does not require a separating character.
Select which files to load/reload into the data source by selecting the checkbox located in the “Load/Reload” column.
After selecting the desired file(s), click the “Save Changes” button to load/reload files.

The images below visually display this process.

To delete a file from the data source, follow these steps:

Select which files to delete by checking the checkbox in the “Delete” column. If you would like to delete all files in the data source, click the “Select All to Delete” link instead.
After selecting the desired files, click the “Save Changes” button.

Database Data Sources

All information found here occurs in the Data Sources interface on the System Administration tab.

When a user is trying to initiate a Data Source Configuration, they can select one of the Database options from the Data Source Type picklist. The Database options are “SQL Server” and “Oracle.” Below is an example of how the interface would look if the user selected the "SQL Server" option. However, the "Oracle" option has the same fields available.

LADOTD Data Source Configuration (2).png

To create a Database data source, follow these steps:

Fill out the database connection fields. The Server, User Name, Password, Database, and Shortcut parameters are required for managing a database source type.
- Server -- Name of the server.
- User Name -- Username for the database.
- Password -- Password used to connect to the database.
- Database -- Name of the database.
- Shortcut -- Name of the data source. This is the name that will appear in all data source picklists.
After all parameters have a value, click the “Verify Source” button in the lower left corner of the interface to verify the connection to the specified database.
If the connection is valid, click the “Save Changes” button.

Here is a visual of these steps:

LA HPMS Workflow Image Update (1).png

Map Server Data Sources

All information found here occurs in the Data Sources interface on the System Administration tab.

When a user is trying to initiate a Data Source Configuration, they can select the "Map Server" option from the Data Source Type picklist. This will trigger the following interface to appear:

LADOTD Data Source Configuration (4).png

To create a map service data source, follow these steps:

Fill out the map service parameter fields. The Service Directory, Service, Service Type, Include in Map Legend, and Shortcut parameters are required when managing a map service data source type.
- Service Directory -- URL of the map server.
- Service -- Name of the map service.
- Service Type -- Type of service (MapServer, FeatureServer, etc.).
- Include in Map Legend -- Include events in the selected map service in the map legend.
- Shortcut -- Name of the data source. This is the name that will appear in all data source picklists.
After all parameters have a value, click the “Verify Source” button to verify the connection to the map service.
If the connection is valid, click the “Save Changes” button.

Here is a visual of these steps:

LA HPMS Workflow Image Update (2).png

Access Data Sources

All information found here occurs in the Data Sources interface on the System Administration tab.

When a user is trying to initiate a Data Source Configuration, they can select the "Access" option from the Data Source Type picklist. Then, the following interface will appear:

LADOTD Data Source Configuration (5).png

To create an "Access" data source, follow these steps:

Click the "Show/Add Files" to open the "Files Found" interface. If the desired file already exists in the file share, skip steps 2 & 3.
Click the "Choose Files" button. A file manager will open prompting the user to add files from the local computer. Only one Access file can be added to an Access data source.
After selecting the desired file, click on the "Open" button. The file will then appear in the file share.
To finish uploading the file to the data source, select the checkbox to the left of the file and click the "Add Files to Source" button.
Then, fill out the "Shortcut" parameter. Use the Shortcut field to specify a shortcut name for the data source. This shortcut will appear in all data source picklists.
After all parameters have a value, click the "Verify Source" button to verify the connection to the Access file.
If the connection is valid, click the "Save Changes" button.

Here is a visual of these steps:

Data Tables Configuration

After configuring data sources, the user can create a data table in the Data Table Configuration interface. In order to access this interface, the user must locate the System Administration tab and navigate to the Data Tables Configuration icon. The image below shows this icon in a red box.

Users can create and manage data tables used throughout the application in the Data Table Configuration interface. This interface provides the user with three core functions in the workflow:

Data Table Creation -- Used to create new data tables.
Data Table Definition – Used to edit the information and the definition of the selected data table; concentrated in the Data Table Information, Required Items, and Attributes tabs.
Data Table Population – Used to populate the selected data table with the data specified in Data Table Definition.

Data Table Creation

The Data Table Configuration interface allows the user to create data tables. To create a new data table, the user can follow these steps:

(1) First, click the "Create New" button on the Data Table Configuration interface to trigger the appearance of the Create New interface.

(2) Then, fill out the necessary and desired fields.

Field	Required? (Y/N)	Description
Name	Yes	Textbox used to enter a name for the data table.
Description	No	Textbox used to enter a description for the data table.
Year	Yes	Textbox used to specify the year of the data table.
Type	No	Picklist used to specify a HPMS Data Table Type.
Temporal Date	No	Single selection "bubble" used to specify if the data table will retrieve temporal data.
Setup Table	No	Single selection "bubble" used to copy a data table definition from a previously created data table.

(3) Finally, click the “Create” button at the bottom of the interface after all desired fields have a value.

Data Table Definition

The Data Table Configuration interface provides options to edit or manage general information and the definition of the selected data table using the three tabs provided: Data Table Information, Required Items, and Attributes.

Data Table Information

The first tab, Data Table Information, is used to edit the general information of the selected data table. This tab will be initially displayed when the user selects the Data Table Configuration icon, and it contains many fields, such as the Name and Year textboxes.

Required Items

The second tab on the Data Tables Configuration interface, Required Items, allows the user to specify the location of the source data for routes and sample data. In order to accomplish this goal, the user can select the desired Data Table in the top left picklist on the interface. This tab also possesses its own internal tabs-- Routes and Sample Section Locations-- to enter the appropriate information.

Required Items Tab

Users can utilize the Routes tab to enter in the source of the route network. There are two options for sources here: R&H and Non-R&H.

Required Items -- R&H Source

To add a R&H route source, the user must follow these steps.

Check the “Is R&H” checkbox at the top left of the interface, under the internal tabs. The fields will then change to support R&H route sources.
Fill out the Map Service, Network Name, Version, and Filters fields.
After filling in the desired fields, click the “Save Changes” button at the bottom of the interface.

Required Items -- Non-R&H Source

To add a Non-R&H route source, the user must follow these steps.

Uncheck the “Is R&H” checkbox at the top left of the interface, under the internal tabs. The fields will then change to support Non-R&H route sources.
Fill out the Data Source Dropdown, Table Name, Route ID, From Measure, To Measure, From Date, To Date, and Filters fields.
After filling in the desired fields, click the “Save Changes” button at the bottom of the interface.

Sample Section Locations Tab

The Sample Section Tab can be used to specify the source data for samples. Similar to the Routes tab, the fields on this tab change based on the R&H or Non-R&H status.

Sample Section Locations -- R&H Source

To add a R&H sample source, the user must follow these steps.

Check the “Is R&H” checkbox at the top left of the interface, under the internal tabs. The fields will then change to support a R&H registered event.
Fill out the Map Service, Version, Event Name, Source, HPMS Data Table, and Filters fields.
After filling in the desired fields, click the “Save Changes” button at the bottom of the interface.

Sample Section Locations -- Non-R&H Source

To add a Non-R&H sample source, the user must follow these steps.

Uncheck the “Is R&H” checkbox at the top left of the interface, under the internal tabs. The fields will change to support a Non-R&H event.
Fill out the Data Source, Table Name, Column, Route ID, From Measure, To Measure, From Date, To Date, and Filters fields. The user can select the Allow Save to Source checkbox if desired.
After filling in the desired fields, click the “Save Changes” button at the bottom of the interface.

Attributes

The third tab on the Data Tables Configuration interface, Attributes, can be used to define the sources and parameters for each of the HPMS data items. Similar to the Required Items tab, the Attributes Tab also has internal tabs; these four tabs are R&H Events, Non-R&H Events, Parent/Child Events, and Derived Events. Each of these tabs has specific guidelines attached to them on how to properly add data items.

R&H Events, Non-R&H Events, Parent/Child Events Tabs

The R&H Events tab is used to add data items from a registered Roads and Highways event, the Non-R&H Events tab from a file or database table source, and the Parent/Child Events tab from a parent data item. In order to add a R&H, Non-R&H, or Parent/Child data item, users must follow the steps below.

Click the “Add New Row” hyperlink to add a blank row. To copy an existing row, check the checkbox located to the left of the data item. After selecting the desired rows, click the “Copy Selected Rows” link. All fields are populated except the Item Name column.
Fill out the parameters. Edit a parameter by clicking into the desired cell. A picklist or textbox will appear relative to the column being edited.
After adding the desired data items, click the “Save Changes” button at the bottom of the interface.

Parameters

The second step on adding a data item from the R&H, Non-R&H, Parent/Child Events tabs includes either editing or adding certain parameters. Those parameters, and which tab they are listed under, are outlined in the table.

Parameter	Internal Tab	Description
Item Name	R&H, Non-R&H, Parent/Child	Used to specify a data item.
Map Service	R&H	Used to specify which map service the R&H event is located in.
Version	R&H	Used to specify which geodatabase version to use for the data item.
Event	R&H	Used to specify which R&H event to use for the selected data item.
Column	R&H, Non-R&H, Parent/Child	Used to specify the source column to use for the selected data item.
Filters	R&H, Non-R&H, Parent/Child	Used to enter a SQL filter the Populate/Population process uses to retrieve a subset of data from the from the selected event, table, or file.
Comment	R&H, Non-R&H, Parent/Child	Used to specify a field to use for comments in submittal files for the selected data item.
Data Source	Non-R&H, Parent/Child	Used to specify the data source containing the table or file for the selected data item.

Table/File Name	Non-R&H, Parent/Child	Used to specify the table or file containing the data for the selected data item. Populated once a data source is selected.
Route ID	Non-R&H	Used to specify the Route ID field when importing data.
From Measure	Non-R&H	Used to specify the From Measure field when importing data.
To Measure	Non-R&H	Used to specify the To Measure field when importing data.
From Date	Non-R&H	Used to specify the From Date field when importing data.
To Date	Non-R&H	Used to specify the To Date field when importing data.
Parent Item	Parent/Child	Used to specify which data item is the parent item.
Parent Column	Parent/Child	Used to specify the parent column to use for the selected data item.

Derived Events Tabs

The Derived Events tab is used to add derived data items. For users to add a Derived Events data item, they must follow the steps below.

Click the “Add New Row” link to add a blank row. To copy an existing row, check the checkbox located to the left of the data item. After selecting the desired rows, click the “Copy Selected Rows” link. All fields are populated except the Item Name column.
Select the desired data item by clicking into Item Name column. Use this column to specify which derived data item to add to the data table. The Description column is auto populated with the Item Description of a data item.
After adding the desired data items, click the “Save Changes” button at the bottom of the interface.

Delete Data Item

If a user wishes to delete a data item from any of the four tabs, they can follow these steps:

Select the checkbox located in the first column of each desired item or use the checkbox in the table header to select all data items for deletion.
After selecting the desired items, click the “Delete All Selected” hyperlink to permanently delete the items from the data table definition.

Data Table Population

Once the user has configured all the routes, samples, and desired HPMS data items, they can populate the data table by clicking the "Populate Data Table" button found on the Data Table Information, Required Items, or Attributes tab. These tabs are located under the Data Tables Configuration icon on the System Administration ribbon. After the populate process is complete, the button will change to display the message, "Refresh Data Table."

At any point, the user can reload the data in the table with the latest updates by clicking the "Refresh Data Table" button. This population process only adds data items that are complete (i.e., all required fields have values on the data table). The "Attributes Complete Message/Count" will appear below the Attributes tab's table to display the number of data items that are complete, and it will appear in the data table after the populate/refresh process.

In the image below, the Refresh Data Table button and the Attributes Complete Message/Count are indicated in red boxes to show their position and format on the interface.

After populating the data table, the user should check the Required Items and Attributes tabs to see if an error occurred during the populate process. On the Required Items tab, an icon will appear in the tab header. On the Attributes tab, an icon will appear in the "Status" column (shown above). The three statuses and their icons are described below.

Icon	Type	Description
	Success	Indicates that no errors were encountered while importing data for the item.
	Warning	Indicates that a non-fatal error occurred while importing data for the item. Hovering over the icon will display details of the error.
	Fatal Error	Indicates that a fatal error occurred while importing data for the item. Hovering over the icon will display details of the error.

Populate Report

After the successful completion of the Data Table Population, the user can access the populate report by clicking the "View Populate Report" hyperlink. This link can be accessed by following these steps:

LA HPMS Check Populate Report.png

The Populate Report interface shows all warnings and errors found while populating. The populate process attempts to correct warnings and remove errors on import if possible. However, the user can also review and resolve warnings in the Edit Log/Save to Source interfaces under the Edit module. Any errors found during the populate process will need to be fixed in the source data (Data Table Configuration), and the data table will need to be repopulated. The user can repeat this process until the data in this report is at an acceptable level.

Validations

After Building a Data Table, the user can move on to the Validations step in the workflow. The Validations tab provides tools to run a series of different validation checks on routes and HPMS data items before submitting data. These checks could indicate where incorrect or missing values are located or if a route has an invalid geometry. Five Validation Checks are embedded into the LADOTD HPMS application to aid with the validation step of the workflow. These can be located by going to the Validations module and selecting any of the icons contained within the "HPMS Validations" section.

Validation Rules Maintenance

The Validation Rules Maintenance interface is an important element of the validations step of the HPMS workflow. This interface outlines the parameters of certain data items, implementing rules that will trigger errors if these item types do not comply. Users can locate this interface by following the steps below. The user can confirm that they are in the correct location by looking at the top of the interface (on the last step) to view the title.

LA HPMS Validation Rules Maintenance.png

The rules for Import, Cross, and Coverage validations are found in this interface. To fill the interface with information from a specific rule, the user can select the desired category in the “Validation Rules Type” picklist at the top of the interface. Then, the Validation Rules List table will be populated with the rules pertaining to that type.

Edit a Rule

In order to edit a rule, the user must locate the "Edit Rules" interface on the Edit tab. In this interface, the user must first select the rule type they wish to edit (Import, Coverage, or Cross) from the picklist at the top of the Validation Rules Maintenance Interface. Then, the user can follow the steps below. Most steps will be associated with a table number (first, second, third, or fourth) which corresponds to the table placement as it is listed on the interface.

(1) Select a data item in the Data Item column (First Table).

(2) Edit the failure message by clicking into the textbox and adding a message. If an HPMS Data Item does not have a rule for the selected Rule Type, the failure message will appear blank (First Table).

(3) After selecting a data item, use the Validation Rules Definition table to add a criterion by clicking the “+” button on the lefthand side of the table. The plus sign will be located on the "+/-" column on the last, empty row (Second Table).

(4) Use the Left Condition table to edit the Left Condition column in the Validation Rule Definition table (Third Table).

NOTE: The user can utilize the Left Condition table to select a Condition Type in the Type column (Data Item, Value, and Overlay Column), edit a Condition Value (picklist or textbox), add an arithmetic operation in the Arithmetic column (operation between 2+ conditions), add a condition (left “+” button), and remove a condition (left “X“ button).

(5) Use the Right Condition table to edit the Right Condition column in the Validation Rule Definition table (Fourth Table).

NOTE: The user can utilize the Right Condition table to select a Condition Type in the Type column (Data Item, Value, Code list, and Overlay Column), edit a Condition Value (picklist or textbox), add an arithmetic operation in the Arithmetic column (operation between 2+ conditions), add a condition (left “+” button), and remove a condition (left “X“ button).

(6) Use the Join and Parentheses options to group or create condition rule criteria (Second Table).

(7) Use the Validation Rule Definition table to delete a criterion if desired (Second Table).

NOTE: The user can delete a criterion by clicking the “X” button on the lefthand side of the table.

(8) After editing the desired rule, click the “Save Changes” button.

Add New & Delete Rules

To add a new validation rule, click the “Add Rule” link, then follow the steps above to edit the new rule. To delete a validation rule, check the checkbox to the left of the desired rule. After selecting the desired rules, click the “Delete All Selected” link. Click the “Save Changes” button to save changes.

Validation Checks

As specified on the Validations article, users can find missing and/or invalid values for a selected data table by utilizing Validation Checks. There are five Validation Checks in the LADOTD HPMS application:

Icon	Name	Description
	Route/LRS	Use this interface to run route ID, geometry, and measure validations.
	Sample Sections and TOPS	Use this interface to run validations for Sample Sections and TOPS items.
	Import	Use this interface to run import validations for the HPMS Data Items.
	Cross	Use this interface to run cross validations for the HPMS Data Items.
	Coverage	Use this interface to run coverage validations for the HPMS Data Items.

Route/LRS Validation Check

The Route/LRS interface provides options to validate route ID, geometry, and measure conformity. These validations use the R&H data source defined in the data table to identify Route ID and LRS data quality issues, such as duplicate Route IDs and measures. To access the Route/LRS Validations interface, users can select the Route/LRS icon in the Validations tab. To run a Route/LRS validation report:

Click the Validations tab on the main interface, then select the first icon on this ribbon, "Route/LRS." This leads to a pop-up window.
Select a “Reference Network” by clicking the designated circle, either Statewide Routes or LRS ID Routes, to use to perform the validation checks.
Select "Validations to Run" by checking the checkboxes to the left of the desired validation or by clicking the “Select All” hyperlink if the user wishes to view all validations.
Click the “Open as PDF” button to open the report in PDF format or the “Open as Excel” button to open the report in Excel format.

Each resulting report will contain the following columns:

Column	Description
Route ID	The route location of the segment.
From Measure	The beginning point of the segment.
To Measure	The ending point of the segment.
Data Values	The data values for the failed validation checks.
Failed Validation	The validation type that failed.

Sample Sections and TOPS Validation Check

The Sample Sections and TOPS Validations interface provides options to validate samples and TOPS items (Functional System, Urban Code, Facility Type, Through Lanes, and AADT). To access this interface, users can select the Sample Sections and TOPS menu item in the Validations tab. To run a Samples Sections and TOPS validation report:

Select the “Specific Location” bubble under the "Select the location(s) to check" header and fill out the associated filters (picklists/textbox) to run the validation checks on a subset of locations; the user can also select the “Statewide” bubble instead to run the checks on the full extent of data.
Select the desired validation by clicking on its name in the “Select the validation to run” section. Only one validation can be run at a time.
Click the “Open as PDF” button to open the report in PDF format or the “Open Report Window” button to open the report in a new pop-up window. Report Windows offer additional functionality, such as mapping the results or opening the results in Excel Format.

Each report will contain the following columns:

Column	Description
Sample ID	The Sample Section ID of the segment.
Parish	The Parish location of the segment.
Route ID	The route location of the segment.
From Measure	The beginning point of the segment.
To Measure	The ending point of the segment.
Problem Feature	The feature that failed the validation check.
Data Values	The values of the feature that failed the validation check.
Failed Validation	The failure message of the validation check (configured in the Edit Rules interface).
(Pencil Icon)	The Validation Editing menu icon.

Additional functions are also included at the top of the report:

Function	Description
Map Symbol Color	Picklist of colors to display the results on a map.
Map	Toggles to the Map Frame and highlights the selected records in the selected map symbol color.
Print	Opens the Windows Print Dialog to customize and print the results.
View in Excel	Prompts the user to open the file in Excel or save the results locally in Excel format.

Import/Cross/Coverage Validation Check

While the Import, Cross, and Coverage validation checks are separate checks the user can run, they follow the same pattern for instigation and possess the same report columns; therefore, all three can be discussed simultaneously. The Import, Cross, and Coverage Validation interfaces are used to run the corresponding validations for one or more data items. To access this interface, users can select the Import, Cross, or Coverage Validation icon on the ribbon in the Validation tab. To run an Import, Cross, or Coverage validation report:

Select the “Specific Location” bubble under the "Select the location(s) to check" header and fill out the associated filters (picklists/textbox) to run the validation checks on a subset of locations; the user can also select the “Statewide” bubble instead to run the checks on the full extent of data.
Select data items to include in the validation report. The user can do this by checking the checkboxes located to the left of each desired data item under the "Select the validation(s) to run" header. The “Select All” hyperlink can also be used to select all data items, or the “Select TOPS Data Items” hyperlink to select all TOPS data items if available.
Click the “Open as PDF” button to open the report in PDF format or the “Open Report Window” button to open the report in a new popup window. Report Windows offer additional functionality, such as mapping the results or opening the results in Excel Format.

All resulting Import, Cross, and Coverage validation reports will contain the following columns:

Column	Description
Parish	The Parish location of the segment.
Route ID	The route location of the segment.
From Measure	The beginning point of the segment.
To Measure	The ending point of the segment.
Problem Feature	The feature that failed the validation check.
Data Values	The value(s) of the feature that failed the validation check.
Failed Validation	The failure message of the validation check (configured in the Edit Rules interface).
(Pencil Icon)	The Validation Editing menu icon.

Additional functions are also included at the top of the report:

Function	Description
Map Symbol Color	Picklist of colors to display the results on a map.
Map	Toggles to the Map Frame and highlights the selected records in the selected map symbol color.
Print	Opens the Windows Print Dialog to customize and print the results.
View in Excel	Prompts the user to open the file in Excel or save the results locally in Excel format.

Edit Data

One of the main abilities HPMS Manager provides is the ability to edit data in order to address and correct data issues found as a result of Validations. Users can take on this ability through the Validation Edit Menu and Basic Editor. Users can also view and save edits previously applied to the data table through the application. More detailed information is given below in a table format which summarizes the function and icons of both editing interfaces.

Icon	Name	Description
	Validation Edit Menu	Edit data and correct validation errors.
	Basic Editor	Search, create, and update data in the data table.

Validation Edit Menu

During the validation process, the user can edit data and correct validation errors using the Validation Edit Menu. When the user opens the Validation Edit Menu, a window similar to the below will appear.

Open the Interface

In order to open the Validation Edit Menu, the user must follow these steps:

Fill out the appropriate validations check interface (Sample Sections & TOPS, Import, Cross, or Coverage) and select the "Open Report Window" button.
Select the pencil icon () on the desired data item row in the resulting pop-up. Once selected, a window will appear with a table of data items along the route corresponding to the selected rule in the validation report.

There are seven static columns displayed in the Validation Edit Menu table: checkbox selector, validation error (), Parish, Route ID, From Measure, To Measure, Section Length, and Sample ID. The table also contains additional columns for other data items; these columns are determined by the validation report from which the Validation Edit Menu was opened.

Correct Errors

The user can correct validation errors in the Validation Edit Menu table. The steps below will guide you through the correcting process.

Find a row where a caution icon () appears in the Validation Error column or use the “Next” and “Previous” links above the table to navigate to the next or previous validation error.
Hover the cursor over the caution icon () to view a description of the validation error.
Edit data items by clicking into the desired cell. Depending on the item, a picklist or a text field will appear. As updates occur, rows will be checked again for validation errors. If no errors exist for the row, the error icon will be removed. If an error is created for a row, an error icon will appear in the Error Icon column.
After fixing the validation errors, click the “Save Changes” button. To commit changes to the source data, check the “Save data to source” checkbox before saving changes.

NOTE: Currently, the Route ID, From Measure, and To Measure fields are not editable through the Validation Edit Menu. Additionally, adding and deleting a row is disabled at this time.

Basic Editor

The Basic Editor tool, an essential part of the Edit Data step of the workflow, can be accessed through the Edit tab. The user can search for a route using the Select from Map or Enter Route options. After finding the desired route, the user can implement these actions:

Select an Edit Group. Basic Editor contains six static columns (checkbox selector, validation error, Parish, Route ID, From Measure, and To Measure). The Edit Groups picklist can be used to add additional columns to view and edit. If none of the groups listed have the desired columns to add, users can create a new Edit Group by opening the Edit Groups interface.
Map the desired route. On the Basic Editor interface, users can click the “Find” button near the top right of the window to retrieve and map the desired route.
Edit a data item. By clicking into the desired cell, users can edit data items. Depending on the data item, a picklist or textbox will appear in this editable cell. As updates occur, rows will be checked again for validation errors. If a new value fails a validation check, an Error icon will appear in the validation error column. Hovering over the error column will display a description of the error.
Add a row. Users can click the “Add Row” link to add a new row to the Basic Editor table. New rows will appear at the top of the table.
Delete a row. To delete a row, users can check the checkboxes to the left of the desired segments. After selecting the desired segments, the user can click the “Delete Selected Rows” link.

Changes cannot be saved if gaps or overlaps are created by deleting/adding a new row or if any validation errors were created during the editing process.

Query for a Route

There are two ways to query for a route in Basic Editor: (1) Select From Map and (2) Enter Route.

(1) Select From Map

The Select From Map option can be used to open the Basic Editor from a map-selected location. To query for a route using this option, the user can navigate to the Select From Map icon on the Edit module. This icon will be the first on the menu ribbon. Then, the user can use their mouse to zoom to the desired area on the map and click on that location. This will provide them with a list of routes near the clicked location. If the "Select From Map" icon becomes unclicked during this process, it is probably due to efforts to zoom on the map that occurred after clicking this icon; the user can simply reselect this icon to enable it once more. Finally, the user can select the intended route from the list and click the Basic Editor link at the base of the resulting location pop-up box.

(2) Enter Route

The user can also manually enter the desired route’s information. In order to accomplish this, the user must locate the Basic Editor icon on the Edit module. This is the second icon on the menu ribbon, and it rests beside the Select From Map icon. Once the Basic Editor icon is selected, a pop-up window will appear at the base of the map interface. From this pop-up window, the user can select the "Enter Route" button which will trigger the appearance of a new pop-up window. The user must fill the fields in the window that are listed in the table below. When all fields have a value, the user can click the "Select Route" button.

Field	Description
Parish	Used to specify a parish boundary.
System Code	Used to specify a route system.
Route Name	Used to specify a route name.
Direction	Used to specify inventory direction.
Feature Type	Used to specify feature type.
Sequence number	Used to specify sequence number.

Edit Groups

The Edit Groups interface is used to create, save, or delete groupings of columns designated for editing. The Basic Editor uses Edit Groups to add additional columns for viewing and editing in its interface. The Edit Groups interface can be accessed in two ways. For one, users can navigate to the Edit tab; under the Management section on the menu ribbon, the "Edit Groups" icon can be found and selected. Alternatively, users can click the “Select Columns…” option in the Edit Group picklist in the Basic Editor interface. To find the Basic Editor interface, the user can go to the Edit tab and select the "Basic Editor" icon under the Data Editing section.

To edit or create groups, users can follow these six steps once they are in the Edit Groups interface:

Select a value in the "Edit Group" picklist to edit an existing group or click the "Add New" button to create a new group.
Use the "+" and "-" buttons on the left side of the "Available Columns" box to find the desired data items. When the interface shows a plus sign, the data items for each major category are hidden; when the interface shows a minus sign, the data items are expanded on the interface.
To add data items to the "Selected Columns" table, click on a data item to select it. Then, click the "Add >" button. To quickly add TOPS items, click the "Select TOPS" link.
To remove data items from the “Selected Columns table, click on the data items to select them. Then, click the "< Remove" button. To remove all data items, click the "<< Remove All" button. To quickly remove TOPS Items, click the "Deselect TOPS" link.
Edit the name in the "Group Name" textbox if needed.
After adding the desired data items/columns, click the "Save Changes" button. The Edit Groups interface requires at least one column and a name in order to save.

Data Cleaning Icons

The Data Cleaning section of the Edit tab provides tools to fix issues found in the Roads and Highways events, such as gaps in the route segments or measure offsets that exist between data items. The following interfaces are provided to assist in fixing events:

Icon	Name	Used to Find and Fix...
	Fix Event Gaps	Roads and Highways events
	Snap Events to Route	Measure offsets between routes and events
	Fix Event Offsets	Measure offsets between events
	Fix Event Overlaps	Overlapping events

Fix Event Gaps

The Fix Event Gaps interface is used to find and fix gaps that exist in the source data of a Roads and Highways event. Users can open the Fix Event Gaps interface by selecting the icon on the Data Cleaning section of the Edit menu. Once the user has entered this interface, they will have the ability to locate and correct the apparent gaps by following these steps:

Fill in all filters (Event, Statewide/Parish, System Types, and Route Types) to find gaps within the specified parameters.
After filling all filters, click the “Find Gaps” button to the right of the filters. The table on the lower half of the interface will then update to reflect the gaps found in the event data.
Resolve gaps in the table by clicking into a cell under the event column and filling in an appropriate value.
After resolving the desired segments, click the “Save Changes” button at the bottom of the interface to update the data table. To update the source data, check the “Save data to source” before saving changes.

Snap Events to Route

The Snap Events to Route interface is used to find and fix micro gaps or overlaps that exist between a Roads and Highways event and the ends of routes. When changes are saved, edits are automatically applied to the R&H source event data defined by the information in the selected data table. Users can open the Snap Events to Route interface by selecting the icon in the Data Cleaning section on the Edit menu. Once the user has entered this interface, they will have the ability to locate and correct the apparent micro gaps/overlaps by following these steps:

Fill in all filters (Event, System Types, and Route Types) to find offsets within the specified parameters.
After filling all filters, click the “Find Events” button to the right of the filters. The table on the lower half of the interface will then update to reflect the offsets found between events and routes.
Snap events to the route endpoints by selecting the checkbox on the desired row.
After selecting the desired segments, click the “Save Changes” button at the bottom of the interface to update the data.

Fix Event Offsets

The Fix Event Offsets interface is used to find measure offsets that exist between data items. Users can open the Fix Event Offsets interface by selecting the icon in the Data Cleaning section on the Edit menu. Once the user has entered this interface, they will have the ability to locate and correct the measure offsets by following these steps:

Fill in all filters (Statewide/Parish, Event to Fix, Event to Compare, and Tolerance) to find offsets within the specified parameters.
After filling all filters, click the “Find Offsets” button to the right of the filters. The table on the lower half of the interface will then update to reflect measure differences between the selected event and the controlled event. The measures of the “Event to Fix” item will appear in bold if they do not match the “Event to Compare” measures.
Update measures by checking the checkbox in the first column of the table. By checking the checkbox, the "Event to Fix" measures will be updated to reflect the corresponding "Event to Compare" measures once Save Changes is selected.
After selecting the desired segments, click the “Save Changes” button at the bottom of the interface to update the measures. To save the updates to the source data, check the “Save data to source” checkbox before saving changes.

Fix Event Overlaps

The Fix Event Overlaps interface is used to find and fix overlaps that exist within a Roads and Highways event. When changes are saved, edits are automatically applied to the R&H source event data defined by the information in the selected data table. Users can open the Fix Event Overlaps interface by selecting the icon in the Data Cleaning section on the Edit menu. Once the user has entered this interface, they will have the ability to locate and correct the overlaps by following these steps:

Fill all filters (Event, System Types, and Route Types) to find gaps within the specified parameters.
After filling all filters, click the “Find Overlaps” button to the right of the filters. The table on the lower half of the interface will then update to reflect the overlaps found in the event data.
Resolve overlaps in the table by clicking on the “Edit Source” link on the desired row. This will open the source event data for the selected segment.
Edit the source by clicking into the desired cell. A picklist or textbox will appear relative to the column which will grant the user editing capabilities. Delete segments by checking the checkbox in the first column of the table, then click the “Delete Selected Rows” link.
After resolving the overlaps, click the “Save Changes” button at the bottom of the interface to update the source data.

Edit Log

The Edit Log interface provides a viewable history of the changes made to each data table. To open the Edit Log interface, the user must select the icon on the Management section of the Edit tab. Once the user has entered this interface, they can view the changes by following these steps:

Select the desired data table using the Data Table picklist. This picklist will simply be labeled "Data" on the interface.
Apply the desired filters (Refresh Date, User, Data Item, Parish, System Code, and Route Name).
Click the “Filter” button to the right of the filters to apply the chosen options. The table in the lower portion of the interface will then update to reflect the new filters.
Click the “Retrieve Next 20,000 Records” link to view the next 20,000 edits or click the “Retrieve Previous 20,000 Records” link to view the previous 20,000 edits.
Click the “Open as PDF” button at the base of the interface to view the results in PDF format or the “Open in Excel” button to view the results in Excel format.

Save Data to Source

The Save Data to Source interface provides the option to save data edits made to a data table back to the source data. If edits made in the Validation Edit Menu and Basic Editor failed to save to the source data, another attempt can be made in this interface. The user can open the Save Data to Source interface by selecting the icon in the Management section of the Edit tab. Once the user has entered this interface, they can locate and save edits by following these steps:

Select the desired data table in the Data Table picklist. This picklist will simply be labeled "Data" on the interface.
Apply the desired filters (User, Data Item, Parish, System Code, Route Name, Show Import Edits, Only show edits user can save to source, and R&H Radio Buttons).
Click the “Filter” button to the right of the filters to apply the chosen options.
To save edits to the source data, select the desired rows by clicking the checkbox in the first column or select all rows by clicking the checkbox in the table header.
After selecting the desired rows, click the “Save Data to Source” button at the base of the interface.

Sample Adequacy

The Sample Adequacy tab is used to identify and create potential samples, as well as manage existing ones. This tab is the sole focus of the fifth step of the workflow which allows the user to verify that the data is adequately sampled and to address issues of over or under sampling. HPMS Manager offers seven interfaces to assist in reporting samples.

Icon	Name	Used To...
	Create TOPS	Create a Table of Potential Samples (TOPS) based on the data in a HPMS Data Table. All other interfaces in the Sample Adequacy tab cannot be used until this step is performed.
	Adjust TOPS	Merge small segments together based on TOPS items.
	Check Adequacy	View the number of unsampled TOPS sections, required samples, and current samples for each Sample Panel (Functional System, Volume Group, & Urban Area stratum).
	Potential Samples	Identify and add samples to the Sample Panel.
	Expansion Factors	Calculate and view expansion factors for Sample Panels.
	Sample Risk Analysis	Review current Samples Panels for samples that are at risk of moving to a higher or lower volume group.
	Delete Samples	Review and remove samples from the Sample Panel.

There is one additional icon on the Sample Adequacy tab; this icon is the sole item in the Maintenance section. It is:

Icon	Name	Used To...
	Precision Level	View and update the confidence level and precision rate of each Functional System and Urban Code combination.

Create TOPs

The user must generate a Table of Potential Samples (TOPS) data set using the Create TOPS interface before creating and managing samples in other interfaces. This tab primarily functions as a means to break down records and categorize them into Sample Panels/Stratums, which are defined by Volume Group, Functional System, and Urban Code. The user can open this essential interface by selecting the icon in the Sample Adequacy tab. To Create a TOPS data set or sample table, the user can follow these steps:

Select the desired data table year in the “Create TOPS for Year” dropdown. After selecting a year, the “using Data” dropdown to its direct right will be populated with Data Tables related to that year.
Select the desired data table in the “using Data” dropdown.
After selecting both items, click the “Create TOPS” button.

The samples table that is generated will possess the TOPS data items, including Functional System, Facility Type, Urban Code, AADT, Through Lanes for all Federal-aid highways, and all other public roads not classified as local roads or rural minor collectors. If edits are made outside of the Sample Adequacy tab, such as in Basic Editor or the Validation Edit Menu, this process will need to be ran again to have the latest data present.

Adjust TOPs

After using the Create TOPS interface, the user can move on to utilize other interfaces in the Sample Adequacy tab. The Adjust TOPS icon () directly follows the Create TOPS icon on the menu ribbon. This interface is used to find small segments where TOPS data items do not align at exact measures and merge them. In order to accomplish this goal, the interface possesses three action tabs: Summary, Detail, and Changes.

Summary Tab

The Summary tab is used to identify small segments, with a maximum length specified by the user, where TOPS data items do not align at exact measures and merge them. To find the small segments, users can follow these steps:

Select an option in the "Data to Adjust" bubble selection area. Select “Statewide” to locate small segments in the full TOPS data set or “Parish” to locate small segments in a subset of data based on the selected Parish in the picklist.
Set the data item precedence by selecting the order for obtaining attribute values in the "Parent TOPS Data Item Precedence" list. This will determine how small segments will be merged into adjacent segments. To change the order, click the desired data item and use the up or down arrows.
Enter a maximum segment length, or measure tolerance, in the “Measure Tolerance” text box. The measure tolerance can be in units of feet or miles which is selected in the picklist.
After giving the desired options a value, click the “View TOPS Changes” button.

After running the changes, the “TOPS Changes Summary” section of the interface will display the overall number of required sample changes from the original TOPS data and the modified TOPS data based on the length. There are three view-only textboxes and a table in this portion. The “Total Samples Required Before Changes” textbox shows the original, overall number of samples. The “Total Samples Required After Changes” textbox shows the overall number of samples that would need to be reported if the small segments were merged. The “Difference in Samples Required” textbox shows the numerical difference in the original and modified TOPS data. The “Stratums with Required Sample Changes” table below the textboxes breaks down this difference value and shows which stratums would be affected by the changes. These numbers can appear negative, indicating less required samples, or positive, indicating the stratum grew to require more samples.

Detail Tab

The Details Tab is used to compare the number of TOPS locations and required samples from the original TOPS set against the modified TOPS set per Functional System, Urban Code, and Volume Group stratum.

Rows

When the rows of the table are collapsed ( caret), they will only show general information about the Functional Systems and their changes. In this state, the rows will simply state "[#] Urban Areas with changes to Number of TOPS/Required Samples" across from the associated Functional System title. However, the rows can expand to reveal the specific Urban Area entries and their changes if the user clicks the caret.

In the expanded state, the first row of numbers in the Urban Area entry contains the original TOPS set, and the second rows contains the modified TOPS set. If a number is shown in blue in the second row, this indicates that a change has occurred in the number of TOPS locations. If a number is shown in purple, this indicates that a change has occurred in the number of samples required per volume group.

Changes Tab

The Changes tab is used to identify where the five TOPS data items do not align at exact measures and what their new values will be if the modified data set is saved. The table contains the TOPS data item, Route ID, adjusted measures (from/to), original measures (from/to), old value, and adjusted value columns. The modified measures will appear in bold in either the “Adjust From Measure” or “Adjust To Measure” column depending on which measure needs to be updated.

Saving Adjust TOPS

The modified data set can be saved on any of the three tabs (Summary, Detail, or Changes). In order to save the updated data, the user must select the "Update TOPS" button at the base of the interface. This selection will update the data in the samples/TOPS tables and the selected data table. The user can also commit the modified data to the original source by selecting the "Save to Source" checkbox before clicking "Update TOPS."

Check Adequacy

After using the Create TOPS interface, the user can move on to utilize other interfaces in the Sample Adequacy tab. Check Adequacy () is one available sample interface. This interface is used to view the new number of unsampled TOPS, required samples, and current samples for each stratum (Functional System, Volume Group, and Urban Code grouping). This allows users to quickly identify stratums that do not meet the sample adequacy requirements. The table below describes the functions of the Table Elements in the Check Adequacy interface.

Table Element	Description
Second Column	Displays the precision level (confidence level – precision rate) used to calculate the number of required samples. These values can be edited in the Precision Level interface in the Sample Adequacy tab.
Third Column	Displays a caution symbol or green check mark.
Caution Symbol	Indicates that a stratum has an insufficient number of samples.
Adjacent Number (to Caution Symbol)	Denotes how many stratums are deficient.
Carets	Allows users to expand or collapse the stratum data.

Cell Information

Each cell under the Volume Group section contains three numbers:

The number of unsampled TOPS Sections -- the number of TOPS locations that do not have a Sample ID for the stratum.
The number of required samples -- the number of samples needed for this sample stratum, calculated using FHWA’s Sample Size Estimation equation.
The number of provided samples -- the number of TOPS locations that do have a Sample ID for the stratum.

The first number will appear as a link that opens the Potential Samples interface on the Sample Adequacy tab. This allows the users to easily add samples to a stratum with an insufficient number of samples (denoted by the third number in a cell being red). Below is a visual that shows each number type and style on a sample Volume Group cell.

Potential Samples

After using the Create TOPS interface, the user can move on to utilize other interfaces in the Sample Adequacy tab. Potential Samples () is one available sample interface. This interface is used to add samples to meet FHWA requirements.

Filters -- Top Filters

The user can search by stratum on the Potential Samples interface through the Volume Group, Functional System, and Urban Code filters at the top of the Potential Samples interface. After selecting values for the filters, the user can click the “Find Now” button to have a list of segments appear in the table. The resulting segments include unsampled TOPS locations and existing sample sections.

When accessing Potential Samples through Check Adequacy or Expansion Factors, the filters will be pre-populated to reflect the selected stratum. Check Adequacy will connect to this interface through the linked, first number on each cell.

Filters -- Data Completeness Filters

Data Completeness provides additional filters in this interface. This portion contains two checkboxes, a textbox, and a link that all help with narrowing the information on the table.

Filters -- Potential Sample Table

The Potential Sample Table will be populated with TOPS sections within the specified Volume Group, Functional System, and Urban Code selected. Users can add samples in two ways: manual and random selection.

Manually Add Samples

To manually add samples, follow the steps listed below:

Check the checkbox in the first column on the desired segment.
- Checkboxes will not be present for segments already designated as samples.
- Segments that appear red in the table do not meet AADT criteria specified in the Data Completeness section.
- Segments that appear orange in the table do not meet segment length restrictions set by the FHWA.
- The “Completeness” column can be used to find the segments with the most amount of data items that exist on a segment. The number in this column specifies how many data items exist (1st number) versus (/) the total amount of data items in the selected data table (2nd number). Clicking on the completeness field will display a popup showing a list of data items that exist.
Add a new sample ID by clicking the Samples column and entering a value in the textbox.
- If no sample ID is provided before saving, one will be generated automatically based on the current year and zero-padded to support a 12-digit format.
After selecting all desired segments, click the “Add Samples” button to add the new samples to the samples table and data table.
- To apply changes to the data source, check the “Save to Source” checkbox before clicking “Add Samples.”

Randomly Add Samples

To randomly select samples, follow the steps listed below:

Click the “Random Select” button to open the Random Samples interface.
Specify the number of samples to be created by entering a value in the “Number to Randomly Select” textbox.
Check the “Exclude Segments not meeting AADT criteria” and “Exclude Segments not meeting length restrictions” checkboxes if desired.
- Check the “Exclude Segments not meeting AADT criteria” checkbox to prevent from randomly selecting a sample that does meet the criteria specified in the Potential Samples Data Completeness section. The checkbox will be disabled in this interface if the “AADT not within…” checkbox is not checked in the Data Completeness section.
- Check the “Exclude Segments not meeting length restrictions” checkbox to prevent samples from being randomly selected that do not meet length restrictions set by the FHWA.
After all desired parameters have been set, click the “Select Samples” button to randomly select the provided number of samples.
- These samples will be given a generated sample ID based on the current year and zero-padded to support a 12-digit format.
Finish adding the samples to the sample table and data table by clicking the “Add Samples” button on the Potential Samples interface.
- To apply changes to the data source, check the “Save to Source” checkbox before clicking “Add Samples.”

Sample Table

Below the data table, in the "Sample Table" section, the number of required samples, existing samples, samples that are needed to meet requirements, and total samples can be found. The number of selected samples and total number of samples will increase or decrease by selecting segments to sample using either method above.

Expansion Factors

After using the Create TOPS interface, the user can move on to utilize other interfaces in the Sample Adequacy tab. Users can check if a stratum is under-sampled by using the Expansion Factors interface. The interface calculates this by dividing the total length of a particular stratum by the total length of sample segments in a stratum. If the number exceeds a maximum of one hundred, the number will appear red to show the stratum is under-sampled. In order to take these actions, the user can locate the icon on the Sample Adequacy tab and section.

The Expansion Factors interface has certain elements which allow actions and provide information to the user. These elements are:

Element	Function
Calculate Expansion Factors button	Generates the calculation of the expansion factors.
Caret ()	Expands or collapses stratums.
Caution icon ()	Notifies the user of any expansion factors that exceed the recommended upper bound; displayed in the second column of the table.
Links (ex. )	Indicates the expansion factors that exceed the recommended upper boundary; opens the Potential Samples interface.

Sample Risk Analysis

After using the Create TOPS interface, the user can move on to utilize other interfaces in the Sample Adequacy tab. The Sample Risk Analysis is one available interface. If a stratum is oversampled, retaining a surplus could be warranted if a stratum is at risk of losing multiple samples. The Sample Risk interface helps determine if a stratum has potential to lose samples by showing which samples are at risk of migrating to a lower or higher range volume group. In order to open this interface, the user can locate the icon on the Sample Adequacy tab and section.

Risk Analysis Parameters

In the Risk Analysis Parameters section, users can set a percentage to identify samples within a certain range of the upper or lower bounds of a Volume Group. This field is required to perform an analysis.

Optional Filters

Two optional filters are available to narrow the results. Both of these filters are located directly below the Risk Analysis Parameters.

The ability to filter stratums that do not have a certain percentage of at-risk samples. To apply this filter, check the “% of the Number of Required Samples” checkbox, select a query operator (>, <, >=, <=, or =) in the dropdown, and specify a percentage in the textbox.
The ability to filter stratums that do not have a certain number of at-risk samples. To apply this filter, check the “Show Stratums At Risk Samples” checkbox, select a query operator (>, <, >=, <=, or =) in the dropdown, and specify an amount in the textbox.

Tables

After the required Risk Analysis Parameter and optional filters are set, the user can select the "Perform Analysis" button. This will populate the table below the parameters and filters, called the Sample Risk Stratum Table, with information based on the parameters specified. Then, the user can select a row in this table to populate the Sample Risk Detail Table. This table will be titled, Sample [Urban Code/ FSystem/ Volume Group]. Any samples at risk of leaving will appear in red.

Delete Samples

The Delete Samples interface can be used to reduce over-populating or to relocate a sample by deleting it in this interface and adding it back in Potential Samples. After using Check Adequacy to check if a sample stratum is oversampled, the user can utilize the Delete Samples interface to delete such stratums. If the number of provided samples is significantly more than the number of required samples in the Check Adequacy table, the stratum may be oversampled, and samples might need to be deleted. The Delete Samples interface can be accessed by selecting the Sample Adequacy tab. This interface is marked by a purple trashcan icon (), and it is the last icon in the Sample Adequacy section. To delete a sample, follow these steps:

Select the desired data table year in the “Year” picklist.
Select the desired “Data” table to use in the Data picklist.
Click the “Find Samples” button to find all sampled segments in a data table.
Click the “Save Changes” button to save changes to the selected sample and data table. To save changes back to the source data, the “Save to Source” checkbox needs to be selected before clicking the “Save Changes” button.

If a stratum contains three segments or fewer, the FHWA requires all segments to be sampled. It is not advised to delete a sample in a stratum with three or less segments.

Precision Level

The Precision Level interface () is used to view and update the confidence level and precision rate of each Functional System and Urban Code combination. It plays a very important role, for its data is used to calculate the number of required samples per stratum on the Check Adequacy and Adjust TOPS interfaces. The Precision Level interface can be accessed on the Sample Adequacy tab; it is the only icon under the Maintenance section. To edit a confidence level or precision rate, the user can follow these steps:

Click into the desired cell.
Edit the resulting textbox.
Click the “Save Changes” button.

Standard Reports

One of the last items to check before submitting data to the FHWA is mileage. The LADOTD HPMS Manager aids this last check by constructing preconfigured reports that list mileage in different ways. These preconfigured reports can be accessed by selecting the Reports tab. Once selected, three icons will appear: HPMS, Advanced, and HPMS Report Status. To access the Standard Reports, or preconfigured reports, the user can select the HPMS icon (outlined in red below).

Then, the user will be able to select one of the available preconfigured reports:

Report	Lists the...
Certified Mileage by County	Mileage for Interstate, State, Local, and other routes, grouped by County.
Certified Mileage by County - Detailed	Mileage for Interstate, State, Local, and other routes, grouped by County, along with each route that is included in the group and the associated mileage.
Consistency Report	Length (in miles) of AADT, Through Lanes, Ownership, and Control, grouped by F_System.
Extent and Travel – Interstate by Route Number	Miles, Lane Miles, and Vehicle Miles for each Interstate route.
Extent and Travel – Interstate by Route Number (Comparison)	Miles, Lane Miles, and Vehicle Miles for each Interstate route for 2 years. Includes the percent change for Miles, Lane Miles, and Vehicle Miles.
Extent and Travel – Statewide Summary	Miles, Lane Miles, and Vehicle Miles by Small Urban, Rural, All Urbanized, and All Urban areas, grouped by Urban Code and F_System.
Extent and Travel – Statewide Summary (Comparison)	Miles, Lane Miles, and Vehicle Miles by Small Urban, Rural, All Urbanized, and All Urban areas, grouped by Urban Code and F_System for 2 years. Includes the percent change for Miles, Lane Miles, and Vehicle Miles.
Extent and Travel – Urbanized Summary	Miles, Lane Miles, and Vehicle Miles for each Urban Code, grouped by Urban Code and F_System.
Extent and Travel – Urbanized Summary (Comparison)	Miles, Lane Miles, and Vehicle Miles for each Urban Code, grouped by Urban Code and F_System for 2 years. Includes the percent change for Miles, Lane Miles, and Vehicle Miles.
Extent and Travel on the NHS	Miles, Lane Miles, and Vehicle Miles for each NHS type, grouped by NHS and F_System.
Extent and Travel on the NHS (Comparison)	Miles, Lane Miles, and Vehicle Miles for each NHS type, grouped by NHS and F_System for 2 years. Includes the percent change for Miles, Lane Miles, and Vehicle Miles.
Ownership Report	Mileage for each Ownership value, grouped by Ownership and F_System.

To create a Standard Report, the user can follow the steps below after entering the HPMS interface on the Reports tab.

Select a data table to retrieve mileage from the "Data" picklist.
Select the desired report by clicking on the report name in the "Select the Report" section.
Apply the desired filters: Parish, Roadway Type, and Number of Lanes (if applicable).
Click the “Open as PDF” button to open the report in PDF format or the “Open in Excel” button to open the report in Excel format.

Submittals

The last step of the HPMS process is submittals. After collecting and validating the data, the Submittals tab allows the user to generate submittal and summary files for submission to FHWA. The Submittal tab provides the following tools to create submittal and summary files:

Icon	Name	Use To...
	ARNOLD Segments	Generate route network output.
	Road Segments	Create files for the HPMS Submittal process.
	Sample Limits	Generate a text file of Samples Locations.
	County	Edit and export county summary data.
	Non-Federal Aid	Edit and export non-federal aid summary data.
	Road Event Collection	Update and create files for the HPMS Submittal process.
	Road Estimates	Generate a text file of Samples Locations.

ARNOLD Segments

The ARNOLD Segments interface provides options to generate Route outputs in Shapefile, File Geodatabase, or text file format. The ARNOLD Segments interface () can be located by selecting the Submittals tab and navigating to the first section-- Section Files. The ARNOLD Segments interface is the first icon in this section and the first on the Submittals menu. To create an ARNOLD Segments submittal file, follow these steps:

Select a data table in the "Data Table" picklist.
Select a file type: Shapefile, File Geodatabase, and Text File.
Select a route type in the "Generate Files By" section.
- If the user selects the “Route Type” option, they can choose from the four checkboxes-- Interstate, US Route, State Route, or Local-- to clarify the desired route (multi-select allowed).
After selecting the desired options, click the “Export Data” button.

Road Segments

The Road Segments interface provides options to create one or more section files for the various data items. The Road Segments interface () can be located by selecting the Submittals tab and navigating to the first section-- Section Files. The Road Segments interface is the second icon in this section and the second on the Submittals menu. To create section files, follow these steps:

Select a data table in the "Data Table" picklist.
Fill out the information in the "File Creation" section.
- Select an output File Type: CSV or Text.
- Select what type of files to generate: Create Individual Files or Create One File.
  - Create Individual Files (in zipped file) – Used to create individual section files based on the grouping specified in the "Group Files By" picklist (Route Type/Route, Data Item, or Route Type and Data Item).
  - Create One File – Used to create one section file containing the data for all selected data items.
- Select a Reference Network: Statewide Routes or LRS ID Routes.
- Select the optional checkboxes if desired.
  - Exclude Nulls – Used to exclude sections where a data item does not exist from the generated section file.
  - Break on sample sections – Used to split output segments data where samples exist.
Select either the Road Designations, Road Events, or Road Identifications tab.
- Road Designation tab – filter by route type and the five FHWA designated road designation data items.
- Road Events tab – filter by route type and the remaining FHWA designated data items.
- Road Identifications – filter by specific data items (Alternative Route Name, Route Number, Route Qualifier, and Route Signing).
Fill out either the Routes or Data Items section under the selected tab.
- If the user chooses to fill out the Route section, they must first select an option in the picklist: Route Type or Select Route(s).
  - If Route Type is selected, the user must then select one or more checkbox manually or by clicking the "Select All" link.
  - If Select Route(s) is selected, the user must enter a complete Route LRS (Parish, System Code, Route Name, Direction, and Feature Type), then select "Add Route >". Multiple routes can be added.
- If the user chooses to fill out the Data Items section, they must select one or more checkbox manually or through one of the "Select All" links.
  - The "Select All" link will check all checkboxes. The "Select All TOPS Data Items" link will only check the TOPS items.
  - If this section contains any grayed-out items, this indicates that those data items are not in the selected data table.
- While both sections can be filled to create section files, only one section is required to be filled. If a route/route type is selected with no specified data item, all data items will appear in the file. If a data item is selected with no specified route type, all route types will appear in the file.
Click the "Create Section File(s)" button to generate section files.

Sample Limits

The Sample Limits interface provides options to generate a text file of sample locations. This interface can be used to report all sample locations, or a subset based on the selected route type. The Sample Limits interface () can be located by selecting the Submittals tab and navigating to the first section-- Section Files. The Sample Limits interface is the third/last icon in this section and the third on the Submittals menu. To create a file in the interface, follow these steps:

Select a data table in the "Data Table" dropdown.
Select a Reference Network to use.
Select "All Samples" or a route type(s) in the "Generate Files By" section.
Select the "Create File(s)" button located at the bottom of the interface.

The resulting Sample Limits file will include the following header columns: BeginDate, StateID, RouteID, BeginPoint, EndPoint, SampleID, and Comments.

County

The County interface provides options to import, recalculate, edit, export, and generate county summary data. The County interface () can be located by selecting the Submittals tab and navigating to the second section-- Summary Files. The County interface is the first icon in this section and the fourth on the Submittals menu.

Import a File

The user can populate the County Summaries table by importing a file or recalculating the data. To import a county summary file, follow these steps:

Click the "Choose File" button at the bottom left of the interface.
Select a file to import.
- To import a file, it must have the following header columns: BeginDate, StateID, CountyID, FSystem, UrbanID, Ownership, SystemLength, and Comments.
After selecting the desired file, click the "Open" button.

Recalculate Data

The user can populate the County Summaries table by importing a file or recalculating the data. To recalculate the data, follow these steps:

Select a data table in the "Data Table" picklist.
- The recalculate process uses the data table to retrieve routes that classify as rural minor collectors and local roads for each urbanized area and rural areas.
Click the “Recalculate” button.
If the new values are sufficient, click the "Save Changes" button to save the new values.

Edit Data

The first column in the interface table-- Override-- is available to initiate the editing process for the desired record. To fully edit a record, follow these steps:

Select the checkbox in the "Override" column for the desired record or click on a record that has been previously overridden.
Once selected, a textbox will appear in the System_Length and Comments columns to allow edits.
After entering the desired changes, click the "Save Changes" button.

Overridden records will not be recalculated or be overwritten by the import process.

Export Data

To export the county summary table, the user can click the "Export to Pipe Delimited File" link located at the bottom right of the interface. The file will be in a text file in pipe delimited format and will contain the following header columns: BeginDate, StateID, CountyID, FSystem, UrbanID, Ownership, SystemLength, and Comments.

Non-Federal Aid

The Non-Federal Aid Summaries interface provides options to import, edit, export, and recalculate non-federal aid summary data. The Non-Federal Aid interface () can be located by selecting the Submittals tab and navigating to the second section-- Summary Files. The Non-Federal Aid interface is the second/last icon in this section and the fifth on the Submittals menu.

Import a File

The user can populate the Non-Federal Aid Summaries table by importing a file or recalculating the data. To import a non-federal aid summary file, follow these steps:

Click the "Choose File" button at the bottom left of the interface.
Select a file to import.
- To import the file, it must have the following header columns: BeginDate, StateID, FSystem, UrbanID, VMT, and Comments.
After selecting the desired file, click the "Open" button.

Recalculate Data

The user can populate the Non-Federal Aid Summaries table by importing a file or recalculating the data. To recalculate the data, follow these steps:

Select a data table in the "Data Table" picklist.
- The recalculate process uses the data table to retrieve routes that classify as rural minor collectors and local roads for each urbanized area and rural areas.
Click the "Recalculate" button.
If the new values are sufficient, click the "Save Changes" button to save the new values.

Edit Data

The first column in the interface table-- Override-- is available to initiate the editing process for the desired record. To fully edit a record, follow these steps:

Select the checkbox in the "Override" column for the desired record or click on a record that has been previously overridden.
Once selected, a textbox will appear in the Local VMT and Comments columns to allow edits.
After entering the desired changes, click the "Save Changes" button.

Overridden records will not be recalculated or be overridden by the import process. The user can also edit the Rural Local AADT, Rural Minor Collector AADT, and Small Urban Local AADT values in this interface by following these steps:

Click into the corresponding textbox located in the Summarized AADTs section (Rural Local AADT, Rural Minor Collector AADT, or Small Urban Local AADT).
Edit the value by typing into the textbox.
Click the "Save Changes" button.

Export

To export the non-federal aid summary table, the user can click the "Export to Pipe Delimited File" link located at the bottom right of the interface. The file will be in a text file in pipe delimited format and will contain the following headers: BeginDate, StateID, FSystem, UrbanID, VMT, and Comments.

Road Event Collection

The Road Event Collection interface provides options to view, import, export, and edit data collection metadata. The Road Event Collection interface () can be located by selecting the Submittals tab and navigating to the third section-- Catalog Files. The Road Event Collection interface is the first icon in this section and the sixth on the Submittals menu.

Import a File

To import a Road Event Collection Methods file, follow these steps:

Click the "Choose File" button at the bottom left of the interface.
Select a file to import.
- To import a file, it must have the following header columns: BeginDate, StateID, MetadataType, FSystem, IsUrban, IsStateOwned, ValueNumeric, and Comments.
After selecting the desired file, click the "Open" button.

Edit Data

The first column in the interface table-- Override-- is available to initiate the editing process for the desired record. To fully edit a record, follow these steps:

Select the checkbox in the "Override" column for the desired record or click on a record that has been previously overridden.
Depending on the Metadata Type for the selected record, a picklist or textbox will appear, and the Value and Comments columns will become editable.
After entering the desired changes, click the “Save Changes” button.

Export

To export the Road Event Collection Methods table, the user can click the “Export to Pipe Delimited File” link located at the bottom right of the interface. The exported file will be in pipe delimited format and will contain the following header columns: BeginDate, StateID, MetadataType, FSystem, IsUrban, IsStateOwned, ValueNumeric, and Comments.

Road Estimates

The Road Estimates interface provides options to view and edit estimate values. The Road Estimates interface () can be located by selecting the Submittals tab and navigating to the third section-- Catalog Files. The Road Estimates interface is the second/last icon in this section and the seventh on the Submittals menu.

Import a File

To import a Road Estimates file, follow these steps:

Click the "Choose File" button at the bottom left of the interface.
Select a file to import.
- To import a file, it must have the following header columns: BeginDate, StateID, EstimateType, FSystem, IsUrban, IsStateOwned, ValueNumeric, and Comments.
After selecting the desired file, click the "Open" button.

Edit

The first column in the interface table-- Override-- is available to initiate the editing process for the desired record. To fully edit a record, follow these steps:

Select the checkbox in the "Override" column for the desired record or click on a record that has been previously overridden.
Depending on the Estimate Type for the selected record, a picklist or textbox will appear, and the Value and Comments columns will become editable.
After entering in the desired changes, click the "Save Changes" button.

Export

To export the Road Estimates table, the user can click the "Export to Pipe Delimited File" link located at the bottom right of the interface. The exported file will be in pipe delimited format and will contain the following header columns: BeginDate, StateID, EstimateType, FSystem, IsUrban, IsStateOwned, ValueNumeric, and Comments.

HPMS Report Status

The HPMS Report Status interface can be used to check on the HPMS submittal progress. This interface helps keep track of the number of validation errors that still exist and submittal files that have yet to be created. The HPMS Report Status interface () can be located by selecting the Reports tab and navigating to the second section-- Status. The HPMS Report Status interface is the only icon in this section and the third on the Reports menu.

Item Complete Status

To mark a Report Status item as complete, the user can select the checkbox to the left of the item. The progress bar will update after marking items as complete or incomplete.

Section Validations

The Section Validations portion of the HPMS Report Status interface is used to view the progress of the Route Import, Event Import, Coverage Validations, and Cross Check Validations. This section displays the number of invalidations found, along with the latest date each validation was performed.

Sample Validations

The Sample Validations portion of the HPMS Report Status interface is used to view the progress of the Sample and TOPS validations. This section displays the number of invalidations found for each Sample and TOPS validation report, along with the latest date each validation was performed.

Submittal Files

The Submittal Files portion of the HPMS Report Status interface is used to view the progress of the various files required for HPMS submittals. If a file is created in HPMS Manager, a last created date will appear beside the item. This section also contains a link to open the Section File Submittal Status interface.

Section File Submittal Status Link

The sole link in the Submittal Files portion-- the Section File Submittal Status link-- opens the Section File Submittal Status interface. This interface is used to track which data items had a section file created.

The Section File Submittal Status interface is divided into ten tabs based on the different FHWA categories according to HPMS 9.0 specifications (Designations, Identifications, Inventory, Lanes, Intersections, Traffic, Control, Pavement, Terrain, and Travel Time). Marking items as complete here will update the progress bar on the HPMS Report Status interface. The text for the Section File Submittal Status link will also change to reflect the number of items marked as complete.

Help Articles

If the user wishes to view a summary of the help articles for this application, they can click here.

Search

Welcome to PMG Support

Workflow

Build a Data Table

Data Source Configuration

Managing Data Sources

File Data Sources

Database Data Sources

Map Server Data Sources

Access Data Sources

Data Tables Configuration

Data Table Creation

Data Table Definition

Data Table Information

Required Items

Attributes

Data Table Population

Populate Report

Validations

Validation Rules Maintenance

Edit a Rule

Add New & Delete Rules

Validation Checks

Route/LRS Validation Check

Sample Sections and TOPS Validation Check

Import/Cross/Coverage Validation Check

Edit Data

Validation Edit Menu

Open the Interface

Correct Errors

Basic Editor

Query for a Route

(1) Select From Map

(2) Enter Route

Edit Groups

Data Cleaning Icons

Fix Event Gaps

Snap Events to Route

Fix Event Offsets

Fix Event Overlaps

Edit Log

Save Data to Source

Sample Adequacy

Create TOPs

Adjust TOPs

Summary Tab

Detail Tab

Rows

Changes Tab

Saving Adjust TOPS

Check Adequacy

Cell Information

Potential Samples

Filters -- Top Filters

Filters -- Data Completeness Filters

Filters -- Potential Sample Table

Manually Add Samples

Randomly Add Samples

Sample Table

Expansion Factors

Sample Risk Analysis

Risk Analysis Parameters

Optional Filters

Tables

Delete Samples

Precision Level

Standard Reports

Submittals

ARNOLD Segments

Road Segments

Sample Limits

County

Import a File

Recalculate Data

Edit Data

Export Data

Non-Federal Aid

Import a File

Recalculate Data

Edit Data