Shakeel Tariq
$5/hr
Electrical Engineer
- Reply rate:
- -
- Availability:
- Full-time (40 hrs/wk)
- Age:
- 34 years old
- Location:
- Rawalpindi, Punjab, Pakistan
- Experience:
- 2 years
A project report on FSP errors in Database
Project Report
FSP Errors and Techniques for Their
Removal for Smooth Order
Management in RTR
This Project is based on real time
solutions of FSP errors occurred
during CRM Rollout.
Muhammad Shakeel Tariq
Management Associate
Office Of
Baber Siddique
SM MM&BB
Business Operations
RTR
October 20, 2016
Contents
Introduction ...................................................................................................................................................... 3
Problem Statement ........................................................................................................................................... 3
Trainings ............................................................................................................................................................ 3
Educating other Regions ................................................................................................................................... 3
Solution ............................................................................................................................................................. 4
Data Collection from Region ............................................................................................................................. 4
FSP errors and their removal ............................................................................................................................. 4
FSP Error Code 4 ............................................................................................................................................ 5
Scenario 1 .................................................................................................................................................. 5
Solution of Scenario 1 ............................................................................................................................... 5
Scenario 2 .................................................................................................................................................. 6
Solution of Scenario 2 ............................................................................................................................... 6
Scenario 3 .................................................................................................................................................. 7
Solution of Scenario 3 ............................................................................................................................... 7
FSP Error Code 5 ............................................................................................................................................ 8
BB Integration ID ....................................................................................................................................... 8
Solution of FSP Error Code 5 ......................................................................................................................... 8
Identification of Error ................................................................................................................................ 9
Identification of wrong PSTN .................................................................................................................. 10
Removal of BB Integration ID of Wrong PSTN ........................................................................................ 13
Reassigning Origional BB Integration ID to Correct PSTN ....................................................................... 14
FSP Error Code -1 ........................................................................................................................................ 15
Solution ................................................................................................................................................... 15
Conclusion ....................................................................................................................................................... 16
Introduction
During the rollout of CRM OSS a new set of errors was introduced in the system called as “FSP Errors” in
“WFRC” step during order management. First of all let us understand “what is FSP”. FSP Stands for
“Frame”, “Slot”, and “Port”. In Hardware level all the DSLs and terminated on DSLAM/MSAG. A
DSLAM/MSAG has multiple Frames, each frame has multiple slots and in each slot there are 32/64 Ports
and on each port a DSL line is terminated. So a DSL user has a Specific FSP so he could connect to internet.
This is the hardware port inventory, similarly in MAXIMO database a Logical port inventory is present and
there are logical devices each has logical frames, slots and ports which can be observed under device data
tab in MAXIMO.
When a broadband order is in WFRA (Waiting for resource allocation) step, CRM user has to allot proper
FSP and then execute the order but in some cases he misses something and order goes on to next step
which is WFRC (Waiting for resource configuration). When we execute the order further in BPM, it fails and
goes to “Activation/Deactivation Failed Manual” while giving one of the FSP failure errors.
Now this error is to resolved by regional team, in RTR case it is me who has to resolve each case.
Problem Statement
1. Initially in whole RTR there were 896 working PSTN numbers whose FSP info was missing in
MAXIMO, which indicates the problem that if in future an order is going to be placed on any
number out of those 896 numbers it will definitely go to FSP failure.
2. Meanwhile new orders were going into FSP failure which was directly affecting the business.
Trainings
I had about 1.5 months of training under IBM and CRM teams in which I had proper workshops of account
management and order management in CRM and MAXIMO. Moreover a specific workshop of FSP errors
removal was given by IBM team.
Educating other Regions
I have given on phone trainings of FSP to other regions like LTR, HTR and MTR in the beginning when FSP
error got introduced in the system. I helped other regions to process these errors and smoothened their
order management.
Solution
The main solution was to address the first problem which was getting the 896 numbers data fixed in
MAXIMO and then daily FSP failure error had to be removed.
Data Collection from Region
First of all 896 numbers were divided division wise and then sent to BMs/ABMs of concerning divisions in
following format so that they could enter the device IP and Correct FSP on which given numbers were
working.
SERIAL_NUM
Division
REGION
Device IP
Frame
Slot
Port-
Attock
RTR-
Attock
RTR-
Attock
RTR-
Attock
RTR-
Attock
RTR-
Attock
RTR
This took a lot of time because indicating each port was not an easy task for regional team but after all the
data collected from region was compiled In the file as shown below and sent it to software development
team for being uploaded in MAXIMO data base to counter the FSP errors once and for all.
SERIAL_NUM
Division
REGION
Device IP
Frame
Slot
Port
-
Attock
RTR
-
0
8
29
-
Attock
RTR
-
0
13
12
-
Attock
RTR
-
0
11
21
-
Attock
RTR
-
0
9
10
-
Attock
RTR
-
0
10
19
-
Attock
RTR-
After uploading the data in database most of the FSP missing numbers were corrected so the ratio of FSP
failure cases were decreased quite a lot.
This smoothen the order management system which increased the business and also the revenue.
Moreover customer satisfaction increased due to urgent order completion.
FSP errors and their removal
New orders were going into FSP failure due to ignorance of regional team. Those errors were supposed to
be removed by me as a regional POC for CRM issues.
Now there are 3 types of FSP errors.
1. FSP Error Code 4
2. FSP Error Code 5
3. FSP Error Code -1
FSP Error Code 4
When FSP of specific number is not present in MAXIMO, then following error occurs in BPM order UI.
“Get FSP Data Service Call | Return Code: 4| Return Description: No Data found against this
asset Id| Asset ID:-| Product: Broadband”
Now there are three different scenarios for this error, I will discuss it one by one.
Scenario 1
“Multiple Ports in ISSUED state against same PSTN”
Go to Logical Inventory PSTN UI, and query the PSTN.
Solution of Scenario 1
If multiple rows appear in PORTS DATA section, identify the Port which needs to be reset and go to device
data.
1. Go Device Data Menu & Select PORT INVENTORY tab
2. Query the identified Port
3. Change the status of the port
Scenario 2
“Port Status is not ISSUED”
Solution of Scenario 2
1. Go to DEVICE DATA UI and search the PSTN in PORTS INVENTORY tab.
2. If the status of Port is BLOCKED / SPARE / PREOCCUPIED, It can be changed to ISSUED.
Scenario 3
“If PSTN is not tagged on a Port”
Solution of Scenario 3
1. Go to DEVICE DATA UI and Query Device
2. Search Port in PORT INVENTORY tab.
3. Enter Area Code, PSTN and BB Integration ID in Data Dialog box
4. Change Status of the Port to issued.
FSP Error Code 5
When there are 2 PSTNs tagged on same BB integration ID then on BPM UI this error arises.
“FSP Data Failure | Return Code: 5| Return Description: More than one rows found against the
Asset ID| Asset ID: | Product: ”
BB Integration ID
It is an 8-12 digit unique code for unique broadband. It basically integrates CRM UI and MAXIMO UI for
communication. In CRM you can see the BB integration ID through following steps.
1. Go to Siebel Order which is stuck due to incorrect / missing FSP data
2. In Line Items applet, go to CPE Return link
3. Pick Asset Integration ID for Broadband line item
Now for proper communication between CRM, MAXIMO and BPM this ID should be uniquely present in
each system. It means that, in “MAXIMO Logical PSTN Inventory” each PSTN must have its unique BB
Integration ID. If one ID is given to 2 PSTNs in MAXIMO then order on any of these 2 PSTNs will get stuck
while given FSP error code 5.
Solution of FSP Error Code 5
Solution of FSP error code 5 is bit lengthy, as it involves the identification of wrongly tagged PSTN and
there is no direct way in the system to identify that how many numbers are tagged with one BB integration
ID?. So when we get to identify the wrongly tagged PSTN we change the BB ID of other number and that’s
how this error is removed.
This is described step by step below.
Identification of Error
First of all query the order in CRM and drill it down
Under failure reason tab identify the FSP failure error
Identification of wrong PSTN
Wrong PSTN can be identified from MAXIMO. Steps are shown below.
We can see that FSP info is alright in MAXIMO so FSP should be shown in CRM.
But when we see the FSP info in CRM it shows nothing which is basically an identification that its is FSP 5
Issue.
Now we have to change the BB integration ID of correct PSTN to identify the wrong PSTN who has the
same BB ID. For this goto device data and then port inventory and change the BB ID of PSTN as shown in
steps below.
Now when we goto CRM and get the FSP button we can see the wrong data and we can identify the
incorrect PSTN who has the same BB integration ID.
Removal of BB Integration ID of Wrong PSTN
Now go to logical inventory PSTN in MAXIMO and going into device data and identifying the concerning FSP
we can remove the BB integration ID as shown below.
Reassigning Origional BB Integration ID to Correct PSTN
Now we have to reassign the correct BB integration ID to our original PSTN, so for this query the number in
logical inventory PSTN and go to device data and then port inventory and identify the FSP on which
number is issued. After this change the BB integration ID to its original value as shown in steps below.
Now we can see that in CRM the FSP is corrected.
After correction of this error we get the order retried from SDN and order gets processed successfully.
FSP Error Code -1
When Tag in and Tag out are missing in MAXIMO then on BPM UI this error arises.
“FSP Data Failure | Return Code: -1| Return Description: Tag In and Tag Out Missing| Asset ID:
| Product: ”
Solution
This type of cases is very seldom and we have to contact to NOC for its solution because region don’t have
rights to edit the TAG in/Out data in MAXIMO. NOC uploads the data and we send the order to SDN for
reprocessing. That’s how this error gets removed.
Conclusion
After successful uploading of regional FSP data the FSP failure cases got reduced which smoothed the
process of order management and because of this regional performance got improved and also customer
satisfaction increased.
------------------------------------------------------------
