DRAFT ADS Roadway Testing and Evaluation SOW Version Date 10819.docx

Draft October 2015

Version Date: October 8, 2019

Office of Operations

Statement of Work

For

Development of Innovative Techniques and Methods that Support a Changeable Roadway Testing Environment Technical Support Services

1.0 Overview

This is a non-personal services contract or task order to Develop Innovative Techniques and Methods that Support a Modular and Changeable Roadway Environment that Can Support Joint Automated Driving Systems (ADS) and Roadway Testing and Evaluation. The Government will not exercise any supervision or control over the contract or task order service providers performing the services herein. Such service providers shall be accountable solely to the Contractor who, in turn is responsible to the Government as defined in this Statement of Work (SOW). The Contractor shall perform to the standards herein.

1.1 Background

This research will investigate and develop techniques, methods, and objects that can be used to mimic roadway operations, and/or traffic control for joint human, ADS, and other road user testing and evaluation. As more information becomes available and ADS can be demonstrated, there will be a need to present different scenarios to ADS to evaluate how the ADS interpret the roadway environment. In addition, investigations will need to be done regarding how the roadway can be adapted to enhance the interpretation to ensure safe and efficient operations of ADS, human drivers, and other road users. This work will identify the joint needs of ADS and the roadway, develop alternative techniques and the innovative technology that could be used, and the prototyping and testing of modular and changeable roadway features that include but are not limited to curbs, pavement markings and delineation devices, traffic signals, and roadway lighting.

Creating a modular roadway testing and evaluation capability will support ADS developers and roadway providers:

· Understand and evaluate how roadways can be adapted to enhance performance of ADS

· Support the development and planning of joint roadway and ADS testing activities.

· Extend testing and evaluation activities given the ability to support reconfiguration of roadway features.

· Facilitate collaboration among stakeholders to identify and modify testing configurations that meet the multiple needs of stakeholders.

· Address testing and evaluation under complex roadway environments.

This research addresses the need to adapt roadway features to support all roadway users including ADS. The research will support the joint testing and evaluation activities identified by commenters to the FHWA Request for Information (RFI) regarding Automated Driving Systems. The research will build a more robust and efficient testing and evaluation capability that will support the testing and evaluation that needs to take place to adapt our roadways to support the evolutionary deployment of ADS. It will provide the tools and information necessary for ADS developers as well as infrastructure owners and operators to make the most appropriate investment decisions.

1.2 Objective

The objective is to evaluate the feasibility of mimicking roadway features that will facilitate depiction of realistic roadway scenarios to all road users but that the scenario can be easily custom configured or changed to a different scenario without permanently changing basic test facilities roadway configurations. The techniques and methods will need to mimic roadway features that include but are not limited to traffic control devices and roadway makings. The results will support joint ADS and roadway testing in relation to multiple staged roadway environment scenarios.

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 the tasks identified. The tasks below identify elements of the investigation that support the following:

· Establishment of stakeholder collaboration.

· Identification and depiction of basic and challenging roadway environments to study roadway and ADS interaction.

· Development of a basic understanding of how ADS perceive the roadway environment

· Identification of roadway features that are instrumental regarding how ADS perceive the roadway environment.

· Identification of materials, fabrications, and configurations that can be used to mimic roadway features (includes roadway markings and other traffic control devices) that are representative to human drives and ADS but support a modular changeable test environment.

· Development, test, and evaluation of artificial roadway features that support accurate testing of changed/enhanced roadway features and modular/changeable roadway environment scenarios.

· Development of a proof-of-concept prototype roadway scenario using artificial roadway features to prove the concept and evaluate the feasibility of the prototypes to support collaborative roadway/AV testing via staged roadway environments.

Task 1: Project Management The Contractor shall provide project management support for all tasks described in this Scope of Work.

The Contractor shall attend a task order kick-off meeting in the Washington, D.C. area within two weeks of award, and present the proposed approach outlined in a draft Project Management Plan (PMP) and project schedule at the kick-off meeting. The Contractor shall develop the initial PMP based on the technical work defined in this document. A template for the PMP can be found in Appendix II.

Based on discussions at the kick-off meeting, the Contractor shall develop a final PMP that guides the execution of tasks identified in this Statement of Work. The Contractor shall follow PMI’s (Project Management Institute) Project Management Body of Knowledge (PMBOK) standard ANSI/PMI 99-001-2008. The PMP shall include plans for: Scope Management, Cost Management, Quality Management, Human Resources Management, Communications Management, and Risk Management.

The Contractor shall prepare a detailed project schedule, in Microsoft Project that lists all planned tasks and milestones for the project. All activities shall have their predecessors and successors clearly identified, to enable the calculation of a critical path for the project. The detailed project schedule shall reflect a work breakdown structure (WBS) comprising at least three levels.

