RFI_SS_2027_NPMRDS_w_draftSOW_7_21_2026.pdf

Federal Highway Administration (FHWA) Request for Information (RFI/ Sources Sought (SS) Notice/ Market Research

Office of Highway Policy Information (HPL)

1. SUBMITTAL INFORMATION

ISSUE DATE: Tuesday, July 21, 2026

DUE DATE FOR CAPABILITY STATEMENTS/ RESPONSES:

No later than (NLT) 2:00PM Eastern Time (ET) Wednesday, August 5, 2026 SUBMIT RESPONSES TO: Myla Wyatt myla.wyatt@dot.gov

SUBMIT QUESTIONS TO: Myla Wyatt myla.wyatt@dot.gov NLT 2:00PM ET Monday, July 27, 2026. Some questions or inquires may not receive a response.

In addition, questions received after the due date and time may not receive a response.

PLEASE do not post, upload, or submit questions or capability statements to SAM.gov. Questions and responses posted or submitted via SAM.gov may not be answered or considered.

SUBMITTALS SHOULD BE MADE IN ELECTRONIC FORMAT:

See below Section 5 entitled, “REQUESTED CONTENT OF RESPONSES TO THIS RFI/SOURCES SOUGHT” for submittal content instructions.

2. INTRODUCTION

Potential Sources Sought. This is NOT a solicitation for quotes/submissions/proposals. Federal Highway Administration (FHWA) is conducting market research to identify potential sources for an anticipated requirement. The purpose of this notice is to obtain information, for planning purposes, regarding (1) the availability and capability of qualified sources to perform all or some of the work described below; and (2) the size classification of the available and capable sources relative to the North American Industry Classification System (NAICS) code for the proposed acquisition.

This notice does not solicit quotations/proposals. Responses to this notice are not offers and cannot be accepted by the Government to form a binding contract. Additionally, the FHWA will not provide reimbursement for any information that may be submitted in response to this RFI/SS notice.

Companies/Firms/Respondents are solely responsible for all expenses associated with responding to this RFI/SS notice. Responding to this RFI/SS notice will neither increase nor decrease the likelihood of being awarded any contract in the future by FHWA for the requisite services.

Pursuant to 48 C.F.R., Part 10, the Government is conducting market research to:

• Determine what sources exist that can satisfy the Government’s requirements listed below,

• Determine the capabilities of potential sources,

• Determine the size and status of potential sources, and

• Determine the level of competition (i.e. 8(a), set-aside, or full and open).

mailto:myla.wyatt@dot.gov mailto:myla.wyatt@dot.gov

The results of this RFI/SS notice will assist in identifying potential quoters having an interest in, and the resources to accomplish the work and contribute to determining the method of procurement.

3. BACKGROUND

Federal Highway Administration ( FHWA) an operating agency within the U.S. Department of Transportation (USDOT) is charged with the broad responsibility of ensuring that America’s roads and highways continue to be the safest and most technologically up to date. With continued growth in both traffic and freight volumes, significant portions of the transportation system experience congested conditions on a regular basis, leading to unreliable service to the American people. FHWA has engaged in broad activities in partnership with state and local transportation agencies to improve travel reliability and mitigate congestion. From a traffic flow standpoint, these activities include but are not limited to:

• Real-time and forecasted information;

• Measuring/monitoring passenger and freight system performance;

• Analytical foundation/tools/data;

• State of the art technologies and strategies, including operational tests of intelligent transportation system technologies;

• Development of standards for information exchange;

• Guidance and funding for infrastructure and Intelligent Transportation System (ITS) Projects;

• Integration across system elements, jurisdictions, and modes; and

• Assistance for transportation and planning professionals in developing the knowledge and skills needed to do their jobs effectively.

Together, these activities build the solution set required to proactively operate the transportation system.

Proactively operating the transportation system begins with awareness that routine operation is not addressing significant congestion or regular operational problems. Proactive management can only happen where there is good available information about what is currently happening, how the operation of the system is being impacted, and what actions are necessary to make the system operate better.

This is only possible with a good analytical foundation, and a plan for how the transportation system should be operated. This foundation should include the use of appropriate performance metrics, establishing targets for system performance, and the use of appropriate analysis tools to identify, develop, and evaluate solutions to operational problems, and an investment plan exhibiting a capable workforce necessary to implement the chosen solutions.

To date, the FHWA has evaluated measures of travel time, travel time variability, reliability, speeds, and related metrics through efforts such as the data and value-added products derived from the Urban Congestion Report (UCR), Freight Mobility Trends (FMT) program, and the NPMRDS. The FHWA has supported transportation agencies and their needs to plan for and better manage the transportation network throughout the United States and continues to do so in response to the performance measure and management requirements of Moving Ahead for Progress 21 (MAP-21), the Fixing America’s Surface Transportation (FAST) Act, and the current Infrastructure Investment and Jobs Act (IIJA).

4. OBJECTIVE

The objective of the requirement is to gain access to timely and quality travel time data referred to as the National Performance Management Research Data Set (NPMRDS) data covering the National Highway System (NHS) and obtain technical support needed by Federal, state, and local agencies to carry out the data application and data analysis related to Transportation Performance Management (TPM).

The requirement for acquiring NPMRDS Data, Obtaining Technical Support, and Conducting Data Analysis”, FHWA Office of Highway Policy Information (HPPI) seeks to continue to provide the NPMRDS data as a tool and information source for the US Department of Transportation, FHWA, State Transportation Departments (DOTs), and Metropolitan Planning Organizations (MPOs) / Council of Governments (COGs) to use in transportation performance measurement and management.

For more information on the existing FMT, NPMRDS and UCR programs, see the following links:

• https://ops.fhwa.dot.gov/freight/freight_analysis/perform_meas/index.htm

• https://ops.fhwa.dot.gov/perf_measurement/index.htm

• http://ops.fhwa.dot.gov/perf_measurement/ucr/index.htm

USDOT and FHWA continue to have the need to access travel time data for all traffic, including passenger and freight traffic on the NHS.

5. REQUESTED CONTENT OF RESPONSES TO THIS RFI/SOURCES SOUGHT NOTICE

Interested parties who consider themselves qualified to perform all the listed services herein are invited to submit a capabilities statement/response to this RFI/SS notice.

Responses shall clearly identify:

1. Name, Address, Point of Contact(s) (POC(s));

2. SAM.gov Unique Entity ID (UEI)

3. CAGE Code

4. GSA Schedule Number (if applicable);

5. Size standard under NAICS code under NAICS code 541990 All Other Professional, Scientific and Technical Services

6. Identify all applicable classifications for your organization such as:

a. Large Business

b. Small Business

c. Small Disadvantaged Business

d. Economically Disadvantaged Woman-Owned Small Business (EDWOSB)

e. Woman-Owned Small Business (WOSB)

f. 8 (a)

g. HUBZone

h. Service-Disabled Veteran Owned Small Business (SDVOSB)

i. Veteran Owned Small Business (VOSB)

j. Non-Profit https://ops.fhwa.dot.gov/freight/freight_analysis/perform_meas/index.htm https://ops.fhwa.dot.gov/perf_measurement/index.htm http://ops.fhwa.dot.gov/perf_measurement/ucr/index.htm http://www.ops.fhwa.dot.gov/perf_measurement/ucr/index.htm

Potential sources are requested to submit a capability statement which addresses their company’s/firm’s ability to deliver the required products and/or services as detailed in the RFI/SS notice and attached draft Statement of Work (SOW). The capability statement should clearly detail the following:

1. Detailed description of technical capabilities and relevant experience to perform the work described in Section 4 above and attached draft SOW.

2. Detailed description of experience and expertise of potential staff and the ability to perform the required services;

3. Detailed description of relevant projects completed within the last three (3) years related to the anticipated objectives of this project with information about client/customer, scope, dollar value, specific services/data provided, and examples of noteworthy outcomes/success

4. Detailed description of available facilities to perform the work detailed in Section 4 above and attached draft SOW.

PAGE LIMIT: The capability statement shall be no more than six (6) pages in length, single-spaced, with font sized 11 or larger using Times New Roman or Arial. The minimum font size for charts shall be 10 point. Margins (Top, Bottom, Right and Left) no smaller than 1” (headers and footers are allowed in the margins) page size shall be no greater than 8.5” x 11.” Submission shall be provided in electronic format readable and searchable by Adobe Acrobat, Microsoft Word, or Google Docs. Do NOT submit marketing material, slide presentations or technical papers. PLEASE DO NOT SUBMIT RESUMES.

6. NOTES

PARTICIPATION IN MARKET RESEARCH IN NO WAY WILL EFFECT

COMPANY’S/FIRM’S ELIGIBILITY TO COMPETE FOR THESE SERVICES IF AN

REQUEST FOR QUOTATION (RFQ)/REQUEST FOR PROPOSAL (RFP) IS

SUBSEQUENTLY ISSUED.

PARTICIPATION IN MARKET RESEARCH IN NO WAY WILL INFLUENCE A SOURCE

SELECTION DECISION FOR THESE POTENTIAL SERVICES.

This RFI/SS notice is not to be construed to be a commitment on the part of the Government to award a contract, nor does the Government intend to pay for any information or responses submitted as the result of this RFI/sources sought notice.

PURSUANT TO REVOLUTIONARY FAR OVERHAUL (RFO) FEDERAL

ACQUISITION REGULATION (FAR) PART 10-FOR MARKET RESEARCH

PURPOSES ONLY- This draft Statement of Work (SOW) is solely for informational, market research, and planning purposes only and does not commit the Government to any further contract actions, i.e., solicitation and/or contract.

Companies, firms, and entities are advised that the United States Government will not pay for any information or administrative cost incurred in preparation of any type of response (capabilities statement, etc..) to this Request for Information (RFI) or Sources Sought Notice. Any questions, inquiries, or exchanges about the draft Statement of Work (SOW) are not offers or quotes and cannot be accepted by the U.S Government to form a binding contract. This is a “draft” SOW and contents may be revised.

Statement of Work (SOW) - Description/Specifications

1.0 BACKGROUND

Federal Highway Administration ( FHWA) an operating agency within the U.S.

Department of Transportation (USDOT) is charged with the broad responsibility of ensuring that America’s roads and highways continue to be the safest and most technologically up to date. With continued growth in both traffic and freight volumes, significant portions of the transportation system experience congested conditions on a regular basis, leading to unreliable service to the American people. FHWA has engaged in broad activities in partnership with State and local transportation agencies to improve travel reliability and mitigate congestion. From a traffic flow standpoint, these activities include but are not limited to:

• Real-time and forecasted information;

• Measuring/monitoring passenger and freight system performance;

• Analytical foundation/tools/data;

• State of the art technologies and strategies, including operational tests of intelligent transportation system technologies;

• Development of standards for information exchange;

• Guidance and funding for infrastructure and Intelligent Transportation System (ITS) Projects;

• Integration across system elements, jurisdictions, and modes; and

• Assistance for transportation and planning professionals in developing the knowledge and skills needed to do their jobs effectively.

Together, these activities build the solution set required to proactively operate the transportation system. Proactively operating the transportation system begins with awareness that routine operation is not addressing significant congestion or regular operational problems. Proactive management can only happen where there is good available information about what is currently happening, how the operation of the system is being impacted, and what actions are necessary to make the system operate better.

This is only possible with a good analytical foundation, and a plan for how the transportation system should be operated. This foundation should include the use of appropriate performance metrics, establishing targets for system performance, and the use of appropriate analysis tools to identify, develop, and evaluate solutions to operational problems, and an investment plan exhibiting a capable workforce necessary to implement the chosen solutions.

To date, the FHWA has evaluated measures of travel time, travel time variability, reliability, speeds, and related metrics through efforts such as the data and value-added products derived from the Urban Congestion Report (UCR), Freight Mobility Trends (FMT) program, and the National Performance Management Research Data Set (NPMRDS). The FHWA has supported transportation agencies and their needs to plan for and better manage the transportation network throughout the United States and continues to do so in response to the performance measure and management requirements of Moving Ahead for Progress 21 (MAP-21), the Fixing America’s Surface Transportation (FAST) Act, and the current Infrastructure Investment and Jobs Act (IIJA).

The requirement for acquiring NPMRDS Data, Obtaining Technical Support, and Conducting Data Analysis”, FHWA Office of Highway Policy Information (HPPI) seeks to continue to provide the NPMRDS data as a tool and information source for the US Department of Transportation, FHWA, State Transportation Departments (DOTs), and Metropolitan Planning Organizations (MPOs) / Council of Governments (COGs) to use in transportation performance measurement and management.

For more information on the existing FMT, NPMRDS and UCR programs, see the following links:

• https://ops.fhwa.dot.gov/freight/freight_analysis/perform_meas/index.htm

• https://ops.fhwa.dot.gov/perf_measurement/index.htm

• http://ops.fhwa.dot.gov/perf_measurement/ucr/index.htm

The US DOT and the FHWA continue to have the need to access travel time data for all traffic, including passenger and freight traffic on the NHS.

2.0 OBJECTIVE

The objective of the requirement is to gain access to timely and quality travel time data referred to as the NPMRDS data covering the National Highway System (NHS) and obtain technical support needed by Federal, state, and local agencies to carry out the data application and data analysis related to Transportation Performance Management (TPM).

3.0 CONTRACT SCOPE

The scope of the contract is limited to:

a) Obtain quality travel time and relevant data referred to as the NPMRDS data on the

