Request for Letters of Intent. Connected Traffic Control System (CTCS): Research Planning and Concept Development. October 18, 2017.

Transcription

1 Request for Letters of Intent Connected Traffic Control System (CTCS): Research Planning and Concept Development October 18, 2017 Issued by University of Virginia Center for Transportation Studies Charlottesville, Virginia On Behalf of Connected Vehicle Pooled Fund Study

2 I. GENERAL INFORMATION Request for Letters of Intent (RFLI) Name: Connected Traffic Control System (CTCS): Research Planning and Concept Development The RFLI has been posted on the Connected Vehicle Pooled Fund Study (CV PFS) website ( for your information. Addenda and attachments will be posted if issued. It is the responsibility of interested parties to ensure that the latest version of the entire RFLI and related links are reviewed prior to submission of a letter of intent. We encourage you to check the website frequently for any changes prior to the due date. For ease of reference, each firm or individual receiving this RFLI is referred to as an interested party and the firm or individual selected as a potential partner of the University of Virginia Center for Transportation Studies (UVA CTS) on behalf of the CV PFS is referred to as the Subcontractor. This RFLI states the instructions for submitting letters of intent, and the procedure and criteria by which a Subcontractor may be selected. RFLI Schedule: Issue Date: Wednesday, October 18, 2017 RFLI Questions: Any questions or requests for necessary additional information concerning this RFLI must be ed to the UVA CTS listed below no later than 3:00 p.m. ET on Tuesday, October 31, 2017 in order to guarantee a timely response prior to the letter of intent due date. Letters of Intent Due Date: 3:00 p.m. ET on Wednesday, November 15, Letters of Intent must be sent to the UVA CTS via using the contact information in the box below. The UVA CTS reserves the right to reject letters of intent received after the stated due date and time. Expected Subcontract Start Date: February 2018 o Term: For eighteen months o Level of Effort: $400,000 REFER ALL QUESTIONS TO: University of Virginia Center for Transportation Studies Attention: Hyungjun Park Phone: hpark@ .virginia.edu 1

3 Procedure: It is important to note that preparation and submission of a letter of intent (for detailed contents, see Section IV. Contents of the Letter of Intent), in response to this RFLI, is completely voluntary, without any bearing on contractual obligations. In case none of the submitted letters of intent is satisfactory to CV PFS team s expectation, the CV PFS team may opt not to establish a subcontract. The purpose of this RFLI is to identify a potential partner that may work, as a Subcontractor, with the CV PFS and the UVA CTS on the project outlined in this RFLI. Once all the letters of intent are received, the below procedure will be followed: 1. The CV PFS team members will evaluate the letters of intent (including a signed cover letter, a proposal, and a budget) submitted in response to the RFLI to identify an interested party that best meets CV PFS s needs as a preferred Subcontractor; 2. Once a preferred Subcontractor is identified, the CV PFS and the selected preferred Subcontractor will conduct negotiations to come to an agreement on the scope and budget of a subcontract; and 3. Finally, a formal subcontract will be established through the University of Virginia Office of Sponsored Programs and the preferred Subcontractor officially becomes the Subcontractor. II. BACKGROUND INFORMATION CONNECTED VEHICLE POOLED FUND STUDY The project detailed in this RFLI is intended to investigate Connected Traffic Control System: Research Planning and Concept Development for the CV PFS entitled Program to Support the Development and Deployment of Connected Vehicle Applications. This CV PFS was created by a group of state, local, and international transportation agencies and the Federal Highway Administration (FHWA), with the Virginia Department of Transportation (VDOT) serving as the lead agency. The UVA CTS is supporting VDOT on the pooled fund study, serving as the technical and administrative lead for the effort. For more information about the pooled fund study, please visit Since 2011, CV PFS and the United States Department of Transportation (USDOT) have been collaborating to develop and demonstrate the Multi-Modal Intelligent Traffic Signal Systems (MMITSS) under the Dynamic Mobility Application Program of USDOT. The Phase 1 (Development of Concept of Operations, System Requirements, System Design and a Test Plan) and the Phase 2 (System Development, Deployment and Field Test) of the MMITSS projects were completed. Currently, the MMITSS Phase 3 (Deployment Readiness Enhancement) is under way. As an extension to these MMITSS efforts, CV PFS and USDOT have agreed on pursuing the Connected Traffic Control System: Research Planning and Concept Development project together to conduct the foundational research for the future traffic control systems under 2

4 the upcoming connected vehicle environment. Similar to the MMITSS Phase 1-3 effort, USDOT will provide CV PFS with fund and the CV PFS team will provide additional matching fund. Finally, UVA CTS will manage the MMITSS Phase 3 project on behalf of CV PFS and USDOT. INTRODUCTION The Intelligent Transportation Systems (ITS) Strategic Plan identifies six focus areas that the Federal ITS program is pursuing over a five-year period and details the overall approach for advancing each category from research through field testing to technology transfer to the support of widespread deployment. Connected Vehicle and Automation are among the identified areas. The USDOT Vehicle to Infrastructure (V2I) Program aims to leverage connected vehicle technology in order to develop and evaluate a systems environment that allows transfer of information between vehicles and infrastructure to enable benefits in safety, mobility, and environment. The program research also involves multiple transportation agencies and modes, which include passenger cars, transit vehicles, freight vehicles, pedestrians, and bicyclists, and both technical and institutional elements. The scope of the V2I program includes supporting the development of enabling V2I technologies, applications, and facilitating deployment through provision of products, tools, and other implementation support. While there has been progress in connected vehicle integration with individual traffic signals (e.g., Signal Phase and Timing message, Pedestrian applications at signalized intersection), and modeling of corridor applications like signal priority, there is a need for research toward a broader view of operational control that considers both Connected Vehicles and Automation. The vision for this research planning effort is to build upon the progress in the MMITSS research and development and progress toward next generation research that recognizes the value of developing a comprehensive systematic approach to traffic operations that incorporates connected and automated vehicles (CAVs). Automation may vary significantly in design and operation; the modes of operation (including levels of automation) and control strategies need to be taken into consideration so that expected benefits, such as reductions in crashes and smoother or more efficient flow, can be realized and potential adverse impacts like conflicts with human driving patterns minimized. Connectivity with infrastructure has significant potential for implementing new advanced operations and control strategies on arterials and interchanges that are currently controlled by traffic signals designed and operated for human drivers. Developments and anticipated deployments in vehicle automation have been rapid; this effort envisions a more thorough examination of interaction between vehicles and transportation network infrastructure that could include operational control elements over a larger scope than an intersection (arterials, interchanges with freeways, etc.). It is anticipated that control elements will be examined initially at lower levels of automation (e.g., infrastructure communication could provide input to Level 1 longitudinal control), however this effort also needs to consider the impacts of vehicle automation developments at higher levels which may or may not be connected. The proposed CTCS effort is one of the research areas identified under the V2I Program as a high priority for infrastructure owners and operators. CTCS research is designed to focus on the complexity and interaction of traffic, including CAVs and multimodal and other roadway users, 1 3

5 as it moves on arterials and freeway interchanges, to enable integrated traffic control operations. By recognizing the capabilities and needs of different roadway users in this environment, transportation system management and operations (TSMO) can better achieve improvements and minimize adverse impacts. Multiple factors need to be considered, including safety, mobility, and environment impacts, and performance measures that reflect local infrastructure operator needs. CTCS will incorporate traffic control related CAV applications (e.g., red light violation warning, eco-departure and arrival, MMITSS, etc.) into an integrated traffic control concept based on use cases or packages that considers how control strategies on arterials and freeway interchanges will work in conjunction using performance-based decision factors. CTCS research will use a systematic and stakeholder-focused approach to identify operational and control needs across arterial, interchange and freeway environments as adoption of connected and automated vehicles increases, and develop concepts and capabilities that address these needs. These activities will build upon and leverage progress in related areas such as MMITSS applications, MMITSS deployment readiness, and automated control. The envisioned future capability will allow infrastructure operators to execute control strategies that balance a diverse group of roadway user needs temporally and geographically. In order to assess the potential for CTCS improvements, a variety of research questions need to be answered within a highly-dynamic, evolving environment. An incremental approach is anticipated so that developments and changes in technologies and adoption can be reflected in research stages. Coordination with other related research activities (e.g., MMITSS Deployment Readiness, USDOT connected vehicle and automation research, and other activity such as NCHRP 20-24(98)/ CAV research, etc.) will be important in order to maintain awareness and allow for mutually beneficial sharing of information and results. Given that many activities and efforts may relate to the CTCS vision, this project aims to conduct a stakeholder-focused research planning process to identify and prioritize potential research and development efforts, and initiate concept development in high priority area(s) that support the future development of prototypes and implementation. III. SCOPE OF SERVICES The UVA CTS, on behalf of CV PFS, seeks a qualified organization (the Subcontractor ) to conduct foundational analysis and design to prepare for the development and eventual deployment of the Connected Traffic Control System (CTCS) (the Services ). A. GOAL AND OBJECTIVES The goal of this project is to develop the research plan of the Connected Traffic Control System (CTCS) with prioritized research areas, and develop the concept of operations (ConOps) of the high priority research area(s). The objectives of this project are: To review the existing studies and developments and engage with stakeholders to identify the needs of the current traffic control systems as CAVs become more common, and map the potential benefits that can be achieved under CTCS. 4

6 To engage, coordinate and collaborate with other stakeholders, including other researchers, infrastructure owner operations staff, deployers, traffic signal control vendors, standards groups, vehicle systems representatives like the Crash Avoidance Metrics Partners (CAMP) 2 and other Original Equipment Manufacturers (OEMs), to avoid duplication where possible and enhance research outcomes through validation of needs and constraints. To develop the CTCS research plan and provide supporting information to enable assessment and prioritization of continued short and longer term research and development strategy. To develop a CTCS Concept of Operations (ConOps) of the high priority research area(s) that comprehends the entire roadway system (i.e., considering traffic signals along arterials, interactions with ramp terminals, and ultimately freeway facilities from a multimodal perspective that considers connected automation). B. DETAILED REQUIREMENTS In order to accomplish the objectives of this project, the Subcontractor shall perform the following tasks: Task 1: Project Management Task 2: Stakeholder Engagement Planning for Research Task 3: Research Review Task 4: Assessment of Technology Readiness Levels for Priority Research Areas Task 5: Development of CTCS Research Plan Task 6: Development of Concept of Operations (ConOps) of High-Priority Research Area(s) Note: Some activities may be in parallel, not necessarily sequential. Table 1 provides an example of the task schedule: Table 1 Example Task Schedule Project Month Task 1 Task 2 Task 3 Task 4 Task 5 Task 6 2 CAMP is working with USDOT under a cooperative agreement to further V2I research; any interaction/activity with CAMP will be through approval/coordination with USDOT. 5

7 Task 1: Project Management The purpose of this task is for the Subcontractor to provide project management support for all tasks described in this scope of services. The Subcontractor shall conduct the followings specific task items: Develop a Project Management Plan (PMP) that guides the execution of Work Task Activities identified in this scope of services. The PMP shall include plans for: Scope Management, Cost Management, Quality Management, Human Resources Management, Communications Management, and Risk Management. Prepare a detailed Project Schedule that lists all planned tasks and milestones for the project and submit an electronic project file in Microsoft Project 2010 or higher format. 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) consisting of at least two levels. The Project Schedule shall be updated monthly. Participate in a project kick-off meeting within four weeks of contract award to ensure common understanding of scope with USDOT and PFS Members. Schedule and participate in a monthly project status calls, team meetings and teleconferences as requested. Prior to each call or meeting, prepare an agenda that includes project progress, schedule, scope issues, budget, and results of tasks at team meetings. Within a week of each call or meeting, prepare team meeting summaries, which will, at a minimum, track the status of action items. Submit a monthly progress report by the 15th of each month. These reports shall identify all deliverables and deliverable status (not initiated, in progress X% complete, draft delivered, in revision X% complete, final delivered, accepted). Monthly reports shall contain a narrative of accomplishments by task and projected activities in the next quarterly period. Monthly reports shall also contain an updated project schedule with a risk narrative and a projected cost-to-complete narrative. Attend a project closeout meeting in the last week of the project. At this meeting, 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. The Subcontractor shall submit the DRAFT PMP and Project Schedule for review by the Project Manager, the PFS Members, USDOT coordinator and other USDOT representatives, and revise based on feedback received. Based on the discussions at the kickoff meeting and the comments received, the Subcontractor shall submit to the Project Manager and USDOT coordinator the REVISED PMP, Project Schedule and the Comment Resolution Report that documents how each comment was resolved. The Subcontractor shall discuss the resolution of the comments with the Project Manager, the PFS Members, USDOT coordinator and the USDOT 6

