TJT S E50 –Yritysmuodostelmat ja niideninformaatiojärjestelmät 2006

Jukka Heikkiläjups@cc.jyu.fi

Marikka Heikkilämheikkil@jyu.fi

2

Interface between platforms and tech

• Technology platform (and a business model): – strategic alignment – partner & customer interoperability– support for processes– fit with architecture – fit with generic services– change management

Strategy

BusinessModel

BusinessProcesses

ICT pressure

e-Business opportunities

& changee-Business

processadaptation

Planninglevel

Architecturallevel

Implementationlevel

1

2

3

5

4 6

3

List oftechnical

issues

4

5

Enabling technologies for inter-organizational co-operation• Standard interfaces & architectures

– Data integration standards• e.g. EDI, ANSI X.12, iPDM/PLM

– Process integration stds• Workflows, Partnering processes

– eBusiness stds & approaches• e.g. RosettaNet, ebXML, BPEL4WS

– Business components & services• Collaborative platforms

– e.g. Notes, Quickplace, WebEX

6

Data integration

• EDI(FACT)– Working solution, but probably too time

consuming, expensive, rigid for SMEs• Big players CALS and product data lifecycle management

• Continuous Acquisition and Life-cycle Support• STEP/CALS• iPDM/PLM

• EAN connection• Message types grow in number

– International trade– Industry specific stds– E.g. ANSI X12

• 1992 105 different message types• 1998 297 –”-

7

UNCID -in the 60’s: Thus, once a company decides it will use EDI, it will require agreement with its trading partners on at least the following issues, the priorities of which will vary

based upon the specific needs of that company:

a) selection of EDI messages, message standards and methods of communication;

b) responsibilities for ensuring that the equipment, software and services are operated and maintained effectively;

c) procedures for making any systems changes which may impair the ability of the trading partners to communicate;

d) security procedures and services;e) the points at which EDI messages have legal effect;f) the roles and contracts of any third party service providers;g) procedures for dealing with technical errors;h) the needs (if any) for confidentiality;i) liabilities in the event of any delay or failure to meet agreed EDI

communications requirements;j) the laws governing the interchange of EDI messages and the

arrangements of the parties; andk) methods for resolving any possible disputes.

8

INCOTERMS Toimitustapalausekkeet

• EXW EX WORKS (... named place) • FCA FREE CARRIER (... named place) • FAS FREE ALONGSIDE SHIP (... named port of shipment) • FOB FREE ON BOARD (... named port of shipment) • CFR COST AND FREIGHT (... named port of destination) • CIF COST, INSURANCE AND FREIGHT (... named port of

destination) • CPT CARRIAGE PAID TO (... named place of destination) • CIP CARRIAGE AND INSURANCE PAID TO (... named place of

destination) • DAF DELIVERED AT FRONTIER (... named place) • DES DELIVERED EX SHIP (... named port of destination) • DEQ DELIVERED EX QUAY (... named port of destination) • DDU DELIVERED DUTY UNPAID (... named place of

destination)• DDP DELIVERED DUTY PAID (... named place of destination)

9

PAYTERMSMaksutapalausekkeet

– Payment on an agreed date – Date of payment determined by delivery of the goods

• Payment in advance - ANTICIP • Payment on delivery - CASH• Payment to the carrier on delivery - REMBURS • Payment by end of month of delivery - ULTIMO • DEL/nM - Payment at the end of a period following delivery

– Date of payment determined by receipt of the invoice • CASHFAC; CASHINV - Payment on receipt of the invoice • vastaavasti FACULTIMO; INVULTIMO; FAC/nM; INV/nM

– Compensatory payment - COMPENSE – Payment on consignment - CONSIGN

10

Financial ’EDI’

• Finnish interbanking transaction system– Accounts– Joint Venture Automatia Oy

• International SWIFT Society for Worldwide Inter-bankFinancial Telecommunications – Bank group IDs (originally, only, e.g. NDEAFIHH)

• Viimeksi hyväksytty– “Kansainvälinen pankkitilin numero (International

Bank Account Number, IBAN) otettiin Suomessakäyttöön 01.10.2001 kansainvälisen maksuliikenteenhelpottamiseksi. Numeron on määritellytEurooppalaisten pankkien standardointijärjestö(European Committee for Banking Standards, ECBS) dokumentissa EBS204 (European Banking Standard) ja se on myös ISO:n standardi 13616” (c.f. Vuori, 2002).

11

Some special stds

• ISBN = International Standard Book Number• ISSN = International Standard Serial Number • ISMN = International Standard Music Number • ISWC = International Standard Work Code

• + DOI, MARC etc.

12

JÄRJESTELMÄ-INTEGRAATTORI

ASIANTUNTIJA-PALVELUT

OMAT TUOTTEET

KANSAINVÄLISYYS

Excellence in eBusinessExcellence in eBusiness

EDI-architecture: EDI-system

Application Interface

Adapter

Converter

Transport Module

Network

Mon

itor a

nd

Con

figur

atio

nU

ser I

nter

face

Application Sovellukset ja tietovarastotSovellukset ja tietovarastot

SäännötSäännöt

