1. Roman Agaev, M.Sc, PMP
Owner, Supra Information Technology ltd.
Common MSISDN resource
Number Management
Author: Roman Agaev
Date: Tuesday, March 27, 2007
-1-

2. Roman Agaev, M.Sc, PMP
Owner, Supra Information Technology ltd.
Contents
1 Abstract.......................................................................................................................4
2 Analysis.......................................................................................................................4
2.1 First Option – New entities..............................................................................4
2.2 Second option – Siebel's native entities...........................................................5
2.3 Third Option – combination.............................................................................6
3 Design.........................................................................................................................7
4 Conclusion...................................................................................................................7
5 Appendixes..................................................................................................................8
-2-

3. Roman Agaev, M.Sc, PMP
Owner, Supra Information Technology ltd.
Figures
Figure 2-1: Number management - new entities............................................................5
Figure 2-2: Number management - native entities.........................................................5
Figure 2-3: Number Management - new entities combined with native entities...........6
-3-

4. Roman Agaev, M.Sc, PMP
Owner, Supra Information Technology ltd.
1Abstract
This essay takes as its purpose an analysis an prior design of stand alone module that
will deal with MSISDN resource.
The following are several significant emphasizes regarding the module:
Number Management is an integral part of the Line activation process.
The quantity of numbers aspires to a fix known amount.
Numbers can be divided into groups.
Numbers has many logic links with other entities (orders, quotes, assets).
Numbers can be associated to Customer account in a many to one relation
(few numbers to one customer account).
After an order completion the customer's asset needs to be link to a number
(as another asset or via intersection to number management)
A number is not an attribute of an asset.
A number is not a product
Several products will have a dedicated range of numbers (by default, a CSR
can choose to override)
2Analysis
As part of analysis stage several possibilities were consider. The following sections
views and describes the discovered options.
2.1First Option – New entities
This option fulfills the requirement without using Siebel's native entities
-4-

5. Roman Agaev, M.Sc, PMP
Owner, Supra Information Technology ltd.
Figure 2-1: Number management - new entities
The Numbers table aspires to a fix amount, therefore it is easier to perform a search
for assets in the number management. Relation between Numbers to asset will be
done using a new Intersection table (not part of Siebel Data Model). Through this
table we can start with a number and find an asset or start with an assetId and find the
number associated.
This solution allows for future scalability, however, has overhead of configuration
and adding tables to Siebel Data Model.
2.2Second option – Siebel's native entities
This option fulfills the requirement by only using Siebel's native entities
Figure 2-2: Number management - native entities
The Numbers table is actually a part of the asset table (S_ASSET). In this
implementation a search for MSISDN will be on the Intersection table between the
actual asset and the Number asset associated (S_ASSET_REL). It is important to
understand that the intersection table will be continuously increased with any changes
done between numbers and assets.
This solution doesn't require changes to Siebel Data Modes and has no overhead of
configuration. However using this solution can cause performance problem because
of large amount of records in the S_ASSET table and the continuously growth of the
S_ASSET_REL table.
In this solution the link between assets is both hierarchical and relational.
-5-

6. Roman Agaev, M.Sc, PMP
Owner, Supra Information Technology ltd.
2.3Third Option – combination
This option fulfills the requirements by using both Seibel entities with new entities.
Figure 2-3: Number Management - new entities combined with native entities
This approach combines the first and second options, the number management is done
outside of Siebel Data Model and the link to assets is done via assets that are created
in advance, the number of those assets is equal to the number of MSISDNs in the
number management. These assets will be linked to the customer's assets through a
one to one link using a pointer in the asset table (e.g. Service Point Id).
In this option a search for MSISDN will be done in the intersection table
(S_ASSET_REL). Here as well, a continuously growth of the S_ASSET_REL table is
expected. Implementing this option add new tables to Siebel Data Model (less than
the first option) and requires some configuration to be performed.
With this solution there is the possibility of performance problem caused by the
growth in S_ASSET_REL and the large amount of records in S_ASSET.
In this solution the link between assets is both hierarchical and relational.
The preferable solution is first one thanks to its quality in terms of database
performance and separate module approach. Although the lack of additional
-6-

7. Roman Agaev, M.Sc, PMP
Owner, Supra Information Technology ltd.
configuration the solution seems to be very powerful when provides strong
scalability, availability and reliability qualities.
3Design
The module described through the analysis within prior section underlied by the
following database1, business, and graphic user interface layers objects:
Main numbers table
Four intersection tables between order item, quote item, asset, product and main
numbers table
Number history table
Number portability table
Number portability contact table
Business component based on main numbers table
Business component based on extension tables presents number portability issue
Business component based on number history table
Business component based on number contact related to the number that has
been ported through the number portability process
Business object that consolidates all above
Applets, Views, Screen
The neediness for intersection tables requires clarification:
The reason for 1:M between number and item or asset is that number can
participate during its life in many different items/assets
The reason for 1:M between item or asset and number is divided on two cases:
Item case – neediness of multiple selection within order process
Asset case – history of number management
4Conclusion
This essay in a brief but concluded way describes the Number Management module.
The module is not presented as part of Siebel out of the box environment and need to
be developed as separate module.
Their flexibility and benefits vote for themselves, the module is needed in each Telco
application.
1
The appropriate designs may be found within Appendixes section of the document
-7-

8. Roman Agaev, M.Sc, PMP
Owner, Supra Information Technology ltd.
5Appendixes
"Workflow usage best practices" (Roman Agaev)
"Common VBC paradigm" (Roman Agaev)
"Common error handling mechanism" (Roman Agaev)
The following documents present design of needed database layer:
CX_NUMBER_MGMT ()
CX_NP_DATA_X ()
CX_NUMBER_MGMT_XM ()
CX_ORITM_NMGMT ()
CX_QUITM_NMGMT ()
CX_ASSET_NMGMT ()
-8-