Why Resilience, Risk and Compliance Belong on One Platform

Ask eRMA

In many organizations, three teams describe the same things in three different tools. Business continuity maps services, applications, sites and vendors to recovery objectives. Risk management rates the same vendors and applications in a risk register. Compliance links the same services to regulations and tests the same controls for auditors. Each tool is internally consistent. Together they rarely agree, and the gaps between them are where problems hide.

What goes wrong when they live apart

  • The same vendor is rated three ways. Critical in the BIA, moderate in the risk register, compliant in the audit file. Nobody notices until an incident or an examination does.
  • The same control is tested three times. Once as part of an exercise, once as a risk treatment, once for a compliance audit, each by a different team with different evidence.
  • Gaps fall between the tools. A high risk with no scenario or plan behind it. An obligation with no tested control. A recovery objective that has never been proven. Each team sees its own part, and nobody sees the gap.
  • Evidence is assembled by hand. Every audit or regulatory request starts with exports and spreadsheets from several systems.

Why the three are converging now

Regulators increasingly look at operational risk and resilience as one subject. In Canada, OSFI Guideline E-21 brings operational risk management and operational resilience together. In the United States, the banking agencies’ sound practices paper on operational resilience builds on existing risk management, business continuity and third-party guidance. Gulf regulators such as SAMA and the CBUAE also expect continuity, cyber and operational risk to be governed consistently.

The standards point the same way. ISO 22301 and ISO/IEC 27001 share the same high-level structure, and ISO 31000 sets out the risk principles both rely on. Separate tools for each make that shared structure harder to show.

What “integrated” should mean

Integration is not a bundle of modules sold under one name. It means:

  1. One set of records. Services, processes, applications, sites and vendors exist once. The BIA, the risk register and the compliance view link to them rather than copying them.
  2. Test once, use many times. One control test, with its evidence, can support a risk treatment, several obligations and continuity assurance at the same time.
  3. Gaps visible across functions. A high risk without a scenario or plan, an obligation without a tested control, or an unproven RTO is shown as a gap, whichever team owns it.
  4. Shared data, separate accountability. Risk managers, compliance owners and continuity coordinators keep their own rights and decisions. Sensitive risks can stay restricted to the people who should see them.
  5. Traceable in both directions. From a regulation to the control and evidence that satisfy it, and from a service to everything it must meet.

Integration doesn’t mean buying everything at once

Many organizations start with continuity, add risk when the register outgrows its spreadsheet, and add compliance when audit demands grow. That works well, as long as each addition uses the same records rather than a new copy. The question to ask is not “does the vendor have a GRC module?” but “will the module I add next year use the data I enter this year?”

Where eRMA fits

eRMA, the resilience platform from eBRP Solutions, keeps continuity, risk and compliance on one set of records. Core eRMA includes the BIA, dependencies, plans, exercises, incidents and risk assessment on the same processes, applications, services, sites and vendors. Enterprise risk management and compliance extend it on the same data:

  • Enterprise Risk Management (ERM): an ISO 31000 risk register in which each risk’s priority is computed, never typed in, and shows why it ranks where it does. It includes a control library with ISO 22301 and ISO 27001 references, a bow-tie of causes, controls and consequences, control tests with segregation of duties and attestation, and a flag on any high risk with no scenario or plan behind it.
  • Compliance (GRC): regulations and obligations linked to the records already in eRMA, compliance posture per regulation, and a trace from rule to control to evidence. One tested control can satisfy many obligations, and owners attest that their obligations are met.

Risk and compliance rights are assigned through teams, and restricted risks stay visible only to the people who should see them.

Three questions to ask any vendor

  1. Show one vendor everywhere. Open a critical vendor in the BIA, the risk register and the compliance view. Is it one record or three?
  2. Show one test, many uses. Show a single control test supporting a risk treatment and more than one obligation.
  3. Show a gap between teams. Show a high risk with no plan behind it. Does the platform flag it, and who sees the flag?

Continuity, risk and compliance will keep their own teams and their own decisions. They no longer need their own copies of the organization.

Download this as a one-page Brief: Resilience, risk and compliance on one platform (PDF)

Join an eRMA showcase: sixty minutes, live on Microsoft Teams.  ·  Download the eRMA brochure: see the possibilities.

The Resilience Report Nobody Reads (and What to Send Instead)

Every resilience program produces it. A report of two hundred pages, a workbook of twenty tabs and two thousand rows, assembled over two weeks and sent to the people who are meant to govern the program. It shows that a great deal of work was done. What it rarely shows is whether the organization could keep delivering if something went wrong tomorrow, and it almost never gets read.

That isn’t a failing of executives. It is a failing of the format.

Why the big report fails

It answers the wrong question. A long report is organized the way the program is organized: BIA, then risk, then plans, then exercises, each with its own appendix. A leader’s question cuts across all of them: “Can we keep delivering our important services, and if not, what is in the way?” The answer is spread over a hundred pages, so nobody assembles it.

