You are on page 1of 15

“We are about to embark on the a BETA phase of our global ERP

Implementation Project.

This means we will create a Proof of Concept to test our Austin business
processes against the Infor M3 ERP functionality.

It will take effort from key users in our larger business units to support the
project activities and ensure that we have a robust model to identify any gaps
and quantify business benefits in going forward.”

Peter Forsyth, MD and Project Sponsor


ERP Implementation
one austin one vision one team one system

Business Case for Transformational Change

Date: June 2020


Presenters: Sandra Hansen, Project Manager | Jan Weldon, Change Manager
Please watch in slideshow mode

We will go over
these slides in
the meeting

one austin | one vision | one team | one system


3
High level end to end process

one austin | one vision| one team | one system


What we have now - current State
CREO
May have many
Financial iterative process steps,
Systems Data Extract including reconcilliation

Infor ??

MYOB Data Load


D D
D
Reckon at D at R
at
a at a ep
a Host
Soft land E a E or
E
xt Lo xtr tin
nt Spring ra ad ac g
ry Data Load
ct t
JAQ
??
Pronto
2 versions
Data Extract

Fin System ADP SugarCRM


Other
Systems
Manual one austin | one vision| one team | one system
Future state: Infor M3 - ERP FUNCTIONALITY

Business
Windchill intelligence and
CREO data analytic
/reporting tools

Data
Transfer
Birst
D
Da
at ta R
a Tr ep
E Infor M3 an or
sfe
nt r
tin
ry g
d/EPM
Data
Transfer

EDI Financial budget


ADP & forecasting
tool
System

Manual
6
one austin | one vision| one team | one system
ERP is the integrated Procurement of goods/services: Supplier information > purchase order approvals
management of main > receipting of goods/services > invoice matching > supplier payments>
business processes: credit notes > accounts payable
• supported by one Purchase CRM: Sales/Maintenance > customer information & pipeline data >
system, to Pay quotes > order entry > credit check/limits > delivery > invoicing >
• used to collect, store, credit notes > statements > accounts receivable
manage, interpret data Order to
from many business Cash
Engineering, Quality Management , manufacturing,
activities, production & warehouse processing: materials movement >
• to understand and utilise Production inventory WIP > BoM > receipt, putaway, returns > approval
resources efficiently and to Inventory process > sub-contractor operations/services
effectively ™
Cost accounting > sales tax > budgeting > GLs > journals >
Finance assets > payroll > banking maps per country >
consolidation > treasury & cash flow
Accounting software Master Data
& Integration Customer and Supplier Master Data > item data >
• deals exclusively with
accounting transactions applicable employee data > related tables> interface templates >
Performance
such as: Management
IT administration processes > automated testing
o payroll
Standard financial reports: GL, AP, AR, FA, tax, budgeting >
o accounts receivable
forecasting > cube reporting > d/EPM analytics
o accounts payable
o trial balances

7 one austin | one vision| one team | one system
Implementation approach We are here!

1. BETA Build 2. One Austin 3. Initial Implementation 4. Progression of


• Out of the box Template of ERP Solution Phased Roll out
functionality, configured • 3 x prototypes • Identified BU • All other BUs, includes
for Austin • 3 x trial data technical review
• Technical review
• Based on design rules conversions completed
from process workshops • Global processes
• Understanding of and glossary
baseline with gaps • Monitoring metrics
identified established
• Business benefits • Technical review
identified completed

8 one austin | one vision| one team | one system


BETA – what do we get

A base model in Infor M3 to visualise ERP functionality and demonstrate the business process from
Customer opportunity through to shipping.

Built on the information and process flows gathered over the past two years from all the business units.

 Configured: out of the box system functionality using system features and based on Austin’s business
processes.
x Customised: modifications to the system functionality

Note: workflow will not be enacted and forms will not have finalised format

 Build remotely (COVID19)


 Limited Austin data
 Demonstrates key scenarios
 Business benefits identified

9 one austin | one vision| one team | one system


Beta Phase High Level Timeline
June July August September

5 Jun 12 Jun 19 Jun 26 Jun 3 Jul 10 Jul 17 Jul 24 Jul 31 July 7 Aug 14 Aug 21 Aug 28 Aug 4 Sep 11 Sep 18 Sep 25 Sep

Data prep M3 build configuration


Demo Demo
Data prep M3 test

M3 workshops M3 presentations
Beta Build

Business

feedback
& ERP functional discussions
Business
Review
M3 Optimise

M3 ERP gaps identify & document

*Project ERP configuration design


STEEL
Finalise ERP future phases Statement of Work
Planning –
future phases Benefits analysis
Benefit workshops; data collection Board
Submission
* ERP – Enterprise Resource Management Identify opportunities Identify benefits
** PLM - Product Lifecycle Management Update Business Case

*ERP /
PLM/ERP interface demo & data prep Workshops & design
**PLM
& Nesting
Demo Nesting interface design
Interface

Business Process Leads and Experts Rick Reynolds | Johnny Greer; Deon Wessels | Chris Double

10 one austin | one vision | one team | one system


Meetings with selected key users will be schedule to workshop any
configuration requirements Who is involved and
We will try to program within 2-hour windows
Functional experts from our ComActivity implementation partners will when
call/email when they need more information or clarification
• The final version demo will be available to everyone via a video link –
(approach it weeks 9 - 11) We also want to spend time
on benefit opportunities:
Example of programming:
We know we'll save time by
not duplicating processes,
but what does that actually
mean?

We will work with the


business to break this down
even further, so we can
quantify the actual profit and
work through how to collect
data to create a baseline
and then accurately
measure what's achieved.
11 one austin | one vision | one team | one system
Next steps… Questions…

• Work through the Proof of Concept build with


both the functional experts from our implementation
partner ComActivity and our key resources
• Define/quantify business benefit opportunities
• Determine gaps and mitigations

BUILD, TEST, REVIEW, DEMONSTRATE


12 one austin | one vision | one team | one system
The following
slides are for
your
information
Q&A
Here are some frequently asked questions/answers:
Why do we need a Beta Model?
• The engineering and manufacturing areas are key. We will work through our processes to determine how to get this information transitioned
across to the ERP.
We will then ensure that any manufacturing orders, inventory, purchase orders, labour and other costs are attributed to the Customer Order.
• This gives us increased visibility across our product from quote to shipping. The Proof of Concept will validate how it will work and what else
we need to do to close any gaps.
What will the BETA Model look like?
• The system is Infor M3 ERP functionality and will be configured (not customised) based on process information gathered from business
units over the last 2 years.
• Configured: out of the box system functionality using system features and based on Austin’s business processes.
• Customised: modifications to the system functionality that doesn’t currently exist anywhere in the software, such as a new feature.
• ComActivity is the implementation partner – the functional experts that will work with Austin to configure the proof of concept environment.
How long will BETA Phase take?
• Approximately 6 months, which will go quickly! It will require prompt input from key users to answer any questions ComActivity functional
experts may have during the build.
When will we get to see it
• Throughout the build, key users across USA and Australian business units will be involved in some of the activities like provision of
templates/data/ etc.
• We will regularly show the results and will provide updates, with the final model to be shared to all via video link.

one austin | one vision | one team | one system


Additional
information

Email us at

Project Steel SharePoint Site


• Please let us know if you can't access

projectsteel@austineng.com.au

one austin | one vision | one team | one system

You might also like