693JJ322R000002_A002.pdf

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing items 8 and 15, and returning or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

E. IMPORTANT: Contractor is not is required to sign this document and return copies to the issuing office.

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE

2. AMENDMENT/MODIFICATION NUMBER 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQUISITION NUMBER 5. PROJECT NUMBER (If applicable)

7. ADMINISTERED BY (If other than Item 6) CODE

STANDARD FORM 30 (REV. 11/2016)

Prescribed by GSA FAR (48 CFR) 53.243

FACILITY CODE

9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NUMBER

10B. DATED (SEE ITEM 13)

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers is extended. is not extended.

12. ACCOUNTING AND APPROPRIATION DATA (If required) copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NUMBER AS DESCRIBED IN ITEM 14.

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER

NUMBER IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15C. DATE SIGNED

15A. NAME AND TITLE OF SIGNER (Type or print)

16C. DATE SIGNED

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

PAGE OF PAGES

6. ISSUED BY CODE

8. NAME AND ADDRESS OF CONTRACTOR (Number, street, county, State and ZIP Code) (X)

CODE

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

Previous edition unusable

A002

N/A

N/A

N/A

N/A

N/A

The purpose of this amendment is to:

1) Extend the proposal due date, from 12/01/2021, 1:00 PM ET, to 12/03/2021, 1:00 PM ET

2) Make revisions to the solicitation, as indicated in the attached pages with red and stricken through text.

A signed copy of this amendment is required to be included in the submission of proposals.

FEDERAL HIGHWAY ADMINISTRATION

OFFICE OF ACQUISITION AND GRANTS MANAGEMENT

1200 NEW JERSEY AVENUE, SE

WASHINGTON, DC 20590

N/A

N/A

693JJ322R000002

N/A

1 58

11/29/2021

11/02/2021

N/A

REQUEST FOR PROPOSAL 693JJ322R000002 Page 1 of 57 Amendment A002

REQUEST FOR PROPOSAL (RFP)

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: Gunnar Prutz, Contract Specialist Telephone: (360) 619-7685 Email: Gunnar.Prutz@dot.gov

Solicitation Number: 693JJ322R000002

Title: The National Performance Management Research Data Set

(NPMRDS) and Technical and Data-Sharing Support

Solicitation Release Date: 11/02/2021

Technical Questions Due Date: 11/16/2021 1:00 PM Eastern Time

Proposal Due Date: 12/031/2021 1:00 PM Eastern Time

REQUEST FOR PROPOSAL 693JJ322R000002 Page 2 of 57

SECTION I

RFP INFORMATION AND INSTRUCTIONS FOR PREPARATION OF PROPOSALS

RFP INFORMATION

This is a combined synopsis/solicitation for commercial items prepared in accordance with the format in subpart 12.6, as supplemented with additional information included in this notice. This announcement constitutes the only solicitation; proposals are being requested and a written solicitation will not be issued.

This is an unrestricted, non-set aside Firm Fixed Price (FFP) RFP. This solicitation is prepared in accordance with Federal Acquisition Regulation (FAR) Part 12, the acquisition of commercial items in conjunction with the policies and procedures as prescribed in FAR 15, Contracting by Negotiation. The solicitation document and incorporated provisions and clauses are those in effect through Federal Acquisition Circular (FAC) 2021-07.

This solicitation’s North American Industry Classification System (NAICS) code is 541990 with an industry size standard of $16.5 Million A responsible offeror is one whose proposal 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 proposal submission in order to be eligible to receive an award under this RFP.

All questions concerning the RFP shall be submitted electronically to Gunnar Prutz via email at Gunnar.Prutz@dot.gov, no later than 1:00 PM Eastern Time (ET), on November 16, 2021 in order for responses to all reasonable questions to be conveyed in a timely manner.

INSTRUCTIONS FOR PREPARATION OF PROPOSALS

In responding to this RFP, proposals MUST adhere to the following:

1) Proposal Format

a) Do not include marketing materials.

b) Proposals shall be prepared to print on 8½ x 11-inch paper.

c) Margins (Top, Bottom, Right and Left) no smaller than 1" (headers and footers are allowed in the margins)

d) Arial or Times New Roman size 12 font

e) Offers shall be submitted in a format readable by Microsoft (MS) Word, MS

Excel, or in text searchable PDF format, as applicable.

f) Volume 1 Technical Proposal is limited to 50 pages, not including resumes, cover page and table of contents. Resumes are limited to 2 pages each.

REQUEST FOR PROPOSAL 693JJ322R000002 Page 3 of 57

g) Volume 2 Price Proposal does not have a page limitation.

h) The subject line of your email and all correspondence must include the

RFP number found on the cover page.

2) Proposal Content and Configuration

