Erp Implementation for Steel Industry

7056 Words Oct 22nd, 2012 29 Pages
ERP Implementation for Steel Industry | Critical Success Factors and SAP ASAP | |


Introduction 3 About SAP 3 Literature Review 4 ASAP Methodology 4 Critical Success Factors 5 Analyzing SAP ERP 's success in Steel Industry 8 Case Study: Tata Steel 8 Case Study: Jindal Stainless Ltd. 15 Conclusion 17 References 18

In order to eliminate the problems associated with legacy systems, a new breed of software systems, called Enterprise Resource Planning (ERP), was created. These systems provide a single source of data with designed integration between different functional modules (for example, Accounting, Sales and Distribution, Materials Management, Production planning, etc.). These ERP
…show more content…
This methodology provides an excellent tool for small and midsize companies to rapidly implement SAP and take advantage of its integrated business processes. ASAP provides content, tools, and expertise based on thousands of successful implementations by SAP and its partners. The ASAP methodology consists of a roadmap that defines the five phases of SAP implementation process and supports these with a comprehensive project plan.
ASAP Roadmap
Phase 1: Project Preparation - This phase provides initial planning and preparation for the implementation which includes project plan, project scope, and project team organization. In this phase the initiation of the SAP ERP project, which includes the overall goals, detailed task plans, and processes is formally announced to the company
Phase 2: Business Blueprint - In this phase the scope of the implementation are documented and defined and the Business Blueprint is created. The Business Blueprint is a detailed documentation of the company’s requirements. Application consultants and the Business Process Teams achieve a common understanding of how the enterprise intends to run its business within the SAP ERP System, by carrying out requirements-gathering workshops. The Business Blueprint is created by detailed documentation of the results gathered during these requirements workshops. Furthermore, the Business Blueprint serves to document the business process requirements of
Open Document