During an incident the plan sits in one place, the tasks in another and the status in a call. The record gets rebuilt afterwards from memory.

How it works

  1. 01

    Open and assess

    Record the incident, add the processes, applications, servers and locations involved, and invoke the right teams.

  2. 02

    Activate with a preview

    See the tasks, the ones ready at once and the expected recovery before anything is created.

  3. 03

    Work the tasks

    Pick, hold, skip and complete. Successors become ready and the schedule moves with them.

What you get

  • Assess records one at a time, or bring a whole scenario in with one confirmation.
  • Activation previews tasks, milestones and expected recovery first. A plan nobody has worked can be deactivated.
  • Raise an issue and escalate it. The task halts until a supervisor resolves it.
  • The incident monitor counts plans, tasks, operators and issues, and refreshes while the incident is open.
  • Only administrators, incident commanders and members of the teams involved can see an incident.
33 of 33

task statuses rebuilt by eRMA v10 matched what the previous eBRP Suite stored.

Verified on a test incident.

Replay it step by step.

Slide to any recorded moment and see how many tasks were complete, open, on hold or not yet activated. Each plan is drawn on its own schedule bar.

Illustrative interface with demo data.
See eRMA v10 live in 20 minutes.Book a demo