Mallipohjat ja Java/ActiveX -komponentitMallipohjat ja Java/ActiveX -komponentit

XML tagit, agentitXML tagit, agentit

XML jäsennin / generaattoriXML jäsennin / generaattori

XML / EDI dataXML / EDI data

Dokumenttiobjektimalli (DOM) tai tiedosto/sanomaDokumenttiobjektimalli (DOM) tai tiedosto/sanoma

Varastointi ja kuljetusVarastointi ja kuljetus

EDI (Valtokari, 2000; Kalkkinen 2000)

13

JÄRJESTELMÄ-INTEGRAATTORI

ASIANTUNTIJA-PALVELUT

OMAT TUOTTEET

KANSAINVÄLISYYS

Excellence in eBusinessExcellence in eBusiness

EDI architecture: modules

• Transport Module transport the EDI-messages to the business partner and receives messages from network.– Transport framing may be used (ED2, ED3).– Typical protocols include FTP, email and HTTP.

• User Interfaces are used to perform configuration and monitor traffic through the EDI-system.

JÄRJESTELMÄ-INTEGRAATTORI

ASIANTUNTIJA-PALVELUT

OMAT TUOTTEET

KANSAINVÄLISYYS

Excellence in eBusinessExcellence in eBusiness

EDI architecture: modules

• Application Interface handles data interchange with the application and supports application logic. The data format used is specific to the application (inhouse-format).

• Adapter may perform some processing to the inhouse-data (for example ad-hoc fixes).

• Converter performs conversion between inhouse-and EDI-format.– EDIFACT, XML/EDI, ANSI X.12

EDI (Valtokari, 2000)

14

15

NetData experiences (Kotinurmi, 2003)

16

NetData experiences (Kotinurmi, 2003)

17

Outcome (IBM, 2004)

18

Enterprise Systems (ES) and the Supply Chain

Davenport & Brooks, 2004

• Most companies now prefer to have their ES communicate directly with each other using XML over the Internet

• They still must determine –either individually or as members of an industry group –– How to interface their information and business

processes with their trading partners– Ensure that parties agree on meanings of

entities– What steps are required

19

Enterprise Systems (ES) and the Supply Chain

Davenport & Brooks, 2004

1. Alternative: Develop one-by-one interfaces• Example: PolyOne

• Using translations software PolyOne has direct connection between its SAP and supplier’s SAP

• Total 8 suppliers and customers connected

2. alternative: Industry hub– Example: elemica

• Chemical industry consortium• Mission to connect the ES of the 22 chemical

firms that sponsor it.– Practically every chemical firm has installed

SAP

20

Collaborative platforms/Hubs

21

Hubs and/or Buses (IBM, 2004)

22

Anilinker

• Business process services– Purchasing and procurement– Sales– Invoicing and financing– Logistics– Product Data Management

• Services– Project management services– Process modeling services (e.g. RosettaNet)– Operating services

23

Process Integration

24

Buses (c.f. IBM, 2004)

25

New technologies:Generic Web Services architecture, vendor specific

architectures and emerging standardsNew

Standard: BPEL4WS

Enhanced process management through new standards(O’Riordan, D. 2002 / MP)

26

PIP

An example of PIP: It specifies the public process between companies. Public process specification creates a need for company’s internal processes (Anilinker & Iocore, 2002).

27

Standards convergence

28

RosettaNet Standards Convergence Standards Convergence – Two Views

Standards convergence opportunities generally fit into one of these views:

1. Content Standards – The ebusiness information published as a standard. These standards include processes, industry specific dictionary structures, data elements, code lists and identification keys.

2. Architecture Standards – The structure, format and language used to represent the ebusiness ‘content’information. These architectural standards are outlined in detail in the BIC Model.

RosettaNet convergence planning examines opportunities for both viewsThere are some standards that fit into both views and for convergence planning are listed twice as required

29

Somestds – itis notreadyyet, ifever

(Anilinker & Iocore, 2002)

30

Key

• TPA = Trading Partner Agreement– sopimusmallit täydentämään prosesseja

• PIP = Partner Interface Process – dokkarit, suorituskyky, suojaukset, toimijat yms.

• RNIF = RosettaNet Implementation Framework– siirto- ja suojausprotokollamäärittely

• BPSS = Business Process Specification Schema• CC = Core Components• CPPA = Collaboration-Protocol Profile and Agreement• RN BD/TD = RosettaNet Business Dictionary/Technical

Dictionary• RegRep = Registaration for company profiles• ebMS = ebXML Messaging Service

31

Why Intl stds? (Granada research, 2001)Table 5. Various Codes for the Item “Battery”

Scheme Name

Code Instance

Chief Characteristics

SIC/NAICS

3-35-9-11

(Manufacturing Elect. Equip Other Battery)

• Identifies broad industry, product, and

service categories • Too high level for effective spend analysis. • Unable to drill down to contractible groups.

UCC/EAN

0-39800-08252-7

Type Manufacturer Item Check

• Product identification code, not classification

code (see section above) • Identifies branded merchandise by

manufacturer • No item hierarchy; strictly used for

identification NIGP

11223344556

• Used by local government purchasing

agencies • Maintains hierarchy • Proprietary code (fee-based usage)

Internal/Proprietary

112-003-121

Division Department Expense Item

• Proprietary codes only useful to a single

company. Expensive to require trading partners to use same code.

• Not maintained. • Limited or non-existent hierarchy

UNSPSC

26-11-17-09 Segment Family Class Commodity

• Identifies product and service by category • High specificity • Multiple hierarchies allow

aggregation/disaggregation to any relevant level of analysis

32

International stds• Unambiquous product numbering is needed

– EAN Electronic Article Numbering (UPC = U.S./CAN) to identify

• GTIN Global Trade Item Number– EAN International and UCC (Uniform Code Council) global

coding scheme EAN-13, EAN-8, UPC-A (UCC-12), UPC-E, EAN-14 (EAN/UCC-14, DUN-14, SCC-14)

– UNSPSC United Nations Standard Product and Services Code to classify and for analysis

• Unambigous enterprise numbering D-U-N-S Data Universal Numbering System

• American National Standards Institute, ANSI ASC X12, since 1989• UN/EDIFACT -council, since 1991• International Standards Organization (ISO), since 1993• United States Government (ECAT), since 1994• European Commission (EDIRA, i.e. European Commission), since 1995

– Tens of millions of companies and their rating (DUNS & Bradstreet)

33

Content View The RosettaNet Convergence Decision Matrix below includes the different types of content defined as standards. These items below only reference the specification content. The standards for structure, format and languages used to represent this business content are summarized in the second decision matrix shown at the end of this page.PLEASE NOTE: Italics items are still under consideration for adoption

RosettaNet Standards ConvergenceDecision Matrix

Content Deliverable

Build Lead Motivate Adopt

Process RosettaNet Partner Interface Processes(R)

Malyasian GovernmenteCustoms DeclarationPhilippines GovernmenteCustoms Declaration

OASIS Electronic Procurement StandardsSWIFT Payment

CompTIA WarrantyECIX/Si2 Quick Data QueryEIDX Clickable Business Process ModelsJEITA Business Process Scenarios (Japan)NEMI/IPC 2577 Mfg QualityNEMI/IPC 2578 Bill of Material, Approved Mfg List, Engineering Change Request/OrderTMF Telecommunications ProcessesVICS CPFR - ForecastingNEMI/IPC 2776 Manufacturing Genealogy

Structured Messages

RosettaNet Partner Interface Process

NEMI/IPC 2571 Product Data eXchange

Data Dictionaries

RosettaNet Business Dictionary (RNBD)RosettaNet Technical Dictionary (RNTD)

JEITA/ECALS EC Technical Dictionary ElementsECIX/Si2 EC Technical Dictionary ElementsIEC IEC6-1360 EC Technical Dictionary ElementsNIST/IEC/ECALS, ISO TC184/SC4/WG2 (PLIB) OIDDI -Interoperable Dictionary Domains

Information Objects

RosettaNet Universal Structures ContentRosettaNet Class

ebXML Core Components

Data Elements RosettaNet Simple TypeRosettaNet Complex Type (data element with code list)

CompTIA WarrantyNEMI/IPC 2578 Bill of Material, Approved Mfg List, Engineering Change Request/OrderNEMI/IPC 2577 Mfg QualityW3C - Date & TimeNEMI/IPC 2776 Manufacturing Genealogy

Code Lists RosettaNet Payment TermsRosettaNet Transportation Service LevelsRosettaNet Product Categories

HSTUS - Commodity Code for TarrifIANA MIME - Media (file) TypesIATA APC - Airport CodesISO 639-2 - LanguageISO 3166-3 - CountryISO 4217 - CurrencyUNSPSC - Product ClassU.S. Census Bureau NAICS - Industry Class

Identification Keys

D&B DUNS -Company IdentiferNMFTA SCAC - Company IdentiferSWIFT - BIC Bank IdentifierUCC GTIN -Product Identifier

34

Architecture Deliverable

Build Lead Motivate Adopt

Methodology RosettaNet/EAN.UCC XML Schema Design GuidelinesRosettaNet Implementation Guidelines (RIG)RosettaNet/Edifice/ UN/CEFACT Trading Partner Agreement

OASIS UBL - Schema Design Guidelines

Content & Process Definition

RosettaNet Universal, Domain, & System StructuresRosettaNet Access PatternsRosettaNet Information Model

RosettaNet/EAN.UCC Key & Key Resolution MechanismRosettaNet Message ConstraintsRosettaNet Dictionary Architecture

IETF/ISO/EAN.UCC Universal Code List Mapping

OMG UML - Data Modeling LangaugeW3C DTDebXML BPSS ECIX/Si2 Parametric PIPW3C XML 1.0 - Markup LanguageEAN.UCC, UN/CEFACT Standard HeaderebXML Core Components Context AssemblyAIA UDEF - Identify Data ElementsW3C OWL -Constraint LanguageW3C RDF

Content & Process Specialization

RosettaNet Single and Multi-domain Interchange StructuresRosettaNet Net Change Descriptions

RosettaNet Long Running Multiparty Process Choreography

OASIS BPEL -Message Control & Choreograph

ebXML BPSS v1.05 - Design PatternW3C OWL++

Repository & Registry

RosettaNet Repository and Registry Semantics

ebXML RegRep - Registry & Repository OASIS UDDI - Discovery Registry

Physical Connection Provisioning

ebXML CPP/A - Partner Profiling

Execution Infrastructure

RosettaNet Implementation Framework (RNIF)

RosettaNet Choreography Enforcement

IETF HTTP/1.1 - Transport ProtocolIETF S/MIME ver 2 - EncryptionIETF SMTP - Transport ProtocolIETF PKCS #7 - message encryptionITU-T Rec X.509 - digital certificatesebXML ebMS- Messaging, Transport, Routing (TRP) & SecurityW3C XSLT ver 2.0 Style Sheet Language WS-I -Messaging, Transport, Routing (TRP) & Security

Architecture View The Standards Convergence Decision Matrix below includes the different types of architecture components defined as standards that are used for structure, format, language, method to develop and method to implement other standards. The matrix above shows the actual business content being represented using the architectural standards summarized in the matrix below.PLEASE NOTE: Italics items are still under consideration for adoption

RosettaNet Standards ConvergenceDecision Matrix

35

In addition…

• Alignment with other stds-frameworks• Glossaries (ontologies), of standards• Roadmaps for embedding

36

RosettaNet Standards ConvergenceGlossary

Bank Identifer Code BIC Unique identifer for a bank. SWIFT is the registration authority.

BPEL Business Process Execution Languagehttp://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsbpel

BPSSBusiness Process Specification Schema

Choreography EnforcementEnsuring the execution of the business process choreography by trading Partners is as specified in the PIP

Collaborative Planning Forecasting and Replenishment initiative

CPFR Process definition for advanced forecasting

CPP/A Collaborative Protocol Profile and Agreement http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ebxml-cppa

Data Universal Numbering System DUNS Unique identifier for a company. Numbers are assigned and maintained by Dun and Bradstreet

Design GuidelineRosettaNet generated set of rules and guidelines for creation of RosettaNet specifications

Dictionary Architecture www.rosettanet.org/dictionaryarchitecture

ebMS http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ebxml-msg

Extensible Markup Language XML Language concerned with creating, sharing and processing information. Designed to be a container (using tags to enclose the data or information) as it is transported over a network

Global Trade Item Number GTIN Unique identifer for a product. The Uniform Code Council (UCC) is the UN/SPSC maintenance agency

Harmonized Scheduled Tarrif U.S. HSTUS

Commodity Code that is used to assess the tarrif amount due for input / expert. Used to be Export Commodity Code Number (ECCN) but this code is obsoleted

Hypertext Transfer Protocol HTTP Protocol for standard transmission on the World Wide Web

Implementation GuidelineRosettaNet generated set of rules and guidelines for use of RosettaNet specifications

Information ModelThe explicit representation of document structure in UML and XML for reuse and consistency

Interchange StructureThe structure of a message

ISO 639-2 Code list to represent language names

ISO 3166-3 Code list to represent country names and their subdivisions

ISO 4217 Code list to represent currencies. The British Standards institution (BSI) is the ISO 4217 maintenance agency.

KeyA unique identifier

Key Resolution MechanismAn algorithm for mapping a key to an entity

Long Running Multiparty Process Choreography

The choreography of business process when multiple trading partners are involved in multiple asynchronous, and possibly simultaneous, business transactions

that do not have a time limit for completion of the overall business process, even though individual business transactions may have a time limit for completion

Message ConstraintsConstraints on the existence and value of elements of a message.

37

RosettaNet Standards ConvergenceGlossary

OWL Web Ontology Languagehttp://www.w3.org/2001/sw/WebOnt/

OWL++ Enhancement to OWL that supports temporal and process constraints

RegRep ebXML Registryhttp://www.oasis-open.org/committees/tc_home.php?wg_abbrev=regrep

RFDRadio Frequency Id

RosettaNet Implementation Framework RNIF

RosettaNet Implementation Guide RIGImplementation Guide for a PIP

Schema Specification for the structure and semantics of related data. Schema is used to understand or validate a group of data

Secure/MIME S/MIME

Protocol to support encryption of messages based on RSA's public key encryption technology.

Simple Mail Transfer Protocol SMTP Protocol to transfer mail on the World Wide Web.

Single Domain Interchange StructureInterchange Structure that uses information model for

Standard Carrier Alpha Code SCAC Unique identifier for a company.

UBL http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl

UDDI http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=uddi-spec

Unified Modeling Language UML Language for object oriented analysis and design.

United Nations Standard Product and Services Code

UNSPSC

Code list to represent product class. The Uniform Code Council (UCC) is the UNSPSC maintenance agency.

Universal Structure Information Object. A RosettaNet term applied to commonly used business information objects that remain the same across all PIPs

X.509 Recommendation for authentication certificate scheme from the International Telecommunication Union (ITU-T), which is used for SSL/TLS authentication.

XML Schema Recommendation for authentication certificate scheme from the International Telecommunication Union (ITU-T), which is used for SSL/TLS authentication.

Multi-domain Interchange StructureAn interchange structure that uses information model from multiple domains

Multipurpose Internet Mail Extension MIME Code list to represent media or file types. Provided by Internet Assigned Numbers Authority (IANA).

Net Change Descriptions The description of all possible values of a component of the information model (change domain), how the changes to these values will be carried out

(change rules), under what conditions (change preconditions)

North American Industry Classification System

NAICS

Code list to represent industry names

38

Year Business Content Convergence

1999 Code List:UNSPSC - Product Class

Identification Keys:D&B DUNS -Company IdentiferUCC GTIN -Product Identifier

2000 Process:ECIX/Si2 Quick Data Query

Data Dictionary:JEITA/ECALS EC Technical Dictionary ElementsECIX/Si2 EC Technical Dictionary ElementsIEC IEC6-1360 EC Technical Dictionary Elements

Data Element:W3C - Date & Time

Code Lists:ISO 639-2 - LanguageISO 3166-3 - CountryISO 4217 - Currency

2001 Process:VICS CPFR - Collaborative Forecasting

2002 Process and Data Elements:CompTIA WarrantyEIDX Click-able Business Process ModelsNEMI/IPC 2577 Mfg QualityNEMI/IPC 2578 Bill of Material, Approved Mfg List, Engineering Change Request/Order

Structured Messages:NEMI/IPC 2571 Product Data eXchange

Code Lists:HSTUS - Commodity Code for TarrifIANA MIME - Media (file) TypesIATA APC - Airport CodesU.S. Census Bureau NAICS - Industry Class

Identification Keys:NMFTA SCAC - Company IdentiferSWIFT - BIC Bank Identifier

2003 Process:SWIFT PaymentMalyasian Government eCustoms DeclarationPhilippines Government eCustoms DeclarationTMF Telecommunications Processes

2004 Process and Data Elements:NEMI/IPC 2776 Manufacturing Genealogy

Data Dictionary:

NIST/IEC/ECALS, ISO TC184/SC4/WG2 (PLIB) OIDDI -Interoperable Dictionary DomainsInformation Object:

ebXML Core Components

Content View

PLEASE NOTE: Italicsitems are still under

consideration for adoption

RosettaNet

Standards ConvergenceRoadmap

39

Methodology:OASIS UBL - Schema Design Guidelines

Content & Process Definition:EAN.UCC, UN/CEFACT Standard HeaderIETF/ISO/EAN.UCC Universal Code List Mapping ebXML Core Components Context AssemblyAIA UDEF - Identify Data ElementsW3C OWL -Constraint LanguageW3C RDF

Content & Process Specialization:W3C OWL++OASIS BPEL - Message Control & Choreograph

Repository & Registry:ebXML RegRep - Registry & RepositoryOASIS UDDI - Discovery Registry

Execution Infrastructure:ebXML ebMS- Messaging, Transport, Routing (TRP) & SecurityW3C XSLT ver 2.0 Style Sheet Language WS-I -Messaging, Transport, Routing (TRP) & Security

Year Architectural Standards Adoption

1999 (RosettaNet Published RNIF 1.0 & 1.1)Content & Process Definition:

W3C XML 1.0 - Markup LanguageW3C DTDebXML BPSS v1.5 - Design Pattern

Execution Infrastructure:IETF HTTP/1.1 - Transport ProtocolITU-T Rec X.509 - digital certificates

2000 Content & Process Definition:ECIX/Si2 Parametric PIP Pattern

2001 (RosettaNet published RNIF 2.0)Execution Infrastructure:

IETF S/MIME ver 2 - EncryptionIETF SMTP - Transport ProtocolIETF PKCS #7 - message encryption

2002 (RosettaNet approved new PIP Specification Format)Content & Process Definition:

OMG UML - Data Modeling LangaugeebXML BPSS

Physical Connection Provisioning:ebXML CPP/A - Partner Profiling

2003

Architecture View

PLEASE NOTE: Italicsitems are still under

consideration for adoption

RosettaNet Standards ConvergenceRoadmap

40

PIP

• RosettaNet Partner Interface Processes® (PIPs®) define business processes between trading partners.

• PIPs fit into seven Clusters, or groups of core business processes, – that represent the backbone of the trading network. – Each Cluster is broken down into Segments - cross-

enterprise processes involving more than one type of trading partner.

• PIPs are specialized system-to-system XML-based dialogs• Each PIP specification includes

– a business document with the vocabulary, and – a business process with the choreography of the

message dialog.

41

PIP Directory