NHS with perpetual accesses by the Federal Highway Administration (FHWA) at the https://ops.fhwa.dot.gov/freight/freight_analysis/perform_meas/index.htm https://ops.fhwa.dot.gov/perf_measurement/index.htm http://ops.fhwa.dot.gov/perf_measurement/ucr/index.htm http://www.ops.fhwa.dot.gov/perf_measurement/ucr/index.htm

US Department of Transportation (DOT), other US DOT operating administrations, and other bureaus and offices within the US DOT, all State or equivalent highway agencies (State DOTs), and local MPOs / COGs.

b) Provide technical support regarding data application and usage for transportation performance measures and disseminate the data to customers through an efficient and easy to use online platform or portal.

c) Deliver all other analytical products as specified.

The above coverages are further defined and described below.

4.0 DETAILED REQUIREMENT

NOTE:

The FHWA does not collect Personally Identifiable Information (PII) under this contract.

PII includes names, medical information, Personally Identifiable Financial Information (PIFI), and unique identifiers such as driver’s license, passport, or social security number.

The specific goal of the contract is to support the FHWA and other users for the continued NPMRDS program including data, technical assistance, and data-sharing covering:

• Gaining access to a national travel time data set with specific attributes referred to as the NPMRDS;

• Obtaining a Geospatial Information System (GIS) dataset defined as the Performance Network, possessing the Highway Performance Monitoring System (HPMS) attributes through the conflation of the NPMRDS and HPMS geospatial datasets;

