Roles:

SAP EWM Implementation

Industry:

Food & Beverage

Roles:

Project Lead | Solution Architect

Corner Stones:

14 Warehouse numbers (EWM Embedded )
Duration ~2 years Design / Implement / GoLive & Hypercare
Part of an S/4 Transformation

Highlights:

Key Challnges:

L ogitiscs business without SAP (EWM) know-how
Little SAP (EWM) know-how in the implementation team
Complex system landscape

Approach.

2. Project Kick Off

1. Starting Point.

Identification of main process clusters
Complexity drivers deep dives
Effort estimation & project timeline derivation
Synchronization with the S/4 transformation timeline

Predecessor implementation team failed
State of current implementation "fruitless"
Switch of the implementation team required
No design / implementation documentation

4. Integrative Testing

3. Design & Implement

Process by process system design & implemenentation
Main steps :

3 Integration Tests
Testing of load & mass processing (typical daily load processing )

(1) Process design draft (2) Business alignment & approval (3) Template implementation - (4) Variant localization (5) Internal testing (6) Business Handover

6. GoLive & Hypercare

5. GoLive Preparation

Issue Handling
(1) Problem identification by on-site team (2) Debugging & bug fixing by remote team
Rolling Optimization
(1) Improvement identification (2) Effort estimation (3) Prioritization according to duration, cost & benefit (4) Remote team implementation & testing

Business trainings
Hypercare team upskilling
Detailed scheduling of the hypercare team (24/7 multiple locations)

7. Application Maintenance Handover

AMS process & operating mode set up
Training documents & internal Wiki set up
Continuous improvement & change process

Designing & Implementing an Interface to a Logistics Service Provider

Industry:

Logistics Service Provider

Roles:

Part Project Lead | Solution Architect

Corner Stones:

ECC ERP & EWM system landscape on LSP side
S/4 HANA system landscape on customer side
Duration ~1 year design / implement / test
Part of an S/4 Transformation

Highlights:

Comprehensive integration of an external warehouse management system
Close to standard LE-IDW interface
High process variety & complexity

Key Challenges:

Two implementation teams (Customer & LSP)
No process or system documentation on customer side

Approach.

2. AS-IS Process Analysis

1. Starting Point.

Creation of a omprehensive as-is process documentation
Deep dives with process experts
Integrative workshops

S olution architecture by previous team embraced 3 powerpoint slides ( & missed most of the complexity drivers)
Very stiff timeline due to planed S/4 rollout
Poor design / implementation documentation

3. To-Be Process Specification

4. Implementation

To-be process definition & business alignment (both systems)
To-be Interface architecture definition

Step by step interface implementation
Process Scope: Inbound / Outbound / Cross- & Intrecompany / Transport Handling / Kitting / Physical Inventory / Stock Transfers / Quality Inspection / Empties Management / Exception Handling

6. GoLive Preparation

5. Testing

Definition of a consistent concept for the migration of stock & master data in both systems
Cutover structuring & planning

Definition of t est cases / test steps / ex pected results for both systems
Test data derivation
Monitoring & defect handling concept

SAP EWM Implementation

Industry:

Aerospace

Roles:

Project Lead | Solution Architect

Corner Stones:

1 warehouse number (Decentral EWM on ECC)
2 automated storage systems
Duration ~1 year Design / Implement / GoLive & Hypercare

Highlights:

Application of the "API-Driven ABAP Development Concept"
Complex customer specific Fiori applications
Complex out of standard PP-Integration

Key Challenges:

Defined blue print (pre-project) basically useless
Little SAP (EWM) know-how in the implementation team
High degree of customer specific programming

6. GoLive & Hypercare

Approach.

2. To-Be Process Definition

1. Starting Point.

High pressure on implementation team due to insufficient results in the predecessor project
Complete redesign of process & system landscape required

High pressure on implementation team due to insufficient results in the predecessor project
Complete redesign of process & system landscape required

Definition of system architecture
Detailed design of fiori applications
Alignment of fiori applications & processes with business based on mockups
Detailed implementation planning

4. Testing

3. Implementation

Application of the "API-Driven ABAP Development Concept" (read more)

Main steps:

Definition of test cases / test steps / expected results
Derivation of test data
Monitoring & defect handling concept

(1) Rollout of the "API-Driven ABAP Development Framework" (1) Implementation of additionally required API elements (2) implementation of the customer specific layer (3) implementation of test programs & unit tests

6. GoLive & Hypercare

5. GoLive Preparation

Business training & shadowing by the onsite team
Rolling optimization: (1) Improvement identification (2) Effort estimation (3) Prioritization regarding duration-cost-benefit (4) Implementation & testing

Definition of a cutover concept
Definition of a stock migration approach
Creation of concepts & templates for the migration of historical data and master data

Rollout & Localization of an S/4 HANA Template in the DACH Region

Industry:

Construction Industry

Roles:

Functional Streamlead - Logistics

Corner Stones:

~ 40 Warehouses - 13 of which on EWM
Duration ~ 2 years (Localization only)

Highlights:

Project frozen without GoLive
High organizational complexity
Close to "Standard" S/4 implementation

Key Challenges:

GoLive in other regions problematic
"Global Template" mostly does not meet local requirements
Very stiff "Process Follows System Approach"

Approach - It's worth to learn from Bad Practice.

1. Starting Point

2. Global Template Fit-Gap

Global template build & rolled out in smaller regions
GoLive in other regions unsuccessful
Local team faces many uncertainties regarding how to apply the global template without loosing operability

(1) As-Is process identification
(2) Global template fit check
(3) To-Be Process definition & d ocumentation
(5) Gap identification

4. Testing

3. Localization

Definition of t est cases / test steps / e xpected results
Test data derivation
Monitoring & defect handling concept

"Fit To Global Template Approach"
Adjust process as much as possible
Adjust solution as little as possible

5. Freeze

Project freeze due to multiple reasons

(1) Risk of inoperability
(2) Budget
(3) Difficult market situation

About

Lets's Connect

Work

About Me

Projects

Solutions & Methods

SELECTED PROJECTS

PROJECTS.

A Selection of COMPANIES I have worked with.

Projects DEEP DIVE.

SAP EWM Implementation

Industry:

Food & Beverage

Approach.

2. Project Kick Off

1. Starting Point.

4. Integrative Testing

3. Design & Implement

6. GoLive & Hypercare

5. GoLive Preparation

7. Application Maintenance Handover

Designing & Implementing an Interface to a Logistics Service Provider

Industry:

Logistics Service Provider

Approach.

2. AS-IS Process Analysis

1. Starting Point.

3. To-Be Process Specification

4. Implementation

6. GoLive Preparation

5. Testing

SAP EWM Implementation

Industry:

Aerospace

6. GoLive & Hypercare

Approach.

2. To-Be Process Definition

1. Starting Point.

4. Testing

3. Implementation

6. GoLive & Hypercare

5. GoLive Preparation

Rollout & Localization of an S/4 HANA Template in the DACH Region

Industry:

Construction Industry

Approach - It's worth to learn from Bad Practice.

1. Starting Point

2. Global Template Fit-Gap

4. Testing

3. Localization

5. Freeze

About

Lets's Connect

Work

A Selection of COMPANIES
I have worked with.

Projects
DEEP DIVE.