SIEBEL RELEASE 30

Muhammad Awais Akhtar

Project Description
Siebel Release 30
Risks:
Regulatory requirements if any may affect this Release.
Negotiation on efforts for AD stream that is-in progress between TP and Accenture. This can impact the
schedule & Cost.
Siebel Release 30
(12 CRs)
S&D CRs
4
MKT & BS CRs
2
CVM&A
1
RA CRs
1
CCD/CDM CRs
4
Status:
UD-BSS & Stakeholder Scoping sessions
concluded.
BSS & Stakeholders to email queries regarding CRs
will be addressed this week.
Next Action Items:
WBS sharing by BSS Planning.
Siebel release prioritization session with
stakeholder, for Business Case & Rationale.
D-2 Approval
Release Process:
August April
May
Initiation
D1 Approval
Scoping (Analysis Phase ) Implementation Phase
Go Live
D2 Approval & Prioritization
Siebel Release 30
Category
Man Hour
(estimation)
High Business Value 4150
Low Business Value 5700
Project 5 1500
Total 11350
2 Requirements are Out of Scope
Siebel Release 30
Summary:
SR # CR Name
Requirement
No.
Requirement Description Comments
Effort
Estimation
1 Re-initiation Plan R1 Bulk functionality for Rejected Import NPRs Low Business Value 500
2
Reprocessing in
Bulk Wrong
Credentials
R1
While creating import NPR, new credentials should be accepted; currently
there's an expiry time of 20 days.
High Business
Value
200
3
Usability
Enhancement
R1
R1 Organization type field in Customer screen should either be read-only
once the value is set upon customer creation or in case it is editable, audit
trail should be maintained
Low Business Value 200
R2
R2 Designation field in the Contacts tab should allow space as special
character between words.
Low Business Value 150
R3
R3-New separated payment component for M2M SIMs to be developed in
CRM.
High Business
Value
300
R4
Edit option required for Invoice Address. activity need to be created as
well
Low Business Value 250
R5 Black List Option should available on Asset Tab. Visibility on Asset Tab Low Business Value 200
R6
The Customer Tag should be place in Asset Tab for quick notification
comments tag should be visible on asset tab
Low Business Value 200
R7
There should be single portal for all tasks Temp Waiver, Adjustments,
Waiver, Email Id update and Invoices. -
Low Business Value 300
R8
Customers suggestion is to add different Invoice email address for their
different numbers even if they are on same ownership.
Low Business Value 300
R9
All VAS & Components status must be colour code to identify the respective
status.
Low Business Value 250
R10 Change Records Options for Asset Status Change in bulk in Asset Tab Low Business Value 200
R11 Data export option from CRM in Postpaid Asset Tab Low Business Value 200
R12
Sim-Modification through simplification tab in state of
Active/Blocked/Suspended/Restricted state.
Low Business Value 200
R13
Change Records options for Credit Class Change-Admin in bulk in Billing
Account Tab. Required Columns: Credit Class, Change Type, Reason,
Duration (In Days), Remarks
Low Business Value 250
R14
Change Records Options for Asset Status Change in bulk in Asset Tab;
Required Columns: Action Type, New Originator, New Reason, Comments
Low Business Value 250
R15 New tab needs to be added in main Tabs with the name of Modifications. Low Business Value 300
Siebel Release 30
Siebel Release 30
SR # CR Name
Requirement
No.
Requirement Description Comments
Effort
Estimation
4 789 Blacklist sync
R1
All currently blacklisted CNIC on Siebel need to be copied to 789
Server
(sync Activity) ?
R2
789 Server should reject any subsequent requests for SIM
activation against blacklisted CNIC
High Business
Value
200
R3
Any future blacklisting of CNIC on Siebel should be
simultaneously updated on 789 Server to ensure both lists are in sync
High Business
Value
300
5
MNP Rejection on
Loan
R1
stop porting out of numbers who have taken balance from TP as form of
Loan (-ve balance) [Why?]
High Business
Value
500
R2
Daily Report of all NPRs rejected on this condition to be sent to certain
email (Default: MNP.Support@waridtel.com) [Why?]
6
Package Plan
Conversion Reattempt
R1 Automated Retry for PP Change on charge error
High Business
Value
500
7
Change od Ownership
SO
R1
In case of Change of Ownership NADRA verification functionality of
CNIC must be in place to reduce entry of fake CNIC in our CRM.
System should not allow document Type and document number
unaligned like if CRO select Passport as document type in CRM then
system should not allow him to enter CNIC in document number field
but alphanumeric passport only (format needs to ensure).
system should show the source like COO done through Siebel or via
668 authorization process.
Any SO pertaining to the BVS should show BVS flag e.g. either it pass
through BVS or not.
[Already]
[Password-Cnic
business
process]
[why source
want to bi-
furcated]
[Why required?]
500
R2 Root cause fixation of data posting issue (Error Console)
(CRM
Modernization
scope)
?
R3
Combo Box is required with list of values e.g. Defense Organization,
NGO etc. And this field should be mandatory. (Corporate Connections)
Designation field is required in contacts tab with other fields like First
Name, Last Name and Document Number. (Corporate Connections)
High Business
Value
250
R4 Respective Reports
High Business
Value
200
Siebel Release 30
SR # CR Name
Requirement
No.
Requirement Description Comments
Effort
Estimation
8
Project-5 Phase
3A
R1
existing MSISDN & CNIC should be removed from TP-PMD and
triggered -1 at local and if MSISDN reported to PMD than trigger -1
subjected to
response from
NADRA; if Project 5
is not needed after
BVS Go-Live then the
CR should be
rejected
1500
R2
Business can un-authorize MNP numbers as per PTA direction and
rights for MNP number un-authorization only be assigned to the
specific tracker 668 (S&SC) IDs
R3
P-5 phase II implementation on dummy to actual functionality.
(Prepaid tab)
R4 Project-5 phase I and II should implement on simplification Tab.
R5
P-5 phase II implementation on number authorization and/or un-
authorization.
R6
P-5 phase II implementation on individual to corporate and/or
corporate to individual.
R7
P-5 phase II implementation should be done at number termination
(GUI) and bulk (bulks that are used in write-off activity and/or bulk
number terminations like recycling etc.). Inc. consumer & business
segments
R8
P-5 phase II implementation on change of ownership. (Consumer &
business Segments)
R9
A Utility with the help of which CDM team can insert number in TP
PMD layer and utility can sync number on all relative nodes in
system.
9
Single Name
Acceptance
R1
NPR generation, incase 667 message does not include the
Subscribers Second (last) Name
High Business Value 200
Siebel Release 30
SR # CR Name
Requiremen
t No.
Requirement Description Comments
Effort
Estim
ation
10
Siebel SR
Deletion
(CCD)
R1 SR Deletion should be disabled or should have audit trail
High Business
Value
Okay 200
R2 SMS Functionality for Port in Numbers
Low Business
Value
We cannot updated
on each step
300
R3
Any MSISDN complaint for xyz reason will also display the count
of complaint related to the same work code against the same
MSISDN
Low Business
Value
SED checking? 200
R4
SR creation tab contains the fields to display package plan and
IMSI for the entered MSISDN. It should also be available when the
SR records extracted from the Siebel in available formats
Low Business
Value
Why? 100
R5
to segregate the re-escalated issues, no mechanism is currently
available
Low Business
Value
SED checking? 200
11
Receipt Re-
Name in
Siebel (CCD)
R1 To change all credit classes of same SME in bulk and in one go
Low Business
Value
Technical Limitation,
can be done via bulk
200
R2 To change asset status of same SME in Bulk in one go
Low Business
Value
Technical Limitation,
can be done via bulk
200
R3
To export MSISDNs and Puk & Pin Codes against ICC Codes
from Inventory Tab
Low Business
Value
Analysis 200
R4
Need to change the receipt name from Telenor Pakistan Official
payment Receipt to Telenor Customer Service Activation Form
Low Business
Value
Why? 200
R5
All the receipts of MNP activities need to align with the fields in
MNP receipts
Low Business
Value
??? 250
12 IR ME Check R1
Allowing multiple additions to the mutual exclusivity checklist
against IR
High Business
Value
300
13
Magic Screen
CR For Siebel
R1
The functionality requires that the Current balance parameter and
Balance validity parameter should be exposed to Magic Screen by
TIBCO against any MSISDN in real time.
High Business
Value
500