Vbmo2009 Presentation

Wout Hofman, VMBO workshop

VBMO workshop, december 2009

Wout Hofman (TNO), YaoHua Tan (VU, TUD)

Requirements for interoperability modelling in service systems based on BeerLL

December 2009Wout Hofman, VMBO workshop2

Content of the presentation

• Research question

• Service Systems• general concept• BeerLL, a Living Lab in ITAIDE• Modeling requirements

• Web Service Modeling Ontology• WSMO concepts• Observations

• Application of WSMO to BeerLL• data requirements• process requirements

• Conclusions and further research


Research question

Which modelling techniques can be used for modelling interoperability in service systems, which gives sub questions:

1. what are service systems and their requirements to modelling techniques?

2. from e3-value to services3. what techniques are available?4. what is their applicability to model service systems?

This contribution is limited to WSMO, Web Service Modelling Ontology.


Service systems have an economic perspective

1. Service: value-based proposition of a provider (Spohrer) with the objective of value exchange (e3-value)• customer: initiator of a service• goal: primary objective for design and operation of services (e.g. transport)• input/output of services• collaboration choreography• service enablers:

• human or subject• physical resources• information

2. Value co-creation: a service system comprises service providers and customers working together to co produce value in complex value chains or networks (Spohrer et.al.)

3. Dynamic (network) versus static (value chain) setting


Prof. Dr. Yao-Hua Tan

ITAIDE – Information Technology for Adoption and Intelligent Design for e-Government

• Integrated Research Project• 4.5 year (January 2006 – June 2010)

• EU FP6 IT funding 5.8 Meuro


Beer Living Lab objective: fraud reduction (value perspective and identification of services)

value exchange

equals (business) service?

value port equals service access point(technology

view)? value chain?

DEMO:transaction


e3-value and interoperability modelling

• ‘value port’• to show the provision or

requesting of value objects• abstraction of internal business

processes

• ‘value exchange’:• connection of two value ports

• ‘dependency path’• a set of dependency nodes and

segments that leads from a start stimulus to an end stimulus

• ‘service’• value based proposition of provider

(Spohrer)• abstraction of internal (business)

processes• services accessed via ‘service access

point’ (‘port type’)• note: ‘service’ is currently defined in e3-

value as an example of a value object• ‘(business) transaction’:

• execution of a service of a provider by a customer

• dynamic: actual connection

• ‘value chain’:• a set of collaborating actors executing a

business transaction• transaction coordination by each actor

in a value chain represented by a transaction tree


Each value chain can be represented by a transaction tree, example derived from dependency path.

customer

supermarket

retailer UK

customs UKHeineken NL

carrier customs NL

transport

service

declarationservice

beer production/selling

service

declarationservice

beer sellingservice

beer sellingservice

prod.unit transport

control(sensors)

control

control


Interaction sequencing in value chains can be represented by sequence diagrams• each value chain has another sequence diagram• value chains depend on decoupling points (Monhemius et.al.)

Heineken NL Heineken UK Retailer UKDutch Tax UK Tax Supermarket

Order

Order

Carrier

Order

Transport instruction

Planning

Delivery schedule

Declaration

Shipment Authorisation

Transport report

Delivery schedule

Delivery schedule

Arrival report

Excise movement

Arrival report (exc. payment)

Approval

Arrival report

Arrival report

Arrival report


BeerLL – data structure modelling limited set of services (simplified model)

UN/CefactCore

Component


Modeling requirements (information perspective)

• Autonomy is the basic requirement (EU: subsidiarity):• each actor has its specific semantics• each actor decides on its value chain

• Data requirements• inclusion/reference to existing data structures (e.g. core components)• generation of XML Schema from data structure (consistency, completeness)

• per interaction type• for all interaction types

• process requirements• support of services that constitute different value chains• interleaving of services to allow parallel processing of outsourced services• exceptions


Second question: available techniques. The SOA paradigm offers this type of flexibility.

servicesservices

conceptsconcepts

semanticssemantics

technologytechnology

• COSMO (mediation)• WSMO/OWL-S• Archimate (architectural perspective)

• WSMO• OWL-S• SAWSDL• BPMn (processes and choreography)

• BPEL for orchestration• Web Service Definition Language• XML Schema (business documents)

Available technology and concepts for services.


WSMO concepts seem in line with characteristics of service systems• information semantics - ontology• functional semantics:

