DTFH6117R00005.pdf

DTFH6117R00005

SOLICITATION, OFFER AND AWARD

4. TYPE OF SOLICITATION2. CONTRACT NUMBER 3. SOLICITATION NUMBER

7. ISSUED BY CODE 8. ADDRESS OFFER TO (If other than Item 7)

ORDER UNDER DPAS (15 CFR 700)

6. REQUISITION/PURCHASE NUMBER

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".

NEGOTIATED (RFP)

SEALED BID (IFB)

5. DATE ISSUED

1. THIS CONTRACT IS A RATED RATING PAGE OF PAGES

1 63

C. E-MAIL ADDRESS

EXT.NUMBERAREA CODE

B. TELEPHONE (NO COLLECT CALLS)A. NAME

10. FOR

INFORMATION

CALL:

CAUTION: LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and conditions contained in this solicitation.

(Date)(Hour) depository located in copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if hand carried, in the

SOLICITATION

9. Sealed offers in original and

PART IV - REPRESENTATIONS AND INSTRUCTIONS

OTHER STATEMENTS OF OFFERORS

EVALUATION FACTORS FOR AWARD

INSTRS., CONDS., AND NOTICES TO OFFERORS

REPRESENTATIONS, CERTIFICATIONS AND

LIST OF ATTACHMENTS

CONTRACT CLAUSES

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACH.

I

J

K

L

M SPECIAL CONTRACT REQUIREMENTS

CONTRACT ADMINISTRATION DATA

DELIVERIES OR PERFORMANCE

INSPECTION AND ACCEPTANCE

PACKAGING AND MARKING

DESCRIPTION/SPECS./WORK STATEMENT

SUPPLIES OR SERVICES AND PRICES/COSTS

SOLICITATION/CONTRACT FORM

PART II - CONTRACT CLAUSESPART I - THE SCHEDULE

H

G

F

E

D

C

B

A

SEC. DESCRIPTION PAGE(S) (X) DESCRIPTION SEC. (X)

11. TABLE OF CONTENTS

18. OFFER DATE17. SIGNATURE

SUCH ADDRESS IN SCHEDULE.

IS DIFFERENT FROM ABOVE - ENTER

15C. CHECK IF REMITTANCE ADDRESS

EXT.NUMBERAREA CODE

15B. TELEPHONE NUMBER

(Type or print)AND

ADDRESS

OF

OFFEROR

CODE FACILITY

16. NAME AND TITLE OF PERSON AUTHORIZED TO SIGN OFFER15A. NAME

DATEAMENDMENT NO.DATEAMENDMENT NO.

and related documents numbered and dated):

amendments to the SOLICITATION for offerors