8 representatives as needed. The Subcontractor shall make any final revisions based on additional feedback received, and deliver the Final PMP and Project Schedule. NOTE: The deliverables created in this work will support the full development of deployable applications within the CTCS concept. The UVA CTS expects the Subcontractor to apply sound systems engineering principles 3 in conducting this work. Task 1 Deliverables: DRAFT PMP and Project Schedule Briefing Materials, Kick-Off Meeting REVISED PMP, Project Schedule and the Comment Resolution Report FINAL PMP and Project Schedule Monthly Progress Reports Monthly Project Status Call Agendas and Minutes Team Meeting Agendas and Summaries, as needed Briefing Materials, Closeout Meeting Task 2: Stakeholder Engagement Planning for Research The purpose of this task is to ensure that the CTCS research plan development activities draw upon input and feedback from all relevant stakeholder groups that relate to connected traffic control operations so that the resulting research plan is balanced and reflects stakeholder needs, priorities, and constraints. This task is cross-cutting in nature and will cover planning and coordination for stakeholder engagement conducted in later tasks. Results from stakeholder engagements shall be documented as part of the corresponding Task activities. The Subcontractor shall develop a Stakeholder Engagement Plan that identifies potential stakeholders from academia, and public and private sectors, describes the goals of the stakeholder engagement (for example, to identify and prioritize research areas), describes the engagement activities and schedule, and the two-way communication plan with the stakeholders throughout the entire project. The Stakeholder Engagement Plan will be used to guide the Subcontractor s engagement activities with stakeholders in other tasks (such as the nature of the workshop and other engagements needed for Task 4). The Subcontractor shall work especially closely with PFS representatives and the MMITSS Deployment Readiness Enhancements contractor (under separate contract) to ensure full input from both groups. The Subcontractor shall develop a plan to convey the CTCS concept to stakeholders and solicit the stakeholder input from a broad set of modes and system users, including but not limited to federal, state and local departments of transportation, transit agencies, freight stakeholders, and organizations 3 7

