90 likes | 214 Views
Business Continuity. ALARM 04 CONFERENCE How to start a Business Continuity Plan by Bill Sulman and Jon Chesher Heath Lambert Group. What is a BCP?. A plan in the event of disaster Ultimate fallback situation Can be used for smaller incidents No good just having some contacts
E N D
Business Continuity ALARM 04 CONFERENCE How to start a Business Continuity Plan by Bill Sulman and Jon Chesher Heath Lambert Group
What is a BCP? • A plan in the event of disaster • Ultimate fallback situation • Can be used for smaller incidents • No good just having some contacts • Links with Emergency Plan • Looks inwards thus is different
Commitment • Senior Management need to commit • Plan might need some resourcing • Cost of hot, warm and cold start • Someone to manage the emergency • Someone to carry on normal activities • Allocation of priorities by management
Why do we need it? • % of organisations never recover • Potential failure of organisation • Corporate Governance requires it • CPA and BSI (PAS) 56 • The ultimate failure in CPA terms • Reputation/ property/ people • Civil Contingencies Bill
How to begin • Y2K is a start, but its only IT • Templates are available and can help • Framework within which to work • Departments to work on own plan • Fitting the bits into the jigsaw • Bids for “desks” in emergency centre?
Crisis teams Alternative premises Equipment IT Essential Services Personnel Supply/ delivery Risk analysis Evacuation Plan Training Business Recovery Contacts Telephone Trees Check lists What should it contain
Who should be involved? • Designate a BCP central team • Teams for IT, HR, PR and Property • A team in each Department to do plan • Overall control of plan • Designated person/ trainer/ consultant • Not everyone- need to know basis
Departmental/Corporate • Sort out your own departmental needs • Business Impact Analysis • Needs and Risks • 24 hours/ 3 days/ 7 days priorities • Insert into corporate framework • Jigsaw - premises and other needs
Updating and Testing • Getting the document finished • Keeping it live • Controlled access • Updates regularly • Availability to staff • Test it regularly