As professionals the exciting and fun part of our jobs is identifying and solving a great challenge that helps drive our business and make us better. However the daily grind keeps us from finding the time and energy needed to be innovative and forward looking. Personally as a software engineer I look to automate every non-fun part of my job (and my life) so I can focus as much effort as possible on solving these challenges and feeling the reward for doing so. Automation brings scalability, consistency, maintainability and definition to the things we do. I could come home at the end of the day and say “I spent the day building personalized reports for all 100 of our business leaders today”, only to have to say it again next month. Or I could come home and say “I spent the day building a system to send reports to business leaders and it doesn’t care how many of them there are”. Clearly the latter is the leader, the innovator and the one who’s going to make a difference. We built ReportWORQ to enable you to build a system and make that difference.
In my previous post, Data Warehouse versus Data Lake – The What and the Why (Part one), I discussed the differences between data lakes and data warehouses and when you would use each pattern. In this post I’ll discuss, at a high level, an iterative process for building a data warehouse.
The Dashboard tool in Cognos Analytics 11.0.12 now has the capability of drilling-through to reports, enabling integration between dashboards and reports, and thus access to more detailed information from high-level dashboards.
Topics: Cognos Analytics
How many projects have you been involved with where you told your business partner you have all the data they need, only to find out the data is far from complete or not in a form they can use? How many deadlines are missed as a result? How does this impact your relationship with other parts of your organization?
As the CFO, maybe you have been happy with Cognos Planning (CP), or maybe you have not. Maybe you are aware of the end user and administrator issues with CP, or maybe you are not. Maybe you prefer being slow to adopt newer technology, or maybe you are not. Either way to any of these questions, here are six main reasons why you, as the CFO, should upgrade to PA as a no-brainer decision:
Cognos Planning (formally known as Adaytum Planning) has had a good run, but the state-of-the-art solution, with respect to planning and forecasting systems, has moved on since the early 1990s. Today, we have higher expectations, including:
Cognos Planning (formally known as Adaytum Planning) has served many companies well since the early 1990’s, but is approaching the end of its life from an IBM support perspective, and the product is no longer being further developed by IBM.
Topics: planning analytics
The target audience for this blog post is anyone on IBM Cognos TM1 10.2.2, or an older release, who is looking to upgrade to IBM Planning Analytics. TM1 10.2.0 will no longer be supported by IBM after September 2018 (this year) and TM1 10.2.2 will no longer be supported after September 2019.
Topics: planning analytics