9 representing pedestrian and non-motorized forms of travel. In addition, the Subcontractor shall include the following entity representative(s) in the stakeholder list: CAMP, OEMs and Infrastructure Owner/Operators (IOO) ATCMTD, CV Pilot and Smart Columbus Demonstration Contractors V2I Deployment Coalition Traffic Signal, Arterial and Freeway Operations related Groups Connected Vehicle and Automation Application Developers/Vendors Traffic Signal Control Vendors Transit / Bus representatives Vulnerable Road User Programs The Subcontractor shall submit the DRAFT Stakeholder Engagement Plan for review by the Project Manager, the PFS Members, USDOT coordinator and other USDOT representatives, and revise based on feedback received. The Subcontractor shall submit to the Project Manager and USDOT coordinator the REVISED Stakeholder Engagement Plan and the Comment Resolution Report that documents how each comment was resolved. The Subcontractor shall discuss the resolution of the comments with the Project Manager, the PFS Members, USDOT coordinator and the USDOT representatives as needed. The Subcontractor shall make any final revisions based on additional feedback received, and deliver the Final Stakeholder Engagement Plan. Task 2 Deliverables: DRAFT Stakeholder Engagement Plan REVISED Stakeholder Engagement Plan and the Comment Resolution Report FINAL Stakeholder Engagement Plan Task 3: Research Review The purpose of this task is for the Subcontractor to review the existing research, identify the gaps, and solicit initial stakeholder input in identifying potential research areas and priorities, user needs, transformative benefits or goals, and corresponding performance measures for the CTCS. The Subcontractor shall perform a literature review to identify and synthesize the existing studies and research, developments and deployments, and map the potential benefits that can be achieved under CTCS. The literature review shall include but is not limited to the following efforts: a) current research in the area of connected and automated vehicles at the University of Michigan, b) research in the area of connected vehicles at Carnegie Mellon University, c) ongoing research being pursued at Virginia Tech Transportation Institute especially in the area of Eco-Approach and Departure, d) current research at Mississippi State University in the area of connected vehicles e) on-going USDOT sponsored deployments, such as Connected Vehicle Pilot projects and Smart Columbus, f) on-going work to make Multi-Modal Intelligent Traffic 8

