NZ Post – Our journey to becoming a Connected Enterprise

Michael Brosnahan

2

Mention "NZ Post" and you'll probably think of this...

3

Our mail network is a significant part of what we do...

4

But we do some other stuff as well...

5

But the pressures on our traditional business are well known

6

● with Merchants and Retailers● with Logistic Networks

○ Universal Postal Union○ Global Logistics Partners

● with Government Agencies○ Customs○ NZTA, NZQA, StudyLink

● for Customer Solutions● for Web and Mobile App development

What we increasingly do is...

Integration

7

• Microsoft BizTalk• IBM MQSeries• File Transfer System (FTS) • SFTP• Scripted File Transfer• Direct Database access• Email• JBOSS ESB• SOAP Web Services• bespoke REST/JSON APIs

Technology is a critical enabler in delivering our future

Integration - We have a lot of that!

8

Which is where Mulesoft comes in...

9

Vendor Landscape

Vendor A Vendor B Vendor C Vendor D Vendor E Vendor F

Deployment Model

Cloud Admin & Dev PortalLocal Hosted Proxy

Cloud - AWS HostedOn Premise

tbd Appliance - Physical or Virtual

Cloud Admin & Dev PortalLocal Hosted Proxy (Optional)

On Premise

Licence Model Annual subscription Licence- Event based- Enterprise

tbd Annual Subscription Annual Subscription FOSSComm Licence

Heritage API API XML Gateway XML Gateway SOA / ESB SOA / ESB

Forrester View Strong Performer Excluded Strong Performer Leader No Product (at time of research)

Leader

Local Presence None NZ (1 person)Syd, AUST (2)

Local Partner Auck, NZ

Syd, AUST. Recently purchased by CA

Syd, AUST. Local partners: TBD

None. Some Local Use of ESB and API Product Sets

Indicative Cost $XX K per annum Cloud $XXX K per annum

TBD Basic: $XXX K+ HA: $XXk + Dev Portal: $XXX K

$XX K per annum FOSSSupport (Optional) $ XXX K

10

• We knew we needed a partner

• A partner that was at the forefront of APIs & Integration

• We didn’t want to make a significant capital investment

• We did need to be able to test, learn and iterate quickly

• We wanted a Cloud platform with OnPrem as an option

• Mulesoft was the only provider we felt met those needs

Vendor Selection process

11

• Early Adopter Status- Mulesoft gives us the ability to influence their product

roadmap

• Design First Approach- Interface design first focus was a good fit with our

market lead strategy- Ability to mock an interface

• Local Support- We needed a vendor with a New Zealand, or at least

an Australian presence- Local partner network also important

Why we selected Mulesoft

12

The Anypoint platform is at the heart of our API Strategy

13

• Driving a singular focus across the Enterprise in relation to our APIs

• APIs now viewed as a strategic asset and key enabler in the execution of our strategy

• Helps to reduce the complexity of our legacy technology silos

• We have built cross functional teams to deliver API products to market

• We have designed, built and are soon to deploy 12 new API products

Results of our API Programme to date

Technology Characteristics

15

Phase 1 - API facade over disparate business units

API Project Overview

16

API Project Overview

17

Phase 2 - Reconfiguration behind the API facade

API Project Overview

Customer feedback

19

Use Cases - Addressing for BNZ Credit Card applications

'Using the NZ Post address autocomplete API ... was a no brainer for us.

Customers save time filling out the form, usually only needing to enter the first part of their street for the full address to pop up. 

For BNZ it was easy to integrate and ensures we have the most up-to-date address to send customers their new credit card.' 

Matt Davin, Agile Business Lead, BNZ Digital

20

"Looks pretty solid and clear to me ... it pretty much exactly meets my expectations of how such a resource should

function"

Developer Feedback – the good

"I built a prototype on a Saturday morning and it worked as advertised"

"It looks good. In fact it looks better than the provision by xxxxxx and that's their core business. If carriers had web

services of this clarity there would be no need for us to use a middle-man like ."

21

"Can you please clarify how I can begin the process of getting an authorisation token, including: what is grant type,

setting up an application, what are client ids and client secret, etc. So I can make some test calls to the API."

And the not so good……

"I couldn’t understand it so I stopped"

"I am a little lost about where I can begin. All I want is an authorisation code so I can test sending requests and

responses to the API. Why must I set up an application?"

22

Developer Resource Centre - Sample Design

23

How using MuleSoft has assisted our API Journey

● iPaaS - Easy to get started. No servers to provide. No software to install

● RAML - Mock interface. Design first approach. Define and release working interface to integration partners, then rapidly iterate. Central specification supports parallel development

● Open standards, such as OAuth, allow for rapid development and developer engagement

● Rapidly evolving platform● Deployment to CloudHub is easy● Run integrations locally. Speed up development cycles

24

What we plan to do next

25 l All contents Copyright © 2014, MuleSoft Inc.

Questions?

Thank You