Database Reference
In-Depth Information
Service Request is received as a delimited file, containing one or more ordered items ac-
cording to the advertised CTU products. The COM module verifies a client's profile and
the current products registered for this customer.
A further Service Request in the TOM module is converted into working order with lines
that are sorted according to business logic and enriched with the client's information. For
instance, if a client needs TV channels in higher quality over the Internet, the currently
provisioned Internet bandwidth must be adjusted to these requirements. Consequently,
copper or optic cables must be considered and verified; some newly advertised features
cannot be supported by older versions of the
Set Top Box
(
STB
).
There are certain interdependencies between core telecom products such as VOIP and In-
ternet, and Order provisioning must adhere to these rules of practical fulfillment. From the
field force management perspective, for instance, you cannot send a technician to install
the cable modem or STB if the cable requirements are not met. All of this must be care-
fully analyzed for converting the received commercial order into its technical implementa-
tion plan.
Therefore, Order lines are grouped for parallel or sequential processing and are passed to
the service provisioning module for actual processing. As you can understand, every
single line of commercial order could be potentially converted into multiple lines of tech-
nical tasks that are related to certain application endpoints or other compositions. Thus,
there are a lot of
IF-ELSE
controls included in the last module in an attempt to cover all
the possible business combinations.
This last module presents a lot of adapters and partner links to endpoint systems, acting as
service providers for IP Provisioning, DTV Provisioning, registration/alteration in CRM,
and so on. After completing the list of technical tasks that are related to a single Order
line, its status must be returned to the caller of the process. The last successfully executed
Order line will update the Order status if all the line invocations were successful. A failure
in the execution of the group of invocations (or single operation in the group) related to a
single Order line leads to complex compensation activities. The complexity could be very
high as the number of combinations of technical tasks related to one Order line is massive.
Thus, in most cases, developers just park the error order in the error queue for manual re-
covery. In an attempt to help operational personnel with order recovery, developers de-
cided to log error information with excessive details. Regretfully, due to the complexity of
the compositions and the number of telecom subsystems involved, there are also several
logs and information related to errors that are not centralized.
Search WWH ::
Custom Search