RE: SYS21 - Key Performance Indicators / Measurements

At Williams Controls we are measuring delivery performance on a daily basis
using a set of queries which I created. We also measure Inventory accuracy
once a year when we perform a stock count. I am currently developing some
programs which will measure delivery performance more accurately than from
the queries. This is made more complicated for us because we also use
advanced customer scheduling and advanced shipping as well as using advanced
order entry.

This is how I am planning to get the performance data.
1) At the beginning of the week, extract all orders and customer schedules
due to be delivered for that week.
2) At the end of each day, extract the order changes for that day and update
the weekly schedule.
3) At the end of each day, extract shipments using journal changes on ACP04
and OEP70. From this information write data to a file for all shipments that
were due to be shipped in that week. For each part and customer I will write
out a record which will show if it was shipped early, on time or late. I
will also write records to another file which will report everything that
was shipped and the number of days late the shipment is. At the end of the
week I will export the data to Excel and create bar charts and pie charts.

I agree that System 21 does not provide much help in this area. Maybe the
KPI fastpack will help.

We are unable to check delivery performance from our suppliers because we
use blanket purchase orders, so we tend to look at the parts we were unable
to ship on time and find out what purchase parts we were waiting for.

Phil.


-----Original Message-----
From: Dan Thomas [mailto:dthomas@mdimail.net]
Sent: Thursday, August 01, 2002 6:39 AM
To: 'JBAUSers-L@midrange.com'
Subject: SYS21 - Key Performance Indicators / Measurements


I'm wondering how other System 21 users are measuring the following things:

Order Fill rates
On-Time shipments
Order/picking/shipping turnaround time
Receiving turnaround time
Pick Accuracy
Receiving/putaway accuracy
Inventory accuracy

Our definitions:

Order fill rate (percent of order lines shipped complete by due date -or-
percent of order lines that never backordered).   The latter just measures
proper stock levels and the former is somewhat of a service rate.  We've
also been asked to provide fill rates at an order level (rather than line)
where all lines must be "filled" or the order is considered not filled.

On-Time shipments (percent of orders and/or order lines shipped by
(sometimes "on) the requested date.

Order turnaround time (average time between receipt of order and time to
pick -or- time to ship).  We normally consider only those orders requested
to ship same day for this measurement.

Pick accuracy (percent of order lines picked without an error, i.e. either
wrong item/lot or quantity)

Receiving accuracy (percent of lines received properly, i.e. correct item#,
lot#, quantity, unit of measure and expiration date and where warehouse
location recorded in system is actual location used - not necessarily what
system suggested)

Inventory accuracy (either percent of item/lot#s having correct balance
during physical inventories -or- percent having correct balance and being in
correct warehouse location).

We are on v3.5.0 and use the warehousing module.  We use System 21 requested
delivery dates (DTDRxx) as scheduled ship date.  It seemed to make more
sense to instruct people when to ship something explicitly rather than tell
them when it needed to arrive and just know transit times.  When given a
requested delivery date by a customer, we calculate the scheduled ship date
by considering the transportation transit time.  In our environment we don't
allow any over/under ships and most orders ship the same day from stock.

In my opinion, every one of these measurement have significant challenges in
being produced.  For one things, how in System 21 do you define errors?  We
record errors in an external system and use queries against System 21 to get
the totals and then calculate the percentages in a spreadsheet.   Some of
the timing measurements are difficult because either there is no date and/or
timestamp -or- it is indirect (have you tried getting from order lines to
warehouse activity files - it isn't simple).

Dan Thomas
Director of Information Technology
MDI
4500 Progress Blvd
Louisville, KY  40218
(502) 318-1208

_______________________________________________
This is the GEAC/JBA System 21 Users (JBAUSERS-L) mailing list
To post a message email: JBAUSERS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/jbausers-l
or email: JBAUSERS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/jbausers-l.