Implementation of an ERP System to Digitize and Optimize all Company Processes

Table of Contents

1. Project Definition

1.1 Background of the Project

1.2 Project Goal

1.3 Environmental Analysis

2. Project Initiation

2.1 Project Charter

2.2 Justification: SWOT Analysis

3. Project Management Plan

3.1 Organisation Plan

3.2 Work Breakdown Structure

3.3 Time management

3.3.1 PERT

3.3.2 Network and Gantt diagramm

3.4 Cost and Resource Management

3.5 Risk Management

3.6 Stakeholder Management

3.7 Change Control Management

4. Project execution and monitoring

4.1 0 – 50 % - 100 % method: Status 27.03.2024

4.2 Earned value analysis (EVA): Status 27.03.2024

4.3 Root Cause Analysis

5 Project Closing

5.1 Summary of deliverables

5.2 Final Report

5.3 Lessons learned

Project Goal and Objectives

The primary objective of this project is to implement an ERP system at MüllerHahn GmbH to digitize core business processes, thereby reducing cycle times, operational costs, and error rates while enhancing overall decision-making capabilities within the company.

• Digitization of company-wide business processes to resolve operational confusion.
• Reduction of cycle times and error rates by 30% through system automation.
• Achievement of annual cost savings totaling 50,000 euros.
• Successful transition from analog work methods to a structured, data-driven ERP environment.

Excerpt from the Book

Summary of Chapters

1. Project Definition: Outlines the necessity for the ERP system due to company growth and the limitations of analog warehouse and purchasing processes.

2. Project Initiation: Covers the creation of the project charter and the strategic justification for the project using a SWOT analysis.

3. Project Management Plan: Details the organizational structure, work breakdown, scheduling tools like PERT and Gantt diagrams, and protocols for risk, stakeholder, and change management.

4. Project execution and monitoring: Explains the monitoring of project progress using the 0-100% method, earned value analysis, and identifying root causes for delays via Ishikawa diagrams.

5. Project Closing: Summarizes the project deliverables, evaluates final reporting outcomes, and highlights key lessons learned for future implementations.

Keywords

ERP system, MüllerHahn GmbH, project management, SWOT analysis, process digitalization, earned value analysis, cost management, risk management, stakeholder engagement, change control, PERT, Gantt chart, Ishikawa diagram, lessons learned, implementation strategy.

Frequently Asked Questions

What is the primary focus of this project documentation?

The document focuses on the end-to-end implementation of an ERP system at MüllerHahn GmbH, covering initial definition, planning, monitoring, and final closure.

What are the core thematic areas covered?

Key areas include project planning, cost/resource management, risk assessment, stakeholder communication, and post-implementation evaluation.

What is the main objective the author aims to achieve?

The primary goal is to digitize analog business processes to improve efficiency, reduce operational costs by 50,000 euros annually, and lower error rates by 30%.

Which scientific methods are utilized in the project plan?

The methodology includes SWOT analysis for strategic planning, the PERT method for estimation, earned value analysis for performance tracking, and the Ishikawa (fishbone) diagram for root cause analysis.

What specific aspects are addressed in the project execution phase?

It covers progress tracking through the 0-50-100% method, adherence to the cost baseline, and technical troubleshooting when project milestones face delays.

Which keywords best characterize the project?

ERP implementation, process digitalization, project control, cost-benefit analysis, and change management.

What role does the SWOT analysis play in the project's justification?

It provides a structured way to identify organizational strengths that support the transition, while highlighting risks that need to be mitigated to ensure project viability.

How were project delays handled during the monitoring phase?

The project team utilized root cause analysis (Ishikawa diagram) to identify the underlying reasons for delays in system testing and subsequently developed specific problem-solving suggestions.