Troubleshooting Your Domino HTTP Server Crashes and Hangs

Troubleshooting Your Domino HTTP Server Crashes and Hangs

An A-Z guide to planning, managing, and executing an SAP NetWeaver BI project - Part 2 Dr. Bjarne Berg MyITgroup 2007 Wellesley Information Services. All rights reserved. What Weve Covered So Far (in Part 1) Writing your SAP BW business case Defining the scope of your implementation Writing a milestone plan Developing your staffing plan Budgeting On-boarding and training Writing your workplan Monitoring the progress of your project Monitoring quality / instituting a formal approval process Why you need an SAP BW user acceptance group 2 What Well Cover Now (In Part 2) Final Preparatory steps Methodology details Lessons learned Requirements and approvals The Blueprinting Phase The Realization Phase The Implementation Phase

Wrap-up 3 What Well Cover Final Preparatory steps Methodology Lessons learned Requirements and approvals The Blueprinting Phase The Realization Phase The Implementation Phase Wrap-up 4 Project Preparation: Some Key Observations Project Projectcharter: charter:Represents Representsan anagreement agreement on, on,and andcommitment commitmentto, to,the thedeliverables deliverablesofofthe the project, project,as aswell wellas asthe thetime timeconstraints, constraints, resources, resources,standards, standards,and andbudget

budgetofofthe the project. project. Project Projectplan: plan:This Thisisisthe thefirst firstcut. cut. ItItfocuses focuses on onmilestones milestonesand andwork workpackages. packages. Core Activities 1.1 Initial Project Planning 1.2 Project Procedures 1.3 Training Preparation 1.4 Project Kickoff 1.5 Technical Requirements Planning 1.6 Quality Check Project Preparation Scope: Scope:Sets Setsthe theinitial initialdefinition definitionofofthe theproject. project. Project Projectteam teamorganization: organization:Sets Setsthe thewho whoofof the theproject. project. ItItdecides decideswho whowill willbe beinvolved, involved, and what their goal is. and what their goal is.

Standards Standardsand andprocedures: procedures:Sets Setsthe thewhy why and andhow howofofthe theproject. project. Standardizes Standardizeshow how meetings meetingsare arerun, run,how howdocuments documentsare arehandled, handled, etc. soeveryone everyoneunderstands understandswhat whatisisgoing goingon. on. This is what we covered in Part 1 Note Source: Pauline Woods-Wilson 5 What is ASAP? Examples for Accelerators: Project Plan, Estimating Design Strategies, Scope Definition Documentation, Issues Db Fill Fillin inthe theBlank Blank Versus Versus Start Startfrom fromScratch

Scratch Workshop Agenda Questionnaires End-User Procedures Test Plans Technical Procedures Made Easy guidebooks (printout, data transfer, system administration) 6 The ASAP Approach (from Part-1) Integration Testing Create Technical specs Create Functional specs No System Testing Complete? No Yes Unit Testing Complete? Yes Configuration Yes Peer Review No Approved? Peer Review Yes No Complete? No Yes Approved?

Structured walkthrough No Complete? Yes Structured walkthrough 7 Alternative Approach For Smaller Projects (I.E. 1st Go-live) Keep the scope focused and use a simple approach: Activate standard content Request for modifications Inscope? Yes Make enhancements No Load infocube User acceptance session Test In-future scope? No Review data quality issues Create 2-3 sample queries Deploy Rejection No functional or technical specs are used in this approach. The user acceptance session is used to refine requirements

8 Critical Success Factors for SAP BW Projects Individual Organizational Technological Methodology The best people End users on the team Platform sizing Proper scope Backfilling Communication with users Testing tools Leadership and commitment Single location Documentation and training internal Integration testing before releasing changes Budget for consulting and training Good SAP consultants Breadth and depth of training Do not modify code Overseas contacts Source: Lee Schlenker

Note These are lessons learned the hard way Dont re-invent the wheel--learn from others. 9 SAP Solution Manager Upgrade Projects e-Learning New in 2004 Landscape Reporting Test Organizer Customizing Synchronization Support Desk T ool Content Source: SAP AG Services Best Practice Documents Roadmaps Service Delivery Platform Solution Monitoring Service Level Reporting Implementation Platform Implementation Content Change Request Management Gatew ay to SAP SAP Support Was added in 2004 10

