Built by

A NEW DIGITAL ECOSYSTEMOVER THE TOP OF THE NBN

DOUG NIXON - CEO

Key influences

1. The delivery of the nbn footprint.

2. Virtualisation of the network as well as servers – “cloud resources”.

3. Disruptive business models and players. Eg Amazon vs AT&T

Resultant Change

4. Service Providers need to see themselves as Digital Service Providers.

5. Services need to be delivered through an ecosystem of partners.

6. Product Engineering and Operations need to change to support these.

Service Provider End State – Over the Top of the nbn

In the Operations Centre of the future, OSS/BSS will not be systems, but a collection of functions similar to the trend towards network functions being componentised. Jenny Huang, Lead OSS/BSS Standards, AT&T

We’re seeing a standardisation of services and the emergence of commodity compute as something that is absolutely sufficient and capable of managing and running our business. Therefore the need for bespoke, engineered solutions becomes a thing of the past.George Glass, Chief Architect BT

Service Provider End State – Operations Centre

Source: tmforum, “Building the Operations Center of the Future”, October 2015

1. Open Dynamic APIs at all layers.

2. Closed loop control and automation, with real time, zero touch orchestration.

3. Real time data analytics.

4. Transparent end to end management across partners.

5. Security designed in from the beginning.

Operations Centre of the Future – Key Principles

Source: tmforum, “Building the Operations Center of the Future”, October 2015

Standard Building Blocks 1. Touchpoints and APIs

Retail ServiceProvider

nbnco

Qualify

Address

New

Order

Buyer Journey

Noti

ficati

ons

Supplier Journey

Common Information Model

Dynamic Data APIs

Independent processes

Processes joined by touchpoint/API

Standard Building Blocks 2. Layered Components

Retail ServiceProvider

Supplier Eg nbnco

RSP Product

Internal Resource External Resource

NxAS Product

Shared Specification Template

The RSP considers nbn access as a re-useable component.• API• Process• Specification

Discrete Supplier Processes

Standard Building Blocks 3. Specification & Dynamic API

Example Specification for Voice

Dynamic API Payload generated by specification

Product Specification in Designer UI

Standard Building Blocks 3. Specification aligned Process

Product Specification in Designer UI

Associated Process

Example Specification for NZ Broadband

API Improvement over time

Dynamic API Business Benefits• Rapid Change• Lifecycle Management• Multiple Concurrent Versions allows phasing of change per customer

Stage 1 Static, Hard Coded Expensive to Change Some lifecycle management

Stage 2 Name/Value Pairs Ok to change Poor lifecycle management

Stage 3 Dynamic Fast to change Good lifecycle management

nbn & tmforum APIs

VIRTUAL IT BUNDLE

VIRTUAL NETWORK

SASS + IAAS CLUSTER

FIBRE ACCESS(LAYER 2)

VIRTUAL FIREWALL

RUN TIME / ORCHESTRATION LAYER

DESIGN TIME / BUNDLING LAYER

1 2 3 4

SELF SERVICE PORTAL / B2B

TELFLOW SERVICE PROVIDER SELF SERVICE CUSTOMER

PRODUCT MANAGER

1 2

TMF Active Catalogue PSASOAP

TMF Open Digital APIREST

B2B2X Best PracticeebXML

Sample Bundling for a Service Provider

Dynamic Data APIs

IOT - An Amazon example

Dynamic REST API’s

Shadow could be driven by Specifications

New DSP Apps

Beta Announced October 2015

Priced at ~$8 per million messages

RUN TIME / ORCHESTRATION LAYER

DESIGN TIME / BUNDLING LAYER SELF SERVICE PORTAL / B2B

TELFLOW SERVICE PROVIDER SELF SERVICE CUSTOMER

PRODUCT MANAGER

1 2

Service Provider – IOT Manager

ACTI

VATI

ON

ALER

TS

STAT

E

IOTResourceManager

MEFResourceManager

VirtualResourceManager-IaaS-NFV

StandardAPIsSharedMetadata

• Take a single approach for Virtualised and Legacy bundling and orchestration.

• Use modern dynamic APIs.Which track are you on?• Digital Disruptor?• Legacy?• Comfortable and Relaxed?

Summary

Telflow Powered by

Questions and comments.THANK YOU