Sei sulla pagina 1di 17

Team Leads Meeting

May 19, 2008


Agenda

 Data Approach
 Execution of Business Blueprint
 Project Org Alignment
Data Approach
Data Approach for Project Lighthouse

Data Design ownership to reside within Process Tracks


List of all Master & Transactional objects - Satyam Data Lead
Data objects ownership assigned to
 Examples
 MM, BoM, Routings –P2F
 Customer Master – O2C
 Asset Master – Finance
 Vendor Master – P2P
Owner Functional team/resource drives design for the “object” across all tracks
Functional Specs created by the Functional Teams
 Data Input Template
 Includes Test Scripts for Unit Testing
Tech Specs & Development owned by Tech Team
 Data Migration Plan to be owned by the Data Leads
Data input template – Satyam Data Lead
Data Cleansing and formatting – SanDisk Data Lead
Data extraction – SanDisk Data Lead
Legacy system mapping – Coordinated by SanDisk Lead
Data Load into SAP – Satyam Data Lead
Data Conversion & Testing
Business Blueprint
Execution
Blueprint Planning
Status

Task Status
Track Specific Planning Complete – Satyam and SanDisk
Consolidation Round 1 05/20 : Satyam – slipped by 2 days
Consolidation Round 2 (final) 05/21 : Satyam + SanDisk
Preparatory Materials Templates 05/21 : Satyam
Resource Loading – Project Plan 05/27 : Satyam + SanDisk

The project plan will callout detailed schedules with a 2 - 4 week look ahead window.
Blueprint Execution Steps

 Identify Workshops as per SAP


Reference Structure
 Organizational Elements + General Settings
 Master Data
 Business Process
 Mapped to current Global High Level Design

 Run the Workshops


 Preparation
 Workshop
 Documentation
 Review & Sign-of
Blueprint Events
 Preparation
 Satyam
 Prepare a “straw man” of the process (PoC where applicable)
 Provide a Workshop Expectation Sheet
 Provide a Process/Object Specific Workshop Template
 SanDisk
 Pre-Read Global High-Level Design documents
 Block the time slot for availability
 Support for Logistics
 Workshop
 Satyam
 Conduct the workshop
 Document “As-Is”/“To-Be” Process
 SanDisk
 Participate in the Workshop – decision oriented
 Documentation
 Satyam
 Prepare sub-process wise Business Blueprint Document
 Review & Sign-of
 SanDisk & Satyam
 To review the Business Blueprint Document and sign-of
How Business Blueprinting Works

A Blueprint is designed in workshops


 Purpose
 Compare the Company’s processes to SAP Best Practices
and understand how the Company will work in the future.
 Process
 Start with pre-Blueprint knowledge
 Compare to SAP Best Practice Processes
 Understand gaps
 Brainstorm solutions
 Develop To Be processes
 Convert solutions to requirements
 Document
 Review & Sign-of
Business Blueprint Consists Of:
 Business Process Structure
 Process Documentation
 Organizational Documentation
 Master Data Documentation
Workshops Provide Inputs to the Blueprint
Document

Inputs
Inputs Workshop
Workshop Outputs
Outputs Integrated
Integrated Design
Design
Session
Session

 Position
Position papers
papers 
 Define
Define scope
scope 
 Decision
Decision log
log

 Report
Report inventory
inventory 
 Summarize
Summarize SAP SAP 
 Functional
Functional 
 Focus
Focus on
on integration
integration

 Dept
Dept roles
roles and
and best practices
best practices requirements
requirements listing
listing issues
issues
responsibilities
responsibilities 
 Define to-be
Define to-be process
process  Business process
 Business process 
 Resolve
Resolve outstanding
outstanding

 Forms,
Forms, templates,
templates, 
 Define
Define org
org change
change master
master list
list issues
issues
input
input screens used
screens used 
 Identify
Identify key
key business
business 
 Reports, interfaces,
Reports, interfaces, 
 Obtain validation
Obtain validation of
of

 Data
Data && data
data source
source decisions
decisions conversions,
conversions, forms,
forms, solution design
solution design
 enhancements
enhancements

 As-Is
As-Is business
business  Walk
Walk thru
thru application
application
process
process flows  
 System
System configuration
configuration
flows  Perform
Perform gap
gap analysis
analysis

 Pre-Blueprint  
 Testing
Testing requirements
requirements
Pre-Blueprint  Review
Review action
action items
items
workshop
workshop notes
notes and
and deliverables
deliverables 
 Open
Open issues
issues
Solution Manager
Central Tool For Blueprinting
Solution Manager Provides

Three structure levels (scenario, process, process step)


Best Practice standard SAP process documentation
Reuse (copy or reference) of other processes
Administrative project information
Process graphics – Exportable to Aris
Generation of Business Blueprint Word document

Solution Manager Documents can be exposed to the employee portal.


Some Templates
Document Template

Blueprint Workshop Document


Blueprint
Workshop Template

Business Blueprint Document


Business Blueprint
Template

Functional Specification Document


Functional
Specification Template

Technical Specification Document


Technical
Specification Template
Samples (flying height)

Business Blueprint Document


GL - Blueprint

Functional Specification Document


PO Form FS

Technical Specification Document


Technical
Specification
Organization Alignment
Org Alignment to Suit the Project Execution
Delta Changes

 AP -> Finance
 AR -> Finance
 Product Costing – Finance
 Inventory
 Accounting -> Finance
 Physical Inventory Management -> PTF
 Duty Calc + Trade Dox -> GTS

Potrebbero piacerti anche