• goal: customer requirements• capability: real value of a service• mediation: matching of goal and capability (type of service discovery)

• behaviour – choreography of interactions offered across an interface• grounding – relation between conceptual specification (WSML) and

technical solution (WSDL/XML Schema)


WSMO is the application of Abstract State Machines in the service domain

Capability

pre-conditionsassumptions

post-conditionseffects

Goal

mediation

transition transition transition transition

transition transition transition

interface/choreography/orchestration –implementation support of a capability

information semantics

ASM


The basic observation relates to ‘abstractness’of WSMO (ASM)• Pro: ability to express behaviour of complex systems as a set of

transitions

• Con: difficult to model because of its dynamics:• WSMO choreography combines choreography and orchestration of services

• a transition of a capability can trigger a goal, thus dynamically composing value chains in service systems,

• which gives no distinction between ‘internal’ and ‘external’ visible states• Non-deterministic behaviour:

• no operators between transitions• inherent feature of ASM

• Basic issue:• a capability specifies the actual operation on a state space expressed by an

ontology• a capability requires a choreography and is supported by an orchestration• choreography and orchestration are also modelled as transitions on the state

space• choreography could be modelled according as a transaction pattern (Demo)


customer provider

Application of WSMO to BeerLL - autonomy

CapabilityGoalgoal

mediation

transition transition

informationsemantics

transitiontransitiontransitiontransitiontransitiontransition

transitiontransitiontransitiontransitiontransition

informationsemantics

service or process mediationor choreography standardization

(collaboration protocols)?

data mediationor shared ontology

(extended Core Components,Common Information Model)?


Application of WSMO to BeerLL – domain semantics

Inclusion of structures

(core comp.)

resources

resourcetypes

actor rolesevent

event


An example of a capability of a service implemented by BeerLL for tracking and tracing containers with sensors

capability LocateContainerimportsOntology “goodsDeclaration"precondition TRECNumberdefinedBy ?packaging memberOf packagingand ?packaging[TRECNumber hasValue ?TRECNumber].

postcondition PhysicalLocationdefinedBy exists ?TRECNumber (?packagingType

[packagingType hasValue ?TRECNumber] )implies ?location[(packagingType+location)

hasValue ?location]and ?departureDateAndTime[(packagingType+location)

hasValue ?departureDateAndTime].


Application of WSMO to BeerLL – process requirements

WSMO web services can be appliedWSMO web services can be appliedservices for value chainsservices for value chains

Specifications of transitions consisting of choreography and orchestration, which requires choreography mediation

Specifications of transitions consisting of choreography and orchestration, which requires choreography mediation

interleaving of services

interleaving of services

WSMO (ASM) basically specifies a correct system, which needs to include services for handling exceptions from the ‘real world’ (completeness)

WSMO (ASM) basically specifies a correct system, which needs to include services for handling exceptions from the ‘real world’ (completeness)

exceptionsexceptions

WSMO as redesign of existing services or generation of technical services (WSDL/XML Schema; shared ontology or interaction types?)

WSMO as redesign of existing services or generation of technical services (WSDL/XML Schema; shared ontology or interaction types?)

groundinggrounding


We are currently working on the following model, which could be related to REA.

businesstransaction

eventresource

value pro-position

capability

actor

transactionprotocol

eventtypes

resourcetype

belongs to

is of

initiator

provider

published by

is ofrefers to

refers to

has a

is part ofcan be transferred by

is transferred by

is of

equals business service?

has

described by state machines?

equals choreography?

Demo transaction pattern

can be specified for interoperability

in a business area/sector

WSMO-PA: WSMO meta structure for

Public Administration

business activity?


Conclusions and further research

• Conclusions:• ontology for domain semantics offers better inclusion of other structures than

other methods like UML object diagrams• formal methods force correctness of specifications (completeness is difficult

to enforce good design)• abstract specification graphical support

• Further research/discussion:• How to get from e3-value to services? REA and interoperability model?• Role of shared ontology for business interoperability• Support of mediation• Non-determinism and other formalisms:

• collaboration protocols with a requirement for operators (see for instance workflow patterns)• ‘time’ as discriminating factor between two transitions• timed, coloured Petrinets are an alternative (graphical support, operators, patterns, time, formal

model)• COSMO: a model for collaboration• finite state machines?

Vbmo2009 Presentation

Technology

Transcript of Vbmo2009 Presentation