Within 4 weeks of task order award, the Contractor shall schedule a coordination meeting with the Contracting Officer or Contracting Officer’s Representative (COR)and other FHWA representatives to review the final PMP and project schedule to ensure consensus on the overall approach for project execution. If the FHWA deems it necessary for the Contractor to revise any of these documents, the Contractor shall revise accordingly and submit a final version of the documents for FHWA review and approval.

NOTE: The Contractor shall not proceed with the activities described in the PMP and Project Schedule without written approval to proceed from the COR.

The Contractor shall attend monthly team meetings or teleconferences as requested by the COR and/or Government Task Monitor (GTM). The Contractor shall be prepared to report on progress, schedule, scope issues, budget, and results of tasks at team meetings. The Contractor shall prepare team meeting summaries, which will, at a minimum, track the status of action items.

The Contractor shall provide monthly progress reports. These reports shall cover the work progress of all tasks described in this Statement of Work. In addition, the reports shall include the following items:

· A one (1) page summary of the overall progress, including:

· Major accomplishments;

· A clear and complete account of the work performance during the reporting period.

· Near-term milestones; and

· Variances from the current work plan, including planned corrective actions.

· Summary of each active 2nd-level WBS element, including:

· Estimated % work complete;

· Brief list of activities/deliverables completed that month;

· Brief list of activities anticipated in the next month;

· Brief list of outstanding issues/comments requiring FHWA attention; and

· Status of each deliverable including the outline, the draft (or interim) version, and the final version.

· A Risk Management Log that documents risks that might affect the project and the characteristics of the risk. Types of risks that must be considered include risks potentially impacting: project schedule, scope, and costs. A Risk Management Log must be maintained on an on-going basis during the entire period of performance to track risks, mitigation plans, and status. Each risk will have a unique number, probability of occurrence and impact of occurrence rating. An example of a Risk Management Log can be found in Appendix I.

The Contractor shall, throughout the project, support FHWA with communicating the processes and results of this project to various ADS stakeholders. As directed by the COR, the Contractor shall develop and/or deliver presentations (not to exceed 2) on project-related findings at various industry conferences (e.g. AASHTO, ITS America Annual Meeting, etc.).

The Contractor shall attend a project closeout meeting in the Washington, D.C. area estimated to occur during the last few weeks of the project. The Contractor shall present a summary of work performed under each task, the status of each deliverable, and identify pending or incomplete deliverables, and the total funds expended.

Deliverables:

· Briefing Materials, Kick-Off Meeting

· Draft PMP, Final PMP

· Draft Project Schedule, Final Project Schedule

· Team Meetings Summaries

· Monthly Status Reports

· Conference/ Workshop Presentation (up to 2)

· Conference/Workshop Presentation Materials (up to 2 sets)

· Briefing Materials, Closeout Meeting

Task 2: Establish Stakeholder Collaboration and Review To advanced joint understanding of the nexus of technical capabilities that will be necessary to support the safe integration of AV into our roadway systems, stakeholders need to be able to collaborate on joint testing and evaluation activities. This research needs to start this understanding by establishing and using a representative set of stakeholders that will collaborate on the development of modular and changeable testing environments that meet the needs of ADS developers and roadway providers.

The contractor shall establish a group that represents both private and public sectors stakeholders that need to participate in roadway/ADS testing and evaluation. These stakeholders include but are not limited to state and local infrastructure owners and operators, ADS developers, AV testing facilitates, AV manufactures, sensor developers, and AV traffic modeling and simulation experts. The stakeholders shall not only review the elements of this research but participate to determine the value of the capability to mimic roadway environment scenarios and how that will enable collaborative evaluation and identification of the nexus of roadway and ADS technology that will support the safe AV integration into the roadway environment.

It is expected that the participating stakeholders bring expertise, knowledge, facilities, and equipment necessary to conduct joint collaborative development and testing of artificial roadway features, support the Proof-of-Concept, and participate in evaluating the feasibility of changeable roadway scenarios for AV testing.

This task needs to develop a Stakeholder Modular Roadway Environment Study Group Charter that identifies the criteria for representation, the number of representatives needed, how representative selections will be made, how additions will be accommodated, and indication of the level of commitment of individual stakeholders as well as of the collective stakeholder group that is expected.

The contractor shall obtain commitment of Stakeholders for the duration of the study that included identifying each stakeholder’s point of contact and other subject matter experts that will participate in the development and assessment of artificial roadway environment capabilities.

