SOA Overview and Benefits at Ford

An Overview of SOA
SOA Center of Excellence
July 2012
Haiwei Chen
Agenda
Ford Global SOA Program

SOA Jargon
Whats Different about SOA?
SOA Goals and Benefits
Implementing SOA at Ford
Q&A
12/3/2017
Application Development 2
Ford Motor Company IT
Agenda
Appendix
SOA definition by OASIS
Key principles of SOA
Web Services characteristics
When to create Web Services?
IBM DataPower and Microsoft BizTalk
Global SOA Program Scorecard (Jan 1st, 2012)
Case studies
References
12/3/2017
Global SOA Program
Established in 2008, with the goal of defining
processes, standards and best practices to identify,
build, and catalog reusable software assets
Is managed under Java Shared Services within AD
Having participants from AD NA, FoE and APA,
across different functional areas
ET Enterprise Architecture, Solution Architecture, Research
Java Center of Excellence
SOA Center of Excellence
Ford Credit
Key areas
Program Management and SOA Governance
Standards and Best Practices (aka Service Architecture)
SOA Infrastructure
12/3/2017
Global SOA Program Scorecard (July 1, 2012)
Savings ($000s)
Development 2010 2011 YTD Cum Points of interest

savings 2012 2009-2012
Realized program savings now > $4M, >
Target $1,540 $2,000 $2500 $7,240 $1M per year
Potential (pre- $2,000 $3,470 $1,181 $8,228

analysis)
Rejected -$416 -$758 -$237 -$1,697
Potential (post- $1,584 $2,712 $944 $6,531

analysis)
O/(U) target $44 $712 $-1,556 $709
Realized from $1,112 $1,509 $928 $4,100

development
Remaining $472 $1,203 -$16 $2,431
Memo:
Potential (post-analysis) is measurement against target
since money is removed from projects at SEER estimate.
Agility
Memo:
Dev hours saved is calculated as potential 2012 development hours saved from re-use: 20,708 hrs
post-analysis savings/avg hourly rate ($48)
SOA Team Connect Site /SOA Team tab/ Program Management 5

What is SOA?
Definition
SOA is an architectural style that encourages the
creation of loosely coupled business applications
with services as building blocks. The services are
potentially reusable, interoperable, and can be
composed, to enable business flexibility.
There are other definitions

Definition from OASIS can be found in the Appendix
12/3/2017
Business Capability
Business Capability
defines what a business does or needs to do
to fulfill its objectives and responsibilities
not about how things are done or to be done
examples
Updating vehicle service history
Decoding VINs
Submitting warranty claims
Fulfilling vehicle orders
Note: in this presentation, when we say capability we mean business
capability.
12/3/2017
Service
Service
is an implementation of related capabilities;
exists as physically independent software and
can be used by applications via remote access.
Note: A Component is a set of related classes or modules that provide

capabilities and need to be distributed to applications for use.
12/3/2017
Web Services
Web Services
are services
are implemented by following Web Services
Interoperability standards
are commonly used to realize SOA
are current recommendation at Ford
Note: Web Services Interoperability Organization (WS-I) is an

industry consortium governing Web Services interoperability.
12/3/2017
Whats different about SOA?
SOA focuses on Services
Services are building blocks for solutions;
Services are reusable across ownership boundaries.
Uniform means for offering / accessing services results in

easier integration
Consumer and provider interoperate intrinsically;
SOA enables easier integration with legacy systems.
SOA based solutions provide better support for changes

Service interface decouples consumer and provider;
Services can be repeatedly composed to create new solutions.
12/3/2017
Case Study: Consumer Data Refinery
CDR Application in Marketing and Sales
supports inquiries, updates, and management of consumer
information, vehicle ownership, vehicle service history, service offers,
marketing promotion, etc.
capabilities (e.g. register consumer, update vehicle service history, retrieve
consumer contact info ) are implemented as reusable Web Services
LCS
(Consumer)
IP Firewall
IP Firewall
MSS360,
CDR
INRIX(SYNC) DataPower
(Provider)
(Consumer)
Owner Web
(Consumer)
Internet DMZ Ford Intranet

12/3/2017
Impact Analysis: Consumer Data Refinery
With traditional approach
if consumer related information is duplicated in multiple applications
data fragmentation is an issue; data synchronization among systems is a challenge
if applications duplicate capabilities (e.g. managing marketing promotion)
applications end up with non-value-added development work and support
if applications integrate with CDR to access needed functions / data
through various mechanisms
more cost in managing / supporting application portfolio, different integration methods
With SOA / Web Services

