《IEEE-1512.2-2004.pdf》由会员分享，可在线阅读，更多相关《IEEE-1512.2-2004.pdf（183页珍藏版）》请在三一文库上搜索。
1、IEEE Std 1512.2-2004 IEEE Standards 1512.2 TM IEEE Standard for Public Safety Traffic Incident Management Message Sets for Use by Emergency Management Centers 3 Park Avenue, New York, NY 10016-5997, USA IEEE Standards Coordinating Committee 32 Sponsored by the IEEE Standards Coordinating Committee 3
2、2 on Intelligent Transportation Systems IEEE Standards 29 November 2004 Print: SH95277 PDF: SS95277 Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/20/2007 10:14:27 MDTNo re
3、production or networking permitted without license from IHS -,-,- IEEE Std 1512.2-2004 IEEE Standard for Public Safety Traffic Incident Management Message Sets for Use by Emergency Management Centers Sponsor Standards Coordinating Committee 32 (SCC 32) on IEEE Intelligent Transportation Systems Appr
4、oved 23 September 2004 IEEE-SA Standards Board Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/20/2007 10:14:27 MDTNo reproduction or networking permitted without license fr
5、om IHS -,-,- The Institute of Electrical and Electronics Engineers, Inc. 3 Park Avenue, New York, NY 10016-5997, USA Copyright 2004 by the Institute of Electrical and Electronics Engineers, Inc. All rights reserved. Published 29 November 2004. Printed in the United States of America. IEEE and 1512 a
6、re registered trademarks in the U.S. Patent +1 978 750 8400. Permission to photocopy portions of any individual standard for educational classroom use can also be obtained through the Copyright Clearance Center. NOTEAttention is called to the possibility that implementation of this standard may requ
7、ire use of subject matter covered by patent rights. By publication of this standard, no position is taken with respect to the existence or validity of any patent rights in connection therewith. The IEEE shall not be responsible for identifying patents for which a license may be required by an IEEE s
8、tandard or for conducting inquiries into the legal validity or scope of those patents that are brought to its attention. Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/20/2
9、007 10:14:27 MDTNo reproduction or networking permitted without license from IHS -,-,- ivCopyright 2004 IEEE. All rights reserved. Introduction (This introduction is not part of IEEE Std 1512.2-2004, IEEE Standard For Public Safety Traffic Incident Management Message Sets for Use by Emergency Manage
10、ment Centers.) The Incident Management Working Group was formed from a cross section of intelligent transportation system (ITS) and incident management practitioners in 1997 to address the problems and concerns of dispatching traffic management centers interacting with each other in the resolution o
11、f (primarily) roadway services disruptions (and certain other events on the highway)generically referred to as incidents. Advancing the greater coordination of these centers and their cross-servicing over various jurisdictional boundaries is the primary objective of this Working Group. This standard
12、, IEEE Std 1512.2-2004, is one of several related standards in this area and deals primarily with the communication of vital data of a public safety nature involved in transportation-related events. It is a companion standard to a base standard, IEEE Std 1512-2000.a Other categories of communication
13、, having to do with transportation management, hazardous material, and other cargo are addressed in other companion standards generated by the Working Group. The base standard, this standard, and other companion standards together comprise what shall be known as the IEEE 1512 Family of Standards. Th
14、e base standard includes more general introductory material for the family of standards, including the other companion standards and the relationship between the family of standards and other ITS standards and the National ITS Architecture. That material will not be repeated here. Rather, the remain
15、der of this Introduction will present a statement of the problem this companion standard is to address and its goal. Problem statement In the course of a transportation-related event where multiple public safety agencies are involved, there is a critical need to coordinate the management of the even
16、t among those agencies. Involved public safety agencies may include law enforcement, fire and rescue, emergency medical services (EMS), hazardous material management, traffic management, towing and recovery, and others. Each agency has a separate set of tasks, resources, and communication gear; yet
17、the agencies need to coordinate their separate actions. The challenge to be met by the IEEE 1512 Family of Standards is to specify message sets to support communication to coordinate those separate actions. That coordination extends to five categories of information, as follows: 1)Situation awarenes
18、s: A common-format rendition of the situation, i.e., the spatial layout, general aspects such as smoke and fire, what each agency is doing, and the tracking of several variables in a summary way: injured, response personnel, response equipment, witnesses, perpetrators, involved vehicles, and cargo.
19、2)Each agencys plan of action: A flexible format for agencies to disseminate their plans, so that each agency can take all other agencies plans into account in its own planning and management. That exchange can support the specification of a single incident-wide action plan, or simply each agency sp
20、ecifying its own plan, to be followed separately but accounting for the plans of the other agencies. 3)Asset management: An effective way for the agencies to share information about availability of assets for interagency management, and then to facilitate the interagency use of those assets, i.e., w
21、here Agency A requests that an asset of Agency B be dispatched to the incident. This extends to informing other agencies of the need for services such as law enforcement, evacuation, medical treatment, rescue, fire suppression, and hazardous material management. 4)Warning information: Emergency evac
22、uation, responder distress, cautions for responders, and “be on lookout for” information. aInformation on references can be found in Clause 2. Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=NASA Technical Standards 1/9972545001 N
23、ot for Resale, 04/20/2007 10:14:27 MDTNo reproduction or networking permitted without license from IHS -,-,- Copyright 2004 IEEE. All rights reserved.v 5)Messaging overhead: Message priority, drill/not-a-drill, acknowledgement, ability to address by function as opposed to by agency name, and determi
24、ning whether or not a center is functioning. Goal of this companion standard The goal of this companion standard is to specify message sets to support the exchange of the five types of information previously listed. More precisely, it is to specify the message sets that support that exchange, in com
25、bination with the message sets specified in the rest of the IEEE 1512 Family of Standards. As of this writing, that family of standards includes: Base standard: IEEE Std 1512-2000 Companion standard: IEEE Std 1512.1-2003 Companion standard: IEEE Std 1512.3-2002 As part of its support of that exchang
26、e, this companion standard will support existing conventions and nomenclature for established practices in public safety incident management, in particular the National Incident Management System (NIMS)b and existing formats for incident action plans. At the same time, the message sets will not requ
27、ire that the local implementation use NIMS or any particular format for an incident action plan. While in some local implementations any multi-agency incident is coordinated with a single plan, in other local implementations conventions are oriented around each agency having its own plan without any
28、 single, explicitly integrated plan. Both of those cases are supported by this standard. References to incident command systems (ICS) and unified command systems (UCS) in this standard shall be taken to also refer to the NIMS. Companion standards This standard, IEEE Std 1512.2-2004, provides informa
29、tion on additional messages, data frames, and data elements beyond those appearing in the base standard, IEEE Std 1512-2000, and the companion standards listed earlier. In order to make full use of this information, the base standard, companion standards, and other references to ITS and industry sta
30、ndards may also need to be employed. That is particularly true in the area of message set reuse, where the contents of various elements have been taken from well-established practices, both within and outside that of the ITS and the public safety industries. The standard and use with data registries
31、 This standard was developed in conjunction with entries designed to be made into a data registry. The following information may be useful to persons wishing to track the data structures described in this standard with those entries or in other similar registries. In each of the data structures foun
32、d in Clause 5, Clause 6, and Clause 7, the following metadata fields are used and are equivalent to the named fields in a data registry. The mapping between these fields is as follows. The specific clause numbering and name of an entry is also the descriptive name of that entry in the registry (the
33、part that follows after the “:” is the name used). The one or more paragraphs that then follow, headed “Use,” form the description entry. The final one or more paragraphs, headed “Remarks,” form the remarks entry. The section headed “Used by” contains linkages to other data structures that in turn r
34、efer to this one. In a data registry, the fields related data concept and relationship type may be used to convey this information, along with other relationships. The section headed “ASN.1 Representation” contains all the ASN.1 defining code. In a data registry, this information is broken up among
35、the fields: ASN.1 name, data type, valid value rule, and body. The ASN.1 name contains the formal ASN.1 Type Definition name of the object. The data type contains the base type from which it is defined. The valid value rule, or the body, then b U.S. Department of Homeland Security, www.dhs.gov, Marc
36、h 1, 2004. As of this writing, the exact URL is: www.dhs.gov/interweb/ assetlibrary/NIMS-90-web.pdf. Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/20/2007 10:14:27 MDTNo r
37、eproduction or networking permitted without license from IHS -,-,- viCopyright 2004 IEEE. All rights reserved. contains the various constraints, declared constants, enumerations values, and comments of the rest of the definition. In the case of data element entries, this information is found in the
38、valid value rule, while in the case of data frames and messages, this information is placed into the body field. Other fields used in a data registry (such as units or formula) are, typically, not provided with content from this standard, or are self-evident and constant in nature. The source field
39、is an example of this, and its value for all entries from this standard is IEEE 1512.2-2004. Notice to users Errata Errata, if any, for this and all other standards can be accessed at the following URL: http:/ standards.ieee.org/reading/ieee/updates/errata/index.html. Users are encouraged to check t
40、his URL for errata periodically. Interpretations Current interpretations can be accessed at the following URL: http:/standards.ieee.org/reading/ieee/interp/ index.html. Patents Attention is called to the possibility that implementation of this standard may require use of subject matter covered by pa
41、tent rights. By publication of this standard, no position is taken with respect to the existence or validity of any patent rights in connection therewith. The IEEE shall not be responsible for identifying patents or patent applications for which a license may be required to implement an IEEE standar
42、d or for conducting inquiries into the legal validity or scope of those patents that are brought to its attention. Participants At the time this standard was completed, the Incident Management Working Group for Intelligent Transportation Systems had the following membership: Ann Lorscheider, Chair J
43、erry Althauser, Vice-Chair April Walker, Sub-Chair George Ake Kurt Aufschneider Robert M. Barrett Ken Brooke Chester H. Chandler James Cheeks Bruce W. Churchill David Cope John Corbin Robert B. “Tip” Franklin, Jr. Wayne L. Gisler Michael Granados David Helman Kyle Hortin Dave Kelley Thomas M. Kuriha
44、ra John Lathrop Chuck Manuel Ed Mark Harlin McEwan Tom Merkle James Mona Michael Ogden Robert Rausch Michael Ritchie Rich Roberts Sharon Sanders Andrew M. Schoka Sheldon G. (Bo) Strickland Paul Thorpe Ken Vaughn Steven Verbil Copyright The Institute of Electrical and Electronics Engineers, Inc. Prov
45、ided by IHS under license with IEEELicensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/20/2007 10:14:27 MDTNo reproduction or networking permitted without license from IHS -,-,- Copyright 2004 IEEE. All rights reserved.vii The following members of the individual balloting committee vot
46、ed on this standard. Balloters may have voted for approval, disapproval, or abstention. When the IEEE-SA Standards Board approved this standard on 23 September 2004, it had the following membership: Don Wright, Chair Steve M. Mills, Vice Chair Judith Gorman, Secretary *Member Emeritus Also included
47、are the following nonvoting IEEE-SA Standards Board liaisons: Satish K. Aggarwal, NRC Representative Richard DeBlasio, DOE Representative Alan Cookson, NIST Representative Noelle D. Humenick IEEE Standards Project Editor Gerald Althauser Kurt Aufschneider Robert Barrett Dennis Bodson Ken Brooke Ches
48、ter H. Chandler James M. Cheeks Keith Chow John M. Corbin Dr. Guru Dutt Dhingra Robert B. Franklin Wayne L. Gisler Michael Granados Gloria Gwynne David L. Helman Kyle Hortin Piotr Karocki Thomas M Kurihara Jeremy Landt Ann Lorscheider William Lumpkins Edward L. Mark Tom Merkle James Mona Michael A.
49、Ogden Klaus Rapf Robert Rausch Michael Ritchie Rich Roberts Michael Shirven Gil Shultz Robert Soranno Sheldon G. Strickland Paul Thorpe April Walker Filip Weytjens Chuck Adams H. Stephen Berger Mark D. Bowman Joseph A. Bruder Bob Davis Roberto de Boisson Julian Forster* Arnold M. Greenspan Mark S. Halpin Raymond