r&a2008 berg dashboards v5

8/13/2019 R&A2008 Berg Dashboards v5

http://slidepdf.com/reader/full/ra2008-berg-dashboards-v5 1/56

© 2008 Wellesley Information Services. All rights reserved.

Building cockpits anddashboards: Shortcuts,

design best practices, andguidelines to ensure you pickthe right SAP NetWeaver BItool for the job

Dr. Bjarne Berg



2

What We’ll Cover …

• Background, terminology, and examples

• Tool options

• What makes a good cockpit

• Which tool is right !or me

• Wrap"up



3

Dashboard Scorecard Cockpits

Purpose Displays performance Displays progress Displays status and events

Usage Performance monitoring Performance management Performance management

Updates Real-time feeds Monthly snapshots Daily snapshots

Data Events Summaries Summaries and events

Measures Metrics KPIs Metrics & KPIs

Context Exceptionsalerts !argets and thresholds !rends

Source "in#ed to systems "in#ed to plans "in#ed to $I systemsSources% ayne Ec#erson' ())*+

$,arne $erg ())

Background and Terminology

#any companies and people con!use the concepts o! dash$oards,

scorecards, and cockpits. They vary in terms o! purpose, usage,

source, data, etc.

#ost B% systems !all in to the cockpits category

hese are typical para!eters, and so!e !ay be slightly different

"e#g#, so!e !etrics in a cockpit !ay only be updated !onthly$#

%o&ever, such deviations should be e'ceptions#

$,arne $erg ()).



4

Typical Components o! a Cockpit& '(# (xample

• )igher"

levelnavigation

$et*een

vie*s

• (xternal

data

• +raphical

displaysComparative$enchmarking

-ogical grouping o!similar in!ormation



5

'(# #anagement Cockpit

Illustrate best

practices, bench!arks,

or target perfor!ance

(usto!i)ed navigation

!enus and buttons



6

*ink !ore

docu!entation

(entral navigation can

change !ultiple vie&s

+ake !ultiple

!easures available

Source: SAP A, -../

avigations -inked to #ultiple /ie*s





• Tool options

• What makes a good cockpit


• Wrap"up



Tool 0ptions

• '(# C1#

• We$ 2pplication Designer 3We$ 2D4

• '21 etWeaver /isual Composer

• 1u$lishing to the portal

• Custom cockpits 3B% 5ava 'D64• Third"party cockpits

8



'trategy #anagement and 1er!ormance #easurement 7 C1#

The presentation layer in '21

#anagement cockpits has!our layers&

•Cockpit )igh"level overvie* 3consists o! *alls4•Wall 2 logical grouping o! measures•-ogical vie* The display level o! the cockpit8 consists o! !rames•9rame -o*est level o! individual measure display

hese presentation layer objects are already Web0

enabled and integrated &ith the Portal# hey also

provide built0in drill0do&ns and navigation, based

on ho& you constructed your !easures#



What is '(# 7 C1#

The Corporate 1er!ormance #onitor 3'(#"C1#4 is part o! the'trategic (nterprise #anagement B% tool suite. %t consists o! the1er!ormance #easurement 31#4 area and the 'trategy managementarea 3'#4.

The Performance Management area consists of four distinct areas&

:. #anagement Cockpit;. #easure Builder

<. Benchmarking

=. Delivery o! $usiness content

The Strategy Management consists also of four areas

:. Balanced 'corecard

;. 'trategy modeling

<. /alue Driver Tree

ObjectiveObjective

MeasureMeasure Value Driver TreeValue Driver Tree

Risk Risk

Strategy Strategy

InitiativeInitiative

Source: 1# *o!bard, -..2



'(# 7 C1# Walls

Walls are the highest level o! the '(#"C1# Cockpit. >esearch has

sho*n that more than ? *alls are hard to read and comprehend. %dealnum$ers are <, @ or ?.

#ajor considerationAA

)umans have a hardtime remem$ering,organiing, and retainin!ormation that isasymmetrical.

This is true !orhearing, seeing,tasting, !eeling andsmelling.

3ead !ore about the cognitive revolution and the article thatstarted it all: Ne&ell and Si!on 4he !agic nu!ber 56 "78/2$



