The following are the demands that are worked during the period 16 th March 2015 DEC 2015.

Example:
1. DM - DM9828 last 90 days Non_Usage _Prepaid data for subscriber
Role: datastage developer
Duration: Jun 2015 - Oct 2015
Requirement Description
The requirement is for providing a 90 days non usage cube for prepaid customer
base to Vodafone group
Scope
The Scope of this document is to meet the following requirements:
90 days prepaid non-usage cases to be tracked with no balance left for deduction.
Summary of this report to be published to Group

This is for PAN India Implementation for prepaid subscribers.

A new cube that provides the details of 90 days non-usage prepaid

customers

Various Activities performed:

1. Requirement Gathering:
Coordinated with Business Architect, business IT and business users to understand
the requirement. Also integrated with internal teams to understand the requirement
and impact. Being involved in all the team meeting till date to understand the
requirement in a better way.
2. Design:
Technical design document is completed.
Also technical design is completed. The batch is successfully running. All the data is
loaded in cube form as per requirement it was a daily cube for Pan India.
3. Coding:
The report is generated for all circles as well
developed for fetching data from source .As
does not use any of the data services from
etc,have been identified and are reflected
cognos.

as PAN India. Such a logic have been

per requirement the subscriber who
last 90 days such as call,SMS,GPRS
in daily cube ,which is produced by

4. Testing :
Unit testing was done during development and sample test cases were performed
on the data that were gathered by reporting. SIT was also performed on the data, I

was fully responsible

for
delivering the requirement throughout the various
phases of SDLC and necessary changes were implemented before delivery. SIT
signoff along with QA signoff was received and data was successfully loaded.
5 UAT:
The requirement was as per business need and therefore UAT signoff was received
to implement the necessary requirement in production which is in progress.
6. Implementation and Support:
Coordinated with TBO team and the cube was deployed in the production server and
implemented the requirement successfully.

The following are the demands that are worked during the period 16 th March 2015 DEC 2015.
Example:
2. DM DM10499 MNP PHASE 2
Role: datastage developer
Duration: Jun 2015 - DEC 2015
Requirement Description
DM10449 will allow mobile subscriber to retain the existing mobile number while
moving from one Service provider to another Service provider across PAN India This
demand will provide smooth transfer of customer porting from Vodafone to
Vodafone.

Scope
The Scope of this document is to meet the following requirements:

Vodafone to Vodafone inter circle porting

Other to Vodafone inter circle porting
Vodafone to other inter circle porting
Enterprise as well as retail customers using GSM based services
PAN India

Various Activities performed:

1. Requirement Gathering:
Coordinated with Business Architect, business IT and business users to understand
the requirement. Also integrated with internal teams to understand the requirement
and impact. Being involved in all the team meeting till date to understand the
requirement in a better way.

2. Design:
Technical design document is completed.
Also technical design is completed. The batch is successfully running. All the data is
loaded in cube form as per requirement it was a daily cube for Pan India.
1. New ETL process will be developed which will run daily at late night. The
time will be decided during design time. The process will connect to NPG
ODS and will extract all prepaid numbers which are activated in recipient
circle and the donor service provider is Vodafone.
2. The ETL process will push the feed to Fly Text server.
3. New ETL process will be developed which will run daily at late night.

The time will be decided during design time. The process will
connect to NPG ODS and will extract all prepaid numbers which are
ported out and recipient service provider is Vodafone.
4. The ETL process will push the feed to Fly Text server
5. Both feeds will be PAN India and will have MSISDN, Circle ID, activation /
deactivation timestamp. Other attributes will be decided during design
time.
6. Naming convention of the feed will be decided at design time .

3. Coding:
The report is generated for all circles as well as PAN India. Such a logic have been
developed for fetching data from source .As per requirement the subscriber who
does mobile number portability inter circle or intra-circle basis and tagging to as
NMNP-VF,NMNP-OTHERS,LOCAL-MNP,OTVF-MNP.
4. Testing :
Unit testing was done during development and sample test cases were performed
on the data that were gathered by reporting. SIT was also performed on the data, I
was fully responsible
for
delivering the requirement throughout the various
phases of SDLC and necessary changes were implemented before delivery. SIT
signoff along with QA signoff was received and data was successfully loaded.
5 UAT:
It is in the UAT phase, as the major requirement comes under mnp,some more
information wants to get by user ,so that I am working on the customer satisfaction

fact as it is major part of business and IBM.some more columns I need to add and
some transformation needs to done in the generated cube.
6. Implementation and Support:
Coordinated with TBO team and the cube is aligned to deploy in 20 h release of
December.

3. DM DM10334 8TH AMENDMENT FOR DATA USERS CONSENT

Role: datastage developer
Duration: Jun 2015 - DEC 2015
Requirement Description

Requirement is to provides Design specification for TRAI DM for 8th Amendment of Data
Services.
Scope
The Scope of this document is to meet the following requirements:

Below functionalities to be developed as clause of 10B Activation or De activation of Data

Services as part of TRAI amendment of TCPR released on 7th August 2015.

For all new customers, data service should be disabled. To activate it, explicit START
consent should be sent to toll free short code @1925 through IVR, SMS.No service provider
shall activate or deactivate data service of consumer without explicit consent.

Request for Data Pack activation during new acquisition, Add on packs, Booster packs,
Implicit Data Benefits in Tariff Plan will not be considered as consent and additional explicit
consent will be needed.

For existing customers no change is expected and implicit START consent should be
considered until explicit STOP request is received.

For activation of data services for consumers with data only connection (Dongle
subscribers), the existing prescribed procedure for CAF verification to be followed, with
explicit consent through 1925.

Changes on IVR to support TRAI recommendation for Start/Stop

On sending Stop on 1925 existing process would be followed

Various Activities performed:

1. Requirement Gathering:
Coordinated with Business Architect, business IT and business users to understand
the requirement. Also integrated with internal teams to understand the requirement

and impact. Being involved in all the team meeting till date to understand the
requirement in a better way.

2. Design:
Technical design document is completed.
Also technical design is completed. The batch is successfully running. All the data is
loaded in cube form as per requirement it was a daily cube for Pan India.

New ETL job which will extract data from UPSS

CM_SUBS_SERVICES_#cir# for STOPDATA service on D-3 basis.

New ETL job which will extract data from DOX ODS service agreement
table for barring service soc code on D-3 basis.

Based on above input, data will be loaded in target staging table.

For device type, data will be extracted from TD handset model subs
history table to identify device type.

ARPU will be derived from TD DIM_SUBS_USAGE_REV_HISTORY.

SPINE table will be used to derive customer type (COCP / IOIP).

If data is not available in lookup tables, then it will be considered as

Unknown.

Based on data from staging table and lookup tables, new job will
perform transformation and load final data in new Netezza table.

Based on above target table new report will be provided on COGNOS as

per format given in FRS.

The report will be provided on daily basis with D-4 latency.

3. Coding:
The report is generated for all circles as well as PAN India. Such a logic have been
developed for fetching data from source .As per requirement the subscriber who
have been activated or deactivated their data services tagging start/stop services
identified and going to give in report form.
4. Testing :

Unit testing was done during development and sample test cases were performed
on the data that were gathered by reporting. SIT was also performed on the data, I
was fully responsible
for
delivering the requirement throughout the various
phases of SDLC and necessary changes were implemented before delivery. SIT
signoff along with QA signoff was received and data was successfully loaded.
5 UAT:
The requirement was as per business need and therefore UAT signoff was received
to implement the necessary requirement in production which is in progress.

6. Implementation and Support:

Coordinated with TBO team and the cube is aligned to deploy in 10th release of
December.