Enterprise Architect's Role in Cloud Adoption
•Download as PPT, PDF•
6 likes•1,491 views
The document discusses the role of enterprise architects in cloud adoption. It provides examples of how enterprise architects helped two clients leverage cloud computing to improve user experiences and enable rapid business transformation. The key takeaways are that enterprise architects should utilize their expertise in enterprise architecture domains to support cloud adoption and lead enterprise-wide transformation initiatives involving cloud. Architects need skills in business processes, business cases, ROI analysis and technical architecture definition to effectively guide organizations' cloud strategies.
![Agenda ,[object Object],[object Object],[object Object],[object Object],Cloud, the Enterprise, and the Enterprise Architect](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (15)
Similar to Enterprise Architect's Role in Cloud Adoption
Similar to Enterprise Architect's Role in Cloud Adoption (20)
Recently uploaded
Recently uploaded (20)
Enterprise Architect's Role in Cloud Adoption
- 1. Cloud, the Enterprise, and the Enterprise Architect A necessary convergence for sustainable business value Pamela K. Isom, Executive Architect, IBM Global Business Services October 20, 2010
- 6. Infrastructure-as-a-Service (IaaS) Platform-as-a-Service (PaaS) Software-as-a-Service (SaaS) Servers Networking Storage Middleware Collaboration Financials CRM/ERP/HR Industry Applications Data Center Fabric Shared virtualized, dynamic provisioning Database Web 2.0 Application Runtime Java Runtime Development Tooling Vendors Business Process-as-a-Service (BPaaS) Employee Benefits Mgmt. Industry-specific Processes Procurement Business Travel Business processes executed on behalf of the consumer by the provider Examples: compute resources, servers, networking, data center fabric, storage Cloud highlights Cloud, the Enterprise, and the Enterprise Architect In general there are four cloud service types and … Examples: database software, development tooling, JavaTM runtime, Web 2.0 application runtime Examples: e-mail, Web conferencing, collaboration, CRM, ERP, industry applications Examples: HR, procurement, accounting, back-office processes
- 9. Cloud and EA Interlock - can vary per business situation IaaS SaaS BPaaS PaaS methodology principles arch. domains Cloud enabled, all, in part, none
- 15. Thank you Q&A Notes contact me at [email_address]
Editor's Notes
- In fact a cloud computing study conducted last year showed that around the world there is a universal interest in cloud computing, and some key identified desired benefits organizations would like to receive when implementing a cloud solution. Cost take out was high with 77% saying this should be a benefit they get, and 75% citing time to value/speed/agility as a key benefit. At the same time, 69% have deep concerns about the security and resiliency of cloud computing. Most organizations are now looking at cloud computing from a business workload, or business process perspective, and those industries adopting cloud more rapidly tend to be those that are under substantial cost pressures today – government which includes federal, state, and local, education, manufacturing utilities and retail are early adopters of cloud.
- Workshop conducted by Pamela K. Isom (pisom@us.ibm.com) - 05.2010 – Impact 2010 Conference
- Workshop conducted by Pamela K. Isom (pisom@us.ibm.com) - 05.2010 – Impact 2010 Conference Exploratory Cloud – initial foray into cloud computing, with the implementation primarily aimed at developing cloud delivery skills and experience Departmental Cloud – both the IT organization supplying cloud services, and the consumer of cloud services, are within the same departmental management domain Enterprise Cloud – the IT organization supplying the cloud, and the organization consuming cloud services are within the same enterprise, but cross internal management boundaries Both BSS and OSS are within the same enterprise management boundary as the cloud services Exclusive Cloud – the IT organization(s) 1+n, providing cloud services, and the organization(s) 1+n, consuming cloud services, are known entities able to pre-negotiate service level parameters, e.g. a value net or procuring private cloud services from a third party. The business relationship can extend beyond simple consumer / supplier, but is not required. BSS is static, pre-negotiated, OSS is dynamic. Open Cloud – the consuming and supplying organizations are unknown to each other prior to services being requested. The primary implication is that the negotiation of cloud services must be an automated event, standards based, and governance terms are defined and controlled by the supplier. Both OSS and BSS are dynamic In both cases, the hardware/software supporting the cloud service are owned by the provider In a private cloud, both the consumer of cloud services, and the provider of those services, exist within the same enterprise A public cloud is one in which the consumer of cloud services and the provider of cloud services exist in separate enterprises