SAP BI Process Review

- ABB

26th August 2013

Agenda
Objective
Current Process Understanding

Support
Development
Recommendation

Support Process
Development Process
Next Step To Summarize
Some Best Practices
Deliverables
Discussion

Objective
Objective to study the current process and provide
the best practice approach :

Support

Process

Documentation

Development

Process

Documentation

Support Process & Documentation

Understanding on Current Status
Task

Priority

Status

Induction Manual
Project Overview
Getting Started
About the Landscape / Application
Overview of the Functional Modules
Overview of the Service Level Agreement

Project Communication
Hands-off with Other Team
Project Reference Document
Communication process on Data Non-availability to Business User
Data Load Failure / Delay in Data Load

Data Refresh on Ad-hoc / Cut-Over

System Maintenance
High /
Available

Medium /
Partially Available

Low /
Not Available

Support Process & Documentation

Understanding on Current StatusContd
Task

Priority

Status

Alert Message
Data Load Success / Failure Message
Long Running Job

Escalation process
Data Non-availability / Data Load Failure
Governance and Control Process in Production environment
Process Chain Creation / Modification
Infopackage / DTP Creation / Modification (Used in Process Chain)
Data Load Monitoring Kit
Defined frequency wise list of Jobs
Process Chain Summary / Detail design document
Approval Process for Data Refresh on Cut-over / Ad-hoc
Review with Service Manager on pre-defined frequency
Incident Tracking

Available
/ High

Partially Available
/ Medium

Not Available
/ Low

Development Process & Documentation

Understanding on Current Status
Task

Priority

Status

Blueprint Document
Project Overview
About the Landscape / Application
Build Architecture
Authorization Strategy
Testing Strategy

Data Refresh Strategy

Data Retention Strategy
Development Guidelines
Transport Guidelines
Project Communication

Hands-off with Other Team

Project Reference Document
High /
Available

Medium /
Partially Available

Low /
Not Available

Development Process & Documentation

Understanding on Current StatusContd
Task

Priority

Status

Development Activity
Requirement Gathering
Technical Design
Technical Design Approval
Unit Testing
Peer Review

System Integration Testing SIT

User Integration Testing - UAT
KT with Support team - Overview
Deployment
Support

KT with Support Team & Sign-Off

Change Request Process
High /
Available

Medium /
Partially Available

Low /
Not Available

Recommendation on Support Process

System
Process Chain Re-Design
Alert Message on data load Failure / Success

Synchronizations of Process Chain across landscape

Proper classification on all Incident in HPSM tool
Track all Activity / Issues in Production through HPSM tool

Process
Detailed escalation Process
Support Activity Review Process
Governance and Control Process in Production Environment Changes
Communication Process on Data Non-availability to Business users

Documentation
Induction Manual
Inadequate Job Monitoring List Required for Day to Day Monitoring
Inadequate Process chain Design Support document for decision making

before doing any change to process chain

* Any Change Request handle by Support Team would have to follow the Development Guidelines

Recommendation on Development Process

System
Better Use of Technical Content
Review and Redesign the current model as applicable

Process
Setup Build Architecture
Setup Development standards
Setup Transport Strategy

Setup Data Refresh Strategy

Setup Data Retention Strategy
Development Review with architect
Setup Technical Design Approval Process

Better use of HPALM tool for tracking all UAT issues

KT with Support team before and after moving the changes to production

Documentation
Blueprint Document

Current Delivery Model & Implementation Status

Onsite

Delivery Model

Implementation Status - Sample

ABB Service Manager

Other Vendors

TCS Co-ordinator

Not followed
Naming
Standards
No Standard
Implementation
Approach

Offshore
TCS Co-ordinator

TCS Support &

Development Team
InfoObjects

Process Chain

Process Chain Design - Sample

US Baldor Installed Base

