CPED Staff Proposal: New Autonomous Vehicle Program Data Reporting
1. AV Pilot Program Quarterly Reporting
Going forward, participants in the AV Pilot programs will be required to submit
quarterly data reports using the same templates as AV Deployment program
participants. AV Deployment quarterly reporting requirements are described in
D.20 -11-046 (as modified by D.21 -05-017); see Appendix A. The AV Deployment
quarterly reporting templates are available on the Commission’s website . This
requirement will go into effect immediately upon publishing of the updated data
reporting requirements.
2. Collision Reporting
Collision reporting in AV Deployment shall be modeled on DMV form OL -316.1
Reporting is required for any autonomous vehicle operating under a CPUC
Deployment authorization. If such a vehicle is involved in a collision resulting in
damage of property, bodily injury, or death, the AV carrier will report the
following within 10 days after the collision:
• Carrier information: Name, address, telephone number
• Collision information: Date, time, location (address or intersection)
• Vehicle information (AV): Vehicle year, make, model, license plate number
including state of registration, number of vehicle occupants (including
both public and carrier employees)
• Other party information:
o For other vehicles: Vehicle year, make, model, license plate number
including state of registration
o Pedestrians, bicyclists, or property involved, and information on
property damage, injuries, fatalities
o Injuries or fatalities of occupant(s) of involved vehicle(s)
• Collision conditions and circumstances, select one or more as applicable
for each party involved:
o Weather conditions (clear, cloudy, raining, snowing, fog/visibility,
wind, other)
o Lighting conditions (daylight, dusk/dawn, dark – street lights, dark
– no street lights, dark – street lights non -functioning)
o Roadway surface (dry, wet, snowy/icy, slippery)
o Roadway conditions (holes/deep rut, loose material on roadway,
obstruction on roadway, construction/repair zone, reduced
roadway width, flooded, other, no unusual conditions)
o Movement preceding collision (stopped, proceeding straight, ran off
road, making right turn, making left turn, making u turn, backing,
slowing/stopping, passing other vehicle, changing lanes, parking
maneuver, entering traffic, other unsafe turning, crossings into
opposing lane, parked, merging, traveling wrong way, other)
o Type of collision (head -on, side swipe, rear end, b roadside, hit
object, overturned, vehicle/pedestrian, other)
o Other associated factors (CVC sections violated/cited, vision
obscurement, inattention, stop and go traffic, entering/leaving
ramp, previous collision, unfamiliar road, defective equipment,
uninvolved vehicle, other, none apparent, runaway vehicle)
• Narrative description of collision, explaining the factors noted above as
necessary
The Consumer Protection and Enforcement Division will provide a fillable form
or spreadsheet for submission of this in formation.
Collision reports will be posted publicly on the Commission’s website, with any
personally identifying information (such as names, addresses, driver’s license
numbers, license plates) redacted.
3. Monthly Reporting
Participants in the AV program shall report the information below to CPED
monthly. Reports will be due on the 10th of each month for the preceding month.
• Operations summary
o Number of trips
▪ By zip code (origin and destination)
o Number of passengers carried
o Number of vehicles operating
▪ Number of unique vehicles that operated that month
▪ Maximum vehicles operating daily within the month
▪ Median vehicles operating daily within the month
o Vehicle miles traveled2
▪ Period 1
▪ Period 2
▪ Period 3
▪ Total
• For every instance where an AV achieved a minimal risk condition
(MRC)3, list:
o License plate, VIN, or other unique identifier for AV involved
o Date and time AV achieved minimal risk condition
o Location of MRC
▪ Latitude and longitude
▪ More than 18 inches from curb?
▪ Blocking or partially blocking a travel lane?
▪ Blocking or partially blocking a bike lane?
▪ Blocking or partially blocking a transit -only lane?
▪ Within 200 feet of the nearest rail of any rail grade crossing?
o Involvement of law enforcement or other first responders
▪ Law enforcement/first responders involved?
▪ Citation issued?
o Resolution of MRC: returned to automated operation remotely (by
remote operator), returned to automated operation manually (in -
person), returned to automated operation without manual or remote
operator intervention, manually driven away, towed, other
(describe)
o Response time
▪ For incidents requiring manual removal of vehicle or other in -
person manual intervention: time of dispatch, arrival at
vehicle, vehicle removed or returned to automated operation
▪ For incidents resolved remotely: time remote operator
connected to vehicle, time vehicle returned to automated
operation (or situation otherwise resolved; describe in
narrative)
▪ For incidents resolved without in -person or remote operator
engagement: time vehicle returned to automated operation
and moved from location of stop
o Number of passengers in vehicle, if applicable
▪ If passengers were present in the vehicle, how ride was
resolved – e.g., completed in same AV (autonomous mode),
completed in same AV (manual mode), completed in a
different vehicle, passenger ended ride early, etc.
o Narrative description of event, including:
▪ Factors that led to or caused fallback to MRC
▪ Impacts or risk to safety of passengers and other road users
▪ Remediation; steps taken to prevent future occurrences
• Count of passenger pickup and drop -off occurring more than 18 inches
from the curb and fraction of all pickups and drop -offs occurring more
than 18 inches from the curb
o By zip code
o By census tract
o By time of day (hour)
4. Data Sharing from Local Jurisdictions
Municipalities have unique access to data on what is occurring on the streets
within their jurisdictions. CPED invites parties to comment on 1) their interest in
voluntary reporting of relevant municipal data to CPED and 2) what data are
available, regularly reportable, and relevant to the monitoring and evaluation of
AV operations.
Examples might include 911 reports, citations by local police or parking officials,
and other data. Reports should be anonymized or otherwise redacted to prevent
disclosure of personally identifiable information.
