What is the Organisation module in BCMLogic Next for?
The Organisation module defines which processes, functions and tasks the company performs, what resources they need and what the organisational structure looks like. It is the shared register for all analyses: BIA, risk and vendor assessments use the same processes and assets, so dependencies described once are visible everywhere, and What-If analysis shows the effects of a failure across the whole chain.
Structure, processes and assets in practice
Recordings from the BCMLogic Next platform. Pick an area – the next recording starts automatically.
Your real legal and operational structure – not a simplified version
The organisational tree is not cosmetic. It is the axis along which risks, processes, assets and dependencies are assigned, aggregated and reported.
Multi-entity hierarchy
Parent company, subsidiaries, branches, shared service centres and cross-border structures as one living tree.
Owners and users
Every process, asset and vendor relationship has an owner in a specific part of the structure. Assignments can be imported from Active Directory.
Inter-entity dependencies
Shared IT services, centralised functions and intra-group agreements that affect the resilience of the whole group.
Permissions by structure
Analyses, incidents and risks are assigned to units, so users see what they are responsible for.
The process register – the backbone of BIA, risk and plans
Every critical function is anchored in a process. A process has an owner, a criticality classification, time parameters and a chain of dependencies on assets and vendors.
Assets with valuation and step-by-step risk analysis
Assets fall into categories – locations, systems, ICT applications – and are shared by the BIA, risk assessment and minimum acceptable configuration.
Asset profile and valuation
Owner, type, linked critical processes and confidentiality, integrity and availability (CIA) valuation with justification.
Threats
Threats relevant to the asset, selected from a catalogue.
Vulnerabilities
Vulnerabilities from a catalogue, added manually or imported from scan results.
Inherent risk
Assessment of threat–vulnerability scenarios before controls.
Controls and treatment
Existing safeguards and the risk treatment plan.
Residual risk and acceptance
Control effectiveness for each scenario, the aggregated risk level and the acceptance decision.
Analysis steps and valuation scales are configurable.
“If this fails, what stops working?”
The What-If engine runs on the structure, process register and asset register. You choose the failed element – an asset, vendor, ICT service or process – and the degradation level. The platform propagates the impact up the dependency graph and shows where RTO or MTPD is breached.
Scenario: failure of the CRM database server.
Illustrative scenario. Colours: red – MTPD exceeded, orange – RTO at risk, green – minor impact.
Hard dependency
No alternative – full impact transfer. Unclassified dependencies are treated as hard by default.
Degraded dependency
Partial impact transfer, around 50%. The process keeps running, but with limitations.
Redundant dependency
An alternative exists – minimal impact transfer, around 20%.
When a process depends on several affected elements, worst-case propagation is applied. In risk analysis, overestimating impact is safer than missing it.
Typical uses of What-If analysis
Tabletop exercises
An ISO 22301-aligned failure scenario without triggering a real incident.
Concentration risk (DORA Article 29)
How many critical functions depend on a single ICT vendor.
Justifying redundancy investment
Whether a backup element really protects a critical function.
Management review
A concrete number of functions at risk instead of a vague “high risk” – with an exportable scenario report.
Organisation feeds every module of the platform
Structure, processes and assets described once are reused in every subsequent analysis.
Business continuity
Process BIA, emergency plans, scenarios and tests built on the process and resource registers.
Risk management
Risks assigned to processes, assets and units, aggregated along the structure.
Vendor management
Vendors and contracts linked to the processes that depend on them.
See your structure and a What-If analysis
In the demo we show how to map a group structure and the process and asset registers, then run a failure scenario and see which critical functions are at risk.
Live walkthrough
About 30 minutes with a BCMLogic expert, with an example tailored to your sector.
Implementation kick-off
The Organisation module is the first step of implementation – we show how quickly a shared process and asset base can be built.
Frequently asked questions about the Organisation module
Answers for BCM, risk, IT and security teams.
What is the Organisation module in BCMLogic Next for?
Does BCMLogic Next support groups and multiple companies?
How do you build a register of processes and critical functions for DORA?
What is a What-If impact analysis?
How is failure impact propagation calculated?
Can the structure and users be imported from Active Directory?
How does an asset inventory support NIS2?
Start with an organisation map your board will understand
We will show how BCMLogic Next builds a shared base of structure, processes and assets – and how a single What-If scenario shows which critical functions are genuinely at risk.