Dashboards Dictionary

The material in this document is for informational purposes only. This guide assumes that the most recent version of Rampiva Automate is in use unless otherwise noted in the prerequisites. The products it describes are subject to change without prior notice, due to the manufacturer’s continuous development program. Rampiva makes no representations or warranties with respect to this document or with respect to the products described herein. Rampiva shall not be liable for any damages, losses, costs or expenses, direct, indirect or incidental, consequential or special, arising out of, or related to the use of this material or the products described herein.

Introduction

This document describes the data model used in the Rampiva Baseline Introductory Dashboards. This is a subset of the fields available in Rampiva Automate.

The last section of this document is a guide on how to interpret the calculations from the growth scenario from the dashboards.

Tables and Variables

Organizations

The Organizations table tracks information about the user, entered when registering for a Rampiva Baseline license.

In this table, Baseline automatically collects:

  • organizationId, a unique alphanumeric value generated by Rampiva

  • organizatioName, the organization name the user enters when registering for a Rampiva Baseline license

  • organizationType, generated by Rampiva to indicate users of the Rampiva Baseline product or users of a full Rampiva Automate product

  • organizationIsActive, a binary field indicating whether the organization is active in the Rampiva Portal

Licenses

The Licenses table tracks information about the Rampiva License .

In this table, Baseline automatically collects:

  • licenseId, a unique alphanumeric value generated by Rampiva

  • organizationId, defined above

  • licenseName, a value derived from the other properties of the license

  • licenseEnvironment, the environment for which the license was issued

  • licenseIsActive, a binary field indicating whether the license is active in the Rampiva Portal

Users

The Users table tracks information about the individual user who is performing tasks in Nuix.

In this table, Baseline automatically collects:

  • userId, a unique alphanumeric value generated by Rampiva Baseline for each user

  • userTimeZone, automatically generated by Rampiva based on the machine details of the individual user

 

Rampiva Dashboards also support collecting additional information about the users, when using a Rampiva Automate license. In Baseline this field is anonymized by replacing its value with an automatically generated one containing the prefix of the userID:

  • userName, the individual name associated with each user

 

The information in this table is based on the user’s login credentials. Organizations that use generic user credentials, or whose users share login credentials, should take this into account when analyzing user-related data.

Nuix Cases

The NuixCases table tracks individual Nuix Case databases as unique objects. These databases are created in Nuix Workstation or with the Nuix Engine.

In this table, Baseline automatically collects:

  • nuixCaseID, a unique alphanumeric value generated by Nuix when the Case is created

  • nuixCaseVersion, the version of the Nuix Engine required to open the Nuix Case

  • nuixCaseCreationDate, the date and time when the Nuix Case was created

  • nuixCaseLastModifiedDate, the date and time when the Nuix Case database was last changed

 

Rampiva Dashboards also support collecting additional information about the Cases, when using a Rampiva Automate License. In Baseline these fields are anonymized by replacing their values with automatically generated ones containing the prefix of the nuixCaseID:

  • nuixCaseLocation, the file path where the Nuix Case is stored

  • nuixCaseName, the user-supplied name of the Nuix Case

 

Finally, the PowerBI model in Baseline also calculates:

  • nuixCaseCreationHour, the hour of the day when the Nuix Case was created, on a scale of midnight (0) to 11PM (23)

  • nuixCaseLastModifiedHour, the hour of the day when the Nuix Case was last modified, on a scale of midnight (0) to 11PM (23)

  • nuixCaseAge (d), the number of days between the day the Nuix Case was created and the current day

  • nuixCaseActive (d), the number of days between the day the Nuix Case was created and the day it was last modified

  • nuixCaseInactive (d), the number of days between the day the Nuix Case was last modified and the current day

Tranches

The Tranches table tracks activity before Export operations as unique objects. A Nuix Case may contain multiple Tranches, but a Tranche cannot relate to more than one Nuix Case. A Tranche may include activity across multiple Sessions, and a Session may include activity that impacts multiple Tranches. For example, if a user adds evidence from three sources, deduplicates the items, applies a date filter and then exports the remaining items, that is a single Tranche. If that same user then runs another add evidence operation, deduplicates that material against the original set, applies a date filter and exports just the unique items from the new source, that is a second Tranche, but all of the activity occurred within a single Session.

