Changes between Version 4 and Version 5 of BluePrintCERT


Ignore:
Timestamp:
12/05/10 19:13:52 (11 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrintCERT

    v4 v5  
    1212 * http://bazaar.launchpad.net/~rhok-vol/sahana-eden/trunk
    1313
     14== Use Cases ==
     15
    1416Deployment workflow:
    1517 * https://docs1.google.com/drawings/edit?id=1aDe6FNX1MPsq3wke-_GoT9GwZYcRBPj7HKJNRaGsRGs&hl=en&authkey=COTHiIAP
    1618
    17 Workplan:
     19
     20 1. Each volunteer who completes the CERT basic training program will be entered into the database.
     21
     22 2. Web-accessible user interface allows volunteers to update selected information on their account.
     23
     24 3. Primary & secondary admins from any CERT group can create an "Event", which can be a disaster, drill, exercise, training, etc.
     25 * [Event = Project in current Eden terminology. Ideally want a simple deployment setting to convert between the 2 terms]
     26
     27 4. After creating an event, the admin may search for volunteers to respond to that event by specifying specific skills, location and interests.
     28 * ''the majority of deployments are 3-8 hours, but I can imagine one lasting longer.  However, we could create separate events for each day''
     29 * ''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.''
     30 * [We can use Sahana Eden ‘Tasks’ to manage deployments]
     31
     32 5. A request for volunteers is sent by email, SMS and Google Talk to the search result set.
     33
     34 6. Volunteers can respond by email, SMS or Google Talk to be deployed, and will then receive a second communication with deployment details
     35
     36 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.
     37
     38 8. A list will be generated with the names and skillsets of the volunteers to be deployed and sent to the event incident commander.
     39
     40 9. When a volunteer arrives at the event scene, he / she can text or email a confirmation of arrival to the system.
     41
     42 10. When a volunteer leaves the event scene, confirmation of exit.
     43
     44 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.
     45
     46== Workplan ==
    1847 * https://docs.google.com/document/d/1ekhiNz7cmryynt1FeeXi6IXNx9b-3ANfZxX-F9hyqmk/edit?hl=en_GB#
    1948