Implementing Hyperion in Multiple Geographies Anjula Sengar and Canan Akkan AMOSCA

You might also like

Download as pdf or txt
Download as pdf or txt
You are on page 1of 23

Implementing HFM in multiple

geographies
Anjula Sengar/Canan Akkan
Amosca
AGENDA

01 Brightstar Overview

02 Project Overview

03 The Implementation

04 Go Live & Challenges Ahead

Brightstar Proprietary & Confidential 2


Brightstar.
Serving Wireless.

Approximately
2 billion mobile devices
are sold
each year

3
50,000+ customers & over 100,000 points of sale
OEMs Operators Retailers & Dealers

We Serve the World’s Best

4
Delivering products &
services in more than
DENMARK 125+ countries with
FINLAND
GERMANY
HUNGARY
local presence in 50+
NETHERLANDS
NORWAY
countries
SPAIN
SWEDEN
U.S.
CANADA UNITED KINGDOM

ARGENTINA HONDURAS
BOLIVIA JAMAICA
BRAZIL MEXICO
CHILE NICARAGUA
COLOMBIA PANAMA
COSTA RICA PARAGUAY
DOMINICAN REPUBLIC PERU BOTSWANA
ECUADOR PUERTO RICO DUBAI AUSTRALIA
EL SALVADOR URUGUAY EGYPT BANGLADESH
GUATEMALA VENEZUELA MOROCCO FRENCH POLYNESIA
MOZAMBIQUE HONG KONG
NAMIBIA INDONESIA
NIGERIA JAPAN
SOUTH AFRICA MACAU
TURKEY MALAYSIA
UGANDA NEW ZEALAND
ZAMBIA SINGAPORE
SRI LANKA
THAILAND
VIETNAM
AGENDA

01 Brightstar Overview

02 Project Overview

03 The Implementation

04 Go Live & Challenges Ahead

Brightstar Proprietary & Confidential 6


Project Overview with AMOSCA
The end game – Corporate Vision

• Common ERP (under review)

• Common global platform for Financial


Performance Management

• HFM, Hyperion Planning

• Global Financial and Management


Reporting solution

• Global Budgeting and Forecasting


solution

8
European Reporting Strategy
Why the need for change? What are we trying to achieve? How do we intend to go about it?

• Enable support of Corporate, • Key stakeholder solution and


• Fragmented systems and processes Regional and entity reporting process design
across financial and management requirements more effectively than is
reporting is driving misalignment, possible now through
waste and excessive month end cycle implementation of European HFM • 3 phase plan to improve reporting
times solution– drive close cycle times systems and processes
• Finance resources disproportionately down to 4 days by December 2014
support information production • Increase business insight and
rather than value added insight and • Corporate sponsorship
consistency of reporting
advice.
• Reduced workload through:
• Analytical and business insight • Self sufficiency, leveraging experts as
activity are largely manual. - Standardised & simplified processes. required
• Corporate and external reporting - Maximised use of automation,
and information requirements, systems and optimised processes to
demands will not decrease improve the quality and timeliness of
outputs and
• Align European solution with Global
solution vision, enable retro fit back
into global design by leveraging
existing IP and procured software
and valid solution work completed to
date
Future State – what do we want
Objectives
to end up with
1. Create a European regional reporting strategy and capability that is consistent with Corporate
reporting systems vision, and leverages Brightstar Corporate strategy, platforms and solutions

2. Support B* Corporate, European region and divisional financial, management reporting requirements
with European region HFM solution

3. Build European reporting solutions that allows future integration to Corporate application, and
supports regional information and reporting requirements

4. Significantly reduce monthly, quarterly and yearly reporting cycle times by December 2014 (from 16
days to 4)

5. Create a single, integrated consistent framework for all types of monthly, quarterly and annual
reporting processes and requirements in Europe

6. Drive data quality, data and process ownership

7. Reduce the cost and effort and manual interventions associated with reporting

8. Minimum disruption, Don’t try and fix what’s not broken – eg ERP & Insight

9. European owned, managed and maintained solutions and processes that can evolve with the business
10
The HFM that is currently being designed and planned for implementation to support financial
close processes has a number of key gaps need to be resolved at Corporate, regional and legal
entity levels

Challenges and Gaps Key Questions


• No integrated EPM and BI solution architecture exists • Does the current HFM solution design support the
to support all Corporate and / or regional and / or legal vision for an integrated, global financial reporting
entity financial reporting requirements solution
• “Use Cases” - end to end, integrated functional and process
requirements for financial reporting activities supported by • Are all financial reporting, use case, functional,
HFM has not been completed. technical and process requirements met by the
solution.
• Not all procured solutions (eg Essbase and OBI) are
currently being leveraged, or included at all in solution • Are the above requirements known and
design for Brightstar documented?
• HFM solution design is focussed on Corporate,
regional and legal entity support and benefit is low or nil • How do we best leverage ALL the available
procured software to meet the above
• Process re-engineering, deployment, training and change requirements, once known and validated
management plans are unclear
• Corporate and Regional management (financial) • Can the work that has been completed to date be
reporting has significant gaps that require addressing leveraged to provide benefit to, and accelerate
eg consolidated PL, BS, CF regional and legal entity financial reporting
capability
• Fiscal year end change (and implementation plans) is
out of scope and high impact if required • How do we specifically address significant
European financial reporting systems, process,
• Europe is out of scope, and currently has very limited integration and automation issues.
EPM capability.
• How can we lock in and deliver value for Brightstar
• A further 24 key gaps have been highlighted and from the investments already made in the HFM
socialised by Kris Murphy. stream

These materials are confidential and should not be printed, downloaded or distributed. BRIGHTSTAR 11
Where coming from?
• See next slide
• Typical position
• Usually described as aspirational
• Does it look familiar?
What should
How do we fix this ?
our TAX liability
be I’m sure it will
Regulators have
Concerns reconcile….
eventually.

IRS Inconsistent
Reports
Tax Regulatory Financial . . . . . . Managerial
Reporting Reporting Reporting Reporting
Merger…I’ll just add more
Future projections accounts!!
that’s easy… Finance will Fix it.

PC BAD
General Ledger
Data...
Tools
Reconciliation
Issues

Source Source Source Source . . . . . . Source


Systems Systems Systems Systems Systems
Key elements in a financial systems architecture
include:
SOURCE FINANCIAL DATA DECISION SUPPORT
DATA TRANSPARENCY
SYSTEMS STORAGE & REPORTING

Financial Consolidation Consolidation


Systems Extraction & Transformation
Engine
AP
General Ledger Regulatory &
FA Financial Management Control Statutory
Payroll
Reconciliation & Suspense BU, Product
Control Profitability
Application Financial Data
Systems Repository (or Customer
Data Marts) Profitability
IL/GS/EB Common
Ref Data Budgeting &
Etc
Forecasting

A/C Rules Engine Procurement Expense Mgt


Manual Reporting
Transactions
Messaging Infrastructure
Fixed Assets Treasury
Late Entries Reporting
Adjustments
Etc Taxation
Data Management
AGENDA

01 Brightstar Overview

02 Project Overview

03 The Implementation

04 Go Live & Challenges Ahead

Brightstar Proprietary & Confidential 15


High level systems strategy – Europe

HFM Project

16
Data Identifying Data

Pushing Data IN

Solution FDM
Financial Reporting
 Formatted Report writer
 Report, Books and batches
 Schedule email reports
 Deliver PDF or web link
 GAAP compliant
 Reporting annotations
Smartview
 Bank and Funding Partner
Reporting – “Bank Reporting”
 COE Staff Results
 CFO Main Deck
 EBITDA Master
 Monthly Profile ROIC Detail
 Quarterly Analytics Template
1. Reporting Nature
2. Geography
3. Line of Business
4. Department Cost Centre
Metadata 10 5. SoftBank Related Party
6. Details
7. Currency Overides
8. Customers
Logical Dimension Custom Dimensions 9. OEMs
10. Products

Softbank- RP
Cost Centre
Geography

Customers
Reporting

Overrides

Prodcust
Nature

Details

OEMs
LOB

Revenue accounts in PL X X X
Cost of Sales accounts in PL X X X
Total Operating Expense accounts X X X
in PL
All PL accounts X X
Balance Sheet accounts X X*
Softbank Related Party accounts in X X
PL and BS
Investment & Equty Account X X
Cash Flow Accounts X X**
EU Sales and COGS (EU specific)* X X X X
EU A/R Inventory X
AGENDA

01 Brightstar Overview

02 Project Overview

03 The Implementation

04 Go Live & Challenges Ahead

Brightstar Proprietary & Confidential 21


• Resources ( Internal and
External)
• Softbank Reporting
Requirements
• Acquisitions
• BAU processes
Thank you!

You might also like