| 29 | | === Radios === |
| | 24 | == Requirements == |
| | 25 | === Dispatch === |
| | 26 | One of the biggest problems right now, which could potentially be easy to solve is Dispatch. |
| | 27 | |
| | 28 | Currently the OPCOM provides the EMS crew with the limited available information & then they deploy. There is no way to update the crews except for voice radio. Since all EMS crew have smartphones then a simple app to update the crea with the precise incident location & any extra information on scale, etc would be extremely valuable. |
| | 29 | |
| | 30 | A possible solution would be to use OpenGeoSMS. ITRI Taiwan have developed an OpenGeoSMS Android client which supports the following features: |
| | 31 | * Incident Reporting (simple 'Current Location + Text Field') |
| | 32 | * Task Dispatch (simple view received 'Location + Text' on Map) |
| | 33 | * Team Communication (again, simple 'Location + Text'): |
| | 34 | * Where I am |
| | 35 | * Where are you? |
| | 36 | * Where shall we meet? |
| | 37 | |
| | 38 | === HRM === |
| | 39 | Import HRM data from https://rnbp.prociv.pt/rnbp/portal/ |
| | 40 | * (this system keeps crashing & was expensive) |
| | 41 | * Can export as ;-separated CSV using SQL commands |
| | 42 | * No need to have the output look the same as the current PDFs |
| | 43 | |
| | 44 | === Incident Tracking === |
| | 45 | There is a need to share data about an incident between a fire department and the district command center. |
| | 46 | Current process is that the OPCOM at the Firedep provides the information over thre radio, on the other side, another OPCOM is writing it all on paper, and type it again in a completely different software running on windows console....This takes a long time. |
| | 47 | |
| | 48 | Data Attributes: |
| | 49 | * date |
| | 50 | * time of alert |
| | 51 | * time of dispatch |
| | 52 | * location |
| | 53 | * type of emergency |
| | 54 | * vehicle |
| | 55 | * crew |
| | 56 | |
| | 57 | === Location Updates via Radio === |
| | 58 | Use GPS from Tetra radios to show Personnel & Vehicles on the Map |
| | 59 | |
| 49 | | == Requirements == |
| 50 | | === Dispatch === |
| 51 | | One of the biggest problems right now, which could potentially be easy to solve is Dispatch. |
| 52 | | |
| 53 | | Currently the OPCOM provides the EMS crew with the limited available information & then they deploy. There is no way to update the crews except for voice radio. Since all EMS crew have smartphones then a simple app to update the crea with the precise incident location & any extra information on scale, etc would be extremely valuable. |
| 54 | | |
| 55 | | A possible solution would be to use OpenGeoSMS. ITRI Taiwan have developed an OpenGeoSMS Android client which supports the following features: |
| 56 | | * Incident Reporting (simple 'Current Location + Text Field') |
| 57 | | * Task Dispatch (simple view received 'Location + Text' on Map) |
| 58 | | * Team Communication (again, simple 'Location + Text'): |
| 59 | | * Where I am |
| 60 | | * Where are you? |
| 61 | | * Where shall we meet? |
| 62 | | |
| 63 | | === Incident Tracking === |
| 64 | | There is a need to share data about an incident between a fire department and the district command center. |
| 65 | | Current process is that the OPCOM at the Firedep provides the information over thre radio, on the other side, another OPCOM is writing it all on paper, and type it again in a completely different software running on windows console....This takes a long time. |
| 66 | | |
| 67 | | Data Attributes: |
| 68 | | * date |
| 69 | | * time of alert |
| 70 | | * time of dispatch |
| 71 | | * location |
| 72 | | * type of emergency |
| 73 | | * vehicle |
| 74 | | * crew |
