Project a4 claudia guglielmina txt e solutions arne j rgen berre sintef
This presentation is the property of its rightful owner.
Sponsored Links
1 / 58

Project A4 Claudia Guglielmina, TXT e-solutions Arne-Jørgen Berre, SINTEF PowerPoint PPT Presentation


  • 87 Views
  • Uploaded on
  • Presentation posted in: General

ATHENA Final Review 27 - 29 March 2007 Madeira, Portugal. Project A4 Claudia Guglielmina, TXT e-solutions Arne-Jørgen Berre, SINTEF. Project goals.

Download Presentation

Project A4 Claudia Guglielmina, TXT e-solutions Arne-Jørgen Berre, SINTEF

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Project a4 claudia guglielmina txt e solutions arne j rgen berre sintef

ATHENA Final Review

27 - 29 March 2007

Madeira, Portugal

Project A4

Claudia Guglielmina, TXT e-solutions

Arne-Jørgen Berre, SINTEF


Project goals

Project goals

  • To synthesise the results of the research performed in Action Line A projects into a conceptual, applicative and technical ATHENA Interoperability Framework (AIF) and instantiating it to the ATHENA Interoperability Profiles (AIPs) needed to implement the Action Line B scenarios (WPA4.2 –> DA4.2)

  • To detail the technical AIF, Product/Process Interoperability frameworks, and to validate results against the requirements by describing the identified profiles

    (WPA4.3 –> DA4.3, WPA4.4 –> DA4.4) and DA4.6 (Validation)

  • To define and implement a Suite of Software Services to cover the whole life cycle of the implementation of an interoperability project (WPA4.5, WPA4.6 –> DA4.5)


Athena a4 deliverables

ATHENA A4 deliverables

D.A4.2

Specification of Interoperability

Framework and Profiles, Guidelines and Best Practices

AIF Website

Project

support

suite

D.A4.3

Product-based Interoperability Infrastructure

D.A4.5

Interoperability Life-cycle

Services specifications

Product infrastructure

D.A4.6

Validation of Research

Results

D.A4.4

Process-based Interoperability Infrastructure

Process infrastructure


Presentation outline and speakers

Presentation outline and speakers


Athena interoperability framework aif

ATHENA Interoperability Framework (AIF)


Sources and usage of the aif

Sources and usage of the AIF

used for further identification of research requirements

integrates

research

results of

AL A

integrates experience from AL A prototypes and B5 technology testing

integrates prototypes

of AL A

projects

for a given

profile

used for transfer of knowledge regarding application of integration technologies

used in B5 for technology testing based on profiles


Aif success criteria research and development

AIF success criteria (research and development)

  • Holistic, generic, configurable and extensible solution approach to interoperability.

    • By holistic we mean that the framework should capture and inter-relate information from many perspectives covering business, knowledge, technical (ICT) and semantic issues relevant to interoperability.

    • By generic we mean that the framework should be applicable and usable in numerous user scenarios having different interoperability requirements.

    • By configurable we mean that the framework should allow to be customised to specific application domains and industry sectors.

    • By extensible we mean that the framework should define guidelines and to include new perspectives according to different business and/or stakeholder concerns.

  • Instantiation of the framework with research results from ATHENA.

    • By instantiation we mean to successfully integrate results from the three research areas enterprise modelling, architectures and platforms, and ontology of ATHENA.


Specification and development of the aif

Specification and development of the AIF


Athena interoperability reference architecture

ATHENA Interoperability Reference Architecture


Aif conceptual integration

AIF – Conceptual integration


Conceptual integration

Conceptual integration

  • AIF provides a compound framework and associated reference architecture for capturing the research elements and solutions to interoperability issues that address the problem in a holistic way.

  • The specification of the AIF has been formalised using a model-driven approach – the AIF conceptual model.

  • The conceptual model is structured into separate model packages covering specific concept domains that we see relevant for addressing interoperability.


Interoperability framework

Interoperability framework


Interoperability reference architecture

Interoperability reference architecture


Interoperability modelling

Interoperability modelling


Aif applicative integration

AIF – Applicative integration


Athena interoperability methodology aim

ATHENA Interoperability Methodology (AIM)


Baseline methodology

Baseline methodology


Requirements solutions mapping

Requirements – solutions mapping


Athena knowledge base implemented in prot g

ATHENA Knowledge Base (implemented in Protégé)


Athena interoperability methodology summary

ATHENA Knowledge Base

(implemented in Protégé)

ATHENA Interoperability Methodology (summary)

[Deliverable D.A4.5]

Tool support


Aif technical integration

AIF – Technical integration


Technical architecture

Technical architecture


Technical architecture services

Technical architecture – Services


Example configuration and implementation

Example configuration and implementation


Process based interoperability infrastructure deliverable d a4 4

Process-based interoperability infrastructure[Deliverable D.A4.4]

  • Service-enabled cross-organisational business processes (CBPs)

  • Direct path between business level and design and execution of business processes by service composition

  • Model-driven and CBP modelling approach for technical and execution levels

  • Link the service level descriptions to the business processes

  • Pilot examples:

    • CRF Strategic Sourcing

    • AIDIMA e-Procurement


Product based interoperability infrastructure deliverable d a4 3

Product-based interoperability infrastructure[Deliverable D.A4.3]

Product-based interoperability is characterized by the terms shared knowledge and concurrent access

Both terms refer to a collaborative situation where several people work together on the same product (business object)

The word product is used because product development and product lifecycle management are typical examples

  • Pilot examples:

  • EADS NCPD pilot

  • INTRACOM PPM pilot


Athena interoperability profiles aips

