IEEE 1512 3-2006 en Standard for Hazardous Material Incident Management Message Sets for Use by Emergency Management Centers《应急管理中心用危险材料事故管理信息集》.pdf

1、IEEE Std 1512.3-2006(Revision of IEEE Std 1512.3-2002)IEEE Standard for Hazardous MaterialIncident Management Message Setsfor Use by Emergency ManagementCentersI E E E3 Park Avenue New York, NY 10016-5997, USA7 July 2006Intelligent Transportation Systems CommitteeSponsored by theIEEE Vehicular Techn

2、ology SocietyIEEE Std 1512.3-2006(Revision ofIEEE Std 1512.3-2002)IEEE Standard for Hazardous Material Incident Management Message Sets for Use by Emergency Management CentersSponsorIntelligent Transportation Systems Committeeof theIEEE Vehicular Technology SocietyApproved 8 June 2006IEEE-SA Standar

3、ds BoardThe Institute of Electrical and Electronics Engineers, Inc.3 Park Avenue, New York, NY 10016-5997, USACopyright 2006 by the Institute of Electrical and Electronics Engineers, Inc.All rights reserved. Published 7 July 2006. Printed in the United States of America.IEEE is a registered trademar

4、k in the U.S. Patent +1 978 750 8400. Permission to photocopy portions ofany individual standard for educational classroom use can also be obtained through the Copyright ClearanceCenter.ivCopyright 2006 IEEE. All rights reserved.IntroductionThe Incident Management Working Group was formed from a cro

5、ss section of ITS (IntelligentTransportation System) and incident management practitioners in 1997 to address the problems andconcerns of dispatching traffic management centers interacting with each other in the resolution of(primarily) roadway services disruptions (and certain other events on the h

6、ighway), generically referred to asincidents. Advancing the greater coordination of these centers and their cross servicing over variousjurisdictional boundaries is the primary objective of this Working Group.This standard is one of several related standards in this area and deals primarily with the

7、 communication ofvital data of a public safety and/or emergency management nature involved in transportation-related events.It is a companion volume to a Base Standard: IEEE Std 1512-2006. Other categories of communication,having to do with transportation management, hazardous material, and other ca

8、rgo are addressed in othercompanion volumes generated by the Working Group. The Base Standard, this volume, and othercompanion volumes together comprise what shall be known as the IEEE 1512 Family of Standards.The Base Standard includes more general introductory material for the family of standards,

9、 including theother companion volumes and the relationship between the family of standards and other ITS standards andthe National ITS Architecture. That material will not be repeated here. Rather, the remainder of this sectionwill present a statement of the problem this companion volume is to addre

10、ss and its goal.Problem statementIn the course of a transportation-related event where multiple public safety agencies are involved, there is acritical need to coordinate the management of the event among those agencies. Involved public safetyagencies may include law enforcement, fire and rescue, em

11、ergency medical services (EMS), hazardousmaterial management, traffic management, towing and recovery, and others. Each agency has a separate setof tasks, resources, and communication gear; yet the agencies need to coordinate their separate actions.The challenge to be met by the IEEE 1512 Family of

12、Standards is to specify message sets to supportcommunication to coordinate those separate actions. That coordination extends to five categories ofinformation, as follows:a) Situation awareness: A common-format rendition of the situation, i.e., the spatial layout, generalaspects such as smoke and fir

13、e, what each agency is doing, and tracking several variables in asummary way: injured, response personnel, response equipment, witnesses, perpetrators, involvedvehicles, and cargo. And as a special subject area of this volume, detailed information relating to thecargo and any hazardous aspects that

14、it may contain and of which others need to be aware.b) Each agencys plan of action: A flexible format for agencies to disseminate their plans, so that eachagency can take all other agencies plans into account in its own planning and management. Thatexchange can support the specification of a single

15、incident-wide action plan, or simply each agencyspecifying its own plan, to be followed separately but accounting for the plans of the other agencies.c) Asset management: An effective way for the agencies to share information about availability ofassets for inter-agency management, and then to facil

16、itate the inter-agency use of those assets, i.e.,where Agency A requests that an asset of Agency B be dispatched to the incident. This approachextends to informing other agencies of the need for services such as law enforcement, evacuation,medical treatment, rescue, fire suppression, and hazardous m

17、aterial management.d) Warning information: Emergency evacuation, responder distress, cautions for responders, and “beon lookout for” information.This introduction is not part of IEEE Std 1512.3, IEEE Standard For Hazardous Material Incident ManagementMessage Sets for Use by Emergency Management Cent

18、ers.vCopyright 2006 IEEE. All rights reserved.e) Messaging overhead: Message priority, drill/not-a-drill, acknowledgment, ability to address byfunction as opposed to by agency name, and determining whether a center is functioning.That presents us with the basis for stating the goal.Goal of this comp

