Technique/SAP BO2012. 5. 4. 22:47

Hierarchy layout in WEBI XI3.1 does not come in the same way as in BEx query output.

We do have a drill function in WEBi which will drill the hirerchy from one level to another, but we cannot see all the levels of hierarchies when drilled as we see in the BEx query output.

 

FOLD/UNFOLD Function:

 

If we do not want to see the detailed rows in our report we can use the fold/unfold function.When table or break is folded the rows are collapsed and only the header and footers are displayed.

In WEBi XI3.1 we can make use of the FOLD/UNFOLD functionality to get the same hierarchy structure that we see when we run the BEx query.

 

Note: Tables must have header/footer to be folded and unfolded.

 

BEx query output:

Hierarchy in BEx.png

 

 

Below are the steps to achive the same hierarchy layout as we have in BEx.

 

1) Drag all the level (L00,L01,L02 etc) of hierarchy and the required measures in the WEBi query.

2) Apply break on the dimension object (L00 and L01 dimension objects i.e. the first and second level of hierarchy as we have 3 levels in the current example) on which the hierarchy is to be created(break is not applied in the last level i.e. L02).

3) Drag the measure in the rows, the measure value will be summed up for L00 and L01, if not then sum the measures value at each break.

4) Enable the Fold/Unfold function as shown in the below figure.

 

Fold_unfold 2.png

As you can see that the measure value for L01 (India) is the 106 which is the sum of measure value for L01 (Maharashtra(6),Goa(68) and Punjab(32)). Similarly for L01 the measure value will be sum of the measure value for L02 object. We have the L00, L01 and L02 dimension objects draged in the report and have hidden the border of the columns to make the hierarchy structure look the same as we have in BEx.

Note: The above solution cannot be implemented if we have more then one hierarchy displayed in the report.




http://scn.sap.com/community/businessobjects-web-intelligence/blog/2012/05/04/hierarchy-in-webi-as-displayed-by-bex-query?utm_source=twitterfeed&utm_medium=twitter

Posted by AgnesKim
Technique/SAP BW2012. 4. 20. 10:42

Version management in SAP BW 7.3

Posted by GV Satya in GV Satya's Blog on Apr 19, 2012 5:30:06 PM

We might have an idea about version management in SAP BW but can you find complete history about changes made to particular object like how many time Info Object get modified /changed.

 

Scenario: Customer wants information about change to the Info Object (0Product), till SAP BW7.0 we can find only last changed information for the same.

Here is the Solution: Below Steps would help you to create historical version automatically in SAP BW 7.3.

 

Go to SPRO -->SAP ReferenceIMG -->SAP Net Weaver -->Business Warehouse -->General Settings --> Create Historical TLOGO Versions Automatically.

Ver1.jpg

Click on New Entries and maintain Object type (CUBE/DSO/Info Object etc...) from TLOGO object like below screen

Ver2.png

Enter the object type as IOBJ for Info Object,Check the below screen 

Ver3.png

Then goto RSA1 and select object maintenance screen then click on version management from Goto menu 

Ver4.png

We can observe the below screen that Active and Modified versions are temporary origin, 

hence it would not store in Database table

Ver5.png

Also we can find the History of version (object change version )with date and time,

We can observe that Version is would increase for each change.

Ver6.png

You can do comparison between different versions and can export in to the file (Example : XML)

Ver7.png

We can implement the same process for other Objects like DSO, Info Cube.


Posted by AgnesKim
Technique/SAP BW2012. 4. 20. 10:41

You have come across a situation where in many queries are wrongly assigned to roles and you are required to make the roles in an orderly fashion.

Given the scenario you just went into the roles and deleted unwanted queries from the roles.

 

Now you want cross verify if the users have superior or deficient access to the queries in short you want to know which all queries a particular user have access to??

 

How are you going to check this?? Well, its excellent if the idea has hit upon; otherwise you find this blog worth a flip through.

 

