3. Andreas gave a great presentation on ‘product representations’ to allow fast service
innovation on top of existing telco services / assets / platforms
4. The ‘product representations’ deals with the challenge of where to manage the user
data for a service – in the service or in the network.
Andreas proposes a balance between the two (reuse and flexibility).
5. The last point is the key, the role of architects in the API-defined telco is becoming critical to
finding the balance between re-use and agility. The answers are not obvious, hence the need
for a unit like Telecom Italia’s ‘NetAPI’ group to get right balance of reuse and agility without
creating a complex mess – as we’ll see later in the Thomson Reuters case study.
6. Telecom Italia is one of the leading API deployments (Telefonica being another) they
have focused on using APIs internally and with existing partners.
7. The big news was their API traffic has grown from 1B transactions per month to 1.5B.
14. More Telcos need to see how financial services view latency and reliability!
15.
16. They over their platform costs with a membership fee (liimited competition so can get
away with that while difficult for telcos to do) and the platform is used to drive sales
17. Solid advice on managing the complexity we see in Telefonica and Telecom Italia as
their API programs grow. Bottom line – ‘eat your own dog food FIRST’
18.
19. Many operators are finding exposing APIs from their BSS help their partners sell
more of their services.
21. Focus on being a payment service provider NOT the long-tail
22. Focus on being a payment service provider across a range of media and access. BUT
to be competitive in the long term they will need to become a true payment service
provider across physical good and services, else they will be squeezed out of their
digital niche by existing payment networks.