In this table, Baseline automatically collects:

  • nuixCaseId, defined above

  • trancheId, a unique alphanumeric value for each Tranche

  • tranchePosition, the order of each Tranche relative to the other Tranches in the Case

  • trancheIsFirst, a binary field indicating the first Tranche in the Case

  • trancheIsLast, a binary field indicating the last Tranche in the Case to date

  • trancheStartDate, the date and time the work associated with the Tranche started

  • trancheEndDate, the date and time the work associated with the Tranche ended

  • trancheEndOperationType, the last operation in the Tranche, typically an Export operation, or another operation if subsequent work was performed in the Case after the last Export

  • volumeLoaded, the sum of the audited size of data loaded during the Tranche

  • volumeOcred, the sum of the audited size of the data OCRed during the Tranche

  • volumeExported, the sum of the audited size of data export during the Tranche, using Legal Export, Native Export or Other Export

 

 The PowerBI model in Baseline also calculates:

  • trancheStartHour, the hour of the day when the tranche was started, on a scale of midnight (0) to 11PM (23)

  • trancheDuration (s), the time in seconds between the either creation of the Case and the first Export operation, or the last Export operation and following Export operation indicating the end of this tranche

  • trancheVolume (GB), the sum of data processed during the tranche, calculated as the sum of volumeLoaded, volumeOcred, and volumeExported, converted to gigabytes

  • trancheThroughput (GB/h), which measures the speed at which data is processed during the tranche

Sessions

The Sessions table tracks individual Sessions as unique objects. A Session in Nuix is the collection of activity that occurs between the Nuix Case being opened and the Nuix Case being closed. A Nuix Case may have multiple Sessions associated with it, but a Session can only be associated with a single Nuix Case. A Tranche may measure activity the occurs over multiple Sessions, but activity from one Session may also impact different Tranches in the same Case.

In this table, Baseline automatically collects:

  • sessionId, a unique alphanumeric value for each Session

  • nuixLicenseType, the class of the Nuix Workers used in the Session, for example enterprise-workstation or enterprise-arx

  • nuixVersion, the version of the Nuix Engine under which the activity was performed

  • productName, the name of the product that recorded the activity, for example, Nuix, Rampiva Engine, or Rampiva Baseline

  • productVersion, the version of the product that recorded the activity

  • sessionStartDate, the date and time the Session started, which corresponds to the date and time the Nuix Workers used for Session were checked out from the Nuix license pool or dongle

  • sessionEndDate, the date and time the Session ended, which corresponds to the date and time the Nuix Workers used for Session were returned to the Nuix license pool or dongle

  • nuixWorkers, the number of Nuix Workers (also called Nuix Cores) that were checked out from the license pool or dongle to run the specific Session

  • sessionIdleTimeBeforeExport, a field that sums up the duration of time before an export that the session was idle, in seconds. Exports of all types are considered. Idle time is defined as any time the Nuix Workers are not processing data and there is no user-driven activity through Nuix Workstation. In addition to this field, the Session table includes additional fields which record the idle time before the specific Legal Export, Native Export and Other Export operations:

    • sessionIdleTimeBeforeLegalExport

    • sessionIdleTimeBeforeNativeExport

    • sessionIdleTimeBeforeExportExport

  • sessionIdleTimeAfterExport, a field that sums up the duration of time after an export that the Session was idle, in seconds. Exports of all types are considered. In addition to this field, the Session table includes additional fields which record the idle time after the specific Legal Export, Native Export and Other Export operations:

    • sessionIdleTimeAfterLegalExport

    • sessionIdleTimeAfterNativeExport

    • sessionIdleTimeAfterExportExport

  • volumeLoaded, the sum of the audited size of the data that was loaded in Nuix the Session, in bytes

  • volumeOcred, the sum of the audited size of the data that was OCRed in the Session

  • volumeExported, the sum of the audited size of the data that was exported in the Session

 

