Keda's ERP Implementation - Group 20
Keda's ERP Implementation - Group 20
Keda's ERP Implementation - Group 20
Disconnected business units often duplicated identical processing tasks- resulting in redundancy and
heightened costs.
Very little information flowed between departments- managers could not make timely, well-informed, holistic
business decisions & act strategically- therefore lacking in competing from local and foreign companies
To retain its leadership position and continue growing, Keda needed to continue innovating in terms of
product development, business management and operations, and it needed to be more informed about
production, sales and, most importantly, customers
Pressure from Chinese government agencies to innovate to catch up with foreign firms
Poor inventory management- low volumes and high customization across an increasingly diverse product
line made it difficult to keep track of the many unique, individual parts
Struggled to meet demand- due to production delays as resources and facilities were not being optimally
utilized, reusable materials and parts were often scrapped
Need for expansion & diversifying produt portfolio
Computerization at Keda
There were three main roles: the key users, the consultant
and the IT officers
In recruiting departmental representative, Zhu involve
representatives such as departmental
managers, essential operational staff, who possessed
comprehensive understanding of the department
Each ERP module was assigned an owner from
associated department, responsible for workflow and
operational details of the module. They also provided
training to others in department
Implementing SAP
Challenges:
1. Operations and workflow in many departments had to be modified & streamlined
2. Organisation's structure to be adjusted to accommodate ERP system
3. New Data model had to be devised to support all operations & workflow which was much time consuming
4. Disagreements over to changes- 1. between different module owners & 2. module owners and consultants
Top management was continuously involved- Board chairman himself was present in several meetings &
Implementations that helped the implementation
Staff training was conducted in parallel with system training that saved time & the users were able to identify
potential malfunctions & gaps
Going Live
Before ERP roll out (system deployment) was executed, production delays or suspensions was foreseen.
However, due to lack of alternative & Top management's agreement, it was implemented. Following
were the practical scenarios faced
work became more tedious. For example, materials for production now had to be checked into and
out from the warehouse
pressure on the Purchasing Department and its manager increased due to new design & new
production orders everyday
Even after system rollout, some users were not completely satisfied with system operations and
interfaces
Future of ERP