1. 1 © ATHENA Consortium 2007 ATHENA Put in Perspective Rainer Ruggaber, SAP Arne Berre, SINTEF ATHENA M36 Final Review 27.-29. March 2007 Madeira, Portugal

2. 2 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 By 2010, enterprises will be able to seamlessly interoperate with others no interoperability Seamless interoperability 2010 past Main Objective: Contribution to enabling enterprises to seamlessly interoperate with others ATHENA

3. 3 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Interoperability Definition ● Interoperability (Def): “the ability of two or more systems or components to exchange information and to use the information that has been exchanged” (IEEE Standard Computer Dictionary) Seamless (Def): “perfectly consistent and coherent” (WordNet) “not having or joined by a seam or seams” (WordNet)

4. 4 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Outline ● From IDEAS to ATHENA ● Motivation – Interoperability ● ATHENA Set-up ● ATHENA Organizational Approach ● ATHENA Technical Approach ● ATHENA Results ● ATHENA Evaluation

5. 5 © ATHENA Consortium 2007 From IDEAS to ATHENA ATHENA M36 Final Review 27.-29. March 2007 Madeira, Portugal

6. 6 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Timeline of Enterprise Interoperability Activities 20022003200420052006 IDEAS ATHENA IP 2007 … ATHENA Prep other research activities INTEROP NoE EIC INTEROP Vlab INTEROP Prep Enterprise Interoperability Cluster and Enterprise Interoperability Roadmap

7. 7 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Framew ork 1st Level Framew ork 2nd Level ONTOLO GY QUALITY ATTRIBUTES Semanti cs Secur ity Scalabi lity Evolu tion ENTERPR.MODELENTERPR.MODEL Busines s Decision al Model Business Model Business Processe s Knowle dge Organisa tion Roles Skills Compete ncies QUALITY ATTRIBUTES Knowled ge Assets Perform ance Availa bility Portabi lity ARCHITECTARCHITECT Applicat ion Solution Manage ment Workplac e Interacti on Applicati on Logic Process Logic DataProduct Data Process Data Knowled ge Data Commer ce Data Commu nication IDEAS Interoperability framework Enterprise Model Architecture Semantics

8. 8 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Building on IDEAS foundations ● IDEAS Interoperability Framework ● IDEAS Roadmap as base for identification of Research Challenges Business Knowledge ICT Systems Semantics Simplified IDEAS Interoperability Framework used in ATHENA ● Business layer : business environment and business processes ● Knowledge layer : organisational roles, skills and competencies of employees and knowledge assets ● ICT Systems layer : applications, data and communication components ● Semantics : create mutual understanding on all layers

9. 9 © ATHENA Consortium 2007 Motivation - Interoperability ATHENA M36 Final Review 27.-29. March 2007 Madeira, Portugal

10. 10 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Situation description – Interoperability ● Interoperability is strategically important ● Over 90% of CIOs consider Collaboration a “ Strategic Necessity ” or “ Very Important ” (AMR Research 2005) ● Interoperability is expensive ● 30-40% of companies’ IT budget is spent on integration (Gartner and AMR) ● $29 billion by 2006 for application integration by IT professional services (Gartner Group, 2003) ● Interoperability is time-critical ● Integration of single Interface takes 2PM on average ● In CPG the #2 to market sells 25% less than #1 ● Interoperability is complex ● Proliferation of B2B standards – with frequent changes ● Fragmented solutions - Islands of interoperability providing Industry or application specific solutions ● Wide variety of business network types with different requirements: more stable alliances (e.g. Supply Chains) to more transitory alliances (e.g. virtual organizations) ● Interoperability is not a product, it is a characteristic of a system

11. 11 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Challenges in Enterprise System Interoperability Today‘s situation in integration projects Therefore, there is a need to take a fresh look at interoperability and propose an integrated, holistic approach to address this problem. ATHENA is addressing this topic. Proprietary data formats without semantics, many incompatible standards; hard coded transformations Information Processes embedded in application logic; modeling tools mainly for drawing; disjoint B2B process modeling; programmatic integration Processes Capturing Enterprise Knowledge is too time consuming and expensive; no exchange of models; models and reality often not synchronized Enterprise Modelling Consensus efforts do not tap their full potential in industry usage Community Static definition & usage; current WS standards landscape not interoperable Services Incomplete models for value assessment of interoperability projects Business

