In reading the 1-800-JUNK-VAN case,
Kingo has some IT issues that he must deal with to make his business flow
smoothly. His main goal is to either
design or implement a system of information flow to improve day to day
operations as well as to allow him to manage his employees effectively. His day to day problems consisted of
inefficiency, errors, operational complexity, reliance on email, geographical
dispersion, and an absence of face to face interaction with employees.
Their
process seemed very tedious and there was a lot of room for mistakes since
information was being passed through many different hands. It involved emailing customer information
directly to drivers on jobs they were to perform, operators entering
information manually into MS-Works, and data clerks modifying that information
when the transaction is done. The human error increases as the amount of people
touch detailed information. By inserting
a system by which a computer can handle detailed information, you automatically
increase your efficiency tremendously.
Kingo
contemplated 5 options to improve the overall process and make his business more
efficient: Microsoft Access, custom application, Google Docs, Platform as a
Service, and ERP System (Enterprise Resource Planning System). The consultants that 1800JunkVan hired to
solve this issue, analyzed each option very well and decided that the best
course of action was the Platform as a Service (PaaS) option. This is a cloud based service that had many
different functions to which IT help would be needed. They argued that it would eventually be more
beneficial to the company because start up costs would be minimal, there were
no annual contracts to be tied to, employees would be able to gain access to it
remotely, and there were many options or functions that can be used with little
training. They also argued that by
paying a little more in fees, you would be able to get extra features such as
mobile applications which can make communication with the drivers become
simple.
After
the presentation and Q&A’s were completed, professor Peterson realized
that the case had made a mistake on the name of the system to which the
consultants recommended. Initially the
consultants were recommending Platform as a service. Platform as a service meant that the consumer
creates the software using tools and/or libraries from the provider. The
consumer also controls software deployment and configuration settings. The
provider provides the networks, servers, storage and other services. Software as a service is software that is
developed and hosted by the SaaS vendor by which the end user customer accesses
over the Internet. Unlike the Platform
as a Service application that users install on their computers or servers, the
SaaS vendor owns the software and runs it on computers in its data center. The customer basically rents the software for
a monthly fee. Both applications basically do the same thing however, with
SaaS, maintenance and support is handled by the SaaS vendor instead of the
customer which relieves the burden and cost of implementing an IT department.
I
think that the consultants made a correct assessment of the issue at hand by
recommending the SaaS. The balance
between price, customization, mobile applications, functionality, and IT
support makes this the optimal fit for an organization such as
1800-JUNKVAN. Kingo should have no
problem identifying the correct solution moving forward.
No comments:
Post a Comment