3. Classic And New Business Metrics
Classic Business Metric Enabled By
Cost cutting
Automation
Removing geographic constraints
Process reengineering
Compliance
Policy enforcement
Reporting
Agility
Model-driven design
Lightweight development methods
Rules integration family
New Business Metric Enabled By
Customer experience Mobile/social/cloud
Event-driven processes
Revenue generation Mobile/social/cloud
Gamification
Business innovation Mobile/social/cloud
Big data
Internet of things
4. SOA and BPM Business Objectives
SOA BPM
Accelerate time-to-market and/or reduce
cost of IT as an expense of doing business
Must integrate business processes to meet
some corporate mandate (often driven by
M&A or regulatory compliance)
Reduce errors and operational costs by
automating manually-driven business
processes
Accelerate application development/
deployment cycles by reusing existing IT assets
to assemble composite applications
Execute employee/customer self-service
initiatives
Reduce cost/time of hand coding and
maintaining point-to-point application
interfaces
Integration with business partners, supply
chain
Mandate/need to increase
production/output, but maintain costs
Eliminate costly, low value-add process
steps
Greater visibility into operations (helps
with compliance, and process improvement)
Ensure compliance, and make audits easier
Reduce errors and operational costs by
standardizing business processes with
automation
Enhance customer service and retention
Employee self-service initiatives
More efficient financial reporting
5. BPM+SOA Business Drivers
Operational excellence
Agility of the organization - More control to the business operation managers : Forecast, Measure
performance, React to turbulences
Build the “on demand” organization vs “Everything is static”
Efficiency of the organization
Reduce cost of global workforce
Accelerate application development/deployment cycles by reusing existing IT assets to assemble
composite applications
Maximize utilization of resources (People)
Enhance customer experience
The right work done by the right resource in the customer context contributes to better serving customer
request
Key to managing “the three V’s”
Increasing Volume, Velocity and Variety of data, events, processes, competitors, markets, etc
7. Generic Business Use case : A high-level view of
how BPM and SOA fit together.
SOA and BPM together : Generic Business Use case
8. SOA and BPM Together : Business Use case
SOA & BPM combine to have composite service -
9. Fusion Architecture
SOA Composite Layer
CRM ERP Legacy External
Partner
Data
Assets
Busine
ss
Rules
BPM Orchestration Layer
Monito
ring
Error
Handli
ng
Services – Work Manager
Process Automation Modeler
11. SCA - Reference Architecture
» Implementation Type : Business Logic
» Service : Transports
» Reference : Partners
Service Component Architecture (SCA) -
12. SOA Design Pattern
» Mediation
» Orchestration
» Composition : Service composition for complex multi-layer service
networks (SCA)
Model – Driven SOA Design Pattern
17. Service development with AMX
» Equates to an application
» Configuration of Services
» Contains services, components, references & wires to interconnect them
Connecting Composite elements -
Composite
23. Bottom Line
• Although many user organizations have separate service-oriented
architecture and business process management initiatives under way,
both are more successful and the benefits are compounded when they
are united.
• To get the best business value out of SOA and BPM, the two initiatives
should collaborate at multiple levels, coordinate and share key
resources. This is the most effective way to drive business priorities
through the IT infrastructure, and it is a powerful method for aligning
business with IT.
• Bottom line ROI –
» REDUCING COSTS
» INCREASING COMPETITIVE ADVANTAGE
Automational – improving process efficiency, usually through automating processes Geographical – looking at different locations, including things like outsourcing • parts of your process Disintermediating – cutting out the middle man, through things like customer • selfservice
A composite contains components, services, references, the wires that interconnect them, and properties that are used to configure the components. Composites can be nested (contained by other composites). A root composite equates to an SCA application.
Model composite services Separates Business logic (Components) and Transports(Bindings) Wires tie consumers and providers. Components utilizeShared Resources and PropertiesShared Resources injected to components at runtime.
manual labor, which saves time and can also reduce error rates reducing time to market