1. Enterprise Transform: Now is the turning point
Live and Learn
Enterprise Transform: Now is the turning point
To service of data reliably, with the highest availability and in a cost-efficient way.
22 September 2016
Version 1.0

3. Apply game-changing technologies
Enhanced partnering opportunities
Full compatibility with the trend
Opportunity to rapidly adopt
Flexibility in infrastructure investments
Decreases in infrastructure costs
Reduced time to market
Cloud and the Enterprise

4. primary measurements
Quality Improved quality through use of specialized resources, processes, and facilities
Reliability Highly available solutions and infrastructure
Capability Flexibility of existing solutions to be cost effectively reused to enable new initiatives
Time Scaling of capacity to match business requirements directly (just in time)
Efficiency Cost improvement of operations
Velocity Agility to quickly adopt or support new functions and capabilities for the business
Focus Enablement of human resources to focus on business needs

5. Key Benefits of Cloud
cost efficiency
Agility
adaptability

6. COMMON SENSE

7. MISSION CRITICAL CORE BUSINESS IMPORTANT Essential
Categories of business systems
•• Critical to the health or safety of employees, clients, and partners
•• Will threaten the ongoing viability of the organization and/or its reputation if service is compromised for more than 1 to 4 hours
•• Will cause major legal, compliance, or regulatory ramifications if service is compromised for more than 1 to 4 hours
•• High chance of threatening the ongoing viability of the organization and/or its reputation if service is compromised for more than 4 hours
•• High chance of major legal, compliance, or regulatory ramifications if service is compromised for more than 4 hours
•• Critical component in providing academic, administrative, or medical operations
•• Outage impacts more than one area or system
•• Chance of threatening the ongoing viability of the organization and/or its reputation if service is compromised for more than 1 day
•• Chance of major legal, compliance, or regulatory ramifications if service is compromised for more than 1 day
•• Generates daily financial revenue equal to or greater than “$x” (business to determine actual number for itself in its context)
•• Outage impacts more than one area
•• Chance of threatening the ongoing viability of the organization and/or its reputation if service is compromised for more than 5 days
•• Chance of major legal, compliance, or regulatory ramifications if service is compromised for more than 5 days
•• Adds capability or value to a mission-critical system as a dependency

8. •• Critical to the health or safety of employees, clients, and partners
•• Will threaten the ongoing viability of the organization and/or its reputation if service is compromised for more than 1 to 4 hours
•• Will cause major legal, compliance, or regulatory ramifications if service is compromised for more than 1 to 4 hours
•• High chance of threatening the ongoing viability of the organization and/or its reputation if service is compromised for more than 4 hours
•• High chance of major legal, compliance, or regulatory ramifications if service is compromised for more than 4 hours
•• Critical component in providing academic, administrative, or medical operations
•• Outage impacts more than one area or system
•• Chance of threatening the ongoing viability of the organization and/or its reputation if service is compromised for more than 1 day
•• Chance of major legal, compliance, or regulatory ramifications if service is compromised for more than 1 day
•• Generates daily financial revenue equal to or greater than “$x” (business to determine actual number for itself in its context)
•• Outage impacts more than one area
•• Chance of threatening the ongoing viability of the organization and/or its reputation if service is compromised for more than 5 days
•• Chance of major legal, compliance, or regulatory ramifications if service is compromised for more than 5 days
•• Adds capability or value to a mission-critical system as a dependency

9. THE SCOPE Which services—existing or new—will be adopted
When the services will be adopted
Which cloud provider(s) will be used
Cost of preparation and migration
Potential savings that the migration will bring

10. WHAT IS CLOUD Virtualization Manage Hosting Mobility
Private Environment
Multi-tenancy
Service Farm
Hosting
Location Dependence
High CAPEX Upfront Cost
Dynamic Provisioning
Traditional License Model
Web Service

11. WHAT IS CLOUD Pay-per-Use Metered Billing Reduced upfront CAPEX
On-Demand, scalability Up & Down
Dynamic Provisioning & Process Automation
Multi-tenants with Network Access
Standard Web Services APIs for Integration
Self-Service Portal for End user

12. What is the first workloads to move to the cloud
Source: ESG, 2015

13. Best Practical DON’T try to iterate to success. DON’T over secure.
WORK from the data up to the services, and the application.
DON’T forget about performance, security, and governance.
DON’T follow the hype. Follow your own requirements.
DO consider the changes to the application architecture that should be made to take better advantage of the cloud platforms.
DO consider altering the application to use native cloud features.
DO make sure to understand all existing and future regulatory requirements, and consider those requirements in your cloud architecture and design.

14. ITSM/ISMS ITIL/ISO RISK/COMPLIANCE
COMMON SENSE
GRC/CIA
ITSM/ISMS ITIL/ISO RISK/COMPLIANCE

15. Thank you