|
PerformAPSâ„¢ - 100
PerformAPSâ„¢ APS production scheduling software is the next level up from Preactor Lite. Like Preactor Lite, Preactor 100 APS has a fixed set of data tables and menu buttons, but has additional functionality for more demanding applications. |
|
PerformAPSâ„¢ - 200
PerformAPSâ„¢ 200 is the entry level configurable product; it can be integrated with other applications such as ERP/MRP, MES and data collection packages. The data table fields and menu buttons can be customized to meet your application requirements. |
|
PerformAPSâ„¢ - 300
PerformAPSâ„¢ 300 FCS production scheduling is a multiple constraint scheduler. This means that you can define as many resources (constraints) as you like for each operation. Secondary resources can be made finite or infinite and you can set up secondary resource groups to define, for example, operator skill teams. |
|
PerformAPSâ„¢ - 400 APS
PerformAPSâ„¢ 400 APS production scheduling software adds additional features and functionality over the Preactor FCS members of the Preactor family of production scheduling tools. |
|
PerformAPSâ„¢ - 500 APS
PerformAPSâ„¢ Preactor 500 APS is the next level up from 400 APS the difference being that it has access to the Preactor BoM Exploder or PBX. |
|
PerformAPSâ„¢ - 600 APS
PerformAPSâ„¢ 600 APS is a package that includes Preactor 500 APS, for the planner to manipulate and interact with the schedule, and a Preactor SCS to hold the live schedule and respond to electronic CTP enquiries. |
|
PerformAPSâ„¢ - Enterprise
PerformAPSâ„¢ Enterprise is a multi-license product designed for companies who are going to implement Preactor production scheduling at multiple plants. PE comes with one control license and a number of run-time licenses which can be run as Preactor 400 APS, 500 APS or SCS functionality. The control license is used to create and modify the configurations to run on each of the run-time licenses. It then compiles these configurations. Run-time systems are typically installed at each plant where Preactor is to be used and will only run compiled configurations created and compiled by the PE control system. |
| |