It is out of date on arrival. Two weeks of collation means the numbers describe the program as it was, not as it is. By the time a question comes back, the analyst has to re-run the spreadsheet to answer it.

No two versions agree. Each line of business keeps its own workbook, with its own definitions. Totals from different reports don’t reconcile, and a meeting that should be about decisions turns into a meeting about whose numbers are right.

Green hides gaps. A status column turns green when a document exists and its review date is current. Missing data shows as blank, and blank reads as fine. A program can look healthy on paper while its recovery objectives have never been tested.

What leaders actually need

Executives and program stakeholders need far less, presented far better:

  • One answer per question. Can we deliver within tolerance? Where is risk concentrated? Is the BIA cycle on track? Each question gets its own page, with the answer first.
  • The exceptions, by name. The service whose recovery has never been proven, the single supplier three lines of business depend on, the plan overdue for review.
  • Their own part of the organization. The board sees the enterprise; a business head sees their division; a department head sees their department, with the same measures at every level.
  • Movement over time. Better or worse than last quarter, and since when.
  • A way to check. Any number can be followed back to the records behind it, by whoever is entitled to see them.

Five tests for a resilience dashboard

Many tools now offer a “dashboard”. Before trusting one with a board, put it through five tests.

  1. Is it live? Does it read the records the program maintains, or a copy exported last month? If someone has to refresh it by hand, it is the old report with better colours.
  2. Does unknown look like unknown? A service with no evidence of recovery should show as unproven, not green. Ask to see a record with missing data and check how it is counted.
  3. Do the totals agree for everyone? If a department head and the CEO see different totals because of their access, the dashboard creates the same reconciliation argument as the spreadsheets. Totals should count everything; only detail should be restricted.
  4. Does it follow the organization? One dashboard should serve every level by changing scope, not by building a separate report for each division. A restructure shouldn’t break it.
  5. Can it leave the room safely? Boards still want paper. A printed page should state what it shows, who produced it, when, for which part of the organization, the date the data is as of, and how it may be shared. Without that, a printout becomes an uncontrolled copy the moment it’s made.

The board pack doesn’t disappear. It gets thinner.

Governance still needs a record: minutes refer to what the board saw, auditors ask for it later, and regulators expect evidence that leadership was informed. The difference is that the pack becomes a dated snapshot of live dashboards, built in minutes instead of weeks, rather than a document assembled by hand. The detail is still there for anyone who needs it, one click behind the summary rather than a hundred pages behind it.

Where eRMA fits

eRMA, the resilience platform from eBRP Solutions, includes Executive Dashboards that pass all five tests:

  • The answer comes first: six headline numbers, each with its trend.
  • One page for every level: the org chart, coloured by risk; click a unit to look inside.
  • Every number opens: the records behind it, with the same totals for everyone. Unknown is never shown as healthy.
  • Ready for the board: print a dated, marked board pack, or share a live link.

See the Executive Dashboards feature →

Three questions for your next board report

  • Which page would a director need to read to know whether the important services can be delivered within tolerance?
  • How old are the numbers on that page on the day the board reads it?
  • If a director asks “which service, and why?”, how long does the answer take?

If the honest answers are “page 140”, “a month” and “we’ll come back to you”, the program isn’t short of data. It’s short of a page that gets read.

Join an eRMA showcase: sixty minutes, live on Microsoft Teams.  ·  Download the eRMA brochure: see the possibilities.

Data Management: keep the spine of your resilience program current

Every resilience answer runs along the same spine: the service at the head, and the people, processes, technology, facilities and suppliers it depends on. The impact of an outage, whether a plan can meet its RTO, who to call at 2 AM: each one is read from those records. Most programs load them once, at implementation, and then watch them age. People move, applications are retired, a supplier changes, two servers become one. Within a year the dependency graph describes a business that no longer exists. Data Management is how eRMA keeps the spine current.

The problem it solves

  • “Everything was loaded at go-live. Nobody has touched the server list since.”
  • “HR knows who left last month. The call tree doesn’t.”
  • “Every bulk update is a weekend project, because nobody can see what the spreadsheet will change until it has changed it.”

How it works

1. Start with the records the spine is made of

Data Management opens on the core entities, in the order they depend on each other: locations, employees, vendors and teams first; then hardware, virtual servers, databases, networks and applications; then processes and services; then the plans, scenarios, exercises and risks built on top of them. Each phase finds the records the earlier phases created, so links are resolved by business key, not by hand.

Data Management load order: base entities first, then processes and services, plans, scenarios, exercises, compliance, risk, strategy, BIA, map and sites, each phase finding the records the earlier ones created

The overview shows how many records of each kind the program holds, so a gap in the spine is visible at a glance.

Data Management overview counting the core records the program holds: locations, employees, vendors, teams, servers, databases, networks, applications, processes, services and recovery plans

2. One published contract for every file

