RFQ HPPI260001PR National Road Network Project.pdf
PDF 515 KB Posted
- Attached to
- National Road Network Project
- Solicitation number
- HPPI260001PR
About this file
This is a Request for Quotation (RFQ) from the Federal Highway Administration (FHWA) for the National Road Network (NRN) Project. The small business set-aside contract is for defining a product specification and creating a conceptual model of a national-level geospatial road network dataset. The NAICS code is 541370 (Surveying and Mapping), with a size standard of $19.0 million. The period of performance is twelve months from the date of award, with a firm fixed price payment structure across multiple contract line items (CLINs).
Key project objectives include developing a consistent national spatial road network that addresses connectivity between interstate and intrastate borders, represents multi-carriageway roadways, and ensures spatial accuracy. The contractor will work with ten pilot states in the Southeast Region to research challenges in creating the network. Deliverables include documentation of business/technical requirements, data source identification, product specification, validation criteria, update procedures, and a final comprehensive report. The solicitation was released on January 13, 2026, with technical questions due by February 3, 2026, and quotations due by February 10, 2026. Optional tasks may include external presentations about the project.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Amendment A001 HPPI260001PR_National Road Network Project .pdf | ||
| NRN Questions and Answers 02062026.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
REQUEST FOR QUOTATION (RFQ)
Issuing Office: United States Department of Transportation
Federal Highway Administration (FHWA) Office of Acquisition & Grants Management (HCFA)
1200 New Jersey Avenue, SE Washington, DC 20590-0001
Agency Contact: Josephine Helms, Contracting Officer Email: josephine.helms@dot.gov
RFQ Number: HPPI260001PR
Title: National Road Network Project
Solicitation Release Date: January 13, 2026
Technical Questions Due Date: February 3, 2026, 4:00 p.m. ET
Quotation Due Date: February 10, 2026, 4:00 p.m. ET mailto:josephine.helms@dot.gov
PART I
INFORMATION AND INSTRUCTIONS FOR PREPARATION OF QUOTATIONS
This is a combined synopsis/solicitation for commercial products or commercial services prepared in accordance with the format in Revolutionary Federal Acquisition Regulation Overhaul (RFO)part 12. This announcement constitutes the only solicitation; proposals are being requested and a written solicitation will not be issued.
This is an Open Market, Firm Fixed Price (FFP), request for quotation (RFQ). This solicitation is prepared in accordance with Federal Acquisition Regulation (FAR) Part 12, Acquisition of Commercial Items, in conjunction with the policies and procedures for solicitation, evaluation, and award as prescribed in FAR 13, Simplified Acquisition Procedures (SAP). The solicitation document and incorporated provisions and clauses are those in effect through Federal Acquisition Circular (FAC) 2025-06.
This solicitation is a small business set-aside. The North American Industry Classification System (NAICS) code is 541370 Surveying and Mapping, Size Standard $19.0 million. A responsible quoter is one whose quotation conforms to the solicitation and will be most advantageous to the Government. It is the contractor’s responsibility to be familiar with applicable clauses and provisions. FAR Provisions and Clauses may be viewed and/or downloaded from http://www.acquisition.gov/far.
All contractors must have a current active registration in the System for Award Management (www.SAM.gov) at the time of quote submission in order to be eligible to receive an award under this RFQ.
System updates may lag policy updates. The System for Award Management (SAM) may continue to require entities to complete representations based on provisions that are not included in DOT solicitations. Examples include:
• 52.222-25, Affirmative Action Compliance, and
• 52.212-3(d), Offeror Representations and Certifications—Commercial Products and Commercial Services.
Contracting officers will not need to consider these representations when making award decisions or enforce requirements. Entities are not required to, nor are they able to, update their entity registration to remove these representations in SAM.
http://www.acquisition.gov/far http://www.sam.gov/
INSTRUCTIONS FOR PREPARATION OF QUOTATIONS
In responding to this RFQ, quotations MUST include the following:
1. Technical Quote: Narrative discussion addressing the quoter’s technical approach and technical merit factors identified in Part I, Section 6.0, Evaluation of Quotations. A description of how the Statement of Work or Performance Work Statement requirements will be completed.
2. Price Quote: Submitted pricing in the format of the Schedule of Service, Contract Line Item Number (CLIN) Structure table shown in Part II.
3. Past Performance: The Government, at its sole discretion, will seek past performance information from sources such as the Government’s Contractor’s Performance Assessment Reporting System (CPARS).
4. Organizational Information: Quotations shall include the following mandatory business information regarding your company in the body of the cover email message:
• Confirmation your company accepts government purchase orders
• Business Size under NAICS 541370
• Unique Entity Identifier (UEI) and Electronic Funds Transfer (EFT) Indicator (if applicable):
• Federal Tax Identification Number (TIN) (9-Digits)
• Correct Mailing Address for the order (include name, telephone, email address); Note:
Mailing address and entity name shall match the information in www.sam.gov
5. Instructions for Preparation of Quotations: Quotation materials must be organized as follows: Section 1 - Technical Quotation and Section 2 - Price Quotation. All sections must be clearly separated from the other (i.e., separate electronic files), price information must only be supplied in the Price Quotation, the Technical Quotation must not contain any price information.
To be acceptable, the quotation must meet all of the requirements set forth in the Statement of Work (SOW).
• Quotations shall be submitted electronically as Adobe (.pdf) files with the technical capability, pricing, past performance, and organizational information sections submitted in a SINGLE email whose size shall not exceed 10 Megabytes. Do not include marketing materials.
• Quotations must be formatted to print on 8½ x 11-inch paper without any additional scaling.
• Margins (Top, Bottom, Right and Left) no smaller than 1" (headers and footers are allowed in the margins)
• Times New Roman size 11 font must be used.
• Price Quotations must be submitted in a format readable by MS Excel and PDF formats. Technical quotations must be submitted in a text searchable PDF format.
• Section 1 Technical Quotation is limited to a total of 15 pages. Resumes are excluded from the Technical Quotation page limitation but are themselves limited to no more than two pages each. The table of contents and cover page are also excluded from the overall page limit.
• Section 2 Price Quotation does not have a page limitation.
The subject line of your email and all correspondence must include the RFQ number found on the cover page. Send to Josephine.Helms@dot.gov and CC Carolyn.lethert@dot.gov.
6. Evaluation of Quotations: The Government will evaluate quotes and make a best value award decision based on the following factors rated. (A) Technical Capability; (B) Price;
and (C) Past Performance. Technical and past performance, when combined, are more important than cost or price. The ultimate award decision will be made based on a determination of overall best value, each of the three factors considered.
Technical Capability shall be based on the factors below:
The Offeror’s approach to performing the requirements and its capability to successfully perform the contract will be evaluated.
Proposals will be evaluated based on the following:
Note: All bulleted items noted below are considered equal in the overall evaluation of Technical Capability.
• Ability to clearly describe the task order objectives, needs, and ways they will be addressed;
• Demonstrated sound, feasible, and achievable technical approaches to accomplishing the requirements of the task order;
• Demonstrated technical and subject matter expertise of the proposed team, as evidenced by academic credentials and professional experience;
• Demonstrated recent successful experience in accomplishing work associated with the SOW identified objectives and tasks;
• Demonstrated experience in scenic byways projects or programs, mapping and GIS, and outreach, including byways promotional materials, educational materials, and program information.
• Acceptable and reasonable contingency plans to replace key personnel over the period of performance without adversely affecting performance;
• Presented specific performance metrics that may be used to gauge progress for the successful delivery of task requirements and/or status reports that can be used to monitor performance of the requirement;
• Demonstrated organizational commitments; and
• Demonstrated collaborative approaches and partnerships.
NOTE: Failure to furnish all information required above may result in your quotation being considered non-responsive and eliminated from further consideration.
mailto:Josephine.Helms@dot.gov mailto:Carolyn.lethert@dot.gov
PART II
SCHEDULE OF SERVICES
The Contractor shall furnish all supplies/services to perform the tasks described under this purchase order titled, National Road Network Project. The Contractor shall furnish all supplies/services in support of the mission of the FHWA.
This is an Open Market RFQ for a firm fixed price contract, Request for Quotation and Quoters shall quote a total price breakdown utilizing the CLIN chart below.
CLIN TASK DESCRIPTION PRICE
00101 1 Firm fixed price for completion of kick-off meeting tasks described in Section 1.3, Task 1 “Meetings and Coordination.”
00101
*Firm fixed price for completion of monthly reporting tasks described in Section 1.3, Task 1 “Meetings and Coordination.”
00101
Firm fixed price for completion of working sessions tasks described in Section 1.3, Task 2 “NRN Specification Requirements Documentation.”
00101
Firm fixed price for completion of final business/technical specification report tasks described in Section 1.3, Task 2 “NRN Specification Requirements Documentation.”
00101
Firm fixed price for completion of the data source report tasks described in Section 1.3, Task 3 “Identify Sources.”
00101
Firm fixed price for completion of the metadata input tasks described in Section 1.3, Task 3 “Identify Sources.”
00101
Firm fixed price for completion of the NRN specification document tasks described in Section 1.3, Task 4 “Create Product Specification and Conceptual Model of the
NRN.”
00101
Firm fixed price for completion of the working model development and demonstration tasks described in Section 1.3, Task 4 “Create Product Specification and Conceptual Model of the NRN.”
00101
Firm fixed price for completion of the review and validation document tasks described in Section 1.3, Task 5 “Validation and enhancement.”
00101
Firm fixed price for completion of the annual update workflow document tasks described in Section 1.3, Task 6 “Update Procedures.”
00101
Firm fixed price for completion of the workflow demonstration tasks described in Section 1.3, Task 6 “Update Procedures.”
00101
Firm fixed price for completion of the final report and product tasks described in Section 1.3, Task 7 “Final Reports and Products.”
10101 8
Firm fixed price for completion of the NRN presentation tasks described in Section 1.3, Optional Task 8 “External Presentations.”
10201 8
Travel costs reimbursement associated with completion of tasks described in Section 1.3, Optional Task 8 “External Presentations” not to exceed $10,000.
$10,000
TOTAL PRICE: $
*NOTE: Unless otherwise negotiated and approved, the contractor will be paid the FFP of each CLIN upon successful completion and Government acceptance. The contractor may also request milestone payments in accordance with work completed and accepted by the Government.
Satisfactory completion and acceptance will be made by the Contracting Officer’s Representative (COR). The contractor should provide a suggested Milestone Payment Schedule should they wish to be paid each month for the monthly reporting tasks described in Section 1.3, Task 1 “Meetings and Coordination” and/or for other tasks.
Part III
Statement of Work (SOW)
Federal Highway Administration
Office of Highway Policy Information
National Road Network (NRN) Project
1.0 OVERVIEW
The Government intends to award a non-personal services purchase order to define a product specification and create a conceptual model of the National Road Network (NRN). The Government will not exercise any supervision or control over the service providers performing the services herein. Such service providers shall be accountable solely to the Contractor who, in turn is responsible to the Government as defined in this Statement of Work (SOW). The Contractor shall perform to the standards herein.
1.1 BACKGROUND
In December 2019, Congress provided FHWA with an appropriation to create a national-level geo-spatial data set using data already collected under Highway Performance Monitoring System (HPMS). Congressional guidance directed FHWA to ensure that this dataset support interagency use and address three areas of interest:
o connectivity of the networks at interstate and intrastate borders, o spatial representation of multi-carriageway roadways including attribution, and o spatial accuracy of the network.
In 2022 FHWA established the National Road Network (NRN) Pilot with the goal of informing the development of a national spatial network of all roads that has a consistent data standard with both intrastate and interstate connectivity. FHWA is working with ten pilot States to research and address the challenges of achieving these goals. Each pilot State received grants and have identified specific challenges in creating a national network.
FHWA intends to create a product specification and conceptual model NRN product using the research conducted in the pilot States and business requirements provided in the congressional authorization. This conceptual model will address how the NRN can be updated and maintained as future HPMS data are received. Shortly after the NRN conceptual model is developed and accepted, FHWA will apply the conceptual model to an NRN including all States, District of Columbia, and territories through automated processes and procedures via a future contract.
State DOTs currently provide spatial data to the All-Road Network of Linear Referenced Data (ARNOLD) database. The database represents all public roads within their respective States through the HPMS, which geolocates mileage, usage, performance, and condition data. ARNOLD provides the ability to map and visualize data critical for policy decision makers and provides a tool to evaluate health, safety, and status of the nation’s highways. This data is an important asset to transportation research and broader economic communities at-large.
However, ARNOLD does face challenges. As State DOTs provide data independently, inconsistent connectivity between neighboring States limits data use for interstate analysis, emergency management and relief, and freight flow. Another challenge is inconsistent State reporting standards regarding the extent (limiting local data) and complexity (divided facility representation) of data.
1.2 OBJECTIVE
The objective of this contract is to define a product specification and data structure to represent the NRN. The deliverables from this project will be documentation that defines a spatial framework to geolocate features and attributes to support safety analysis, planning applications, freight analysis, conditions, emergency response, asset management and project locations related to all public roads in the United States.
Using the defined specification, a conceptual model will be created with data from the HPMS and other secondary sources. The working conceptual model will be demonstrated showing how it addresses the business requirements listed above for pilot states that have been identified for the NRN initiative. The specification will define data validation criteria and network maintenance procedures to be used as annual HPMS and other sources are received.
1.3 DETAILED REQUIREMENTS
The Contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to conduct the work.
Task 1 – Meetings & Coordination
FHWA will facilitate the scheduling of meetings for the NRN Team members and Contractor throughout the entire project. The meetings will be held via Microsoft (MS) Teams with coordination via email. The Contractor will take notes during all meetings and collect, distribute, and maintain these notes for the team in MS Word or Excel, if necessary for data, charts, etc. in an easily accessible electronic format.
The Contractor shall participate in a kick-off meeting via MS Teams with the NRN Team and Contracting staff within ten business days of the contract’s effective date. During this meeting, the parties shall identify and introduce key staff members, review the tasks and requirements, address any questions or concerns, and review the timeline for the work to be performed.
The Contractor agrees to attend progress meetings, as requested by FHWA, to review and discuss the Contractor’s performance and any difficulties being encountered in the successful execution of the tasks. Appropriate action shall be taken to resolve outstanding issues. The Contractor shall provide monthly reports documenting all activities undertaken and any issues that may have arisen during the reporting period. The FHWA will use the monthly reports to determine whether there is a need for a progress meeting.
Deliverables
1. Meetings
a. Meetings notes should be disseminated to the NRN Team no later than three business days after a meeting.
2. Kick-off Meeting
a. The Contractor will document the kick-off meeting and disseminate these notes to the NRN Team seven business days after the kick-off meeting.
3. Monthly Reports
a. These monthly reports shall be due for each month of the performance period, and due no later than the tenth business day of the following month. These should be sent to the NRN Team lead and the Contracting Officer Representative (COR).
Task 2 – NRN Specification Requirements Documentation
The contractor shall review the provided business stake holder requirements in terms of scope, extent, content of what the NRN must possess. The following is a general list of the known business requirements. However, adjustments may be made during clarification sessions with the NRN Team.
General:
a. Scope: Roads in the United States, Territories, and the District of Columbia
b. Extent: All public roads, including local roads
c. Representation:
i. Facility and divided facility (dual carriageway)
ii. Intersection and interchange model.
d. Measures:
i. Length
ii. Lane-length
iii. Vehicle distance traveled
e. Source: Annual acquisition of data through State DOT Data Partners and other available sources. HPMS is the primary source for this effort.
f. Connectivity: Topologically connected both interstate and intrastate
g. Referencing: Linear referencing system support
h. Update: Incremental update process.
i. Purpose: The NRN is an analysis and planning network and not to be used for real time navigation.
Business use cases:
The NRN will support the following as the system of record for the:
i. National Highway System (NHS)
ii. Strategic Highway System (STRAHNAT)
iii. National Network (NN)
iv. National Highway Freight Network (NHFN)
j. Pavement Condition and Ride Quality
k. Emergency planning and response
l. Safety analysis
m. Freight movement and analysis
n. Asset management, including structures and ferry boats
o. Project locations
Deliverables
1. The contractor shall organize and manage working sessions with the NRN team for the purpose of clarifying and refining the technical requirements.
2. The contractor shall provide documentation with the business/technical requirements.
3. The Contractor shall demonstrate the final business/technical specification.
a. The report shall outline the technical requirements, cross-walked with the business requirement.
Task 3- Identify Sources
HPMS has been identified as a primary source for the NRN. There are some potential attributes or features that may be appropriate to go beyond HPMS, for example ferry boats, bridges, road names, etc. These sources need to be identified and then explore the feasibility and limitations on their use. Sources may need licensing agreements or memorandum of understanding between federal agencies. Once identified and evaluated, properly document metadata and point of contacts for the potential source.
Deliverables
1. The contractor shall provide a report with the identified data sources and the point of contact for the source.
2. The contractor shall provide the input to the metadata for the identified source. The metadata should include any limitation on the release or use of the data.
Task 4 –Create Product Specification and Conceptual Model of the NRN
The contractor shall develop a specification for the NRN based on the business/technical requirements established in Task 2. This shall be done in coordination and collaboration with FHWA throughout the process. FHWA has been working with ten NRN pilot State DOTs in the Southeast Region of the U.S. (AL, DC, DE, FL, GA, MD, MS, NC, SC, and VA). Data from the HPMS is readily available. Other potential sources may need to be acquired as noted in task 3.
The specification shall outline the details of the data structure of the NRN. It will include the geometry and non-geometric attributes that make up the network product.
This task also will include a working conceptual model with data from the pilot states.
The task will conclude with a demonstration to the NRN Team and other stakeholders showing how the conceptual model addresses the business/technical requirements defined in Task 2.
Deliverables
1. The contractor shall provide a documented NRN specification.
2. The Contractor shall develop a working conceptual model, including pilot states data from HPMS.
3. The contractor shall demonstrate the conceptual model to the NRN Team.
Task 5 – Validation and enhancement
The specification shall define the validity of the data. Criteria will need to be established for a quality data review. For example, determining “dirty” geometry, missing and invalid data and unconnected routes where expected. There needs to be opportunities within the criteria where automated “fixes” can be applied, where appropriate and possible. For example, a rule could be identified to snap unconnected routes together that are not within a specified tolerance.
Deliverables
1. Establish and document review and validation criteria to be used as basis for developing an automated validation engine.
Task 6 – Update Procedures
The NRN is to be updated on an annual basis as new ARNOLD data are received through the HPMS. The specifications need the capability to accept those temporal changes though an incremental/transactional process. The update procedure should have an automated process that works with the database structure to receive these changes.
Deliverables
1. The contractor shall provide a workflow that describes the annual update procedures for the NRN through an incremental/transactional process.
2. The contractor shall demonstrate to the NRN Team the feasibility of the workflow with pilot data.
Task 7 – Final Report & Products
Completion of Tasks 2 through 6 documents the business/technical requirements and NRN specifications. This documentation shall be compiled and edited into a single report detailing the NRN specifications.
Deliverables
1. The contractor shall compile all documentation resulting from Tasks 2 through 6 into a single report, that includes:
a. Data specification
b. Validation criteria
c. Update procedures
2. The discussion of the NRN conceptual model will include example data from the pilot States.
Task 8 – External Presentations (optional)
FHWA may promote the NRN conceptual model at professional conferences. There may be opportunities for the contractor to assist in developing and presenting at these events.
Deliverables
1. Assist FHWA in developing presentations regarding the NRN specification and conceptual model.
2. Assist FHWA in presenting the NRN specification and conceptual model at professional events.
2.0 PERIOD OF PERFORMANCE
The period of performance, including the optional task if executed, shall be for twelve
(12) months from the date of award.
3.0 GENERAL
3.1 HOURS OF OPERATION
Under this task order, the Contractor is responsible for conducting business, between the hours of 8:00 a.m. – 5:00 p.m. Eastern Time. Monday thru Friday except Federal holidays or when the Government is closed due to local or national emergencies, administrative closings, or similar Government directed closings. The Contractor may propose alternate work hours to be approved by the COR. The Contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this SOW when the Government is not closed for the above reasons.
When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the workforce are essential.
3.2 PLACE OF PERFORMANCE
The work to be performed under this task order shall be performed at the contractor’s facility.
3.3 PHYSICAL SECURITY
Not Applicable
3.4 SPECIAL QUALIFICATIONS
Contractor support personnel shall possess specialized skills in data management and analytics, converting data into visualizations, as well as experience with Web, multimedia, or video design software. Contractor support personnel shall possess subject matter expertise in the mapping of roadway networks.
3.5 PERIODIC PROGRESS MEETINGS
The contractor agrees to attend progress meetings requested by the contracting activity.
The COR and other Government personnel shall meet regularly with the contractor to review the contractor’s performance. At these regularly scheduled meetings the COR will apprise the contractor of how the Government views the contractor’s performance and the contractor shall apprise the Government of problems, if any, being experienced.
Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the Government.
3.6 IDENTIFICATION OF CONTRACTOR EMPLOYEES
All contractor personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by contractors suitably marked as contractor products or that contractor participation is appropriately disclosed. Contractors shall wear badges identifying them as contractor personnel where on-site at the Government’s facility.
3.7 CONTRACTOR TRAVEL
As discussed in optional Task 8, it is anticipated that the contractor may travel during the period of performance for presentation(s). Travel may be funded at the discretion of the Task Manager. All travel requires Government approval / authorization and notification to the Task Manager.
Travel costs shall be reimbursable in accordance with the Federal Travel Regulations and are not to exceed $10,000.
3.8 OTHER DIRECT COSTS
Not Applicable.
3.9 ORGANIZATIONAL CONFLICT OF INTEREST
Contractor and subcontract personnel performing work under this task order may receive, have access to, or participate in the development of proprietary or source selection information (e.g. cost or pricing information, budget information or analyses, specifications, or work statements, etc.) or perform evaluation services which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in Federal Acquisition Regulations Subpart 9.5. The contractor shall notify the CO immediately whenever he / she becomes aware that such access or participation may result in any actual or potential OCI and may merit the submittal of a plan to the CO to avoid or mitigate any such OCI. This mitigation plan would be determined to be acceptable solely at the discretion of the CO, and in the event the CO unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the CO may affect other remedies as he or she deems necessary, including prohibiting the contractor participation in subsequent contracted requirements which may affected by the OCI.
3.10 PHASE IN / PHASE OUT PERIOD
Not Applicable
3.11 DATA RIGHTS
The Government has unlimited rights to all documents / material produced under this task order. All documents and materials, to include the source code of any software produced under this contract, shall be Government owned and the property of the Government with all rights and privileges of ownership / copyright belonging exclusively to the Government. These documents and materials may not be used or sold by the contractor without written permission from the CO. All materials supplied to the Government shall be sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights.
4.0 GOVERNMENT FURNISHED EQUIPMENT AND SERVICES
4.1 SERVICES
Not Applicable
4.2 EQUIPMENT AND FACILITIES
No equipment or facilities will be provided.
4.3 MATERIALS
Not Applicable
5.0 APPLICABLE PUBLICATIONS
Not Applicable.
6.0 ATTACHMENT / TECHNICAL EXHIBIT LIST
6.1 Technical Exhibit 1 – Deliverables Schedule
6.2 Technical Exhibit 2 – Section 508 Requirements
6.1 TECHNICAL EXHIBIT 1 – Deliverables Schedule
TASK DELIVERABLE Number of
Copies DUE Date
Task 1 Meetings n/a Initial kick-off within 10 days after contract award date, then as requested
Meeting Minutes, 1 each (electronic)
Within 5 days after meetings
Monthly progress tracker 1 each (electronic)
Monthly, no later than the tenth business day of the following month
Task 2 Working Sessions with the NRN Team n/a Within a month of contract award date.
Documentation of requirements 1 each Within 2 months of
TASK DELIVERABLE Number of Copies
DUE Date
(electronic) contract award date.
Demonstration of the business/ technical requirements of the conceptual model n/a Within 3 months after
Task 3
Identify sources report 1 each (electronic)
Within 3 months after contract award date.
Input to the metadata for identified sources
1 each (electronic)
Within 3.5 months after contract award date.
Task 4 Documented NRN conceptual model specification
1 each (electronic)
Within 4.5 months after contract award date.
Working NRN conceptual model n/a Within 4.5 months after contract award date.
Demonstration of conceptual model n/a Within 4.5 months after contract award date.
Task 5 Establish and document review and validation criteria
1 each (electronic)
Within 5.5 months after contract award date.
Task 6 Workflow describing annual update procedures for NRN through incremental/ transactional process
1 each (electronic)
Within 6 months after contract award date.
Demonstrate to the project team feasibility of the workflow with pilot data n/a Within 6 months after
Task 7
Compile all documentation resulting from Tasks 2 through 6 into a single report.
1 each (electronic)
Within 7 months after contract award date.
NRN conceptual model n/a Within 8 months after contract award date.
Task 8
OPTIONAL
Assist FHWA in developing presentations regarding NRN conceptual model
1 each (electronic)
Within 12 months after contract award date.
Assist FHWA in presenting NRN conceptual model at professional events n/a Within 12 months after
Deliverables Shall Be Sent To:
Stephen Hickok Federal Highway Administration
1200 New Jersey Avenue, SE Washington, DC 20590-9898
Or to: stephen.hickok@dot.gov
All deliverables must be Google documents (Docs, Sheets, or Slides), Microsoft Office (2010 or later), Adobe PDF, or applicable visualization software (ArcGIS, Tableau, etc.)
format. The contractor shall provide sample review materials to ensure the final documents, and visual aids will be of acceptable quality and format for the Government.
Draft materials shall be distributed electronically via email to the COR. The Government’s comments shall be incorporated into the final materials, or feedback shall be provided to the COR to request clarification or resolution of conflicting comments.
There shall be no references to the contractor, including contractor logos, on any of the materials. Department of Transportation Form F 1700.7 or similar acknowledgement can be prepared by the contractor for inclusion with the materials. Approval by the COR is required before being included with the final materials.
6.2 TECHNICAL EXHIBIT 2 –
REQUIREMENTS FOR IMPLEMENTING SECTION 508 STANDARDS
The following applies to all FHWA Contracts issued on or after January 18, 2018 containing Information and Communication Technology (ICT) as a deliverable. In addition to the work requirements specified in this statement of work, vendors must ensure that all ICT that they prepare will meet the requirements of Section 508 of the Rehabilitation Act and the Information and Communication Technology (ICT) Final Standards and Guidelines (508 Refresh) at 36 CFR Part 1194. As defined in the 508 Refresh, at 36 CFR Part 1194, Appendix A, E103.4, ICT is “Information technology and other equipment, systems, technologies, or processes, for which the principal function is the creation, manipulation, storage, display, receipt, or transmission of electronic data and information, as well as any associated content.
Examples of ICT include but are not limited to computers and peripheral equipment;
information kiosks and transaction machines; telecommunications equipment; customer premises equipment; multifunction office machines; software; applications; Web sites;
videos; and electronic documents.” Section 508 requires that all electronic products prepared for the Federal Government be accessible to persons with disabilities, including those with vision, hearing, cognitive, and mobility impairments.
Applicable Standards:
• Appendix A to Part 1194 – Section 508 of the Rehabilitation Act: Application and Scoping Requirements
• Appendix B to Part 1194 – Section 255 of the Communications Act: Application and Scoping Requirements
• Appendix C to Part 1194 – Functional Performance Criteria and Technical Requirements mailto:stephen.hickok@dot.gov https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines#appendix-a https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines#appendix-a https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines#appendix-a https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines#appendix-b https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines#appendix-b https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines#appendix-b https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines#appendix-c https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines#appendix-c https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines#appendix-c
Section 508 Refresh standards are available at https://www.access- board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh.
Before final acceptance of any ICT item, including updates and replacements, if the contractor claims its products or services satisfy the applicable Revised 508 Standards specified in the statement of work, and the contracting officer’s representative, in coordination with the contracting officer, determines that any furnished ICT item is not in compliance with such requirements, the contracting officer will promptly inform the contractor in writing of the noncompliance. The contractor shall, at no cost to the agency, repair or replace the non-compliant products or services within the period specified by the contracting officer.
PART IV
CONTRACTOR PERFORMANCE ASSESSMENT REPORTING SYSTEM (CPARS)
Contractor Performance Evaluations
(a) Interim and final evaluations of contractor performance will be prepared on this contract in accordance with FAR 42.1502 and TAM 1242.1502. The final performance evaluations will be prepared at the time of completion of work.
(b) The contractor can elect to review the evaluation and submit additional information or a rebuttal statement. The contractor will be permitted 60 calendar days to respond. Contractor response is voluntary. If the contractor does not respond within 60 days, the Government will presume that the contractor has no comment. Any disagreement between the parties regarding an evaluation will be referred to an individual at a level above the CO, whose decision is final.
(c) Copies of the evaluations, contractor responses, and review comments, if any, will be retained as part of the contract file, and may be used to support future award decisions.
The Federal Highway Administration utilizes the contractor Performance Assessment Reporting System (CPARS) to record and maintain past performance information. CPARS is used to document contractor performance information that is required by Federal Regulations.
CPARS reference material can be accessed at http://www.cpars.gov/.
The registration process requires the contractor to identify an individual that will serve as a primary contact. This individual will be authorized access to the evaluation for review and comment. In addition, the contractor is encouraged to identify a secondary contact in the event the primary contact is unavailable to process the evaluation within the required 60-day time period. After the FHWA Contract Specialist registers the contract in CPARS, the contractor will receive a system generated e-mail notifying him/her that the contract is registered. A system generated e-mail will also provide the contractor with a User ID if the person does not already have a CPARS User ID.
Once a performance evaluation has been prepared and is ready for comment, the contractor representative will receive a system generated e-mail notification that the performance evaluation is electronically available for review and comment. The contractor representative will receive an automated e-mail whenever an assessment is completed and can subsequently retrieve the completed assessment from CPARS.
Contractors may access evaluations at http://www.cpars.gov/ for review and comment in
CPARS.
https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh
PART V
FEDERAL ACQUISITION REGULATION (FAR) [AND TRANSPORTATION
ACQUISITION REGULATION (TAR)] PROVISIONS AND CLAUSES
PROVISIONS
FAR & TAR PROVISIONS INCORPORATED BY REFERENCE
52.252-1 Solicitation Provisions Incorporated by Reference (Feb 1998) This solicitation incorporates one or more solicitation provisions by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. The offeror is cautioned that the listed provisions may include blocks that must be completed by the offeror and submitted with its quotation or offer. In lieu of submitting the full text of those provisions, the offeror may identify the provision by paragraph identifier and provide the appropriate information with its quotation or offer. Also, the full text of a solicitation provision may be accessed electronically at https://www.acquisition.gov/far
52.203-11 Certification and Disclosure Regarding Payments to Influence Certain
Federal Transactions (SEP 2024) 52.203-18 Prohibition on Contracting with Entities that Require Certain Internal
Confidentiality Agreements or Statement-Representation (JAN 2017) 52.204-7 System for Award Management (NOV 2024)(DEVIATION Sept 2025) 52.209-2 Prohibition on Contracting with Inverted Domestic Corporations –
Representation (NOV 2015)(DEVIATION SEP 2025) 52.212-1 Instructions to Offerors -- Commercial Products and Commercial Services
(SEP 2023)(DEVIATION SEP 2025)
52.222-56 Certification Regarding Trafficking in Persons Compliance Plan(OCT
2025)(DEVIATION OCT 2025)
52.229-11 Tax on Certain Foreign Procurements -- Notice and Representation (Jun
2020) 1252.239-71 Information Technology Security Plan and Accreditation (Nov 2022)
FAR & TAR PROVISIONS IN FULL TEXT
52.209-7 Information Regarding Responsibility Matters (Oct 2018)(DEVIATION SEP
2025)
(a) Definitions. As used in this provision— Administrative proceeding means a non-judicial process that is adjudicatory in nature in order to make a determination of fault or liability (e.g., Securities and Exchange Commission Administrative Proceedings, Civilian Board of Contract Appeals Proceedings, and Armed Services Board of Contract Appeals Proceedings). This includes https://www.acquisition.gov/far administrative proceedings at the Federal and State level but only in connection with performance of a Federal contract or grant. It does not include agency actions such as contract audits, site visits, corrective plans, or inspection of deliverables.
Federal contracts and grants with total value greater than $10,000,000 means—
(1) The total value of all current, active contracts and grants, including all priced options; and
(2) The total value of all current, active orders including all priced options under indefinite-delivery, indefinite-quantity, 8(a), or requirements contracts (including task and delivery and multiple-award Schedules).
Principal means an officer, director, owner, partner, or a person having primary management or supervisory responsibilities within a business entity (e.g., general manager; plant manager; head of a division or business segment; and similar positions).
(b) The offeror □ has □ does not have current active Federal contracts and grants with total value greater than $10,000,000.
(c) If the offeror checked "has" in paragraph (b) of this provision, the offeror represents, by submission of this offer, that the information it has entered in the Federal Awardee Performance and Integrity Information System (FAPIIS) is current, accurate, and complete as of the date of submission of this offer with regard to the following information:
(1) Whether the offeror, and/or any of its principals, has or has not, within the last five years, in connection with the award to or performance by the offeror of a Federal contract or grant, been the subject of a proceeding, at the Federal or State level that resulted in any of the following dispositions:
(i) In a criminal proceeding, a conviction.
(ii) In a civil proceeding, a finding of fault and liability that results in the payment of a monetary fine, penalty, reimbursement, restitution, or damages of $5,000 or more.
(iii) In an administrative proceeding, a finding of fault and liability that results in–
(A) The payment of a monetary fine or penalty of $5,000 or more;
or
(B) The payment of a reimbursement, restitution, or damages in excess of $100,000.
(iv) In a criminal, civil, or administrative proceeding, a disposition of the matter by consent or compromise with an acknowledgment of fault by the
Contractor if the proceeding could have led to any of the outcomes specified in paragraphs (c)(1)(i), (c)(1)(ii), or (c)(1)(iii) of this provision.
(2) If the offeror has been involved in the last five years in any of the occurrences listed in (c)(1) of this provision, whether the offeror has provided the requested information with regard to each occurrence.
(d) The offeror shall post the information in paragraphs (c)(1)(i) through (c)(1)(iv) of this provision in FAPIIS as required through maintaining an active registration in the System for Award Management, which can be accessed via https://www.sam.gov (see 52.204-7).
(End of provision)
52.240-90 Security Prohibitions and Exclusions Representations and Certifications
(DEVIATION SEP 2025)
(a) Definitions. As used in this provision—
Backhaul, covered article, covered telecommunications equipment or services, critical technology, FASCSA order, Intelligence community, interconnection arrangements, national security system, roaming, sensitive compartmented information, sensitive compartmented information system, source, and substantial or essential component have the meanings provided in the clause 52.240-91, Security Prohibitions and Exclusions.
Business operations means engaging in commerce in any form, including by acquiring, developing, maintaining, owning, selling, possessing, leasing, or operating equipment, facilities, personnel, products, services, personal property, real property, or any other apparatus of business or commerce.
Marginalized populations of Sudan means—
(1) Adversely affected groups in regions authorized to receive assistance under section 8(c) of the Darfur Peace and Accountability Act (Pub. L. 109-344) (50 U.S.C. 1701 note); and
(2) Marginalized areas in Northern Sudan described in section 4(9) of such Act.
Restricted business operations means business operations in Sudan that include power production activities, mineral extraction activities, oil-related activities, or the production of military equipment, as those terms are defined in the Sudan Accountability and Divestment Act of 2007 (Pub. L. 110-174). Restricted business operations do not include business operations that the person (as that term is defined in Section 2 of the Sudan Accountability and Divestment Act of 2007) conducting the business can demonstrate—
(1) Are conducted under contract directly and exclusively with the regional government of southern Sudan;
(2) Are conducted under specific authorization from the Office of Foreign Assets Control in the Department of the Treasury, or are expressly exempted under Federal law from the requirement to be conducted under such authorization;
(3) Consist of providing goods or services to marginalized populations of Sudan;
(4) Consist of providing goods or services to an internationally recognized peacekeeping force or humanitarian organization;
(5) Consist of providing goods or services that are used only to promote health or education; or
(6) Have been voluntarily suspended.
Sensitive technology—
(1) Means hardware, software, telecommunications equipment, or any other technology that is to be used specifically—
(i) To restrict the free flow of unbiased information in Iran; or
(ii) To disrupt, monitor, or otherwise restrict speech of the people of Iran; and
(2) Does not include information or informational materials the export of which the President does not have the authority to regulate or prohibit pursuant to section 203(b)(3) of the International Emergency Economic Powers Act (50 U.S.C. 1702(b)(3)).
(b) Procedures.
(1) Covered telecommunications and video surveillance. The Offeror shall review the list of excluded parties in the System for Award Management (SAM) at https://www.sam.gov for entities excluded from receiving federal awards for “covered telecommunications equipment or services.”
(2) FASCSA Orders.
(i) The Offeror shall search in SAM for the phrase “FASCSA order” for any covered article, or any products or services produced or provided by a source, if there is an applicable FASCSA order described in paragraph (e) of FAR 52.240- 91, Security Prohibitions and Exclusions.
(ii) The Offeror shall review the solicitation for any FASCSA orders that are not in SAM but are effective and apply to the solicitation and resultant contract (see FAR 40.204-1(c)(2)).
(iii) FASCSA orders issued after the date of solicitation do not apply unless added by an amendment to the solicitation.
(c) Covered telecommunications equipment or services representations. By submission of its offer, the Offeror represents that, after conducting a reasonable inquiry (that looks at any information in the Offeror’s possession but does not need to include an internal or third-party audit)—
(1) It will not provide covered telecommunications equipment or services to the Government in the performance of any contract, subcontract or other contractual instrument resulting from this solicitation, except as waived by the solicitation, or as disclosed in paragraph (g); and
(2) It does not use covered telecommunications equipment or services, or use any equipment, system, or service that uses covered telecommunications equipment or services, except as waived by the solicitation, or as disclosed in paragraph (g).
(d) FASCSA Representation. By submission of this offer, the offeror represents that it has conducted a reasonable inquiry, and that the offeror does not propose to provide or use in response to this solicitation any covered article, or any products or services produced or provided by a source, if the covered article or the source is prohibited by an applicable FASCSA order in effect on the date the solicitation was issued, except as waived by the solicitation, or as disclosed in paragraph (g). A reasonable inquiry will look at any information in the offeror’s possession but does not need to include an internal or third-party audit.
(e) Sudan certification. By submission of its offer, the offeror certifies, after conducting a reasonable inquiry (that looks at any information in the offeror’s possession but does not need to include an internal or third-party audit), that the offeror does not conduct any restricted business operations in Sudan.
(f) Iran Representation and Certifications.
(1) Except as provided in paragraph (f)(2) of this provision or if a waiver has been granted in accordance with FAR 40.203-3, the offeror, after conducting a reasonable inquiry (that looks at any information in the offeror’s possession but does not need to include an internal or third-party audit), by submission of its offer —
(i) Represents, to the best of its knowledge and belief, that the offeror does not export any sensitive technology to the government of Iran or any entities or individuals owned or controlled by, or acting on behalf or at the direction of, the government of Iran;
(ii) Certifies that the offeror, or any person (as defined at section 15 of the Iran Sanctions Act of 1996, Pub. L. 104-172, 50 U.S.C. 1701 note) owned or controlled by the offeror, does not engage in any activities for which sanctions may be imposed under section 5 of the Act. These sanctioned activities are in the areas of development of the petroleum resources of Iran, production of refined petroleum products in Iran, sale and provision of refined petroleum products to
Iran, and contributing to Iran’s ability to acquire or develop certain weapons or technologies; and
(iii) Certifies that the offeror, and any person owned or controlled by the offeror, does not knowingly engage in any transaction that exceeds $15,000 with Iran’s…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .