Index  Home

Production Scheduler

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

Caution: This feature is only available on-premise. If you are using the Cloud solution, this document is not relevant.

Note: For higher performances, host PlannerOne on a dedicated server.

CategoryConfiguration 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. Make sure you perform this as administrator.
    >> 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. Refer to this page for more details on this framework and how to get it.
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 all depend on the amount of data in the production plan: number of work orders, operations, links, and resources. You need a minimum of dedicated memory for each user accessing PlannerOne concurrently.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 planCPURAMRAM additional concurrent userBandwidthStorage
Up to 4,0002 vCPU XEON 2.2 (2.7) Ghz4 GB200 MB450 Mbps1 GB
Up to 8,0002 vCPU XEON 2.5 (3.3) Ghz8 GB300 MB750 Mbps1,5 GB
Up to 16,0004 vCPU XEON 2.8 (3.6) Ghz12 GB400 MB1000 Mbps2 GB
More than 16,0004 vCPU XEON 3.2 (3.6) Ghz16 GB600 MB2000 Mbps4 GB

Disk bandwidth is not critical because it is only used during 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 is, the faster the CPU and the more memory you need. The scheduling engines use about 100% of a CPU but are hardly distributable, which means it can go up to 120%, depending on your model and criteria. This is why the CPU frequency is more important than the number of CPUs.


Index  Home