Pooja Vishwakarma 270003D1VW firstname.lastname@example.org | | Tags:  10 cognos bi | 0 Comments | 591 Visits
Wanted to write something, so chose to write something about Cognos BI, I am new to blogging so please be considerate if you fell the content is not great enough to read or something. These are something basic about Cognos BI Reports.
IBM Cognos is the world leader in business intelligence (BI) and performance management software for the enterprise. Cognos BI provides the capability to distribute reports and dashboards with personalized content for each recipient from a single report
nDistribute reports on-demand or based on a time or calendar-based schedule, events or an external trigger
nSchedule simultaneous or sequential batch reporting jobs for multiple output formats, destinations, and views
nSupports industry standard security authentication sources and data and communication protocols and encryption standards
nCognos 8 has a scalable, multi-tiered architecture:
–DataSingle API lets programmers customize , expose, or hide any BI capability using any programming language, e.g. Java, MS .Net, C, C+.
Forrest Palmer 270001YU2V email@example.com | | Tags:  bicc data_goverance data_quality bi | 0 Comments | 548 Visits
I often get asked about the importance of having your data in excellent shape - accurate, complete, relevant, etc - before you start using BI. The conventional wisdom, usually in IT, is that the data has to be right or the users will not trust it. Of course, that's true - to a point. The success of any reports, dashboards, scorecards or analytics often rests on the quality and trust people have in the data they see through that BI content. But the reality is that the data is never perfect. The "single version of the truth" (something I question as a goal but that's another day) is a journey that will never be reached 100%. So waiting until the data is completely trustworthy before rolling out BI is a folly that, in fact, will slow down the realization and need for data quality to be addressed where it needs to be addressed - in the business.
The truth is that data quality is often improved because of BI. While the first reaction might be to "blame the messenger" - the reports or tools that were used - the reality is that exposing data quality issues and discussing how to address them is essential to establishing the sense of ownership in the business and the subsequent need for governance programs that will continually improve the quality over time.
To be clear, we cannot build BI on top of truly bad data and expect that to be acceptable. Our data warehouses and data marts must meet a sufficient level of quality to make the use of that data valuable and meaningful. But don't let the quest for "the best" prevent us from starting our journey towards "the better".
Which means we need to move to both a information governance mandate and a BI governance (e.g. BICC) mandate that work in concert and alignment with each other. And that means that our information management strategy and our BI strategy have to be viewed together. Each depends on the other.
And yet too often companies are more focused on one or the other. Some companies start headlong into a BI strategy without any real consideration of the information management strategy that goes with it. The result is a truly failed BI initiative that will struggle to regain credibility. And there are probably just as many companies who invest a tremendous effort on data warehouse design and development, MDM, and data governance with little attention to how the business can effectively use all that data with BI.
So which comes first - the need for information governance and information strategy or the need for BI governance and BI strategy? Chicken or egg?