Each proposal volume shall be provided by email to Gunnar.Prutz@dot.gov and Amalia.Rodezno@dot.gov. If necessary, offerors may provide a URL link as part of their proposal package to download data files that are too large to email. These files shall not be revised by offerors after the submission of the proposal. The proposals shall match the volume and parts format described below:

Volume I – Technical Proposal (Parts I and II): No more than 50 pages total (excluding resumes, cover page, table of contents, and Spatial Data appendix)

a) Part I – Technical/Management Approach

b) Part II – Staffing Proposal/Resumes – No limit on total resume pages, limit resumes to 2 pages each.

Volume II – Business Information and Price Proposal (Parts I-V):

a) Part I –Price Information

b) Part II – Subcontracts/Consultants

c) Part III – Other Financial/Organizational Information

d) Part IV – Subcontracting Plan

e) Part V – Past Performance – Not to exceed 10 pages.

NOTE: No page limits required for Volume II (a) – (d)

Volume I – Technical Proposal

This volume shall consist of two parts; Part I – Technical/Management Approach and Part II – Staffing Proposal/Resumes. No price data shall be included in any part of Volume I.

NOTE: The Offeror shall indicate under Volume I of the proposal, the name(s) and title(s) of the person(s) who writes the proposal and his/her relationship to the offering organization.

Part I – Technical/Management Approach

NOTE: The Offeror’s response shall demonstrate an understanding of the requirements and approach to addressing the work tasks anticipated and how the contract requirements and objectives will be met. The proposal shall not repeat the Section III – Statement of Work requirements, but instead demonstrate an understanding of the issues involved, the approach to addressing such issues, and the unique experience of the offeror’s team to address such considerations.

REQUEST FOR PROPOSAL 693JJ322R000002 Page 4 of 57

The Offeror shall describe their capability and experience and explain how its data meets this requirement and demonstrate the following in response to this solicitation:

a) The proposal shall indicate the vehicle probe data that will be used, the sources of the probes, and how the Offeror shall achieve access to the probe data.

b) The proposal shall demonstrate the level of coverage for the required geography, and in conjunction with the Section III. 4.1 Task 1 requirement, provide a year’s worth of spatial and temporal coverage information (perfect spatial and temporal coverage would mean that probe travel time data is available on the entire National Highway System (NHS) and at all times of day). The information about the coverage of the data set shall include diagnostic information and a forecast of this diagnostic evaluation for the previous full calendar year.

NOTE: Coverage accuracy and detail will be considered in proposal evaluation. Using path processing is one approach to providing additional coverage while retaining the “actual, observed measurement” requirement of this work.

The Offeror shall provide as an appendix the past 12 months’ worth of spatial and temporal coverage information. This information will not count towards the proposal page limitation.

NOTE: Below are sample charts for the Spatial/Temporal reporting for daytime hours on weekdays, and overnight and weekends):

5-minute time periods Covered - Daytime (6-8), Weekdays

All Traffic Miles Interstate (IS) Non-IS

NHS

Freight Miles Passenger Miles

Interstate (IS) Non-IS NHS Interstate Non-IS

(IS) NHS

75%-100% 50%-75% 25%-50% 0%-25%

5-minute time periods Covered – All Other Times (overnight, weekends)

All Traffic Miles Freight Miles Passenger Miles

Interstate (IS) Non-IS

NHS

Interstate (IS) Non-IS

NHS

Interstate Non-IS

(IS) NHS

75%-100%

REQUEST FOR PROPOSAL 693JJ322R000002 Page 5 of 57

c) If the vehicle probe data is not owned or currently possessed by the Offeror, the Offeror’s proposal shall include a signed commitment letter from at least one vendor to provide data necessary to meet the contract requirements and demonstrate the ability to establish and maintain agreements with appropriate vehicle probe data vendors to ensure continuous data collection. The Offeror shall demonstrate the ability to maintain agreement with appropriate probe data source to ensure continuous data collection.

d) Since continuous data collection is a requirement within the contract, the Offeror shall include documentation of a plan for maintaining and increasing the number of vehicle probes as part of this data set.

e) Within their proposal, the Offeror shall demonstrate the data quality and accuracy, including:

(1) The completeness, strength and adequacy of proposed accuracy and reliability of data.

(2) The adequacy of data sample and description as outlined in Section III.4.2, Task 2.

f) Provide a detailed explanation of its vehicle probe data sources and the metadata that would be provided with travel times and average speeds. The Offeror shall demonstrate an ability to provide a record for every 5-minute period whether it includes travel time/average speed data from an observed probe or not. The required monthly data includes, at minimum, the following:

• Time,

• Date,

• Direction of travel,

• 3 Travel Times (Passenger only, Freight only and All Vehicles),

• Average Speed, and

• Location: segment id, route, State (State coding must be in FIPS2).

