3 Tenets on the Integration of Information Technology with Emergency Management
In the past few years, i’ve been working on better defining how technology and emergency management (EM) can play well together. It is a project that feels mostly like trying to get fire to be wet or convincing the color orange to be purple.
Current technology is often bloated in terms of memory usage, filled with subroutines that monitor all of our activity or simply provide the makers with endless data about their users. Or, at best, it is simply robbing us of our attention span. For example, this article notes:
“In 2004, we measured the average attention on a screen to be 2½ minutes,” Mark said. “Some years later, we found attention spans to be about 75 seconds. Now we find people can only pay attention to one screen for an average of 47 seconds.”
And yet, we see endless calls for tech and EM to work together without much really being done to help consumers, potential victims of a hazard event, connect with EM through the tech those tech companies have created. This, more than tech integration for things like situation awareness or new products or platforms, is what tech integration could and should look like.
From the EM perspective as it waits for the tech industry to dot their i’s and cross the t’s of the things they’ve made, there is a whole other potential way to think about tech integration. It seems to me that what EM should be doing is helping humanity prepare for the various consequences of everything we’ve been doing in the tech sector. Because, if anything, tech will be (and has been) the source of additional, ride-a-long, or supplemental hazard events as we’ve become more tech dependent.
A lot of the inspiration for this particular approach came from (of all things) Godzilla vs Hedorah wherein a creature from another galaxy crash lands on earth in the midst of some of our heaviest years of pollution. Hedorah feeds off of this pollution and by the end of the movie, humanity recognizes what they have done and begin to work against themselves.
Godzilla vs Hedorah really provides hyperbole about what we’re doing to ourselves, our planet, and each other. This type of movie cannot be made today without it being ripped to shreds by folks who’s livelihood depends on not accepting the responsibility of their actions. For example, the creature begins to grow due to an oil tanker colliding with another oil tanker. This level of pollution results in a potentially more destructive force than Godzilla who was created by American Nuclear Bomb testing.
There is a frustrating amount of potential with regard to the uses of technology that tech firms tend to ignore (or buy their way out of — e.g. OnStar hosting call centers instead of writing software that notifies 9–1–1 of an accident upon detection, cell phone companies being more amenable to allowing PSAPs to access mobile phones directly, and other issues around POTS/VOIP).
This lack of engagement makes sense as it is not a profit serving space for those tech companies. It would require tech firms to navigate civic structures of varying levels (local, state, federal, national) or, at best, to enter in to an endless process of creating and maintaining infrastructure independent of profit-generating enterprise.
Concurrent to this lack of engagement with EM in general, there is a frustrating lack of engagement of tech that EM practitioners also do. Much like that of the tech firms, any EM practitioner engaging with tech must face a stark, militaristic collection of policies and procedures that were written before technology existed in its current ubiquity, and it shows no sign of being adjusted as the resources required would probably require every budget for every EOC in the country to be quadrupled and combined together…and it probably still wouldn’t be enough.
And everywhere in between we see firms and EM practitioners doing the thing that parents do with kids, “talk to your mom” and when you talk to your mom, “talk to your dad.” And this endless cycle continues ad nauseam.
So what to do?
I’ve written previously about the “Right Mindset” needed for tech in EM. Coating yourself in tech, teaching use instead of literacy, and creating tools without actual buy-in (having 1 or 2 stakeholders doesn’t count) from EM practice just doesn’t work. This needs to be said because this is the standard operating procedures for tech itself.
To that end, I think there are some ways to really begin to foster a mindset for tech adoption in EM that works. They need to encapsulate 3 distinct aspects of EM: analytics, what is best encapsulated by the word, “analytics, and, basic tech skills.” While each of these are marked by terms that carry their own baggage, they’re much more pointed.
The 3 tenets that form the foundation upon which technology use in EM could be built are best summarized as:
- EM Technology should primarily be used before a hazard event for planning and mitigation analytics (analytics).
- EM’s response technology needs to work during a response when all other technology doesn’t work or focus on extensible solutions for infrastructure damage (city planning).
- EM’s everyday focus on technology should be primarily around the concept of the risks they create (basic tech skills).
Each tenet requires an intense amount of work but even a shallow approach of these tenets would result in a sizable step toward a public discussion and requirement to assume responsibility for the risks companies manufacture.
Before — Analytics and EM
There are so, so many things to begin with here. From Supply chains, to models of equity, to models of risk, this is perhaps the easiest aspect of the tech industry to support because it is inexpensive, useful, and can really help given that the tech industry itself is responsible for the massive amount of (useless) data that exists.
I can remember interviewing for my current job with a statistics professor. He provided for me a discussion of Pareto Charts. I remember us talking about putting price tags on everything all over the city into a spreadsheet that would accept a feed from the PSAP. Each incident would impact a particular region and you’d prioritize based on cost, based on potential costs, and based on the cost to dispatch. This idea isn’t that great, really, because it revolves around money and so this means the rich parts of town will always, always get prioritized. Yet, we can consider risk, we can use the “risk indices” that have been developed over the years and actually correct them, validate them (because they aren’t right now).
What analytics can do is relatively simple. I’ll make it into a list:
- Help EM get past the “Whole Community Approach” which is just not working but gives EM practitioners a pass when they make plans using it. By focusing on actually crunching numbers, even a weighted distribution or quota system (as troublesome as they are) would be better than the current modes of approach.
- Supply Chain Maintenance is something that just often isn’t done. There was a story from Hurricane Maria about some guy’s computer getting broken which then resulted in the entire supply chain for Puerto Rico to be lost. While EM blamed much of this on the “corruption of local officials” there was significant blame to be spread all over the place. You may ask why or what this has to do with analytics and mostly this is the supplemental part of it. In order to do analytics, one needs to understand the entire pipeline of data gathering to data cleaning to the creation of new information and this means a whole lot of understanding of “basic computing” as well as “basic analytics.”
- The Future of Emergency Management is something that has been difficult to discern. While there are more frequent, and will be more frequent hazards in the future, there has been little done to embrace the future. Where analytics and computing can help here is to do something that is done in the EU and elsewhere, but not here in the US, to collect and examine After-Action Reports to understand the whole of EM’s efforts on all kinds of disaster at once. This is also an entry point for training Artificial Intelligence though AI’s use in EM is far, far off.
And this is just a brief discussion of where analytics can help EM. The wonderful part of this type of work is that it requires a user become a lot more intimately connected to their computers. From use of command lines to installation of packages to the scraping, gathering, and manipulation of large amounts of data, this skillset is a huge boon to EM and is something I am actively pursuing.
During — EM Tech Needs to Work When Nothing Else Does
This is a fancy way of saying that if the Smart Cities initiatives are to be taken seriously, we need to make sure that EM is involved with the re-design of cities. It isn’t enough to re-design the cities around technology. Re-designing cities around cars was absolutely horrendous and it may destroy the planet before we get around to trying something else.
What can EM do with designing cities, you may ask?
Well, already we see things like Fire Hydrants, Fire Extinguishers, Hoses, Ladders, Fire Doors, and things that matter in a disaster. However, these things are also just a tiny part of preparation for the kinds of things the earth creates. Buildings are almost always filled to the brim with poison in the form of plastic. They are filled with inadequate capabilities to deal with all manner of potential hazard events that we do not prepare well for. Things like building in an earthquake zone should require Earthquake proofing of some kind or another. Building in a flood plain should require adequate measures that will replace what is demolished while building.
We need to treat cities as large-scale designed environments like we do with the cities inside of large video games. In this way, EM can get involved with city design by providing context for all manner of way that we endanger ourselves.
In addition, there are some technologies that could be useful for what we need. For example, what we do need are:
- Mesh Networks that activate upon a hazard event.
- Extensible Software that is set up to access those meshes.
- Apps that activate in a disaster declaration to use on those mesh networks.
- Access to phone location data during a disaster.
- Indoor-based location services.
- A way to gather locations of devices, their activity, and various ways that electronics are being used post-disaster.
- Cities that break in ways that afford residents with materials to use for shelters.
- More frequent shelters built before a disaster.
- Training and materials that provide residents with spaces and places to go in the midst of a disaster.
In short, what the above list is is essentially stuff that already exists but not in a way that EM can use. Extensible software is of interest to me specifically as we already see untold numbers of folks in disaster going nuts with improvising all sorts of things with tech that isn’t mean to do what it is being used for.
This level of “hacking” or re-designing something in real time was so prevalent in the early days of computing. Bringing parts of this back for EM to advise on and potentially request is nothing short of a victory over capitalism and profit. Speaking of this capacity of advising, the last tenet is just that, EM should be a risk grader of all tech that reaches a certain threshold.
All the time — EM Should Focus on Risk Created by Tech
EM understands and deals with catastrophe created by risk. Or to be more plain, it concentrates on things when human culture has failed, receded, or has otherwise disappeared. In this vein, it seems pertinent that the easiest way of integrating technology with EM is to foster the idea that EM should be producing content focused on how different technologies will fare should a hazard event occur. Like the FDA, where EM can help is by assigning something like a risk modifier to each new technology that is released at local, regional, state, federal, and national levels.
But what does this mean?
Well, disasters are not created by a single hazard event like a tornado or an earthquake. Instead, the local area is made more and more fragile as humanity inserts itself into an area where particular hazard events may or may not take place. Each house, strip mall, telephone pole, road, drive-way, underground wire, sewer, automobile, truck, moped, and person weakens an area. That weakness impacts the natural abilities of the earth we build on to protect us from the elements. It also raises the risk of each individual that lives within an area.
And all that there is to really protect us from ourselves is an EM agency, group, or volunteer group. We have no protections from ourselves, from the companies producing any of the list above. We have no protections from technology companies, from manufacturing processes, and we do not have any sort of mechanism through which to hoist responsibilities for the risks created by those companies.
While we see some calls for this through texts like Ruined by Design: How Designers Destroyed the World, and What We Can Do to Fix It, there has been little to no movement within government spaces to begin to regulate or at least outline how tech companies, how any company, should be held responsible for their part in risk. This is where the potential elevation of EM back to a cabinet level agency would move from a fantastic move for mitigation to a fantastic move in general.
So how to get there?
These 3 tenets provide a robust collection of impulses, energies, and focuses for any developer looking to deal with the risks of the social lives of the everyday non-human. But the question that should be asked of any post like this remains, “How do we get there?”
This, like any largescale effort, begins with a step. Initially, these steps are things like trainings, white papers, partnerships, experimentation, and a whole lot of very ugly public discussion.
There is a rather large roadblock of public opinion about the government due to increased risk of some groups over time. And so, equity must be pursued against portions of the political sphere’s call for anything involving equity to be called, “CRT.”
So how do we get there? Not easily.
The central problem isn’t the lack of an agency or the lack of regulation, it’s the lack of interest in our own safety because we aren’t all actively in peril all of the time. And yet, this is becoming harder and harder to deny. Whether it be a rising frequency of hazard events, a rising severity of events, or humanity noticing how much they’ve put themselves at peril, risk will define this century and mitigation must become normalized should we desire to survive in the centuries that will follow.
Finishing Up
In the end, I suppose this entire article is a way of saying, “Let’s actually build what EM wants versus trying to take existing, subpar products and force it on EM.” In addition, we suggest that EM should become a home for labeling the risk inherent in all technologies whether it be focused on a calorie-like label on products that describe how it increases risks under certain conditions.
Is any of this possible? Sure. As we learned from COVID:
The first lesson the coronavirus has taught us is also the most astounding: we have actually proven that it is possible, in a few weeks, to put an economic system on hold everywhere in the world and at the same time, a system that we were told it was impossible to slow down or redirect. To every ecologist’s argument about changing our ways of life, there was always the opposing argument about the irreversible force of the ‘train of progress’ that nothing could derail ‘because of globalisation’, they would say. And yet it is precisely its globalised character that makes this infamous development so fragile, so likely to do the opposite and come to a screeching halt.
And so what, if anything, we have learned in recent memory is that we actually can be responsible despite those who would benefit from irresponsible inaction in the face over an overwhelming need for action.
All we need is a thing to respond to that includes or is focused on the needs above. A good example of this is cell phone integration with 9–1–1. While this is still probably a good couple decades away from full integration, that this moment exists in history is something to be inspired, calmed, or even get a little hopeful for despite the constant delaying tactic of waivers. After all, this has happened before and in the hearings about cell phone integration with 9–1–1, we see this quote that is hugely relevant today:
Nevertheless, the public safety community urges that the Commission be firm and, to the extent possible, hold the carriers to the existing deadlines, because lives are at stake. Every day of delay is another day that the public is at risk because of the inability to quickly and accurately locate emergencies reported on wireless telephones.
Perhaps this time though, we can avoid constant delays and waivers of responsibility in favor of mitigating avoidable deaths rather than waiting until the death count is so high that public furor forces actions that should have been taken far sooner.