Pak Elektronic Limited

Case Report Pak Electronic Limited Converting Systems to ERP Executive sum-up Pak Elektron Limited (picture element), a large manufacturer of consumer home appliances and power transformers, initiated an training form conversion to a tier 1 enterprise imagery planning (ERP) formation in 2007. After the Phase I of carrying into action by 2011, Pak Elektron was facing a runniness crisis that hindered effectuation of further modules. legacy systems were still being widely used, and staff had grown uncomfortable and repellant to change.The contents of this case report include problem identification, finding criteria evaluation, election analysis, and recommendation. Those aforementioned sections depart send Pak Elektrons problems in their project management, their cypher forecasting and planning, their pecuniary patronise, and their human resources and information system death penalty. Based on those problems and our analysis, four alternatives were identified, and the option of a Phased Module ERP executing was recommended.Pak Elektron Limited ( pixel) had everyplace a hundred different systems being used internally, mostly in-house essential stand-alone applications, with some multi-user applications interspersed. Independent carrying into actions and systems promoted the lack of integrating and alike(p) describe, as well as poor quality and timeliness of data. first-class honours degree in 2007, PEL had started converting its information systems to prophesiers EBS Tier 1 ERP system. Problem Identification cat Management Since the resignation of Atif Ameen, PEL has lacked a project champion with extensive experience in IT operation and system implementation.In addition, the estimated implementation period had extended beyond the proposed 2 years, which has change magnitude cost and economic uncertainty for the come with. Budget Forecasting and Planning PEL had poor budget forecasting and analysis, which resulted in insufficient shor t-term assets to support the purchasing of necessary equipment, training costs, and consultancy costs. Financial issues PEL faced a short-term liquidity crisis, and did non have the fiscal heart for respectable system implementation. To mitigate this, some bank loan repayments were hiatusructured in 2010 to exert cash flow in response to the liquidity crisisHuman Resources Staff were distasteful to a systems change. New skills were required, which meant that staffs expertise with the legacy systems were inconsequential. team spirit was low, which resulted in experienced staff leaving the company. Likewise, the IT department encountered a match betwixt legitimate and needed skill set, resulting in unsanded hires and increase project duration due to this transition. Salary discrepancies with old staff and new hires also resulted in high turnover within the IT department data Systems Implementation The implementation process was ineffective and inefficient.PEL needed to spe nd excess resources to run parallel implementation, as numerous system functions were not support. critical/Decision Criteria Cost infrastructure, systems, implementation, maintenance (40%) Cost is the most important decision criterion for PEL. Due to the numerous financial problems that the company has experienced, including a liquidity crisis, it is important that the proposed solution is cost-efficient with regards to infrastructure support, purchasing new systems, implementing systems, and musical accompaniment system maintenance.Integration among ancestry silos and processes (35%) PEL has 25 branches in Pakistan, therefore, communication between the branches and with the central database is necessary. The solution needs to support or improve the integration of as to allow PEL to shorten the time required to develop useful information for timely decision-making. In addition, the solution needs to unify up all the branches with the central database in a better vane structur e as to reduce the internal e-mail traffic. Quality and truth of data (10%)The proposed solution needs to address PELs antecedent problems of double-entry, frequent reconciliations, and other issues concerning the quality and accuracy of data. Ideally, the solution lead either mitigate the systems that impede quality and accuracy, remove them, or improve them. rough-and-ready and timely implementation (10%) Unexpected changes in business operations school principal to disruptive structural changes during systems implementation. Such changes apprize add complexity and deferred the progress, which means longer the time of implementation and higher risk of failure.The proposed system will need to be effective and timely with regards to implementation to mitigate this risk. real-time and useful financial reporting (5%) This criteria addresses PELs need for the system to create a more real-time and useful financial reporting system that is standardized across the organization in order to follow out reporting standards, and promote greater financial decision making. Alternatives 1. Phased Module ERP implementation PEL is being stretched thin many areas due to external factors, and their broad-based systems implementation plan, which was demonstrated in Phase I.Within Phase I, they took a look at 18 different systems, and only managed the implementation of five. PEL needs an nimble action phase-it-in strategy as to focus all of its implementation into the financial reporting Oracle suite. The organization has 5 systems implemented further implementation in this area will be more cost-effective and time-efficient. Furthermore, avocation this implementation, all legacy systems with regards to financial reporting will be removed, and the rest of the project will be re-assessed until implementation of other business suites is feasible. 2.Recall Oracle system, and take a look at other module and ERP options full full general ERPs, like Oracles EBS system, shar e a alike weakness they are made for general organizations, and therefore may not accommodate a specialise fit. PEL has other options with regards to systems implementation and selection, such as development custom ERP software package based on the current legacy system that disrupts the business model as little as possible. PEL can also purchase and implement separate, more specialized suites such as Salesforce for CRM, a cloud based accounting system for financial reporting (Wave), amongst others.It terms of cost, this is an expensive option as customized ERP software is extremely expensive and requires development time. Purchasing individual modules for certain business functions will also be more expensive than a general system due to reduced bundle savings. A customized ERP system will help the silos reintegrate more efficiently due to more in-line processes supported within the system. Customizable modules would ideally improve efficiency of each individual silo. 3. rich rollout of ERP modules Implementation of Phase II and III Budget is the biggest constraint in this option.However, this will ensure full migration away from legacy systems, and will address the concern of generating standardized reports and ensuring data quality. Although data integration may be achieved, PEL should expect high resistance from staff. With full rollout, PEL has the options of a. Hiring/developing in-house expertise to lead implementation of Phase II and III b. Re-hiring AFF tribute Systems conversion risks could have been mitigated had PEL properly planned the ERP migration. Project management was poor and did not assess the full needs and requirements of the company as a whole.Alternative 1, Phased Module ERP implementation, is the best option for PEL. Once the financial systems have been properly implemented (whether in-house or through consultants), PEL can then take a regroup strategy and reassess their situation. If the long-term implementation of the financ e suite is successful, then they can move onward with reduced employee resistance. If the changes in productivity are minor, PEL can exact to avoid implementing systems in other business functions, and avoid disruption the silos. The goals of integration and timeliness of data will be achieved.