Metso in brief - Aalto · Trigger Adapter Script Sending Application Receiving Application MQ Broker Integration App. MQ ... Metso Paper Baan 3498724 = Metso Automation MfgPro

Enterprise Application Integration(EAI) at Metso Oyj

Markku LeikasMetso IT

EAI Development Manager12-oct-2005

2 © Metso Corporation 2003

Metso in brief

• Global technology company• Serves the pulp and paper

industry, rock and minerals processing, energy and selected other industries

• Net sales of approx. EUR 4 billion in 2004

• Approx. 22,000 employees in more than 50 countries

• Listed on the Helsinki (ME01V.HEX) and New York (MX.NYSE) Stock Exchanges

• Approx. 27,000 shareholders


Metso’s global operations

Production and salesSales and aftermarket units

Canada

USA

Mexico

PeruBrazil

Argentina

AustraliaNew Zealand

IndonesiaSingaporeMalaysia

South Africa

ZambiaZimbabwe

Ghana

Spain

Russia

JapanIran

India

China

Taiwan

Thailand

South Korea

United ArabEmirates

TurkeyPortugal

Germany, Switzerland, AustriaItaly

FranceBelgium, The Netherlands

United KingdomDenmark Poland, Czech Republic

Croatia

Romania, Bulgaria

EstoniaSwedenFinlandNorway

Costa Rica

Hungary, Ukraine

Kazakhstan

Uzbekistan

Chile


Net sales by market areaJanuary - June 2005

(1-12/2004 in brackets)

North America21% (21%)

South America10% (8%)

Asia-Pacific 18% (23%)

Other countries5% (6%)

Finland9% (9%)

Other Nordic countries12% (8%)

Other European countries 25% (25%)


Metso characteristics

• International - languages- legislation- different time-zones

• Focus on engineering and manufacturing- low-medium volumes- often highly customized

• Changes of corporate structure each year - divestments and acquisitions

• Heterogeneous information systems• Extensively outsourced IT & carefully budgeted IT spending• A single IT system cannot serve all the needs

--> Need for enterprise application integration


Business Process Management (Business Process and Workflow Modeling)

Standard Library for Business Messages and Processes (XML, RosettaNet, SOAP, WSDL, etc.)

ERP Finance

HR

PDMData

Warehouse

Business Management PlatformEAI Hub

Integration, Message Flows and Business Process Automation

Customers

Suppliers

Distributors

Partners Systems

Marketplaces

S2Si

Vendors &Partners

Customers

Employees

People

Portal

Business Integration Environment

CMMSCRM Notes Billing

Other Application


What enterprise application integration is

• A portfolio of methodologies and expert services to integrate distributed (in time and space) business applications together to run a business process

• An expert service to develop and install the integrations• A monitoring system and processes to detect failures in

message delivery • An expert service to recover from delivery failures• A business message log / audit trail system (f.ex SOX

requirements)• Some software and hardware


Environment layout

EAI Broker Active EAI Broker PassiveMessage Warehouse

Notes Gateway

Managed Notes Domain

B2B Gateway

Internet EDI Operators

Application Server

Managed Web UI Domain

SQL Server Front End

Managed SQL Server Domain

Business UnitApps

Managed SAP Domain

Managed Baan Domain


Products being used

• IBM p630 AIX 5.xx• IBM DB2 universal database• IBM WebSphere MQ• IBM WebSphere MQ Broker• IBM WebSphere MQ Workflow (under pilot)• TietoEnator TE MOM API Adapter• TietoEnator Message Warehouse• Custom File adapter


B2B GTW WMQ

FTP /ssh/pgp WMQ

HTTPsBW

SUPPLIERS PARTNERS CUSTOMERS

ANILinkerB2B Service

eMail

ANI LinkerWEB Transfer

Whatever protocols

ANI LinkerWEB Transfer

MetsoEmailrouter

FIREWALL

B2B

