NRN Questions and Answers 02062026.pdf

NRN Questions and Answers

XX Company is ineligible to bid because we do not fit the Small Business criteria. I have been searching for some to discuss partnership to support a bid, but I only know of ones that do not meet the criteria, either.

Would you please share a list of companies who are eligible that have expressed interest so I may contact them?

There is one small business I can share with you that listed themselves as an Interested Vendor in SAM.gov in the published the Sources Sought. Geodata Corporation. *any small businesses who may be interested in partnering should list their name in the Interested Vendor Section

We are seeking clarification regarding the Technical Capability evaluation factor, specifically the requirement for "Demonstrated experience in scenic byways projects or programs, mapping and GIS, and outreach, including byways promotional materials, educational materials, and program information" on page 4 of the RFQ document. Our team has demonstrated experience in all areas listed, including mapping and GIS and outreach, but we have limited or no direct experience in "scenic byways projects or programs." Since this is one of several bulleted items under Technical Capability, we would appreciate clarification on whether demonstrated experience in "scenic byways projects or programs" is a mandatory element for a quotation to be considered technically acceptable, or if strong experience in the other areas listed (mapping, GIS, and outreach) can compensate for less experience in scenic byways

Demonstrated experience in "scenic byways projects or programs" is not a mandatory element for a quotation to be considered technically acceptable. Strong experience in the other areas listed (mapping, GIS, and outreach) can compensate for less experience in scenic byways.

Is FHWA able to provide a representative sample dataset from one of the pilot states’ HPMS submissions for proposal calibration and alignment purposes?

No, FHWA is not able to provide sample data from the pilot States. However, as noted in the RFQ, geospatial data from the HPMS is readily available to the public

In reviewing the State-provided geospatial data, there are known inconsistencies in data completeness and level of detail. Is the contractor responsible for delivering a normalized, consistent national dataset view, or is the intent to document these inconsistencies and define a specification that accommodates them?

The intent is to document these inconsistencies and define a specification that accommodates them.

Is the scope of this effort limited to the listed pilot states, or should the conceptual model also address Alaska and Hawaii at a high level?

The conceptual model should apply to all States, DC, and Puerto Rico.

What is the expected deliverable format of the geospatial National Roadway Model (e.g., linear referencing constructs, layered representations, or three-dimensional conceptual views)?

As discussed in the RFP under Task 7, 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.

Does FHWA anticipate the NRN conceptual model being limited to linear representations, or should the specification allow for multiple abstract representations without defining an operational implementation?

We anticipate that the conceptual model will be limited to linear representations.

For multi-carriageway roadways, should the NRN specification evaluate and recommend appropriate representation approaches (e.g., independent carriageway geometries versus unified network representations with carriageway attributes), rather than assuming a single predefined approach?

The NRN specification may either evaluate and recommend approaches or may assume a single approach. If assuming a single approach, the specification should clearly indicate why the contractor selected the single predefined approach.

For the “working conceptual model” deliverable, is FHWA expecting an executable system, or would exported artifacts such as documentation, schemas, example datasets, and visualization outputs be sufficient, provided they are platform-agnostic and usable without proprietary licensing?

In reference to the “Working NRN Conceptual Model” deliverable in Task 4, exported artifacts would be sufficient.

Are contractors permitted to use commercial geospatial tools internally for analysis and visualization activities, provided that all contract deliverables are Government-owned, platform-neutral, and delivered without licensing dependencies?

As indicated in the RFQ, 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 may use other tools internally.

يغτ→τغ

╗Ï ðغل╤

Foreign nationals may support the tasks subject to federal laws and regulations. Review DOT Order 1630.2C Personnel Security Management, Item 11, on page 41.

Is there an incumbent contractor or internal FHWA team currently performing related NRN specification or research activities?

No.

Is there an estimated budget ceiling or anticipated funding range for this effort that FHWA is able to share for planning purposes?

No, the cost proposal should include all anticipated costs needed to complete the project.

The solicitation identifies NAICS 541370 (Surveying and Mapping). If an offeror is a small business but does not currently have NAICS 541370 listed in its SAM registration, may the offeror still submit a quotation under this RFQ?

Yes, there is no requirement for an offeror to have the specific NAICS code listed in its SAM profile to be eligible for award, provided the firm meets the small business size standard for that code. In this case the size standard is $19 million.

