skeleton - docbox.etsi.org · web viewedited by b. wisner and j ... have separate emergency power...

TS 103 260-1 V0.1.2 (2014-10)

Satellite Earth Stations and Systems (SES); Reference scenario for the deployment of emergency

communications; Part 1: Earthquake

TECHNICAL SPECIFICATION

ReferenceDTS/SES-00341-1

KeywordsEmergency, satellite, telecommunications,

earthquake

ETSI

650 Route des LuciolesF-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 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/88

Important notice

Individual copies of the present document can be downloaded from:http://www.etsi.org

The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).

In case of dispute, the reference shall be the printing on ETSI printers of the 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:http://portal.etsi.org/chaircor/ETSI_support.asp

Copyright Notification

No part may be reproduced except as authorised by written permission.The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute yyyy.All rights reserved.

DECTTM, PLUGTESTSTM, UMTSTM and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.3GPPTM and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and

of the 3GPP Organisational Partners.GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.

ETSI

TS 103 260-1 V0.1.2 (2014-10)2

http://portal.etsi.org/tb/status/status.asp

http://www.etsi.org/

ContentsContents 3

Intellectual Property Rights 5

Foreword 5

Introduction 5

1 Scope 6

2 References 6

2.1 Normative references 6

2.2 Informative references 6

3 Definitions and abbreviations 7

3.1 Definitions 7

3.2 Abbreviations7

4 Disaster Scenario9

4.1 Scenario Definition 9

4.1.1 Physical Effects 9

4.1.1.1Collapse of buildings 9

4.1.1.2Fire (F) 9

4.1.1.3Chemical Accident (CA) Error! Bookmark not defined.

4.1.1.4Disruption infrastructure9

4.1.1.4.1 Power 10

4.1.1.4.2 Transport facilities Error! Bookmark not defined.

4.1.1.4.3 Water supply 10

4.1.1.4.4 Sanitation 10

4.1.1.4.5 Telecommunication 10

4.1.1.5Disruption of services Error! Bookmark not defined.

4.1.2 Disaster Response Actions 10

4.1.2.1General 11

4.1.2.2Situation assessment Error! Bookmark not defined.

4.1.2.3Search and Rescue 15

4.1.2.4Triage/ First Aid Error! Bookmark not defined.

4.1.2.5Fire-fighting/ Chemical incidents Error! Bookmark not defined.

4.1.2.6Command and control structures 15

4.1.2.7Logistics 16

ETSI

TS 103 260-1 V0.1.2 (2014-10)3

4.1.2.8Evacuation of population 16

4.1.2.9Emergency shelters Error! Bookmark not defined.

4.1.2.10 Information Error! Bookmark not defined.

4.1.3 Entities involved 10

4.1.4 Quantitative timeline10

5 Information Exchanges 16

5.1 Characteristics of Information Exchanges 17

5.1.1 Communications services requirements 19

5.1.2 Speech services 19

5.1.2.1Point To Point Speech Services 19

5.1.2.2Group Speech Services 19

5.1.2.3Push To Talk (PoC)/Command and Control (C&C) features 20

5.1.2.4Video Tele-Conferencing 20

5.1.2.5Data services 20

5.1.2.6Paging (short message) Services 20

5.1.2.7Status Monitoring and Location Services 21

5.1.2.8FRs – FRs22

5.1.2.9FRs – corresponding CP 22

5.1.2.10 CP – CP 22

5.1.2.11 CP – EATF 22

5.1.2.12 CPs – External entities 22

5.1.2.13 CPs – External information 22

5.1.3 User requirements for Information Exchange 25

6 Topology Model 25

Annex A (informative): Major Recent Earthquakes 26

Annex B (informative): Fictive example scenario timeline 26

Annex <X> (informative): Bibliography 26

7 History 26

ETSI

TS 103 260-1 V0.1.2 (2014-10)4

Intellectual Property RightsIPRs 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.

ForewordThis Technical Specification (TS) has been produced by ETSI Technical Committee Satellite Earth Stations and Systems (SES).

The present document is part 1 of a two-part deliverable.

IntroductionMajor 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 rescue workers to respond and coordinate their activities effectively. Satellites can play a role in replacing or supplementing other 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, and

temporary replacement of broken/saturated infrastructures by means of backhauling

fast deployment of temporary communication networks in emergency situations.

Hence a set of requirements for such links needs to be established in emergency situations.

The work is also a response to EC mandate M/496, specifically dossier 9 "Disaster Management" part 2: “Emergency Telecommunication Services” which aims to support standardisation for the optimal needs of the emergency responders.

The regulations and operating procedures for Emergency Responses varies between Member States e.g. the organisation responsible for the emergency can be the police, the fire and rescue organisation, a dedicated organisation for this purpose (e.g. Civil Protection) or others.

ETSI

TS 103 260-1 V0.1.2 (2014-10)5

1 ScopeThis document defines firstly a disaster scenario. It then defines the gross communication needs of the actors involved without specifying the network technologies involved. Finally the more detailed results of topology modelling of these communications requirements are provided.

The reference scenario for an earthquake is defined in order to allow evaluation and dimensioning of required overall emergency telecommunications, and may also be useful to dimension the needs for satellite-based telecommunications in future.

This scenario includes potential, though not explicit, roles for satellite systems for the telecommunication services identified.

The response services defined for these scenarios are limited to safety-related services (i.e. not security such as law enforcement).

2[1] ReferencesReferences 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 referenced 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.

2.1[1.1] Normative referencesThe following referenced documents are necessary for the application of the present document.

2.2[1.2] Informative referencesClause 2.2 shall only contain informative references which are cited in the document itself.

[i.1] ETSI TR 102 180: "Emergency Communications (EMTEL); Basis of requirements for communication of individuals with authorities/organizations in case of distress (Emergency call handling)".

[i.2] ETSI TS 102 181: "Emergency Communications (EMTEL); Requirements for communication between authorities/organizations during emergencies".

[i.3] ETSI TS 102 182: “Emergency Communications (EMTEL); Requirements for communications from authorities/organizations to individuals, groups or the general public during emergencies”.

[i.4] ETSI TR 102 299: "Emergency Communications (EMTEL); Collection of European Regulatory Texts and orientations".

[i.5] 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.6] ETSI TR 102 476: "Emergency Communications (EMTEL); Emergency calls and VoIP: possible short and long term solutions and standardization activities".

[i.7] ETSI TR 102 641: “Satellite Earth Stations and Systems (SES); Overview of present satellite emergency communications resources”.

ETSI

TS 103 260-1 V0.1.2 (2014-10)6

http://docbox.etsi.org/Reference

[i.8] ETSI TR 103 166: "Satellite Earth Stations and Systems (SES); Satellite Emergency Communications (SatEC); Emergency Communication Cell over Satellite (ECCS)".

[i.9] ETSI TS 103 260-2: “Satellite Earth Stations and Systems (SES); Reference scenario for the deployment of emergency communications; Part 2: Mass Casualty Incident in Public Transportation”

[i.10] Mandates from the European Commission?????

[i.11] ITU-T Recommendation G.1010: End-user multimedia QoS categories

[i.12] ITU-R Resolution 647: Space services emergency database

[i.13] Report ITU-R S.2151-1: “Use and examples of systems in the fixed satellite service in the event of natural disasters and similar emergencies for warning and relief operations”

[i.14] “Environmental health in emergencies and disasters: a practical guide”. Edited by B. Wisner and J. Adams, World Health Organization, 2003.

[i.15] European Union Handbook on assistance intervention in the Frame of community mechanism for the cooperation of civil protection

[i.16]

3[2] Definitions and abbreviationsN.B. All of this clause will be updated/ coordinated with the MTA deliverable when the documents are stable.

3.1[2.1] DefinitionsFor the purposes of the present document, the following terms and definitions apply:

Aftershocks: Smaller earthquakes over the days/ weeks following the main earthquake. These may be sufficiently strong to cause substantial added damage.

Emergency: an event or situation which threatens serious damage to human welfare or to the environment.

Emergency Control Centre (ECC): facilities used by emergency organisations to handle rescue actions in answer to emergency calls

Emergency service: service, recognised 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

Field emergency control centre (FECC): facilities used by emergency organisations to handle rescue actions in the field

Flash flood: A rapid flooding of low-lying areas; washes, rivers, dry lakes and basins. (http://en.wikipedia.org/wiki/Flash_flood)

Hazard area: Area with obvious or supposed threats to physical/psychological health, properties, and/or environment.

Incident area: area where the incident occurred, and/or the area which needs communication coverage to manage the response implemented

Public Safety Answering Point (PSAP): physical location where emergency calls are received under the responsibility of a public authority

Quality of Experience: The overall acceptability of an application or service, as perceived subjectively by the end-user (see notes 1 and 2). (from ETSI TR 126 944)

NOTE 1: Quality of Experience includes the complete end-to-end system effects (client, terminal, network, services infrastructure, etc).

ETSI

TS 103 260-1 V0.1.2 (2014-10)7

Egil Bovim, 05/11/14,

Presently not used in the document

NOTE 2: Overall acceptability may be influenced by user expectations and context.

For the purpose of the present document, QoE is limited to those parameters that are reasonably expected to be under the control of the Service Provider, i.e. it excludes aspects of specific terminal equipment implementation. In the document, the exact E2E measurement point will be defined for each service.

QoE indicates performance metrics as expressed from the end service user's point of view. They can be required or reported by the common users, and may be stated irrespective of their measurability.

In general, a Service Provider will set service requirements in line with the end-user's expected QoE, which needs to be translated into parameters or metrics that the service provider can control or measure. Thus, it is necessary to map QoE metrics to measurable End-to-end Service QoS and System QoS parameters, which provide the means for the service providers to guarantee the service quality.

3.2[2.2] AbbreviationsFor the purposes of the present document, the following abbreviations apply:

CAP Common Alerting ProtocolCEPT Conférence Européenne des Postes et TélécommunicationsECA European Common AllocationECC European Communications CommitteeECC Emergency Control CentreELT Emergency Locator TransmitterEMTEL EMergency TELecommunicationsEPIRB Emergency Position Indicating Radio BeaconETSI European Telecommunications Standards InstituteFECC Field emergency control centreFSS Fixed Satellite ServiceGNSS Global Navigation Satellite SystemGOES Geostationary Operational Environmental SatelliteGPS Global Positioning SystemGSO Geostationary OrbitICT Information and Communication TechnologyIPR Intellectual Property RightISO International Standardisation OrganisationITU International Telecommunication UnionITU-R International Telecommunication Union Radiocommunications SectorITU-T International Telecommunication Union Telecommunications SectorLEO Low Earth OrbitMSS Mobile Satellite ServiceNRBC Nuclear, Radiological, Bacteriological, ChemicalOASIS Organisation for the Advancement of Structured Information StandardsPAMR Public Access Mobile RadioPLB Personal Locator BeaconPLMN Public Land Mobile NetworkPMR Private Mobile RadioPPDR Public Protection and Disaster ReliefPSAP Public Safety Answering PointPSTN Public Switched Telephony NetworkQoE Quality of ExperienceRCC Rescue Coordination CentreRDSS Radio Determination Satellite ServiceSARSAT Search And Rescue Satellite-Aided TrackingSatEC Satellite Emergency Communications Working GroupSCN Satellite Communications and Navigation Working Group SG Study Group

ETSI

TS 103 260-1 V0.1.2 (2014-10)8

SES Satellite Earth Station and SystemsTC Technical CommitteeTETRA Terrestrial Trunked RadioTR Technical ReportTS Technical SpecificationV Voice

ETSI

TS 103 260-1 V0.1.2 (2014-10)9

4[3] Disaster ScenarioThis clause defines an earthquake scenario, firstly in terms of its main constituent events and secondly by its physical consequences. Subsequently the response actions by emergency forces to this scenario are defined in terms of the casualties involved, the actors and organisations, overall operating modes, duration and dimensioning factors etc..

The scenario is sufficiently generic to be considered representative of potential future earthquakes, and thus to allow relevant communication characteristics for current and future needs to be established.

4.1[3.1] Scenario DefinitionA summary of recent earthquakes and their effects is given in Annex A as examples of the scale of events being considered.

The Earthquake is assumed to be of a magnitude sufficient to cause a multitude of physical effects, such as collapsed buildings, disruption of infrastructure, lack of power, lack of telecommunications, fires, risks of chemical accidents etc. Each of these incidents may not differ much from isolated similar incidents of this nature, but the added challenge is that the incidents happen at the same time, thus reinforcing the effects and strains on available resources.

The earthquake hits a city with a total population of 350 000, positioned among mountains in a coastal area, at midday.

Figure X, Disaster scene

A: Sector A, domestic area

B: Sector B, industrial area

C: Sector C, entrance area main road and power line

D: Entrance small road/ bridge

E: Ambulance station, assembly point

F: Medical treatment area Sector A

G: Medicals treatment area Sector B

ETSI

TS 103 260-1 V0.1.2 (2014-10)10

Distances: C to E: 7kms

E to A: 3kms

E to B: 2kms

E to D: 6kms

Give simple diagram showing relationships (incl. approx. distances) of Incident area(s), Hazard area(s), sectors etc. e.g:

The Incident Area: Central parts of the city. Covers an area of appr. 15 x 25 12 kms.

The Hazard AreasSectors: The damage is not evenly spread in the city. Areas of severe damage are defined as hazard areaszones (see figure x)

A detailed description of the incident is provided in Annex X

o Sector A: ……TBD

o Sector B: ……TBD

[1)] Sector C: ……TBD

