Difference between revisions of "ANLY482 AY2017-18 T2 Group 05 Project Overview"

From Analytics Practicum
Jump to navigation Jump to search
Line 57: Line 57:
 
'''Visual Dashboard:''' The creation of a visual dashboard to showcase our data analysis will be well anticipated by RDP
 
'''Visual Dashboard:''' The creation of a visual dashboard to showcase our data analysis will be well anticipated by RDP
  
==<div style="background: #DD597D; line-height: 0.3em; font-family:calibri;  border-left: #CFCFCF solid 15px;"><div style="border-left: #FFFFFF solid 5px; padding:15px;font-size:15px;"><font color= "#F2F1EF"><strong>Project Meetings</strong></font></div></div>==
+
==<div style="background: #DD597D; line-height: 0.3em; font-family:calibri;  border-left: #CFCFCF solid 15px;"><div style="border-left: #FFFFFF solid 5px; padding:15px;font-size:15px;"><font color= "#F2F1EF"><strong>Meetings with Project Coordinator, Project Client and Team</strong></font></div></div>==
 
Our team aims to meet our Project Coordinator, Professor Kam Tin Seong on average of at least once every week in order to ensure that we are progressing on the right track. We also met our client/project sponsor once a month to update them on our progress and validate our analysis, while our internal team meetings are held at least twice a week. All minutes can be found under "Project Documentation".
 
Our team aims to meet our Project Coordinator, Professor Kam Tin Seong on average of at least once every week in order to ensure that we are progressing on the right track. We also met our client/project sponsor once a month to update them on our progress and validate our analysis, while our internal team meetings are held at least twice a week. All minutes can be found under "Project Documentation".
  
Line 78: Line 78:
 
5. Identify merchants who are underperforming in terms of number and value approved transactions, and merchants who contribute to the highest number of rejected transaction. Thereafter, we hope to set performance benchmark for these laggard merchants should RDP intend to retain them.
 
5. Identify merchants who are underperforming in terms of number and value approved transactions, and merchants who contribute to the highest number of rejected transaction. Thereafter, we hope to set performance benchmark for these laggard merchants should RDP intend to retain them.
 
<br><br>
 
<br><br>
<b>Sub-Objective:</b>
+
<b>Sub-Objectives:</b>
 
<br>
 
<br>
 
6. In order to visualise and compare the performance among merchants on a fairer ground, we seek to group merchants into bins based on the number of transactions per merchant.
 
6. In order to visualise and compare the performance among merchants on a fairer ground, we seek to group merchants into bins based on the number of transactions per merchant.
Line 87: Line 87:
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
! Task !! Description
+
! Task !! Description
 
|-
 
|-
 
| Gather Requirements || Confirm and gather sponsor requirements
 
| Gather Requirements || Confirm and gather sponsor requirements
Line 95: Line 95:
 
| Project Proposal || Prepare project proposal and Wikipage
 
| Project Proposal || Prepare project proposal and Wikipage
 
|-
 
|-
| Data Exploration and Preparation || Ensuring that data is clean and can be analysed using analytical software; If necessary, transform data (e.g. remove outliers / recode variables for software to read; Conduct exploratory data analysis)
+
| Data Exploration and Preparation || Ensuring that data is clean and can be analysed using analytical software; We also have to transform data (e.g. remove outliers and recode variables for analytical software to read); and conduct exploratory data analysis
 
|-
 
|-
| Model Building || Through research findings and experience, we will attach and test suitable models to our data
+
| Model Building || Through research findings and experience, we will attach and test suitable models to our data. We have used Interactive Binning and Time Series data analysis to generate insights
 
|-
 
|-
 
| Project Revision (Mid-Term) || Assisted by RDP through obtaining feedback during our sponsor meeting
 
| Project Revision (Mid-Term) || Assisted by RDP through obtaining feedback during our sponsor meeting
Line 103: Line 103:
 
| Mid-term Preparation || Prepare mid-term report, presentation and Wikipage
 
| Mid-term Preparation || Prepare mid-term report, presentation and Wikipage
 
|-
 
|-
| Model Validation and Refinement || Conduct hypothesis testing (e.g.  Ensure the results are similar when attached to a different year of study) and refine analysis of data
+
| Model Validation and Refinement || Perform Time Series Clustering; Conduct independent sample t-tests (e.g.  Ensure the results are similar when attached to different years of study) and refine analysis of data
 
|-
 
|-
| Insights and Recommendations || Create visualisation from analysis results and formulate recommendations for our sponsor
+
| Insights and Recommendations || Create visualisation from analysis results and formulate recommendations for our client
 
|-
 
|-
| Project Revision || Assisted by RDP through obtaining feedback during our sponsor meeting; Align our final deliverables with sponsor requirements
+
| Project Revision || Assisted by RDP through obtaining feedback during our client meeting; Align our final deliverables with client requirements
 
|-
 
|-
 
| Final Preparation || Prepare abstract and full paper, final Wikipage update and final presentation with necessary deliverables
 
| Final Preparation || Prepare abstract and full paper, final Wikipage update and final presentation with necessary deliverables
 