SAP BI Best Practices some hints This tool is still being enhanced, but has several BI-specific project accelerators that you wont find in SAP Solution Manager. It has been available since March 2003. The current release is as of August 2006 (v1.7). You can access SAP BI Best Practices for BI at: 11 Option Workplans Based on Deliverables The best practice documents are organized around scenarios, which simplify the collection of tools Source: SAP Jan, 2007 12 SAP BI Best Practices What Versions Does It Support? SAP BI 7.0 The SAP Best Practices tool was developed for SAP BW 3.5, and later updated for SAP BI 7.0. SAP App. Compon ent Software Component Release Level Highest Support Package SAP BW SAP_BASIS

700 0007 SAPKA70007 SAP_ABA 700 0007 SAPKA70007 SAP_BW 700 0007 SAPKW70007 PI_BASIS 2005_1_700 0007 SAPKIPYJ77 BI_CONT 702 0004 SAPKIBIHP4 SCM 500 0002 SAPKY50002 SAP_BW 700 0005 SAPKW70005 SAP_BASIS

700 0005 SAPKB70005 SAP_ABA 700 0009 SAPKA70005 SAP_BASIS 700 0007 SAPKA70007 SAP_ABA 700 0007 SAPKA70007 SAP_APPL 600 0004 SAPKH60004 PI_BASIS 2005_1_700 0007 SAPKIPYJ77 SAP_BASIS 700 0007 SAPKA70007

SAP_ABA 700 0007 SAPKA70007 BBPCRM 500 0004 SAPKU50004 PI_BASIS 2005_1_700 0007 SAPKIPYJ77 SAP SCM SAP BW 3.5 mySAP Application Component SAP BW Software Component Release Level Highest Support Package SAP_BASIS 640 0004 SAPKB64004 SAP_ABA 640 0004

SAPKA64004 SAP_BW 350 0004 SAPKW35004 PI_BASIS 2004_1_640 0004 SAPKIPYI64 BI_CONT 352 0002 SAPKIBIEP2 Source: SAP Jan, 2007 SAP ERP 2005 SAP CRM While Whileinstall installrecommendations recommendationsare arebased basedon onSAP SAPBW BW3.5/ 3.5/or orBI BI7.0, 7.0,most most management managementtools, tools,accelerators, accelerators,and andthe thesample samplework

workplan planare arenot notversion-specific version-specific 13 Rapid Application Development (RAD) Be flexible and consider using a RAD (Rapid Application development) approach for the initial information requirements gathering task. Typical ways to conduct this include: Ask for 1-2 days of uninterrupted time, and provide lunch on-site Invite power users, casual users, today's report writers, and managers Remove cell phones, PDA, pagers, and email access Keep a rapid pace, and a manageable number of attendees (no more than 20) Focus on shared information needs, and conduct multiple sessions if needed Don't get trapped in details; give people a chance to provide feedback in writing and follow-up later with individuals You can use the session as an information sharing event, and give a brief overview of what you are attempting to do 14 What Well Cover Final Preparatory steps The Blueprinting Phase

Leveraging the standard content Modeling your solution Deliverables The Realization Phase The Implementation Phase Wrap-up 15 A Process Look at Getting Functional Specifications Create a contact group and contact list for business input and requirements Name JoeJones JosephJones JoeJones JoeJones JoeJones JosephJones JoeJones JoeJones JoeJones JosephJones JoeJones JosephJones JoeJones Organization MYORG Ltd YourORG Ltd MYORG Ltd MYORG Ltd MYORG Ltd YourORG Ltd MYORG Ltd MYORG Ltd MYORG Ltd YourORG Ltd MYORG Ltd YourORG Ltd MYORG Ltd Phone Number 918-123-1234 918-123-1234 123-123-1234 918-123-1234 918-123-1238 918-123-1239 918-123-1234

918-123-1234 918-123-1234 918-123-1234 918-123-1234 918-123-1234 123-123-1234 Don't Forget Create a tool to collect info requests and business input Gather Disposition information the info. requests to using the tool BW or R/3 Consolidate Build storage requirements objects and load programs and write functional specs Construct reports and navigation features starts by documentation tool for TeamTeam starts byreviewing reviewing documentation tool for documentation completeness Revie w nrequi rements identify correspondi g Data M odeland (InfoCube/ODS) D1 D1aa true No Communicate to

