What is the BCM module in BCMLogic Next?
It is business continuity management software that takes the organisation through the full BCM cycle: business impact analysis (BIA), strategies and emergency plans, scenarios, tests and post-test recommendations. Process and resource data come from the Organisation module, so the RTO set in the BIA flows straight into the plans, and test results flow back into the analysis.
What working in the BCM module looks like
Short recordings from the BCMLogic Next platform. Pick an area on the left – the next recording starts automatically when one ends.
RTO, RPO, MTPD and MAC – what you set in a BIA
Four parameters determine how fast and to what extent a process must recover. The timeline shows how they relate during a disruption.
Example timeline of a process disruption. RTO, RPO and MTPD are set in the BIA for each process separately.
RPO – Recovery Point Objective
The maximum period for which data may be lost. It determines how often backups or replication must run.
RTO – Recovery Time Objective
The time within which a process or resource must be back in operation after a disruption. Recovery strategies and priorities follow from it.
MTPD – Maximum Tolerable Period of Disruption
The longest outage after which the impact on the organisation becomes unacceptable. RTO must be shorter.
MAC – Minimum Acceptable Configuration
The minimum set of resources – people, systems, locations, vendors – needed to keep a process running in emergency mode.
The full business continuity cycle in one system
Each stage builds on the previous one, so the plan never drifts away from the analysis and test findings do not stay in someone’s notes.
Business impact analysis (BIA)
For each process: financial, operational, regulatory and reputational impact, time parameters and the minimum resource configuration built from the resource and contract registers.
Strategies and emergency plans
Who, what, in which order and with which resources – measured against the RTO from the BIA. DR plans, operational plans, staff relocation plans.
Scenarios
Plans grouped into scenarios by type of event. A scenario specifies which plans to activate and in what order.
Tests and exercises
Schedule of scenario and procedure tests, tabletop exercises and vendor-involved tests – with the status of every test.
Recommendations and updates
Findings from tests and audits become tasks with an owner and deadline. Changes flow back into the BIA and the plans.
This summary is for information only. The scope of obligations depends on the entity’s status and current legislation.
What the business continuity module includes
Ready-made screens and workflows based on methodologies developed over more than ten years of implementations. Use them as they are or adapt them to your own methodology in implementation workshops.
Comprehensive register
Processes and functions, services, resource requirements, organisational structure, crisis teams and backup locations in one repository.
Guided BIA
A configurable wizard covers process criticality, time objectives and the minimum acceptable resource configuration.
Continuity risk assessment
Risk assessed by process, resource (IT, people, locations, vendors) or unit – with potential losses linked to BIA data.
Versioned procedures
A repository of plans and procedures with a version comparator: differences between the current and draft version are visible before approval.
Scenarios and notifications
Scenarios based on event type, likelihood and impact. They can be linked hierarchically and trigger notifications.
Tests and recommendations
Plan tests of any combination of procedures, processes and resources, and track post-audit recommendations in a dedicated workflow.
A process owner who does a BIA once a quarter does not need to know the system. The wizard – or a conversation with the Expert GRC assistant – guides them with questions, suggests resources used in similar processes and ends with a summary for approval. The BCM team gets consistent data instead of spreadsheets in different formats.
Business continuity draws on data from the whole platform
BCM does not work in isolation. The same processes, resources and contracts feed risk assessment and vendor oversight.
Organisation
Structure, process and asset registers, plus What-If analysis: what stops working when a specific system or vendor fails.
Risk management
Business continuity risks in the risk register, with controls, treatment plans and KRIs.
Vendor management
Contracts identified in the BIA as essential for a process, assessed against DORA, NIS2 and continuity requirements.
See a BIA and an emergency plan on data similar to yours
In the demo we walk through the BIA of a selected process, an emergency plan and the test schedule – and show how BIA results translate into risk and vendor data.
Live walkthrough
About 30 minutes with a BCMLogic expert, focused on your questions and your sector.
Your methodology
We look at how impact scales, wizard steps and workflow can match the methodology your organisation uses.
Frequently asked questions about business continuity management
Answers to the questions we hear most often from BCM, risk and security teams.
What is business continuity management (BCM)?
What is a BIA and how do you carry it out in BCMLogic Next?
What is the difference between RTO, RPO and MTPD?
What business continuity requirements does DORA impose?
Does NIS2 require business continuity plans?
How should business continuity plans be tested?
How do we move existing BIAs and plans from Word or Excel into BCMLogic Next?
What should ISO 22301-aligned BCM software include?
A business continuity plan that works on the day of the disruption
We will show how BCMLogic Next connects the BIA, plans, tests and vendors into one process – and how to keep it current without assembling documents by hand before every audit.