Below are the definitions for the PP (Production Planning) Key Performance Indicators from the BW "RCS PP KPI" workbook.

Planned orders in the past

Definition

Extraction of the number of planned orders in the past

Good practice

Planned orders should be converted to process orders between three and seven days prior to production or deleted if the requirement which generated the order no longer exists, or is, for one reason or another, erroneous.
There should be no planned orders in the past.
All planned orders in the past consume raw materials or intermediates and have a negative impact on the efficient functioning of the MRP, they can also have a negative impact on the functioning of the ATP - depending on whether the planned orders are fixed or not and depending on the availabilty check group used.

Calculation

Planned orders with a finish date prior to the date of extraction are counted.

Analysis axes

Rhodia -> GBU -> Plant -> MRP Controller

Comments

This indicator is particularly good for sites that do not plan at all! Therefore possible future evolutions are to ensure that a production plan (planned and process orders) exist in the future for each plant, and over what horizon.

Process orders in the past

Definition

Extraction of the number of process orders in the past.

Good practice

Process orders should be confirmed in a timely manner, and if there are any production delays then these orders should be re-scheduled to reflect the reality of the ongoing situation.
Ideally there should be no process orders in the past, but in reality there is often a slight delay between the actual (physical) completion of the production and it's confirmation in RCS.
All process orders in the past a negative impact on the efficient functioning of the MRPand the ATP.
Also any unconfirmed process orders generate a projected stock based on the theoretical consumptions and in certain circumstances these can be different from the relity of the actual consumptions and therefore less precise than actual consumptions in the confirmed process orders (both in quantities and actaul batches consumed).

Comparaison between entities

Comparison possible betwee MRP controllers within a division, between divisions within an enterprise etc.

Calculation

Process orders with a finish date prior to the date of extraction are counted and divided by the average number of process orders confirmed per month (calculated on a twelve month rolling average)

Analysis axes

Rhodia -> GBU -> Plant -> MRP Controller

Comments

This indicator is particularly good for sites that do not plan at all! Therefore possible future evolutions are to ensure that a production plan (planned and process orders) exist in the future for each plant, and over what horizon.

Number of active entries in the COGI

Definition

Good practice

 This indicator is simply an extraction of the number of untreated active entries in the COGI related to process orders.
This extraction gives an idea as to whether goods movements in error are being treated in a timely manner or not.

All entries in the COGI should be treated in a timely manner and so in general this figure should be zero or very low.
As a minimum these entries should be treated daily and so we should not find the same entry extraction after extraction
Untreated entries can cause the following problems :

• Errors in the stock values
• Errors in production variances
• Difficulties for month end closing.

With resulting consequences on the propositions made by MRP and on actual process order costs and financial variances.

Comparaison between entities

Comparison possible betwee MRP controllers within a division, between divisions within an enterprise etc.

Calculation

No calculation. Simple extraction of number of entries linked to process orders active in the COGI.
This extraction is made early every Wednesday morning (French time).

Analysis axes

Rhodia -> GBU -> Plant -> MRP Controller

Comments

This is a basic indicator of poor practices and is low if the entries are treated by any means.
Potential future evolutions include tracing deleted entries from the COGI which have all the negative impacts above, but with the added difficulty that it is difficult to trace and treat the problem after deletion.

The best way to get IT support is to use the new Service One Platform.