Benchmark Testing Procedure
This benchmark procedure demonstrates and quantifies DAIRS's incredible
speed advantage over other systems.
If you find a system that even comes close, please call us. We would like to
hear about it.
Have a Part Number selected which is typical and is available in system stock.
Have an existing customer selected.
Note: Under ideal conditions, after selecting test Part Number and customer
number system should be used normally for several hours to purge any caches.
Instruct the user that they will be given a part number which they should
check stock, pricing, and sales/purchasing history, and then quote. Also they
will be given a customer name. After quoting a price, they will immediately
enter an order for the named customer per the quotation they gave.
If more than one lot of the quoted part exists in inventory, they should also
select the stock line to pull from to fill the order.
They should then pick the item in the system and generate the invoice so that all
inventory and accounts receivable records are updated. The user should be
instructed to go as quickly as possible. As this is a test of system and
interface speed, it is the best speed that the system allows for that is
being measured so any trials "botched" by the user should be discarded and repeated.
If repeated user errors recur resulting from some fault of the user interface
then these should be counted.
Once the order has been invoiced
the procedure has been completed and the timer will be stopped.
Start within the application, at any screen or operation. Give the user the
pre-selected random part number, say "go!", and start the clock
- Lookup part number stock quantity, pricing, stock location, and history, in order to quote
- Look up the customer by name
- Enter the entire order and select the stock to ship
- Invoice the shipment
Done - stop the clock
The above does not include the time to physically pick the stocked item, converse with the
customer, or physically print-out a hardcopy of the invoice.
A measure of system and user interface overhead, this test gauges how fast a
proficient user can view, enter, and process data, and demonstrates how much
of a users time the system takes away from other productive tasks.
It also quantifies how much valuable time must go into each order.
compares how much time is necessary to carry out certain standard operations.
A computer system is a tool intended to save the user time. With the DAIRS system
the above operations can be completed in less than one minute, as quickly as 40 seconds.
Average trials with DAIRS take between 45-55 seconds.
How much time does your system require to do these operations?
How many times per day do you look up parts and enter orders?
How much would you like to have that time free for other useful tasks?