ISO/TR 22351:2015 PDF

Societal security — Emergency management — Message structure for exchange of information

Название (английский):

ISO/TR 22351:2015

Societal security — Emergency management — Message structure for exchange of information

Статус документа:: Действующий
Формат:: Электронный (PDF)
Количество страниц:: 90
Дата публикации:: 1 сентября 2015 г.
Издание:: ISO TR 22351 edition 1 version 1
ICS:: 03.100.01

Тип поставки:

Full version1 350 €Read online 24h10 €Read online 72h15 €

Язык документа:

ruen

Срок поставки:15 раб. дн. (перевод)

Цена:1 350 €

Описание (английский):

ISO/TR 22351:2015 describes a message structure for the exchange of information between organizations involved in emergency management. An organization can ingest the received information, based on the message structure, in its own operational picture. The structured message is called Emergency Management Shared Information (EMSI). ISO/TR 22351:2015 describes the message structure built in order to facilitate interoperability between existing and new information systems. The intended audience of ISO/TR 22351:2015 is control room engineers, information systems designers and decision makers in emergency management. NOTE The EMSI can be used complementary to other message protocols, as for example the common alert protocol (CAP).

Технические детали

Технический комитет: ISO/TC 292 - Security and resilience
SKU: ISO/TR 22351:2015

Abstract

Overview

ISO/TR 22351:2015 - "Societal security - Emergency management - Message structure for exchange of information" defines a standardized message structure, the Emergency Management Shared Information (EMSI), for exchanging operational information between organizations involved in emergency management. The Technical Report is aimed at improving interoperability, enabling different information systems to ingest and present shared information in their own operational picture. EMSI is complementary to other protocols such as the Common Alerting Protocol (CAP).

Key Topics

EMSI structure and content
- Four element groups: CONTEXT, EVENT, RESOURCE, MISSION. CONTEXT and EVENT are mandatory; RESOURCE and MISSION are optional.
- Context covers message identification, originator, creation time, confidentiality, urgency and links to external information.
- Event covers assessment, declaration/observation times, location, casualties and predictions.
- Resource and mission describe assets, capabilities, positions and tasks.
Element definition rules
- Elements described by name, definition, type, cardinality and value domain.
- Types include basic data types (strings, integers, floats), enumerations (limited lists), and extensive code lists (dictionaries).
- Naming constraints: element names in English and limited to 32 characters; free-text fields should be limited (recommended max ~500 characters).
Codes dictionary and multilingual support
- EMSI uses a hierarchical codes dictionary to avoid free text and enable automatic translation to local languages.
- Code structure: hierarchical elements separated by “/”; code tokens use 1–8 uppercase letters A–Z and digits 0–9 (example: MAT/VEH/ROADVE/FRFGTN/BREATH).
Implementation guidance
- XML is the recommended encoding for EMSI messages to facilitate system integration and automated processing.

Applications and Users

Primary users
- Control room engineers, information systems designers, emergency management decision makers.
Practical applications
- Real‑time sharing of situational awareness data across agencies (police, fire, medical, civil protection).
- Cross-border and civil–military coordination where differing terminologies and languages exist.
- Integrating feeds into command-and-control dashboards, resource tracking, and mission planning systems.
Benefits
- Faster, automated data ingestion into operational pictures, improved coordination, reduced ambiguity through coded values and translations.

Related Standards

ISO 22320 - Guidance on incident response and operational coordination (interoperability focus).
ISO 22300 - Societal security terminology used by ISO/TR 22351.
Common Alerting Protocol (CAP) - EMSI can be used complementarily with CAP for alerting workflows.

Keywords: ISO/TR 22351:2015, EMSI, emergency management, message structure, interoperability, XML, codes dictionary, situational awareness, information exchange.

Overview

Key Topics

EMSI structure and content
- Four element groups: CONTEXT, EVENT, RESOURCE, MISSION. CONTEXT and EVENT are mandatory; RESOURCE and MISSION are optional.
- Context covers message identification, originator, creation time, confidentiality, urgency and links to external information.
- Event covers assessment, declaration/observation times, location, casualties and predictions.
- Resource and mission describe assets, capabilities, positions and tasks.
Element definition rules
- Elements described by name, definition, type, cardinality and value domain.
- Types include basic data types (strings, integers, floats), enumerations (limited lists), and extensive code lists (dictionaries).
- Naming constraints: element names in English and limited to 32 characters; free-text fields should be limited (recommended max ~500 characters).
Codes dictionary and multilingual support
- EMSI uses a hierarchical codes dictionary to avoid free text and enable automatic translation to local languages.
- Code structure: hierarchical elements separated by “/”; code tokens use 1–8 uppercase letters A–Z and digits 0–9 (example: MAT/VEH/ROADVE/FRFGTN/BREATH).
Implementation guidance
- XML is the recommended encoding for EMSI messages to facilitate system integration and automated processing.

Applications and Users

Primary users
- Control room engineers, information systems designers, emergency management decision makers.
Practical applications
- Real‑time sharing of situational awareness data across agencies (police, fire, medical, civil protection).
- Cross-border and civil–military coordination where differing terminologies and languages exist.
- Integrating feeds into command-and-control dashboards, resource tracking, and mission planning systems.
Benefits
- Faster, automated data ingestion into operational pictures, improved coordination, reduced ambiguity through coded values and translations.

Related Standards

ISO 22320 - Guidance on incident response and operational coordination (interoperability focus).
ISO 22300 - Societal security terminology used by ISO/TR 22351.
Common Alerting Protocol (CAP) - EMSI can be used complementarily with CAP for alerting workflows.

Keywords: ISO/TR 22351:2015, EMSI, emergency management, message structure, interoperability, XML, codes dictionary, situational awareness, information exchange.

ISO/TR 22351:2015 PDF

Технические детали

Abstract

Overview

Key Topics

Applications and Users

Related Standards

Похожие стандарты

Abstract

Overview

Key Topics

Applications and Users

Related Standards

Похожие стандарты

Societal security — Emergency management — Requirements for incident response

Security and resilience - Vocabulary (ISO 22300:2025)

Water quality — Biological classification of rivers — Part 1: Guidance on the interpretation of biological qu…

Standard Practice for Use of a Radiochromic Liquid Dosimetry System (Withdrawn 2020)

Standard Practice for Dosimetry in Gamma Irradiation Facilities for Food Processing (Withdrawn 2013)

Standard Practice for Dosimetry in Electron Beam and X-Ray (Bremsstrahlung) Irradiation Facilities for Food P…

Standard Practice for Dosimetry in Radiation Processing

Standard Terminology for Additive Manufacturing—Coordinate Systems and Test Methodologies