Every entity has a template and a field guide: the required columns, each column’s type and length, the allowed values, and the business key that identifies a record. The same definitions drive import, export and the pre-check, so a file built from the template today still loads next year. The pre-check reads each file as it is uploaded and flags a missing header, a blank required cell, a date that isn’t a date or a value outside the list, before anything runs.

3. See every change before it lands

Every import starts with a dry run. Per file, it reports how many records will be added, how many updated, how many left as they are, and which rows can’t be accepted, with the reason. Nothing is written until an administrator commits, and the commit is one transaction: all of it or none of it. On a live database a restore point is taken first. Update mode refreshes existing records in place, matched by business key, so a refresh changes what changed and nothing else.

4. Refresh on a schedule, not as a project

The systems that already know the truth keep the spine current: the HR feed, the CMDB extract, the vendor master. A schedule picks up their files from a drop folder daily, weekly or as soon as a file arrives. Each run starts with the same dry run and commits only when the result is clean and inside the limits its owner set: how many changes, how many deletions, what share of employees may be removed in one run. Anything outside those limits is held, not applied, and appears in the owner’s MyWorkspace with the reason. An employee missing from the HR feed is retired in the same gated run.

A check-only schedule answers “would this feed be clean today?” without changing anything: the safe way to bring a new source online before it is trusted to commit.

5. Take it all out, and back in

An export pack holds every file in load order, in exactly the template layout, with a manifest of what it contains. Re-import an unchanged pack and the dry run says: nothing to change. That round trip is the test that the contract is honest, and it makes the pack a portable copy of the program for a test environment, an audit or a move. Exports can run on a schedule too, to a folder, for reporting or an off-site copy. Every import and export is logged: who, when, what and how many rows.

Data Management is open to administrators only. Everyone else exports from their own list pages, and only the records they are allowed to read.

What it proves

The Impact Map, the business impact analysis, recovery strategies and plans all read the same records. Keep those records current and every answer built on them stays current: an outage traced today reaches the processes that exist today, and a call tree reaches the people who still work there. Change is visible before it lands, bounded when it runs on its own, and recorded afterwards. The spine stays true without a re-implementation every year.

Join an eRMA showcase: sixty minutes, live on Microsoft Teams.  ·  Download the eRMA brochure: see the possibilities.

Fewer People, More Duties, Less Time: What BCM Platforms Must Do

Ask eRMA

Three pressures now shape almost every business continuity program. Teams are smaller, often one or two people supported by part-time coordinators. Their remit keeps growing: operational resilience, third-party dependencies, cyber recovery, regulatory evidence. And the time allowed to answer is shrinking, from the next quarterly report to the next fifteen minutes of an incident. A platform chosen for a larger team and a slower world makes all three worse. A platform designed for them gives time back.

The three pressures

  • Fewer people. The program depends on managers and coordinators whose main job is something else. Every extra form, login or follow-up costs participation.
  • More duties. Business impact, dependencies, plans, exercises, incidents, risk and evidence for auditors are increasingly expected from the same team, and expected to agree with each other.
  • Less time. Leaders and regulators expect a current answer when they ask, not after a data call. During an incident, the window is minutes.

Six design priorities

1. Ask once, reuse everywhere

The same fact, such as the applications a process uses, should be entered once and appear in the BIA, the dependency map, the plans and the reports. Where processes share a parent, answers should be inherited rather than collected again. Every repeated question is a cost paid by a busy manager.

2. Let the people closest to the data maintain it

Contact details, locations, duties and availability change weekly. Central teams can’t keep up with that by email. Staff should be able to keep their own information current, with an endorsement step where accuracy matters, so the program owner reviews changes instead of typing them.

3. Load in bulk, safely

Organizations rarely start from nothing. Data arrives from HR systems, application inventories, vendor lists and older tools. A platform should take it in bulk through templates, check it before anything is saved, allow a dry run, and export it back out in the same format, so a load can be repeated without fear.

4. Show what needs attention first

A small team can’t browse its way to the problem. Each role should land on what needs it: overdue reviews, gaps between recovery objectives, plans not exercised. Navigation menus are for finding things; the first screen is for deciding what to do next.

5. Settle the order of recovery before the incident

When time is short, the running order can’t be worked out live. Plans should be sequenced by their dependencies ahead of time, so the total recovery path is known. On the day, activation, roll call, tasks and decisions belong in one live view rather than across email threads and phone calls.

6. Be honest about gaps

Dashboards that turn green when data is missing are worse than none, because they hide the gaps a small team most needs to see. Missing data should read as “Unknown”. Data a viewer may not see should read as “Restricted”, never as zero, so totals are never quietly wrong.

Who should drive the design?

Platform design is often argued in terms of program deliverables, user expectations or industry practice. All three matter, but each answers a different question:

  • Program deliverables decide what the platform must produce: the BIA, plans, exercise evidence, reports for leaders and regulators.
  • Users decide how it should work: the managers, coordinators and staff who give it a few minutes a quarter. If it doesn’t suit them, the data goes stale and the deliverables fail anyway.
  • The industry sets only the minimum: standards such as ISO 22301 and regulatory expectations define what must be covered, not how pleasant or fast it is to cover it.