PIP 0A1: Notification of Failure (Version V02.00.00 - In Production)PIP 0C1: Asynchronous Test Notification (Version R01.02.00 )PIP 0C2: Asynchronous Test Request / Confirmation (Version R01.03.00D)PIP 0C3: Synchronous Test Notification (Version R01.02.00)PIP 0C4: Synchronous Test Query / Response (Version R01.02.01)PIP 1A1: Request Account Setup (Beta Version B01.00.00A - Waiting Validation)PIP 1A2: Maintain Account (Beta Version B01.00.00B - Waiting Validation)PIP 1B1: Manage Product Information Subscriptions (Version 1.0 - Waiting Validation)PIP 2A1: Distribute New Product Information (Version V02.00.00 - In Production)PIP 2A2: Query Product Information (Version 1.0 - Waiting Validation)PIP 2A3: Query Marketing Information (Beta Version B01.00.00A - Waiting Validation)PIP 2A4: Query Sales Promotion & Rebate Information (Beta Version B01.00.00A - Waiting Validation)PIP 2A5: Query Technical Information (Version 1.0 - Obsolete (replaced by 2A9))PIP 2A6: Query Product Lifecycle Information (Beta Version B01.00.00A - Waiting Validation)PIP 2A7: Query Product Discontinuation Information (Beta Version B01.00.00A - Waiting Validation)PIP 2A8: Distribute Product Stock Keeping Unit (SKU) (Version 1.1 - Waiting Validation)PIP 2A9: Query Technical Product Information (Version V01.01.01 - In Production)PIP 2A10: Distribute Design Engineering Information (Version V02.00.00 - In Production)PIP 2A11: Query Product Master (Not Yet Published - On Hold)PIP 2A12: Distribute Product Master (Version V01.03.00 - In Production)PIP 2A13: Distribute Material Composition Information (Version V11.01.00 - In Production)PIP 2A15: Request Material Composition Information (Version R11.00.00A - Waiting Validation)PIP 2B1: Change Basic Product Information (Beta Version B01.00.00B - Waiting Validation)PIP 2B2: Change Marketing Information (Beta Version B01.00.00A - Waiting Validation)PIP 2B3: Change Sales Promotion & Rebate Information (Version B01.00.00A - Waiting Validation)PIP 2B4: Change Product Technical Information (Version B01.00.00A - Waiting Validation)PIP 2B5: Change Product Lifecycle Information (Version B01.00.00A - Waiting Validation)PIP 2B6: Query Optional Product Information (Not Yet Published - On Hold)PIP 2B7: Notify of Product Change (Not Yet Published - On Hold)PIP 2B8: Notify of Product Change Query (Not Yet Published - On Hold)PIP 2B9: Notify of Product Change Acceptance (Not Yet Published - On Hold)PIP 2B10: Notify of Cancel Product Change (Not Yet Published - On Hold)PIP 2B11: Query Product Change (Not Yet Published - On Hold)PIP 2C1: Distribute Engineering Change Status (Version R01.00.00 - Waiting Validation)PIP 2C2: Request Engineering Change (Version R01.00.00 - Waiting Validation)PIP 2C3: Distribute Engineering Change Response (Version R01.00.00 - Waiting Validation)PIP 2C4: Request Engineering Change Approval (Version R01.00.00 - Waiting Validation)PIP 2C5: Notify of Engineering Change Order (RosettaNet - RosettaNet Standards - PIP Directory)PIP 2C6: Notify of Engineering Change Implementation Plan (Version R01.00.00 - Waiting Validation)PIP 2C7: Request Bill Of Material (Version R01.00.00 - Waiting Validation)PIP 2C8: Notify of Bill Of Material (Version R01.01.00B - Waiting Validation)PIP 2C9: Request Approved Manufacturer List (PIP 2C9: Request Approved Manufacturer List)PIP 2C10: Notify of Approved Manufacturer List (Version R01.01.00B - Waiting Validation)PIP 3A1: Request Quote (Version V02.01.00 - In Production)PIP 3A2: Request Price and Availability (Version V02.00.00 - In Production)PIP 3A3: Request Shopping Cart Transfer (Release Version R02.00.00 - Waiting Validation)PIP 3A4: Request Purchase Order (Version V02.03.00 - In Production)PIP 3A5: Query Order Status (Version R02.00.00 - Waiting Validation)PIP 3A6: Distribute Order Status (Version V02.02.00 - In Production)PIP 3A7: Notify of Purchase Order Update (Version V02.03.00)PIP 3A8: Request Purchase Order Change (Version V01.03.00 - In Production)PIP 3A9: Request Purchase Order Cancellation (Version V01.01.00 - In Production)PIP 3A10: Notify of Quote Acknowledgment (Release Version R01.00.00 - Waiting Validation)PIP 3A11: Notify of Authorization to Build (On Hold)PIP 3A12: Notify of Authorization to Ship (On Hold)PIP 3A13: Notify of Purchase Order Information (Version R01.00.00A - Waiting Validation)PIP 3A14: Distribute Planned Order (Version R01.00.00A - Waiting Validation)PIP 3B1: Distribute Transportation Projection (Version R01.00.00 - Waiting Validation)PIP 3B2: Notify of Advance Shipment (Version V01.01.00 - In Production)

