Attachment 1_PWS.pdf

Performance Work Statement for

Analysis of Truck Telematics Data to Identify Accident Hazard Roadways Segments

1.0 Overview

This is a non-personal services contract to provide Analysis of Truck Telematics Data to Identify Accident Hazard Roadways Segments. The Government will not exercise any supervision or control over the contract or service providers performing the services herein. Such service providers shall be accountable solely to the Contractor who, in turn is responsible to the Government as defined in this Performance Work Statement (PWS). The Contractor shall perform to the standards herein.

1.1 Background

FHWA Office of Freight Management (HOFM) promotes efficient, seamless, and secure freight flows on the U.S. transportation system and across our borders. The smooth and secure flow of freight is important to our nation's economy and to our global connectivity. To advance this mission, HOFM:

• Administers the National Highway Freight Program.

• Implements programs and projects in accordance with federal laws and regulations.

• Develops freight guidance in accordance with current federal laws and regulations.

• Oversees enforcement of commercial motor vehicle size and weight regulations.

• Develop tools and procedures to implement freight planning and programs.

• Develops freight analytical tools, performance measures, and data.

• Conducts research on freight transportation management and operations.

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

• Collaborates on multimodal freight transportation and supply chain initiatives with the DOT Multimodal Freight Office, Federal Aviation Administration (FAA), Federal Railroad Administration (FRA), Maritime Administration (MARAD), and Bureau of Transportation Statistics (BTS).

Together, these activities build a greater understanding of freight transportation issues and trends, foster public/private partnerships, improve operations through advanced technologies, and educate and train freight transportation professionals. Contract support is needed to assist the HOFM staff in meeting various requirements of the freight program, including but not limited to, supporting the implementation of freight provisions of current federal laws and regulations impacting freight transportation and planning.

1.2 Objective

The purpose of this project is to minimize accident risks on the U.S. roadways by conducting nationwide research and analysis of truck telematics data from real world heavy commercial trucks operations. The objective of this project is to research and analysis of truck telematics data for identifying highway segments where commercial trucks are exhibiting patterns of heavy breaking or evasive maneuvers that could be indicative of locations with safety concerns.

1.3 Detailed Requirement

The Contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform analysis of truck telematics data to identify accident hazard roadway segments.

Task 1. Project Management

1.1. Project Management Plan and Project Schedule

The Contractor shall draft a Project Management Plan to be reviewed at the kick-off meeting. The Project Management Plan shall include:

• Project schedule and work task dependencies.

• Staff labor/cost distribution by task.

• Communications management plan.

• Project risk management.

• Quality management plan.

• Approach to reviewing draft reports and public affairs approval.

• Meeting requirements of Section 508 of the Rehabilitation Act of 1973 (508 compliance).

NOTE: The Project Management Plan shall be consistent with the contract and all exhibits. The Project Management 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.

Deliverables:

• Draft Project Management Plan 3 business days prior to the kick-off meeting.

1.2. Kickoff Meeting

The Contractor shall arrange a kick-off meeting to:

• Identify refinements that need to be made to shape the final project management plan.

• Receive guidance from the FHWA Contracting Officer’s Representative and finalize the project management plan.

• Describe risks and risk mitigation measures.

• Present the project schedule.

Key project personnel from USDOT are expected to attend. The Contractor may be required to host the web conference and shall be prepared to provide options for web conferencing platform. The kickoff meeting shall be scheduled within 14 days of contract award. The Contractor shall develop a kick-off meeting summary and final Project Management Plan. The final Project Management Plan shall include all pertinent work information identified during the kickoff meeting.

Deliverables:

• Kickoff meeting agenda 3 business days prior to the kick-off meeting.

• Web/Teleconference Kick-off meeting within 14 days of award.

• Kick-off meeting summary within 1 week following the kick-off meeting.

• Final Project Management Plan within 2 weeks following the kick-off meeting.

1.3. Project Meetings

FHWA anticipates monthly project meetings to receive updates on project progress, next month’s plan, and to discuss challenges, risks, and proposed solutions.

Representatives from other USDOT offices modal administrations will be involved.

Contractor’s key project personnel shall attend, and the Contractor may be required to host the web conference and shall be prepared to provide options for web conferencing platform.

Deliverables:

• Monthly project meetings (web-based), meeting presentation, and meeting notes.

1.4. Monthly Progress Reports and Invoicing

Following the kick-off meeting, the Contractor shall coordinate monthly status calls with the FHWA to provide updates on progress, and to resolve risks.

• Monthly progress reports.

Task 2. Commercial heavy trucks Telematic Data and Analysis

Activities under this task shall focus on establishment of truck telematic data, proposing analysis methods, conducting analysis, preparing summary results, visuals, maps and submitting reports. The contractor shall:

2.1. Establishment of Truck Telematics Data

The contractor shall provide or obtain real world commercial truck telematics data collected from trucking operations within the U.S. that are required to calculate information such as acceleration, deceleration, turning and skidding for safety hazard locations investigation. At minimum, the telematics data shall include trucking operations on the National Highway System. The FHWA does not expect to receive raw proprietary telematics data as project submittals, only post processed and aggerated data will be part of FHWA project deliverables.

• Presentations to describe potential input data for analysis.

• Truck telematics data or aggregated/postprocessed truck telematics data and data documentation.

• Other associated input data for analysis such as spatial roadway network and documentation.

2.2. Conduct Research to Develop Analysis Framework for Implementation

The contractor shall conduct research to propose, develop, and deploy methods to identify safety hazards utilizing real world truck telematics data such as hard braking and sudden steering from the telematics data. Under this activity, the contractor shall develop a technical memo describing proposed analysis and data application approach for network screening to identify and evaluate crash patterns, diagnosing conditions contributing to the evasive maneuvers, evaluating effectiveness of potential safety countermeasures, and identifying locations that could be most likely to benefit from safety improvements.

• Presentations to describe input data, propose analysis methods and expected summary results to establish propose analysis framework for Task 2.2.

• A detail technical memo describing data, propose analysis methods and analysis framework for implementation, expected final results with templates for FHWA approval.

2.3. Implementation of Proposed Analysis Framework and Analysis Results

The contractor shall conduct analysis continuing from above tasks 2.1 and 2.2 to prepare final results including development of safety hazard segment heat maps and data on the National Highway System. Under this activity, the contractor shall perform analysis, prepare, and submit summary results, visuals, maps, processed data, presentation to share final results for a webinar and reports as project submittals. The contractor will work with FHWA to conduct one webinar with local planning agencies, MPOs, State DOTs, and industry stakeholders to share final results.

• Presentation to describe analysis, results and outline a technical memo to summaries Task 2.3. This deliverable may be published on the FHWA webpage or distribute for webinar.

• A technical memo describing methods, analysis, and findings from Task 2.3.

• Final results, post processed telematics data, summary results, visuals, and maps from Task 2.3.

• Project summary reports and maps. This deliverable may be published on the

FHWA webpage.

Note: Deliverables that are identified for publication on the FHWA webpage will go through the below listed five separate sequential review processes. Once all the comments have been satisfactorily addressed, FHWA will accept deliverables to move to the subsequent reviews for further approval.

• Draft 1 for technical review.

• Draft 2 for HOFM and HOP editorial review.

• Draft 3 for legal review.

• Draft 4 for Public Affairs review.

• Draft 5 for 508 reviews.

2.0 Period of Performance

The period of performance shall be for one (1) Base period of twenty-four (24) months.

3.0 General

The Contractor shall develop and maintain an effective Quality Control Plan (QCP) to ensure services are performed in accordance with this PWS. The Contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services.

The Contractor’s QCP is the means by which he/her assures that his/her work complies with the requirement of the purchase order. The QCP is to be delivered within 30 days after task award.

After government acceptance of the QCP, the Contractor shall receive the Contract Officer’s (CO) acceptance in writing of any proposed change to the government accepted QCP.

3.1 Hours of Operation (Note: This section applies to work conducted at a Government Facility, enter “N/A” if place of performance is at the contractor’s facility N/A

3.2 Place of Performance

The work to be performed under this contract shall be performed at the contractor facility.

3.3 Physical Security

The Contractor shall be responsible for safeguarding all government equipment, information, and property provided for Contractor use.

3.4 Special Qualifications

N/A

3.5 Periodic Progress Meetings

The contractor agrees to attend progress meetings. The Contracting Officer or Contracting Officer’s Representative (COR), and other Government personnel, as appropriate, may meet periodically with the Contractor to review the Contractor's performance. At these meetings, the CO will apprise the Contractor of how the government views the Contractor's performance and the Contractor will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the government.

3.6 Identification of Contractor Employees

All contractor personnel attending meetings, answering Government telephones, and working in other situations where their Contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by Contractors are suitably marked as Contractor products or that Contractor participation is appropriately disclosed.

3.7 Contractor Travel

Travel is not required.

3.8 Materials

N/A

3.9 Organizational Conflict of Interest

Contractor and subcontract personnel performing work under this award may receive, have access to, or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.), or perform evaluation services which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5. The Contractor shall notify the CO immediately whenever he/she becomes aware that such access or participation may result in any actual or potential OCI, and may merit the submittal of a plan to the CO to avoid or mitigate any such OCI. This mitigation plan would be determined to be acceptable solely at the discretion of the CO, and in the event the CO unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may effect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

3.10 Phase In /Phase out Period

N/A

4.0 Government Furnished Equipment and Services (Note: enter “N/A” for the elements that are not applicable to your project) N/A

4.1 Services

N/A

4.2 Facilities

N/A

4.3 Materials

N/A

Exhibit List:

• Exhibit 1 Performance Requirements Summary

• Exhibit 2 Deliverables Schedule

EXHIBIT 1

PERFORMANCE REQUIREMENTS SUMMARY

The Contractor service requirements are summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success.

Performance Objective (The Service required— usually a shall statement) Performance Standard

Performance Threshold (This is the maximum error rate.)

Method of Surveillance

PRS # 1.

The Contractor shall provide project management plan that outlines the project production work plan and quality control procedure for each task.

The Contractor provided project management plan shall also identify the project schedule and work task dependencies, staff labor/cost distribution by task, proposed channels of communication, approach to reviewing IT / Public Affairs 508 compliance approval, primary and secondary reviewers and their roles, and deliverable due dates.

Zero deviation from standard.

100% COR

will review upon receipt.

PRS # 2

The Contractor will work with FHWA to conduct one webinar with local planning agencies, MPOs, State DOTs, and industry stakeholders to share final results

The Contractor shall organize and facilitate delivery of the webinar with stakeholders including hosting webinar, developing presentation materials, and notes.

The contractor shall provide 508 compliant presentations.

100% COR will review upon receipt.

PRS # 3

The contractor shall provide final report and related summary data resulted from the analysis.

Report shall include the elements identified in the technical memo, final results including description of data and details about applied analysis processes.

No more than zero technical and grammatical errors. Zero deviation from standard.

100% COR will review upon receipt.

EXHIBIT 2

DELIVERABLES SCHEDULE

This technical exhibit lists any reports or documentation that is required as a deliverable to include the frequency, # of copies, medium/format and who/where it is to be submitted. A deliverable is anything that can be physically delivered but may include non-physical things such as meeting minutes.

Deliverable Compliant Frequency

# of Copies Medium/Format

Submit To

1.1 Draft Project

Management

No Once, 3 business days prior to the kick-off meeting

One copy MS Word and another format as accepted by

FHWA

COR

1.2.1 Kickoff

meeting agenda.

No Once, 3 business days prior to the kick-off meeting

One copy MS Word, and another format as accepted by

FHWA

COR

1.2.2 Web/Teleconfere nce Kick-off meeting

No Once within 14 days of award.

One copy [MS Teams, Zoom and another format as accepted by

FHWA

COR

1.2.3 Kick-off

meeting summary

No Once, within 1 week following the kick-off meeting.

One copy [MS Word, PDF, and another format as accepted by

FHWA

COR

1.2.4 Final

Project Management Plan

No Once, within 2 weeks following the kick-off meeting.

One copy MS Word, PDF, and another format as accepted by

FHWA

COR

1.3.1 Monthly

project meetings (web-based), meeting presentation, and meeting notes.

No Monthly, within 1 week following the meeting.

One copy MS Word, MS PowerPoint, PDF, and another format as accepted by

FHWA

COR

1.4.1 Monthly

progress reports.

No Monthly, within 1 week of the following month

One copy MS Word and another format as accepted by

Deliverable Compliant Frequency

# of Copies Medium/Format

Submit To

2.1.1 Presentations to describe potential input data for analysis.

No Once, within 2 months of award

One copy MS Word, MS PowerPoint, PDF, MS Excel, and another format as accepted by

FHWA

COR

2.1.2 Truck

telematics data or aggregated/postp rocessed truck telematics data and data within 3 months of award.

One copy MS Excel, Tableau, ArcGIS and another format as accepted by

FHWA

COR

2.1.3 Other

associated input data for analysis such as spatial roadway network and within 3 months of award.

One copy MS Excel, Tableau, ArcGIS and another format as accepted by

FHWA

COR

2.2.1 Presentations to describe input data, propose analysis methods and expected summary results to establish propose analysis framework for Task 2.2.

within 4 months of award.

One copy MS Word, MS PowerPoint, PDF, MS Excel, and another format as accepted by

FHWA

COR

2.2.2 A detail

technical memo describing data, propose analysis methods and analysis framework for implementation, expected final results with templates for FHWA approval.

within 6 months of award.

One copy MS Word and another format as accepted by

Deliverable Compliant Frequency

# of Copies Medium/Format

Submit To

2.3.1 Presentation to describe analysis, results and outline a technical memo to summaries Task 2.3.

Yes Once, within 12 months of award.

One copy PowerPoint and another format as accepted by

FHWA

COR

2.3.2 A technical

memo describing methods, analysis, and findings from Task 2.3.

within 15 months of award.

One copy MS Word, MS Excel, and another format as accepted by

FHWA

COR

2.3.3 Final

results, post processed telematics data, summary results, visuals, and maps from Task 2.3.

No Once, within 15 months of award.

One copy MS Excel, Tableau, ArcGIS and another format as accepted by

FHWA

COR

2.3.4 Project

summary reports and maps.

Yes Once, within 18 months of award.

One copy MS Word, PDF, and another format as accepted by