10 Signal Systems (MMITSS) deployment ready (e.g., Utah DOT and PFS projects), g) other USDOT sponsored research such as University Transportation Center (UTC) research, GlidePath application (cooperative adaptive cruise control (CACC) and Eco-Approach and Departure) and Automated Traffic Signal Performance Measures (ATSPMs), h) NCHRP Connected Automation Research efforts, and i) related automation developments. It should be noted that there are other nascent efforts currently underway in Florida and grants awarded as part of the Advanced Transportation and Congestion Mitigation Technologies Deployment (ATCMTD) that consider connected and automated vehicles to solve real-world issues. The Subcontractor shall include a broad portfolio of research, which may include both published and ongoing efforts, in the area of connected and automated vehicles and not restricted to the aforementioned research. Based on the Task 2 stakeholder engagement planning, the Subcontractor shall engage with relevant stakeholder groups to ensure that the literature/research review is comprehensive and adequately captures potential areas for further assessment in Task 4. The research review report shall include a summary of the stakeholder engagement and feedback/takeaways from this activity. The Subcontractor shall also review and consider previous research planning documents developed by the US DOT V2I Program. 4 As part of the research review, the Subcontractor shall identify potential research areas for the CTCS and conduct an initial high-level assessment of Technology Readiness Levels (TRL) 5 of the identified research areas. The TRL assessments in this task are not intended to be precise, but rather to help guide the initial categorization of potential research; Task 4 includes a more indepth assessment. The Subcontractor shall submit the DRAFT Research Review for review by the Project Manager, the PFS Members, USDOT coordinator and other USDOT representatives, and revise based on feedback received. The Subcontractor shall submit to the Project Manager and USDOT coordinator the REVISED Research Review and the Comment Resolution Report that documents how each comment was resolved. The Subcontractor shall discuss the resolution of the comments with the Project Manager, the PFS Members, USDOT coordinator and the USDOT representatives as needed. The Subcontractor shall make any final revisions based on additional feedback received, and deliver the Final Research Review. Task 3 Deliverables: DRAFT Research Review REVISED Research Review and the Comment Resolution Report FINAL Research Review 4 Internal US DOT document. Will be available upon request

