Emergency management with smart2project
Why?
Emergency management ensures that when an attack occurs, an organization can return to normal operations as quickly as possible to minimize damage.
The number of possible hazards that can threaten a company or an authority is very large. And especially in the last few years, there have certainly been more that were not previously on the radar screen, e.g. floods, energy bottlenecks, supply chain disruptions or pandemic-related staff absences etc.
Drawing up comprehensive emergency plans for all possible hazards is certainly far too much work and can hardly be done as part of day-to-day operations. So the challenges is to assess how much effort do I put into contingency plans for something that is unlikely to ever occur? Or conversely, how little effort do I put into something that does occur and has quite dire consequences?
To make matters worse, calculations of probabilities of occurrence have not exactly proven reliable, especially in the recent past.
So if we don’t know exactly what is coming, we have to think about what is actually being threatened.
In the case of companies, it is the processes and services that are needed to enable the company to add value. In the case of public authorities, it is the specialist procedures that mean that the service to citizens can no longer be provided in the event of a failure.
It is therefore important to clarify which data is needed to avert a “life-threatening” situation for the company or the authority.
Solution approach:
If one has this data basis, one can concentrate on the creation of only a few emergency plans. These refer to the so-called “chaos phase”, immediately after the “attack” (by attack is meant any event that can be of different origin, so also e.g. flood, storm, fire, pandemic etc.) has been noticed.
These contingency plans are always the same, because in the chaos phase you have to set up a plan on how to manage uncertainties, whatever they may be. So you have to clarify:
How does the organization go about first determining who or what is “attacking”?
How do you counter the chaos that occurs to protect personnel and company assets?
These two points are largely independent of the type of hazard. Only the third point then deals individually with what has been damaged. This then clarifies:
How will the incident be remedied and what needs to be done to establish emergency operations as quickly as possible, which can then be quickly transitioned to normal operations.
And this is exactly where smart2project comes in, because the central data foundation creates the necessary data basis by linking and structuring all data from the areas of personnel, processes and services and infrastructure in a meaningful way.
Once the case occurs, the templates can be cloned from the archive and come into implementation
Conclusion:
The focus of smart2project’s emergency management is not to establish and store a comprehensive, individual emergency plan for every possible hazard. It is to establish an emergency management that standardizes the process planning in the chaos phase for all types of emergencies and then creates the data basis for quickly entering emergency operation and then returning to normal operation.
