integrating business processes - aalto ea lesson 4 part 1_2.pdf · 3.10: eai, (enterprise ......

SoberITSoftware Business and Engineering Institute

HELSINKI UNIVERSITY OF TECHNOLOGY

Integrating Business Processes

Enterprise Application Integration

Timo Itälä, Paavo Kotinurmi2007



Course Map 2007

12.9: EA (Enterprise Architecture) Overview19.9: ERP (Enterprise Resource Planning) systems26.9: BI (Business Intelligence) and Data Warehousing3.10: EAI, (Enterprise Application Integration) BPM (Business Process Management) and SOA (Service OrientedArchitecture)

Timo Itälä: Integrating Business ProcessesPaavo Kotinurmi: Enterprise Application Integration, RosettaNet, ebXMLTimo Itälä: BPM and SOATimo Itälä: Case Satakunta

10.10: ECM (Enterprise Content Management) and PDM (Product Data Management)

17.10: Enterprise Architecture Rewisited24.10: Governance, EA Summary



In the early days...

Automation of manual tasksPayrollBookkeepingOrder entryInvoicingStatistics

Input Output

Data Program

Computer



The next steps...Application packages

PersonnellEconomy administrationProduction ControlMaterial RequirementsInventory-Orders-Shipping-InvoicingPurchasingProduct development...

User tasks

Databases

Applications

Platforms



Business processes...

Integration needed...”a business process is a series of steps designed to produce a product or service. Most processes (...) are cross-functional, spanning the ‘white space’ between the boxes on the organization chart" Applications support functional areas and have their own data and input/output formatsSupport for business processes need integration of the applications to support the flow of the processes

flow of dataflow of controlflow of work



Example: Paper sales and distribution

Core business processesSales forecasting and budgetingOrder entry and delivery

FunctionsAdministrationProductionShipments managementSales/shipmentsCustomer

Information flows within a business process betweenfunctions

Source: Jouko Hannus: Prosessijohtaminen, 1993


HELSINKI UNIVERSITY OF TECHNOLOGY 7

Example: Integration of information flow

Applicationshave interfacesexchange messagessupport their ownmessaging protocols

Message Brokerintegrate severalapplicationsprovide conversionroutines for codesand formatssupport multiplemessaging protocols

Source: Jouko Hannus: Prosessijohtaminen, 1993



The integration stack

Transport Layer: Physicaland logical connections

Content Layer: Syntaxand semantics

Process Layer: Participantsand rolesChoreography and orchestration

Adaptation: Applications

Example: Persons from differentcountries with different nativelanguages need to do business with each other



Who does the adaptation?

I talk Your language to YouThe sender does the adaptation

You talk my language to meThe receiver does the adaptation

I talk my language to him, he talks your language to You, He does the translation

The middleman does the adaptation

I talk Esperanto, You talk EsperantoThe sender and the receiver both do the adaptation

I

The Sender

He

The Middleman

You

The Receiver



Integration topology options

Layers may have different topologies

Point-to-point Hub and spoke Common definitions



Data is different...Transaction data

AmountEuroTime stamp

Reference dataOrganizationLocationProductCustomer

Process dataProduction batch numberOrder numberPacking list numberInvoice numberProcess instance unique identifiers

Transactions:

Production: DeliveriesSales: OrdersShipping: ShipmentsBilling: InvoicesFinance: Payments



Master Data Management (MDM)

Integration of MDMProcess: Who, When, WhereContent: Common meaningsTransport: Repository - interfaces

HistoryVersioning of reference dataOperational systemsData Warehouse

Internal - ExternalInside the enterpriseBetween enterprises

Reference data



Application integration options

Options within an enterpriseSingle application: ERP, CRM, FinancialsSingle database, multiple applicationsShared application components, common APIsMessages between applicationsDesktop integrationService Oriented Architectures



Business to business integration (B2Bi)

EAI

EAI

EAI

EAI

Different requirementswithin enterprises and between enterprises

Different approacheswithin enterprises and between enterprises

EAI

Company A

Company B

B2Bi services

Company D



Enterprise Application Integration

Point-to-point

EAI

With 68 systems there are 2278 possible (n*(n-1)/2) interconnections!

With 68 systems there are 68 possible interconnections!

Average organisation has 68 application systems according to a study of 400 enterprises(Finland Government 3500, EA case hundreds)



EAI box in ERP presentation

EAI tools ship with adapters to popular packaged applications (e.g. SAP)



Pitfalls in point-to-point integration

Complexity Custom InterfacesManual re-keyingStovepiped processesData migration & consistency



EAI services

PDM system

CRM solution

Supply Chain Mgmt

eCommerce

Enterprise Resource Planning system

Siebel

WWW

I2eMatrix

SAP R/3

Pakki

Legacy application

Integrated enterprise



EAI selling arguments

Adding new interfaces or new application cheaper

Utilizing legacy systems (information availability)

Fewer interfaces

Data transformations in one place with ready-made tools

Reusability

Flexibility

Better control and visibility with transactions



EAI services include

Platform, protocol management..

Asynchronous,Synchronous messaging support..

Security services, encryption,non-repudiation..etc

Routing services, publish/subscribe..

Directory services..

Metadata management & repository services..

Event management, topology & synchronization..

Data mapping & transformation services.. (not always unified data model behind)



EAI limitations

EAI doesn’t solve semantic problems – you still need to define intermediate data formats etc.

EAI products are fairly young (except Message Oriented Middleware)

Standardization, information ownership, semantics etc big problems also within companies

Customer data…

Product data…

Technology is not enough, sometimes need to adjust processes

Most EAI projects fail (70%) - Constant change, Lack of EAI experts, Competing standards, EAI is a tool paradigm, ..



EAI services

PDM system

CRM solution

Supply Chain Mgmt

eCommerce

Enterprise Resource Planning system

Siebel

WWW

I2eMatrix

SAP R/3

Pakki

Legacy application

Semantically integrated enterprise ?!?

transformation

transformationtransformation

transformation

transformation

Is the transformation mess still n(n-1)/2?

Or is the so called canonical format as universal transformation target in the middle 2*n?



Business to business integration (B2Bi)

EAI

EAI

EAI

EAI

Different requirementswithin enterprises and between enterprises

Different approacheswithin enterprises and between enterprises

EAI

Company A

Company B

B2Bi services

Company D



EDI background

The creators of Electronic Data Interchange (EDI) were

mainly concerned about the size of their messages.

EDI messages are very compressed and use codes to

represent complex values.

The metadata is stripped from an EDI message

makes the message difficult to read and debug (but

they are meant for computers not human)

EDI programmers are hard to train and expensive to

keep. This complexity drives cost.

No one global EDI standard (UN/CEFACT, X.12)



EDI (EDIFACT order)UNH+0002771776+ORDERS:D:99A:UN:FI0084’BGM+105+40063000277177602748497+9’DTM+4:20000705:102’DTM+2:20000706:102’DTM+9:20000705:102’NAD+BY+003709895955:100++TRADEKA OY’NAD+SE+003702134547:100++OY HARTWALL AB’NAD+CN+40063000::92++VALINTATALOHERVANTA+LINDFORSINKATU 2+TAMPERE++33720’LIN+1++6413600001584:EN’IMD+F+8+:::HTW NOVELLE ORANGE LIME 1,5 L’QTY+21:144’LIN+2++6413600000280:EN’IMD+F+8+-:::VICHY 0,33L/HARTWALL’QTY+21:430’UNS+S’CNT+2:2’UNT+17+0002771776'

Source: TIEKE (EDI standards implementation guidelines document)



Motivation for integration & e-business standards

Data transfer needs high, volume high, probability of human errors high,

frequency of data transfer Integration is needed between systemsXML has been central element in recent B2B standardization but XML alone is not enoughAlthough following are all human readable/interpretable, computers have problems in these things

<e-business/> <date>10/3/2007</date><eBusiness/> <date>3rd October 2007</date><E-business/> <xs:date>2007-10-03</xs:date>

XML provides a syntax way to represent information

Need standard to define commonly understood business documents

B2B standards often don’t just standardize the business documents, but define also the inter-company business processes and how the business documents can be securely transported over the Internet



Automatic process

Business Document is standardized message encoded using XML or EDI

Reliable messaging =“postal service”



RosettaNet messaging principle

Internet & XML

RosettaNet defines processes and a framework for how data gets passed over the Web and certain handshake criteria.

Company A

SAPERP

Company Specific processing

I2APS

Company BCompany Specific

processing

Translate from RosettaNet standards to Company A system data set.

Translate from RosettaNet standards to Company Bsystem data set.

source: RosettaNet



Problem that RosettaNet tries to solve

Standards needed to enable system-to-system

B2B collaboration.

Helps solving some semantical problems in

specific industry by providing message

guidelines, dictionaries and unique identifiers

Defines standard business processes

Reliable messaging over Internet



B2B Process Integration

Process PO

Send POCustomer

Send POSupplier

ProcessSales Order

Customer Supplier

Receive POAcknowledge

Send POAcknowledge

Send POResponse

Close

Send PO

Receive POResponse

Send POResponse

Acknowledge

Receive PO

Send POResponse

Receive POResponse

Acknowledge

Receive PO

CheckCustomer

CheckCredit

CheckAvailability

Create SalesOrder

Receive POAcknowledge

Send POAcknowledge

Send POResponse

Close

Receive PORequest

SelectSupplier

GenerateRFQ

SendRFQ

Select RFQResponse

SendPO

Close

Send PO

Receive POResponse

Send POResponse

Acknowledge

Receive PO

Send POResponse

Receive POResponse

Acknowledge

Receive PO

CheckCustomer

CheckCredit

CheckAvailability

Create SalesOrder

Private process(Company -specific)

Public process(Standard)

Public process(Standard)

Private process(Company -specific)

PO

CRM

SCM

ERP

Figu

re p

rovi

ded

by V

itria

Sys

tem

s



Other standards for B2B integration

UBLebXMLNumerousindustry-specificstandards

Usage Example

33 Build System

Specifications

Profiles

Scenarios

Request ebXML specification

11

44 Register company profile

Query about Company X

55

Request Company X’s Scenario

99

DOBUSINESS!

11

DOBUSINESS!

11

Send Company X’s Scenario1010

ebXML BP Model

ebXML BO Library

Send Company X’s Profile66

Submit TPA77

TPA Accepted88

Send ebXML specification 22



Today what implemented and Tomorrow

Latest XI (Netweaver v. 7.1 , ESB support)

SAP 6.0 also advertised as enabling enterprise SOA

integrating business processes - aalto ea lesson 4 part 1_2.pdf · 3.10: eai, (enterprise ......

Documents