This information in this topic is intended to be a generic guide to use as a starting point in the planning of your ATS CM4D implementation of CM4D Server, CM4D Peruse, CM4D Upload Portal and support services. While the CM4D modules interact with one another and are mostly interdependent, if installed on separate machines then requirements might be considered individually. In cases where your system implementation combines one or more server configurations on the same machine, the minimum specifications for the combined system types must be met.

To jump to individual topics, use the links below:

CM4D System Requirements

CM4D Peruse System Requirements

CM4D Upload Portal System Requirements

General Recommendations

Some important things to note that pertain to CM4D systems in general:

  • Database Management System - All installations of ATS CM4D rely on an external database to store the quality data. The DBMS can be local to the CM4D installation or on a centralized server with access for clients within a network.
  • Windows System Updates - Windows System Updates should be kept up to date to ensure the computer has any critical Root Certificate updates that might be required by digitally signed software.
  • Supported Operating Systems Disclaimer - ATS customer support of a Windows Operating System ends when Microsoft stops supporting the version.
  • Server Memory Limits - CM4D Server is pre-configured with a single DataSmith Batch process and two CM4D worker processes for CM4D Scheduler. In addition, the CM4D Web application requires its own dedicated CM4D worker processes. The number of CM4D Web worker processes should be based on the number of users who are simultaneously generating reports on demand. Utilizing current Virtualization technology, you could monitor peak memory demand over time to better tune available memory to prevent page swapping. Most Virtualization technology also makes used of shared or balloon memory, which allows the host to dynamically adjust available memory based on load demand. Visit the Microsoft library for information on Memory Limits for Windows Releases.
  • Installer Prerequisites - Some installers have prerequisites which must be installed prior to the install of the software. By default, any prerequisites not present or require updates are downloaded automatically when needed during installation. Downloading and installing these prerequisites manually is only required if you plan to run the installer on a machine that does not have an internet connection.
  • CPUs - 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. CPU specifications may change in proportion to the CM4D Server load. ATS recommends Virtualized Server environments whenever possible.
  • Hard Drive - 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.
  • Minimum Resolution - CM4D and DataSmith dialogs require a minimum screen resolution of 1280x1024. For wide screens, a minimum resolution of 1920x1080 is recommended.
  • Web Browser Support - CM4D applications support most up-to-date web browsers - Chrome, Edge, Firefox. Internet Explorer is outdated and therefore not supported.
  • Network Speed - Any CM4D implementations in a network with centralized databases and/or distributed services require sufficient internet/network speeds for transferring data and communication between ATS products/services. For CM4D Peruse clients, internet speed impacts the loading/rendering of the 3D model because the 3D model is streamed to the client and rendered on the client machine.

ATS Product Compatibility

Refer to the table below to check which versions of ATS Products are compatible with your version of CM4D:

  CM4D 25.2 CM4D 25.3
ATS Security & Configuration 1.9 1.10+
ATS Licensing 4.0+ 4.0+
ATS Reporting 1.4+ 1.4+
ATS Bus 3.2+ 3.2+

ATS License Servers

ATS CM4D v25 and higher requires ATS Licensing Server 4.0+. This is a plugin application that must be installed on the same machine as ATS Security and Configuration Manager. By default, the port used for the Licensing service is 44335.

CM4D Configuration Plugin

Refer to the ATS Security help documentation for system requirements.

CM4D Configuration is a plugin for ATS Security and Configuration Manager which administrates the configuration and settings for several CM4D applications and/or services, including databases, Peruse/Upload Portal configuration, DataSmith Batch jobs and EventSmith subscriptions. This plugin is installed by uploading the plugin package (ATS.CM4DPlugin.zip) in ATS Security and Configuration Manager. 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.

See the topic CM4D Configuration Plugin Overview for more information.

CM4D Recommendations

Below is an overall summary of the requirements and recommendations for various types of CM4D installations.

  Minimum Recommended
Servers Windows Server 2019 Standard Windows Server 2022 Standard
Clients Windows 10 Pro Windows 11 Pro
DBMS Microsoft SQL Server 2016 Standard Microsoft SQL Server 2022 Standard
Server CPU   help-circle 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. 4-6 Cores 2Ghz 4-6 Cores 3Ghz
Client CPU i5 Dual or Quad Core i7 Dual or Quad Core
Server RAM 12Gb-16Gb 24Gb+
Client RAM 8Gb 16Gb
Server HDD   help-circle SSDs are always recommended for the best performance. 150Gb 150Gb+
Client HDD 1-6Gb (installation only) 10Gb+
Client GPU   help-circle A discreet GPU is preferred. 32Mb (OpenGL) 128Mb (OpenGL)
PDF Printer eDocPrinter PDF Pro 6.98.6405 ATS CM4D Printer (from ATS)
Web Browser Chrome, Edge, Firefox Chrome
Network   1Gbps

See the topic CM4D System Requirements for the full requirements and recommendations.

CM4D Peruse Recommendations

Below is an overall summary of the requirements and recommendations for various types of CM4D Peruse installations. CM4D Peruse runs as a web application accessed via the network/internet, so clients only need a web browser to access the software installed on a network server or host machine via the internet. 3D models are rendered in the client systems' web browser by the HOOPS Web Viewer component in CM4D Peruse.

