Weitere ähnliche Inhalte Ähnlich wie Service Oriented Infrastructure (20) Kürzlich hochgeladen (20) Service Oriented Infrastructure7. SOI: What it looks like Services Subscribers Publishers Identity Management Management & Monitoring Database File Email Collaboration Web Hosting CRM Portal 8. Getting There Define & Prioritise Services Define Enterprise Consumer Experience Plan Forward & Backward Consolidation Transition to Service Management 23. Does SOI really have an ROI Basic Rationalized Virtualized Service-Based Standardized Infrastructure resources pooled Services managed holistically Uncoordinated infrastructure Standard resources, configurations Consolidate to fewer Policy/Value-Based Dynamic optimization to meet SLAs SMDS Objective Ability to Change Pricing Scheme Business Interface Resource Utilization Organization IT Management Processes Reduce complexity Economies of scale Flexibility, reduce costs Service-level delivery React Weeks Weeks to days Weeks to minutes Minutes Months to weeks Fixed costs Reduced, fixed costs Fixed shared costs Variable usage costs None, ad hoc Business agility Minutes to seconds Variable business costs Class-of-service SLAs Class-of-service SLAs Flexible SLAs End-to-end SLAs No SLAs Known Rationalized Shared pools Service-based pools Unknown Central control Consolidated Pooled ownership Service-oriented None Business SLAs Policy-based sharing Business-oriented Reactive -Proactive Life cycle management Proactive Mature problem mgmt Proactive Prediction, dynamic capacity Service End-to-end service management Chaotic – Reactive Ad hoc Value Policy management 26. © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. Hinweis der Redaktion 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. Each new application or part of infrastructure is introduced as a stovepipe. 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. Higher cost, more complexity Less secure (no end-to-end identity management) Compliance difficult/expensive to enforce cross-company CRM, ERP vendors are typically 3 rd party. However these are now being forced to take an SOA perspective. 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. Poor user experience re-enforces the “IT as a necessary evil” mindset Lower productivity These all increase business risk Cost implications of diuplication Poor service experience for customers (inconsistencies) 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. The problem with consolidation from an SOI perspective is that it is viewed as a project. Once consolidation is complete, its finished. There is no change in approach for future projects, resulting in more stovepipes. SOI fundamentally changes the thinking from stovepipes and solutions to shared services which applications can consume. The definition of insanity if doing the same thing and expecting different results! 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. ROI=Estimated cost savings (e.g. lower management overhead) and improved user experience vs technical complexity and scale of service 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. User experience is one of the key things which, if done correctly, will make the business think of IT as a strategic asset. The moment IT becomes “exposed” to the business (e.g. having to manually map network drives, call helpdesk to add a new printer when roaming), it becomes an overhead: poor perception, and costs productivity At this phase, we’re looking at the enterprise user experience, not service user experience. Subscriber experience = graceful failure mode: when service dependency fails, give users a “service currently unavailable” page rather than application error 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. Infrastructure Architects can help Solution Architects in this area 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. Service Support Incident management Problem management Configuration management Change management Release management 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. Technology: no QOS. Support of vendor (e.g. moving functionality out of stove pipe) Performance: moving functionality off hosts (e.g. MIIS and SQL) 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. Virtualisation: some QOS controls isolation (security/regulatory) Clustering: Offering better SLAs for minimal extra cost Lowering operational cost – maintenance easier to perform in service hours 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. Capacity: how much storage? How much network bandwidth Performance: user/subscriber load Scalability model: up, out, partition? 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. Schema: use ADAM as application directory where you can extend the schema. Proxy calls into AD meaning you still take advantage of the directory “service”. Regulatory: split the users across forests (or maybe domains). Establish trusts if possible. Security: split the users across domains 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary. Gartner model 02/26/12 19:30 © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.