Operational resilience software that proves what recovers.
eRMA maps every important service to what it depends on, measures whether it can recover in time, and keeps the evidence. Every module answers one question a decision-maker asks, and all of them read the same records.
What operational resilience software should change
The usual method is an annual survey, a plan in a document, an exercise written up in slides and a certificate on the wall. It proves effort, not recovery. eRMA starts from the services the business can't afford to lose and works backwards:
- The service is the spine. Every process, application, location, supplier and team is linked to the services it supports, so an outage can be traced before it happens.
- Recovery is measured, not assumed. Targets come from the business impact analysis; plans are scheduled against them; exercises record what each entity actually achieved.
- Unknown is never green. Missing data shows as a gap, and restricted records are counted, never left out.
- Compliance is an output. The evidence a regulator asks for comes from the records the program keeps every day, not from a separate project.
One platform, one version of the truth
MyWorkspace
What needs attention right now?
One landing page per role. Work, readiness and incidents ranked by what matters most.
- Own, Govern and Operate views, shown only when the role has them
- Overdue and upcoming reviews, surveys and exercises in one list
- Resilience readiness by processes, applications and locations
- An incident banner that follows the user across every page
Business Impact Analysis
How fast must it be back?
ISO-aligned analysis rates harm by impact category over time, then sets MTPD, RTO, RPO and criticality.
- Run it on an entity or on its group, and let approved values inherit down
- Survey editor, self-assign and release, live completion progress
- Weighted scoring with configurable bands
- Approved results feed every other module
Dependency Mapping, Impact Map & Scenarios
What fails if this goes down?
Draw dependencies on a canvas, trace any outage to everything it reaches, and build scenarios from them.
- Dependency Designer: links drawn, reviewed and saved together
- Impact map flags the dependencies that would break a recovery target
- Scenario builder shows what fails if a site or system is lost
- Scenarios drive both exercises and incident activation
Risk Assessment
What threatens the target?
A single scored register replaces scattered risk lists.
- Likelihood x impact matrix with inherent and residual ratings
- Owners, review dates, controls and treatment actions
- Threats linked to scenarios, so unprotected high risks show as gaps
- Risks roll up from applications and services
Strategy Development
The entity is down. What are the options?
A ranked shortlist of recovery options for any failed dependency: location, application, vendor, upstream process or staff.
- Each option shows restore speed, capacity, how long it can be sustained, cost and needs
- What-if view and coverage view expose entities with no viable option
- Options can point to the plan that carries them out
Plans, Templates & Plan Gantt
Can the plan meet the target?
Plans built from one standard per plan kind, with procedures, owners and durations, scheduled against the recovery time they must meet.
- Plan templates give every plan of a kind the same structure
- Critical path and earliest starts calculated from predecessors
- Compare plan duration to the RTO of every covered entity
- Print and PDF in one layout, checklists included
Incident Management
Run the response in one place.
Open, assess, activate, run and close, with the whole picture visible to the people who need it.
- Plan activation, pause and resume, roll call with need-help and location
- Task tracking, issues, messages and a communications log
- Decisions asked, made and recorded
- Service validation and recovery against target
- Post-incident review with follow-up actions
Exercises & Recovery Proof
Did it actually work?
Every exercise is tied to a scenario and run through the incident engine. Every entity gets its own result.
- Record actual recovery time and status per entity against RTO
- Notifications for upcoming runs, results due and overdue actions
- Excel report and export for audit
- Results become recovery evidence alongside real incidents
Map
What is inside the footprint?
Weather, flood, fire and unrest have a footprint. The map shows which locations, people and vendors sit inside it.
- Locations, vendors and employees at their work location (never home)
- Spread and concentration: where critical work sits in one place
- Hands results to incidents, exercises and notifications
Executive Dashboards
Can we keep delivering?
Resilience on one page, read from the same live records the program maintains.
- A scorecard for the board, the organization chart as a heat map
- Plan quality and readiness checked plan by plan
- Same totals for everyone; detail only for those allowed to see it
- Board packs printed dated, scoped and marked
GRC & ERM add-on
Are we compliant, and is enterprise risk in appetite?
An optional add-on that brings obligations, controls and enterprise risk onto the same records.
- Obligations mapped to the services, processes and controls that meet them
- Risk and control self-assessment and an assurance map
- Enterprise risk with appetite, key risk indicators and treatment
Data Management
Get data in. Get data out. Trust the result.
Import and export in one administrator area, so the records behind the program stay current.
- Downloadable templates with a field guide for every column
- Pre-check, dry run and typed confirmation before any commit
- Full export pack that round-trips cleanly back in
Built for regulated enterprises
Operational resilience rules ask the same questions in different words: which services matter, what they depend on, how long they can be down, whether recovery has been tested, and what happened in the last incident. eRMA answers them from one set of records, so the evidence for DORA, OCC and FFIEC guidance, OSFI Guideline E-21, federal continuity of operations (COOP) and ISO 22301 comes from the program itself.
Questions buyers ask
What is operational resilience software?
Operational resilience software helps an organization keep its important services running through a disruption. It maps each service to the people, processes, technology, facilities and suppliers it depends on, sets how fast each must be back, plans and exercises the recovery, and keeps the evidence that recovery works.
How is it different from backup or disaster recovery software?
Backup and disaster recovery tools restore data and systems. Operational resilience software works one level up: it shows which business services depend on those systems, what an outage would reach, who responds, and whether recovery meets its target. The two work together.
Which regulations does eRMA help with?
eRMA produces the evidence that operational resilience rules ask for: important services and their dependencies, impact tolerances and recovery objectives, tested recovery, incident records and third-party exposure. That evidence supports programs under rules such as DORA, OCC and FFIEC guidance, OSFI Guideline E-21, federal continuity of operations (COOP) requirements and ISO 22301.
How can I see eRMA working?
Join a live eRMA showcase on Microsoft Teams, or book a demo built around one of your own services.
The next disruption is already scheduled. The response should be too.
See eRMA run against real resilience data. Live on Teams or in a demo built around your service. No slideware.