Is report Is this bus. leader documentation complete? Yes reporting need Yes D4report No D2 D2.5 exist No Significant D3 Is system the this No Does anIs Intraday in -"indatamodels scope" resource report? Infocube/ODS ofnumber users? No Request additional intensive? No input frommember Business Team Yes Yes R/3 is selected as Yes Reporting Tool R/3 is selected selected as as and is A2 Reporting Tool indocumented doc. tool Total Cost of and documented

Ownership Responsibl e Analysis Team member acqui r es/documents additional information R/3 is selected as Communicate Reporting Tool D8cost Noand dispositionfinal Iseffective? BW indocumented doc. tool Yes BW is selected as D5 Communicate Reporting Tool Does Yes disposition final documented Yes Standard R/3 No in and the documentation tool content exist? BW is selected R/3D9Tool D6 reporting tool andas Change Selection Does Request is subm

itted if Process Communicate Is itD7 less to the scope changed Standard BW No expensive disposition final content create No exist? R/3? in Standard Report Yes as Yes ABAP/R/3QueryWriter BW is selected BW is selected as Communicate R/3 is selected as Reporting Other Reporting Tool and Reporting Tool Tool and disposition finalCustom documented documented tool in doc. andindocumented tool in doc. doc. tool A3 Consolidation Sub - ifReport & eliProcess m inate appropriate (winnowing) Communicate disposition final Communicate disposition final Communicate disposition final R/3 team make final disposition BW Team to forward detailed

based on selecompleted cted BW - Reporting or R/3 Toolreport specifications A4reports Baseline There is more than one way to collect this information. However, a formal process should exist to capture requirements & communicate what is being developed. We will now examine the most common form of RAD (Rapid Application Development). 16 Getting the Functional Specifications Note Best Practice Avoid taking a total inventory of all reports in the organization. The "top-5" (most used) sales, distribution, inventory etc. reports from each department will cover the vast majority of the reporting needs. A single SAP BW "report" may satisfy dozens of today's static reports. It is therefore impossible to map each individual legacy report to a single BW report. Avoid attempting to replicate each report based on what you might have in place today. Accept new ways of accessing data. 17 Getting the Functional Specifications (cont.) Create a form that captures the business core requirements in a structured format Tip Create a simple Information Request Form, and use it to gather the core relevant information about each report being requested by the business community. This should include at least the following fields: - Contact info about the requestor

- Department - Name of report - Purpose of report - Description of report - Type of users (mgr./analyst/casual) - Number of users expected - Frequency of report (daily/monthly) - Data currency (yesterday/today) - Security requirements - How is this reporting done today - Comments 18 Sample Info Request Form: Document requirements in a standardized format Prioritize requirements Consolidate requirements Support follow-up discussions and reviews. Tool P1 19 of 2 Sample Info Request Form: Other uses: Post the form on the Intranet, thereby giving stakeholders an easy way to communicate with the project team

Use the Comment section for security requirements, or add a separate section for this. Note the section for dispositioning the requirement Tool P2 20 of 2 An Example 21 An Example 22 Consider Multiple Ways of Displaying the Same Data!! Deliver reports in a consistent manner to users (one version of the "truth"), but use different mechanisms to do so Managers and executives tends to prefer simple and directed interfaces Casual users tends to prefer predictable structured access to data Analysts and power users tend to prefer high flexibility and unstructured access to data KPI & Scorecard Formatted Simple Easy to view Limited nav Aggregates Flat Reporting Formatted

Print Form based Static Predictable access OLAP Reporting Drill Down OR OR Slice and Dice Analyse Data Mining Search and discover Don't underestimate users need to access the information in various ways. 23 Blueprinting Phase: Some Key Observations Getting Gettingthe theright rightrequirements: requirements: Finding Findingout outthe thedetailed detailedfunctional functional specs specsofofwhat whatusers usersreally reallyneed needand and not notjust justwhat whatthey theywant. want. Deciding Decidingwhat whatwill willbe bedeveloped developedinin SAP SAPBW BWand

