Satellite Earth Stations and Systems (SES); Reference scenario for the deployment of emergency communications; Part 2: Mass casualty incident in public transportation

DTS/SES-00341-2

General Information

Status
Published
Publication Date
21-May-2015
Current Stage
12 - Completion
Due Date
31-May-2015
Completion Date
22-May-2015
Mandate
Ref Project
Standard
ETSI TS 103 260-2 V1.1.1 (2015-05) - Satellite Earth Stations and Systems (SES); Reference scenario for the deployment of emergency communications; Part 2: Mass casualty incident in public transportation
English language
46 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


TECHNICAL SPECIFICATION
Satellite Earth Stations and Systems (SES);
Reference scenario for the deployment of
emergency communications;
Part 2: Mass casualty incident in public transportation

2 ETSI TS 103 260-2 V1.1.1 (2015-05)

Reference
DTS/SES-00341-2
Keywords
emergency, satellite
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2015.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI TS 103 260-2 V1.1.1 (2015-05)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
Introduction . 5
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 7
3 Definitions, symbols and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 9
4 Disaster scenario . 10
4.1 General . 10
4.2 Scenario definition . 10
4.3 Tasks and activities . 11
4.4 Accident response actions . 12
4.4.1 General . 12
4.4.2 Emergency management . 12
4.4.3 Risk management and damage mitigation . 13
4.4.4 Casualty logistics . 14
5 Information exchanges . 16
5.1 General . 16
5.2 Communication needs between emergency management hierarchies . 17
5.3 Communication needs by action . 18
5.3.1 Emergency management . 18
5.3.2 Risk management and damage mitigation . 20
5.3.2.1 Fire-fighting . 20
5.3.2.2 Rescue . 21
5.3.2.3 Maintenance of public order . 23
5.3.2.4 Provisions . 23
5.3.3 Casualty logistics . 23
5.3.3.1 Overview . 23
5.3.3.2 Treatment and medical evacuation . 23
5.3.3.3 Temporary shelter and evacuation . 27
5.4 Characteristics of emergency communication services . 27
5.4.1 General . 27
5.4.2 Speech services . 27
5.4.2.1 Main requirements . 27
5.4.2.2 PMR group call channels . 27
5.4.3 Paging (short message) services . 28
5.4.4 Status monitoring and location services. 28
5.4.5 Data services . 28
6 Topology model . 29
6.1 General . 29
6.2 Model graphics . 29
6.3 Model specification . 30
6.3.1 Scenario quantities . 30
6.3.2 Locations . 31
6.3.2.1 On-site . 31
6.3.2.2 Off-site . 31
6.3.3 On-site actors . 32
Annex A (informative): Modelling specification of objects, parameters and behaviour . 34
ETSI
4 ETSI TS 103 260-2 V1.1.1 (2015-05)
A.1 Modelling assumptions. 34
A.2 Modelling action/time parameters . 34
A.3 Pseudo-code describing the model behaviour . 35
A.3.1 Pseudo-code describing the initialization of the simulation including placement of locations . 35
A.3.2 Pseudo code describing the mobility and sequential actions of the respective actors . 36
A.3.3 Pseudo code describing the end of the incident and "ramp down" . 39
A.4 Objects and their parameters . 39
Annex B (informative): Bibliography . 45
History . 46