11 Task 4: Assessment of Technology Readiness Levels for Priority Research Areas The purpose of this task is for the Subcontractor to seek more in-depth stakeholder input and prioritize the CTCS research areas generated from Task 3. To gather stakeholder input to prioritize the identified research areas, the Subcontractor shall arrange for and host an in-person stakeholder workshop and other engagements (e.g., additional web workshop, survey, etc.), as planned in Task 2. The stakeholder workshop may be held in conjunction with other events, such as the CV PFS in person meeting or the Transportation Research Board (TRB) annual meeting. The Subcontractor shall also include a remote web conference feature to interact with remote participants. The Subcontractor shall, at a minimum, include the stakeholder groups listed in Task 2. The proposed budget shall include the fund to support this in-person stakeholder workshop. Note that the CV PFS will fund the travels made by the CV PFS members and a limited number of public sector stakeholders to participate in this workshop. The Subcontractor shall consolidate and analyze the feedback from the stakeholders and identify the priority research areas that may be candidates for prototype development and testing efforts under the CTCS. The Subcontractor shall update the TRL assessment of the identified priority research areas to include a more in-depth assessment and understand the level of deployment readiness. It is important to note that deployment readiness includes institutional and other factors that are not limited to technical capability. Discussion of relevant deployment readiness factors, including potential uncertainties and impediments, and summary of stakeholder feedback, shall also be included in the documentation for this task. The Subcontractor shall incorporate these factors into a Priority Assessment for each identified priority research area. The Subcontractor shall submit the DRAFT Technology Readiness Levels (TRL) and Priority Assessment of CTCS Research Areas for review by the Project Manager, the PFS Members, USDOT coordinator and other USDOT representatives, and revise based on feedback received. The Subcontractor shall brief Stakeholder Engagement Workshop Results and Updated CTCS TRL/Priority Assessment to the Project Manager, the PFS Members, USDOT coordinator and other USDOT representatives. The Subcontractor shall submit to the Project Manager and USDOT coordinator the REVISED CTCS TRL/Priority Assessment and the Comment Resolution Report that documents how each comment was resolved. The Subcontractor shall make any final revisions based on additional feedback received, and deliver the Final CTCS TRL/Priority Assessment. Task 4 Deliverables: Stakeholder Engagement/Workshop and Briefing Materials DRAFT TRL/Priority Assessment of CTCS Research Areas Briefing of Stakeholder Engagement/Workshop Results and Updated CTCS TRL/Priority Assessment REVISED TRL/Priority Assessment and the Comment Resolution Report FINAL TRL/Priority Assessment of CTCS Research Areas 10