12. 12 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 technical standardisation content standardisation taken from Shai Agassi, SAP FKOM 05 Focus on optimizing operation of interoperability Focus on using interoperability for differentiation

13. 13 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Towards a Process of Interoperability Starting point is the desire of two enterprises to work together. Before they are able to work together they have to go through a process to achieve interoperability. Gaps Identified Collaboration Context Decision to evaluate collaboration Decision to realize collaboration Interoperable Solution ImplementationAnalysisDefinition Operation Identify Interoperability Situation Resolve Interoperability Mismatches Implement Interoperability Solution Maintain Interoperability Decision to go operational Decision to create solution Set-Up … …

14. 14 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Approaches for the “Definition” Step Enterprise A Bottom up: Top down: Collaboration space: Standards, best practices Enterprise A Enterprise B

15. 15 © ATHENA Consortium 2007 ATHENA Set-up ATHENA M36 Final Review 27.-29. March 2007 Madeira, Portugal

16. 16 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Decomposition of ATHENA Objectives Overall Objective Business Objectives Strategic ObjectiveS&T Objectives AL A ProjectsAL B Activities contribution achieve Technical results Business results Strategic results Means/ Actions

17. 17 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Business Objectives* ● to realise more economic businesses through improvements in efficiency, productivity and cost effectiveness; ● to realise more flexible, fluid and nimble businesses which are able to move into new markets and product areas rapidly; ● to realise more knowledge-intensive businesses which are based on the wide diffusion and re-use of knowledge assets; ● to realise more robust businesses through stable and dependable solutions which are scalable and recoverable; ● to realise more valuable businesses from a long term and more general perspective * objectives have been set for the 5 year programme

18. 18 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Scientific and technology objectives* ● to define a technologically neutral reference model that provides a stable, generic foundation for specific technical innovations; ● to define interoperability requirements for applications, data and communications and provide solutions that meet these requirements; ● to provide methods which enterprises can use to manage organisational roles, skills, competencies, and knowledge assets for its own operation and for collaboration with other enterprises; ● to provide semantic mediation solutions which enable and support the above; ● to provide components of interoperability infrastructures * objectives have been set for the 5 year programme

19. 19 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Strategic Objective* * objectives have been set for the 5 year programme ● to establish, become and be recognised in research and industry as a permanent world-class European Hub acting as a reference point in interoperability.

20. 20 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Identification of research challenges Business Knowledge Systems year 1year 2year 3year 4year 5 persistent services business process ontology process model interoperability modeling cross- organizational business processes Unified Paradigm Interoperability Infrastructure Federated Paradigm Interoperability Infrastructure Flexible Enterprise & Process Customisation Support networked EM language\ Enterprise Visual Scenes/Holistic Enterprise Design and Operation roles and policies enterprise model interoperability (distributed) model generated solutions and work places service description Service discovery service negotiation Cross-organizational Business Process Execution Semantic Mapping & Mediation Autonomous Architectures Model Driven SoA Active Models Federated Architectures Non- functional Interoperabili ty semantic annotation ontology authoring and management Networked Enterprise Operation Support service orchestration service brokering & mediation Integrated Paradigm Interoperability Infrastructure

21. 21 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Defined Projects and Activities Action Line A: Research A1Enterprise Modelling in the Context of Collaborative Enterprises A2Cross-Organisational Business Processes A3Knowledge Support and Semantic Mediation Solutions A4Interoperability Framework and Services for Networked Enterprises A5Planned and Customisable Service-Oriented Architectures A6Model-driven and Adaptive Interoperability Architectures A7 Business Documents and Protocols A8 SME Interoperability in Practice Action Line B: Community Building B1Community Creation and EIC Establishment B2Knowledge Sharing B3Business Interoperability Research B4Dynamic Requirement Definition B5Piloting including Technology Testing Coordination and Pilot Infrastructure B6Training Action Line C: Management C1Programme Administration C2Scientific Coordination C3Exploitation C4IT Integration

22. 22 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 ATHENA - Consortium Technology Providers Industry Partners Academic / Research Partners University St. Gallen

23. 23 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Involved Research Communities Business Process Management ATHENA Integrated Project Enterprise Modeling Web Services Model-Driven Architecture Business / Economic Research Semantics