A platform built to the industry minimum often passes an evaluation checklist and then struggles with adoption. Under today’s pressures, the users’ “how” is where most of the value lies.

Where eRMA fits

eRMA, the resilience platform from eBRP Solutions, is designed for small teams with a wide remit. All of the following are available today:

  • Ask once: one connected model of processes, applications, services, locations, vendors and people, used by the BIA, the Impact Map, plans and reports, with group BIA and inheritance.
  • Closest to the data: the Employee Kiosk, where staff keep their own profile, whereabouts and duties current, with endorsement.
  • Bulk, safely: Data Management templates with pre-checks, dry runs, and an export and re-import round trip.
  • Attention first: role-based workspaces that open on what needs that person’s attention.
  • Recovery order: the Plan Sequencer for the running order, and Incident Management for activation, roll call, tasks, decisions and messages in one live view.
  • Honest gaps: “Unknown” is never shown as healthy, and “Restricted” is never shown as zero.

See it: Dependency Designer and Impact Map →

See it: Plan Sequencer →

Three questions to ask any vendor

  1. Show a coordinator’s quarter. What does a part-time coordinator do in the platform in a quarter, and how long does it take?
  2. Show a bulk load, twice. Load a file, fix an error, and load it again. What protects the data the second time?
  3. Show the first fifteen minutes. From activation to the first decision in an incident, where does each person look?

Smaller teams aren’t a temporary condition. The platform should be designed for the team the program has, not the one it had.

Download this as a one-page Brief: Six design priorities for a BCM platform (PDF)

Download the eRMA brochure · Join the next live showcase

Executive Dashboards: resilience on one page, not two hundred

Leaders ask the same few questions about resilience. Are we ready? Can we keep delivering? Where is the organization weakest? eRMA’s Executive Dashboards answer them on one page, from the records the program keeps up to date every day. Nothing is copied into a spreadsheet, so there is nothing to reconcile.

The problem it solves

  • “The board pack takes two weeks to put together, and it’s out of date the day it’s printed.”
  • “Every business line reports its own numbers, and they never add up.”
  • “The answer the board wants is somewhere on page 140.”

How it works

1. The answer comes first

The Executive Resilience Scorecard opens on one question: are we ready? It answers with a handful of figures: important services ready tonight, services proven within their RTO, programs at their coverage target, and risks above appetite. Each says what changed since the last review and which records need a decision. Below them, one bar shows how prepared each important service is, and names the weakest condition.

Executive Resilience Scorecard answering Are we ready: important services ready tonight, proven within RTO, programs at target, risks above appetite and obligations not compliant, with the preparedness of the important services below

2. One picture for every level

The Organization Resilience Map shows the whole organization as one picture. Each unit is a box: its size is the records it owns, its colour is the measure chosen, such as open risks, untested recovery or overdue reviews. A ranking beside it puts the units worst for their size first, so a small unit with a big problem is not hidden behind a large one. Click a unit to look inside it.

Organization Resilience Map as a treemap: each unit's box sized by the records it owns and coloured by open risks per 10 records, with the units ranked worst for their size

3. Every number opens

Click a number to see the records behind it. Everyone sees the same totals. Records a viewer is not allowed to open are still counted, but not shown.

One dashboard per question

  • The board: the Executive Resilience Scorecard. Are we ready?
  • The COO: Can We Keep Delivering? Important services against their recovery time and tolerance, single points of failure, and dependencies shared across lines of business.
  • The CRO: Enterprise Risk. Inherent and residual risk, movement and treatment, for the organization and each unit.
  • Business heads: the Line of Business Scorecard, with the asks for the quarter’s review.
  • The program manager: Plan Quality and Readiness, Recovery Proof and Testing, and Governance and Data Health.
  • Compliance: ISO 22301 Tracking, clause by clause; with the GRC add-on, Regulatory Compliance and Assurance and Findings.
Can We Keep Delivering: important services that would recover too slowly today, beyond tolerance, single points of failure and cross line of business processes, with recovery time against tolerance per service

Ready for the board

Every dashboard has a Report and exports to PDF and Excel, dated and marked confidential. Combine several into one board pack, or freeze a snapshot and share it with chosen teams.

What it proves

One set of numbers, taken from the program’s own records, for the board and the business alike. Unknown is never shown as healthy, a walkthrough is never counted as proof, and Restricted is never shown as zero.

Join an eRMA showcase: sixty minutes, live on Microsoft Teams.  ·  Download the eRMA brochure: see the possibilities.

Map and situational awareness: see what an event will reach

Every resilience program eventually gets the same phone call: there is a wildfire, a hurricane warning, a flood, a power cut across a region. What do we have there? Most programs answer it by searching spreadsheets for city names. eRMA answers it on a map. Every process, application, service, plan, server, employee and vendor is placed where it actually runs, so the question becomes a picture: where your records are, how exposed they are, and what is coming toward them.