12 Task 5: Development of CTCS Research Plan The purpose of this task is to develop the CTCS research plan based upon the findings from Task 3 and 4, an assessment of feasibility, deployment interest, prioritization of CTCS research areas and development efforts. Sufficient detail shall be provided to enable understanding of needs, high-level expected benefits and costs, risks, and short term and long term expectations for realization of CTCS research and development results. Based on the results of Task 4, for each priority research area, the Subcontractor shall identify related research projects, interdependencies within the Connected Vehicle program and other USDOT-related activities, potential standards work, and outreach and policy needs. In addition, the Subcontractor shall provide recommended level of effort, duration, sequencing (including dependencies) and key milestones for each priority research area for CTCS research and development. In the research plan, the Subcontractor shall identify a clear path from research through to deployment, including early opportunities to incrementally deploy technologies within the overall goal of CTCS. The path of the CTCS shall be coordinated with the related USDOT research, and depict the planned steps using the USDOT roadmap template 6. For the short-term research areas (within 5 years), the Subcontractor shall identify and document the individual research and development projects to include the project description, and recommended project schedule, cost, deliverables, etc. For longer-term research areas (5-10 years), a higher-level view is appropriate, with approximate level of effort and timeframe for activity areas. The Subcontractor shall submit the DRAFT CTCS Research Plan for review by the Project Manager, the PFS Members, USDOT coordinator and other USDOT representatives, and revise based on feedback received. The Subcontractor shall submit to the Project Manager and USDOT coordinator the REVISED CTCS Research Plan and the Comment Resolution Report that documents how each comment was resolved. The Subcontractor shall brief the REVISED CTCS Research Plan to the Project Manager, the PFS Members, USDOT coordinator and other USDOT representatives. The Subcontractor shall make any final revisions based on additional feedback received, and deliver the Final CTCS Research Plan. Task 5 Deliverables: DRAFT CTCS Research Plan REVISED CTCS Research Plan and the Comment Resolution Report CTCS Research Plan Briefing FINAL CTCS Research Plan Task 6: Development of Concept of Operations (ConOps) of High-Priority Research Area(s) 6 The USDOT roadmap template is available upon request. 11

