Reply To: Vehicle Automation Capability

Homepage Forums Reply To: Vehicle Automation Capability

Posted: Jun/23/2016 at 11:23am – author:sweissman
tgorman wrote:

While I agree that some of the information should be captured, from the standpoint of having to fill out MMUCC crashes on the LE side at scenes, I don’t feel capturing the actual type of technology present would be feasible, accurate, or captured properly.  Many people operating their vehicles don’t know the technologies that exist in the vehicles (some don’t actually know what type of car they are operating). I understand that gathering the information is helpful for a multitude of reasons but let’s now forget a crash is small portion of what a LE officer is doing and many of them are busy (budget cuts are not helping) and the information may not be gathered with a degree of accuracy and thus giving you bad data which in my opinion is worse than not having the data.


Everyone is making excellent points, and I completely agree here that this data will be difficult to collect at first. If I may shed some light on our thinking (MMUCC proposed revisions), this is intended to be more of a placeholder at first. Changing forms and the databases that house State crash data takes years, sometimes decades. But the technology is progressing so rapidly, it was imperative that MMUCC propose this element so that States could gradually integrate this type of data, and eventually have a way of accurately collecting it. Before a train can travel, we must first build the rails.


Additionally, I would agree that capability is insufficient. The element should be proposed with two parts – what is the capability and what was active at time of crash? In time, these might prove to be powerful data that drive future decisions on vehicle automation. This is a great time to have this conversation.

Scroll to Top
Please include the time the issue happend (with timezone), what you did to trigger the error (ex: what link you clicked on, or did it happen on page load? etc.)
Please attach a screenshot of the problem/error (if any)