Q1 Report


Project Kick-off Meeting

During an initial kick-off project meeting on January 6, 2017, at the Las Vegas City Hall, the project team reviewed a number of topics to better define the scope and intent of the project.

The first discussion was to come to consensus on four “use cases” (scenarios) that would serve as a framework for the vehicle-to-city connectivity and data flow.  The four use cases are:

  • UC1 Speeding Warning -- Display a warning to drivers that they are exceeding the current speed limit, thus lowering the risk of pedestrian strikes.
  • UC2 High-risk Pedestrian Area Warning -- Using the vehicle’s position and time of day, display a warning on the IVI when the vehicle is nearing an area that is known to be a high risk area for pedestrians.
  • UC3 Bus Stop Warning -- Riders often get off a bus and attempt to cross the street, increasing the chance of a vehicle hitting them.  By alerting drivers in the area via the IVI that a bus is stopped at a nearby bus stop, these accidents could be prevented.
  • UC4 Traffic Congestion Warning -- It is not always possible for drivers to see stopped traffic ahead.  By collecting information from stopped vehicles to determine if there is potential congestion, and displaying a warning to driversapproaching the position of the last car with the traffic congestion, the chance of rear-end collisions could be reduced.

The project team agreed that project success criteria would be learned as the pilot progressed, but two suggestions for criteria were:

  • Using speed data, determine if drivers actually slowdown in response to warnings.  Measure and report success rates.
  • Gather qualitative feedback from drivers through interviews, surveys and in-car video.

Next, the GENIVI team introduced the technologies that would be involved (On-board unit, Remote Vehicle Interaction [RVI] software and Big Data Management Software) to deliver the identified use cases).

The kick-off meeting concluded with a definition of initial project milestones and a general goal to get a single vehicle equipped and connected to the server-based software by the end of March.

Q1 Project Progress

During a subsequent team meeting, it was decided that because of the number of participants and the breadth of the project focus, four sub-teams should be launched around the following topics:

  • Hardware/On-board Unit
  • Servers/Data
  • Communications
  • Executive Topics/Planning

The Hardware/On-board Unit Sub-team:

  • Tracked the progress and completion of a Vehicle-to-X (V2X) prototype board that, along with a Raspberry Pi board and a series of cables, would make up the on-board unit device
  • Developed a bill of materials (BOM) required for full connectivity of a vehicle and established a purchasing list so that all components and parts could be ordered easily
  • Discussed how to mount the on-board units with safety and fleet managers from the city
  • Decided on a GSM-based, mobile network model for data movement to/from the vehicles
  • Identified a list of fleet vehicles to be equipped with the OBU during the project
  • Produced the necessary software scripts to gather, push, and display data through the OBU   

The Servers/Data Sub-team:

  • Discussed the requirements for the necessary servers to host the RVI and Hortonworks software and delivered a requirements document to the City’s IT department
  • Discussed the sources of and make-up of the required data to support the fulfillment of the intended use cases/scenarios

The Communications Sub-team:

  • Developed a three-month communication plan for the pilot
  • Drafted content that could eventually be used to develop a first announcement on pilot project progress

The Executive Sub-team:

  • Discussed and produced the necessary legal agreements for the pilot
  • Drafted a Request for Information (RFI) document to obtain information from organizations wishing to participate in the pilot
  • Agreed to hold a mid-year review of project scope and progress, at which they would also begin considering additional organizations participating in the project
  • Agreed to establish a “portal” on which documents could be shared and eventually to have a dedicated project website

End of Quarter Status:

  • Legal Agreements and Disclaimers: Generally complete, though the GENIVI-Las Vegas agreement was pending approval at a city council meeting in April.
  • Hardware/On-board Unit: Additional testing of all components of the on-board unit across an AT&T mobile network was pending in April prior to an initial install of a vehicle as soon after as possible; additional V2X boards must be manufactured and the on-board units assembled and loaded with GENIVI software prior to installation; a mounting bracket for the on-board unit required additional research as suggested options were deemed to not work.
  • Servers/Data: Server procurement and installation timelines pushed the availability of the required server and software infrastructure to Q2.  Data sources and make-up will be tested once the data servers are available and the Hortonworks data management software has been installed and configured.