1 Santos, Coutinho, Cretan, Beca, Jardim-Goncalves - IWEI2013 Standardisation Tools for Negotiating Interoperability Solutions Tiago Santos Carlos Coutinho.

1Santos, Coutinho, Cretan, Beca, Jardim-Goncalves -IWEI2013 Standardisation Tools for Negotiating Interoperability Solutions

Standardisation Tools for Negotiating Interoperability

Solutions

Tiago SantosCarlos Coutinho

Adina CretanMiguel Beca

Ricardo Jardim-Goncalves

March 25th 2013

2IWEI2013

Contents

Overview

Problems

Research Questions & Hypotheses

Proposed Solutions

Case Study Validation

Conclusions

Standardisation Tools for Negotiating Interoperability SolutionsSantos, Coutinho, Cretan, Beca, Jardim-Goncalves -

3IWEI2013

Overview / Background


Enterprise Interoperability (EI):

Enterprises face the constant need to evolve:

o Capable of forming Virtual Organisations (VOs);

o Compliance to the applicable legislation and regulation;

o Improving Quality Standards for service (e.g., accessibility);

o Support of new platforms & technological solutions (e.g., mobile, cloud);

o Support of new design and look & feel trends;

o Compliance to evolving standards and continuous improvement.

Seamless exchange of information:

o Internally (inter-departments), Externally (partners, suppliers) and both;

o Common understanding of the information by all parties.

4IWEI2013 Standardisation Tools for Negotiating Interoperability SolutionsSantos, Coutinho, Cretan, Beca, Jardim-Goncalves -

Enterprise Interoperability (EI):

Sustainable Enterprise Interoperability (SEI):

o Continuous maintenance activities regarding some major aspects;


o Supported by the Agents technology.

5IWEI2013 Standardisation Tools for Negotiating Interoperability SolutionsSantos, Coutinho, Cretan, Beca, Jardim-Goncalves -


Knowledge Management:

Development of strategies to capture knowledge;

Supported by Rules Engine technology.

Negotiation Management:

Creation of negotiation strategies;

Also supported by Rules Engine technology.

6IWEI2013

Problems


Enterprise Interoperability (EI) maintenance:

Problems regarding Interoperability:

o Interoperability is frail to concepts and semantics change;

o Once lost, it takes some time to regain interoperability – downtime;

o Higher interoperability complexity + Little knowledge Harder to regain it.

Strategies:

o SMEs: Frequent adapting to the new changing realities;

o Introduce a negotiation system to the SEI;

o Use of standard concepts in negotiation and knowledge techniques.

7IWEI2013

Research Questions & Hypotheses


Research Question:

How to develop a framework that can boost its standardization?

Options:

Using best-practices;

Re-using standard concepts.

8IWEI2013

Contribution to State of the Art


What’s New:

The concept of negotiations in the SEI;

Framework + Methodology for monitoring and control of interoperability:

o Determine the knowledge of each enterprise;

o Control the different negotiation strategies.

Establish negotiation as a standard approach to found solutions for

enterprise interoperability.

9IWEI2013

Proposed Solution


Framework for Sustainability of the Interoperability:

Two different applications (forming an environment using JADE)

o The central point of the environment, the System Controller;

o The client application, the Trigger Agent;

10IWEI2013

Proposed Solution


Framework for Sustainability of the Interoperability:

Negotiation Manager and Knowledge Manager

o Use of Drools as rule engine;

o Controlled by rules.

rule “Rule-Example-Reject” when $map : java.util.HashMap(

this[“Energy efficiency”] == false, this[“High energy consumption”] == false,

this[“Costs reduction”] == false,this[“More costs”] == false,this[“Less availability”] == false,this[“More availability”] == true,this[“Less performance”] == false,this[“More performance”] == true,this[“Agent”] == “TriggerAgent-2”,

then resBean.addReject();end

11IWEI2013

Application in a real Use-Case


Tested some real changes in a web-service;

Problem:

o Determine the real downtime of a system;

o Interoperability changes with crescent complexity;

o Interoperability relies on closed-environment controlled conditions;

o Compare the results without interoperability negotiation.

The tested web-service:

o Java web-service with a simple method;

o Perform changes in the web-service, increasing the scenario complexity;

o Register all downtimes for each complexity.

12IWEI2013

Application in a real Use-Case


The results of the tests:

1 2 3 4 5 60

1000

2000

3000

4000

5000

6000

7000

8000

9000

10000

With NEGOSEIO

InteroperabilityRe-establishment Time(Downtime) in minutes

InteroperabilityComplexity Scenarios(increasing complexity)

13IWEI2013

Conclusions


The framework provides formal methods & procedures which favour the reuse of tools and lessons-learned;

Enterprises downtime can be reduced with the interoperability negotiations:

o Making stronger and healthier relations between enterprises;

o Minimizing the costs of the enterprises downtimes.

13IWEI2013

Standardisation


The framework provides a standard for dealing with interoperability throughout the whole enterprise product lifecycle;

New standard negotiation techniques were created, like the Block and the Split;

Re-using some standard concepts and using the best-practices, the developed framework established a negotiation standard to deal with the enterprise interoperability problems.

14IWEI2013

Questions & Answers


1 Santos, Coutinho, Cretan, Beca, Jardim-Goncalves - IWEI2013 Standardisation Tools for Negotiating Interoperability Solutions Tiago Santos Carlos Coutinho.

Documents

o interoperability

control of interoperability

regulation o

o capable

o smes

enterprise o control

iwei2013 standardisation

o common understanding