4.1.1[3.1.1] Physical EffectsThe effects of the earthquake on the population and infrastructure will last for an appreciable time, even many years, but our focus is on the period for which emergency communications are needed. The nature of these consequences is as follows.

4.1.1.1[3.1.1.1] Collapse of buildings

There is a large number of buildings, commercial and domestic (e.g. blocks of flats) in varying state of collapse. One primary school with an enrolment of 340 students is involved.

An initially unknown number of individuals is trapped within the rubble.

4.1.1.2[3.1.1.2] Fire

There are four two separate on-going fires, with a risk of spreading to buildings that have not collapsed

4.1.1.3[3.1.1.3] Disruption of infrastructure

Disruption of infrastructure is partly due to direct effects of movements during the earthquake, but also caused by a considerable landslide which covers buildings, roads etc.

The landslide covers the main road leading into the incident area. Alternative road to the area is via a bridge, which has a weight limit of 3 tons. It is initially unclear whether this bridge has got structural damage.

4.1.1.3.1[3.1.1.3.1] Power

There is a complete loss of power within the area directly hitincident area. As one of the major power lines pass through the area, there is also a reduced power capacity in the city at large. Some critical facilities, e.g. hospitals, have separate emergency power supply, but other facilities are faced with periodical power cuts..

4.1.1.3.2[3.1.1.3.2] Water supply

Water pipes in the affected area have been broken, leading to a total loss of water supply.

ETSI

TS 103 260-1 V0.1.2 (2014-10)11

4.1.1.3.3[3.1.1.3.3] Sanitation

Sewage systems in the affected area have been broken and are non-functional.

4.1.1.3.4[3.1.1.3.4] Telecommunication

Public systems: The fixed line telephony is broken in the affected area, as is fibre connections from other commercial providers. There is a access from some areas to public mobile networks via one base station outside the affected area. Capacity is, however, very limited.

Private mobile radio: The situation is the same as for mobile networks, with extremely limited coverage and capacity.

4.2[3.2] Actors and RolesThis clause defines the aActors and their main roles within the Incident Areain handling the disaster. Depending on local/ national organisation of services and division of tasks/ responsibilities, the entities involved and their individual areas of work may differ.

In addition to their primary roles, actors may participate in other tasks, as shown in table X below

Site management: Coordination of actors and reporting to local/ national authorities, leading the CFECC

Fire and rescue: Securing the hazard areas, fighting fires and searching for individuals

Health services: Triage and treatment of the injured, organising medical evacuation out of the incident area

Police: Public order,

Local authorities: Providing supplies, shelters etc.

Utilities/ Roads departments: Temporary or permanent replacement of destroyed infrastructure

Civil Protection: Registration of individuals, assisting in SAR, treatment of the injured, and re-establishing of infrastructure.

Military forces: As for Civil Protection above.

NGO/ Voluntary organisations: Depending on the incident, these may have a wide variety of roles, typically assisting the public services which are in place.

Media/ Individuals: Have no specific role in the handling of the incident, but may to a considerable degree influence the availability of communication systems (e.g. media using satellite communication for streaming)

List groups or “Entities” involved and their general roles (but not specific to this scenario).

Individuals, media etc. to be included under one topic. Not considered as a requirement for comms needs but may impact overall needs.

Individuals (no role or action?)

Non Governmental Organisations (NGO)

The term NGO covers a wide variety of entities. Most activities in big disasters may be taken care of by public bodies (e.g. SAR, medical services) and NGOs working together. NGOs will typically bring their own communication systems, or base their telecommunication on public services like GSM. For their operational work their communication needs will not differ greatly from those of the public services who they replace or with whom they share roles. In

ETSI

TS 103 260-1 V0.1.2 (2014-10)12


This section describes largely the same as the table “entities involved” further down. Would it be against ETSI rules to have the table as the main content of the section?

addition, the NGOs may want to establish their own communication links to their mother organisations outside the Incident Scene. This may be done both using mobile networks, or satellite systems.

CFECC

Depending on national regulations, a Coordinating Field Emergency Control Centre will be established

The role of CFECC is to coordinate the efforts made by the different actors within the Incident Scene. CFECC normally acts as the main communication body with central authorities, and will report on issues like number of casualties, needs for resources etc. to central authorities. Individual services will normally also communicate with their professional bodies on purely professional issues.

Implementation of emergency control structures is a major task which puts great demands on telecommunication systems at a stage where these will be under considerable strain or broken down.

4.3[3.3] Disaster Response ActionsThe actions of the Actors (defined in 4.2 above) in the Incident Area of this particular scenario are further defined below including overall duration for each action. For timelines see annex X

Time 0 corresponds to midday as the time of the actual earthquake.

Overall duration for each Action to be defined, but details to be included in Annex for reference by and purposes of modelling if needed.

For each action, list who is involved, start, intermediate and end points.

Despite detailed information being hard to get at, personnel on duty with the emergency services are alerted by the respective ECCs via the respective services´ PMR. General alerts are submitted in accordance with existing plans, via SMS.

The area consists of blocks of flats, one primary school, a shopping centre and a diversity of small-scale industry. There is one ambulance station within the affected area, but no police or fire/ rescue stations. The population of the affected area is 4 500. The actual number present in the area at the time of the earthquake is unknown.

4.3.1[3.3.1] Initial AlertingMembers of the public calling PSAPs via national emergency numbers or the pan-European emergency number 112. normally provide the initial alerting of incidents/ disasters. In this particular case the emergency number will have very limited functionality within the incident area.

The initial alerting starts immediately, and should be completed within 30-40 minutes. The PSAP will, however, stay busy for the whole duration of the handling of the earthquake as members of public will tend to use emergency number for update later as well.

Time line:

0 min: Although located outside the affected area, the personnel on duty at the ECCs notes the earthquake. Operational staff is notified via pre-set procedures that they should be on the alert, and routine tasks (e.g. non-critical patient transports) be postponed till further notice.

15 min: Ambulance staff at the station within the affected area reports to ECC that there are substantial damages, and ask for additional resources to be sent to the area

15 min: ECC health notifies other ECCs, emergency services resources dispatched to incident scene

25 min: F&R team reports on blocked main road, only light vehicles to be dispatched till further notice.

30 min: Central authorities make request for geological expertise to evaluate the landslide.

ETSI

TS 103 260-1 V0.1.2 (2014-10)13


All of this is too detailed - move to response actions. Start with a general overview of the scenario – a diagram is needed, then define necessary details

30 min: Ambulance helicopter arrives on scene. Before landing it makes a round over the affected area, taking video which is transferred to the health ECC and from there to relevant authorities.

[3.3.2] Assessment of Situation and Need for Resources

Assessment of The overall responsibility lies with the site management. The assessment will start immediately the first indications of an incident/ disaster are presented, and last for the entire handling of the disaster. Before emergency control structures (section X below) are in place, the actors who are involved, in the case of this scenario PSAP/ ECCs and ambulance on site, make the assessments. Site management will need assistance from specialist entities like roads departments, geologists etc.

4.3.2 T transport access

Although not being counted as an emergency services, Roads department will play an important role in this scenario. Re-instating the main road will depend on geological survey, which will take time, so the first priority is to assess the situation on the bridge with weight limitation.

In addition to re-instating roads, there is a need for establishing landing areas for helicopters.

This work will start within 30-60 minutes from the earthquake and last for days.

Include bridges, helipad, etc.

Time line:

30 min: Request from central authorities to Roads department to assess the capacity of the remaining bridge

50 min: Assessment team on site, taking photos and submitting them to central roads department.

65 minutes: Conclusion: The weight limit raised to 12 tons, subject to traffic regulation (only one car at the time).

135 minutes: Reparative work on landslide initiated, but made difficult by risks of further landslides.

8 hours: Work on landslide stopped as it gets dark and it is no longer possible to continuously assess the risk for further landslides.

19 hours: Work on landslide is started again. Assistance from defence forces engineers.

23 hours: Main road opened for limited traffic.

[3.3.3] Assessment and handling of (Specific) RisksThe landslide, which represents both a scene of damage to individuals and structures, and a barrier for rescue work, has to be dealt with. Risk assessment for further damage has to be carried out by expert on geology. Such expertise is typically only available at a limited number of locations.

A complete inventory of injured structures is a priority. This has to be mapped against registers of dangerous substances etc., kept by the owners of the structures.

Defining hazard areas is also an on-going task. Risks that need to be assessed include

- Dangerous substances (including exposure to chemical substances)- Additional collapse of buildings/ landslides etc.- Pollution/ contamination of water sources

Assessment of specific risks will be most resource demanding in the initial phases, but last for the whole period of the handling of the disaster.

ETSI

TS 103 260-1 V0.1.2 (2014-10)14

Once a specific risk has been identified, actions are taken to reduce it to a level where it is safe to perform rescue work. The site management has the overall responsibility for this. Specialists carry out the actual work, initially Fire and Rescue, but with assistance from other specialists as needed in each case.

Include dangerous goods etc.

Time line:

30 min: Expertise requested

90 min: Arriving on scene, pictures to be submitted

120 minutes: Conclusion, advise for reparative work provided.

[3.3.4] Implementation of Emergency Control StructuresOnce the individual emergency services (F&R, police, health) arrive on scene, they will will establish Site Emergency Coordination Centres (SECCs), normally staffed with the most senior memberssenior members of staff on scene at the time. The service in responsible for coordination of services will establish CFECC. Members of SECC will normally represent their services in the CFEEC.

CFECC consists of senior representatives for the various services involved, such as Fire and rescue, Health, Police etc. and is the main point of contact for regional/ national authorities, even though the ECCs will also normally communicate with their own control rooms outside the incident area.

Once ECCs and CFECC are established, they will stay active for the whole duration of the handling of the disaster.

As the resources are limited, it is decided that the ECCs and CFECC are established close to the ambulance station (see fig X)

List who is involved, start, intermediate and end points.

Implementation of emergency control structures is a major task which puts great demands on telecommunication systems at a stage where these will be under considerable strain or broken down.

CFECC

Timeline:

45 min: Limited number of staff from all rescue services present, CFECC established.

47 min: A preliminary situation report (V) is submitted to authorities; procedures and links for communication to SECC are established. Updates and requests are made to authorities continuously for the next two hours.

60min: Written situation report in accordance with premade plans is submitted to authorities, updated every hour for the first 24 hours.

90 min: Videoconference with authorities, pictures from scene submitted. Videoconference between members of CFECC and authorities planned for every 2 hours.

100min: Preliminary report on needs for water/ sanitation/ food/ shelter is submitted to authorities

115 minutes: Local “air traffic control” established, landing area for helicopter appointed. Ambulance helicopters arriving every 15 minutes, airlifting patients out of incident scene.

120 min: Generators and tents are brought in, are distributed between services and set up.

150 min: Plans for evacuation of non-injured individuals are set up, transport resources asked for.

3 hours: Situation report: No/ minor injuries: Not known, local treatment only 127, need for hospital treatment 235, dead 15.

ETSI

TS 103 260-1 V0.1.2 (2014-10)15

4 hours: Food and water is brought in and distributed to the rescued and to the rescue teams. Supplies are to arrive every 3 hours, following specified requests from CFECC

6 hours: Lists prepared on staff rotation, the responsibility for ensuring that so happens lies with the service EECs, but reports are made to CFECC.

9 hours: Situation report: No/ minor injuries appr 600, local treatment 212, need for hospital treatment 320, not accounted for: not known.

10 hours: Re-enforcement from NGOs from outside the city, assisting in supplying water/ food.

[3.3.5] Fire fighting and rescue Fire and Rescue services are the main responsible bodies for fire fighting and SAR. However, depending on the size of the incident, and local decisions, other services, such as Civil Protection, Military, NGOs and voluntary organisations will also participate. The initial activity will be to reduce risks for (further) personal injuries. The activities include fire-fighting, measurement/ containment of hazardous material/ dangerous substances, securing of collapsing buildings etc. Once an area is declared safe, search and rescue will be initiated. F&R will provide limited first aid; the main activity is to transport casualties to where the medical services take over. The initially limited access to the incident area provides serious limitations to the activities, particularly in terms of fire fighting.

This activity will also continue for the whole duration of the handling of the disaster.

Timeline:

30 min: First team (4 persons) arrive on scene, reports to ECC (V), starts surveying the scene and reports continuously to ECC for the next hour. Pictures of the scene are sent to the ECC.

35 min: Fire trucks are dispatched to scene, but awaiting permission to cross the bridge

40 min: Additional 8 officers arrive on scene; SECC is established and reported to ECC

45 min: Delegate to CFECC is appointed

50 min: SECC is overwhelmed by survivors, police summoned to keep order.

65 min: 8 fire trucks with personnel and equipment arrive on scene and start fire fighting.

70 min: Smoke divers prepare for action, 2 of them have helmet cameras which can submit streaming video.

75 min: Part of the stricken area is declared safe. Reported to CFECC who reports to authorities

80 min: Building plans for collapsed buildings are requested from central authorities.

95 min: SAR teams, each of 2 officers, is established and search is starting.

105 min: 15 individuals are evacuated and taken over by medical services.

120 min: Dead people are located.

120min: Specialist team (building surveyors) arrive on scene. Their task is to control and if necessary, take steps to make areas safe for rescue work. They communicate to central authorities (via SECC/ CFECC) sending and receiving building plans and pictures.

2 hours 30 min: 80 volunteers from Red Cross arrive, and are set to work on SAR.

3 hours: 6 teams (NGO) with rescue dogs arrive on scene and start their work in the areas so far declared safe.

5 hours: Surveyors have checked collapsed buildings, cleared 10 but decided that 4 blocks of flat and the primary school needs further work to be declared safe. Specialist workforce is requested via CFECC

6 hours: Fire trucks from other services arrive and assist

7 hours: Fires are terminated, all efforts now on search and rescue

7 – 20 hours: Search and rescue activities continues throughout the night, but at a lower rate due to darkness.

ETSI

TS 103 260-1 V0.1.2 (2014-10)16

23 hours: With the opening of the road, heavy equipment is brought in for securing buildings etc.

4.3.3[3.3.6] Treatment of CasualtiesTreatment of casualties is started on scene, and in many cases patients are then submitted to health care facilities outside the incident area.

4.3.3.1 First Aid

Initial first aid is carried out by whoever locates the individual. SAR-workers are normally trained in lifesaving first actions (e.g. free airways). As soon as possible after the earthquake health personnel will arrive in the incident area, and temporary treatment centres will be established. This work starts immediately, and is continued for as long as more survivors are found.

4.3.3.2 Minor injuries

Depending on available resources individuals with minor injuries will either be treated on site and then evacuated together with un-injured, or they will not get any treatment but be advised to seek assistance for themselves once they are out of the incident area.

4.3.3.3 Medical Evacuation

Patients needing further treatment will be evacuated by ambulance, helicopter or other vehicles equipped for the purpose.

The logistics concerning medical evacuation in big disasters are demanding. The number of casualties typically exceeds the capacity of local hospitals, and a referral chain involving several health facilities outside the incident area has to be established and implemented.

Medical evacuation will start within an hour after the earthquake. The highest number of casualties will be identified within 4-5 hours, after which time the number will go down. As there are difficulties with access, medical evacuation will go on for the first 24 hours. This task is carried out by health personnel, with assistance of representatives from NGOs and military.

4.3.3.4 Deaths

Health personnel are responsible for declaring individuals for dead. Civil Protection will establish a facility for the dead within the incident area. Establishing the facility is done as soon as it is known to be needed. Transporting the dead out of the incident area will have lower priority than medical and other evacuation.

4.3.4 Health

In an earthquake of this magnitude, health care provision will be a priority, but the resources available will be far from sufficient. The local health services will need assistance from other regions, and in severe cases even internationally.

Timeline:

0 min: Ambulance station hit by earthquake. Garage broken down, vehicle rendered inoperative. Means of communication lost.

15 min: Preliminary assessment made, officer moved to site with PMR coverage and reports to ECC, requesting resources.

30 min: Ambulance helicopter arrives on scene. Before landing it surveys the stricken area, submitting streaming video to health ECC.

40 min: 3 more ambulances (6 officers) arrive on scene. Temporary SECC is established (awaiting arrival of officer who is to permanently run SECC).

ETSI

TS 103 260-1 V0.1.2 (2014-10)17

45 min: Trailers with emergency medical equipment dispatched, waiting at bridge.

45 min: Reports to CFECC, locations for triage/ treatment are established, and treatment started. Medical services overloaded, repeat request for more resources.

60 min: Continuous reporting to CFECC (Numbers and names of patients)

70 min: Hospital team (8 officers) and leader SECC are brought in by ambulance helicopter, starts working with the injured.

75 min: Ambulance manager and First aid manager are appointed, report continuously to SECC

90 min: Another 4 helicopters are brought in and continue airlifting patients to hospital.

120 min: Direct communication link between treatment area and hospital is set up (V+D). The local hospital is overloaded; plans for further evacuation are made, and system for reporting of patients from the Incident Scene is established in collaboration with CFECC

3 -5 hours: 10 ambulance teams from other hospitals arrive on scene, medical evacuation continues by road and by air.

7 – 20 hours: Patients continue to be brought in.

22 hours: The number of patients being brought in is now lower than the day before, but the patients who do come, tend to have more serious injuries. Consultations with hospitals, both local and specialised, are done via Video conferencing.

[3.3.6.1]

4.3.5[3.3.7] EvacuationIn this scenario, where there is a rather well defined incident scene surrounded by areas with functioning services, evacuation out of the incident scene will be done. With only one access route for the first hours, this is going to be a challenge in itselfsubstantial challenge. The responsibility for evacuation lies with Local Authorities and Civil Protection. Once systems have been established, and the road is passable, evacuation out of the incident area should be completed in 1 days.

Evacuation of injured individuals; (“medevacs”) will be the responsibility of the health services. This section deals with evacuation of individuals who are either not injured, or have minor injuries that have either been dealt with on scene, or will be dealt with by health services outside the directly hit area.

Timeline:

60 min: System for registration of individuals able to walk and report is set up.

65 min: Request for transport is forward via CFECC to authorities.

90 min: The request is re-enforced and specified; the need is for small vehicles who can transport people to the access bridge, from where they should be transported further in bigger buses to areas decided and prepared by the authorities.

150 min: Small vehicles arrive and start evacuation

2 hours+++: Registration and evacuation is on-going, continuous reporting made to CFECC who forward the reports to authorities.

[3.3.8] Provisions

4.3.5.1[3.3.8.1] Power

In most MSs the responsibility for power supply lies with power corporations. The ownership differs between fully authority owned units to private companies. Regardless of the ownership, the power corporations have responsibilities and will have plans for replacement of power in disasters. Civil protection will also have resources and responsibilities in this situation.

The lack of power is an important obstacle to efficient rescue work. The corrective matters are as follows:

ETSI

TS 103 260-1 V0.1.2 (2014-10)18

Timeline:

120 mins: First generators are brought in, more are requested for.

180 mins: System for regular supply of fuel for generators established, dedicated personnel responsible for maintaining control and ensuring that they are in working order.

4 hours: More generators and lighting equipment arrives from outside the city.

5 hours: Mapping of damages completed and reported via CFECC to power provider.

24 hours: Staff and equipment in place, start working on emergency supply to most critical areas.

27 hours: Limited power supply available. Power supplies will be seriously affected in a major earthquake. Intermediate measures, like supply of generators, will start within 2-3 hours. Priority is given to basic power-supply to mission critical installations, such as treatment centres and shelters. Initially power will be supplied via generators, which are brought in.

Restoration of power supply will start within a couple of hours from the earthquake. Supply chains for fuel to generators have to be established, and temporary cabling etc. made available. Permanent repair of broken infrastructure will take time (weeks/ months) and start when the area is declared safe.

4.3.5.2[3.3.8.2] Water, Food and Sanitation

Wheras food supply normally is the responsibility of private companies, the responsibility To provide safe water supply and food is a priority.

Timeline:

90 min: Request made as part of the regular videoconference between CFECC and authorities.

4 hours +++: Drinking water (bottled) and emergency food brought in and distributed to both casualties and rescue workers. System established for continuous supply, based on requests from CFECC. Initially authorities provide the service, but the work is gradually taken over by NGO. for supply of water and sanitation varies between MSs between private and public actors.

All these supply chains will be broken in earthquakes. The responsibility will be taken over by public entities, the actual work carried out by public services (Civil protection, local authorities) with assistance from NGOs.

The supply chains will be established during the first 5-6 hours, and will be functioning for as long as there are casualties within the incident area.

[3.3.8.3] Sanitation

The need for latrines, toilet paper, facilities for hand wash etc. will become evident at an early stage. The Municipality has a pre-arranged agreement with a private supplier.

Timeline:

90 minutes: The need for pit latrines etc. is made clear from CFECC in the conference, Municipal authorities activate the plan as formerly laid out.

4 hours: The first truck loaded with the equipment arrives at the bridge, and receives a description from CFECC as to where the latrines are to be positioned.

7 hours: The pit-latrines are in place

7hours +++: The provider maintains the latrines, empties them bringing the sewage out of the area etc. Reports are made to CFECC as agreed in plan.

[3.3.8.4] Temporary Shelters

Despite the priority being on evacuating casualties out of the incident scene, there will be a need for temporaryl shelter, as the transport capacity, both medical and non-medical, will not be able to meet the need. The prime responisibilty lies with the local authority. In big disasters the local authorities will not have sufficient resources, and assistance will be provided by central authorities (civil protection, defence forces etc) and NGOS

ETSI

TS 103 260-1 V0.1.2 (2014-10)19

Like for other provisions, the needs for temporary shelters will be identified by the incident site management within 1-2 hours, and requests for assistance will be forwarded to central authorities. The establishment of shelters will start on site within 12 hours, and the activity will increase over the next 24 hours till the needs are met. The shelters, like the other provisions, will have to be maintained for as long as there are casualties in the incident area. Temporary shelters (tents) are provided by defence forces and NGOs.

Timeline

90 min. Need for shelters is discussed in videoconference, supplied by written report at 100min Central authorities forward the request to defence force and NGOs.

3 hours: An inventory of available tents/ personnel to set them up and possible times of arrival are received by CFECC, plans made for deployment within incident area.

5-18 hours: Tents arrive and are set up.

[3.3.9] Maintenance of Public Order The responsibility for maintaining public order lies with the police. Other services, e.g. civil defence, military defence, and NGOs will be brought in for assistance, but they will be working under the leadership of the police. A major earthquake with widespread injuries to individuals and infrastructure causes disruptions of social structures, and risk for disturbances to rescue work.

Maintenance of public order will be initiated within 2 hours of the disaster, and be maintained for as long as there are restrictions on entry to the incident area, i.e. for weeks/ months. This could be caused by individuals searching for their relatives, criminal elements and onlookers (including representatives of media). It is paramount that access to the Incident Scene is controlled. Police will normally establish a SECC within the Incident Scene. The overall command, however, will lie with the Police ECC.

Timeline:

30 min: 2 officers arrive on scene, reports to ECC, requesting more resources (V)

45 min: Reports to CFECC

50 min: Summoned to SECC F&R where a large group of people have gathered demanding assistance and information. Information is submitted contiuouslycontinuously to CFEEC who submits the reports to the authorities every 30 minutes.

55 min: 10 more officers arrive on scene. SECC is established, teams of 2 officers start securing and patrolling the area. All officers connected by PMR. For the first 12 hours each officer is on the radio with the SECC at an average of 2 minutes per hour.

60 minutes: System for registration of individuals able to walk and report is set up.

75 min: 16 more officers arrive on scene. The area is cordoned off and patrolled. System for access control, registering who enters and leaves the area is established, information conveyed continuously to authorities via CFECC. Traffic control at bridge is established

90 minutes +++: Congestion at the bridge (entry point), police make a priority list and officers are there to guide the traffic.

5 hours: Additionally 30 officers from neighbouring forces arrive on scene.

7 hours: 120 officers from national forces arrive on scene.

[3.3.10] Information Services

4.3.5.3 Individuals

Non-injured victims, bystanders and individuals who are outside the incident area all will want and need information on the incident. In addition to general news which are submitted via media, many will need more specific information.

ETSI

TS 103 260-1 V0.1.2 (2014-10)20


I understand now that the whole of this section falls outside the scope. I have to admit that I find that odd, but the bosses are the bosses, and they are right, even if they are wrong!

Examples will be information about friends and relatives with whom they have lost contact, information on damage to properties etc.

An information centre will be set up outside the incident area, with the responsibility to communicate via websites, social media, email, phone etc. More specific services, like “I am alive” may be set up.

The responsibility for information lies with the authority in charge of handling the incident. The information systems are set up in accordance with plans within 3 hours after the disaster, and will last for as long as the handling of the disaster is on going.

4.3.5.4 Media

Media do not constitute an actor in emergency handling, but have a role to play in providing general information to the society at large. The authority in charge of handling the disaster will also be responsible for coordinating the relations with the media. This work will start within 2 hours after the disaster, and will go on throughout the handling of the disaster.

In big disasters media is an important user of public communication systems, particularly satellite systems. This may lead to problems for the emergency services, as the capacity is limited.

Non-injured victims, bystanders, journalists, etc.

[3.4] Not to be considered for Information flow requirements.Actors/Actions Summary

The table below summarises the correspondence between the defined Actors and the Actions.

ETSI

TS 103 260-1 V0.1.2 (2014-10)21


The word “correspondence” may be seen as meaning “communication” or “information exchange”. Any suggestions for a better expression?

X: Overall responsibility for the action

ETSI

TS 103 260-1 V0.1.2 (2014-10)22

a: Assisting in the action

Modify table according to roles and actions defined above.

Add table(s) with order of magnitude quantities of personnel for separate actions as necessary

5[4] Information ExchangesThis clause firstly defines the information exchanges involving the actors (entities) defined in clause 4.2 and 4.3 within and to/from the Incident Area.

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.

This clause then describes the characteristics of the information exchanges, based on actors and actions. ………..

5.1 Earthquake scenario information flowsThis clause defines the overall user requirements for information exchange followed by a description of the necessary services.

The diagram below describes……………..

Figure 5-1: Earthquake scenario organisational hierarchy and related information flows

ETSI

TS 103 260-1 V0.1.2 (2014-10)23


Organisation of chapter according to Michelle:5 Information exchangesOverall requirements, diagram+ text (cf. MTA document)5.1 User Requirements for information exchangetext : General considerations, describes the overall reqs for user info exchange5.2 Communication Needs by Actions EQ/MTA scenario information flows (one sub-section per action) - Tables with Source-to-destination Communications needs 5.3 characteristics of information exchanges

This scenario assumes multi-disciplinary rescue teams: for example Discipline A (Fire& Rescue team), Discipline B (Health and medical emergency team) and Discipline C (police or public order forces).

The Off-site Actors and their roles are shown but are not further detailed below.

ETSI

TS 103 260-1 V0.1.2 (2014-10)24

5.2 The general flows of information exchanges are common to the Emergemcy Scenarios in Parts 1 & 2 of this specification and are shown in Figure 5-2 below.

[4.1] RJM: Reference to EMTEL???

[4.2]

[4.3]

[4.4] Figure 5-2: Earthquake scenario information flows

[4.5]

[4.6] This scenario has multi-disciplinary rescue teams: for example discipline A (Fire& Rescue team), Discipline B (Health and medical emergency team) and Discipline C (police or state armed forces).

[4.7] User requirements for information exchangeFirstly general consideration then requirements between incident area and off-site support area, before it goes on to look at the needs for information exchange per Action. n…..

ETSI

TS 103 260-1 V0.1.2 (2014-10)25

5.2.1 General considerationsApart from user requirements on performance and reliability of information exchange the most important aspects of communication equipment to be used by emergency services are:

Functionality in terms of capability, compatibility, interoperability, security and safety;

Usability, i.e. hardware considerations, ergonomics, and user interface;

Supportability in terms of sustainability, configurability, and modularity.

These requirement categories are listed for completeness only since their description is beyond the scope of this specification.

All involved decision makers on all levels of the incident management hierarchy continuously iterate decision cycles, which can be considered as information processing. The main elements of a decision cycle are:

(obtain task);

Investigate/check situation;

Evaluate situation/resources and plan;

Decide;

Act and/or instruct;

(report status).

A key prerequisite for appropriate decision making is timely acquisition of distributed information via different communication channels and assembling a common operating picture (COP), which again has to be processed, distributed, and adequately presented to involved stakeholders.

The decision cycle frequency is influenced by various factors. As a rule of thumb, the frequency depends on the risks to different assets: threat to human life or physical condition vs. threat to animals vs. threat to environment and properties. Conversely, requirements on performance and reliability of information exchange means are partly driven by the frequency of the decision cycle.

Generally, information exchange based on voice has several distinct (dis-)advantages:

Intuitively way of exchanging information, even in stressful situations; high interactivity;

No eye-contact needed; sending/receiving information are not exclusive tasks;

Simple (unidirectional) one-to-many communication;

Robust, but limited information exchange rate;

Not suitable for synchronising data (e.g., lists) between several parties.

The following sections list qualitative requirements for different information types and services.

Use separate table (as below) for each Action

5.2.2 Between incident area and Off-site support areaSource to destination(s)

Type of information Service Requirements

CFECC/FECC to ECC status reports, demand notification voice speech intelligibility/quality, call setup time, end-to-end delay

ECC to CFECC/FECC tasks, allocated resources voice speech intelligibility/quality, call setup time, end-to-end delay

CFECC/FECC to ECC common operating picture data data integrity, data timeliness

ETSI

TS 103 260-1 V0.1.2 (2014-10)26


The relationship with NGOs seems to be missing here. Communication with NGO management will be at authority level, whereas there is a communication at field management level (for the lack of a better word) level between the CFECC and NGO field management. On operational level there needs to be a communication between SECC and the field personnel, I have included that in each of the actions tables in 5.3, as personnel from NGOs working in the field (e.g.SAR) will be coordinated by the relevant SECC.

(minutes), medium throughput

ECC to CFECC/FECC common operating picture

background information (e.g., construction plans, maps/GIS, manuals, guidelines, information on relevant infrastructure etc.)

data data integrity, data timeliness (minutes), medium to high throughput

ICC to/from hospital or telemedicine centre

telemedicine applications multi-media

setup time, constant quality, integrity, high throughput

5.2.3 Within incident area

5.2.3.1 Emergency service disciplines

Source to destination(s) Type of information Service Requirements

emergency teams/officers to SECC

status reports, availability, constraints, demand notification, risks

voice (group call)

speech intelligibility/quality, call setup time, end-to-end delay

emergency teams to team officer/SECC

PPE parameters data data integrity, data timeliness (seconds), low throughput

SECC to emergency teams/officers

tasks, allocated resources voice (group call)


SECCs to SECCs task coordination, availability, constraints, demand, risks

voice (group call)


SECCs to SECCs common operating picture data data integrity, data timeliness (minutes), medium to low throughput

SECC to FECC/CFECC status report, demand, availability, constraints, risks

voice (group call)


FECC/CFECC to SECC decisions, deployment area, tasks, resources to be used, risks

voice (group call)


SECC to FECC/CFECC common operating picture data data integrity, data timeliness (minutes), medium to low throughput

FECC/CFECC to SECC common operating picture data data integrity, data timeliness (minutes), medium to low throughput

Note: The hazard area(s) are not considered as having separate user requirements from the above, but the QoE requirements may be higher.

5.3 Communication needs by Action

1. 5.3.1

Inital alertingNote: Communication between members of the public and PSAP falls outside the scope of this TS

Source to destination(s)

Type of information Service Requirements

ETSI

TS 103 260-1 V0.1.2 (2014-10)27


This may either be a section in this chapter, or the wording may be worked into section 4.2 above.

PSAP to ECC Relay information from callers: Situation assessment, numbers of injured etc.

Voice

(1 to 1 or

group call)


PSAP to ECC GIS information, Caller line ID Data data integrity, data timeliness (seconds), low throughput

5.3.2 Assessment of Situation and Need for ResourcesSource to destination(s) Type of information Service Requirements

Emergency teams/officers to respective ECCs

(Initial phase, before SECC/CFECC have been set up)

Status reports Voice (group call?)

Speech intelligibility/quality, call setup time, end-to-end delay

Emergency teams/officers to respective ECCs


Status reports (Position, pictures, reports in pre-planned format and content)

