Message sets for incident management ranked sixth out of forty-four on the ITS America standards survey and are therefore a major component of the Intelligent Transportation Infrastructure. The IEEE is not currently developing standards in this particular area but the Institute is developing standards in an equally high priority area of the ITS, namely, the Dedicated Short Range Communications Subsystem (DSRC).

During this project, we have amassed considerable information and expertise to recognize the critical importance of well-defined standard incident management data flows of the overall integrity of the National ITS. In addition, we have consulted with numerous experts in the field and are convinced that we can assemble the necessary engineer and scientist volunteers and informed industry advisors to form the IEEE Working Group(s) and can engage the required subject matter experts to support their activities in the design, specification, development and publication of the required standards to meet the architectural requirements.

Funding provided through the cooperative agreement will facilitate and expedite work that would normally be done entirely on a volunteer/as available basis. Without this support, the time required for completion of the tasks proposed in this project plan would be significantly increased.

The funding will be primarily used to engage the subject matter experts as consultants. However, to expedite the standards development and to ensure coordinated technical and operational aspects of the ITS with other standards development organizations as well and the IT community, some funding will be used for Program Management and administrative (staff) support as shown in the budget.

I. SCOPE AND FIELD OF APPLICATION

The Project will be conducted under the auspices of the IEEE Standard Coordinating Committee on Intelligent Transportation Systems (SCC32).

Message sets for incident management include all message sets transmitted between the emergency management subsystem to all other subsystems and providers. As identified in the National Architecture, these include the Emergency Telephone System, Fleet and Freight Management, Information Service Provider, Other Emergency Management Centers, Planning Subsystem, Traffic Management, and Transit Management.

Incident management is understood to encompass five basic tasks:

• incident detection and verification,
• incident response,
• incident site management,
• incident clearance, and
• vehicle operator information.

This Project Plan is for the first phase in this extensive program and will address message sets from the Emergency Management Center (EMC) to the Traffic Management Center (TMC) and E911 and other EMs designated in this project plan as Emergency Telephone Systems (ETS). Phases two and three covering the other relationships, will be the subject of two separate project plans.

The message sets between the EMC and the TMC were chosen in the first phase for several reasons. First, the Traffic Management Data Dictionary is well advanced in its development and will provide a starting point for message sets between the EMC and the TMC. Second, expansion of the National Transportation Communications Intelligent

Transportation System Protocol (NTCIP) for EMC to TMC is a logical extension of the current NTCIP. This project will also examine the extensions of NTCIP required for TMC to EMC message sets.

II. SPECIFIC TASKS

1. Survey existing programs in Incident Management with emphasis on interaction with traffic management.

A consultant will be tasked to review, collect, and consolidate currently available information on incident management programs, particularly in the interaction between EMCs and TMCs. An example is an incident management program being conducted jointly by CALTRANS and the California Highway Patrol.

2. Survey existing programs on ETS.

A consultant will be tasked to review, collect, and consolidate currently available information on existing programs on ETS with emphasis on communication requirements between the ETS and the EMC.

3. Analysis of NTCIP and EMC to TMC requirements.

A consultant will be tasked to review the needs of EMC to TMC communications and the requirements on NTCIP to meet these needs.

4. Coordinate with other efforts.

The Project will be continually coordinated with the other Standard Development

Organizations (SDOs) and the ITS Architecture Team as well as the ITS community through the ITS America Council of Standards Organizations (CSO). In particular, a close cooperative relationship will be established with the AASHTO/ITE/NEMA Committee on the NTCIP project, the AASHTO/ITE Traffic Management Data Dictionary project and the SAE Committee on E911 in addition to the standards work being performed in other IEEE Working Groups, e.g. the Working Group on Data Dictionaries and Message Sets Template.

A very important area of coordination is with the "not for profit" organizations and corporations dedicated to emergency and safety requirements associated with transportation, such as NENA and APCO. It is expected that members of these types of organizations will actively participate in the standards development work and receive partial funding of their involvement as a result of an initial outreach program.

5. Hold workshops.

Workshops and working group meetings will be held for participants to define and resolve issues, for subject matter experts to present the results of the tasks performed, and to perform and review preliminary standards work. Workshops will be arranged to coincide with specific milestones in the development of the standards , and will be populated by both private and public sector stakeholders in addition to industry experts,

6. Draft Standard for ETS to EMC Message Sets.

A consultant will be tasked to write requirements for ETS to EMC Message Sets and, at the appropriate time, to prepare the text of the draft standard(s).

7. Draft Standard for TMC to EMC Message Sets

A consultant will be tasked to write requirements for TMC to EMC Message Sets and, at the appropriate time, to prepare the text of the a draft standard(s).

8. Merge Draft Standards.

A consultant will be tasked to merge the draft standard(s) for ETS to EMC Message Sets and the draft standard(s) for TMC to EMC Message sets into one comprehensive standard.

9. Project management

As the IEEE is the lead SDO on this Project Plan, in addition to coordinating and managing the work specified in this Project Plan, (e.g. activity arrangements and scheduling, staffing requirements, reporting and general coordination with other SDOs, the Architecture Team and the IEEE Program Manager), project management will also include the oversight and integration of work outsourced to the supporting SDOs. The project management activity will also embrace required outreach assignments.

Misc.

In addition, IEEE will provide Web site services throughout the project for all tasks above.

III. SCHEDULE

The Project Schedule is included as Attachment A.

IV. PRODUCTS

The products of Tasks 1, 2, and 3 will be reports. The product of Task 5 will be workshop reports. The products of Task 6, 7 and 8 will be a draft standard(s). Tasks 4 and 9, which are management and coordination functions, will be reported in the quarterly status reports. Products from Tasks 1 - 8 will be supplied to the major program SDOs in addition to the FHWA Joint Program Office and the Architecture Team, as soon as available to assist in the cross system coordination of standards and reports. In addition, when the corresponding published IEEE standards are available, copies will also be distributed to the same parties.

V. RELATIONSHIP WITH OTHER EFFORTS

Relationships with other SDOs have been described under Task 4. Direct support will be provided by AASHTO, ITE and SAE and this is described in their submissions attached as Appendices ???. In addition, the work is closely related to the standards development being undertaken by ASTM on the ISO Layer 1 & 2 requirements and the general activities of ISO in TC204. Close cooperation with both these organizations and monitoring of the wireline standards in development by ANSI Committee T1 and wireless standards development by TIA is necessary to ensure interoperability and the reliability of the Incident Management data flows.

VI. PROJECT LEADER

The Project Leader will be the Chair of the Working Group on Message Sets for Incident Management within the IEEE Committee, SCC32 (to be appointed). The overall management of the project will be conducted by Ivor Knight.

Telephone 310 865-5167

Fax 301 865-3581

Email i.knight@ieee.org

Cellphone 410 491-5489

VII. BUDGET

The Project Budget is included as Attachment B.

VIII. FUNDING RATIONALE

Funding provided through the Cooperative Agreement will facilitate and expedite work that would normally be done entirely on a volunteer/as available basis, significantly lengthening time required for completion of tasks proposed in this Project Plan.

Available in hard copy only.

Available in hard copy only.

Available in hard copy only.

Available in hard copy only.

Available in hard copy only.