Changes between Version 4 and Version 5 of ITC 371 Project Management

12/04/13 18:42:59 (11 years ago)



  • ITC 371 Project Management

    v4 v5  
    44== Introduction ==
    5 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.
     5During a natural disaster, notification and assignment of key resources is a key component of an effective response.  As disaster data and needs are gathered, that information must be disseminated in a fashion that is effective, efficient, and contains protective measures that will prevent issues from being overlooked.  The data must be conveyed in a "many to many" format, similar to joins and grouping within a relational database.  The goal is to categorize, notify, allocate resources from a pool, and notify those resources whenever a new issue is presented.  We believe that this will help expedite a cohesive response to issues which arise in a natural disaster.
    66== Stakeholders ==
    77The 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.