opportunity to commonize business functions and determine System of
Record for common information; and implement them as services
enable reuse / single-point-of-access
result: an IT enterprise with reduced waste and redundancy, reduced size and
operational cost
effort: SOA mindset; closer collaborations between business and IT, and more up-front
analysis; service-oriented analysis and design; build and support services
12/3/2017
Case Summary: Whats different about SOA?
App1 App2 App3 App1 App2 App3
Service Interfaces
Application Specific Interfaces Service1 Service2 Service3
Focuses on services which are building blocks for solutions

Services can be reused across application and organization
boundaries.
12/3/2017
Case Study: VIN Decoder Service
VIN Decoder in Marketing and Sales
provides basic vehicle information based on supplied VINs
service-enabling Mainframe capability for non-Mainframe apps
the service offers technology-agnostic interface, making systems
easier to interoperate
Stored Procedures contain

Client/Server the logic to perform
Consumer ELVIS validation and decoding of
the VIN string
J2EE Consumer WSMOD

(Service Provider) DB2 Connect
DB2
Mainframe

Consumer
12/3/2017
Impact Analysis: VIN Decoder Service
if VIN decoding and/or VINs are duplicated in multiple applications
adding fragmentation / redundancy to the enterprise yields no business value
integration with ELVIS DB2 SP via DB2 Connect
assuming consumer applications can make DB2 RPC call is a risk
letting ELVIS manage DB2 access control isnt a good design
changes are hard, esp. when the capability is expanded to support new
requirements (e.g. Ford Credit Wholesale Securitization)
tight coupling with use of DB2 leading to more integration effort and cost, esp. when
changes are needed
encapsulate the capability provided by Mainframe with a web service
the service is standard-compliant & supported by different vendor tools
consumers and provider communicate using XML-based messages
result: consumers and the provider interoperating natively makes integration easier
effort: SOA mindset; up-front collaborations/analysis among stakeholders; service-
oriented analysis and design; build and support the services
12/3/2017
Case Study: B2D Integration
High-level Requirement
Business interaction between Ford internal, dealer-facing
applications (OWS/LDS/) and Dealership/DMS
Need to support
A few thousand dealerships
Disparate systems at dealerships
Need loosely-coupled architecture to support changes
and interoperability
Solution based on SOA / Web Services
follows industry standards, not tying to particular vendor, platform
enables complex message exchange patterns
leverages service intermediary for common functions
12/3/2017
Impact Analysis: B2D Integration
Huge challenges
Dealership / DMS may not want to take traditional approaches such as EDI, FTP, etc.
to interact with Ford internal systems
Use of VPN / ANX for communications may not be possible
high cost in delivering a viable solution
high risk for failure

commonization of process and information
use of public internet for dealers to communicate with Ford, with
security solution being part of SOA implementation
standards-based solution supported by different vendors
loosely-coupled architecture eases the integration effort in adding new dealerships
and new Ford internal dealer-facing applications and supporting changes;
the solution is scalable
effort: SOA mindset; up-front investment; service-oriented analysis and design; build
ESB functions; build and support services
12/3/2017
Case Study: B2D Integration
SPS
SOAP X509 SOAP

IP Firewall
IP Firewall
HTTP/HTTPS Security HTTPS/WSL
Dealer DMS DataPower BizTalk ESB OWS
LDS
Message
Store
12/3/2017
App1 App2 App3
Service Interface Service Interfaces
Service1 Service2 Service3
SOA advocates loosely coupled architecture

Web Services are built to be interoperable, making integration easier
Service-enabling capabilities implemented on legacy systems makes
legacy assets easier to access
12/3/2017
Case Study: Bill of Material Foundation
BOMF in PDS
Part of EPIC Program (Enterprise Process and IT Commonality)
Managing BOM information
Addressing issues
Multiple masters of BOM information each with its own interface
Conceptual differences in the data model for each system
Front-end tightly coupled with back-end solution

