Specifying application of a device such as an arrow board

[rdsheckler]

Several of the device types that exist in WZDX can be used in a variety of applications. Do we want to have specific applications?

For instance, we have arrow boards that are mounted on trailers, service trucks, TMA trucks, striping trucks, sweepers, etc. We track the application in our system and plan on passing that along in our feed with the assumption that the users will find value in these details. Does WZDX want to put some standardization into these sort of specific applications, and can we suggest a short list of such applications?

[rdsheckler]

As an example, at iCone, some of the applications in which we see arrow boards deployed are:

• Trailer • TMA, this encompasses a lot of applications, basically anything were a person is exposed should be in front of a TMA! o "shadowing" o cone deployment/retrieval o pot hole patching o crack filling o guide rail repair • Plows and Salt trucks • Line painting • Street sweeping • Incident response ("Road Ranger", tow trucks, etc.)

[RHolt-RIDOT]

Great question @rdsheckler. Appreciate you sharing the list above. However I wonder if such specific applications may be too varied / great in number to try and capture all, and wonder/suggest, if it hasn't already been done, it might be better to come up with a list of the general/overall messages to road users that each and every type of smart Temporary Traffic Control Device (TTCD) in a work zone can be intended to convey, regardless of what the specific work activity(ies) may be happening. If such would be helpful/valuable to stakeholders (and again if not already done or covered by WZDx), I offer a Draft list below, which may certainly be biased from my DOT side of things (if data providers and private industry find value in more specific data/info like has been listed above for arrow boards, then I don't want or intend to disregard that).

• Regulatory, Road Closed / Follow Detour

• Regulatory, Speed Limit (Enforceable by Law) In Effect or Active

• Regulatory, Stop Control / Stop Here

• Regulatory, Automated Speed Enforcement In Effect or Active

• Regulatory (and/or Warning, if applicable?), Merge Here / Take Turns

• Warning (and/or Regulatory, if applicable?), Over-Sized Vehicle Detected

• Warning, Advisory Speed Limit In Effect or Active

• Warning, Speed Feedback / Slow Down

• Warning, Road, Lane(s), or Shoulder(s) Closed Ahead

• Warning, Lane Closed / Merge Right (or Left)

• Warning, Shoulder Closed

• Warning, Road Worker(s) Ahead / Be Prepared to Stop or Slow As/If Necessary

• Warning, Flagger Ahead / Be Prepared to Stop or Slow As/If Necessary (this could be combined w/ above if desired)

• Warning, Traffic Congestion or Queue Ahead / Be Prepared to Stop or Slow As/If Necessary

• Warning, Narrow Road or Lane(s) Ahead / Be Prepared to Slow As/If Necessary

• Warning, Adverse Weather Condition Detected Ahead / Be Prepared to Stop or Slow As/If Necessary

• Warning, Adverse Roadway Condition Detected Ahead / Be Prepared to Stop or Slow As/If Necessary

• Warning, New or Changed Traffic Pattern Ahead

• Guidance, Travel Time or other Travel-Reliability Related Info

• Guidance, Parking Info

• Guidance, Planned Special Event Info

I may certainly be missing some key ones from the above, this is just a first shot.

[j-d-b]

Based on co-chairs discussion 2022-09-22, no consumers have expressed interest for this data. MassDOT noted they just need to know if a device (e.g. arrow board) is moving (FieldDeviceCoreDetails is_moving) and that there is an arrow board (marking a lane closure), not what the arrow board is mounted on.