Fill in the form below and we will contact you shortly to organised your personalised demonstration of the Noggin platform.
An integrated resilience workspace that seamlessly integrates 10 core solutions into one, easy-to-use software platform.
The world's leading integrated resilience workspace for risk and business continuity management, operational resilience, incident & crisis management, and security & safety operations.
Explore Noggin's integrated resilience software, purpose-built for any industry.
Emergency Management Software
Published February 7, 2024
No doubt you’ve heard this before, but it bears repeating. In the midst of an emergency, getting the right resources, to the right place, at the right time can prove the difference between life or death. Those are the stakes of resource management in a nutshell.
So what’s resource management actually? It’s the organizational function dedicated to coordinating and overseeing tools, processes, and systems that help provide incident managers with appropriate resources in an appropriate timeframe during a crisis. Yet resource management has wider applicability outside of a purely emergency management context. Just think about it, all public safety and emergency teams can benefit from better allocating their resources whether for business-as-usual work, special projects, or incidents.
That being said, some of the best resource-handling frameworks have emerged out of emergency management. The frameworks set out to help organizations improve operational flexibility and enhance capacity. The ultimate goal being to help teams problem solve quickly (but not carelessly,) a necessity in emergency response. The frameworks do so by offering a series of best practices that emergency management and public safety teams, whether working individually or in concert with mutual aid partners, can deploy to effectively respond to incidents.
In the U.S., for instance, the National Incident Management System (NIMS,) developed by the Department of Homeland Security in the early 2000s, lays out a standardized approach to incident management. The approach is based on a few core concepts: A consistent method for identifying, acquiring, allocating, and tracking resources.
While certainly helpful, NIMS and other frameworks are just that, theoretical constructs. In order for teams to actually drive operational efficiency and accelerate the pace of effective command during emergencies, they will need to turn the theory into practice, not only before crisis strikes but also in the context of business-as-usual work and special projects. To do so, they will have to overcome some common operational challenges.
For one, business-as-usual work, even when central to the well-functioning of an organization, often remains far less transparent to decision makers than special project work. In consequence, business-as-usual work gets treated as unproductive and expendable, while special project work is perceived as lucrative and time sensitive. Case in point: we often see major projects cannibalizing available resources from business-as-usual work.
Unfortunately, this fundamental lack of understanding of most business-as-usual tasks is only one of the many challenges hindering the effectiveness of resource management. Another: the fact that geographically dispersed teams generally experience greater difficulty in coordinating resources. What’s more, teams often deploy the wrong resources to a project and end up wasting crucial time. The same goes when communication flows are inefficient and resource documentation is inadequate.
Often at fault is poor resource capacity planning, which leads to poor resource allocation. The best resources get overbooked and overburdened with trivial projects by managers who don’t understand core project demands. The overall failure of resource optimization in turn creates inefficiency and confusion.
So what can be done? Simply increasing the visibility of business-as-usual work is a start. But how? In most existing resource management solutions, business-as-usual work often gets notated as if it were just another project. Tasks and activities need to be clearly laid out, so as to justify resource allocation for each business-asusual activity.
The resource management challenges listed above only get exacerbated in an emergency management context, where incidents happen (and evolve) quickly. Without proper planning, teams will find themselves overwhelmed by the volume of unplanned resource requests; and resources themselves will be shuttled along without proper transition periods between deployments.
In the case of disasters, teams also have to avoid the negative consequences of resource convergence, when people, goods, and services are sent into an emergency zone all at once. Convergence can lead to resource congestion, which only hinders the delivery of aid.
Another wrinkle: in the case of large-scale emergencies, multiple agencies will usually respond in concert. Emergency response providers can include a mix of federal, state, and local public safety, law enforcement, emergency response, emergency medical (including hospital emergency facilities), and related personnel agencies, and authorities. That’s quite the mix.
Each one of those responding agencies brings with it its own set of competencies, experiences, and systems to bear in an emergency response scenario already marked by a high level of complexity. Here are some other multi-agency, emergency response resource management challenges:
Effective collaboration requires a clear understanding of roles, responsibilities, and, of course, resources. Or as James Carfano puts it: “Indeed, the sheer number of responders dictates the need for a more integrated structure to coordinate and prioritize the activities of multiple response entities.”
Teams need a strong, shared understanding of the situation at hand. But achieving that level of situational awareness can be nigh impossible without the right resource management tools, especially for teams who rely on verbal interactions and manual processes. Instead, teams should look for a robust, integrated resource management system to help increase operational effectiveness, achieve shared situational awareness, increase the speed of command, and enhance security. The ideal system should have the following features and functionality:
But when it comes to what’s actually available on the resource management technology market, procuring teams will run in to some significant limitations. On one end of the spectrum, you’ll find response organizations repurposing large-scale enterprise systems, like Enterprise Resource Planning (ERP,) computer-aided dispatch (CAD), and/or asset management solutions, for their more targeted resource management requirements.
As a result, resource management gets attached to a larger, enterprise-wide system, one originally procured and deployed to solve another business challenge. By design, that kind of system tends to be heavy, complex, and inflexible. Extending functionality for purely resource management purposes can be complicated. And what’s more, information modalities tend to be unilateral and rarely mobile friendly.
Additionally, enterprise-wide systems are usually cost prohibitive. Ongoing subscription costs easily run up in the millions and even tens of millions of dollars, including hidden costs for protracted set up and complex implementations.
On the other end of the spectrum though, you’ll just find almost entirely manual tools, like Excel spreadsheets. When it comes down to it, there are very few, cost-effective, multi-functional offerings in the middle.
A stand-alone, curated resource management solution, Noggin OCA is built specifically for incident and emergency management scenarios and therefore operates independently of other large enterprise systems. OCA also provides the following core resource management benefits:
A targeted resource management solution can help transform the resource management function at your organization from an imprecise art to an exact science. And a mobile-optimized, resource management system like Noggin OCA, rather than time-insensitive, face-to-face status meetings, can specifically enable your responders to report back on their tasks and activities, whether in a business-as-usual context or at the height of an emergency.
In either scenario, getting real-time resource information quickly and efficiently can bolster operational effectiveness, improve situational awareness, and lower costs. In the context of a disaster, it can also save lives.
i. Federal Emergency Management Agency. Available at https://emilms.fema.gov/IS700aNEW/NIMS0104summary.htm.
ii. Similarly, in Australia AIIMS (the Australasian Inter-service Incident Management System) provides a common management framework, applicable across a whole host of incidents from small to large, to assist with the effective and efficient control of incidents. The framework offers the basis for an expanded response as incidents grow in size and complexity.
iii. Danielle Richards, Mavenlink: The #1 Challenge in Resource Management. Available at http://blog.mavenlink.com/the-1-challenge-in-resourcemanagement-challenges according-to-the-experts.
iv. Danny Hall, Innate: Allocating resources across Business as Usual and projects. Available at https://www.innate-management.com/us/2016/04/14/ allocating-resources-across business-usual-projects/.
v. Teams might also include hazardous materials responders, urban search and rescue assets, community emergency response teams, anti-terrorism units, special weapons and tactics teams, bomb squads, emergency management officials, municipal agencies, in addition to diverse and sundry private organizations. James Carafano, Preparing Responders to Respond: The Challenges to Emergency Preparedness in the 21st Century: The Heritage Foundation. Available at https://www.heritage.org/homeland-security/report/preparing responders-respond-the-challenges-emergency-preparednessthe.
vi. Aslak Wegner Eide, Ida Maria Haugstveit, et al, SINTEF ICT: Key challenges in multi-agency collaboration during large-scale emergency management.Available at http://ceur ws.org/Vol-953/paper5.pdf.
vii. Ibid.