19、anion volumeThe goal of this companion volume is to specify message sets to support the exchange of the five types ofinformation just listed. More precisely, it is to specify the message sets that support that exchange, incombination with the message sets specified in the rest of the IEEE 1512 Famil

20、y of Standards. As of thiswriting, that IEEE 1512 Family of Standards includes Base Standard: IEEE Std 1512-2006, Standard for Common Incident Management Message Sets forUse by Emergency Management Centers Companion Volume: IEEE Std 1512.1TM-2006, Standard for Traffic Incident Management Mes-sage Se

21、ts for Use by Emergency Management Centers Companion Volume: IEEE Std 1512.2TM-2005, Standard for Public Safety Incident ManagementMessage Sets for Use by Emergency Management CentersAs part of its support of that exchange, this companion volume will support existing conventions andnomenclature for

22、established practices in public safety incident management, in particular the NationalIncident Management System (NIMS)1and existing formats for incident action plans. At the same time, themessage sets will not require that the local implementation use NIMS or any particular format for anincident ac

23、tion plan. Although in some local implementations any multiagency incident is coordinated witha single plan, in other local implementations, conventions are oriented around each agency having its ownplan without any single, explicitly integrated plan. Both of those cases are supported by this standa

24、rd.References to ICS and UCS in this volume shall be taken to also refer to the NIMS.Companion volumesThis standard provides information on additional messages, data frames, and data elements beyond thoseappearing in the Base Standard (IEEE Std 1512-2006) and the companion volumes listed above. To m

25、akefull use of this information, the Base Standard, companion volumes, and other references to ITS andindustry standards may also need to be employed. That is particularly true in the area of message set reusewhere the contents of various elements have been taken from well-established practices, bot

26、h within andoutside that of the ITS and the public safety industries.The standard and use with data registriesThe standard was developed in conjunction with entries designed to be made into a data registry. Thefollowing information may be useful to persons wishing to track the data structures descri

27、bed in thisstandard with those entries or in other similar registries.In each of the data structures found in Clause 5 through Clause 7 of this standard, the following meta datafields are used and are equivalent to the named fields in a data registry. The mapping between these fields isas follows. T

28、he specific clause numbering and name of an entry is also the DESCRIPTIVE NAME of thatentry in the registry (the part that follows after the “:” is the name used). The one or more paragraphs thatthen follow, headed “Use,” forms the DESCRIPTION entry. The final one or more paragraphs, headed“Remarks,

29、” forms the REMARKS entry. The section headed “Used by,” contains linkages to other data1U.S. Department of Homeland Security, www.dhs.gov, March 1, 2004. As of this writing, exact URL: http:/www.dhs.gov/interweb/assetlibrary/NIMS-90-web.pdf.viCopyright 2006 IEEE. All rights reserved.then follow, he

30、aded “Use,” forms the DESCRIPTION entry. The final one or more paragraphs, headed“Remarks,” forms the REMARKS entry. The section headed “Used by,” contains linkages to other datastructures that in turn refer to this one. In a data registry, the fields RELATED DATA CONCEPT andRELATIONSHIP TYPE may be

31、 used to convey this information, along with other relationships. The sectionheaded by “ASN.1 Representation,” contains all ASN.1 defining code. In a data registry, this information isbroken up among the fields: ASN.1 NAME, DATA TYPE, VALID VALUE RULE, and BODY. TheASN.1 NAME contains the formal ASN

32、.1 Type Definition name of the object. The DATA TYPE containsthe base type from which it is defined. The VALID VALUE RULE, or the BODY, then contains the variousconstraints, declared constants, enumerations values, and comments of the rest of the definition. In the caseof data element entries, this

33、information is found in the VALID VALUE RULE, whereas in the case of dataframes 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 contentfrom this standard or are self evident and constant i

34、n nature. The SOURCE field is an example of this, andits value for all entries from this standard is IEEE Std 1512.3-2006.Notice to usersErrataErrata, 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

35、 are encouraged to check this URL forerrata periodically.InterpretationsCurrent interpretations can be accessed at the following URL: http:/standards.ieee.org/reading/ieee/interp/index.html.PatentsAttention is called to the possibility that implementation of this standard may require use of subject

36、mattercovered by patent rights. By publication of this standard, no position is taken with respect to the existence orvalidity of any patent rights in connection therewith. The IEEE shall not be responsible for identifyingpatents or patent applications for which a license may be required to implemen

37、t an IEEE standard or forconducting inquiries into the legal validity or scope of those patents that are brought to its attention.viiCopyright 2006 IEEE. All rights reserved.ParticipantsAt the time this standard was completed, the Incident Management Working Group for IntelligentTransportation Syste