andwhat whatwill willbe bemaintained maintained as asR/3 R/3reports. reports. Core Activities 2.1 Project Management Business Blueprint 2.2 Organizational Change Management 2.3 Project Team Training Business Blueprint 2.4 Develop System Environment 2.5 Organizational Structure Definition 2.6 Business Process Definition 2.7 Quality Check Business Blueprint Map Mapthe thefunctional functionalrequirements requirementstotothe the standard standardcontent, content,and andsee seewhat whatcan can be beleveraged leveragedand andwhat whatneeds needstotobe be extended. extended. Create Createdetailed detailedtechnical technical specifications specificationsand anddesigns designsofof infocubes, infocubes,masterdata, masterdata,ODSs, ODSs,and and high-level

high-levelarchitectural architecturaldesigns. designs. Create Createuser useracceptance acceptancegroup(s), group(s),and and have havethem themreview reviewand andgive givefeedback feedback on onthe thesystem systemas asititisisdeveloped. developed. 24 Report Dispositioning: What Goes in BW, and What Stays in R/3? There are many tools that can report on R/3 data, and you might have static reports that truly belong in R/3, which would not be cost effective to move to SAP BW Make cost-effective decisions; just because the report is not in SAP BW does not mean it cannot be added to a Portal or viewed on the Web Not all reports belong in SAP BW; avoid using SAP BW as a "dumping group" You need to make conscious decisions on what reporting needs you are going to meet, and how you will accomplish this Warning We will now take a look at an approach to formal report dispositioning that has been used by a few companies. 25 Key Questions for Report Dispositioning

Is this really a reporting need, or a "want"? Is the data going to be in SAP BW at a frequency that solves the user's request (e.g., intraday reporting)? Is the data needed for this report already in our SAP BW scope? Is there already a report available in R/3? Does standard BW content exist? Is it less expensive to create the report in R/3? Are there a significant number of users? Is the reporting need resource-intensive? Is SAP BW cost effective in the long run (ownership)? 26 Team starts by reviewing documentation tool for documentation completeness cu Review requirements and identify corresponding Data Model (InfoCube/ODS) D1 Is report documentation complete? Yes Tool D1a Is this a true

reporting need No An example of how to decide which reports should be in R/3 or the legacy system (refer to printed version) Communicate to bus. leader Yes No D2 Is this an Intraday report? Request additional input from Business Team member No D2.5 Does data exist in "in-scope" models Infocube/ODS Yes Yes Yes D6 Does Standard BW content exist? Yes BW is selected as Reporting Tool and documented in doc. tool Communicate final disposition No No

D7 Is it less expensive to create in R/3? BW is selected as Reporting Tool and documented in the documentation tool Communicate final disposition D8 Is BW cost effective? Communicate final disposition R/3 is selected as Reporting Tool and documented in doc. tool Communicate final disposition Yes D9 R/3 Tool Selection Process BW is selected as reporting tool and Change Request is submitted if the scope changed No Standard R/3 Yes R/3 is selected as Reporting Tool and documented in doc. tool No No

R/3 is selected as Reporting Tool and documented in doc. tool Yes A2 Total Cost of Ownership Analysis Communicate final disposition D5 Does Standard R/3 content exist? D4 Is the report system resource intensive? No Yes R/3 is selected as Reporting Tool and documented Responsible Team member acquires/documents additional information No D3 Significant number of users? BW is selected as Reporting Tool and documented in doc. tool Communicate final disposition

Communicate final disposition ABAP/ Custom Report Writer Query Other A3 Sub-Process Report Consolidation & eliminate if appropriate (winnowing) R/3 team make final disposition BW Team to forward completed detailed report specifications based on selected Reporting Tool - BW or R/3 A4 Baseline reports 27 Now That You Have Identified the In-Scope Reports, Whats Next? Obtain a copy of each of the current reports that are inscope (not all report across your organization) Great Feature Legacy reports are often a great way to document the data needs They can be used to illustrate how data is currently being summarized and viewed Consolidate the requirements, and look for "low-hanging fruit" Create a physical folder with paper copies of these legacy reports Make sure that the development team has access to them -- this will reduce the time spent in meetings with the business community + + = Many requirements can be met by a single SAP BW report

