Top 10 Maintenance Issues	Issues with standard tools	CXO-Cockpit approach
1. Reporting definitions	All tools use a separate repository for reporting definitions. Hence the definitions of basic items such as Profit and Loss is defined multiple ways	One repository, one set of central definitions
2. Technical Infrastructure	Reporting tools do not always get installed on one server, resulting in high costs of operations, especially when outsourced on a pay-per-server basis	CXO-Cockpit installed on one server
3. Client installations	Standardization of client installations is required, due to the use of Java Virtual Machines and Excel. IE8 not supported yet. High coordination effort required.	No local install. IE8 supported
4. HFM Performance	Performance issues for Web Analysis (especially with multiple users) and SmartView (when large reports generate high numbers of subcubes) on HFM	High performance always
5. Bugs	Long-time known unresolved bugs (e.g. the drill-up in Web Analysis resulting in a query in the wrong entity structure.	Monthly patch process for potential bugs
6. New versions	Various product have independent update frequency resulting in time-critical upgrade projects.
7. Training	All reports have separate intensive training courses for administration and end-users. The total training needed for an administrator is more than 10 days	One day training for administrators
8. SmartView file size	Extensive use of smartview result in large files (>10MB) causing problems with E-mail and storage.	Small CXO-Cockpit Excel-add-in files (typically 100-300KB)
9. Future	Unclear roadmap of Web Analysis (end of life) and OBIEE (still not available on HFM) leaves administrators uncertain of how to structure.	Consistent roadmap of one product
10. Integration	There is no Oracle reporting tool that works cross all Oracle EPM products, causing an even higher number of reporting tools if multiple Oracle EPM products are used.	One product for all Oracle EPM products

Top 10 Maintenance Issues	Issues with standard tools	CXO-Cockpit approach
1. Reporting definitions	All tools use a separate repository for reporting definitions. Hence the definitions of basic items such as Profit and Loss is defined multiple ways	One repository, one set of central definitions
2. Technical Infrastructure	Reporting tools do not always get installed on one server, resulting in high costs of operations, especially when outsourced on a pay-per-server basis	CXO-Cockpit installed on one server
3. Client installations	Standardization of client installations is required, due to the use of Java Virtual Machines and Excel. IE8 not supported yet. High coordination effort required.	No local install. IE8 supported
4. HFM Performance	Performance issues for Web Analysis (especially with multiple users) and SmartView (when large reports generate high numbers of subcubes) on HFM	High performance always
5. Bugs	Long-time known unresolved bugs (e.g. the drill-up in Web Analysis resulting in a query in the wrong entity structure.	Monthly patch process for potential bugs
6. New versions	Various product have independent update frequency resulting in time-critical upgrade projects.
7. Training	All reports have separate intensive training courses for administration and end-users. The total training needed for an administrator is more than 10 days	One day training for administrators
8. SmartView file size	Extensive use of smartview result in large files (>10MB) causing problems with E-mail and storage.	Small CXO-Cockpit Excel-add-in files (typically 100-300KB)
9. Future	Unclear roadmap of Web Analysis (end of life) and OBIEE (still not available on HFM) leaves administrators uncertain of how to structure.	Consistent roadmap of one product
10. Integration	There is no Oracle reporting tool that works cross all Oracle EPM products, causing an even higher number of reporting tools if multiple Oracle EPM products are used.	One product for all Oracle EPM products