• Providing travel time data set on NHS which can be further processed by States or States’ contractors/consultants to fulfill HPMS TPM submissions to all 50 state, DC, and PR DOTs;

• Providing daily, weekly, monthly, and annual NPMRDS and further processed NPMRDS data on the NHS;

• Managing data storage, data access, data usage agreement, and data sharing for all federal partners, State DOTs, MPOs, and other authorized users;

• Providing technical assistance related to the gathering and utilization of the NPMRDS data.

To meet the contract objectives, the Contractor must perform the following tasks:

Task 1 - Project Management

Within two weeks after award, key members of the Contractor’s team must participate in a kick-off meeting with FHWA technical staff, the Contracting Officer’s Representative (COR), and appropriate contractor staff to discuss the tasks and delivery schedule, delineate roles and responsibilities, establish communication protocols, resolve and http://searchfinancialsecurity.techtarget.com/definition/personally-identifiable-financial-information http://whatis.techtarget.com/definition/unique-identifier-UID http://whatis.techtarget.com/definition/unique-identifier-UID identify potential problems, and clarify understandings of the technical aspects of the contract. The Contractor’s project manager must, along with key staff and other contractor representatives including sub-contractor representatives, attend the virtual meeting (Microsoft Teams or like). The Contractor must present to FHWA their proposed Draft Management and Work Plan and when applicable, address the comments/suggestions made by FHWA. The Contractor must prepare and submit to the COR a meeting minute summary within one week after the kick-off meeting.

