Getting Started with DPM > DPM System Requirements
DPM System Requirements
System requirements and release matrices for all PTC products are stored in the Release Advisor. The matrices provide information about the compatible operating systems, web browsers, third-party software, and other PTC products. Follow these links to view the Digital Performance Management (DPM) release matrices:
To view a release matrix in Release Advisor, complete the following steps:
1. Log into the Release Advisor.
2. In the Product Family field on the Primary Product page, select ThingWorx. Then select the Product and Version that you want to view. Click Add.
3. Click Next.
4. The release matrix for the selected product is provided in the Release Matrix field in the Primary Product bar at the top of the page. Click on the release matrix name to open the release matrix for that product.
For additional information on using Release Advisor, see this Technical Support Article in the PTC Knowledge Base.
SQL Database
In addition to the ThingWorx database, DPM requires its own SQL database. Compatible database servers are listed in the Digital Performance Management release matrix in the Release Advisor.
Screen Resolution
The required minimum screen resolution for DPM is 1280x1024.
Hardware Sizing
The following table lists the hardware sizing recommendations for DPM 1.2.x systems, based on the number of pacemakers, sites, and users.
Pacemakers / Sites / Users*
ThingWorx Platform
Microsoft SQL Server** (TWX and DPM)
Storage for 1 Year of History
250 / 5 / 50
16 vCPUs, 32 GB RAM (D8s_v3)
16 vCPUs, 64 GB RAM (D16s_v3)
~400 GB
200 / 4 / 34
8 vCPUs, 32 GB RAM (D8s_v3)
8 vCPUs, 32 GB RAM (D8s v3)
~300 GB
150 / 3 / 25
8 vCPUs, 32 GB RAM (D8s_v3)
8 vCPUs, 32 GB RAM (D8s_v3)
~200 GB
100 / 2 / 17
8 vCPUs, 32 GB RAM (D8s_v3)
8 vCPUs, 32 GB RAM (D8s_v3)
~100 GB
50 / 1 / 10
8 vCPUs, 16 GB RAM (D4s_v3)***
8 vCPUs, 32 GB RAM (D8s_v3)
~50 GB
* Data automation property ingentsion was modeled at three writes per second, per pacemaker.
** If using InfluxDB or PostgreSQL for the ThingWorx database, then the recommended resources here can be split between the two different server components.
*** This size is generally not recommended for production systems. A smaller infrastructure can be used to reduce up-front costs while the system is initially being built. When the system is scaled up, a larger infrastructure is needed, as shown in this table.
Was this helpful?