(The offeror acknowledges receipt of

14. ACKNOWLEDGEMENT OF AMENDMENTS

CALENDAR DAYS (%)30 CALENDAR DAYS (%)20 CALENDAR DAYS (%)10 CALENDAR DAYS (%)

(See Section I, Clause No. 52.232.8)

13. DISCOUNT FOR PROMPT PAYMENT

designated point(s), within the time specified in the schedule.

by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the

12. In compliance with the above, the undersigned agrees, if this offer is accepted within ______________ calendar days (60 calendar days unless a different period is inserted

NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

OFFER (Must be fully completed by offeror)

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

28. AWARD DATE

(Signature of Contracting Officer)

27. UNITED STATES OF AMERICA

25. PAYMENT WILL BE MADE BY

26. NAME OF CONTRACTING OFFICER (Type or print)

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

ITEM

(4 copies unless otherwise specified)

23. SUBMIT INVOICES TO ADDRESS SHOWN IN

41 U.S.C. 253 (c) ( 10 U.S.C. 2304 (c) (

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

21. ACCOUNTING AND APPROPRIATION20. AMOUNT19. ACCEPTED AS TO ITEMS NUMBERED

AWARD (To be completed by government)

CODE

HOTM70731604611/11/2016

X

HCFA

FEDERAL HIGHWAY ADMINISTRATION

OFFICE OF THE CHIEF FINANCIAL OFFICER

OFFICE OF ACQUISITION & GRANTS MGMT

1200 NEW JERSEY AVENUE, SE

WASHINGTON DC 20590

until 1200 ES local time 12/07/2016

Sarah H. Khan 202 Sarah.Khan@dot.gov

366-0220

X

X

X

X

X

X

X

X

X

X

X

X

X

PAGE(S)

Tiffany A. Youther

AUTHORIZED FOR LOCAL REPRODUCTION

Previous edition is unusable

STANDARD FORM 33 (Rev. 9-97)

Prescribed by GSA - FAR (48 CFR) 53.214(c) refer to Section L.8

ITEM NO. SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

NAME OF OFFEROR OR CONTRACTOR

2 63

CONTINUATION SHEET

REFERENCE NO. OF DOCUMENT BEING CONTINUED PAGE OF

DTFH6117R00005

(A) (B) (C) (D) (E) (F)

The Contractor shall furnish all equipment, travel, materials and personnel necessary to provide the Federal Highway Administration (FHWA) with non-personal technical and data-sharing support for the National Performance Management

Research Data Set (NPMRDS).

Period of Performance: 01/01/2017 to 12/31/2022

00001 The Contractor shall provide technical and 12 EA data-sharing support for the NPMRDS and NPMRDS data sets.

Pricing: FFP

Price:

Payment: See J. 1

Period of Performance: 12 months

(Not Separately Priced)

00002 Optional Data - The Contractor shall provide 12 MO passenger data.

Pricing: FFP

Price:

Payment: See J. 1

Period of Performance: 12 months

(Option Line Item)

00003 Option 1 12 MO

The Contractor shall provide technical and data-sharing support for the NPMRDS and NPMRDS data sets.

Pricing: FFP

Price:

Payment: See J. 1

Period of Performance: 12 months

(Option Line Item)

00004 Option 1 12 MO

Optional Data - The Contractor shall provide passenger data.

Pricing: FFP

Price:

Payment: See J. 1

Continued ...

OPTIONAL FORM 336 (4-86)

Sponsored by GSA

FAR (48 CFR) 53.110

NSN 7540-01-152-8067

3 63

CONTINUATION SHEET

REFERENCE NO. OF DOCUMENT BEING CONTINUED PAGE OF

DTFH6117R00005

(A) (B) (C) (D) (E) (F)

Period of Performance: 12 months

(Option Line Item)

00005 Option 2 12 MO

The Contractor shall provide technical and data-sharing support for the NPMRDS and NPMRDS data sets.

Pricing: FFP

Price:

Payment: See J. 1

Period of Performance: 12 months

(Option Line Item)

00006 Option 2 12 MO

Optional Data - The Contractor shall provide passenger data.

Pricing: FFP

Price:

Payment: See J. 1

Period of Performance: 12 months

(Option Line Item)

00007 Option 3 12 MO

The Contractor shall provide technical and data-sharing support for the NPMRDS and NPMRDS data sets.

Pricing: FFP

Price:

Payment: See J. 1

Period of Performance: 12 months

(Option Line Item)

00008 Option 3 12 MO

Continued ...

OPTIONAL FORM 336 (4-86)

Sponsored by GSA

4 63

CONTINUATION SHEET

REFERENCE NO. OF DOCUMENT BEING CONTINUED PAGE OF

DTFH6117R00005

(A) (B) (C) (D) (E) (F)

Optional Data - The Contractor shall provide passenger data.

Pricing: FFP

Price:

Payment: See J. 1

Period of Performance: 12 months

(Option Line Item)

00009 Option 4 12 MO

The Contractor shall provide technical and data-sharing support for the NPMRDS and NPMRDS data sets.

Pricing: FFP

Price:

Payment: See J. 1

Period of Performance: 12 months

(Option Line Item)

00010 Option 4 12 MO

Optional Data - The Contractor shall provide passenger data.

Pricing: FFP

Price:

Payment: See J. 1

Period of Performance: 12 months

(Option Line Item)

00011 Other Direct Cost- Cost Reimbursable

Pricing: CR

Estimated travel: $50,000

Estimated Equipment Material: $100,000

OPTIONAL FORM 336 (4-86)

Sponsored by GSA

SECTION B - Supplies or Services/Prices

B. 1 FIXED PRICE WITH REIMBURSABLE MATERIALS

The Contractor shall furnish all equipment, travel, materials and personnel necessary to provide the Federal Highway Administration (FHWA) with non-personal technical and data-sharing support for the National Performance Management Research Data Set. (NPMRDS), as described in Section C below.

This is a Firm-Fixed-Price (FFP) contract.

B. 2 FIRM FIXED PRICE

The total amount for the performance of this FFP contract is [Total Amount].

NOTE: See Exhibit J.1 for the Milestone Payment Schedule.

SECTION C - Description/Specifications

C.1 BACKGROUND

The FHWA, an agency within the U.S. Department of Transportation (USDOT) is charged with the broad responsibility of ensuring that America’s roads and highways continue to be the safest and most technologically up-to-date. 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, including operational tests of intelligent transportation system technologies;

• Development of standards for information exchange;

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

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

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

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

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

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

To date, the FHWA has evaluated measures of travel time, travel time variability, reliability, speeds and related metrics through efforts such as the data and value-added products derived from the Urban Congestion Report (UCR), Freight 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). Through this contract, the FHWA Office of Travel Management (HOTM) seeks to continue to provide the NPMRDS data as a tool for FHWA, State Department of Transportations (SDOTs) and Metropolitan Planning Organization (MPO) use in performance measurement and management.

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

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

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

The HOTM currently has a contract in place to provide NPMRDS, which serves multiple FHWA functions and will be a primary resource to support MAP-21 Performance Measurement activities. The FHWA requires access to travel time data for all traffic, passenger and freight traffic to support its research requirements, as well as the legislatively mandated performance measure requirements enacted under MAP-21 and Fixing America’s Surface Transportation (FAST) Act. The FHWA does not collect travel time data from primary sources, so a contract with a data provider would be the most efficient option for acquiring access to data.

C.2 OBJECTIVE

The objective of the contract is to support the FHWA HOTM 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;

• Access to the data via electronic download;

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

• Technical Assistance for use of the data; and

• Data quality validation and calibration.

C.3 CONTRACT SCOPE

The scope of the contract is limited to providing limited to providing technical support of the NPMRDS to be available for use by 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 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.

C.4 DETAILED REQUIREMENT

NOTE: The FHWA is not collecting personally identifiable information (PII) under this contract. PII includes names, medical information, personally identifiable financial information (PIFI) and unique identifiers such as driver’s license, passport, or Social Security numbers.

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

Task 1 - Project Management

Within two weeks after award, key members of the Contractor’s team shall participate in an on-site (DOT Headquarters) kick-off meeting with FHWA technical staff, to include the Contracting Officer’s Representative (COR) and appropriate contractor staff 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’s project manager shall attend in person with key staff, and other contractor representatives including sub-contractor representatives may participate via conference call. 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 a meeting minute summary within one week after the kick-off meeting.

Based on the meeting, 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.

http://www.ops.fhwa.dot.gov/perf_measurement/ucr/index.htm http://searchfinancialsecurity.techtarget.com/definition/personally-identifiable-financial-information http://whatis.techtarget.com/definition/unique-identifier-UID http://whatis.techtarget.com/definition/unique-identifier-UID

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 update the Management and Work Plan on a quarterly basis.

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

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

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

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

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

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

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

7) Monitoring and Control Project Work – A plan that identifies how the project work will be tracked, reviewed, and regulated to meet the performance objectives of the project management plan. The Contractor 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.

Task 2 - National Performance Management Research Data Set

The Contractor shall provide FHWA perpetual access to an average travel time 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 the 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 data for the full possible Period of Performance. The FHWA requires actual, observed vehicle travel times and average speeds from vehicle probe data to be delivered as part of this contract. Imputed, predicted or historical data shall not be included, with the exception of path processed data or similar approach. The FHWA’s understanding is that path processed data, in general, is using a single (or more than one) probe to determine travel time over a path where individual segment lengths are too short to receive a time/speed for each.

Average Travel Time and Average Speed Data Requirements

The Contractor shall provide:

• Average travel times and average speeds from vehicle probe data in two classifications: all vehicles and freight trucks.

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.

Optional Data:

• The Contractor shall also provide average travel times and average speeds from vehicle probe data for an optional third classification: passenger only data.

• The Contractor shall provide an optional 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 (travel time/average speed) is path processed (“P”) 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) – proposer shall identify the scale/option they would use.

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.

Path Processing Method

The Contractor shall provide a description of and sample set of any path processed data or similar approaches that are proposed to be used. The Contractor shall provide a detailed explanation of how path processing or similar approach would work and when it would be applied. FHWA’s understanding is that path processed data, in general, is using a single (or more than one) probe to determine travel time over a path where individual segment lengths are too short to receive a time/speed for each.

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 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 http://www.fhwa.dot.gov/policyinformation/hpms/fieldmanual/

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

2. Segment or link definitions shall, at a minimum, contain:

• Beginning and ending latitude; beginning and ending longitude; heading/direction;

• Common name or route number;

• Road class; and unique identifier.

• Attribute data items 1, 2, 3, 4, 17, 18, 19, 20, 64, 65 and 66 as defined in the HPMS Field

Manual http://www.fhwa.dot.gov/policyinformation/hpms/fieldmanual/chapter2.cfm#chapt2_2_2

• On the network side, the same data items as listed above should be included for all links in both directions. The contractor shall use the data from the link:

http://www.fhwa.dot.gov/policyinformation/hpms/shapefiles.cfm (HPMS 2014 data, file “PA_NHS.zip”) for testing.

3. GIS files shall be usable with HPMS geographic network files.

Probe Data Collection Frequency, Quality and Accuracy

Probe data sets must be able to provide data at the frequency and accuracy required to calculate travel time measures for use in performance management. The FHWA requires that this data to be provided in 5 minute increments.

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.

Data Sharing

The FHWA will share data with its contractors, State DOTs, MPOs and their designated contractors, for access to the vehicle data set described above.

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

The FHWA, public transportation agencies and officially designated representatives shall have the right to use the vehicle probe data provided under this contract for transportation planning and operational analyses, service and data quality validation analyses, and all other internal organization applications.

The Contractor shall provide unique log-ins for all users. This means multiple log-ins for all data licensees – including users that may be contractors for the data licensee. The Contractor shall track usage of the data set and provide FHWA with a periodic usage report that provides the contact information for data users including the main contact at each data licensee and all authorized users, statistics on users (i.e. state versus MPO users), and identification of top users (by # of log-ins). It shall be the responsibility of the Contractor to remove log-ins from users who no longer have access to the NPMRDS.

The periodic usage report must include the following fields:

http://www.fhwa.dot.gov/policyinformation/hpms/fieldmanual/chapter2.cfm#chapt2_2_2 http://www.fhwa.dot.gov/policyinformation/hpms/shapefiles.cfm

• Name of Agency

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

• Name of Agency contact

• Address

• Phone number

• E-mail

• All users under this license by:

o Name o E-mail address

Processing Timeframe

The NPMRDS shall be analyzed and processed, at maximum, on a monthly basis. Monthly data shall be provided and made available to meet the needs of the Urban Congestion Report contractors, at maximum, five business days after the close of the month. More frequent or continuous data feeds throughout the month may be considered as an alternate. The full monthly data set must be provided, at maximum, 15 business days after the close of each month. The proposal should include proposed processing timeframe.

Data Dissemination

The Contractor shall provide data to users via an electronic download format or direct download format or some other similar format mutually agreed upon between the contractor and FHWA, within the above processing timeframe. This may require the creation of a secure web page, internet portal or other electronic transfer mechanism for users to pull/download data for their use in support of performance management as described in the above data sharing section. The FHWA, State DOT, MPO, other USDOT, and designated contractor users of the data will request access to the data from the Contractor. The Contractor shall provide FHWA with the names and e-mails of approved users. The data download method shall provide for unique log-ins for approved users. The data shall be available within the appropriate timeframe on any dissemination option provided. The monthly data sets shall be downloadable by state (no regional files).

Technical Support

The Contractor shall provide technical support for FHWA/US DOT users; FHWA contractors; State DOT/MPO users; and State DOT/MPO contractors. Technical support shall be in the form of e-mail.

Primary areas of technical assistance include:

1. Data set elements

2. Data provision/access

3. Data coverage and/or data quality

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

5. Shapefile/GIS assistance in conflating the data

Technical assistance also includes but is not limited to assistance in downloading data, simple uses of the data such as sorting, querying and processing, assistance with shape files, visualization and linear referencing to networks, conflation, use of tools to work with the data and simple performance measurement. The Contractor shall provide a quick start guide to as a primer for data usage that is available to new users.

Additionally, the Contractor shall participate in FHWA quarterly user webinars; discussion, questions, providing information and other support for the FHWA NPMRDS web site(s); be available for two-hour quarterly presentations or in person to data users or potential users; and provide any necessary guides, fact sheets, or directions related to accessing and getting started with the data. Technical support issues and questions shall be addressed within two business days of receipt.

The Contractor shall receive the technical assistance requests directly (via e-mail) and shall log all requests and responses/time of final response for submittal to FHWA in the quarterly progress reports.

Task 3 - Data Validation, Calibration Quality Plans and Descriptive Metadata Documents

The Contractor shall develop a Data Validation, Calibration Quality Plan for the NPMRDS that describes the actions and activities that document and repeatedly confirm the quality of the data set. This plan shall be consistent with the specifications and information provided by the Contractor in Task 2 relating to providing the frequency, quality, accuracy, and spatial and temporal coverage required to calculate speed, travel time and reliability measures. The Contractor shall be able to develop and implement a valid and reliable data validation methodology to validate travel time data. The Contractor shall carry out this Data Validation, Calibration Quality Plan and provide quarterly reports on the results of the quality assessment and validation, any actions needed or required to be taken to meet performance and quality thresholds, and how these actions will be taken.

The Contractor shall develop a document containing descriptive metadata regarding the data set. This document should be comprehensive in nature and describe and explain the data, how it is collected and how it is processed. This document will be made public to the NPRDS users and should not contain any confidential or proprietary information.

C.5 NPMRDS Standard

The NPMRDS must conflate to FHWA’s current NPMRDS and provide the same elements:

• Actual observed travel times for the NHS, STRAHNET, and five mile radius interstates and arterials at border crossings.

• Provided in 5-minute epoch of a 24/7 period, 365 days a year.

• Provide data sharing and data downloading options for users.

• Provide a network/shape-file.

• Provide quality control and calibration.

• Provide technical support, user analysis and user reference materials.

C.6 FIXED PRICE PROGRESS REPORTS

The Contractor shall submit progress reports to the COR and the Contract Specialist (CS). These reports shall be prepared on a monthly basis 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:

(a) A clear account of the work performed under each task during the reporting period.

(b) An outline of the work to be accomplished during the next reporting period.

(c) 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.

C. 7 DIAGNOSTIC REPORTS WITH HEAT MAP

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

1. Percentage of five minute bins covered for all traffic, freight and passenger (if optioned) for both

Interstate and Other 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 epochs filled with average travel times (i.e. a range or delineation to show density of coverage). The report shall be delivered as a high resolution PDF file, web-based format or other readable electronic format with features drawn to fine levels making detailed viewing possible down to the city level.

C.8 ANNUAL REPORT

The contractor shall furnish 1 electronic copy (in Microsoft Office 2010 or equivalent) of a letter-type annual report to the Contracting Officer and to the Contracting Officer’s Representative on or before 30 calendar days before the end of each contract year. The annual report shall contain the following:

(a) A brief narrative commenting on performance during the reporting period for each of the following areas:

(1) Quality of Product/Service

(2) Schedule

(3) Cost Control

(4) Business Relations

(5) Management of Key Personnel

(6) Utilization of Small Businesses

(7) Other

The annual report will be used by the COR as part of the annual performance review.

SECTION D - Packaging and Marking

D.1 PACKAGING

Preservation, packing, and packaging of items for shipment shall be in accordance with best commercial practices and adequate for acceptance by common carrier for safe transportation at the most economical rates.

The contractor shall clearly mark each shipment with the company name, the contract number, and as appropriate the item identification, quantity of items, and notice of partial or final delivery.

Ship to: Federal Highway Administration Office of Travel Operations 1200 New Jersey Avenue, SE Washington, DC 20590

Marked for: COR

SECTION E - Inspection and Acceptance

E.1 INSPECTION AND ACCEPTANCE

All work hereunder shall be subject to review by the Government. The COR specified in the COR appointment letter is responsible for inspection and acceptance of all incoming shipments, documents, and services.

E.2 GOVERNMENT ACCEPTANCE PERIOD

Unless stated elsewhere, the COR will have 10 business days to review draft deliverables and make comments. The Contractor shall have five business days to make corrections and return the corrected deliverable to the Government.

Upon receipt of the final deliverables, the COR will have 10 business days for final review prior to acceptance or to provide documented reasons for non-acceptance to the Contractor.

When the Government fails to complete the review within the review period, or take steps necessary to acknowledge the delay and extend the review period, the deliverable will be deemed accepted by the Government.

E. 3 CLAUSES INCORPORATED BY REFERENCE

FAR 52.246-4 INSPECTION OF SERVICES - FIXED-PRICE. (AUG 1996)

SECTION F - Deliveries or Performance

F.1 PERIOD OF PERFORMANCE

The period of performance under this contract consists of a 12-month base period and four 12-month optional periods, beginning on the effective date of the contract. Should the Government elect to exercise any of the optional periods for additional services under this contract, the total contract period of performance shall be completed within the time frame specified in that optional period. In no event shall the total contract performance period exceed 60 months without written authorization from the Contracting Officer.

F. 2 DELIVERABLE/DELIVERY SUMMARY

The deliverable schedule can be found in Exhibit No. J.2.

F.3 PLACE OF DELIVERY

All deliverables, except the annual and monthly progress report shall be delivered to the COR.

The annual and monthly progress reports shall be delivered to COR and Contract Specialist.

F.4 PLACE OF PERFORMANCE

Unless otherwise specified in Section C, work performed under this contract shall be performed at the Contractor’s facility.

F.5 MINIMUM REQUIREMENTS FOR MATERIALS TO BE POSTED ON FHWA WEBSITES

All web-based deliverables shall conform to the Minimum Requirements for FHWA Web Pages and be compatible with the current FHWA web platform of Adobe ColdFusion (version 10 compatible) and Microsoft SQL (server 2012 or higher compatible). Deliverables will be evaluated for Section 508 compliance, including graceful degradation when JavaScript is disabled and color contrast tests.

Deliverables shall meet W3C coding standards (http://www.w3.org/), FHWA coding standards, and conform to DOT Secure Web Application standards to prevent cross-site scripting (XSS) and SQL Injection.

F.6 CLAUSES INCORPORATED BY REFERENCE

52.242-15 STOP-WORK ORDER. (AUG 1989)

52.247-34 F.O.B. DESTINATION. (NOV 1991)

SECTION G - Contract Administration Data

G.1 PAYMENT- (FFP)

Payment of the prices delineated in Exhibit J.1 will be made after FHWA acceptance in writing, of the deliverables and receipt of a proper invoice.

G. 2 TRAVEL AND PER DIEM

Travel (other than local) may be expected to occur throughout the duration of the contract. The COR will issue the written request for travel if required (excluding local travel).

The Contractor shall invoice in accordance with FAR 31.205-46, Travel Costs, and Federal Travel Regulations, and must submit documentation of all travel costs.

Travel requirements under this contract shall be met using the most economical form of transportation available. All travel shall be scheduled sufficiently in advance to take advantage of offered discount rates, unless authorized by the Contracting Officer.

The following web site provides information on current Per Diem rates:

http://www.gsa.gov/portal/category/100120

G.3 SUBCONTRACTS – ADVANCE NOTIFICATION AND CONSENT

Under this contract, the requirement of FAR 44.2, Consent to Subcontracts, has been fulfilled for the following subcontracts:

(a) [APPROVEDSUBCONTRACTORNAME]

Any future change or revision to the Statement of Work or other applicable aspects of this contract shall include the subcontract(s) only to the extent that performance of the subcontract(s) is directly affected by the change or revision.

G.4 INVOICES

Submit all invoices to one of the following invoice addresses:

All invoices and required supporting documents shall be sent via e-mail to the following e-mail address:

9-AMC-AMZ-FHWA-Invoices@faa.gov .

(a) Include the invoice as an attached PDF document

(b) Include in the e-mail subject line the following:

(1) Invoice No.

(2) Contract Number

(3) Name of your Company/Organization

(4) Attention: Contract Specialist Example: Invoice No. 35 – DTFH6117C000XX – Contractor Name – Attention: Contract Specialist

If the invoice and supporting documents exceed 8 MB as an e-mail attachment, the Contractor must select one of the other submission options presented below:

Invoices submitted via an overnight service must use the following physical address:

http://www.gsa.gov/portal/category/100120 mailto:9-AMC-AMZ-FHWA-Invoices@faa.gov

MMAC

FHWA/AMZ-150

6500 S. MacArthur Blvd Oklahoma City, OK 73169 Attention: Contract Specialist Express Delivery Point of Contact: Ryan Wisniewski, 405-954-8252

Invoices may be submitted via regular U.S. Postal Service to the following address:

Federal Highway Administration Markview Processing P.O. Box 268865 Oklahoma City OK 73126-8865 Attention: Contract Specialist

An invoice submitted to an address other than those identified will be returned to the vendor as non-conforming.

G.5 TECHNICAL DIRECTION

Performance of the work under this contract is subject to the Technical Direction of the COR. The term “Technical Direction” is defined to include, without limitation, the following:

(a) Direction to the Contractor which redirects the efforts, shifts work emphasis between work areas, requires pursuit of certain lines of inquiry, fills in details or otherwise serves to accomplish the statement of work;

(b) Provision of information to the Contractor that assists in the interpretation of drawings, specifications or technical portions of the work description; and,

(c) Review and approval/rejection of technical reports, drawings, specifications and technical information to be delivered by the Contractor.

All Technical Direction must be within the general scope of work stated in the contract. The COR does not have the authority to and may not issue any Technical Direction that:

(a) constitutes an assignment of additional work outside the general scope of the base contract;

(b) constitutes a change as defines in the base contract clause entitled “Changes”;

(c) in any manner causes an increase or decrease in prices set forth in Section B; or

(d) changes any of the expressed terms, conditions or specifications of the contract.

All Technical Direction must be issued in writing, or shall be confirmed in writing by the COR within 3 working days after issuance. The Contractor shall proceed promptly with the performance of duly issued Technical Directions. However, if in the opinion of the Contractor, the direction issued but the COR is within one of the prescribed categories in (i) through (vi) above, the Contractor shall not proceed, but shall notify the Contracting Officer in writing, within 3 working days after receipt of any such direction. The Contracting Officer will determine if the Technical Direction is proper, or if a contract modification would be required to properly implement the direction. Failure of the parties to agree upon the nature of the direction or upon the contract action to be taken with respect thereto shall be subject to the clause included in Section I entitled “Disputes.”

G.6 CONTRACTING OFFICER’S REPRESENTATIVE (COR)

(a) The Contracting Officer is the only individual authorized to enter into or terminate this contract, modify any term or condition of this contract, waive any requirement of this contract, or accept nonconforming work delivered under this contract.

(b) The Contracting Officer shall designate a Contracting Officer’s Representative (COR) by written notice to the Contractor. The COR’s responsibilities shall include technical monitoring of the Contractor’s performance and inspecting and accepting deliveries under the contract.

The COR shall be appointed in writing, at which time ALL of the responsibilities of the COR shall be detailed, and a copy of the appointment memorandum shall be furnished to the Contractor. Any changes to the COR delegation shall be made in writing, either by changes to the existing memorandum, or by issuance of a new appointment memorandum. Copies of any changes shall be provided to the Contractor.

(c) The COR is not authorized to perform, formally or informally, any of the following actions:

(1) Promise, award, agree to award, or execute any contract, contract modification, or notice of intent that changes or may change this contract;

(2) Waive or agree to any modification of the delivery schedule;

(3) Make any final decision on any contract matter subject to the Disputes Clause;

(4) Terminate, for any reason, the Contractor’s right to proceed, or issue any order causing the Contractor to stop work; or

(5) Obligate in any way, the payment of money by the Government.

(d) The Contractor shall comply with the written or oral direction of the Contracting Officer or authorized representative(s) acting within the scope and authority of the appointment memorandum. The Contractor need not proceed with direction that it considers to have been issued without proper authority. The Contractor shall notify the Contracting Officer in writing, with as much detail as possible, when the COR has taken an action or has issued direction (written or oral) that the Contractor considers to exceed the COR’s appointment, within 3 days of the occurrence. Unless otherwise provided in this contract, the Contractor assumes all costs, risks, liabilities, and consequences of performing any work it is directed to perform that falls within any of the categories defined in paragraph (c) prior to receipt of the Contracting Officer’s response issued under paragraph (e) of this clause.

(e) The Contracting Officer shall respond in writing within 30 days to any notice made under paragraph (d) of this clause. A failure of the parties to agree upon the nature of a direction, or upon the contract action to be taken with respect thereto, shall be subject to the provisions of the Disputes clause of this contract.

(f) The Contractor shall provide copies of all correspondence to the Contracting Officer and the COR.

(g) Any action(s) taken by the Contractor, in response to any direction given by any person acting on behalf of the Government or any Government official other than the Contracting Officer or the COR acting within his or her appointment, shall be at the Contractor’s risk.

G.7 CONTRACTOR SUPERVISION

The contractor shall provide total supervision of its staff. Government personnel are not authorized or permitted to supervise any contractor personnel. The contractor's Project Manager for this contract is [Fill-in at Award], who shall communicate with the COR to determine the Government's work requirements as set forth in the Statement of Work and shall assure that these requirements are fulfilled. In the event the designated Project Manager is incapacitated due to illness or injury or otherwise is to be removed by the Contractor during the contract performance, replacement of the incumbent Project Manager shall be subject to the approval of the CO.

G.8 VEHICULAR AND GENERAL PUBLIC LIABILITY INSURANCE

(a) The Government cannot indemnify the Contractor or its subcontractor(s) from liability as a result of the performance of work under this contract. The Contractor shall be liable for, and shall indemnify and hold harmless the Government against all actions or claims for loss of or damage to property or the injury or death of persons, resulting from the fault, negligence, or wrongful act or omission of the Contractor, its agents, or its employees.

(b) Therefore, if the Contractor is required under the Statement of Work of this contract or any task order issued hereunder, to operate motor vehicles, trailers, and/or marine vessels owned or leased by the Government, the Contractor shall obtain adequate property, vehicle and liability insurance during the entire period of performance.

(c) The Contractor agrees to maintain, during the continuance of this contract, vehicular or water craft damage (collision and comprehensive), liability, and general public liability insurance with limits of liability for :

(1) Bodily Injury of not less than $1,000,000 for each person and $2,000,000 for each occurrence; and

(2) Property damage of not less than $200,000 for each accident.

(d) The U.S. Department of Transportation- Federal Highway Administration shall be listed as an Additional Insured Party of any policy obtained under this contract.

(e) The Contractor shall notify the Contracting Officer (CO) in writing that the required insurance has been obtained and shall furnish a copy of any policies to the CO. The policies evidencing required insurance shall contain an endorsement to the effect that any cancellation or any material change adversely affecting the interests of the Government shall not be effective until 30 days after written notice has been provided to the CO. The policies shall exclude any claim by the insurer for subrogation against the Government by reason of any payment under the policies.

SECTION H - Special Contract Requirements

H.1 PROCUREMENT AUTHORITY

The Federal Highway Administration, Office of Acquisition and Grants Management, is the only agency that is authorized to modify, suspend, or terminate performance under this Contract.

H. 2 NON-PERSONAL SERVICES CONTRACT

This contract is a non-personal services contract as defined in the FAR at subpart 37.101. It is understood and agreed that the Contractor and/or Contractor’s employees and subcontractors: (1) shall perform the services specified herein as independent contractors, not as employees of the government; (2) shall be responsible for their own management and administration of the work required and bear sole responsibility for complying with any and all technical, schedule, or financial requirements or constraints attendant to the performance of this contract; (3) shall be free from supervision or control by any government employee with respect to the manner or method of performance of the services specified; but (4) shall, pursuant to the government’s right and obligation to inspect, accept or reject the work, comply with such general direction of the Contracting Officer, or the duly authorized representative of the Contracting Officer, as is necessary to ensure accomplishment of the contract objectives.

H.3 TECHNICAL REPORT SPECIFICATIONS

Unless specified otherwise, technical reports under this contract shall be prepared in accordance with the Guidelines for Preparing FHWA Publications: Technical Reports available at http://www.fhwa.dot.gov/print_package.zip.

H.4 SPECIFICATIONS FOR PUBLICATION DELIVERABLES

All deliverables shall undergo appropriate technical review prior to being delivered. The contractor shall conduct quality control checks to ensure accuracy of all work and that all formatting is preserved. If requested in the task order, the contractor shall provide documentation explaining how reviewer comments on draft products were addressed. The contractor shall be responsible for correction of typographical errors through the blue line stage of production.

Publications Guidelines

All reports to be published, electronically or hard copy, shall be prepared in accordance with the “Guidelines for Preparing FHWA Publications: Technical Reports” at http://www.fhwa.dot.gov/print_package.zip. An HOP Supplement to the Guidelines will be available in the near future to assist the Contractor in greater detail. The Contractor shall specifically follow the Times New Roman font, sized at 12 point for the content text. The headings font size can be a larger font size but the type font should be Times New Roman. One space shall be added between each sentence.

The Contractor shall make sure all of the following is checked for before submitting a publication:

Product Features Does the product follow the Guidelines for Preparing FHWA Publications: Technical Reports and have the correct FHWA logo?

(Find authorized at http://www.fhwa.dot.gov/print_package.zip)

Does the content meet the following standards:

• Plain Language guidelines, including deploying the lowest possible quotient of active voice.

• Synonyms in place of frequently used words (terms like “support” and “develop”) to make the content more interesting to read.

http://www.fhwa.dot.gov/print_package.zip http://www.fhwa.dot.gov/print_package.zip http://www.fhwa.dot.gov/print_package.zip http://www.plainlanguage.gov/

• Parallel sentence construction in tables and bullet points.

Does the overall formatting of reports meet the following criteria?

• Acronyms spelled out:

1) in Table of Contents

2) in titles and headings

3) the first time they appear in the product; and

4) at the beginning of chapters and/or major sections.

• Chapters begin on the right-hand page (i.e., an odd-numbered page.)

• Blank pages are counted in the page number sequence but have no print (such as number or graphics) on the page.

• Right-hand margins are unjustified because type with ragged margin is easier to read.

• Times New Roman font, sized at 12 point for the content text. The headings font size can be a larger font size.

• One space…