The PowerBI model in Baseline also calculates:

  • sessionDuration (s), the duration of the Session, in seconds

  • sessionIdleTime (s), the sum of the idle periods in the Session, in seconds

  • sessionActiveTime (s), the sum of the active periods in the Session, in seconds. This corresponds to the time during which Nuix Workers were actively processing data or the user was engaged in activity through Nuix Workstation

  • sessionNuixWorkerTime (h), the duration that each Nuix Worker is checked out from the licensing pool or dongle during the Session, in hours. This is calculated as the product of Session duration and the number of Workers used in the Session

  • sessionNuixWorkerIdleTime (h), the duration that each Nuix Worker is idle during the Session, in hours

  • sessionNuixWorkerActiveTime (h), the duration that each Nuix Worker is active during the Session, in hours

  • sessionVolumeProcessed (GB), the sum of all data processed during the Session, in gigabytes, calculated as the sum of sessionLoaded, sessionOcred, and sessionExported

  • sessionThroghput (GB/h), the speed at which volume is processed during the session. The model calculates similar throughput values for each measure of Session duration:

    • sessionActiveThroughput (GB/h)

    • sessionNuixWorkerThroughput (GB/h)

    • sessionNuixWorkerActiveThroughput (GB/h)

Operations

The Operations table tracks individual Nuix Operation as unique objects. An Operation in Nuix is any activity that uses a Nuix Worker, such as Add Evidence (i.e., for loading data in the Nuix Case), OCR, Legal Export, Native Export and Other Export, or user activity in Workstation, recorded as Other Non-Worker. Cases, Tranches and Session are all likely to have multiple Operations associated with them, but an Operation can only be associated with a single Case, Tranche and/or Session. Operations are the smallest unit of Nuix activity that can be measured as having a start and an end time.

In this table, Baseline automatically collects:

  • operationId, a unique alphanumeric value for each Operation

  • sessionId, defined above

  • operationExecutionPosition, a field indicating the order in which each operation is executed, relative to the other operations in the Job. In Rampiva Baseline, Operation positions are recorded as 2, 4, 6, …, to indicate that this information was extracted from the Nuix Case history, and that there might be other Operations performed but which did not generate any event in the Case history and as such are not reported on

  • operationStartDate, the time and date when the Operation started

  • operationEndDate, the time and date when the Operation ended

  • operationPercentageOnShift, a field measuring the share of operation's total duration that was performed a standard shift. For the purposes of Rampiva Baseline calculations, a standard shift starts at 8AM and ends at 6PM, under the user’s local time zone. Note: an Operation that runs through the night and into the next shift will have the on-shift clock start again the following morning

  • operationType, a field recording the general type of activity executed, such as LOAD, OCR, LEGAL_EXPORT, NATIVE_EXPORT, OTHER_EXPORT and OTHER_NON_WORKER

  • operationName, a field indicating the name of the Operation. In Rampiva Baseline, the name and type of Operations are directly related. For example, a LOAD Operation will always be recorded with the name Add Evidence. In Rampiva Automate, this field records the name of the Operation in the Workflow, and for a LOAD Operation, the name could be Add Evidence, Reload Items, or Scan Evidence Repositories.

  • itemsCount, the count of the total number of items in scope of a Worker-based Operation, for example, the total number of items loaded, OCRed or exported

  • physicalCount, the total number of items in scope of a Worker-based Operation which are considered physical in Nuix

  • physicalSize, the sum of the physical size of items in scope of a Worker-based Operation

  • auditCount, the total number of items in scope of a Worker-based Operation which are considered audited in Nuix

  • auditSize, the sum of the audited size of items in scope of a Worker-based Operation

  • nuixWorkers, the number of Nuix Workers (also called Nuix Cores) that were checked out from the license pool or dongle to run the specific Operation

 

The PowerBI model in Baseline also calculates:

  • operationDuration (s), the duration in seconds between the Operation start and end time

  • operationStartHour, the hour of the day when the Operation was started, on a scale of midnight (0) to 11PM (23)

  • operationDurationOnShift (s), the length of time in seconds when the operation is running during a standard shift. For the purposes of Rampiva Baseline calculations, a standard shift starts at 8AM and ends at 6PM

  • operationDurationOffShift (s), the length of time in seconds when the operation is running outside of a standard shift

  • operationNuixWorkerTime (h), the sum of the duration that each Nuix Worker is checked out from the licensing pool or dongle during the Operation. This is calculated as the product of Operation duration and the number of Nuix Workers used. By definition, this duration corresponds to active time

 