|}
 
|}

Revision as of 20:18, 25 February 2018

HOME

 

PROJECT OVERVIEW

 

PROJECT FINDINGS

 

PROJECT DOCUMENTATION

 

PROJECT MANAGEMENT

 

ANLY482 HOMEPAGE

Background Data Source Methodology

Project Introduction and Background

Founded by a group of visionary financial technology payment experts in 2011, Red Dot Payment (RDP) has grown into a trusted online payment company providing premium payment solutions and expertise to the brightest merchants across Asia Pacific. Bringing best-in-class practices, RDP is the trusted FinTech partner of banks, merchants, payment schemes, payment gateways, non-banking financial institutions, security and fraud management system providers.

In 2016, RDP grew to handle millions of transactions across the globe, managed by a dedicated 40-person strong operation - with headquarters in Singapore, and offices in Thailand and Indonesia. Its products and services include - RDP connect, InstanCollect, InstanPay, InstanPromo and InstanToken.

Business Problem and Motivation

While RDP handles millions of transactions across the globe, the company has not yet been able to derive any conclusive analysis from its transaction data. There is untapped potential that is unexplored here, as they operate online and thus have the advantage of easily collecting large amounts of valuable data about their merchants as well as their customers. In addition, there are many data points captured previously with little insights derived, resulting in business decisions being driven mainly by intuition. Thus, by providing our team with their existing data, RDP hopes to gather a deeper understanding of their data. Moving forward, RDP hopes to make more informed decisions utilising the patterns we identify from the data.

After meeting with our client to provide updates and generate insights for them, these are the following areas that our client is interested in:

Industry Strategy: RDP is interested to find if our data analysis can provide insights as to which markets or industries they should target in retaining or recruiting new merchants
Visual Dashboard: The creation of a visual dashboard to showcase our data analysis will be well anticipated by RDP

Meetings with Project Coordinator, Project Client and Team

Our team aims to meet our Project Coordinator, Professor Kam Tin Seong on average of at least once every week in order to ensure that we are progressing on the right track. We also met our client/project sponsor once a month to update them on our progress and validate our analysis, while our internal team meetings are held at least twice a week. All minutes can be found under "Project Documentation".

Project Objectives

RDP has collected large amounts of data on transactions with their merchants and respective customers, but they are unaware of how to utilise this data to supplement their business operations. Our project aims to help RDP make sense of their data, to make profound observations from the datasets and to develop recommendations that can help guide their future business decisions.

Previously, we have identified the following objectives in our proposal:

1. To observe and develop meaningful insights from RDP’s datasets by performing exploratory data analysis.
2. To develop a visual dashboard. This will aid RDP in understanding some of their current business issues, as well as benchmark metrics and attributes that the company may not be currently analysing.
3. To formulate recommendations to improve their future business activities based on our findings.

Moving forward, on top of the above project objectives, we have further added on new objectives we aim to achieve in our study in terms of exploratory data analysis:

Main Objective: Identification of Star and Laggard merchants -

4. Compare the performance of merchants in terms of approved transactions, and identify top merchants contributing to the highest number and value of approved transactions. These merchants are valuable to RDP, since it earns commission based on the monetary value of the approved transactions carried out by its merchants and its commission rate is determined by the volume of approved transactions. Thus, we hope that our analysis will allows RDP to better identify these star merchants and invest its efforts to retain and attract them.

5. Identify merchants who are underperforming in terms of number and value approved transactions, and merchants who contribute to the highest number of rejected transaction. Thereafter, we hope to set performance benchmark for these laggard merchants should RDP intend to retain them.

Sub-Objectives:
6. In order to visualise and compare the performance among merchants on a fairer ground, we seek to group merchants into bins based on the number of transactions per merchant.

7. Identify any relationship between the approved/rejected transactions, and (i) the month of the year, (ii) day of the week and (iii) time of the day.

Scope of Project

Task Description
Gather Requirements Confirm and gather sponsor requirements
Initial Research and Preparation Conduct preliminary data exploration and define project objectives and scope
Project Proposal Prepare project proposal and Wikipage
Data Exploration and Preparation Ensuring that data is clean and can be analysed using analytical software; We also have to transform data (e.g. remove outliers and recode variables for analytical software to read); and conduct exploratory data analysis
Model Building Through research findings and experience, we will attach and test suitable models to our data. We have used Interactive Binning and Time Series data analysis to generate insights
Project Revision (Mid-Term) Assisted by RDP through obtaining feedback during our sponsor meeting
Mid-term Preparation Prepare mid-term report, presentation and Wikipage
Model Validation and Refinement Perform Time Series Clustering; Conduct independent sample t-tests (e.g. Ensure the results are similar when attached to different years of study) and refine analysis of data
Insights and Recommendations Create visualisation from analysis results and formulate recommendations for our client
Project Revision Assisted by RDP through obtaining feedback during our client meeting; Align our final deliverables with client requirements
Final Preparation Prepare abstract and full paper, final Wikipage update and final presentation with necessary deliverables