Medium Deployment
Qty | OS | Purpose | CPU | RAM | Storage | Additional Comments |
|---|---|---|---|---|---|---|
1 | Windows Server 2016 or later | Web Server (Review and AI) | 8 | 24GB | 200GB | IIS 10 or later. |
1 | Windows Server 2016 or later | Database Server (Review) | 16 | 128GB | 2.5TB | MSSQL 2016 or later, Standard or Enterprise Edition. |
1 | Windows Server 2016 or later | Database Server (processing / AI) | 16 | 128GB | 2.5TB | MSSQL 2016 or later, Standard or Enterprise Edition. |
1 | Windows Server or Unix/Linux with SMB/CIFS | Shared File Server (all solutions) | 4 | 16GB | 25TB | Can be an existing or new system with SMB storage. |
2 | Windows 10x64 or Windows Server 2016 or later | Processing Desktop Managers | 4 | 4GB | 150GB | |
5 | Windows 10 x64 or Windows Server 2016 or later | Processing Agents | 8 | 8GB | 150GB | Fast, Local Storage highly recommended. |
2 | Windows Server 2016 or later | Review Application Servers | 16 | 64GB | 200GB | OpsCenter thick client will be deployed on one of the Application Servers. |
3 | Windows Server 2016 or later (or Linux/Unix) | ElasticSearch Data Nodes | 4 | 16GB | 2.5TB | Fast, Local Storage highly recommended. 3 Data Nodes, 3 Master Nodes, Coordinator node on one non-Master node. |
1 | Windows Server 2016 or later | Reveal AI Server + Caching Server | 4 | 64GB | 200GB | |
2 | Windows Server 2016 or later | Reveal AI Processing Server | 8 | 64GB | 200GB | |
1 | Linux 7.6 or later | Brainspace Web Server | 36 | 464GB | 8TB | |
1 | Linux 7.6 or later | Brainspace Build Server | 28 | 224GB | 6TB | |
1 | Linux 7.6 or later | Brainspace ODA Server | 26 | 184GB | 8TB |
 |
All components should reside on same subnet to minimize latency.
Optional AI NexBERT functionality is presumed to use Microsoft Azure Machine Learning service. On-premise deployments of NexBERT are supported.
Please keep in mind technical restrictions (Memory, CPU Cores, etc.) for Microsoft SQL Server editions when considering adjustments to the above recommendations; the Reveal solutions can each use separate MSSQL servers if that is beneficial from a budgetary standpoint.
Note
As servers are added, architecture and services change, causing sourcing on some servers to decrease from one deployment to another.