Previstar RESOURCE Manager delivers resource visibility and tracking capabilities throughout all phases of an incident or event. The system’s automated workflow is based in NIMS/ICS processes and principles including FEMA’s resource management lifecycle.

“Resource management involves the coordination and oversight of personnel, tools, processes, and systems that provide incident managers with timely and appropriate resources during an incident.”

Resource management is dynamic and complex. Resource requirements will change as an incident evolves. Often times, incidents will cross jurisdictional and geographic boundaries and require the coordination of resources across local, state and federal agencies. The process becomes increasingly complex if multiple incidents are occurring simultaneously.

Unfortunately, many tools used today such as spreadsheets or basic databases are not build to manage these dynamic complexities.

According to the National Incident Management System, Resource management involves four primary tasks:

• Establishing systems for describing, inventorying, requesting, and tracking resources.
• Activating these systems prior to and during an incident.
• Dispatching resources prior to and during an incident.
• Deactivating or recalling resources during or after incidents

RESOURCE Manager meets these requirements. The system delivers automated capability, scalability, and flexibility to meet operational needs for single incidents or multiple incidents simultaneously.

RESOURCE Manager is based on emergency management standards and enables users to implement a uniform method of identifying, acquiring, allocating, and tracking resources.

RESOURCE Manager is easy to deploy. The step-by-step guidance makes it simple for users who are rarely on the system.

RESOURCE Manager is built on an industry standard architecture (Microsoft). This enables interoperability with existing systems and also provides a platform designed to easily incorporate future enhancements as emergency management standards continue to evolve.

Resource Planning

• Identify inventory – equipment, teams, materials, supplies, certified personnel, and facilities (at the local, regional, or statewide level)
• Manage inventory – quantity available, current location, POC, FEMA Type, calibration dates, certification expirations
• Identify resource shortfalls – automatically compare resource needs with available inventory

Resource Tracking

• Identify Resource Requirements
• Request/Order & Acquire
• Check-n & Assignment
• Mobilize/Deployment
• Demobilize
• Track Cost

Hierarchal Architecture

• Multi-level resource management – view inventory “roll ups” and manage resources at the organizational, jurisdictional, regional, statewide levels
• Manage multiple incident simultaneously

GIS Integration (optional)

• Strategic Situational Awareness/Common Operating Picture - view and manage resource inventory, deployments, facilities, skilled personnel, incident locations, and other critical information wareness/Common Operating Picture - view and manage resource inventory, deployments, facilities, skilled personnel, incident locations, and other critical information

Software Requirements

Minimum	Optimal
Windows Server 2003 w/ SP1	N/A

Database Requirements

Minimum	Optimal
4 GB of RAM	8 GB of RAM
20 GB of free hard drive space	80 GB of free hard drive space
1.2 GHz processor speed	2.8 to 3.4GHz processor speed – Dual Core Processor

Web Portal Requirements

Minimum	Optimal
4 GB of RAM	8 GB of RAM
20 GB of free hard drive space	20 GB of free hard drive space

Does RESOURCE Manager integrate with the CEMPlanner and INCIDENT Manager?


Yes. All modules can work independently or work seamlessly with one another. Organizations can implement RESOURCE Manager today and any other CPS module in the future based on their organizational needs.



Do I have to have all my data uploaded into the system before I can use it for an incident?


No. RESOURCE Manager works with existing datasets but also enables users to manage resources “on the fly”, as in most incident’s it is highly likely that not all resources will have been pre-populated into the system.