ETSI
5 ETSI TS 103 260-2 V1.1.1 (2015-05)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://ipr.etsi.org).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Satellite Earth Stations and
Systems (SES).
The present document is part 2 of a multi-part deliverable covering the reference scenario for the deployment of
emergency communications, as identified below:
Part 1: "Earthquake";
Part 2: "Mass casualty incident in public transportation".
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "may not", "need", "need not", "will",
"will not", "can" and "cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms
for the expression of provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
Introduction
Major emergencies or disasters may result in a need for additional resources in local telecommunications networks,
especially if they are damaged or overloaded, in order to maintain or enhance the ability of emergency services to
respond and coordinate their activities effectively. Satellites can play a role in replacing or supplementing terrestrial
telecommunications links in these scenarios. For example satellite systems can provide:
• broadband and secure communication facilities anywhere/anytime in locations where no other facilities are
available
• temporary replacement of broken/saturated infrastructures by means of backhauling
• fast deployment of temporary communication networks during emergencies/disasters
Hence a basis for requirements for such links needs to be established, and it is intended that the scenarios defined here
may be used for this purpose at a later stage.
The present document also is a response to EC mandate M/496 [i.13], specifically dossier 9 "Disaster Management"
part 2: "Emergency Telecommunication Services" which aims to support standardization for the optimal needs of the
emergency responders.
The use of satellite communication in disasters is described in ETSI TR 102 641 [i.3].
ETSI
6 ETSI TS 103 260-2 V1.1.1 (2015-05)
In the present document, clause 4 defines the scenario, what actions need to be taken by which actors (who will have
communications needs) and what their tasks are. This definition constitutes a basis for clause 5, which defines the
nature of information exchanges needed. Clause 6 defines the detailed parameters relating to positions and movements
of scenario actors, which are intended to form a basis for modelling of the scenario response topology. These
parameters are generic enough to be applicable or adapted to similar but different scenarios, and may eventually be used
to model the requirements for actors' communication exchanges, and associated capacities.

