Scoping Workshop

Production
Planning
MICKAE L QUE SNOT

COPYRIGHT©. TOUS DROITS RÉSERVÉS. PAR MICKAEL QUESNOT 1

Process Breakouts - Purpose &
Guidelines
Purpose of the Breakouts
To understand the key changes and
impacts to existing processes, systems,
and data of implementing SAP
To provide input in determining the effort
and cost of implementing the solution
COPYRIGHT©. TOUS DROITS RÉSERVÉS. PAR MICKAEL QUESNOT
Guidelines
Remember: The breakouts are not
intended to identify all issues or
determine solutions – that will come in
the Blueprint
Assign a Timekeeper to stay on time for
each activity
Be willing to put items in the “parking lot”
2
Process Breakout Topics

◦ Introductions & Overview 10 mins

◦ Activity 1: Current Pain Points 10 mins.
◦ Structured Process Review of SAP 30 mins.
◦ Activity 2: Process Specific “Boulders” Investigation 30 mins.
◦ Activity 3: Process/Application Usage & Alignment 30 mins.
◦ Activity 4: Data Quality 15 mins.
◦ Activity 5: Operational Process Reporting 10 mins.
◦ Address Business Deployment Plan Process Cost Driver Questions 10 mins.
◦ Wrap-Up: Action Items for Next Session, Review Findings 5 mins.

Afternoon Process Breakouts

COPYRIGHT©. TOUS DROITS RÉSERVÉS. PAR MICKAEL QUESNOT 3
Activity 1: Current Pain Points
Objective: Identify major “pain
points” for the “As Is” process
within or across locations
COPYRIGHT©. TOUS DROITS RÉSERVÉS. PAR MICKAEL QUESNOT
A “pain point” is a major issue of For Each Pain Point:
effectiveness, efficiency, or
control that impedes business
success
Identify and define the pain point
Define the nature of the impact
(effectiveness, efficiency, control)
Understand the scope of the impact
(locations, functions, scale)
Remember: Do not try to solve the
problem
4
 Objective: Conduct a “Level 3” SAP process
review to frame out significant differences from
the “As Is” to “To Be” processes, such as:

◦ Different inputs, dependencies, or outputs

Structured ◦ Different features or capabilities (e.g. manual vs.
automated)
Process ◦ Different levels of effectiveness, efficiency, controls
Review ◦ Different data requirements
◦ Don’t design the solution

COPYRIGHT©. TOUS DROITS RÉSERVÉS. PAR MICKAEL QUESNOT 5

Activity 2: Process Specific
“Boulders” Investigation
Objective: Frame out any
“Boulders” that apply to a
particular breakout session.
COPYRIGHT©. TOUS DROITS RÉSERVÉS. PAR MICKAEL QUESNOT
“Boulders” are the big issues For each Boulder:
already identified prior to the
breakout sessions.
Define the issue
Define the nature of the impact
(effectiveness, efficiency, control)
Understand the scope of the impact
(locations, functions, scale)
Don’t try to solve the problem
6
 Activity 3: Process/Application
Usage & Alignment
Objective: Identify systems that
support the business processes
today
COPYRIGHT©. TOUS DROITS RÉSERVÉS. PAR MICKAEL QUESNOT
This includes systems used to
perform the function, as well as
those providing key inputs,
outputs, interfaces, or reference
information
For each system identified:
Name and describe the system
Identify the key supporting functions/data
of the system
Hypothesize if the system will still be
required in the “To Be”
Hypothesize if it will need to interface to
the SAP solution (if known)
7
 Objective
◦ Examine cumbersome processes with respect to
the data that supports them in order to reveal any
underlying data issue which is driving the process
overhead.
◦ Identify known data quality issues and refer them
for additional discussion and analysis.
◦ Awareness of existing data quality issues will allow
Activity 4: for more accurate estimates regarding the scope
and effort required to ready data for the new
Data Quality environment.
Discussion
Ø Keep data issues, concerns and standards in mind
when discussing processes. It may not be the
process. It may be the data.

COPYRIGHT©. TOUS DROITS RÉSERVÉS. PAR MICKAEL QUESNOT 8

 Activity 5: Operational Process
Reporting

Objective: Identify current operational reports For each Report identified:

you can’t leave without in the current
process/solution
Name and describe the objective
Describe impact to efficiency, effectiveness, or control
Hypothesize as to value and applicability of the practice if
adopted on an enterprise basis

COPYRIGHT©. TOUS DROITS RÉSERVÉS. PAR MICKAEL QUESNOT 9

Address
Business
Deployment Specific additional questions based on the
process under discussion:
Plan Process
Cost Driver
Questions

COPYRIGHT©. TOUS DROITS RÉSERVÉS. PAR MICKAEL QUESNOT 10

Wrap-Up

REVIEW / CONFIRM KEY ACTION ITEMS FOR NEXT

FINDINGS SESSION / DAY

COPYRIGHT©. TOUS DROITS RÉSERVÉS. PAR MICKAEL QUESNOT 11

Level 2 Swimlanes

12
 Notes &/or Comments
Production Planning Swimlane

COPYRIGHT©. TOUS DROITS RÉSERVÉS. PAR MICKAEL QUESNOT

13
Level 3 Processes

14
 SCM – Supply Chain Planning
Level 2 Level 3

COPYRIGHT©. TOUS DROITS RÉSERVÉS. PAR MICKAEL QUESNOT 15

 SCM Master Data
Level 2 Level 3

COPYRIGHT©. TOUS DROITS RÉSERVÉS. PAR MICKAEL QUESNOT 16

Process Integration
Diagrams

17
Process Integration Breakouts -
Purpose & Guidelines
Purpose of the Breakouts
To understand the key changes and
impacts to key cross-process “hand-offs”
To provide input in determining the effort
and cost of implementing the solution
COPYRIGHT©. TOUS DROITS RÉSERVÉS. PAR MICKAEL QUESNOT
Guidelines
Remember: The breakouts are not
intended to identify all issues or
determine solutions – that will come in
the Blueprint
Leave time to cover all topics
Be willing to put items in the “parking lot”
18
 Process Breakout Topics

◦ Review Wrap-Up Items / Identify Cross Process Hot

Zones
◦ Structured Process Review of SAP Cross-Process
Topics
Process ◦ Discuss “As Is” Process Variability
Integration ◦ Discuss Relevant Master Data Topics
Breakouts
◦ Wrap-Up: Action Items for Next Session, Review
Findings

COPYRIGHT©. TOUS DROITS RÉSERVÉS. PAR MICKAEL QUESNOT 19

SOM & PP Integration

COPYRIGHT©. TOUS DROITS RÉSERVÉS. PAR MICKAEL QUESNOT 20

PP & SCM Integration

COPYRIGHT©. TOUS DROITS RÉSERVÉS. PAR MICKAEL QUESNOT 21