CERT: Community Emergency Response Teams

Original Problem Definition:

• ​http://wiki.rhok.org/CERTS

Demo site:

• ​http://cert.sahanafoundation.org
• This site needs moving from Healthscapes to Zen

Current Code:

• ​http://bazaar.launchpad.net/~rhok-vol/sahana-eden/trunk

Use Cases

Deployment workflow:

• ​https://docs1.google.com/drawings/edit?id=1aDe6FNX1MPsq3wke-_GoT9GwZYcRBPj7HKJNRaGsRGs&hl=en&authkey=COTHiIAP

1. Each volunteer who completes the CERT basic training program will be entered into the database.

2. Web-accessible user interface allows volunteers to update selected information on their account.

3. Primary & secondary admins from any CERT group can create an "Event", which can be a disaster, drill, exercise, training, etc.

• [Event = Project in current Eden terminology. Ideally want a simple deployment setting to convert between the 2 terms]

4. After creating an event, the admin may search for volunteers to respond to that event by specifying specific skills, location and interests.

• the majority of deployments are 3-8 hours, but I can imagine one lasting longer. However, we could create separate events for each day
• They will be assigned tasks by the IC when they get to the deployment location. I don't think that would be part of this system.
• [We can use Sahana Eden 'Tasks' to manage deployments]

5. A request for volunteers is sent by email, SMS and Google Talk to the search result set.

6. Volunteers can respond by email, SMS or Google Talk to be deployed, and will then receive a second communication with deployment details

• Q: Why not send them the complete details initially, to help them decide if they want to volunteer?
• The second message is still important for confirmation though. - michael.howden
• [lauralanford] We want to avoid spontaneous participants - if deployment details are only sent to confirmed responders, there is less likelihood of unplanned volunteers showing up on site.

7. Once the requested number of volunteers has been met, a second communication will be sent to those who have not yet responded that the request has been filled.

8. A list will be generated with the names and skillsets of the volunteers to be deployed and sent to the event incident commander.

9. When a volunteer arrives at the event scene, he / she can text or email a confirmation of arrival to the system.

10. When a volunteer leaves the event scene, confirmation of exit.

11. If a volunteer has not confirmed exit by the closure of the event, a notice is generated and sent to the IC and the admin who created the event.

Workplan

• ​https://docs.google.com/document/d/1ekhiNz7cmryynt1FeeXi6IXNx9b-3ANfZxX-F9hyqmk/edit?hl=en_GB#

Proposed schema changes:

• ​https://spreadsheets0.google.com/ccc?key=tZcjtk6NVhWC2VkriozZBZA&authkey=CI2E35AH&hl=en&authkey=CI2E35AH#gid=0

Issues

These should be logged as tickets with the 'CERT' Version:

• When adding a new team, _next() should open up the team onto the members tab (see requests -> items for an example)
• Tasks should be appearing as Component Tabs of Project (not sure why this isn’t working, seems setup)
• Add Task should be a client-side unhide (listadd=True), again not sure why this isn’t working.
• When 'open' a person from the Team Members view it should open the Person record not the Membership record

---

BluePrintVolunteer

BluePrints