Server Error
Server Error
Server Error
Server Error
Server Error

Implementation Roadmap

Learn the process you need to follow to learn how eramba is used and implementated

  • Episodes10
  • Duration18m 9s
  • LanguagesEN
Episode 2

Phases

We explain in a little more detail the importance of each phase

Introduction

In this episode, we will briefly describe each implementation phase goal, remember for every use case you choose you will need to go through all phases.

The screenshot below shows a typical customer implementation where colours are used to highlight in which phase they are and how much is left to complete it. We use this system to track down progress when delivering our Implementation Workshops (contact support@eramba.org for quotes).

Install or SaaS

In this phase, you will install eramba or use our SaaS service which makes your life a lot easier since all is up and running and updated for you. The Installation phase includes basic configurations such as email servers, authentication connectors, time zones, Etc.

On-Prem installations are rarely the choice for our enterprise customers because of the complications and costs associated with installing, operating, and updating the software. You can read this post where we explain the ROI for SaaS.

Access Management

Often ignored, this phase is critical. You will define who has access to what. This involves defining groups, accounts and access lists.

Customisation

Every module in the scope of your "Use Case" needs to be customized, with forms and filters to start with but some modules will require further settings (Risk Management, Incident, Etc).

Data Identification & Entry

You will create items (Risks, Controls, etc.) one by one, using CSVs or REST APIs.

The pre-requisite to complete this phase is that of course, you have data to input in the system. Some organisations have this in spreadsheets and some organisations prefer to start from scratch.

Reporting

You will create basic filters that will automatically hit your inbox to remind you about Risks, Policies, Controls, Etc. You will also adjust the landing dashboard and create custom graphical reports.

Automation

You will start using notifications to send automated reports and reminders to people around the organization to collect feedback: Policy Reviews, Control Evidence, Etc.

If you are into automation you will also setup REST APIs to integrate eramba with other systems.

Roll Out

You will let people around the organization know that eramba is up and running and notifications will be sent to them when something is needed. You might want to give them a brief training on what they need to do when emails arrive.