The problem it solves

  • “When an alert comes in, it takes hours to work out which of our sites and processes are in the area.”
  • “We think we have a second site for everything, but nobody has checked how far apart the sites really are.”
  • “Our critical work is concentrated in one city, and the only time anyone noticed was during an outage.”

How it works

1. Every record, placed where it runs

Locations, employees and vendors sit at their own addresses. Processes, applications, services, plans, databases and servers are placed at the locations their dependencies lead to, so a process shows up wherever its people work and wherever its systems run. On each record’s page, a map card under “Where it runs” shows its nearest locations first, with technology sites one click away. Locations the viewer is not allowed to open are drawn in grey and counted, never named. Records with no position are listed as not placed, not quietly left off the map.

2. Spread and concentration, judged for you

Spread looks at each process, application or service and gives it a verdict: single site, clustered, one region, spread or not placed. It can judge by work sites, where the work is done, or by technology sites, where its systems run. Sites closer together than a set distance count as one cluster, so two offices across the street are not mistaken for a recovery option.

eRMA map of North America with record clusters, and the Spread panel judging processes by work site: single site, clustered, one region, spread or not placed

Concentration turns the question around. It groups sites that sit close together, or by state and province, and shows for each area how many critical records would be lost entirely if it went dark, how many employees work there, and how many severe alerts have reached it in the last twelve months. “Find what is lost” lists the records with no site outside the area.

Map of southern Ontario with clusters of records around Toronto and the western end of Lake Ontario, the sites close together that the Concentration panel groups into one area

3. Search any area

Draw a rectangle, circle or polygon, pick a boundary such as a country, state, province or US county, or upload a KML, KMZ or GeoJSON file. eRMA finds every record with a site in the area, or only the ones that would be lost entirely because no work site or technology site sits outside it. Areas can be saved as shared layers and reused in the next exercise.

4. Live hazard alerts over your records

eRMA reads public alert feeds, such as US National Weather Service alerts, FEMA disaster declarations, Canada’s public alerting system, European and global warning services, and the alert feeds of national weather agencies that publish them. Severe and extreme alert zones are drawn over the records they reach. Anyone can watch a layer and be notified when an alert reaches it, and each alert that touched an area is kept as history, so the risk assessment can see what has actually happened at a site, not only what might. Feeds are switched on by each organization, after its administrator accepts each source’s terms; until then eRMA calls nothing outside.

Map of the United States with live severe and extreme weather alert zones drawn in red over the record clusters and vendor sites they reach

5. From the map to the response

When an alert or event needs a response, an incident can be opened straight from the map with its area attached. eRMA assesses every record in the area, suggests a severity from the alert, and keeps a snapshot of what the area held at that moment. A one-page situation brief prints as a PDF. During the incident, its own Map tab shows the assessed records, live alerts over the footprint and the roll call. The same areas become a scenario’s footprint, so an exercise can show exactly what the event would have reached.

What holds it together

  • One set of records. The map, the business impact analysis, the plans and the incident all read the same locations and dependencies. A site is recorded once.
  • Restricted is never zero. Records a viewer cannot open are still counted, so a total on the map matches the total everywhere else.
  • Unknown stays unknown. A record with no position shows as not placed. It never counts as safe because it is missing from the map.
  • People’s homes stay private. Where staff live can be shown only as counts per square, never a home, only to teams an administrator grants, and every look is logged.

Running eRMA in an air-gapped deployment? There, eRMA never calls out. eRMA Portal Services brings live hazards, emerging threats and regulatory change across the gap as signed files, each one verified and approved before anything is applied. Get the eRMA Portal Services brochure (PDF)

See it with your own sites: Book a demo

Justifying a BCM Platform: A Business Case Finance Accepts

Ask eRMA

Budget requests for business continuity often rest on one argument: a disaster would cost far more than the platform. That is usually true, and finance teams usually discount it, because it can’t be tested and it looks the same every year. A business case that gets approved does something different. It shows what the current way of working already costs, and which of those costs a platform removes, using numbers the organization can check.

Why “it prevents disasters” isn’t enough

Avoided-loss arguments ask finance to price an event that may never happen, at a probability nobody can defend. Reviewers treat them as soft benefits, which is fair. The stronger approach treats the avoided loss as the last line of the case, not the first, and builds the rest from costs the organization is already paying.

The current process is not free. Spreadsheets, survey tools, consultant refreshes and staff hours make up a budget nobody tracks. Making it visible is often the most persuasive part of the case.

Four value lines finance can test

Order the benefits from easiest to prove to hardest. Finance reads from the top, and an early line it trusts makes the later ones more credible.

1. Tools and services retired

List what the platform replaces: survey tools, spreadsheet and SharePoint upkeep, a separate risk register, the consultant engagement behind the annual refresh, and any older continuity software still on contract. These are cash lines with invoices behind them, which makes them the easiest to verify.

2. Effort removed

Count the hours the program spends every year. How many managers complete the BIA, how long each questionnaire takes, and how many follow-ups it needs. Add the hours spent updating plans, preparing and writing up exercises, and collecting evidence for auditors. Multiply by a loaded hourly rate your finance team already uses.

