- Designing database models that contain all the
necessary information for those models and
relationships.
- Designing the actual software. This includes user
interfaces, security management system, backup and
archiving systems and mechanisms etc.
- Integration of the system and training the end
users how to work with the software.
Each one of these steps involves constant dialogs
and communication between the ERP vendor, Client
Company, different consultants in certain areas,
software engineers and end users. Should any of
these steps fails, there is a very high probability that
the whole project will fail and lead to huge financial
losses for the vendors and the clients.
But when implemented and integrated correctly
and precisely, one ERP system gives to the company
very powerful tools for running their business in the
most effective way. That means sharp resource
planning and decision making using analytical
instruments; better fast and effective communication
and coordination between company departments and
external counteragents; efficient accounting and
warehouse management; minimizing loses and
abuses of any kinds.
2 EVOLUTION OF THE ERP
SYSTEMS
To understand how the contemporary complex ERP
systems started to exist, we will follow briefly the
natural software evolution during the past 50 years,
using an article on implementation procedures in
ERP systems, written in 2002 by Elisabeth Umble,
Ronald Haft, and Michael Umble.
During the 1960’s the use of software
technologies was mainly for inventory control.
Companies could afford to keep lots of ‘‘just-in-
case’’inventory on hand to satisfy customer demand
and still stay competitive. Consequently, techniques
of the day focused on the most efficient way to
manage large volumes of inventory (Umble, 2003).
Most of the software packages then were designed
and served the purpose for more efficient inventory
control and warehouse management (Ptak, 2000,
Shankarnarayanan, 2000).
In the 1970’s, it became increasingly clear that
companies could no longer afford the luxury of
maintaining large quantities of inventory. This led to
the introduction of material requirements planning
(MRP)systems. MRP represented a huge step
forward in the materials planning process. For the
first time, using a master production schedule,
supported by bill of material files that identified the
specific materials needed to produce each finished
item, a computer could be used to calculate gross
material requirements. Using accurate inventory
record files, the available quantity of on-hand or
scheduled-to-arrive materials could then be used to
determine net material requirements. This then
prompted an activity such as placing an order,
cancelling an existing order, or modifying the timing
of existing orders. For the first time in
manufacturing, there was a formal mechanism for
keeping priorities valid in a changing manufacturing
environment (Umble, 2003). Later the MRP systems
expanded to “closed loop MRP” (Oden, 1993), that
besides inventory planning included also tools for
planning the production levels, sales planning and
scheduling, making business promises to customers,
forecasting and different analysis tools.
In the 1980’s, companies began to take
advantage of the increased power and affordability
of available technology and were able to couple the
movement of inventory with the coincident financial
activity. Manufacturing resources planning (MRP II)
systems evolved to incorporate the financial
accounting system and the financial management
system along with the manufacturing and materials
management systems. This allowed companies to
have a more integrated business system that derived
the material and capacity requirements associated
with a desired operations plan, allowed input of
detailed activities, translated all this to a financial
statement, and suggested a course of action to
address those items that were not in balance with the
desired plan (Ptak, 2000).
By the early 1990s, continuing improvements in
technology allowed MRP II to be expanded to
incorporate all resource planning for the entire
enterprise. Areas such as product design,
information warehousing, materials planning,
capacity planning, communication systems,
humanresources, finance, and project management
could now be included in the plan. Hence, the term,
ERP was coined (Ghosh, 2012).
Since then the ERP systems are becoming larger,
more sophisticated and they are being integrated in
enterprises and companies of all sizes – large
business corporations, medium and small business
enterprises.
Third International Symposium on Business Modeling and Software Design
282