The contractor will manage the stakeholder group and ensure the group is incorporated into all aspects of project planning, development, testing, evaluation, and assessment. The contractor shall develop a Stakeholder Modular Roadway Environment Study Group management plan that identifies how the group will be used to support the subsequent tasks of this project.

Deliverables:

Stakeholder Modular Roadway Environment Study Group Charter Stakeholder Modular Roadway Environment Study Group Management Plan

Task 3: Identification and Description of an Initial Suite of Human/AV Roadway Test and Evaluations Environment Scenarios

The contractor will investigate, identify, and develop descriptions for 7 or fewer human/AV roadway environment scenarios that present normal and challenging situations for both human driven and ADS vehicles.

The contractor shall use the Stakeholder Modular Roadway Environment Study Group (referred to as the Stakeholder Study Group) to identify scenarios as well as information from comments submitted to the FHWA RFI on Automated Driving Systems, and what was heard during the National Dialogues on Highway Automation.

The contractor with the Stakeholder Study Group shall create a table of possible roadway environment scenarios that include a roadway scenario title and associated characteristics for each scenario such as arterial, highway, urban, rural, controlled intersections, curves, passing/no passing, circle, types of vehicles, other road users; etc. The table will be presented to the FHWA to solicit input on the table and selection of roadway scenarios for further development. The COR will account for input from FHWA to identify the 7 or fewer roadway environment scenarios that will be selected for further development.

After COR provides the contractor with the 7 or fewer roadway scenarios, the contractor shall create detailed descriptions for each of the roadway scenarios. Each description needs to include both narrative and visual renditions of each scenario. The description needs to identify roadway scenario characteristics, features, and variations. Roadway features include but are not limited to items such as curbing, roadway markings, traffic control devices, design attributes, traffic interactions, types of road users, median characteristic, and surrounding environment attributes such as vegetation and/or structures. The objective is to describe and present total roadway environment scenarios that will support the identification and description of roadway features that may contribute to both human and ADS perception of the roadway environment.

The contractor with the Stakeholder Study Group shall prepare and submit for review to the FHWA draft detailed descriptions for 3 of the selected roadway scenarios. FHWA will review and make recommendation regarding the structure and composition of the detailed descriptions. The contractor and Stakeholder Study Group will review the recommendations and make changes to the initial draft descriptions. The contractor will resubmit the descriptions to FHWA. After review by FHWA, the COR will instruct the contractor on how to proceed with finalizing the detailed description and indicate that the contractor can apply the detailed description to any remaining selected scenarios.

The contractor and the Stakeholder Study Group will complete development of any remaining roadway scenario descriptions and submit draft descriptions to the FHWA for review and comments. The COR will review comments and make final revision recommendations to the contractor. The contractor will address the recommended revisions and resubmit to the COR.

After the revisions are completed and approved by the COR, the contractor with the Stakeholder Study Group will use the detailed descriptions to complete a roadway feature inventory across the described roadway scenarios. The inventory analysis will include a table, analysis, and narrative that discusses the different roadway features and each feature’s relationships to the various roadway scenarios. The inventory needs to identify which features are included across various scenarios and which features are unique to which scenarios. The contractor with the Stakeholder Study Group will develop a draft inventory that the contractor will submit to the FHWA for review. The COR will coordinate revision recommendation and submit to the contractor. The contractor will address the recommendations and resubmit to the final inventory to the COR.

Deliverables:

Possible Roadway Environment Scenarios Table Draft Detailed Descriptions for Initial 3 Roadway Scenarios Draft Detailed Descriptions for Remaining Roadway Scenarios Final Detailed Descriptions for All Roadway Scenarios Draft Roadway Scenario Features Inventory Final Roadway Scenario Features Inventory

Task 4: Computer Environment Visualizations Tool for Selected Roadway Environment Scenarios and Roadway Features

The contractor will develop computer (gaming) environment visualization using existing computer visualization tools and capabilities for each of the selected roadway environment scenarios per the detailed descriptions and inventory developed in task 3. The objectives of the visualizations are to better understand each roadway scenario, the features associated with each scenario, configuration variations, different visual perspectives such as day/night and different lines-of-sight, curb or shoulder, parking, structures, and interrelationships among features and the roadway environment.

The visualization will be used by the contractor to discuss and refine roadway scenarios and features with both the Stakeholder study group and FHWA. The visualizations will be used to plan and develop roadway artificial feature and artificial roadway environment scenarios. The visualizations will assist with the planning and configuration of test scenarios and the feasibility of a modular and changeable environment. The visualizations need to support roadway scenario variation development capabilities that include changes to roadway features and the roadway environment. This visualization tool is to be used to support the next tasks included in this Scope of Work.