38、ms had the following membership and officers: Ann R. Lorscheider, ChairGerald W. Althauser, Vice ChairMichael Ritchie, Hazmat Sub-ChairWayne I. Gisler, SecretaryThe following members of the individual balloting committee voted on this standard. Balloters may havevoted for approval, disapproval, or a

39、bstention. The Working Group wishes to acknowledge the assistance of SubCarrier Systems Corp (SCSC) and theirITSware tool suite in the preparation of the document. This standard was prepared using the ITSware Mini-Edit automated tools to create and manage the text and the ASN.1 and XML productions f

40、ound in thestandard, and to ensure synchronization between these entries and those of the data registry and otherstandards. The Working Group wishes to acknowledge the assistance of Bancroft Scott and Paul Thorpe of OpenSystems Solutions, Inc. (OSS) in providing the use of their ASN.1 tool suite com

41、piler. The ASN.1 syntaxappearing in this standard was validated using that tool suite compiler.George AkeKurt AufschneiderRobert M. BarrettCharles R. BergerRick GlasscoPatrick ChanChester H. Chandler IIIJames CheeksBruce W. ChurchillDavid CopeJohn CorbinRobert B. Franklin Jr.Michael GranadosDavid He

42、lmanKyle HortinRon IceManny InsignaresValerie KalhammerDavid KelleyDavid KingeryThomas M. KuriharaEva Lerner-LamJohn LathropRoger MaddenChuck ManuelEd MarkHarlin McEwenTom MerkleJames A. MonaSriram NatarajanMichael OgdenRobert RauschAnita C. RickettsRich RobertsDoug RoremSharon SandersAndrew M. Scho

43、kaSheldon G. StricklandPaul ThorpeThomas J. TimchoKen VaughnSteven VerbilApril WalkerAdewole C. AkposeGerald W. AlthauserLee R. ArmstrongKurt AufschneiderSaber Azizi-GhannadCharles L. BarestKeith ChowBruce W. ChurchillTommy P. CooperRonald L. DaubertJesus M. De Leon DiazGary L. DonnerJoe ElyRabiz N.

44、 FodaTip FranklinDavid L. GilmerWayne GislerRandall C. GrovesGloria G. GwynneDavid HelmanDennis K. HolsteinDennis HorwitzArshad HussainOh JongtaekPiotr KarockiRobert B. KelseyJim KulchiskyThomas M. KuriharaGeorge W. KyleShawn M. LeardSolomon LeeYeou Song LeeAnn R. LorscheiderWilliam LumpkinsG. L. Lu

45、riAhmad MahinfallahDavid A. MaleCharles ManuelEdward MarkThomas J. MerkleGary L. MichelJames MonaMichael S. NewmanSatoshi OyamaMichael RitchieRobert A. RobinsonRandall M. SafierMichael SchollesJack ShermanTakashi ShonoDavid SingletonLuca SpotornoGerald J. StueveThomas A. TulliaApril WalkerWilliam Wh

46、ytePaul R. WorkChaehag YiviiiCopyright 2006 IEEE. All rights reserved.The IEEE 1512 Family of Standards is dedicated to the memory of those who lost their lives responding to the tragic events of September 11, 2001. The Working Group honors the men and women who continue to maintain vigilance in pro

47、tecting freedom and security. It is our hope and expectation that these standards will enhance multijurisdictional communications.When the IEEE-SA Standards Board approved this standard on 8 June 2006, it had the followingmembership:Steve M. Mills, ChairRichard H. Hulett, Vice ChairDon Wright, Past

48、ChairJudith Gorman, Secretary*Member Emeritus 2001 The Record, (Bergen County, NJ), Thomas E. Franklin, Staff Photographer. (www.groundzerospirit.org) Mark D. BowmanDennis B. BrophyJoseph BruderRichard CoxBob DavisJulian Forster*Joanna N. GueninMark S. HalpinRaymond HapemanWilliam B. HopfLowell G. J

49、ohnsonHerman KochJoseph L. Koepfinger*David J. LawDaleep C. MohlaPaul NikolichT. W. OlsenGlenn ParsonsRonald C. PetersenGary S. RobinsonFrank StoneMalcolm V. ThadenRichard L. TownsendJoe D. WatsonHoward L. WolfmanixCopyright 2006 IEEE. All rights reserved.Also included are the following nonvoting IEEE-SA Standards Board liaisons:Satish K. Aggarwal, NRC RepresentativeRichard DeBlasio, DOE RepresentativeAlan H. Cookson, NIST RepresentativeMichael D. FisherIEEE Standards Project EditorMatthew CegliaIEEE Standards Program Manager, Technical Program DevelopmentPatricia A. G