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!
Cloud computing: onderbouwde keuzes voor IT en business - Edwin Schouten (IBM) CIO SUMMIT 2014
1. An open cloud architecture is emerging, a must to ensure portability
while preventing vendor lock-in
Analytics
API
Commerce
API
Collaboration
Location
API
API
Data
Services
API
API economy
External
Ecosystem
SaaS
API
Marketplace
App
API
Solutions
API
Cloud operating environment
PaaS
Services & composition patters
API & orchestration
services
Traditional
workloads
Data
store
Mobile
Middleware
Services
Security
Operations
Develop
ment
Software defined environments
IaaS
Workload definition, optimization & orchestration
Resource abstraction & optimization
Software defined
compute
Software defined
storage
Software defined
network
Hardware
2. Cloud enabled
Cloud native
•
Legacy applications based on
traditional middleware stacks
•
Emerging / new applications written to
exploit the new cloud platform
•
Cloud delivery enabled by:
•
Cloud delivery enabled by:
o
o
•
Automation
o
•
Standardization
Portal-enabled access
Requires migration of large volumes of
applications
Resilience assumed at the
infrastructure layer
Competitive displacement
opportunity
+
o
o
Cloud API’s
o
•
Self-service portal
Pools of standard infrastructure
Resilience, scalability and recoverability
designed in at the application layer
New market growth
opportunity
3. So-called “cloud adoption initiatives” can be delivered with multiple
deployment models
Cloud
platform
services
Cloud
enabled
data center
Business
functionality
on cloud
Cloud
service
provider
Create a cloud strategy, roadmap and business model
Traditional
IT
Enterprise data
Enterprise
center
Data Center
Private
cloud
Enterprise data
center
Managed
private cloud
Hosted
private cloud
Enterprise data
center
Enterprise
Shared
private cloud
Public
cloud
Enterprises
Users
Hybrid cloud management, service orchestration and integration
Build it.
Tap Into it.
4. Cloud business strategy approach
Your initial assessment:
where and why ?
Refining your position using IT
business value enablers (attributes)
Initial position of your
competitors ?
Customer Intimacy
Analytics Service
Adoption
Supply Chain
Collaboration
Cloud Service
Adoption
Targeting your new position:
how to improve or maintain?
Define cloud mission to enhance or
maintain your position
Complete the balanced score card
MISSION
WHAT SHOULD THE PROGRAM ACCOMPLISH?
To manage and maintain our water assets cost effectively while improving our service to our customers.
Mission
STRATEGY
for the cloud enabled
business program
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
CRITICAL SUCCESS FACTORS
HOW DOES THE PROGRAM GAUGE PERFORMANCE?
Financial
Strategy
Critical Success
Factors
•
•
•
•
ROI / Payback period
Indirect labor savings
Direct labor savings
Reinvestment of
savings for
infrastructure
improvements
Process
Effectiveness
• Improved crew
utilization
• Reduction in cycle
time
• Reduced back log
• Fewer emergency
repairs
Citizen
Satisfaction
• Higher customer
satisfaction ratings
• Reduced service
disruptions
• Improved emergency
response times
USE CASES
Innovation &
Growth
• Use of predictive
analysis methods to
reduce asset failures
• New services offered
5. Cloud Computing Reference Architecture (CCRA) development process
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.
6. 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
Understand
environment
Define client
Requirements
1. Business drivers
4. Candidate coud
services
2. Business
processes
5. Use cases and
actors
3. Current IT
environment
6. Non-functional
reqirements
Design
solution
Detail design
to define BOM
Define roadmap
& first project
7. System context
9. Architecture
decisions
11. Roadmap
8. Architecture
overview
10. Operational
model
12. Project scope
7. Cloud Computing Reference Architecture (CCRA) – overview
Architectural
principles
Architecture
overview
Standards &
terminology
Cloud service
creation
Use cases & roles
Non-functional
requirements
Consumability
Operational
support services
Software-as-aService
Business support
services
Component model
Operational model
Architectural
decisions
Management
processes
Cloud service
provider
Security
Resiliency
Overcommitment
& placement
Performance &
scalability
Multi-tenancy
Server
virtualization
management
Storage
virtualization
management
Network
virtualization
management
Hybrid cloud
Metering,
accounting &
rating
8. Cloud Computing Reference Architecture (CCRA) – overview
Cloud Service
Consumer
Common Cloud
Management Platform
API
Consumer Inhouse IT
Infrastructure
IaaS
Customer
Account
Management
Provisioning
Monitoring &
Event
Management
Change &
Configuration
Management
Service
Request
Management
Order
Management
Pricing
Entitlement
Management
Image
Lifecycle
Management
Incident &
Problem
Management
IT Service
Level
Management
IT Asset &
License
Management
Capacity &
Performance
Management
Service
Composer
Service
Offering
Management
Subscription
Management
Service
Request
Management
Service
Offering
Catalog
Contracts &
Agreement
Management
Service Automation Management
Platform & Virtualization Management
API
Middleware
Service
Component
Developer
BSS – Business Support
Services
Service Delivery Catalog
Infrastructure
Mgmt Interfaces
Applications
Service Management
Business
Processes
PaaS
Platform Mgmt
Interfaces
Consumer
Business
Manager
Business
Manager
Metering
Rating
Billing
Clearing &
Settlement
Accounts
Payable
Service Development Portal & API
SaaS
Software Mgmt
Interfaces
BPaaS
Service
Manager
OSS – Operational Support
Services
Service Consumer Portal & API
API
Service
Integrator
API
Cloud Service
Integration
Tools
Existing &
3rd party
services,
Partner
Ecosystems
BP Mgmt
Interfaces
Cloud Services
Consumer End
user
Cloud Service
Creator
Cloud Service Provider
Accounts
Receivable
Transition
Manager
Operations
Manager
Service Creation
Tools
Service
Management
Development
Tools
Service Runtime
Development
Tools
Software
Development
Tools
Service Provider Portal & API
Deployment
Architect
Offering
Manager
Security &
Risk Manager
Customer
Care
Image Creation
Tools
Consumer
Administrator
Inf rastructure
Security, Resiliency, Performance & Consumability
Governance