Based on the meeting, the Contractor must further refine their work plan and submit the Final Management and Work Plan to the COR within two weeks after the kick-off meeting. The Management and Work Plan must be consistent with the contract and all exhibits. The Management and Work Plan does not override or change the requirements or exhibits of this contract. The controlling document for the requirements must be the contract, its exhibits, and any modifications issued.

Management and Work Plan

The Contractor is required to provide a Management and Work Plan containing the management approach and critical schedule needed to complete the tasks. Following the kick-off meeting and upon resolution of FHWA comments on the Management and Work Plan, the Contractor must complete a Final Management and Work Plan. The Contractor must update the Management and Work Plan on a quarterly basis.

The Management and Work Plan must include all of the following:

1) Project Scope Statement – A plan to ensure that the project includes all the work required and only the work required, to complete the project successfully.

2) Project Internal Communications Plan – A plan to ensure timely and appropriate generation, collection, distribution, storage, retrieval, and ultimate disposition of project information.

3) Work Breakdown Structure – A subdivision of the major project deliverables and project work into small, more manageable components. Planned duration time can be assigned to each component.

4) Critical Path – It is the longest duration path through a network diagram, and it determines the shortest time to complete the project.

5) Project Schedule using a Gantt chart – A project schedule developed based upon activity sequences, durations, resource requirements, and schedule constraints. The project schedule must include planned start and finish dates, activity sequences, activity durations, planned milestones and the identification of the critical path.

6) Risk Management Plan – A plan to ensure a structured process that conducts risk identification (entered into a risk register) analysis for risk mitigation and developed responses and actions to planned mitigation of risks.

7) Monitoring and Control Project Work – A plan that identifies how the project work will be tracked, reviewed, and regulated to meet the performance objectives of the project management plan. The Contractor must execute the monitoring and control plan to ensure the project is meeting the deliverables outlined in the Statement of Work.

8) Human Resource Plan – A plan that includes roles and responsibilities, project organizational charts, and staffing management plan for the prime and any sub-contractors.

9) Project Closeout Plan – A plan which ensures that all project work is complete and that the project has met its objectives.

Task 1 – Deliverables

Deliverable 1-1: Draft Management and Work Plan The Contractor must deliver the Draft Management and Work Plan in Google Document to FHWA COR within the first week after award.

Deliverable 1-2: Kick-off Meeting The Contractor must host the virtual kick-off meeting via Google Meet with FHWA personnel and key contractor personnels participated 2 weeks after award.

Deliverable 1-3: Final Management and Work Plan The Contractor must deliver the Final Management and Work Plan in Google Document to FHWA COR within 4 weeks after the kick-off meeting.

Deliverable 1-4: Monthly Progress Meetings The Contractor must host the Monthly Progress Meetings via Google Meet monthly with FHWA COR as needed or requested by FHWA COR.

Deliverable 1-5: Monthly Progress Report The Contractor must deliver the monthly progress report in Google Document within the first week of the following month.

Task 2 – Delivering and Supporting the National Performance Management Research Data Set

The Contractor must gather, analyze, host, deliver, and disseminate the NPMRDS data and the Performance Network, meeting all requirements specified in Part 2a - Basic Definitions, Part 2b - NPMRDS Data Elements and Performance Network, Part 2c - Data Sharing and Technical Support, and Part 2d - NPMRDS Data Quality Specification.

Part 2a: Basic Definitions

Probe Vehicle

A probe vehicle is defined as a vehicle equipped with or occupied by sensors, such as Global Positioning System (GPS), that collects and transmits its location, speed, and other travel data to a system. Data gathered from such vehicles are termed as probe-based data, and such vehicles are termed probe vehicles. The Contractor must have access to vehicle probe-based travel time data for the full Period of Performance.

The FHWA requires actual, observed vehicle travel times and average speeds from vehicle probe-based data to be delivered. The travel time data are vehicle type, travel direction, roadway segment specific. Imputed, predicted, or historical data must not be included, with the exception of path processed data or similar approach. The FHWA’s understanding is that path processed data, in general, is using a single (or more than one) probe to determine travel time over a path where individual segment lengths are too short to receive a time/speed for each.

National Highway System (NHS)

NHS is a set of public highways and roads that is significant for the national economy and defense and is geospatially recorded in FHWA HPMS. The latest public available HPMS data serves as the official NHS coverage record.

NHS Roadway Segment

An NHS roadway segment refers to a physical link on the NHS by direction and is represented and addressed by a Travel Message Channel (TMC). The length of an NHS roadway segment used in this project must not be more than half mile and one mile in urban and rural areas, respectively. If a TMC that is longer than the threshold, it must be equality split into multiple Divisions in an order aligned with traffic direction.

Each Division must be assigned with its order number starting from one as the starting division. For example, a segment of urban roadway represented by TMC 110+01023 is

1.4 miles long, this TMC must be split into 3 equal divisions ordered in the direction of traffic flow:1) division 1, 0.4667 mile long as the first division, coded 110+01023_1 under a new data variable name Division, 2) division 2, 0.4667 mile long following the division 1, coded as 110+01023_2 under the variable name Division, and 3) division 3,

0.4667 mile long, coded as 110+01023_3 under the variable name Division.

The vertex order of a TMC follows the travel direction. For example, the two TMCs representing an undivided two-way facility would be visually looking identical.

However, their geometries vertices are ordered in reverse with both follows their traffic direction. The split Division segment must remain the same vertices order as its TMC.

If a TMC does not need to split as its length meets the requirement, its Division code is coded with 0 (zero). For example, TMC 110+01024 is 0.3541 miles long and meets the segment length need. Consequently, there is no need to split it further. The entry for the Division for this TMC under the variable Division is 110+01024_0.

