Professional Documents
Culture Documents
White Paper
9 Reasons to Retire Your
Homegrown ERP Software Solution
Before its Too Late
9 Reasons to Retire Your Homegrown ERP Software Solution Before its Too Late i
WHI TE PAPER
Table of Contents
Introduction ii
Reason 1:
Vulnerability and Isolation of Knowledge 1
Reason 2:
Immediacy and Breadth of Data 2
Reason 3:
Data Duplication and Discrepancies 3
Reason 4:
Lack of Testing 4
Reason 5:
Lack of Vision/New Advances 5
Reason 6:
Shortcomings in Systems Architecture 6
Reason 7:
Costlier Than You Think 7
Reason 8:
No Built-in Learning Management System 8
Reason 9:
Lack of Ability to Easily Integrate 9
Conclusion 9
About Epicor 10
9 Reasons to Retire Your Homegrown ERP Software Solution Before its Too Late i i
WHI TE PAPER
Introduction
In todays complex business environment, it can be very challenging
for in-house IT professionals to keep up with the pace of change
necessary to sustain a competitive advantage.
Whether the homegrown IT system you have seems "fine" for now,
or your company has developed strong loyalty to a custom-built
solution, these options cannot offer you the level of protection and
security of an outside enterprise resource planning (ERP) solution.
ERP system installation is often thought of as the most risky,
expensive, and disruptive investment a distributor can make in their
business. However, you must also consider the inherent risks of a
homegrown solution. When you argue against a potential system
switch with costs, pain, and efficiency concerns, you should take a
look at them as they exist in your current system.
Compared to a robust ERP system built by a well-established
software provider, homegrown tends to be fragile and lacking in-
depth support. And while a custom-built system may seem to offer
control and flexibility, it may actually lock you into a suboptimal
solution. Some basic questions to consider include:
Is software development really your core competency?
Can you spare the programming resources?
Do you have the years and the capital to develop, test, and fine-
tune your application?
What happens if you lose the precious few resources that can
support and maintain your older technology?
What is your visibility into emerging technologies and industry
best practices that other distributors are using?
Is your system truly integrating information and processes from
all functional divisions of your organization, or do you have
disparate data sources running your business?
Cost-effective ERP solutions meet distribution organizations
demands by leveraging existing applications and technologies, while
taking the burden off your internal development resources.
For all of these reasons, it is in your best interest to partner with a
leading ERP provider, in order to advance your operations to the next
level of efficiency.
To help answer the above questions and explain the realities of an
ERP system, we have compiled the top nine reasons to weigh the
advantages of an outside ERP over your homegrown system.
9 Reasons to Retire Your Homegrown ERP Software Solution Before its Too Late 1
WHI TE PAPER
Reason 1:
Vulnerability and Isolation of Knowledge
Using a homegrown solution can raise numerous challenges. For
example, what happens if your IT director is no longer with the
company? Or the programmers who developed the original application
move on to other projects, other jobs, or retirement? You may be
coding in yesterday's technology, and will find it hard to replace
resources who are familiar with and competent in those environments.
Who will take over development of the current system, and how will
they get up to speed on the application? With only a limited staff of
custom programmers, its unlikely that you are taking full advantage of
the ideas and innovations of other leading distributors or industry
consultants. You may never be able to develop capabilities at the rate of
the rest of the industry, and competitors in your market will pass you.
Items to consider
What are you planning to do about areas of the system that were coded
by people who left the company years ago? Typically, there are certain
areas that everyone is afraid to touch because they are not readily
understandable and not coded to standards. If you try to remodel those,
will they ever really work the right way?
9 Reasons to Retire Your Homegrown ERP Software Solution Before its Too Late 2
WHI TE PAPER
Reason 2:
Immediacy and Breadth of Data
Even if you were to successfully reface your homegrown system to a
modern graphical user interface and port to a relational database, you
will still be technically challenged by the core foundation of a custom
systems millions of lines of business code. Moreover, a homegrown
solution is unlikely to include some of the advanced data capabilities of
modern ERP systems:
Batch System vs. Real-Timeolder custom systems are usually
updated via batches (daily or monthly), and it is extremely difficult to
rewrite all the logic into a 100 percent real-time system. Batch
systems also typically have lengthy day-end, month-end, and year-
end processes.
Limited Historyhomegrown systems often have limited
transactional history, as the data is purged every few months. This
forces you to refer back to paper reports or information that is
stored in a separate document imaging system.
Limited or No Drill-Downsolder systems have limited drill-down
capabilities where you can view summary information including paid
A/R invoices, POs, A/P invoices, and GL entries.
User-Friendly Interfacehomegrown systems typically lack the
ability for end users to customize the interface and information to
their specific business needs, make them more efficient, and view
data that is most relevant to their job function.
Items to consider
Lack of rapid access to required information also may require extra
hands to manually track down the data, causing you to overstaff your
customer service department.
9 Reasons to Retire Your Homegrown ERP Software Solution Before its Too Late 3
WHI TE PAPER
Reason 3:
Data Duplication and Discrepancies
It can be quite challenging for company employees to get the data they
need directly from a homegrown solution. If you plan to port data on a
nightly basis to a data warehouse on an open database like Microsoft
SQL Server
, MapPoint
is a registered
trademark and/or trademark of Epicor Software Corporation in the
United States, certain other countries and/or the EU. All other
trademarks mentioned are the property of their respective owners.
Copyright Epicor Software Corporation 2012. All rights reserved. No
part of this publication may be reproduced in any form without the prior
written consent of Epicor Software Corporation.
For more information, contact Epicor Software Corporation: info@epicor.com or www.epicor.com.
Worldwide Headquarters
San Francisco Bay Area
4120 Dublin Boulevard, Suite 300
Dublin, CA 94568 USA
Toll Free: +1.888.448.2636
Direct: +1.925.361.9900
Fax: +1.925.361.9999
www.epicor.com
Latin America and Caribbean
Blvd. Antonio L. Rodriguez #1882 Int. 104
Plaza Central, Col. Santa Maria
Monterrey, Nuevo Leon, CP 64650
Mexico
Phone: +52.81.1551.7100
Fax: +52.81.1551.7117
Europe, Middle East and Africa
No. 1 The Arena
Downshire Way
Bracknell, Berkshire RG12 1PU
United Kingdom
Phone: +44.1344.468.468
Fax: +44.1344.468.010
Asia
238A Thomson Road #23-06
Novena Square Tower A
Singapore 307684
Singapore
Phone: +65.6333.8121
Fax: +65.6333.8131
Australia and New Zealand
Level 34
101 Miller Street
North Sydney NSW 2060
Australia
Phone: +61.2.9927.6200
Fax: +61.2.9927.6298