Hardware & Software Requirements

This article contains information about Reveal software specifications.


The goal of this document is to provide an overview of the minimum hardware and system requirements necessary to deploy a Reveal 11 solution.

This document is intended to be a relatively easy read, with any detailed technical specifications being listed in the specific Appendices or externally referenced documentation. Stated differently, this document will describe what needs to be deployed, along with how-many or how-large, but will not go into extensive technical details on any of the Reveal modules.

Software Products

The combined solution is comprised of the following two modules which work together to provide a cohesive eDiscovery solution:

  • Reveal 11

    Legal document Review solution to allow inspection and output of responsive documents with key capabilities of Assignments, Advanced Searching, Production, Redaction, etc., integrated with modern analytics designed to provide a tactical advantage for lawyers, investigators and knowledge workers who need insight within a communication-based repository. Incorporates data visualization and machine learning that augments the intelligence of subject matter experts, enabling them to dramatically increase the speed to valuable and actionable insights. 

  • Reveal Processing -

    Enterprise-level rapid response solution, which allows an organization to easily identify, reduce, analyze, and export collections of Electronically Stored Information (ESI) in hours as opposed to the traditional Processing model which can be days or potentially weeks. Supports over 100 languages and data export in any required format, including Australian protocols.

Components

Before diving into architectural recommendations, a high-level review of the various components involved in the Reveal solution may be helpful.

Component

Usage Description

Reveal Database Server

Microsoft SQL Server used as the RDBMS repository for Windows-based Reveal modules. Needs to be MSSQL 2016 SP2 or later, either Standard or Enterprise Edition

Reveal Web Server

Microsoft IIS Web Server used by the Reveal Review and Reveal AI modules. Must be version IIS V10 or later

Network File Share

Standard Windows (SMB-based) file share used by all three Windows-based Reveal modules. Can be an existing file share within the environment or a new file share. Synergies exist for Reveal Processing and Reveal Review using the same network share, but the Reveal AI network share can be separated from the other Reveal share if desired.

Processing Discovery Manager

Thick client used by Reveal Processing to create Projects, Import/Export Data, and centrally manage Reveal Processing Agents.

Processing Discovery Agents

Background workers used by Reveal Processing to perform batch related activities such as Import, Export, OCR, etc. This component requires the use of Microsoft Outlook 64-bit.

Review Manager (aka OpsCenter)

Thick client used by Reveal Review to create Projects, Load Data, Index Data, and perform other administrative duties.

Review Application Services

Background Windows services used by Reveal Review for performing a variety of batch related activities such as Assignments, Bulk Tagging, Production, Production Export, etc.

Elasticsearch Nodes

Background Elasticsearch services used by Reveal Review and Processing for supporting searches, but also for storing the content of documents. Review 10.3 uses Elasticsearch 6.x; Review 10.4 uses Elasticsearch 7.x.

Reveal AI Service

Background Windows service used by Reveal AI for Modeling, Job Scheduling and Vector creation activities.

Reveal AI Processing / POS Tagger Services

Background Windows services used by Reveal AI for ingesting new data into the Reveal AI system.

Brainspace Application

Linux-based web server used by Brainspace solution for web end-users and API calls. Must be Linux version 7.6 or later.

Brainspace Analytics

Linux-based server used by Brainspace solution for ingesting new documents. Must be Linux version 7.6 or later.

Brainspace On-Demand Analytics

Linux-based server used by Brainspace solution for on-going (after ingestion) analytics activities. Must be Linux version 7.6 or later.

Deployment - Small Solution

ITEM

SPECIFICATIONS

CPU

  • 2x Intel® Xeon® Gold 6238R 2.2G, 28C/56T, 10.4GT/s, 38.5M Cache, Turbo, HT (125W) DDR4-2933 or similar AMD CPU

Memory

  • 12x 64GB RDIMM, 3200MT/s, Dual Rank

Hard Drive

  • Minimum 12x 1.92TB SSD SAS Read Intensive 12Gbps 512 2.5in Hot-plug AG Drive, minimum 1 Drive Write Per Day (DWPD)

  • PERC H730P or H740P RAID Controller

  • C4, RAID 5 for 3 or more HDDs or SSDs (Matching Type/Speed/Capacity)

