1. Page 1 July 2010 ERP Backbone Phase 2 4 vs. 6 Year Roadmaps Comparison OPE Program P3.2. E-business - Synthesis March 9 th, 2012

2. Page 2 * when applicable, subject to the respect of antitrust law principles E-business objective is to move towards full ERP to ERP integration with major partners, combined with a complete web solution offering Michelin  dealer engagement (AVS) Dealer  Michelin engagement (LOA) TRANSACTIONAL ADVOCATE DURABLE PARTNERS COMPANY OWNED FRANCHISE Sustainable Distribution Full integration ERP to ERP of operational transactions at POS level (D2C, tools to improve dealer order taking as Tyre Selector, eLearning, capture information…) Web interface for reporting to central organization and POS manager Opportunity approach for ERP to ERP Web interface for D2C, reporting and capture information Web interface for D2C and reporting P3.2. Optimize offers commercialization via e-business Mix media – As-Is & needed evolution 100% 0% EUNA Mix media – Target 100% 0% Legend ERP to ERP Asynchronous Telephone Web ERP to ERP Synchronous TransactionalAdvocatePartners

3. Page 3 Developing e-business requires to provide tools supporting both Michelin processes and Customer processes Michelin Marketing information Order preparation / taking Order to invoice Payment Other marketing services Claim and reporting Customers Retail center process map M01 – Monitor center performance M02 – Plan business activity S01 – Manage customer relationship S02 – Manage stocks S03 – Manage human resources S04 – Promote products & services P01 – Sell tires & oil changes Legend Trend against As-Is Fully supported Partially supported / need for non intrusive customization Not supported / need for significant customization Major coverage improvements Major coverage loss Not assessed or out of scope Oracle deployment will improve Customer processes overall support, but adaptations will be needed to improve quick order process Oracle overall coverage is larger than existing tailor-made solutions, but customizations are needed to improve adaptation to Michelin business context Embedded exhaustive reports Navigation not adapted to quick orders “Push-oriented” marketing functionalities Embedded exhaustive reports “Push- oriented” marketing functionalities Availability check too late in the process E-Payment Assessment of Oracle would-be coverage P3.2. Optimize offers commercialization via e-business

4. Page 4 Though Oracle web solution (i-Store) is suitable for historical transactional commitment, it is not adapted to new SC models yet. ERP to ERP is covered Make to commitment Deploy to commitment Long term commitment Make to stock Deploy to commitment Rolling commitment Make to stock Deploy to forecast Transactional commitment Managed outsourced supply Outsourced Demand limits definition / Demand management (upfront order taking) Execution (insourced) Outsourced Execution (wholesalers) The ability to support new SC models seriously questions the web solution sourcing (i-Store?) i-Store ERP to ERP ! i-Store – Key findings ERP to ERP – Key findings  i-Store is fully embedded in the package (~web based order capture)  Full integration  Requires availability of the total backbone to be operated (resulting in high implementation lead time)  Sales agreement (Commercial terms & conditions) are not supported in i-Store  Critical concern for long-term and rolling commitment management  i-Store is fully embedded in the package (~web based order capture)  Full integration  Requires availability of the total backbone to be operated (resulting in high implementation lead time)  Sales agreement (Commercial terms & conditions) are not supported in i-Store  Critical concern for long-term and rolling commitment management ! Sales agreement  Oracle capabilities can cover Michelin needs regarding ERP to ERP integration (both synchronous and asynchronous) P3.2. Optimize offers commercialization via e-business