Strategic direction / solution
Providing BOMF service layer to decouple top-hat and platform
Creating early BOM repository and Web Services
Establishing a foundation for future BOM repository and services
12/3/2017
Impact Analysis: Bill of Material Foundation
continue to use various existing systems (AVBOM, PADB, WERS, )
different systems / platforms / interfaces providing same or similar capabilities
point-to-point interaction with different mechanisms
and integrate with the final, grand BOMF when it becomes available
integrating with BOMF means dramatic changes (tear-off) for consuming applications
not acceptable by business
taking an iterative / incremental approach
defining commonalities, i.e. business capabilities, for particular areas
creating services for those business capabilities
service interfaces are exposed, not the underlying systems, platforms
consumer applications have dependency on the interfaces, not service
implementations
both service consumers and service providers can evolve on their own, yielding
increased business and IT agility
effort: SOA mindset; up-front investment; service-oriented analysis and design;
potential for leveraging ESB functions; build and support services
12/3/2017
Case Study: Bill of Material Foundation
BOMF
Top Hat
user-centric applications focusing on UI, navigation, business process flow,
Platform
back-end providing underlying capabilities / solutions
Demand
/ Use
Interface
Supply
/ Solution
12/3/2017
App1 App2 AppN
Demands
Interface
Suppliers
SystemA SystemB SystemX
Use / supply of services are implementation, platform independent

Consumer applications have little or no knowledge of new system being
the service provider
Changes are easier with service interfaces decoupling the demands and
suppliers
12/3/2017
SOA Goals and Benefits
Increased federation
Services are building blocks of larger compositions while maintaining their
individual autonomy and self-goverance
Increased business and IT alignment
Increased process and information commonization / standardization
Enabling commonization of business processes
Avoiding data duplications with single version of truth
Increased intrinsic interoperability
Standardized services are natively interoperable
Overcome integration challenges
Increased leverage of existing, legacy systems
Service-enabling existing IT assets
Extending the life of legacy applications through gradual migration
Increased business and IT agility
Increased return on investment
Improved efficiency and reduced cost
12/3/2017
Ford has adopted SOA as a strategy
The journey started in 2007
Accomplishments
We have SOA Governance process in place
Weve created standards & best practices
We leverage SOA infrastructure functions
IBM DataPower and Microsoft BizTalk ESB
IBM WebSphere Service Registry and Repository
Focuses of the next six to twelve months

SOA enablement for legacy systems
Exploring alignment of SOA and BEP, SOA and Agile
More use of SOA infrastructure components
Training
12/3/2017
Key to Continued Success
Wider adoption of SOA mindset in IT community (AD, BIT)
Early involvement from Business Architect, Business
Analyst in identifying service opportunities, and performing
service-oriented analysis
Consistent application of design principles and design
standards
Placing best resources in your SOA initiatives
Leveraging JCOE and SOA CoE
Training
Challenges
Its a journey; thereve been challenges at different stages.
12/3/2017
Takeaways
Services are building blocks of IT solutions,
potentially re-usable across ownership boundary.
Applications interoperating with Web Services are
loosely coupled, resulting in easier integration.
Business capabilities implemented in legacy
systems can be service-enabled for broader use.
SOA-based solutions provide increased business
and IT agility.
Fords SOA implementation has matured, but the
journey continues.
Consider SOA an option in your next IT initiative.
12/3/2017
Q&A
12/3/2017
Appendix
12/3/2017
What is SOA?
Service-Oriented Architecture (SOA)

is a paradigm for organizing and utilizing
distributed capabilities that may be under the
control of different ownership domains.
it provides a uniform means to offer, discover,
interact with and use capabilities to produce
desired effects consistent with measurable
preconditions and expectations.
(Source OASIS)
12/3/2017
Key Principles of SOA
Explicit boundaries
Loosely coupled
Standards-compliant
Metadata-driven
Document-centric
Share interfaces, not implementations
Interface are resilient
Services are autonomous
12/3/2017
Web Services != SOA
Web Services
Standards-based, widely supported
Leading technology for implementing SOA
A in SOA is for Architecture
Characteristics such as Loosely Coupled, Sharing
Contracts not implementations,
Design principles and standards
SOA can be implemented without using Web
Services
Developing Services / Web Services here and there
does not necessarily lead to a successful SOA
12/3/2017
Web Service Characteristics
Has a well-defined service contract.
Service contract is exposed via implementation-independent
interface
Service interface is described in platform-neutral form.
Service interface exists as a physically decoupled architectural element.
More emphasis on service interface - Metadata is a First-
Class Citizen
Is Interoperable and standards based.
Is composable.
Service operations often need to be designed to exchange
document-centric messages, such as entire business
documents.
Messages are usually structured by XML schema.
12/3/2017
When to create Web Services?
Accessing functions across ownership boundaries
Supporting interactions between Ford and external vendors
Functions across line of business within Ford
Accessing functions across platform (technology,
language, implementation boundaries) to support
Interoperability.
Support data sharing without replication
Especially for data that often changes
Complex data model required for the function to operate
Supporting single version of truth
Underlying implementation of a function changes
frequently due to changes in business and / or technology
Functions that support / enable / require service
composition, transformation, orchestration by leveraging
infrastructure capability.
Business function, business process.
12/3/2017
DataPower & BizTalk Best Fit Analysis
Functionality DataPower BizTalk
Security Processing Use DP External for B2B WS security. Not suitable.
Pub/ Sub, Store/ Forward Not available. Well suited.

