Reference no: EM132370728
Assignment
1 Objectives
• This case study is designed to give you an opportunity to showcase your:
• Ability to understand and articulate business problems
• Structured problem solving
• Commercial acumen
• Business-orientated creativity and insight
• Communication and presentation style
2 Instructions You have been asked by a large Telco provider to help build an Analytics Strategy for their Digital Finance Function.
As part of this the client asked for a hands on proof of concept (PoC) to analytic that demonstrates the power and practical applicability of analytics, risk and outlier detection.
Your task is to develop materials and:
Talk the client through your findings (keep your presentation to a max of 15 minutes)
Demonstrate your thinking & broader strategy for increasing the adoption of analytics in their finance function
Covering Strategy, People, Process, Data and Technology and where possible demonstrate this through the findings from the PoC analytic
Outline how you can increase the maturity of the client's analytics capabilities over time
Be as creative as possible and feel free to bring any other datasets, reference materials or thought leadership you think this client will find useful Feel free to make any assumptions on client's current state capabilities and desire for analytics insights in the future.
3 Data The data used in this case study is from their finance function (journal entries - financial postings to a company's general ledger). It has been anonymised by masking the true value of several descriptive fields, removing some identifying columns and randomising the journal amounts by some factor.
Data dictionary of important fields:
• GL account - the account the journal is posted to (i.e. revenue or debtors)
• Journal - whether the journal was posted automatically for routine transactions (‘Journal 1', ~9.1m lines) or manually for non-routine transactions (‘Journal 2', ~1.6m lines)
• Account No - a lower level account code under GL account (i.e. interest revenue or sales revenue)
• BAT_NAME - the ID for a single journal posting. All lines for a single journal should net out to zero (for example when a ‘customer' pays a bill, the amount on that bill will be debited from debtors and credited to revenue and there will be two separate lines in the data under the one journal ID)
• JNL_LNE - the line ID for each journal posting
• Period - the month in which the journal was posted (month 1 to 12 of the previous financial year, plus month 13 being month 1 of the current financial year)
• SOURCE_USER - user who entered the journal
• POST_USER - user who posted the journal
• Amount - the dollar amount of the journal Most importantly - remember to have fun in building our your presentation!