PIP 3B3: Distribute Shipment Status (Version R01.00.00 - Waiting Validation)PIP 3B4: Query Shipment Status (Version R01.00.00 - Waiting Validation)PIP 3B5: Request Shipment Change (Version R01.00.00 - Waiting Validation)PIP 3B6: Notify of Shipments Tendered (Version R01.00.00 - Waiting Validation)PIP 3B11: Notify Of Shipping Order (Version R01.00.00A - Waiting Validation)PIP 3B12: Request Shipping Order (Version V01.01.00 - In Production)PIP 3B13: Notify of Shipping Order Confirmation (Version V01.01.00 - In Production)PIP 3B14: Request Shipping Order Cancellation (Version V01.00.00 - In Production)PIP 3B18: Notify of Shipment Documentation (Version V01.01.00 - In Production)PIP 3C1: Return Product (Version V01.00.00 - In Production)PIP 3C2: Request Financing Approval (Version R01.00.00 - Waiting Validation)PIP 3C3: Notify of Invoice (Version V01.01.00 - In Production)PIP 3C4: Notify of Invoice Reject (Version V01.00.00 - In Production)PIP 3C5: Notify of Billing Statement (Version R01.00.00 - Waiting Validation)PIP 3C6: Notify of Remittance Advice (Version V01.01.00 - In Production)PIP 3C7: Notify of Self-Billing Invoice (Version V01.00.01 - In Production)PIP 3D8: Distribute Work in Process (Version V01.00.00 - Obsolete (replaced by 7B1))PIP 3D9: Query Work in Process (Version V01.00.00 - Obsolete (replaced by 7B2))PIP 4A1: Notify of Strategic Forecast (Version V02.00.00 - In Production)PIP 4A2: Notify of Embedded Release Forecast (Version V02.00.00 - In Production)PIP 4A3: Notify of Threshold Release Forecast (Version V02.02.00 - In Production)PIP 4A4: Notify of Planning Release Forecast (Version V03.00.00 - In Production)PIP 4A5: Notify of Forecast Reply (Version V02.00.00 - In Production)PIP 4A6: Notify of Forecasting Exception (Version R01.00.00A - Waiting Validation)PIP 4B2: Notify of Shipment Receipt (Version V01.00.00 - In Production)PIP 4B3: Notify of Consumption (Version V01.01.00 - In Production)PIP 4C1: Distribute Inventory Report (Version V02.03.00 - In Production)PIP 4D1: Notify of Material Release (Version V01.00.01 - In Production)PIP 4E1: Notify of Sales Report (Version R11.01.00B - Waiting Validation)PIP 4E2: Notify of Sales Report Acknowledgement (Version R11.00.00A - Waiting Validation)PIP 5C1: Distribute Product List (Version V01.00.00 - In Production)PIP 5C2: Request Design Registration (Version V01.01.00 - In Production)PIP 5C3: Create Design Win (Version V01.01.00 - In Production)PIP 5C4: Distribute Registration Status (Version V01.05.00 - In Production)PIP 5C5: Query Registration Status (Version B01.00.00D - Waiting Validation)PIP 5D1: Request Ship from Stock and Debit Authorization (Version V01.00.00 - In Production)PIP 5D2: Notify of Blanket Ship from Stock and Debit Authorization (Version R01.02.00C - Waiting Validation)PIP 5D3: Distribute Open Ship from Stock and Debit Authorization Status (Version V01.00.00 - In Production)PIP 5D4: Query Ship from Stock and Debit Authorization Status (Version R01.00.00A - Waiting Validation)PIP 5D5: Create Ship from Stock and Debit Claim Status (Version V01.00.00 - In Production)PIP 5D6: Notify of Ship from Stock and Debit Claim Status (Version R01.00.00A - Waiting Validation)PIP 6A1: Notify of Service Contract Request (Version R11.00.00A - In Validation)PIP 6A2: Notify of Service Contract Reply (Version R11.00.00A - In Validation)PIP 6C1: Query Service Entitlement (Version V01.00.00 - In Production)PIP 6C2: Request Warranty Claim (Version V01.00.00 - In Production)PIP 6C3: Notify of Case Request (Version R11.00.00A - Waiting Validation)PIP 6C4: Notify of Case Confirmation (Version R11.00.00A - Waiting Validation)PIP 7B1: Distribute Work in Process (Version V01.00.00 - In Production)PIP 7B5: Notify Of Manufacturing Work Order (Version V01.01.00 - In Production)PIP 7B6: Notify of Manufacturing Work Order Reply (Version V01.00.00 - In Production)PIP 7C1: Notify of Manufacturing Genealogy (PIP development on-hold)PIP 7C2: Query Manufacturing Genealogy (PIP development on-hold)PIP 7C3: Notify of Quality Goals (PIP development on-hold)PIP 7C4: Notify of Manufacturing Quality (PIP development on-hold)PIP 7C5: Query Manufacturing Quality (PIP development on-hold)PIP 7C6: Distribute Product Quality Event Data (Version V01.00.00 - In Production)PIP 7C7: Notify of Semiconductor Test Data (Version V11.00.00 - In Production)PIP 7C8: Notify of Semiconductor Process Data (Version R11.00.00 - In Validation)

42

CPFR ja WYMIWYG

• e.g., CPFR-systems (Collaborative Planning, Forecasting, and Replenishment)– Continuous improvement in the networked

environment by evaluating operational, result improvement measures

• The data source (where does the data reside) • Frequency of measure • Level of measure (e.g., SKU, category, department,

etc.) • Specific SKU’s to be included in the CPFR process • Agreement on the definition of each measure, and the

method of calculation – a standard minimum metrics program should include

at least one from each area : Customer Service, Inventory, and Forecast Accuracy

43

Inteorganizational systems require standard operative, result oriented measures for

evaluating the effects

It is more about productivity (tuottavuus) and payoff (kannattavuus) than of

