This topic includes basic hardware and software recommendations for CM4D products version 25.3 or higher. The specifications outlined here are only intended to be a generic guide to use as a starting point in the planning of your implementation. Your actual system needs for this application installation can vary based on factors, including number of users or activity.
The following hardware/software recommendations apply to systems running ATS CM4D Peruse servers or Peruse clients.
Refer to the General Recommendations section of the topic System Requirements for more generalized prerequisites and other relevant information.
Peruse Servers
This application may be run as a stand-alone instance or alongside other ATS applications. The CM4D Configuration plugin administrates several CM4D applications and/or services, including CM4D Peruse. Components managed by the CM4D Configuration plugin have requirements that must be met when determining where a specific application and/or service should be installed. However, for the purposes of this topic, the assumption is that CM4D Peruse is installed on an independent server. CM4D Peruse requires an installation of ATS CM4D Server (with the Results database enabled) and CM4D Results Services, which may be on different server from the Peruse application and services.
- Security - It is strongly recommended to publish the services via a reverse proxy or an application gateway. The public endpoint must be secured by TLS.
- SSL Certificate and Key Files - The HOOPS Communicator Server, which is installed along with CM4D Peruse, requires secure certificates. However, HOOPS is a third-party SDK which cannot utilize the Windows Certificate store and therefore requires a separate Certificate File and Private Key File. See the topic SSL Certificates for more details.
- Non-Windows Operating Systems - Linux systems may be used, but ATS does not provide any installers for a Linux environment. ATS does, however, provide Docker support for some of the CM4D Services. See the topic Docker Installations for details.
- Cloud Services - The current architecture does not support a cloud offering towards an on-premises CM4D installation as it would require a connection from our SaaS systems to the on-premises systems.
- VM/Container - CM4D Peruse and its supporting ATS services can be installed on a Virtual Machine or in a container environment.
Peruse Application & Services
The CM4D Peruse server requires the following applications/services:
- Peruse Application with Peruse Services - The CM4D Peruse service must be able to access the CM4D API service.
- HOOPS Communication Server - Installed with CM4D Peruse, HOOPS Communicator is the third-party software facilitating the streaming of 3D model data from CM4D to the HOOPS Web Viewer integrated in CM4D Peruse for client-side rendering.
See the topic HOOPS Communicator Server for more details.
Supporting ATS Applications & Services
The following additional applications/services are required (on the same computer or other network server) for support or configuration of the CM4D Peruse server installation:
- ATS Security and Configuration Manager – Based on OAuth2; requires the necessary access control. Local user credentials are supported but Security Manager can also use external login providers like Azure Active Directory Services. Logins can also be secured via captcha. Minimum version required: ATS Security 1.10+.
- ATS Licensing Plugin (v4.0+)
- CM4D Configuration Plugin
- CM4D API Service - The Peruse installer is dependent on a specific version of the CM4D API. Therefore during the installation when you enter the location of the CM4D API, it checks the version of the API to confirm it is compatible. The CM4D API service is installed using the CM4D Configuration installer.
- CM4D Site and Results Databases - Peruse relies on a connection to the CM4D Site and Results databases.
- Results Services – Peruse requires these services to populate the Results database with data from the CM4D databases.
Hardware & Software
The following recommendations apply to servers hosting the CM4D Peruse application and HOOPS Communication Server, whether it is physical hardware or a virtual machine (VM). For production use, this machine should meet or exceed the minimum hardware recommendations.
| Minimum | Recommended | |
| OS | Windows Server 2019 Standard | Windows Server 2022 Standard |
| CPU The number of threads should correlate to the number of worker processes you intend to have running on a single machine. A large number of processes without sufficient threads can bottleneck your entire system. | 2 Cores 2.5Ghz (64-bit) | 4 Cores 2.5Ghz (64-bit) |
| RAM | 16Gb | 32Gb+ |
| HDD Disk sizing requirements can vary based on amount of CM4D data and files stored on a system. Servers should allow for long term growth. Your actual sizing will be based on the volume of measurement data you plan to store and analyze with CM4D. SSDs are always recommended for the best performance. | 256Gb | 256Gb+ |
Default Ports
The following ports are the default settings used in the three Upload Portal installers:
- Peruse – 4000
- Peruse API – 2000
These ports can be set to a custom port during or after the installation. For a list of default ports used by CM4D-related applications, including Upload Portal, please refer to the topic CM4D Default Ports.
Peruse Clients
A Peruse Client connects remotely (via web browser or mobile device) to the CM4D Peruse application hosted on a server. This configuration assumes ATS software products are installed remotely, so local system specifications are minimal. However, because Peruse Clients perform the rendering of all 3D models, there are some GPU requirements that must be met.
Internet speed impacts the loading/rendering of the 3D model because the model is streamed to the client and rendered on the client machine. Server-side rendering (not available) would require very expensive server hardware.
Hardware & Software
The following recommendations apply to clients connecting to the CM4D Peruse application via Web Browser.
| Supported | |
| OS | Windows, Linux |
| GPU This requirement depends on 3D model complexity. | Up-to-date graphics card (e.g., GeForce RTX 40 series) |
| Web Browser | Chrome, Edge, Firefox (must support WebGL; can be tested here) |
| Network | 1 Gbps |
See here for information on the HOOPS Communicator supported platforms and hardware recommendations.
HOOPS Graphics Support Information
Peruse/HOOPS client-side rendering requires:
- Sufficiently high network bandwidth to serve 3D model data in an acceptable amount of time
- Enough computational power and GPU capability to properly render 3D models
- A web browser [that] supports WebGL (this can be tested here).
Here are some highlights from the TechSoft website that are particularly relevant to CM4D Peruse clients:
| "Because WebGL relies on the client hardware to perform all rendering, any device running the HWV must be sufficient for rendering interactive 3D graphics." |
| "Performance is highly dependent on model complexity. We recommend using NVIDIA Geforce GTX or NVIDIA GRID GPUs." |
Refer to the following links from TechSoft 3D for more detailed and up-to-date information:
Can we improve this topic? Click Send Feedback in the upper right of the screen to share your comments!