1

Confidential - subject to local labour processes and discussion with relevant work councils

2

AGENDA

1. About AXA

2. Context

3. Architecture Overview

4. MDM project

3

AXA Group Solutions at a glance…

AXA is one of the world leading insurance and asset management groups, serving 102 million clients, individuals and business, in 56 countries. One of its Company is AXA Group Solutions which:

Serves most of AXA’s entitiesHas built its service offerings according to IT ambitions of AXA entities / Lines of BusinessHas put the Culture of Trust & Achievement as a business imperativeIs proving its commitment to Corporate Responsibility by putting it into action every day

4

AGENDA

1. About AXA

2. Context

3. Architecture Overview

4. MDM project

5

A Larger transformation program named FLYER…

FLYER Program has been launched in 2007.

FLYER is about convergence of processes & systems for support functions in Europe and is presently made of 2 Finance & Accounting transformation projects:

• SHIP (Investment Accounting & Controlling)

• COPERNIC (Finance & Accounting)

FLYER Program has been launched in 2007.

FLYER is about convergence of processes & systems for support functions in Europe and is presently made of 2 Finance & Accounting transformation projects:

• SHIP (Investment Accounting & Controlling)

• COPERNIC (Finance & Accounting)

Main benefits:Consistent interpretation of group Accounting principles, Reduce crunching activities, Avoid multiple investments on common topics (SII, IFRS, etc..) &

Support Group transversal initiatives.

Main benefits:Consistent interpretation of group Accounting principles, Reduce crunching activities, Avoid multiple investments on common topics (SII, IFRS, etc..) &

Support Group transversal initiatives.

6

Flyer was initiated as a large project that contributes to the transformation of the European finance function

Project that aims at implementing a Target Operating Model (TOM) to the European finance function. The TOM consists of two elements :

A Finance Shared Services Center (FSSC) operated from Pune (India) by AXA Business Services • to support COPERNIC countries • to allow local resources to be more

focused on financial analytical tasks and decision making process

A common Finance & Accounting solution based on shared accounting processes & systems for insurance companies in 9 European countries (Initially)

COPERNIC Common Operating Platform for European Reporting & IFRS Consolidation

COPERNIC Common Operating Platform for European Reporting & IFRS Consolidation

Finance & Accounting Solution Finance shared service center

SHIPSHIP is covering a large scope of Investment accounting and reporting activities all

across Europe

SHIPSHIP is covering a large scope of Investment accounting and reporting activities all

across Europe

7

The benefits of the project are strong for the Group on the long-run…

Four major benefits can be underlined for the project :

1

2

3

4

Consistent AccountingIncrease the security of the Group’s financial statements’ preparation

Consistent AccountingIncrease the security of the Group’s financial statements’ preparation

Improved AccountingHelp finance teams to focus further on their analytical work(reduce crunching activities)

Improved AccountingHelp finance teams to focus further on their analytical work(reduce crunching activities)

Safer organizationReinforce finance function in Europe through shared system and organization

Safer organizationReinforce finance function in Europe through shared system and organization

Optimized costsContribute to group efficiency targets through shared systems, increased automation and implementation of a shared services centre

Optimized costsContribute to group efficiency targets through shared systems, increased automation and implementation of a shared services centre

8

Flyer Domains & Tools Scope

SubLedgers & Bank communication /

reconciliation

Reporting

Consolidation

Master Data

Domains Systems

CAESAR / SAP-ECC (GL) / BW-BO

SAP-ECC

Ariba Invoice / SAP-ECC (AP)

SAP-ECC (AA)

SAP-ECC / Magnitude

BW / BO

SAP-ECC (AR)

SAP-ECC (CO)

CashPooler

Visuel Rappro

Finance & Accounting

9

9

Operational Account (CoA), Entity, Currency, Product, Segment, Portfolio, Insurance Category, Branch, Country, Maturity date, Type of reinsurance, etc.

MD for ReportingMD for

Reporting Hierarchies of

accounts, products…

Link between Operational CoA and MICA accounts, etc.

MD for ClosingMD for Closing Master Data used to control postings (sets of accounts, CoA Group

status zone, transcodification tables, etc) Master Data used to execute General Ledger routines currency

revaluation, P/L allocations…, etc.

MD for ConsolidationMD for Consolidation

Consolidation Type of flows

Consolidation Currency codes and rates

etc.

MD for Subledgers

MD for Subledgers

Vendors Customers Assets

Focus on MasterBusiness view

“Master Data” encompasses all the static information used: To post financial information with the required detail, To operate all posting / closing / reporting / consolidation processes – see example below

Below are provided some examples :

10

ProcessProcess

PeoplePeople

ToolsTools

OrganisationOrganisation(business and IT)(business and IT)

Portugal

UK&I Belgium

Germany

Switzerland

ItalyFrance

Spain

FSSC

A complete platform to serve 9 countries

11

ProcessProcess

PeoplePeople

ToolsTools

OrganisationOrganisation(business and IT)(business and IT)

A complete platform to serve EU + USA + Japan + Asia = 23 countries

CN, HK, ID, IN, LK, JP, MY, PH, SP, TW, TH, VN

US

BE, CH, DE FR, IT, PT, SP, UK/IE, FSSC (ID)

12

AXA Tech (IT infrastructures)

AXA GS Finance Solutions

The Flyer TOM defines the scope of responsibilities between 5 main stakeholders

AXA Business Services

Finance Shared Services Centre

Local AXA Entities

Finance Department

GIE AXA (Plan Budgets-Résultats Central)

Finance & Accountingoperations

2

COPERNIC solution enhancement, strategy

designing and monitoring

(RUN mode)

1

13

AGENDA

1. About AXA

2. Context

3. Architecture Overview

4. MDM project

14

Magnitude (Copernic & Group)

SAP BW

Architecture Overview

C D

I L

Countries

Legacy system

Legacy System

LegacySystem

Legacy System

LegacySystem

Loca

l In

tegr

atio

n La

yer

Loca

l I.L

…

Legacy System

LegacySystem

Loca

l I.L

…

SAP ECC

Group IFRS

Group IFRS

Local GAAPLocal GAAP

Complementary Reporting Datamart

Complementary Reporting Datamart

Financial DatamartFinancial DatamartA posteriori ReconciliationsA posteriori Reconciliations

MagnitudeMagnitude

Transverse Master Data Process

15

As Is Process: MDM Will Manage Interfaces Interface Inventory – Master Data Flows In Addition to a manual process

SAP AA

SAP AP

SAP GL

SAP CO

SAP BW

M3

GroupMagnitude

CopernicMagnitude

M6

CDILCDIL

CDILCDIL

CaptionCaption

Copernic ScopeCopernic Scope

Copernic Data

Integration Layer Area

Application Out of scope of

Core Copernic

Application in scope of Core

Copernic M7

Bank Reconciliation

Tool

Bank Communication

Tool

Banks

Local DWH /taxes/etc

AribaAriba

CountriesLegacy system

Legacy system

Legacy System

Legacy systemLegacy

System

Legacy System

Loca

l In

tegr

atio

n La

yer

M1A

ECCECC

Ariba

SAP AR

M1B

M8

M4

M2

Banks

M9

M5

M 10

M 11

16

What are our challenges ?

1st core

implementatio

n in Finance

Industry

Complex unified master data model

Pioneer

=

Y flows

1st worldwide

convergenc

e project

within AXA

decentraliz

ed GroupIntegrate European cultural

differences

No step by

step

implementatio

n : all

components in

the same time

Encompass

Tools - off

shoring for

business and IT

local

organization

target model for

BAU

Pioneer=

Volume

Pioneer=

Build reporting fonctionnalities

in same timetable than

GL

Pioneer=

Sub ledgers changed

in the same calendar

(investment

accounting,

procurement..)

17

AGENDA

1. About AXA

2. Context

3. Architecture Overview

4. MDM project

18

Business Rationales

Context & stakes

In scope of FLYER, Master data updates are managed using either manually process (via Excel/Access, ...) either with homemade tools:

Manual Development and Deployment High Build Workload / NRTs phases needed for each update

operationVery long and complex propagation process Insecure process / Human errors + data refreshed using non

synchronized interfaces

19

AXA MDM Project

In the context of FLYER, Business and IT teams are updating on a daily basis Master data in the SAP productive system and in particular, the chart of accounts and variables for analysis.

The only way to avoid bugs and to completely control quality is to implement automated management and effective controls of these data,

AXA Group Solutions was seeking for a Master Data Management (i.e. MDM) solution to manage efficiently Non transactional data repositories (i.e. Charts of Accounts, Product, etc.),

At the end of 2013, AXA performed a deep study based on precise costs, flexibility, scalability and architecture criteria that lead to shortlist two tools that suited our needs and then finally chose Orchestra Networks EBX solution with support of APGAR CONSULTING

Model, manage and govern any domain of reference and master data

Reference Data

Thin

gs

Partie

s

Relationships

Master & ReferenceData

Multidomain MDM/RDM Platform

Collaborative, workflow-driven user interface for business users

(internal & external)

Central master data repository based on multi domain data

models

Integration of master data with any system and middleware

platform

Supply Chain

Enterprise Resource Planning

CustomerRelationshipManagement

Human Resources

Big Data

Enterprise PerformanceManagement

Sales Reporting

Business Intelligence

Products

Assets

Customers

Suppliers

Legal Entities

Financial Hierarchies

Reference Data

Operational

Systems

EPM and BI

Finance

Sales

Marketing

ProcurementHR

Operations

Manage the entire life cycle of master data

MeasureIntegrateManageControlDesignDefine

Business terms & definitions

Data & workflowmodels

Data qualityand validation

Data & hierarchyManagement

Integration anddistribution

DQ KPIs anddashboards

Shared features

Version Controland history

Collaborativeworkflow

InheritanceEngine

Security &Permissions

23

Key points of improvementWHY MDM ?

4. Ensure alignment between all Flyer Systems

• Description: Ensure alignment of MD changes between SHIP & COPERNIC, considering their interdependences

• Lessons learnt: Several “re-alignment” campaigns performed in 2011/2012 due to parallel MD processes

4. Ensure alignment between all Flyer Systems

• Description: Ensure alignment of MD changes between SHIP & COPERNIC, considering their interdependences

• Lessons learnt: Several “re-alignment” campaigns performed in 2011/2012 due to parallel MD processes

1. Improve Data Quality / Controls

•Description:• Ensure alignment of build vs design• Ensure correct process is followed (IFC

coordinator)• Ensure control of the authorized modifications

against the data already existing in prod •Lessons learnt: Avoid reproducing major incidents in production on CoA (P&L & B/S setting)

1. Improve Data Quality / Controls

•Description:• Ensure alignment of build vs design• Ensure correct process is followed (IFC

coordinator)• Ensure control of the authorized modifications

against the data already existing in prod •Lessons learnt: Avoid reproducing major incidents in production on CoA (P&L & B/S setting)

2. Accelerate MD update delivery

• Description: The current MD process shows an average 4-9 days timeframe for MD CR lifecycle for BAU/PGLS changes

• Lessons learnt: All countries asked for a reduction in this timeframe, considering their constraints for the closing and knowing that most of the data change requests are submitted just before closing period (see appendices)

2. Accelerate MD update delivery

• Description: The current MD process shows an average 4-9 days timeframe for MD CR lifecycle for BAU/PGLS changes

• Lessons learnt: All countries asked for a reduction in this timeframe, considering their constraints for the closing and knowing that most of the data change requests are submitted just before closing period (see appendices)

3. Facilitate updates propagation

• Description: MD changes should be propagated consistently to all COP environments (LIL, CDIL,…)

• Lessons Learnt: Several massive rejects on Feeders data due to M2 interface & management of versions

3. Facilitate updates propagation

• Description: MD changes should be propagated consistently to all COP environments (LIL, CDIL,…)

• Lessons Learnt: Several massive rejects on Feeders data due to M2 interface & management of versions

5. Reduce workload related to MD updates

• Description: Propose changes in order to minimize the workload burnt on MD updates in the future

5. Reduce workload related to MD updates

• Description: Propose changes in order to minimize the workload burnt on MD updates in the future

24

Target Architecture Functional Architecture Assessment with MDM

Strengths

• Flexible workflow for MD propagation

• MD central repository• Automated process• Reduced manual effort• Previous mechanism is

available as a failback scenario

Weaknesses

• Additional platform to maintain

• Additional interfaces to control and monitor

Constraints

