All Member Forum

 View Only

TMDD Comments Requested by 03/31/15

By Tatiana Richey posted 03-13-2015 09:20 AM

  
This message has been cross posted to the following Discussions: All Member Forum and TMDD Community - ITS Standards discussion .
-------------------------------------------

The TMDD contractor, with input from the TMDD steering committee, has completed Version 3.03c of the Traffic Management Data Dictionary.  This document can be found on the ITE web site under Technical InformationStandardsTMDD and selecting Version 3.3 will bring you to the following URL: http://www.ite.org/standards/tmdd/3.03.asp

Volume 1 of this document includes a discussion of the user needs, requirements derived from the user needs, and a Needs-to-Requirements Traceability Matrix (NRTM). 

Volume II of the document includes the dialogs and data elements which constitute the message sets and schema for exchanges between a traffic management center (TMC) and other centers for the provision of traffic information external to a typical TMC.  This standard has been widely used in previous versions around the country. The purpose of this outreach is to solicit feedback from the stakeholder and user community with respect to any of the following:

  1. Ambiguities in the existing document; our contractor team, working with the software team during the development of a testing tool (Reference Implementation), has attempted to ensure that all requirements trace to a dialog and message in a single manner such that 2 implementations will interoperate.  If you have discovered any issues which might interfere with the development of interoperable systems, please bring these to the attention of the ITE as soon as possible.
  2. Errors in the existing document - any aspect of the existing document which you feel may be in error should be brought to our attention.
  3. Additional User Needs that have not been addressed by the current document. The TMDD has been "around" for more than a decade and was designed to support center-to-center data sharing and shared device management to foster regional systems integration.  During that period of time, many such regional systems have been deployed and we would like to lessons learned to be brought back to the TMDD for additions where appropriate.
  4. Changes you would feel need to be made to improve the operational efficiency or accuracy of the exchanges. 

In all cases, you are asked to be specific in your findings or needs for extensions. General statements such as "the device control is not sufficient" are not helpful and will be ignored.  Rather, if you feel that the control interface is lacking specific commands and/or feedback - please offer the details (XML schema, ASN.1 data definitions) and dialogs to meet the needs.  Identify missing requirements or areas where you have had to extend the standard to meet your specific implementation goals such as beacons as attributes to highway advisory radios or a better mechanism for multi-message HAR message specifications.  Please indicate/propose a solution that we can work with for the next version or updates.

Once we have received your recommendations, our contractor will review the proposed solutions (based on your submissions) and make appropriate recommendations to the steering committee and then follow through with the development of an addendum or corrigendum as necessary for final approval by the steering committee.

Since the schedule is important, we would ask that you please provide your comments to patrick.chan@consystec.com no later than March 31, 2015 so that we can schedule a review and teleconference with the steering committee in April or May 2015.  Our goal is to review and update the TMDD as necessary approximately every 9 months.    
------------------------------



#TMDD
0 comments
47 views

Permalink