Are foreign nationals permitted to support non-sensitive analytical or documentation tasks under this contract, provided they do not access raw state or Federal datasets.

The RFQ allows submission of resumes but does not specify required labor roles or qualifications. Does FHWA have an expectation for specific key personnel resumes (e.g., Project Manager, GIS Lead, Data Architect), or may offerors include resumes at their discretion to demonstrate technical capability?

Offerors may include resumes at their discretion to demonstrate technical capability. While resumes are excluded from the Technical Quotation page limitation, they are themselves limited to no more than two pages each.

The RFQ indicates past performance will be evaluated but does not specify a minimum or maximum number of references. Is FHWA seeking a specific number or format for past performance examples, or may offerors submit a reasonable number of relevant past performance references at their discretion?

Offerors may submit a reasonable number of relevant past performance references at their discretion.

Does FHWA permit the use of subcontractors or teaming partners to support performance under this RFQ, and if so, may the experience and qualifications of subcontractors be considered as part of the Technical Capability and Past Performance evaluation?

While FHWA permits the use of subcontractors, please see FAR 52.219-14 Limitations on Subcontracting. The prime must perform 50% of the work. We may consider the experience and qualification of subcontractors as part of the evaluation.

Does FHWA have any preferred or restricted tools, platforms, or formats (e.g., ArcGIS, open-source GIS, specific database technologies) that offerors should consider when proposing the NRN conceptual model and demonstrations?

As indicated in the RFQ, 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 may use other tools internally.

Is there any Incumbent for this current work ? If Yes is the incumbent eligible for recompete ?

There is no incumbent.

Who was the vendor responsible for establishing the 2022 FHWA the National Road Network (NRN) Pilot?

FHWA awarded Applied Geographic, Inc. (AppGeo) the task order in 2020.

Will the Government provide an example of demonstrated organizational commitments that would be rated favorable during the evaluation?

No, FHWA does not have an example of an organizational commitment that would be rated favorable during the evaluation.

What is the current process that State DOTs use to report their data to ARNOLD?

States provide ARNOLD (the spatial representation of all public roads in a State) by submitting a File GeoDatabase or Shapefile to the Highway Performance Monitoring System (HPMS) application hosted by the FHWA. Upon submission of ARNOLD, HPMS confirms geometries are provided as simple features.

It appears each State DOT is mandated to report their data annually. How many State DOTs are compliant with their mandated reports to ARNOLD?

All 50 States, Puerto Rico, and the District of Columbia consistently provide ARNOLD annually.

Will the Government consider extending the submission date to 2/20/26 to allow for adequate time to address question responses?

Yes, FHWA will extend the submission date. The new date is 2/24/2026 4PM ET.

Can the government also confirm that they do not have a specific software solution chosen for this proposal?

FHWA does not have a specific software solution.

Would the Government confirm that data acquisition is not part of the required scope?

Data acquisition is not part of the required scope. HPMS geospatial data is available publicly.

Can the Government confirm that each state is responsible for providing their data?

Yes, States are responsible for providing tabular and geospatial data to HPMS on an annual basis.

Please confirm that for the #3. Past Performance requirement, the Government only plans to reference the Contractor’s Performance Assessment Reporting System (CPARS), and we are not required to submit any past performance information with our RFQ response.

That is correct.

RFQ §1.1 and §1.2 state FHWA will use research from ten pilot States to inform the NRN specification and conceptual model: Tasks 2–6 reference leveraging that work. Please specify which pilot state artifacts FHWA will provide (e.g., pilot reports, cleaned geodatabases, schema drafts, validation findings, workflow notes, code snippets), for which states, in what formats, and with what data sharing constraints.

FHWA will provide the (unpublished) Pilot State Final Report, which summarizes results of the pilot studies and other work completed to date. As mentioned in the RFQ, geospatial data from the HPMS is readily available to the public.

Task 4 requires a working conceptual model using pilot state data and a demonstration to FHWA. Please clarify the required level of completeness:

(a) schema only with small samples,

(b) populated exemplars for a subset of pilot states, or

(c) fully populated multi-state model suitable for test runs.

Also, confirm whether any automated processes (e.g., loaders, QC scripts) are required at this stage.

As stated in RFQ, this task includes a working conceptual model with data from the pilot states.