Data Data integrity, data timeliness (seconds), low throughput/ video streaming

Respective ECCs to emergency teams/officers


Tasks, allocated resources Voice (1 to 1 or

group call)


Respective ECCs to emergency teams/officers


Status reports/ tasks/ allocated resources

Data

Emergency teams/ officers to SECCs

Status reports Voice (group call?)

See individual actions

Emergency teams/ officers to SECCs

Status reports Data See individual actions

SECCs to emergency teams

Status reports/ allocation of tasks voice

(1 to 1/

group call)

See individual actions

SECCs to emergency teams

Status reports/ allocation of tasks Data See individual actions

SECCs to CFECC Status reports, requests Voice

SECCs to CFECC Status reports, requests (pre-planned forms and intervals/ ad hoc)

Data

ETSI

TS 103 260-1 V0.1.2 (2014-10)28

CFECC to SECCs Status reports, allocation of tasks Voice

CFECC to SECCs Status reports, allocation of tasks Data

CFECC to Authorities/ ECCs

Status reports/requests Voice

CFECC to Authorities/ ECCs

Status reports, requests (pre-planned forms and intervals/ ad hoc)

Data

Authorities/ ECCs to CFECC

Status reports, allocation of tasks Voice

Authorities/ ECCs to CFECC

Status reports, allocation of tasks Data

CFECC to all units Emergency messages Voice (broadcast)

5.3.3 Transport AccessSource to destination(s) Type of information Service Requirements

Assessment team/ site management (roads) to central authority (roads department)

Status reports/ requests Voice

Assessment team/ site management (roads) to central authority (roads department)

Status reports (pictures)

Data

Central authority (roads department) to assessment team/ site management (roads)

Tasks, allocated resources

Voice speech intelligibility/quality, call setup time, end-to-end delay

Central authority (roads department) to assessment team/ site management (roads)

Status reports, maps, overview resources

Data

Site management (roads) to road workers teams

Status reports/ allocation of tasks

Voice

(1 to 1/ group call)

Road workers teams to site management (roads)

Status reports/ requests Voice speech intelligibility/quality, call setup time, end-to-end delay

Site management (roads) to emergency team (public order)

Status reports/ requests (e.g. traffic control)


Emergency team (public order) to site management (roads)

Status reports/ requests (e.g. traffic control)

Voice

Site management (roads) to CFECC Status reports/ requests Voice

Site management (roads) to CFECC Status reports/ requests Data data integrity, data timeliness (minutes), medium to low throughput

CFECC to site management (roads) Status reports/ tasks Voice

CFECC to site management (roads) Status reports/ requests Voice data integrity, data timeliness

ETSI

TS 103 260-1 V0.1.2 (2014-10)29

(minutes), medium to low throughput

Site management (roads) to defence engineers

Status reports/ task allocation

Voice

Site management (roads) to defence engineers

Status reports/ site information

Data data integrity, data timeliness (minutes), medium to low throughput

Defence engineers site management (roads)


Defence engineers site management (roads)

Status reports/ site information


5.3.4 Assessment and handling of (Specific) RisksSource to destination(s) Type of information Service Requirements

Geology expertise to CFECC Status reports, requests Voice speech intelligibility/quality, call setup time, end-to-end delay

Geology expertise to CFECC Status reports, e.g. pictures Data data integrity, data timeliness (seconds), low throughput

CFECC to geology expertise Status reports, task allocation


CFECC to geology expertise Site information, maps, pictures

Data

Geology expertise to central authority (geology)

Status reports, requests Voice speech intelligibility/quality, call setup time, end-to-end delay

Geology expertise to central authority (geology)

Status reports, e.g. pictures Data data integrity, data timeliness (seconds), low throughput

Central authority (geology) to geology expertise

Status reports, task allocation


Central authority (geology) to geology expertise

Site information, maps, pictures, access to

databases

Data

Building surveyors to CFECC Status reports, requests Voice

Building surveyors to CFECC Status reports (premade forms), pictures


CFECC to building surveyors to

Status reports, requests Voice

CFECC to building surveyors to

Status reports Data data integrity, data timeliness (minutes), medium to low throughput

Building surveyors to local authorities

Requests (General information/ drawings etc.)

Voice

Building surveyors to local authorities

Requests (General information/ drawings etc.)


ETSI

TS 103 260-1 V0.1.2 (2014-10)30

Local authorities to building surveyors

Information, requests Voice

Local authorities to building surveyors

Drawings/ plans/ access databases


5.3.5 Implementation of Emergency Control StructuresCovered in the tables in sections 5.2.2 and 5.2.3

5.3.6 Fire fighting and RescueSource to destination(s) Type of information Service Requirements

ECC to emergency teams/ officers (before SECC has been established)

Dispatching Voice Speech intelligibility/quality, call setup time, end-to-end delay


Dispatching (Computer aided dispatch)

Data Data integrity, data timeliness (seconds), low throughput

Emergency teams/ officers to ECC (before SECC has been established)

Status report, requests for resources

Voice Speech intelligibility/quality, call setup time, end-to-end delay


Status report (location/ numbers and description of casualties/

pictures etc.)


SECC fire to emergency teams/ officers

Tasks, allocated resources Voice

(1 to1/ group call)


SECC fire to emergency teams/ officers

Tasks, allocated resources (Pre-prepared forms)

Data

Emergency teams/ officers to SECC fire

Situation reports, requests Voice Speech intelligibility/quality, call setup time, end-to-end delay

Emergency teams/ officers to SECC fire

Status report (location data/ pictures etc, streaming video (smoke divers))

Data

SECCs to NGO emergency teams

Status reports, allocation of tasks

Voice

(1 to 1/ group calls)

NGO teams to SECC Status report, requests Voice

(1 to 1/

group call)


Emergency teams/ officers to emergency teams/ officers

Common operational picture/ sharing of information


ETSI

TS 103 260-1 V0.1.2 (2014-10)31

(1 to 1/

group call)

5.3.7 Treatment of CasualtiesNote: Emergency teams in health include personnel at ambulance cars, ambulance helicopters and triage/ first aid/ treatment points.












pictures etc.)


SECC health to emergency teams/ officers

Tasks, allocated resources/ destinations of patients

Voice (1to 1/

group call)


SECC health to emergency teams/ officers


Data

Emergency teams/ officers to SECC health


Emergency teams/ officers to SECC health

Status report (location data/ pictures etc, streaming video

Data

SECCs to NGO emergency teams Status reports, allocation of tasks

Voice


NGO teams to SECC Status report, requests Voice (1/1

group call)


Emergency teams/ officers to emergency teams/ officers

Common operational picture/ sharing of information

Voice

(1 to 1/

group call)


Emergency teams/ officers to external resources (hospitals)

Status reports, request for specialist assistance


ETSI

TS 103 260-1 V0.1.2 (2014-10)32

Emergency teams/ officers to external resources (hospitals)

Patient information/ telemedicine applications

Data

External resources (hospitals) to emergency teams/ officers

Expert advise/ request for information


External resources (hospitals) to emergency teams/ officers

Telemedicine applications/ access to databases

Data

5.3.8 EvacuationSource to destination(s) Type of information Service Requirements

Civil protection (field) to Civil protection

authority

Status reports, availability, constraints, demand notification, risks


Civil protection (field) to Civil protection

authority

Status reports (numbers of evacuees etc),

Data

Civil protection (field) Civil protection

authority to

Civil protection (field)

Situation reports, requests for information etc.

Voice

Civil protection (field) Civil protection

authority to

Civil protection (field)

Status reports (numbers of evacuees etc.),

Data

Civil Protection to CFECC



Civil protection to CFECC

Status reports Data Data integrity, data timeliness (seconds), low throughput

CFECC to civil protection

Status reports, tasks Voice Speech intelligibility/quality, call setup time, end-to-end delay

CFECC to civil protection

Status reports, maps etc. Data

Civil protection to transport provider(s)

task coordination, availability, constraints, demand, risks

Voice

(1 to 1/

group call)


Civil protection to transport provider(s)

Status reports, transport plans. Data Data integrity, data timeliness (minutes), medium to low throughput

ETSI

TS 103 260-1 V0.1.2 (2014-10)33

5.3.9 Provisions

5.3.9.1 Power


Power corporation (central) to CFECC



Power corporation (central)to CFECC

Status reports (e.g. maps), plans for restoration/ supply of generators etc.

Data data integrity, data timeliness (seconds), low throughput

CFECC to Power corporation (central)

Status report, tasks Voice speech intelligibility/quality, call setup time, end-to-end delay

CFECC to Power corporation (central)

Status reports, tasks. Data

Site management (power) to Power corporation (central)


Site management (power) to Power corporation (central)

Status reports (pictures) Data

Power corporation (central) to site management (power)

Tasks, allocated resources Voice speech intelligibility/quality, call setup time, end-to-end delay

Power corporation (central) to site management (power)

Tasks, allocated resources, maps, Data

Site management (power) to power workers teams

Status reports/ allocation of tasks Voice


Power workers teams to site management (power)




Site management (power) to CFECC


Site management (power) to CFECC

Status reports/ requests Data data integrity, data timeliness (minutes), medium to low throughput

CFECC to site management (power)

Status reports/ tasks Voice

CFECC to site management (power)

Status reports/ tasks Voice data integrity, data timeliness (minutes), medium to low throughput

Site management (power) to civil authorities

Status reports/ task allocation Voice

Site management (power) to civil authoritites

Status reports/ task allocation/site information


ETSI

TS 103 260-1 V0.1.2 (2014-10)34

Civil authorities to site management (power)


Civil authorities to site management (power)

Status reports/ requests/site information (maps)


5.3.9.2 Water, food and sanitation


CFECC to civil protection authority / local authorities



CFECC to civil protection authority/ local authorities

Status report, requests for resources, maps


Civil protection authority/ local authorities to CFECC

Status reports, allocation of resources


Civil protection authority/ local authorities to CFECC


Data

Civil protection authority/ local authorities to site management teams



Civil protection authority/ local authorities to site management teams


Data

Site management teams to civil protection authority/ local authorities



Site management teams to civil protection authority/ local authorities


Data

Site management teams to field workers (civil protection/ local authority/ NGO)


Voice



Field workers (civil protection/ local authority/ NGO) to site management teams

Status reports Voice

5.3.9.3. Temporary SheltersSource to destination(s) Type of information Service Requirements

CFECC to local authorities Status report, requests for resources


CFECC to local authorities Status report, requests for resources, maps


Local authorities to CFECC Status reports, allocation of resources


Local authorities to CFECC Status reports, allocation of resources

Data

ETSI

TS 103 260-1 V0.1.2 (2014-10)35

Local authorities to site management teams



Local authorities to site management teams


Data

Site management teams to local authorities



Site management teams to local authorities


Data

Site management teams to field workers (local authority/ civil protection/ defence fordes/ NGO)


Voice



Field workers (local authority/ civil protection/ defence fordes/ NGO) to site management teams

Status reports Voice

5.3.10 Maintenance of Public OrderSource to destination(s) Type of information Service Requirements











pictures etc.)


SECC police to emergency teams/ officers

Tasks, allocated resources/ destinations of patients

Voice

(1to 1/ group call)


SECC police to emergency teams/ officers


Data

Emergency teams/ officers to SECC police


Emergency teams/ officers to SECC police

Status report (location data/ pictures etc.)

Data

May be removed?????

This clause defines the information flows for Actors within the Incident Area.

ETSI

TS 103 260-1 V0.1.2 (2014-10)36

Replace text in each subclause with table as above.

Change headings to conform with 4.3.

