Aggregation
In a typical FCS application we generally want to see the activities of each individual resource, what the sequence is, when setups start and finish and what the run time periods are, taking into account shift patterns and other constraints such as tooling, operators and so on. In a capacity planning application you would typically aggregate resources into groups such as cells, shops, divisions, or plants.
Why aggregate the resources? It really is a question of practicality, do you really need to know what say Machine A will be doing at 10:30 am at this time next year? Aggregation allows a simpler view of your longer-term demand/capacity relationship.
So using an FCS set up, Preactor models your resources as individual machines and/or operators. In a RCCP set up resources are modeled as cells, shops and plants, while in an MPS set up resources are divisions, and multi-plant enterprises.
Demand aggregation has to reflect capacity aggregation e.g. individual works orders for FCS, finished goods SKUs for MPS, as well as the appropriate time periods. At the MPS level of aggregation you cannot use information such as sequencing of orders within a time period, and thus have no impact of sequence dependent changeover times. Nor can you effectively constrain capacity by such factors such as product mix (e.g. you cannot have all 'red' products within a time period), or other factors such a tool availability. So the accuracy of the results in an MPS configuration will not be as high as in an FCS application.
Graphical MPS
Preactor Graphical MPS is a capacity planning and stock control example whereby we wish to examine the impact of variable demand on the capacity usage and stock levels of each SKU across more than one plant.
Preactor Graphical MPS is not separate product. It is a configuration that will run on Preactor v9.3 licensed for Preactor 300 FCS or Preactor APS.
|