Designing SOA for Multiple Business

Units

Tim Vibbert (SOA Chief)Enterprise Architect

Tim Vibbert (SOA Chief), • Work• Staff Systems Engineer Lockheed Martin

• School• MS Computer Information Science,

LaSalle University• BS Computer Science, UT-Martin

• SOA• OASIS SOA-RM/RA TC• Speaker Innovation World• Keynote Speaker SOA Executive Forum• SOA Consortium

• Social•Twitter: soachief•LinkedIn: Tim Vibbert (SOA Chief)•Blogs:•Thoughts of the SOA Chief•SOA Chief in the Clouds

Who is Lockheed Martin?

Lockheed Martin (LMT)• Defense Contractor• 2007 sales: $41B+• Employees: 140,000 world-wide

LM Corporate Complexity

Chairman, President& Chief Executive Officer

Executive Vice PresidentInformation Systems

& Global Services

Executive Vice PresidentElectronic Systems

Executive Vice PresidentSpace Systems

Senior Vice President & Chief Technology Officer

Senior Vice PresidentCorporate Communications

Vice President Operating Excellence

& Program Management

Senior Vice PresidentHuman Resources

Senior Vice PresidentStrategic Development

Senior Vice President& General Counsel

Senior Vice PresidentWashington Operations

Senior Vice PresidentBusiness Development

Vice President Ethics & Business Conduct

Executive Vice PresidentAeronautics

Executive Vice President& Chief Financial Officer

Business Area Executive Vice Presidents

Staff

LM IS&GS Complexity

Information Systems and Global Services (IS&GS)

• Sales: $10B • Projects: 4,000• Employees: 52,000 world-wide• Operations

1,000 locations, every state in the nation, 50 countries around the world

Global CustomersDomestic

International (UK)

What is the result of such complexity?

An Enterprise IT Jungle

How do enterprises reach this point?

Enterprise IT is an evolved system…

What are the Symptoms?

• Project Based Funding

• ROI Measured Per-Project

• IT Projects create messes for others

• Good for me bad for you thinking…

• Pushing cost and complexity

Tribalism within Organizations

Fragmenting by FunctionBy PlatformBy LegacyGeographyMergers and AcquisitionsSystem Integrators By Centralization

Business UnitsCulture TribesCustomersLong term/short term employees

Good for Me, Bad for You…

Multiple Business Unit SOAs

Business Unit 1 Business Unit 2

Result of SOA Silos

What’s the Cure?

How to Realize the promises of SOA?

Tribalism and Federation RelationshipDifferent groups may select different technologies to satisfy their requirements

• Business Unit 1• Open Source technologies

• Business Unit 2 selects • Single vendor SOA technology stack

Forces governance interoperability• Requires governance interoperability guidelines and

mechanisms• Tribe 1 can not control what tribe 2 does

Different tribes operate on different charging models• Requires design-time and runtime governance interoperability

• Runtime for enforcing service delivery contracts and gather invoicing metrics

• Design-time for advertising the available charging options via metadata

SOA Federation Patterns1. Direct SOA Federation

• Best for small number of federates• Each federate must have a priori knowledge of the other federates

• To which it can communicate• Configured via registry/repository metadata to expose services in other domains

2. Proxied SOA Federation• Many different federates are interconnected via foundation • Foundation serves as a proxy but does not host services

• Federates have no a priori knowledge of other federates just proxy

• Simple governance• Services and delivery contracts defined in foundation the propagated to

federates• Master-slave relationship

3. Complete SOA Federation• Best for extremely complex enterprises with many different federates• More complex extension of proxied pattern

• Hosts enterprise/shared services as well

• Federated governance• Federates have local authority but must observe enterprise foundation concerns

Direct SOA Federation

Business Unit 1 Business Unit 2

Proxied SOA Federation

Enterprise SOA Foundation

Business Unit 1Business Unit 2

Business Unit 3

Service Providers

WSDL/Policy

WSDL/Policy WSDL/Policy

WSDL/Policy

Complete SOA Federation

Business Unit 1

Enterprise SOA Foundation

Business Unit 2

Business Unit 3

Business Unit 4

Open Source

Vendor 2

Vendor 1Different Config

Service ProvidersWSDL/Policy

WSDL/PolicyWSDL/Policy

WSDL/Policy WSDL/Policy

Service ProvidersWSDL/Policy

Result of Enterprise Governance

4 Keys to SOA Federation1.Understand SOA is Enterprise

transformation & not just infrastructure• SOA is a journey not a project

2.Establish Enterprise objectives and outcomes• Define strategy for enterprise SOA adoption• Align business units with the enterprise• Realize impacts of federation and

interoperability on SOA Platform strategies• Align SOA federation strategy with SOA

Governance strategy

4 Keys to SOA Federation

3.Establish Enterprise SOA Foundation• Federated Ecosystem

• Determine the appropriate pattern(s)• Enterprise service delivery platform• Enterprise portfolio

• Governance• policies, processes, best practices• cost models, COE, enterprise service org• waiver plans

4.Allow business units to operate as federates

Pilamaya yelo (Thank You)