Metso EAI / B2B ArchitechtureMetso EAI / B2B Architechture

EAI_HUB

WMQ

Metso Applications

EAI NOTESGTW

WMQ

Message Warehouse

WMQMetso Applications

WMQMetso NotesApplications

EAI


MQ

TE MOMTE MOM

A message flow through the EAI system

Java AdapterScript

Java AdapterTrigger Adapter

Script

Sending Application

Receiving Application

MQ

Broker

Integration App.

MQ

HW & OS HW & OS HW & OS

Message Warehouse


Some basic guidelines of integrations

• All the messages are routed via broker to enable efficient re-routing, if needed

• ONLY asynchronous messaging from and to broker- No HTTP, JDBC, SMTP, telnet, FTP etc calls- That is, de-coupling the applications- High performance, no stalling software processes over the

network (except. Broker-SAP R/3, which has caused some problems)

• Avoidance of database integrations (JDBC etc.)- Integrations through interfaces offered by

applications/application servers - Application business logic changes and database changes do

not affect the interface- Validation of the messages by the applications


About interfacing

• De-facto style is to use filesystem in exchanging messages between the application and EAI environment+ A Metso-standard method for integration+ Easy to develop by using export and import routines found from

most applications+ Archiving of sent messages in sending server- Technically not the best, e.g. filesystem errors (read/write)

difficult to detect- Need for directory polling e.g. with 1 minute interval

• Program-to-program (Java/C) API calls used in some high-volume integrations+ Errors can be monitored by sending and receiving application on

program level+ Immediate messaging- Extensive coding & testing needed


Metso Message Schema Library ScenarioUniform Message Library

Application A1 Application B1

Application A2 Application B2

Application An Application Bm

lka234 xyzlka245 xyzlka284 xyzlka134 xyz lka444 xyzsdd123 xyzsdd234 xyzsdd245 xyzsdd284 xyzsdd134 xyzsdd444 xyz

Transformation Transformation

Transformation

Transformation

Transformation

Transformation

+ Because each application has a different data model, the use of Metso Uniform Message Library would eliminate the need to map the datamodels of different applications directly to one another. Instead, each data model should be mapped to Uniform Message Library.

+ Standard tag naming means much easier and more flexible interfaces to describe, exchange and validate business information.

- The reality is not as bright. We do not start from scratch. Standard generic solution is always more expensive to develop than one individual propriatory implementation

- in practice we are somewhere in the middle in standardization


Transf 1Transf 2

Transf 3Transf 4

Transf 5Transf 6

Transf 7Transf 8

Transf 9Transf 10

Transf 1Transf 2

Transf 3Transf 4

Transf 5Transf 16

Transf 17Transf 18

Transf 19Transf 20

Transf 21Transf 22

Transf 23Transf 24

Transf 25

25pointtopoint transformationsusing individual schemas

Metso Message Library&Transformations

Trans-form 1

Senderschema

Trans-form 2

Senderschema

Trans-form 3

Senderschema

Trans-form 4

Senderschema

Trans-form 5

Senderschema

Trans-form 6

Receiverschema

Trans-form 7

Receiverschema

Trans-form 8

Receiverschema

Trans-form 9

Receiverschema

Trans-f. 10

Receiverschema

10 transformations usingMetso Uniform schemas

MetsoUniformschema


Message standardization

• Trying to use ”standard” XML schemas, e.g. Oagis- XML message data items self-describing, single message

content can vary without problems+ No need to re-invent the wheel (develop own XML formats)+ Messages are parts of wider chain of business processes (e.g.

purchase order message contains the necessary data for invoice message)

- Often difficult to learn and master- No support by the applications, extensive coding needed

• Trying to avoid ASCII files- Fixed structure, changes difficult- Not ”self-describing”+ Comma-separated import & export format quite common


Before messages can be exchanged ,data must be harmonized (using standards)