CN GPGDS Loads
CN, FI, US MM Source list loads
DE GPGDS loads
FI Transactional Loads
US GPGDS Loads
SD: Transactional Data Loading
0MAT_PLANT : Mat Plant Load for US only
ABB Finland Master Chain (AIM) New
Finland CA Master Data CHain
Finland MM Master data main
Finland MM Purchase requisitions 2 at 6:00
Finland MM Purchase requisitions 3 at 12:00
Finland IM Main

Technical Name

ZUSB_IB1
ZGPG_LOADS_CN
ZGPG_ZEORD
ZGPG_DE
ZFI_LOADING_NEW
ZGPG_LOADS
SD_TRAN_META_CHAIN
DATA_LOAD_0MAT_PLANT
ZFIABB_MASTER1
ZFI_CA_MD_MAIN_NEW
ZFI_MM_MD_MAIN_NEW
ZFI_MM_PURREQ_2
ZFI_MM_PURREQ_3
FI_IM_NEW

Schedule Time
No
Dependency
on Master &
Transaction
Data Load

04.14
20.00
02.00
19.30
23.30
02.00
22.30
22.30
23.33
17.34
18.58
06.00
12.00
02.30

Frequency
Daily
Daily
Daily
Daily
Daily
Daily
Daily
Daily
Daily
Daily
Daily
Daily
Daily
Daily

10

Immediate Step
Immediate Step - Critical
Implementation Best Practice

Approach

Development & Naming Standards

Process Chain Design

Dependency between Master and Transaction data load

Proper Utilization of System - Loading data Parallel

Process

Technical Design Approval

Transport Mechanism

Better use of HPSM / HPALM Tool

KT with Support Team before and after Deployment in Production

System

Security & Authorization in Production

One Version across landscape

Better Use of Technical Content

11

Ideal Delivery Model

Onsite

Delivery Model
ABB Service Manager

Other Vendors

TCS Co-ordinator

Offshore

BW/BO Architect

TCS Co-ordinator

Advantages of Recommended Model

Better Solution and Approach

Better Process & Standards

One Version across the landscape

Availability & Quality of data to Business Users

Control on Changes / Transports

Minimize ongoing TCO for maintenance and Upgrade

Improved Business Users Satisfaction

Why do it now ?

Minimal User Base

TCS Support

TCS Development

Minimal Modules / Reports Implemented

Team

Team

Minimal effort on Implementing Changes

Minimal Impact on stabilization

BW/BO Architect Roles & Responsibility

Responsible for implementing standards and best

practices

Support Team Roles & Responsibility

Ensure Data Availability

Responsible for Data Quality

Responsible for smooth Implementation and/or rollout

Process Improvement

Collaboration with Business users, vendors and

partners

Quick turn around on load failure / issues

Control on Process Chain Design and Dependency

Identify Roadmap and Strategy

Support to Business Users

Evaluate and Introduce new technology

Co-ordination with other teams

Responsible for Knowledge Retention

* Above model not represent actual no of resources

12

Next Step - To Summarize

People

Focused group of BI SMEs and BW/BO Architect skill-set provide better and
scalable solution

Process

Set Process to accelerate, % reduction in the number of defects and %

reduction in cost of operations

Transform

Implement the proposed corrective measures to improve the operations

efficiency and information Quality

Monitor

Technology adoption, Control on Process and Changes will enhance the

overall effectiveness of the system.

Overall

Clear demonstration of Business Benefits delivered and Improved Business

Users Satisfaction Index

13

Some Best Practices

SAP BI as an Enterprise Data Warehouse

Quality of Measures and Analysis
Strategic

Measure Business Performance

Mange by metrics.

BI Analytic Capabilities

Strategic

Tools : Design Studio , Dashboards and

Predictive Analysis

Tactical

Access and interpret data for executives and

Managers.

Dashboard Supporting Strategic & Operational

aspects of Business

Tools : Analysis for OLAP, Analysis for

office. SAP Lumira & Business Explorer

Analyze Business Performance

