Submitted:
10 September 2025
Posted:
12 September 2025
You are already at the latest version
Abstract

Keywords:
1. Introduction
2. Background and Related Works
2.1. State of the Art
2.2. Architecture of Assoul et al. [10] and the Need for Empirical Validation
2.2.1. The Architecture
- 1.
- Time efficiency: minimizing transmission and processing times to speed up decision-making and the deployment of emergency services.
- 2.
- Optimal resource allocation: relying on distributed algorithms and decentralized computing capabilities to efficiently direct available resources (personnel, equipment, vehicles).
- 3.
- Adaptability to constrained contexts: taking into account the realities of fragile infrastructure and limited resources by integrating mechanisms such as fault tolerance, low bandwidth requirements, or the ability to operate offline.
- 1.
- The Surveillance and Alerting System (SAS): network of connected objects (IoT) deployed in buildings and strategic areas, equipped with sensors capable of detecting various incidents (fires, accidents, security threats, natural disasters) and automatically generating alerts.
- 2.
- The Edge Server Network (ESN): a set of edge servers, each equipped with FPGA cards, responsible for receiving alerts and performing distributed calculations. These servers model the city as a graph and use a distributed version of Dijkstra’s algorithm to calculate the shortest paths to the incident scene in parallel, taking service priorities into account.
- 3.
- The Intervention Order Processing System (IOPS): present in every emergency service (police, fire brigade, hospitals, etc.), this module receives alerts from edge servers, prioritizes interventions, prepares teams and coordinates communications with other entities.
- 4.
- The Intervention Team Guidance System (ITGS): also based on FPGA, it supports teams in the field by providing optimized routes and dynamically recalculating paths in the event of unforeseen circumstances (traffic jams, road closures, service unavailability).

- In terms of temporal efficiency, the system relies on a systemic reduction in latency (detection → calculation → coordination → execution), thanks to the synergy between edge processing and the distribution of decision-making intelligence.
- For resource allocation, the optimization (ESN) and decision-making (IOPS) functions are distinct but complementary, allowing the architecture to remain flexible and modular.
- In terms of ease of use, the architecture has been explicitly designed for environments with low connectivity and degraded infrastructure, but requires a particular effort in terms of maintenance, training and local supervision.
2.2.2. The Need for Validation
3. Materials and Methods
- The consistency and robustness of the proposed architecture, given the actual constraints in the field;
- The validity of the theoretical analyses summarized in Table 1;
- Expert opinion on the viability and feasibility of the project in the short, medium and long term in contexts comparable to that of Chad;
- The prioritization of tasks to be undertaken for the effective implementation of the system;
- Strategic recommendations for researchers, engineers, public decision-makers and institutions involved in urban crisis management.
- We started by producing all the survey materials (project description, consent form, questionnaire, etc.). Each produced material was then cross-checked by at least two independent experts to ensure their neutrality and accessibility. Each time it was necessary, a pilot phase with five respondents allowed for adjustments to be made to the format and comprehension of the material. (see steps 1 to 3 in Figure 2)
- We then filtered this list to retain only the experts whose profiles met well-defined criteria (including at least five years of professional experience, proven expertise in the relevant fields, diversity of gender and affiliation), as presented in Section 3.2. A total of 100 experts were selected (step 5);
- An initial contact was made with the 100 experts to present the project and the study protocol to them in order to obtain their explicit consent. We obtained the consent of 83 experts; 06 others explicitly stated that they did not have time to participate in the study, while the remaining 11 simply did not respond (step 6);
- A summary description of the architecture and the paper of Assoul et al. were sent to the 83 participants without including the critical analyses previously formulated, in order to avoid confirmation bias. However, our analysis matrix was provided to them as an empty form so that they could study the architecture on the same basis as us (step 7);
- Participants had one month to study the proposal and carry out their own multidimensional analyses using criteria including those we had selected and which guided our own theoretical analysis (step 8);
- We then sent our theoretical analysis to the participants so that they could compare it with their own. We have also attached the questionnaire (step 9);
- Participants had an additional two weeks to cross-reference the analyses and complete the questionnaire independently (step 10);
- After this new deadline, 78 of the 83 participants submitted their responses to the questionnaire. Despite several reminders over an additional week (step 11), we were unable to obtain responses from the remaining 05 experts. Once the data had been collected, a descriptive and thematic statistical analysis was used to assess the level of validation of the initial hypotheses, draw up a feasibility profile, prioritize the critical steps to be taken for deployment, and identify sectoral recommendations (step 12).

