Services & composition patters Resource abstraction & optimization Marketplace Solutions External Ecosystem An open cloud architecture is emerging, a must to ensure portability while preventing vendor lock-in Data store Mobile Middle- ware Services Security Opera- tions Develop ment Traditional workloads Analytics Com- merce Collabo- ration Location Data Services API API API API API API App API API Software defined compute Software defined storage Software defined network Workload definition, optimization & orchestration API & orchestration services Hardware Software defined environments IaaS Cloud operating environment PaaS API economy SaaS
9
Embed
Cloud computing: onderbouwde keuzes voor IT en business - Edwin Schouten (IBM) CIO SUMMIT 2014
Cloud, in al zijn verschijningsvormen, verandert ons dagelijks leven; zowel van consumenten als van bedrijven en publieke organisaties. Veel cloud-gesprekken gaan over technologische (on)mogelijkheden. Logisch, want IT innovatie bepaalt vandaag de dag 99% van de business innovatie. Maar hoe vat je als CIO die koe bij de horens? Hoe ga je, liefst samen met de business, die innovatie handen en voeten geven? IBM heeft haar kennis en ervaring vervat in een aanpak om principiële én praktische keuzes te maken. Samen met de business, of alleen, dat is aan u. In deze workshop delen wij graag onze ervaringen met die aanpak op basis van concrete klantcases. It's time to make choices, and deliver!
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Services & composition patters
Resource abstraction & optimization
Marketplace
Solutions
External
Ecosystem
An open cloud architecture is emerging, a must to ensure portability
while preventing vendor lock-in
Data
store Mobile
Middle-
ware Services Security
Opera-
tions Develop
ment
Traditional
workloads
Analytics Com-
merce Collabo-
ration Location Data Services
API API API API API
API
App
API API
Software defined
compute
Software defined
storage Software defined
network
Workload definition, optimization & orchestration
API & orchestration
services
Hardware
Software defined environments
IaaS
Cloud operating environment
PaaS
API economy
SaaS
• Legacy applications based on traditional middleware stacks
• Cloud delivery enabled by:
o Standardization
o Automation
o Portal-enabled access
• Requires migration of large volumes of applications
• Resilience assumed at the infrastructure layer
Cloud enabled Cloud native
+ Competitive displacement
opportunity New market growth
opportunity
• Emerging / new applications written to exploit the new cloud platform
• Cloud delivery enabled by:
o Self-service portal
o Cloud API’s
o Pools of standard infrastructure
• Resilience, scalability and recoverability designed in at the application layer
Enterprise data
center
Cloud
enabled
data center
Cloud
platform services
Cloud
service provider
Business
functionality on cloud
Private
cloud
Managed
private cloud
Hosted
private cloud Public
cloud
Users
Shared
private cloud
Enterprises
Hybrid cloud management, service orchestration and integration
Traditional
IT
Enterprise
Data Center
Tap Into it. Build it.
Create a cloud strategy, roadmap and business model
Enterprise data
center
So-called “cloud adoption initiatives” can be delivered with multiple
deployment models
Enterprise data
center Enterprise
Your initial assessment:
where and why ?
Customer Intimacy
Analytics Service Adoption
Cloud Service Adoption
Supply Chain Collaboration
Refining your position using IT
business value enablers (attributes)
Define cloud mission to enhance or
maintain your position
Strategy
Critical Success
Factors
Mission for the cloud enabled
business program
Strategy
Critical Success
Factors
Mission for the cloud enabled
business program
Initial position of your
competitors ?
Targeting your new position:
how to improve or maintain?
MISSION
FinancialFinancial Process
Effectiveness
Citizen
Satisfaction
Innovation &
Growth
STRATEGY
CRITICAL SUCCESS FACTORS
WHAT SHOULD THE PROGRAM ACCOMPLISH?
To manage and maintain our water assets cost effectively while improving our service to our customers.
HOW WILL THE PROGRAM ACHIEVE ITS OBJECTIVES?
1. Better management and tracking of asset performance, age and condition
2. Better tracking of spend on parts and labor for repair work
3. Increase customer satisfaction through pro-active maintenance of assets
HOW DOES THE PROGRAM GAUGE PERFORMANCE?
• ROI / Payback period
• Indirect labor savings
• Direct labor savings
• Reinvestment of
savings for
infrastructure
improvements
• Improved crew
utilization
• Reduction in cycle
time
• Reduced back log
• Fewer emergency
repairs
• Higher customer
satisfaction ratings
• Reduced service
disruptions
• Improved emergency
response times
• Use of predictive
analysis methods to
reduce asset failures
• New services offered
USE CASES
Complete the balanced score card
Cloud business strategy approach
Development led by the IBM Cloud Computing Architecture Board
• Comprising technology leaders from IBM Research and IBM’s software, systems and services organizations
• >50 of IBM’s top cloud computing experts represent the core team
Derived from extensive client interaction combined with IBM’s extensive capabilities and experience in building enterprise-class IT systems.
The CCRA provides specifications for
• The physical components of a cloud implementation (network, compute, storage, virtualization)
• Software components required to run management
• Operational processes
• Governance policies tailored for the environment or enterprise
A process of continuous improvement helps
ensure that the reference architecture is both
responsive to changing client and security
requirements and incorporates technology
developments via IBM products and evolving
design specifications.
Cloud Computing Reference Architecture (CCRA) development process
Understand
environment
Define roadmap
& first project Define client
Requirements
Design
solution
Detail design
to define BOM
1. Business drivers
2. Business
processes
3. Current IT
environment
4. Candidate coud
services
5. Use cases and
actors
7. System context
8. Architecture
overview
9. Architecture
decisions
10. Operational
model
11. Roadmap
12. Project scope
6. Non-functional
reqirements
Let's assume you want to engage on the cloud path, and architect an
end-to-end solution. We have defined 12 steps in the CCRA approach