usefulness (hyödyllisyys), as we bring market mechanism

into the network

(example from VICS, 1997; ks. http://www.cpfr.org)

44

Intel and Shinko use RosettaNet standards tobuild forecast-to-cash procurement process (2003)

45

1. 50% reduction in manual workload at Shinko; 2. total elimination of substantial yearly autofax costs; 3. Order management throughput time reduced from 24 hours to less than 1 hour; 4. 100% errorfree purchase order processing

A Partner Interface Process (PIP) defines business processes between trading partners.

46

47

Expected benefits of Phase Two

48

Service requests and process flows (Sanz et al., 2006)

49

Business components: Coordination & Operation

50

Business model evolution on markets

(e-factors, 2004 EU IST 2001 – 34868)

ThematicThematicpriorities

SpatioSpatio--temporaltemporal dimensiondimension

IndividualIndividual

OrganisationOrganisation

IndustryIndustry

SocietySociety

…… componentscomponents//categoriescategoriesacrossacross allall levelslevels((i.e., i.e., thematicthematicprioritiespriorities). The ). The componentscomponentsconsistconsist of of detaileddetailed factorsfactorsrelevantrelevant to to business business modelsmodels. .

The set of The set of factorsfactors maymay varyvarydependingdepending on on the case the case studystudy

SpecialSpecial attentionattentionis is paidpaid to capital to capital market

priorities

TechnicalTechnical

GenericGeneric business business modelmodel frameworkframeworkconsistingconsisting ofof……

market

51

CSOFT metamodel

SERVICE

INFRASTRUCTUREMANAGEMENT FINANCE

CUSTOMERRELATIONSHIP

marketthroughfeedback for

basedon

costs

resource for

basedon

resourcefor

fundedthrough

incomefor

resourcefor

SERVICE

INFRASTRUCTUREMANAGEMENT FINANCE

CUSTOMERRELATIONSHIP

marketthroughfeedback for

basedon

costs

resource for

basedon

resourcefor

fundedthrough

incomefor

resourcefor

Strategy(-ies)

Businessmodel(s)

Businessprocesses

The articulated need for new knowledge, partners,infrastructure, etc…

Inter-organizationalstrategicadjustment

Inter-organizationalprocessadjustment

Intra-organizationalstrategy- Business processes adjustment dueto co-operation

A

BC

Strategy(-ies)

Businessmodel(s)

Businessprocesses

The articulated need for new knowledge, partners,infrastructure, etc…

Inter-organizationalstrategicadjustment

Inter-organizationalprocessadjustment

Intra-organizationalstrategy- Business processes adjustment dueto co-operation

A

BC

• CSOFT metamodel consistsof – Business model concepts

and their relationships(ontology)

• domain specification at large

– Processes for • design

– in co-operation• negotiating

– multi-stage process• operating

– feedback, learning– Case specific limitations &

restrictions

Limitations & restrictions– Non-collusion – competition & neutrality– SEC-rules

Securities and Exchange Commission (SEC)

– Trade UnionsAvailability of capable personnel

– Work protection standards & laws– Work permissions– NDAs– Tax deduction & reliefs rules

Strategy

BusinessModel

BusinessProcesses

ICT pressure

e-Business opportunities

& changee-Business

processadaptation

Planninglevel

Architecturallevel

Implementationlevel

1

2

3

5

4 6

Strategy

BusinessModel

BusinessProcesses

ICT pressure

e-Business opportunities

& changee-Business

processadaptation

Planninglevel

Architecturallevel

Implementationlevel

1

2

3

5

4 6

Metamodel for Joint Business Model Development

+ ProcessOntology CSOFT

Idealistic/GenericBusiness Model

Realized instance of the ideal Business Model

Reality Check

Case & Customerspecific limitations and restrictions

TriangulationReflection Offering limitation

of the CollaborativeNetworkedOrganization

53

Business model triangulation(Hoffner et al, 2004)

54

WebEx

• WebEx Communications, Inc. provides a global network and scalable platform for real-time, interactive multimedia communications services for Websites.

• The services allow end users to share content on the Internet using a standard Web browser. – For the FY ended 12/31/04, revenues increased

32% to $249.1M.

55

Case: Mindspeed Technologies

• Mindspeed Technologies is a provider of semiconductor networking solutions for communications applications in enterprise, access, metropolitan and wide area networks(former division of Conexant of Rockwell).

• Customers include the world’s leading companies in the high-speed infrastructure and wireless industries,

• Problem: Sales reps and channel partners located across the globe.

• training cost-effectively - ever-changing and complex technology.

56

Case: Mindspeed Technologies

• Initial solution: Videoconferencing and group meetings– Monthly training sessions via videoconference

and approximately two face-to-face for 22 sales offices

• high cost, tech. issues, inability to collaborate of videoconferencing

• onsite sales training reduced their time in the field• channel partners?

57

Case: Mindspeed Technologies

• Next solution: – marketing updates and technical training on average

once or twice a week– ongoing technical tutorials for both their direct sales

force and channel partners• sales force can either

– interact with a trainer live or – view prerecorded WebEx training session

– Pros • Training reach (global, 350 external channel partners)• Training delivery cost down by 96%• More time at customers