spat challenge webinar series
play

SPaT Challenge Webinar Series Webinar #1: Initial SPaT Challenge - PowerPoint PPT Presentation

SPaT Challenge Webinar Series Webinar #1: Initial SPaT Challenge Activities 2:00 3:30 PM (Eastern) | March 6, 2018 Webinar Logistics All lines are muted Webinar will be recorded Submit questions and comments in chat or Q&A


  1. SPaT Challenge Webinar Series Webinar #1: Initial SPaT Challenge Activities 2:00 – 3:30 PM (Eastern) | March 6, 2018

  2. Webinar Logistics • All lines are muted • Webinar will be recorded • Submit questions and comments in chat or Q&A section of webinar window • Questions will be answered at webinar conclusion 2

  3. Agenda • Introduction to the SPaT Webinar Series  Blaine Leonard, Utah DOT • Systems Engineering Approach to the SPaT Challenge  Ray Starr, Minnesota DOT  Dean Deeter, Athey Creek Consultants • Costs, Procurement, and Corridor Selection  Blaine Leonard, Utah DOT • Q&A 3

  4. Introduction to the SPaT Webinar Series Blaine Leonard, Utah DOT

  5. Update on V2I Deployment Coalition (V2I DC) Phase 2 • V2I DC activities have resumed • https://transportationops.org/V2I/V2I-overview • SPaT Challenge activities will continue under the Strategic Initiatives Technical Working Group Strategic Initiatives TWG SPaT SPaT Challenge Challenge Tactical Working Resource Team Group 5

  6. Update on V2I DC Phase 2 • Strategic Initiatives Working Group (Phase 1 TWG 1)  Chaired by Greg Larson, Caltrans  Meets 4 th Thursday of every month at 2pm ET  Next meeting: March 22 at 2pm ET • Technical Resources Working Group (Phase 1 TWG 4)  Chaired by Faisal Saleem, MCDOT  Meets 2 nd Wednesday of every month at 11am ET • Peer Exchange & Outreach Working Group  Chaired by Ed Seymour, TTI • To be added to or removed from one or more groups, visit: https://www.surveymonkey.com/r/V2IDC_TWGs 6

  7. SPaT Challenge What is the Challenge? To challenge state and local public sector transportation IOOs to cooperate together to achieve deployment of DSRC infrastructure with SPaT broadcasts in at least one corridor or network (approximately 20 signalized intersections) in each state by January 2020 7

  8. SPaT Challenge What is SPaT? A Signal Phase and Timing (SPaT) message defines the current intersection signal light phases Current state of all lanes at intersection are provided, as well as any active pre-emption or priority. SPaT message defined by SAE J2735 (a subject of a subsequent webinar) 8

  9. SPaT Challenge Why do this Challenge? To provide IOOs with an entry into DSRC-based V2I deployment and gain valuable procurement, licensing, installation, and operation experience, which in turn will:  Lay ground work for more advanced V2I deployments  Show a commitment to OEMs and applications developers  Analogous to early fiber deployments – most benefits came later 9

  10. SPaT Challenge What are the benefits? • Be more prepared for DSRC-equipped vehicles and on-board V2I applications • Useful as testing site for future applications • Supports deployment of V2I applications that build on SPaT at intersections:  Smart Transit Signal Priority  Red Light Violation Warning  Intelligent Signal Systems  Eco-Driver 10

  11. SPaT Challenge What is the long-term goal? • Widespread deployment of V2I applications at intersections will lead to:  Improved safety for drivers and pedestrians  Improved mobility for traveling public, transit, freight, snow plows, and other fleet vehicles • High penetration rates in vehicles  Agency vehicles and OEM-produced vehicles able to utilize and benefit from SPaT broadcasts • We have to start small . . . And scale up! 11

  12. SPaT Challenge Website One-stop shop for SPaT-related information • Overview • Current map with SPaT deployment details and contacts • Resources https://transportationops.org/spatchallenge 12

  13. SPaT Challenge Website + New ConOps Document + Webinar Schedule and Recordings 13

  14. Upcoming SPaT Challenge Webinars • Design Considerations, Part 1  March 20, 2018 2:00-3:30pm ET  Signal controller interface and creation of SPaT messages  Examples of designs for assembling SPaT messages  DSRC licensing • Design Considerations, Part 2  April 17, 2018 2:00-3:30pm ET  MAP messages and vehicle position correction • MAP Creator Tool Demonstration  April 24, 2018 1:00-2:30pm ET  Live technical demonstration and step-by-step training on using the MAP creator tool • Design Considerations, Part 3  May 15, 2018 2:00-3:30pm ET  Backhaul infrastructure, intersection, and roadside equipment specification, design and installation • Deployment & Validation  June 12, 2018 2:00-3:30pm ET  Procurement, validation, verification, and security of SPaT deployments 14

  15. Systems Engineering Approach to the SPaT Challenge Ray Starr, Minnesota DOT

  16. Why a Systems Engineering Approach? • Federal funding requires it • System that meets user needs • Needs are not missed • Common understanding of intent • Basis for testing • Stakeholder roles • Especially valuable for implementing non- routine systems 16

  17. Systems Engineering “Vee” Diagram Source: FHWA https://www.fhwa.dot.gov/cadiv/segb/ 17

  18. Concept of Operations (ConOps) Source: FHWA https://www.fhwa.dot.gov/cadiv/segb/ 18

  19. Concept of Operations (ConOps) • Scope/Background • System overview (Context Diagram) • Operational needs • Concept(s) (apps & functions) • User oriented operational descriptions • Operational scenarios 19

  20. System Requirements Source: FHWA https://www.fhwa.dot.gov/cadiv/segb/ 20

  21. System Requirements • Itemized requirements • Verification method  Demonstration, test, analysis, inspection • References for requirement • Traceability to needs 21

  22. Minnesota’s SPaT Deployment Planning Phase Scope of Work • ConOps • System requirements • Data governance plan & tech support • System security plan • Project deployment plan • Design support • Construction inspection support 22

  23. Minnesota’s ConOps (First Draft) 23

  24. Minnesota’s ConOps (First Draft) Need Challenge Need ID Roadway User Needs General Equipped Vehicle Operator/Self‐Equipped Driver Needs In‐Vehicle equipment running UN‐CC‐1.01‐ Signal Phase and Timing . A General Equipped Vehicle applications need intersection v01 Operator Driver/Self‐Equipped Driver needs advance notice data to support those of signal phase and timing changes to safely approach an applications intersection Drivers may be unaware that UN‐CC‐1.02‐ Dynamic Roadway Maintenance Activity Awareness . A they are approaching a short v01 General Equipped Vehicle Operator Driver/Self‐Equipped term mobile work zone or Driver needs to be aware of dynamic maintenance activities snow plow actively engaging in (e.g. snow plowing, pothole filling) in/along the path of operations travel General Vehicle Operator is UN‐CC‐1.03‐ Pedestrian in Crosswalk Awareness. A General Equipped not aware of pedestrian in v01 Vehicle Operator Driver/Self‐Equipped Driver needs crosswalk due to a‐pillar increased awareness of a pedestrian in a crosswalk when occlusion making a movement at a signalized intersection due to occlusion by the vehicle a‐pillar to reduce the likelihood of a pedestrian crash 24

  25. Minnesota’s ConOps (First Draft) User Class Use Cases SPaT Vehicle‐ Snow Plow CV Data Third‐Party Mobile Pedestrian Signal Mgmt Traffic Work Zone Intersection Priority Signal Data Warning Conflict Sharing System Warning General Equipped X X X Vehicle Operator Self‐Equipped Driver X* X* X* X Unequipped Driver X Snow Plow Operator X X Pedestrian X Traveler Information X Provider Work Zone Worker X Traffic Manager X X X X 25

Recommend


More recommend