• Try to avoid empty spaces, $ut don’t !orce unrelated measures

into the cockpit it con!uses users

• Don’t use as many types o! graphs as possi$le,

and never mix more than < types o! graphs. %! you

use more, users have to interpret the pictures as *ell as the data.

• #issing data

points add

irritation

12

>ules !or +raphs and >eal (state



'(#"C1# >ules !or +raphs and >eal (state 3cont.4

There is nothing *rong *ith using the same type o! graphs

on a cockpit 3e.g., tachometers or line charts4. sers adaptEuickly and can a$sor$ the in!ormation !aster.



Tool 0ptions

• '(# C1#

• We$ 2pplication Designer 3We$ 2D4

• '21 etWeaver /isual Composer


• Custom cockpits 3B% 5ava 'D64• Third"party cockpits

14



15

Cockpits *ith We$ 2D <.x and '21 etWeaver ?.F

• We$ 2pplication Designer can create We$"$ased

cockpits using BW Euery data



16

Cockpits *ith '21 etWeaver ?.F We$ 2D

• e* items include improved ta$ strip container in '21 etWeaver ?.F

!or designing B% We$ applications

• >educes the

amount o!

custom

codingreEuired *ith

the help o!

Command

*iards, 2utocomplete, and

support !or

)T#- tags



'21 etWeaver ?.F We$ 2D e* 9eatures

• We$ %tems& Ta$ 1ages, Button, 'cript %tem 3'21 etWeaver ?.F

'upport 1ackage 'tack ?4• Drag and drop using 2nalysis item

• e* chart types 3heat map, +antt, milestone trend analysis4