The contractor with the Stakeholder Study Group will complete draft visualizations of each environment with alternative configurations and features. FHWA will review the visualizations and provide comments. The contractor will address the comments and finalized the visualizations.

Deliverables:

Draft Visualizations for each roadway scenario and alternative configurations Final Visualizations for each roadway scenario and alternative configurations

Task 5: Roadway Feature Properties, and ADS Recognition and Perception Relationships

The contractor in consultation with the Stakeholder study group will investigate and analyze the characteristics of roadway features provided through the investigations complete under Tasks 3 and 4 to understand the recognition and perception relationships between humans and ADS. Understanding the recognition and perceptions relationship will entail understanding how humans and ADS recognize and perceive road features as well as the total roadway environment. The Stakeholder group will provide input regarding ADS sensor capabilities including if applicable feature electronic signatures. The investigation needs to identify and understand the perception properties of roadway features that include how they look, but also what materials are used in the construction of the roadway feature. A sensor’s recognition and perception of a roadway feature may be district to the material(s) used in the construction of the feature; e.g. the construction that may include a certain material that may cause a distinct signature. The contractor will need to understand the composition of the signature the ADS uses to mimic that signature when creating artificial roadway features.

Using the inventory of roadway features and the visualizations of the selected roadway scenarios, the contractor will investigate and analyze the perception capabilities of ADS (sensor capabilities) as provided by the Stakeholder Study Group. The contractor will use this information to investigate current roadway features and the factors inherent regarding the signatures the sensors receive from various roadway features. The contractor will conduct tests to verify and validate roadway feature ADS perception characteristics and compare to how humans recognize and perceive roadway features.

The contractor shall develop and execute a roadway feature investigation, analysis, and recognition and perception profiles plan. The plan will include an approach to identify the 10 or less prominent roadway features for which profiles will be created. The plan will include identification of ADS sensor capabilities and identify and conduct a methodology to identify how the various sensors used by ADS developers will recognize and perceive various roadway features and the composition of the perception. For example, a traffic signal head is recognized and perceived by an ADS. The sensor may use the shape, and the color and position of the lighted signal. The composition of the signal head (metal) may not contribute to the recognition and perception that an ADS perceives a traffic signal head. The plan needs to include how the contractor will profile each roadway feature and document the needs of each sensor in relation to accurately recognizing and perceiving roadway features.

The contractor shall submit a draft Roadway Features Investigation, Analysis, and Roadway Feature Profiles plan to the Stakeholder Study Group and FHWA for review. The contractor will address the comments and resubmit to the COR for approval. Once the plan is approved the contractor will execute the plan and deliver a draft and final Roadway Features Investigation, Analysis, and Roadway Feature Profiles report.

Deliverables:

Draft Roadway Features Investigation, Analysis, and Roadway Feature Profiles Plan Final Roadway Features Investigation, Analysis, and Roadway Feature Profiles Plan Draft Roadway Features Investigation, Analysis, and Roadway Feature Profiles Report Final Roadway Features Investigation, Analysis, and Roadway Feature Profiles Report

Task 6: Selection and Conceptual Prototypes for Artificial Roadway Features

The contractor shall use the results of Task 3 through 5 to support selection of roadway features to develop artificial roadway feature prototypes. The contractor shall use the descriptions, computer visualizations, inventory, and profiles to understand the feasibility of prototyping roadway features that will support human and ADS recognition and perception and contribute to staging of artificial roadway environment scenarios.

The contractor shall conduct an analysis of the 10 or less Task 5 profiled roadway features and develop metrics to rank the feasibility of developing artificial prototypes. The contractor will work with the Stakeholder Study Group in the development of the metrics and the ranking of potential feature artificial prototypes. The metrics will include analysis of the roadway feature profiles and the expected difficulty regarding mimicking the prototype given ADS sensor recognition and perception of actual roadway feature considering sensor signatures if applicable. The objective is to be able to produce artificial prototypes that provide a similar look, feel, and sensor signature, but that can be deployed, reconfigured to represent roadway features and scenarios without making permanent changes to facilitates. As part of this analysis the contractor will investigate if there are any currently available artificial prototypes of roadway features that can be used or modified and rank according to the metrics. The contractor in coordination with the Stakeholder study group will complete the selection analysis and provide a report that documents the methodology, metrics, identifies the roadway features prototype rankings and the number and type of roadway environment scenarios that can be represented with the roadway feature prototypes recommended. The report will be submitted to FHWA and a meeting will be scheduled to discuss the recommendations discussed in the report. After review and discussion of the recommendation among the contractor, FHWA, and the Stakeholder Study group, the COR will indicate to the contractor which recommended artificial roadway features (7 or less) are selected for conceptual prototype development.