3.1. Presentation of the Questionnaire and the Evaluated Dimensions
3.2. Survey Participant Profiles
- The dense professional network of our Cameroonian collaborators as well as certain professional social media platforms, made it possible to identify and contact experts from various backgrounds (academics, industrialists, practitioners in the field), accelerating the mobilization of participants within a reasonable time-frame;
- Cameroon benefits from a dynamic technological ecosystem, including numerous academic institutions, recognized research centers and a network of qualified professionals, often from various African countries and beyond;
- These characteristics make it a credible testing ground for evaluating the viability of architectures designed for constrained environments, while offering a variety of perspectives and usage contexts.
- At least five years of professional experience in a relevant field (software engineering, distributed systems, embedded computing, critical architecture, etc.);
- Affiliation with a Cameroonian institution at the time of the study (university, technology company, public administration, specialized NGO);
- Expertise in technological and organizational issues related to low-infrastructure information systems, particularly in African urban environments.
- Professional and disciplinary diversity, guaranteeing a plurality of analyses;
- Considerable cumulative experience, ensuring a critical assessment based on practice;
- Direct proximity to the contexts targeted by the architecture, ensuring that the feedback is rooted in the reality of potential uses.
4. Results and Discussion
4.1. Validation of the Architecture and Its Theoretical Analysis
- Feedback on the understanding and structural consistency of the architecture;
- Technical validation elements (relevance of choices, consistency of modules, contextual feasibility);
- Assessment of the validity of the theoretical analysis presented in Table 1 of Section 2.2.1 (strengths, weaknesses, challenges).
4.1.1. Clarity and Understanding of the Architecture
- 12 respondents suggested including graphic illustrations to enhance understanding of the interactions;
- 6 mentioned a need for concrete examples or usage scenarios to contextualize the orchestration mechanisms.
4.1.2. Technical Validation of the Architecture
- n is the number of experts that responded to the item,
- is the given mark to the item by the i-th expert.
- n the number of experts that responded to the item,
- is the mean of the item,
- is the response of the i-th expert,
- A low standard deviation (< 0.5) indicates that the responses are very consistent around the mean,
- A higher standard deviation (> 0.8) indicates greater variability in opinions.
- The potential complexity of deploying edge servers, particularly in terms of maintenance and energy resilience;
- The need to calibrate the technological choice to local constraints, for example by suggesting hybrid configurations combining edge/fog and lightweight cloud.
4.1.3. Validation of Theoretical Analysis (Strengths, Weaknesses, Challenges)
- 74 respondents (94.9%) consider that the strengths identified in the analysis (reduced response time, modularity, adaptability to limited infrastructure) are realistic and well formulated;
- Several respondents emphasized that the system’s ability to operate autonomously at the local level, thanks to edge computing, was a major technological advantage;
- 65 respondents (83.3%) consider the weaknesses identified to be accurate and well defined;
-
However, some suggested adding:
- –
- Dependence on accurate and up-to-date mapping data;
- –
- The hidden costs of inter-system synchronization;
- –
- The management of decision-making conflicts in the event of partial failures.
- The majority (89.7%) considered that human, logistical and political challenges had been adequately addressed, particularly those related to training, maintenance and inter-institutional integration;
- A few suggestions were made to further explore the regulatory dimension, particularly with regard to data protection, the regulation of emergency communications, and the legality of autonomous sensor deployments in public spaces.
- Technically sound and functionally understandable;
- Compatible with environments with limited infrastructure, subject to certain adaptations;
- Adequately analysed in terms of strengths, weaknesses and challenges.
4.2. Project Feasibility and Viability Assessment
4.2.1. General Perception of Feasibility
- 19 respondents (24.4%) believe that the system is entirely feasible with current resources;
- 45 respondents (57.7%) consider it to be partially feasible, but only with gradual adjustments;
- 14 respondents (17.9%) consider its implementation to be difficult or even unlikely in the short term due to structural constraints.
4.2.2. Identified Barriers to Implementation
4.2.3. Identified Facilitating Factors
- The existence of dynamic academic pools training high-level engineers;
- The growing capacity of certain local companies to integrate IoT and cloud technologies;
- Growing openness of public authorities to intervention technologies (video surveillance systems, SMS alerts, GIS systems, etc.);
- Growing inter-institutional collaboration between universities, start-ups and local authorities.
4.2.4. Economic Sustainability and Long-Term Viability
- 29 respondents (37.2%) consider the system to be economically viable provided it is rolled out in a modular and gradual manner;
- 21 respondents (26.9%) consider it to be viable if supported by public or international funding;
- 28 respondents (35.9%) express doubts about economic viability without a clear business model or recurring subsidies.
4.2.5. Mentioned Conditions for Success
- Rapid prototyping of a use case in a medium-sized city (e.g. Douala, Maroua, N’Djamena);
- Deployment using public funds or through public-private partnerships;
- Integration into a multidisciplinary action research project to bring together expertise (urban planning, IT, law, health);
- Capitalization on existing resources (GIS mapping, 4G/5G networks, geolocation systems);
- Institutional support with a communication and training strategy for decision-makers.
4.3. Task Prioritization for Operationalization
- The average priority rating assigned by the experts;
- The percentage of respondents assigning it a high priority (1 or 2) - the High priority rate.
- 1.
- Rapid implementation of a minimum technological foundation, with an emphasis on SAS, ESN and FPGA-based modules;
- 2.
- Availability of reliable mapping data, an essential requirement for route calculation and navigation;
- 3.
- Formalization of orchestration and communication protocols between subsystems (functional interoperability);
- 4.
- Structuring of the project team, with cross-functional skills (sensors, edge, algorithms, user interface);
- 5.
- Real-world testing through a limited but representative pilot program.
- 1.
- Short term: formation of the project team, data structuring, development of the SAS, edge deployment, prototyping of the ESN modules;
- 2.
- Medium term: field testing, development of the IOPS, ITGS integration, securing exchanges, initial institutional partnerships;
- 3.
- Long term: regulation, shared governance, continuing education, maintenance, industrialization of the system.
4.4. Strategic Recommendations from the Experts
5. Critical Analysis and Perspectives
5.1. Critical Analysis of the Methodology
5.2. Critical Analysis of the Obtained Results
5.3. Perspectives
6. Conclusion
Author Contributions
Informed Consent Statement
Data Availability Statement
Conflicts of Interest
References
- Costa, D.G.; Peixoto, J.P.J.; Jesus, T.C.; Portugal, P.; Vasques, F.; Rangel, E.; Peixoto, M. A Survey of Emergencies Management Systems in Smart Cities. IEEE Access 2022, 10, 61843–61872. [CrossRef]
- Elvas, L.B.; Mataloto, B.M.; Martins, A.L.; Ferreira, J.C. Disaster Management in Smart Cities. Smart Cities 2021, 4, 819–839. [CrossRef]
- Al-Smadi, A.M.; Alsmadi, M.K.; Baareh, A.K.; Almarashdeh, I.; Abouelmagd, H.; Ahmed, O.S.S. Emergent situations for smart cities: A survey. International Journal of Electrical and Computer Engineering (IJECE) 2019, 9, 4777–4787. [CrossRef]
- Hayat, P. Smart Cities: A Global Perspective. India Quarterly 2016, 72, 177–191. [CrossRef]
- Jagho Mdemaya, G.B.; Foko Sindjoung, M.L.; Zekeng Ndadji, M.M.; Velempini, M. HERCULE: High-Efficiency Resource Coordination Using Kubernetes and Machine Learning in Edge Computing for Improved QoS and QoE. IEEE Access 2025, 13, 72153–72168. [CrossRef]
- Boutros, A.; Betz, V. FPGA Architecture: Principles and Progression. IEEE Circuits and Systems Magazine 2021, 21, 4–29. [CrossRef]
- Siracusa, M.; Del Sozzo, E.; Rabozzi, M.; Di Tucci, L.; Williams, S.; Sciuto, D.; Santambrogio, M.D. A Comprehensive Methodology to Optimize FPGA Designs via the Roofline Model. IEEE Transactions on Computers 2022, 71, 1903–1915. [CrossRef]
- Eneh, A.; Arinze, U.C. Comparative analysis and implementation of Dijkstra’s shortest path algorithm for emergency response and logistic planning. Nigerian Journal of Technology (NIJOTECH) 2017, 36, 876–888. [CrossRef]
- Zhou, Y.; Jin, X.; Wang, T. FPGA Implementation of A* Algorithm for Real-Time Path Planning. International Journal of Reconfigurable Computing 2020, 2020, 8896386. [CrossRef]
- Aziz Assoul, M.A.; Tahir, A.M.; Mahmoud, T.; Jagho Mdemaya, G.B.; Zekeng Ndadji, M.M. A Comprehensive System Architecture using Field Programmable Gate Arrays Technology, Dijkstra’s Algorithm, and Edge Computing for Emergency Response in Smart Cities. ParadigmPlus 2024, 5, 1–21. [CrossRef]
- Ji, Y.; Wang, W.; Chen, W.; Zhang, L.; Yang, M.; Wang, X. Dijkstra Algorithm Based Building Evacuation Edge Computing and IoT System Design and Implementation. In Proceedings of the 2021 IEEE International Conference on Progress in Informatics and Computing (PIC), 2021, pp. 281–287. [CrossRef]
- Omomule, T.G.; Durodola, B.L.; Orimoloye, S.M. Shortest route analysis for road accident emergency using dijkstra algorithm and fuzzy logic. International Journal of Computer Science and Mobile Computing 2019, 8, 64–73.
- Chen, Y.Z.; Shen, S.F.; Chen, T.; Yang, R. Path Optimization Study for Vehicles Evacuation based on Dijkstra Algorithm. Procedia Engineering 2014, 71, 159–165. [CrossRef]
- Lei, G.; Dou, Y.; Li, R.; Xia, F. An FPGA Implementation for Solving the Large Single-Source-Shortest-Path Problem. IEEE Transactions on Circuits and Systems II: Express Briefs 2016, 63, 473–477. [CrossRef]
- Fernandez, I.; Castillo, J.; Pedraza, C.; Sanchez, C.; Martinez, J.I. Parallel Implementation of the Shortest Path Algorithm on FPGA. In Proceedings of the 2008 4th Southern Conference on Programmable Logic, 2008, pp. 245–248. [CrossRef]
- Esteves, L.T.C.; Oliveira, W.L.A.d.; Farias, P.C.M.d.A. Analysis and Construction of Hardware Accelerators for Calculating the Shortest Path in Real-Time Robot Route Planning. Electronics 2024, 13. [CrossRef]
- Satyanarayanan, M. The Emergence of Edge Computing. Computer 2017, 50, 30–39. [CrossRef]
- Abbas, N.; Zhang, Y.; Taherkordi, A.; Skeie, T. Mobile Edge Computing: A Survey. IEEE Internet of Things Journal 2018, 5, 450–465. [CrossRef]
- McEnroe, P.; Wang, S.; Liyanage, M. A Survey on the Convergence of Edge Computing and AI for UAVs: Opportunities and Challenges. IEEE Internet of Things Journal 2022, 9, 15435–15459. [CrossRef]
- Rosayyan, P.; Paul, J.; Subramaniam, S.; Ganesan, S.I. An optimal control strategy for emergency vehicle priority system in smart cities using edge computing and IOT sensors. Measurement: Sensors 2023, 26, 100697. [CrossRef]
- Xu, H.; Wang, L.; Han, W.; Yang, Y.; Li, J.; Lu, Y.; Li, J. A Survey on UAV Applications in Smart City Management: Challenges, Advances, and Opportunities. IEEE Journal of Selected Topics in Applied Earth Observations and Remote Sensing 2023, 16, 8982–9010. [CrossRef]
- Seong, K.; Jiao, J. Is a Smart City Framework the Key to Disaster Resilience? A Systematic Review. Journal of Planning Literature 2024, 39, 62–78. [CrossRef]
- Zeng, L.; Ye, S.; Chen, X.; Zhang, X.; Ren, J.; Tang, J.; Yang, Y.; Shen, X.S. Edge Graph Intelligence: Reciprocally Empowering Edge Networks With Graph Intelligence. IEEE Communications Surveys & Tutorials 2025, pp. 1–1. [CrossRef]
- Jagho Mdemaya, G.B.; Zekeng Ndadji, M.M.; Foko Sindjoung, M.L.; Velempini, M. Efficient Load-Balancing and Container Deployment for Enhancing Latency in an Edge Computing-Based IoT Network Using Kubernetes for Orchestration. International Journal of Advanced Computer Science and Applications 2024, 15. [CrossRef]
- Zekeng Ndadji, M.M.; Tchoupé Tchendji, M. A Software Architecture for Centralized Management of Structured Documents in a Cooperative Editing Workflow. In Proceedings of the Innovation and Interdisciplinary Solutions for Underserved Areas. Springer, 2018, pp. 279–291. [CrossRef]
- Rodak, A.; Jamson, S.; Kruszewski, M.; Pędzierska, M. User requirements for autonomous vehicles–A comparative analysis of expert and non-expert-based approach. In Proceedings of the 2020 AEIT International Conference of Electrical and Electronic Technologies for Automotive (AEIT AUTOMOTIVE). IEEE, 2020, pp. 1–6.
- Tora, T.T.; Andarge, L.T.; Abebe, A.T.; Utallo, A.U.; Meshesha, D.T.; Wubie, A.F. An expert-based assessment of early warning systems effectiveness in South Ethiopia Regional State. Discover Sustainability 2025, 6, 188. [CrossRef]
| Subsystem | Criterion | Significant contributions | Identified limitations | Technical and contextual challenges |
|---|---|---|---|---|
| SAS | Time efficiency | Rapid detection, local processing via FPGA, reduced network traffic | Does not manage allocation or redundancy of multiple detections | Ensure sensor robustness, avoid false positives/negatives |
| Resource allocation | Triggers the chain without resource prioritization | No allocation intelligence | Coordination with downstream modules for dynamic allocation | |
| Ease of use | Autonomy, offline mode, fault tolerance, low bandwidth requirements | Maintenance of IoT devices, limited on-board energy | Energy management, physical and software resilience | |
| ESN | Time efficiency | Parallel computing (FPGA), route caching, real-time response | Possible network latency in exchanges between edge servers | Efficient synchronization and load balancing between servers |
| Resource allocation | Optimal path calculation, service prioritization | Does not make final intervention decisions | Seamless integration of results into human management systems | |
| Ease of use | Distributed deployment, low dependence on central infrastructure | High initial cost, need for reliable FPGA cards | Maintenance in limited technical environments | |
| IOPS | Time efficiency | Centralized coordination, rapid relay to teams | Dependence on server-field communication | Rapid integration with internal service procedures |
| Resource allocation | Prioritized assignment, adjustment based on feedback | Relies on predefined criteria that are sometimes rigid | Dynamic definition of priorities in unprecedented situations | |
| Ease of use | Interface with conventional notification systems (SMS, sirens) | Depends on a stable network, infrastructure not always available | Adapt to heterogeneous services with varying levels of technology | |
| ITGS | Time efficiency | Autonomous recalculation, guidance in case of obstacles, real-time interface | Depends on the initial quality of maps and routes | Ensuring autonomy in areas with poor coverage |
| Resource allocation | Does not make decisions but ensures optimal execution | No direct resource management | Maintaining synchronization with other components | |
| Ease of use | Intuitive visualization, simple interface, embedded calculation | Limited local processing capacity depending on complexity | Resilience in stressful situations, reliability of embedded hardware |
| Section | Title | Number of questions | Type of questions |
|---|---|---|---|
| 1 | Socio-demographic information | 5 | Closed + Opened |
| 2 | Understanding the architecture | 4 | Closed + Opened |
| 3 | Relevance of the proposed architecture | 6 | Likert scale (1 to 5) |
| 4 | Validity of theoretical analyses | 5 | Likert scale + Justifications |
| 5 | Project feasibility and viability | 6 | Closed + Opened |
| 6 | Recommendations and task prioritization | 5 | Opened |
| Assessed dimension | Targeted objectives | Targeted components |
|---|---|---|
| Understanding the architecture | Verify the clarity and intelligibility of the description. | Summary description of the architecture, SAS–ESN–IOPS–ITGS interactions |
| Technical relevance | Validate the soundness and appropriateness of the technological choices. | FPGA, distributed computing, edge computing, modularity |
| Operational efficiency | Assess the anticipated effects on response times and coordination quality. | Subsystem functionality, overall orchestration |
| Ease of implementation | Identify practical obstacles and feasibility in the African context. | Infrastructure conditions, local human and technical resources |
| Project viability | Estimate the project’s capacity for long-term sustainability (cost, maintenance, evolution). | Overall architecture, energy requirements, interoperability |
| Prioritization of actions | Identify the key stages and their logical order for effective deployment. | Gradual integration, critical requirements, blocking factors |
| Strategic recommendations | Obtain contextualized suggestions for the actors involved. | Academics, engineers, institutions, public decision-makers |
| Distribution of experts by gender | ||
|---|---|---|
| Gender | Total number | Percentage |
| Male | 54 | 69.2% |
| Female | 24 | 30.8% |
| Distribution of experts by age group | ||
| Age group | Total number | Percentage |
| Under 30 years old | 08 | 10.3% |
| 30–39 years old | 33 | 42.3% |
| 40–49 years old | 25 | 32.1% |
| 50 years old or older | 12 | 15.4% |
| Distribution of experts by field of activity | ||
| Main field of activity | Total number | Percentage |
| University/Research | 42 | 53.8% |
| Technology company | 28 | 35.9% |
| Public administration / NGO | 08 | 10.3% |
| Distribution of experts by area of expertise | ||
| Area of expertise | Total number | Percentage |
| Software Engineering | 60 | 76.9% |
| Distributed systems / Edge computing | 41 | 52.6% |
| Embedded computing / FPGA | 16 | 20.5% |
| AI applied to systems | 18 | 23.1% |
| Critical software architecture | 28 | 35.9% |
| Assessed item | Mean / 5 | Standard deviation |
|---|---|---|
| Overall consistency of the technical architecture | 4.51 | 0.52 |
| Relevance of using FPGAs and edge computing | 4.33 | 0.71 |
| Feasibility in low-infrastructure environments | 4.12 | 0.80 |
| Functional distribution among subsystems | 4.46 | 0.59 |
| System responsiveness in handling emergencies | 4.28 | 0.66 |
| Transferability of the system to other African countries | 4.05 | 0.77 |
| Identified barrier | Citations | Percentage |
|---|---|---|
| Hardware costs (FPGA, edge servers, IoT) | 63 | 80.8% |
| Lack of localized specialized skills | 59 | 75.6% |
| Lack of adequate public policies | 47 | 60.3% |
| Lack of structured and reliable urban data | 42 | 53.8% |
| Interoperability issues with existing systems | 33 | 42.3% |
| Low awareness of strategic digital technology among institutions | 28 | 35.9% |
| Rank - Task | Average priority (1–5) | High priority rate (1–2) |
|---|---|---|
| 1 - Development of a SAS prototype (sensors, alerts) | 1.47 | 67/78=85.9% |
| 2 - Collection and structuring of cartographic and urban data | 1.62 | 64/78=82.1% |
| 3 - Initial deployment of edge servers in a pilot area | 1.68 | 63/78=80.8% |
| 4 - Implementation of the ESN (the FPGA module on edge servers) | 1.77 | 61/78=78.2% |
| 5 - Development of an inter-module communication protocol (SAS - ESN - IOPS) | 1.83 | 59/78=75.6% |
| 6 - Formation of a multidisciplinary team of engineers | 1.91 | 58/78=74.4% |
| 7 - Launch of a field test pilot program | 1.95 | 57/78=73.1% |
| 8 - Development of IOPS for tactical coordination | 2.03 | 54/78=69.2% |
| 9 - Development and integration of ITGS into emergency vehicles | 2.12 | 52/78=66.7% |
| 10 - Development of a cybersecurity and data confidentiality policy | 2.18 | 51/78=65.4% |
| 11 - Raising awareness among local authorities | 2.26 | 49/78=62.8% |
| 12 - Creation of a regulatory framework for technological experimentation | 2.32 | 47/78=60.3% |
| 13 - Development of training programs for field teams | 2.44 | 46/78=59.0% |
| 14 - Establishment of an FPGA/Edge maintenance unit | 2.51 | 43/78=55.1% |
| 15 - Establishment of sustainable public-private partnerships | 2.62 | 42/78=53.8% |
| Intended audience | Recommendations |
|---|---|
| Engineers and developers | Adopt an iterative prototyping approach: development must begin with simple prototypes that can be tested in partial environments to assess the robustness |
| Promote the use of open and affordable technologies: low-cost solutions based on replicable FPGA cards and standard sensors are preferable | |
| Prioritize software and hardware resilience: the system must be designed to withstand service interruptions and include local recovery and failover mechanisms | |
| Provide for upward interoperability: communication interfaces must be standardized to enable future integration with other alert or geolocation systems | |
| Researchers and academics | Continue formalization and modeling: it would be useful to formalize the architecture in the form of software architecture models (UML, AADL, BPMN) to support verification processes |
| Strengthen cross-disciplinary collaboration: the project would benefit from involving researchers in urban planning, logistics, geomatics, civil security, etc. | |
| Create field simulation laboratories: universities could serve as testing grounds for simulating emergency responses in a controlled environment | |
| Ensure the sustainability of research through technology transfer: the results should lead to pilot implementations, accompanied by freely reusable documentation | |
| Institutional decision-makers | Develop a specific regulatory framework: a law or directive is needed to facilitate the testing of smart systems in cities, including data collection |
| Create a local technology innovation fund: economic viability will depend on initial public support through targeted calls for projects | |
| Integrate smart emergency response systems into smart city policies: the proposed architecture could become a foundation for national smart city programs | |
| Strengthen professional training and institutional awareness: there is an urgent need to train municipal officials in the management of (distributed) digital systems | |
| Cross-cutting recommendations | Create multi-stakeholder coalitions (city–university–businesses) to jointly test the system |
| Publicly document the results of each implementation phase in order to create a pool of feedback | |
| Continuously assess the social and ethical impacts of the system (confidentiality, algorithmic justice, technological exclusion) |
Disclaimer/Publisher’s Note: The statements, opinions and data contained in all publications are solely those of the individual author(s) and contributor(s) and not of MDPI and/or the editor(s). MDPI and/or the editor(s) disclaim responsibility for any injury to people or property resulting from any ideas, methods, instructions or products referred to in the content. |
© 2025 by the authors. Licensee MDPI, Basel, Switzerland. This article is an open access article distributed under the terms and conditions of the Creative Commons Attribution (CC BY) license (http://creativecommons.org/licenses/by/4.0/).