Statement of Work.pdf

STATEMENT OF WORK

1. BACKGROUND AND PURPOSE

The Federal Highway Administration (FHWA) requires storage of traffic data as part of supporting the National Park Service’s (NPS) Traffic Program. Data are auto-polled daily or manually downloaded monthly from 115 continuous traffic count stations. The data are screened against Quality Control (QC) processes, anomalies are imputed, and the data used to generate monthly and annual traffic data reports.

Currently traffic data are collected using Oriux or Internation Road Dynamics (IRD) traffic counters. Auto-polling is conducted using Oriux’s VIPER software or International Road Dynamics Road Reporter software. Data files can either be binned in an hourly time period or as individual Per Vehicle Records (PVRs).

The purpose of this contract is to provide a Commercial Off-the-Shelf (COTS) solution using a vendor hosted facility capable of meeting the requirements listed within Section 2.

2. REQUIREMENTS

The database shall meet the following requirements:

A. Database Requirements

• Have ability to contain a minimum of 300 continuous count stations and 750 coverage count stations, and 30 years of traffic data. See Appendix A for the List of Count Stations’ Minimum Data Fields.

• Be hosted on vendor’s servers.

• Allow for web interface via the most current version of Windows browsers, including

(but not limited to) Google Chrome and Firefox, to allow those working with the database to impute the traffic data or make reports.

• Ability to create hourly data from a subset of a count station’s detectors by either (1) grouping select detectors or (2) through addition and/or subtraction of select detectors hourly traffic volumes and save the data in a simulated count station.

• Ability to report continuous count station status as functioning correctly or not functioning correctly.

• Accept raw traffic data files as either binned or individual PVRs.

• Data downloaded from the database is to be available as a MS Excel spreadsheet.

• Data must be available to download in a format FHWA’s Office of Highway Policy

Information deems acceptable to be uploaded into FHWA’s Travel Monitoring Analysis System (TMAS) database.

B. QC Requirements

• Include pre-installed QC validation procedures based on industry standards, with the ability to edit and delete as needed.

• Ability to add additional QC validation rules unique to recreation traffic volumes found in the NPS. See Appendix B.

• Ability to flag data that fail automated QC validation and have the user impute or accept flagged data.

STATEMENT OF REQUIREMENTS

• Database must maintain raw (prior to QC updates) and imputed version of the traffic data.

• Ability for user to attach external information affecting count station such as lane closures or weather events to date ranges.

C. Reporting Requirements

• Reports and graphs will be generated by count stations, direction or by all lanes.

• Reports and graphs will have ability to span multiple years and multiple months for a count station.

• Minimum format for download of data, reports and graphs will be latest versions of MS

Word, MS-Excel and Adobe PDF.

a) Monthly Reporting − Create monthly reports based on individual lane, direction or count station. For Excel downloads, reports will fit on one page for the parameters selected. For example, if report was by count station, the report would be one page; however, if the report was by lane and there were six lanes, the report would contain six pages (one per lane).

− Reports shall be able to be produce traffic data in hourly or daily formats.

− Reports shall display all the data for various subgroup increment bins, such as speed

(e.g. less than 50 mph, 50 -55 mph, 55-60 mph, etc.).

b) Annual Reporting − Annual reports shall contain data from up to 750 coverage count stations.

− Create annual reports based on individual lane, direction, count station or from a selected group of count stations.

− In addition to reports producing traditional annual statistics, such Annual Average

Daily Traffic (AADT), reports shall also produce Seasonal Average Daily Traffic (SADT), monthly factors and apply monthly factors to coverage count stations.

D. Help Desk Support

• Vendor shall provide access to technical support from 9 am EST to 6 pm EST, Monday through Friday.

• Allow for ten (10) named FHWA and/or NPS users to have access to technical support.

3. PERIOD OF PERFORMANCE

The contract will consist of one, 12-month base period and two, 12-month option periods, for a total of three years (36 months).

The following schedule of supplies and services contains a Contract Line Item Number (CLIN) structure which corresponds to the supplies and services described in this document.

This table must be filled out by the contractor and returned as part of the quote.

Table 1. Firm-Fixed Price CLINs.

TIME PERIOD AMOUNT

TOTAL BASE PERIOD (10/01/2025-09/30/26) $

CLIN 00001 - TOTAL OPTION PERIOD 1 (10/01/2026-09/30/27) $

CLIN 00002 - TOTAL OPTION PERIOD 2 (10/01/20257-09/30/28) $

GRAND TOTAL ALL OPTION PERIODS $

4. MILESTONE DATES

The following schedule of milestones will be used by the COR to monitor timely progress under this contract.

Table 2. Milestones and Dates.

