| | 15 | The web interface will include fields such as the person reporting, subject, request type, priority, location, and contact information for the person reporting. Once the issue is filed, it will be placed in a queue for a team. An authoritative resource will be notified via one of the aforementioned methods with the expectation that the authority will assign the tasks to individual resources. The system will be able to add assignments for multiple teams if the response required transcend multiple teams. For example, if there was a fire and there were injuries, the incident might have tasks assigned to both EMTs and the fire department. The incident would have to then be individually resolved by each team before falling out of the active queue. |
| | 16 | |
| | 17 | |
| | 18 | Incident numbers will be assigned in chronological order using a counter in web2py. The incidents will have a status of active or inactive inside of the database. Active will be represented by a 1, and inactive will be represented by a 0. Incidents with an inactive status will not show up in the work queue for teams. |
| | 19 | |
| | 20 | |
| | 21 | Incidents that are not assigned once they arrive in the work queue pool will be given a predefined time threshold calculated based on a time stamp when the issue is initially filed. Once the time threshold has been exceeded, it is reintroduced and timestamped within the work queues. Other authoritative resources are then notified. This will occur until the issue is acknowledged and reassigned appropriately. |
| | 22 | |
| | 23 | The software must include functionality to pass the address or latitude coordinates to a cell phone or an auxiliary application to provide directions and a map to the incident. For example, the data could be accessed on a computer and passed into Google maps. |
| | 24 | |
