Search the site...

SASCRUNCH TRAINING
  • Home
  • Member's Area
  • How to Start
  • SAS Interface
  • Creating a Data Set
  • Practical SAS Training Course
  • SAS Certified Specialist Training Program
  • Proc SQL Course
  • Introduction to Time Series Analysis
  • SAS Project Training Course
  • Full Training / Membership
  • Sign up
  • About us
  • Contact us
  • Home
  • Member's Area
  • How to Start
  • SAS Interface
  • Creating a Data Set
  • Practical SAS Training Course
  • SAS Certified Specialist Training Program
  • Proc SQL Course
  • Introduction to Time Series Analysis
  • SAS Project Training Course
  • Full Training / Membership
  • Sign up
  • About us
  • Contact us
Churn Modeling [1-10]


Let's first take a look at the data we have.
proc contents data=import varnum;
run;

The CONTENTS procedure prints the descriptor portion of the data set.

As mentioned, we have 78 columns with 71,047 rows of data in the data set:
Picture

The 78 columns are listed at the bottom:
Picture

​The majority of the columns are numeric except for CSA and CHURNDEP.
Picture
Picture


Let's look at the data dictionary to learn more about each column.
Picture

The data dictionary has a brief description for each column.

Let's look at some examples:
  • REVENUE: The average monthly revenue from the customer
  • MOU: The average minutes used in a month
  • RECCHRGE: The average recurring charge (not excluding additional charges from going over the minutes limit)
  • DIRECTAS: The average number of director assisted calls. 
  • OVERAGE: The average minutes used over the limits.

You can read more on the data dictionary for the rest of the columns.

When you go through the list of columns, you will see the CUSTOMER columns in column 30 in the data dictionary:
Picture

The data is captured on the customers level with each record representing the details of the usage and charges for each customer.
Picture

Programming Tips

In a telecom database, the data is usually captured on many different levels.

Some data sets capture data on the transaction level where each record represents a single transaction at a given time point.

Other data sets capture data on the customer level where each row represents a unique customer profile.

There are also tables containing the daily snapshot of the customers usage information.

It is important to understand the data table structure before performing any manipulation and statistical analysis.
Next

Already a member? Go to member's area.