g) Provide the average travel times and average speeds from vehicle probe data in three classifications: all vehicles, passenger vehicles and freight trucks.

NOTE: The data elements must be identifiable by FHWA route ID and roadway functional class per HPMS definition at http://www.fhwa.dot.gov/policyinformation/hpms/fieldmanual/.

50%-75%

25%-50%

0%-25%

REQUEST FOR PROPOSAL 693JJ322R000002 Page 6 of 57

h) The proposal shall include sample data, identifying a particular time and location, for each classification, as well as a detailed description of how the proposed data meets the above requirements.

i) Geographic Coverage

• The proposal shall describe how the data is statistically significant for the population or is accurate for the travel times/speeds provided) for both freight and all traffic (and optionally, passenger) for the following geographic coverage (220,000 centerline miles of road) under Section III.4.2 Task 2.

• The proposal shall describe and shall include specifications and information on segment lengths, link information and other GIS file parameters under Section III.4.2 Task 2.

j) Probe Data Collection Frequency, Quality and Accuracy - The proposal shall include specifications and information on how probe data frequency, quality, and accuracy requirements will be met. Included in these specifications and information shall be the proposed guarantee of data quality as measured by average absolute speed error and speed error bias. [NOTE: The absolute speed error is defined as the absolute value of the difference between the mean speed reported from the data service and the mean speed provided by validation procedures for a specified time period or polling interval. Error bias is defined as the average speed error (not the absolute value) in each speed range.] The proposal shall demonstrate how they will assure that the data is both complete in coverage throughout the day and absent of any extremely slow speeds that are due to minimal probes from vehicles stopped at signalized intersections. Additionally, the proposal shall address the possibility of confirming that the temporal coverage provided for data collection is consistent with the actual presence of vehicles on the roadway. This may include comparing actual coverage to hourly traffic counts or another method proposed.

k) Processing Timeframe - The proposal shall include proposed processing timeframe.

l) Data Dissemination - The proposal shall include the Offeror’s plan for and methods to disseminate data to FHWA (and USDOT), its contractors and any State DOT, Metropolitan Planning Organizations (MPO) and designated contractor(s) and include how the requirement for timeliness of responses will be met.

m) Technical Support - The proposal must include a detailed description of the proposed means for technical support and include how the requirement for timeliness of responses will be met.

n) The proposal must include a detailed description of how the Offeror shall address data validation, calibration, and quality as described in Section III.4.3, Task 3.

The proposal shall include the Offeror’s validation methodology and approach

REQUEST FOR PROPOSAL 693JJ322R000002 Page 7 of 57 and data quality plan and metadata approaches as outlined in Section III.4.3, Task 3.

o) The proposal must include a detailed description of how the Offeror shall provide the reports and weekly data delivery as outlined in Section III. 4.4, Task 4.

p) The technical approach shall also include a management plan, which details how the Offeror will address the requirements of this RFP.

Part II – Staffing Proposal / Resumes

Offerors shall provide a Master Staffing Matrix, which denotes the key personnel and the staffing levels proposed, and capabilities/credentials.

Additionally, the Offeror shall provide a contingency plan to replace the Key Personnel over the life of the contract. The contingency plan must demonstrate that the Offeror has the ability to replace key personnel without any adverse impact on performance. As a part of the contingency plan the Offeror must demonstrate their recruitment and hiring plan to fill key positions.

Resumes shall be submitted for key personnel only and must be organized and numbered.

Key personnel roles and titles shall be identified and proposed by the Contractor. The resumes shall clearly match the topic area in which the staff member will be utilized and may not exceed 2 pages. The resumes shall include academic background; technical qualifications; project management, subject matter expertise; relevant project level experience; and professional affiliations, licenses, designations or national committee appointments.

Volume II – Business and Price

Part I –Price Information

a) The pricing information provides an overall price proposal by the Offeror with the details and assumptions that are included in the Offeror’s price. Offerors shall submit:

Price proposals must adhere to the pricing structure established in Section II – Schedule of Services.

b) Format and Content. Volume II shall include the following documents (in the order listed):

(1) Pricing Chart - Complete Section II -Schedule of Services, and if requested, a milestone payment schedule.

REQUEST FOR PROPOSAL 693JJ322R000002 Page 8 of 57

(2) Amendments – Signed copies of all solicitation amendments that have been posted on www.SAM.gov

c) Offerors shall submit, under a separate tab, all (if any) assumptions or conditions upon which the Price Proposal is based. Note that assumptions or conditions that are non-conforming to the Government’ solicitation may result in the offer being removed from competition.

Any information submitted must support the price proposed. Include sufficient detail, to clearly establish the relationship of the information provided to the price proposed. Support any information provided by explanations or supporting rationale as needed to permit the Government to evaluate the documentation.