Completeness would likely need to be close to a “fully populated multi-state model suitable for test runs” to progress to Task 5. Automated processes would not be required at this stage.

Tasks 4 and 6 require demonstrations to show the conceptual model and update workflow. Please confirm the format (live workshop, recorded session, or interactive review), expected duration, participant mix (FHWA/HQ and pilot states), and the number of demonstrations for each task.

Each of the two tasks anticipates one live workshop attended by U.S. DOT stakeholders. The contractor should decide how much time is needed to run the two demonstrations.

The SOW is tool agnostic, but deliverables include geospatial models and visualizations. Please indicate any preferred or required platforms (e.g., Esri ArcGIS Pro/Enterprise, QGIS, UML tools, FME).

As indicated in the RFQ, 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 may use other tools internally.

Task 3 requires “input to the metadata for the identified source… including any limitation on the release or use of the data.” Please confirm the metadata standard (e.g., FGDC CSDGM, ISO 19115/19139, or FHWA-defined template) and whether a data dictionary template will be supplied.

Data structure and metadata are expected to meet standards adopted by the Federal Geographic Data Committee (FGDC), which includes ISO 19115. FHWA does not have a template.

Part III / Technical Exhibit 2 requires Section 508 compliance for all ICT. For maps, schema diagrams, and geodatabases, please confirm the required remediation level (alt text + tagged PDFs only vs. full WCAG techniques for charts/maps) and whether a 508 checklist or template is provided by FHWA.

FHWA requires a full remediation level including full WCAG techniques for charts/maps. FHWA does not have a checklist or template to provide at this time.

Task 1 requires a kickoff within ten business days and “progress meetings, as requested,” plus monthly reports. To price accurately, please indicate FHWA’s expected cadence (e.g., biweekly 60 min) and any standing working sessions for Task 2 requirement clarifications.

The contractor should assume one-hour monthly progress meetings, but additional meetings may be needed during some phases of the project. Under Task 2, the contractor shall organize and manage working sessions with the NRN team for the purpose of clarifying and refining the technical requirements.

The contractor should propose the number and cadence of working sessions they anticipate needing to complete Task 2.

Part I limits the Technical Quotation to 15 pages, excluding resumes (max 2 pages each), table of contents, and cover page. Please confirm whether cover letter, diagrams, tables, traceability matrices, schemas, and assumption tables count toward the 15-page limit.

All materials included in the Technical Quotation, including diagrams, tables, traceability matrices, schemas, and assumption tables, count toward the 15-page limit.

Task 5 references “opportunities… where automated ‘fixes’ can be applied.” Please confirm if FHWA expects executable prototype scripts/tools in Task 5 or documentation of candidate rules only, with automation deferred to a future acquisition.

Documentation of candidate automation scripts would be sufficient for this task.

Optional Task 8 permits travel reimbursement up to $10,000 for external presentations. Please indicate the anticipated number of events, typical audience (e.g., GIS T, TRB), and whether abstract/paper development is part of the scope.

Abstract/paper development is part of the scope, and typical audiences would be members of the transportation GIS community that attend GIS-T and TRB. FHWA does not have an anticipated number of events because it would depend upon travel costs.

Does the 11-point font requirement apply to text within headers/footers, graphics, and figures?

Yes, the 11-point font requirement applies to text within headers/footers, graphics, and figures.

Specifically, on page 4, the RFQ states that quotes should include "Demonstrated organizational commitments;" What is meant by commitments? An overall commitment from the organization that we'll provide the staff and resources to complete the project?

Or does this mean our other current project commitments?

Organizational commitment refers to the company’s overall commitment to ensuring that contracts, such as this one, succeed. It may involve available resources and capabilities beyond the assigned project team.

1.1 Please confirm how HPMS and ARNOLD data will be

delivered to the Contractor (e.g., secure portal, SFTP, DOT data hub), including any access prerequisites or lead time after award.

HPMS and ARNOLD are freely available to the public through the DOT DataHub.

1.2 Will the Contractor receive nationwide

HPMS/ARNOLD extracts, pilot-state-only extracts, or both?

Both national and state-level geospatial files are available on the DOT DataHub.

1.3 For each dataset FHWA expects the Contractor to

