Motorola SOA

1
Motorola SOA

• Toby Redshaw
• Corporate VP - IT Strategy, Architecture,
  Emerging Tech and eBusiness

2
SOA

• So what ? Who cares ?
• What happens if you are 25 less efficient in IT
  than your direct competitor ?
• What happens if you are 25 less efficient in
  customer acquisition and retention or supply
  chain ?

3
SOA What Well Cover

• We will cover a lot you will have answers but
  you will have even more questions.
• What the heck is it and what does that mean and
  why you should invest
• Lessons learned
• The New Big Picture
• The New New Big Picture BAM !
• SOA and BAM status
• SOA Infrastructure Components why they are
  important
• Some examples
• Buying / Consuming Software why that changes
• Important to note we are still in the early days
• This is a small slice of Motorolas IT world
  today

4
Why Motorola is Investing in SOA

• It is faster, better, cheaper because of
  standards-based reusable components
• Reuse drives down development costs exponentially
  over time
• Standards-based solutions (XML Web Services)
  across the layers, not just integration
• It uses a new way to develop prototypes using
  Business Process Mapping rather than the old spec
  approach to designing and prototyping
• Rapid application development with composite
  application tools
• Leverages existing solutions - does not replace
  them
• Gartner estimates that it is 63 more efficient
  will be mainstream by 2005

5
SOA Pilots Lessons Learned

• The Good Business / IT Alignment Re-use
• For IT teams development using composite
  application tools allowed rapid delivery of
  projects
• For business teams projects have been built
  top-down from existing processes, not from overly
  complex tech spec docs
• For both teams projects delivered by IT were
  exactly what the business teams asked for, the
  first time
• Components built had re-use potential across the
  project, business group and enterprise

6
SOA Pilots Lessons Learned

• The Bad Standards, Security, Performance,
  Visibility
• For the first few years, immature and incomplete
  standards slowed adoption
• Security concerns- loosely coupled architecture
  can introduce new security challenges
• Performance concerns caused by loosely coupling
  software components and bandwidth-intensive XML
• Without a web services directory (UDDI), any
  reusable components built had no visibility
  outside of the projects

7
SOA Pilots Lessons Learned

• The Ugly The most pressing need to build an SOA
  infrastructure was Web Services Mgmt Security
• Performance and availability monitoring
• Auditing, logging, and metering of transaction
  and performance data
• Security of web services and transactions
• Availability and Fault Tolerance of Web Services
• Intelligent Routing of Web Services traffic
• Interoperability between various enterprise
  platforms
• Provisioning, Subscriptions, Versioning and
  Services life-cycle operations

8
SOA Pilots Lessons Learned

• The Ugly The most pressing need to build an
  SOA infrastructure was Web Services Mgmt
  Security
• Start soon long journey
• Start soon technologically not complex on the
  surface but complicated to execute
• This is a big behavior change serious change
  management needed
• Use an intervention change model
• Invest in communications / training
• Make process work and contextual understanding
  more important
• Understand the tipping points re BPM

9
SOA The New Big Picture
10
SOA BAM The New New Big Picture
11
SOA BAM Current Status

• SOA
• Over 180 services utilizing SOA framework with
  new project opportunities identified each week
• Refining SOA Architecture with maturing
  orchestration, nomenclature and governance
  guidelines
• Creating an ROI model
• Created SOA adoption strategy, guidelines, and
  best practices

12
SOA BAM Current Status

• BAM
• Over 175 BAM monitors deployed spanning
• Siebel to Oracle
• Webchannel to Siebel
• Siebel to Oracle EAI integration
• Averaging over 50 rules per BAM project
• Two BAM projects near completion with multiple
  slated for later this year

13
SOA Infrastructure Components

• UDDI Metadata Repository
• Web Service Management (WSM)
• Web Services Security (WSS)
• Web Services Governance

14
Why is UDDI Important?

• Cornerstone of Service Oriented Architecture
• Drives down costs of new development efforts
• Drives web service adoption and increase
  developer productivity by allowing developers to
  search and reuse services
• Enables reduction in development time
• Provides developers with information on how to
  integrate with business processes
• Drives and enforces standards for organization
  and categorization of service assets

15
Why is Web Services Mgmt. Important?

• Automatic provisioning of new services upon being
  published
• Template applications security and management
  policies and service level agreements based on
  the services category, business entity, etc.
• Finer grained authentication and authorization
  policies than available in UDDI alone
• all transparent from the developer or consumer
  of the service

16
Why is Web Services Security Important?

• Web services require message level security.
• Web services increase points of attack within a
  service oriented architecture
• Service to service authorization and
  authentication required
• Need for Identity management to secure complex
  web service applications
• Traditional firewalls cannot detect malicious
  XML coming through port 80 or 443

17
SOA Examples Business Services

• UDP Warrant Service
• Determines customer warranty in real-time to
  determine possible charges for repair
• UDP Data Services
• Multiple Services from all regions utilizing UDP
  data real-time
• Certificate Download service
• Provisions users for downloads with their phone
  with the appropriate security certificate
• WLAN Services
• Base stations deployed in the field can auto
  register and download security certificate

18
SOA Examples Utility Services

• Directory Authentication
• Provides single service to authenticate users
  against LDAP directory
• Email and SMS Notifications
• Provides multiple methods to send email and SMS
  notifications through web applications and mobile
  clients
• Credit Card Validation (CyberSource)
• Provides real-time credit card validation for
  online orders.

19
SOA Examples Operational Solutions(construction
time)

Displays up-to-date Motorola Legal Entity data,
relevant country location information, and
display entity financial information and reports
within our portal environment by retrieving data
from multiple, disparate systems of record.
20
The role of Motorola IT

• What we were
• Support Infrastructure
• Little perceived business value
• Mountains of spaghetti
• Noahs Ark approach to software
• What we strive to be (AND not OR)
• Reduce costs
• Promote Re-use
• Reduce system complexity
• Provide increased business value
• Accelerate the speed of business
• Expand the world of whats possible
• Enable Seamless mobility

21
Consuming Software?

• Your vendors architectures
• Software as a service
• Real platform thinking
• Rearden Commerce
• Standards are still evolving but we have critical
  mass
• Small Agile kills Big Slow
• Big Agile is just scary

22
Conclusion

• If you have not started you are in reverse
• This is competitively important
• Conceptually simple but BIG change
• Evolving space that is learning intensive
• Build the infrastructure avoid meta spaghetti
• Change the way you buy and consume software
• Get expert help
• Find partners / phone a friend
• (Rearden, Amberpoint, Reuters)