Transcript Foundations of Electronic Commerce and Collaborations

Enterprise
Application Integration
and
Process Modelling
Erik Perjons
DSV, KTH/SU
Why focusing on business
processes?
•
re-engineering the business processes to
make them more effective/efficient
•
easy to understand for non-technical people
•
discover and adopt to changed customer
demands
•
automate the activities in business
processes
Stove pipe problem
Production
$
Purchase
$
Market
Management
Customer
service
Shipment
$
Manufacturing
Marketing
Purchasing
Board of Directors
Receiving
supplier goods
Packaging
Customer service
Quality Assurance
Warehouse
Recieve orders
Deliver/Ship
Business processes cross
departments
Production
$
Purchase
$
Management
Market
Shipment
Customer
service
Packaging
$
Manufacturing
Board of Directors
Marketing
Purchasing
Customer service
Receiving
supplier goods
Quality Assurance
Warehouse
Recieve orders
Deliver/Ship
Solution: Integrated IT systems
Production
$
Purchase
$
Management
Market
Shipment
Customer
service
Packaging
$
Manufacturing
Board of Directors
Marketing
Purchasing
Customer service
Receiving
supplier goods
Quality Assurance
Warehouse
Recieve orders
Deliver/Ship
Why problem integrating IT
systems?
• Different platforms, programming languages,
and formats
• No interfaces
• Legacy systems with no documentation
• Different semantics in the systems (different
meanings of e.g. ”customer”, ”region”,
”product”)
• Need of a routing mechanism
Problem: Constantly changing
business processes
Production
$
Purchase
$
Management
Market
$
Customer
service
Packaging
Manufacturing
Board of Directors
Marketing
Purchasing
Receiving
supplier goods
Customer service
Quality Assurance
Recieve orders
Planning
production
Warehouse
Deliver/Ship
Integration solutions
• ERP and Enterprise systems
- replace existing IT systems with
a new one
• EAI middleware
- integrate existing IT systems
• Electronic collaboration solutions (B2B solutions)
- integrate the suppliers’ and customers’ systems
• Data warehousing
- extract some data from existing IT systems
and load it into a new system for decision
support
ERP systems/Enterprise systems
Production
$
Purchase
$
Management
Market
$
Shipment
Customer
service
Packaging
Manufacturing
Board of Directors
Marketing
Purchasing
Receiving
supplier goods
Customer service
Quality Assurance
Recieve orders
Planning
production
Deliver/Ship
Integration solutions
• ERP and Enterprise systems
- replace existing IT systems with a new one
• EAI middleware
- integrate existing IT systems (RPC,
CORBA, XML, Message Broker, BPMS)
• Electronic collaboration solutions (B2B solutions)
- integrate the suppliers’ and customers’ systems
• Data warehousing
- extract some data from existing IT systems
and load it into a new system for decision
support
EAI: Point-to-Point solutions
Production
$
Purchase
$
Management
Market
$
Shipment
Customer
service
Packaging
Manufacturing
Board of Directors
Marketing
Purchasing
Receiving
supplier goods
Customer service
Quality Assurance
Recieve orders
Planning
production
Warehouse
Deliver/Ship
EAI: Many-to-Many solutions
Production
$
Purchase
$
Management
Market
$
Customer
service
Packaging
Manufacturing
Board of Directors
Marketing
Purchasing
Receiving
supplier goods
Customer service
Quality Assurance
Recieve orders
Planning
production
Warehouse
Deliver/Ship
Message Brokers and BPMS
Application A
Application A
Application A
Application B
Application B
Application B
Application C
Message Broker
BPMS
Application C
D
Application A
Point-to-point
Application D
Many-to-many
- Message Brokers
Application C
Person A
Many-to-many
- BPMS
Business Process Management
Systems (BPMS)
also called Process Brokers, Process Automation
Systems, Workflow Management Systems
- directly executable business models
- support process design (modelling),
execution, analysis, simulation and
optimisation of business
processes
- automate the business processes, or the
information flow
Categorisation of
Business Process Modelling Languages
• Static-oriented languages
-visualise the input and output from activities, but not the
logical order/time, e.g. IDEF0, data flow diagram
• Activity-oriented languages
-decribes which activities follows and precede another in a
process, e.g EPC, UML activity diagram
• State-oriented languages
-describes which states follow and precede another in a
process, e.g UML state diagram
• Communication oriented languages
- focus on the interaction between prople and systems, and
between systems, e.g UML sequence diagram, BML, SDL
Basic process language concepts
Four basic process language concepts, which have the following
intuitive meaning:
A time point is an instant in time, not further
decomposible
An event is an noteworthy occurence
A state shows the condition of a process and can be
represented in several way, e.g. as a set of attribute
values
A activity is something that is performed in a process
Different meaning of basic terms
Two examples (there are more):
State
State
State
State
State
State
Activity
Activity
Time points
Time points
Meta models and reference meta model
Event
Meta Model
Level
-reference
meta model
Meta Model
Level
-modelling
techniques
consists of
consists of
Precedes
Transformation
State
Succeeds
Precedes/
succeeds
Precedes
Precedes
Function
Event
Activity
State
Succeeds
Succeeds
Requirement
occured
Model Level
Capture
requirement
Capture
requirement
Requirement
captured
Requirement
[captured]
Check material
on stock
Requirements
[checked]
X
Material is
on stock
Check material
on stock
[Rosemann&Green, 2002]
Material is
not on stock
EPC
UML Activity Diagram
Data flow diagram
Bokinfo
Anställd
Beställnings
mottagande
Katalogkontroll
Budgetinfo
Budget
kontroll
Lev.info
Beställnings
rutin
Bokhandel
UML Activity Diagram
[no coffee]
Find
Beverage
[found coffee]
Put Coffee
in Filter
Add Water
to Reservoir
Get
Cups
[no cola]
[found cola]
Get Can
of Cola
Put Filter
in Machine
Turn on
machine
Brew
Coffee
Pour
Coffee
Drink
Beverage
[Fowler&Scott, 1997]
UML State Diagram
[not all items
checked]
Checking
[all items
checked&all
items available]
do/check item
[all items
checked&some
items not in stock]
Waiting
Dispatching
do/initiate
delivery
[all items
available]
Delivered
[Fowler&Scott, 1997]
Business Modelling Language (BML)
Customer
Order
Order
update
Timer
T1
Wait for
Event 1
Update
answer
Timer
T1
App A
Order
answer=
OK
Order
answer=
Not OK
End
App A
does not
answer
Operator
End
Business Modelling Language (BML)
Customer
Order
Order
update
Timer
T1
Wait for
Event 1
Update
answer
Timer
T1
App A
Order
answer=
OK
Order
answer=
Not OK
End
App A
does not
answer
Operator
End
Business Modelling Language (BML)
Customer
Order BIA
App A
Operator
Process Broker project
The purpose of the project is to investige
BPMS (Process Brokers), in particular:
• business process modelling languages
• method for application and process
integration
Process Broker project - Telecom case
Dafa
Beställare
Postadressfråga
¤Beställning
Postadressvar
¤Ändra_beställning
¤Fyll_på_epeng_begäran
¤Info
¤Kunddatasvar
¤Felsöksvar
¤Felinfo
(
Automatiskt
Kundmöte
¤Nr-begäran1-svar
¤Nr-begäran2-svar
¤Prebeställning_
info
¤Beställ¤Kund- ning ( 303)
data- ¤Ändra_beställ¤Beställning
fråga ning (340)
¤Ändra_beställ(505) ¤Ta_bort_inlagd
ning (340)
_data (331)
¤Ta_bort_inlagd
_data (331)
¤Nr-begäran1
(unik/nr-förslag)
¤Nr-begäran2
(unik/förslag)
¤Avbryt
¤Boka_nr
¤Släpp_nr
¤Ta_bort_nr
¤Felinfo
(
¤Nr-begäran1-svar
(unik/nr-förslag)
¤Nr-begäran1 ¤Nr-begäran2-svar
¤Nr-begäran2 unik/nr-förslag)
¤Boka_nr_svar
¤Avbryt
¤Ta_bort_nr_svar
¤Släpp_nr_OK
Mobilanvändare
Släpp_nr
¤Ta-bort_
nr-bokning
Boka_nr
Nr-sök
¤Batchbeställning_
SIM-kort
Kundstatus
Kundstatus
Kundstatus
Kortdatabas
¤SIM-kort_
stor_
leverans
Mobiltelefonförsäljare
¤Fordran
Felsök
Felsök
Felsök
¤Epengperiodbetalning
(604)
¤Debitera_
tjänst
Pre-Ändra_
beställ
¤Kortkontrollsvar
¤Kortkontroll
Kortdbhantering
¤Ta_bort_inlagd_data (351)
¤Info_tjänster (371, 372,373,
374, 375)
¤Ny_kunddata (407, 413, 415,
420, 425, 437, 439)
¤Betalasättfråga (403, 430)
¤Giltigt-kort_fråga
¤Felinfo
(605) ¤Felinfo
¤Skicka_nya_
OCR-blanketter
(419, 436)
¤Epengperiodbetalning_
OK ( 606) ¤Pris¤Debitera_ listasvar (602)
tjänst_svar
Fordringskonto
¤Debiteringsunderlag
Beräkna_
periodsumma
PERIODISK_
BETALNING
Efterdebitering
Dra_från_IN-konto
data_OK (353)
¤Fyll_på_epeng
_begäran (402)
Adresskontroll
¤Transinfo
¤Fyll_på_epeng_begäran (401)
¤Epeng_fylls_på_OK (438)
Betalning_via_konto
¤Betalasättsvar(404, 431)
¤Giltigt_kort-svar
¤Kortkontroll-svar
Mobilanvändare
(309, 321,
329, 332,
335, 338,
341, 352)
¤Prislistafråga (601)
Fyll_på_IN_konto
Betalning_via_giro
Välj_betalningssätt
Statistik
¤Transinfo
Euroline_betalning
BETALA
Godkända
transaktioner
Spontanbetalning_giro
Beställ OCR-blankett
¤Skicka_nya_
OCR-blanketter
Statistik¤Felinfo
¤Starta_
¤Beställning_initierad
periodisk_
¤Ändra_beställning_initierad
betalning(501)
¤Ta_bort_inlagd_
¤Skicka_nya_OCRblanketter
Tryckeri
BPIoperatör
Pris-db
¤Transinfo
¤Beställning_
initierad
¤SIM-korts_
¤Ändra_
info_med_
beställning_ adress
initierad
PRE-BESTÄLLNING
¤SIMkortsinfo
¤SIMkortsinfo
Beställning_
KUNDINFO
KUNDINFO kundinfo
KUNDINFO
Pre-Ny_beställ
¤SIM-kort_
beställning_OK
¤Beställning (304)
¤Ändra_beställ- ¤Epeng_
¤Kunddatafylls_
ning (337)
fråga
¤Ta_bort-inlagd_ på ( 435)
(507)
data(328)
¤Beställning
¤Beställ_OK(313)
ning_
¤Ändra_beställOK (336)
ning_OK (339)
¤Beställning_OK( 312)
¤Ta_bort_
¤Ta_bort-in¤Ändra_beställning_OK (342)
inlagd_data_ lagd_data_OK
¤Ta_bort_inlagd_data_OK( 333)
OK
(330)
(510)
¤Beställning_
initierad
¤Boka_nr
¤Ändra_
¤Ta-bort_nr beställning_
¤Boka_nr_svar initierad
¤Ta_bort_nr_svar
¤SIM-kort_
beställning
¤Beställning (334)
¤Ta_bort_
inlagd_data
BESTÄLLNING
Ta_bort_nr
PCR
¤Hjälp_
kund
(412, 424)
Ändra_beställning
¤Beställ- Ny_beställning
ning_OK
¤Kunddata
AUC_borttag
HLR_borttag
¤Kunddata¤Ändra_befråga (115)
svar(509)
ställning_OK
¤Felsök (116)
¤SaldoPPS_borttag
Uppdatera_Open_Voice
¤Kund¤Ta_bort_
svar (503)
datainlagd_data_
Uppdatera_PPS
Kundstatus_borttag
¤Kunddatasvar (508)
OK
Uppdatera_AUC
Uppdatera_HLR
svar
NR-HANTERING
¤SIM-kort_
leverans
Prepay system
¤Kunddatafråga(506)
¤Saldofråga (502)
AUC
Betala_
hjälp
¤Hjälp_
kund_
betala
Mobilanvändare
HomeLocation
Registry
MobilSvar
(HLR)
¤Kunddatasvar (504)
¤Info (511,
513, 514)
Nr-databas
¤Felinfo
(512)
¤Nyttjar
mobiltelefon
¤Beställinfo
(310,320,323, 360)
¤Kunddatafråga
¤Felsök
Kundinfosökare
BPIoperatör
Mobile
Switch
Center
¤PG_fylls_på
¤Epeng_fylls_på
¤BG_fylls_på
Postgiro
¤Kortkontroll-fråga
Euroline
Bankgiro
¤Rekvirera_
epeng (417)
¤Batch_capture
¤Fyll_på_epeng_
svar(409)
Mobilanvändare
SMS
¤Fyll_på_epeng_fråga
(408, 410)
¤Fyll_på_giropengpåpekande (421, 423)
¤Betalakvittens (440)
¤Info (411)
SMCC
Vita Nova project
The purpose of the project is to investige
the potential of BPMS in Health and Medical
Services
DSV’s assignment is to develop a framework
for evaluating business processes models,
BPMS and methods for integrating business
processes
Loosely-Structured Business Processes
project
The purpose of the project is to investige
BPMS for loosely-structured business
processes
• focused on goal and state modelling
• try to define patterns for such business
processes
• case studies: decision-making and lobbying
ebXML and EC4 project
- ebXML is a global standard developed by
UN/CEFACT and OASIS
- EC4 stands for Electronic Commerce and
Collaboration Center
- aims at disseminate knowledge about electronic
commerce and collaboration among researchers,
students and SME
Integration solutions
• ERP and Enterprise systems
- replace existing IT systems with a new one
• EAI middleware
- integrate existing IT systems
• Electronic collaboration solutions (B2B solutions)
- integrate the suppliers’ and
customers’ systems
• Data warehousing
- extract some data from existing IT systems
and load it into a new system for decision
support
B2B - Electronic Collaboration
Integration
Production
Management
$
Purchase
$
Market
Shipment
Customer
service
$
Manufacturing
Marketing
Board of Directors
Purchasing
Packaging
Customer service
Receiving
supplier goods
Suppliers
Quality Assurance
Warehouse
Customers
Recieve orders
Deliver/Ship
Business Processes spanning
several organisations
Company 1
P1.3
P1.1
P1.2
P1.4
Company 3
Company 2
ebXML Electronic Collaboration
Integration Levels
Business Area
Business Domain View
Process Area (supply-chain)
Business Requirements View
Business Process
REA
Business Collaboration
Business Transaction View
Business Transaction
Business Service View
Business Service
MessageServiceHandler
SOAP (WebServices)
Implementation Function View
HTTP SMTP MIME
TCP/ IP
...
...
SOA
Web services and CORBA are different
implementations of Service Oriented
Architecture (SOA)
Register and Store
Service Broker
Find, request and
bind service
Find
Publish
Service Requestor
Publish and provide
service
Service Provider
Request & Bind
Integration solutions
• ERP and Enterprise systems
- replace existing IT systems with a new one
• EAI middleware
- integrate existing IT systems
• Electronic collaboration solutions (B2B solutions)
- integrate the suppliers’ and customers’ systems
• Data warehousing
- extract some data from existing IT systems
and load it into a new system for decision
support
Data warehousing architecture
The back room
The front room
BI/Analysis/OLAP
Data warehouse
External sources
Extract
Transform
Load
(ETL)
Operational DBs/
OLTPs/TPSs
Serve
Data marts
Productt
Time1
Value1
Value11
Product2
Time2
Value2
Value21
Product3
Time3
Value3
Value31
Product4
Time4
Value4
Value41
Query/Reporting
Data mining
Falö aöldf
flaöd aklöd
falö alksdf
Data sources
Legacy systems
OLTP/TP systems
Back end tools
Data staging area
”The data warehouse”
OLAP servers
Front end tools
End user applications
Data warehousing definition
”Data warehousing is a collection
of decision support
technologies, aimed at enabling
the knowledge worker
(executive, manager, analyst) to
make better and faster
decisions.”
[Chaundhuri&Dayal, 1997]