Be precise about the claim: most of this is capacity freed, not cash saved. Say what the team will do with the time, such as more exercises or more coverage, rather than implying headcount reductions nobody has agreed.

3. Audit and regulatory exposure reduced

Don’t put a price on fines. Measure what auditors and regulators actually observe: open findings related to continuity, the time it takes to answer an evidence request, and how many recovery time objectives (RTOs) have been proven in an exercise rather than simply stated. Regulators in the United States, Canada and the Gulf increasingly expect evidence that operational resilience is tested, so a shorter answer time is a credible benefit on its own.

4. Recovery capability improved

This is the avoided-loss line, done properly. Use the impact figures from the organization’s own BIA. Where the platform closes a gap, for example a dependency whose recovery time is longer than its process can tolerate, estimate the hours of disruption it removes, and apply the impact per hour the business has already approved. Show a conservative and an expected value, never just the high one.

Be honest about the cost side

A case that only lists the subscription invites a second review. Include implementation, data migration, integration, training and the internal time needed during rollout. Then compare a three-year total cost of ownership against the three-year cost of the status quo, not against zero. Show a payback period, and say which month the first benefit appears.

Five rules finance respects

  1. Use the organization’s own numbers. Industry averages are easy to dismiss.
  2. Separate cash from capacity. Present them in different rows, and don’t add them together without saying so.
  3. Show a range. Conservative and expected values, with the assumptions written down.
  4. Give each benefit an owner. Someone who will report on it after twelve months.
  5. Measure the baseline now. Without today’s hours and findings, there’s nothing to compare against next year.

Where eRMA fits

eRMA, the resilience platform from eBRP Solutions, maps to each value line. All of the following are available today:

  • Tools retired: BIA, dependencies, plans, exercises, incidents and risk assessment on one data set, with ERM and Compliance (GRC) available as optional add-on modules.
  • Effort removed: group BIA with inheritance, so shared answers are given once; live campaign progress instead of chasing by email; the Employee Kiosk, where staff keep their own details current; and Data Management templates with pre-checks and dry runs for bulk loads.
  • Audit exposure: Exercise results recorded per entity against its RTO, with the evidence kept, plus role-based views that show “Unknown” rather than a false green.
  • Recovery capability: the Impact Map shows where recovery times don’t line up, and the Plan Sequencer shows the full recovery path to check against tolerance.

See it: Business impact analysis →

Three questions finance will ask

  1. What does the current way of working cost today? Have the hours, tools and consultant fees ready.
  2. Which savings are cash and which are capacity? Answer before you’re asked.
  3. How will we know in twelve months? Name the measures and their owners.

The one-page Brief includes a worksheet with each value line and space for your own figures.

Download the worksheet as a one-page Brief: Business case worksheet for a BCM platform (PDF)

Download the eRMA brochure · Join the next live showcase

One resilience program, the right page for every role

A resilience program is run by many people who never look at it the same way. The board wants to know whether the organization can keep delivering. The program manager wants to know what needs attention first. A department head wants to know what they owe the program this week, and an auditor wants proof. eRMA keeps one set of records and gives each of these people their own page into it: their question first, their part of the organization, and only the detail they are allowed to see.

The problem it solves

  • “Every audience gets its own spreadsheet, so every meeting starts by arguing about whose numbers are right.”
  • “Owners only hear from the program once a year, when the BIA form arrives.”
  • “In an incident, nobody is sure who is meant to do what, or what they are allowed to change.”

Six roles, one program

1. Executive sponsor and board: “Can we keep delivering?”

Executives see the program as answers, not appendices. The Executive Resilience Scorecard shows posture, coverage, top risks and overdue reviews on one page. Can We Keep Delivering? compares each important service’s recovery objective with what has actually been proven. When the board meets, the same pages print as a dated, scoped and marked board pack.

Six executive dashboards, one per audience: Executive Resilience Scorecard for the board, Can We Keep Delivering? for the COO, Enterprise Risk for the CRO, BIA Program Progress, Line of Business Scorecard and the Organization Resilience Map

2. Resilience program manager: “What needs me first?”

MyWorkspace opens on a ranked list of what needs attention: BIAs waiting for answers, plans past their review date, services without recovery proof. Each area of the program is a card marked Attention or On track, mapped to the ISO 22301 clause it supports, with the next step one click away. A gap shows as a gap. It never turns green because a document exists.

MyWorkspace Program cards for scope, BIA, risk assessment, strategy, plans and exercise, each marked Attention or On track with its ISO 22301 clause and the next step

3. Regional and business-unit coordinator: “How is my part of the organization doing?”

Coordinators see the same measures as the program manager, scoped to their region, legal entity or line of business. Every dashboard follows the organization tree, so a coordinator can drill from their division into each department, and a restructure changes the scope, not the report.

4. Process, service and application owners: “What do I owe the program?”