[4.7.1] Situation assessmentMembers of public will contact PSAP mainly through available public telephone services. These may have broken down in major earthquakes, leading to delayed alarms, or at least lack of information on the side of the authorities in the early stages of the disaster. Most PSAPs do not have facilities for satellite communication with the public.

[4.7.2] Implementation of Emergency Control StructuresCFEEC, being the main coordinating body within the Incident Scene, will need a stable and well functioning communication link with central authorities. Voice communication is crucial, but there is also a need for data. As a minimum there has to be facility for mail with attachements, particulary and documents and still pictures. Some of the documents exchanged may be of a considerable size. The data communication is typically not time critical, hence the demand is more on a stable connection than on bandwidth.

Data to be transmitted between FECC and central authorities will be maps, plans etc., and reports from Incident Scene activities and needs. Short messages will also be in use.

There will also be a need for telecommunication systems between FECC and entities working within the Indicent Zone. This communication will mainly be voice and short messages. Broadcast facilities will be of use.

Access to the Internet is presently not universally available to FECC, but would be useful.

Real time video is considered useful, but has a lower priority than voice and data.

The communication needs of FECCs for individual services will be dealt with in the respective sections below.

[4.7.3] Damage Control/ Risk ReductionThe department of Fire and Rescue, which is normally in command of this activity, will typically set up a FCC within the Incident Scene. Their communication with F/ R ECC will primarily be based on voice, but transfer of plans, information on dangerous substances etc. will be communicated as data. (e.g. email with attachments).

Information exchange with operational personnel will mainly be based on voice, both one-to-one, group communication and broadcast. There will also be some use of short messages.

Decontamination units may be involved in damage control. These may be part of the Fire and Rescue departments, but also be different units. In addition to voice and short messages these units may need to exchange sensor data (concentrations of gas etc.) to external units.

Defence forces may also have a role in this activity. They will typically bring their own communication systems, mainly for voice.

The communication equipment used has to be compatible with the present risks, such as danger of explosions, high temperatures etc. The user friendliness has to be high, and information exchange has to be possible in areas with high levels of noise.

[4.7.4] Search and Rescue (SAR)Public services participating in SAR will in many cases share a common PMR. The need is for voice, both one-to-one, groups and broadcast. Short messages will also be needed. Transmission of pictures may be useful in some cases, but carry a lower priority than voice and short messages.

Defence forces will as mentioned above bring in their own systems, as will NGOs. The lead entity needs to be able to communicate, at least indirectly, with the personnel from non-emergency services.

ETSI

TS 103 260-1 V0.1.2 (2014-10)37

[4.7.5] First Aid/ TriageThe tendency towards less advanced treatment within the Incident Scene also means less qualified staff on site. This will increase the need for communication between the Incident Scene and better equipped facilities, mainly hospitals. The communication needs are both for advice on treatment, and on information about patients who are being referred. The need is for voice, and for data including pictures. Medical services typically rely either on their PMR or public telephone services for communication. Experiences are that these may not be functional for communication between Incident Scene and hospital, and in those cases satellite communication provides useful alternatives.

[4.7.6] Public OrderThe structure of the police, with ECC being actively in command, emphasises the importance of the link of communication between FECC and ECC. Voice communication is the priority, short messages may be used. The police in most cases relay on their PMR (which may and may not be shared with Fire and Rescue and Medical services). If this system is not working, then public mobile telephone is the second option, followed by satellite systems.

Communication between FECC and operational units within the Incident Scene is based on voice.

[4.7.7] Repair of Infrastructure/ UtilitiesThis activity is carried out by a wide range of actors, who may and may not have their own PMRs. They will all need voice communication with their mother organisations. To what extent they need data communication will differ between organisations, and to what extent they are equipped with updated information on their mobile devices. Their communication with CFEC will mainly be by voice.

[4.7.8] Emergency Supplies/ Temporary Shelters/ SanitationInformation about needs, reports on accessibility etc. will need to be communicated between CFEC and relevant authorities. The communication needs are initially by voice, but data communication will be needed as well, especially at later stages. The need for video conferencing is considered limited.

[4.8] Quantitative considerations5.3.1 PMR group call channelsThe number of required voice channels depends on the number of involved emergency service disciplines and the command structure:

1 group call channel jointly used by ECC, CFECC, and all FECCs;

1 group call channel jointly used by each emergency service’s FECC and all assigned SECCs;

1 group call channel jointly used by each SECC and all assigned emergency team officers;

Optional: 1 group call channel used by each emergency team.

Example: 7 involved emergency service incident commanders manage 3 sectors each, and 3 teams per sector. The total (maximal) number of required voice channels for group calls sums up to 1+7+7*3+7*3*3=86.

5.3.1.1 Data services

Data service requirements are driven by the applications used by emergency service disciplines. Typical use cases for the envisaged MTA response are:

Point-to-point data transfer (e.g., ECC sends background information to CFECC);

Multi-point-to-point data transfer (e.g., PPE data from team members is sent to team officer, aggregation of registration and triage data);

Multi-point-to-multi-point data transfer (e.g., synchronisation of common operating picture or casualties data between ECC/CFECC/FECCs/SECCs);

Unidirectional point-to-point streaming (e.g., data generated by sensors);

ETSI

TS 103 260-1 V0.1.2 (2014-10)38

Bidirectional point-to-point streaming (e.g., real-time telemedicine applications);

Multi-point-to-multi-point streaming (e.g., audio/video conference calls).

5.4[4.9] Characteristics of Emergency Communication ServicesHaitham

Review if, or how much of, this is necessary. Give overview of what we need

QoE needed for services……..

Reference to EMTEL [i.2]

e.g…………….

5.4.1 Data servicesFollowing from “User Perspective” ……………..Relate to QoE

Data service requirements are driven by the applications used by emergency service disciplines. Typical use cases for the envisaged responses from the user perspective are:

Point-to-point data transfer (e.g., ECC sends background information to CFECC);

Multi-point-to-point data transfer (e.g., PPE data from team members is sent to team officer, aggregation of registration and triage data);

Multi-point-to-multi-point data transfer (e.g., synchronisation of common operating picture or casualties data between ECC/CFECC/FECCs/SECCs);

Unidirectional point-to-point streaming (e.g., data generated by sensors);

Bidirectional point-to-point streaming (e.g., real-time telemedicine applications);

Multi-point-to-multi-point streaming (e.g., audio/video conference calls).

5.4.2 Communications services requirementsWith respect to Figure 5-2, the efficient exchange of information a single discipline team, between ECCs and the mobile, and between a temporary task force/command centre and a permanent PSAP/ECC may be facilitated by a number of communication services, described below.

5.4.3[4.9.1] Speech servicesSpeech services are currently the most instinctive and most used communication services in emergencies, and this is likely to remain the case for years to come. For speech services there exist several universal requirements, characterised by:

Speech intelligibility and quality: that received speech is capable of being understood reliably and some cases high speech quality is desirable.

Call setup-time: short call set-up times enable rapid communication of relevant information.

End to end delay: in addition to the call set-up delay, it is recognised that where a duplex voice communication system imposes an end to end delay of over 500 ms there is degradation in the voice quality (International telephone connections and circuits - General Recommendations on the transmission quality for an entire international telephone connection One-way transmission time, ITU-T Recommendation G.114).

ETSI

TS 103 260-1 V0.1.2 (2014-10)39

Also underlying networks (e.g. satellite and terrestrial) should have the capability to handle prioritised calls correctly, including the capability of pre-emption of unprioritised calls. Transit networks should convey priority related signalling in order to support end-to-end priority.

5.4.3.1[4.9.1.1] Point To Point Speech Services

Point to point duplex voice communications are required for many instances to provide communications, particularly between different authorities e.g. between commanders of different emergency services, between emergency service staff and external specialists.

5.4.3.2[4.9.1.2] Group Speech Services

Some examples of groups are:

Talk group: Point-to -multipoint group addressed communication established within a selectable predefined area. The coverage is associated to the group number and may be different of the total coverage. Resources are allocated all the time.

Emergency services call (authority to authority): Two options are possible:

Automatic call set-up of a pre-emptive open channel.

Using a pre-emptive priority, a predefined user (e.g. ECC) shall establish a call chosen on an operational basis.

Intrusion: This service shall allow an authorised user to intervene in an ongoing authority-to-authority call.

Priority call: This service shall allow a call to proceed before any other call with lower priority. The priority level can be assigned according to various criteria.

Dynamic group number assignment: This service shall allow a served user or an authorised user to create, modify and delete a group (dynamic regrouping/group merging).

5.4.3.3[4.9.1.3] Push To Talk (PoC)/Command and Control (C&C) features

Communication should require as little bandwidth as possible. Preferably it should not occupy lines permanently (as most of the group communication services mentioned above do) but data or voice should only be transmitted if information is actually exchanged. This holds especially for emergency communications characterised by many short speech items transmitted between talk group members over a certain period of time (e.g. giving and receiving instructions in C&C communication).

To facilitate this simplex communication services like push to talk can be used. PoC helps to avoid network congestion by transmitting voice over a data channel (GPRS, UMTS) and thus can be used even in times of high traffic on the communication network. Furthermore PoC provides flexible management of user groups.

5.4.3.4[4.9.1.4] Video Tele-Conferencing

VTC may be required to enable effective coordination between services at a command level or below. VTC services may be utilised to provide reconnaissance information from the incident back to control rooms. Note that near-real-time video streaming can be considered as a data service (see below).

5.4.3.5[4.9.1.5] Data services

Data services are used to provide a large number of applications which can have widely differing requirements in terms of capacity, timeliness and robustness of the data service. Ideally, the communication networks should support the required data throughput and minimise end to end delay, especially for applications such as real time video. Noting the extreme circumstances which may be in force during an emergency, it may be desirable for networks to degrade gracefully when user requirements exceed the agreed levels of service.

Table 1 shows the diverse needs of data applications. Where data applications share the use of a data transmission capability, provision of sufficient capacity and effective management must be provided to ensure application data is communicated appropriately.

ETSI

TS 103 260-1 V0.1.2 (2014-10)40

Table 1: Requirements on data applications (Source: TS 102 181)

Service Throughput Timeliness Need for preservation of data integrity

Email Medium Low LowImaging High Low Variable

Digital mapping/ Geographical information

services

High Variable Variable

Location services Low High HighVideo (real time) High High Low

Video (slow scan) Medium Low LowData base access (remote) Variable Variable High

Data base replication High Low HighPersonnel monitoring Low High High

Throughput: data volume in a given time.

Timeliness: importance of the information arriving within an agreed timeframe.

Preservation of data integrity: how (reliable) free from bit errors the information transmission needs to be. E.g. a bitmap image with some errors is still useable; a jpg image with some bit errors may be unreadable.

5.4.3.6[4.9.1.6] Paging (short message) Services

Paging services are used by a variety of authorities in order to contact their personnel, and paging services are available from a variety of networks and technologies. The network needs to be able to identify the requested authorised emergency agent(s), and then deploy the appropriate technology to contact them. This requirement may encompass different communication network technologies, services and applications such as paging, presence, texting, etc.

5.4.3.7[4.9.1.7] Status Monitoring and Location Services

Status monitoring includes a wide variety of parameters, e.g. breathing air tank levels, accountability monitoring, distress buttons and vital signs monitoring. Location services provide real-time information regarding the position of personnel or vehicles to a Command Post (CP). This information may also include status information regarding the person or vehicle. The service may require frequent transmissions to update position; the amount of data transmitted is likely to be small when location is based on satellite-based solutions, but can be quite extensive when location is to be calculated inside buildings as other technologies may have to be used. Location reporting services may be one-way with no acknowledgement, necessitating a robust communication mechanism. Position information may be considered sensitive in some emergencies and may require security mechanisms to protect the data.

