2020

STRATEGY Project

Source: https://strategy-project.eu/

Gaps identified for Stream 1: Search and Rescue

Code	Title/Description	End-users Prioritisation	Relevant opportunities
SaR-1	Standards for technical specifications of UAVs for SaR operations. Currently, many UAVs in the market can support similar features, such as different types of information and imageσ (e.g., thermal images, oblique images, videos and object identification, etc). No particluar standards have been set and, during the project, STRATEGY partners could support testing of specific characteristics, that can be useful for FRs during SaR operations.	Important	Solutions #2, #7 (Annex I) as well as the current CEN CWA 17357:2019 [Urban search and rescue (USaR) robotic platform technical and procedural interoperability – Guide] from INACHUS project (Error! Reference source not found.). Also [20] can be used for information regarding American roadmap for UAVs as a guide. ICAO also has established a working group “The Remotely Aircraft Systems Panel” that currently works on the topi of standardisation for UAS.
SaR-2	Operational Standards for the use of UAVs in SaR operations, in order to minimize endusers exposure to hazards.	Very Important	Operational specifications related to the use of UAVs in every day operations have to be used. It can be supported by solutions #2, #7, #26, #40 as listed in Annex I from STRATEGY partners. Also the Iso 21384-3:2019 could provide some information altough it is for commercial operations. The ASTM F3379-20 could provide specific
				infromation for safely remote pilot of UAS.
	SaR-3	Standardised coordination procedures and means in SaR operations	Important	No specific opportunity identified at this stage
	SaR-4	Standardisation for processes regarding operational needs assessment for a fast and effective response basic on specific criteria (e.g. first aid needs, structural needs, etc.).	Very Important	No specific opportunity identified at this stage
	SaR-5	Standardisation for detectors (e.g. sound) in buildings for SaR operations.  Detectors are key players in damaged buildings for the localization of entrapped people. In this aspect, standardised detectors for such purposes are extremely useful.	Important	No specific opportunity identified at this stage
	SaR-6	Standards for acquiring digital information from victims during SaR operations.	Important	This proposed standardisation item matches with opportunities #15 and57 #34 (IN-PREP project, IDIRΑ project, PFIF de-facto standard) from the list of opportunities (Annex I) and could be tested for further exploitation in terms of standards.
	SaR-7	Standardisation of biometric transmitters integrated in the equipment of First Responders and interconnected with CC systems for personal safety alerts.	Very Important	This gap can be tested with wearable devices with biometric information in order to define exact standardised specifications for similiar equipment and application during SaR operations (#16 list of solutions – Annex I). In addition CWA 17502:2020 can be used as a basis for further development.
	SaR-8	Existing radio communication technologies for mapping of the location and tracking of FRs during SaR operations inside buildings or underground places. Wireless networks that exist in buildings can be used as invisible detectors to track and monitor the position of FRs inside buildings based on wireless communication protocols.	Very Important	No specific opportunity identified at this stage
	SaR-9	Standardised wearable device tags able to read wireless signals and send data to the coordination center. Wearable devices that work as receivers and transmitters of wireless networks to support the location of FRs inside buildings.	Very Important	No specific opportunity identified at this stage

Gaps identified for Stream 2: Critical Infrastructure Protection

Code	Title/Description	End-users Prioritisation	Relevant opportunities
CIP-1	Standardised      format      of      DSS       and Coordination        Centers        of         Critical Infrastructure in terms of equipment. Basic specifications and requirements in terms of equipment and space can be defined for proper coordination centers of critical infrastructures.	Important	The series of EΝ ISO 11064-1, 11064-2, 11064-3, 11064-5, 11064-6 and 11064-7 can be used as a basis to further improvements.
CIP-2	Standardised      format      of      DSS       and Coordination Centers of Critical Infrastructure in terms of interface (GUI and information) and supported functions. Basic specifications and minimum requirements for the Coordination Centers	Important	No specific opportunity identified at this stage

Code	Title/Description	End-users Prioritisation	Relevant opportunities
	of Critical Infrastructures can be set up in terms of user interface, available information, supported functions and graphics user interface.
CIP-3	Standardised post crisis needs assessment tools integrated to existing DSS of Critical Infrastructure.	Important	Based on the list of solutions (Annex I), solution #27 can be used to test such a kind of proposed standardisation item.
CIP-4	UAVs should be able to identify priority areas for mapping into existing and future DSS. Interoperability between UAVs and DSS.	Important	It can be supported by solutions #2, #7, #8, #26 as listed in Annex I from STRATEGY partners, as a testbed.
CIP-5	Standardised intervention plans of first responders for the CI domain.	Important	Potential solution #23 and #38 from Annex I.
CIP-6	Standardised process and methods for dynamic risk evolution incorporated to Critical Infrastructure existing DSS (e.g. fire spread and progress of fire).	Very Important	No specific opportunity identified at this stage
CIP-7	Standardised threat detection systems for Critical Infrastructures installed in CI assets and linked with the DSS and Coordination Centers.	Very Important	Standardisation item already in a mature state related to CEN CWA 17356:2018 (Table 12) and #23 from Annex I.
CIP-8	Standardised data exchange and common Standard Operating Procedures, including security plans, for interconnected CI. Crossorganisation interoperability. Maybe partially covered by information security standards in terms of organisation (e.g. ISO 22396).	Very Important	No specific opportunity identified at this stage
CIP-9	Standardised Risk assessment modelling process for Critical Infrastructure with an all-hazards approach.	Very Important	This gap proposed as standardisation item can be tested based on solution #3 and #22 (Annex I) both targeted on risk assessment for critical infrastructures.
CIP10	Standardised formats and protocols for more efficient information/data sharing between Critical Infrastructure. Possibly solutions related to Command and Control and data sharing could be used for testing.	No specific information	Solutions #19 from Annex I. Partly solution #23 could supporti it for further training.
CIP11	Standardisation of UAVs in data collection and transfer in the daily operation of Critical Infrastructure.	No specific information	It can be supported by solutions #2, #7, #8, #26, #40 as listed in Annex I from STRATEGY partners.
CIP12	Standardised procedures for registration, authentication and authorisation of users in the Coordination Centers system.	Very Important	Solution #22 could be usd as a test to a standardised procedures for the authentication, authorisation and registration of users.
CIP13	Standards for the management of climate change-induced hazard and data interoperability with external weather forecasting for the protection of Critical Infrastructure.	No specific information	No specific opportunity identified at this stage

Gaps identified for Stream 3: Response planning

Code	Title/Description	End-users Prioritisation	Relevant opportunities
ResPl-1	Standards for technical characteristics and features of simulation systems, used for the training of First Responders.	Very Important	Solutions already available from IN-PREP project (#11, #13, #14 from Table in Annex I could support the implementation of a relevant standard.
ResPl-2	Standards for tools regarding the management of resources in operations, e.g. map based tools with coordinates of resources.	Very Important	Solutions #11, #21, #32 and #33 (Annex I) could support the implementation of this standard.
ResPl-3	Process standards to facilitate interoperability between organisations and cross-border cooperation, to enhance synergies and develop interagency frameworks.	No specific information	Solutions #11 and #30 (Annex I) could support the implementation of this proposed standard.
ResPl-4	Operational          Standards             for                debriefing processes after operations, fostering lessons learnt.	No specific information	No specific opportunity identified at this stage
ResPl-5	Standards for innovative solutions enabling the matching between established procedures and capabilities.	Important	Solutions #15 and #30 (Annex I) could be used as a basis for the implementation of such a standard.
ResPl-6	Standardise capabilities in front of preestablished scenarios.	Important	Solution #30 (Annex I) could be used as a basis for the implementation of such a standard.
ResPl-7	Building a common simulation environment.	Very Important	IN-PREP solution can be used for the implementation and testing of such a standard. In addition, the CEN CWA 17515:2020 can be used as a basis (Table 12).
ResPl-8	Standards for pre-planning in-place sheltering. Despite the fact that a couple of standards exist, these standards are not European and may not be devoted to in-place sheltering. They could be used as a basis along with updates could be suggested for Europe.	Very Important	Non European standards (e.g. NFPA 1600) could be used as a basis for the developemnt of a relevant European standard.

Gaps identified for Stream 4: Command and Control

Code	Title/Description	End-users Prioritisation	Relevant opportunities
CC-1	Standardisation of interfaces, to promote data interoperability to get the same picture of the disaster.	Very Important	Currently, various specific technical standards exist, that are related to disaster management. The what extent, these standards cover, is not known at this stage. These standards could be used as a basis for testing and further updates if necessary in specific parts of STRATEGY. CEN CWA 17513:2020.
CC-2	Standardisation of semantic interpretation of the exchanged data.	No Specific Information	Current CEN CWA 17513:2020 “Crisis and disaster management – Semantic and syntactic interoperability” can be used for further exploitation and updates for a new standard.
CC-3	Standardisation of information and information management exchange across borders and organisations.	Very Important	Currently ISO 223797:2014 and EN ISO 22397:2018 exist. As a basis, the current descriptions in existing standards in order to fully test their applicabilty in FR organisations and command and control centers. In addition, ISO 22396:2020 could cover the aspect of information exchange between organisations. This needs further exploitation to check if it

			can cover crisis management situations and especially the cross-border domain.
CC-4	Develop a standardised electronic triage system to improve the logistics and the situation awareness.	No Specific Information	Currently, Emergency Data Exchange Language (EDXL) provides two standards for hospital availability and tracking of emergency patients. These data languages could be further improved to be standards in ETSI or to be implemened futher in order to improve a triage data language.
CC-5	Agreed and standardised format of data commonly shared and standardised situation report, to avoid loss of time in the data homogenization process.	Very Important	Possibly OASIS “Emergency Data Exchange Language Situation Reporting (EDXL-SitRep) Version 1.0”, Solution #33 or CWA 17513:2020.
CC-6	Need of standard and secure protocols for data sharing (what data, where to find, how to receive; the formats are less relevant).	No Specific Information	Possible opportunity: DIN SPEC 91287 “Data interchange between information systems in civil hazard prevention” already exists. Further improvements may be proposed
CC-7	Interconnection of Information Databases/Repositories at National and European Level.	Important	No specific opportunity identified at this stage
CC-8	Standardise methodology for sourcing information (social media, tweets, crowd source information).	No Specific Information	ISO/DIS 22329  “Security and resilience – Emergency management – Guidelines for the use of social media in emergencies” already exists. This could be futher exploited and tested and become a European standard.
CC-9	Standardisation of data security (encryption) and privacy both between organisation and between organisations and citizens.	Very Important	Solution #5 from Annex I.
CC10	Standardisation of information display (e.g images, videos) for specific tools and GUI of CC systems.	Very Important	Soutions #32, #33, #35 (Annex I) related to ENGAGE C3i could be used as a testbed to supoort the development of such as standard.
CC11	Specification of the data requirements that need to be transmitted by the sensor to the central system.	Very Important	Solution #19 could partially support the development of such a gap. As this gap is not only directly related to crisis management other purely technical standards could be checked for best results.
CC12	Classification of information based on the criticality/importance of information and response level.	Less Important	Solution #22 could support such kind of a development as an example from critical infrastructure classification.
CC13	Resource Management tools: Standardisation of assignment of resources to a mission, standardised procedures for assigning resources. Standardised capability mapping (incl. all organisations, tasks, roles,	Very Important	Solution #21, #25, #32, #33 (Annex I).

	responsibilities, equipemtn, personnel) and procedures/forms for contacting (other authorities point of contacts).
CC14	Emergency      Response       Units       in International Operations: Standardise definition of responsibilities and roles of organisations and authorities regarding international operations. Necessary to have the same norms (like e.g. INSARAG). This norm enables to work together across countries, but also across types of services. Standardisation on EC level is required in order to come to an agreement about automatic registration of location, availability, status and type of emergency response units entering the emergency services’ communication network of another country. Possibly covered by DKE standard.	Important	DKE standard (DIN VDE V 0827-1) could be checked as a generic basis and critical updates based on INSARAG norms could be applied.
CC15	Standardisation of the use of various types of unmanned assets in the standard operating procedures of international teams, their interoperability and of the type of output data.	No Specific Information	Solutions (Annex I) #26, #39, #40. Other related to UAVs (#2, #7) solutions could be used to support a development even if not directy related to the Command and Control stream.
CC16	Standardised capabilities of asset registries in CC systems.	Very Important	Solution #32, #33 related to ENGAGE 3Ci.
CC17	Interoperability of Systems and RealTime Situational Awareness in Firefighting.	Very Important	Solution #32, #33, #36.
CC18	Minimal standards are required for Emergency Medical Services in Europe and inter-connectivity between dispatch centres across borders from WHO (Regional office in Europe).	No Specific Information	No specific opportunity identified at this stage
CC19	Need for standardised process and technology for obtaining and share Common Operational Picture among all stakeholders.	Very Important	Solution #5, #31, #32, #33, #35 could be used.
CC20	Standardisation of minimum common terms/formats and set of requirements for the interoperability of CC systems. Standardised interoperability with legacy systems.	No Specific Information	No specific opportunity identified at this stage
CC21	Standardisation of “limited key information” to share (pre, during, post incident) to improve preparedness, coordination and debriefing (between different actors	No Specific Information	No specific opportunity identified at this stage
	and different hierarchical levels) must be standardised. The minimum requirements should be defined in terms of procedures.
CC22	Standardisation on EC level is required to define various interoperable levels of talk-groups of TETRA and TETRAPOL terminals and an Inter System Interface (ISI) in cross-border level. Currently, while the two systems are interoperable, a topic about interoperability in cross-border domain is raised. It could be further exploited. Past projects have tested interoperability between systems with good results.	No Specific Information	No specific opportunity identified at this stage
CC23	Standardisation for providing dynamic information during an emergency (i.e. evacuation information in real time, location, infrastructure availability, exit routes availability).	No Specific Information	No specific opportunity identified at this stage
CC24	Need for standard messaging to assist digital volunteers.	No Specific Information	This gap may possibly be related to ISO 22319:2017 (Guidelines for planning the involvement of spontaneous volunteers). This ISO could be used as an input to develop a similar approach in terms of digital volunteers.
CC25	An Incident command system, operable at top level (interagency and for cross border incidents) needs an harmonization of command practices, in order to have a better interoperability in case of major incidents; and to be fully connectable to other command systems in the world, e. g. US IC system and UN practices.	No Specific Information	No specific opportunity identified at this stage
CC26	Standardised validation registered users using a role-based approach. Clear definition of user profiles, types and rights for each role. Functional rights according to standardised operational procedures.	Very Important	Solutions #31, #32, #35
CC27	Standardisation of interoperability of the system with mobile devices (such as tablets, smartphones).	Very Important	No specific opportunity identified at this stage
CC28	Standardisation   of            processing                of personal data by the system.	Very Important	No specific opportunity identified at this stage

Gaps identified for Stream 5: Early Warning and Rapid Damage Assessment

Code	Title/Description	End-users Prioritisation	Relevant opportunities
EWRDA-1	Standardisation of interfaces and format for data sharing between devices and equipment.	Very important	No specific opportunity identified at this stage	No specific opportunity identified at this stage
EWRDA -2	Standardised way to communicate public alerting and warning for	No Specific Infromation	The existing ISO for landslides (ISO 22327:2018), the under development for tsunamis (ISO/WD 22328-3) and the generic ISO 22328-1:2020 for	The existing ISO for landslides (ISO 22327:2018), the under development for tsunamis (ISO/WD 22328-3) and the generic ISO 22328-1:2020 for
	earthquakes and other natural disasters, (e.g. floods).	earthquakes and other natural disasters, (e.g. floods).		community based early warning systems coud be used as a basis and further capitalise on it. Standardisation for providing dynamic information during an emergency (i.e. evacuation information in real time, location, infrastructure availability, exit routes availability).
EWRDA -3	Standardised instrumentation and monitoring of buildings for providing alerts and rapid damage assessment.	Standardised instrumentation and monitoring of buildings for providing alerts and rapid damage assessment.	Important	Solution #19 (Annex I) can be used for intrumentation and provide alerts and automatic calls to 112. Solution #37 is also promising for the case of earthquakes.
EWRDA -4	Standardised real-time and near realtime damage assessment methods for fast response based on scientific methods.	Standardised real-time and near realtime damage assessment methods for fast response based on scientific methods.	Very Important	Solution #4, #37 (Annex I)
EWRDA -5	Standards to facilitate interoperability of local/regional platforms for exchanging information (maps, logistic data, assessment data) with international platforms.	Standards to facilitate interoperability of local/regional platforms for exchanging information (maps, logistic data, assessment data) with international platforms.	Important	No specific opportunity identified at this stage
EWRDA -6	UAVs in the use of monitoring, surveillance and early warning.	UAVs in the use of monitoring, surveillance and early warning.	Very Important	Solution #17 (Annex I)
EWRDA -9	Specify type of alerts and measurements reported by the resources at the site scene. Possibility to filter the information using multiple criteria.	Specify type of alerts and measurements reported by the resources at the site scene. Possibility to filter the information using multiple criteria.	Very Important	No specific opportunity identified at this stage

Gaps identified for Stream 6: CBRN-E

Code	Title / Description	End-users Prioritisation	Title / Description End-users Prioritisation Relevant opportunities
CBRNE-1	Methods and guidelines for establishing a sampling strategy and chain of custody (CBRNE). Standardised methods and guidelines for establishing a sampling strategy. Need for pre-standardisation efforts to harmonize assessment of complex indoor infrastructures for CBRN contamination.  Standard operating procedures for sampling of CBRN agents, including the chain of custody.	Important	No specific opportunity identified at this stage
CBRNE-2	Standards and guidelines for use of unmanned aerial systems and their data collection for CBRN. Use of unmanned aerial systems for supporting situational awareness operations. Standardised approach on how to employ UAVs in CBRNE scenarios, for data collection to avoid dissemination of contamination from the hot zone. How to decontaminate, and how data can be rapidly shared among users in the field.	Very Important	Solutions #7, #17, #26 could support the development of such standard.

Gaps identified for Stream 7: Training

Code	Title/Description	End-users Prioritisation	Relevant opportunities
TR-1	Standardisation of exercises on EU and international level and common scenarios. How to plan, implement and evaluate commonly accepted procedures.	Very Important	Built on already accepted CEN CWA 17514:2020 Systematic assessment of innovative solutions for crisis management – Trial guidance methodology. Solutions #8, #23, #24, #26, #28.
TR-2	Standardised procedures for the evaluation and sharing of lessons learnt between First Responders organisations.	Very important	Solution #13 and #14 (Annex I).
TR-3	Standardised procedures followed by social organisations which would facilitate the work from FRs.	Important	No specific opportunity identified at this stage
TR-4	Standardised training for EMS professionals according to the WHO guidelines.	No specific information	Solution #13 and #14 (Annex I) could be used as the basis for

			testing and implementing a relevant standard.
TR-5	Standardised training for managing the effects of new technologies.	Less Important	No specific opportunity identified at this stage
TR-6	Psychosocial support of victims and FRs after disasters. Harmonised best practices on how to deal with the psychological and social support of both victims and first responders after disasters.	No specific information	No specific opportunity identified at this stage

Gaps identified for Stream 8: Terminology

	Code	Title/Description	End-users          Relevant opportunities Prioritisation
TER-1	Technical standards for multi-lingual interfaces in systems, providing a common understanding.	Less Important	The CWA 17335:2018 could be partially used to test and validate the creation of suc a standard and also used for common terms in the interfaces.
TER-2	Standardised nomenclature and terminology with regards to big data.	No specific information	No specific opportunity identified at this stage
TER-3 (CBRN- E)	Technical standardisation for map-based Command and Control systems, providing visual insight and information about the type and amount of substance and common symbols for similar CBRN-E events, for enhanced Situational Awareness in CBRN-E emergencies.	Very Important	Solution #9 (Annex I).

TER-4	Standardised common symbols and icons regarding natural hazard emergencies in EU level.	Very Important	May partially be covered by ISO 22324:2015. It could be used for further updates and acceptance in EU level. In addition, CWA  17335:2018 could be used for the termonilogy or further improved with common symbols and icosn.
TER-5	Standardisation in classifications and terms regarding meteorological hazards and conditions.	No specific information	Solution #9 (Annex I).
TER-6	Standardisation in the curricular education (terms, symbols, standard procedures etc.) of Emergency Medical Services.	No specific information	No specific opportunity identified at this stage
TER-7 (CC)	Standardisation of semantic interpretation of the exchanged data.	No specific information	CEN CWA 17513:2020 “Crisis and disaster management – Semantic and syntactic interoperability” could be used as a basis for testing and further updates (Table 12).
TER-8	Terminology during command and control of an operation for improved communication between coomand and control personnel and systems.	No specific information	No specific opportunity identified at this stage
TER-9	Standardised systems for the exchange of data with the EU Civil Protection Mechanism.	Very important	No specific opportunity identified at this stage
TER-10	Standardised Social media Early Warning. Common signals for alerting, common codes, common procedures and messages that should be followed in social media.	No specific information	Already existed standard messages formats from ETSI should be considered in such a standard. Also, ISO/DIS 22322 on public warning and ISO/DIS  22324 on colour coded alerts can be also considered.
TER-11	Terminology, symbology standards for social media information. Social media are part of every day life. Terms, symbols to avoid miss-interprentation and misuse is important. Public with the proper training can be used as first responder.	No specific information	No specific opportunity identified at this stage

STRATEGY General Conclusion

1.1        

1.1.1       General conclusions related to end-users needs

• Needs and requirements of end-users expand also in various fields, from simple technological and protective equipment, that can be used in the field for search and rescue operations, to latest state-of-the-art technologies incorporated in large command and control and coordination centres.  
• Needs of end-users are not always expressed clearly.
• On the contrary end-users system requirements are clearer and more precise.
• There is significant need for interoperability in all aspects, technical and procedural. Training, terminology, common procedures and data sharing between organisations in all potential levels (cross-border, cross-sector, cross-hierarchy) and between organisations and citizens are of crucial importance and the most commonly requested. This is particularly evident in enduser needs and requirements that lie within the command and control category (section

3.2.4).

• The majority of needs is relevant to the Command and Control stream, followed by Critical Infrastructure Protection. Response Planning and Training are also of great importance (section 3.2.1).
• Standardisation of Terminology and semantics is also very important for end-users of various sectors in order to support cross-organisational operations and coordination.
• Critical Infrastructure Protection stream is closely related to needs in terms of risk assessment, Responses Planning stream relates to risk assessment and situation awareness, Command and Control stream is closely related to technical interoperability, situation awareness and easy to use systems. Early Warning and Rapid Damage Assessment stream is related both to risk assessment and communication (technical interoperability) needs. For CBRN-E stream technical interoperability and situational awareness are the most important needs categories. Training stream is related in general to training needs and similar is for Terminology stream. In addition, Terminology stream is related also to procedural interoperability (section 3.2.5).

1.1.2       General conclusions on standards

• A great variety of standards exist worldwide. The structure of standardisation bodies may provide a good overview of standards related to crisis management but this does not necessarily mean that the process is straightforward. Relevant to any topic standards could be “hidden” on less relevant committees. This is more evident as far as technical standards are concerned. D1.2 Project handbook may provide more information regarding the standardisation landscape.
• Standards vary from very generic and procedural to extremely specific, most often the technical ones.
• An effort was made to focus more on the technical committees that are more closely related to crisis management. This implies that the list is not exhaustive and other standards may exist in order to cover various issues that may arise.
• The majority of standards are related to the Critical Infrastructure Protection stream. Response Planning and Command and Control streams are the next ones with relevant existing standards (section 4.2.1).
• Mitigation is the phase in the disaster management phase with the highest number of standards (section 4.2.2).
• Many standards exist for the need category Legal/Regulations/Guidelines. Situation awareness is also related to many standards. 
• Procedural interoperability lacks significantly in available standards. 
• Technical interoperability related to crisis management do exist. In general, it may not be sufficiently covered in the crisis management domain. As a matter of fact, various standards exist that could potentially cover parts of interoperability, but more technical and thorough research is needed in the next steps of STRATEGY and has to be very specific to the final gaps/items that will be decided to proceed further to a pre-standardisation scheme. Technical standards can be endless and also many other professional/de facto standards exist and not only official.

1.1.3       General conclusions on opportunities

• CWAs are considered as opportunities for the concept of the project. Existing CWAs must be used in the framework of STRATEGY.
• Solutions that address and cover needs are also considered opportunities.
• Both CWAs and various technological solutions have been already identified.
• Future work of CEN could also be an opportunity.
• Especially for the CBRN-E stream, results from other EDA initiatives should be considered besides the solutions that have already identified in the proposal stage.

1.1.4       Comments and observations on gaps

• Important and numerous standardisation gaps are present in all streams.
• The title and scope description of standards is not always enough to understand its relevancy to a need. Moreover, in some cases technical expertise is needed, in order to recognise whether certain standards respond to specific technical needs.
• There are often overlaps between streams, disaster management phases and needs categories in both the identified needs and available standards that make the gap identification procedure more difficult. To tackle this issue, needs that belong to the same “family” have been merged together and all of the possible standards that respond to them were taken into account.
• Some gaps are specific but others are more generic, in accordance with corresponding needs.
• Effort was made to identify unique gaps, however some degree of overlapping can be identified, especially to the more generic ones. This is minimum and can be totally eliminated if the final item that will proceed to further pre-standardisation activities is better specified in WP2.
• Matching between gaps and identified opportunities seems feasible even from this early stage.
• Based on the abovementioned, gaps have been translated into potential standardisation items.
• Prioritisation of gaps follows the prioritisation of respective needs.
• In total, 98 gaps identified in all streams. For Search and Rescue stream 9 gaps have been identified, 13 for Critical Infrastructure Protection, 8 for Response Planning, 28 for Command and Control, 9 for Early Warning and Rapid Damage Assessment, 14 for CBRN-E, 6 for Training and 11 for Terminology.
• Command and control presented most of the gaps, as it covers a range of activities also highly related with technological communication and data exchange tools.
• Standardisation gaps identified are similar to other projects.
• Interoperability is encountered as an operational and technical standardisation need in almost every stream.
• UAVs are a field that is not covered by standards and this is also something pointed out from [20]. Use of UAVs is on the rise in all phases of crisis management and high need for their implementation is expressed in several streams. This is highly related with interoperability requirements, both technical and procedural.
• Standardisation of risk assessment for different aspects is also highly requested.

Annex I – List of solutions considered as opportunities

See here.