After the artificial roadway feature prototypes are identified (7 or less) and accepted by FHWA, the contractor will generate conceptual prototypes for the selected roadway features. For the conceptual prototypes, the contractor will need to document the overall concept for each prototype with respect to functionality, design, structure, materials, and operational characteristics. The conceptual prototypes descriptions will need to include engineering schematics, material identification, component fabrication instructions, and prototype assembly procedures. The contractor will collaborate with the Stakeholder Study Group to develop the conceptual prototypes and incorporating information from task 3 through 5, but confirming and refining the concept via input from the Stakeholder Study Group. The contractor will develop 2 initial conceptual prototypes for select roadway features. The objective is to determine if the development of the conceptual prototype will adequately support later development and testing of the prototype. The contractor will develop with the Stakeholder study group an initial conceptual prototype annotated outline. The contractor and the Stakeholder Study group will include in the annotated outline how each element of the outline will contribute and support later prototype development and testing. The annotated outline will be submitted for FHWA review. After the outline comments are addressed, the COR will authorize the contractor to proceed with development to the 2 initial conceptual prototypes. Drafts of the 2 conceptual prototypes will be submitted to FHWA for review. The contractor will schedule a meeting to present and discuss the 2 initial prototypes with the Stakeholder study group and FHWA. After FHWA comments are addressed, the contractor will finalize the initial 2 conceptual prototypes to FHWA. Once the initial 2 are completed the contractor in collaboration with the Stakeholder study group will develop draft conceptual prototypes for the remaining selected artificial roadway features. The drafts will be submitted to FHWA for review. After FHWA sends comments, the contractor will schedule a meeting to review the draft conceptual prototypes. The contractor and the Stakeholder study group will discuss how the drafts will support the next tasks for this project and address any FHWA concerns. After the meeting, the contractor will address any FHWA concerns and submit final conceptual prototypes for each of the selected artificial roadway features.

Deliverables Artificial Roadway Feature Prototypes Ranking and Recommendation Report Conceptual Prototype Annotated Outline Draft Conceptual Prototype Reports for 2 Initial Artificial Roadway Features Final Conceptual Prototype Reports for 2 Initial Artificial Roadway Features Draft Conceptual Prototype Reports for Remaining Artificial Roadway Features Final Conceptual Prototype Reports for Remaining Artificial Roadway Features

NOTE: Tasks 7 is Option 1. Work may not take place on this task until a task order modification exercising the option and signed by the Contracting Officer is received.

The period of performance of Option 1 will be from the effective date of the modification through the conclusion of the task order period of performance.

Task 7: Individual Artificial Roadway Feature Prototypes Fabrication, Testing, and Proof-of-Concept Roadway Scenario Demonstration

The objective of this task is for the contractor in collaboration with the Stakeholder Study Group to fabricate and test individual artificial roadway feature prototypes. The contractor will develop fabrication and test plans for each of the concept prototypes created per Task 6, The plans will include how each prototype will be fabricated in accordance with the information and instruction provide in the conceptual prototype reports. The plans will identify interim component and final prototype testing requirements that include data identification, equipment needs, facility needs, analysis and evaluation approach for both human and ADS recognition and perception. The testing requirements will also include test procedures that identify set-up; execution including the number of qualified test runs for evaluation analysis; facility requirements; environment requirements; data retrieval and processing; and Stakeholder Study Group participation.

The contractor shall in collaboration with the Stakeholder Study Group prepare a semi-generic artificial roadway feature prototype fabrication and testing plan that will be applied to one prototype. The fabrication and testing plan as indicated above will cover all aspects, even aspects that may not apply to the example prototype including a section on materials and testing with human drivers and ADS to evaluate and compare the artificial roadway feature prototype to the actual roadway feature. The comparison testing will produce a prototype mimic ranking approach that supports understanding the level/threshold required for artificial prototypes to accurately portray actual features and support scenario configurations and testing. The Stakeholder Study Group will collaborate with the contractor such that the contractor can incorporate ADS characteristics and challenges into the fabrication and testing plans. The contractor will submit a draft semi-generic artificial roadway feature prototype fabrication and testing plan to FHWA for review. The FHWA will send comments and that the contractor will address. After the comments are satisfactorily addressed and the initial plan finalized, the COR will authorize the contractor to execute the initial plan on the one prototype. The contractor will fabricate and test per the test plan and incorporate Stakeholder study group participation and FHWA observation. The FHWA will be notified of the schedule for the final testing to support attendance of observers. Once the final testing is completed, the contractor will produce a prototype fabrication and testing report that documents the procedures and results of the comparison testing including mimic ranking level. The contactor will submit the report to FHWA for review. After the FHWA sends comments to the contactor, the contractor will schedule a meeting to discuss the comments and any issue or challenges that need to be addressed regarding the plan and application to the remaining prototypes. After the FHWA and challenges are addressed, the COR will instruct the contactor to prepare fabrication and test plans for the remaining prototypes.

