| | 74 | |
| | 75 | I would phrase the features in these kind of terms (note we have *all* |
| | 76 | of these features already - they 'just' need bringing together into a |
| | 77 | coherent template which has been tested and documented) |
| | 78 | |
| | 79 | * Staff/Volunteer Management |
| | 80 | - Credentials can be tracked (Skills, Training & Experience) to remind |
| | 81 | people when they need to attend refresher trainings and see where |
| | 82 | there are gaps in cover that need addressing |
| | 83 | |
| | 84 | * Asset Management |
| | 85 | - Assets can be tracked through purchase, deployment, loans and repairs. |
| | 86 | |
| | 87 | * Fleet Management |
| | 88 | - Vehicles can have their fuel usage monitored and use GPS Tracking to |
| | 89 | report their current positions |
| | 90 | |
| | 91 | * Incident Reporting |
| | 92 | - Incidents can be logged by call centre staff or can be reported from |
| | 93 | the field by both trusted agents & the general public (including |
| | 94 | through Twitter/SMS/Email) |
| | 95 | |
| | 96 | * Dispatch |
| | 97 | - Teams of people & their equipment (vehicles/radios/etc) can be |
| | 98 | assigned to an incident according to their Skills & Availability |
| | 99 | (Rostering) |
| | 100 | |
| | 101 | * Incident Management |
| | 102 | - SOP checklists can be worked through based on scenario templates |
| | 103 | - The Incident Manager can file status updates & request additional |
| | 104 | resources to be dispatched |
| | 105 | |
| | 106 | * Share Information amongst heterogeneous systems |
| | 107 | - FYI &/or Action requests can be shared with all authorised |
| | 108 | stakeholders, whether or not they use Sahana (as long as they support |
| | 109 | open standards such as EDXL or we develop a custom adapter) |
| | 110 | |
