Please wait,
Processing your request...

Coat of arms family Van Soest Aengevaeren

... | Selecteer de Nederlandse taal

| User: Guest | Login

webhalla

The Bertels: John, Paul, George and Bernie. #theBeatles #joke #BernieSanders #Mittens https://t.co/rXvrXhDTam
23 Jan 2021

The #EDPB and #EDPS have adopted joint opinions on two sets of contractual clauses (#SCCs). One opinion on the SCCs for contracts between #controllers and #processors and one on the SCCs for the #transfer of personal data to #thirdcountries. #GDPR #Privacy https://t.co/t059wpaEIQ
18 Jan 2021

To all my followers: https://t.co/4Dqau5A7us
24 Dec 2020

The Lord of the #Ringo Peter Jackson #PeterJackson reveals #sneak #preview of his delayed #TheBeatles music #documentary. "THE BEATLES: GET BACK" https://t.co/W8NF3X0XQ9
21 Dec 2020

21 Dec 2020

ICT-Hotlist Topic

Back to the ICT-Hotlist...

Don't miss latest updates Follow

@WebHalla

Business Continuity Management: an introduction.

By Johan van Soest.

Published : 2016-12-09.

Last updated : 2017-05-02.

What is the purpose of Business Continuity Management?

The goal of a Business Continuity Manager is, within the limits and conditions formulated by company management, to take care that the normal activities of the company, organization or institution can (re-)start, within a stipulated time frame, when a calamity or disaster occurs. Governments pay special attention to information/data and ICT systems that receive, save, edit, view and send data as these are the most important resources for the contemporary business operations.

Business Continuity Management: some calamities we all can recognize.

Consequences of a calamity

The abruptness and the often large impact on the normal functioning of an organization can result in, among other things, the following:

Chaos and uncertainty
Demotivated employees
Services or products cannot be supplied (on time)
Financial auditing is no longer possible
Fraud
Damage to Image/brand/reputation
Information is no longer at hand
Vital information is lost
Injured or died (key) employees

A survey conducted by the American "National Archives & Records Administration" under banks, insurance companies, manufacturing and logistics companies shows that 25% of these companies that fell victim to a 2 to 5-day ICT disruptive calamity went bankrupt immediately. 93% of the companies that lose their ICT systems for 10 days or more, close down within a year. Shockingly high numbers that make no one happy.

What to do?

Awareness that a fire, power failure or other disaster not only affects your neighbour is the first step. Start with the questions "what am I going to do about it?" and "who is going to do it?". These articles may help getting you started:

Within your company or organization, you can implement the Business Continuity Management process based on the Deming Cycle of Continuous Improvement so existing procedures will be regularly reviewed, improved and changes consolidated so they match your ever changing business processes.

Deming Cycle of Continuous Improvement (Plan, Do, Check and Act) with consolidation.

Glossary

Calamity:

A calamity mostly arises from an incident of external origin that expands across multiple hardware systems, software systems or even employees. These incidents include:

Fire
Economic boycotts
Epidemics
Hacking
Floods
Sabotage
Software errors
Storm damages
Failing software updates

Of course a failure can result in a calamity. For example, a server that is running too hot for a long time and reports "overheating" as a failure can eventually result in a calamity such as a fire.

Failure:

Briefly formulated a failure is a confined problem that relates to one program or one hardware component. Solutions for failures are mostly found in redundancy and high availability systems ( HA )

You may vote your opinion about this article:

Scripts and programming examples disclaimer

Unless stated otherwise, the script sources and programming examples provided are copyrighted freeware. You may modify them, as long as a reference to the original code and hyperlink to the source page is included in the modified code and documentation. However, it is not allowed to publish (copies of) scripts and programming examples on your own site, blog, vlog, or distribute them on paper or any other medium, without prior written consent.
Many of the techniques used in these scripts, including but not limited to modifying the registry or system files and settings, impose a risk of rendering the Operating System inoperable and loss of data. Make sure you have verified full backups and the associated restore software available before running any script or programming example. Use these scripts and programming examples entirely at your own risk. All liability claims against the author in relation to material or non-material losses caused by the use, misuse or non-use of the information provided, or the use of incorrect or incomplete information, are excluded. All content is subject to change and provided without obligation.