Coordinator - bounswe/bounswe2023group1 GitHub Wiki
|
Ayşe is a 42-year-old employee in Ahbap, a non-governmental organization that focuses on disaster relief efforts. Prior to the disaster, Ayşe was already a registered user of the disaster platform. As a disaster coordination and assistance worker, she applied to become a coordinator in the system through Ahbap, and her application was approved by the administrators. Thus, she became responsible for coordination processes and creating action in the system during a crisis. After a devastating earthquake hit Kahramanmaraş region, many people, both those in need of resources and those providing supply, logged in to the system. As a coordinator, Ayşe is responsible for matching the available supplies with the demands and creating action plans to manage logistics and coordinate the disaster response. To do this effectively, she needs highly efficient workflows to categorize information, visualize it, and coordinate different actions. |
|---|
-
Ayşe was registered to the system before the disaster occurred.
-
A governmental or non-governmental organization nominated Ayşe to become a coordinator.
-
Administrators confirmed Ayşe’s appointment as coordinator.
-
Ayşe was familiar with the system before the disaster.
-
Ayşe should also be familiar with the conditions on the ground also through other means.
-
Ayşe has reliable internet access.
- 1.1.2.2.1 Coordinators shall be assigned by admins.
- 1.1.2.2.2 Coordinators shall be unassigned by admins only.
- 1.1.2.2.3 Coordinators shall be able to suspend a user if this user is not a coordinator or admin.
- 1.1.2.2.4 Coordinators shall be able to request a responder to take a specific action. The coordinator must provide all the necessary information for the action.
- 1.1.2.2.5 Coordinators shall be able to create tasks consisting of to-do action lists that can be marked as completed by responders, allowing for easy progress tracking of the tasks
- 1.1.2.2.6 Coordinator shall be able to remove the assignee(s) from the task.
- 1.1.2.2.7 Coordinators shall be able to get notifications for new responders signed up to the system for specific needs.
- 1.1.2.2.8 Coordinators shall be able to view all user profiles, actions, and information provided by facilitators.
- 1.1.2.2.9 Coordinators shall be able to view, delete or reply to the requests.
- 1.1.2.2.10 Coordinators shall be able to share information and update information shared by themselves.
- 1.1.2.2.11 Coordinators shall be able to delete or update information shared by facilitators.
- 1.1.2.2.12 Coordinators shall be able to view, delete or reply to reported problems.
- 1.1.2.2.13 Coordinators shall be able to send requests to the admins.
-
Ayşe logs into the Disaster Response Platform and navigates to the dashboard where she can see the list of responders and their resources.
-
Ayşe approves a facilitator request from an aid center located in the disaster area, granting the user "Facilitator" authority. With this new role, the user can create requests on behalf of victims based on the latest information from the region, helping to coordinate a more effective response effort. Now, Ayşe can see the demands of this facilitator on the dashboard.
-
A facilitator makes an urgent request for 600 boxes of food to be delivered to an aid center in Elbistan. Ayşe receives the request and quickly locates available food resources by filtering the resources on the platform's map and dashboard.
-
Ayşe checks the dashboard and finds 600 available boxes of food located at a resource collection point in Ankara. She then creates an action using this resource. Then, she tries to locate an available actor with a suitable vehicle that can pick up the food and deliver them to the aid center. She cannot find a truck with a driver, but truck owners looking for a driver and drivers looking for a truck appear on the dashboard.
-
Ayşe matches a driver with an available truck and creates an action for the driver to go and get the truck. She fills the required fields of the action creation such as type of action, location, urgency, time frame, etc. This action appears as a path to Ayşe on the map (driver to truck), and she can track this action and monitor its progress until it is completed.
-
After the driver obtains the truck, she creates a path for the driver to take the tents in the collection center in Ankara and send them to the aid center in the disaster area in Elbistan, and gives this task to the truck driver. Instead of assigning these actions to the driver one by one, it creates a to-do list that assigns them all. After the all actions in the to-do list are checked by the driver, as the final stage of the task, the facilitator from the aid center must confirm that the necessary resources have reached the area and that the task has been completed.
-
After the facilitator receives the food and confirms the shipment is complete, the task is tagged as completed.