The Division serves as the base unit to collect travel time data. Travel time data of a TMC consists of all Division travel times.

Performance Network

In general, the Performance Network is referred to as a geospatial dataset, produced through the integration/conflation of the NPMRDS GIS dataset with the FHWA HPMS GIS dataset and possessing attributes associated with both original datasets.

The Performance Network is an annual product where it is based on the latest available HPMS and the current year NPMRDS GIS data. In addition to the need of the Contractor to devise a Portal/API/Mechanism to disseminate the Performance Networks to users including the public, FHWA will also independently distribute the Performance Networks to the public via FHWA website to promote accountability.

National Performance Management Research Data Set (NPMRDS)

The Raw NPMRDS is defined as a set of travel time data recorded separately for passenger vehicles, freight trucks, and the overall fleet wide vehicles, traveling on the NHS in a 5-minute interval for each roadway segment by travel direction, represented by a Division which may be a subsegment of a TMC, acquired through probe data, and linked to the Performance Network.

The PM3 NPMRDS is defined as a set of travel time data aggregated from the Raw NPMRDS data to 15-minute interval, temporally, and the entire TMC, spatially. The 15-minute interval must be hour-aligned. All divisions of a TMC must be included in the aggregation.

Unless specified otherwise, the term NPMRDS data covers both the Raw NPMRDS data and the PM3 NPMRDS data.

Part 2b: NPMRDS Data Elements and Performance Network

The Raw NPMRDS Data Elements and Performance Network contains Division (sub TMC) level resolution data. The Division level resolution data serves as the foundation for other derived data and various applications and is addressed by the Division code. The PM3 NPMRDS data, aggregated from the Raw data, is addressed by the TMC code.

The Performance Network is the GIS data gained by conflating the NPMRDS geospatial data with the HPMS geospatial data.

The Performance Network consists of two separated GIS data sets. The first GIS data set is the Division Performance Network data set with individual Division as unique GIS features. The second GIS data set is the TMC Performance Network with individual TMC as unique feature.

The FHWA suggests that the conflation work should be carried out first between the Division NPMRDS and the HPMS. From there, subdivisions within a TMC are aggregated to obtain the TMC Performance Network.

Travel Time Data Elements:

The Contractor must analyze, and process travel time data as outlined below.

Raw NPMRDS data

Raw NPMRDS data is at the Division resolution level with a 5-minute interval daily.

Travel time data must include the following data elements.

• Average travel speed and travel time, minimum, and maximum travel times based on probe data for each of the three vehicle groupings: all vehicles, passenger vehicles only, and freight trucks only.

• The average directional travel speed and travel times, minimum, and maximum travel times must be delivered for every 5-minute period of every day and all days of a year for every Divisions covering the entire NHS road segments including NHS Intermodal Connectors.

• The full extent of the NHS as defined by the latest available FHWA HPMS must be covered.

• A descriptive data element called Intensity data (1-5) that informs the sample size (e.g., a number from “1” to “4” indicates the number of probes, and “5” indicates 5 or more probes.) during the 5-minute interval.

Table 1 illustrates the average, minimum, and maximum travel times data. For a hypothetical Division 133P04531_1 on December 12, 2025, from 16:00 to 16:05 (a 5‑minute interval). During this period, 12 probes (all vehicles) traversed the Division.

Their average travel time was 36.5 seconds, calculated as (t1 + t2 + t3 + … + t12) / 12.

The maximum travel time was 48.1 seconds (recorded by vehicle t3), and the minimum travel time was 28.2 seconds (recorded by vehicle t12), the Intensity is 5. The average speed is 49.3 MPH, calculated as (12xDivion_length)/(t1+t2+ …t12).

Table 1. Daily Raw NPMRDS Data Example

State Division Code TMC

Vehic le

Type

Timesta mp in Local Time Zone

Aver age

Trav el

Time (s)

Ave rage Spee d

(MP

H)

Mini mum Trav el Time

(s)

Maxim um

Travel Time (s)

Intensit y

AK 133P04531_1 133P04

531 A 1/1/2027

18:00 36.5 49.3 28.2 48.1 5

AK 133P04531_2 133P04

531 P 1/1/2027

18:05 30.8 58.5 21.1 33.6 2

AK 196+01010_0 196+01

010 F 1/1/2027

18:05 32.2 45.1 25.2 36.1 5

AK 196-01011_0 196-

01011 1/1/2027

18:10 30.3 46.2 26.1 38.9 5

AK 134N50501_1 134N5

0501 1/1/2027

19:10 30.5 56.8 30.5 30.5 1

AK 134N50501_2

134N5

1/1/2027 19:10 29.8 60.1 25.1 35.1 2

AK 134N50501_3

134N5

1/1/2027 19:315 … … .. … 3

Vehicle Type: A - All, P - Passenger, F - Freight

PM3 NPMRDS data The PM3 NPMRDS data is obtained by processing the Raw NPMRDS data by follow the two-step procedures outlined below, and data format presented in Table 2.

Step One – Spatially aggregation to obtain the TMC 5-minute interval travel time data. For any TMC that has no Division split, the Step One is skipped. For any TMC which has Division splits, algebraically sum all divisions’ Average Travel Time, Minimum Travel Time and Maximum Travel Time as the TMC travel times, respectively.