use (HPMS, ARNOLD, and any initial secondary sources), can FHWA provide approximate data sizing guidance (e.g., file sizes in GB, record/feature counts, and number of attributes/columns)?

No, FHWA is not able to provide such guidance at this time.

1.4 What file/data formats are expected for source

deliveries (e.g., CSV/Excel, FGDB, shapefile, database dump, API, etc.)?

HPMS and ARNOLD files are available in multiple formats including shape files, GeoJSON, and CSV.

1.5 Are there any data handling, storage, or security

constraints that affect where data can be stored/processed (given the RFQ indicates no equipment/facilities are provided)?

In reference to Task 1, no because the data are publically available.

2.1 For divided facilities (dual carriageways), does FHWA

have a preferred representation approach (e.g., separate directional centerlines vs. a single facility feature with directional attributes)?

Separate directional centerlines

2.2 For intersections/interchanges, what level of detail is

expected in the conceptual model (e.g., basic node-edge connectivity vs. explicit ramp/junction feature classes)?

Ramps are represented as their own feature in

ARNOLD.

2.3 For required measures (length, lane-length, VDT), does FHWA have authoritative definitions/calculation rules and/or source-of-truth fields we should use?

ARNOLD is a Linear Referencing System by which all lengths are determined. Any downstream calculations based on segment lengths, such as Lane Miles or Daily Vehicle Miles Traveled, uses the LRS based segment lengths in concert with other collected data (such as through lanes and Annual Average Daily Traffic) that is reported on the provided LRS. FHWA considers what is provided by the States as authoritative and only compares prior State submittals to determine the validity of incoming data submittals.

2.4 Connectivity requirement: Does FHWA have a

defined tolerance/threshold for “topologically connected” at state borders and within states (e.g., snap tolerance, allowable gaps, exceptions)?

No, FHWA does not have a defined tolerance/threshold.

2.5 LRS support: What minimum LRS capability must be

demonstrated (route IDs, measures, calibration strategy, event tables), and does FHWA have preferred conventions?

The model will need to accommodate the inclusion of all feature identification information (Route IDs, Begin Point, and End Point) and HPMS roadway attribute data as defined in the ARNOLD Reference Manual and HPMS Field Manual. A calibration strategy should be developed to handle the discrepancy between the measured length per the LRS, and geometric length.

3.1 Which secondary sources does FHWA anticipate are

most important to evaluate for the NRN specification (e.g., structures/bridges, ferry routes, road names, other)?

There is no priority order at this time.

3.2 Will FHWA provide access to any secondary sources, or is the Contractor expected to obtain them (including any licensing/MOU efforts)?

The contractor is expected to obtain them.

3.3 For Task 3 “metadata input,” does FHWA have a

required metadata standard/template and a target repository/tool for metadata entry?

Data structure and metadata are expected to meet standards adopted by the Federal Geographic Data Committee (FGDC), which includes ISO 19115.

FHWA does not have a template or tool.

4.1 Please clarify what constitutes a “working NRN

conceptual model” deliverable for acceptance (e.g., geodatabase schema + sample data, diagrams only, scripts, map services, etc.).

As stated in the RFQ, this task includes a working conceptual model with data from the pilot states. It likely would need to be a multi-State model suitable for test runs to progress to Task 5.

4.2 Please clarify what constitutes a “demonstration” for

acceptance (live demo via web services/apps vs.

walkthrough of offline artifacts and outputs).

This task anticipates a live workshop attended by U.S.

DOT stakeholders.

4.3 The RFQ references pilot states identified for the

NRN initiative. Can FHWA confirm the pilot states to be used for the conceptual model demonstration?

As indicated in the RFQ, the pilot States are Alabama, the District of Columbia, Delaware, Florida, Georgia, Maryland, Mississippi, North Carolina, South Carolina, and Virginia.

4.4 Will FHWA provide pilot-state stakeholder points of

contact and coordinate participation for working sessions/feedback?

If State participation is required, FHWA will provide POCs. However, the contractor will coordinate participation.

5.1 Should validation criteria be designed for pilot-state

demonstration only, or intended to scale to national implementation needs?

While informed by the demonstration, it is intended to scale to national implementation.

5.2 Does FHWA have acceptance thresholds for

validation categories (connectivity, spatial accuracy, divided facility consistency, attribute completeness), or should the Contractor propose?

The contractor should propose the acceptance thresholds.

