A New Era of Thinking - IBM · 6 A new era of thinking Platform related services provided by Kesko...
Transcript of A New Era of Thinking - IBM · 6 A new era of thinking Platform related services provided by Kesko...
1
A new era of thinking
© 2016 IBM Corporation
Kesko APIt digikehityksen vauhdittajana - Kesko APIs enabling digital development Marjukka Niinioja, ICT Development Manager, API Development @mniinioja @Kesko_Oyj
IBM BusinessConnect A new era of thinking
2
A new era of thinking
3
DIGITAL SERVICES INCREASE LONG-TERM VALUE OF CUSTOMER
RELATIONSHIP
4
A new era of thinking
Customers and partners of Kesko Digital Services
Consumers (B2C)
Project customers
(B2P)
Organi-sations (B2B)
Students, Researchers, Startups
Suppliers Professional
Networks, VCs,
Retailers Tech
partners Everyone at Kesko
End users
Digital service development partners Kesko owned and 3rd party services
Innovation and transformative knowledge network
5
A new era of thinking
Cus
tom
er
Con
tact
s A
PI
Agr
eem
ent
AP
I
Loya
lty A
PI
Offe
r AP
I
Pro
duct
AP
I
Bas
ket A
PI
Ord
er A
PI
Rec
ipe
AP
I
Ava
ilabi
lity
AP
I
Pric
e A
PI
Imag
e A
PI
Stre
amin
g A
PI
Kes
ko D
evel
opm
ent E
nviro
nmen
t AW
S –
Man
agem
ent –
Sup
port
– D
ocum
enta
tion
D
igita
l Coo
k Bo
ok –
Tes
ting
- Dev
elop
men
t
API Management
Web Analytics
Order Mgmt
Campaign Mgmt
Customer Mgmt
Agreement Mgmt
Social Listening
Business Intelligence
Programmatic Media Buy
Authenti-cation
Store & Organisation Mgmt
Offer Mgmt
Price Mgmt
Ad Mgmt
Targeting
Omni-channel customer journeys via Kesko owned and 3rd party services
Kesko Digital Platform (shared services)
Enterprise applications and customized content management
6
A new era of thinking
Platform related services provided by Kesko IT Digital development to business units and partners
Value Proposition:
• Attractive and Functional Digital Services
• Co-creation with Partners and Business Units
• Reliable Data Security and Data Protection
• Integrations for Partner Network • Solid Process Interface • Speed of Delivery
New service built in to the Platform
3rd party API or Application usíng Platform APIs and
Kesko ID
New Platform Compatible Service
Rows of common code or amount of shared computing resources
Amount of consulting
One of Kesko’s digital goals: ”Create the
best application for grocery stores – Customer decides the channel, we provide
the best service experience”
8
A new era of thinking
Grocery store customer experience
8
”What should we eat today?”
Customer
•Recipes •Offers •Inspiration •Shopping list
Solution
• K-store • K-ruoka.fi • K-ruoka
mobile
Shopping
Unified omni-
channel feedback handling
Feed-back
CASE K-RUOKA.FI
Case K-ruoka mobiili
K-Ruoka mobile downloads
326 000
0
50 000
100 000
150 000
200 000
250 000
300 000
350 000
Jan Feb Mar Apr May Jun Jul Aug Sep
Lataukset kumulatiivisesti Source: Google Analytics
12
A new era of thinking
© 2016 IBM Corporation
© 2016 IBM Corporation
APIs powering the K-Ruoka app
Well designed Apis make different data compatible
13
Product API
Customer API
Recepies API
Availability API
Stores API Rating API
Satisfaction API
Order API
Price API
GET /products/6410405095893 { ”name”: ” Pirkka lactose free milk drink }
POST /orders { ”ean”: ” 6410405095893”, ”name”: ”Pirkka lactose free milk drink” }
GET /availability/ 6410405095893 { ”ean”: ” 6410405095893”, ”name”: ” Pirkka lactose free milk drink” }
14
{ "Id": "7228", "Name": ”Apple-Vanilla Naked Cake", "Ingredients": [ "Name": ”egg", "Amount": "3", "Name": “sugar", "Amount": "2 1/2", "Name": ”melted butter","Amount": "50", "Name": "Pirkka lactose free milk drink", "Ean": "6410405095893", "Amount": "1",
Recipes via API
15
A new era of thinking
Customer-related Product-related
Orders and order history Product related content
• Loyalty programmes
• Store –related
• Customer targeted -content
Kesko API - universe
Specific set of similar APIs for each area of business: - Hardware - Grocery - Car
dealership - Machines - Specialty
stores
Common APIs
16
A new era of thinking
Importance of Being Organized
16
Agile scrum & kanban teams
Policy making and
management
Agile development
support Architecture
Marketing communication
tools and guidelines
Cross-channel coordination
Service Designers
Digital platform product management
”Kesko Digi Cook Book”
Platform services
management
Guidelines - Feedback
Guidelines - Feedback
Education/MarCom Change management Vendor management
17
A new era of thinking
17
Developer expectation for API management
DevOps –mentality & Automation • Command-line publishing of API versions • Full access to configuration and deployment • Integration with open source libraries, Git version control, cloud infrastructure • Mocking through documentation (or is mocking a bad word already…) • Plug-and-play using API documentation standards OpenAPI (Swagger),
RAML Easy security • OpenID Connect /JWT validation • Easy concepts with integration to authentication providers
18
A new era of thinking
18
Why use any integration platform?
• Rate limits • Developer Expierience: Documentation, Feedback, Information channel • Client registrations (know who uses your APIs) • Defined workflow • Security and access management (even self-service) • Transformations
19
A new era of thinking
19
API portal for developers & partners: access, docs, support, visiblity
20
A new era of thinking
20
End-user and Developer worries
Response times • One API can go through 2-3 gateways and integration platforms and end up in a legacy
ERP etc. • If every layer adds 1000ms+ then you are in trouble • Is it a good or better choice for developers to use native technology for the integration
platform?
Are integration platforms ever great for all things? Isn’t integration platform a “single-point-of-failure”? Where is the fine line with SOAish and Microservice solutions, and should we build a “mega-api” across all business functions even if data is similar and comes from same backend system or should be break it up
21
A new era of thinking
21
Developing APIs is about developing your organization
• Who owns APIs - business or IT? What does ownership and API actually mean? Is owning API different than owning the data coming out of the API? Who pays, who creates roadmaps?
• What is our partner strategy? Who can use the APIs and who decides it?
• Whose responsibility is communicating the APIs to the partner network, customers with integration needs and developer and startup communities?
• Can we and should we develop APIs in big projects with defined schedule, scope and resource or do we need to treat them as continuous services and adopt more agile principles (maybe more Kanban than even Scrum…)
22
A new era of thinking
22 | A new era of thinking
Thank you! See you next in Junction 2016 Hackathon – https://hackjunction.com/tracks/ecommerce/ @Kesko_Oyj @mniinioja