The figure above, which depicts an excerpt of the TAM, shows how the GISDATA supplied Telcordia products support the TAM suggested applications relevant to COMPASS.Between Expediter, DCAT, Granite, and Activator all functions suggested by the document “GB929 TM Forum Applications Framework (TAM), Rel.3-2” will be covered. Specifically, Expediter and the DCAT Engine will address all of the functions suggested by chapters “5.03 Customer Order Management“ and “06.03 Service Order Management“ of said document, while the Resource Component Interface will be responsible for supporting the functions stated in chapter “07.04 Resource Order Management”.
Telcordia Dynamic Service Catalog (DCAT) is system focusing on product lifecycle and customer fulfillment management. Using graphical interface it is possible to make models to standardize how products, services, resources, and business interactions are defined and managed across BSS/OSS. DCAT is used for order (product) decomposition purposes through its exposed engine.In the context of the OSS solution it is used as a repository for storing product and service model information (model for short) to be used for commercial order decomposition in the Expediter supported order management process.The DCAT functionality is extended further by way of the DCAT Engine module which runs the recommendation engine and creates input to Expediter for control of the fulfillment part of the order management process.Telcordia Expediter is an order management and automation platform providing a graphical design tool supporting BPML standards help end user define and develop customized business flows and GUIs. Through its APIs it supports connection to number of standardized protocols to other systems. In the solution Expediter has orchestration role towards all OSS systems included in provisioning process.In the context of the OSS solution, Expediter is used to manage the interfaces to various systems needed for service activation (e.g., WWMS and TOPS). Moreover its work-flow execution capabilities will be used to implement those parts of the provisioning and activation processes whose complexity will benefit from visually rendering the control flow.Resource components represent a set of SOA components which can be consumed by any system via standardized interface. Resource components internally communicate with Granite Inventory, CNUM, GIS, and other systems. The key features of those components are to provide the functionality of a provisioning engine.The order management process consists of several phases, the main ones of which are order orchestration, service provisioning, and service activation.
The picture above shows an example of a product model, where one of the resource facing services is thought to refer to an Expediter process. This then makes the entire product model one that requires a complex process-flow for its implementation. This is to say, each of the resource facing services shown in the diagram need to point to an Expediter process. And each of their descendant components are translated into data which are transmitted as part of the technical order sent back to Expediter.While the components in the green triangle exhibit a level of complexity which requires the Expediter process to be designed prior to completing the DCAT modeling, the other resource facing services can potentially be supported by Expediter process metadata which never changes at runtime. Or, said differently, the characteristic values associated with the two resource facing services to the far right of the green triangle are fully specified at design-time already and, hence, could be hardwired into the Expediter process.
The picture above adds the correlations which exist between the resources of the MaxADSL product. When the underlying network resources are to be provisioned and activated, it will be necessary to use business rules in order to determine the exact sequence in which each of the components need to be evaluated. Given the relatively simple product and the relatively small number of references, one can imagine that the processing of such a much can quickly become quite complex. Add on top of this the fact that all of the references need to be described using characteristics, the resulting model will undoubtedly be hard to understand.The above picture shows four resource facing resources. The Physical Access Service can be thought of as data container. It does not require a process because the SWInventoryRServices, which requires an Expediter process-flow to be designed, will use all of its data (as indicated by the reference, for instance). Moreover, the seven resource components, which make up this resource facing service, too are linked by references. This then provides yet another indication to have a process candidate that will benefit from being designed using the graphical tool process design tool provided with the Expediter Service Designer.
The picture above describes the physical layer and the BB portion of the HT ADSL service in terms of a DCAT product model. The physical access components are referenced by resource components which are able to trigger specific resource components. The PSTN part is handled by the existing interface, aka the DIS Interface Manager resource component.
Croatian Telekom NGOSS projects – Shape of things to came …
1<br />Croatian Telekom NGOSS projects – Shape of things to came …<br />Dominik Periškić T- Hrvatski Telekom d.d.<br />Damir Medved<br />GISDATA d.o.o.<br />
Hrvatski Telekom d.d. T-HT<br /><ul><li>Croatia
300.000 IPTV subscribers (including HDTV from 2008)
Massive Fiber rollout ongoing (PON) – 50.000 connections by the end of the year</li></ul>2<br />57% of Croatian households connected via broadband compared to an average of 55% in Western Europe<br />
GDi SYSTEMS - GISDATA GROUP<br />3<br /><ul><li>GISDATA GROUP of companies in 2009 - the largest (revenues, resources) and leading (experience, references, growth) geoinformation systems application company in CEE