hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
a2ed1c18e57b2a5468fbd4579c87a077 | 103 246-1 | 4.1 Location based applications requirements | |
a2ed1c18e57b2a5468fbd4579c87a077 | 103 246-1 | 4.1.1 Reminder of ETSI TR 103 183 content | ETSI TR 103 183 [i.1] provides a thorough inventory of the location based applications which is used as a reference in the present document. The present clause summarizes the classification work which was conducted in order to identify those applications driving the requirements. These requirements were organized into ... |
a2ed1c18e57b2a5468fbd4579c87a077 | 103 246-1 | 4.1.2 Common requirements | Based on ETSI TR 103 183 [i.1], the following requirements were identified as shared by all location-based applications: • Services remain available over a predefined service area. • Management of multiple end users: - The application shall be used by one or multiple end users. • Management of the location targets: - T... |
a2ed1c18e57b2a5468fbd4579c87a077 | 103 246-1 | 4.1.3 Specific requirements | Application classes were established in ETSI TR 103 183 [i.1] by gathering location-based applications having the same differentiating requirement(s). An inventory of these requirements is summarized below in order to list the requirements specific to a subset of applications. ETSI ETSI TS 103 246-1 V1.3.1 (2020-10) 12... |
a2ed1c18e57b2a5468fbd4579c87a077 | 103 246-1 | 4.2 Generic location-based application use case | Table 4-1 lists the description of the different cases of location-based applications, all extracted from the inventory made in ETSI TR 103 183 [i.1] and summarized in clause 4.1. The case of airport vehicle management has been added. ETSI ETSI TS 103 246-1 V1.3.1 (2020-10) 14 Table 4-1: Example of location-based appli... |
a2ed1c18e57b2a5468fbd4579c87a077 | 103 246-1 | 4.3 GNSS-based location systems | The present document provides the functional requirements applicable to GNSS-Based Location Systems (GBLS). GBLS are defined as Location Systems using GNSS as a primary source of positioning. Hence, a GBLS shall support at least one of the GNSS methods listed in clause A.1. Optionally, it may support one or several of ... |
a2ed1c18e57b2a5468fbd4579c87a077 | 103 246-1 | 5.1 Functional requirements outline | Clauses 5.2 and 5.3 provide the functional requirements applicable to the GBLS. These requirements are derived from location based application requirements inventoried in clause 4.1. An outline of the derivation strategy is given within this clause, and summarized in annex B (mapping between location based applications... |
a2ed1c18e57b2a5468fbd4579c87a077 | 103 246-1 | 5.2 Mandatory requirements | |
a2ed1c18e57b2a5468fbd4579c87a077 | 103 246-1 | 5.2.1 Positioning techniques | The following mandatory requirements are applicable to any GBLS. In order to support the location based application requirement over a wide variety of potential service areas (in terms of characteristics such as size, location, obstacle density), it is mandatory that GBLS uses a GNSS positioning technique as the main s... |
a2ed1c18e57b2a5468fbd4579c87a077 | 103 246-1 | 5.2.2 Location-related data delivery | The following mandatory requirements are applicable to any GBLS. In order to support the application requirement to deliver services to end-users, it is expected that the GBLS is not only able to deliver the location-related data through a dedicated interface to an external entity (i.e. the application module), but als... |
a2ed1c18e57b2a5468fbd4579c87a077 | 103 246-1 | 5.2.3 Location system policies | The following mandatory requirements are applicable to any GBLS. For the majority of applications, location targets are owned by location targets users, whose private information, including identity and location-related data, needs to be protected. GBLS, as the component generating and delivering the location-related d... |
a2ed1c18e57b2a5468fbd4579c87a077 | 103 246-1 | 5.3 Requirements for optional features | |
a2ed1c18e57b2a5468fbd4579c87a077 | 103 246-1 | 5.3.1 Positioning techniques | The following optional features may be applicable to GBLS. Some of the specific requirements identified in clause 4.1.2, require the combining of GNSS measurements as a primary source of positioning with additional measurements provided by additional sensors, as a way to improve the positioning accuracy. As a consequen... |
a2ed1c18e57b2a5468fbd4579c87a077 | 103 246-1 | 5.3.2 Location-related data content | Some of the applications require location target movement information, in addition to their position. This information is mainly target speed and acceleration, heading, angular speed and angular acceleration. Some of this information can be reconstructed at application module level, based on the position alone. However... |
a2ed1c18e57b2a5468fbd4579c87a077 | 103 246-1 | 5.3.3 Location-related data delivery | The availability of a location service is a requirement for some applications. As a major contributor to the service provision, GBLS itself may therefore be required to be able to provide location-related data in a specified percentage of time (also called availability). This ability mainly depends on three GBLS parame... |
a2ed1c18e57b2a5468fbd4579c87a077 | 103 246-1 | 5.4 GBLS Functional requirements summary | Figure 5-1 gives a summary of the GBLS functional requirements identified above. Figure 5-1: Functional requirements for GNSS-Based Location Systems Provide location of Location target(s) using GNSS Technological requirements Data content requirements Data Delivery requirements System Policy requirements Multi- sensor ... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 1 Scope | The present document defines a reference scenario for a mass-transportation accident (MTA) in a rural environment. The scenario includes definition of the responders involved and their gross communication needs without specifying the network technologies involved. Finally the topology modelling of the responders involv... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 2 References | |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks in... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 3 Definitions, symbols and abbreviations | |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: accident: unplanned, unexpected, unintended and undesirable happening which results in or has the potential for injury, harm, ill-health or damage [i.7] casualty: individual in the incident area and requiring evacuation including those... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: CCP Casualty Collection Point CFECC Coordinating Field Emergency Control Centre COP Common Operating Picture DCP Deceased Collection Point EC European Commission ECC Emergency Control Centre EMTEL EMergency TELecommunications ET Emergency Team... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 4 Disaster scenario | |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 4.1 General | This clause firstly defines a mass transportation accident (MTA) scenario. Subsequently the response actions by emergency services to this scenario are defined in terms of the services involved, actors, roles, and organizational structures. The main characteristics of an MTA in a rural environment are: • Many casualtie... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 4.2 Scenario definition | The disaster scenario is a train crash due to a collision with a road vehicle at a level crossing located in a sparsely populated countryside environment. Some coaches of the passenger train overturn resulting in 170 casualties. The overhead line is not damaged. 120 casualties are not injured, 30 are slightly injured, ... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 4.3 Tasks and activities | This clause defines the response entities (i.e. actors) and their roles within the incident area in handling the accident. The main entities are emergency services and relevant authorities and/or NGOs supporting the emergency services. Depending on local/national organization of services and division of tasks/responsib... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 4.4 Accident response actions | |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 4.4.1 General | The actions of the actors (defined in clause 4.3) in the incident area of this particular scenario are further defined below including overall duration for each action. Figure 4.2 shows the general organizational hierarchy of the teams of actors (responders) involved. Figure 4.2: Responder organizational hierarchy |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 4.4.2 Emergency management | Deployed emergency services set up their own management structure in terms of service field emergency control centres (FECCs) and SubService emergency control centres (SECCs), as shown in figure 4.2. The actions in table 4.1 are sorted according to their ideal occurrence. In fact, nearly all actions of all involved act... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 4.4.3 Risk management and damage mitigation | Risk management is a key response activity which is in the MTA scenario mainly related to the hazard area. The deployed emergency services have to identify risks, assess risks, and plan risk mitigation measures. Tables 4.2 and 4.3 describe main activities of fire-fighting and rescue emergency services. Table 4.2: Fire-... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 4.4.4 Casualty logistics | The activities related to casualty management are depicted in figure 4.3. Injured casualties are either transported directly to hospitals ("immediate medical evacuation - medevac") or taken to the temporary care centre (TCC). Depending on their health status and depending on available resources these casualties are eit... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 5 Information exchanges | |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 5.1 General | The response organizations involved in the MTA will include those who are active in the incident area and others who remain outside of this area (i.e. in the off-site/support area). Information exchanges arising from the scenario between organizations solely within off-site areas are out of scope as they are assumed to... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 5.3 Communication needs by action | |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 5.3.1 Emergency management | Generic (qualitative) emergency management communication needs of the involved emergency services are listed in the following tables. Quantitative parameters will be described in clause 5.4. task report report task higher level of hierarchy lower level of hierarchy act / instruct evaluate / plan / decide check / adjust... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 5.3.2 Risk management and damage mitigation | |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 5.3.2.1 Fire-fighting | Figure 5.3 depicts the information exchanges for the fire-fighting tasks in the described MTA. Figure 5.3: Fire-fighting information exchanges The main information exchanges are as follows: • Deployed teams issue continuously updated status reports and demand notification towards the higher management levels. • In the ... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 5.3.2.2 Rescue | Figure 5.4 depicts the information exchanges for the rescue tasks in the described MTA. The main information exchanges are as follows: • Deployed teams issue continuously updated status reports and demand notification towards the higher management levels. • In the opposite direction, higher management levels inform low... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 5.3.2.3 Maintenance of public order | The envisaged MTA scenario does not involve dedicated on-site police control centres (FECC/SECC). There are direct information exchanges between police teams and the off-site ECC. Table 5.5: Information exchanges maintenance of public order Source to destination(s) Type of information Main communications service Main r... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 5.3.2.4 Provisions | Information exchanges between LEMA and shelters outside the incident area are out of scope of the present document. The LEMA provides general support to the deployed emergency services both directly via the CFECC and indirectly via the ECC. |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 5.3.3 Casualty logistics | |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 5.3.3.1 Overview | Information exchanges related to treatment and medical evacuation of casualties (see figure 4.3) are depicted in figure 5.5. The holding area serves as buffer for arriving transport and medical evacuation vehicles and emergency teams. Figure 5.5: Health service information exchanges |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 5.3.3.2 Treatment and medical evacuation | The main objective of MCI logistics in the incident area and of medical evacuation logistics is keeping track of all casualties. Rough knowledge of all casualties' current locations is desirable, but detailed movement patterns are not required. An overview of remaining casualties in vicinity of the CCP(s), patients ent... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 5.3.3.3 Temporary shelter and evacuation | Information exchanges related to evacuation coordination are listed in table 5.9. Table 5.9: Information exchanges temporary shelter and evacuation Source to destination(s) Type of information Main communications service Main requirements SECC relevant authority/NGO temporary shelter to emergency teams Tasks, decisions... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 5.4 Characteristics of emergency communication services | |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 5.4.1 General | This clause describes main characteristics of emergency communications services. As described above a major share of the information exchanges requires real-time communication. A detailed discussion of related quality of service and quality of experience requirements is available in ETSI TR 102 643 [i.12]. |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 5.4.2 Speech services | |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 5.4.2.1 Main requirements | Speech 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 several universal requirements exist, characterized by: Speech intelligibility and quality: that received speech is capable of being unders... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 5.4.2.2 PMR group call channels | The number of required voice channels depends on the number of involved emergency service disciplines and the management structure: ETSI ETSI TS 103 260-2 V1.1.1 (2015-05) 28 • 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 as... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 5.4.3 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 authorized emergency agent(s), and then deploy the appropriate technology to contact them. This ... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 5.4.4 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 an emergency team leader. This information may also include ... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 5.4.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 minimize end to end delay, especially for applications su... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 6 Topology model | |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 6.1 General | Topology modelling is generally used to represent a network's layout and dynamics mathematically in terms of the topology of the network nodes, represented here by the scenario actors. Algorithms may be chosen to depict properties such as the location and motion of the nodes, and whether nodes switch on/off during the ... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 6.2 Model graphics | Figure 4.1 in clause 4.2 shows the physical layout of the incident area. Figure 6.1 shows a snapshot of the incident area at the highest point of activity, complying with the requirements defined in clause 6.3 regarding the positions in the incident area and the mobility of the actors. ETSI ETSI TS 103 260-2 V1.1.1 (20... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 6.3 Model specification | |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 6.3.1 Scenario quantities | This clause specifies the topology of the actors and physical locations involved, together with their properties and parameters. An implementation of the reference topology of this type of event shall conform to the following model, made of a set of tables and illustrations. It is specified here in a top down approach,... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 6.3.2 Locations | |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 6.3.2.1 On-site | Table 6.2: On-site locations Location Requirements on position Time-variant parameters Time-invariant parameters Hazard area Inside incident area. For simplicity, a stationary hazard area is considered only. n/a Centre coordinates, size Casualty Collection Point(s) (CCP) Outside hazard area, inside incident area. Numbe... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 6.3.2.2 Off-site | Table 6.3: Off-site locations Location Notes Time-variant parameters Time-invariant parameters Ambulance station(s) Nearest station: 25 km distance Journey time to incident area (CCP, TCC, holding area) Capacity (number of teams / ambulances available) Fire station(s) Nearest station: 15 km distance Journey time to inc... |
e68c64a86967323a7070a20833555ccf | 103 260-2 | 6.3.3 On-site actors | On-site actors and their properties are listed in table 6.4. The notation for the topology properties are as follows: /P: Position /M: Mobility /B: Start condition /MT: Mid-term step /E: Stop condition Table 6.4: On-site actors Actor Requirements on position and mobility Requirements on behaviour and presence on site (... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 1 Scope | The present document defines an earthquake disaster scenario. The scenario includes definition of the responders involved and their gross communication needs without specifying the network technologies involved. Finally the topology modelling of the responders involved is defined, in terms of their disposition in the I... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 2 References | |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks in... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 3 Definitions and Abbreviations | |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: casualty: individual in the incident area and requiring evacuation including those who are: (i) non-injured, but affected, (ii) injured and treated on site, (iii) injured and needing treatment off-site (medevac), and (iv) deceased. com... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: CCP Casualty Collection Point CFECC Coordinating Field Emergency Control Centre CFEEC Coordinating Field Emergency Control Centre COP Common Operating Picture DCP Deceased Collection Point ECC Emergency Control Centre EM-DAT The International ... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 4 Disaster scenario | |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 4.1 General | This clause defines an earthquake (EQ) scenario, firstly in terms of its main constituent events and secondly by its physical consequences. Subsequently the response actions by emergency services to this scenario are defined in terms of the casualties involved, the actors and organizations, overall operating modes, dur... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 4.2 Scenario definition | |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 4.2.1 General | A summary of recent EQ s and their effects is given in annex A as examples of the scale of events being considered. The disaster scenario is an EQ in an urban area. It is of a magnitude sufficient to cause a multitude of physical effects, such as collapsed buildings, disruption of infrastructure, lack of power, lack of... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 4.2.2 Physical effects | |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 4.2.2.1 Collapse of buildings | There is a large number of buildings in varying state of collapse. In area A the damages are to domestic structures (blocks of flats) a shopping centre and a school with an enrolment of 350 students and a staff of 100 officers. A total of 1 750 individuals are initially unaccounted for, many of them suspected to be tra... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 4.2.2.2 Fire | There is a fire in a department store in the shopping centre (area A), threatening to spread to other shops as well. ETSI ETSI TS 103 260-1 V1.1.1 (2015-05) 12 In Area B there is a fire in a bus garage/ workshop. |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 4.2.3 Disruption of infrastructure | |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 4.2.3.1 Road access | 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. A result of the limit is that trucks, such as standard fire engines, are unable to enter into the incident area. It is initially unclear whether this bridge has got struct... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 4.2.3.2 Power | There is a complete loss of power within the incident 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 others are faced with periodical power cuts. |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 4.2.3.3 Water supply | Water pipes, both in areas A and B, have been broken, leading to a total loss of water supply. |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 4.2.3.4 Sanitation | Sewage systems, both in areas A and B, have been broken and are non-functional. |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 4.2.3.5 Telecommunication | There are widespread damages to telecommunications systems in the incident area. Expert teams are brought in to do repair. |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 4.3 Tasks and activities | This clause defines the response entities (actors) and their roles within the incident area in handling the disaster. Depending on local/ national organization of services and division of tasks/ responsibilities, the entities involved and their individual areas of work may differ in practice. In addition to their prima... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 4.4 Disaster response actions | |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 4.4.1 General | The actions of the actors (defined in clause 4.3) in the incident area of this particular scenario are further defined below including overall duration for each action. A more detailed timeline is given in annex C. ETSI ETSI TS 103 260-1 V1.1.1 (2015-05) 13 Figure 4.2 shows the general organizational hierarchy of the t... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 4.4.2 Emergency management | Deployed emergency services set up their own management structure in terms of service field emergency control centres (FECCs) and SubService emergency control centres (SECCs), as shown in figure 4.2. The actions in table 4.1 are sorted according to their ideal occurrence. In fact, nearly all actions of all involved act... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 4.4.3 Risk management and damage mitigation | Table 4.2: Road access Involved actors Actions Start point Intermediate point End point Duration Roads department/ geologists Initial assessment 30 minutes after the EQ when problems are reported by operational emergency services When assessment is made and reparative actions are initiated. Temporary repair completed H... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 4.4.4 Casualty Logistics | The activities related to casualty management are depicted in figure 4.2. Injured casualties are either transported directly to hospitals ("immediate medevac") or taken to the temporary care centre (TCC). Depending on their health status and available resources these casualties are either handed over to temporary shelt... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 5 Information Exchanges | |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 5.1 General | The response organizations involved in handling the EQ will include those who are active in the incident area and others who remain outside of this area (i.e. in the off-site/support area). Information exchanges arising from the scenario between organizations solely within off-site areas are out of scope as they are as... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 5.3 Communication needs by action | |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 5.3.1 Emergency management | Generic (qualitative) emergency management communication needs of the involved emergency services are listed in the following tables. Quantitative parameters will be described in clause 5.4. Table 5.1: Emergency management within incident area Source to destination(s) Type of information Main communication service Main... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 5.3.2 Risk management and damage mitigation | |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 5.3.2.1 Road access | The communication lines used by the roads department field workers are given in table 5.3. ETSI ETSI TS 103 260-1 V1.1.1 (2015-05) 22 Table 5.3: Road access Source to destination(s) Type of information Main communication service Main Requirements Assessment team/ site management (roads) to central authority (roads depa... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 5.3.2.2 Assessment and handling of specific risks | Officers summoned to the incident area to assess and handle specific risks (e.g. geologists, building surveyors) will need communication both to CFECC and to their "home bases" as shown in table 5.4. ETSI ETSI TS 103 260-1 V1.1.1 (2015-05) 23 Table 5.4: Assessment and handling of Specific Risks Source to destination(s)... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 5.3.2.3 Fire-fighting | Figure 5.3 depicts the information exchanges for the fire-fighting tasks in the described earthquake. ETSI ETSI TS 103 260-1 V1.1.1 (2015-05) 24 Figure 5.3: Fire-fighting information exchanges The main information exchanges are as follows: • Deployed teams issue continuously updated status reports and demand notificati... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 5.3.2.4 Rescue | Figure 5.6 depicts the information exchanges for the rescue tasks in the described earthquake. The main information exchanges are as follows: • Deployed teams issue continuously updated status reports and demand notification towards the higher management levels. • In the opposite direction, higher management levels inf... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 5.3.2.5 Maintenance of public order | The communication needs for maintaining public order in an EQ are depicted in table 5.7 Table 5.7: Maintenance of public order Source to destination(s) Type of information Main communications service Main Requirements ECC to emergency teams/ officers (before SECC has been established) Dispatching Voice Good speech inte... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 5.3.2.6 Provisions | The communication needs concerning provisions are listed in the tables 5.8 to 5.10 below. Table 5.8: Power supply restoration Source to destination(s) Type of information Main communication service Main Requirements Power corporation (central) to CFECC Status reports, availability, constraints, demand notification, ris... |
44fd21f096236c80c3014aba7b37f64a | 103 260-1 | 5.3.3 Casualty logistics |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.