Croatian Telekom NGOSS projects – Shape of things to came …
•Télécharger en tant que PPTX, PDF•
2 j'aime•1,114 vues
Croatian Telekom NGOSS Projects
![Hrvatski Telekom d.d. T-HT ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à Croatian Telekom NGOSS projects – Shape of things to came …
Similaire à Croatian Telekom NGOSS projects – Shape of things to came … (20)
Plus de Damir Medved
Plus de Damir Medved (13)
Croatian Telekom NGOSS projects – Shape of things to came …
- 1. 1 Croatian Telekom NGOSS projects – Shape of things to came … Dominik Periškić T- Hrvatski Telekom d.d. Damir Medved GISDATA d.o.o.
- 3. Population : 4,5 M
- 4. GDP Total 82 BN US$
- 5. GDP per capita 18.500 US$
- 6. HT - Part of DT group (51%)
- 8. 2.680.000 mobile customers (UMTS/HDSPA)
- 9. 700.000 broadband customers ( 4 – 20 mbps)
- 10. 300.000 IPTV subscribers (including HDTV from 2008)
- 11. Massive Fiber rollout ongoing (PON) – 50.000 connections by the end of the year2 57% of Croatian households connected via broadband compared to an average of 55% in Western Europe
- 13. Leaders in SEE in telecom NGOSS and VAS apps
- 14. Amongst largest in its class in EMEA region
- 15. Educating, leading the way
- 17. updates to multiple systems
- 18. multiple skill sets required for each application
- 19. ‘Re-Inventing the Wheel’ each time
- 20. Extended time for E2E testing
- 22. cost of new product business cases can’t be justified
- 24. Voice and data orders separated
- 25. Fixed portfolio difficult to change
- 26. reliance on manual processes and handovers
- 27. result: order experience can be unsatisfactory
- 28. high incidence of errors, missing orders and partial orders
- 29. reliance on availability of sales personnel to take orders
- 30. reduced ability to track and manage orders online Time to Market Time to Deliver
- 31. T-HT: OSS PAST 5
- 32. T-HT Landscape 1998 – 2003 (voice) 6
- 33. ConsolidatedT-HT Landscape– endof2004 (voice) 7
- 34. T-HT Landscape – endof2008 (voice) 8
- 36. TMF Recommendations thatInfluenced COMPASS 10
- 37. TELCORDIA SOLUTIONS Dynamic Service Catalogue, Expediter 11
- 38. Genericinteraction CRM – OM – DCAT - GI 12
- 39. COMPASS Alignment with TMF TAM Visualized 13
- 40. COMPASS Complete Architectural Solution And Support 14
- 42. Foster reusability of resource components(optimize resource consumption with help of catalog)
- 43. Create order management and fulfillment processes entirely driven by catalogue data
- 44. Under business rule control select from several feasible alternatives the solution which make the most sense from a network and/or operations perspective
- 45. Make workflow control catalogue data driven
- 46. Employ standardized (Move / Add / Change / Delete) operations for interworking with non-COMPASS system
- 48. Flow-through Order Management Order Entry/Service Selection Account Data Request Options Search Options (including 3rd Parties) Quote Preparation Obtain numbers Valid Commercial Order Order Control and Decomposition Billing Activities Number status update SLA Create/Updates Dispatch Requests Provisioning Work Order Activation Work Order Provision Valid Order Design and Assign Select Resources Activate Component Create Service Instance Provide Status Manage Exceptions 3rd Parties CRM Rating/Billing Dynamic Service Catalog 2 3 1 4 5 7 6 9 7 20 CNUM Expediter Service/ Device Director 11 10 8 21 12 20 13 19 Network Engineer Granite 16 17 15 20 14 Discovery Performance & Fault Management Activator Planning and Forecasting 18 18 Networks 17
- 49. Defining process in models 18
- 50. Sample MODEL Realitycheck 19
- 51. ADSL with POTS: Model Showing References Between Resources 20
- 52. DCAT product model 21
- 54. Future proof design achieved
- 55. By the end of 2010 fully operational COMPASS NGOSS landscape is expected to be in the production
- 56. END OF NGOSS EVOLUTION IN T-HT
- 57. Be aware: Transformation of the BSS/OSS systems is not revolution, but EVOLUTION, so you cannot rush it !
Notes de l'éditeur
- 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.