ETSI
7 ETSI TS 103 260-2 V1.1.1 (2015-05)
1 Scope
The present document defines a reference scenario for a mass-transportation accident (MTA) in a rural environment.
The scenario includes definition of the responders involved and their gross communication needs without specifying the
network technologies involved. Finally the topology modelling of the responders involved is defined, in terms of their
disposition in the incident area, their time evolution and their movements (if any).
The scenario is not generic in the sense of representing all emergencies of this type, but is intended to be a "typical"
example, and thus a reference in order to allow evaluation and dimensioning of required overall emergency
telecommunications.
The regulations and operating procedures for emergency responses vary between countries; for example the
organization responsible for the overall emergency management can be the police, the fire or rescue organization, a
dedicated organization for this purpose (e.g. civil protection), or others.
The response services defined for these scenarios are limited to safety-related services (i.e. not security such as law
enforcement).
Casualties and personnel not active in the rescue operations (e.g. the press) have been excluded, as their
communications needs are not covered by the emergency communication systems considered here, but their needs are
considered in ETSI TR 102 410 [i.2].
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
Not applicable.
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI TS 102 181: "Emergency Communications (EMTEL); Requirements for communication
between authorities/organizations during emergencies".
[i.2] ETSI TR 102 410: "Emergency Communications (EMTEL); Basis of requirements for
communications between individuals and between individuals and authorities whilst emergencies
are in progress".
[i.3] ETSI TR 102 641: "Satellite Earth Stations and Systems (SES); Overview of present satellite
emergency communications resources".
ETSI
8 ETSI TS 103 260-2 V1.1.1 (2015-05)
[i.4] Recommendation ITU-T G.114. Series G: Transmission Systems and Media, Digital Systems and
Networks. International telephone connections and circuits - General recommendations on the
transmission quality for an entire international telephone connection. One-way transmission time.
[i.5] United Nations Disaster Assessment and Coordination UNDAC Field Handbook.
[i.6] European Union Handbook on Assistance Intervention in the Frame of Community Mechanism for
the Cooperation of Civil Protection.
[i.7] Cabinet Office. UK Civil Protection Lexicon.
[i.8] Hamdi Monia, Franck Laurent and Lagrange Xavier: "Topology modelling and network
partitioning: an application to forest firefighting". Radio science bulletin, 2013, pp. 8-20.
[i.9] Franck Laurent, Hamdi Monia and Giraldo Rodriguez Carlos: "Topology modelling of emergency
communication networks: caveats and pitfalls". The International Emergency Management Society
Workshop 2011, The International Management Society, 22-23 June 2011, Nîmes, France, 2011.
[i.10] Aschenbruck Nils, Gerhards-Padilla Elmar and Martini Peter: "Modelling mobility in disaster area
scenarios". Performance Evaluation, 2009, vol. 66, n 12, pp. 773-790.
[i.11] Schwamborn Matthias, Aschenbruck Nils and Martini Peter: "A realistic trace-based mobility
model for first responder scenarios". Proceedings of the 13th ACM international conference on
Modeling, analysis, and simulation of wireless and mobile systems, Bodrum, Turkey, October 17-
21, 2010.
[i.12] ETSI TR 102 643: "Human Factors (HF); Quality of Experience (QoE) requirements for real-time
communication services".
[i.13] EC mandate M/496: "M/496 Mandate addressed to CEN, CENELEC and ETSI to develop
standardisation regarding spaceindustry (phase 3 of the process)".
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
accident: unplanned, unexpected, unintended and undesirable happening which results in or has the potential for injury,
harm, ill-health or damage [i.7]
casualty: individual in the incident area and requiring evacuation including those who are:
(i) non-injured, but affected,
(ii) injured and treated on site,
(iii) injured and needing treatment off-site (medevac), and
(iv) deceased.
Common Operating Picture (COP): single display of information collected from and shared by more than one agency
or organization that contributes to a common understanding of a situation and its associated hazards and risks along
with the position of resources and other overlays of information that support individual and collective decision making
[i.7]
control centre: operations centre from which the management and co-ordination of the response by each emergency
service to an emergency are carried out [i.7]
disaster: emergency (usually but not exclusively of natural causes) causing, or threatening to cause, widespread and
serious disruption to community life through death, injury, and/or damage to property and/or the environment [i.7]
emergency: an event or situation which threatens serious damage to human welfare, environment, or security (based on
[i.7])
ETSI
9 ETSI TS 103 260-2 V1.1.1 (2015-05)
Emergency Control Centre (ECC): facilities used by emergency organizations to handle rescue actions in answer to
an emergency call ETSI TS 102 181 [i.1]
emergency service: service, recognized as such by the member state, that provides immediate and rapid assistance in
situations where there is a direct risk to life or limb, individual or public health or safety, to private or public property,
or the environment but not necessarily limited to these situations ETSI TS 102 181 [i.1]
emergency team (ET): the smallest group of actors (i.e. one or more) considered to be acting together.
Field Emergency Control Centre (FECC): facilities used by emergency service organizations to manage, command,
coordinate, and control rescue works and logistics in the incident area
Geographical Information System (GIS): computer based system that supports the capture, management, analysis and
modelling of geographically referenced data [i.7]
hazard area: area with obvious or supposed threats to physical/psychological health, properties, and/or environment
holding area: generic term for an area to which resources and personnel not immediately required at the scene or being
held for further use, can be directed to standby [i.7]
incident: event or situation that requires a response from the emergency services or other responders [i.7]
incident area: area where the incident occurred, and/or the area which needs communication coverage to manage the
response implemented ETSI TS 102 181 [i.1]
incident commander: the nominated officer with overall responsibility for management, command, coordination, and
control of rescue and relief works in the incident area
Local Emergency Management Authority (LEMA): local organization within the public services fully or partly
responsible for emergency preparedness and handling of incidents (based on ETSI TS 102 181 [i.1])
Mass Casualty Incident (MCI): incident (or series of incidents) causing casualties on a scale that is beyond the normal
resources of the emergency services [i.7]
Non-Governmental Organization (NGO): organization that is neither run or controlled by a government nor a profit-
oriented business
Personal Protective Equipment (PPE): protective clothing, helmets, goggles or other garment designed to protect the
wearer's body from injury [i.7]
Public Safety Answering Point (PSAP): physical location where emergency calls are received under the responsibility
of a public authority ETSI TS 102 181 [i.1]
Respiratory Protective Equipment (RPE): designed to protect workers from dusts, fumes, vapours or gases [i.9]
site incident officer: representative from the affected organization, when an incident occurs within the perimeter of an
industrial or commercial establishment, public venue, airport or harbour, to liaise with the emergency management
structures [i.7]
triage: assessment of casualties and allocation of priorities by the medical or ambulance staff (based on [i.7])
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
CCP Casualty Collection Point
CFECC Coordinating Field Emergency Control Centre
COP Common Operating Picture
DCP Deceased Collection Point
EC European Commission
ECC Emergency Control Centre
EMTEL EMergency TELecommunications
ET Emergency Team
ETSI European Telecommunications Standards Institute
FECC Field Emergency Control Centre
ETSI
10 ETSI TS 103 260-2 V1.1.1 (2015-05)
GIS Geographical Information System
IC Incident Commander
IPR Intellectual Property Right
ISO International Standardization Organization
ITU International Telecommunication Union
ITU-R International Telecommunication Union Radiocommunications Sector
ITU-T International Telecommunication Union Telecommunications Sector
LEMA Local Emergency Management Authority
MCI Mass Casualty Incident
Medevac Medical Evacuation
MIC Medical Incident Commander
MTA Mass Transportation Accident
NGO Non-Governmental Organization
PMR Private Mobile Radio
PPE Personal Protective Equipment
PSAP Public Safety Answering Point
SatEC Satellite Emergency Communications Working Group
SECC SubService Emergency Control Centre
SES Satellite Earth Station and Systems
SQ Scenario Quantity
STF Specialist Task Force
TC Technical Committee
TCC Temporary Care Centre
TR Technical Report
TS Technical Specification
4 Disaster scenario
4.1 General
This clause firstly defines a mass transportation accident (MTA) scenario. Subsequently the response actions by
emergency services to this scenario are defined in terms of the services involved, actors, roles, and organizational
structures.
The main characteristics of an MTA in a rural environment are:
• Many casualties in the incident area.
• Accident is concentrated on a small geographical area.
• Access limitations (e.g. narrow roads or dirt tracks only).
• Limited available emergency services resources.
• Limited nearby hospital treatment capacities and/or treatment specialities.
• Sparse communication network coverage/capacities, both for private mobile radio (PMR) and commercial
wireless services.
4.2 Scenario definition
The disaster scenario is a train crash due to a collision with a road vehicle at a level crossing located in a sparsely
populated countryside environment. Some coaches of the passenger train overturn resulting in 170 casualties. The
overhead line is not damaged.
120 casualties are not injured, 30 are slightly injured, 15 are seriously injured, 5 are dead, and 10 casualties are trapped.
The accident happens in the evening of a cold winter day.
ETSI
11 ETSI TS 103 260-2 V1.1.1 (2015-05)
C E
Incident Area
Hazard
Area
A
60m 400m
B
D F
100m
600m
Figure 4.1: Geographical layout of the incident area
Figure 4.1 depicts the geographical layout of the MTA with zones and support areas:
The incident area has a dimension of 400 m by 600 m.
1) The hazard area includes the derailed/overturned coaches and the destroyed road vehicle and has a dimension
of 100 m by 60 m.
2) "A" denotes the rail track.
3) "B" denotes the road with the level crossing.
4) "C" is the nearest ambulance station (25 km distance to hazard area).
5) "D" is the nearest fire station (15 km distance to hazard area).
6) "E" is the nearest shelter (15 km distance to hazard area).
7) "F" is the nearest hospital (25 km distance to hazard area).
The rear part of the train blocks the level crossing so that road traffic cannot pass any more. There is neither light nor
heating in the coaches. Additionally, smoke emerges from one of the coaches.
Main consequence of the MTA is a mass casualty incident (MCI) requiring efficient casualty treatment and transport
logistics.
4.3 Tasks and activities
This clause defines the response entities (i.e. actors) and their roles within the incident area in handling the accident.
The main entities are emergency services and relevant authorities and/or NGOs supporting the emergency services.
Depending on local/national organization of services and division of tasks/responsibilities, the entities involved, their
responsibilities, and their individual areas of work may differ between countries.
In addition to their primary roles, actors may participate in other tasks. The roles will differ between countries, but a
typical distribution of roles is given below:
1) Emergency management: setting up of management structures for all involved emergency services,
coordination of emergency services, and reporting to the emergency control centre (ECC) and to the local
emergency management authority (LEMA) [i.5], [i.6], leading the coordinating field emergency control centre
(CFECC).
2) Fire-fighting: securing the hazard area, fighting fires.
3) Rescue: securing the hazard area, rescuing casualties.
4) Maintenance of public order: documentation, investigations.
ETSI
12 ETSI TS 103 260-2 V1.1.1 (2015-05)
5) Provisions: supplies, shelters, transport.
6) Casualty logistics: triage, registration, and treatment of the injured, organizing and conducting medical
evacuation out of the incident area, organizing and conducting evacuation of non-injured casualties out of the
incident area.
The actions during the emergency response in the incident area of this particular scenario are further defined in the
following clauses.
4.4 Accident response actions
4.4.1 General
The actions of the actors (defined in clause 4.3) in the incident area of this particular scenario are further defined below
including overall duration for each action.
Figure 4.2 shows the general organizational hierarchy of the teams of actors (responders) involved.
Off-Site/Support Area
Incident Area
Coordinating
Field ECC (CFECC)
Service 1 Service 2
ECC (FECC) ECC(FECC)
SubService 1 SubService 2 SubService 1 SubService 2
ECC (SECC) ECC (SECC) ECC(SECC) ECC(SECC)
ECC: Emergenc y Control Centre
Service e.g. Fire-fighting & Rescue
: Hierarchical links
Sub-Service: e.g. Fire-fighting

