Upload
others
View
2
Download
0
Embed Size (px)
Citation preview
www.incose.org/symp2017
Operational Concept Framework to support government policy & regulation on Connected and Automated Vehicles
Richard Fullalove, CPEng, MSc(Eng) Manager, Systems Engineering Process
Asset Standards Authority, Transport for NSW
Key topics
www.incose.org/symp2017 2
• Why a CAV OpsCon Framework? • Levels of automation • Operational context • Operational outcomes • Operational use cases • Operational migration • Operational modes • Operational interfaces • Operational actors • Operational zoning • Operational scenarios • Operational risks • Conclusion
Why a CAV OpsCon Framework?
www.incose.org/symp2017 3
• Tells "day-in-the-life" story of how CAVs might operate • Identifies operations and support assets and resources • Valid reference point throughout the system lifetime • Living document - regularly reviewed and updated • Informs development of road policy / regulations • Facilitates controlled introduction of CAVs onto the road • Identifies need to re-configure existing road infrastructure • Informs the “Need” and “Plan” phases of asset lifecycle
CAV Levels of Automation
www.incose.org/symp2017 4
• L0 (No Automation): Automated system has no vehicle control, but may issue warnings.
• L1 (Driver Assistance): Driver must be ready to take control at any time. • L2 (Partial Automation): The driver is obliged to detect objects and events
and respond if the automated system fails to respond properly. • L3 (Conditional Automation): Within known, limited environments (such as
freeways), the driver can safely turn their attention away from driving tasks. • L4 (High Automation): The automated system can control the vehicle in all
but a few environments such as severe weather. • L5 (Full Automation): Other than setting the destination and starting the
system, no human intervention is required in all driving modes
SAE International brochure, "Automated driving - Levels of driving automation are defined in new SAE International Standard J3016"
CAV Operational Context
www.incose.org/symp2017 5
• Mass transport system (intercity, metro, light rail, bus, ferry) • “Smart City/Precinct” initiatives • The “Internet of Things” (IoT) • “Big Data” initiatives • Co-operative Intelligent Transport Systems (C-ITS) • Governance & Regulatory Frameworks
•Risk/Safety Assurance Framework •Transport Regulatory Framework •Road Infrastructure Investment Framework
CAV Operational Outcomes
www.incose.org/symp2017 6
Benefits: • Reduced road congestion • Reduced road accidents (safety) • Reduced single-user vehicle traffic • Increased human productivity • Improved equitable mobility access • …and more… Dis-benefits: • Increasing automation replacing human jobs (taxis, truckers) • Unexpected events that software (AI) cannot interpret • …and more?
CAV Operational Use Cases
www.incose.org/symp2017 7
• Privately owned P2P • Mobility-as-a-Service (MaaS) P2P • Bus Mass Transit • Human Mobility-impaired • Commercial/Freight • Road Maintenance • …and others
CAV Operational Migration
www.incose.org/symp2017 8
Possible migration timeline: • Current situation: Levels 0/1/2 prevalent (2017) • Interim future situation 1: Levels 1/2/3 prevalent (2025) • Interim future situation 2: Levels 2/3/4 prevalent (2035) • Final future situation: Level 5 prevalent (>2050)
Note: Tesla Autopilot currently considered Level 2
CAV Operational Modes
www.incose.org/symp2017 9
• Normal mode (all functions and capabilities available) • Degraded mode (degradation or loss of one function) • Emergency mode (loss of multiple functions and capability) • Maintenance mode
Normal Mode Degraded Mode Emergency Mode
CAV Operational Interfaces
www.incose.org/symp2017 10
CAV
CAV Maintenance Facility
Vehicle LicensingAuthority
Vehicle Insurer
CAV Vehicle Supplier (software update)
Map Data Agency(Google, Nearmap)
MaaS P2P CAVService Provider
(Uber, Taxis)
Other CAVs
Electronic Road Sign
Intelligent Transport Systems
(SCATS, C-ITS)
CAV Owner/Operator (1st Party)
CAV Owner/Operator (1st Party) CAV
Passengers (2nd Party)
CAV Passengers (2nd Party) Vulnerable
Road Users (3nd Party)
VulnerableRoad Users (3nd Party)
Non-CAVs
EmergencyServices
(Police, Ambulance) Road Authority(Operator/Maintainer)
Mobile DataDevice
Mobile DataDevice
EmergencyServices
Staff
EmergencyServices
Staff
HumanDriversHumanDrivers
HumanUsers/
Operators
HumanUsers/
Operators
CAV Operational Actors Actors include the user, as well as other entities that will need to interact with the CAV over an operational interface.
• CAV owner/operator (the direct user) • Vulnerable road users (e.g. pedestrians, cyclists) • Roadside ITS infrastructure • Emergency services (e.g. police, ambulance, vehicle recovery) • Road operator/maintainer (public & private/toll) • Vehicle service centre (e.g. “over the air” diagnostic data download) • Vehicle supplier (e.g. “over the air” software updates)
www.incose.org/symp2017 11
CAV Operational Zoning Physical zones where a CAV may be permitted to operate at a certain level of automation Until CAVs are ubiquitous, zoning may be based on: • Segregated geographic areas (e.g. Level 4/5 on campus areas only) • Separate lanes (e.g. CAV use of existing bus/taxi lanes) • Separate road types (e.g. >= Level 2 automation on motorways only)
May need to plan for new or altered zones to accommodate CAVs at specific levels of automation: • Physical barriers • Lane markings (e.g. “CAV only” or “Level 2 only”) • Signage (e.g. “Select Level 3”) • Virtual (electronic) barriers
www.incose.org/symp2017 12
CAV Operational Scenarios (1)
• “Platooning” of CAVs • Traffic light intersection scenario • CAV/non-CAV overtaking scenario • Pedestrian encounter • Police encounter (static or moving) • Roadworks encounter • …and many more (39 scenarios identified so far…)
www.incose.org/symp2017 13
CAV Operational Scenarios (2)
www.incose.org/symp2017 14
CAV/CAV PlatooningCAV
CAV
CAV
CAVUser
CAVUser
CAVUser
Traffic Light Intersection
NonCAV
CAV
CAV
CAV-Electronic Road Signs (/ITS)
CAVUser
CAV
Electronic Road Sign
CAV-Pedestrian
Pedstrian(Obstacle)
CAVUser
CAV
Response: Stop/Avoid
Playing Pokemon GoLalalalalala
CAV-Roadworks
TrafficControl
RoadworksTeam
CAVUser
CAV
Response: Stop/Avoid
Caution, road works ahead!
CAV Operational Scenarios (3)
www.incose.org/symp2017 15
Home
CAVOwner
CAV
Home
MaaS P2P Customer
MaaSCAV
CAV
CAV
CAV
CAV(auto fail)???
RecoveryVehicle
CAV(total fail)
NonCAV
CAV
CAV
Non-CAV
CAV
CAV
CAV
CAV
Electronic Road Sign
Pedstrian(Obstacle)
CAV
Playing Pokemon GoLalalalalala
Carjacker(Obstacle)
CAVUser
CAV
Gimme your car and your
money!
Police Officer(Obstacle)
CAVUser
CAV
Stop for a breath test!
CAVUser
CAV
Police Vehicle(Obstacle)
PoliceOfficer
Stop, you nearly collided
with me! TrafficControl
RoadworksTeam
CAV
Caution, road works ahead!
CAV
CAV???
CAV???
CAVUser
Non-CAVDriver
Police
VehicleRecovery Police
Vehicle
CAV
RecoveryVehicle
NonCAV
Police
VehicleRecovery Police
Vehicle
CAV
RecoveryVehicle
CAV
CAV Refuel/RechargeFacility CAV
CAV MaintenanceFacility CAV
CAV RepairFacility CAV
Vehicle LicensingAuthority (RMS) CAV
Vehicle InsurerCAV
MaaS CAVService Provider CAV
CAV SupplierCAV
Road Map Data Supplier
CAV
CAV
Non-CAV CAV
Light RailVehicle
Non-CAV
Train
CAV
X
CAV
Hacker
???
victims
CAVVBIED
Terrorist
SecurityServices
CAV
Toll Gate & Cameras
CAV
RecoveryVehicle
Non-CAV
CAV
CAV???
CAV
Transport Interchange
??????
CAV
CAV Kiss & Ride operations at multi-modal transport interchange node
Cyber-attack on CAVs by hackers
CAV parking operations in at-grade or multi-story car-park.
No need for car-parks?
Aggressive driving behaviour toward
CAV by non-CAV
Safe recovery of broken-down CAV
by recovery vehicle
Personal P2P CAV owner/operator
MaaS P2P CAV Service customer
CAV Platooning scenario
CAV partial auto functional failure
Broken-down CAV interaction with recovery vehicle
CAV Toll Road Systems encounter
CAV terrorist VBIED encounter
CAV encounter with roadworks
CAV encounter with moving
police vehicle
CAV encounter with static police
RBT/Speeding
CAV encounter with carjacker or roadside robber
CAV encounter with pedestrian/jaywalker
CAV encounter with Digital Vehicle
Electronic Info Signs
CAV to non-CAV dangerous overtaking encounter
CAV to traffic light intersection encounter
(CAVs and non-CAVs)
CAV???
CAV to railway level crossing encounter
CAV to Light Rail mixed alignment encounter
CAV encounter with bad weather, low visibility
CAV transition from surfaced to non-
surfaced road/track
CAV interaction with CAV repair facility (unplanned repair)
CAV interaction with CAV maintenance facility (planned service)
CAV interaction with refuel/recharge facility
CAV-CAV collision scenario and interaction with police
& vehicle recovery
CAV-non CAV collision scenario and interaction with
police & vehicle recovery
CAV encounter with low visibility driving conditions
CAV encounter with unexpected
road diversion
CAV encounter with unexpected road hazard (any)
CAV interaction with vehicle licensing authority
to validate license
CAV interaction with vehicle insurer to validate
insurance claims
CAV interaction with MaaS P2P CAV
service providerCAV interaction with CAV supplier (e.g. S/W update)
CAV interaction with road map data agency
CAV Operational Risks Example: "loss of lane-keeping function leading to undesired and uncontrolled change of lane by the CAV“
www.incose.org/symp2017 16
Possible outcomes (consequences) for this risk: A. CAV crosses multiple lanes and runs off the
road (single vehicle V2I collision) B. CAV crosses one or more lanes and collides
with one or more other vehicles (multiple vehicle V2V collision)
C. CAV crosses into, and remains in, adjacent same-direction lane with no collision (no loss)
Conclusion The CAV Operational Concept Framework can be used to: • identify scenarios that require new or updated policy and
regulations, as well as to plan road infrastructure upgrades • systematically analyse the rapid rate of CAV-related
innovations to assist transport policy-makers to respond • Have a platform that can be expanded and adapted to
accommodate future new CAV innovations as they are delivered from the industry
www.incose.org/symp2017 17
www.incose.org/symp2017