For example, TMC 110+01023 contains 3 Divisions as 110+01023_1, 110+01023_2 and 110+01023_3 with Average Travel Time/Minimum Travel Time/Maximum Travel Time of 35.0/30.0/38.0, 36.0/31.0/40.0 and 35.5/29.0/39.0 seconds, respectively. The TMC 110+01023 Average Travel Time/ Minimum Travel Time/Maximum Travel Time would be 96.5 (35.0+36.0+35.5)/90.0 (30.0+31.0+29.0)/117.0 (38.0+40.0+39.0), respectively.

The TMC Average Travel Speed is calculated by the entire TMC length divided by the TMC Average Travel Time. Taking the same example as above, assuming the entire TMC length is 1.4 mile, the TMC 110+01023 Average Travel Speed would be 52.2 MPH (1.4 mile/96.5 seconds.)

The Intensity of the TMC is the algebraic sum of all its divisions Intensity, or 5 should it be over 5.

If any single Division of a TMC is missing 5-minute interval data, the TMC 5-minute interval data must be treated as Missing Data for the corresponding TMC.

Step Two – Temporally aggregation of the Step One results to obtain the TMC 15-minute travel time data. The TMC 15-minute interval Average Travel Time/Average Travel Speed/Minimum Travel Time/Maximum Travel Time are the algebraic average of these values among the 3-consecutive TMC 5-minute data from Step One, respectively, excluding any TMC 5-minute interval that marked as Missing Data in Step one.

Taking the same example as above, TMC 110+01023 has Missing Data for 1/1/2027 18:00, has 1/1/2027 18:05 Average Travel Time/Average Travel Speed/Minimum Travel Time/Maximum Travel Time of 95.0/53.1/90.0/120.0, respectively; and has 1/1/2027 18:10 data of 98.0/51.4/92.0/135.0, respectively. The TMC 110+01023 1/1/2027 18:00 15-minute interval Average Travel Time, Average Travel Speed, Minimum Travel Time and Maximum Travel Time data for 1/1/2027 18:00 would be 96.5 ((95.0+98.0)/2), 52.3 ((53.1+51.4)/2), 91.0 ((90.0+92.0)/2), and 127.5 ((120.0+135.0)/2.)

The TMC 15-Minute interval Average Travel Speed is calculated by the entire TMC length by the TMC 15-minute interval Average Travel Time.

The TMC 15-minute interval Intensity is the algebraic sum of all its 3-consecutive 5-minute Intensity, excluding any TMC 5-minute interval that are marked as Missing Data in Step One, or 5 should it be over 5.

Taking the same example as above, TMC 110+01023 has Missing Data for 1/1/2027 18:00, has Intensity of 3 for 1/1/2027 18:05, and 4 for 1/1/2027 18:10. The TMC 110+01023 1/1/2027 18:00 15-minute interval Intensity will be 5 (as 3 + 4 is over 5.)

Table 2. Daily PM3 NPMRDS Data Example

Sta te

TMC

Code

Vehic le

Type

Timestam p in Local Time Zone

Avera ge

Trave l Time

(s)

Avera ge

Speed

(MPH

Minim um

Travel Time

(s)

Maxim um

Travel Time

(s)

Intens ity

AK

133P045 31 A

1/1/2027 18:00 62.3 57.9 59.5 65.1 3

AK

196+010 10 F

1/1/2027 18:15 32.2 45.1 25.2 36.1 5

AK

196- 01011 P

1/1/2027 18:30 30.3 46.2 26.1 38.9 5

AK

134N50

1/1/2027 19:00 120.6 60.1 100.5 130.5 5

Vehicle Type: A - All, P - Passenger, F - Freight

Performance Networks

The Performance Networks must be obtained at two levels:1) the Division Performance Network with individual Division as the unique GIS feature and 2) the TMC Performance Network with individual TMC as the unique GIS feature.

Attention:

The Performance Networks are based on the NPMRDS Geospatial Network Data, supplemented by the HPMS Geospatial Data for needed attributes.

The Division feature must have the split geometry from its TMC with inherited native TMC attributes as described below:

• Division_Code – the unique identifier for the division. It is concatenated from TMC code and the division number. For example, 110+01023_2 is the second division of TMC 110+01023 that is longer than specified length threshold;

120P95096_0 is the only one division of 120P95096 that is not longer than the specified length threshold.

• TMC code – the actual TMC code

• Road_Number, Road_Name, First_Name, LinearTMC, Country, State, County, Zip_Code, Direction, Road_Class, Func_Class, Timezone, Num_Lanes, TMC_Linear, FRC, Border_Set, Thru_Lanes, Is_Primary – these attributes are inherited from native TMC attributes

• Start_Latitude, Start_Longitude, End_Latitude, End_Longitude – the WGS 84 coordinates of the beginning and ending points of division geometry.

• Length_in_Miles – the length of the division in miles.

The Division GIS feature must conflate with the latest HPMS data set (NHS subset) to include the following HPMS data items:

• YearId, StateId, RouteId, BeginPoint, EndPoint, F_System, Urban_ID, Facility_Type, Structure_Type, Through_Lanes, RouteNumber, RouteSigning, RouteQualifier, RouteName, AADT, AADT_Single_Unit, AADT_Combination, NHS, STRAHNET, NN, NHFN, Speed_Limit, Dir_Through_Lanes as defined in the HPMS Field Manual at:

https://www.fhwa.dot.gov/policyinformation/hpms/fieldmanual/page00.cfm.

During the HPMS conflation process, only One-Way, Two-Way and Ramp (HPMS Facility_Type 1, 2 and 4) facilities would be used as candidates to determine the above HPMS attributes. For a non-inventory direction division, all these HPMS attributes must be copied from the correspondent HPMS inventory direction segment. BeginPoint and EndPoint must not be adjusted per the division’s extension but truly matching that from HPMS segment if a division falls within the HPMS segment. If a division covers more than one HPMS segment, use the attributes of the spatially dominated HPMS segment. If a division is not fully covered by HPMS segment(s), take the attributes of the only available HPMS segment.