5.3 Are there FHWA-preferred validation tools/methods

(e.g., topology rules, Data Reviewer, custom scripts), or should the Contractor propose a best-fit approach?

The contractor should propose a best-fit method.

6.1 How are annual HPMS/ARNOLD updates delivered

(full replacement vs. deltas), and do deliveries include change flags/history that support a transactional/delta workflow?

Currently, HPMS/ARNOLD is delivered as a full replacement on an annual frequency. Temporal analysis is based on Data Year. HPMS is considering the development of an incremental submittal process, which may necessitate discussion of its impact to the

NRN.

6.2 When the RFQ describes

“incremental/transactional” updates, does FHWA intend database-style transactions/versioning, packaged deltas, or another specific approach?

The contractor should propose a best-fit solution.

6.3 For the required workflow feasibility demonstration, what pilot dataset(s) or scenario size/complexity should we assume for demonstrating annual change processing?

The scenarios should include relevant HPMS/ARNOLD data from all pilot States.

6.4 Does FHWA expect any prototype scripts/ETL

artifacts to be delivered as part of the update workflow documentation/demonstration, or is documentation + example outputs sufficient?

At a minimum, FHWA would expect the delivery of prototype scripts/ETL artifacts that support the example output.

7.1 Does FHWA provide any preferred templates for

reports/tracker documents (monthly progress tracker, requirements documentation, specification report)?

NO, FHWA does not have a preferred template.

7.2 The RFQ indicates deliverables should not include

contractor logos/references. Please confirm this applies to all deliverables and presentation materials.

Yes, this applies to all deliverables including presentation materials.

7.3 For any visualization outputs (if used for

demonstrations), what level of Section 508/ICT conformance is expected for web-based components vs.

static documents?

FHWA requires a full remediation level including full WCAG techniques for charts/maps.

8.1 What meeting cadence should the Contractor

assume beyond the initial working sessions (e.g., weekly, biweekly, monthly)?

The contractor should assume one-hour monthly meetings, but additional meetings may be needed during some phases of the project.

8.2 Is there an existing monthly progress tracker format

FHWA prefers?

No, FHWA does not have a preferred progress tracker format.

9.1 How many external presentations/events are

anticipated under Optional Task 8, and what audiences/venues are envisioned?

FHWA does not have an anticipated number of events because it would depend upon travel costs. Typical audiences would be members of the transportation GIS community that attend GIS-T and TRB.

9.2 Should the Contractor assume zero travel unless

explicitly authorized (given the travel NTE), or plan for 1– 2 trips?

The contractor may propose no travel (virtual attendence only), trips, or a combination or both.

Regarding Task 6 – Update Procedures, does the government require the retention of previous data? Such as when lanes are added to a highway, would the old width & lane count need to be retained to view the previous state of the road?

As described in Task 6, the NRN is to be updated annually. The contractor shall provide a workflow that describes the annual update procedures for the NRN through an incremental/transactional process, and this workflow should describe how record revisions are documented.

Regarding Task 3 – Identify Sources, is it expected that extra sources are to be used solely for attribution of HPMS features? Or would it be acceptable for data sources outside of HPMS to be used in place of the HPMS in situations where they are more accurate and/or more complete?

It is expected that extra sources beyond HPMS would augment, not replace, HPMS features in the NRN.

Regarding Task 3 – During the course of Task 3 when the Contractor identifies and shows sources supplied by commercial entities (e.g. sample GIS map data) that require licensing agreements for the Government to use in HPMS, does the Government claim this as material that now becomes government property identified in Section 3.11?

If the Contractor acquires data or other materials for this effort, then the materials become government property.

Is a contractor teaming arrangement between an eligible small business and a large business allowable to successfully complete the tasks of this RFQ?

Yes. The Small has to be the prime and the large would have to do 50% or less of the work. We can only award to a small. See FAR clause 52.219-14 Limitations on Subcontracting.

Due to the short time between the due date for questions and the due date for RFQ responses, is it possible to extend the RFQ due date to the end of the following week (February 20)?

Yes, FHWA will extend the submission date. The new date is 2/24/2026 4pm ET.

Will the Government provide a specific technical definition for "public roads" to be used for the National Road Network (NRN), and does this definition differ from the standard HPMS criteria of being "open to public travel"?

