|Version 4 (modified by 8 years ago) ( diff ),|
BluePrint : Resource Tagging for Ticketing System
The solution relates to the issue of resource tagging and how emergency management resources are notified. This concept relates to the problem of resource tagging in a "many to many" environment through the use of relational databases. It is basically the way the data is created within the database, how it's manipulated, and how it is utilized to associate incidents to authority and available resources. It will provide a way of categorizing large amounts of data based on type, priority, and allocating it to an appropriate pool/team of resources. The way the data is handled is similar to the open source software osTicket or Front Range Solutions HEAT.
The users of the solution would be local government, emergency management officials, and first responders. It will help them streamline their work queuing and prevent issues from falling through the cracks through the use of a proactive alert system that re-queues unassigned work. This solution would impact the end users, because it automates re-queuing of unassigned issues. It makes it very difficult for things to fall through the cracks. Given that the stakeholders are typically the same individuals and organizations listed in the resource pool, it would assist them with an automated mechanism for queuing their work based on priority. It would also provide a method of handling the data in such a fashion that it could be easily ported into a mapping system similar to Google Earth. When an issue passes the threshold for reassignment, it would then dump the item back into the queue and alert other authoritative resources.
This project would require a web server (Apache), a PHP handler (phpMyAdmin), and a functional SQL database similar to those used in MySQL Community Server.
The primary issue created by handling data this way would that the data is initially put in by users. Although data checking can be done for correct format, it would be very difficult to verify that an address is correct. Also, the person reporting the issue may not be physically on site. This would also create problems with pulling GPS information from a cell phone. The constraint would be that location information would need to be accurate for the system to be effective with geo-tagging.
Sahana Eden Ticketing System.jpg
) - added by 8 years ago.
Resource Tagging System Blueprint
) - added by 8 years ago.
Work Flow Document
- questionaire.PNG (19.1 KB ) - added by 8 years ago.
- gantt.jpg (121.7 KB ) - added by 8 years ago.
- tasks.jpg (85.3 KB ) - added by 8 years ago.
Download all attachments as: .zip