28 The Blueprinting Phase: Leveraging Standard Content As a guiding principle, map requirements to standard content before customizing Mostly standard storage objects Some customization Highly customized storage objects 31% 36% However, youll probably also have external data sources that require custom ODSs and InfoCubes Customizing lower level objects will cause higher level standard objects to not work, unless you are willing to customize these also. 33% An example from a large manufacturing company BW Content available (3.5.1) (3.5.1): Cockpits Workbooks Queries Roles MultiCubes

??? 1,979 3,299 861 121 InfoCube 605 ODS objects 349 InfoObjects 11,772 29 The Blueprinting Phase: Model Your Solution 1. Create a model based on pre-delivered SAP BW content 2. Map your data requirements to the delivered content, and identify gaps 3. Identify where the data gaps are going to be sourced from Material Material number Material entered Material group Item category Product hierarchy EAN/UPC Storage Requirements Plant Shipping/receiving point Currency Key Unit of Measure Base unit of measure Sales unit of measure Volume unit of measure Weight unit of measure Billing Customer + Unit Logistics Sold-to Ship-to Bill-to Payer Customer class Customer group

~ Customer country ~ Customer region ~ Customer postal code ~ Customer industry code 1 End user Number of billing documents Number biling line items Billed item quantity Net weight Subtotal 1 Subtotal 2 Subtotal 3 Subtotal 4 Subtotal 5 Subtotal 6 Subtotal A Net value Cost Tax amount Volume Organization Standard content Company code Division Distribution channel Sales organization Sales group Map functional requirements to the standard content before you make enhancements Personnel Sales rep number Accounting Cost center Profit center Controlling area Account assignment group Billing information Billing document Billing item Billing type Billing category Billing date Creation date Cancel indicator Output medium ~ Batch billing indicator

Debit/credit reason code Biling category Reference document Payment terms Cancelled billing document Divison for the order header Pricing procedure Document details Sales order document type Sales deal Sales docuement Time Calendar Calendar Calendar Calendar year month week day Storage Objects LEGEND Delivered in standard extractors Delivered in LO extractor Not in delivered Content -but in R-3 30 Standard Content Vs. Customization All functional areas are not equally supported by strong standard SAP BW business content. Some areas have much you can leverage, others will require significant enhancement to meet your requirements Approximate Usage of Standard Content BW 3.5 (percentage of overall development effort) 100 80 The differences are often due to customization on the R/3-side by companies and/or industry solutions. 60 40

20 0 * Rapidly improving content 31 What Well Cover Final Preparatory steps The Blueprinting Phase The Realization Phase Building ODSs and InfoCubes Planning, Managing and executing system test Planning, Managing and executing integration and performance test Issue resolution, logs, sign-off and approvals The Implementation Phase Wrap-up 32 Realization Phase: Some Key Observations Core Activities 3.1 Project Management Realization 3.2 Organizational Change Management 3.3 Training Realization 3.4 Baseline Configuration and reviews 3.5 System Management 3.6 Final Configuration and Confirmation 3.7 Prepare & Coordinate interface development 3.8 Develop Data Conversion Programs (if any) 3.9 Develop Queries 3.10 Develop User interface enhancements 3.11 Determine additional reporting requirements 3.12 Create structured reports 3.13 Establish Authorization Concept 3.14 Establish Data Archiving plan (if applicable) Development DevelopmentPrograms: Programs:Provide Provide details

of added programming details of added programming structures structures End EndUser UserTraining TrainingMaterial Material Configuration Configurationand andTesting TestingPlans: Plans: Define how the configuration Define how the configurationwill willbe be implemented and how it will be implemented and how it will be tested tested Source: Pauline Woods-Wilson 3.15 Final Integration Test 3.16 Quality Check Realization 33 Building ODSs and InfoCubes TIPS 1 Review the functional requirements and 6 Do not allow exceptions to your naming conventions technical design 2 Make sure you have established Data 7 Make sure that putting out fires does not Stewards for master data, and assign take precedence, becoming the master data to specific developers default architecture and standard. 3 Have your ETL developers work 8 Try new ideas in a sandbox environment , for the individual who is responsible and dont contaminate the development environment. for creating process chains (organizationally)

