Service acquisition, Billing &

Mediation has to be handled

in CDR. DSPT service acqui-
sition, technical order man-
agement and billing will be
done in CDR CRM, Clarity
and Billing respectively.
Following scenarios have to
be modelled as a part of cap-
turing DSPT service:
New Provision
Change in facility
Plan change
Disconnect
Offline order entry
Dunning (No automatic
integration with switch
involved)
Technical and Billing com-
plaints
PT and VPT services over
DSPT should not be
charged for shift.
New Provision Order
Once the customer places a
request for a new DSPT ser-
vice, CSR takes the necessary
details and creates a sales or-
der in CRM.
The following details will be
populated on the order on new
DSPT order
Order Type: New
Order Sub Type: Provision
Connection Type: Perma-
nent
Installation Exchange Type
= Rural
CRM system shall give provi-
sion to accept indoor comple-
tion date on the order and this
date should be equal or great-
er than billing account crea-
tion date. This will be used for
offline order entry.
Once the payment is collected
from PMS, the order is sub-
mitted to Clarity.
Clarity will have a manual
task at SSA level for provi-
sioning. Once the necessary
details are entered and DSPT
is activated, the same is up-
dated to Billing.
After getting the success mes-
sage from billing, CRM will
convert the order to asset for
new order.
PCO and VPT services over
DSPT will be handled in CDR.
Billing
Billing system will accept
DSPT as a new service type
and account type.
No DSPT specific accesor-
ries are to be configured.
Local, STD, ISD, OG Bar
and IC Bar facilities are
configured for DSPT.
Billing will configure the
rentals and usage plans as
per the requirement for the
DSPT customers.
The bills will be generated
for the DSPT customers as
done for other customers.
Billing has to accept the
payments posted in PMS
for DSPT invoices.
Billing has to include DSPT
services in regular dunning
process.
Billing system should ac-
cept adjustments, refunds,
refinance and all other bill-
ing related requests.
CLM to be configured.
Loyalty to be exempted
CRM
Separate billing account
shall be created with Ac-
count Type and Sub Type
with DSPT
Allow to populate the bill-
Digital Satellite Phone Terminal (DSPT Billing through CDR system)
B
S
N
L

MA R C H 2 0 1 4
V O L U ME V , I S S U E 2
I T P R O J E C T C I R C L E
N E W S

I T R E S O U R C E S :
R E Q U E S T T O
A L L C I R C L E S F R O M
CDR Project Portal
BSNL Intranet> CDR Project

CDR DashBoard

CDR FAQs
BSNL Intranet>CDR Dash-

IT Circle Project Tracker (ITP)

SSAwise Online Billpay data
BSNL Intranet>IT Circle Project

CDR Project Presentations
BSNL Intranet>IT Circle Project

South Zone Report Server
East Zone Report server
itpc.edc.bsnl.co.in
MP Billing
Mpbs.bsnl.co.in
Facebook
Www.facebook.com/
bsnl.connect
Land & Building Assets
civilmis.bsnl.co.in

Page 2 I T P R O J E C T C I R C L E N E WS
ing account created date as
similar like offline order.
The following details
should be created on the
new order
Service Line: Basic
Phone Service.
Service: Wireless
Service Type: DSPT
Service Sub Type: DSPT
No accessories will be pre-
sent for DSPT service.
Facilities same as Billing
needs to be configured in
CRM.
Allow only new, facility
change, plan change and
disconnect orders on DSPT
service.
CRM system should be
allowed to accept the bill-
ing complaints and will be
assigned to the SSA AOTR.
CRM system should allow
to raise the adjustments,
refunds and refinance re-
quest.
CRM system should not
allow to create account
hierarchy for DSPT cus-
tomers.
Committed period will be 2
years for DSPT and the
penalty charges as Rs.10000
will be configured in case
of pre-closure.
Offline order processes to
be desinged.
Technical complaints will
be accepted through all
available channels which
are currently valid for LL
service.
PMS
PMS will allow to accept
payments for DSPT cus-
tomers.
Restoration of service will
be triggered post accepting
payment.
Clarity
Following configurations need
to be done at Clarity with
respect to DSPT implementa-
tion:
Separate service type will
be created with applicable
tasks, accessories and facili-
ties.
No network inventory will
be required to be captured.
Number inventory will be
captured and will be mod-
elled at a circle level with
circle specific codes.
The following details will be
created for a new order
DSPT ACTIVATION
(Manual task at SSA Level)
Allows only new, change
in facility, plan change and
disconnect orders on DSPT
service.
DSPT Activation will be
manual task and will be
assigned to the appropriate
workforce at SSA level.
In Dunning, suspension
and restoration orders
would be created in Clarity
but will be handled manu-
ally
Clarity system should ac-
cept technical faults for
DSPT from CRM. It would
be tracked to closure manu-
ally.
Mediation
Transit calls are of two
types:
A) From 899 to landline
and mobile i.e O/G calls
from DSPT.
B) From Landline/mobile
to 899 series (DSPT). i.e
I/C calls to DSPT.
Charge bands will not be
available in raw CDRs.
Changes to be made in the
business logic to handle
raw CDRs for EWSD
switch are:
Case A will be treated as
the Billable Calls and all
the other calls from Case
B will be filtered out as
Non-Billables.
Appending of actual Cir-
cle Code (As per the
DSPT Circle wise level list
given by rating) in the
processed CDR's instead
of default circle code
which is taken corre-
sponding to the system
portal from which the
raw file is passed.
In case of Intra Circle
Mobile Calls (based on
the calling DSPT circle
code and Called no Mo-
bile Circle Code)
NW- '0' from called
mobile No is being re-
moved as is done pres-
ently in case of Intra
Circle Mobile Calls.
SE - '0' will not be
trimmed. Called num-
ber to be shared as is to
billing.
North DC will pull the raw
CDR file from EWSD switch
and push it to south media-
tion as well. It will further
process the CDRs and dif-
ferentiate between north
and west based on the circle
codes. It will further push
the processed CDRs to West
zone.
Once the file is received at
South Medation, it will start
processing the CDRs based
on circle codes and once
done, processed file will
push the same to East medi-
ation.
Calls will be segregated as
local, intra, inter so that
separate usage type IDs/
Event type IDs are config-
ured. This is done to accom-
modate traffic identification
in future (if necessary).