Figure 4.2: Responder organizational hierarchy
4.4.2 Emergency management
Deployed emergency services set up their own management structure in terms of service field emergency control
centres (FECCs) and SubService emergency control centres (SECCs), as shown in figure 4.2. The actions in table 4.1
are sorted according to their ideal occurrence. In fact, nearly all actions of all involved actors are conducted nearly
simultaneously so that there is no distinct order.
ETSI
13 ETSI TS 103 260-2 V1.1.1 (2015-05)
Table 4.1: Emergency management
Involved actors Actions Start Intermediate End point Duration
point point
All involved emergency Transport of emergency First Arrival Arrival Minutes
services management personnel and alerting
equipment (e.g. command
vehicle) to the incident area
Incident commander (IC) Establishing emergency Arrival CFECC in place End of Hours
management structures emergency
response works
Fire service Establishing emergency Arrival All End of Hours
management structures FECCs/SECCs in emergency
place response works
Rescue service Establishing emergency Arrival All End of Hours
management structures FECCs/SECCs in emergency
place response works
Health service Establishing emergency Arrival All End of Hours
management structures FECCs/SECCs in emergency
place response works
Relevant authority/non- Establishing emergency Arrival All End of Hours
governmental management structures FECCs/SECCs in emergency
organizations (NGO) place response works
Site incident officers E.g. railway operator and Arrival - End of Hours/days
roads department emergency
representatives; response works
Consulting to emergency
services
4.4.3 Risk management and damage mitigation
Risk management is a key response activity which is in the MTA scenario mainly related to the hazard area. The
deployed emergency services have to identify risks, assess risks, and plan risk mitigation measures. Tables 4.2 and 4.3
describe main activities of fire-fighting and rescue emergency services.
Table 4.2: Fire-fighting
Involved Actions Start Intermediate End point Duration
actors point point
Fire service Transport of emergency teams (ET) and First Arrival Arrival Minutes
fire-fighting equipment to the alerting
incident/hazard area
Fire service Risk identification/assessment; Arrival All fires out, End of Hours
Set-up of exclusion zone (i.e. inner hazard area emergency
cordon); secured response works
Immediate life-saving measures;
Handing over of casualties to health
service at CCPs;
Fire-fighting, securing the hazard area;
Reporting to CFECC
Site incident Support to fire-fighting (e.g. grounding of Arrival Reporting to fire- End of Hours
officers overhead line) fighting emergency
response works
ETSI
14 ETSI TS 103 260-2 V1.1.1 (2015-05)
Table 4.3: Rescue
Involved Actions Start Intermediate End point Duration
actors point point
Rescue Transport of emergency teams (ET) First Arrival Arrival Minutes
service and rescue equipment to the alerting
incident/hazard area
Rescue Risk identification/assessment; Arrival All casualties End of rescue works (all Hours
service Localization of casualties in hazard localized casualties
area; rescued/evacuated from
Rescue/evacuation of casualties out hazard area)
of hazard area (e.g. medical
evacuation with stretchers, vehicle
extrication)
Immediate life-saving measures;
Handing over of casualties to health
service at CCPs;
Reporting to CFECC
Site Support to rescue (e.g. consulting, Arrival Reporting to End of emergency Hours
incident grounding of overhead line) rescue response works
officers
Damage mitigation is not only restricted to physical damages in the hazard area. It includes security aspects and
provisions supply.
Table 4.4: Maintenance of public order
Involved actors Actions Start point Intermediate point End point Duration
Police Public order; Arrival - End of investigations Hours/days
Documentation;
Investigation;
Table 4.5: Provisions
Involved Actions Start point Intermediate point End point Duration
actors
LEMA Shelter provision; Assessment All non-injured casualties All non-injured Hours
Support to organization at temporary shelter casualties outside
of evacuation; incident area
General support to
deployed emergency
services
4.4.4 Casualty logistics
The activities related to casualty management are depicted in figure 4.3. Injured casualties are either transported directly
to hospitals ("immediate medical evacuation - medevac") or taken to the temporary care centre (TCC). Depending on
their health status and depending on available resources these casualties are either handed over to a temporary shelter or
transported to hospitals.
Non-injured casualties are directly guided to a temporary shelter and then evacuated to shelters outside the incident
area.
For the scope of the present document, logistics related to deceased casualties are not considered.
ETSI
15 ETSI TS 103 260-2 V1.1.1 (2015-05)
Deceased
Collection
Point(s)
immediate medevac
treatment
Casualty Temporary medevac
Hazard
Collection Care Hospitals
Area
Point(s) Centre(s)
no treatment no medevac
evacuation
Temporary
Shelter
Shelter(s)
Incident Area
Casualties
Figure 4.3: Casualty flow chart
Tables 4.6 and 4.7 describe the actors and actions related to casualty logistics both for injured and non-injured
casualties.
Table 4.6: Treatment and medical evacuation
Involved Actions Start point Intermediate point End point Duration
actors
Health Transport of emergency teams First alerting Arrival Arrival Minutes
service, NGO (ET) and medical equipment to the
incident area
Health Immediate life-saving measures; Discovery of All casualties No casualties Hours
service CCP Take-over of casualties at CCP(s); casualties assessed and at CCPs any
Search for individuals outside registered more
hazard area;
Assessment of all casualties
(triage) and registration;
Initial treatment and stabilization,
preparation for medical
evacuation;
Documentation of findings and
reporting
Health Assessment of casualties (triage) TCC available Most urgent No casualties Hours
service TCC and registration; casualties on their at TCC any
Initial treatment and stabilization, way to hospitals more
preparation for medical evacuation
Health Medical evacuation of casualties Overview of all Most urgent No casualties
Hours
service according to priority. Note: casualties' casualties on their at TCC any
medevac destination hospital has to be priorities way to hospitals more
chosen according to treatment available
capacity and type of injury.
ETSI
16 ETSI TS 103 260-2 V1.1.1 (2015-05)
Table 4.7: Temporary shelter and evacuation
Involved actors Actions Start Intermediate point End point Duration
point
Relevant Transport of emergency First Arrival Arrival Minutes
authority/NGO teams (ET), transport alerting
vehicles, and shelter
equipment to the incident
area
Relevant Provision of temporary Arrival Temporary shelter No non-injured Hours
authority/NGO shelter, psycho-social care available casualties at
temporary shelter temporary shelter
any more
Relevant Evacuation of casualties Arrival No casualties at All non-injured Hours
authority/NGO temporary shelter casualties at shelter
evacuation any more or on their way
home
5 Information exchanges
5.1 General
The response organizations involved in the MTA will include those who are active in the incident area and others who
remain outside of this area (i.e. in the off-site/support area).
Information exchanges arising from the scenario between organizations solely within off-site areas are out of scope as
they are assumed to be satisfied with existing infrastructure, whilst those in the incident area may need additional
emergency communications infrastructure.
Hence this clause firstly defines the information exchanges involving the actors (response entities) defined in
clauses 4.3 and 4.4 within and to/from the incident area.
The overall requirements are compatible with ETSI TS 102 181 [i.1], but this clause defines their specific application to
this scenario.
This clause then describes the characteristics of the information exchanges, based on the actors and actions. Information
exchanges include both physical communications and telecoms services.
Figure 5.1 depicts the organizational hierarchy and its associated lines of communication in a scenario of this type. In
addition, there is a need for communication between these structures and off-site organizations which is shown as
"horizontal" exchanges.
The off-site area comprises:
• Public safety answering points (PSAPs) / emergency control centres (ECCs) for individual (or integrated)
emergency services A, B, C (e.g. fire-fighting and rescue, health service, police) plus assisting PSAPs/ECCs
for support in case of major incidents.
• LEMA represents the local government level and carries out general management and coordination of all
response activities.
• (Inter-)national resources incl. NGOs provide support to the deployed emergency services.
Within the incident area involved emergency services are organized in a hierarchical management structure:
• The CFECC is staffed with a coordinating incident commander or a coordinating task force.
• In most cases for each emergency service 1, 2, 3 there is a dedicated ECC (FECC).
• Dedicated tasks/responsibilities of emergency services can be managed from SECCs which report to the upper
layer FECC.
• Deployed emergency teams (ETs) may be grouped as divisions.
ETSI
17 ETSI TS 103 260-2 V1.1.1 (2015-05)
LEMA
(Local emergency
Management Authority)
Public Safety Answering Point
Service A, B, C
(Inter-)National
Emergency Control Centre
Resources incl. NGOs
Service A, B, C
Assisting
Telecoms
PSAPs/ECCs
Services
Off-Site/Support Area
Incident Area
Coordinating
Field ECC (CFECC)
Service 1 Service 2
ECC (FECC) ECC(FECC)
SubService 1 SubService 2 SubService 1 SubService 2
ECC (SECC) ECC (SECC) ECC(SECC) ECC(SECC)
Sub-
Sub- Sub- Sub- Sub- Sub-
ServiceService ServicSere vice ServicSee rvice
1 1 2 2 1 1
ET1 ET1 ET2 ET1 ET2
ET2
Division n
Division 1
ECC: Emergency Control Centre
: information exchanges
Service e.g. Fire-fighting & Rescue
: Hierarchical links and associated information exchanges
Sub-Service: e.g. Fire-fighting
ET: Emergency Team
Figure 5.1: Responder organizational hierarchy and related information flows
NOTE: Information exchanges solely within off-site areas and arising from the scenario are out of scope as they
are assumed to be satisfied with existing infrastructure.
5.2 Communication needs between emergency management
hierarchies
The hierarchical structure of emergency services requires information exchanges between the management levels as
task descriptions from higher to lower levels and status reports in the opposite direction. All involved decision makers
on all hierarchy levels continuously iterate management and decision cycles, which are depicted in figure 5.2. The main
elements of a management cycle are:
• Obtain task from higher level.
• Observe and/or investigate situation, obtain report from lower level.
• Evaluate situation/resources, plan and decide.
• Act and/or instruct lower level.
• Check and adjust if necessary.
• Report status to higher level.
ETSI
18 ETSI TS 103 260-2 V1.1.1 (2015-05)
task
report
higher level
of hierarchy
check / observe /
investigate
adjust
emergency service
hierarchy level
act / evaluate /
instruct plan /
decide
lower level
of hierarchy
task report
Figure 5.2: Generic management cycle for area of responsibility
A key prerequisite for appropriate decision making is timely acquisition of relevant reports and distributed information
via different communication channels and assembling a common operating picture (COP), which again has to be
processed, distributed, and appropriately presented to involved decision makers and stakeholders.
The management cycle frequencies and associated information exchanges in terms of task descriptions and status
reports depend on:
• Risks to different assets: threat to human life or physical condition vs. threat to animals vs. threat to
environment and properties.
• The level of hierarchy and the sort of task. The closer emergency teams are deployed to the incident/hazard
area, the faster the current situation has to be re-assessed.
Conversely, requirements on performance and reliability of information exchange means are partly driven by the
frequency of the decision cycle.
5.3 Communication needs by action
5.3.1 Emergency management
Generic (qualitativ
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.

Loading comments...