IBM Cognos Planning: V10 and Beyond
2 likes4,375 views
The document is a slide deck from a webinar discussing IBM Cognos Planning Version 10 details and its evolution from earlier versions, highlighting improvements and key differences. It includes a case study from Trimble Navigation focusing on their transition to Cognos from previous planning systems due to scalability and performance issues. Additionally, it suggests considering TM1 as a more suitable solution for handling larger datasets and real-time data movement.
IBM Cognos Planning: V10 and Beyond
- 1. Cognos Planning v10 and Beyond 05/18/2011 www.senturus.com Helping Companies Learn From the Past, Manage the 1 Present and Shape the Future
- 2. Agenda • Introduction • Client Cast Study - Trimble Navigation, Moving beyond Cognos Enterprise Planning • Key differences of earlier versions of Cognos Enterprise Planning compared to v10 • Moving beyond Cognos Enterprise Planning to TM1 2
- 3. This slide deck is part of a recorded webinar. To view the FREE recording of this entire presentation and download the slide deck, go to www.senturus.com/recorded-webinars.php You will find this—and many other recorded webinars-- under the “IBM Cognos Enterprise Planning and TM1” 3
- 4. Welcome and Introduction • Senturus: – Chris Fargo, Account Manager • 510.473.7096, cfargo@senturus.com – Jim Frazier, Vice President of Sales – Greg Herrera, CEO • Trimble Navigation: – Barry Schaeffer, Director of FP&A • IBM: – Michael Mackevicius, Partner Enablement Manager – Jeff Allen, Solutions Specialist – Business Analytics 4
- 5. Who is Senturus ? • Consulting firm specializing in Corporate Performance Management – Business Intelligence and Enterprise Planning & Budgeting – Platform-independent – San Francisco Business Times Hall of Fame -- Four consecutive years in Fast 100 list of fastest-growing private companies in the Bay Area • Experience – 10-year focus on performance management – More than 1,000 projects for 450+ clients • People – Business depth combined with technical expertise. Former CFOs, CIOs, Controllers, Directors... 5
- 6. A few of our 450+ Clients 6
- 7. Barry Schaeffer, Director of Financial Planning & Analysis CLIENT CASE STUDY - TRIMBLE NAVIGATION 7
- 8. Financial Planning Systems at Trimble Congnos Enterprise Planning v10 and Beyond 8
- 9. About Trimble Trimble applies technology to make field and mobile workers in businesses and government significantly more productive. Solutions are focused on applications requiring position or location—including surveying, construction, agriculture, fleet and asset management, public safety and mapping. In addition to utilizing positioning technologies, such as GPS, lasers and optics, Trimble solutions may include software content specific to the needs of the user. Wireless technologies are utilized to deliver the solution to the user and to ensure a tight coupling of the field and the back office. Founded in 1978, Trimble is headquartered in Sunnyvale, Calif. 9
- 10. Convergence of Three Technologies Domain specific field app sw Cellular Back office integration Radio Enterprise-wide solutions Bluetooth Internet-hosted solutions Satellite WiFi GPS Optical Inertial 3-D scanning 10
- 11. Trimble Planning Tool History • Pre 2006: Hyperion Pillar. File based. Didn’t scale • Early 2006 replaced with Cognos Planning – Head to head with Hyperion Planning – Won out based on break back • 2007-2010 – Huge wins with Cognos Planning: ‘a modeling tool’ – Some key disappointments 11
- 12. Huge Wins with Cognos Planning • Expanded divisional forecasting to: – Entity forecasting for tax planning – Emerging market forecasting for bus development – Long-range planning • Replaced many Microsoft Excel/Outlook-centric processes with Cognos Planning – Profit sharing and management bonus models – Accounting/tax/audit/SEC schedules – Detailed facilities and IT allocation models – Data center/IT cost accounting model • All of these significantly reduced man hours yet increased accuracy 12
- 13. Disappointments • Cognos Planning has cell count limitations – Not a secret. Cognos Support will tell you this – We’ve had to artificially break models into multiple pieces more maintenance and processes req’d • Elist dimension is an inhibitor – Security can only be applied via this one dimension – Only one small piece of this dimension’s hierarchy can be opened in a cube at a time – Processing time impacted by elist dimension size • Data flows between applications not real-time – Most models require ‘processes’ to be run in order for data changes to propagate entire model 13
- 14. Solving our Budget Tool Dilemma • Due to size, Cognos Planning can no longer handle Trimble’s annual bottoms up budget • Considering TM1 as a replacement • Size/cell count approaches no practical limit • All dimensions created equal. Security can be applied to any or many. Opening ‘everything at once’ a reality • Data can be moved real-time throughout all pieces of model. And very quickly 14
- 15. Cognos Planning Budget Illustration Employee Departments Departments B and and accounts and accounts headcount accounts Employee Departments Allocations Departments A and and accounts setup and accounts P&L headcount accounts Boxes separated by arrows are non-real time data flows Full model requires 8-12 hours of overnight processing ‘A’ represents divisional finance user. ‘B’ is functional or local site contributor. Require separate ‘slices’ 15
- 16. TM1 Illustration from Workshop* Allocations setup A Employee Departments P&L and and accounts B headcount accounts * Proof of concept workshop conducted April, 2011 All data moves real time between pieces Full model requires zero batch processing ‘A’ and ‘B’ users granted access to any piece of model 16
- 17. Looking Beyond Fixing the Budget Today Planning x Business Environment Intelligence Environment Bottoms Up Billings Budget Data Planning Business Vision Forecast, Other plans Environment Intelligence GL Data Environment Bonus HR Data data Today: BI only used against static data owned by ERP or IT BI can’t merge real-time planning data with other data Planning only handles small sets of non-real time BI data Vision: Bring all data together regardless of size Improved efficiency, analytics, accuracy, decision time 17
- 18. This slide deck is part of a recorded webinar. To view the FREE recording of this entire presentation and download the slide deck, go to www.senturus.com/recorded-webinars.php You will find this—and many other recorded webinars-- under the “IBM Cognos Enterprise Planning and TM1” 18
- 19. Presented by Michael Mackevicius, IBM WHAT’S NEW IN COGNOS PLANNING VERSION 10? 19
- 20. Increased User Controls and Flexibility User Controlled Nesting Cube Model User defined Cube Order User defined Views Support for Word Wrap Date Picker Support for Hierarchies Zoom Freeze Panes Sorting & Hiding 20
- 21. All BiFs supported in Contributor • @DCF • @NPer • @DelayDebt • @Outlook • @Delay • @PMT Stock • @Proportion • @Drive • @PV • @FV • @Rate • @ICF • @SeasonLite • @Lease • @StockflowAF • @Lease • @Tier Variable • @Time (All Methods NOW • @MovAvg Supported) • @MovMed • @MovSum 21
- 22. Easier to Maintain & Deploy Enterprise-wide, Improved Publish & Deployment Options • Table and View Publish • New client is built in – Index Management Java using Eclipse • No reliance on Active X – Bulk Load Tool Optimizations Controls • Incremental Publish – Tree and Grid – Handles e-list or d-list change • No Com Registration – a manifest is used • Except Dimension for Publish • Level Change – Job_Begin should be a lot faster 22
- 23. IBM Cognos Planning 10, IBM Cognos Planning 10 provides: • Significant scalability and performance improvements • Better use of computer hardware resources • Improved reconcile performance and workload management • Lower and more predictable storage volumes and improved job system resilience • Optimized publish processes and optimized data types • Conformance with IBM Cognos Business Intelligence 10.1 23
- 24. IBM Cognos Planning v 10, IBM Cognos Planning Contributor improvements • Provisioning is improved so that you can now have automatic updates of rich client components from a secured Web server. • You can now see the sum of values contained in cells that you select. • Significant performance improvements on the Workflow page. • Significant performance improvements in the grid for large models with sparse access, applications with long e-lists, and complex models with many links targeting individual cubes. 24
- 25. IBM Cognos Planning v 10, Macro system improvements • Running macros in parallel is supported and can improve the use of server resources. • Starting or restarting a macro at a specific step. • New Model Doctor macro that configures and runs the Contributor Model Review Tool as a macro step. The output of the Model Doctor macro is an HTML report containing a list of certain noteworthy attributes of the model it was run against. 25
- 26. IBM Cognos Planning v 10, IBM Cognos Planning, Contributor Administration Console improvements • Previewing nodes are now supported. • Access blocks replace and improve upon cut-down models. • The process of creating and updating packages as part of the Go to Production process now runs using the Scheduler Credentials account. 26
- 27. IBM Cognos Planning v 10, IBM Cognos Planning, Engine and runtime improvements • New lighter runtime model definition which decreases download times. • Controlling node access improved. • Cache management in Planning Service improved, and as a result, the memory footprint for the Planning Server is reduced. • The Planning Service can now be run as a non-administrative account or as a network service account, which allows increased security on computers running IBM Cognos Planning. • Aggregating data more efficiently, which results in the reduction of memory used and provides better compression of the data during the Reconcile - Data aggregation phase. 27
- 28. IBM Cognos Planning v 10, IBM Cognos Planning • Publishing and database improvements – Annotations and Attached Document tables do not use a dimension for publish – New views added to the Publish Tables schema – Uses more efficient data types in IBM DB2 for text • Job system improvements – Processes multiple jobs more efficiently as they reach the Job_End phase – Automatically retrys job items that fail – Switches jobs with more efficiency 28
- 29. IBM Cognos Planning v TM1, Sparsity. • Consider this simple two Dimensional Cube to illustrate the point Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Total Q1 Q2 Q3 Q4 Product A Product B Product C Time dimension – 12 Months and 4 Totals Total Product Product Dimension – 3 Products and 1 Total Total Leaf Level Cells = 3x12 = 36 Total Potential Cells = 4x16 = 64 Scenario Analyst TM1 1 Cell Populated 64 1 2 Cells Populated 64 2 All Leaf Cells 64 36 Populated 29
- 30. Contributor Distributed Architecture Server End User PC IE Browser / ActiveX XML Blobs containing data and meta data Contributor Template XML Blob is downloaded to PC and rendered in memory of PC to be accessed by user via IE/ActiveX 1. Model Size limited by memory on PC 2. Requires ActiveX download – not ideal in XML Blobs are locked down IT environments updated during GTP process 3. Can only view parent and children (not multi-levels) 4. Multi-node views limited by memory (parent and children) 30
- 31. This slide deck is part of a recorded webinar. To view the FREE recording of this entire presentation and download the slide deck, go to www.senturus.com/recorded-webinars.php You will find this—and many other recorded webinars-- under the “IBM Cognos Enterprise Planning and TM1” 31
- 32. Product Differences as related to IBM Cognos Planning IBM COGNOS TM1 32
- 33. TM1 Scalability • TM1 is a 64 bit application (versus 32 bit for EP) • TM1 handles Sparsity (EP does not) – Only allocates memory for non-zero cells – Only allocates memory for leaf level cells • All data remains on the server (no client downloads) • All metadata is maintained and held centrally – Changes are immediately available • Load Data directly into the Cube – Data is immediately available once loaded • All data is immediately available for reporting and Excel 33
- 34. Dimensions • TM1 has allows multiple aliases and attributes – The Account Dimension in TM1-101 would require at least 5 d-lists in EP • Code and Description • Code Only • Data Entry Subset • Analysis Subset • Default Subset • TM1 Allows alternative hierarchies • TM1 has a ‘graphical’ hierarchy manager • TM1 allows subsets on the same dimension • TM1 allows security against any dimension in the model (EP only allows on workflow dimension) 34
- 35. Leveraging Senturus’ Experience • Contact Chris Fargo to line up a no- charge Planning Product Strategy assessment for existing Cognos Planning clients – Does it make sense in your situation to: • Stay with status quo? • Upgrade to IBM Cognos Planning 10? • Upgrade to IBM Cognos TM1? • Other? • Chris Fargo 510.473.7096 cfargo@senturus.com 35
- 36. This slide deck is part of a recorded webinar. To view the FREE recording of this entire presentation and download the slide deck, go to www.senturus.com/recorded-webinars.php You will find this—and many other recorded webinars-- under the “IBM Cognos Enterprise Planning and TM1” 36
- 37. Contact Senturus Senturus, Inc www.senturus.com sales@senturus.com 888-601-6010 37
- 38. 38 38 38