1. Jonathan Cunliffe Group IT Projects Manager United Business Media Group Reporting Project

2. United Business Media Who are United Business Media?

3. United Business Media A leading provider of business information services to the technology, healthcare, media, automotive, financial services and property industries Provide services in news distribution, market research, publishing and events to customers across the globe Brands include:  PR Newswire - world’s leading corporate news distribution service  NOP World, one of the largest market research groups globally  CMP, the B2B media and exhibition group operating in the US, UK, Asia and Europe.

4. Major UBM Products

5. UBM Media Channels

10. United Business Media What size of system were we implementing?

11. United Business Media For Group Reporting, Divisions report to Head Office  10 Divisional Offices in US  2 Divisional Offices in UK  1 Divisional Office in Asia  Head Office operations in Ireland, Luxembourg, NY and London 25 divisional users of the system plus Head Office staff

12. The Project and its Drivers When and why did the project start?

13. The Project and its Drivers 2003 - Decided to replace Group Reporting system Main Drivers were:  End of life of existing application  Looking for enhanced analysis and production reporting capabilities for group management  Statutory and Management applications to sit on 1 platform  Wanted to automate cash flow  Required more real-time validation checks  Aiming for improved inter-company reconciliation  Wanted integration with local accounting applications such as Oracle GLs  Looking for quicker system operation in general From beginning considered Project Management methods

14. Software Selection What steps did we take to select the vendor and software?

15. Software Selection First collected “feature” requirements using Use-Case modelling Drew up a list of all known vendors 20+ and then using a Gartner survey, narrowed this down to 5 Initial introduction to each of these products and requirements sent to vendors Utilised scripted scenarios Cartesis Magnitude was chosen as most suitable product for our requirements on this particular project

16. Selection of the Vendor and Software Why did we choose Cartesis?

17. Selection of the Vendor and Software Why did we choose Cartesis?  The Magnitude software met our feature requirements  Specifically Intercompany Reconciliation was better  Cartesis showed best understanding our particular requirements  Known quantity as a supplier long relationship with UBM

18. Selection of the Vendor and Software What were the challenges?

19. Selection of the Vendor and Software Challenges:  Getting stakeholders to buy in to the process  Trying to remove prejudice towards/against certain products  Concentrating on our requirements rather than being impressed by features that were not actually useful to us

20. Project Management Approach What project management approach did we take?

21. Project Management Approach Used PRINCE2 Project Method, which revolves around:  Management by exception  Defining the requirements  Having representatives from the users, suppliers and the business  Has a project manager and project assurance  Actively manages risks and issues  Puts in place a clear communications plan  Focuses on quality checking  Has specific planning techniques Timing was not ideal But the Project Method did deliver and is being used on many other projects now

22. Stakeholders

23. DCFO CFO Group Head of Accounts And Divisional Users Group Financial Systems Analyst And Cartesis Project Manager from US HO Group IT Projects Manager Internal and external team managers

24. Results and Benefits What did we get from the project?

25. Results and Benefits Faster consolidation – from hours to seconds Enhanced usability and interface Up-to-date software Running on industry standard databases Significantly greater detail of data Many more reporting/analysis options – company/FX simulation More flexible to update company and account structures than previous application Platform upon which we can expand our management systems

26. Key Lessons Learned What were the key lessons to learn for the future?

27. Key Lessons Learned As part of PRINCE2 process an End Project Review Lessons Learned - 5 main areas  Understand the method to be used and treat project roles seriously  Do not under-resource from the start  Do not start project until user requirements agreed and signed  Manage risks - but also give each an owner  Operate a dual-level communication channel with vendor

28. Future Steps What are we going to do next?

29. Future Steps Launch our Statutory part of the system with IFRS capability for interims, followed by US GAAP capability for year end Refinement Project – to enhance the applications further to remove some areas where we evolved the system Roll out Magnitude management system for one of our divisions CMP Medica  Additional 30 Offices  Subset of our Group Application so quicker development  Possibly explore this model for other group companies Ensure the applications are SOX compliant for next year Consider Magnitude for planning, forecasting and budgeting

30. Summary In summary…

31. Summary Challenging at times and many lessons learned Overall has been a successful implementation Project Team now fully understands the benefits of Project Management You may be able to benefit from our experience Questions…