13 The purpose of this task is for the Subcontractor to develop a Concept of Operations (ConOps) document(s) for the CTCS high priority research area(s) in support of future prototyping efforts. The Subcontractor shall coordinate with the Project Manager, the PFS Members, USDOT coordinator and other USDOT representatives to select the high-priority research area(s). The decision to select one, or more than one, ConOps to be developed in this task will depend in large part on the Research Plan results. The Subcontractor shall provide support for this selection process to consider results from other Tasks, program plans, related efforts made by other parties, and other developments. The Subcontractor shall use the Stakeholder Engagement Plan as developed in Task 2 as a guide to conduct engagement activities, such as a user needs workshop or walkthroughs. However, since this task relies upon a narrower, more focused group of stakeholders than earlier tasks, the Subcontractor shall first identify the relevant stakeholders that can provide input on user needs, operational considerations, and other aspects of the concept being developed, and work with the Project Manager and USDOT coordinator to review and coordinate the planned stakeholder participation under this Task. In case an in-person meeting is proposed by the Subcontractor, the proposed budget shall include the fund to support this in-person meeting. Note that the CV PFS will fund the travels made by the CV PFS members and a limited number of public sector stakeholders to participate in this workshop. The Subcontractor shall follow the guidance in IEEE Standard , IEEE Guide for Information Technology System Definition Concept of Operations (ConOps) Document. The Subcontractor shall apply sound Systems Engineering principles in conducting this work. The ConOps shall define what transformative goals might be realized with the CTCS research area(s), and the corresponding qualitative and quantitative measures for estimating the performance of the applications in achieving these transformative goals. The ConOps shall specifically consider operational scenarios that allow for the logical evolution from current practice to the end-state condition proposed for CTCS. The Subcontractor shall submit the DRAFT ConOps for review by the Project Manager, the PFS Members, USDOT coordinator and other USDOT representatives, and revise based on feedback received. The Subcontractor shall submit to the Project Manager and USDOT coordinator the REVISED ConOps and the Comment Resolution Report that documents how each comment was resolved. The Subcontractor shall schedule and conduct a face-to-face review ( walkthrough see IEEE Std for this and all subsequent reviews) of the revised ConOps with the project manager, the PFS members, USDOT coordinator, other USDOT representatives and key stakeholders to obtain comments on the ConOps from a functional, technical, management, and implementation perspective. This face-to-face review shall be supplemented with a web conference for remote stakeholder participation upon approval from the Pooled Fund Study 12

