Data & Intelligence

Cognos TM1 Reporting Solution Strategy

Solve, then Evolve

All Cognos TM1 implementations require a strategy to deliver an appropriate reporting solution. This is the plan that will ensure that each business user will have access to all the TM1 data that they need, in the most usable format and in a timely manner. This plan must be based upon environmental configurations, user experience levels as well as time and budget constraints. The plan should outline a strategy that will meet the business requirements during acceptance testing, initial deployment to production as well for a conceivable period of time into the future.

A proven, best practice strategy for reporting is to Solve, then Evolve.

solve

With this approach, the applications “core statement” needs are first identified and “solved for”. These are not individual analyst support reports or ad hoc data queries but only those reports required to complete (close) and/or monitor a business process (P&L, Income Statement, Balance Sheet, etc.). These reports may also include critical KPI’s or KRI’s. These reports are usually fixed in format and require a standardized styling format. They may be parameter-driven, for example “Income Statement” by period, or by country. These reports lend themselves best to being deployed using TM1 Websheets.

 

Once the standard “book of business” statement reports have been delivered, ancillary statistical reporting needs can then be considered. These reporting needs are usually much more individualized and narrowly focused. These would include very specific views of data based upon specific business questions. They can include “check” and “reconciliation” views of data. These reports are almost always solvable using TM1 compiled cube views that are accessible using TM1 Web and the TM1 CubeViewer. The TM1 CubeViewer will also allow users to perform various filtering and drilling operations upon the data that each cube view displays.

Data Intelligence - The Future of Big Data
The Future of Big Data

With some guidance, you can craft a data platform that is right for your organization’s needs and gets the most return from your data capital.

Get the Guide

 

Finally, as the application matures and the level of user experience increases, it may be beneficial to evolve the reporting solution by considering the deployment of TM1 Perspectives to specific members of the business user community. These users will usually be the “power users” of the group with responsibility for performing more in depth, advanced or complicated analysis and reporting. Because of the nature of TM1 Perspectives, it is recommended that care be taken before offering Perspectives as a user option. Performance and concurrency are the 2 main areas that may have a detrimental effect on both the Perspectives user as well as the overall TM1 application.

 

Bulk Absorption and Configuration

From a pure architectural perspective, what is sometimes referred to as “bulk uploading” sometimes is (mistakenly) considered to be part of reporting or included in the data consumption component of the application.  Loading and/or updating data is part of the applications absorption or configurations components and should be handled with a best practice approach of leveraging TM1 TurboIntegrator scripts and/or active Websheets (designed based upon user and environmental requirements and constraints).

 

Conclusion

It is important to keep the implementation of the reporting solution (the consumption layer) separate and distinct from the key value add (the processing) of the TM1 application being deployed. From an architectural perspective, the manner of consuming the applications data may (and most likely) will evolve:

 

  • As user needs and level of expertise change, the method for consuming data my need to change.
  • Other reporting tools and/or technologies may be considered in the future (for example Cognos Insight or Cognos BI) which will change the method for data consumption.
  • Organizational changes may require additional or different analysis and reporting and therefore may change the method of data consumption.

 

Keeping the data consumption layer distinct form the applications value add will allow the method for data consumption to be more fluid, be tuned for performance and change (if needed) with little or no modifications to the core application.

jm

About the Author

Mr. Miller is an IBM certified and accomplished Senior Project Leader and Application/System Architect-Developer with over 30 years of extensive applications and system design and development experience. His current role is National FPM Practice Leader. His experience includes BI, Web architecture & design, systems analysis, GUI design and testing, Database modeling and systems analysis, design, and development of Client/Server, Web and Mainframe applications and systems utilizing: Applix TM1 (including TM1 rules, TI, TM1Web and Planning Manager), dynaSight - ArcPlan, ASP, DHTML, XML, IIS, MS Visual Basic and VBA, Visual Studio, PERL, Websuite, MS SQL Server, ORACLE, SYBASE SQL Server, etc. His Responsibilities have included all aspects of Windows and SQL solution development and design including: analysis; GUI (and Web site) design; data modeling; table, screen/form and script development; SQL (and remote stored procedures and triggers) development and testing; test preparation and management and training of programming staff. Other experience includes development of ETL infrastructure such as data transfer automation between mainframe (DB2, Lawson, Great Plains, etc.) systems and client/server SQL server and Web based applications and integration of enterprise applications and data sources. In addition, Mr. Miller has acted as Internet Applications Development Manager responsible for the design, development, QA and delivery of multiple Web Sites including online trading applications, warehouse process control and scheduling systems and administrative and control applications. Mr. Miller also was responsible for the design, development and administration of a Web based financial reporting system for a 450 million dollar organization, reporting directly to the CFO and his executive team. Mr. Miller has also been responsible for managing and directing multiple resources in various management roles including project and team leader, lead developer and applications development director. Specialties Include: Cognos/TM1 Design and Development, Cognos Planning, IBM SPSS and Modeler, OLAP, Visual Basic, SQL Server, Forecasting and Planning; International Application Development, Business Intelligence, Project Development. IBM Certified Developer - Cognos TM1 (perfect score 100% on exam) IBM Certified Business Analyst - Cognos TM1

More from this Author

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Subscribe to the Weekly Blog Digest:

Sign Up