$50,000 PSC paid a CPA firm $50,000 a year to prepare its financial statements. The new
software would prepare the statements automatically.
$40,000 Because the old system did not have credit-managing capabilities, it was hard to
detect past-due accounts. Earlier detection of past-due accounts would result in
faster collections, fewer lost customers, and fewer write-offs.
Unknown The major reason for acquiring the system was to improve customer service by
making more detailed customer information available.
After estimated annual maintenance costs of $10,000, there was an annual return on
investment of $224,000. Because the system would pay for itself in less than a year, Steve
bought it and wrote off his $20,000 investment in the other system.
When DSM installed the software, Steve found out that the promised features were not
available and that there was no immediate plan to add them. Although Steve and Mike were
upset, they had to shoulder some of the blame for not insisting on the two features before
signing the deal. They found a program that automatically determined the cheapest way to
pack and ship an order. DSM agreed to pay half of the $10,000 cost to integrate it into the
program. DSM offered to create the module to reflect customer credits and back orders for
another $20,000, but Steve declined. These problems pushed the conversion date back several
months.
PSC spent three months preparing to implement the new system. Training PSC employees to
use the new system was particularly important. Adding a customer to the database required
only one screen with the old system, the new software required six screens. Employees were
taught to shout “Fire!” when they had a problem they could not handle. Mike or a DSM
programmer explained the error and how to correct it. During implementation, the new
system was tested for glitches by processing real data. Looking back, Mike admits three
months were not nearly enough for the training and testing. They should have used twice as
much time to identify and eliminate glitches.
When PSC converted to the new system, telephone operators were confronted with situations
they had not been trained to handle. Soon everyone was yelling “Fire!” at the same time. In
less than one hour, so many operators were waiting for help that the programmers stopped
explaining the correct procedures and simply ran from operator to operator correcting
problems. Mistakes were repeated numerous times, and the situation intensified. Some
employees, frustrated by their inability to work the new system, broke down and cried openly.
In the warehouse, Steve was not having much fun either. On a normal day, PSC has 200 to 300
boxes ready for 3:30 P.M. shipment. On conversion day, a lone box sat ready to go. Facing the
first default on his 24-hour turnaround promise, Steve, Terri, Mike, and a few others stayed
past midnight packing and loading boxes on trucks. They barely made it to the UPS hub on
time.
The next day, order entry and shipping proceeded more smoothly, but Steve could not
retrieve data to monitor sales. That did not make him feel too kindly about his $200,000
system or DSM. It took Steve weeks to figure out how to get data to monitor sales. When he
did, he was horrified that sales had dropped 15%. They had focused so hard on getting the
system up and running that they took their eyes off the customers. To make matters worse,
Steve could not get information on sales by customer, salesperson, or product, nor could he
figure out why or where sales were falling. Things quickly improved after “Hell Week.”
Orders were entered just as quickly, and warehouse operations improved thanks to the
integrated add-in program. The new system provided pickers with the most efficient path to