4 Avoid nested ODS layers, and keep the 9 Keep details for multi-use in the ODS and architecture as pristine as possible do not design the ODS based on the needs of a single infoCube. 5 Make your transformations part of 10 Developers must unit test all of their update rules into infocubes if you need work and personally sign-off on their to be able to reconcile to the source storage object. system. Keep the details in the ODS. 34 Consider Upgrading to SAP BI in SAP NetWeaver 2004s On a typical SAP BW project, 40-60% of project effort will be spent on data integration, transformation, and loads BI in SAP NetWeaver 2004 has a new GUI to help you write transformations, potentially saving you a lot of time! Source SAP AG 35 The SAP BW Test Methodology Methodology used for System and Integration tests Test Strategy Test Plan Test Execution Problem Resolution SAP R/3 and BW testing is not different from a methodology standpoint, but the execution is. 36 System Test: Planning Tasks\Dates December 2003 January 2004 Identify People for Testing February 2004 1-Mar 8-Mar 15-Mar 22-Mar 29-Mar 5-Apr

s, a g r o f p to sto e m i t o n "There's dy late" rea we're al Schedule Facilities Prioritize Test Areas (Queries) Send out Meeting Notice Execute System Test Document Results Problem Resolution Activities Tasks 1 2 3 4 5 Create test script Identify roles to be used Documentation on using test tools Procedure for documenting test results Training sessions for using test scripts 6 7 8 9 Identify key contacts Communicate about transports Arrange time for progress control Schedule facilities 11 12 1

10 2 3 9 Business analysts are responsible for planning, coordinating, and executing the system testing of queries. 4 8 7 6 5 Timing 37 Deliver Cost and Profitability Order Manufacturing Plan and scheduling Demand planning Source Environment preparation 4/2 4/1 3/31 3/30 3/29 3/28 3/27 3/26 3/25 3/24 3/23

3/22 3/21 3/20 3/19 3/18 3/17 3/16 3/15 3/14 3/13 3/12 3/11 3/10 3/9 3/8 3/7 3/6 3/5 3/4 3/3 3/2 3/1 System Test Scheduling: Example Resolving outstanding issues and retesting = Morning session 8:30 - noon = Evening session 12:30 - 5:00

Each team has dedicated time in the test room Provide food and snacks At least 2 testers (preferably 3) should be assigned to test each query All test results must be logged 38 System Test: Checklist Preparations People Data source/cubes/ODS/queries prioritized for testing Queries developed and available in the SAP BW test environment Track specific test plans created using test template Test cases written Individuals (testers) perform the identified tests Testers invited to complete SAP BW on-line training Availability of testers confirmed Security roles tested and user IDs for testers have been created Logistics Testers familiarized with test results recording tools Identify test location and verify resources Rooms, computers, sapgui, network connections, phone, etc.

Plan for problem resolution 39 Integration Test: Planning Tasks\Dates March 2004 29-Mar 5-Apr 12-Apr 19-Apr 26-Apr 3-May 10-May 17-May Identify People for Testing Schedule Facilities Prioritize Test Areas (Queries) Send out Meeting Notice Execute System Test Document Results Problem Resolution Progress meeting Held daily to monitor progress and resolve common issues Attendees: Business analysts, back-end developers, query developers, test coordinator, and Test Problem Report (TPR) administrator Purpose: Discuss common issues, monitor progress, discuss plan changes Duration: 30 minutes 40 Performance Testing Performance test execution Identify queries to be performance tuned, and determine cutoff load for load test e.g. 40% of actual users (not named) Schedule queries to run in background, and execute each query while load scripts are running to simulate real users Monitor your system continuously, and attempt tuning at the query level

Perform analysis based on benchmarks, and build aggregates and/or indexes Record findings in a formal tracking tool available to everyone Meet with developers daily to discuss issues Problem resolution: Look at the new BI Accelerator in SAP BI 7.0 for improved performance !!! 41 Source: Alexander Peter, SAP AG Test Signoffs Signoff procedure Document test feedback and update logs Review open issues Prioritize outstanding issues Agree on scope decisions and resolutions Obtain approvals from business representatives or steering committee 42 What Well Cover Final Preparatory steps The Blueprinting Phase The Realization Phase The Implementation Phase Executing cut-over to production Conducting end-user and power user training Establishing end-user support organization Post-implementation review and next steps Wrap-up

