1 / 58

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.

randy
Télécharger la présentation

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. 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)

  3. 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

  4. Presentation outline and speakers

  5. ATHENA Interoperability Framework (AIF)

  6. 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

  7. 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.

  8. Specification and development of the AIF

  9. ATHENA Interoperability Reference Architecture

  10. AIF – Conceptual integration

  11. 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.

  12. Interoperability framework

  13. Interoperability reference architecture

  14. Interoperability modelling

  15. AIF – Applicative integration

  16. ATHENA Interoperability Methodology (AIM)

  17. Baseline methodology

  18. Requirements – solutions mapping

  19. ATHENA Knowledge Base (implemented in Protégé)

  20. ATHENA Knowledge Base (implemented in Protégé) ATHENA Interoperability Methodology (summary) [Deliverable D.A4.5] Tool support

  21. AIF – Technical integration

  22. Technical architecture

  23. Technical architecture – Services

  24. Example configuration and implementation

  25. 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

  26. 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

  27. ATHENA Interoperability Profiles (AIPs)

  28. 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).

  29. ATHENA Knowledge Base (implemented in Protégé) Development of interoperability profiles Tool support

  30. ATHENA Interoperability Profiles (AIPs)

  31. Application of the AIF

  32. 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

  33. 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

  34. Scope of the application

  35. Starting Information Base about the IV&I Business Objectives BIF profile – To be - Approach Identify BIF Profile

  36. BIF profile – To be - Result Process visibility

  37. Application of the AIM baseline methodology

  38. 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

  39. Mapping BIF to EIMM - Approach Identified EIMM detailed Categories Identified BIF Profile

  40. BIF – EIMM Mapping - Result

  41. 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

  42. Mapping EIMM to Modelling Parameters Deducing Example

  43. Application of the AIM baseline methodology

  44. 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

  45. 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

  46. Application of the AIM baseline methodology

  47. Requirements – solutions mapping Functions

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

  49. Example - Mapping Generic to Specific Solution

  50. Mapping Solution - Summary

More Related