(Asynchronous Messaging)
Schema Validation Well suited. Not recommended
Protocol mediation HTTP(S) common implementation in HTTP(S) common implementation in

Supported
Ford Ford
MQ possible but not proven out. MQ common implementation in Ford..
FTP/SFTP possible but not ideal. FTP/SFTP possible but not proven
out.
Service Orchestration Not suitable. Well suited.
Request Response(Synchronous) Well suited for service Virtualization. Not preferred.
Message Transformation Well suited. Flexible GUI. Minimize transformations.

Offload to DP.
Event Processing Not suitable. Well suited.

Research
Rules Processing Not suitable. Has Rules Engine for lightweight rules
encoding.
Legacy Modernization Well suited but not proven out. Not preferred.
12/3/2017
BizTalk Capabilities
Microsoft BizTalk Server 2010 Capabilities
Protocol bridge
HTTP(S), SOAP, MQ, WCF, SQL, Oracle, DB2,
FTP(S), SharePoint, File, PeopleSoft, others
Message mediation
Message transformation
Message routing
Logic Orchestrations
BizTalk ESB 18-NOV-2011 36

BizTalk Capabilities
Microsoft BizTalk Server 2010 Capabilities
Reliable messaging (Store and Forward)
Message Exchange Patterns (MEP)

Publish/Subscribe
Asynchronous request/response
Synchronous request/response
One way
BizTalk ESB 18-NOV-2011 37

Global SOA Program Scorecard (January 1, 2012)
Service and Re-usable Asset metrics
Production Services Ratings Registered Services Category & Status

Dec 1 Jan 1
Usage intent In production In development
Production Services 195 196
Re-usable as-is (SOAP) 63 63 Enterprise 31 23
Reusable- Advise SOAP changes 56 57 Portfolio 136 54
Non-SOAP reusable items 75 75
Application 29 38
Not recommended 1 1
Totals 196 115
Production Service Types

Web Services 121
DB Stored Procedures 23
MQ, HTTP, Other 52
KPI
% recommended as-is services is 52% (Does not
include non- SOAP items.)

Global SOA Program Scorecard (January 1 2012)
Service Governance and Cultural Change
YTD Service Opportunity Reviews Service Mediations
US FoE APA CMSA Successfully resolved 6
# of known dev projects 244 37 113 3 In progress 0

Unsuccessfully resolved 1
% of projects with SOA potential 27% 30% 19% 100%
Total 7
% reviewed projects using SOA 77% 55% 57% 67%
Rejected Reasons
Points of interest
APA shows Technical 20
continued Project cancellations 103
improvement
over Q3 Requirement changes 141
Resulting recommendations Functionality lacking 11

Other 14
Service/Re-use Pipeline
Total 289
(2009-2011)
New/updated Re-use Education Sessions
services services
General 15 SOA User
Recommendations 336 489 group
Business Analyst 5
Evaluating 40 128 members:
PTG 1 321
In development 79 119
Architects/Developers 15
Implemented 103 67
Project Managers 5
Rejected 114 175
SD LL5+ 5
Security & Controls 1
SOA Team Connect Site /SOA Team tab/ Program Management

Total 47
39
Global SOA Program Scorecard (January,1 2012)
Savings ($000s)
Development 2009 2010 YTD Cum Points of interest

savings 2011 2009-2011
$2,712K savings substantially exceeds
Target $1200 $1,540 $2,000 $4,740 annual target by 36%, frees development
hours for other projects
Potential (pre- $1,577 $2,000 $3,470 $7,047
analysis)
Rejected -$286 -$416 -$758 -$1,460
Potential (post- $1,291 $1,584 $2,712 $5,587

analysis)
O/(U) target $99 $44 $712 $847
Realized from $551 $1,112 $1,509 $3,172

