The ModelEnterprise approach

Implementing a ModelEnterprise application is a relatively straightforward, but nevertheless results in the capture of a wealth of corporate information in a form that can be used to provide value many times over in the future. The steps are described below.

Step 1 - Build a model of the site or multi-site enterprise

This is the most time-consuming step. Typically models are built over a period of 1 to 3 months by a small team of PSE modelling experts working closely with site personnel.

This approach helps ensure the most rapid and cost-effective implementation of a fit-for-purpose model, and also help transfer modelling know-how to the organisation.

The information required for the model is shown schematically on the right. Enterprise model

Most of this is readily available. For example, recipes can be taken directly from the SAP system or equivalent.

Unlike other planning and scheduling tools, it is not necessary to formulate complex sets of rules.

All you need to do is to define the underlying definitions of equipment, materials, recipes and other relevant information.

ModelEnterprise takes care of all the inter-relationships between resources and demands automatically.

Because the model is based on quantitative equipment and material information rather than rules that may have only a limited area of validity, the model has a wide range of applicability.

The investment in such a model can be considered 'model equity'. The model is a valuable asset that can be used many times over during the life of the facility or wider enterprise for a number of different purposes.

Step 2 - Formulate and execute the optimisation

Optimising involves the following steps:

2(a) Providing order information

Examples are customer delivery requirements such as delivery date, products, quantity, minimum delivery amount, penalties for late delivery, etc.

The order information may also include anticipated orders, for campaign planning applications.

2(b) Formulating the optimisation

This involves determining and describing the objective. ModelEnterprise allows virtually any type of objective to be set, as long as the objective can reasonably be achieved by manipulating the degrees of freedom within the plant.

Typical examples of objectives are:

manufacturing objectives, such as maximising utilisation of a particular equipment item during a campaign, or obtaining maximum production against manufacturing costraints
financial objectives, such as minimising the cashflow impact of work-in-progress

The constraints for the optimisation arise naturally from the description of equipment, recipes and other resources entered during step 1.

2(c) Executing the optimisation and analysing the results

Results in MS Excel

Results in ModelEnterprise Gantt viewer/editor – click to enlarge

The results of the optimisation can be viewed in many diffferent ways (see right).

If the results for any reason do not reflect practicable solutions, it is possible to intervene manually and re-run the optimisation.

For example, a particular item of equipment (or area of manufacturing plant) may no longer be available during a certain period. An operation for this equipment can be dragged to an appropriate point in the schedule and the optimisation re-run to find a new optimum that reflects the constraint.

Step 3 - Implement

Some ModelEnterprise applications are aimed at optimising aspects of plant design or situation of facilities.

Most applications are however aimed at optimising important aspects plant operation, and it is desirable to implement these in plant systems in such a way that they can be run from day to day, or as the changing resource and demand scenarios require.

Implementation can take many forms, depending on the objective. Results may be, for example:

provided in report form using standard MS office software
sent to the plant scheduling system in order to implement the optimal schedules
provided to the purchasing system, in order to purchase materials according to the optimal cashflow profile determined by the ModelEnterprise optimiser
sent to the Management Information System for support of management operational decisions