• Skip to main content

IBM Blueview

Cognos Analytics and all things IBM

  • The Blog
  • Cognos Glossary
  • Cognos Resources
  • About Me
  • Categories
    • Cognos
      • Data Modules
      • Administration
      • Framework Manager
      • Dashboards
    • Opinion
    • Community Spotlight
  • PMsquare
  • Subscribe

The Blog

Watson Analytics Review: Natural Language Query

April 26, 2015 by Ryan Dolley 2 Comments

Be sure to see my Watson Analytics First Look for a high level take on the tool and check out the upcoming Cognos Vs Watson series to understand how Natural Language Query compares to similar tools and features in Cognos.

In part one of my Watson Analytics review we’re going to take a deeper look at the Natural Language Query capabilities embedded in the tool. IBM has been been hyping Watson Analytics as the next generation, quantum leap, pick-your-superlative Big Advancement to put the BI startups back in their place and reclaim their spot as king atop Mt. Gartner. Read on to see if Big Blue has a shot at the crown.

From Ignorance to Insight, Faster

IBM’s approach with Watson Analytics is to minimize the effort necessary to turn raw data into insight and to experience those insights visually rather than as a chart or crosstab. The hope is to leapfrog current BI darling Tableau with a graphically modern UI that intelligently analyzes data, identifies interesting relationships and allows users to explore them using natural language queries and visualizations. I illustrate how this works in the gif below:

Watson Analytics Review Explore Open
This is my first GIF… If I wanna go viral I’m going to need to add a cat…
  1. First I click on an uploaded data set, in this case offensive statistics from the 2014 NFL regular season.
  2. Watson presents twelve visualizations based on relationships it identified in the data set. No human intelligence was involved in finding or visualizing these relationships!
  3. I choose “What is the breakdown of Receiving TD by Location and Position” and boom! The Explore tool renders pretty tree chart showing exactly that.

Two clicks. Two clicks! That’s what it took to go from a freshly uploaded CSV of raw data to visual output. In Cognos Workspace Advanced that is probably one hundred twenty clicks and in Tableau, maybe sixteen? Working with Watson Analytics isn’t always that simple but fact that it can be is quite promising.

Ask And Ye Shall Receive (A Chart)

So what if Watson, in all his wisdom, fails to anticipate your question with zero input from you? Because Watson (kind of) understands English here are two options; free form a question in the text box, or click “How To Ask A Question” and use the just-launched query builder to guide you to a phrase Watson can understand. Take a look at the options below:

Watson Analytics Review Natural Language Query Options
Watson Analytics provides tons of options to build Natural Language Queries
  1. This is the data set I want to query. A single click will open the “Starting Points” window you see above.
  2. These are interesting relationships Watson Analytics automatically identified. Clicking on any of these will launch the Explore tool with the visualization described.
  3. This text box is where you ask Watson questions in plain English. When you submit a query the suggested visualizations below will update to reflect Watson’s best guess at the answer.
  4. Here you can access the “Ask a question about your data” screen, which provides a guided Natural Language Query building experience.
  5. Clicking “Create your own” will let you jump directly into the Explore, Predict and Assemble tools using this data set.

Ask Watson Analytics Yourself

Let’s take a look at the free form question option. Watson is best at interpreting language that contains column titles and specific data values from your data set in combination with a keyword telling him what sort of relationship you’re looking for – Compare, Trend, Average, Maximum, Count, Correlation, etc…

Here I type “Most Touchdowns By Player” into the text box. This is not precisely the kind of language outlined above but it is close to how actual human beings speak. None of these words are exact matches to what Watson expects – there are Total Touchdown, Passing Touchdown and Rushing Touchdown columns in the data but nothing called “Touchdowns”, and “Most” is not one of Watson’s listed keywords. Let’s see the results:

Watson Analytics Review Explore Natural Language
Watson can you hear me?
  1. Clicking on my data set brings up Watson’s suggested visualization?
  2. Liking none of them, I type in my desired query, “Most Touchdowns By Player”
  3. “How do the values of Total Touchdowns compare by Player Name” seems to capture the spirit of it.
  4. The Explore tool opens with the visualization Watson Analytics feels best represents the answer to our question.

Or Get A Little Help

The example above worked great, but believe me there are plenty of times Watson will have no idea what you are trying to ask him. IBM just launched a feature that allows you to construct your query sentence using column titles from your data set and the keywords Watson is designed to recognize. Instead of typing in the text box, click “How To Ask A Question?” to get to the screen below:

Watson Analytics Review Natural Query Builder
Watson Analytics will guide you in writing a query it can understand
  1. I choose the “Breakdown” Natural Language Query starting point because I want to see which players scored the most receiving touchdowns against each team in the NFL.
  2. In the drop down boxes I select “Receiving TD”, “Opposition” and “Player Name”. Then I click “Ask”.
  3. Watson returns to the “Starting Point” screen and displays the relationships it identified based on my question. I click on the one I am most interested in.
  4. The Explore tool opens with the visualization I choose populated with data and ready for further analysis.

It’s important to note, no setup is required to use a feature like this. Watson figures out all of the data types when you upload a file and provides these query building starting points, no metadata modeling required. Using the dropdown lists you select from your data items and click “ask” to see what visualizations Watson suggests.

How Natural Is Natural Though?

These capabilities are impressive. Watson Analytics is targeting business users and executives who don’t have time to wait for someone like me to write a complex SQL statement for them, and also don’t have time to go back to college and learn to do it themselves. Allowing them to query the data in English really is the giant leap forward IBM purports it to be…

… for the most part. The thing is “Natural Language” means “Not SQL or another coding language” more than it means “How I talk about the NFL at the bar.” Let’s explore the limitations of Watson Analytics Natural Language Query as it exists today by trying to determine the best quarterback in the NFL.

“Who is the best quarterback?”

Straightforward, conversational and exactly how you’d phrase it over some wings and beer. Let’s see how Watson Analytics responds:

Watson Analytics Review Natural Language Best QB
These visualizations are not “somewhat relevant…”

Watson has no idea what we’re asking. “Best” is not a term computers will understand for a looooong time, and even then our disagreement over the criteria for determining “best” is what makes the question fun to begin with. “Quarterback” Watson could understand but only if it’s spelled out in the “Position” column. It isn’t, it’s “QB” and so this sentence is complete nonsense to Watson.

“Who are the top ten QB?”

Here we’re providing Watson Analytics with the correct reference to the position (“QB” instead of “Quarterback”) and providing it with a specific set we’re concerned with, the top ten. Think we’ll have more success?

Watson Analytics Review Natural Language Top Ten QB
It’s answering the question we asked… we just didn’t ask the question we intended.

Well… sort of. Because we correctly used “QB” Watson Analytics has determined that we are talking about Position, and our use of “Top 10” is leading it to show breakdowns, counts and comparisons. It appears to be connecting “who” to “Player Name”. However we haven’t provided it a measure so it is comparing Player Name and Position.

That it is able to make these connections is impressive but we are no closer to identifying the best quarterback in the NFL. Let’s try again, this time with some more measurable criteria.

“What is the breakdown of player name by passing td and passing yards?”

Now we’re speaking Watson Analytics! Check out these results:

Watson Analytics Review Natural Language Query Speaking The Language
Now we’re speaking Watson Analytics!

Here we used the keyword “Breakdown” and directly referenced the columns we are interested in comparing, Passing TD and Passing yards. By giving Watson Analytics the measures we want to see rather than a fuzzy human term like “best” we get the results we are seeking. Let’s choose “What is the relationship between Passing TD and Passing Yards by Player Name?” and see the results as rendered in the Explore tool:

Watson Analytics Review Natural Language Query Best QB verdict
We still don’t know who is the best, but we can say with certainty who it isn’t… Blake Bortles.

Explore Your Options From Here

You may be wondering if Watson Analytics forces you to submit query after query until you get the phrasing just right to render the visualization you seek. The answer is thankfully, “No.” Once you get into the Explore tool pictured above you can tweak or completely change the visualization much like you would with Tableau. The Natural Language Query is the starting point of a conversation with your data that provides a first visualization from which to work. I will give more details of the Explore tool in an upcoming post.

Verdict: Not Perfect, But Perfect For The Right Users

As you can see, the Natural Language Query feature of Watson Analytics is a powerful tool for quickly identifying interesting relationships and generating modern looking visualizations without writing code or wrangling with chart axis and dimensional aggregates. BI professionals and advanced business users may wish they could skip it entirely and jump straight into the X – Y graph making with which they have expertise, but these people are not the target audience of Watson Analytics.

The relatively conversational nature of the Natural Language Queries Watson Analytics can interpret and the speed at which it presents and visualizes multiple possible relationships derived from a query makes this feature ideal for line of business analysts and executives who want a low cost, self service experience they can easily understand. That it requires no input from IT is either a blessing or curse depending on your perspective, but IBM is expected to unveil integration between Watson Analytics and Cognos Business Intelligence in the coming months.