Submission of certified cost or pricing data is not required.

Part II – Subcontracts

If subcontractors will be used in carrying out the requirements of this project, the following minimum information concerning the subcontractor shall be furnished:

a) Name and address of the subcontractor.

Part III – Other Financial / Organizational Information

Provide the following information:

a) A completed copy of FAR Provision 52.212-3 in this RFP, if the Offeror’s representations and certifications in the System for Award Management are not current.

b) Completed FAR Provisions 52.204-24, 52.204-26, 52.209-7, 52.229-11.

Completed TAR Provision 1252.237-71.

c) Conflicts of Interest - The Offeror shall provide a brief statement in its proposal that describes in a concise manner all past, present or planned organizational, contractual or other interest(s), which may affect the Offerors' ability to perform the proposed contract in an impartial and objective manner. The Contracting Officer will review the statement and may require additional relevant information from the Offerors. In accordance with FAR Subpart 9.5, all such information, and any other relevant information known to DOT, will be used to determine whether an award to the Offerors may create an actual or potential conflict of interest. If any such conflict of interest is found to exist, the Contracting Officer may (a) disqualify the Offerors, or (b) determine that it is otherwise in the best interest of the United States to contract with the Offerors and include appropriate provisions to mitigate or avoid such conflict in the contract awarded.

REQUEST FOR PROPOSAL 693JJ322R000002 Page 9 of 57

d) The Offeror must state that they agree to all terms and conditions of this solicitation, which consists of the RFP Sections I through IV, including all documents, exhibits, and all other attachments that are incorporated therein by reference and made a part thereof, or provide an explanation for any exceptions.

e) Provide the name(s) of, email addresses, and telephone number of personnel authorized to represent and negotiate on behalf of your business.

f) Provide the information requested below:

(1) DUNS Number:

(2) Taxpayer Identification Number:

(3) Home Office Congressional District

(4) Business size & type [e.g. HUBZone, SDVOSB, WOSB etc.]

Part IV - Subcontracting Plan:

Subcontracting Plan:

Each prime offeror who is other than a small business shall include within its proposal a complete copy of the prime offeror’s Subcontracting Plan, satisfactorily addressing all of the requirements set forth in FAR Clause 52.219-9.

The Offeror shall also submit a subcontracting plan in accordance with the instructions/format in Attachment 7. In the event that the Offeror has no such plan, the form shall be submitted with “no plan identified” indicated on the form as applicable and the offeror shall submit a statement of circumstances supporting that determination.

Part V - Past Performance

The Offeror shall describe in its proposal no more than five related contract/ subcontract past performance descriptions ranked and numbered from one to five, with one being most relevant. The Offeror shall describe their proposed team’s relevant past performance within the past five years on projects of similar size, scope and complexity to the work required under this RFP. Past performance information submitted by offerors must be for work performed within the last five years. Past Performance will be determined “relevant” if the performance involves work performed within the past five years that is the same or similar in nature, size, and complexity to the goods and services being procured under this solicitation. Each description shall not exceed two pages each for a total maximum page count of 10 pages and must contain contact information, contract number with agency or business name, total value, narrative of work performed by the offeror, and the period of performance.

BEST VALUE EVALUATION

a) Award will be made to the Offeror(s): whose proposal conforms to the solicitation requirements; who is determined responsible in accordance with FAR 9.1 by

REQUEST FOR PROPOSAL 693JJ322R000002 Page 10 of 57 possessing the financial and other capabilities to fulfill the requirements of the contract; and whose proposal is evaluated by an integrated assessment of price and non-price evaluation factors, to provide the best value to the Government.

b) Evaluation of Proposals

(1) Initial Evaluation of Proposals - All offers received will be evaluated in accordance with the stated evaluation factors. The Government intends to make an award without discussions based solely upon initial proposals.

Therefore, offerors should ensure that their initial proposal constitutes their best offer in terms of both price and the technical solution being proposed. Notwithstanding, the Government reserves the right to hold discussions if determined to be in the Government’s best interest to do so.

(2) Discussions/Final Proposal Revisions - Except as described in (iii) below, if discussions are held, the Contracting Officer will establish a competitive range comprised of the most highly rated proposals. If the Contracting Officer determines that the number of proposals that would otherwise be in the competitive range exceeds the number at which an efficient competition can be conducted, the Contracting Officer may limit the number of proposals in the competitive range to the greatest number that will permit an efficient competition among the most highly- rated proposals. Only those offerors in the competitive range will be offered an opportunity to participate further in the procurement.

(i) The Contracting Officer will engage in discussions with all offerors in the competitive range in accordance with FAR 15.306.

At the conclusion of discussions, a final common cut-off date for submission of final proposal revisions will be established. Those offerors remaining in the competitive range will be invited to submit Final Proposal Revisions.