24. 24 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 ATHENA Industry Pilots ● AIDIMA ● eProcurement in the SME Furniture Industry ● CR FIAT ● Strategic Sourcing in the Automotive Industry ● EADS CCR ● Collaborative Product Design in the Aerospace Industry ● INTRACOM ● Product Portfolio Management in the Telecommunication Equip. Industry ● AIAG ● Inventory Visibility in the Automotive Industry ● CAS ● Vehicle Configuration in the Automotive Industry

25. 25 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 ATHENA Programme Building Blocks Requirements Piloting / Testing Community Building B4, B3 B5 B1,B2,B3, B6,C3 Research & Technology Development A1-A8

26. 26 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 “Research Guiding and Evaluation Cycle” Requirements Analysis Research Pilots Validation Refined Requirements Methodology, Guidelines, Reference Architectures Scenario

27. 27 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 CATS – Cross-Action Line Teams ● Created in the first year of ATHENA to improve collaboration between AL A and AL B ● Goal to support definition and set-up of the Pilots ● Originally 4 CATS have been established ● Assigned to pilot ● Pilot owner is leading the CATS ● AL A representatives

28. 28 © ATHENA Consortium 2007 ATHENA Organisational Approach ATHENA M36 Final Review 27.-29. March 2007 Madeira, Portugal

29. 29 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Adapting 1: Implementation Plan Updates ● Update in M12 ● New Projects planned (A7, A8, A1 Extension) ● Improved and adapted the number of deliverables and subproject calls ● Update in M24 ● reclassification of Deliverables ● minor re-allocations of resources and refocusing of projects / activities ● Goal: Revisit the DoW, keep it “alive”

30. 30 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Adapting 2: Calls for new project partners ● B3 open call ● Goal: “contributions in the space of Business Interoperability Framework and Interoperability Impact Assessment” ● INSEAD and University of St. Gallen formally joined the ATHENA consortium in M18 ● B5-1, B5-2 open calls ● Goal of B5-1: Outbound Logistics ● Goal of B5-2: Inventory Visibility ● Overall 15 proposals received ● Review of the proposals by at least two independent reviewers ● For B5-1: CAS, AVAG, SMC formally joined the ATHENA Consortium in M25 ● For B5-2: AIAG, FOS formally joined the ATHENA Consortium in M25 ● Conclusion: worth the effort for the project

31. 31 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Project / Sub-project Schedules A1 M1 M12M24M36 A2 A3 A4 A5 A6 A7 A8 B5 Sub-Proj. 1 B5 Sub-Proj. 2 B3 Sub-Proj. Updated Implementation Plan B5 Sub Project Calls B3 Sub Project Call “Original” ATHENA A1’ C4’

32. 32 © ATHENA Consortium 2007 ATHENA Technical Approach ATHENA M36 Final Review 27.-29. March 2007 Madeira, Portugal

33. 33 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 ATHENA Big Picture – Abstract View Enterprise AEnterprise B Business Business Processes Services Information / Data Semantics Mismatches prohibit interoperability Vision: Seamless Interoperability of Business Systems and Applications to enable collaboration Approach: Interoperability must address all aspects of Enterprise collaboration

34. 34 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Organization B ATHENA Big Picture - External Views Organization A Internal View private interaction – ensures autonomy of participants public interaction – ensures interoperability by defining a collaboration context External View

35. 35 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 ATHENA Interoperability Reference Architecture (A4) with ATHENA technical solutions to bridge the gap A4 – Interoperability Framework A8 – SME Interoperability in Practice A6 A3 A1 A2 A5 A7 A6

36. 36 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 ATHENA Interoperability Methodology (AIM)

37. 37 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 ATHENA Interoperability methodology (AIM)

38. 38 © ATHENA Consortium 2007 ATHENA Results ATHENA M36 Final Review 27.-29. March 2007 Madeira, Portugal