• (xport B% We$ applications in 1D9 !ormat

• Command Wiard !or generating We$21% commands

• %ntegration *ith '21 etWeaver ?.F B(x >eport Designer !or

!ormatted reports

17



B% We$ 21% Commands

• Gou can use B% We$ 21% commands !or carrying out

certain actions in B% We$ 2pplications (xport to (xcel, 1D9, etc.

0-21 !unctions& 2pply 9ilter values, remove drill do*ns

• Command Wiards guide you through the steps !or

creating a B% We$ 21% command

• Commands appear together

!or easy access

Data 1rovider We$ %tems

We$ Templates

18

We$ cockpits developed $y We$ 2D in '21

etWeaver ?.F can $e interactive, includemany data sources, and $e very !lexi$le



19

Command Wiard and 5ava'cript

• se Command Wiard !or generating 5ava'cript code !or the

'cript %tem to use in custom cockpit applications

This is a great !eature !or$uilding custom !eatures into

your cockpits $ased onstandard 5ava'cript



20

#ore e* Cockpit 0ptions

• 1ersonalie B% Euery varia$les

• Bookmark the navigational state o! the B% We$ application• 1er!orm multidimensional analysis o! B% Euery data

• 2llo* users to create exceptions and conditions !or B% Euery data

These !eatures make iteasier to customie thedataset that Eueriesreturn to the We$cockpit



21

We$ 2D Cockpits in '21 (nterprise 1ortal

Directly pu$lish B% We$ cockpits to 1ortal Content Catalog using the

1u$lish option !rom We$ 2D

1ortal and B% system connection should$e set up per '21 ote H:?H@F



22

Broadcast Cockpit /ie*s sing We$ 2D

• %n '21 etWeaver ?.F, use %n!ormation Broadcaster to $roadcast B%

We$ applications 3e.g., cockpit vie*s4 to (nterprise 1ortal 6# !oldersand via email in various !ormats 31D9, #)T#-, )T#-4

• %n!ormation Broadcaster>eporting 2gent 3'21 BW <.x4 can

precalculate B% We$ applications to enhance per!ormance



Tool 0ptions

• '(# C1#

• We$ 2pplication Designer 3We$ 2D4• '21 etWeaver /isual Composer


•

Custom cockpits 3B% 5ava 'D64• Third"party cockpits

23



24

/isual Composer

2 /isual Composer is a tool to visualie the data. %t is a $ro*ser"$asedmodeling and design tool !or rapid application development I prototypingin a code"!ree development environment.



25

/isual Composer is (asy !or 1o*er sers to -earn

/isual Composer is a po*er user tool that is simple to learn !orsomeone *ith a little $it o! technical $ackground 3i.e. controllers,

report *riters, analysts4.

Source: SAP

Take advantage o! pre$uiltanalytic $usiness packages

o coding reEuired tocreate great"lookingWe$"$ased cockpits



26

/isual Composer !or Complex cockpits

#odeling o! B% applications using the B% kit o! the /isual

Composer allo*s $usiness users to create analytical content!or '21 portal. %t o!!ers the integration *ith B% %n!o1roviders,vie*s, B(x *e$ applications, 1D9 and more via W(B 21% asaccess to

other datasources suchas 0-21 andrelational data

sources4 via5avaconnectors

Image source: Cubeserv



27

'21 etWeaver /isual Composer Data1roviders

• Gou can use B% Eueries and vie*s as Data1roviders !or '21

etWeaver /isual Composer models• Gou also can use B% Euery !unctionalities !or exceptions and

varia$les along *ith '21 etWeaver /isual Composer

models

• '21 etWeaver

/isual Composer

allo*s access to B%history, !avorites,

and roles



28

/isual Composer Data #ethods

• Can integrate data !rom multiple data sources, including

'21 and non"'21 systems, into one model• Di!!erent options availa$le !or data access include&

B% (xtension 6it

>emote 9unction Call 3>9C4

We$ services• B% (xtension 6it allo*s access

to the !ollo*ing Data'ources '21 etWeaver ;FF= B%

3BW <.@ 'upport 1ackage :=4 '21 etWeaver B% ?.F

5DBC

J#-2



29

Details a$out /isual Composer Cockpits

•Delivered as part o! (nterprise 1ortal in '21 etWeaver B% ?.F sage

Type 3'1'K and higher4•Di!!erent options availa$le !or rendering /isual Composer output

9lashWe$ Dynpro 3)T#-4

•9lash provides high"end visualiation o! /isual Composer models

'ince a cockpit may havemany di!!erent Data'ources3Eueries4, it can take Euitesome time to execute themi! the memory cache is not

used consistently



30

The !uture o! /isual Composer

'21 5uly, ;FFK& Composition (nvironment including

/isual Composer continues to $e the go"to product !orcreating composite applications.

Source: SAP, Jul 2008



Tool 0ptions

• '(# C1#



•


31



32

We$ Cockpit in the 1ortal

%ntegrate Eueries andWe$ applications into theportal throughpu$lishing, $roadcasting,or We$ calls

The portal can eitherreceive designed pages

passively or activelycreate communities, We$pages, colla$orationrooms, or cockpits

Broadcasting

Publishing



33

We$ Cockpit in the 1ortal 3cont.4

• The '(#"C1# cockpits

are already part o! theportal, so you can access

them there

• i/ie*s can $uild custom

portal cockpits *ith

i/ie*s !rom many data

sources 3We$ 2D, BW,

'(#, '21 ><, We$4 andin many !ormats 3graphs,

pictures, !igures, ta$les4

• i/ie*s can also $e

interactive



34

'21 etWeaver ?.F /isual Composer 1ortal 1u$lishing

• '21 etWeaver /isual

Composer Design timedeploys /isual

Composer models

directly as i/ie*s to

1ortal Content Catalog

• Gou can then use /isual

Composer i/ie*s inportal pages, roles, etc.



35

Building a We$ Cockpit in the 1ortal

The trick in developing custom We$

cockpits in the portal is to managethe real estate care!ully

#ost pure i/ie*"$ased cockpits are

cluttered and hard to read andnavigate

:. 'tart *ith logical groupings o!

items 3sales, !inance, e.g.4

;. -imit colors to complementary

!ormats 3*e *ill look at these later4

<. 'hare the same navigation menus

and ta$s as the portal

=. 2void running text, !lashes,

animations, layering and scrolling

text 3this is an a$solute no"no4



Tool 0ptions

• '(# C1#



•


36



37

B% 5ava 'D6"Based Cockpits

• B% 5ava 'D6 can $e used !or custom applications $ased on '21 B%

and non"'21 data.• B% 5ava 'D6 provides access to relational and 0-21 data sources

using 5DBC, J#-2, 0DB0 etc.

• 2ccess to ;FFL data sources using the 5DBC drivers.

Source: SAP A, -../

1ava progra!!ers &illrecogni)e theSoft&are 9evelop!ent

it "S9$ !ainlibraries such as theabstract &indo&ingtoolkit "AW$ and the;I0oriented S&ingobject library as &ell

d k i 3 4



38

B% 5ava 'D6"Based Cockpits 3cont.4

• '21 etWeaver Developer 'tudio can develop B% 5ava 'D6"$ased

applications

• Can use along *ith '21 5ava We$ Dynpro

%nteresteddevelopers should!amiliariethemselves *ith'21 etWeaver

Developer 'tudio

Tip

l 0 i



Tool 0ptions

• '(# C1#



•


39

Thi d 1 C k i



40

Third"1arty Cockpits

• 'ome $est"o!"$reed cockpit tools incorporate '21 B% as part

o! a We$ item provider, or more commonly through BWEueries !ed $y B21%s or 0-( DB !or 0-21 30DB04 in BW

• 'ome even provide separate #ultidimensional 0nline

2nalytical 1rocessing 3#0-214 solutions tightly connected

to '21 BW )int& reading >'M ta$les inside BW

+icrosoft

(ognos



War >ooms and (xternal 2ccess



43

;. (xternal access to in!ormation is more common.

/endors and customers love itA

<. Gou can $uild *ar rooms !or colla$orativedecision making using cockpits

:.'hared cockpits are mostuse!ul

=. Cockpits reEuire a true B% in!rastructure.%t is tempting to jump straight to thecockpit development, $ut it is almostimpossi$le *ithout a *ell"architectedBW system to support it.

ote

War >ooms and (xternal 2ccess

2 + d C k it % 'i l



44

2 +ood Cockpit %s 'imple

The majority o! usage o! cockpits is in user segments : and @.Gou should use B% Eueries and 0-21 !or the other segments.

ote

'egment :& Trackers " <?N

Tracking " Characteried $y lo* duration

overall.

'egment ;& >eservers " <N

-o* duration per page vie*.

'egment <& ncommitted " :FN

Characteried $y long duration.

Complex decisions.

'egment =& %n!o +atherers " =N

Concentrated in in!ormation areas.

>arely reach transaction areas.

'egment @& 'ingle"clickers " <;N

/isit homepage only.

'egment O& Wanderers " :@N

/ery !e*, very random pages.

9e* hits, $ut long duration per pagevie*. !"am#le source: $r% Paul S&ru##, Su' ()cross&ems

The average manager navigates in no more than ? dimensions and only ; levels deep

3=H vie*s4. There!ore, the majority o! users o! cockpits need a !e*, simple, $ut highly

in!ormative, vie*s. The other user community is $est served $y 0-21 Eueries.

Th d ! ' d



The eed !or 'peed

• When cockpits $ring together data !rom many sources

during runtime, it can $e slo* and cum$ersome This is $ecause *hen your system accesses the portal cockpit,

it may have to execute supporting cockpit Eueries

• 'olution& Gou can present static images 3i.e., static )T#-

!rom B(x Broadcaster into a portal i/ie*4 or you can

cache Eueries results $y using B(x Broadcaster in '21

etWeaver ?.F

45

The eed !or 'peed 3cont 4



46

The eed !or 'peed 3cont.4

• '21 etWeaver ?.F allo*s you to !ill the resident memory o!

your server *ith pre"run results 3cache4. This provides!aster response to the users, since the Euery result sets are

accessed !rom memory instead o! re"executed on the

data$ase side.

SAP NetWeaver 5#.

%#10>T2T& 0ld >eporting 2gent scenarios still run in

'21 etWeaver ?.F. )o*ever, >eporting 2gent *ill not $e

developed !urther and is removed !rom '21 etWeaver

?.F Work$ench. %n '21 etWeaver B% ?.F you can only

reach it $y transaction code >(10>T%+M2+(T

SAP BW <#/

The eed !or 'peed B% 2ccelerator



47

The eed !or 'peed " B% 2ccelerator

The '21 B%

2ccelerator makes

Euery response time

@F":F,FFF !aster.

Gou use process

chains to maintain

the )12 engine a!tereach data load

!P" Sun and IBM have standard solutions ranging#ro$ %&'( to %')*(+ that can be installed and

tested in as little as ',- .eeks /+ S0P license #ees1

SAP

BW

Any

tool

Breaking ne&s: <- b Blades areno& certified by SAP "1uly -..=$

What We’ll Cover



48



• Tool options• What makes a good cockpit


•

Wrap"up

What '21 Tool 'hould % se



49

What '21 Tool 'hould % se

BW 3.x

Web AD

SAP Net-Weaer

!""#sWeb AD

SAPNetWeae

r $isua%Co&poser

SAP

S'M-CPM

(hird-

part)cockpits

*aa SD+too%s

Porta%i$ie,s

Mu%tidi&ensiona% Ana%)sis u%%/ - - - -

Porta% integration -

0nor&ation Broadcaster - - - - -1or&atted reporting - - - - - -

2raphica% options de%iered/ - -

Auto&atic code generation - - - - -

SAP integration

Direct support or non-BW data - - - -

Si&p%icit) to use and %earn - - - - -

here are !any options and so!eti!es the choice is based on

&hat you are fa!iliar &ith and &hether you enjoy using ne& tools

e* Tools >oadmap



50

e* Tools >oadmap

Source SAP A*, Ju'e 2008

B0B5 capa$ilities Dash$oards and >eports



51

B0B5 capa$ilities 7 Dash$oards and >eports

(rystal 3eports for pi'el for!atted

reports has been available &ith SAP

BI>BW since -..-# his tool can beintegrated into your tool portfolio using

e'isting SAP NetWeaver BI ?ueries

"N@: (rystal (rystal *ight &ill be the core tools for

for!atted reports starting -.7.$

+9ashboards can be built using

Ccelsius#

+CcelsiusD &ill be launched in -..8,

and &ill be 4the flagship product for

data visuali)ation dashboards6

+B' Web Application 9esigner &ill

not be enhanced further beyond3elease NW 5#7 in -..=#

Source SAP A*,

Ju'e 2008

What We’ll Cover



52

What We ll Cover …


• Tool options• What makes a good cockpit


•

Wrap"up

>esources



53

>esources

• C0#(>%T 31resentations, 2rticles and 2ccellerators4http&csc"studentWe$.lrc.edus*pBergBBMindexMmain.htm

• '21 0nline )elp BW and (1 %ntegration http&help.sap.comsaphelpMn*F=helpdataena<?$@K<c;=<HeOO!e:

FFFFFFFa::=FK=content.htm

• 'D BW )o* to +uides " )o* to integrate /isual Composer2pplications and B(x We$ Templates https&***.sdn.sap.comirjservletprtportalprtrootdocsli$raryuui

dad:K;ac?"FaF:"FF:F"=!$K"Ka=d;:?$:Hc:

•

BW Expert 3***.BW(xpert0nline.com4P QCreate nparalleled 2nalytical 2pplications *ith '21 etWeaver B%,

/isual Composer, and #acromedia 9lexR $y #oya Watson and 5udy6estecher, '21 -a$s, 5anuary ;FFO issueP >eEuires access to credentials to vie* !ull article text

? 6ey 1oints to Take )ome




• There are many *ays to $uild We$ cockpits and '21 has

tools !or them all• -ook at in"house We$ skills $e!ore you decide on

the tool

• '21 1er!ormance #anagement is a great tool !or those

*ith limited We$ skills, $ut reEuires consistency in

per!ormance measures 3roll"ups4 and structured

navigation

•

'21 etWeaver /isual Composer is great !or complexgraphing

• We$ 2D is the tool o! choice $y experienced We$

programmers *ho *ant total design !reedom54





• Third"party tools !or We$ cockpits are emerging and some

are Euite advanced 3Cognos, e.g.4

• While all these tools gives you a great deal o! !lexi$ility, it is

the use o! the real estate, colors, graphs, and consistency

that is going to determine i! your cockpit is success!ul&

'pend serious time designing instead o! codingA

55

Gour TurnA



Gour TurnA

)o* to contact me&

Dr. Bjarne Berg

$$ergScomerit.net

r&a2008 berg dashboards v5

Documents