Owners see only what is theirs: the BIA to answer, the plan to review, the dependency to confirm, the approval waiting for them. MyWorkspace switches between three modes. Own shows an owner’s records and tasks, Govern shows the program, and Operate takes over when an incident is open.

MyWorkspace mode switch: Own, Govern and Operate, with a time horizon of today, this week or the next 30 days

5. Incident lead: “Who is affected, and who is on it?”

When an incident opens, the response runs from one page: plans activated, tasks for each team, a roll call that knows who is away, decisions recorded as they are made, and messages to the teams involved. Each person sees why they have access, such as incident commander or an invoked team, so nobody has to guess what they are allowed to change.

An open incident with buttons to message teams, record a decision and flag it enterprise-wide, and a line telling the viewer why they have access: incident commander, team invoked

6. Auditor and compliance: “Can I prove it?”

Auditors read everything and change nothing: the audit trail, approvals, access changes, export logs and the evidence behind each figure. Evidence packs collect the register, responses, approvals and gaps in one download, so an audit request does not turn into a two-week project.

Everyone else keeps their own part current too. Through the Employee Kiosk, staff maintain their own profile, contact details and whereabouts, so a roll call reaches the right people.

What holds it together

  • One set of records. Every role reads the same BIA, plans, risks and evidence. Nothing is copied into a second spreadsheet for a different audience.
  • Roles come from teams. Access is granted to teams, not to individuals, and duties that should be kept apart, such as approving your own work, are checked.
  • Same totals for everyone. Totals count every record, so no two people see different numbers. Only the detail depends on what a viewer may open; the rest shows as Restricted, never as zero.
  • Unknown stays unknown. A record with no evidence shows as unproven for every role, from the department to the board.

The six roles at a glance: One program, six questions (PDF, 9 pages)

See it with the roles in your own program: Book a demo

Data Residency vs One Resilience Program: The Federated Answer

A resilience program is judged as a whole. Boards and regulators ask whether critical services can stay within tolerance, wherever they run. But the data behind that answer is increasingly tied to where it was created. A multinational must keep employee and incident data in-country. A group of near-independent businesses wants each to run its own program. A public agency runs many independent operations on the same HR, IT and facilities. Each case pulls the data apart while the program still has to hold together.

Why one central database stops working

The default answer is one platform, one database, with access rules that keep each unit to its own records. That works well inside one jurisdiction. It stops working when:

  • The law decides where data lives. Privacy, residency and sovereign-hosting rules can require personal and operational data to stay in the country. Access rules do not change where data is stored.
  • Some sites cannot be connected. Defence, government and critical-infrastructure sites often run air-gapped. A central platform cannot reach them, and they cannot reach it.
  • Units need real independence. A business being prepared for sale, or a government operation with its own mandate, needs its own platform, not a filtered view of someone else’s.

The opposite answer, a separate tool per country or unit, keeps the data local but loses the program. Each site defines “critical” differently, shared services are recorded several times, and the enterprise view becomes a spreadsheet assembled by hand.

What federation means

Federation sits between the two. Each jurisdiction, line of business or operation runs its own complete platform, hosted where its data must live. One platform acts as the hub. Records fall into three classes:

  • Global: the method and the standards (risk scales, impact categories, BIA time buckets, the control library, plan templates) and the shared entities everyone depends on (enterprise applications, shared services such as HR and payroll, global vendors). These are owned once at the hub and flow down as read-only copies.
  • Local: processes, sites, BIA, plans, risks, exercises and incidents. These stay in the local platform. An agreed summary flows up.
  • Private: people, contacts, evidence files and restricted risks. These never leave the local platform at all.

The enterprise view is built from the summaries: every critical service’s recovery objectives, its dependency on shared services, its last exercise result, across every site, without the hub ever holding another country’s personal data.

Four design choices that decide whether it works

  1. One owner per record. Every shared record has exactly one owning platform; everyone else holds a read-only copy. Nothing is ever merged, so two sites can never disagree about the same record. Change requests go to the owner.
  2. Summaries, filtered at the source. Each summary field carries a data class, and the local platform decides which classes may leave before anything is sent. That is where data-protection officers can sign off the flow.
  3. Standards first. An enterprise heat map only means something if every site uses the same scales. Sharing the standards is the first step of any federation, and the cheapest.
  4. Signed bundles, customer-held keys. Updates move as signed, encrypted bundles in numbered order, so they work across an air gap as well as over a network. The organization, not the vendor, holds the keys.

Incidents need one more thing: a small, fast status channel. When a shared entity such as an enterprise ERP fails, its owner raises the incident once and every dependent site sees its own impact immediately, while the full incident record stays local.

Questions to ask before choosing a platform

  • Where does each kind of record physically live: people, sites, incidents, evidence, restricted records?
  • What exactly leaves a jurisdiction, and who can switch a field off?
  • Who can edit a shared record, and what happens when two sites disagree?
  • Who holds the signing and encryption keys?
  • How do updates and incident status reach a site with no live connection?
  • How does a business unit move to another site or platform after a reorganization?