39. 39 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Original ATHENA Key Results ATHENA: Contribute to enabling enterprises to interoperate. Technical Results 6, 7, 8 – ATHENA Interoperability Framework: Reference Architecture, Interoperability Infrastructure, Guidelines and Best Practices 9 - Collaborative Enterprise Modelling Platform 10 - Cross-Org. Business Process Modelling and Enactment 11 - Ontology-based Semantic Annotation and Reconciliation method/language/tool 12 - Service Composition Framework 13 - Model-driven and Adaptable Interoperability Framework and Infrastructure Strategic Results 3 - Interoperability Impact Assessment 4 - Policy Action Recommendations 5 - Enterprise Interoperability Centre (EIC) Business Results 1 - Business Interoperability Framework 2 - Interoperability requirements for applications

40. 40 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Updated ATHENA Key Results (D.C2.2 – M37) ATHENA: Contribute to enabling enterprises to interoperate. Technical Results 6 - ATHENA Interoperability Framework and Methodology 7 - Collaborative Enterprise Modelling Platform 8 - Cross-Organisational Business Process Modelling and Enactment 9 - Ontology-based Semantic Annotation and Reconciliation method/language/tool 10 - Adaptive and Service Oriented Infrastructure 11 - Model-driven and Adaptable Interoperability Framework Strategic Results 4 - Enterprise Interoperability Centre (EIC) 5 - ATHENA Outreach Business Results 1 - Business Interoperability Framework 2 - ATHENA Applications in Industry 3 - Interoperability Impact Assessment

41. 41 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 ATHENA Key Results and Contribution Areas Business Document Mgmt. Required Provided Cross-OrganisationalBusiness Processes CollaborativeEnterprise Modelling Flexible Execution andComposition of Services Data Transformation Model-Driven Development Information Services Processes Enterprise Modelling Ontologies and Semantic Information Services Processes Enterprise Modelling Policy Action Recommendations Interoperability Impact Assessment Model - IIAM Business Interoperability Framework - BIF ATHENA Applications in Industry Enterprise Interoperability Center - EIC ATHENA Conference – i-ESA Business Results Strategic Results “Community Building” Technical Results Business Interoperability Industry Policy Community Technology

42. 42 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Process towards interoperability Agent Modelling and Execution CBP Modelling Service Modelling Model Transformation Data Mapping Enterprise & Business Modelling tools MPCE with POP* files Semantic Reconciliator Data Mapping EM/CIM --> PIM mapping ImplementationAnalysisDefinition CBP simulation Business Process Enactment Enterprise & Business Modelling tools Process View / Private Process Modelling Task/Activity Modelling Model Transformation EM/CIM --> PIM mapping Semantic Annotator Ontology builder BPEL Engine Task/Activity Enactment Enterprise & Business Modelling tools Service Enactment MGWP Runtime Reconciliator Data Instance Mapping Interoperability Assessment Maturity Models Establishment Concepts Gaps Identified Collaboration Context Interoperable Solution

43. 43 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 ATHENA Results (D.C2.2 – M37) – Part 1 Key ResultContributing ATHENA Result 1 - Business Interoperability Framework - Business Interoperability Framework (page 10) 2 -ATHENA Applications in Industry - Inventory Visibility and Interoperability Pilot in the Automotive Industry (page 12) - Vehicle Configuration Pilot in the Automotive Industry (page 14) - Collaborative Product Development Pilot in the Automotive Industry (page 16) - Networked Collaborative Product Development Pilot in the Aerospace Industry (page 17) - eProcurement Pilot in the Furniture Industry (page 19) - Product Portfolio Management Pilot in the Telecommunication Equipment Industry (page 21) - ATHENA Technical Solutions (page 22) - Provisioning Model for SME Interoperability Services (page 23) 3 - Interoperability Impact Assessment - Interoperability Impact Assessment (page 11) 4 - Enterprise Interoperability Centre (EIC) - Enterprise Interoperability Centre (EIC) (page 24) 5 - ATHENA Outreach - ATHENA Conference (page 26) - Visibility and Awareness Created (page 28) - Policy Action Recommendations (page 29) - ATHENA Interoperability Training (page 30) 6 - ATHENA Interoperability Framework and Methodology - ATHENA Interoperability Framework (AIF) (page 31) - Dynamic Requirement Definition Approach (page 32) - Testing Methodology (page 34)

