STATEMENT OF REQUIREMENT.docx

STATEMENT OF REQUIREMENTS

1. BACKGROUND AND PURPOSE

The Federal Highway Administration (FHWA) requires storage of traffic data as part supporting the National Park Service’s (NPS) the Traffic Management Program. Data are collected (auto polled) daily from 109 continuous traffic count stations. The data are downloaded nightly, screened for data anomalies and used to generate monthly and annual traffic data reports.

Currently traffic data are collected using Peek Traffic Corporation’s traffic counters, either the ADR-Sabre. Auto polling is conducted using Peek’s auto polling software.

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:

REQUIREMENT 1.0. General Database Requirements

· Maintain raw (prior to QA/QC updates) and imputed version of the traffic data.

· Have ability to contain a minimum of 300 continuous count stations and 750 coverage count stations, and 30 years of traffic data.

· 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.

· Have a web portal to allow public viewing of limited amounts of data.

REQUIREMENT 2.0. Continuous Count Station Requirements

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

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

REQUIREMENT 3.0. Quality Assurance/Quality Control (QA/QC)

· Include pre-installed QA/QC validation procedures based on industry standards.

· Ability to add additional QA/QC checks, edit existing QA/QC, and delete QA/QC checks as needed.

· Ability to flag data that fail QA/QC checks.

· Ability to impute or accept flagged data.

REQUIREMENT 4.0. Reporting and Data Sharing Requirements Monthly and Annual reports must have following abilities:

· Reports and graphs will be generated by count stations.

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

· Reports and graphs need to be broken down by lane, by direction, or for all lanes.

· Minimum format for download of data, reports and graphs will be latest versions of MS-Word, MS-Excel and Adobe PDF.

Sub- Requirement 4.1. Additional Monthly Report Requirements

· Create monthly reports based on individual lane, direction, or count station. For Word 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.).

Sub-Requirement 4.2. Additional Annual Report Requirements

· Annual reports shall contain data from up to 750 coverage count stations.

· Create annual reports based on individual lane, direction, count station, or of 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.

REQUIREMENT 5.0. Help Desk Support

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

· Allow for five (5) named FHWA and NPS users to have access to technical support

3.0 PERIOD OF PERFORMANCE

The contract will consist of 1, 12-month base period and 4, 12-month option periods for a total of 5 years (60 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 Addendum 1.0 (Statement of Requirements).

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

FIRM-FIXED-PRICE CLINs

TOTAL BASE PERIOD (09/30/2020-09/30/21) $______________

TOTAL OPTION PERIOD 1 (09/30/2021-09/30/22) $______________

TOTAL OPTION PERIOD 4 (09/30/2024-09/30/25) $______________

GRAND TOTAL ALL OPTION PERIODS $______________

4.0 MILESTONE DATES

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

PLANNED COMPLETION DATE

Kick-Off Meeting

Within 10 days of contract award

Help Desk Support

On-going through end of the period of performance for the contract