The Division GIS feature must also include the following calculated fields as described:

• Dir_Through_Lanes_Calculated - For One_Way facilities, it must be set to Dir_Through_Lanes of the conflated HPMS segment or Through_Lanes should Dir_Through_Lanes is missing in HPMS data set. For Two-Way facilities, the inventory direction division must be set to the Dir_Through_Lanes of the HPMS inventory direction segment if it presents; the non-inventory direction division must be set to the Dir_Through_Lanes of the non-inventory direction HPMS segment if both the HPMS segment (Facility_Type of 6) and Dir_Through_Lanes are presented. If either inventory division or non-inventory division cannot derive https://www.fhwa.dot.gov/policyinformation/hpms/fieldmanual/page00.cfm.

the field value this far, set the missing one as Through_Lanes minus the available Dir_Through_Lanes_Calculated value. If both divisions cannot derive the value this far, equally split Through_Lanes as their value.

• Dir_AADT_Calculated is calculated by AADT x Dir_Through_Lanes_Calculated

/ Through_Lanes.

The Division Performance Network with all Division GIS features conflated with HPMS data set must be in ESRI FGDB format with a coordinate system as WGS84. All column names must be named as they are specified above and must not be truncated.

The TMC Performance Network is formed based on Division Performance Network.

The TMC feature must have its original geometry from its TMC with inherited native TMC attributes as described above for Division feature except Start_Latitude, Start_Longitude, End_Latitude, End_Longitude and Length_In_Miles are all the TMC’s, not of the division’s. The TMC feature geometry must not be spatially aggregated from its division’s geometries, even though which are split from TMC feature geometry.

The TMC GIS feature must include the conflated HPMS attributes as specified above for Division feature. These HPMS attributes, except AADT, AADT_Single_Unit, AADT_Combination, AADT, AADT_Single_Unit, AADT_Combination, shall be aggregated from already conflated division features in a way to take the spatially dominated divisions values as the TMC attributes values. For example, one TMC covers 3 different divisions, but 2 divisions are having the same attribute values, the TMC attribute values shall take that of the 2 divisions as it spatially dominates the TMC coverage assuming all divisions have the same length. AADT, AADT_Single_Unit, AADT_Combination, AADT, AADT_Single_Unit and AADT_Combination attributes must be the length weighted averages from all Divisions of the TMC.

Given the Divisions provide a much higher spatial resolution than TMCs do, the FHWA urges the contractor to carry out the development of the Division Performance Network first. Based on the established Division Performance Network, the TMC performance network can be gained as stated above.

HPMS Conflation Timeline

HPMS data is about 24 months or more lagging behind the NPMRDS GIS dataset. For example, 2025 HPMS NHS data is most likely available in November 2026. The Contractor must conflate with 2025 HPMS NHS data and update the 2026 NPMRDS data starting in December 2026 and get the 2026 NPMRDS data updated and ready no later than February 28, 2027. The scope of the NPMRDS together with above attributes will be continued till the next year’s HPMS NHS Data update. In the case of the example, the Divisions and TMC and their attributes for year 2027 will be the same as the last updated per conflation with 2025 HPMS NHS data till the next update of 2026 HPMS NHS Data at the end of 2027.

Further Explanation of Data Timeline

• HPMS NHS data is about 24 months lagging the NPMRDS data. The HPMS NHS data defines the final NPMRDS NHS data coverage and attributes.

• NPMRDS should always use the latest available HPMS defined NHS network and attributes for data reporting.

• The syncing/conflation of the NPMRDS data with the HPMS NHS data to gain the Performance Network typically starts in December and completes by February 28 of the following year, ensuring the NPMRDS data is updated for State DOT TPM usages.

• Before the HPMS conflation starts in December of the year, the delivered NPMRDS data covers NHS defined by HPMS data 2-year prior and contains HPMS attributes of 2-year prior. After the completion of HPMS conflation by February 28, the final updated NPMRDS data would cover NHS defined by HPMS data 1-year prior and contains HPMS attributes of 1-year prior.

• The update to NPMDS data in the aspect of HPMS NHS data conflation includes the daily released Division level data, TMC level, Weekly, Monthly and Annual nationwide summary data, Division Performance Network and TMC Performance Network, and all other performance data specified in this SOW as the optional tasks should they elected to be exercised. The NPMRDS data update in this regard implies actions towards re-delivering of any earlier delivered data before HPMS conflation.

• Since the NHS scope including all related HPMS attributes may be changed, though slightly, compared with the last updated one that was used to collect NPMRDS travel time data started from the earlier of the year, the update to the entire NPMRDS data by February 28 implies that the Raw NPMRDS data collection shall cover more than the NHS scope defined, or the historical Raw NPMRDS data since day one of the year for all the newly added NHS roadways must be collected after the NHS scope is updated.

• The contractor must identify and summary what data has been updated or affected, and what had been removed or added due to conflation by February 28, accordingly, notify the NPMRDS data user community about the changes to the earlier deliveries.

Part 2c: Data Access and Sharing, and Technical Support

Data Access

The Contractor must host and provide the infrastructure for data storage and access of all NPMRDS data stated in this SOW. The Contractor must make the storage and access perpetually available to NPMRDS data users.

The access of the NPMRDS must be through a user-friendly web application, which is often referred as Data Portal in this contract, with GIS mapping as the essential interface.

