Production Scheduler

This document describes the minimum configuration requirements when installing Production Scheduler.

Warning :
This feature is related to a feature available only on-premise. If you are using the Cloud solution, this documentation is not relevant.

To achieve higher performances, it is highly recommended that you host PlannerOne on a dedicated server.

Category	Configuration requirements
Operating system	Microsoft Windows 2012 R2 64-bit with IIS 8 / 8.5 Microsoft Windows 2008 R2 64-bit with IIS 7.5
.NET framework	4.5.2, full package x64 (mandatory version)
Package manager	Nuget v2.8.5 To install nuget v2.8.5.208 launch the Windows powershell and execute the following command inside the powershell, ensure to perform this as the ‘administrator’ user. >> Install-PackageProvider _Name NuGet –MinimumVersion 2.8.5.208 –Force
Windows Management Framework (WMF)	5.0 This framework is required for the PowerShell® tools you will need to deploy the planning software components. (For details on this framework and how to get it, please refer to https://www.microsoft.com/en-us/download/details.aspx?id=50395
Disk space	300 MB for each running instance of PlannerOne. 100 MB required for the .NET framework.

The disk space, the memory size, and the network bandwidth depend on the amount of data in the production plan: number of work orders, of operations, of links, of resources.
For each user accessing PlannerOne concurrently, you need a minimum of dedicated memory.

Below are some standard configurations for one instance and one user, to serve as a starting point for your sizing analysis:

Number of operations in the plan	CPU	RAM	RAM additional concurrent user	Bandwidth	Storage
Up to 4,000	2 vCPU XEON 2.2 (2.7) Ghz	4 GB	200 MB	450 Mbps	1 GB
Up to 8,000	2 vCPU XEON 2.5 (3.3) Ghz	8 GB	300 MB	750 Mbps	1,5 GB
Up to 16,000	4 vCPU XEON 2.8 (3.6) Ghz	12 GB	400 MB	1000 Mbps	2 GB
More than 16,000	4 vCPU XEON 3.2 (3.6) Ghz	16 GB	600 MB	2000 Mbps	4 GB

Disk bandwidth is not critical because it is used only at startup and when saving the plan (which is a background process).

The sequencing and scheduling processes compute intensive activities. The more data you have and the more complex your business model, the faster the CPU and the more memory you need. The scheduling engines use about 100% of a CPU but are hardly distributable, so it can go up to 120%, depending on your model and criteria. That’s why the CPU frequency is more important than the number of CPUs.

Index Home