Smart Work Zone Kickoff Meeting Minutes (1 31 22) - usdot-jpo-ode/wzdx GitHub Wiki

WZDx Smart Work Zone Subgroup Kickoff Meeting

January 31, 2022

Purpose

This Subgroup is the lead steward in proposing the means and necessary documentation/process for adding smart work zone device data to a new feed for SWZ device data within the WZDx Specification. During the previous cycle, the subgroup developed and released a new feed with SWZ device data. During this cycle, the SWZ Subgroup shall work with committee members to revise and update the smart work zone device data feed.

Agenda

  • Sign-in
  • Introduce Co-chairs and Review Subgroup Purpose, Scope and Objectives
  • Review Activities and Milestones
  • Overview of SWZ Device Feed
  • Live demo on Github of the SWZDeviceFeed
  • Back Log Items
  • Open Discussion
  • Action Items and Next Steps

Notes

Introduction (Neil Boudreau)

Neil Boudreau presented the project Scope, Objectives, Activities, and Milestones as listed in the meeting presentation.

SWZDeviceFeed Live Demo (Jacob Brady)

Jacob Brady presented a demo of the WZDx SWZ device feed repository and where the defined objects can be found. It was noted that the data flow chart should be added to the repository, not just shown in the pull request.

Back Log Items (Ben Acimovic)

Ben Acimovic presented the list of Back Log Items, requesting that participants discuss their needs, wants, and nice-to-haves to define a priority order of the list. A survey will be sent out to all members later in the week to receive feedback on back log items that are most important to SWZDeviceFeed users.

Facilitated Discussion (All Participants)

  • Neil Boudreau – We should include ‘Mobile Operations’ in this list.
  • Peter Kirkelis – ‘Workers Present’ is a high priority. (Sinclair Stolle agrees)
  • Juan Pava – ‘Board Heading/Bearing Angle’ is high priority.
  • Juan Pava –Should we (or can we) specify required refresh rates per device type? It may be outside the scope of this project, but this group would be good to talk about it. For example, noting the change in the feed every 1-2 minutes and perhaps health checks every 30 minutes. The time to update the information for the feed and how often the data is refreshed are two different things. We only want to know when something changes.
  • Devorah Henderson – We should discuss lane-level data and road events. How will road geometry be defined for sensor data reference? Who is responsible for that road geometry?
    • Jacob Brady – We should not require linking lane-level data to a road event. We did not have enough time to determine the needed level of information for a road event during the first phase, so we just referenced the appropriate already-defined road event. We will want to cover the lane-level data in a future implementation.
  • Russell Holt – Is there a need to address pedestrian/bike detection?
    • The focus has been on freeways/highways, but we can consider more local impacts as well. (Margaret Kubilins agrees that local government agencies will benefit from ped/bike consideration. Rented scooters have GPS that could be useful here.)
    • Ross Sheckler – This can lead to ADA matters with sidewalks. We should focus on the easy tasks first before tackling the more difficult problems (i.e. ped/bike)
  • Todd Foster – How agencies verify/digest/output to public needs to be done first with this feed. We should present some successful implementation before shifting to a task with a very different scope. (Ross Sheckler and Jeremy A agree)

Action Items and Next Steps (Neil Boudreau and Ben Acimovic)

  1. Next meeting is schedules for Monday, February 28th at 2PM
  2. Survey will be released for members to define Back Log Items priority levels.

Participants

  • Colorado DOT – Benjamin Acimovic*
  • iCone Products – Ross Sheckler*
  • Massachusetts DOT – Neil Boudreau*
  • Ver-Mac – Todd Foster*
  • Arizona DOT – Adam Carreon
  • Arizona DOT – Jerome Choy
  • Arizona DOT – Anissa Gerard
  • ArizoNa DOT – Marty Lauber
  • ATSSA – Donna Clark
  • Austin, TX – Luke Urie
  • Booz Allen Hamilton – Mahsa Ettefagh
  • Civiltronics – Derek White
  • Connecticut DOT – Jennifer Petrario
  • FHWA – Murat Omay
  • Florida DOT – Edward Albritton
  • GM – David Craig
  • HAAS Alert – Jeremy Agulnek
  • Hill and Smith – Todd Hartnett
  • Hill and Smith – Pete Krikelis
  • Hillsborough County – James Cullins
  • IBI Group – Jacob Brady
  • IBI Group – Michelle Boucher
  • IBI Group – David Siegel
  • Illinois DOT – Juan Pava
  • Illinois DOT - Peter Stresino
  • Iowa DOT – Dan Sprengeler
  • Iowa DOT – Sinclair Stolle
  • Iowa State University – Skylar Knickerbocker
  • Kentucky DOT – Andrew G Williams
  • Kentucky Transportation – Brandon Saylor
  • Massachusetts DOT – Carrie McInerney
  • Massachusetts DOT – Corey O’Connor
  • The Middlesex Corporation – Daniel DeRoehn
  • Minnesota DOT – Michelle Moser
  • Mixon Hill – Christopher Poe
  • QLynx Technologies – Devorah Henderson
  • Rhode Island DOT – Russell Holt
  • The Sanborn Map Company, Inc. – John Copple
  • Tampa, FL – Margaret Kubilins
  • TomTom – Robert Hoyler
  • Utah DOT – Chuck Felice
  • Volpe – Molly Behan
  • Volpe – Nate Deshmukh-Towery
  • Volpe – Hadrian CTR Merced Hernandez
  • Volpe – Mark Mockett
  • Wanco – Tim Paulino
  • Washington DOT – Tony Leingang
  • Wisconsin DOT – Erin Schwark

*Smart Work Zone Subgroup co-chair