Table 2 shows a summary of characteristics of the identifed communication service. Satellite and terrestrial communication networks should be able to provide the required data rates and QoS provisioning parameters. [HC: The table is copied from Widens project deliverable D2.1, but I could not obtain the original reference. Can Anton or Julian help to identify a similar information, espcially if it is ETSI document, thanks ]

Table 2: Characteristics of the identified communication services (Source Widens project D2.1)

ETSI

TS 103 260-1 V0.1.2 (2014-10)41

7.1.2 Communications flows

Based on an assessment of the currently used communication services within the public safety sector it can be concluded that public safety mobile communications are voice-based with widespread use of group calls (“network-centric”1), also called talkgroups. These are called Push-to-talk calls (PTT calls) Point-to-point voice calls (P2P calls) are also used specially by emergency managers.According to user comments, positioning information of emergency units deployed in the disaster area is also currently in used in most of Public Agencies that counts on narrowband data channels of TETRA technology. However, there is a trend towards using a range of data applications alongside traditional voice applications to enhance communications. Data services have widely differing requirements in terms of capacity, timeliness and robustness of the data service. Some the communication flows between various entities (in Figure 1) are described below:

5.4.3.8[4.9.1.8] FRs – FRs

For example, the First Responders (FRs) in each emergency team (Discipline A, B or C) has its own and unique talkgroup.

5.4.3.9[4.9.1.9] FRs – corresponding CP

Bidirectional voice communication is allowed between the FRs and their Command Post (CP) since they share the same voice group.

Bidirectional data communication is allowed also between FRs and their CP primarily for geo-positioning applications. Special data services are required for the Fire & Rescue discipline in hot area since they may carry special equipment which needs to transmit data to the corresponding CP. Examples of this equipment are wearable biometric sensors, radiation or gas sensors, video cameras, positioning equipment. CPs should have equipment to receive, integrate and display all these data acquiring valuable risk management information. Crucial actions are allowed, i.e. FRs could be

1 “Network-centric” refers to sharing of information between people and devices in a many-to-many (group) configuration, as is often used within the public safety sector)

ETSI

TS 103 260-1 V0.1.2 (2014-10)42

rescued if irregular vital constants are observed. FRs will receive alerts, positioning information, commands to proceed, etc, through voice communication or data displayed in their user interface.

5.4.3.10[4.9.1.10] CP – CP

In the case several CPs are deployed they all should have bidirectional communication among them sharing valuable risk management information from their corresponding Emergency Agency.

5.4.3.11[4.9.1.11] CP – EATF

All CPs deployed in the disaster area and the global coordination centre (Emergency Authority Task Force, EATF) in Figure 1, should have bidirectional voice and data communication among them sharing valuable risk management information or commands to proceed.

5.4.3.12[4.9.1.12] CPs – External entities

Certain CPs have bidirectional communications with external entities with or sometimes without the intervention of the EATF, such as Fire & Rescue communicate with medical vehicles with hospitals. In addition to current operational practices where just voice calls are performed, paramedical users have suggested to enable ambulances to send data files with injured victims lists or electrocardiogram (ECG) traces to the hospital to reduce reaction time attending the victims.

5.4.3.13[4.9.1.13] CPs – External information

It is desirable for CPs to have external connections in order to enhance effectiveness of the operational procedures. One example is access to detailed maps for geo-localisation support units would receive detailed information of the target location. Another application could be accessing the Fire Risk Assessment Indices of the affected area which takes into account baseline vegetation information (vigour, condition, etc). Access near real time satellite images is a new service provided by current observation LEO satellites in charge of image acquisition of the hot spots within several hours from the start of the emergency.

7.1.2 Communications flows [HC: This is a forest fire example from MONET deliverable D2.4. I was wondering if we could scale it up (e.g. 10 time) for an earthquake scenario. May be Anton and Egil could comment here]

First emergency units arrive on the biggest fire centre. Emergency responders establish command post and fire officials assess situation.

6 fire-fighters of each squad approach the wildfire in order to extinguish it, not separating more than 300m from their auto-pump vehicle since this is the maximum hose extension. Thus, the auto-pump team, the driver and a fire-fighter, remains in the auto-pump to maintain the water supply. The rest of the emergency responders remain also in the warm area.

Two Police patrols detect the smaller forest fire centre 5 kilometres away from the previous one. The police units alert habitants for evacuation and contact the Police CP in main fire centre to ask the BO for support units. Finally, three CPs and their corresponding FRs are set up in hot and warm areas of this second fire centre, starting the second emergency phase which involves higher number of communications since more emergency responders are present in the scenario.

It will be assumed that 15 affected people have to be carried to the nearest hospitals.

The players and vehicles (CP included) finally deployed in each fire centre are summarised in Table 3Error: Reference source not found.

Table 3: Example communications requirements for forest fire scenario (Source MONET project D2.4)

COMMUNICATION REQUIREMENTS IN the biggest forest fire centre

Public safety agency Service in use Users SAT Comm. flow Requiremen Occurrence

ETSI

TS 103 260-1 V0.1.2 (2014-10)43

MANET/SAT0 t level

fire brigade in

hot area

PTT Voice Call

120 MANET/SAT

Fire Brigade CP from/to fire-fighters in hot area

Mandatory

926,4 PTT/15 minutes during busiest hours

463,2 PTT/15 minutes during regular hours

Personnel monitoring

120 MANET/SATFire-fighters in hot area to CP

RequiredNominal each 5s while moving.

Location services 120 MANET/SAT

Fire Brigade units (pedestrian) to CP

Mandatory

Nominal each 1,5 minutes while moving.

Each 5 mins if stopped.

Real Time Video 20

20 Fire-fighters to CP

20 Fire-fighters in hot area to CP

Desirable

20 transmitting continuously during all disaster

fire brigade in

WARM area

P2P Voice Calls

1CP SATFire Brigade CP to BO and other CPs

Mandatory 12 P2P/h

PTT Voice Call

40 MANET/SAT

Fire Brigade CP from/to fire-fighters in warm area

Mandatory

308,8 PTT/15 minutes during busiest hours


Location services

40+20 MANET/SAT

Fire Brigade units (pedestrian and vehicles) to CP

Mandatory

Nominal each 1,5 minutes while moving.

Each 5 minutes if stopped.

Real Time Video

1CP SAT Fire Brigade CP to BO Desirable

1 transmitting continuously during all disaster

POLICE DEPARTMENT

P2P Voice Call 1 SAT

Police CP from/to BO and to other CPs

Mandatory 12 P2P/h

PTT Voice Calls

10 MANET/SATPolice CP from/to policemen

Mandatory

77,2 PTT/15 minutes during busiest hour


0 SAT means the communication will go through satellite link. MANET/SAT means satellite access is used as back up.

ETSI

TS 103 260-1 V0.1.2 (2014-10)44

Location services

10+5 MANET/SAT

Police units (pedestrian and vehicles) to CP

Mandatory

Each 1,5 minutes while moving. Each 5 minutes if stopped.

Medical services

P2P Voice Call 1CP SAT

Police CP from/to BO and to other CPs

Medical CP to hospitals

Mandatory

12 P2P/h

30 P2P during all disaster considering 15 victims

PTT Voice Calls

30 MANET/SAT

Medical CP from/to doctors/nurses

Mandatory

231,6 PTT/15 minutes during busiest hour

115,8PTT/15 minutes during regular hours

Location services

30+10 MANET/SAT

Medical units (pedestrian and vehicles) to CP

Mandatory

Each 1,5 minutes while moving.

Each 5 minutes if stopped.

6[5] Topology ModelA textual, graphical or mathematical topological model showing how end-users are deployed/move in their field of activity. This topological model may make reference to existing work but it must be part of the reference scenario.

It should include or define constraints impacting the networks formed from the various information exchanges. These constraints are – for example – derived from the mobility patterns of the users. From a technology standpoint, mobility patterns yield representative figures for wireless links lifetime and environment.

6.1[5.1] Assumptions

6.2 Nature of Model

6.3 Resultse.g. Data rates

ETSI

TS 103 260-1 V0.1.2 (2014-10)45

6.3.1.1.1.1.1.1[5.1.1.1.1.1.1.1] Annex A (informative):Major Recent Earthquakes

Date Country Place Mag People Buildings CostEurope Killed Injured Affected homeless demolished damaged

'000s '000s MEuro

20/05/2012 Italy Emilia 6 24 350 25 20 15800+

11/05/2011 Spain Lorca 5.3 10 167 15 20006/04/2009 Italy L'Aquila 6.3 295 1600 56 50 10000 250007/09/1999 Greece Athens 5.9 143 115 2,700 35,000 4200

Outside Europe

11/03/2011 Japan Honshu 9 20000 370 210000

12/01/2010 Haiti Haiti 7 222500 3700 105,000 188,383 800030/09/2009 Indonesia Padang 7.5 1200 2500 220012/05/2008 China Eastern

Sichuan7.9 87500 4600 85000

Sources: EMDAT, USGS

Annex B (informative):

Annex <X> (informative):Bibliography

The annex entitled "Bibliography" is optional.