There’s Much More To Watson Analytics

Natural Language Query is really just the gateway to Watson Analytics. There are three fully fuctional tools, Explore, Predict and Assemble that I will give the full treatment in standalone reviews before wrapping up with an comprehensive overview of Watson Analytics and how it fits into IBM’s portfolio and the BI marketplace. Overall I feel this tool shows great promise and I’m excited to see what IBM does with it going forward.

 

 

 

 

Elementary My Dear: Watson Analytics First Look

March 30, 2015 by Ryan Dolley 2 Comments

Today I’m going to take a first look at Watson Analytics, the newest BI offering from IBM. To say Watson Analytics is critical to IBM is an understatement. While IBM assures investors of their profitable future as a cloud analytics and services company, Gartner’s 2015 BI Magic Quadrant shows continued deterioration for IBM in the face of stiff competition from Tableau, Qlik and others.

The market clamors for easily deployed, departmental, user friendly BI tools and IBM’s existing champion Cognos is a slow moving behemoth tailored to IT managed enterprise deployments. Their first crack at meeting the new demands of analytics users, Cognos Insight, saw very limited adoption. So IBM went back to the drawing board and Watson Analytics was born.

A New Business Model for IBM Analytics?

Let’s get the most important question out of the way – how much does it cost? Watson Analytics is currently a cloud only app which can be accessed for free with .xlsx or .csv data sources of up to 500,00 rows and 50 columns with 500MB of total storage. 1,000,000 rows and 256 columns with 2GB total storage will run you $30.00 a month. This smartly removes the two biggest roadblocks to acquisition faced by Cognos, SPSS or TM1 – the IT Department and a few million dollars.

Pricing as of 3/29/2015
Probably not going to need a capital project for this…

IBM has taken all the hard won software know-how of their existing analytics stack and applied it to Watson Analytics. You can see the fingerprints of Cognos and SPSS all over. SPSS handles the statistical magic happening under the hood while the Cognos RAVE visualization engine appears to drive data presentation. It’s wrapped in a mostly intuitive and very modern UI capable of competing with Tableau & Friends in the battle for eyeballs.

Who Is Your Watson? And What Does He Do??

There are currently three main features to Watson Analytics, Explore, Predict and Assemble. To help illustrate how they function I created some visualizations and predictions using a data set of 2014 NFL offensive stats. I will give each of these features the full treatment in future posts. Below is a quick overview and screenshot of the output.

Explore

Explore is kind of the “query tool” of Watson Analytics. Here you create visualizations and do guided data discovery. Swapping between visualizations is intuitive and there is a surprising amount of control hidden away in a few hard to find menus. Let’s take a look at the basic layout.

Watson Analytics Explore’s the Lions receiver corps.
  • The small blue summary charts at the top of the screen are interesting relationships identified automatically when Watson Analytics first analyzes the data set. Clicking on them will take you to a fully realized visualization of lower level detail.
  • The visualization itself occupies the center of the screen and is fully interactive. For example, clicking on the “Calvin Johnson” tree map segment opens a menu that allows you to change, filter or exclude that element.
  • To the right of the visualization is the key and a slide filter. These were generated automatically and provide an additional way to edit or filter the data elements on the visualization.
  • The bottom of the screen lists all data elements and provides access to more advanced capabilities, including custom calculations and the ability to define dimensions for slice-and-dice analysis.

Predict

Predict is probably the part of Watson Analytics most aggressively marketed by IBM. Predict does exactly you think – applies statistical models to make a predictive analysis of the data set. It’s highly automated and you do not need to be a data science to understand the output, which perhaps a double edged sword because if you aren’t a data scientist there’s a big risk of misinterpreting the data.

So you're saying the people  to whom the ball is thrown are the people who most catch it?
So you’re saying the people to whom the ball is thrown are the people who most catch it?
  • The top of the screen provides various details about the prediction, including a score of the data quality, top field associations, and additional statistically significant relationships.
  • In the center we see the primary predictive relationships in the data – in the case, that receiving targets and yards are the primary predictors of total receptions. More interesting perhaps is the much weaker relationship between touchdowns and total receptions.
  • You can go into much greater detail about the statistics behind all of these elements with just a click. I’ll explore this in detail in an upcoming post.

Assemble

