Below are the definitions for the OTC (Order to Cash) Key Performance Indicators from the BW "RCS OTC KPI" workbook.

Use of option 'Fixed date and Qty'

IndicatorUse of option 'Fixed date and Qty'
StreamOTC
Process / Sub-processSales
Target 
Expected Evolution↑for Priority 1,  ↓ for other priorities

Definition

Allow to check whether this functionality is used or not, and to measure evolution (progress or degradation) compared to previous months

Good practice

To be used according the rules defined by each enterprise.
'Diphenols' example : to be fixed for 'strategic customer' (delivery priority = 1) : once the delivery date confirmed 

Purposes : 

Calculation

Caculate per Sales Office, then per Sales organisation :
   . total number of sales order items  
   . % = weight vs total number at sales office level 
   . total number of sales order items for customer with 'delivery priority' = 1
         ... number of items with this option flagged.
         ... % =  corresponding number of items with this option flagged
                     ------------------------------------------------------------------------------
                     total number of Item orders with 'delivery priority' = 1

   . total number of sales order items for customer with 'delivery priority'  'not equal to 1'
         ... number of items with this option flagged.
         ... % =  corresponding number of items with this option flagged
                     ---------------------------------------------------------
                     total number of Item orders with 'delivery priority' 'not equal to 1'

Analysis axis

Mode of deliveries creation

IndicatorMode of deliveries creation
StreamOTC
Process / Sub-processLogistics
Target95-98%
Expected Evolution

 

Definition

Allow to check whether this functionality is well used to give to people time to manage the 'delivery troubles'.

 

Good practice

Created by an overnight batch : # 95-98%

… By user : # 2 to 5 %

Purposes is to be created on time according to the due date : either 'Material avail. Date' or 'Transportation plan. date'.

Calculation

Calculate per 'Shipping point' :
 . total number of 'Deliveries'  
 . % = weight vs total number at 'Plant' level

   . Automatic mode
       ... number of items with userid = OPSCHEDULE.
       ... % =  number of deliveries with userid = OPSCHEDULE
                   -----------------------------------------------------------------------
                                 total number of deliveries

   . Manual mode : same mode of calculation

Analysis axis

Mode of Shipments creation

IndicatorMode of deliveries creation
StreamOTC
Process / Sub-processLogistics
Target95%
Expected Evolution

Definition

Allow to check whether this functionality is well used to give to people time to manage the 'Shipments troubles'.

Good practice

Best practice : to be created either : 

Purposes :

Good practice if represent # 5% : manually by user ; with risk that ship doc not created on time

Calculation

Calculate per 'Transportation Planning point' and 'Shipment type'

Shipment type level :
 . total number of 'shipments' per shipment type
 . % = weight vs total number at 'TPP' level

Analysis axis