ADOGRC Hardware/Software Requirements
ADOGRC is based on ADONIS, therefore all Hardware and Software Requirements of ADONIS. There are some cases, however, where ADOGRC requires increased resources depending on the size of your environment and the number of active users. Please check the ADONIS Hardware and Software Requirements carefully. In the next section you will find a list of items where ADOGRC deviates from the standard ADONIS requirements.
Increased Minimal Requirements
This section contains a list where ADOGRC requires increased resources compared to the ADONIS minimal requirements. This is the minimum for any ADOGRC deployment, depending on the size of your environment and number of users, you may have to adapt these values accordingly.
Database System
Microsoft SQL Server: Due to restrictions on functionality, size and performance, the Microsoft SQL Server Express Editions are not supported by ADOGRC.
Hard Disk Capacity: ADOGRC supports the upload of external documents, e.g. protocols for control executions. These documents are stored in the database and will therefore increase the required hard disk space for the database files.
Web Client Screen Resolution
As ADOGRC offers a large number dashboards presenting a lot of vital information (e.g. listing all risks of an organisation and their most important characteristics) and charts, a screen resolution of 1920 x 1080 or higher is recommended.
Application and Web Server Containers
ADOGRC Scheduler: The ADOGRC Scheduler component performs recurring operational tasks in the background and requires an additional aworker process resulting in a minimum of 2 aworker processes. This increases the RAM and CPU requirements as described below.
| Component | CPUs/Cores | Memory |
| Web Server Container | 4 CPUs or more |
|
| Application Server Container |
|
|
Sizing Estimation
The basis for a confident definition of resources needed, is to estimate the size of the entire deployment, which includes objects, external documents and users, as accurately as possible. This helps ensure optimal performance for your users during their activities in the software. If you need guidance on how to estimate sizing, contact your BOC consultant.
The three main factors for size estimation are:
- Number of ADOGRC objects
- Schedule of activities with these objects
- Number of concurrently active users
Number of ADOGRC Objects
In this section you will find some guidance on size estimation and examples for customer scenarios of different organizational maturity.
ADOGRC offers a large number of object types, depending on the GRC domain and your license. To get a feeling for how many objects will be generated in your environment, let's look at an example:
In Risk Management you document all Risks you need to manage to comply with regulations or pass certifications. Each of these Risks will typically have one or more Controls to manage those Risks. Control Tests are used to check if the Controls are valid and the information is up-to-date. Control Executions will then document when and how those Controls were executed. By looking at those relations, you get a first rough estimate of the number of objects necessary to meet your needs.
The next step is to estimate how often these objects change. To be compliant, each change in an object will create a new version reflecting the change. Depending on the number of changes, the number of objects can increase considerably over the years.
Schedule of Activities
In our example, Control Tests have to be executed regularly to validate Controls and Control Executions are then performing the actual Control for the assigned Risk. Usually those activities are on a schedule, like once a month or once a quarter.
This has a large impact on performance considerations because activity in the software may be not be distributed evenly across a month. For example, if 50% of the Control Executions need to be performed on the 1st of each month, then all users performing these executions will be working at the same time on a large number of objects. Such spikes in activity must be matched with the appropriate hardware sizing because in exactly these situations you need the best performance for your users.
Number of Concurrent Users
As we have seen, the schedule of activities has a direct relation to the number of concurrently active users but there are usually also users working consistently with objects outside a specific schedule. These users have to be added to the sizing considerations because the generate the base load on the system.
Organizational Maturity and Size
Based on the considerations outlined above, you can compare your estimates with the two examples in this section to determine the projected size of your deployment. The ADOGRC standard deployment will fit into the hardware requirements above while the ADOGRC deployment with high organizational maturity will need a significant increase in resources.
ADOGRC Standard Deployment
This example describes a typical ADOGRC deployment which should fit most customer environments.
| Number of ADOGRC objects | between 4,000 and 8,000 ADOGRC objects |
| Number of users participating in ADOGRC workflows |
|
| System load due to common workflow deadlines | Schedules for assessments and reviews are distributed across multiple phases throughout the year to avoid excessive load spikes on certain dates |
| External documents uploaded | uploaded documents do not exceed 5 GB total |
ADOGRC Deployment with High Organizational Maturity
This example is for deployments with a high organizational maturity, appropriate for customers who have to meet high levels of compliance requirements and use ADOGRC to work in multiple GRC domains which is typical for large companies with lots of active users.
| Number of ADOGRC objects | between 15,000 and 20,000 ADOGRC objects |
| Number of users participating in ADOGRC workflows |
|
| System load due to common workflow deadlines | Deadlines for assessments and reviews are distributed across multiple phases throughout the year to avoid excessive load spikes on certain dates |
| External documents uploaded | uploaded documents exceeding 10 GB total |