development
Remaining $740 $472 $1,203 $2,415
Memo:
Potential (post-analysis) is measurement against target
since money is removed from projects at SEER estimate.
Agility
Memo:
Dev hours saved is calculated as potential 2011 development hours saved from re-use: 56,500 hrs
post-analysis savings/avg hourly rate ($48)

Case Studies
CDR (Consumer Data Refinery)
Requirement
Need to support inquiries and updates of consumer, vehicle
ownership, vehicle service history, servicer offers, marketing
promotion,
Solution
Exposing capabilities as Web Services
Data sharing without replication / single version of truth
Some of the Web Services (in PROD)
ConsumerContact
ConsumerB2CProfile
ConsumerServiceHistory
ConsumerOwnerRewards
ConsumerServiceRebateSelection
12/3/2017
CDR Web Services with DataPower
LCS
(Consumer)
SOAP X509 SOAP

IP Firewall
IP Firewall
MSS360, HTTP/HTTPS Security HTTPS/WSL
CDR
INRIX(SYNC) DataPower (Provider)
(Consumer) SFTP FTP
-- Transformation
-- Routing Owner Web
-- Protocol bridging (Consumer)
-- Central policy enforcement
-- X509 support
-- XML validation, XML threat protection
-- Message signing, encryption/decryption
12/3/2017
Case Studies
OWS / B2D Integration
High-level Requirement
Business interaction between Ford internal, dealer-
facing applications (OWS/LDS/) and Dealership/DMS
Example Use Case Requirements
DMS interacting with Ford internal apps
DMS invokes Ford internal function asynchronously
Ford invokes DMS function asynchronously
Guaranteed Delivery for messaging between DMS and
Ford
12/3/2017
Case Studies
OWS / B2D Integration
Solution
Exposing/Accessing capabilities via Web Services
Use DataPower as intermediary for
Security checking (AuthN, AuthA, en-/de-cryption, digital
signature, XML validation, )
Broker (X509 Certificate -- WSL Cookie; SFTP -- FTP)
Routing
Use BizTalk as intermediary for
Store/Forward
Routing
Asynchronous messaging
12/3/2017
Inbound Messaging
-- Perform AuthN
and Site-level AuthZ
with SPS (Security
Provisioning
Services)
SPS
SOAP X509 SOAP

IP Firewall
IP Firewall
Message
Store
12/3/2017
Outbound Messaging
-- Get DelivPref,
SiteURL, Cert for the
Site Code associated
with the message
SPS
SOAP X509 SOAP

IP Firewall
IP Firewall
-- WS-Addressing TO is supplied in msg

BizTalk forwards msg to DataPower Message
-- DelivPref is Push Store
BizTalk forwards msg to DataPower
-- DelivPref is Queue for DMS to pull
BizTalk stores msg for DMS to retrieve
based on its own timed polling
-- DelivPref is Notify for DMS to pull
BizTalk posts Youve got mail to DMS for
it to retrieve msg.
12/3/2017
Case Studies
SOA Design Patterns Used
Synchronous and Asynchronous Messaging
Service Broker
Intermediate Routing
Async Queuing
Policy Centralization
12/3/2017
Case Studies
BOMF (Bill of Material Foundation)
Requirement
Managing BOM information
Addressing existing BOM fragmentation issues:
Multiple masters of BOM information each with its own interface
Conceptual differences in the data model for each system
Front-end tightly coupled with back-end solution
Performance concerns with some BOM tools
Strategic direction / solution

Providing BOMF service layer to decouple top-hat and platform
Creating early BOM repository and Web Services
Establishing a foundation for future BOM repository and services
12/3/2017
Case Studies
BOMF - systems involved, integrated, or to be consolidated
Process Process Process Process Process Process

Driven Driven Driven Driven Driven Driven
BOM BOM BOM BOM BOM BOM
PDBC PDBC
PADB MPNR PADB MPNR PADB MPNR
PPL CMMS PPL CMMS PPL CMMS PPL CMMS CMMS
GPIRS AVBOM GPIRS AVBOM GPIRS
WERS PTMS WERS PTMS WERS WERS

