1	Smart Roadside Initiative USDOT ITS Connected Vehicle Workshop Kate Hartman September 26, 2012
2	Agenda SRI Background and Governing Efforts SRI Vision and Goals Project Team Technical Approach SRI Concept Task Detail: Task 5.1-5.2 High-Level Project Schedule Completed, Current and Upcoming Activities
3	SRI Background What is Smart Roadside? A joint modal initiative between Federal Highway Administration (FHWA) and Federal Motor Carrier Administration (FMCSA). Focus: the development of roadside infrastructure for commercial vehicle operations that employs technologies for information sharing. USDOT vision: demonstrate, evaluate, and deploy interoperable technology and improved data sharing to improve safety, security, operational efficiency, and mobility on the Nation's freight transportation system. Related Research: Wireless Roadside Inspection Program Universal Identification for CMVs Electronic Screening/Virtual Weigh Stations Truck Parking Program
4	SRI – USDOT Governing Efforts USDOT ITS Strategic Research Plan, 2010-2014; defines the strategic direction for the USDOT's ITS research program for the next five years. Emphasis: connected vehicle technologies and applications that uses wireless communications to provide connectivity with and between vehicles; between vehicles and roadway infrastructure; and among vehicles, infrastructure and wireless consumer devices. Areas: safety, mobility, environment SRI represents research to improve safety and mobility of commercial vehicle operations. V2I: Investigate key questions such as are vehicle based safety applications using V2I communications effective and do they have benefits SRI represents mode-specific research in this area with regards to commercial vehicles.
5	SRI Vision and Goals Vision: Commercial vehicles, motor carriers, enforcement resources, highway facilities, intermodal facilities, toll facilities, and other nodes on the transportation system collect data for their own purposes and share the data seamlessly with the relevant parties, in order to improve motor carrier safety, security, operational efficiency, and freight mobility. Goals: Build, install and test prototype of Smart Roadside Application(s) Enable data exchange between vehicle and roadside infrastructures which connect to authoritative databases for information and relevant data.
6	Project Team USDOT: ITS JPO, FHWA, FMCSA: Project Sponsor SAIC Prime Contractor Lead: project management, systems engineering, and prototype design, development, build, install and test North Dakota State’s Upper Great Plains Transportation Institute (UGPTI) Led applications analysis of deployed systems Subject Matter Expertise for design American Transportation Research Institute (ATRI) Led applications analysis of research projects Technical advisor to project team representing the trucking industry Delcan Corporation Led the development of the SRI Concept of Operations Commercial Vehicle Safety Alliance (CVSA) Technical advisor to project team representing the commercial vehicle enforcement community
7	Technical Approach Overview
8	SRI Framework
9	SRI Overview Elements Users: Industry and government users that would access the various capabilities delivered through the system User Interface Applications: Mechanisms by which users would request and receive information and forward instructions External System Interfaces: Linkages with the business and government systems that are needed to gain access to data and disseminate information
10	Task 2-3 Results: User Needs
11	Task 4 Concept of Operations May 2012 Identifies current system and shortcomings Future system concept and capabilities: Identifying Entities on the Road Sharing Information—establishing a common framework Enhanced Electronic Screening—attended and unattended Integrating Public- and Private-Sector Data Streamlined/Accelerated Inspections—Wireless Roadside Inspections and traditional inspections Performance-Based Standards and an Architecture Scenarios: Compliant CMV (“Green Light”) Compliant CMV – Os/Ow permit verification Non-compliant CMV (“Red Light”) Non-compliant CMV – illegal bypass Real-time truck parking information system
12	Task 5 Overview Kickoff in May 2012 Prototype Design, Build and Install: System Requirements Site Selection Architecture Component Level Design Prototype Development and Test Build and Install Prototype Prototype Field Testing Documentation
13	Task 5.1System Requirements: Site Selections Candidates Alberta, Canada Colorado Maine Michigan Connected Vehicle Test Bed Minnesota North Dakota New Jersey Pennsylvania Tennessee Florida Process Survey Distribution (50 states) Inventory of current physical infrastructure, IT tools, communications infrastructure, physical layout and hardware. Evaluation of available infrastructure, availability for participation
14	Task 5.1 – System Requirements Draft submission to USDOT – 8/10/12 USDOT comments: 8/31/12 Revision: 9/18/12 Walkthrough: tentative early October Final SyRS: 10/29/12 or sooner IEEE 1233 compliant
15	Task 5.1 System Requirements - Details Traceability: Unique identifier Source Verification method: Test Analysis Demonstration Inspection Demonstration Location: Michigan and/or Colorado Future Site Categories: System Interface Application Performance Security Additional Content: Physical Requirements: Environmental Construction Durability/Adaptability Data Requirements System Operations Specifications
16	Task 5.2 System Architecture Draft submission to USDOT – 8/10/12 USDOT comments: 8/31/12 Revision: 9/18/12 Walkthrough: tentative early October Final SAD: 10/29/12 or sooner Sources: Architecture Description Document, Version 1.1, 11/26/07 (Software Engineering Institute) IEEE Recommended Practice for Architectural Description of Software-Intensive Systems (IEEE Std 1471-2000)
17	Task 5.2 System Architecture - Details Architecture decisions Operational and logical views Operational elements Software components Information exchanges System views: Components and relationships Technical views and technologies
18	Task 5.2 – Functional Architecture
19	Project Schedule
20	Completed Activities Project Management Plan Systems Engineering Master Schedule Systems Engineering Management Plan Configuration Management Plan Task 2-3 Tech Memo 1: Documentation Review Task 2-3 Tech Memo 2: User Needs Task 2-3 Tech Memo 3: Prioritization of Applications Task 4: Draft ConOps Task 4: ConOps Walkthroughs Stakeholder Engagement: Reviews of user needs, operational policies, operational constraints
21	Current and Upcoming Activities Current Activities Scheduling and preparing SyRS and SAD walkthroughs Upcoming Activities: SyRS and SAD walkthroughs SyRS and SAD Final versions Kickoff SRI system design
22	Points of Contact