Assemble is the dashboarding tool in Watson Analtyics. This is where you combine the visualizations from Explore and insights of Predict to tell the graphical story of the data. It provides an interactive environment and, I think, looks quite good compared to Cognos. But in its current form your options for sharing and collaboration are pretty sparse.

Calvin Johnson, resident touchdown machine.
Calvin Johnson, resident touchdown machine.
  • The dashboard is highly interactive without any configuration, which should make Cognos developers accustomed to Active Reports party in the streets.
  • New tabs and a variety of visualizations, images and external content can be added easily at the top of the screen.
  • Total development time for a dashboard is reduced to minutes vs days or weeks in Cognos. I built this in about four minutes (and you can tell!)

And Now For The Secret Sauce

Looks cool so far but is that it? Well, no. Embedded in everything is a search box connected to a natural language processor that generates visualizations on the fly rather than crawling for pre-existing content…! To me this is the most exciting feature of the whole thing because so much of my job is hand crafting bespoke, locally sourced reports and visualizations which, popular as they may be in certain parts of Brooklyn, is a job better done by a machine.

Okay Watson is smart but maybe not quite that smart...
Okay Watson is smart but maybe not quite that smart…

The suggested visualizations you see above in response to my query are not something a human being was paid to create, and that seems to me to be the secret sauce of Watson Analytics. More than the predictive modeling and the cloud and the other buzzwords, this is the big improvement on IBM’s existing analytics platforms. Type in a question and get three days worth of the BI team’s best visualizations. Don’t like the results? Just ask another question.

Watson Analytics, Cognos and The Future

I am still thinking through the implications of IBM’s new direction for both the Cognos platform and Cognos developers. IBM has not outlined publicly their integration plans between the two platforms but it’s easy see this as the direction in which Cognos is headed in terms of functionality and aesthetics. As impressive as the above features are the infrastructure currently surrounding Watson Analytics for collaboration, metadata management, security, etc… is non-existent. I suspect that Cognos will be a primary vehicle bringing Watson to the enterprise.

Made it to the end? Man you must be as nerdy about this stuff as I. Check back soon for detailed explorations of Watson Analytics’ core features, as well as my thoughts on where all this is headed.

Cognos?! Who Needs Cognos When You’ve Got a Watson!

March 29, 2015 by Ryan Dolley Leave a Comment

NOTE: This diatribe was originally posted January 29th, 2015 at my old blogger domain. Since then I have in fact gotten a demonstration of Watson Analytics in the hands of a highly skilled presenter and was fairly impressed with the tool. IBM still needs to outline their vision for the integration of Watson into Cognos but you can fairly say of this post: “Foot, prepare to meet Mr. Mouth…”

 

IBM held a webinar today (January 29th, 2015) titled “IBM Watson Analytics for IBM Cognos Users. Here is my run down of what Big Blue had to show:

  • Watson is an unstoppable beast… in slide decks: Every time I see a Watson presentation the visualizations look great and the marketing speak makes it sound like a game changer. However I have yet to see an actual demonstration of the damn thing.
  • Cognos sure sounds boring: IBM gets positively tired whenever the conversation shifts to Cognos. You can tell how unexcited they are to sell things like “trusted source of data.” Who needs trust when you’ve got a sweet graph!
  • The Watson – Cognos integration does not exist: As per the slide deck, the current integration point between the two is that you take what you learned in Watson and send an email to someone in IT asking them to change something in Cognos to match your new insight. Awesome.

I had high(er) hopes for this presentation. Given the title I was expecting to see IBM’s vision for how Watson and Cognos exist in an analytics ecosystem, or at least an outline of some integration points between the two. IBM had nothing to say about Cognos though other than to acknowledge its existence, which… whatever. Just another wasted opportunity from Big Blue so par for the course.

More than anything I’d like them to actually demonstrate Watson in the hands of a highly skilled presenter. Because, as you’ll see in a future post, my experience with the Watson “freemium edition” is less than stellar…

Cognos 64-bit Reporting and When to Use It

March 17, 2015 by Ryan Dolley 3 Comments

