Disaster Agents

Every year, Southeast countries suffer floods causing many deaths. We built Disaster Agents using Solace Agent Mesh to help rescue teams improve workflows and handle complex analysis.

Comment

Inspiration

We got our inspiration from our country's (Vietnam) last year natural disaster.

What it does

It takes information from the user (person who needs to be rescued) phone number, location, description of the current situation, and the number of people affected. After that, the information is sent to the Solace Agent Mesh, which the Orchestrator Agent will validate this information and split out the tasks among other agents (Severity Agent to calculate severity score, and Deployment Agent to calculate personnel needed).

How we built it

For the front end, we use Javascript, CSS, and the React library. For the backend, we use Solace Agent Mesh, and to configure the agent, we need 2 files. The configuration file of the agent (.YAML) file, and the tools (.py) file. For deployment, we deployed it to AWS cloud EC2 with CI/CD practice

Challenges we ran into

We had issues with communication between the Orchestrator Agent with other Agents. Also, the agents are sometimes inconsistent. Besides, we also had time management conflict, merging code conflict, and developing environment.

Accomplishments that we're proud of

We are proud of having a meaningful project. Additionally, we got all our planned features implemented.

What we learned

We learned about Solace Mesh Agent framework, how to pitch, how to make new friends, how to communicate within the team.

What's next for Disaster Agents

We hope we could get Disaster Agent to run offline, having more agent, and having it runs on a mobile phone.

Built With

Share this project:

Updates