The contractor with the Stakeholder study group shall prepare draft fabrication and test plans for the remaining prototypes in accordance with the semi-generic plan adapted to the unique characteristics of each prototype. The draft plans will be submitted to FHWA for review. The contractor shall address the comments sent by FHWA and resubmit the plans. Once the plans are approved, the COR will instruct the contractor to execute the fabrication and testing of the remaining prototypes. The contractor and the Stakeholder Study Group will schedule regular meetings with FHWA to monitor the fabrication and testing of the remaining prototypes and identify any issues or risks that may be encountered. The FHWA will be informed of all final testing schedules to support possible observation. After final testing the contractor will prepare draft fabrication and testing reports and submit to FHWA for review. The contractor will address FHWA comments and finalize the reports. After the reports are finalized the contractor will create an inventory of the fabricated artificial roadway feature prototypes that describes each prototypes purpose, actual feature mimicking, operational description, set-up and configuration requirements, operational instructions, mimic level, and roadway environment scenarios each supports.

Using artificial roadway features from the inventory, the contractor and the Stakeholder Study Group will develop and stage a Proof-of-Concept of a roadway scenario that both human and ADS driven vehicles can recognize, perceive, and successfully navigate. The contractor and the Stakeholder Study Group will develop a Proof-of-Concept plan that describes the proof-of-concept roadway scenario, how it will be executed, and method to evaluate proof-of-concept including a final report. The contractor will submit the plan to FHWA for review. Once the contractor addressed FHWA comments, the COR will instruct the contractor to execute the plan.

Deliverables:

Draft Semi-Generic Initial Prototype Fabrication and Testing Plan Final Semi-Generic Initial Prototype Fabrication and Testing Plan Draft Initial Prototype Fabrication and Testing Report Draft Prototype Fabrication and Testing Plans for Remaining Prototypes Final Prototype Fabrication and Testing Plans for Remaining Prototypes Draft Prototype Fabrication and Testing Report Final Prototype Fabrication and Testing Report Artificial Roadway Features Prototype Inventory Proof-of-Concept Plan Proof-of-Concept Demonstration Proof-of Concept Report

NOTE: Tasks 8 is Option 2. Work may not take place on this task until a task order modification exercising the option and signed by the Contracting Officer is received.

The period of performance of Option 2 will be from the effective date of the modification through the conclusion of the task order period of performance.

Task 8: Staging, Demonstrating, and Assessing the Feasibility of Changeable Artificial Roadway Environment Scenarios

The objective of this task is to understand the feasibility and utility of staging changeable artificial roadway scenarios using artificial roadway features; and if this capability will promote joint collaborative testing of Automated Vehicles in roadway environments.

The contractor will develop a staging, demonstration and feasibility evaluation plan. The plan will use the information from Task 7 to identify and evaluate up to 3 scenarios that can be stage with the developed artificial roadway feature prototypes, demonstrate testing with human driven and ADS vehicles, and demonstrate change-over from one scenario to the next. The plan will identify the scenarios that will be stage and demonstrated, choreograph the change-over from one scenario to the next and the data that needs to be collected to understand the benefits of artificial roadway scenario capabilities. The evaluation described in the plan will include an assessment of the recognition and perception of the roadway scenario and artificial features, the ease or not of changing from one scenario to another and the data that can be obtain from this type of capability and how it would advance joint understanding among roadway providers and ADS developers to advance the integration of AV into our roadway environment. As part of the plan the contractor will specify how the assessment of the changeable capability will be documented that includes video of the demonstrations and scenario change-overs. The assessment needs to be conducted at both the artificial roadway feature and scenarios levels and can identify strengths and weaknesses related to use of various artificial roadway features, possible roadway scenario environment limitations, and human and ADS testing similarities, differences, and the ability for the scenarios to accurately evaluate roadway recognition and perception levels related to actual roadway scenario environments. The plan will include as part of the assessment a live demonstration for FHWA of the roadway scenario environments with change-over, and human and ADS vehicle interaction. The contractor will document the staging, demonstration and assessment of feasibility in a report. The report will document all aspects of the assessment of artificial roadway features and roadway scenarios to support collaborative roadway/ADS development, testing, and evaluation to support ADS integration into our roadway environment.

