This post builds on Enrico Ronco from Telecom Italia summaries on the Messages from the Panel on "Embedding Communications into IT Applications: A Vendor Perspective". Participating companies are: Accenture, Avaya, Oracle.
Avaya
- Need for an agile communication creation environment
- Deliver different level of granularity for different customers
- OASIS can help in filling some gaps (i.e. security, manageability, serviceability of “communication platforms”)
- Occasion for a full automation of business processes (incl. manual processes) – gave examples (sales force automation, extension of communication services with enterprise folders
Accenture
- How to implement SOA in a holistic view? (need for a proper governance capability)
- 4 different levels of maturity of SOA adoption in Telcos: (Plan & Organize, Deploy, Architected, Industrialized). Not necessary to run through them in sequence.
- Understand customer need, make a plan, iterate within phases (level 3 is the most difficult)
- The whole is difficult: services delivered by consultants, but failure in the achievement of the full business value. Difficult for a department to pay for others. Short term funding.
- Gives us a “recipe” for SOA adoption in Telcos: 1) Define governance framework and decide key roles (who should sit in this “board”); 2) define quick goals …
Oracle
- Bridging the “Web” world with the “Telco” world, and “Traditional Telcos” have goals which are different from the “Internet SP”
- Concept of “Standard-Based Service Delivery Platform”: --> look at the OMA OSE
- Then a “process” is suggested for successful deployment of the “Standard SDP”
- Mention of TM Forum Service Delivery Framework (SDF)
- Mention of Oracle’s Application Integration Architecture
- No particular challenge in making things happen, but SOA is not yet "Carrier Grade"
- High availability, predictable low latencies, efficient, scalable …
- Difficult to guarantee throughput, SLA, QoS, lifecycle management of mash ups
Avaya
- Need for an agile communication creation environment
- Deliver different level of granularity for different customers
- OASIS can help in filling some gaps (i.e. security, manageability, serviceability of “communication platforms”)
- Occasion for a full automation of business processes (incl. manual processes) – gave examples (sales force automation, extension of communication services with enterprise folders
Accenture
- How to implement SOA in a holistic view? (need for a proper governance capability)
- 4 different levels of maturity of SOA adoption in Telcos: (Plan & Organize, Deploy, Architected, Industrialized). Not necessary to run through them in sequence.
- Understand customer need, make a plan, iterate within phases (level 3 is the most difficult)
- The whole is difficult: services delivered by consultants, but failure in the achievement of the full business value. Difficult for a department to pay for others. Short term funding.
- Gives us a “recipe” for SOA adoption in Telcos: 1) Define governance framework and decide key roles (who should sit in this “board”); 2) define quick goals …
Oracle
- Bridging the “Web” world with the “Telco” world, and “Traditional Telcos” have goals which are different from the “Internet SP”
- Concept of “Standard-Based Service Delivery Platform”: --> look at the OMA OSE
- Then a “process” is suggested for successful deployment of the “Standard SDP”
- Mention of TM Forum Service Delivery Framework (SDF)
- Mention of Oracle’s Application Integration Architecture
- No particular challenge in making things happen, but SOA is not yet "Carrier Grade"
- High availability, predictable low latencies, efficient, scalable …
- Difficult to guarantee throughput, SLA, QoS, lifecycle management of mash ups
No comments:
Post a Comment