PTMS
SBOM SBOM SBOM SBOM SBOM
iPAS iPAS iPAS iPAS
BOM Foundation BOM Foundation BOM Foundation BOM Foundation BOM Foundation
3Q
4Q
4Q
1Q
2Q
3Q
4Q
1Q
2Q
3Q
4Q
3Q
1Q
2Q
4Q
1Q
2Q
3Q
1Q
2Q
3Q
4Q
1Q
2Q
12/3/2017
Case Studies
Top Hat
user-centric applications focusing on UI, navigation, business process flow,
Platform
back-end providing underlying capabilities / solutions
Demand
/ Use
Interface
Supply
/ Solution
12/3/2017
Case Studies
Some of the Web Services (in PROD)
ProductStructurePart
ProductStructurePartUsage
ProductStructureLineOfUsage
ProductStructureLineOfPart
ProductConfigurationProductContext
Program
ProgramProductSystemResponsibility
ProductClassificationBaseConstituent
ProductClassificationCPSC
ProductClassificationCrossReference
12/3/2017
References
ITCN News: Ford IT improving application delivery and reducing complexity
http://www.itcn.ford.com/news/Pages/FordITimprovingapplicationdeliveryandreducingcomplexi
ty.aspx
Global SOA SharePoint site
https://comm.sp.ford.com/sites/soa/Pages/Default.aspx
SOA for Web Services Pattern 2012
https://www.lom.ford.com/launchomatic/download?objectId=0900cad980f06f5a&docbase=ed
msna1
Guide to Interoperability
https://www.lom.ford.com/launchomatic/download?objectId=0900cad980a92863&docbase=ed
msna1
Service Registry and Repository
https://www.sarr.ford.com/ServiceRegistry
DataPower SharePoint site
https://comm.sp.ford.com/sites/datapower/Pages/Default.aspx
BizTalk SharePoint site
https://team.sp.ford.com/sites/ESB/
12/3/2017

SOA Overview and Benefits at Ford

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SOA Overview and Benefits at Ford

Uploaded by

Copyright:

Available Formats

An Overview of SOA

SOA Center of Excellence

Ford Global SOA Program

Development 2010 2011 YTD Cum Points of interest

Potential (pre- $2,000 $3,470 $1,181 $8,228

Potential (post- $1,584 $2,712 $944 $6,531

Realized from $1,112 $1,509 $928 $4,100

SOA Team Connect Site /SOA Team tab/ Program Management 5

There are other definitions

Note: A Component is a set of related classes or modules that provide

Note: Web Services Interoperability Organization (WS-I) is an

Uniform means for offering / accessing services results in

SOA based solutions provide better support for changes

Internet DMZ Ford Intranet

With SOA / Web Services

Application Specific Interfaces Service1 Service2 Service3

Focuses on services which are building blocks for solutions

Stored Procedures contain

J2EE Consumer WSMOD

With SOA / Web Services

SOAP X509 SOAP

Internet DMZ Ford Intranet

App1 App2 App3

Service Interface Service Interfaces

Service1 Service2 Service3

SOA advocates loosely coupled architecture

SystemA SystemB SystemX

Use / supply of services are implementation, platform independent

Focuses of the next six to twelve months

Service-Oriented Architecture (SOA)

Pub/ Sub, Store/ Forward Not available. Well suited.

Schema Validation Well suited. Not recommended

Protocol mediation HTTP(S) common implementation in HTTP(S) common implementation in

Request Response(Synchronous) Well suited for service Virtualization. Not preferred.

Message Transformation Well suited. Flexible GUI. Minimize transformations.

Event Processing Not suitable. Well suited.

BizTalk ESB 18-NOV-2011 36

Reliable messaging (Store and Forward)

Message Exchange Patterns (MEP)

BizTalk ESB 18-NOV-2011 37

Service and Re-usable Asset metrics

Production Services Ratings Registered Services Category & Status

Production Service Types

MQ, HTTP, Other 52

SOA Team Connect Site /SOA Team tab/ Program Management 38

Service Governance and Cultural Change

YTD Service Opportunity Reviews Service Mediations

US FoE APA CMSA Successfully resolved 6

# of known dev projects 244 37 113 3 In progress 0

Resulting recommendations Functionality lacking 11

SOA Team Connect Site /SOA Team tab/ Program Management

Development 2009 2010 YTD Cum Points of interest

Potential (post- $1,291 $1,584 $2,712 $5,587

Realized from $551 $1,112 $1,509 $3,172

SOA Team Connect Site /SOA Team tab/ Program Management 40

SOAP X509 SOAP

Internet DMZ Ford Intranet

SOAP X509 SOAP

Internet DMZ Ford Intranet

SOAP X509 SOAP

-- WS-Addressing TO is supplied in msg

Internet DMZ Ford Intranet

Strategic direction / solution