Most businesses nowadays have set out on their journey of digital transformation. Unfortunately most businesses have not really understood what digital transformation is. Most think, there is an end to the journey and it could be approached just like any other project. This presentation debunks the most common misconceptions on digital transformation and introduce a lean, pragmatic approach to it. It all starts by being “API Aware”. The presentation includes what the WSO2 platform brings to the table in order to make every stakeholder API aware in a digital transformation journey in a lean manner with predictable results.

1. Chief Technology Officer – Mitra Innovation
Simplifying Digital Transformation with
an “API Aware” Mind-Set
Sudaraka Jayashanka
Enterprise Integration Architect – Travis Perkins Plc
Mark Cater

2. The Era of Digital
Transformation
World is Looking for Digital Transformation

3. Digital Transformation, Is it understood well?

4. Digital Transformation, Is it understood well?

5. The End Goal
PROCESS
TECHNOLOGY
PEOPLE
Transformed
values
enhanced data
privacy and
client data
protection
tech re-skilled
workforce
competitive
enhanced
services
agility with new
products
enhanced sales
enhanced marketing
strategies
Insights on
customers,
products,
services and
employees
predictability
Customer and
employee
engagement
TRANSFORMED
VALUES

6. Simplification =
Decomposition

7. Digital Transformation
Canvas

8. KEY RESULT DECOMPOSER MODEL
CAPABILITY MAP BRIDGE
EMPLOYEES LEGACY ASSETS
EXTERNAL FACTORS EXPERINCE/INSIGHTS
TCO AGILITY INNOVATION
REFERENCE ARCH/ CATALYSTSDELIVERY PLAN
Identified key results
from the objectives for
Digital Transformation
The key results are decomposed into more manageable set of solutions
The solutions derived
and broken into
capabilities which can be
individually identifiable
map
Reference architectures and solutions catalysts to
seamlessly deliver the capabilities in an agile manner
Agile based delivery plan
that constantly aligns
with the key results

9. THANK YOU
wso2.com

10. Travis Perkins Group Overview
(Mark Carter)

11. ● Travis Perkins PLC formed in 1988
● UK’s largest distributor of building materials
● Supplied building materials to the trade for over 200
years
● 20+ brands in the Group
T
R
A
V
I
S
P
E
R
K
I
N
S

12. The largest supplier of buildings materials
General Merchanting ~ 810 branches
#2 kitchen distributor to tradeMarket leading general
merchant to trade customers
Consumer ~560 stores
Fastest growing
national DIY retailer
#2 tile
retailer
Integrated multi-channel
trade counter
Plumbing & Heating
Leading distributor to Domestic Installers
Leading distributor to Contract installers
Leading wholesaler to trade distributors
Fast growing renewable heating distributor
~475 branches Contracts ~175 branches
Fastest growing
specialist distributor
of ceilings, insulation
and drywall
Leading specialist
distributor of
pipeline and heating
solutions
Leading specialist
distributor of civils,
heavy building
materials & drainage

13. Transforming Travis Perkins
with an API Mindset

14. T
H
E
C
H
A
L
L
E
N
G
E

15. O
U
R
A
P
P
R
O
A
C
H
● Use Integration as an enabler
● Provide a layer of abstraction
● Meet the need of our integration styles
● Start our journey with private APIs
● Scalable for future growth and transformation

16. B
L
U
E
P
R
I
N
T
Building Blocks
Cementing Foundations
Defining Patterns
Established Structure
Still building...

17. Building Blocks
Creating reusable building blocks
that can be plugged in and
configured for each integration
promotes consistency,
standardisation and more
importantly saves time.
The crucial link to building integrations fast
Making Lego requires a lot of work… Using Lego is child’s-play

18. Building Blocks
Example: Logger
Standard, Reusable, Assemble instead of Build
{
"timestamp": "2017-10-30T16:43:06.654+0000",
"level": "INFO",
"thread": "SynapseWorker-5",
"logData": {
"loggerVersion": "3.0",
"correlationId": "48675a95-924a-420f-b8a8-aae93ff12f90",
"capability": "Accounts Payable",
"integrationReference": "SED8",
"integrationVersion": "1.0.0",
"messageType": "CUSTOMER_INVOICE",
"clientMessageId": "11111111-2222-3333-4444-555555555555",
"businessId": "123456",
"sequenceName": "receive-customer-invoice-v1-main-sequence",
"contentType": "application/xml",
"message": "Message received"
}
}
Logger
<call-template description="Call: logger-v3-template" target="logger-v3-template">
<with-param name="integrationReference" value="SED8"/>
<with-param name="integrationVersion" value="1.0.0"/>
<with-param name="sequenceName" value="receive-customer-invoice-v1-main-sequence"/>
<with-param name="logMessage" value="Info or error message"/>
<with-param name="errorReason" value="Failed to complete something"/>
<with-param name="logLevel" value="INFO"/>
<with-param name="includeMessageBody" value="true"/>
<with-param name="unhandledError" value="true"/>
</call-template>
Input Output

19. The Cement (Glue)
ESB
Client Client Client
Adapter Adapter
Routing and Mediation
Adapter Adapter Adapter
Destination Destination Destination
Standard Message
Bespoke Messages
● Messages are passed between
systems
● Messages are structured
according to a Canonical Data
Model
● If they are constructed in a
standard way they are easier to
manage
● If their payloads are
standardised, integrations are
simpler
● Routes become reusable
Logging &
Monitoring
Validation
Web API Message API

20. E
S
T
.
S
T
R
U
C
T
U
R
E

21. ● Partner APIs
● Find the low hanging fruit
● API Analytics
● Reusable APIs
● Security
Re-using and maximising our internal APIs for
consumption from valued partners
A
D
D
I
N
G
V
A
L
U
E

22. O
U
R
L
E
A
R
N
I
N
G
S
● Capacity Management
● Logging and Monitoring
● Be Agile in your approach (fail fast)
● Consider support from the outset
● Design with scalability in mind
● Understand the tools and use the best tool for the job
● Think about re-usability - avoid duplication
● Governance

23. THANK YOU
wso2.com