• The same customers and suppliers have different codes in different systems Metso Paper Baan 3498724 = Metso Automation MfgPro FFLKJFD = ”UPM-Kymmene Oyj”- How to know how much we have sold to each customer?- How to know how much we purchased from each supplier?- How to invoice the same customer on a single invoice from all

the business units (ERPs)?• The same parts have different item codes in different

systems (AD69693 = IUWEEEW01 = 15x85 mm bolt)- What are the amounts of each type of parts we have bought?- How to plan the production?- Who is the alternative parts provider?

• Avoid using cross-reference tables!


Message Standardizationlevels at EAI

TODAYINTERNALMESSAGES• Message Naming

•Functional names (propriatory)•RosettaNet•OAGIS XML

• Message Classification•RosettaNet

• Message Header •Metso Message Header( by TE MOM) •SOAP Header •RosettaNet Headers

• Message Content•Application propriatory•OAGIS XML•ANI Linker xml•RosettaNet xml•Prindex xml•WSDL xml•Dictionaries : FISGMS, PSK , ..

•B2B Business Process Messages•Using BP execution languages•RosettaNet (PIP )processes

TOMORROWB2BMESSAGES

??


Metso STD EAI Message HeaderMetso STD EAI Message Header<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE MessageHeader SYSTEM "MetsoEAIMessageHeader_1.0.dtd">

<MessageHeader><SenderAppID>MPFIBANP1</SenderAppID><SenderApp>BAN</SenderApp><SenderAppDesc>Metso Paper production BAAN</SenderAppDesc><ErrorEmailRecipient>[email protected]</ErrorEmailRecipient><Date>20031125</Date><Filename>data1234.txt</Filename><GroupReferenceID></GroupReferenceID><HeaderVersion>1.00</HeaderVersion><MessageID>PURCHASE_ORDER</MessageID><MessageFormat>OAGISXML</MessageFormat><MessageFormatVersion></MessageFormatVersion><MessageReferenceId>1234567890</MessageReferenceId><MessageSize> </MessageSize><ReceiverAppID>MCFISAPP1</ReceiverAppID><SenderBA>MP</SenderBA><SenderLegalCompany>MP123</SenderLegalCompany><SenderDept>MPABC</SenderDept><SenderMA>EMEA</SenderMA><Time>141013</Time><Usage>PRD</Usage><ReceiverBA>MP</ReceiverBA>

</MessageHeader>


EAI Message ManagementEAI Message ManagementRosettaNet Based classification

Message type classes


Metso Message

Warehouse

Metso Message

Warehouse


Metso Message WareHouse

additional views

Metso Message WareHouse

additional views


Message Statusesto be viewed at Message WareHouse

Message Statusesto be viewed at Message WareHouse


Message Status DescriptionsMessage Status Descriptions


Metso EAI MINT HelpDeskMetso EAI MINT HelpDesk


Metso EAI MINT HelpDeskMetso EAI MINT HelpDesk


Some Statistics

• 237 integrations (a message X from application A to B)• 79 applications integrated• ~50 servers (separate IP addresses)• ~4000 messages/day• 95% of integrations are made via directory systems by using

files• 40% of messages are in XML format


Unit costs/integration (K€)(a large SAP R/3 integration project)

EAI Point-to-point (FTP) Point-to-point (MQ)Per integration Per integration Per integration

Specification & Project Management 3,05 3,05 3,05SW Lic. + Custom Development 3,69 4,23 4,38Data Conversions 1,07 1,07 1,07Testing 1,47 2,17 2,17Deployment/roll-out 1,23 1,36 1,36TOTAL CAPEX 10,51 11,87 12,02

SW + Developments Maintenance 0,74 0,85 0,88Operating costs + lic.deprec. + salaries 0,79 0,04 0,51Trouble shooting transfer errors 0,11 1,08 0,16BU Trouble shooting content errors 0,54 1,08 1,08Total OPEX/year 2,18 3,03 2,63

Some Finnish Industry Wide B2B activities


