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 |
|