eRMA and federation

eRMA, the resilience platform from eBRP Solutions, runs on the customer’s own infrastructure, including air-gapped networks, and takes in outside data as signed bundles rather than live connections. Access is granted through teams, sensitive risks can be restricted to the people who should see them, and a complete export pack carries a whole program from one platform to another. These are the foundations the federated model builds on.

The full model is set out in the whitepaper Federated resilience: one program, many jurisdictions (PDF).

Planning a multi-jurisdiction program? Talk to eBRP Solutions.

What Should a Business Continuity Platform Actually Solve?

Ask eRMA

Budgeting season is when many business continuity teams decide whether to renew, replace or buy a platform. The feature lists vendors send are long and look alike. A better starting point is the opposite question: which business problems should the platform make smaller every year? Across banking, insurance, healthcare, energy and the public sector, in North America and the Gulf, the same six come up again and again.

1. The picture is out of date the day it’s approved

The annual business impact analysis (BIA) is the classic example. Questionnaires go out in spring, the results are approved in autumn, and by then teams have reorganized, applications have moved and vendors have changed. The program produces a document, not a current picture.

What good looks like: ISO/TS 22317 treats the BIA as an activity you keep up, not a one-off project. The people who own the data keep it current, a change triggers a review rather than a date on the calendar, and nobody is asked the same question twice. Where processes share a parent, answers are inherited rather than collected again.

Ask a vendor: how does a single change reach the BIA without starting a new cycle?

2. Nobody can see what depends on what

Dependencies usually live in spreadsheets, one per team. Each is right on its own terms, and together they miss the application, site or vendor that quietly supports three critical services at once. That gap tends to show up during an incident, which is the worst time to find it.

What good looks like: one dependency model that connects processes, applications, services, locations, vendors and people. The model should flag a gap on its own, for example an upstream application whose recovery time is longer than the process that needs it can tolerate.

3. Recovery times are stated, not proven

A recovery time objective (RTO) written in a BIA is a target. Until an exercise shows the organization can meet it, it remains an assumption. Many exercise reports are narratives, which makes it hard to say which RTOs were tested and which were met.

What good looks like: ISO 22301 (clause 8.5) asks for an exercise program that validates continuity arrangements. In practice that means recording results per process, application or service against its RTO, and keeping that evidence where an auditor or regulator can follow it.

4. Plans exist, but not in an order anyone can run

Large programs have dozens of plans. Each may be sound on its own, but on the day, someone has to know which runs first, which waits for another, and how long the whole chain takes. That order often lives in one experienced person’s head.

What good looks like: plans sequenced by their dependencies and recovery times, so the total recovery path is visible and can be checked against the business’s tolerance before an incident, not during one.

5. Risk and continuity live in separate worlds

The risk register sits in one tool, the BIA in another and controls in a third. The same vendor can be rated three different ways, and nobody notices until an audit. Regulators increasingly look at operational risk and resilience together, for example OSFI Guideline E-21 in Canada and the US agencies’ sound practices paper on operational resilience.

What good looks like: risk assessments that use the same processes, applications, locations and vendors as the BIA, so a risk rating and an impact rating describe the same thing.

6. Leaders can’t get a straight answer quickly

Executives receive long reports or dashboards that are green because nothing has been measured. Neither helps a leader decide in the minute they have.

What good looks like: each role sees first what needs its attention. Missing data shows as “Unknown”, never as healthy. Data a viewer may not see shows as “Restricted”, never as zero, so a total is never quietly wrong.

Where eRMA fits

eRMA, the resilience platform from eBRP Solutions, was designed around these six problems. All of the following are available today:

  • Business impact analysis with group BIA and inheritance, and live progress for each campaign. The Employee Kiosk lets staff keep their own details current.
  • Impact Map and Dependency Designer: one connected model of processes, applications, services, locations, vendors and people, with RTO gaps shown where they occur.
  • Exercise: rehearse a scenario and record results for each entity against its RTO, with the evidence kept.
  • Plan Sequencer: one bar per plan, chained finish-to-start, so the recovery path can be seen and adjusted.
  • Risk Assessment on the same entities as the BIA, with ERM and Compliance (GRC) available as optional add-on modules.
  • Role-based workspaces that lead with what needs attention, where “Unknown” is never green and “Restricted” is never zero.

See it: Business impact analysis →

See it: Dependency Designer and Impact Map →

See it: Plan Sequencer →

Three questions to ask any vendor

  1. Show one change, live. Add a new application that supports a critical service, and show how it reaches the BIA, the plans and the dashboard, without slides.
  2. Show a proven RTO. Where does the platform show that a recovery time was exercised and met, not only stated?
  3. Show the first ten seconds. What does a senior leader see on opening the platform, and what does it show when data is missing?

A platform earns its budget when these six problems get smaller every year.

Download this as a one-page Brief: What should a business continuity platform solve? (PDF)

Download the eRMA brochure · Join the next live showcase