14 team. The Subcontractor shall provide a walkthrough comment resolution report that documents how each comment was resolved as well as the REVISED ConOps. The Subcontractor shall make any revisions based on additional feedback received at the walkthrough and deliver the Final ConOps. Task 6 Deliverables: DRAFT CTCS ConOps of High-Priority Research Area(s) REVISED CTCS ConOps and the Comment Resolution Report CTCS ConOps Walkthrough and Workbooks REVISED CTCS ConOps and Walkthrough Comment Resolution Report FINAL CTCS ConOps of High-Priority Research Area(s) C. DELIVERABLES AND SCHEDULE The Subcontractor shall submit Interim and Final Deliverables concurrently to the UVA CTS, to the USDOT Coordinator and to ITSProjects@dot.gov. The Subcontractor shall include the contract number (and task order number if appropriate) in the for each deliverable. The Subcontractor shall propose dates that account for the proposed approach. Note that task activities are not necessarily sequential, and some activities (such as stakeholder engagement) are expected to be concurrent with others. The UVA CTS s proposed timeframe is outlined in the table below: TASK NAME AND DELIVERABLE DUE DATE 508 Compliant Deliverables 7 Task 1: Project and Systems Engineering Management DRAFT PMP and Project Schedule Within 2 weeks of Award Briefing Materials, Kick-Off Meeting Within 4 weeks of Award REVISED PMP, Project Schedule and the Comment Resolution Report Within 6 weeks after Award FINAL PMP and Project Schedule Within 8 weeks after Award Monthly Progress Reports 15th of each month Monthly Project Status Call Agendas and Minutes Every month Team Meeting Agendas and Summaries As needed Briefing Materials, Closeout Meeting Within 1 week before Contract ends Task 2: Stakeholder Engagement Planning for Research DRAFT Stakeholder Engagement Plan Within 8 weeks after Award REVISED Stakeholder Engagement Plan and the Within 12 weeks after Award Comment Resolution Report FINAL Stakeholder Engagement Plan Within 14 weeks after Award X Task 3: Research Review DRAFT Research Review Within 16 weeks after Award 7 Please follow ITS JPO s publication guidelines: 13

15 TASK NAME AND DELIVERABLE DUE DATE 508 Compliant Deliverables 7 REVISED Research Review and the Comment Within 20 weeks after Award Resolution Report FINAL Research Review Within 24 weeks after Award X Task 4: Assessment of Technology Readiness Levels for Prioritized Research Areas Stakeholder Engagement/Workshop and Briefing Within 28 weeks after Award Materials DRAFT TRL/Priority Assessment of CTCS Prioritized Research Areas Within 32 weeks after Award Briefing of Stakeholder Engagement/Workshop Results and Updated CTCS TRL/Priority Within 36 weeks after Award Assessment REVISED TRL/Priority Assessment and the Comment Resolution Report Within 40 weeks after Award FINAL TRL/Priority Assessment of CTCS Prioritized Research Areas Within 44 weeks after Award X Task 5: Development of CTCS Research Plan UPDATED CTCS Research Plan Within 46 Weeks after Award REVISED CTCS Research Plan and the Comment Resolution Report Within 50 Weeks after Award CTCS Research Plan Briefing Within 54 Weeks after Award FINAL CTCS Research Plan Within 58 Weeks after Award X Task 6: Development of Concept of Operations (ConOps) of High-Priority Research Area(s) DRAFT CTCS ConOps of High-Priority Research Area(s) Within 60 Weeks after Award REVISED CTCS ConOps and the Comment Resolution Report Within 64 Weeks after Award CTCS ConOps Walkthrough and Workbooks Within 68 Weeks after Award REVISED CTCS ConOps and Walkthrough Comment Resolution Report Within 72 Weeks after Award FINAL CTCS ConOps of High-Priority Research Within 74 Weeks after Award Area(s) X IV. CONTENTS OF THE LETTER OF INTENT Letters of Intent are to provide a concise description of the research plan and capabilities of the interested party to satisfy the requirements of the RFLI. Emphasis will be on completeness and clarity of content. The letter of intent should include a signed cover letter, a proposal, and a proposed budget. The interested party shall submit the following in the letter of intent: 1. A signed cover letter (2 pages or less) 2. A proposal (20 pages or less, not including a title page and qualifications of participants) a. A detailed description and the full plan, to include a timeline, to accomplish the project proposed 14

16 b. A brief history of the interested party and its experience, qualifications and success in providing the type of service requested 3. The interested party s proposed price / fee for providing the Services (no page limit) V. BASIS OF SELECTION OF SUBCONTRACTOR Letters of intent accompanied with proposals will be evaluated based upon the overall merits/value including, but not limited to, price. All letters received will be carefully evaluated by the CV PFS based on the following criteria: 1. The interested party s technical plan to provide the CV PFS with the products as described in the Scope of Services section; 2. The interested party s experience in providing Services similar to those described in this RFLI; and 3. The interested party s price/fee for providing the Services. 15