43 Final Preparation Phase: Some Key Observations The TheCutover CutoverPlan Planand andthe theTechnical Technical Operations Manual describe Operations Manual describethe thedetails details on onhow howtotomove movetotothe theproduction production environment and go live environment and go live Stress Stress&&Volume VolumeTests Testsconfirm confirmthe the production hardwares capabilities production hardwares capabilities The TheEnd EndUser UserTraining Trainingdocument document describes the delivery of the describes the delivery of thenecessary necessary levels levelsofofSAP SAPtraining trainingprior priortotogoing

goinglive live Core Activities Source: Pauline Woods-Wilson 4.1 Project Management Final Preparation 4.2 Training Final Preparation 4.3 Acceptance Testing 4.4 System Management 4.5 Detailed Project Planning 4.6 Cutover 4.7 Quality Check Final Preparation 44 Conducting End-User and Power User Training Web-based All users Training Tutorials Instructor-led On-site Power users Executives Vendor-based Developers Support staff 1) Create, or buy, an on-line help and training system. Make sure you use many images and links. 2) Consider using animations to demonstrate 45 complicated tasks as well. Establishing End-User Support Organization Getting Power Users involved early is important to the overall success of a Data Warehousing project To help support businesses that have already gone live, a strong local community of ambassadors is needed. Without them, ongoing projects can get bogged down with basic report support and enhancement requests. 46 Go-Live: Some Key Observations

The Thelast lastdeliverable deliverablefor forthe theimplementation implementation ensures high system performance ensures high system performancethrough through monitoring and feedback monitoring and feedback Source: Pauline Woods-Wilson We Weneed needtotoexecute executeissue issueresolution resolutionplans plans and contingency plans and contingency plans Core Activities 5.1 Production Support 5.2 Project End AAlessons lessonslearned learnedsession sessionshould shouldbe be held at the end of the project to assure held at the end of the project to assure organizational organizationalawareness awarenessand andeducation

education The Thesupport supportorganization organizationwill willtake takeover overthe the system after a pre-determined time period. system after a pre-determined time period. Some Someteam teammembers membersmay maytransition transitioninto intotheir their new roles as support staff new roles as support staff This Thisisisaacritical criticaltime timewhen whenaaSWAT SWATteam team that thatquickly quicklyaddresses addressesuser userconcerns concernscan can make all the difference in how the system make all the difference in how the systemisis received receivedamong

amongthe theusers users 47 Tracking Load Performance During the first 6 weeks after each go-live, you should formally track the load performance by process chain to see if you have any systematic issues Load performance rate 100% 90% 80% 70% 60% 50% 40% 30% 20% 10% 3/ 20 /2 3/ 005 22 /2 3/ 005 24 /2 3/ 005 26 /2 3/ 005 28 /2 3/ 005 30 /2 0 4/ 05 1/ 20 4/ 05 3/ 20 4/ 05 5/ 20 4/ 05 7/

20 4/ 05 9/ 2 4/ 005 11 /2 4/ 005 13 /2 4/ 005 15 /2 4/ 005 17 /2 4/ 005 19 /2 4/ 005 21 /2 4/ 005 23 /2 4/ 005 25 /2 4/ 005 27 /2 4/ 005 29 /2 0 5/ 05 1/ 20 5/ 05 3/ 20 5/ 05 5/ 20 5/ 05 7/ 20 05 0% It is also a great way to document your success!! 48 Tracking Load Performance (cont.)

A stabilization period after each go-live is normal, until the new process chains has been tuned in the production box This is a time when active monitoring of process chains should occur Production Performance Areas of BW Data Load Issues Nov. 1st through Dec. 15th Demand Planning 7 Transaction global 6 Source Purchase Orders Roughcut 4 Material Movements MD - Bev. Packaging 3 Master data 2 Hierarchies 1 12/15/04 12/14/04 12/13/04 12/12/04 12/11/04 12/9/04 12/10/04 12/8/04

