**[Virginia Department of Transportation]{.underline}**

**[Response to:]{.underline}**

**[Section 1201 Interim Guidance]{.underline}**

**[Real-Time System Management Information Program Data Exchange
Formats]{.underline}**

**[February 12, 2008]{.underline}**

The following is the Virginia Department of Transportation's response to
the request for comments on the "Publication of Interim Guidance on the
Information Sharing Specifications and Data Exchange Formats for the
Real-Time System Management Information Program" by the Federal Highway
Administration, FHWA Docket No. FHWA-2007-28969 for Notice of
publication of interim guidance; request for comments.

The Virginia Department of Transportation (VDOT) supports the concept of
developing data exchange formats for systems to exchange data between
one another. VDOT feels that data should be capable of being readily
exchanged across jurisdictional boundaries. As an example, data
collected by highway and transit monitoring systems should be shared
between states, and between state and local agencies to benefit the
traveling public. Data exchange formats provide a roadmap to link
functional specifications to commonly used ITS standards. As you will
see from our response, VDOT supports this concept in our current
infrastructure. It is VDOT's recommendation that data exchange formats
should not be revised at arbitrary intervals. Rather, the interval
should be driven by industry need for new features, known deficiencies
with the standard, and any ambiguities in interpreting the standard.

In this response, VDOT makes reference to the standards currently used
in applications throughout the state. VDOT appreciates the opportunity
to join other states in providing comments concerning the information
sharing specification and data exchange formats for the real-time system
management information program. We support the end goal for these data
exchange formats to enable agencies to collect data from other systems
and provide information externally without establishing a different data
exchange format with each system interface.

As VDOT indicated in our previous FHWA / AASHTO response to Section
1201, request for information on the Real-Time System Management
Information Program submitted on July 3, 2006 and this response, VDOT
strongly supports the concept for establishing a standardized format for
the information related to real-time travel conditions. This
standardized approach will determine the tools and processes needed to
collect and disseminate such information. In our 2006 response, VDOT
recommended that the data exchange formats be established by the
Secretary, and follow the standards currently in practice or yet to be
developed under the auspices of the cooperative agreements to "foster
the development of ITS standards" between the U.S. DOT and other
Standard Development Organizations. It is still VDOT's position that the
Section 1201 mandates must provide a new source of funding for the
development, implementation and maintenance of such a program. The
implementation of Section 1201 will necessitate reviews of the ITS
architecture at the regional and statewide levels, and will likely
result in changes of priorities for some ITS projects.

[VDOT offers the following response to the questions in the
notice]{.underline}:

1.  **What guidance would facilitate the application of data exchange
    formats in your organization?**

Response:

> FHWA could collect best practices and examples from other state DOTs
> on how they used these data exchange standards. For example, what
> value ranges was selected for certain parameters, and which optional
> data elements were used.

2.  **Does the reference document provide adequate detail on the nature
    of interoperability to be attained through application of the data
    exchange formats?**

Response:

> Yes, the reference document is well-organized by focusing on key
> interfaces within the National ITS Architecture.

3.  **Does your organization make use of the ATIS-01 Broadcast Traveler
    Information Market Package defined in the National ITS
    Architecture?**

> Response:
>
> VDOT generally provides the data flows associated with the following
> interfaces specified by the ATIS01-Broadcast Traveler Information
> Market Package:

-   Traffic Management Information

-   Maintenance and Construction Management

-   Information Service Provider Information

-   Emergency Management Information

4.  **What is a reasonable interval between publications of new versions
    of the data exchange formats?**

> Response:
>
> The interval between publications of new versions of standards should
> not adhere to a fixed time frame. Rather, the interval should be
> driven by industry need for new features, known deficiencies with the
> standard, and any ambiguities in interpreting the standard.

5.  **Is there sufficient detail in the "Functional Area/Specification
    Description?" If not, how much further requirement description would
    be required?**

> Response:
>
> VDOT feels that the level of detail in the Function/Specification
> Description column is sufficient.

6.  **Many of the specifications map to messages that have optional
    elements. Should there be changes to the identification of the
    [optional elements]{.underline}, which would change the nature of
    the message as defined by the Standard Development Organization?**

> Response:
>
> Any changes to the optional status of a given message should be based
> on overwhelming implementation by DOT practitioners. It is recommended
> that the proposed RTIP Specifications table indicate which
> Dialogs/Messages are fully dependant on optional elements.