MILESTONE DELIVERABLE PLANNED COMPLETION DATE

Kick-Off Meeting Meeting Minutes Within 10 days of contract award Help Desk Support On-going through end of the period of performance for the contract

Appendix A -- List of Count Stations’ Minimum Data Fields

Count Station Data Fields (Continuous and Coverage)

• Park Name and Park Alpha Code

• Park Number

• NPS Region

• Count Station Name

• Count Station Number

• Reference Group

• Lane ID

• Lane Direction of Travel

• Segment’s RIP Route Number

• Segment’s RIP Route Name

• Segment’s Description

• Segment’s Beginning and Ending Mile Points

• Segment’s Beginning and Ending Latitude/Longitude

• Segment’s Beginning and Ending Descriptions

• General Comments

Traffic Data Fields (Continuous and Coverage)

• Year, Month, Date and Day of Week of the Count

• Twenty-four hourly traffic volume, starting at 12 AM

• Total Daily Traffic

• Speed (PVR data only)

• Vehicle Classification (PVR data only)

Appendix B -- Quality Control Rules

Table 3. Traffic Count Quality Control Validation Rules.

RULE NAME AND DESCRIPTION THRESHOLD / FLAGGED AS INVALID IF

1. Percent Complete Not a validation rule, but a reported statistic.

2. Valid Days in MADW: The number of valid daily counts required to calculate each monthly average day of the week (MADW) count.

Less than two 100%-complete days of valid counts for each day of the week.

3. Valid Hours in Daily Count: The number of valid hours required for calculation of a daily count.

Less than 24 hours of valid data in a day.

4. Consecutive Zero Values: The maximum number of consecutive zero-volume hourly counts.

For recreational locations: More than 20 consecutive zero values.

For non-recreational locations: More than eight consecutive zero values.

5. Daytime Allowable Zero Values: The maximum number of zero-volume hourly counts between 7:00 a.m. and 7:00 p.m.

This rule is not applied if daily volume is less than 200 vehicles.

For recreational locations: More than four zero values between 7 am and 7 pm.

For non-recreational locations: More than two zero values between 7 am and 7 pm.

6. Consecutive Identical Non-Zero Values: The maximum number of consecutive identical non-zero values (applied to hourly volume values).

This rule is not applied if daily volume is less than 200 vehicles OR if hourly volumes are equal to or less than 15.

Four or more consecutive identical non-zero count values (hourly volume values).

7. Maximum Vehicles: The maximum allowable number of vehicles per hour per lane.

For recreational locations: Greater than 600 vehicles per hour per lane. Exceptions exist for certain stations.

For non-recreational locations: Greater than 2,400 vehicles per hour per lane.

8. Ratio of Lane 2 to Lane 1 Counts: The maximum allowable ratio of lane 2 (passing lane) to lane 1 (rightmost driving lane) counts.

For recreational locations: Not recommended at any current location.

For non-recreational locations: Various ratios based on site.

9. Ratio of Noon to Midnight Counts: The minimum allowable ratio of noon (12p-1p) to midnight (12a-1a) hourly counts on the same calendar day. Only applied when noon and midnight counts are nonzero.

For recreational locations: Ratio of noon to midnight count less than 1.

For non-recreational locations: Ratio of noon to midnight count less than 1 OR greater than 120.

10 and 11. Maximum Hourly Difference in Current Month: Compares each days’ hourly count with the Monthly Average Day of Week (MADW) hourly count for current month and year. If MADW hourly count not available in current month and year, use the previous year MADW, same month.

The total daily volume must fall within two standard deviations of the Monthly Average Day of Week (MADW) daily volume.

12. Interval – Boundary Hours: Compares a zero-volume hourly count to one or more boundary hours with a minimum threshold.

Either boundary hourly count (the hour before or after) of more than 50 vehicles adjacent to a zero-volume hourly count. Select sites use a boundary hourly count of 100 vehicles.

13. Ratio of Peak Hour to Daily Count: The maximum allowable ratio of the peak hour count to the total daily count.

For recreational locations: Ratio of peak hour to daily count greater than 35%. Select stations are set at 40%.

For non-recreational locations: Ratio of peak hour to daily count greater than 25%. Select stations are set at 30%.

14. Daily Directional Split: The maximum allowable directional split for all lanes, by day.

Varies by count station.

15. Total Daily Count: The minimum allowable total daily count, by lane.

Daily total volume count is less than 1.

16. ADT vs. MADW: Compares each daily count subtotal with the Monthly Average Day of Week (MADW) daily total for current month. If MADW daily count not available in current month and year, use the previous year MADW, same month.

The total daily volume must fall within two standard deviations of the Monthly Average Day of Week (MADW) daily volume.