(ii) Final Evaluation of Offers. A final proposal evaluation will be performed after receipt of Final Proposal Revisions.

(iii) The Government may enter into discussions with any Offeror(s) solely regarding their Small Business Subcontracting Plan (if applicable), for the purpose of improving that plan in the interest of meeting the Government’s socio-economic goals, without developing a competitive range or engaging with all or other offerors. Offerors subject to this paragraph shall not be allowed to revise any other portion of their proposal.

EVALUATION CRITERIA

In determining which proposal provides the best value to the Government, an integrated evaluation and assessment of offers will be conducted. The evaluation will consist of three

REQUEST FOR PROPOSAL 693JJ322R000002 Page 11 of 57 factors: Technical, Past Performance, and Price. The Technical factor is more important than Past Performance, and when the two non-price factors (Technical and Past Performance) are combined, they are more important than price.

Based upon the results of the integrated assessment of the technical, past performance and price proposals, the Government may make an award to other than the lowest-priced offeror or the offeror with the highest technical rating if the source selection official determines that to do so would result in the best value to the Government.

Offeror’s proposals will be reviewed for page limitations. Pages exceeding the page limitation will be eliminated from evaluation.

A proposal receiving an “Unsatisfactory” or “Fail” rating in one or more factors may be removed from further consideration for award or continued evaluation.

a) TECHNICAL

Technical proposals will be evaluated and assessed based on the following criteria of equal importance. The technical factor consists of the following subfactors and elements.

The subfactors listed are relatively equal in importance.

(1) The proposal includes a technical/management approach demonstrating experience and capability to perform the tasks outlined in Section III and all the terms and conditions of the RFP:

(i) An approach to produce actual measured travel times and speeds from probe data and timely delivery of data.

(ii) The strength and completeness of all traffic, passenger and freight data sets as outlined in the Section III.

(iii) Proven consistency with existing NPMRDS implementation of requirements (i.e. requirements in Statement of Work Task 2)

(iv) The level of completeness of geographic coverage to be provided and the relevant temporal coverage.

(v) The completeness, strength and adequacy of proposed specifications and information on segment lengths, link information and other GIS file and data packet parameters to be provided as outlined in the statement of work.

(vi) The strength and completeness of proposed data dissemination approach(es).

(vii) The viability and usefulness of technical assistance approach.

(viii) The approach to and viability of Task 4 weekly data downloads and statistics deliverables to FHWA.

(ix) The level of statistical significance of data set.

REQUEST FOR PROPOSAL 693JJ322R000002 Page 12 of 57

(2) The proposal demonstrated a technically proposed staffing approach showing that proposed staff have the relevant experience, education and expertise to successfully perform the work required in the RFP;

(i) Knowledge of and proven expertise with the type of work to be performed as outlined in solicitation that shall include the following:

Probe data cleansing and aggregation.

GIS use and conflation.

Dissemination of data approaches.

Previous probe or traffic data analysis experience.

Technical assistance experience.

(ii) Proposed Key Personnel - Demonstrated education, experience, and accomplishments of key personnel to perform their proposed duties under the contract.

(iii) The proposal includes a sound, adequate, clear, and realistic proposed project team organization and contingency plan;

• Organizational Structure and Capability.

• Organizational hierarchies, roles, responsibilities, and lines of communication between team members.

• Sufficient approach to risk management.

b) PAST PERFORMANCE EVALUATION

Past performance information is evaluated as a predictor of future contract performance.

Using past performance information for each offeror, the Government will assess the probability that the instant requirement will be successfully completed in accordance with contract terms.

The Government will evaluate the merits of the offeror's past performance on the basis of its performance record. The Government will consider the following areas in its evaluation of past performance:

(1) Timeliness – Delivery or Performance;

(2) Quality of products or services provided;

(3) Cost control;

(4) Relevance and recency of the of the prior work to the requirements of the solicitation including scope, size, and currency.

(5) Overall Management of the project;

(6) Compliance with subcontracting plans/goals; and

(7) General trends in past performance.

The Government will consider past performance information submitted by the offeror on its predecessor companies, key personnel who have relevant experience, or its performance as a subcontractor performing major or critical aspects of the requirement.

REQUEST FOR PROPOSAL 693JJ322R000002 Page 13 of 57

Offerors may provide information on problems encountered on identified contracts and the offeror's corrective actions.

The Government reserves the right to assess the past performance of proposed subcontractors.

The Government will use its discretion to determine the sources of past performance information used in the evaluation, and the information may be obtained from references provided by the Offeror, the agency’s knowledge of contractor performance, other government agencies or commercial entities, or past performance databases.

In the case of an offeror without a record of relevant past performance or for whom information on past performance is not available, the offeror will not be evaluated favorably or unfavorably.