Managed Reporting
Operational

Day to day operational needs.

Key Performance Metrics in line with Strategy, Goals & Objectives

Tools : Web Intelligence and Crystal reports

Finance
Operational

Strategic KPIs & Predictive Analysis

Sales &
Distribution

Supply Chain

COPA

SAP BW Infrastructure and Applications

Build BI Infrastructure and

governance mechanisms
To address Enterprise information
Management needs

Enterprise wide information infrastructure

Applications
15

Selecting the Right Reporting Tool

16

BI/Analytics Dashboard Design Principles

1. Show information on Dashboards that can be acted upon at a glance
The most important information/KPIs is shown in a very simple format. The type
of information should also be able to be acted upon, so that static information is
kept to a minimum.
Based on best practices, it is ideal to limit the number of graphs/elements to 3-7
per report.

2. Need to answer question on each potential KPI on the report: How will
the information be used?

Wireframe #1

Without a defined purpose of each KPI/element on the dashboard, it will quickly

fill with hollow data.
The first question that users most commonly ask is: What can I see in the
Dashboard? This question can lead to a polished interface, but primitive
capability

3. Eliminate white space without cluttering

Dashboards need to convey useful information in a few seconds. Too much white
space will make the Dashboard seem inadequate. Clutter will make it too difficult
to digest at once.

Wireframe #2

17
TCS Confidential

BI/Analytics Dashboard Design Principles (contd.)

4. A Dashboard report is not used to show all information of a system at
once
Many times, users think they want to see ALL the information on a particular
segment of the business in one report (sales, distribution, marketing). If we show
too much information and make too many connections, the performance of the
reports will suffer, and the end users will abandon using the Dashboard.
The Dashboard will also become too complex to quickly mine information from.

5. There must be context for each element on the Dashboard

Wireframe #3

Showing two completely different KPIs that are not related to each other serves no
purpose. Those KPIs must be on a separate report, or one must be dropped.
Having KPIs that are based or work off each other is the most optimal way to show
information.

6. The most important information should be located on the lefttop/center of the screen
Eyes tend to gravitate towards those areas
Focusing on placing elements in these areas will allow for a more natural flow of
the Dashboard
The area that is least noticed by the user is the bottom right

Wireframe #4

18
TCS Confidential

Data Structure for Business

Analysis & Reporting

Transformation representing
Business Subjects

Staging Layer

Meta Data

Transformation Layer

No Transformation

Transformation

Stores one day Data as close

to source system

Open Hub

Stable Structure , No Reporting

Master Data

Subject Layer

Non-SAP System

Reporting Layer

Data Distribution (Outbound) layer

BW Build Approach 1

No Transformation

Source System
Source of Data

SAP ECC

19

Data Structure for Business

Analysis & Reporting

Subject Layer
Stable Structure , No Reporting

Propagation Layer
Stores Data as close to source
system with region wise split

Meta Data

Transformation representing
Business Subjects

Master Data

Transformation Layer

Transformation

Division wise Split

Staging Layer
Stores one day Data as close
to source system

Source System
Source of Data

Open Hub

No Transformation

Non-SAP System

Reporting Layer

Data Distribution (Outbound) layer

BW Build Approach 2

No Transformation

SAP ECC

20

Sample Process Chain Design

21

Deliverables

Support

Induction Manual Template

Data Load Monitoring Kit

KT Checklist

Escalation Process Document

Monthly Review Meeting with Service Manager Template

Weekly Review with Technical Lead Template

Development

Blueprint Template

Project Plan Template

Estimation Template

BI Test Case Template

BI Test Plan Template

Architecture Guidelines

Development Guidelines

22

DeliverablesContd

Development

Naming Standard Guidelines

BO Authentication Guidelines

BO Security Guidelines

BO Performance Guidelines

Requirement Checklist

BO Deployment Checklist

BO Dashboard Standards

BO Design Standards

23

Discussion

Thank You