44. 44 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 ATHENA Results (D.C2.2 – M37) – Part 2 Key ResultContributing ATHENA Result 7 - Collaborative Enterprise Modelling Platform POP* Language Interchange Format and Methodology (page 35) MPCE Modelling Platform for Collaborative Enterprises (page 36) EIMM Enterprise Interoperability Maturity Model (page 37) Interoperability Establishing Methodology for SMEs (page 38) 8 - Cross-Organisational Business Process Modelling and Enactment Modelling Cross-organisational Business Processes in ARIS and MO²GO (page 39) Cross-organisational Business Processes Modelling Tool (Maestro) (page 40) Cross-organisational Business Process Engine (Nehemiah) (page 41) Task Management Engine (see page 42) ATHENA Event and Document Correlation (AEDoC) (page 43) Service Enablement of Cross-Organisational Business Processes (Gabriel (page 44) Business Document Modelling (page 45) Mapping of Business Documents (page 46) Repository for Business Documents (page 47) Business Protocol Support (page 48) 9 - Ontology-based Semantic Annotation and Reconciliation method/language/tool ATHENA Ontology Management System (ATHOS & OPAL) (page 49) ATHENA Semantic Annotation System (A*) (page 50) ATHENA Reconciliation Rule Generator (ARGOS) (page 51) ATHENA Reconciliation Engine (ARES) (page 53) Management of RDF Schemas (THEMIS) (page 54) XML-to-RDF-to-XML Transformations (X2R2X) (page 55) 10 - Adaptive and Service Oriented Infrastructure Perspectives in Service-Oriented Architectures and their Application in Environments that Require Solutions to be Planned and Customisable (page 56) Semantic support for the description and modelling of the service description framework (page 57) Service Execution Framework (Johnson/Lyndon) (page 58) WSDL Analyzer (page 59) JACK Autonomous Agents Framework (page 60) ATHENA Conformance Testing Suite (page 62) WS-I Compliant Web Service Security (page 64) 11 - Model-driven and Adaptable Interoperability Framework Model-driven development (MDD) framework for Web Services (page 65) Model-Driven and Adaptive Interoperability Runtime Tools and Services (page 66) CIM to PIM Transformations (page 68) UMT2OWLS Transformation (page 70) PIM4SOA Metamodels (page 71) PIM to PSM Transformation (page 72) Model-Driven and Adaptive Interoperability Development Tools (page 73) ATHENA Autonomous Computing Framework (page 74) Model-Driven and Adaptive Interoperability Runtime Tools and Services (page 75) Model-Driven and Adaptive Interoperability Methodologies and Guidelines (page 77)

45. 45 © ATHENA Consortium 2007 ATHENA Evaluation ATHENA M36 Final Review 27.-29. March 2007 Madeira, Portugal

46. 46 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Validation of ATHENA Research Results Scenario Level ● Goal: Validate that the Research Results meet the requirements of an application in industry ● Carried out on the level of the Pilot ● Documented: D.B5.4 (M36) Technical / Research Level ● Goal: Validate that the Research Results meet the requirements of the AL A project set out in the beginning ● Carried out on the level of the individual AL A project ● Documented: D.A1.6.1 (M24), D.A2.5 (M24), WD.A3.2 (M36), D.A4.6 (M36), D.A5.5 (M24), WD.A6.7.1 (M24)

47. 47 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Expectations for Scenario-Level Validation ● Research ● Goal: Realize a novel research concept as a prototypical implementation / tool ● Constraints: Integration with other tools, Usability ● Piloting ● Goal: Realize an industry use case using multiple tools ● Constraint: Industrial users use the tools; Demo Deployment environment ● Industry Application ● Goal: Realize a business application ● Constraint: industry strength and industry level infrastructure / deployment environment

48. 48 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 ATHENA Objective was … ● … contribute to enabling enterprises to seamlessly interoperate with others or in other words … ● “better interoperability” ● “better” could mean cheaper, faster, economic to realize a new process, easier, … ● B3 and Pilot evaluations show ● ATHENA contributes to ● easier integration of additional business partners (e.g. CRF) ● improved quality of business collaboration (e.g. AIDIMA) ● lower cost of set-up of interoperability (e.g. AIAG) ● faster set-up of interoperability (e.g. CRF) ● realize new business opportunities (e.g. CAS) ● lower cost for operation of interoperable solutions (e.g. AIDIMA) ● leveraging knowledge for improved decision making (e.g. INTRACOM)

49. 49 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Approaches for the “Definition” Phase Enterprise A Bottom up: Top down: Collaboration space: Standards, best practices Enterprise A Enterprise B INTRACOM CAS CRM AIDIMA Documents AIAG EADS infrastructure CRF Documents CAS Config EADS Process CRF Process AIDIMA Process

50. 50 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 technical standardisation content standardisation taken from Shai Agassi, SAP FKOM 05 AIAG CAS AIDIMA CRF INTRACOM EADS

51. 51 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Business Objectives* (revisited) ● to realise more economic businesses through improvements in efficiency, productivity and cost effectiveness; ● to realise more flexible, fluid and nimble businesses which are able to move into new markets and product areas rapidly; ● to realise more knowledge-intensive businesses which are based on the wide diffusion and re-use of knowledge assets; ● to realise more robust businesses through stable and dependable solutions which are scalable and recoverable; ● to realise more valuable businesses from a long term and more general perspective * objectives have been set for the 5 year programme ● optimize operation of interoperability ● reduce time in the set-up phase ● enterprise assets are explicitly modelled for later reuse ● improvements with respect to robustness possible ● understand the business value of interoperability and have a method to improve it

52. 52 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Scientific and technology objectives* (revisited) ● to define a technologically neutral reference model that provides a stable, generic foundation for specific technical innovations; ● to define interoperability requirements for applications, data and communications and provide solutions that meet these requirements; ● to provide methods which enterprises can use to manage organisational roles, skills, competencies, and knowledge assets for its own operation and for collaboration with other enterprises; ● to provide semantic mediation solutions which enable and support the above; ● to provide components of interoperability infrastructures * objectives have been set for the 5 year programme ● AIF, Reference Architecture and AIM defined ● Industry Scenarios and the DRDS ● Tools for modelling of enterprise assets on different abstraction level. ● ATHENA Semantic Tool Suite ● Full Set of Tool chains addressing different aspects of interoperability

53. 53 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Strategic Objective* (revisited) * objectives have been set for the 5 year programme ● to establish, become and be recognised in research and industry as a permanent world-class European Hub acting as a reference point in interoperability. ● EIC was founded and had its launch event (27. April 2007, Brussels) ● Additional EIC Forums providing value to members to be set-up ● ATHENA Outreach (Dissemination, Training, …)

54. 54 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 By 2010, enterprises will be able to seamlessly interoperate with others no interoperability Seamless interoperability 2010 past ATHENA has achieved its objective by enabling enterprises to connect and link up their systems …. Still, new research questions remain: ATHENA Dynamic, automatic Interoperability Interoperability in enterprise networks with new, changing, and previously unknown partners Retain Interoperability in times of change

55. 55 © ATHENA Consortium 2007 Thank You ATHENA M36 Final Review 27.-29. March 2007 Madeira, Portugal

56. 56 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Dimension 2: Conceptual levels ● Multiple stakeholders are involved in collaborations: ● Business Expert ● IT Architect ● Administrator ● Support stakeholders by appropriate views of the collaboration: ● Business Expert - Business View ● IT Architect- Technical View ● Administrator-Execution View ● Views are realized through abstraction levels ● Business View - Business level (~ CIM / EM) ● Technical View- Technical level (~ PIM) ● Execution View- Execution level(~ PSM)

57. 57 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 AIF Technical architecture

58. 58 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 AIF Technical architecture – Services

59. 59 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 AIF - Example configuration and implementation

60. 60 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 ATHENA Interoperability Methodology (AIM)

61. 61 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 AIM Baseline methodology

62. 62 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 other targets (e.g. agents, P2P) BPEL Nehemiah MM WSDLXSD ATHENA Integrating Dimensions POP* SOA Meta Model Business Level (~EM/CIM) Technical Level (~PIM) Execution Level (~PSM) Business Process Services Information / Data Transformation other Aspects Nehemiah Johnson MaestroLyndonGabriel MPCE UML Profile ATHOS A* ARGOS ARES Semaphore ARIS- SOA MM MO²GO – SOA MM POP* – SOA MM Testing METISMO²GOARIS GRAI MGWP BDI AgentsBRMF SOA MM - WSDL AKM Exec UML Profile WSDL Analyser POP* PIM4SOA SOA MM - BDI SOA MM - BPEL STEP - SOA MM BPEL Eng

63. 63 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 other targets (e.g. agents, P2P) BPEL Nehemiah MM WSDLXSD Demonstration 1: Definition and management of the Collaboration Space POP* SOA Meta Model Business Level (~EM/CIM) Technical Level (~PIM) Execution Level (~PSM) Business Process Services Information / Data Transformation other Aspects Nehmiah Johnson MaestroLyndonGabriel MPCE UML Profile ATHOS A* ARGOS ARES Semaphore ARIS- SOA MM MO²GO – SOA MM POP* – SOA MM Testing MO²GOARIS GRAI BDI AgentsBRMF SOA MM - WSDL UML Profile WSDL Analyser PIM4SOA SOA MM - BDI SOA MM - BPEL BPEL Eng STEP - SOA MM METIS AKM Exec POP* MGWP AKM Execution platform as the access point for the networked organization Projects: A1, A6, A4 with links to all AL A projects

64. 64 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 other targets (e.g. agents, P2P) BPEL Nehemiah MM WSDLXSD Demonstration 2: Support collaboration of actors (business partners, IT department, external consultants) POP* SOA Meta Model Business Level (~EM/CIM) Technical Level (~PIM) Execution Level (~PSM) Business Process Services Information / Data Transformation other Aspects Nehmiah Johnson MaestroLyndonGabriel UML Profile ATHOS A* ARGOS ARES Semaphore ARIS- SOA MM Mogoo – SOA MM POP* – SOA MM Testing MGWP BDI AgentsBRMF SOA MM - WSDL WSDL Analyser PIM4SOA SOA MM - BDI SOA MM - BPEL AKM Exec BPEL Eng STEP - SOA MM POP* MPCE MO 2 GOARIS GRAIUML Profile METIS POP* and MPCE for horizontal and vertical exchange of Enterprise Models Project: A1

65. 65 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 other targets (e.g. agents, P2P) BPEL Nehemiah MM WSDLXSD Demonstration 3: Definition and automation of Change Management Process POP* SOA Meta Model Business Level (~EM/CIM) Technical Level (~PIM) Execution Level (~PSM) Business Process Services Information / Data Transformation other Aspects Johnson UML Profile ATHOS A* ARGOS ARES Semaphore ARIS- SOA MM POP* – SOA MM Testing MGWP BDI Agents SOA MM - WSDL WSDL Analyser PIM4SOA SOA MM - BDI SOA MM - BPEL AKM Exec STEP - SOA MM POP* MPCE ARIS GRAIUML Profile BPEL Eng METIS Nehemiah Johnson MaestroLyndonGabriel MO²GO – SOA MM BRMF Mo 2 go Cross-organisational Business Processes and their Service Enactment including robust execution. Projects: A2, A5, A1, A6

66. 66 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 other targets (e.g. agents, P2P) BPEL Nehemiah MM WSDLXSD Demonstration 4: Meta-Models and Model Transformation to support multiple implementation targets POP* SOA Meta Model Business Level (~EM/CIM) Technical Level (~PIM) Execution Level (~PSM) Business Process Services Information / Data Transformation other Aspects Johnson ATHOS A* ARGOS ARES Semaphore POP* – SOA MM Testing MGWP WSDL Analyser AKM Exec STEP - SOA MM POP* MPCE GRAIUML Profile METIS Nehmiah Johnson MaestroLyndonGabriel Mogoo – SOA MM Mogoo UML Profile ARIS- SOA MM BDI Agents SOA MM - WSDL PIM4SOA SOA MM - BDI SOA MM - BPEL ARIS BRMF BPEL Eng Business level models -> PIM-for-SOA -> PSM models and Flexible enactment using BDI agents. Projects: A6, A1, A5

67. 67 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 other targets (e.g. agents, P2P) BPEL Nehemiah MM WSDLXSD Demonstration 5: Management of Service-Oriented Architectures POP* SOA Meta Model Business Level (~EM/CIM) Technical Level (~PIM) Execution Level (~PSM) Business Process Services Information / Data Transformation other Aspects ATHOS A* ARGOS ARES Semaphore POP* – SOA MM MGWP AKM Exec STEP - SOA MM POP* MPCE GRAIUML Profile METIS Nehmiah MaestroGabriel Mogoo – SOA MM Mogoo UML Profile ARIS- SOA MM BDI Agents SOA MM - WSDL PIM4SOA SOA MM - BDI SOA MM - BPEL ARIS BRMF BPEL Eng Johnson Testing WSDL Analyser Johnson Lyndon Gabriel Flexible service infrastructure providing built-in services and Reconciliation of Service Definition mismatches. Projects: A5

68. 68 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 other targets (e.g. agents, P2P) BPEL Nehemiah MM WSDLXSD Demonstration 6: Identifying and resolving mismatches in product data exchange POP* SOA Meta Model Business Level (~EM/CIM) Technical Level (~PIM) Execution Level (~PSM) Business Process Services Information / Data Transformation other Aspects Semaphore POP* – SOA MM MGWP AKM Exec STEP - SOA MM POP* MPCE GRAIUML Profile METIS Nehmiah MaestroGabriel Mogoo – SOA MM Mogoo UML Profile ARIS- SOA MM BDI Agents SOA MM - WSDL PIM4SOA SOA MM - BDI SOA MM - BPEL ARIS BRMF BPEL Eng Testing WSDL Analyser Johnson Lyndon Gabriel ATHOS A* ARGOS ARES Johnson Using Semantic annotation and reconciliation to resolve mismatches Projects: A3, A5

69. 69 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Three main areas of action (Impl Plan Update M12) ● Implement DoW Changes for ● Content / Resources ● Unlock “frozen” resources (A2/A4) – B4 ● Improve / Adapt /revise ● Scrutinise number and structure of deliverables ● Numbers of Sub-project calls ● Define new projects ● Extension of A1 ● Two project areas planed / resources available (A7, A8)

70. 70 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Implementation Plan Up Date (M24) ● Implementation Plan Up Date after 1. Reporting Period was spanning year 2 and 3 ● Year 2 binding, year 3 to be updated ● Only minor amendments were needed for this Implementation Plan Up Date after 2. Reporting Period ● 23 deliverables were re-classified to be able to provide them to specified recipients after PCC decision ● Several minor resource re-allocation within WP’s or projects or between partners ● New Work Package B5.11 to test the applicability of ATHENA tools in a consensus building process in an EIC Forum ● PGM appreciates clarification for timing of “Due-date / Submission” for deliverables for finalisation of up date

71. 71 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 B5 Sub-Project Calls - I ● Two Calls: ● B5-1 Outbound Logistics ● B5-2 Inventory Visibility ● Call open from 10 October to 17 November 2005 ● Publication via the press, email, web ● Call document downloads: 1.851 ● Expressions of Interest received: ~ 60 ● Proposals received via EPSS: 15 ● Involving 34 organisations with grants requested ranging from 125 T€ to 320 T€. ● Coordinators: 9 OMS, 2 NMS, 2 Ass. C., 1 USA

72. 72 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 B5 Sub-Project Call - II ● Evaluation completed on: 30 November 2005 ● 4 Evaluators in total / 2 per Call ● Retained proposals: ● B 5-1: 37990 CAS, total cost: 648 T€, grant: 313 T€ ● CAS Software AG (Coordinator) ● SMC InformationsTechnologien AG ● AVAG Holding AG ● B 5-2: 37975 AIAG, total cost: 1.100 T€, :grant 320 T€ ● AIAG (Coordinator) ● NIST ● KorBIT ● University of Belgrade

73. 73 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Yearly update of the implementation plan (M12)

74. 74 ATHENA M36 Final Review, March 2007, Madeira © ATHENA Consortium 2007 Tools to be used during different phases (early draft) Analysis Negotiation Realization Document Compare Capability Tables Gap table Collaboration Context CBP Modelling Enterprise & Business Modelling tools EM/CIM--> PIM mapping Ontology Builder Model Transformation Process View / Private Process Modelling Enterprise & Business Modelling tools Task/Activity Modelling EM/CIM--> PIM mapping MPCE with POP* files Semantic Annotator Semantic Reconciliator Runtime Reconciliator Service Enactment Agent Modelling and Execution Business Process Enactment BPEL Engine Task/Activity Enactment Service Modelling MGWP Enterprise & Business Modelling tools Data Mapping CBP simulation Model Transformation Data Instance Mapping Data Mapping