I discussed in an earlier post the misconception that 32-bit Cognos application servers cannot execute 64-bit Cognos queries when in fact they can. This means that for most Cognos customers leaving the report service execution mode set to 32-bit is a smart move; existing 32-bit CQE content will work alongside 64-bit DQM content and you do not have to set up advanced routing rules to prevent 32-bit queries from hitting a 64-bit server. There are three cases in which I recommend deviating from this path:

  • You have extremely visual reports: When a query comes in that requires DQM your 32-bit Report Service will hand it off to the 64-bit Query Service to build and execute the query plan. The Query Service will pass the result set back to the Report Service to generate the report and everyone wins. If, however, your reports are extremely visually complicated the 32-bit Report Service can still serve as a bottleneck as it is restricted by the old-school RAM limitations of 32-bit processes. Routing this report to a 64-bit DQM server will resolve this problem.
  • You are making the leap to Dynamic Cubes:  This one is more of a preference than a hard-and-fast rule, but if you intend to realize the ridiculous performance gains that come with Dynamic Cubes I highly suggest you quarantine them to a 64-bit only server and route all Dynamic Cube traffic to that server. This will simplify troubleshooting and performance tuning for your cubes and secure your CQE queries against disruption. It also gives you a 64-bit landing place as you migrate legacy queries to DQM.
  • You are a new Cognos customer: If you are reading this having just inked your five year enterprise licensing agreement with IBM, you need to ensure that you are only building and developing in DQM. I cannot emphasize enough the importance of this point. I have it on very good authority that CQE will receive only bug-fixes going forward and that future versions of Cognos will execute CQE queries but all new development will be DQM only. Do not devote a single second to learning about or developing CQE content!

So there you have it!  If you are an existing Cognos customer you should feel fine leaving the report service execution mode on 32-bit and riding those CQE queries as long as you can. I recommend standing up a 64-bit DQM server only if you run into performance issues caused by the 32-bit report service for the time being.

Everyone needs to be planning a migration to 64-bit only, however. Dynamic Cubes are a great reason to start but the fact is that 64 bit Cognos is the future, and the future may be much closer than you think…

Yes that ending was intentionally cryptic. Not sure how much I can talk about yet… 😉

64-bit vs 32-bit Ain’t Just for Playstation and Nintendo

March 17, 2015 by Ryan Dolley 1 Comment

Redditor Aybabtu123 on the IBM Cognos subreddit asks:

“I’m putting together a 10.2.2 sandbox environment and I’d like to enable dynamic query mode on it. Is it true that all datasources must be 64 bit for this?”

This is a great question and one that IBM frequently discusses in a way that is clear as mud, so here is the answer as succinctly as I can phrase it. Assuming a 64-bit installation of Cognos on a 64-bit server with a 64-bit OS…

  • With the Report Server Execution mode in Cognos Configuration set to 32-bit, queries routed to this server will execute in either CQE or DQM depending on how the datasource and package have been defined.
  • With the Report Server Execution mode in Cognos Configuration set to 64-bit, queries routed to this server will only execute in DQM. CQE queries will error out.
Cognos 64-bit option
Where the magic happens

Cognos is automatically set to 32-bit Report Server Execution upon installation, so as long as you don’t change it your application servers will be able to execute both 32-bit (CQE) and 64-bit (DQM) queries – and by extension utilize both CQE and DQM datasources.

Tomorrow (or soon anyway) we’ll discuss what situations would warrant switching to a 64-bit only application server and the steps you need to take to properly route traffic. I’ll give you a big hint though, and it rhymes with crynamic dubes.

We Need To Talk: The Blue View Manifesto

March 12, 2015 by Ryan Dolley 1 Comment

We need to talk.

I am continuously surprised at the lack of strong IBM Cognos community content available on the web. With a few notable exceptions Cognos blogs burn bright, die fast and leave a handful of good posts slowly aging into obsolescence.

If you have made a career in Cognos this is a critical time. Cognos can do data discovery, visualization, self-service and collaboration but even IBM seems to lack a holistic vision to stitch it together.  Or else True Blue and the business partners are content to keep it behind the consulting pay wall.

That’s a huge problem. That’s the old world that Tableau and Birst have been sent here to destroy. Yes the new breed of BI tools are powerful and cool and excel in their particular niche, but more than anything they foster a user community that feels connected to one another. Last time I checked Tableau’s forum had over 18,000 posts. Where is IBM’s forum?

That’s a trick question because it doesn’t matter. A software community can only be formed and sustained by a group of people who have knowledge and the passion to share it. The deeply technical how-to’s and the holistic design philosophies have already been crafted by the army of talented Cognos developers.

We just need to talk about it.

So let’s start now.

 

  • « Go to Previous Page
  • Go to page 1
  • Interim pages omitted …
  • Go to page 4
  • Go to page 5
  • Go to page 6

Copyright © 2021 · Atmosphere Pro on Genesis Framework · WordPress · Log in