The contractor will submit a draft staging, demonstration, and feasibility evaluation plan to FHWA for review and schedule a briefing on the draft plan. The date, time, and place will be discussed with the COR. The COR will confirm the date, time, place and attendance with the contractor. At the briefing, the contractor will lead a walk through and review of the plan. The FHWA will discuss the plan. The FHWA will also provide written comments for the draft plan. The contractor will address FHWA’s comments and finalize the plan. After FHWA approval of the final plan, the COR will instruct the contractor to execute the plan includes the live demonstration and development of draft and final staging, demonstration, and assessment of Artificial Roadway Scenarios Feasibility reports.

Deliverables Draft Staging, Demonstrating, and Assessing the Feasibility of Changeable Artificial Roadway Environment Scenarios plan Final Staging, Demonstrating, and Assessing the Feasibility of Changeable Artificial Roadway Environment Scenarios plan Demonstration Draft Staging, Demonstration, and Assessment of Artificial Roadway Scenarios Feasibility report.

Final Staging, Demonstration, and Assessment of Artificial Roadway Scenarios Feasibility report.

2.0 Period of Performance

The Period of Performance reads as follows:

Base Period: 24 months Option 1 Period: 12 months Option 2 Period: 12 months

3.0 General

3.1 Hours of Operation Not Applicable

3.2 Place of Performance

The work to be performed under this task order shall be performed at contractor’s, or subcontractor’s facilities.

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

Not Applicable

3.5 Periodic Progress Meetings

The contractor agrees to attend progress meetings. The 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 Contractor shall be required to travel throughout CONUS during the performance of this task order to attend meetings, and conferences. The Contractor may be required to travel to off-site training locations and to ship equipment to these locations in support of this SOW. All travel requires Government approval/authorization and notification to the COR.

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

4.0 Government Furnished Equipment and Services

4.1 Services Not Applicable

4.2 Facilities Not Applicable

4.3 Materials Not Applicable

5.0 Applicable Clauses

See Solicitation.

6.0 Attachment/Exhibit List

6.1Exhibit 1 Deliverables Schedule

6.3 Exhibit 2

Schedule of Services (To be included at award)

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

Unless stated elsewhere in this task order, the COR will have 14 calendar days to review draft deliverables and make comments. The Contractor shall have 14 calendar days to make corrections and return the corrected draft deliverable to the Government. This is considered “turn” 1, turn 1 a primary turn by default is 14 calendar days per side, subsequent secondary “turns” will be limited to 7 calendar days per side. If accepted, the Contractor will have 14 calendar days to prepare the draft final for review (PDF version of the actual document).

FHWA will start the internal review for clearance process, consisting of review by the Office of Operations’ (HOP) Marketing and Outreach Coordinator (Coordinator), Information Specialist, Office of Chief Counsel, and Office of Public Affairs. Please note this process can take up to 4 months of review time.

For further clarification, a draft is the stage where the COR/TOCOR reviews the deliverable. The draft final deliverable is the stage where the HOP Coordinator, Information Specialist, Office of the Chief Counsel, and Public Affairs reviews the deliverable. The draft final deliverable stage can take up to the 4 months of review time. The deliverable isn’t considered final until Public Affairs accepts the deliverable. The COR will notify the Contractor and accept the deliverable.

And/or 508

Task 1:

Briefing Materials, Kick-Off Meeting

Print No

No Within two weeks of award

Electronic copies of Briefing materials and 15 hard copies for kick-off meeting

PowerPoint and WORD

COR and CO via email and hard copies to attendees at kick-off meeting

Task 1:

Draft PMP Print No

No Within two weeks of award

Electronic copies of Draft PMP and 15 hard copies for kick-off meeting

Task 1:

Final PMP Print No

No Within four weeks of award

Electronic copies of Draft PMP and 15 hard copies for coordination meeting

Task 1:

Draft Project Schedule Print No

No Within two weeks of award

Electronic copies of Draft Project Schedule and 15 hard copies for kick-off meeting

Task 1:

Final Project Schedule Print No

No Within four weeks of award

Electronic copies of Final Project Schedule and 15 hard copies for coordination meeting

Task 1:

Team Meetings Summaries

Print No

No Within four days after each team meeting

Electronic copies

Task 1:

Monthly Status Reports

Print No

No Within one week after the previous month

Electronic copies

Task 1:

Conference/ Workshop Presentation

Print No

No As directed by COR

N/A

Task 1:

Conference/ Workshop Presentation Materials

Print No

No As directed by COR and 6 weeks prior to scheduled presentation to accommodate FHWA approval process

Electronic copies

Task 1:

Briefing, Closeout meeting Print No