• Need of ETL solution• Synchronization between

MD model changes and MD data changes

• PRD-> non-PRD communication

Current assessment for Entity With MDMClearquest (2 scenarios)

Submit the automated

change request

Submit the automated

change request

SAP ECC

Review and approve

propagation

Review and approve

propagation

Country / MDM POC

Central Team / MD team

Build / IT support

Manual flow

Automated flow

EBX5 PRD

Data Integration Layer

Conversion + propagation Conversion + propagation

BW Ariba

Backend

BuildDEVBuildDEV

TestQA

TestQA

DeployPRD

DeployPRD

Update the file format

for change

Update the file format

for change1

1

2

Automated MD propagation

Manual MD propagation

Review the changes and

update the central white paper

Review the changes and

update the central white paper

Change CQ status

according to MDM WF

Change CQ status

according to MDM WF

Change WF status

according to RM

Change WF status

according to RM

Change CQ status

according to RM

Change CQ status

according to RM2

25

IS ArchitectureTarget application landscape architecture

Business Systems

Central Integration LayerOrchestra Networks EBX5 MDM

COP ECC

SHIP2 ECC

BW

HTTPS flow / SOAP SSL Webservice

File Transfer (UDM)

Internal Data flow

Technical Components

Business Applications

Clearquest

Citrix

EBX AS (Tomcat)

SAP RFC/SNC / TCP/IP secure proprietary protocol

Web Server (Apache)

ClearQuest

ETL PRD

SAP Non-PRD

Ariba

Non-PRD

Active Directory

SMTP

Ariba Non-PRD

Ariba

File Watcher

TIVOLI

File Watche

r

TIVOLIORA Shared Platform

SMTP Gateway

Dedicated VLAN

File System

EBX DB

26

IS ArchitectureTarget application landscape

DEV

COP ECC PRD

SHIP2 ECC PRD

BW PRD

HTTPS flow / SOAP SSL Webservice

File Transfer (UDM)

Internal Data flow

Technical Components

Business Applications

SAP RFC/SNC / TCP/IP secure proprietary protocol

DEV

CDIL PRD

Ariba PRD

File System

QA PRD

CDIL DEV CDIL QA

MD

ME

TL

Info

rma

tica

Bu

sin

ess

Ap

plic

atio

n

EBX DEV

EBX QA

QA+CERT PRD

COP ECC QA

SHIP2 ECC QA

BW QA

Ariba QA

COP ECC CERT

SHIP2 ECC CERT

BW CERT

Ariba CERT

COP ECC DEV

SHIP2 ECC DEV

BW DEV

Ariba DEV

EBX PRD

Fro

nte

nd

Citrix DEV Citrix PRDClearquest DEV

ClearQuest

Clearquest PRD

ClearQuest

SMTP

TIVOLI

Network SharedComponents

SVN

27

The benefits of the project are strong for the Group on the long-run… Impact on Flyer MDM Process

Key benefits of Flyer MDM Project

•Share 1 MDM platform for all countries

•Redefine Accounting Master Data processes in order to maximise convergence of MDM process & enable support of Offshore teams

•Define one common language for MDM Process in Europe• 1 common data model & data governance body• 1 common accounting & reporting system• 1 common Target Operating Model

Key benefits of Flyer MDM Project

•Share 1 MDM platform for all countries

•Redefine Accounting Master Data processes in order to maximise convergence of MDM process & enable support of Offshore teams

•Define one common language for MDM Process in Europe• 1 common data model & data governance body• 1 common accounting & reporting system• 1 common Target Operating Model

Mutualizing the MDM process over all the countries in scope of Flyer program: Mutualizing the MDM process over all the countries in scope of Flyer program:

28

SAP (ERP):

SOA Framework:

The Enterprise software that addresses solutions for managing a company for its master data, GL, transactions …

The Services framework from AN Info Systems GmbH, that enables us to develop and deploy unlimited data services in Real time Mode in a Plug & Play model.

Orchestra Networks:Multi-domain (Entities, Ref Data, GL, BW, CoA …), Localization for 23 countries, Hierarchy Management, Flexibility, Model Driven, Data Quality, Distributed Deployment, Security…..

Apgar Consulting :

MDM Methodology and Fast-tracks