8
Blueprint Approach Dilip Sadh

33472151 dilip-sadh-blueprint-approach

Embed Size (px)

DESCRIPTION

 

Citation preview

  • 1. Blueprint ApproachDilip Sadh

2. Contents1. Introduction Objectives & Expectations Guiding Principals2. Review GBM Process flow diagrams Business documents3. Configuration Questions Data required for configuration4. Review GAPS Review identified GAPs Gather data on new GAPs Legal and localization Requirements5. Gaps & Disposition6. Wrap up 3. Overall ApproachBlueprint Plan Workshop Prep Workshop Execution Gaps ConfirmationWorkshop Prep:Normative future state process flows are developed using SAP and GBMNormative Business Blueprint Questions are developed taking inputs from GBM (Global Business Model) and Key-S&N resourcesWorkshop Presentation Material highlighting relevant SAP functionality is show-casedWorkshop Agenda / Meeting Minutes document is prepared including a detailed workshop schedule by process areaWorkshop Execution:Normative content (future state process flows and Business blueprint Questions) reviewed and discussed with theworkshop participants.A Design by Acception approach pursued to make decisions on open itemsA formal list of Open Issues and Gaps captured and published along with meeting minutesA list of requirements and settings to set up the new plant and companyFinalized Process flows and Business Blueprint publishedGaps Confirmation:Functionality Gaps compiled across all process areas compiled for disposition as custom development (Reports,Interfaces, Extensions and Forms) pursuant to Management Approval.A formal Blueprint Validation exercise and confirm business sign-off and approval to move forward. 4. Overall ApproachProcess DecompositionsThe critical 5 to 10 business processes that: Defines the entire value chain,Process Scenarios (5 10 E2E) Crosses functional, geographic, company boundaries (Source to Pay) Integrates upstream and downstream activities Have measurable outcomesWorkshops Executed at this level V Typically 5 to 10 major process within the E2E process that: Process Can be subdivided into process steps assignable to Process Roles (Manage Direct Purchasing) Maintain discrete metrics unique to its specific activitiesVLogical groupings of business transactions:1. Finance to Manage E.g., Create, Change, Release order Process Step Must be uniquely assignable to a Role without separation of duties conflicts2. Source to Pay (Including WM) (Create Purchase Order Spot Buy)3. Order to Cash4. Plan to ProduceV5. Quality Management?Lowest level of work activity in Blueprinting: Transaction Individual SAP transactions (ME21N, ME22N, ME23N) Consists of one or more SAP entry screens 5. Workshop PreparationNormative Workshop Package Future State Process Flows: Future state process flows defined to the lowest process step level Future state process flows based on SAP and Capgemini best practices Normative inputs from GBM (Global Business Model) and key business experts Work process roles identified at the process step level Business Blueprint QA Document: Business Process Blueprint organized at the process level Normative business requirements captured in the blueprint document Normative Question-Answer to define the business blueprint in SAP Normative organizational construct captured at the process level Workshop Presentation: Formal workshop presentation that facilitates execution of the workshop. Key SAP capabilities that are relevant for the future state design are delineated. Critical Lead Practices relevant for the workshop topic are highlighted Workshop Agenda / Meeting Minutes Template: A consistent template used to describe the workshop agenda. Meeting invitees captured Known Issues, Operational Reporting needs and Gaps captured across the project 6. Workshop ExecutionDay-in-the Life Workshops will be executed at Process Level Workshop Participants are empowered to make decisions The following work products will be delivered in the specified sequence Confirm Workshop Attendance and review agenda using the Meeting minutes template Walks-through the Future State Process Flows from GBM (Global Business Model) Workshop presentation material is reviewed and key SAP functionality relevant for the workshop is reviewed (with optional live demos) Business blueprint Questions reviewed and inputs from Business team members solicited Gaps are captured and documented Review of open issues and gaps Publish Workshop minutes and finalized workshop package 7. Workshop ExecutionFinalized Workshop PackageFinalized Future State Process Flows: Future state process flows defined to the process step level reviewed and finalizedFinalized Business Blueprint QA Document: Finalized business blueprint document publishedPublish Workshop Meeting Minutes : Meeting minutes and summery information captured and published Final list of Issues, Operational Reporting needs and Gaps captured across the project published 8. Gaps & DispositionRICEFDisposition of Gaps identified including estimated for development for managementreview and approvalList of approved RICEF objects developedReports: Operational Reports to be generated from ECCInterfaces: Interfaces with systems that exchange information with SAPConversion: Master and Transaction data conversion needs identifiedEnhancements: Enhancements to the core SAP solutionForms: Outputs from the SAP solution