12/7/04 12/6/04 12/5/04 12/4/04 12/3/04 12/2/04 12/1/04 11/30/04 11/29/04 11/28/04 11/27/04 11/26/04 11/25/04 11/24/04 11/23/04 11/22/04 11/21/04 11/20/04 11/19/04 11/18/04 11/17/04 11/16/04 11/15/04 11/14/04 11/13/04 11/12/04 11/11/04

11/9/04 11/10/04 11/8/04 11/7/04 11/6/04 11/5/04 11/4/04 11/3/04 0 11/2/04 Greycon 11/1/04 Number of Issues 5 CO -line items 49 Go-live: Post-Implementation Review Alignment Are we doing the right things? Are we doing them the right way? Integration Benefits Are we getting the benefits? Are we getting them done well? Capability/Efficiency The Information Paradox: John Thorp 50

What Well Cover Final Preparatory steps The Blueprinting Phase The Realization Phase The Implementation Phase Wrap-up 51 Resources a) Rapid Development by Steve McConnell Paperback: 680 pages ; Publisher: Microsoft Press; ISBN: 1556159005 b) Start to Finish Guide to IT Project Management by Jeremy Kadlec Digital: 109 pages. Publisher: NetImpress; ISBN: B0000W86H2 Download it at: c) Dr. Bjarne Berg Home page ( 52 7 Key Points to Take Home Keep the team relatively small & focused Size your project based on your teams experience and skills, in addition to scope Make the implementations interactive instead of Big-Bang Follow a proven methodology

Dont cram all of your reports into BW (some belong in R/3) Track quality, and create a formal approval process Involve power users and ambassadors in the development project 53 Your Turn!!! How to contact me: [email protected] 54

Recently Viewed Presentations

  • Living Psychology by Karen Huffman

    Living Psychology by Karen Huffman

    Title: Living Psychology by Karen Huffman Author: JPhillips Last modified by: Lisa Raskin Created Date: 4/12/2011 2:51:01 PM Document presentation format
  • Presentation Name

    Presentation Name

    Draw a Lewis Structure for CS2 Periodic Table Formal Charges and Oxidation Numbers Molecular Geometry Molecular Geometry for Propane, 1-Propanol, and Propene Hybridization and Bond Types for Propane, 1-Propanol, and Propene Hybrid Orbital Geometry
  • Lecture: 3 - Stock and Bond Valuation How

    Lecture: 3 - Stock and Bond Valuation How

    Maturity - length of time until Par value is paid off Lecture: 3 - Stock and Bond Valuation Bond Valuation "A Bond is an Annuity Plus a Single Face Value Payment" Annual Coupon Lecture 3 - Stock and Bond Valuation...
  • CCHAP Practice Managers Meeting Telehealth Tuesday March 11th

    CCHAP Practice Managers Meeting Telehealth Tuesday March 11th

    Reduce travel and expense for patients and families. Quality. Decrease response / wait times. Increased quality of care in geographic areas with lack of expertise. Medical Staff Satisfaction. Decreased travel / "burnout" Coordinated care. Support for community providers. Financial &...


    I will copy these for our Thinking Skills Folder so everyone can share our BRILLIANT ideas. HAVE FUN! How does it all fit together? Bloom's Revised Taxonomy Creating Green Hat, Construction Key, SCAMPER, Ridiculous Key, Combination Key, Invention Key Evaluating...
  • 1920-40 - Point Loma High School

    1920-40 - Point Loma High School

    The destroyer Greer was attacked by a German submarine - Roosevelt ordered American ships to shoot any German or Italian ships Pearl Harbor (1941) In September 1940 Germany, Italy, and Japan signed the Tripartite Pact - each nation promised to...
  • Lateral and Surface Area of Solid Figures

    Lateral and Surface Area of Solid Figures

    Lateral vs Surface Area . Lateral Area: The area of the sides of a three-dimensional geometric figure. Surface Area: The . total area . of the surface of a three-dimensional object.
  • Sports Nutrition KELSEY JOHNSON Standard Football Nutrition Recommendations

    Sports Nutrition KELSEY JOHNSON Standard Football Nutrition Recommendations

    2.7 grams of CHO per pound of body weight per day. 3.6-4.5 grams of CHO per pound of body weight during hard training. Pre-exercise Meal . Eat 3-4 hours before an event providing 200-350 grams of carbohydrates (4 g/kg). Avoid...