The spatial and temporal selection for data load must be straightforward and intuitive for entry level users. The data portal must provide a clear UI navigating users to download different types of NPRMDS data as further stated below:

• Download Raw MPNRDS data

• Download PM3 NPMRDS data

• Download Division Performance Network

• Download TMC Performance Network

• Download Weekly, Monthly, and Annual Nationwide Summary Data

• Download Monthly, Quarterly and Annual Performance Measures

The functionalities and availabilities of functions will be subject to user types where FHWA must have access to all functionalities, state DOTs and MPOs must be able to download data for their state (Raw NPMRDS, PM3 NPMRDS, Division Performance Network, and TMC performance Network).

The Contractor must provide the access of NPMRDS data via REST APIs with access key management functionalities to control the access in terms of who can access what type of data within what timeframes. The key must not be perpetual and must be expired certain time after it is assigned. The grant and re-grant the REST API access key is identical to the access of NPMRDS data from the data portal.

The data portal must be ready to expand to cover requirements specified in the optional tasks should they elected to be exercised. For example, to allow users to specify both spatial and temporal selections via Work Zone Exchange Data Files, and to compute specific performance metrics for these selections.

Data Sharing

The Contractor must ensure the NPMRDS data are accessible to all users including FHWA, State, DC, and PR DOTs, MPOs/COGs, other operating administrations at the US DOT, and other Federal partners, and authorized contractors by the forementioned entities working on TPM work and program. The Contractor must lead and manage the access through an authorized users program ensuring all signed the Data Sharing Agreements (DSA), and all authorized users have the right to aggregate the Division/TMC 5-minute and 15-minute interval daily level data and share their results with the public regarding any products (e.g. performance measures) derived from the original data. The approved NPMRDS data users who have signed the DSA will not have the right to use the NPMRDS data set for any project not authorized by FHWA, state DOTs, MPOs, other operating administrations at the US DOT, or other Federal partners.

The approved NPMRDS data users who have signed the DSA may store the Division/TMC 5-minute and 15-minute daily level data, and the Division Performance Network or the TMC Performance Network for approved project related analyses. The stored NPMRDS data must be removed from the persistent storage after the project is complete or expired.

While the approved NPMRDS data users who have signed the DSA must not disseminate the Division/TMC 5-minute/15-minute daily travel time data, FHWA will release both the Division and TMC Performance Networks to the public to improve public accountability in addition to the Contactor’s Portal/API/Mechanism to releases the Performance Network to authorized users.

The Contractor must implement user and data access control management mechanism in the data portal. Upon approval by FHWA COR, the Contractor must grant data access via the data portal to all authorized users including FHWA, State, DC, and PR DOTs, MPOs/COGs, other operating administrations at the US DOT, and other Federal partners, and authorized contractors.

The FHWA, public transportation agencies and officially designated representatives must have the right to use the NPMRDS data provided under this contract for transportation planning, operational and safety research and development analyses, data quality validation analyses, and all other internal organization applications.

The Contractor must provide unique online accesses for all users including multiple users from the same agencies, entities or authorized contractors.

The Contractor may define reasonable restrictions to safeguard the commercial value of the Contractor’s vehicle probe data, but any such restrictions must not impede the use of the data for the envisioned purposes.

The Contractor must track the usage of the NPMRDS data and provide FHWA with quarterly usage report. The report should identify users from each agency, entities or authorized contractors with users email addresses and other relevant data gathered, access frequencies, and data used.

The Contractor must remove users who are no longer authorized to access the NPMRDS.

Such removal must also be reported via the quarterly usage report.

The quarterly usage report must include the following fields:

Worksheet: Cumulative Active Users with activation dates)

• Name of Agency

• Type of Agency (Federal, International, State, MPO)

• User first name

• User last name

• User E-mail

• User phone number

• Activation date

• # of times accessed the data during the quarter from the data portal

• General statistical metrics for REST API accesses

Worksheet (Cumulative Deactivated Users with deactivation dates)

• User agency

• Username

• User email address

• Date of deactivation

Technical Support

The Contractor must provide timely and competent professional technical support to FHWA, all State, DC, and PR DOTs, MPOs/COGs, other operating administrations at the US DOT, and other Federal partners involved in transportation analyses using the NPMRDS data. Technical support must be in the form of e-mail or web-based communication (e.g., Google Meet, Zoom). Timely manner support means same day answers and no later than COB next day services. Competent professional technical support means solution orientated answers.

Primary areas of technical support include:

1. Data set elements

2. Data provision/access

3. Data coverage and/or data quality

4. Getting started with the data (i.e. mapping, conflation assistance, and simple analysis of the data)

5. GIS Dataset/GIS assistance in conflating the data

6. Answering data user questions

Technical support also includes but is not limited to assistance in downloading data, accessing data via REST APIs, using data such as deriving simple performance measurements, and visualizing data via commonly used GIS tools.

The Contractor must provide a quick start guide to users as a primer for data usage. The quick start guide shall include 1) the dataset metadata – what variables (date items), variable definitions, units, variable sources are, 2) variable relationships to other variables, 3) steps and equations deriving speeds including the percentile speed computation for different time periods, 4) steps and equations deriving all stated national level weekly/monthly/annual summary data, and 5) how to download the data from the contractor platform including potential file sizes, file format, and other information to make the download and usage of the data efficiently. This user guide must not contain any proprietary information affecting public release. The user guide may be distributed publicly by FHWA.

The Contractor must organize and host the FHWA’s biannual (twice a year) NPMRDS user webinar for discussion, questions and…