Difference between revisions of "ANLY482 AY2017-18 T1 Group1: Project Overview"

From Analytics Practicum
Jump to navigation Jump to search
(Created page with "<!-- Start Main Navigation Bar --> {|style="background-color:#AE0000; font-family:montserrat; font-size:140%; text-align:center;" width="100%" cellspacing="0" | | style="borde...")
 
 
(10 intermediate revisions by 2 users not shown)
Line 2: Line 2:
 
{|style="background-color:#AE0000; font-family:montserrat; font-size:140%; text-align:center;" width="100%" cellspacing="0" |
 
{|style="background-color:#AE0000; font-family:montserrat; font-size:140%; text-align:center;" width="100%" cellspacing="0" |
 
| style="border-bottom:7px solid #830909;" width="10%" |
 
| style="border-bottom:7px solid #830909;" width="10%" |
[[ANLY482_AY2017-18_T1_Group1: Home | <font color="#ffffff">Home</font>]]
+
[[ANLY482_AY2017-18_T2_Group1: Home | <font color="#ffffff">Home</font>]]
  
 
| style="border-bottom:7px solid #830909;" width="10%" |
 
| style="border-bottom:7px solid #830909;" width="10%" |
[[ANLY482_AY2017-18_T1_Group1: Team | <font color="#ffffff">Team</font>]]
+
[[ANLY482_AY2017-18_T2_Group1: Team | <font color="#ffffff">Team</font>]]
  
 
| style="border-bottom:7px solid #FF9E0A;" width="7%" |
 
| style="border-bottom:7px solid #FF9E0A;" width="7%" |
Line 20: Line 20:
  
 
| style="border-bottom:7px solid #830909;" width="10%" |
 
| style="border-bottom:7px solid #830909;" width="10%" |
[[ANLY482_AY2017-18_T1_Group1: Main Page| <font color="#ffffff">Main Page</font>]]
+
[[ANLY482_AY2017-18_Term_2: Main Page| <font color="#ffffff">Main Page</font>]]
 
|}
 
|}
 
<!-- End Main Navigation Bar -->
 
<!-- End Main Navigation Bar -->
Line 27: Line 27:
  
 
<!-- Start Information -->
 
<!-- Start Information -->
<div style="background:#AE0000; line-height:0.3em; font-family:montserrat; font-size:120%; border-left:#FFE2C0 solid 15px;"><div style="border-left:#fff solid 5px; padding:15px;"><font color="#fff"><strong>'''Introduction'''
 
<font color="#fff"></font> </strong></font></div></div>
 
 
<div style="color:#212121;">
 
 
Our project sponsor, eatigo, currently has 2 million registered users. Out of this, only 30% have ever made a reservation through Eatigo. Even amongst this 30%, reservation and reactivation rates remain low as each customer makes only 1.6 bookings on average per month. Our sponsor believes that there is higher potential, given their presence in markets such as Singapore and Thailand, both of which  are amongst the top 3 spenders in South-East Asia when it comes to dining out.
 
</div>
 
 
 
<div style="background:#AE0000; line-height:0.3em; font-family:montserrat; font-size:120%; border-left:#FFE2C0 solid 15px;"><div style="border-left:#fff solid 5px; padding:15px;"><font color="#fff"><strong>'''Motivation'''
 
<div style="background:#AE0000; line-height:0.3em; font-family:montserrat; font-size:120%; border-left:#FFE2C0 solid 15px;"><div style="border-left:#fff solid 5px; padding:15px;"><font color="#fff"><strong>'''Motivation'''
 
<font color="#fff"></font> </strong></font></div></div>
 
<font color="#fff"></font> </strong></font></div></div>
  
 
<div style="color:#212121;">
 
<div style="color:#212121;">
 
+
Our project sponsor, eatigo, currently has 2 million registered users. However, reservation and reactivation rates remain low as only 30% of eatigo's subscribers have ever made a reservation. Further, even amongst this 30%, each customer makes only 1.6 bookings on average per month. Our sponsor believes that there is higher potential, given their presence in markets such as Singapore and Thailand, both of which  are amongst the top 3 spenders in South-East Asia when it comes to dining out.
Eatigo’s business model is such that it earns revenue when customers show up for their booking. For every customer that does show up, Eatigo receives a certain fee from the vendors. Therefore, it is crucial for eatigo to have a good vendor listing (so customers are interested in making their booking through eatigo) and ensure that customers are aware of these vendor listings and discounts available (so customers are incentivized to make their booking through eatigo). To do this, our sponsor would like us to  develop intelligence about customer dining patterns by utilizing Eatigo’s transaction, redemption and vendor data. Eatigo can leverage on this intelligence to not only optimize yield management but also attract new vendors.  
+
<br />
 +
Eatigo’s business model is such that it earns revenue when customers show up for their booking. For every customer that does show up, Eatigo receives a certain fee from the vendors. Therefore, it is crucial for eatigo to have a good vendor listing (so customers are interested in making their booking through eatigo) and ensure that customers are aware of these vendor listings and discounts available (so customers are incentivized to make their booking through eatigo).  
 +
<br />
 +
Through our project, aim to improve reservation rates amongst subscribers who have never made a booking and reactivation rates amongst subscribers who have made a fewer number of bookings per month. We plan to do this by analysing transaction, redemption and vendor data to reveal booking patterns across customer & vendor types.
  
 
<div style="background:#AE0000; line-height:0.3em; font-family:montserrat; font-size:120%; border-left:#FFE2C0 solid 15px;"><div style="border-left:#fff solid 5px; padding:15px;"><font color="#fff"><strong>'''Objectives'''
 
<div style="background:#AE0000; line-height:0.3em; font-family:montserrat; font-size:120%; border-left:#FFE2C0 solid 15px;"><div style="border-left:#fff solid 5px; padding:15px;"><font color="#fff"><strong>'''Objectives'''
 
<font color="#fff"></font> </strong></font></div></div>
 
<font color="#fff"></font> </strong></font></div></div>
  
As described, the overall objective of our project is to help eatigo increase number of bookings per customer and potentially attract more vendors.
+
As described, the overall objective of our project is to help eatigo increase number of bookings per customer. With this in mind, at this stage, our aim is to conduct an Exploratory Data Analysis (EDA) to understand the vendor choice, booking and redemption patterns of eatigo customers across its 8 regions, and 700 restaurants.
With this in mind, at this stage, our aim is to conduct an Exploratory Data Analysis (EDA) to understand the vendor choice, booking and redemption patterns of eatigo customers across its 6 regions, and 700 restaurants.
 
  
 
From our EDA, we would like to answer the following questions from our datasets :<br />
 
From our EDA, we would like to answer the following questions from our datasets :<br />
Line 59: Line 53:
 
* The customer clusters by restaurant type, location, timing and discount preferences
 
* The customer clusters by restaurant type, location, timing and discount preferences
  
The current objectives may be subjected to further changes after we have obtained and look at the actual data.
+
The current objectives may be subject to further changes after we have obtained the actual data.
 +
 
 +
<div style="background:#AE0000; line-height:0.3em; font-family:montserrat; font-size:120%; border-left:#FFE2C0 solid 15px;"><div style="border-left:#fff solid 5px; padding:15px;"><font color="#fff"><strong>'''Data Sources'''
 +
<font color="#fff"></font> </strong></font></div></div>
 +
 
 +
<div style="color:#212121;">
 +
 
 +
We are waiting on the data from the sponsor, which we will be receiving once the Non-Disclosure Agreement is signed.
 +
 
 +
We have currently requested for the following categories of data:
 +
# Vendor Data
 +
# Transaction Data
 +
# Redemption Data
 +
Some of the variables that we expect to receive in these datasets include the following:
 +
 
 +
{| class="wikitable"
 +
|-
 +
! Vendor Data !! Transaction Data !! Redemption Data
 +
|-
 +
| Restaurant ID || User ID || User ID
 +
|-
 +
| Country || Restaurant Booked ID || Restaurant Booking ID
 +
|-
 +
| Restaurant Name || Country || Country
 +
|-
 +
| Cuisine|| Number of Diners || Number of Diners
 +
|-
 +
| Location (Neighbourhood) || Date & Time of Present Booking || Date & Time of Present Booking
 +
|-
 +
| Opening Hours|| Date & Time of First Booking || Discount Received
 +
|-
 +
| Peak Hour Time|| Booking Type|| Promotion Code
 +
|-
 +
| Planned Discounts || Booking Status || Booking Status
 +
|-
 +
| Maximum Capacity || Booking History || Showing up History
 +
|-
 +
| || Cuisine Preferences|| Cuisine Preferences
 +
|}
 +
 
  
[[https://wiki.smu.edu.sg/ANLY482/index.php?title=ANLY482_AY2017-18_T1_Group1%3A_Team&action=edit&redlink=1 <font color="Blue">Meet the Team</font>]]
+
References:
 +
  “Singapore Among Top Spenders, Asia Pacific Survey” (http://www.todayonline.com/singapore/singapore-among-top-spenders-asia-pacific-dining-survey)
 +
  “How Eatigo has Disrupted the Food Space.” (https://ecommerceiq.asia/eatigo-food-commerce/)
 +
[[https://wiki.smu.edu.sg/ANLY482/ANLY482_AY2017-18_T1_Group1%3A_Project_Findings<font color="Blue">Read about our Methodology and Findings! </font>]]
 
<!-- End Information -->
 
<!-- End Information -->

Latest revision as of 22:54, 14 January 2018

Home

Team

Project Overview

Project Findings

Project Management

Documentation

Main Page


Motivation

Our project sponsor, eatigo, currently has 2 million registered users. However, reservation and reactivation rates remain low as only 30% of eatigo's subscribers have ever made a reservation. Further, even amongst this 30%, each customer makes only 1.6 bookings on average per month. Our sponsor believes that there is higher potential, given their presence in markets such as Singapore and Thailand, both of which are amongst the top 3 spenders in South-East Asia when it comes to dining out.
Eatigo’s business model is such that it earns revenue when customers show up for their booking. For every customer that does show up, Eatigo receives a certain fee from the vendors. Therefore, it is crucial for eatigo to have a good vendor listing (so customers are interested in making their booking through eatigo) and ensure that customers are aware of these vendor listings and discounts available (so customers are incentivized to make their booking through eatigo).
Through our project, aim to improve reservation rates amongst subscribers who have never made a booking and reactivation rates amongst subscribers who have made a fewer number of bookings per month. We plan to do this by analysing transaction, redemption and vendor data to reveal booking patterns across customer & vendor types.

Objectives

As described, the overall objective of our project is to help eatigo increase number of bookings per customer. With this in mind, at this stage, our aim is to conduct an Exploratory Data Analysis (EDA) to understand the vendor choice, booking and redemption patterns of eatigo customers across its 8 regions, and 700 restaurants.

From our EDA, we would like to answer the following questions from our datasets :
1. Analysis of Vendor Data

  • Variation of booking patterns across cuisines
  • Variation of booking patterns across neighbourhoods
  • Variation of peak and downtime across restaurants
  • Understanding the potential of optimizing discounts provided by restaurants within the same neighbourhood

2. Analysis of Customer (Transaction & Redemption) Data:

  • Variations of booking patterns across customers that have made bookings previously
  • The average gap between the time booking is made and the time customers have to show up at the restaurant
  • The customer clusters by restaurant type, location, timing and discount preferences

The current objectives may be subject to further changes after we have obtained the actual data.

Data Sources

We are waiting on the data from the sponsor, which we will be receiving once the Non-Disclosure Agreement is signed.

We have currently requested for the following categories of data:

  1. Vendor Data
  2. Transaction Data
  3. Redemption Data

Some of the variables that we expect to receive in these datasets include the following:

Vendor Data Transaction Data Redemption Data
Restaurant ID User ID User ID
Country Restaurant Booked ID Restaurant Booking ID
Restaurant Name Country Country
Cuisine Number of Diners Number of Diners
Location (Neighbourhood) Date & Time of Present Booking Date & Time of Present Booking
Opening Hours Date & Time of First Booking Discount Received
Peak Hour Time Booking Type Promotion Code
Planned Discounts Booking Status Booking Status
Maximum Capacity Booking History Showing up History
Cuisine Preferences Cuisine Preferences


References:

 “Singapore Among Top Spenders, Asia Pacific Survey” (http://www.todayonline.com/singapore/singapore-among-top-spenders-asia-pacific-dining-survey)
 “How Eatigo has Disrupted the Food Space.” (https://ecommerceiq.asia/eatigo-food-commerce/) 

[Read about our Methodology and Findings! ]