Communication

  • 4 x Embedded Broadcom (or compatible), Gigabit Ethernet NICS with TOE or 10Gbps+ connectivity

CD/DVD

  • DVD+/-RW, SATA, Internal

Software

  • Windows Server 2019, Standard Edition

  • Microsoft SQL Server 2019 Standard, minimum 4 CORE, OEM, NFI, ENGLISH

  • VMware ESXi or other virtual hypervisor

Power

  • Standard + Redundant 870 Watt hot-plug power supply

  • Auto-switching universal 110/220 Volts

Chassis

  • PowerEdge R740xd(2) Server or comparable HP, Lenovo, etc

  • Height: 46.63cm (18.4")

  • Length: 73.18cm (28.9") (overall including bezel)

  • Width: 21.79cm (8.6")

  • Weight (maximum config): 35.3kg (78.0lb)

Regulatory

  • FCC (U.S. only) Class A, ICES (Canada) Class A, CE Mark (EN 55022 Class A, EN55024, EN61000-3-2, EN61000-3-3), VCCI (Japan) Class A, BSMI (Taiwan) Class A, C-Tick (Australia/New Zealand) Class A, SABS (South Africa) Class A, CCC (China) Class A, MIC (Korea) Class A, UL 60950-1, CAN/CSA C22.2 No. 60950-1, EN 60950-1, IEC 60950-1

Environmental

  • Operating Temperature: 10º C to 35º C (50º F to 95º F)

  • Storage Temperature: -40º C to 65º C (-40º F to 149º F)

Power Requirements

  • Power Supplies are plugged into either PDU (Datacenter / Colocation) or UPS (Office)
  • Data Center Requirements:
    • Rackspace Needed: 2 Rack Units

    • Estimated Power Draw: 482W, 1645 BTU/HR

  • For Network Connectivity, the following is needed:

    • iDRAC: 1 x RJ45 1Gbe Network Switch Port

    • Host Network LAN Interface: 2 x RJ45 1Gbe or 10Gbe Network Switch Ports

Deployment - Medium Solution

ITEM

SPECIFICATIONS

CPU

  • 2x Intel® Xeon® Gold 6238R 2.2G, 28C/56T, 10.4GT/s, 38.5M Cache, Turbo, HT (125W) DDR4-2933 or similar AMD CPU

Memory

  • Minimum 12x 64GB RDIMM, 3200MT/s, Dual Rank

Hard Drive

  • Minimum 8x 3.84TB SSD SAS Read Intensive 12Gbps 512e 2.5in Hot-Plug AG Drive, minimum 1 Drive Write Per Day (DWPD)

  • PERC H730P or H740P RAID Controller

  • C4, RAID 5 for 3 or more HDDs or SSDs (Matching Type/Speed/Capacity)

Communication

  • 4 x Embedded Broadcom (or compatible), Gigabit Ethernet NICS with TOE or 10Gbps+ connectivity

CD/DVD

  • DVD+/-RW, SATA, Internal

Software

  • Windows Server 2019, Standard Edition

  • Microsoft SQL Server 2019 Standard, minimum 16 CORE, OEM, NFI, ENGLISH

  • VMware ESXi or other virtual hypervisor

Power

  • Standard + Redundant 870 Watt hot-plug power supply

  • Auto-switching universal 110/220 Volts

Chassis

  • PowerEdge R740xd(2) Server or comparable HP, Lenovo, etc

  • Height: 46.63cm (18.4")

  • Length: 73.18cm (28.9") (overall including bezel)

  • Width: 21.79cm (8.6")

  • Weight (maximum config): 35.3kg (78.0lb)

Regulatory

  • FCC (U.S. only) Class A, ICES (Canada) Class A, CE Mark (EN 55022 Class A, EN55024, EN61000-3-2, EN61000-3-3), VCCI (Japan) Class A, BSMI (Taiwan) Class A, C-Tick (Australia/New Zealand) Class A, SABS (South Africa) Class A, CCC (China) Class A, MIC (Korea) Class A, UL 60950-1, CAN/CSA C22.2 No. 60950-1, EN 60950-1, IEC 60950-1

Environmental

  • Operating Temperature: 10º C to 35º C (50º F to 95º F)

  • Storage Temperature: -40º C to 65º C (-40º F to 149º F)

Quantity

  • Minimum of 2 Enterprise Dell Servers, as specified above

Power Requirements

  • Power Supplies are plugged into either PDU (Datacenter / Colocation) or UPS (Office)
  • Data Center Requirements:
    • Rackspace Needed: 4+ Rack Units

    • Estimated Power Draw Per Server: 482W, 1645 BTU/HR

  • For Network Connectivity, the following is needed Per Unit:

    • iDRAC: 1 x RJ45 1Gbe Network Switch Port

    • Host Network LAN Interface: 2 x RJ45 1Gbe or 10Gbe Network Switch Ports

Other Deployment considerations regardless of size:

  • Reveal will provide Reveal software and licensing. Client is responsible for Microsoft and other environmental licensing.

  • Reveal can assist with remote deployment if remote control is provided through Zoom or other screen sharing technology.

  • The following is additional software to be installed to support the Reveal Platform:

    • Microsoft .NET Framwork 4.7.1

    • Office 2016 64-bit with Outlook default mail profile

    • Lotus Notes 9.0.1 or later with default mail profile

    • SQL Server Management Studio Express (Optional)

    • Security – Antivirus

  • Apply your corporate policy to create backups for file, VMs and SQL.

  • Reveal recommends that if Dell HW is leveraged, Dell Pro Support is purchased to assist with any hardware issues.

As an alternate approach to self-provisioning a mobile solution, Reveal IT Partner George Jon offers an appliance or Kit solution that can be shipped and deployed onsite. White Glove Service is an optional feature for delivery and installation. This service involves a GJ Engineer personally delivering the Kit to client site for installation, testing and admin/backend training anywhere in the world. The cost for this service is $2,500 USD / day plus travel expenses for the Single Server.

If a Kit requires shipping outside of the United States, GJ will need to know both the country where the device is purchased and final destination for shipping/tax purposes and to provide an accurate delivery timeline.

Reveal Cloud AI (Optional)

The Cloud AI platform of Reveal is essentially a middleware layer that handles communication with AWS for cloud analytic functions. At time of writing we support integration with AWS analytics only.

Qty

OS

Purpose

CPU

RAM

Storage

Additional Comments

1

Linux 7.6 or later

Orchestrator

Transcription

Archive Wrk

8

32GB

2TB

This server should have as much free space as the largest image labeling plus the largest transcription job you intend to run times 2.

  • An AWS account should be provisioned.
  • The Cloud AI platform makes use of the following AWS services:
    • Rekognition (image labelling)

    • Comprehend (language detection in transcription)

    • Translate

    • Transcribe

  • You must verify that these services exist in the AWS region you're setting up in.

  • The Cloud AI system uses an S3 bucket for staging purposes. This is necessary as AWS services require data to be stored locally in S3 for analysis to be performed.

Frequently Asked Questions

  1. Question: Are these the only options available?

    Answer: No, not at all. The architectures described in this document illustrate minimum guidelines for likely deployment scenarios, but discussions with Reveal technicians for what-if scenarios are definitely encouraged as every organization's eDiscovery needs will vary greatly based on document complexity, number of graphics versus text in various documents, and the desired workflow within your eDiscovery operations.

  2. Question: Can Virtual or Physical system be used?

    Answer: Yes, but since eDiscovery needs rarely involve static usage, deployment onto Virtual Infrastructure is strongly recommended both for short-term spikes as well as ongoing growth of usage.

  3. Question: Some scenarios list throughput estimates, are those guaranteed results?

    Answer: Unfortunately, no. While those estimates are derived based on real-world usage of the Reveal-Brainspace solutions, numerous factors exist (document complexity, storage speed, etc.) which will impact overall throughput. Also, timeframe expectations vary between organizations. In most scenarios, throughput can be increased with either more robust systems or greater quantities of some components. Please feel free to discuss possible areas to improve throughput for certain activities with Reveal-Brainspace technicians during initial planning or deployment as well as over the long-run.

  4. Question: Is Microsoft Outlook required on each Reveal Processing Agent?

    Answer: Yes, as of now, this is a technical requirement.

  5. Question: Is Microsoft Office required on each Reveal Processing Discovery Manager system?

    Answer: No, this is not a technical requirement, but many users find that having MSOffice installed on these systems can assist with QC and troubleshooting activities.

  6. Question: Do all components involved with the Reveal solution have to remain online 24x7?

    Answer: No, in many scenarios, idle systems can be taken offline when not actively in use. An example of this would include Processing Agents when no Processing is actively being performed.

  7. Question: Is Elasticsearch only used for Review searching?

    Answer: No, the Reveal Review product stores the actual text from documents in Elasticsearch. Elasticsearch needs to be online for almost all Reviewing activities.

  8. Question: What integrations exist between the Reveal products?

    Answer: Reveal Processing can directly export to Reveal Review although the "Uploader" feature in the Reveal Review web front-end is only available currently in the Reveal SaaS offering.

  9. Question: Both the Processing Agent and the Elasticsearch components stress the use of high-speed storage. Is this required?

    Answer: No, but it is strongly recommended. Both of these components are very I/O intensive, so having local, high-speed storage can greatly reduce the duration of many activities.

  10. Question: Some of the resource requirements are significant; can we start smaller than what is listed and expand later as activity increases?

    Answer: Yes, but keep in mind that adjustments in allocated resources may not be deemed necessary until in-progress activities are underway, often with a pending deadline, and adjustments to some resources (typically CPU and Memory) may require an outage which can be difficult to schedule if large batch jobs are executing. The minimum resource allocations described in this document target eventual usage scenarios, but feel free to start smaller, and adjust upward when necessary, always keeping a close eye on resource consumption and live throughput.

  11. Question: The documented Reveal solution appears to be heavily reliant upon Microsoft products; is this a requirement?

    Answer: Yes. While some components such as Elasticsearch and the SMB Network Share can be deployed on other Operating Systems, the basis of the Reveal solution makes specific use of functionality within the Microsoft stack: IIS, MSSQL and .NET/C#.

  12. Question: The documented Brainspace solution appears to be heavily reliant upon Linux operating systems; is this a requirement?

    Answer: Yes. The Brainspace solution is deployed solely on Linux systems.

  13. Question: Can SAN or NAS storage technologies be utilized in the solution?

    Answer: Yes, these are very common. Just keep in mind that during high-load scenarios (Importing, Indexing, Production, etc.), the speed of storage will be a critical factor in the duration of those activities.

  14. Question: Why are so many Reveal Processing Agents recommended?

    Answer: Currently, the Reveal Processing Agent software can perform various tasks, but not at the same time. Multiple Processing Agents help ensure that no activities will be queued waiting for another activity to complete.

  15. Question: Storage requirements for MSSQL system are high, is this required?

    Answer: Best Practices are to utilize full-recovery model in the MSSQL environment. Storage allocations can be trimmed slightly if using simple-recovery model.

  16. Question: Do the Discovery Manager and Review Manager thick clients have to reside on their own systems?

    Answer: No. Typically, customers will deploy Discovery Manager on its own System, with Review Manager either being deployed on the same system as Discovery Manager or one of the Review Application Servers.

  17. Question: How should backups be configured for Reveal Solutions?

    Answer: Best Practices leverage differing backup strategies for each functional area. For example, SQL data should be in Full-Recovery mode and leverage Native SQL backups, while Elasticsearch should leverage built in backup/restore functionality through Curator. Brainspace, file servers, and virtual machines would leverage a form of Virtualization aware backup products.

  18. Question: How many external IP addresses are necessary if we need external reviewers?

    Answer: If using a proxy or load balancer one IP would be necessary. However, Additional IP addresses may be necessary for multiple web servers or publishing multiple services such as Review, Brainspace, and keycloak authentication services.

 

Last Updated 11/09/2022