Early Warning - Tech Demo
Demonstration of a full stack implementation using a Early Warning use case
Last updated
Was this helpful?
Demonstration of a full stack implementation using a Early Warning use case
Last updated
Was this helpful?
The demo of a early warning system focuses on efficient communication between civil servants and communities in a given region. The system enables civil servants to validate raw threat information and create broadcasts to inform communities about potential hazards, while collecting structured feedback from recipients.
With this use case implementation, we demonstrate the GovStack approach through...
Modular and scalable architecture
A-synchronous data exchange between micro services / Building Block enables future scaling to additional messaging channels, sectors and recipients. See architecture diagram below.
Integration of Building Blocks Software
For this demo, we chose the following software applications (does not imply a recommendation):
BB Messaging: RapidPro (for bi-directional communication)
BB Information Mediator (Pub/Sub): Kafka
BB Registry: PostgreSQL
Backend Visualization
As core features of the demo are hidden in the backend, we implemented a side bar visualizing the handling of broadcasts by micro services and Building Blocks.
Data Privacy Note: By clicking on one of the access points you enter web applications operated by the Deutsche Gesellschaft für Internationale Zusammenarbeit (GIZ) GmbH where these Data Protection Notice and Registration Information are valid.
Email: firstUser@test.com
Password: asdf1234
Check marking "I accept the Terms and Conditions" is technically necessary but has no legal implication.
Threat: Raw information regarding a warning or potential hazard. This is what admins (civil servants) see and use to create broadcasts.
Broadcast: Information that is shared with a group of end-users. These are created based on threats and distributed to affected people.
Feedbacks: Messages received in response to broadcasts or about ongoing situations.
The following diagram shows one use case instance with used applications and Building Blocks.
The following diagram shows the BPM of the core process: Using threat information to issue a broadcast.
You can find the open source code and helm charts for deployment in the following repositories:
The following information are valid for all web applications linked in the access points chapter.
GIZ processes personal data exclusively in accordance with the and the . Personal data are, for example, name, address, email addresses and user behaviour.
When visiting a , GIZ itself processes only the data that is automatically transmitted by the browser and technically required in order to display the website correctly and to ensure its stability and security. Each time a web application is accessed, the data stored includes, but is not limited to the following:
Users also have the right in accordance with Article 77 GDPR to lodge a complaint with the competent data protection supervisory authority. The competent authority is the Federal Commissioner for Data Protection and Freedom of Information ().
