where cloud computing meets enterprise architecture

Download Where cloud computing meets Enterprise Architecture

Post on 20-Aug-2015




0 download

Embed Size (px)


  1. 1. Where Cloud Computing Meets Enterprise ArchitectureProf. Richardus Eko IndrajitPresident of IASA Indonesia indrajit@iasahome.org
  2. 2. To Know is To Love: am I an IT Architect ?Facts of Life:Richardus EKO Indrajit (indrajit@post.harvard.edu)International Zodiak: Aquarius - Chinese Zodiak: MonkeyLEFT BRAIN RIGHT BRAIN Professor of ComputerScience Band player (keyboard, guitar, and drum) 2 PhDs, 5 Masters, 1Bch., 25 certs Personal motivators, Master of Ceremony Reading, teaching,research Card Magic, Traveling, Photography, PNX 35 published books 5 music albums IT consultants,practitioners, and trainers Happy husband and father of three wonderful children
  3. 3. Scenario on the Air Transportation BusinessCEO to CIO instruction: We need an application that can automate the process of buying flight ticket to issuing boarding pass of our passengers Please dont forget to include the electronic payment system to ensure our revenue management intact You might develop or buy anything as long as it is fulfilled the requirement and within our company budget Dont forget to include the change management program in it as we have to educate many people
  4. 4. Scenario on the Air Transportation BusinessCMO to CIO new instruction: Most of our customers are group travellers, weneed to link all passengers through facebookapplication And they also want to have group messangersenabled through either their yahoo or blackberryplatform Oh, dont forget to synchronise their travellingscheduled with either microsoft outlook calendar orapple ical The most important thing is we need it as soon aspossible, not more than one month time
  5. 5. Scenario on the Air Transportation BusinessCFO to CIO instruction To beat our competitors, we allow our customers topay the ticket right after they enjoy the travel They can pay it by using credit card, debit card,prepaid card, or even paypal For those of them who are the customers ofcitibank or bangkok bank, a special discount isapplied One more thing, they can also free to use theirfrequent flyer points to be exchanged into money,based on the latest currency exchange determinedby bank of new york
  6. 6. Scenario on the Air Transportation BusinessCOO to CIO instruction As soon as our ticket agent issues the ticket, everypassengers can freely check-in and book the seatas they like through the internet or any mobiledevice and of course the boarding ticket can beprinted accordingly (physical or electronic boardingpass) For international flight, based on its travellingitenerary, the electronic immigration card would beissued automatically to immigration officer,allowing the passengers to have a quickimmigration process Can we have this thing implemented by next month
  7. 7. More Requirements from Time to Time Every repeated (loyal) passengers does not have todo the same process all over again Should their flight is delayed, they will automaticallyrebooked to the closest schedule To hinder the passengers of being late in boarding,an automatic message would be delivered throughtheir twitter account, sms, or blackberry push mail For reporting purposes, all record of travellingdocuments would be electronically sent to thepassengers and their sponsors As the business grows, the company developbusiness alliance with other air transportationcarriers an integrated system is required toenhance the services
  8. 8. The CIO ChallengeWhat the most CIOs is going to say:Can I kill myself?May I quit the job?Are you trying to fire me?Can I recruit more IT people and aresources?Have you decide to allocate a lot of money to do it?The Boss answer is: No! It is your job to make it a reality; do it within ourlimited budget; in a very short time; and with a goodquality of delivery! There is no excuse, because our competitor can do iteasily within the same constraints and similarobjectives also!
  9. 9. Focus of Today Discussion
  10. 10. Cloud Computing from Wikipedia Point of View
  11. 11. Cloud Computing from Google Point of View
  12. 12. The Common Denominator
  13. 13. The Philosophy of Cloud You can see it, but you can not touch it ! Its shape is unique, never be the same ! It covers us from heat, and give us rain ! Nobody owns it, but everybody loves it !Very easy to draw it, because it is simple !
  14. 14. The History of Cloud PhilosopyWe definitely need IT for our enterprise, but:What we need is IT capability, not its entityOur business is not IT, leave it to somebody elseWe can not bare the risks born from IT possessionPlease hide complexity, we have enough problems alreadyIT issues trigger internal conflict, lets transfer the problemsLets focus the energy on the value, not on the developmentPLEASE HELP US .. !!!
  15. 15. Handling the Dilemma If you try to fulfill the requirements internallyby yourself alone, you will face a high risk ofdevelopment and deployment with a highprobability of failure;but If you dont fulfill the requirements you will belosing the competition for sureSo, do not worry to throw this hot ball to somebodyelse who are used to face the problems andmaking money out of such dilemmatic issues !!!Leave it to the cloud !!!
  16. 16. The Way They Handle It as long as there are guarantee traffic oftransactions and volume within a certain period of time (multi yearcontract) a spectrum of services shall be provided because governing IT is their main business and managing services are their corecompetencies where the fees are based on operational cost(can be shifted to customers) so that the clients do not require to investanything
  17. 17. The Values of the Cloud Converting from CAPEX to OPEX due to thepotential economy of scale Staying away from COMPLEXITY problems(the beauty of simplicity) Transferring business RISKS to the otherparties Protecting the business from HIGH-COSToperation to conduct non-value added orsupporting activities (focus to the core values) Adopting easily with fast and dynamicCHANGE
  18. 18. The Various Business Models Outsourcing - time dependent, as time goes by,benefits increase Shared-Services - participation dependent, themore parties the better Exchanges Hub - standard dependent, themore compliance the higher value Utility Model - Infrastructure dependent, themature the technology the better
  19. 19. Look at the Complexity
  20. 20. Leave It to the CloudCloud #1 Cloud #2Cloud #3Cloud #4
  21. 21. Study di Cloud from Different PerspectivesCloud #1 Cloud #2Cloud #3Cloud #4From theFrom theUSERS Perspective PROVIDERS Perspective
  22. 22. Cloud Issues: WHO ? Who are they inside the cloud? Why are they involved within the cloud? What are the roles of each party? What are the relations among those parties? Who manage all participants in the cloud? Who is responsible for the liability issues? Who hold the highest accountability in thecloud? Who should be contacted in the emergencytime? Who will be liable for any risk or incidentoccurred?
  23. 23. Cloud Issues: WHAT ? What are they doing inside the clouds? What services they offer to the customers? What are the mechanism inside cloud? What kind of operational procedures theyfollow? What rules of the games exist within thecloud? What do and dont practices inside thecloud? What to be considered in involving the cloud? What is the high risk faced by the cloud? What kind of cloud is appropriate for thebusiness?
  24. 24. Cloud Issues: HOW ? How do they handle my data? How do they take care of the security issues? How do they design the robust infrastructure? How can they deal with various requirements? How far can they go with all complex services? How they make money from handling hugerisks? How can people trust them ethically andlegally? How to ensure the endured quality ofservices? How much money they will charge thecompany?
  25. 25. Cloud and Enterprise Architecture: Principle #1 Requirements: PUSH after thorough STUDY TrainingindependentValue-basedMass customisation designedapplicationparadigm
  26. 26. Cloud and Enterprise Architecture: Principle #2Bottom-Line: SERVICE LEVEL EXPECTATIONRoutinefeatures InnovativeAd-hoc 24/7capabilitiesneeds availabilities
  27. 27. Cloud and Enterprise Architecture: Principle #3 Compliance: GOVERNANCE MECHANISM Securitymodel Liabilityagreement AuditablesystemRiskstrategyBCP/DRP
  28. 28. Cloud and Enterprise Architecture: Principle #4 Value: BUSINESS MODELSScope and PartnershipsResponsibilities AgreementCAPEX and Scalability vs.OPEX Proportion Sustainability
  29. 29. The Way to Architect Your IT EnterpriseBusiness ArchitectureDynamic Products and Services required Adaptable ProcessesApplication andDatabase and Network andPeople andSoftware Information Infrastructure StakeholdersArchitectureArchitecture ArchitectureArchitecture
  30. 30. The Way to Architect Your IT EnterpriseBusiness ArchitectureApplication andDatabase and Network andPeople andSoftware Information Infrastructure StakeholdersArchitectureArchitecture ArchitectureArchitecture
  31. 31. One Million Dollar Question ?How to DESIGN and to DEVELOP aCOMPONENT BASEDTECHNOLOGY RESOURCES ???Application and Database and Network andPeople andSoftwareInformation Infrastructure StakeholdersArchitecture Architecture ArchitectureArchitecture
  32. 32. Thank You Questions and Answers SessionProf. Richardus Eko IndrajitPresident of IASA Indonesia indrajit@iasahome.org