Design of Large-scale Enterprise Interoperable Value Webs

Transcription

1 EI2N Workshop Design of Large-scale Enterprise Interoperable Value Webs EI2N workshop, Crete 2011 Wout Hofman, TNO Matthijs Punter, TNO

2 Trends and implications Economic perspective: growing importance of services in open, globally operating organizational networks Organizational networks (defined in service science) require interoperability: dynamic configuration of resources that interact via value propositions with a governance mechanism Current interoperability solutions are closed systems, not able to function in a service society.

3 Closed systems are based on localized Implementation Guides with different semantics and syntax. global industry standards specific application industry standards regional industry standards national standards

4 Concepts for business interoperability Concepts business activity customer service provider value proposition resource transaction phase interaction type business transaction interaction Description generic activity of more than one actor changing state of a system actor requesting the execution of a business activity actor providing a business activity instance of a business activity of a service provider a person and/or real world object required by or exchanged as part of a business activity phases governing value exchange according a value proposition event with a function in a transaction phase all information shared between customer and provider as specified by transaction phases actual event between customer and service provider for a business transaction Relevant source WSMO capability, ASM state transition service science service science service science REA DEMO DEMO REA EDI

5 Basic structure of a business interoperability ontology based on these concepts input business activity output basic model owned by resource can contain place input output business activity availabilty business transaction provider initiator actor previous interaction This model represents the concepts that need to be managed by a tool interaction type transaction phase

6 This structure can be refined e.g. logistics Value proposition or business service: a business activity offered by a specific service provider

7 Example: logistic business activities Transport movement of cargo items and/or equipment (containers) from one place to another Transshipment discharging cargo items and/or equipment (containers) from one transport means to another. Formally: transshipment is defined as the duration of the movement of cargo items/containers between two calls

8 Transport activity parameters for transport services of service providers pre-condition postcondition cargo type to be transported (e.g. pallets, packages, containers) min/max number of units of that cargo physical characteristics of the cargo (e.g. min/max weights, dimensions, temperature) cargo description (e.g. electronics, textile) dangerous indication from location (regions, countries, etc.) to location (regions, countries, etc.) duration (min/max, guaranteed, expected, etc.) See for instance: FreightFinder, FreightQuote, TransportMarketPlace.com

9 Separation of semantics specifying interoperability and technology for data sharing Web Ontology Language (OWL) user/business interoperability modelling value propositions with parameters Semantic models and choreography security and prviacy messaging asynchronous communication events + web services architectural grounding (events +) web crawling synchronous communication web services syntax: XML, EDIfact, etc. transport (TCP/IP, http(s), etc.) technical interoperability Electronic Data Interchange, XML Event-Driven Service Oriented Architecture Semantic Web Architecture Service Oriented Architecture

10 The following technology components need to be managed (1) Electronic Data Interchange: Trade Data Elements specification of data elements including data types (derived from documentation) Core Components complex data types, e.g. date/time including format and time zone specifier and address United Nations Standard Messages hierarchical structures with segments build of Core Components (a segment is a specialized Core Component) extensible Markup Language: (complex) elements XML Schema Definitions (XSDs), which are complex elements Events are constructed of XSDs

11 The following technology components need to be managed (2 Web Services) Port (URL), binding (association between interface and port), and interface Operation can take place at an interface according to input and output parameters Parameters messages represented by XSDs

12 which leads to the following technical concepts to be managed by a tool

13 The issue is to manage business concepts and their grounding or representation by technical concepts - reminder business concepts architectural grounding messaging events + web services (events +) web crawling web services technical concepts

14 leading to the following ontology representing business and technical concepts owned by resource can contain place input output business activity availabilty business transaction provider initiator actor previous interaction interaction type business concepts transaction phase represented by grounded by architectural grounding Trade Data Elements Core Components EDI UNSMs Element name XSD Parameter in out fault Interface Operation Binding Port technical concepts EDI XML events Web Services

15 Tool support an ontology and a technical component business concepts ontologies, data structures, etc.. Business Interoperability Modelling ontologies, business activity choreography EDI UNSMs, XSDs, etc. Architectural Grounding technical concepts messages, web services etc.

16 Current tooling Ontology editors (e.g. Protégé) support networked ontologies no specific version for managing business concepts not a graphical interface (some basic plugins available) XML, Web Service and EDI editors: support the management of technical concepts mostly also a graphical interface no meta model for EDI, leading to limited toolset and closed solutions Architectural grounding is lacking: ontology editors support representation, e.g. to XSDs and/or Web services grounding of ontologies to existing structures (EDI, XSDs, Web Services) is not specified

17 Next steps Refine the ontology for managing business and technical concepts Apply it as a graphical user interface for managing concepts, associations and rules for a particular business area, e.g. logistics (EU FP7 SEC Cassandra and EU FP7 INFOSOC icargo)