Model Based Planningin
Service Oriented Architecture(SOA)
Dave McCoyAssociate Technical Fellow
The Boeing Company
2
Definitions
Service Oriented ArchitectureService Oriented Architecture (SOA) is
an architectural concept where software functionalities are exposed as services.
ServiceServiceRequestorRequestor
ServiceServiceProviderProvider
ServiceRegistry
Network Existing SystemsOrServices
Service
A Service is a software component designed to be invoked by name across applications or across organizations via a well-defined interface
ServiceServiceInterfaceInterface
Service
ServiceServiceImplementationImplementation
Service characteristics: Network-enabled Self-contained Client-agnostic
3
SOA Attributes
Benefits
Characteristics
Smaller software components, and greater reuse of standard software through plug and play approach
Heavily dependent of use of industry standards and a robust network
Business flexibility provided by increased granularity of processes enabled through services
Ability to quickly create business processes and composite applications to respond to changes in the marketplace
Decrease development and deployment cycle times through the use of pre-built, reusable services building blocks
4
• 1970 - 1980’s● Monolithic applications● Mainframe ~ dumb terminal● Little integration, Applications in functional domains
• 1990’s● Distributed applications● Client ~ server● Integration within functions domains / application suites ~
proprietary• Early 2000’s
● Loosely Coupled Applications● Web enabled● Integration using proprietary middleware and some web services
• Late 2000’s● Composite applications● Rich web clients / portals● Standards based integration and orchestration
What is Really Different
By 2008, Gartner predicts that SOA will be a prevailing software-engineering practice, ending the 40-year domination of monolithic software architecture
RigidSilo’s
AgileCollaboration
5
Industry Trends
Gartner● “By 2006, more than 60 percent of enterprises will consider
SOA a guiding principle in designing their new mission-critical business applications and business processes (0.7 probability)”.
● “By 2006, more than 75 percent of midsize and large enterprises will have deployed SOA-enabled development tools and middleware (0.8 probability)”
● “Services-oriented development will dramatically increase in near future.”
6
SOA Maturity ~ Gartner
SOA
Business EventManagement
EnterpriseService Bus
7
IT Architecture Overview
BusinessIntelligenceServices
ProcessOrchestration
ServiceRegistry
B2BInteractions
CollaborationTools
Portal Service
Applications& Data
Application functions are built as components (or "services") that are loosely-coupled andwell-defined to support interoperability, and to improve flexibility and re-use
IBM’s ESB Graphic
8
1970’s● Paper planning● Word of mouth
1980’s● Electronic textual instructions● Network
1990’s ● More computer based textual instructions● 2D graphical additions● Internet
2000’s● 3D graphic additions● Network bandwidth increases● Web based textual/graphical instructions● Model based work instructions
Evolution of Aerospace Assembly Planning
By 2010, …..
Text based
INFORMATIONCONTENT
9PDM
2D WorkInstructions
3D WorkInstructions
ManufacturingPlanning
ProcessOrchestration
Web ServicesWeb Services
Assembly Planning in SOA
Automation
Internet
Suppliers
10
Web Based 3D Viewer Integrated
XVL – eXtensible Virtual world description Language
11
XVL
• Develops standards-based XVL® 3D format– Provides 1/50-1/200 compression of 3D images
• order of magnitude better than currently available
– XML-based format fuses visual and non-visual data – Works with major CAD/CAM systems – Highly accurate
• Leverages 3D data across the enterprise by XVL®– Speeds development & design cycles – Allows departments and partners collaborate – Enables automation and reduces costs for improved Manufacturing,
Customer Service, Marketing, etc.
12
Web Based 3D Viewer Integrated
http://www.lattice3d.com/3ddemo/SW/SW.html
13
Web Based 3D Viewer Integrated
http://www.lattice3d.com/3ddemo/AssemblyInstructions/index.xml#
14
Major Challenges
• Maturity of SOA• Process Orchestration• Vendor Support• Interoperability Standards
– S95, OASIS, BPEL
This Is Where We Need To Work Together
15
Process Orchestration
Application Process Logic
Functions
Today
Could support different business
model
Services
Process Execution/Engine
Future
Application / NewProcess
16
Future
• Agile systems that adapt quickly to changing markets and process requirements
• Incorporation of new technologies:– Web Services
• XML, HTTP, SOAP
• Service Oriented Architecture• Model Driven Enterprise• Process Orchestration along Supply Chain• IT Skills to Support New Environment
The Future Has Never Been More Exciting And Challenging
Thank You