Minimum Recommended
Servers Windows Server 2019 Standard Windows Server 2022 Standard
Clients Windows 10 Pro Windows 11 Pro
Server CPU   help-circle 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)
Server RAM 16Gb 32Gb+
Server HDD   help-circle SSDs are always recommended for the best performance. 256Gb 256Gb+
Client GPU   help-circle This requirement depends on 3D model complexity. Up-to-date graphics card  
Web Browser Chrome, Edge, Firefox (must support WebGL; can be tested here)
Network   1 Gbps

See the topic CM4D Peruse System Requirements for the full requirements and recommendations.

CM4D Upload Portal Recommendations

Below is an overall summary of the requirements and recommendations for various types of CM4D Upload Portal installations.

  Minimum Recommended
Servers Windows Server 2019 Standard, Linux Windows Server 2022 Standard
Clients Windows, iOS, mobile devices (with compatible 3rd party software)
Server CPU   help-circle 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. 1 Core 1.4Ghz (64-bit) 2 Cores 2Ghz (64-bit)
Server RAM 4Gb 8Gb+
Server HDD   help-circle SSDs are always recommended for the best performance. 10Gb 10Gb+
Web Browser Chrome, Firefox, Edge, Safari Chrome

See the topic CM4D Upload Portal System Requirements for the full requirements and recommendations.

CM4D File Servers

The ATS CM4D applications require a shared location to store and access related files such as:

  • CM4D Report Templates - *.4dc
  • DataSmith translators - *.4DataSmith
  • Model Images (2D/3D) - *.wrl, *.jpg, etc.
  • RAW Incoming Data Inboxes
  • Rendered Reports - *.PDF

These files are used or produced by CM4D Server and CM4D Clients. For example, if an End User running a CM4D Client does not have access to the file share storing the *.4DC files, they will not be able to view or edit the report templates. If that CM4D report template includes any part models, the user will also need to have at least read access to the folder where the image file is stored.

Since CM4D is Windows based, this location is represented as a normal Microsoft Windows SMB File Share. For most CM4D Customers, the SMB share used for CM4D files usually resides directly on the CM4D Automation server or on another preexisting SMB file server (such as existing file shares used by used by Quality Department).

Firewall Port Reference

This port is used by the ATS Configuration Manager web application and corresponding Windows service. The web address used by clients to connect to the web application includes the port number.
This port is used by CM4D to communicate between the ATS Licensing Server and clients. When the client PC runs a CM4D application, it sends a request to the application server (where the ATS Licensing Server is installed) to check if there is an available license in the database via ATS Licensing Manager on TCP port 8001. If any available license exists, the application server sends the information back to the client to run related application. If TCP 8001 is not open, clients will not be able to run any CM4D application in their local environment.
This port is used by CM4D clients to communicate with the Licensing plugin in the ATS Configuration Manager. This is part of the URL which defines the Web API for the ATS Licensing plugin.
This port is used by the ATS Security Manager web application and corresponding Windows service.
This port is used by the CM4D API service, which supports the web applications CM4D Peruse and Upload Portal and their associated Windows services.
This port is used by web server to run the CM4D Peruse web application and corresponding Windows service. The web address used by clients to connect to the web application includes the port number.
This port is used by the Peruse API service, which supports the Peruse web application and corresponding Windows service. This service runs behind the scenes on the host server and is not visible to connecting clients.
This port is used by web server to run the CM4D Upload Portal web application and corresponding Windows service. The web address used by clients to connect to the web application includes the port number.
This port is used by CM4D to reach the Scheduler Manager Services (which is running on the application server) from client PCs. Clients that have privileges for Scheduler Manager can control scheduled reports and alarms to print PDFs or trigger alarm conditions on report templates. In addition, there are two services on the application server (ATS CM4D Scheduler and ATS CM4D Launcher) that are running for scheduled report processing. If TCP 36057 is not open, a client will not able to reach the Scheduler Manager to configure or manage unless Scheduler Manager is located on the local server.
This port is used by the DataSmith Batch Proxy service, which supports the CM4D Upload Portal web application and corresponding Windows service. This service runs behind the scenes on the host server and is not visible to connecting clients.
This port is used by the DataSmith Translator service, which supports the CM4D Upload Portal web application and corresponding Windows service. This service runs behind the scenes on the host server and is not visible to connecting clients.
This is the default port for Windows for File Sharing. In computer networking, Server Message Block (SMB), one version of which was also known as Common Internet File System (CIFS), operates as an application-layer network protocol mainly used for providing shared access to files, printers, and serial ports and miscellaneous communications between nodes on a network. CM4D needs a shared folder on the network to store all CM4D managed report templates, translators, Inboxes, etc. Clients should be able to reach this shared folder to modify and manage report templates and translators. DataSmith Batch Manager is using this shared folder to locate defined Inbox folders and to process automatically data files via DataSmith. If TCP 445 is not open, clients cannot work on any CM4D Files or update any DataSmithBatch Settings.
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.
This is the default port for Microsoft SQL Server database management system (MSSQL) server. As CM4D uses MS SQL Server to locate CM4D Site, CM4D and Results databases, this port must be open for clients to access data via CM4D applications and services.
[Optional] Install a third-party virus scanner for scanning uploaded data files in CM4D Upload Portal.

Hardware Reference

Software Reference

Can we improve this topic? Click   Send Feedback in the upper right of the screen to share your comments!