BizTalk serverSAP XI

webMethods

Customer

Provider

Customer

Provider

Provider

PIP3A4 _POB1(PIP3A4 _Conf)B2

PIP3B2 _NotifB3

(PIP3A4 _Conf)A2PIP3A4 _POA1

PIP3B2 _NotifA3

TradeXpress

Customer

Provider

Customer

Provider

D1D2

D3C1C2

C3 F1F2

F3E1E2

E3

Customer role: UPM, Metso

Provider role: Metso, Siemens

Transmitted messages: PIP 3A4_Purchase Order, PIP 3B2_Delivery_NotificationAvailable, but not transmitted messages:PIP 3A4_Order Confirmation, PIP 3A9_Order Cancellation, PIP 3A9_Order Cancellation Confirmation

WBI Connect

Architechture of Rubic Paper cluster RosettaNet study at HUT spring 2004Architechture of Rubic Paper cluster

RosettaNet study at HUT spring 2004


•Component manufacturer

ABC123

Mill

XYZ321

System manufacturer

LMN999

Item classification and identification Item classification and identification

• GUID - Global Unique IDentifier

• PUID - Product Unique IDentifier- ABB:12345- VAL7654321

• Designation- Position number- Type code

- Name / Title• Dictionary is needed

Needed for mapping data at EAI / B2B!Specified in projects : FISGMS & PSK (59,74) etc


How to solve product data interoperability problems in the paper cluster equipmentsupply network.

PaperIX defines:• product data exchange format• how product data is delivered• how product data is positioned to product data

applications

PaperIX technology:• format language: XML• delivery: WWW• positioning: product and

mill structures

PaperIXI B2B Product Data Exchange Research Project

(2002-2004)

PaperIXI B2B Product Data Exchange Research Project

(2002-2004)


PaperIXI mill model

transform

transform

transform

transform

transform transform

transform

transform

transform

transform

PaperIXI Mill Model ConceptPaperIXI Mill Model Concept


DictionaryWebService

Product and Service Supplier

Internet

Public Standard for Industry Data

eXchange

Requirements, specifications, orders, work orders, reports ...Product data, engineering design data, maintenance, invoicing ...

Project/installed base data

Project and lifecyclescenarios

Mill A

XML

Plant B

Plant C

etc

XML

Consultants

XML

Alliance / Prindex(Product Data Exchange)Visio(2005/oct--->?)

Company back-endspecific interface:Mapping,Transforming, Filtering, Security


Internet

Partners Customers Suppliers

B2BGateway

Corporate,Data Providerand Data User

FIREWALLDictionaryBusiness rules and filtersMapsTransformations

Dynamic User access to manageand change Filtering Policies

Data exchange interface

PRINDEX XML

MappingTranforming

Filtering

Industry(group) specific dictionaryrepository

Corporate Data Exchange Interface Scenario

Corporate product, engineering and asset

managament data repositories


Metamodel based Schema implementation

PumpValve

TankPipeline

ProductRelation

Property

Individual

etc.

Meta model

Commonclassification

Ahlstrom Pump APT 51-12

Lightnin Agitator 75-Q-7.5SKF Bearing 6201-2ZNR

LengthMassflow

General rules for dictionary modellingare set on meta model level

Items

Scope of the subproject


Meta model bindings

Meta model expressed in anon-implementation-specific format e.g. UML + documentation

Dictionary concepts and rules

XML Schema implementation

RDF implementation

(e.g. OWL implementation, not included to the project tasks)

New future possibilities

MetamodelXML schema

Discpiline specific XML schemas

Inheritance

All the schemas definingexchanged data inherit fromcommon metamodel schema,ensuring consistency.


Thank You

• questions?

Documents

Metso in brief - Aalto · Trigger Adapter Script Sending Application Receiving Application MQ Broker Integration App. MQ ... Metso Paper Baan 3498724 = Metso Automation MfgPro