c) PRICE EVALUATION

Proposed prices will be evaluated but not scored. The Government will evaluate the Offeror’s total proposed price to determine if the price is fair and reasonable. The Government will evaluate total price inclusive of all options. The price evaluation will determine whether the proposed prices are complete and reasonable in relation to the solicitation requirements. Proposed prices must be entirely compatible with the technical proposal and consistent with the pricing requirements listed in this solicitation.

d) SMALL BUSINESS SUBCONTRACTING PLAN

The Small Business Subcontracting Plan (if applicable) will be evaluated on a “Pass/Fail” basis considering the Government’s socio-economic goals as stated in Attachment 7 and in compliance with the requirements of FAR 52.219-9.

REQUEST FOR PROPOSAL 693JJ322R000002 Page 14 of 57

SECTION II

SCHEDULE OF SERVICES

The Contractor shall furnish all services and required supplies to perform the tasks described under this contract entitled, The National Performance Management Research Data Set (NPMRDS) and Technical and Data-Sharing Support.

This is a non-set aside, Firm Fixed Price Request for Proposal and offerors shall propose a total price breakdown utilizing the CLIN chart below.

CLIN DESCRIPTION PRICE

The Contractor shall provide NPMRDS data sets, passenger data, and technical and data-sharing support services for NPMRDS.

Pricing: Firm Fixed Price Period of Performance: 12-months from the effective date of the award

Option Period 1: The Contractor shall provide NPMRDS data sets, passenger data, and technical and data-sharing support services for NPMRDS.

Pricing: Firm Fixed Price Period of Performance: 12-month extension to the period of performance

Option Period 2: The Contractor shall provide NPMRDS data sets, passenger data, and technical and data-sharing support services for NPMRDS.

Option Period 3: The Contractor shall provide NPMRDS data sets, passenger data, and technical and data-sharing support services for NPMRDS.

Option Period 4: The Contractor shall provide NPMRDS data sets, passenger data, and technical and data-sharing support services for NPMRDS.

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 request milestone payments in accordance with work completed and accepted by the Government.

Satisfactory completion and acceptance will be determined by the Contracting Officer’s Representative (COR).

REQUEST FOR PROPOSAL 693JJ322R000002 Page 15 of 57

SECTION III

STATEMENT OF WORK

1.0 OVERVIEW AND BACKGROUND

The Federal Highway Administration (FHWA), an agency within the U.S. Department of Transportation (US DOT) 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. Although State, local, and tribal governments own most of the Nation’s highways, FHWA provides financial and technical support for constructing, improving, and preserving America’s highway system.

Continued growth in both traffic and freight volumes means that significant portions of the transportation system experience congested conditions on a regular basis and provide increasingly unreliable service. Where these conditions exist, a more proactive approach to operating the system is needed. Operating the system in a more proactive manner can help reduce congestion, improve freight productivity, improve safety, reduce harmful greenhouse gas emissions, and lead to more livable communities. Operating the system proactively can also defer or eliminate the need for increasingly expensive and difficult capacity expansion projects.

FHWA engages in activities to develop and implement:

• Real-time and forecasted information;

• Measuring/monitoring passenger and freight system performance;

• Analytical foundation/tools/data;

• State of the art technologies and strategies;

• Development of standards for information exchange;

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

Projects, including operational tests of ITS technologies;

• 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; and

• Provision of the National performance Management Research Data Set (NPMRDS) for use by US DOT, State Departments of Transportation (DOTs) and Metropolitan Planning Organizations (MPO), and their contractors.

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 Performance Measure (FPM) 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) and the Fixing America’s Surface Transportation (FAST) Act. Through this contract, the FHWA Office of Highway Policy Information seeks to continue to provide the NPMRDS data as a tool for FHWA, State DOTs, MPOs and their contractors for use in performance measurement and management activities.

REQUEST FOR PROPOSAL 693JJ322R000002 Page 16 of 57

For more information on the existing FPM, 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://www.ops.fhwa.dot.gov/perf_measurement/ucr/index.htm

The Office of Transportation Management currently has a contract in place to provide the NPMRDS, which serves multiple FHWA functions and is the primary resource to support MAP- 21 Performance Measurement activities, specifically those associated with the third performance measures rulemaking, or PM3. The FHWA requires access to travel time data for all vehicles, passenger and freight traffic to support its research requirements, as well as the legislatively mandated performance measure requirements enacted under MAP-21 and the FAST Act. The FHWA does not collect travel time data from primary sources, so a contract with a data provider is the most efficient option for acquiring access to data. This new contract will be under FHWA’s Office of Highway Policy Information.

2.0 OBJECTIVE

The objective of the contract is to support the FHWA Office of Highway Policy Information for continued NPMRDS technical assistance and data-sharing support and to provide:

