Friday, May 17, 2013
I've been learning to come to terms with my Gremlins. To recognise who they are, and what they are saying to me. They appear to act in my best interest, sometimes pretending to be looking out for my best interest, and to make sure I am comfortable.
In reality, they keep me from moving forward. They tell me "it won't work; it's too risky, I'm not ready, the time is not right..." . They tell me to stay with what I know, wait for the right conditions, play it safe...
Well, I am on to my Gremlins. I am starting to understand now that to move forward, I must be prepared to be uncomfortable, to move outside of my comfort zones. I need to stop making excuses, stop looking elsewhere for answers, and to try, and if I fail, try again.
My greatest obstacle preventing me from making that big break is honouring my Gremlins.
What is preventing you from making that breakthrough?
Thursday, July 15, 2010
I’ve been trying to slowly push the concept of implementing a Business Intelligence platform and finally managed to get the ear of the CIO, who told me “Well, I like your idea. Tell you what, provide a quick demo and if I like it I’ll take it to the Business people.” I was excited, and immediately began probing to see which processes would be the best to map for a proof-of-concept demo.
I came away feeling that what will really seal the deal would be a whizz-bang demo showing a hierarchy of dashboards, each boasting fancy graphs of many colours, with hover and click effects, and perhaps soothing music playing in the background. “Make it look nice, and add our logo to the page, ” I was reminded.
This got me to wonder to what extent dashboards needs to be technology focused. In this fast changing technological environment, dashboards have to be – technologically speaking – responsive, relevant and multi-leveled and a good dose of technology is required to provide that. However, at some point, the dashboard has to stop being a technological gimmick and start being reflective of the business environment. At this point, responsiveness, relevance and multi-levelness must be about the business processes, and the technology used to present the information starts to become less and less relevant, as the data presented is probed to deeper levels.
Building a dashboard therefore requires a good balance between the technology used and the information it provides. Far too often, a dashboard project is embarked on largely because of the eye-candy it provides (normally compared to current solutions). Over time, the new bells and whistles become old-hat, and the business is no further from where it was prior to the project. So we wait for the next big technological wave…and the cycle continues.
A dashboard should be one of the deliverable of the strategic intent of the organisation to provide the business with meaningful information. It should be guided by a information management strategy, which should covers all aspects of delivering information to the business. An analysis must be undertaken to understand what is being presented, to whom, and how that information is used by the business. Skipping this portion of the project will bring the whiz-bang, but will run out of flavour as soon as the ooh-aahs subside.
Before embarking on your next dashboard project, ask whether the strategic intent is balanced well with the technology you are presenting. You could use the following points to score your dashboard.
- Check that your are providing a visual presentation of the measure
After all, your dashboard is a visual concept. Don't over-do the seriousness of the dashboard, and lose the visual impact in the process.
- Provide the ability to identify and correct trends
Information in dashboards must be used to present masses of data compressed into small components, so that trends and patterns are easily recognisable.
- Provide a measure of efficiencies/inefficiencies
Pictures on the dashboard are no good if they are not supported by measures. The interpretation of the measures against planned or total performance should also be at hand to provide perspective to the measures.
- Show details
Summary data is best suited for some level of audiences (for example senior management), but details should always be available, or be pointed to if the detail data itself is not available to the dashboard.
Sunday, January 24, 2010
One question that comes up often is how to redirect the user to a dashboard, instead of the Pentaho User Console.
Generally, the use will invoke the Pentaho webapp by typing the following URL:
This results in the invocation of the script biserver-ce/tomcat/webapps/pentaho/index.jsp.
<title>Pentaho BI Platform</title>
< META HTTP-EQUIV="refresh" CONTENT="0;URL=./Home" >
A quick glance at this file reveals that the script redirects execution to the file biserver-ce/tomcat/webapps/pentaho/jsp/Home.jsp.
To redirect Pentaho to load a specific dashboard page instead of running Home.jsp, we change the index.jsp file in the webapps directory, as in the following example:
<title>Pentaho BI Platform</title>
<META HTTP-EQUIV="refresh" CONTENT="0;URL=/pentaho/content/pentaho-cdf/RenderXCDF?solution=mydashboard&path=/company&action=homedashboard.xcdf&template=companyview">
This loads the file
with the template companyview.
The Pentaho platform by default requires authentication before serving any content. If you haven't logged in, then you will first be directed to the login screen. Upon a succesful login, you will be directed to the dashboard.
Sunday, September 6, 2009
...but I really see the point of Richard Stallman's rant about how to avoid being faced with a software patent issue with ongoing use of Mono.
After a little searching, I finally took the plunge and removed Mono from my Ubuntu-based operating system.
I won't miss the Tomboy notes taker much, and my system is not running any faster without mono. Since doing that, I've been reading up on trying to determine how wise my action was, and judging from some of the many writeups on the topic. I convinced that I did the right thing.
Monday, August 31, 2009
A short while ago, I wrote up and quick tutorial to create a new look and feel to your CDF pages.
In there, I wrote:
In order to replace the CE demo look and feel with my own, I needed to make changes to the template-dashboard.html file.
While this is certainly possible, another approach is to leave the current dashboard templates alone and create a new set of dashboard templates. In this way, it may even be possible to use different templates withing the same solution.
All dashboard template reside in this directory:
In order to create a new template, simply insert a new file in this directory, and name it as follows:
Note: In the file name above, only the "templatename" portion may be changed. everything else must remain as indicated.
You can then proceed to create the template as indicated in the linked page above.
To call up the dashboard page with the new template, add the template parameter to the URL
Saturday, August 8, 2009
It was always possible to embed Pentaho into a custom application with your own functionality and look and feel. So the CDF is offering nothing new. It's the ease and simplicity of its solution that stands it apart from other alternatives.
I've created a quick tutorial that explains how to use the CDF to create your own look and feel.
You can read the article on the Pentaho WIKI.