Movex@Actelion

1. Movex@Actelion

2. Agenda • Actelion, a short portrait • Migration to M3: Background • History of M3 at Actelion • System outsourcing • Lessons learned • Success story figures and contact Movex@Actelion

3. Agenda • Actelion, a short portrait • Migration to M3: Background • History of M3 at Actelion • System outsourcing • Lessons learned • Success story figures and contact Movex@Actelion

4. Actelion: Facts and Figures Movex@Actelion

5. Agenda • Actelion, a short portrait • Migration to M3: Background • History of M3 at Actelion • The project approach • System outsourcing • Delivery scenario • Lessons learned • Success story figures and contact Movex@Actelion

6. MigrationMovex V12 Sp 13 to M3 • Why to change to M3? • V12 get out of maintenance per September 2008 • Support get more and more difficult • Missing Audit Trail functionality in Supply Chain • New Roles Based Concept for Enhanced and Simplified Security Administration • LSO/LES • New Life Cycle Manager Simplifies the Installation, Maintenance and Monitoring • A new comprehensive and easy-to-use traceability package, making it possible to define necessary IT controls to comply with legal (SOX) or industry requirements (FDA) Movex@Actelion

7. MigrationMovex V12 Sp 13 to M3 • What were the timeline challenges for this project? • Worldwide usage of M3 need to get started at the same day • Actelion operates 1 Company with multiple division, facilities and ware houses • Best date to change over to M3 was driven by month end closing and finalization of quarterly based external auditing • Implementation and modification of Quality and ITGC controls during the migration project Movex@Actelion

8. Agenda • Actelion, a short portrait • Migration to M3: Background • History of M3 at Actelion • System outsourcing • Lessons learned • Success story figures and contact Movex@Actelion

9. History:Set-up Movex within Actelion • Start Version 11.2 in 2000 • Start with CH and USA in Version 11.2 • Single use of FIM • Start up COM and MPM in 2001 • Other subsidiaries start up with Movex in 2001 • Worldwide utilization of Movex 2002 • Upgrade Version 12.Java in 2004 • Roll-out Logistics into selected affiliates • Upgrade to M3 in 2008 • Installation LSO/LES in 2010 Movex@Actelion

10. 33 Countries running M3 • Canada • USA • Mexico • Brazil • Japan • Australia • China • Korea • Singapore • India • Turkey • Greece • Israel • Russia • Switzerland • Germany • France • Netherlands • UK • Nordics • Austria • Italy • Spain • Luxembourg • Cyprus • Czech • Slovakia • Poland • Portugal Movex@Actelion

11. Partcipation of Actelion for Co-Development • Some countries are not yet available as market modification • Graham asked Actelion to participate in the Co-Development • Number 1 country is Turkey • Under the leadership of Graham a team has been assigned • Team members are from Lawson and Customer • Actelion took over the input what are the legal demands for Finance in Turkey • To support LPD we involved our tax Councel and the FM Turkey • Project definition will been written by Lawson • Customers will sign the contract for the Co-Development • The development will start after sign off the contract • Co-development market modifications will be part in our service contract Movex@Actelion

12. Financestructure and budgeting • 55 legal entities with one common finance structure • Accounts • Cost Center • Activities/Projects • Products • Budget and actual are done to all those dimensions • Revaluation local currencies to group currency (CHF) • US-GAAP and statutory accounting • Consolidation Movex@Actelion

13. Logisticsstructure and budgeting • 55 legal entities with one common logistics data structure • Facilities • Warehouses • Price Lists • Items • Order Types • Product Costing • Centralized Budget and actual controls • Centralized Inventory Management • Audit trail Movex@Actelion

14. Datastructure • Common chart of accounts US-GAAP based • Common cost center and cost center structure • Common projects and project structure • Common products and product structure • Common data structure of customer and supplier master data • Common warehouse and facility data • Company parameter are centrally maintained • Restrictive handling of local exceptions Movex@Actelion

15. Follow Up Projects After Upgrade to M3 • Additional functions within M3 Toolbox • Invoice scanning • Standardized Interface for E-banking to Deutsche Bank • Installation LSO/LES Movex@Actelion

16. Agenda • Actelion, a short portrait • Migration to M3: Background • History of M3 at Actelion • System outsourcing • Lessons learned • Success story figures and contact Movex@Actelion

17. M3 InfrastructureOutsourcing Movex@Actelion

18. Agenda • Actelion, a short portrait • Migration to M3: Background • History of M3 at Actelion • System outsourcing • Lessons learned • Success story figures and contact Movex@Actelion

19. Lessons Learned Which activities and processes worked well? • Internal professional PM from a “neutral” department • Weekly project team meeting • (Bi) weekly project status reporting to all involved parties • Frequently onsite project meetings with external partners for status,risk & issue and next activities updates • Small dedicated project core team with clear roles and responsibilities • Early project involvement of Actelion’s GQM department • Confirmed commitment for dedicated Lawson resources through the whole project life cycle • Go/NoGo decision meeting with all impacted parties (externals & internals) Movex@Actelion

20. Lessons Learned Which could have been improved, and how? • Financial budget tracking was not easy through to the fact of different cost centers at Actelion and on the other side only one collective Lawson invoice • Improved cost transparency in the budget setup process with Lawson • Only a low number of Lawson project team members were already up to speed for their new product release M3 as Actelion was one of the first Lawson international customer which upgraded to the latest version of M3 • We face again that Actelion is one of the first M3 user upgrade to LES • It‘s mandatory to apply an expert team for strategically und operational activities on both side • International expertise is required Movex@Actelion

21. Lawson User GroupInternational Operating Companies Founding April 14 2010 in Germany There should be a platform to collect information Release management Market modification (Lawson, Partner, Co-Development) Movex in General Complete set of Lawson documentation should be available for all customers and not a separated documentation database for Lawson Better search function within the knowledge base There should be a forum where customers and Lawson can communicate open chat forum blog in MyLawson Improvement of I-support quality Movex@Actelion

22. Agenda • Actelion, a short portrait • Migration to M3: Background • History of M3 at Actelion • System outsourcing • Lessons learned • Success story figures and contact Movex@Actelion

23. Success Story Figures • Successful Migration Project • Change over to M3 at the same date all around the globe (Big Bang) • M3 get redesigned for Actelion today's and future demands • Lawson supported the whole project with an effective team • Lawson centralized project management coordinated all resources necessary during the migration phase • Decision for doing the upgrade step wise was the right one • Next project is ahead (v10) Movex@Actelion

24. Thank you very much for your attention! • Contact Information: • Volker.Dierks@actelion.com Movex@Actelion