• Access to a national travel time data set with specific attributes required for the

NPMRDS;

• Shape-files to support analysis of the data, including conflation with the Highway Performance Monitoring System (HPMS) and/or its attributes;

• Access to the data via user friendly online download;

• Access and data sharing agreements for all federal partners, State DOTs and MPOs;

• Technical Assistance for use of the data; and

• Data quality validation and calibration; and

• Monthly and weekly statistics, reports and downloads.

3.0 CONTRACT SCOPE

The purpose of this contract is to provide technical data, services and support for the NPMRDS to be available for use by FHWA/US DOT and for State DOTs and MPOs for their use in performance measurement and management activities. This technical support shall require the Contractor to provide FHWA perpetual access to an average travel time data set derived from vehicle probes, disseminate this data to other government agencies, provide updated shapefiles and conflation where necessary, and provide technical support for the data set. The Contractor shall also develop and carry out data validation, calibration quality plans and develop descriptive metadata documents. Finally, the Contractor shall provide weekly and/or monthly downloads and statistics/reports on several metrics.

4.0 DETAILED REQUIREMENT

NOTE: The FHWA is not collecting personally identifiable information (PII) under this contract. PII includes names, medical information, personally identifiable financial information

REQUEST FOR PROPOSAL 693JJ322R000002 Page 17 of 57

(PIFI) and unique identifiers such as driver’s license, passport, or Social Security numbers.

In order to meet the contract objectives, the Contractor shall perform the following tasks:

4.1 Task 1 - Project Management

Kick-off Meeting

Within two weeks after award, key members of the Contractor’s team, as identified by the Government, shall participate in a virtual kick-off meeting with FHWA technical staff, to include the Contracting Officer’s Representative (COR) to discuss the tasks and delivery schedule, delineate roles and responsibilities, and establish communication protocols, resolve and identify potential problems, and clarify understandings of the technical aspects of the contract. The Contractor shall present to FHWA their proposed Draft Management and Work Plan and when applicable, address the comments/suggestions made by FHWA. The Contractor shall prepare and submit to the COR summary meeting minutes within one week after the kick-off meeting.

Based on comments provided at the kick-off meeting and comments provided in writing from the COR, the Contractor shall 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 shall be consistent with the contract and all exhibits. The Management and Work Plan shall not be construed to override or change the requirement or exhibits of this contract. The controlling document for the requirement shall be the contract, its exhibits, and any modifications issued.

Management and Work Plan

The Contractor shall 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 shall complete a Final Management and Work Plan. The Contractor shall then update the Management and Work Plan on a quarterly basis.

The Management and Work Plan shall include all 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

REQUEST FOR PROPOSAL 693JJ322R000002 Page 18 of 57 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 develops 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 shall execute the monitoring and control plan to ensure the project is meeting the deliverables outlined in the Statement of Work.

8. Human Resource Plan –To include roles and responsibilities, project organizational charts, and staffing management plan for the prime and any sub-contractors.

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

Progress Reports

The Contractor shall submit progress reports to the COR and the Contracting Officer (CO).

These reports shall be prepared monthly and submitted within the first five business days of the month following the reporting period. The reports shall be in format as directed by the COR and, at a minimum, include the following items:

1. A clear account of the work performed under each task during the reporting period.

2. An outline of the work to be accomplished during the next reporting period.

3. A description of any problem encountered or anticipated that will affect the completion of any work within the timeframe set, together with recommended solutions to such problems; or, a statement that no problems were encountered.

Diagnostic Reports with Heat Map

The Contractor shall submit monthly diagnostic reports along with the monthly progress that includes the following:

1. Percentage of five-minute bins covered for all traffic, freight and passenger for both Interstate and Other National Highway System (NHS).

2. A Heat Map with density of coverage across the NHS for passenger, freight, and combined coverage. The density of coverage can be descriptive of the percent of total possible 5-minute time periods filled with average travel times (i.e. a range or delineation to show density of coverage). The report shall be delivered as a map and/or via web-based format.

Annual Report

The Contractor shall furnish 1 electronic copy of a letter-type annual report to the CO and to the COR on or before 30 calendar days before the end of each contract year. The annual report shall contain the following:

REQUEST FOR PROPOSAL 693JJ322R000002 Page 19 of 57

1. A brief narrative commenting on performance during the reporting period for each of the following areas:

Quality of Product/Service Schedule Business Relations Management of Key Personnel Utilization of Small Businesses Other

2. The annual report shall also include, in a separate file, a Traffic Message Channel (TMC) inventory for the prior year. The inventory shall include such items as necessary for FHWA to check metric submissions each year based on NPMRDS data used in metric calculations. At minimum, the annual TMC inventory shall contain for each TMC on the NHS the following fields:

tmc, type, roadnumber, roadname, firstname, lineartmc, country, state, county, zip, direction, start_latitude, start_longitude, end_latitude, end_longitude, miles, road_class, func_class, timezone_name, num_lanes, tmclinear, frc, border_set, f_system, urban_code, faciltype, structype, thrulanes, route_numb, route_sign, route_qual, altrtename, aadt, aadt_singl, aadt_combi, nhs, nhs_pct, strhnt_typ, strhnt_pct, truck, isprimary, state_code, and year_record o Refer to the following document for more information on these requirements:

Highway Performance Monitoring System Field Manual Supplemental Guidance:

Travel Time Metric Data Reporting Requirements & Specifications at the following link: https://www.fhwa.dot.gov/tpm/guidance/pm3_hpms.pdf.

o Definitions: “Border_set” is a simple Yes or No on whether that element is part of the border data set as specified on p. 20, Geographic Coverage, Metadata.

“isprimary” indicates the “primary” TMC for an Interstate segment that has overlapping TMCs (this is only applicable when there are overlapping segmentation and may not be needed otherwise). “Timezone_name” is the time zone that a majority of a segment (in current NPMRDS, the TMC) is in.

4.2 Task 2 - National Performance Management Research Data Set

The Contractor shall provide FHWA perpetual access to an average travel time and speed data set derived from vehicle probes. The Contractor shall also provide such access to State DOTs, MPOs, other operating administrations at USDOT, and Federal partners involved in transportation analyses. The data set shall be accessible by Contractors performing work for FHWA, State DOTs, MPOs, other operating administrations at USDOT, and Federal partners.

Finally, licensed users shall have the right to aggregate data to share with the public as well as any products (e.g., performance measures) derived from the data set.

Probe Vehicle Requirements

The Contractor shall have access to vehicle probe-based travel time and speed data for the full possible Period of Performance. The FHWA requires actual, observed vehicle travel times and

REQUEST FOR PROPOSAL 693JJ322R000002 Page 20 of 57 average speeds from vehicle probe data to be delivered as part of this contract. Imputed, predicted or historical data shall not be included, except for 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 and speed over a path where individual segment lengths are too short to receive a time/speed for each.

Average Travel Time and Average Speed Data Requirements

The Contractor shall provide the following data elements:

• Average travel times and average speeds from vehicle probe data in three classifications:

all vehicles, passenger vehicles only and freight trucks only.

o The average travel times and average speeds shall be delivered for every 5-minute period of every day, month, year covered under this contract for every road segment on the NHS.

• The Contractor shall provide a descriptive data element that informs the data user about the following and propose how they would implement this data element:

o Whether or not the data (average travel time/average speed) is path processed (“P” or similar) o An indication of the sample size (e.g., “1” means one probe, “2” means between 1 and 5 probes; 3 means more than 5 probes or more specific) – proposer shall identify the scale/option they would use. The Government would like the most specific indication possible/allowable.

The data elements must be identifiable by FHWA roadway ID and roadway functional class per HPMS definition at http://www.fhwa.dot.gov/policyinformation/hpms/fieldmanual/ - see more details in the “Geographic Coverage” section below.

Geographic Coverage, Metadata

At a minimum, the data set shall be provided from a statistically significant sample size of probes for the following geographic coverage (approximately 220,000 centerline miles of road):

• United States Interstate System;

• NHS including NHS intermodal connectors;

• Strategic Defense Network Roadways (STRHANET); and

• Border crossings on principal arterials. Arterials within a five-mile radius on either side of the border at the top 20 United States/Canada Border Crossings as measured by average daily truck trips. These crossings are:

o MI: Detroit o NY: Buffalo-Niagara Falls o MI: Port Huron o WA: Blaine o NY: Champlain-Rouses Pt.

o ND: Pembina o NY: Alexandria Bay/Cape Vincent

REQUEST FOR PROPOSAL 693JJ322R000002 Page 21 of 57 o WA: Sumas o MT: Sweetgrass o VT: Derby Line o ME: Houlton o ME: Jackman o VT: Highgate Springs o ND: Portal o ME: Calais o ID: Eastport o WA: Lynden o MI: Sault Ste. Marie o NY: Ogdensburg o ME: Madawaska

• Arterials within a five-mile radius on either side of the border at the top six United

States/Mexico Border Crossings as measured by average daily truck trips. These crossings are:

o TX: Laredo o CA: Otay Mesa o TX: El Paso o TX: Hidalgo o CA: Calexico East o AZ: Nogales

Transportation network Geographic Information System (GIS) and data file parameters for the NPMRDS shall include the following:

1. The Contractor shall provide data via logical segments and segment lengths, preferably directly comparable to HPMS data.

2. Segment or…