7.  **Does your organization make use of the ITS Standards that are
    referenced in the data exchange formats?**

> Response:
>
> Yes. VDOT uses the following data exchange standards between its
> Traffic Management Centers and Transportation Emergency Operations
> Center and a Data Gateway, which enables exchanges with Computer Aided
> Dispatch systems and a Regional Transportation Clearinghouse known as
> RITIS. VDOT's Traffic Management Centers and Transportation Emergency
> Operations Center will use VaTraffic as its event/incident data
> application statewide.

**VATraffic**

VaTraffic is a web-browser based application that exchanges data with
the following systems:

1.  Traffic Management Centers which includes all statewide actionable
    information;

2.  511 Virginia --our Traveler Information statewide system for phone,
    Web and E-mail alerts;

3.  The Roadway Network System (RNS);

4.  A work order tracking system for state property repair needs;

5.  VDOT's Dashboard for tracking performance measures;

6.  The VaTraffic Global Database, which is a database management system
    utilized for data archival purposes;

7.  Other Incident Management tracking systems;

8.  and the Data Gateway, which serves as the clearinghouse for all of
    these applications.

The VaTraffic application is an integrated solution for gathering,
storing and disseminating relevant roadway information to field
personnel, management and the traveling public, especially in the event
of emergencies, such as daily traffic incidents and severe weather.
VaTraffic is designed to improve VDOT's operations by providing a more
efficient and advanced integrated data management platform for managing
a variety of activities that affect the quality of traveler's experience
in the Commonwealth. VaTraffic will play a central role in how VDOT
actively manages transportation system operations, from the day-to-day
process of managing traffic incidents, to serving as a source of data to
support ongoing assessment of traffic conditions and maintenance
planning.

The VaTraffic system will help VDOT achieve the four goals stated in its
2005 Business Plan:

-   Improve Safety

-   Improve Highway Operational Performance

-   Preserve the Infrastructure

-   Improve Security

**RITIS**

The Regional Integrated Transportation Information System (RITIS)
collects, integrates, and disseminates transportation data from traffic
and transit management centers in Maryland, D.C. and Virginia. RITIS
currently disseminates data via the following standards:

-   SAE J2354 "Message Set for Advanced Traveler Information System
    (ATIS)"

-   ITE "Traffic Management Data Dictionary (TMDD)" v2.1

-   IEEE IM 1512.1 "Traffic Incident Management Message Sets for Use By
    Emergency Management Centers"

RITIS developers plan to update data feeds as new versions of these or
other standards become adopted. RITIS developers make every effort to
strictly follow the standards with minimal use of extensions so as to
allow for the greatest interoperability between systems.

**VDOT TMCs**

Most of VDOT's Traffic Management Centers (TMCs) employ the following
data exchange standards:

  ------ ----------------------------------------------------------------
  CAP    The Common Alert Protocol (CAP) is used to send alerts from
         Computer Aided Dispatch (CAD) systems to a Data Gateway that
         makes the data available to VDOT's TMCs. CAP is also used to
         receive messages from AMBERAlert.com.

  1512   VDOT uses the IEEE 1512 standard for data exchanges between the
         Data Gateway and external systems.

  EDXL   VDOT uses the EDXL distribution element to wrap messages
         exchanged with the Data Gateway. The use of EDXL also meets the
         requirements for data sharing equipment mandated by the Virginia
         Commission on Interoperability to receive state grants.

  TMDD   VDOT has experimented with the TMDD standard to exchange device
         information with the Data Gateway.

  OGC    VDOT uses a number of OGC standards to exchange GIS data between
         its TMCs and other systems. Standards used include: WMS, WMS-C,
         WFS, and WPS.

  OMF    VDOT has experimented with using OMF standards for the exchange
         of weather data between its TMCs and other external systems.
  ------ ----------------------------------------------------------------

8.  **Would independent certification or self-certification be more
    effective for validating the application of the data exchange
    formats?**

Response:

> VDOT feels that independent certification would be more effective for
> validating data exchange formats.

9.  **Do the data exchange formats relate to the operational practices
    of your organization?**

> Response:
>
> Yes, generally. VDOT currently uses the Common Alert Protocol (CAP),
> TMDD and IEEE 1512 standards for internal and external dissemination
> of Traffic Management, Emergency Management, and Traveler Information
> data.