Transcript Document

Integration Of Applications,
A Challenge Of Any Modern Company
Marilza Maia
Sr. IT Architect
[email protected]
Agenda
 SOA Reference Architecture
 BPM Suite and Technology
 Integrating information, services, processes, and policies for variability
 Customer Experiences





Large TELCO Company in Europe
Police Services SOA Solution
Large Bank in the United States
Insurance Company in the United States
Energy and Utilities in the United States
SOA Reference Architecture
Business Services, Business Rules and
Business Events
Supports enterprise business goals through business
functional services and business event patterns
Development
Services
Interaction Services
Process Services
Enables collaboration
between people, processes &
information
Orchestrate and automate
business processes
Integrated
environment
for design and
creation of
solution assets
Information Services
Manages diverse data and
content in a unified
manner
Manage and
secure
services,
applications &
resources
Enterprise Service Bus
Partner Services
Business App Services
Access Services
Connect with trading
partners
Build on a robust,
scaleable, and secure
services environment
Facilitate interactions with
existing information and
application assets
Infrastructure Services
Optimizes throughput, availability and utilization
Management
Services
Targeting an Integrated Business Integrity Management Framework
Today
?
?
Policies
Emerging
?
Policies not consistently
understood or followed
Future
Policy Integrity
Formal standards and policy
management solutions
Business
Integrity
Processes
Process Integrity
Policy
Incomplete view of
process execution
Formal standards and process
management solutions, with modularity
?
Core
Entities
Process
Services
Service Integrity
Ad hoc services
without a
Data
structured granularity
approach
Services exposing and consumed by business
processes. Granularity with enterprise
Information
Data in
Inconsistent information
multiple sources
Today information, processes,
services and policies are typically
inconsistent and incomplete
Services
Information Integrity
Master Information Management: a single
semantic definition of core entities
Emerging solutions address
consistencies and management of
policies, processes, services and core
entities independently
An integrated and automated
approach to policy, process,
services and core entity
management emerges.
The Engine of a Robust, Integrated BPM Suite
Composite Business
Applications
Pre-built Industry
Accelerators
Business
Services
Business
Content
Modeling and
Simulation
Sales
Channels
Operations
Partners
Roles
Finance
Process
Execution
BPM
Registry
Repository
Business Processes
ESB
Business Activity
Monitoring
SOA
On-premises
Outsourced
Partners
IT
Respond Quickly to Business Demands with Powerful Capabilities
Manage BPM and SOA Assets across their Lifecycle
Accelerate time to value across the BPM lifecycle
Manage IT Assets
(e.g. BPEL, WSDL)
Manage Business Assets
(e.g. Models, Roles)
IT
Leader
IT
Developer
IT
Architect
Govern and
Perform Impact
Analysis
Publish
and Deploy
Administer
Repository
Federated Search
And Publish
Design-time
Run-time
WebSphere Services Registry and Repository
Advanced Lifecycle Edition
Integrating information,
services, processes, and
policies for variability
Moving business logic away from Business
Process design into metadata and policies
Process segment with many different service permutations
and complex service mediation.
Eg: Billing service to access either Mobile Billing System, or
Fixed Line Billing system
Business Process
Services
A
a1
End :Points:
A
a2
Business Process
Services:
A
A
End Points:
a1
a2
Business Services:
B
C
Business
Service
Repository
Policies
Meta-Data
Composition
development
Business Services Dynamic Assembler
End Points:
b1
b2
b3
c1
c2
d1
d2 …
N
A
a3
B
b1
B
b2
C
c1
C
c2
Defining modularity from Business Process Modeling Notation (BPMN) categories
There are three basic types of sub-models within an end-to-end BPMN model:
1. Collaboration Processes: exchanges between 2 independent business entities.
e.g. Supplier/Partner Interactions
2. Abstract (public) processes: End to end view from a participant point of view.
Monitoring
model
e.g. Order to bill
3. Private (internal) business processes: single business owner and a main core entity
Contract & variability between the wagons- Separation of services
e.g. Customer Service
e.g. Manufacturing
Business Services link
the private processes
together
e.g. Supply Chain
e.g. Accounting
Automation
model
e.g. Billing
Example of Rules and Policies for simplifying processes and for dynamicity
Activation Service Specific Process is Plugged In at Runtime
Customer Location = [Wellington, Auckland, …]
Policy owned by the
business controls which
variation is used.
Product Type = [Multiple Play, High Definition VoD, …]
If the customer's category is residential
and the value of the customer's average
spending is more than 150 €
Then change the Elite Status to Gold
Activate
Connection
Service
ILog
Rules
The lifecycle and
implementation of each
variation is now decoupled from the main
process.
For the ActivateConnection Business Service
When
Product is Triple Play AND
Channel is Web AND
Role is Self Service OR
Customer is Residential
Then
Elite Status is Gold AND
Use the Activate Fiber To Home
Process
Business
Space Policy
Activate DSL
Activate Fiber
To Home
Activate
Wireless
(FUTURE)
Normalization of enterprise activities
Business and technical
information model
normalization
Business “city
planning” map and
business processes
normalization
SID, ACORD,
CIM, IFW
APQC, SCOR,
eTOM, IFW
Application “city
planning”
implementation map
normalization including
interfaces and services
CIM, IEC 61968,
OAGIS, IFW, TAM
(TMF).
Technical infrastructure
normalization
OSGi, WS-I, SOA
reference architecture
Large TELCO Company
in Europe
eTOM – Processes also are at Level 3 Order Handling
OPERATIONS
Operations
Support & Readiness
1.1
Fulfillment
1.2
CRM
Support & Readiness
1.3
1.6
Selling
Marketing
Fulfillment
Response
1.7
Problem
Handling
1.5
Order
Handling
1.9
SERVICE
2..2
2.3
Service Mgmt. & Operations
Service Configuration
R Track & Manage
Determine Customer
Authorize Credit
Support & Readiness
& Activation e Customer Order
Order Feasibility
c Handling
…
RESOURCE
3.1
SUPPLIER/
PARTNER
Issue Customer
Orders
4.1
Report Customer
Order Handling
3.2
Resource Mgmt. & Operations
Support & Readiness
S/PRM
Support & Readiness
S/P Requisition Management
4.6
Billing & Collections
Management
2.4
2.5
Service & Specific
Instance Rating
Close Customer Order
Resource
Trouble Mgt.
3.5
4.2
Customer
QoS / SLA
Management
Service
Service
Problem
Quality
Complete Customer
Order
Management
Management
3.3
Resource Provisioning
1.8
Retention & Loyalty
Order Handling
2.1
Billing
Customer Interface Management
1.4
CUSTOMER
Assurance
4.3
S/P
Problem
Reporting&
Mgt.
3.4
Resource
Perform. Mgt.
Resource Data Collection & Processing
4.4
S/P
Perform. Mgt.
Supplier / Partner Interface Management
4.5
S/P Settlements & Billing Mgt.
Catalog Driven Business Process
eTOM Processes
SID Catalog
Decompose each products
in services and loop on
services
Service Characteristic
Specification &
Characteristic Value in
Catalog contain the
configuration values to
use
Using SID Product Customer & Resource Facing Service structure to create
Catalog driven business processes
Commercial View
Product
Multiple Play
Pasarella (multiple play for family)
TV
Voice
Broadband
HDTV
Functional
ADSL Access
View
Service
ATM
Resource
ATM Circuit
GPON
Music
Monitoring
STB Sale
STB Rental
TV Packages
Wireless
Ethernet
IPTV (VoD)
VoIP Account(s)
VoIP Config
VOD Channels VoIP URI
Set Top Internet access
DTH
VoIP Buddy List
Set Top Box VoIP
Set Top Box TV
Information Variability Pattern from Telco SID Standard
Name of ASE
Definition
Entity
Entities represent classes of objects that play a business function. Entities can be either managed or unmanaged.
Specification
Specifications are used to define the invariant characteristics (attributes, methods, constraints, and relationships) of an
object. Specifications exist for ManagedEntities, Products, Resources, Services, Locations, Roles, Policies, and Processes.
Role (can be defined
for human and nonhuman)
Roles characterize the function that a particular object plays. The characterization may be to specify attributes, methods,
constraints, and/or relationships that the entity has.
Location
Locations are used to identify a position, address, geographic area, or particular structure.
Identity
Identities are used to enable an object to be recognized. Some objects can be recognized by one of several identities.
Policy
A Policy is a set of rules that is used to manage and control the changing or maintaining of the state of one or more objects.
This ASE contains objects that can represent policies as well as define how they are used by management applications.
Interaction
An Interaction is an arrangement, contract, communication or joint activity between one or more participants (which can be
Parties or Entities). An Interaction may refer to a Product, Service, Resource, and involve particular Locations.
Party
A Party is an abstract concept that represents groups of People and/or Organizations.
ManagementDomain
A ManagementDomain represents a special grouping of ManagedEntities that has two important properties. First, it is used
to partition managed objects into a meaningful logical grouping. Second, it defines a common administrative domain that is
used to administer the managed objects that it contains.
Process
A Process is a systematic sequence of actions used to achieve a goal.
Characteristic
A Characteristic represents the essential attributes, methods, constraints, and/or relationships that typify the object that it
applies to.
Capacity
The Capacity of an object represents the total measured amount that the object can contain.
Use case for a Telco Company in Europe
Product Catalog
CRM
Custom
Order Repository
Process Integration
Order Management
WPS/WBSF/TOCP
Transformation
Mediations
Service
Provisioning
Resource
Provisioning
Enterprise Service Bus
Order Management Performance Scenario
Police Services
SOA Solution
Enterprise Service Bus Architecture Vision
Browsers
PDA
Pervasive
“Mobile”
Portal Server
SAP
Business Processes
Modeled:
Process Server
Oracle Apps
ICDMS
New Composite
Applications
Enterprise Service Bus
External
Connections
Security Agencies
Existing
Applications & Data
CICS/IMS
Solaris / Sun
Partners and Vendors
Other Apps
Information
Aggregation
Other Transaction Mgmt
Document Mgmt
Windows / Intel
DBMS & other
information sources
Linux
Service Oriented Interface - Pilot Solution
CICS/IMS
Web
Services
Information
Services
J2EE
App Server
(WAS,SUN)
Web
Services
.Net
App Server
Web
Services
Web
Services
Service
Repository/
Registry
Enterprise Service Bus
Common Data Model
Code
Tables
Auditing
Logging
Data Models
(XML Schema)
Service Contracts
(WSDL & WS-Policy)
Large Bank
in United States
Retail Banking - Account Open System Overview
Interact
eComm
(Third-Party User Interface)
Account
Opening
1a
5
Apps
Sales
7
3a
6
3c
WebSphere
Business Activity
Dashboard
1b
3b
2
Case
Services
Services
2
Booking and
Features setup
IMS
Process Business
events are
captured
1a
4
7
3a
Account Opening
Process
Third=Party
Operational Database
Events
Account Opening
KPI’s
Third-Party Apps
Core
Services
WebSphere Process Server
WebSphere Business
Activity Monitor
Common Business
Events
User Data
6
5
Process Business Objects
are persisted in the WPS
Datastore
WPS
Database
Account Opening
Process State
WBA
Database
Account Opening
KPI’s
Account Open Component Model
Insurance Company
in United States
BPM Solution for Insurance Claims Payment
Insurance
App1
Insurance
App2
BPEL
Claims
User
Interface
Adapter
Claims
Business Process
Choreographer
ACORD
MSG
Insurance
App3
Insurance
App4
ACORD
MSG
OFAC
Compliance
Energy & Utilities
in United States
SmartGrid - Meter Operations Integration
Meter
Data
System
WS
Internet
App
Metering
Operations
JMS
WS
Adapters Layer
Smart Grid Meter Integration
(Canonical CIM Based Message Format )
Integration
Persistence
Store
Adapters Layer
WS
Meter System1
WS
JMS
Meter System2
Meter Reading Request Business Object Model
Meter Reading Response Business Object Model
Meter Reading Request and
Response Messages
Meter Reading Request
Meter Reading Response
Conclusion
 A flexible approach needs to look at information, processes and services
with variability. A policy vocabulary derives from the business information
model
 Variability and flexibility are not only technical but more important are
business related and include semantic aspects
 Time to value comes from business and technical accelerators that we
have constructed from standards and experience
Questions?