It shall contain a list of standards, books, articles, or other sources on a particular subject which are not mentioned in the document itself (see clause 12.2 of the EDRs http://portal.etsi.org/edithelp/Files/other/EDRs_navigator.chm).

It shall not include references mentioned in the document.

<Publication>: "<Title>".

OR

<Publication>: "<Title>".

Annex <X> (informative: Detailed Scenario DefinitionThis annex provides a detailed description of the scenario, which forms the basis for the modelling, described in chapter X.

Incident area: An area of 12x15kms in a city of 350 000 inhabitants. The area is pretty isolated; the main road access is damaged by a landslide (see sector C below). In addition to the main road, there is a smaller road crossing a bridge (see sector D below)

There is one high voltage cable to the area; water supply is via underground pipes from a lake outside the incident area.

None of the emergency services have ECCs within the incident area, but there is an ambulance station based at D

Sector A (domestic/ shopping area):

ETSI

TS 103 260-1 V0.1.2 (2014-10)46

http://portal.etsi.org/edithelp/Files/other/EDRs_navigator.chm

- In the north-western part of the incident area

- Totally or partly collapsed buildings:

o Primary school, enrolment 350, staff 100

o 7 blocks of flats, totally 140 flats, approximately 480 persons live there. Not known how many who were at home at the time of the earthquake

o 45 bungalows, approximately 240 persons live there.

o Shopping centre consisting of 15 small and large enterprises, total staff 240, number of customers present not known. Three is a fire covering an area of 1 department store.

- Specific risks:

o 1 petrol station is partly damaged, it has tanks of diesel, petrol and LPG

Sector B (industrial area): - In the south western part of the city

- Totally or partly collapsed buildings:

o 3 factory buildings (meat processing, clothes manufacturing, mechanical enterprise), totally 600 employees

o Bus garage/ workshop on fire. 45 employees, 25 buses with diesel tanks

- Specific risks

o Tanks containing gas. The status concerning leakage etc. is not known.

Sector C: (Hillside, mainly farming area)- The earthquake has led to a landslide which has broken the power line supplying the incident area, and closed

the main road leading into the incident area

Sector D: (Secondary road, crossing a bridge)- The earthquake has led to structural damages on the bridge; it is initially unclear to what extent that has

reduced the load carrying capacity. Landslide breaking the power-line and covering the road. No cars hit by the landslide, but the road is blocked

- The bridge has minor damages from the earthquake, uncertainty as to how this affects its load capacity

Annex <X> (informative): Disaster response actions – timelines6.3.2 Initial Alerting 0 min: Although located outside the affected area, the personnel on duty at the ECCs note the earthquake. Operational staff is notified via pre-set procedures that they should be on the alert, and routine tasks (e.g. non-critical patient transports) be postponed till further notice.

ETSI

TS 103 260-1 V0.1.2 (2014-10)47


I am not sure how we do the numbering here.

3 min++: PSAP receives a high number of calls from the affected areas, the overall picture is unclear but information as it comes is continuously forwarded to the ECCs of the individual services.

6.3.3 Assessment of Situation and Need for Resources 12 min: Ambulance staff at the station within the incident area registers substantial damages, and ask ECC health for additional resources to be sent to the area

15 min: ECC health notifies other ECCs, emergency services resources dispatched to incident scene

25 min: F&R team reports on blocked main road, only light vehicles to be dispatched till further notice.

30 min: Central authorities make request for geological expertise to evaluate the landslide.

30 min: Ambulance helicopter arrives on scene. Before landing it makes a round over the affected area, taking video, which is transferred, to the health ECC and forwarded by them to relevant authorities. The damage is assessed to be considerable, several roads within the incident area are blocked, and there is substantial uncertainty as to the conditions of several bridges in the area.

35 min: The helicopter crew request assistance in assessing/ clearing temporary landing spots

45 min: CFECC in place and takes over, assessment constitutes part of their activity and reporting (see section X below)

6.3.4 Transport access30 min: Request from Central Authorities to Roads Department to assess the capacity of the remaining bridge

50 min: Assessment team on site, taking photos and submitting them to central roads department.

65 minutes: Conclusion: The weight limit raised to 12 tons, subject to traffic regulation (only one car at the time).

135 minutes: Reparative work on landslide initiated, but made difficult by risks of further landslides.

3 hours: 4 different areas identified as suited for landing for the helicopters involved.

8 hours: Work on landslide stopped as it gets dark and it is no longer possible to continuously assess the risk for further landslides.

19 hours: Work on landslide is started again. Assistance from defence forces engineers.

23 hours: Main road opened for limited traffic.

6.3.5 Assessment and handling of (specific) Risks30 min: Geologic Expertise requested

90 min: Geologists arriving on scene, pictures to be submitted

120 minutes: Conclusion, advise for reparative landslide work provided.

120min: Specialist team (building surveyors, 12 officers) arrive on scene. They are distributed to sectors A and B to control and if necessary, take steps to make areas safe for rescue work. They communicate to central authorities (via CFECC) sending and receiving building plans and pictures.

5 hours: Surveyors have checked collapsed buildings, cleared 10 but decided that 4 blocks of flat and the primary school needs further work to be declared safe. Specialist workforce is requested via CFECC

ETSI

TS 103 260-1 V0.1.2 (2014-10)48

6.3.6 Implementation of Emergency Control Structures20 min: SECC (health) consisting of 1 ambulance officer is established

30 min: SECC (F&R) is established

30 min: SECC (Police) is established

45 min: CFECC established.

55 min: A preliminary situation report (V) is submitted to authorities; procedures and links for communication to SECC are established. Updates and requests are made to authorities continuously for the next two hours.

60min: Written situation report in accordance with premade plans is submitted to authorities, updated every hour for the first 24 hours.

90 min: Videoconference with authorities, pictures from scene submitted. Videoconference between members of CFECC and authorities planned for every 2 hours.

100min: Preliminary report on needs for water/ sanitation/ food/ shelter is submitted to authorities

115 minutes: Local “air traffic control” established, landing area for helicopter appointed. Ambulance helicopters are now arriving every 15 minutes, airlifting patients out of incident scene.

120 min: Generators and tents are brought in, are distributed between services and set up.

150 min: Plans for evacuation of non-injured individuals are set up, transport resources asked for.

3 hours: Situation report: No/ minor injuries: Not known, local treatment only 127, need for hospital treatment 235, dead 15.

4 hours: Food and water is brought in and distributed to the rescued and to the rescue teams. Supplies are to arrive every 3 hours, following specified requests from CFECC

6 hours: Lists prepared on staff rotation, the responsibility for ensuring that so happens lies with the service EECs, but reports are made to CFECC.

9 hours: Situation report: No/ minor injuries appr 600, local treatment 212, need for hospital treatment 320, not accounted for: not known.

10 hours: Re-enforcement from NGOs from outside the city, assisting in supplying water/ food.

6.3.7 Firefighting and rescue 30 min: First team (4 persons) arrive on scene, reports to ECC, starts surveying the scene and reports continuously to ECC for the next hour. Pictures of the scene are sent to the ECC.

35 min: Fire trucks are dispatched to scene, but awaiting permission to cross the bridge

40 min: Additional 8 officers arrive on scene; SECC is established and reported to ECC

50 min: SECC is overloaded by survivors, police summoned to keep order.

65 min: 8 fire trucks with personnel (5 officers each) and equipment arrive on scene. 4 are deployed to sector A, the other 4 to sector B, where they start fire fighting.

70 min: A team of smoke divers (4 officers) arrive at sector A where they prepare for action, 2 of them have helmet cameras able to submit streaming video.

75 min: Part of the stricken area is declared safe. Reported to CFECC who reports to authorities

80 min: A team of smoke divers (4 officers) is deployed to Sector B, 2 of them able to submit streaming video from helmet cameras.

80 min: Building plans for collapsed buildings are requested from central authorities.

95 min: 10 SAR teams, each of 2 officers, are established and search is starting, 6 teams at sector A, 4 at sector B.

ETSI

TS 103 260-1 V0.1.2 (2014-10)49

105 min: 15 individuals are evacuated and taken over by medical services.

120 min: Dead people are located.

2 hours 30 min: 80 volunteers from Red Cross arrive, and are set to work on SAR in sectors A and B.

3 hours: 6 teams (1 person and dog in each team) NGO) with rescue dogs arrive on scene and start their work in the areas so far declared safe.

6 hours: 12 fire trucks (5 officers each) from other services arrive and assist

7 hours: Fires at sector A is terminated, all efforts now on search and rescue

9 hours: Fire at sector B is terminated

7 – 20 hours: Search and rescue activities continue throughout the night, but at a lower rate due to darkness.

23 hours: With the opening of the road, heavy equipment is brought in for securing buildings etc.

6.3.8 Treatment of CasualtiesTimeline:

0 min: Ambulance station hit by earthquake. Garage broken down, 1 out of 2 vehicles rendered inoperative.

13 min: Preliminary assessment made, officer reports to ECC, requesting resources. Temporary SECC(health) is established (awaiting arrival of officer who is to permanently run SECC).

30 min: Ambulance helicopter arrives on scene. Before landing it surveys the stricken area, submitting streaming video to ECC health.

40 min: 3 more ambulances (6 officers) arrive on scene and are distributed to sectors A and B.

45 min: 4 Trailers with emergency medical equipment dispatched, waiting at bridge.

45 min: Reports to CFECC, locations for triage/ treatment are established, and treatment started. Medical services overloaded, repeat request for more resources.

60 min: Continuous reporting to CFECC (Numbers and names of patients)

70 min: 2 hospital teams (8 officers each) and leader SECC are brought in by ambulance helicopter, starts working with the injured.

75 min: Ambulance manager and First aid manager are appointed, report continuously to SECC

90 min: Another 4 helicopters are brought in and continue airlifting patients to hospital.

120 min: Direct communication link between treatment area and hospital is set up (V+D). The local hospital is overloaded; plans for further evacuation are made, and system for reporting of patients from the Incident Scene is established in collaboration with CFECC

125 min:

3 -5 hours: 10 ambulance teams from other hospitals arrive on scene, medical evacuation continues by road and by air.

7 – 20 hours: Patients continue to be brought in.

22 hours: The number of patients being brought in is now lower than the day before, but the patients who do come, tend to have more serious injuries. Consultations with hospitals, both local and specialised, are done via Video conferencing.

6.3.9 Evacuation65 min: Team from coordination entity (Civil protection) arrives and sets up centre for registration of individuals.

ETSI

TS 103 260-1 V0.1.2 (2014-10)50

65 min: Request for transport is forward via CFECC to authorities.

90 min: The request is re-enforced and specified; the need is for small vehicles who can transport people to the access bridge, from where they should be transported further in bigger buses to areas decided and prepared by the authorities.

150 min: Small vehicles arrive and start evacuation

2 hours+++: Registration and evacuation is on-going, continuous reporting made to CFECC who forward the reports to authorities.

6.3.10 Provisions

6.3.10.1 Power120 mins: First generators are brought in, more are requested for. Generators are supplied by the power corporation.

180 mins: System for regular supply of fuel for generators established, dedicated personnel responsible for maintaining control and ensuring that they are in working order.

4 hours: More generators and lighting equipment arrives from outside the city.

5 hours: Mapping of damages completed and reported via CFECC to power provider.

24 hours: Staff and equipment in place, start working on emergency supply to most critical areas.

27 hours: Limited power supply available.

6.3.10.2 Water, food and sanitation To provide safe water supply and food is a priority.

90 min: Request made as part of the regular videoconference between CFECC and authorities.

4 hours: The first truck loaded with the equipment arrives at the bridge, and receives a description from CFECC as to where the supplies are to be unloaded.

7hours +++: Continuous supplies and emptying of latrines is on-going, continuous reporting to CFECC

6.3.10.3 Temporary Shelters90 min. Need for shelters is discussed in videoconference, supplied by written report at 100min Central authorities forward the request to defence force and NGOs.

3 hours: An inventory of available tents/ personnel to set them up and possible times of arrival are received by CFECC, plans made for deployment within incident area.

5-18 hours: Tents, supplied by Local Authority and Civil Defence arrive and are set up by officers from the two entities.

6.3.11 Maintenance of Public Order 30 min: 2 officers arrive on scene, establish SECC, reports to ECC, requesting more resources

45 min: Reports to CFECC

50 min: Summoned to SECC F&R where a large group of people have gathered demanding assistance and information. Information is submitted continuously to CFEEC who submits the reports to the authorities every 30 minutes.

55 min: 10 more officers arrive on scene. SECC is established, teams of 2 officers start securing and patrolling the area. All officers connected by PMR. For the first 12 hours each officer is on the radio with the SECC at an average of 2 minutes per hour.

60 minutes: System for registration of individuals able to walk and report is set up.

75 min: 16 more officers arrive on scene. The area is cordoned off and patrolled. System for access control, registering who enters and leaves the area is established, information conveyed continuously to authorities via CFECC. Traffic control at bridge is established

ETSI

TS 103 260-1 V0.1.2 (2014-10)51

90 minutes +++: Congestion at the bridge (entry point), police make a priority list and officers are there to guide the traffic.

5 hours: Additionally 30 officers from neighbouring forces arrive on scene.

7 hours: 120 officers from national forces arrive on scene.

7[6] HistoryDocument history

V0.0.1 Feb 2014 TOC + contents definition

V0.0.2 Feb 2014 First scenario contents

V0.0.3 Feb 2014 Scenario update

V0.0.4 April 2014 Updated with text in 4 and 5

V0.0.5 April 2014 Updated with Annex A, B and further text. etc.

V0.0.6 April 2014 Updated references

V0.1.1 Oct 2014 First Draft

V0.1.2 Oct 2014 Updated by STF, with WG comments etc.

ETSI

TS 103 260-1 V0.1.2 (2014-10)52

skeleton - docbox.etsi.org · web viewedited by b. wisner and j ... have separate emergency power...

Documents