This topic includes the system requirements for all CM4D modules, both desktop and web applications. While the CM4D modules interact with one another and are mostly interdependent, if installed on separate machines then requirements might be considered individually.
To view individual topics, use the links below:
CM4D Upload Portal System Requirements
Some important things to note that pertain to all CM4D systems:
- 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.
- 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.
General Recommendations
| Minimum | Recommended | |
| Servers | Windows Server 2019 Standard | Windows Server 2022 Standard |
| Clients | Windows 10 Pro | Windows 11 Pro |
| Databases | Microsoft SQL Server 2016 Standard | Microsoft SQL Server 2022 Standard |
| Server 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. | 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 SSDs are always recommended for the best performance. | 150GB | 150GB+ |
| Client HDD | 1-6GB (installation only) | 10GB+ |
ATS CM4D Requirements
This topic includes the hardware and software requirements and recommendations for the basic configurations of CM4D v25 or higher. These specifications outlined here are intended to be a generic guide to use as a starting point in the planning of your ATS CM4D implementation.
The following software and hardware requirements must be met for the Server that will be running a CM4D Server installation.
Some CM4D configurations may combine one or more Server types on the same machine. In this case the specifications for all Server role requirements must be met by the server that is running everything.
Typical use: Large networks with one or more servers hosting centralized databases and running the Site Automation services for multiple CM4D Clients.
CM4D Database Server
The Database Server hosts the Database Management System (i.e., SQL Server) for the CM4D databases. The DBMS can be local to the CM4D installation or on a centralized server within the network.
All installations of ATS CM4D rely on an external database to store the quality data.
| Operating Systems |
|
| CPU |
|
CPU specifications may change in proportion to the CM4D Server load. ATS recommends Virtualized Server environments whenever possible.
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. |
| RAM |
|
| 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. |
| Database Management System |
The CM4D Results Database requires the SQL Server Instance Feature - Full-Text and Semantic Extractions for Search. See the topic Results Database for the DBA for details. Firewall ports for SQL Server: TCP 1433-1434 (default) CM4D Upload Portal, ATS Security and Configuration Manager and ATS Licensing require individual databases. These databases can be hosted on the same database server used for CM4D. |
CM4D Application Server
The Application Server typically includes the CM4D Server desktop applications and automation services.
| Operating Systems |
|
| CPU |
|
CPU specifications may change in proportion to the CM4D Server load. ATS recommends Virtualized Server environments whenever possible.
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. |
| RAM |
|
| HDD |
|
| Network |
|
| Third Party Software |
|
Web Server
The Web Server hosts the following web applications: CM4D Peruse, CM4D Upload Portal or CM4D Web. It may also host the administrative tool, ATS Security and Configuration Manager and its supporting plugins (such as ATS Licensing Server and CM4D Configuration).
| Operating Systems |
|
| CPU |
|
CPU specifications may change in proportion to the CM4D Server load. ATS recommends Virtualized Server environments whenever possible.
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. |
| RAM |
|
| HDD |
|
| Network |
|
| Web Browser |
Internet Explorer is outdated and therefore not supported. |
| Windows Features |
|
ATS License Server
ATS CM4D v25 and higher requires ATS Licensing Server 4.0. or higher. 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.
Refer to the online documentation for ATS Licensing Server for the latest requirements.
CM4D File Server
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, CM4DWeb, and any 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).
| Operating Systems |
|
| CPU |
|
CPU specifications may change in proportion to the CM4D Server load. ATS recommends Virtualized Server environments whenever possible.
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. |
| RAM |
|
| 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. |
| Network |
|
CM4D Clients
The following software and hardware requirements must be met for the machine that will be running a CM4D Client installation. There are two primary ways the Client version of CM4D might be implemented:
- CM4D Client - A local desktop CM4D installation that connects to a centralized database and utilizes components from an Application Server or other shared network resources used by CM4D.
- CM4D Workstation - A self-contained instance of the Client install that has ATS CM4D, ATS Licensing, and the SQL Databases all on the same machine.
CM4D Clients can support a local SQL installation. However, ATS recommends a centralized SQL Instance whenever possible.
CM4D Client
This section includes the requirements for CM4D Clients that will have the CM4D installation, ATS Licensing, and SQL Databases on the same machine.
Typical use: Machines on the plant floor running CM4D Interactive or Workcell, connecting to the central server for its database and license. This could also be used for a CM4D Scheduler Client that is utilized by the server to automatically generate reports.
| Operating Systems |
|
| GPU |
|
A discrete GPU is preferred.
CM4D and DataSmith dialogs require a minimum screen resolution of 1280x1024. For wide screens, a minimum resolution of 1920x1080 is recommended. |
CM4D Workstation
This section includes the requirements for CM4D Workstation clients that will have the CM4D installation, ATS Licensing, and SQL Databases on the same workstation (machine).
Typical use: This configuration is usually the Node-locked CM4D Classic Developer and DataSmith licenses and is used by report template developers and DataSmith translator developers. Generally, this is used when by organizations that do not have the Site Automation package or does not use CM4D widely throughout a large network to need shared databases.
Other use: CM4D Interactive or CM4D Workcell systems.
| Operating Systems |
|
| CPU |
|
CPU specifications may change in proportion to the CM4D Server load. ATS recommends Virtualized Server environments whenever possible.
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. |
| RAM |
|
| GPU |
|
A discrete GPU is preferred.
CM4D and DataSmith dialogs require a minimum screen resolution of 1280x1024. For wide screens, a minimum resolution of 1920x1080 is recommended. |
| HDD |
|
Disk sizing requirements can vary based on amount of CM4D data and files stored on a system. 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. |
| Database Management System |
The CM4D Results Database requires the SQL Server Instance Feature - Full-Text and Semantic Extractions for Search. See the topic Results Database for the DBA for details. |
| Licensing |
|
Web Client
A Web Client refers to a user connecting remotely (via web browser or mobile device) to CM4D Peruse, CM4D Upload Portal or CM4D Web applications hosted on a Web Server. This configuration does not require any installed ATS software products.
Typical use: Multiple users throughout the network, those with limited knowledge of CM4D, but need on-demand access to reports.
| Operating Systems |
|
| Third Party Software |
|
ATS CM4D Upload Portal Requirements
This topic includes the general system requirements and recommendations for a stand-alone installation of CM4D Upload Portal. These recommendations are generic, so your actual system needs for this application installation can vary based on factors including number of users or activity.
About CM4D Upload Portal Installations
This application may be run as a stand-alone instance or alongside other ATS applications. However, for the purposes of this topic, the assumption is that CM4D Upload Portal is installed on an independent server. CM4D Upload Portal requires an installation of ATS CM4D Server, which may be on different server from the Upload Portal application and 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.
CM4D Upload Portal and its supporting ATS services can be installed on a Virtual Machine or in a container environment.
It is strongly recommended to publish the services via a reverse proxy or an application gateway. The public endpoint must be secured by TLS.
Upload Portal Application
The CM4D Upload Portal machine requires the following applications/services:
- Upload Portal Application with Upload Portal Service - The CM4D Upload Portal service must be able to access the DataSmith Batch Proxy service.
- DataSmith Translator Service
Upload Portal supports scanning of uploaded files for potential viruses, as described in the documentation here.
Supporting ATS Applications
The following additional applications/services are required (on the same computer or other network server) for support or configuration of the CM4D Upload Portal 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.
- ATS Licensing Plugin (v4.0+)
- CM4D Configuration Plugin
- CM4D API Service
- CM4D Server with DataSmith Batch Service
- CM4D Site Database
- DataSmith Batch Proxy Service – Must be installed on the each machine that has an instance of the DataSmith Batch service. This proxy connects the CM4D DataSmith Batch to the Upload Portal used for the import of supplier data.
Hardware & Software Requirements
The following hardware and software specifications apply to any computers hosting the CM4D Upload Portal application, whether it is physical hardware or a virtual machine (VM). For production use, this machine should meet or exceed the minimum hardware recommendations.
| Operating Systems |
|
Linux systems may be used, but ATS does not provide any installers for a Linux environment.
| CPU |
|
| RAM |
|
| HDD |
SSDs are always recommended for the best performance. |
| Database Management System |
The CM4D Results Database requires the SQL Server Instance Feature - Full-Text and Semantic Extractions for Search. See the topic Results Database for the DBA for details. Firewall ports for SQL Server: TCP 1433-1434 (default) CM4D Upload Portal, ATS Security and Configuration Manager and ATS Licensing require individual databases. These databases can be hosted on the same database server used for CM4D. |
| Web Browser |
|
End users access the application via a web browser. CM4D Upload Portal is based on HTML5, so its only requirement is that the browser is up to date with current technologies.
Internet Explorer is outdated and therefore not supported. |
Other Prerequisites
The following is only required if you plan to install the Upload Portal on a machine that does not have an internet connection. With an internet connection, the prerequisite is downloaded and installed automatically by the Upload Portal installer.
- Microsoft .NET Core Hosting Bundle Runtime 3.1.10
Available Ports
The following ports are the default settings used in the three Upload Portal installers:
- Upload Portal – 4600
- DataSmith Translator – 4500
- DataSmith Batch Proxy - 3200
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.
Upload Portal Deployment Example
The following diagram demonstrates a complete deployment of the Upload Portal and its supporting ATS applications/services on one server, with the supporting CM4D services on another server.
|
|
|
Machine 1 - Configuration Server
|
Machine 2 - CM4D Application Server
|
For more examples, please refer to the topic CM4D Upload Portal Deployments.
Firewall Port Reference
Hardware Reference
Software Reference