Go to User Maintenance - SU01 and get the list of roles assigned to the user.

IMG0.png

 

As a next step restrict contents of the table AGR_HIER (through SE11/SE16) with the roles we have copied and with extended name SAP_BW_QUERIES as shown below.

 

IMG1.png

This will list all the queries assigned to a user or in other way a user can access,

IMG2.png

You can similarly get the workbooks, webtemplates, and query views by giving the extended name as RRMX, SAP_BW_BTMP, and SAP_BW_VIEW respectively.

 

By seeing the table contents many of you might be guessing about the unique ID as the extended ID of a query shown under the transport request.

 

Well, if that’s the case, you are wrong. To relate the extended ID and unique ID of a query you would need another table RSRREPDIR - Directory of all reports.

Below drawing for a Query Artist P &L – SW test (Query) makes it clear how the unique ID and extended ID are related.

IMG3.png

Posted by AgnesKim
Technique/DashBoard 2011. 12. 28. 14:49

The Do’s And Don’ts Of Infographic Design


Editor’s Note: You might want to read Nathan Yau’s article The Do’s And Don’ts Of Infographic Design: Revisited (http://www.smashingmagazine.com/2011/10/21/the-do%e2%80%99s-and-don%e2%80%99ts-of-infographic-design-revisited/) here on Smashing Magazine which is a response to this article.

Since the dawn of the Internet, the demand for good design has continued to skyrocket. From Web 1.0 to Web 2.0 and beyond, designers have remained on their toes as they define the trends and expectations of our online universe. The Internet is a great designer’s playground, and online businesses are growing more and more appreciative of what can be gained from a bit of well-executed eye candy. Over the past two years, this fact has become the backbone of a growing trend in online marketing: the infographic.

Infographics are visual representations of information, or “data viz” as the cool kids call it these days. The term “data viz” comes from “data visualization,” which implies that sets of data will be displayed in a unique way that can be seen, rather than read. This visualization should not be left up to interpretation, it should instead be designed in a way that provides a universal conclusion for all viewers. In the simplest terms, infographics are not too different than the charts and graphs that programs like Excel have been spitting out for years.

Of course, just as Web 2.0 changed 1.0, today’s infographics are far more eye-catching than simple pie charts and bar graphs. Today, infographics compile many different data visualizations into one cohesive piece of “eye candy.” They have evolved with design trends, received some creative facelifts, and the Internet is now getting filled with interesting information delivered in enthralling ways.

While some design trends come and go, infographics are here to stay. With brands like USA Today, The New York Times and Google and even President Obama getting behind them (http://www.whitehouse.gov/search/site/infographic), infographics are becoming a powerful tool for disseminating huge amounts of information to the masses. Companies large and small are using infographics to build their brands, educate their audience and optimize their search engine ranking through link-building. This is why learning how to design a good infographic is a must, and avoiding the common pitfalls of infographic design could mean the difference between landing a big client and losing them entirely.

[Editor's note: Have you already got your copy of the Smashing Book #2? The book shares valuable practical insight into design, usability and coding. Have a look at the contents.]

Wrapping Your Mind Around Data Viz

Designing an infographic is not the same as designing a website, flier, brochure, etc. Even some of the best designers, with portfolios that would make you drool, cannot execute an effective infographic design. Creating infographics is a challenge and requires a mindset that does not come naturally to everyone. But that mindset can be gained through practice and by sticking to certain standards, the most important of which is to respect and understand data viz. Here are some simple rules to follow when wrapping your mind around proper data viz.

Show, Don’t Tell

A rule of cinema is to show, don’t tell. The same holds true for infographic design. The foundation of any good infographic is data viz. As an infographic designer, you may or may not determine the concept and compile all of the research for the final design, but either way you are responsible for turning that information into a visually stimulating, cohesive design that tells a story and that doesn’t miss a single opportunity to visualize data. Take this portion of an infographic about Twitter by ViralMS as an example:

twitter infographic
This Twitter infographic writes out the data, rather than visualizing it.

What’s wrong with this infographic? It breaks the first rule right out of the gate. When you have an opportunity to display information visually, take it. Here, the tweets per second could have at least been shown in a bar graph. This would enable someone to quickly look at this section and see what’s going on; by seeing the various heights of the bars, the eye could have quickly gauged the differences in tweets per second per event without having to read anything.

If you’re having trouble adhering to this rule, try keeping all of your text on one layer of your AI file (excluding text inside charts and graphs). Every once in a while, turn off the text layer and see whether the infographic still makes sense. If there isn’t any data viz, or if a bunch of pictures are missing context, then you are doing too much telling and not enough showing.

If the Client Wanted an Excel Chart, They Wouldn’t Need You

It might sound harsh, but it’s true. If infographics were as simple as laying out a bunch of standard charts and graphs on a page, then clients would not need to search out great designers. Many tools are online that can create colorful pie charts, line graphs and bar graphs, so you have to take things to the next level for your design to stand out. Taking the data from above, which of the two graphs below do you think would make a client happier?

unique data viz
Two ways to visualize the data from the Twitter example above.

If you answered Graph B, you’re catching on. Of course, not all data lends itself to creative and unique graphs. Graph A might work very well if the rest of the infographic shared a similar aesthetic. Sometimes you just have to bite the bullet and produce a traditional bar graph or pie chart; nevertheless, always consider ways to dress it up, as in the examples below:

infographic examples
Ways to dress up simple graphs for an infographic.

Typography Should Not Be a Crutch

Typography can make or break a design, but it should not be the solution to a data viz problem. More often than not, designers begin an infographic with a great deal of energy and excitement, but they lose steam fast as they continue down the page. This often leads to quick decisions and poor solutions, like using typography to show off a big number instead of visualizing it in some way. Here’s an example:

Too much dependence on typography
TravelMatch’s infographic highlights too much.

Whenever I see this, I’m reminded of the “Where’s the beef?” ad campaign, and I think, “Where’s the data viz?” Although Sketch Rockwell is one of my all-time favorite fonts, this is a perfect example of relying too much on typography.

Any time a research number is provided to you for an infographic, ask yourself how it can be visualized. Percentages can always be visualized with creative pie charts; numerical values in a set can usually be turned into a unique bar graph; and when numbers don’t fit on a consistent scale, you might be able to visualize them in a diagram. Here is another way the above data could have been visualized:

data visualization
An example of how to visualize the TravelMatch data, rather than relying on typography.

Typography Has Its Place

All that being said, typography does have its uses, which should not be ignored when creating an infographic. Most of the time, you will want to focus your creative typographical energies on titles and headings. The title of the infographic is a perfect opportunity to use a fun and eye-catching font and to give it a treatment that fits the theme or topic. Just make sure the title isn’t so distracting that it takes away from the reason we are looking at the infographic in the first place. The truth of the matter is that some infographic topics are boring, but the right title design can engage people enough to scroll through.

Similarly, headings help to break up an infographic and make the data easier to take in, giving you another chance to let your font-nerd flag fly.


The title of an infographic is your chance to draw attention to the design.

Organization And Storyline

Organizing an infographic in a way that makes sense and that keeps the viewer interested is not always easy, but it’s part of the job for most infographic designers. Usually, you will be given a lot of data and will need to create a visual story out of it. This can be challenging at first, but you can follow some general rules to make things easier.

Wireframe the Infographic

Wireframing an infographic enables you to work out a storyboard and layout for the design. You may have an idea of the story you want to tell, but as you start laying things out, you might hit a wall and have to start over. Having to reorganize after having already done a lot of the design is incredibly frustrating. Avoid this by setting up your storyline at the start to determine what data to show and how. Set aside an hour to sketch things out and make sure it all makes sense. This will also help to ensure that the color palette you will choose drives attention to the important points and keeps the eye flowing down the page.

Think Outside the Box

As you wireframe the infographic, you will identify section breaks that help to tell the story. Most infographics online have a vertical flow, in which each section has a heading to distinguish it from the last. This gets boring fast. Organizing the data and sectioning off information without relying entirely on headings and color breaks is a good way to break the monotony.

For instance, rather than going for a typical one-column layout, you could use two columns in certain parts. You could also break up sections with borders, with backgrounds of different shapes or give the entire design a road or path theme. Here’s some outside the box layouts to get your creative juices flowing:

unique infographic layouts
There are many unique ways to lay out an infographic that will keep the viewer engaged.

Tell a Story

All good stories have a beginning, middle and end. Infographics deserve the same treatment. At the beginning of the infographic, introduce the problem or thesis. From there, back it up with data. Finally, end the infographic with a conclusion.

Visualize the Hook

Every good infographic has a hook or primary take-away that makes the viewer say “A-ha!” As a designer, you should make this hook the focal point of the design if at all possible. Placing the hook at either the center or very end of the infographic is usually best, so that it grabs more attention. Give the most important information the most visual weight, so that viewers know what to take away. Here are some examples of well visualized hooks:

hooks in infographics
Hooks should either be in the center, beginning, or end of the infographic and need the greatest visual emphasis.

Cleaning Things Up With Color

The difference a color palette can make is amazing, especially in the world of infographics. The right palette can help organize an infographic, evangelize the brand, reinforce the topic and more. The wrong palette can turn a great topic into an eyesore, harm the brand’s image and convey the wrong message. Here are some tips to consider when choosing colors for your infographic.

Make It Universal

In Web design, it’s always important to choose a palette that fits the theme of the website and that is neutral enough for a diverse group of visitors. Because infographics are primarily shared online, picking the right palette for an array of visitors is equally important. You must also consider what looks good online.

For instance, dominant dark colors and neons typically do not translate well on infographics; neon on black can be hard to read, and if there is a lot of data, taking it all in will be a challenge. Also, avoid white as a background whenever possible. Infographics are often shared on multiple websites and blogs, most of which have white backgrounds. If your infographic’s background is also white, then deciphering where it begins and ends will be difficult.

A Three-Color Palette Is Easy on the Eyes

With all of the data that goes into an infographic, make sure that the reader’s eye easily flows down the page; the wrong color palette can be a big barrier to this. Choose a palette that doesn’t attack the senses. And consider doing this before you start designing, because it will help you determine how to visualize the various elements.

If picking a color palette is hard for you, stick to the rule of three. Choose three primary colors. Of the three, one should be the background color (usually the lightest of the three), and the other two should break up the sections. If you need to add other colors, use shades of the three main colors. This will keep the palette cohesive and calming, rather than jarring.

Use the Tools at Your Disposal

When picking colors, you don’t have to reinvent the wheel. A number of great websites out there will help you choose the right palette for your infographic. Adobe’s Kuler (http://kuler.adobe.com) offers fresh themes and a searchable database, as well as an easy tool to adjust the palette that you’re interested in. One issue with Kuler is that all of the palettes have five colors, and the colors are sometimes from completely different families, rather than shades of a few primary colors, so finding the right palette can be like searching for a needle in a haystack.

Another color-picking tool is COLOURlovers (http://www.colourlovers.com/). This database is easier to search through: it breaks palettes into different themes and can be sorted by favorites. While most of the palettes also consist of five colors, the colors are not always given equal weight; instead, the tool suggests which should be dominant. Here are some good and bad palettes for infographics:

infographic color palettes (http://www.colourlovers.com/)

Final Thoughts

While these standards are important to consider for most infographic designs, sometimes an infographic comes along that breaks all of these rules and still succeeds immensely. In the end, clients like “eye candy” and designs that “pop!” While such terms are subjective (and annoying to most designers), we all know a great infographic design when we see one, and your clients do, too. Use these rules to guide you into the infographic realm, but create your own techniques and standards after you’ve gained some experience.

(al)



http://www.smashingmagazine.com/2011/10/14/the-dos-and-donts-of-infographic-design/



Posted by AgnesKim
Technique/DashBoard 2011. 12. 21. 17:38

Human Capital Dashboard Tracks Strategic HR Metrics Using Xcelsius

A Human Capital Dashboard addresses what was deemed a weakness in HR measurements – that companies gather human resource metrics but don’t use them strategically. A 2004 survey of senior executives, managers and HR professionals showed a wide gap between HR KPI collection and the use of that information as a management tool. See Human Capital Metrics: Most Users are Missing the Point.

Enterprise Dashboards, of course, are excellent in providing actionable business intelligence and are tools used to bridge gaps such as these.

Thanks to a Dashboard Spy over at Inverra, a consulting company with a focus on performance dashboards and scorcards, we get this great live demo of an Xcelsius Human Capital Dashboard. It really works hard to address that gap between knowledge and action by providing human capital metrics that are grouped in an intuitive and helpful way. Let’s start by looking at the screenshot of the dashboard:

Human Capital Dashboard

Remember, these are just screenshots of the dashboard. The live demo is definitely worth visiting as you can see the many pages of the dashboard and get a sense as to the interactivity that Crystal Xcelsius can provide.

The KPI views of the human capital dashboard are driven by departments within the company. You use the selector in the middle to select different departments. Drilling down within the dashboard brings you this view:

Human Capital Metrics for a Manufacturing Department

The HR metrics are divided into the four main groups of

Key Talent Processes
Human Capital Balance Sheet
Workforce Analytics
Compensation and Benefits

Within the category of Key Talent Processes, we have KPIs within sub-categories: Supply Resources (Open Positions, Speed to Hire, Employee Movement, New Hire Success, Leader Span of Control), Improve Capabilities (Key Job Skill Depth, Timely Feedback, Return on Training, Succession Ready, HR Span of Support), Reward Performance (Bonus Measures, Promotions)

In the Human Capital Balance Sheet, we have the following metrics: Assets (Leader Effectiveness, Investment in Leaders, HR Effectiveness, Investment in HR), Liabilities (Labor Cost, Cost to Hire, Cost to Develop, Cost to Manage, Cost of Benefits, Cost of Turnover), Equity (Competence – ‘Can Do”, Engagement – “Want To”).

In terms of Workforce Analytics, we have these HR Metrics: Demographics (Average Age, Avverage Pay, Average Tenure, Average Promotion Rate), Diversity (Ethnicity, Academic, Language), Turnover (Voluntary, Manager, Key Job, New Hire, Diversity)

Finally, in the category of Compensation & Benefits, we look at KPIs in these sub-areas: Compensation (Overall Compensation Ratio, Overall Pay at Risk, Top Performer Pay, Bottom Performer Pay, Key Job Pay, Diversity Pay), Retirement (Participation Rate, Average Deferral, Average Balance) and Health & Welfare (Medical Claims, Unused PTO, Disability Claims)

A great collection of human capital metrics, wouldn’t you say?

I had the opportunity to ask my source (Pat Quirk at Inverra) about the human capital dashboard and the underlying technology and process.

Here we have some notes on the HR metrics:

Annotations on Human Resource Dashboard

Notes about Human Capital Dashboard

Metrics for HR Capital Dashboard

In terms of the technology behind this dashboard, the technical team at Inverra chose Crystal Xcelsius by Business Objects. I asked them to explain some of their reasoning and they were kind enough to provide a glimpse of their thinking:

We went with Xcelsius Pro 4.5 and Microsoft Excel because we found that the combination provided basically better, faster, and far cheaper, monthly scorecards and dashboards. We highly recommend the “pro” package to anyone with basic excel/powerpoint-ish skills – we don’t recommend it for real-time applications or those without requisite underlying skills.

Other points made by the team:

  • Really need multiple skill sets to get most out of the package – creativity (design, look and feel, color, form) + perfectionism (get all the details in / working) + analytical (understand nuances of package / data)
  • More advanced work in Xcelcius takes months of hands-on time to master – that is why we created a business model to do that work for clients, thereby allowing them to focus on insights and action
  • Not geared for real-time updates (unless you purchase far more expensive enterprise version and licenses)
  • No IT capital expenditure needed
  • No IT licensing needed
  • No IT software needed
  • No IT service requests / support

In terms of the process used in their dashboard projects, here is a typical flow:

  • We consult with clients on metric selection
  • Client feeds us raw data and we do intermediary calculations
  • We get client data updates in any format they want (.txt, .ppt, .xls etc) from as many sources as they have (hr, ops, peoplesoft, OD, etc)
  • We maintain data warehouse
  • We build the template (took a day for me to build this)
  • We maintain the data in a simple data warehouse
  • We store as little as possible in the underlying file to keep performance high
  • Usually have 1 tab with selectors, 1 tab with data
  • Use hlookups extensively within the main tab to pull from the data tab as user navigates
  • We update and deploy the dashboard (typically monthly)
  • We include unlimited updates and mods to the dashboard in our $250 / month pricing model
  • Typically takes several weeks to align executives and select key measures
  • Typically start with straw model and cut-back / add based on what data client actually has
  • Typically have place-holders for more advanced metrics and start data gathering go-forward and add results as they become available

Again, Dashboard Spy readers should check out the live demo for the full effect of this human capital dashboard.

Also, be sure to check out:

Free Human Resource Magazines and White papers

Tags: Human Capital Dashboard, HR Metrics, Human Resources KPI, HR Dashboard, Executive Dashboards, Enterprise Dashboards, Crystal Xcelsius Dashboard, Business Objects Dashboard, Inverra

Related Business Intelligence Dashboard Examples:

          Posted by AgnesKim
          Technique/DashBoard 2011. 12. 21. 17:34

          Dashboard Design: Bullet Graph vs. Bar Chart

          Posted by: gstanley on November 29th, 2011 Leave a Comment

          We invest a lot of time and energy communicating our research, because unless we can effectively communicate our findings they are useless.  When goal is to communicate the most valuable information with the least most of ink that can be understood with the least amount of effort.  For your reference, our major influences are Deirdre McCloskey on writing, Stephen Few on dashboard design, and Edward Tufte on data visualization.

          Recently, CAN conducted a customer satisfaction survey for the Georgia Regional transportation Authority.  In addition to developing, deploying and analyzing the customer survey, CAN went above and beyond to improve how GRTA reported the results of their annual survey.  In this post, I will explain why we used a modified bullet graph instead of a bar chart to answer the business question.

          The purpose of the graph is to help answer the business question of how does GRTA compare to two competitors across 17 different metrics.  While GRTA needs to continually improve, for the purpose of  answering the business question the exact score was not important, but instead the difference between each competitor and compared to others how does GRTA score.  Comparing each company by metric was the main influence behind the design on CAN’s graph.

          The Original Graph

           

           

          The CAN Graph

          - In the original graph, the bold vertical lines focus the viewer how each metric scored, by encouraging the eyes to go up and down.  In the CAN graph, the light gray horizontal lines encourage the eyes to travel left and right to compare each companies performance.  Also, we used light gray lines so that we did not dominate the graph with supporting data.

          - In the original graph, there is no simple way to show the spread between the different competitors, besides comparing each line together.  However, it important to know how competitive each metric is when answering the business question.  When designing the CAN Graph, we darkened a length of the light gray horizontal lines to show the minimum and maximum score on the service quality index.  This

          - In the original graph, using four different colors made it difficult to make a memorable distinction between each company, take up an unnecessary amount of space, and impossible for color blind (10% of males) to make distinctions.  Using different shades of gray CAN made it easy for everyone, including the colorblind, to distinguish between different companies.  In addition to adding an additional way to differentiate between companies, using different shapes allowed for better distinction when multiple companies score close to each other.

          - In the original graph, the overall low graphical quality such as broken vertical lines, faded colors and pixilated font created an unnecessary distraction, and reduce the credibility of the results.  While this might seem petty, producing graphs that are crisp and well designed help develop trust with the audience.  In the CAN Graph, we produced the entire graph in black and white, so that the report can easily be reproduced on either a color or black and white printer.

          Posted by AgnesKim
          Technique/DashBoard 2011. 12. 21. 17:30

          This is the second part in a series about better dashboard design. This part, Flow, follows Message to highlight the importance of taking that message and making it easy to work through in light of the larger business process.

          Having said that and before we continue, we wanted to reveal an internal conversation we’ve been having about the example (Federal IT Dashboard) that we’ve selected to demonstrate some of our thinking. We appreciate that it is hard to build dashboards that satisfy a broad audience. From initial conception to delivery, these forces, often at cross-purposes, can chip away at an intuitive and clear design. This series of posts isn’t meant to disparage the hard work and deep thinking that clearly went into the design of the Fed IT Dashboard; it is meant to offer some perspective and hopefully useful lessons for others in their dashboard design projects.


          Part 2: Flow

          In Part 1: Message, Zach introduced the results of some thinking we’ve been having about the Federal IT dashboard and how to continue to improve the effectiveness of its ability to communicate with data. This week, we’ll take a look at the next step in the process: Flow.

          Simple

          Communicating with data is like telling a story: there’s a beginning, a middle, and an end. When you grab that latest book from your favorite author, you know just where to get started, and (if that author is any good) you know exactly when it’s the end. Well, telling a story with a data application is just the same. The information designer needs to lay out the components of the story in a way that facilitates starting, learning, and finishing strong. We call this the workflow of the application. A great application workflow is not evidenced by easy-to-use software (although this might very well be a byproduct), but rather a great application workflow is about helping the user transparently achieve the objectives that make them successful at their job.

          So let’s look at some of the principles that we at Juice would use to take the flow of the Fed IT dashboard to the next level.

          Principle 1: Know what objectives people are trying to achieve

          The first step to knowing the objectives of the users is to know who the users are. Because of the tremendous reach of the Federal IT Dashboard, this is a particularly difficult problem as the audience is so broad. Generally speaking, we think there are three types of users for this system:

          • Inquisitive masses – Scope: broad but shallow – These folks are the general public; those people who are most likely looking for high level information and are looking for answers to broadly curious questions.

          • Informed but distant 3rd parties – Scope: medium breadth, medium depth – This second group includes people who are looking for information on a specific program to compare to another program that they are more familiar with. In the case of the Federal IT Dashboard, this may include the CIO of a related project, or the chair of a Senate subcommittee, or a political watchdog group doing some research.

          • Involved 1st parties – Scope: narrow but deep – This third group represents those who are directly involved with a specific program and want to drill deep to learn as much as they can about a single specific program.

          Principle 2: Know how the solution will fit into the broader workflow

          Since most “normal” people are paid to get stuff done and not paid to use software, it’s important for the application designer to make sure the tools that they provide are, at a minimum, supporting the workflow, and preferably, transparent to the workflow. Questions that the designer wants to make sure the user doesn’t find themselves asking are “Where do I start?”, “What’s the next step through the app?”, “What’s the end point and how do I know I’m finished?”.

          Looking at the Federal IT Dashboard homepage, it’s not clear to me that there’s actually a place to start. The very first image is the Performance summary on the left with the column chart on the right. But just as I’ve decided that I can click, the image changes. I find myself being confused by this almost every time I visit this site – especially since I can’t click on the other views in the image rotation. All of a sudden, I’ve gone from trying to complete my workflow to trying to figure out how to get back to the dashboard – not very transparent.

          Using existing methods such as behavior diagrams (such as Interaction Diagrams, Event Diagrams, and Use Case Diagrams) can really help an application designer overcome these sorts of hurdles and define intuitive action flows.

          Principle 3: Make navigating the application layout intuitive

          When considering application navigation layout, use a single simple rule: start high and enable drill down.

          Start with high level KPIs that indicate the overall performance with as few metrics as are possible so the first thing that the user sees on a dashboard is nearly instantly comprehensible. This sometimes requires the application designer to be ruthless about “who” makes the metric cut for the first view. The number should immediately indicate whether further investigation is required. In our mockup, the important numbers are just four: spending and change, and performance and change.

          KPIS

          The goal is that it’s simple enough that a first time user can quickly determine what’s next, but an experienced user can quickly determine if anything significant has changed since their last visit.

          Once the high level “first view” is identified, enable the user to easily drill down for additional information and exploration. For example, as the user is investigating a particular number, clicking directly on that number should reveal the next layer of information. This is where the Federal IT Dashboard excels, by the way. Users can drill down by clicking on program names, or chart segments, and can navigate back up the crumb trail by clicking “clear” at the top of the data table or on the current view parent.

          Filters

          Finally, we need to address the main navigation. Navigation elements that are positioned such that they imply some sort of relationship, such as menu items, should either be siblings, or parent-child entities. In the case of the main navigation tabs on the Federal IT Dashboard, the items Home, Portfolio, Tools, and Data Feeds are distinct areas but all have different relationships to each other – or worse aren’t related. This makes navigation difficult because the user has to context shift to navigate. It’s a little like “Apples”, “Transportation”, “Monday”, and “Swimming” – they don’t have any thing to do with each other.

          It’s OK to use tabs, but make sure they contain distinct and separate domains or views. For the Federal IT Dashboard, I think navigation would be more intuitive if the Home, Portfolio, and Tools tabs were merged. Start all the users with the overview, then allow them to navigate via the visualization to the Portfolio view. Then, toggle that view with the views that under the Tools tab based on the view the user needs to see.


          http://www.juiceanalytics.com/writing/dashboard-design-flow/

           
          Posted by AgnesKim
          Technique/DashBoard 2011. 12. 21. 17:29

          2011 Dashboard Design Contest Winners Announced!

          Thursday, December 15, 2011

          We want to thank everyone who participated in our Dashboard Design Contest. Unfortunately, there can only be two winners. After carefully reviewing each submission, Dashboard Insight is pleased to announce the winners of our Dashboard Design Contest!

          Best Dashboard of 2011

          The winner is Mike Moore! He used Tableau Software to create his submission. Here’s a preview.


          Click image to view live dashboard.

          Best Visual Interface of 2011

          The winner is Patrick Tehubijuluw! He used QlikView to create his submission. Here’s a preview.


          Click image to enlarge.

          Our editor, Alexander “Sandy” Chiang, will be writing a review on why these entries won and how they could be further improved in a few days. Once that’s done, they will be featured on Dashboard Insight!

          A big thank you goes out to our sponsors for making this happen! Without their support, this contest would have never happened. Please do check out their respective products when you have a chance by clicking on their logos.

          Congratulations again to both contestants and stay tuned for the full reviews.


          http://www.dashboardinsight.com/news/news-posts/dashboar-design-contest-winners.aspx
          Posted by AgnesKim
          Technique/DashBoard 2011. 12. 21. 17:26
          Posted by AgnesKim
          Technique/SAP BW2011. 12. 8. 09:05

          All You Need to Know about HybridProvider in BW 7.30

               Rakesh Kalyankar    Article     (PDF 1 MB)     14 November 2011

          Overview

          The paper provides a detailed description about the following aspects of hybrid providers: - Purpose - Use-cases - Metadata - Modeling - Usage - Technical details


          Posted by AgnesKim