The PowerBI model also infers the staff work required to support the operation:

  • Inferred Staff Work - Manual (h), the sum of the Operation durations, with the exception of Operations requiring Nuix Workers for which only the first 5 minutes are considered. This captures an estimate of the human time required to set up and run these activities in a manual processing environment, based on client input and operational experience

  • Est. Staff Work - Rampiva (h), estimated to be 5 minutes per Add Evidence Operation, which is the average time required to schedule a Job in Rampiva Automate

The staff work calculated in hours corresponds to the direct time that can be linked to human activity performed in Nuix. This metric does not include activities such as staging/archival of data, reporting, or project management, and other related work which is performed outside of Nuix Cases.

Measures

In addition to the individual tables, the PowerBI model also generates a number of specific aggregate measures used in visuals and which are stored in the 00_DescriptiveStatistics table. The meaning of most of these measures are readily understandable from their names, but users are encouraged to inquire through the Baseline User Community for more detail.

However, there is a specific Measure that should be defined:

  • Efficiency, the sum of the durations for each Nuix Worker where the Worker was active divided by the sum of the durations for each Nuix Worker were the Worker was idle. This Measure captures the amount of time that Nuix Workers are actually processing data relative to the amount of time that they are checked out from the license pool.

Scenario 1: 5-Year Growth

The goal of these calculations is to help Baseline users apply the observed utilization and performance patterns to a specific question: what resources will be needed in 5 years if demand for data processing activity aligns with estimated year-to-year growth?

These calculations present the additional Nuix Workers and headcount required by the user's current operating model, and those required if the user adopts Rampiva. The values are presented for educational purposes, and should not be considered recommendations, quotes, commitments, or advice.

Input Data

The fields in the Enter Scenario Information section are designed to be filled out by the user:

  • Current Nuix Utilization: an estimate of how utilization of the Nuix environment, and implicitly, how much more capacity can the environment support to maintain the same service level.

  • Nuix Spend: the cost of the Nuix licenses

  • Nuix Worker Count: the number of Nuix Workers licensed

  • Staff Spend: the cost associated with the staff that is running Nuix projects

  • Forecast Annual Growth: the estimated year-over-year growth of projects with similar requirements as the ones from the previous year

Last 365 Days

The values in this section are a summary of the amount data processed in the last 365 days, as well as calculations of available and used capacity:

  • Cases: the number of Nuix Cases created

  • Sessions: the number of Sessions ran

  • Volume (GB): the volume of data processed, in gigabytes

  • Total Nuix Capacity (h): the total available Nuix capacity, in hours, calculated from the Used Nuix Capacity and the used-provided estimated Current Nuix Utilization

  • Used Nuix Capacity (h): the used Nuix capacity, in hours, calculated as the duration that each Nuix Worker was used

  • Used Staff Capacity (h): The inferred duration that can be linked to human activity performed in Nuix (see the Operations table). This metric does not include activities such as stating/archival of data, reporting, or project management, and other related work which is performed outside of Nuix Cases.

Year 5 Forecast

The values in this section are a calculation of the amount of data that is expected to be processed in year 5, given the year-over-year forecasted growth, as well as the the required additional capacity to support this volume in year 5, in a manual environment as well as in an environment with Rampiva Automate:

  • Required Additional Nuix Capacity:

    • Manual: the increase in Nuix capacity, proportional to the increase of data, required above the available capacity

    • Rampiva: the increase in Nuix capacity, calculated similarly to the Manual value, and taking into account an average observed Efficiency of 98.5% in Rampiva Automate environments

  • Required Additional Staff Capacity:

    • Manual: the increase in Staff capacity, proportional to the increase of data

    • Rampiva: the increase in Staff capacity, taking into account the lower amount of manual work required in a Rampiva environment. If the total amount of manual work required is determine to be lowed than the current value, the calculation is performed under the assumption that the Staff capacity can be re-allocated to other projects or business-lines, which corresponds to cost savings associated with the processing activities

  • Required Rampiva Capacity: the cost of the Rampiva license

  • Total Cost: the total cost in year 5 required to support the growth

  • Rampiva Savings: the savings realized by using Rampiva Automate in year 5