ATHENA Interoperability Profiles (AIPs)


Interoperability profile

Interoperability profile

An interoperability profile means a collection of ATHENA generic solutions that work together to solve a set of meaningful interoperability generic problems (interoperability issues).


Development of interoperability profiles

ATHENA Knowledge Base

(implemented in Protégé)

Development of interoperability profiles

Tool support


Athena interoperability profiles aips1

ATHENA Interoperability Profiles (AIPs)


Application of the aif

Application of the AIF


Inventory visibility and interoperability iv i introduction

Specification and

Implementation Assistant

Data Types Requirements

From fragmented disjoined specifications …

Inventory Visibility and Interoperability (IV&I) - Introduction

… to model based views required for specification and implementation


Objectives for application

Objectives for application

  • Completeness: Identification of all critical items to be covered into the model

  • Time: Duration for determining the right modelling approach

  • Adaptability: What's happen when the entry point and contingencies are not quite clear


Scope of the application

Scope of the application


Bif profile to be approach

Starting Information Base about the IV&I Business Objectives

BIF profile – To be - Approach

Identify BIF Profile


Bif profile to be result

BIF profile – To be - Result

Process visibility


Application of the aim baseline methodology

Application of the AIM baseline methodology


Eimm integrated into the establishment methodology

EIMM integrated into the Establishment Methodology

Enterprise Model

(Execution and continuous improvement of enterprise model supported collaboration processes)

Model Quality

Deducing the Modelling Approach

&

the Methodology

ModellingParameter

Business Scope of Modelling Task

Assessment according to the Enterprise Interoperability Maturity Model (EIMM)

Enterprise Maturity

Current & Future

BIF Profile


Mapping bif to eimm approach

Mapping BIF to EIMM - Approach

Identified EIMM detailed Categories

Identified BIF Profile


Bif eimm mapping result

BIF – EIMM Mapping - Result


Mapping to modelling concept target

Mapping to Modelling Concept - Target

Focuses on the level of detail of the collaboration that should be regarded. Here the Enterprise Aspects are covered - as now included into the ISO 19440 „Constructs for Enterprise Modelling

Aims at supporting the user to achieve an accurate visualisation of the interested aspects.

Perspective of the model. The idea is to focus the different requirements for the model that can be deduced from the scope


Mapping eimm to modelling parameters

Mapping EIMM to Modelling Parameters

Deducing

Example


Application of the aim baseline methodology1

Application of the AIM baseline methodology


Approach perform functional analysis based on aif railroad and required interoperability functions

Approach – Perform Functional Analysis based on AIF Railroad and required Interoperability Functions

AIAG Scenario

ATHENA Railroad

Business Needs

and Requirements

DRDS Knowledge Base

Interoperability Functions

List of generic functions


Functional analysis result for aiag scenario

Model related Solutions

Create Model

Execute Model (transform data)

Transform Model horizontal/

Transform Model vertical)

Enrich models

Create compatible views of a model

Mapping of data in models

SW Component related solution

Searching

Selecting

Invocation

Analysis and Testing

Assessment

conformance test,

logic test

performance test

Search for content

Connectivity

Naming

Provide Connection

Routing (messages and models)

Functional Analysis – Result for AIAG Scenario


Application of the aim baseline methodology2

Application of the AIM baseline methodology


Requirements solutions mapping1

Requirements – solutions mapping

Functions


Project a4 claudia guglielmina txt e solutions arne j rgen berre sintef

Context elements modelled in Protégé – Business needs and Generic solutions are annotated with these classes


Example mapping generic to specific solution

Example - Mapping Generic to Specific Solution


Mapping solution summary

Mapping Solution - Summary


Concluding remarks on aif application in the iv i pilot

Concluding remarks on AIF application in the IV&I pilot

  • Completeness: Identification of all critical items to be covered into the model – By applying BIF and EIMM the precision of the to-be modelling concept was very convincing e.g. some aspects were not foreseen in before hand by using traditional approaches

  • Time: Duration for determining the right modelling approach - Elaboration of Modelling Concept based on BIF and EIMM was quite fast – less than 1hour

  • Adaptability: What's happen when the entry point and contingencies are not quite clear – e.g.Functional Analysis and Assessment were done in parallel  Methodology parts needs to be more modular and need a more precise architecture for that


Validation of results

Validation of results


Validation methodology deliverable d a4 6

Validation methodology [Deliverable D.A4.6]

The methodology used for the validation of the other A4 results has been adapted to the theoretical nature of the AIF. Instead of the Athena Requirements and the Business needs used for the validation of the A4 tools, the AIF Success Criteria have been applied. In this context no quantitative measurement has been achieved but only qualitative variables:


Validation results

Validation results

The identified gaps either in integrating ATHENA solutions for providing an end to end solution to a scenario or in providing a missing functionality is a valuable feedback and input to future research activities aiming at the AIF improvement and enrichment


Conclusion and future work

Conclusion and future work


Claimed results and major contributions

Claimed results and major contributions

  • ATHENA Interoperability Reference Architecture

  • Specification of the ATHENA Interoperability Framework

  • ATHENA Interoperability Methodology (AIM)

  • ATHENA Interoperability Profiles and Dynamic Requirement Definition

  • Interoperability Project Support Suite

  • Process-based Interoperability Infrastructure

  • Product-based Interoperability Infrastructure


Future work

Future work

  • Towards an operational solution on the Web

  • Definition and implementation of interoperability service utilities (ISUs)

  • Refinement of interoperability profiles

  • Input to the development of the European Interoperability Framework (EIF)


Thank you

Thank you


  • Login