As defined in the HPMS Field Manual, a “A public road is any road or street owned and maintained by a public authority and open to public travel. [23 U.S.C.

101(a)].”

Does the requirement to include "all public roads" encompass administrative or restricted routes within National Parks and Forest Service lands, or private roads that are currently excluded from standard state reporting?

The requirement includes all roads reported to HPMS.

Does the Government require the National Road Network (NRN) to support a specific linear referencing method, such as Milepoint or Reference Post, or is the contractor expected to propose a standard best suited for the conceptual model?

The contractor is expected to propose a standard best suited for the model.

Is the requirement for "topological connectivity" limited to geometric shared nodes at borders, or should the conceptual model support advanced network analysis features such as graph-based routing?

Topological connectivity for geometric shared nodes at borders is a minimum requirement, but the contractor can propose advanced features as well.

Among the listed business use cases (e.g., NHS, Freight, Safety, and Asset Management) - are there specific priority domains that the working conceptual model demonstration must address first?

No, there is no priority order at this time.

When reconciling secondary data sources such as State DOT LRS with the primary HPMS source, which dataset should be designated as the "system of record" for geometry versus attribution if spatial discrepancies are identified?

HPMS should be considered the system of record.

Are there specific existing federal metadata templates or schemas that the identified source metadata must be mapped to, or is the contractor responsible for defining the metadata structure?

Data structure and metadata are expected to meet standards adopted by the Federal Geographic Data Committee (FGDC), which includes ISO 19115. FHWA does not have a template.

Does the Government require the National Road Network (NRN) to utilize a specific Coordinate Reference System (CRS), such as unprojected WGS84 or NAD83, or should the contractor recommend a projection optimized for analysis?

The contractor should recommend a projection optimized for analysis

Are there specific external geospatial standards, such as OGC Simple Features or ISO 19115, that the data structure and metadata must strictly adhere to?

Data structure and metadata are expected to meet standards adopted by the Federal Geographic Data Committee (FGDC), which includes ISO 19115.

However, OGC Simple Features (ISO 19125) will continue to need to be considered when determining rules for data storage.

For the demonstration of the conceptual model, is the contractor expected to develop a custom interactive user interface or dashboard, what level of interactivity is expected?

As stated in the RFQ, Task 4 includes a working conceptual model with data from the pilot states. A model suitable for interactive test runs likely is needed to progress to Task 5.

How detailed do the QA and validation criteria need to be for topology and attributes?

The criteria should be of sufficient detail for a future developer to implement easily within an automated validation engine.

Does the Government require specific temporal versioning for updates, for instance a temporal database schema that maintains a historical lineage?

As described in Task 6, the NRN is to be updated annually. The contractor shall provide a workflow that describes the annual update procedures for the NRN through an incremental/transactional process, and this workflow should describe how record revisions are documented.

Does the conceptual model deliverable require the deployment of a tile server or map service? If a hosted service is not required, what specific visualization platforms or software environments must the data structure be compatible with?

A hosted service is not required. As indicated in the RFQ, 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 may use other tools internally.

If an interactive prototype or dashboard is delivered, does the Government require full 508 compliance (e.g., keyboard navigation, screen reader compatibility for map features, legends, etc.)?

Yes, FHWA would require full Section 508 compliance.

For static maps included in the final reports, what standard of accessibility is expected (e.g., alt-text summaries, high contrast, long descriptions, etc.)?

FHWA requires a full remediation level including full WCAG techniques for charts/maps.

Should the final Product Specification deliverable include guidance to assist future users in maintaining Section 508 compliance when utilizing the National Road Network (NRN) data?

No, the Product Specification deliverable does not need to include Section 508 guidance.

The SOW references specifications, documentation, and demonstrations. For the Proofs of Concept, does FHWA prefer executable code and working demonstrations built on top of modeled pilot data over strictly conceptual demonstrations?

Yes, FHWA prefers executable code and working demonstrations built with pilot data over strictly conceptual demonstrations.

For Task 5, does FHWA envision that validation criteria may include both automated fixes (within clearly defined tolerances) and cases explicitly flagged for human review? Essentially, to form a validation "engine" that combines automatic detection and resolution plus identification of issues requiring human intervention?

Yes, the validation engine likely would use both automatic detection and resolution plus identification of issues requiring human intervention.