Professional Documents
Culture Documents
MI0029 - Enterprise Resource Planning
MI0029 - Enterprise Resource Planning
MI0029 - Enterprise Resource Planning
Assignment Set- 1
Business Integration
The first and most important advantage lies in the promotion
of integration. The reason why ERP packages are considered
to be integrated is the automatic data updating that is
possible among the related business components. Since
conventional company information systems were aimed at
the optimization of independent business functions in
business units, almost all were weak in terms of the
communication and integration of information that
transcended the different business functions.
Flexibility
The second advantage of ERP packages is their flexibility.
Different languages, currencies, accounting standards and
so on can be covered in one system and and functions that
comprehensively manage multiple locations of a company
can be packaged and implemented automatically. To cope
with company globalization and system unification, this
flexibility is essential, and one can say that it has major
advantages, not simply for development and maintenance,
but also in terms of management.
Better Analysis and Planning Capabilities
Another advantage is the boost to the planning functions. By
enabling the comprehensive and unified management of
related business and its data, it becomes possible to fully
utilize many types of decision support systems and
simulation functions. Furthermore, since it becomes possible
to carry out, flexibly and in real time, the filing and analysis
of data from a variety of dimensions, one is able to give the
decision-makers the information they want; thus enabling
them to make better and informed decisions.
Hr R/3 – An Overview
R/3 employs a three-tier client/server architecture widely
recognized by SAP customers, technology partners and
industry analysts as a winning approach to solving some of
today's most demanding information- management
challenges. The three-tiered architecture separates a system
into three functional layers, each structured to support the
demands of its function.
R/3 Modules
R/3's applications are modules. They can either be used
alone or in combination with other solutions. From a process-
oriented perspective, greater integration of applications
increases the benefits derived. The following are the R/3
modules:
Pre-Evaluation Screening :
Once the company has decided to go in for the ERP system,
the search for the perfect package starts. But there are
hundreds of ERP vendors – of all sizes and shapes – all
claiming to have the solution that is ideal for you. Analysing
all the packages before reaching a decision is not a viable
solution. It is also a very time consuming process. So it is
better to limit the number of packages that are evaluated to
less than five. It is always better to do a thorough and
detailed evaluation of a small number of packages,
than doing a superficial analysis of dozens of packages.
Package Evaluation
The evaluation/selection process is one of the most
important phases of the ERP implementation, because the
package that you select will decide the success or failure of
the project. Since ERP systems involve huge
investments, once a package is purchased, it is not an easy
task to switch to
another one. So it is a 'do it right the first time' proposition.
There is little
room for error.
Gap Analysis
This is, arguably, the most crucial phase for the success of
the ERP
implementation. Put very simply, this is the process through
which
companies create a complete model of where they are now,
and in which
direction they want to head in the future. The trick is to
design a model
which both anticipates and covers any functional gaps. It has
been
estimated that even the best ERP package, custom tailored
to a company's
needs, meets only 80% of the company's functional
requirements. company-wide acceptance. The package
experts or the consultants can act
as mediators, or play the role of explaining the pros and
cons of each
package.
Re engineering
It is in this phase that the human factors are taken into
account. In ERP
implementation settings, re engineering has two different
connotations. The first connotation is the controversial one,
involving the use of ERP to aid in downsizing efforts. And
there have been occasions where high-level
executives have invoked the re engineering slogan, and
purchased an ERP
package with the aim of reducing significant numbers of
employees.
Configuration
This is the main functional area of the ERP implementation.
There is a bit of
mystique around the configuration process and for good
reason: the Holy
Grail or unwritten rule of ERP implementation is,
synchronizing existing
company practices with the ERP package rather than
changing the source
code and customizing it to suit the company. In order to do
so, business
processes have to be understood and mapped in such a way
that the
arrived-at solutions match up with the overall goals of the
company.
Testing
This is the phase where you try to break the system. You
have reached a
point where you are testing real case scenarios. The system
is configured
and now you must come up with extreme-case scenarios–
system overloads, multiple users logging on at the same
time with the same query, users entering invalid data,
hackers trying to access restricted areas and so on. The test
cases must be designed specifically to find the weak links in
the
system and these bugs should be fixed before going live.
Going Live
This is it. Lights on, switches thrown, gloves off. On the
technical side, the
work is almost complete–data conversion is done, databases
are up and
running; and on the functional side, the prototype is fully
configured and
tested and ready to go operational. The system is officially
proclaimed
operational, even though the implementation team must
have been testing it and running it successfully for some
time. But once the system is 'live', the old system is
removed, and the new system is used for doing business.
End-User Training
This is the phase where the actual users of the system will
be given training
on how to use the system. This phase starts much before the
system goes
live. The employees who are going to use the new system
are identified.
Their current skills are noted and based on the current skill
levels, they are
divided into groups. Then each group is given training on the
new system.
This training is very important as the success of the ERP
system is in the
hands of the end-users. So these training sessions should
give the
participants an overall view of the system and how individual
actions would
affect the entire system. In addition to these general topics,
each employee
is trained on the job or task that he/she ip supposed to
perform once the
system goes live. It is human nature to resist change. Also
many people are
afraid of computers and other new technologies. So there
will be resistance
to change.
P – Kanban
Most manufacturing companies view the making of a product
as continuous – from design, manufacture, and distribution
to sales and customer se vice. For many companies, the
heart of this process is the Kanban, a Japanese term for
Visual record', which directly or indirectly drives much of tl
manufacturing organization. It was originally developed at
Toyota in tl 1950s as a way of managing material flow on the
assembly line. Over the pa three decades the Kanban
process, which is a highly efficient and effective factory
production system, has developed into an optimum
manufacturing environment leading to global
competitiveness. The Kanban process of production is
sometimes incorrectly described as simple just-in-time
management technique, a concept that attempts to maintain
minimum inventory. The Kanban process involves more than
fine tuning production and supplier scheduling systems,
where inventories are
minimised by supplying the components only when needed
in production, and work progress in closely monitored. It also
encourages industrial reengineering such as a 'module and
cellular production' system, and group production
techniques, where team members are responsible for
specific work element and employees are encouraged to
effectively participate in continuously in proving the Kanban
processes within the Kaizen (continuous improvement
concept.
Benefits of JIT
JIT is continuously seeking to reduce inventory levels of work
in process (WIP), raw-materials and finished goods.
Therefore, less space is required with lower inventories so
there is less chance of the product becoming damaged,
spoiled or obsolete. Material handling of lots can be
automated, and operations can be placed closer together,
enhancing communication and teamwork. The following are
some of the benefits of a properly implemented JIT system: