Hyperion  User  Group  Presentation

No v   2 0 1 6

Contents

• About  Oz• Our  History  with  Hyperion• Why  the  SAP  Hyperion  Project?• Why  PBCS?• Timeline• What  does  the  end  product  look  like?• Lessons  learned• Next  Steps

About  Oz

• ASX200  Listed  Copper-­focused  company  based  in  SA• Formed  in  2008  (ex  Oxiana and  Zinifex)• Recently  relocated  HQ  from  Melbourne  to  Adelaide  in  July  2015• Prominent  Hill  is  the  primary  operation  • Development  of  the  Carrapeteena resource  is  underway• A  number  of  Exploration  JV’s  underway  to  identify  the  next  project

• Growth  strategy  in  place  focused  on  creating  value  for  all  stakeholders

OZ  Minerals

P A G E   4 /

Operating  mine

Developing  mine

Exploration

WA

NT

QLD

NSW

VIC

TAS

ACT

SA

Gawler  Craton

Prominent  Hill  Operation• Open  pit  and  underground  operations• Copper  concentrate  (containing  gold  

and  silver)

Carrapateena  Project• Project  in  FS• Iron  oxide  copper-­‐gold  deposit

Mount  Keith  JV• Yandal  One  JV  with  Toro  Energy  • Exploring  for  nickel  sulphide  

mineralisation

Eloise  Project  JV• JV  with  Minotaur  Exploration• Exploring  for  Cannington  style  

lead/zinc/silver  mineralisation

Mount  Woods  JV• JV  with  Minotaur  Exploration  • Exploring  for  brownfield  copper  

resources  around  Prominent  Hill

ASX Code OZL

Shares  on  issue 299  million

Market Capitalisation ~$2.5 billion*

September  2016  cash  balance(unaudited)

$509  million

Debt No  Debt

*  As  at  November  2016

A  Growth  Oriented  Mining  Company

West  Musgrave  JV• JV  with  Cassini  Resources  • Access  to  an  established  copper/nickel  

project  and  significant  portion  of  a  new  mining  province

Coompana Province  JV• JV  with  Mithril Resources• Exploring  for  magmatic  nickel/copper  

deposits  

History  of  the  Oz  Hyperion  System

HP  Implementation

2006HP  Extension  &  

HFM  Implementation

2008Upgrade  to  11.1.2.2

20122009

Upgrade  to  11.1.1.3

• Hyperion  has  been  successfully  used  for  10  years• But  we  recognized  lots  of  scope  for  improvement  including  better  alignment  between  Operational  (HP)  and  Corporate  view  (HFM)

• Our  solutions  design  was  based  on  2006  thinking  /  so  many  things  have  changed  in  the  software  which  we  were  not  leveraging

• And  we  had  an  un  healthy  reliance  on  Smartview

Why  the  SAP  Hyperion  Project?

• Oz  Minerals’  existing  ERP  Ellipse  6.3  was  nearing  the  end  of  its  shelf  life  • Support  for  the  platform  and  version  was  scheduled  to  cease  in  late  2016• Oz’s  IT  Department  embarked  on  a  search  for  a  replacement  ERP  and/or  upgrade• At  the  same  time  Oz’s  Hyperion  system  was  becoming  due  for  an  upgrade  • The  business  undertook  an  extensive  selection  process,  deciding  on  SAP  and  partnered  with  another  Western  Australian  based  company  -­ Dyflex

• Planned  implementation  was  for  a  rapid  deployment  using  a  template  approach• It  necessitated  the  adoption  of  a  standard  mining  template’s  CoAs as  a  starting  point    • Once  the  decision  was  made  to  change  the  company’s  CoAs,  Hyperion  by  necessity  needed  to  change

• Had  tentatively  decided  on  PBCS  anyhow  as  the  numbers  stacked  up  when  looking  at  future  expenditure  over  five  years

• SAP  would  replace  Ellipse,  and  PBCS  would  replace  both  Hyperion  Planning  and  HFM

Why  PBCS?

• The  new  CoA  in  SAP  necessitated  major  changes  to  Hyperion

