Organisation module · the platform foundation

Organisational structure, processes and resources.
One database for BCM, risk and vendors.

The Organisation module is the starting point of BCMLogic Next – everything else builds on it. You map the real legal and operational structure, the register of processes and functions, and the asset register. The same data is used by the BIA, risk assessment, vendor oversight and What-If impact analysis.

In brief

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.

Key facts

Structure: group, companies, branches and units – in list and org chart views

Processes and functions: a hierarchical model: business processes, critical or important functions (DORA), projects, products

Assets: locations, systems and ICT applications with confidentiality, integrity and availability valuation

Perspectives: the same process viewed from a business continuity, risk or compliance perspective

What-If: failure impact propagated up the dependency graph, with an MTPD breach counter
See it in action

Structure, processes and assets in practice

Recordings from the BCMLogic Next platform. Pick an area – the next recording starts automatically.

BCMLogic Next · Organisation

The group company register, followed by the organisational structure in list and org chart views.
Organisational structure

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.

Process register

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.

A process catalogue organised by entity, department and criticality level.
BIA integration: RTO, RPO, MTPD and minimum resource requirements at process level, passed on to business continuity plans.
Links to ICT assets, services and vendors – data for What-If analysis and the DORA Register of Information.
Owner, last and next review dates – fully auditable.
One process, three perspectives: business continuity (current BIA), risk (number and level of risks) and compliance.
Regulatory classification
DORA
Flagging critical or important functions (as defined in Article 3(22)) and the ICT assets supporting them.
ISO 22301
Processes and activities in scope of the business impact analysis.
NIS2
Processes and information systems within the scope of the information security management system.
Asset register

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.

1

Asset profile and valuation

Owner, type, linked critical processes and confidentiality, integrity and availability (CIA) valuation with justification.

2

Threats

Threats relevant to the asset, selected from a catalogue.

3

Vulnerabilities

Vulnerabilities from a catalogue, added manually or imported from scan results.

4

Inherent risk

Assessment of threat–vulnerability scenarios before controls.

5

Controls and treatment

Existing safeguards and the risk treatment plan.

6

Residual risk and acceptance

Control effectiveness for each scenario, the aggregated risk level and the acceptance decision.

Why it matters
A single source of data
An asset described once is used in the BIA, in risk assessment and in What-If analysis.
Methodology at hand
The Methodology button in the analysis shows the scales and assessment criteria in use.
Inventory for the ISMS
An asset register with CIA valuation supports the information security risk assessment required by ISO/IEC 27001 and NIS2.

Analysis steps and valuation scales are configurable.

What-If impact analysis

“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.

Example What-If scenario: failure of the CRM database server and its impact on critical processesFAILED ELEMENTICT SERVICES AND SYSTEMSCRITICAL PROCESSEShard 100%degraded ~50%redundant ~20%CRM database serverCRM database serverfailure – total lossCRM applicationCRM applicationunavailableCustomer portalCustomer portalpartially workingData warehouseData warehousefailed over to backupComplaints handlingComplaints handlingMTPD exceededSalesSalesRTO at riskManagement reportingManagement reportingminor impact

Scenario: failure of the CRM database server.

Hard dependency → CRM application unavailable → Complaints handling: MTPD exceeded
Degraded dependency → customer portal partially working → Sales: RTO at risk
Redundant dependency → data warehouse on backup → Management reporting: minor impact
1
critical function with MTPD exceededthe key number of the scenario

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%.

Deliberately conservative assumptions

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.

Related modules

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.

BCM module →

Risk management

Risks assigned to processes, assets and units, aggregated along the structure.

Risk module →

Vendor management

Vendors and contracts linked to the processes that depend on them.

Vendor module →

Online demo

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.

Book a demo →

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.

FAQ

Frequently asked questions about the Organisation module

Answers for BCM, risk, IT and security teams.

What is the Organisation module in BCMLogic Next for?
The Organisation module is the foundation of the platform: it holds the organisational structure, the register of processes and functions and the asset register. All other modules – BIA, risk assessment, vendor management – and the What-If impact analysis use this data.
Does BCMLogic Next support groups and multiple companies?
Yes. The platform natively supports multi-entity organisations: parent company, subsidiaries, branches, shared service centres and cross-border structures. The company register and org chart let you assign processes, assets and risks to specific entities and aggregate them at group level.
How do you build a register of processes and critical functions for DORA?
In BCMLogic Next processes and functions form a hierarchical model. Each process has an owner, criticality classification, time parameters and links to ICT assets and vendors. Critical or important functions within the meaning of DORA (Article 3(22)) are flagged in the register, and the links feed the BIA, ICT risk assessment and the Register of Information.
What is a What-If impact analysis?
It is a simulation that answers the question of what stops working when a specific asset, vendor, ICT service or process fails. The platform propagates the impact up the dependency graph and shows a hierarchical list of effects, the dependency graph, the number of critical functions with MTPD exceeded and an exportable scenario report.
How is failure impact propagation calculated?
BCMLogic Next distinguishes three dependency types: hard (full impact transfer), degraded (around 50%) and redundant (around 20%). When a process depends on several affected elements, the worst case applies, and unclassified dependencies are treated as hard.
Can the structure and users be imported from Active Directory?
Yes. User assignments to organisational units can be maintained in the platform or imported from an external system such as Active Directory. The scope of the integration is agreed during implementation.
How does an asset inventory support NIS2?
The information security management system required of essential and important entities under NIS2 relies on risk assessment for information systems. The asset register in BCMLogic Next holds confidentiality, integrity and availability valuations, threats, vulnerabilities and controls, and its links to processes show which services are at risk. In Poland, obligations under the amended KSC Act must be implemented by 3 April 2027.
Next step

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.

Book a demo →