SPaT Challenge Webinar Series
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 section of webinar window • Questions will be answered at webinar conclusion 2
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
Introduction to the SPaT Webinar Series Blaine Leonard, Utah DOT
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 Challenge Resource Team
SPaT Challenge Tactical Working Group
5
Update on V2I DC Phase 2 • Strategic Initiatives Working Group (Phase 1 TWG 1) Chaired by Greg Larson, Caltrans Meets 4th 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 2nd 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
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
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
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
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
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
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
SPaT Challenge Website
+ New ConOps Document + Webinar Schedule and Recordings 13
Upcoming SPaT Challenge Webinars •
Design Considerations, Part 1
•
Design Considerations, Part 2
•
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
•
April 17, 2018 2:00-3:30pm ET MAP messages and vehicle position correction
MAP Creator Tool Demonstration
•
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
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
Systems Engineering Approach to the SPaT Challenge Ray Starr, Minnesota DOT
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 nonroutine systems 16
Systems Engineering “Vee” Diagram
https://www.fhwa.dot.gov/cadiv/segb/
Source: FHWA 17
Concept of Operations (ConOps)
https://www.fhwa.dot.gov/cadiv/segb/
Source: FHWA 18
Concept of Operations (ConOps) • • • • • •
Scope/Background System overview (Context Diagram) Operational needs Concept(s) (apps & functions) User oriented operational descriptions Operational scenarios
19
System Requirements
https://www.fhwa.dot.gov/cadiv/segb/
Source: FHWA 20
System Requirements • Itemized requirements • Verification method Demonstration, test, analysis, inspection
• References for requirement • Traceability to needs
21
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
Minnesota’s ConOps (First Draft)
23
Minnesota’s ConOps (First Draft) Challenge
Need ID
Need
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 v01 Vehicle Operator Driver/Self‐Equipped Driver needs not aware of pedestrian in increased awareness of a pedestrian in a crosswalk when crosswalk due to a‐pillar making a movement at a signalized intersection due to occlusion occlusion by the vehicle a‐pillar to reduce the likelihood of a pedestrian crash
24
Minnesota’s ConOps (First Draft) User Class SPaT
General Equipped Vehicle Operator Self‐Equipped Driver Unequipped Driver Snow Plow Operator Pedestrian Traveler Information Provider Work Zone Worker Traffic Manager
X
Vehicle‐ Pedestrian Intersection Conflict Warning X
X*
X*
Use Cases Snow Plow CV Data Signal Mgmt Priority
Third‐Party Traffic Signal Data Sharing
Mobile Work Zone Warning System X
X* X
X X X
X X
X
X
X
X X
25
Minnesota’s ConOps (First Draft) Use Vehicle‐Pedestrian Intersection Conflict Warning Case Scenari UC2‐S1: Normal Operating Conditions – Pedestrian in o ID and Signalized Crosswalk Title Improve awareness of pedestrians to general Scenari equipped vehicle operators o Notify and warn general equipped vehicle Objectiv operators when their path of travel is across a e crosswalk with a pedestrian in it The system properly determines there is a pedestrian in the vehicle’s path Operati onal The system properly notifies the General Event(s) Equipped Vehicle Operator of a pedestrian in the path of the vehicle User Role Safely traverse the crosswalk Pedestrian User(s) at the intersection General Equipped Safely navigate through the Vehicle Operator intersection A vehicle is waiting to make a permitted (not protected) left turn at a red light Opposing traffic is queued at the same signalized intersection A pedestrian is waiting to cross the opposing crosswalk, but is traveling against the flow of opposing traffic Initial The pedestrian has performed all required Conditio actions (e.g. pressing the pedestrian crossing ns push button) to receive a walk signal during the next cycle Note: This scenario is generally applicable to any pedestrian movement and general equipped vehicle movement such that the path of the vehicle crosses the path of the pedestrian when the pedestrian has the right‐of‐way.
Post‐ Conditi ons
Scenario Diagram
Traceab ility
Source
Step
Key Action
General
1
Traffic Signal turns green (permitted) for the vehicle and for opposing traffic
2
Simultaneously receives a walk signal and begins to cross the crosswalk to the left of the vehicle
Crosswalk is in the intended path of the vehicle
CC System
3
Issues notification to general equipped vehicle operator that there is a pedestrian in the crosswalk.
As the system properly detects a potential conflict between the vehicle and the pedestrian
General Equipped Vehicle Operator
4
Advances into the intersection and stops, waiting for opposing traffic to clear
General
5
Opposing traffic clears the intersection
Pedestria n
6
Continues to cross and remains in the crosswalk
CC System
7
Continues to issue notification to general See Step 3 vehicle operator that comment there is a pedestrian in the crosswalk.
Pedestria n
Key Actions and Flow of Events
Comments Solid green bulb (no left turn arrow) indicates a permitted left turn
CC System Inputs
CC System Outputs
The pedestrian safely crosses the intersection in the crosswalk The general equipped vehicle operator completes the left turn without compromising the safety of the pedestrian UN‐CC‐1.03‐v01 Pedestrian in Crosswalk Awareness UN‐CC‐4.01‐v01 Pedestrian in Crosswalk Safety Detection (of Pedestrian) Map Input (from Traffic Manager) Position Correction Data (from NTRIP Caster) Raw Traffic Signal Data (from Traffic Signal Controller) General Equipped Vehicle Location/Motion (from GNSS) Pedestrian in Crosswalk Notification (to General Equipped Vehicle Operator) Pedestrian in Crosswalk Warning (to General Equipped Vehicle Operator)
26
Systems Engineering “Vee” Diagram
https://www.fhwa.dot.gov/cadiv/segb/
Source: FHWA 27
SPaT Challenge Model ConOps & Requirements Dean Deeter, Athey Creek Consultants
SPaT Challenge Model ConOps & Requirements Overview Four Things I’d Like to Accomplish Today 1. Introduce the Model ConOps & Requirements Documents 2. Define the term “SPaT Infrastructure System” 3. Describe the Approach to the Documents 4. Share a Few Examples of Details 29
Introduction to the Model Documents • SPaT Challenge Model Concept of Operations and Functional Requirements Two stand-alone but related documents Available online:
https://transportationops.org/spatchallenge/resources
• Developed to help agencies plan a SPaT infrastructure deployment • Written for transportation agencies to adapt to various local site conditions, individual practices, and to address specific needs • Represents initial “model” concepts • These are “working drafts” to serve as resources to you. Not prescriptive in any way 30
Defining “SPaT Infrastructure System” Sources of SPaT Data
Users who will Benefit From SPaT Data
Driver
Traffic Signal Systems
Pedestrians
31
SPaT Enabled V2I Connected Vehicle Systems Users who will Benefit From SPaT Data
Sources of SPaT Data
Driver
Traffic Signal Systems
SPaT Enabled Connected Vehicle Systems Pedestrians
32
Defining “SPaT Infrastructure System” Sources of SPaT Data
SPAT Infrastructure System (the Focus of the ConOps Document)
Users who will Benefit From SPaT Data
Driver
Traffic Signal Systems
New infrastructure to securely communicate SPaT, MAP, and supporing data to Vehicles and Pedestrian devices. Pedestrians
May also receive data from vehicles and pedestrian devices.
33
Defining “SPaT Infrastructure System” Sources of SPaT Data
SPAT Infrastructure System (the Focus of the ConOps Document)
Traffic Signal Systems
New infrastructure to securely communicate SPaT, MAP, and supporing data to Vehicles and Pedestrian devices.
Direct Users of the SpaT Infrastructure System
Users who will Benefit From SPaT Data
SPAT Vehicle System Applications that will be installed on passenger or fleet vehicles to communicate with SPaT Infrastructure Systems to receive data, and use the data to support the drivers’ safety, mobility, and efficiency.
Driver
Pedestrians
May also receive data from vehicles and pedestrian devices.
Personal Information Devices (a User of the SPaT Infrastructure System)
Handheld devices that receive communications from the infrastructure and support pedestrians as they cross intersections
34
SPaT Challenge Model ConOps • Focused on SPaT Infrastructure System • Needs and Operational Concepts written for – Indirect stakeholders: Pedestrians and drivers
Direct stakeholders: SPaT Vehicle System equipped with applications Pedestrian Personal Information Devices (PIDs) Traffic Signal System including system controlling the traffic signals at the intersection Traffic Data System including traffic conditions databases, central signal control systems (CSCS), and Advanced Traffic Management Systems (ATMS) Security Back End including the Security Credentials Management System Traffic Engineering Staff Maintenance Staff 35
SPaT Challenge Model ConOps • V2I applications based on SPaT that are considered in the Model ConOps
36
Section 2 – Current Situation and Needs • Current System Overview • Stakeholders Indirect Users Users Other Stakeholders
• Stakeholders Use of the SPaT Infrastructure System • Stakeholders Needs Challenge Indirect User Stakeholder Needs Driver Needs Vehicles running red lights and entering signalized intersections is a safety concern, with an average of 700 fatalities each year, 90,000 injuries related to an average of 100,000 red light running related crashes.
Need ID
1.1
Need
Drivers need a red light violation warning (RLVW) to help them avoid unintended red light violations.
37
Section 3 – Operational Concept for the SPaT Infrastructure System • How each user will interact with the SPaT Infrastructure System • Users include humans and systems • Written as numbered lines for traceability by the Requirements 3.3
SPaT Vehicle Systems’ Perspective
3.3.1
SPaT Vehicle Systems will receive current signal phase and timing (SPaT Data) from the SPaT Infrastructure System for the approaching intersection. (Need 3.1) 3.3.1.1 For intersections equipped with SPaT Infrastructure Systems, SPaT Vehicle Systems will receive the SPaT Data upstream of the intersection, beginning at a distance that enables the SPaT Vehicle System to perform needed calculations and information display to 38 drivers. (Need 8.3)
Section 4 – Operational Concept for SPaT, MAP, and Traffic Data • Presents details about the use of J2735 SPaT and MAP Message, as well as details about Traffic Controller Data • Our attempt to get as much of the information describing this data exchange into one document
39
Section 5 – Operational Scenario
• Initial Conditions • Sequence of Events
Chronological description of the interactions of the SPaT Infrastructure System with the users 5.2
Sequence of events
Map Message: 1. The SPaT Vehicle System receives the MAP message and validates the security credentials. 2. The SPaT Vehicle System checks the message revision number and determines it has never received this revision of the MAP message (alternate ‐ the SPaT Vehicle System determines it has already received this revision of the MAP message and skips step 3.) 3. The SPaT Vehicle System decodes the MAP message and determines a. Intersection location. b. Ingress and egress lane geometry and location. c. Connections from ingress lanes to egress lanes via specific maneuvers. a. The signal group IDs related to the connections.
40
SPaT Challenge Model Requirements • Contain industry input • Include relevant specifications and standards • Define the minimal requirements to maintain compatibility between broadcast SPaT messages and vehicle on-board units planned by automobile industry • Requirements organization on next slide 41
Group 7: Manage Preemption / Priority
Traffic Signal Controller
Group 1: Manage Interface to SPaT Sources Interface with the Traffic Signal Controller
Central Signal Control System
Interface with the Central Signal Control System
Monitor Preemption & Priority Requests Manage Conflicting Signal Request Messages (SRMs) Request Preemption & Priority Obtain Preemption & Priority Status Assemble Standard Signal Status Messages (SSM)
Traffic Data System
Group 9: Manage Traffic Data System Interface Exchange data with the Traffic Data System
Group 8: Manage Vehicle & PID Data Monitor Basic Safety Messages (BSM), Probe Vehicle Data (PVD) & Personal Safety Messages (PSM) Convert BSM & PSM to Detector Calls
Security Back End
Group 11: Manage Security Back End Interface Configure data exchanges Configure the security back end system
Group 4: Manage Maps Manage a Map database Manage Map Dynamic Features
Assemble SPaT messages that conform to the SAE J2735 standard message format.
Assemble MAP messages that conform to the SAE J2735 standard message format
Assemble SPaT messages that comply with other standardized message formats.
Assemble other standard MAP messages Group 5: Manage Position Correction Obtain Position Correction Data Obtain data for Position Correction messages Assemble SAE J2735 compliant position correction messages Assemble other standard correction messages
Group 12: Provide Support
Group 6: Manage SPaT Vehicle System Interface
SPaT Vehicle System
Broadcast 5.9 GHz DSRC Messages Receive and process 5.9 GHz DSRC Messages Publish Data over alternate communications Mediums Receive Data over alternate communications Mediums
Personal Information Device
Manage Logs Group 10: Manage Security Obtain valid Security Credentials Verify Received Message Credentials
Configure Messages Manage MAP Data Manage GPS Corrections Manage Detection Zones Manage Reports
Notes: Bold text and boxes represents minimum SPaT Functions to support Vehicle based applications
Assemble the content needed for Standard SPaT Messages
Assemble the content needed for MAP Message
Aggregate BSM & PVD Data Assemble Traffic Data Messages
Group 2: Manage SPaT
Apply Security Credentials to broadcasts Manage access to the system network
Manage Alerts Provide Diagnostics Reset the System Configure System
Group 3: Manage User Interface
Traffic Engineer
Include an interface for users to manage the SPaT infrastructure System and its data Include security to limit user access Display information to users
Maintenance Tech
42
Group 7: Manage Preemption / Priority
Traffic Signal Controller
Group 1: Manage Interface to SPaT Sources Interface with the Traffic Signal Controller
Central Signal Control System
Interface with the Central Signal Control System
Monitor Preemption & Priority Requests Manage Conflicting Signal Request Messages (SRMs) Request Preemption & Priority Obtain Preemption & Priority Status Assemble Standard Signal Status Messages (SSM)
Traffic Data System
Group 9: Manage Traffic Data System Interface Exchange data with the Traffic Data System
Group 8: Manage Vehicle & PID Data Monitor Basic Safety Messages (BSM), Probe Vehicle Data (PVD) & Personal Safety Messages (PSM) Convert BSM & PSM to Detector Calls
Security Back End
Group 11: Manage Security Back End Interface Configure data exchanges Configure the security back end system
Group 4: Manage Maps Manage a Map database Manage Map Dynamic Features
Assemble SPaT messages that conform to the SAE J2735 standard message format.
Assemble MAP messages that conform to the SAE J2735 standard message format
Assemble SPaT messages that comply with other standardized message formats.
Assemble other standard MAP messages Group 5: Manage Position Correction Obtain Position Correction Data Obtain data for Position Correction messages Assemble SAE J2735 compliant position correction messages Assemble other standard correction messages
Group 12: Provide Support
Group 6: Manage SPaT Vehicle System Interface
SPaT Vehicle System
Broadcast 5.9 GHz DSRC Messages Receive and process 5.9 GHz DSRC Messages Publish Data over alternate communications Mediums Receive Data over alternate communications Mediums
Personal Information Device
Manage Logs Group 10: Manage Security Obtain valid Security Credentials Verify Received Message Credentials
Configure Messages Manage MAP Data Manage GPS Corrections Manage Detection Zones Manage Reports
Notes: Bold text and boxes represents minimum SPaT Functions to support Vehicle based applications
Assemble the content needed for Standard SPaT Messages
Assemble the content needed for MAP Message
Aggregate BSM & PVD Data Assemble Traffic Data Messages
Group 2: Manage SPaT
Apply Security Credentials to broadcasts Manage access to the system network
Manage Alerts Provide Diagnostics Reset the System Configure System
Group 3: Manage User Interface
Traffic Engineer
Include an interface for users to manage the SPaT infrastructure System and its data Include security to limit user access Display information to users
Maintenance Tech
43
Group 7: Manage Preemption / Priority
Traffic Signal Controller
Group 1: Manage Interface to SPaT Sources Interface with the Traffic Signal Controller
Central Signal Control System
Interface with the Central Signal Control System
Monitor Preemption & Priority Requests Manage Conflicting Signal Request Messages (SRMs) Request Preemption & Priority Obtain Preemption & Priority Status Assemble Standard Signal Status Messages (SSM)
Traffic Data System
Group 9: Manage Traffic Data System Interface Exchange data with the Traffic Data System
Group 8: Manage Vehicle & PID Data Monitor Basic Safety Messages (BSM), Probe Vehicle Data (PVD) & Personal Safety Messages (PSM) Convert BSM & PSM to Detector Calls
Security Back End
Group 11: Manage Security Back End Interface Configure data exchanges Configure the security back end system
Group 4: Manage Maps Manage a Map database Manage Map Dynamic Features
Assemble SPaT messages that conform to the SAE J2735 standard message format.
Assemble MAP messages that conform to the SAE J2735 standard message format
Assemble SPaT messages that comply with other standardized message formats.
Assemble other standard MAP messages Group 5: Manage Position Correction Obtain Position Correction Data Obtain data for Position Correction messages Assemble SAE J2735 compliant position correction messages Assemble other standard correction messages
Group 12: Provide Support
Group 6: Manage SPaT Vehicle System Interface
SPaT Vehicle System
Broadcast 5.9 GHz DSRC Messages Receive and process 5.9 GHz DSRC Messages Publish Data over alternate communications Mediums Receive Data over alternate communications Mediums
Personal Information Device
Manage Logs Group 10: Manage Security Obtain valid Security Credentials Verify Received Message Credentials
Configure Messages Manage MAP Data Manage GPS Corrections Manage Detection Zones Manage Reports
Notes: Bold text and boxes represents minimum SPaT Functions to support Vehicle based applications
Assemble the content needed for Standard SPaT Messages
Assemble the content needed for MAP Message
Aggregate BSM & PVD Data Assemble Traffic Data Messages
Group 2: Manage SPaT
Apply Security Credentials to broadcasts Manage access to the system network
Manage Alerts Provide Diagnostics Reset the System Configure System
Group 3: Manage User Interface
Traffic Engineer
Include an interface for users to manage the SPaT infrastructure System and its data Include security to limit user access Display information to users
Maintenance Tech
44
Group 7: Manage Preemption / Priority
Traffic Signal Controller
Group 1: Manage Interface to SPaT Sources Interface with the Traffic Signal Controller
Central Signal Control System
Interface with the Central Signal Control System
Monitor Preemption & Priority Requests Manage Conflicting Signal Request Messages (SRMs) Request Preemption & Priority Obtain Preemption & Priority Status Assemble Standard Signal Status Messages (SSM)
Traffic Data System
Group 9: Manage Traffic Data System Interface Exchange data with the Traffic Data System
Group 8: Manage Vehicle & PID Data Monitor Basic Safety Messages (BSM), Probe Vehicle Data (PVD) & Personal Safety Messages (PSM) Convert BSM & PSM to Detector Calls
Security Back End
Group 11: Manage Security Back End Interface Configure data exchanges Configure the security back end system
Group 4: Manage Maps Manage a Map database Manage Map Dynamic Features
Assemble SPaT messages that conform to the SAE J2735 standard message format.
Assemble MAP messages that conform to the SAE J2735 standard message format
Assemble SPaT messages that comply with other standardized message formats.
Assemble other standard MAP messages Group 5: Manage Position Correction Obtain Position Correction Data Obtain data for Position Correction messages Assemble SAE J2735 compliant position correction messages Assemble other standard correction messages
Group 12: Provide Support
Group 6: Manage SPaT Vehicle System Interface
SPaT Vehicle System
Broadcast 5.9 GHz DSRC Messages Receive and process 5.9 GHz DSRC Messages Publish Data over alternate communications Mediums Receive Data over alternate communications Mediums
Personal Information Device
Manage Logs Group 10: Manage Security Obtain valid Security Credentials Verify Received Message Credentials
Configure Messages Manage MAP Data Manage GPS Corrections Manage Detection Zones Manage Reports
Notes: Bold text and boxes represents minimum SPaT Functions to support Vehicle based applications
Assemble the content needed for Standard SPaT Messages
Assemble the content needed for MAP Message
Aggregate BSM & PVD Data Assemble Traffic Data Messages
Group 2: Manage SPaT
Apply Security Credentials to broadcasts Manage access to the system network
Manage Alerts Provide Diagnostics Reset the System Configure System
Group 3: Manage User Interface
Traffic Engineer
Include an interface for users to manage the SPaT infrastructure System and its data Include security to limit user access Display information to users
Maintenance Tech
45
Group 7: Manage Preemption / Priority
Traffic Signal Controller
Group 1: Manage Interface to SPaT Sources Interface with the Traffic Signal Controller
Central Signal Control System
Interface with the Central Signal Control System
Monitor Preemption & Priority Requests Manage Conflicting Signal Request Messages (SRMs) Request Preemption & Priority Obtain Preemption & Priority Status Assemble Standard Signal Status Messages (SSM)
Traffic Data System
Group 9: Manage Traffic Data System Interface Exchange data with the Traffic Data System
Group 8: Manage Vehicle & PID Data Monitor Basic Safety Messages (BSM), Probe Vehicle Data (PVD) & Personal Safety Messages (PSM) Convert BSM & PSM to Detector Calls
Security Back End
Group 11: Manage Security Back End Interface Configure data exchanges Configure the security back end system
Group 4: Manage Maps Manage a Map database Manage Map Dynamic Features
Assemble SPaT messages that conform to the SAE J2735 standard message format.
Assemble MAP messages that conform to the SAE J2735 standard message format
Assemble SPaT messages that comply with other standardized message formats.
Assemble other standard MAP messages Group 5: Manage Position Correction Obtain Position Correction Data Obtain data for Position Correction messages Assemble SAE J2735 compliant position correction messages Assemble other standard correction messages
Group 12: Provide Support
Group 6: Manage SPaT Vehicle System Interface
SPaT Vehicle System
Broadcast 5.9 GHz DSRC Messages Receive and process 5.9 GHz DSRC Messages Publish Data over alternate communications Mediums Receive Data over alternate communications Mediums
Personal Information Device
Manage Logs Group 10: Manage Security Obtain valid Security Credentials Verify Received Message Credentials
Configure Messages Manage MAP Data Manage GPS Corrections Manage Detection Zones Manage Reports
Notes: Bold text and boxes represents minimum SPaT Functions to support Vehicle based applications
Assemble the content needed for Standard SPaT Messages
Assemble the content needed for MAP Message
Aggregate BSM & PVD Data Assemble Traffic Data Messages
Group 2: Manage SPaT
Apply Security Credentials to broadcasts Manage access to the system network
Manage Alerts Provide Diagnostics Reset the System Configure System
Group 3: Manage User Interface
Traffic Engineer
Include an interface for users to manage the SPaT infrastructure System and its data Include security to limit user access Display information to users
Maintenance Tech
46
Model Requirements Document • Example of a Requirement, and mapping to the Numbered Operational Concept Group 2: Manage SPaT Requirements describing the functions of the SPaT Infrastructure to assemble the SPaT data into standard SPaT messages for broadcast. 2.1
The SPaT Infrastructure System shall assemble the content needed for standard SPaT messages.
2.1.1
The SPaT Infrastructure System shall process the message containing SPaT data obtained from the Traffic Signal System and generate a SPaT message.
Minimum; RLVW
3.3.1.3
47
SPaT Challenge Model Requirements Requirements classified as: • Minimum: necessary to achieve minimum SPaT broadcast functionality to support Red Light Violation Warning (RLVW) • Optional: alternate approach to achieve minimum SPaT functionality e.g. a different message format or communication mechanism
• Optional – minimum for application: necessary if additional functionality is desired; not needed for minimum functionality e.g. priority/preemption and data collection from vehicles
• Optional – recommended: improves system manageability, but not needed for minimum functionality e.g. reporting, log, and user management tools 48
Verifying and Validating SPaT Deployments SPaT Challenge Verification Document: https://transportationops.org/content/spat-challengeverification-document
• Developed by the Crash Avoidance Metrics Partnership (CAMP) • Intent is to ensure: Deployments are compatible and meet minimum requirements for on-board applications released by automobile manufacturers Compatibility with future Red Light Violation Warning (RLVW) applications
• More on this topic during Webinar #5 49
Costs, Procurement, and Corridor Selection Blaine Leonard, Utah DOT
Corridor Selection • Select a Corridor / Area Infrastructure Compatibility Signal Controllers Backhaul and Central Control of Intersections Number of signals
Concept of Operations Consider local conditions and needs Identify partners and partners Future V2I Applications (Long-term Strategy)
Get on the NOCOE SPaT Challenge Map 51
Corridor Selection / Procurement • Define Operations / Requirements System Requirements Messages Being Sent – SPaT and MAP Messages Being Received – BSM Other Messages (Application Dependent) • SRM, SSM, TIM, etc
Performance Requirements Security (SCMS)
52
Procurement • Procurement Approaches Government Procurement Testing / Small Quantity Full Procurement
Partner / University Consultant Faster Ownership / Maintenance
53
Procurement • Define Hardware Requirements RSU 4.1 Specification Outside Certification (pending) Specific Requirements Messages Performance Security
Software Development Kit (SDK) Needed for software development / modification
OBUs (optional) Number of radios (one vs two) 54
Procurement • Other Hardware Cabling Mounting Processor (optional)
55
Costs • Disclaimer . . . Every deployment is different – lots of variables Learning Curve – Experience of Team Consultant vs In-house Efforts (or Combination) Testing Applications Beyond SPaT Procurement Variations Installation Parameters
We would love your input on cost experience! 56
Costs • Hardware RSU $1500 to $3200
Mounting Brackets, Cables, Power Supply $200 to $600
OBU $900 to $1500
57
Costs • Engineering Design / Testing $1000 to $8500
Installation / Integration $2000 to $11,000 Location of DSRC Installation Lane Closures / Night Work
Create MAP Data (future webinar) $400 to $1500 Use of Tool Local Mapping 58
Webinar Wrap-Up and Q&A
Next SPaT Challenge Webinar • Design Considerations, Part 1 March 20, 2018 2:00pm ET Minimum content for SPaT broadcasts to be verified/validated Signal controller interface and creation of SPaT messages Examples of designs for assembling SPaT messages DSRC licensing • Registration: https://transportationops.org/event/webinar-2spat-challenge-design-considerations-part-1 60
Q&A Submit questions and comments in chat or Q&A section of webinar window
Upcoming SPaT Challenge Webinars Design Considerations, Part 1 Design Considerations, Part 2 MAP Creator Tool Demonstration Design Considerations, Part 3 Deployment & Validation
March 20, 2018 2:00-3:30pm ET April 17, 2018 2:00-3:30pm ET April 24, 2018 1:00-2:30pm ET May 15, 2018 2:00-3:30pm ET June 12, 2018 2:00-3:30pm ET
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 section of webinar window • Questions will be answered at webinar conclusion 2
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
Introduction to the SPaT Webinar Series Blaine Leonard, Utah DOT
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 Challenge Resource Team
SPaT Challenge Tactical Working Group
5
Update on V2I DC Phase 2 • Strategic Initiatives Working Group (Phase 1 TWG 1) Chaired by Greg Larson, Caltrans Meets 4th 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 2nd 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
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
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
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
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
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
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
SPaT Challenge Website
+ New ConOps Document + Webinar Schedule and Recordings 13
Upcoming SPaT Challenge Webinars •
Design Considerations, Part 1
•
Design Considerations, Part 2
•
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
•
April 17, 2018 2:00-3:30pm ET MAP messages and vehicle position correction
MAP Creator Tool Demonstration
•
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
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
Systems Engineering Approach to the SPaT Challenge Ray Starr, Minnesota DOT
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 nonroutine systems 16
Systems Engineering “Vee” Diagram
https://www.fhwa.dot.gov/cadiv/segb/
Source: FHWA 17
Concept of Operations (ConOps)
https://www.fhwa.dot.gov/cadiv/segb/
Source: FHWA 18
Concept of Operations (ConOps) • • • • • •
Scope/Background System overview (Context Diagram) Operational needs Concept(s) (apps & functions) User oriented operational descriptions Operational scenarios
19
System Requirements
https://www.fhwa.dot.gov/cadiv/segb/
Source: FHWA 20
System Requirements • Itemized requirements • Verification method Demonstration, test, analysis, inspection
• References for requirement • Traceability to needs
21
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
Minnesota’s ConOps (First Draft)
23
Minnesota’s ConOps (First Draft) Challenge
Need ID
Need
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 v01 Vehicle Operator Driver/Self‐Equipped Driver needs not aware of pedestrian in increased awareness of a pedestrian in a crosswalk when crosswalk due to a‐pillar making a movement at a signalized intersection due to occlusion occlusion by the vehicle a‐pillar to reduce the likelihood of a pedestrian crash
24
Minnesota’s ConOps (First Draft) User Class SPaT
General Equipped Vehicle Operator Self‐Equipped Driver Unequipped Driver Snow Plow Operator Pedestrian Traveler Information Provider Work Zone Worker Traffic Manager
X
Vehicle‐ Pedestrian Intersection Conflict Warning X
X*
X*
Use Cases Snow Plow CV Data Signal Mgmt Priority
Third‐Party Traffic Signal Data Sharing
Mobile Work Zone Warning System X
X* X
X X X
X X
X
X
X
X X
25
Minnesota’s ConOps (First Draft) Use Vehicle‐Pedestrian Intersection Conflict Warning Case Scenari UC2‐S1: Normal Operating Conditions – Pedestrian in o ID and Signalized Crosswalk Title Improve awareness of pedestrians to general Scenari equipped vehicle operators o Notify and warn general equipped vehicle Objectiv operators when their path of travel is across a e crosswalk with a pedestrian in it The system properly determines there is a pedestrian in the vehicle’s path Operati onal The system properly notifies the General Event(s) Equipped Vehicle Operator of a pedestrian in the path of the vehicle User Role Safely traverse the crosswalk Pedestrian User(s) at the intersection General Equipped Safely navigate through the Vehicle Operator intersection A vehicle is waiting to make a permitted (not protected) left turn at a red light Opposing traffic is queued at the same signalized intersection A pedestrian is waiting to cross the opposing crosswalk, but is traveling against the flow of opposing traffic Initial The pedestrian has performed all required Conditio actions (e.g. pressing the pedestrian crossing ns push button) to receive a walk signal during the next cycle Note: This scenario is generally applicable to any pedestrian movement and general equipped vehicle movement such that the path of the vehicle crosses the path of the pedestrian when the pedestrian has the right‐of‐way.
Post‐ Conditi ons
Scenario Diagram
Traceab ility
Source
Step
Key Action
General
1
Traffic Signal turns green (permitted) for the vehicle and for opposing traffic
2
Simultaneously receives a walk signal and begins to cross the crosswalk to the left of the vehicle
Crosswalk is in the intended path of the vehicle
CC System
3
Issues notification to general equipped vehicle operator that there is a pedestrian in the crosswalk.
As the system properly detects a potential conflict between the vehicle and the pedestrian
General Equipped Vehicle Operator
4
Advances into the intersection and stops, waiting for opposing traffic to clear
General
5
Opposing traffic clears the intersection
Pedestria n
6
Continues to cross and remains in the crosswalk
CC System
7
Continues to issue notification to general See Step 3 vehicle operator that comment there is a pedestrian in the crosswalk.
Pedestria n
Key Actions and Flow of Events
Comments Solid green bulb (no left turn arrow) indicates a permitted left turn
CC System Inputs
CC System Outputs
The pedestrian safely crosses the intersection in the crosswalk The general equipped vehicle operator completes the left turn without compromising the safety of the pedestrian UN‐CC‐1.03‐v01 Pedestrian in Crosswalk Awareness UN‐CC‐4.01‐v01 Pedestrian in Crosswalk Safety Detection (of Pedestrian) Map Input (from Traffic Manager) Position Correction Data (from NTRIP Caster) Raw Traffic Signal Data (from Traffic Signal Controller) General Equipped Vehicle Location/Motion (from GNSS) Pedestrian in Crosswalk Notification (to General Equipped Vehicle Operator) Pedestrian in Crosswalk Warning (to General Equipped Vehicle Operator)
26
Systems Engineering “Vee” Diagram
https://www.fhwa.dot.gov/cadiv/segb/
Source: FHWA 27
SPaT Challenge Model ConOps & Requirements Dean Deeter, Athey Creek Consultants
SPaT Challenge Model ConOps & Requirements Overview Four Things I’d Like to Accomplish Today 1. Introduce the Model ConOps & Requirements Documents 2. Define the term “SPaT Infrastructure System” 3. Describe the Approach to the Documents 4. Share a Few Examples of Details 29
Introduction to the Model Documents • SPaT Challenge Model Concept of Operations and Functional Requirements Two stand-alone but related documents Available online:
https://transportationops.org/spatchallenge/resources
• Developed to help agencies plan a SPaT infrastructure deployment • Written for transportation agencies to adapt to various local site conditions, individual practices, and to address specific needs • Represents initial “model” concepts • These are “working drafts” to serve as resources to you. Not prescriptive in any way 30
Defining “SPaT Infrastructure System” Sources of SPaT Data
Users who will Benefit From SPaT Data
Driver
Traffic Signal Systems
Pedestrians
31
SPaT Enabled V2I Connected Vehicle Systems Users who will Benefit From SPaT Data
Sources of SPaT Data
Driver
Traffic Signal Systems
SPaT Enabled Connected Vehicle Systems Pedestrians
32
Defining “SPaT Infrastructure System” Sources of SPaT Data
SPAT Infrastructure System (the Focus of the ConOps Document)
Users who will Benefit From SPaT Data
Driver
Traffic Signal Systems
New infrastructure to securely communicate SPaT, MAP, and supporing data to Vehicles and Pedestrian devices. Pedestrians
May also receive data from vehicles and pedestrian devices.
33
Defining “SPaT Infrastructure System” Sources of SPaT Data
SPAT Infrastructure System (the Focus of the ConOps Document)
Traffic Signal Systems
New infrastructure to securely communicate SPaT, MAP, and supporing data to Vehicles and Pedestrian devices.
Direct Users of the SpaT Infrastructure System
Users who will Benefit From SPaT Data
SPAT Vehicle System Applications that will be installed on passenger or fleet vehicles to communicate with SPaT Infrastructure Systems to receive data, and use the data to support the drivers’ safety, mobility, and efficiency.
Driver
Pedestrians
May also receive data from vehicles and pedestrian devices.
Personal Information Devices (a User of the SPaT Infrastructure System)
Handheld devices that receive communications from the infrastructure and support pedestrians as they cross intersections
34
SPaT Challenge Model ConOps • Focused on SPaT Infrastructure System • Needs and Operational Concepts written for – Indirect stakeholders: Pedestrians and drivers
Direct stakeholders: SPaT Vehicle System equipped with applications Pedestrian Personal Information Devices (PIDs) Traffic Signal System including system controlling the traffic signals at the intersection Traffic Data System including traffic conditions databases, central signal control systems (CSCS), and Advanced Traffic Management Systems (ATMS) Security Back End including the Security Credentials Management System Traffic Engineering Staff Maintenance Staff 35
SPaT Challenge Model ConOps • V2I applications based on SPaT that are considered in the Model ConOps
36
Section 2 – Current Situation and Needs • Current System Overview • Stakeholders Indirect Users Users Other Stakeholders
• Stakeholders Use of the SPaT Infrastructure System • Stakeholders Needs Challenge Indirect User Stakeholder Needs Driver Needs Vehicles running red lights and entering signalized intersections is a safety concern, with an average of 700 fatalities each year, 90,000 injuries related to an average of 100,000 red light running related crashes.
Need ID
1.1
Need
Drivers need a red light violation warning (RLVW) to help them avoid unintended red light violations.
37
Section 3 – Operational Concept for the SPaT Infrastructure System • How each user will interact with the SPaT Infrastructure System • Users include humans and systems • Written as numbered lines for traceability by the Requirements 3.3
SPaT Vehicle Systems’ Perspective
3.3.1
SPaT Vehicle Systems will receive current signal phase and timing (SPaT Data) from the SPaT Infrastructure System for the approaching intersection. (Need 3.1) 3.3.1.1 For intersections equipped with SPaT Infrastructure Systems, SPaT Vehicle Systems will receive the SPaT Data upstream of the intersection, beginning at a distance that enables the SPaT Vehicle System to perform needed calculations and information display to 38 drivers. (Need 8.3)
Section 4 – Operational Concept for SPaT, MAP, and Traffic Data • Presents details about the use of J2735 SPaT and MAP Message, as well as details about Traffic Controller Data • Our attempt to get as much of the information describing this data exchange into one document
39
Section 5 – Operational Scenario
• Initial Conditions • Sequence of Events
Chronological description of the interactions of the SPaT Infrastructure System with the users 5.2
Sequence of events
Map Message: 1. The SPaT Vehicle System receives the MAP message and validates the security credentials. 2. The SPaT Vehicle System checks the message revision number and determines it has never received this revision of the MAP message (alternate ‐ the SPaT Vehicle System determines it has already received this revision of the MAP message and skips step 3.) 3. The SPaT Vehicle System decodes the MAP message and determines a. Intersection location. b. Ingress and egress lane geometry and location. c. Connections from ingress lanes to egress lanes via specific maneuvers. a. The signal group IDs related to the connections.
40
SPaT Challenge Model Requirements • Contain industry input • Include relevant specifications and standards • Define the minimal requirements to maintain compatibility between broadcast SPaT messages and vehicle on-board units planned by automobile industry • Requirements organization on next slide 41
Group 7: Manage Preemption / Priority
Traffic Signal Controller
Group 1: Manage Interface to SPaT Sources Interface with the Traffic Signal Controller
Central Signal Control System
Interface with the Central Signal Control System
Monitor Preemption & Priority Requests Manage Conflicting Signal Request Messages (SRMs) Request Preemption & Priority Obtain Preemption & Priority Status Assemble Standard Signal Status Messages (SSM)
Traffic Data System
Group 9: Manage Traffic Data System Interface Exchange data with the Traffic Data System
Group 8: Manage Vehicle & PID Data Monitor Basic Safety Messages (BSM), Probe Vehicle Data (PVD) & Personal Safety Messages (PSM) Convert BSM & PSM to Detector Calls
Security Back End
Group 11: Manage Security Back End Interface Configure data exchanges Configure the security back end system
Group 4: Manage Maps Manage a Map database Manage Map Dynamic Features
Assemble SPaT messages that conform to the SAE J2735 standard message format.
Assemble MAP messages that conform to the SAE J2735 standard message format
Assemble SPaT messages that comply with other standardized message formats.
Assemble other standard MAP messages Group 5: Manage Position Correction Obtain Position Correction Data Obtain data for Position Correction messages Assemble SAE J2735 compliant position correction messages Assemble other standard correction messages
Group 12: Provide Support
Group 6: Manage SPaT Vehicle System Interface
SPaT Vehicle System
Broadcast 5.9 GHz DSRC Messages Receive and process 5.9 GHz DSRC Messages Publish Data over alternate communications Mediums Receive Data over alternate communications Mediums
Personal Information Device
Manage Logs Group 10: Manage Security Obtain valid Security Credentials Verify Received Message Credentials
Configure Messages Manage MAP Data Manage GPS Corrections Manage Detection Zones Manage Reports
Notes: Bold text and boxes represents minimum SPaT Functions to support Vehicle based applications
Assemble the content needed for Standard SPaT Messages
Assemble the content needed for MAP Message
Aggregate BSM & PVD Data Assemble Traffic Data Messages
Group 2: Manage SPaT
Apply Security Credentials to broadcasts Manage access to the system network
Manage Alerts Provide Diagnostics Reset the System Configure System
Group 3: Manage User Interface
Traffic Engineer
Include an interface for users to manage the SPaT infrastructure System and its data Include security to limit user access Display information to users
Maintenance Tech
42
Group 7: Manage Preemption / Priority
Traffic Signal Controller
Group 1: Manage Interface to SPaT Sources Interface with the Traffic Signal Controller
Central Signal Control System
Interface with the Central Signal Control System
Monitor Preemption & Priority Requests Manage Conflicting Signal Request Messages (SRMs) Request Preemption & Priority Obtain Preemption & Priority Status Assemble Standard Signal Status Messages (SSM)
Traffic Data System
Group 9: Manage Traffic Data System Interface Exchange data with the Traffic Data System
Group 8: Manage Vehicle & PID Data Monitor Basic Safety Messages (BSM), Probe Vehicle Data (PVD) & Personal Safety Messages (PSM) Convert BSM & PSM to Detector Calls
Security Back End
Group 11: Manage Security Back End Interface Configure data exchanges Configure the security back end system
Group 4: Manage Maps Manage a Map database Manage Map Dynamic Features
Assemble SPaT messages that conform to the SAE J2735 standard message format.
Assemble MAP messages that conform to the SAE J2735 standard message format
Assemble SPaT messages that comply with other standardized message formats.
Assemble other standard MAP messages Group 5: Manage Position Correction Obtain Position Correction Data Obtain data for Position Correction messages Assemble SAE J2735 compliant position correction messages Assemble other standard correction messages
Group 12: Provide Support
Group 6: Manage SPaT Vehicle System Interface
SPaT Vehicle System
Broadcast 5.9 GHz DSRC Messages Receive and process 5.9 GHz DSRC Messages Publish Data over alternate communications Mediums Receive Data over alternate communications Mediums
Personal Information Device
Manage Logs Group 10: Manage Security Obtain valid Security Credentials Verify Received Message Credentials
Configure Messages Manage MAP Data Manage GPS Corrections Manage Detection Zones Manage Reports
Notes: Bold text and boxes represents minimum SPaT Functions to support Vehicle based applications
Assemble the content needed for Standard SPaT Messages
Assemble the content needed for MAP Message
Aggregate BSM & PVD Data Assemble Traffic Data Messages
Group 2: Manage SPaT
Apply Security Credentials to broadcasts Manage access to the system network
Manage Alerts Provide Diagnostics Reset the System Configure System
Group 3: Manage User Interface
Traffic Engineer
Include an interface for users to manage the SPaT infrastructure System and its data Include security to limit user access Display information to users
Maintenance Tech
43
Group 7: Manage Preemption / Priority
Traffic Signal Controller
Group 1: Manage Interface to SPaT Sources Interface with the Traffic Signal Controller
Central Signal Control System
Interface with the Central Signal Control System
Monitor Preemption & Priority Requests Manage Conflicting Signal Request Messages (SRMs) Request Preemption & Priority Obtain Preemption & Priority Status Assemble Standard Signal Status Messages (SSM)
Traffic Data System
Group 9: Manage Traffic Data System Interface Exchange data with the Traffic Data System
Group 8: Manage Vehicle & PID Data Monitor Basic Safety Messages (BSM), Probe Vehicle Data (PVD) & Personal Safety Messages (PSM) Convert BSM & PSM to Detector Calls
Security Back End
Group 11: Manage Security Back End Interface Configure data exchanges Configure the security back end system
Group 4: Manage Maps Manage a Map database Manage Map Dynamic Features
Assemble SPaT messages that conform to the SAE J2735 standard message format.
Assemble MAP messages that conform to the SAE J2735 standard message format
Assemble SPaT messages that comply with other standardized message formats.
Assemble other standard MAP messages Group 5: Manage Position Correction Obtain Position Correction Data Obtain data for Position Correction messages Assemble SAE J2735 compliant position correction messages Assemble other standard correction messages
Group 12: Provide Support
Group 6: Manage SPaT Vehicle System Interface
SPaT Vehicle System
Broadcast 5.9 GHz DSRC Messages Receive and process 5.9 GHz DSRC Messages Publish Data over alternate communications Mediums Receive Data over alternate communications Mediums
Personal Information Device
Manage Logs Group 10: Manage Security Obtain valid Security Credentials Verify Received Message Credentials
Configure Messages Manage MAP Data Manage GPS Corrections Manage Detection Zones Manage Reports
Notes: Bold text and boxes represents minimum SPaT Functions to support Vehicle based applications
Assemble the content needed for Standard SPaT Messages
Assemble the content needed for MAP Message
Aggregate BSM & PVD Data Assemble Traffic Data Messages
Group 2: Manage SPaT
Apply Security Credentials to broadcasts Manage access to the system network
Manage Alerts Provide Diagnostics Reset the System Configure System
Group 3: Manage User Interface
Traffic Engineer
Include an interface for users to manage the SPaT infrastructure System and its data Include security to limit user access Display information to users
Maintenance Tech
44
Group 7: Manage Preemption / Priority
Traffic Signal Controller
Group 1: Manage Interface to SPaT Sources Interface with the Traffic Signal Controller
Central Signal Control System
Interface with the Central Signal Control System
Monitor Preemption & Priority Requests Manage Conflicting Signal Request Messages (SRMs) Request Preemption & Priority Obtain Preemption & Priority Status Assemble Standard Signal Status Messages (SSM)
Traffic Data System
Group 9: Manage Traffic Data System Interface Exchange data with the Traffic Data System
Group 8: Manage Vehicle & PID Data Monitor Basic Safety Messages (BSM), Probe Vehicle Data (PVD) & Personal Safety Messages (PSM) Convert BSM & PSM to Detector Calls
Security Back End
Group 11: Manage Security Back End Interface Configure data exchanges Configure the security back end system
Group 4: Manage Maps Manage a Map database Manage Map Dynamic Features
Assemble SPaT messages that conform to the SAE J2735 standard message format.
Assemble MAP messages that conform to the SAE J2735 standard message format
Assemble SPaT messages that comply with other standardized message formats.
Assemble other standard MAP messages Group 5: Manage Position Correction Obtain Position Correction Data Obtain data for Position Correction messages Assemble SAE J2735 compliant position correction messages Assemble other standard correction messages
Group 12: Provide Support
Group 6: Manage SPaT Vehicle System Interface
SPaT Vehicle System
Broadcast 5.9 GHz DSRC Messages Receive and process 5.9 GHz DSRC Messages Publish Data over alternate communications Mediums Receive Data over alternate communications Mediums
Personal Information Device
Manage Logs Group 10: Manage Security Obtain valid Security Credentials Verify Received Message Credentials
Configure Messages Manage MAP Data Manage GPS Corrections Manage Detection Zones Manage Reports
Notes: Bold text and boxes represents minimum SPaT Functions to support Vehicle based applications
Assemble the content needed for Standard SPaT Messages
Assemble the content needed for MAP Message
Aggregate BSM & PVD Data Assemble Traffic Data Messages
Group 2: Manage SPaT
Apply Security Credentials to broadcasts Manage access to the system network
Manage Alerts Provide Diagnostics Reset the System Configure System
Group 3: Manage User Interface
Traffic Engineer
Include an interface for users to manage the SPaT infrastructure System and its data Include security to limit user access Display information to users
Maintenance Tech
45
Group 7: Manage Preemption / Priority
Traffic Signal Controller
Group 1: Manage Interface to SPaT Sources Interface with the Traffic Signal Controller
Central Signal Control System
Interface with the Central Signal Control System
Monitor Preemption & Priority Requests Manage Conflicting Signal Request Messages (SRMs) Request Preemption & Priority Obtain Preemption & Priority Status Assemble Standard Signal Status Messages (SSM)
Traffic Data System
Group 9: Manage Traffic Data System Interface Exchange data with the Traffic Data System
Group 8: Manage Vehicle & PID Data Monitor Basic Safety Messages (BSM), Probe Vehicle Data (PVD) & Personal Safety Messages (PSM) Convert BSM & PSM to Detector Calls
Security Back End
Group 11: Manage Security Back End Interface Configure data exchanges Configure the security back end system
Group 4: Manage Maps Manage a Map database Manage Map Dynamic Features
Assemble SPaT messages that conform to the SAE J2735 standard message format.
Assemble MAP messages that conform to the SAE J2735 standard message format
Assemble SPaT messages that comply with other standardized message formats.
Assemble other standard MAP messages Group 5: Manage Position Correction Obtain Position Correction Data Obtain data for Position Correction messages Assemble SAE J2735 compliant position correction messages Assemble other standard correction messages
Group 12: Provide Support
Group 6: Manage SPaT Vehicle System Interface
SPaT Vehicle System
Broadcast 5.9 GHz DSRC Messages Receive and process 5.9 GHz DSRC Messages Publish Data over alternate communications Mediums Receive Data over alternate communications Mediums
Personal Information Device
Manage Logs Group 10: Manage Security Obtain valid Security Credentials Verify Received Message Credentials
Configure Messages Manage MAP Data Manage GPS Corrections Manage Detection Zones Manage Reports
Notes: Bold text and boxes represents minimum SPaT Functions to support Vehicle based applications
Assemble the content needed for Standard SPaT Messages
Assemble the content needed for MAP Message
Aggregate BSM & PVD Data Assemble Traffic Data Messages
Group 2: Manage SPaT
Apply Security Credentials to broadcasts Manage access to the system network
Manage Alerts Provide Diagnostics Reset the System Configure System
Group 3: Manage User Interface
Traffic Engineer
Include an interface for users to manage the SPaT infrastructure System and its data Include security to limit user access Display information to users
Maintenance Tech
46
Model Requirements Document • Example of a Requirement, and mapping to the Numbered Operational Concept Group 2: Manage SPaT Requirements describing the functions of the SPaT Infrastructure to assemble the SPaT data into standard SPaT messages for broadcast. 2.1
The SPaT Infrastructure System shall assemble the content needed for standard SPaT messages.
2.1.1
The SPaT Infrastructure System shall process the message containing SPaT data obtained from the Traffic Signal System and generate a SPaT message.
Minimum; RLVW
3.3.1.3
47
SPaT Challenge Model Requirements Requirements classified as: • Minimum: necessary to achieve minimum SPaT broadcast functionality to support Red Light Violation Warning (RLVW) • Optional: alternate approach to achieve minimum SPaT functionality e.g. a different message format or communication mechanism
• Optional – minimum for application: necessary if additional functionality is desired; not needed for minimum functionality e.g. priority/preemption and data collection from vehicles
• Optional – recommended: improves system manageability, but not needed for minimum functionality e.g. reporting, log, and user management tools 48
Verifying and Validating SPaT Deployments SPaT Challenge Verification Document: https://transportationops.org/content/spat-challengeverification-document
• Developed by the Crash Avoidance Metrics Partnership (CAMP) • Intent is to ensure: Deployments are compatible and meet minimum requirements for on-board applications released by automobile manufacturers Compatibility with future Red Light Violation Warning (RLVW) applications
• More on this topic during Webinar #5 49
Costs, Procurement, and Corridor Selection Blaine Leonard, Utah DOT
Corridor Selection • Select a Corridor / Area Infrastructure Compatibility Signal Controllers Backhaul and Central Control of Intersections Number of signals
Concept of Operations Consider local conditions and needs Identify partners and partners Future V2I Applications (Long-term Strategy)
Get on the NOCOE SPaT Challenge Map 51
Corridor Selection / Procurement • Define Operations / Requirements System Requirements Messages Being Sent – SPaT and MAP Messages Being Received – BSM Other Messages (Application Dependent) • SRM, SSM, TIM, etc
Performance Requirements Security (SCMS)
52
Procurement • Procurement Approaches Government Procurement Testing / Small Quantity Full Procurement
Partner / University Consultant Faster Ownership / Maintenance
53
Procurement • Define Hardware Requirements RSU 4.1 Specification Outside Certification (pending) Specific Requirements Messages Performance Security
Software Development Kit (SDK) Needed for software development / modification
OBUs (optional) Number of radios (one vs two) 54
Procurement • Other Hardware Cabling Mounting Processor (optional)
55
Costs • Disclaimer . . . Every deployment is different – lots of variables Learning Curve – Experience of Team Consultant vs In-house Efforts (or Combination) Testing Applications Beyond SPaT Procurement Variations Installation Parameters
We would love your input on cost experience! 56
Costs • Hardware RSU $1500 to $3200
Mounting Brackets, Cables, Power Supply $200 to $600
OBU $900 to $1500
57
Costs • Engineering Design / Testing $1000 to $8500
Installation / Integration $2000 to $11,000 Location of DSRC Installation Lane Closures / Night Work
Create MAP Data (future webinar) $400 to $1500 Use of Tool Local Mapping 58
Webinar Wrap-Up and Q&A
Next SPaT Challenge Webinar • Design Considerations, Part 1 March 20, 2018 2:00pm ET Minimum content for SPaT broadcasts to be verified/validated Signal controller interface and creation of SPaT messages Examples of designs for assembling SPaT messages DSRC licensing • Registration: https://transportationops.org/event/webinar-2spat-challenge-design-considerations-part-1 60
Q&A Submit questions and comments in chat or Q&A section of webinar window
Upcoming SPaT Challenge Webinars Design Considerations, Part 1 Design Considerations, Part 2 MAP Creator Tool Demonstration Design Considerations, Part 3 Deployment & Validation
March 20, 2018 2:00-3:30pm ET April 17, 2018 2:00-3:30pm ET April 24, 2018 1:00-2:30pm ET May 15, 2018 2:00-3:30pm ET June 12, 2018 2:00-3:30pm ET