• Our  old  system  was  ……  old

• Decision  to  go  with  PBCS  because:-­• The  software’s  capabilities  much  extended  (ASO  a  big  one)• Lower  total  cost  over  5  years• Recommended  by  M-­Power• Consistent  with  Oracle’s  direction

Timeline

Task  Description Oct  to  Dec  15

Jan  to  Mar  16

Apr  to  Jun  16

Jul  to  Sep16

Oct  to  Dec16

Jan  to  Mar  17

SAPScope  /  AssessBuildDeploy

Hyperion

Scope  /  AssessRequirements  /  DesignBuild  Month  End  SolutionTest  and  DeployBuild  Planning  SolutionTest  and  Deploy  

Original  plan  was  to  complete  this  Nov  16.  Resourcing  

conflicts  made  caused  us  to  push  this  out

Old  On  Premise  ArchitectureSource  Data

Extract  &  Load  Data

7  x  HP  Applications  and  1  x  HFM

Jigsaw

Ad-­Hoc  Analysis

Reports

Forecast  &  Budget  Data  

Entry

Ellipse

Presentation  Layer

KeyActualPlan

Smartview

Over  time  our  solution  had  become  siloed  /  single  source  of  the  truth  compromised

HFM

FDMEE

New  PBCS  ArchitectureSource  Data

Extract  &  Load  Data

1  x  HP  Application

Jigsaw

Ad-­Hoc  Analysis

Reports

Forecast  &  Budget  Data  

Entry

Ellipse

Presentation  Layer

KeyActualPlan

SmartviewStats

Workforce

FinanceFINRPT(ASO)

Dashboards

This  is  our  single  source  of  the  truth

Some  things  are  different  /  some  are  not

Day  Stats

For  10  years  we  have  successfully  used  Hyperion  for  daily  /  weekly  reporting.

At  7am  every  day  a  series  of  reports  are  e  automatically  e  mailed  across  the  company

Validations

We  have  added  multiple  validations  into  our  system  to  highlight  issues  or  errors

Focus  on  Pre  Build  Reports  (not  Smartview)

Lessons  Learned

• Rapid  Deployment  is  easier  said  than  done,  resist  burdening  the  project  with  the  administrative  requirements  of  a  fully  fledged  project  without  time  constraints

• Would  have  been  much  easier  to  implement  PBCS  once  SAP  had  been  fully  implemented  and  the  system  and  CoAs bedded  down

• Significant  rework  caused  by  endless  “Chicken  and  Egg”  scenarios• Unforeseen  benefit  in  building  both  systems  concurrently  – the  systems  are  more  cohesive.  Built  to  work  together  not  against  each  other

• Need  the  same  cohesion  in  your  project  team.  We  have  been  fortunate  enough  to  have  people  who  are  passionate  about  delivering  the  very  best  system  they  possibly  can.

• Surprisingly  adopting  the  new  system  and  getting  people  on  board  has  been  easy.  The  change  in  ERP  was  so  significant,  it  has  stolen  the  lime  light,  and  therefore  adopting  Hyperion  PBCS  has  been  relatively  easy

• Ensure  you  have  good  partners  with  sound  technical  knowledge,  and  who  have  your  project’s  success  as  their  one  and  only  focus.

Next  Steps

• Survive  our  1st  month  end!• We  still  need  to  complete  and  test  the  new  planning  model• Due  to  our  annual  budget  cycle  we  have  completed  our  2017  Budget  in  the  existing  Hyperion  Planning  model  

• Need  to  transfer  the  underlying  data  from  the  existing  planning  model  to  the  new  planning  model  and  complet UAT

• And  then  it  will  be  year  end!• Need  to  bed  down  the  work  we’ve  done  and  Take  stock• There  is  a  lot  of  unused  functionality  in  PBCS  that  we  are  yet  to  tap  into  and  the  beauty  of  the  cloud  is  we  will  always  have  the  latest  and  greatest.

• Need  to  assess  and  then  develop  functionality  that  fits  into  our  strategy  and  aspirations  of  being  a  Modern  Mining  Company  

Thankyou

No v   2 0 1 6