No Briefing materials provided 2 weeks prior to closeout meeting. Meeting scheduled as directed by COR within 3 weeks of end of period of performance for Base period and subsequent options if option executed.

Electronic copies and 15 hard copies provided to attendees of closeout meeting

Task 2:

Stakeholder Modular Roadway Environment Study Group Charter Print No yes Within 6 weeks of award

Electronic

Task 2:

Stakeholder Modular Roadway Environment Study Group Management Plan Print No yes

Task 3:

Possible Roadway Environment Scenarios Table Print No yes Within 12 weeks of award

Electronic

Task 3:

Draft Detailed Descriptions for Initial 3 Roadway Scenarios Print No yes Within 20 weeks of award

Electronic

Task 3:

Draft Detailed Descriptions for Remaining Roadway Scenarios Print No yes Within 30 weeks of award

Electronic

Task 3:

Final Detailed Descriptions for All Roadway Scenarios Print No yes Within 33 weeks of award

Electronic

Task 3:

Draft Roadway Scenario Features Inventory Print No yes Within 36 weeks of award

Electronic

Task 3:

Final Roadway Scenario Features Inventory Print No yes Within 40 weeks of award

Electronic

Task 4:

Draft Visualizations for each roadway scenario and alternative configurations Print No yes Within 43 weeks of award

Electronic

Task 4:

Final Visualizations for each roadway scenario and alternative configurations Print No yes Within 46 weeks of award

Electronic

Task 5:

Draft Roadway Features Investigation, Analysis, and Roadway Feature Profiles Plan Print No yes Within 50 weeks of award

Electronic

Task 5:

Final Roadway Features Investigation, Analysis, and Roadway Feature Profiles Plan Print No yes Within 53 weeks of award

Electronic

Task 5:

Draft Roadway Features Investigation, Analysis, and Roadway Feature Profiles Report Print No yes Within 65 weeks of award

Electronic

Task 5:

Final Roadway Features Investigation, Analysis, and Roadway Feature Profiles Report Print No yes Within 68 weeks of award

Electronic

Task 6:

Artificial Roadway Feature Prototypes Ranking and Recommendation Report Print No yes Within 74 weeks of award

Electronic

Task 6:

Conceptual Prototype Annotated Outline Print No yes Within 77 weeks of award

Electronic

Task 6:

Draft Conceptual Prototype Reports for 2 Initial Artificial Roadway Features Print No yes Within 83 weeks of award

Electronic

Task 6:

Final Conceptual Prototype Reports for 2 Initial Artificial Roadway Features Print No yes Within 86 weeks of award

Electronic

Task 6:

Draft Conceptual Prototype Reports for Remaining Artificial Roadway Features Print No yes Within 96 weeks of award

Electronic

Task6:

Final Conceptual Prototype Reports for Remaining Artificial Roadway Features Print No yes Within 100 weeks of award

Electronic

Option 1- Task 7:

Draft Semi-Generic Initial Prototype Fabrication and Testing Plan Print No yes Within 4 weeks of Option 1 award

Electronic

Option 1 – Task 7:

Final Semi-Generic Initial Prototype Fabrication and Testing Plan Print No

No Within 7 weeks of Option 1 award

Electronic

Option 1 – Task 7:

Draft initial Prototype Fabrication and Testing Report Print No

No Within 13 weeks of Option 1 award

Electronic

Option 1 – Task 7:

Draft Prototype Fabrication and Testing Plans for Remaining Prototypes Print No

Within 17 weeks of Option 1 award

Electronic

Option 1 – Task 7:

Final Prototype Fabrication and Testing Plans for Remaining Prototypes Print No yes Within 20 weeks of Option 1 award

Electronic

Option 1 – Task 7:

Draft Prototype Fabrication and Testing Report Print No

No Within 32 weeks of Option 1 award

Electronic

Option 1 – Task 7:

Final Prototype Fabrication and Testing Report Print No yes Within 35 weeks of Option 1 award

Electronic

Option 1- Task 7:

Artificial Roadway Features Prototype Inventory Print No yes Within 38 weeks of Option 1 award

Electronic

Option 1 – Task 7:

Proof-of-Concept Plan Print No yes Within 40 weeks of Option 1 award

Electronic

Option 1 – Task 7:

Proof-of-Concept Demonstration

Option 1 – Task 7:

Proof-of Concept Report Print No yes Within 48 weeks of Option 1 award

Electronic

Option 2 – Task 8:

Draft Staging, Demonstrating, and Assessing the Feasibility of Changeable Artificial Roadway Environment Scenarios plan Print No

No Within 4 weeks of Option 2 award

Electronic

Option 2 – Task 8:

Final Staging, Demonstrating, and Assessing the Feasibility of…