Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Designingsoaformultiplebusinessunits 090312214200-phpapp01

626 views

Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

Designingsoaformultiplebusinessunits 090312214200-phpapp01

  1. 1. Designing SOA for Multiple Business Units Tim Vibbert (SOA Chief) Enterprise Architect
  2. 2. Tim Vibbert (SOA Chief), <ul><li>Work </li></ul><ul><li>Staff Systems Engineer Lockheed Martin </li></ul><ul><li>School </li></ul><ul><li>MS Computer Information Science, LaSalle University </li></ul><ul><li>BS Computer Science, UT-Martin </li></ul><ul><li>SOA </li></ul><ul><li>OASIS SOA-RM/RA TC </li></ul><ul><li>Speaker Innovation World </li></ul><ul><li>Keynote Speaker SOA Executive Forum </li></ul><ul><li>SOA Consortium </li></ul><ul><li>Social </li></ul><ul><ul><li>Twitter: soachief </li></ul></ul><ul><ul><li>LinkedIn: Tim Vibbert (SOA Chief) </li></ul></ul><ul><ul><li>Blogs: </li></ul></ul><ul><ul><li>Thoughts of the SOA Chief </li></ul></ul><ul><ul><li>SOA Chief in the Clouds </li></ul></ul>
  3. 3. <ul><li>Who is Lockheed Martin? </li></ul>
  4. 4. Lockheed Martin (LMT) <ul><li>Defense Contractor </li></ul><ul><li>2007 sales: $41B+ </li></ul><ul><li>Employees: 140,000 world-wide </li></ul>
  5. 5. LM Corporate Complexity
  6. 6. LM IS&GS Complexity
  7. 7. Information Systems and Global Services (IS&GS) <ul><ul><li>Sales: $10B </li></ul></ul><ul><ul><li>Projects: 4,000 </li></ul></ul><ul><ul><li>Employees: 52,000 world-wide </li></ul></ul><ul><ul><li>Operations </li></ul></ul><ul><ul><li>1,000 locations, every state in the nation, 50 countries around the world </li></ul></ul>
  8. 8. Global Customers Domestic International (UK)
  9. 9. <ul><li>What is the result of such complexity? </li></ul>
  10. 10. An Enterprise IT Jungle
  11. 11. <ul><li>How do enterprises reach this point? </li></ul>
  12. 12. Enterprise IT is an evolved system…
  13. 13. What are the Symptoms? <ul><li>Project Based Funding </li></ul><ul><li>ROI Measured Per-Project </li></ul><ul><li>IT Projects create messes for others </li></ul><ul><li>Good for me bad for you thinking… </li></ul><ul><li>Pushing cost and complexity </li></ul>
  14. 14. Tribalism within Organizations <ul><li>Fragmenting by Function </li></ul><ul><li>By Platform </li></ul><ul><li>By Legacy </li></ul><ul><li>Geography </li></ul><ul><li>Mergers and Acquisitions </li></ul><ul><li>System Integrators </li></ul><ul><li>By Centralization </li></ul><ul><li>Business Units </li></ul><ul><li>Culture Tribes </li></ul><ul><li>Customers </li></ul><ul><li>Long term/short term employees </li></ul>Good for Me, Bad for You…
  15. 15. Multiple Business Unit SOAs Business Unit 1 Business Unit 2
  16. 16. Result of SOA Silos
  17. 17. <ul><li>What’s the Cure? </li></ul>
  18. 18. How to Realize the promises of SOA?
  19. 19. Tribalism and Federation Relationship <ul><li>Different groups may select different technologies to satisfy their requirements </li></ul><ul><ul><li>Business Unit 1 </li></ul></ul><ul><ul><ul><li>Open Source technologies </li></ul></ul></ul><ul><ul><li>Business Unit 2 selects </li></ul></ul><ul><ul><ul><li>Single vendor SOA technology stack </li></ul></ul></ul><ul><li>Forces governance interoperability </li></ul><ul><ul><li>Requires governance interoperability guidelines and mechanisms </li></ul></ul><ul><ul><ul><li>Tribe 1 can not control what tribe 2 does </li></ul></ul></ul><ul><li>Different tribes operate on different charging models </li></ul><ul><ul><li>Requires design-time and runtime governance interoperability </li></ul></ul><ul><ul><ul><li>Runtime for enforcing service delivery contracts and gather invoicing metrics </li></ul></ul></ul><ul><ul><ul><li>Design-time for advertising the available charging options via metadata </li></ul></ul></ul>
  20. 20. SOA Federation Patterns <ul><li>Direct SOA Federation </li></ul><ul><ul><li>Best for small number of federates </li></ul></ul><ul><ul><li>Each federate must have a priori knowledge of the other federates </li></ul></ul><ul><ul><ul><li>To which it can communicate </li></ul></ul></ul><ul><ul><ul><li>Configured via registry/repository metadata to expose services in other domains </li></ul></ul></ul><ul><li>Proxied SOA Federation </li></ul><ul><ul><li>Many different federates are interconnected via foundation </li></ul></ul><ul><ul><li>Foundation serves as a proxy but does not host services </li></ul></ul><ul><ul><ul><li>Federates have no a priori knowledge of other federates just proxy </li></ul></ul></ul><ul><ul><li>Simple governance </li></ul></ul><ul><ul><ul><li>Services and delivery contracts defined in foundation the propagated to federates </li></ul></ul></ul><ul><ul><ul><ul><li>Master-slave relationship </li></ul></ul></ul></ul><ul><li>Complete SOA Federation </li></ul><ul><ul><li>Best for extremely complex enterprises with many different federates </li></ul></ul><ul><ul><li>More complex extension of proxied pattern </li></ul></ul><ul><ul><ul><li>Hosts enterprise/shared services as well </li></ul></ul></ul><ul><ul><li>Federated governance </li></ul></ul><ul><ul><ul><li>Federates have local authority but must observe enterprise foundation concerns </li></ul></ul></ul>
  21. 21. Direct SOA Federation Business Unit 1 Business Unit 2
  22. 22. Proxied SOA Federation Enterprise SOA Foundation Business Unit 1 Business Unit 2 Business Unit 3 Service Providers WSDL/Policy WSDL/Policy WSDL/Policy WSDL/Policy
  23. 23. Complete SOA Federation Open Source Vendor 2 Vendor 1 Different Config Business Unit 1 Enterprise SOA Foundation Business Unit 2 Business Unit 3 Business Unit 4 Service Providers WSDL/Policy WSDL/Policy WSDL/Policy WSDL/Policy WSDL/Policy Service Providers WSDL/Policy
  24. 24. Result of Enterprise Governance
  25. 25. 4 Keys to SOA Federation <ul><li>Understand SOA is Enterprise transformation & not just infrastructure </li></ul><ul><ul><li>SOA is a journey not a project </li></ul></ul><ul><li>Establish Enterprise objectives and outcomes </li></ul><ul><ul><li>Define strategy for enterprise SOA adoption </li></ul></ul><ul><ul><li>Align business units with the enterprise </li></ul></ul><ul><ul><li>Realize impacts of federation and interoperability on SOA Platform strategies </li></ul></ul><ul><ul><li>Align SOA federation strategy with SOA Governance strategy </li></ul></ul>
  26. 26. 4 Keys to SOA Federation <ul><li>Establish Enterprise SOA Foundation </li></ul><ul><ul><li>Federated Ecosystem </li></ul></ul><ul><ul><ul><li>Determine the appropriate pattern(s) </li></ul></ul></ul><ul><ul><ul><li>Enterprise service delivery platform </li></ul></ul></ul><ul><ul><ul><li>Enterprise portfolio </li></ul></ul></ul><ul><ul><li>Governance </li></ul></ul><ul><ul><ul><li>policies, processes, best practices </li></ul></ul></ul><ul><ul><ul><li>cost models, COE, enterprise service org </li></ul></ul></ul><ul><ul><ul><li>waiver plans </li></ul></ul></ul><ul><li>Allow business units to operate as federates </li></ul>
  27. 27. Pilamaya yelo (Thank You)

×