IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05 050714_ATHENA_DC14_M17_v91_rr.doc/RR CONFIDENTIAL Page 1 / 170 Programme Integrating and Strengthening the European Research Strategic Objective Networked business and government Integrated Project / Programme Title Advanced Technologies for Interoperability of Heterogeneous Enterprise Networks and their Application Acronym ATHENA Project No 507849 ATHENA – Project Name Programme Administration ATHENA - Project No C1 Deliverable C1.4 Updated Implementation Plan M13-M36 Work package – C1.4 Leading Partner: SAP Security Classification: e.g. Project Participants (PP) July, 2005 Version 1.0
Transcript
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
3 Participant list ........................................................................................................ 5
7 Detailed Implementation Plan including the “second 18 months” (from month 13 to month 30)........................................................................................................... 6
7.1 Introduction ...................................................................................................................... 6 7.2 Detailed work plan - Implementation Plan Overview....................................................... 7 7.3 Results ............................................................................................................................. 8 7.4 Work planning ................................................................................................................ 12 7.4.1 Gantt Chart overview of the programme ....................................................................... 12 7.4.2 Gantt Charts Action Line A ............................................................................................ 13 7.4.3 Gantt Charts Action Line B ............................................................................................ 16 7.4.4 Gantt Charts Action Line C ............................................................................................ 17 7.5 Graphical presentation of the components.................................................................... 18 7.6 Detailes work description............................................................................................... 19 7.6.1 Deliverable Overview..................................................................................................... 20 7.6.2 Action Line A – Research and Development................................................................. 23 7.6.2.1 Project A1 – Enterprise Modelling in the Context of Collaborative Enterprises ............ 23 7.6.2.2 Project A2 – Cross-Organisational Business Processes............................................... 36 7.6.2.3 Project A3 – Knowledge Support and Semantic Mediation Solutions ........................... 44 7.6.2.4 Project A4 – Interoperability Framework and Services for Networked Enterprises....... 50 7.6.2.5 Project A5 – Planned and Customisable Service-Oriented Architectures..................... 59 7.6.2.6 Project A6 – Model-driven and Adaptive Interoperability Architectures ........................ 69 7.6.2.7 Project A7 – Business Documents and Protocols ......................................................... 79 7.6.2.8 Project A8 – SME Interoperability in Practice................................................................ 87 7.6.3 Action Line B – Community Building.............................................................................. 95 7.6.3.1 Activity B1 – Community Creation and EIC Establishment ........................................... 95 7.6.3.2 Activity B2 – Knowledge sharing ................................................................................... 99 7.6.3.3 Activity B3 – Business Interoperability Research ........................................................ 105 7.6.3.4 Activity B4 – Dynamic Requirement Definition ............................................................ 111 7.6.3.5 Activity B5 – Piloting including Technology Testing Coordination and Pilot Infrastructure122 7.6.3.6 Activity B6 – Training ................................................................................................... 135 7.6.4 Action Line C – Management ...................................................................................... 142 7.6.4.1 Activity C1 – Programme Administration ..................................................................... 142 7.6.4.2 Activity C2 – Scientific Coordination............................................................................ 147 7.6.4.3 Activity C3 – Exploitation ............................................................................................. 150 7.6.4.4 Activity C4 – IT Infrastructure and Integration ............................................................. 155
8 Change descriptions .......................................................................................... 160 8.1 Proposed Changes included in project/activity descriptions of the implementation plan
update .......................................................................................................................... 160 8.1.1 Action Line A................................................................................................................ 160 8.1.2 Action Line B................................................................................................................ 162 8.1.3 Action Line C................................................................................................................ 164 8.2 Proposed Changes to deliverables.............................................................................. 165 8.2.1 Action Line A................................................................................................................ 165 8.2.2 Action Line B................................................................................................................ 166 8.2.3 Action Line C................................................................................................................ 168
9 Resources.......................................................................................................... 169 9.1 Efforts for the last 24 months (M13 to M36) ................................................................ 169 9.2 Budget for the last 24 months (M13 to M36) ............................................................... 170
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Summary This updated detailed implementation plan takes into consideration and reflects changes in
two main areas: Operational changes based on observations from the execution of the implementation plan
with the intention to streamline, eliminate overlap or redundancies and to increase the efficiency with which the project operates. • Most of these changes are results from the change process adapted by the consortium to
introduce changes in the implementation plan in a transparent and controlled manner. • A minor part of the changes was introduced as an proposal by the Programme Management
(Administration and Scientific Coordination) during the update of the full implementation plan. This changes are mainly initiated and motivated by observations from the programme point of view that might not have been visible for individual project managers before. New Projects were foreseen in the programme approach that the ATHENA consortium
decided to take. Two new project have been drafted and discussed in the last months before the review and have reached a maturity that makes it possible to discus them for approval with the consortium and the Commission and the reviewers. The two projects are in the area of • Business documents and protocols • SME interoperability in practice
The consortium has taken all measures to constantly monitor the programme to make sure
that • the ATHENA programme stays relevant, • that results and deliverables are produced and submitted with a high quality level, • that efficiency and effectiveness reaches the highest sustainable level, • that collaboration and cooperation is in accordance with the requirements in such an
endeavour to be successful, • that individual researchers and the whole team develops and retains a high motivation and a
good spirit that is needed when facing the challenges in such a large undertaking. The main goal and prerequisite for the update was to support the objectives defined in the
Annex I of the model contract and to make sure that the contracted results can best be achieved and respective deliverables as formal proof of work submitted to the convenience and acceptance of the Commission and the reviewers.
Insofar non of the results have been altered or modified. The update of the implementation plan contains a number of changes that concern the actual activities to achieve the results and can be summarised as follows • Deliverables have been adapted in respect to their content, timing and number • Projects have been adapted in their structure and • WP hangs due to “progress/changes” in the available technology
The rational for those changes and a brief description is given in section “Change Description”.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
7 Detailed Implementation Plan including the “second 18 months” (from month 13 to month 30)
7.1 Introduction The Commission model contract requests a regular update of the detailed implementation
plan that is part of Annex I of the contract. The Annex III.3 of the contract specifies the – Updating the implementation plan as
follows. The implementation plan shall be updated annually. These annual updates
may concern only the detailed implementation plan. They shall be submitted in
accordance with the principles foreseen in Article II.7 for the submission of
reports. The Commission shall follow the same procedure for approving the
updates of the implementation plan as that foreseen for reports in Article II.8. According to the “Guidance notes for Integrated Projects, IPs […] have to provide a detailed
Implementation Plan (IPs) […] for the next 18 months of the project, using the format, tabulations etc. of the previous 18 months, as included within Annex I to the contract.
The ATHENA consortium complies with this contractual obligations by providing this Implementation Plan update for the first review of the IP after the first reporting period that was defined to be 12 months.
This implementation plan update follows the approach: The introductory part and the overview is reduced to a minimum of repetition since there is
neither a major change in the overall structure of the work nor in the scientific approach to address the research challenges identified in the Annex I.
Nevertheless it was felt necessary despite repeating content of the original plan to have all project description integrated for reasons of completeness and comprehension. The intention of this update is to issue a single document that provides all what is needed for internal and external programme controlling and as a guidance for all who work in the ATHENA programme.
To achieve this the document is structured according to the Annex I as requested by the guidance notes) and present the actual updated implementation plan and list all changes is the “Change descriptions”
Resources are given in Person Years and are representing the consortium decision of allocation as of 15.03. 2005. Resources distribution is largely the same as in the DoW with variations. Some more adjustments will be needed after the finalisation of this implementation plan update, particularly after the allocation of resources to A7 and A8 that are not concluded yet.
The ATHENA project is contracted for a duration of three years. After this implementation plan would end which is after month 30 only another 6 months would be left another implementation plan update. Consequently this implementation plan covers the full remaining time until month 36. It is though the understanding, that the Commission regards only the part of the implementation plan as contractual relevant and binding that is covered by the next reporting period ( month 13 until month 24).
Numbering and structure is maintained as it was established in the Dow / Annex I. Nevertheless it is tried for better readability to provide a compact overview of both the Deliverables and the project Gantt chart each in one section and not distributed over the whole programme.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
The following implementation plan represents the first up date after the first year of implementation it will cover the next one and a half year of the project: • First implementation plan covers months one (01) to months eighteen (18). • The second implementation plan covers months thirteen (13) to months thirty-six (36). • There is an agreement between the PO that the new implementation plan covers the time
until month 36. The contractual fixed time until the 2nd review includes month 13 until month 24.
• Adjustments of the Implementation plan can then be integrated into the last update that would span the last reporting period between months twenty five (25) to months thirty six (36).
Year 1 Year 2 Year 3
Initial Advance
Adjusted Advance
Adjusted Advance
ReportingAccepted Cost
Detailed Workplan
Detailed Workplan
ReportingAccepted Cost
ReportingAccepted Cost
Detailed Workplan
Review Review Review
Period
1
2
3
Final
Figure 1: Projects reporting period and updates of detailed work plan (implementation
plan)
7.2 Detailed work plan – Implementation Plan Overview The detailed implementation plan for the second reporting period will continue to support
ATHENA’s overall objective to contribute to enabling enterprises to seamlessly interoperate with others, by providing reference architectures, methods, and infrastructure components that solve interoperability difficulties, supported by a large, representative European community.
As the structure of the detailed implementation plan is kept the same as before it s referred to the Dow / Annex I for the overview.
The Action Line A that is grouped into projects is temporarily increasing the number of projects from six to eight, by A7 and A8 until projects A1, A2, A5 and A6 are finished. The third year of ATHENA will see then only four projects A3, A4, A7 and A8. Action Lines B and C are more continuous activities and are virtually unchanged.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Results related to Technical Objectives on Business
• (A2) Modelling method for cross-organisational business processes (CBPs)
• (A1) Views and constructs to represent collaborative enterprises
• (A1) Common collaborative enterprise repository definition
• (A2) CBP modelling tool • (A1) Service definition for collaboration,
synchronisation on demand and management of different distributed enterprise models
• (A1) Collaborative enterprise modelling platform first version
• (A4) Specification and implementation of business interoperability services
• (A5) Specification and modelling of service composition framework
Results related to Technical Objectives on Knowledge /Semantics
• (A3) SoA and Technical specifications of Ontology Authoring and Management System, with Ontology Modelling Language
• (A2) Semantic annotations for business processes
• (A3) Ontology Authoring and Management System for Informational knowledge and Business Processes
• (A3) System for reconciliation rules definition, storage, and management
• (A3) A reconciliation and mediation engine, capable to efficiently process semantic mediation and reconciliation rules
• (A3) Extension of the Semantic Annotation language and tool for business processes
• (A3) Semantic annotation language, method and supporting tool for business information
• (A5) Modelling and specification framework for expressing semantics in SoAs
• (A5) Service brokering & negotiation framework and protocols
• (A6) Agent-based mapping, matchmaking and mediation of services
• (A2/A6) Integration of non-functional aspects in interoperability infrastructures and business processes
Results related to Technical Objectives on ICT / Systems
• (A5) Models of service description and usage
• (A6) Specification of basic architecture reference model for a model-driven and adaptive interoperability architecture and enhanced repository infrastructure
• (A2) Architecture and execution platform for CBPs
• (A1) Collaborative enterprise modelling platform • (A5) Execution framework for planned and
customisable SoAs • (A5) Model and Specification of service
description and usage as well as advanced concepts
• (A5) Service composition framework • (A6) Model-driven and Adaptable
Interoperability Framework and Infrastructure
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Figure 2 provides and overview of the programme on project level. The individual project descriptions contain a Gantt chart that breaks down the project activities in detail. 7.4.1 Gantt Chart overview of the programme
Nr. Proj. Proj./Activi ty Name1 A T H E N A
2 A Action Line A: Research Coordination
3 A1 Enterprise Modelling in the Context of Collaborative Enterprises
4 A2 Cross-Organizational Business Processes
5 A3 Knowledge Support and Semantic Mediation Sol utions
6 A4 Interoperability Framework and Servi ces for Networked Enterpri ses
7 A5 Planned and Customisable Service-Oriented Architectures
8 A6 Model-driven and Adaptive Interoperabil ity Architectures
9 Projects to be defined for the research areaS10 Future proj ects11 B Action Line B: Community Building Coordination
12 B1 Community Creation and EIC Establi shment
13 B2 Knowledge Sharing
14 B3 Business Interoperability Research
15 B4 Dynamic Requi rement Definition
16 B5 Pil oting Includi ng Technology Testing Coordinati on and PilotInfrastructure
Nr. WP/Task Tit le1 A1 Enterprise Modelling in the Context of
Collaborative Enterprises2 A1.1 State of the Art – of industrial EM
approaches to support enterprise3 A1.2 Requirements for model driven
collaborative enterprises and use-cases4 A1.3 Collaborative Enterprise Modelling
languages and constructs5 A1.4 Establishing and Management
Methodology of model driven6 A1.5 Development of Enterprise Modelling
platform to enable and manage7 A1.6 Validation of results8 A1.7 Project Management9 A1.8 Revise the POP* framework10 A1.9 Develop the MPCE for complete EM excha11 A1.10 Converging and harmonise the EIMM
Nr . WP/Task Tit le1 B3 Business Interoperability Research2 B3.1 Business Interoperability Framework3 B3.2 Merged with WP.B3.14 B3.3 Coordination with External Initiatives5 B3.4 Long Term Requirements, Impact
Nr. WP/Task Vorgangsname1 B 4 Dynamic Requirement Definition2 B4.1 Initialisation3 B4.2 DRD System Development4 B4.3 Global Processes Development5 B4.4 Scenarios Identification and Development
Nr. WP/Task Vorgangsname1 B5 Piloting including Technology Testing
Coordination and Pilot Infrastructure2 B5.1 Technology Testing Coordination3 B5.2 Sub Project Call Preparation and
Management4 B5.3 Integration and Prototyping Services5 B5.4 Aerospace Piloting6 B5.5 Automotive Piloting7 B5.6 Furniture Piloting8 B5.7 Telecom Piloting9 B5.8 Pilots in other areas10 B5.9 Outbound Logistics based Pilot11 B5.10 Inventory Visibility based Pilot
Nr. WP/Task Vorgangsname1 C2 Scientif ic Coordination2 C2.1 Technology Council3 C2.2 Action Line Coordination 4 C2.3 Domain Competence Team5 C2.4 User Group Watch Dog
Nr. WP/Tas k Vorgangsnam e1 C3 Exploitation 2 C3.1 Exploitation Planning and Organisation3 C3.2 Exploitation Support Infrastructure4 C3.3 Exploitation Planning
Nr. WP/Task Vorgangsname1 C4: IT Infrastructure and Integration2 C4.1 Design, delivery and support of User Enviroments, Con3 C4.2 Provide and Support user admin. and infrastructure ser4 C4.3 Deleted5 C4.4 Design and delivery of User Environments and Service6 C4.5 Provide and support user administration and infrastruct
7.5 Graphical presentation of the components Figure 4 shows the major components of work for phase 1 including the first 18 months and their interdependencies. The EIC services are indicative; actual services are upon agreement of the EIC members.
Action Line A: Research and Development
ICT Systems
Business & Knowledge
Action Line C: Management
Action Lines B: Community Building
EIC
Enterprise Modelling in the Context of Collaborative Enterprises
Cross-Organisational Business Processes
Knowledge Support and Semantic Mediation Solutions
Interoperability Framework and Services for Networked Enterprises
Model-driven and Adaptive Interoperability Architectures
Planned and Customisable Service-Oriented Architectures
Knowledge Sharing
Business Interoperability Research
Dynamic Requirement Definition
Piloting
Training
Scientific Co-ordinationAdministration
Knowledge Sharing Execution
Business Interoperability Forum
Dynamic Requirement Definition
Technology Testing Network Co-ordination
Interoperability Academy
Sub Project Call Administration
EIC Creation
Exploitation IT Infrastructure
Figure 4: Interdependencies between projects and activities
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
This subsection extensively describes the projects and activities in Action Lines A, B, and C, and their work packages. The table below gives a brief overview over the defined projects and activities. The following subsections contain detailed descriptions of the activities providing objectives, deliverables, description of work, milestones and expected results.
Project / Activity Title Lead
contractor Person-
years Start
month End
month Page
Action Line A: Research Coordination: TXT
A1 Enterprise Modelling in the Context of Collaborative Enterprises
FHG IPK 16,5 M01 M24 23
A2 Cross-Organisational Business Processes SAP 13,7 M01 M24 36
A3 Knowledge Support and Semantic Mediation Solutions
CNR-IASI 12,6 M01 M36 44
A4 Interoperability Framework and Services for Networked Enterprises
TXT 15,6 M07 M36 50
A5 Planned and Customisable Service-Oriented Architectures
SAP 11,4 M01 M24 59
A6 Model-driven and Adaptive Interoperability Architectures
IBM & SIEMENS
17,2 M01 M24 69
A7 Business Documents and Protocols SAP 8,3 M20 M36 79
A8 SME interoperability in Practice ESI 8,3 M20 M36 87
Action Line B: Community Building Coordination: IC FOCUS
B1 Community Creation and EIC Establishment SAP 2,2 M01 M36 95
B2 Knowledge Sharing AIDIMA 7,1 M01 M36 99
B3 Business Interoperability Research IC Focus 10,6 M01 M36 105
7.6.1 Deliverable Overview Section 4 contains the list of deliverables indicating the changes proposed in this document. Action Line A
Del.No Deliverable Title Delivery Date Nature Dissem.
Level
D.A1.1.1 First Version of State of the Art in EM technology to support enterprise interoperability M06 R PU
D.A1.2.1 Model and Report: First Set of Requirements M09 R PU D.A1.3.1 Report on Methodology description and guidelines definition M11 R PU
D.A1.4.1 Report and Model: First Version of Establishing and management approach M12 R PU
D.A1.5.1 Collaborative Modelling Platform specification M04 R CO D.A1.5.2 Collaborative Modelling Platform first prototype M14 P PU D.A1.6.1 Benefit-Assessment M24 R CO D.A1.7.2 Detailed Implementation Plan for Month 12 to Month 30 M11 R CO
D.A2.1 Cross-Organisational Business Process requirements and the State of the Art in Research, Technology and Standards M21 R PU
D.A2.2 Specification of a Cross-Organisational Business Process Model M15 R, P RE
D.A2.3 Architecture for Enactment and Integration of Cross-Organisational Business Processes M18 R RE
D.A2.4 Enactment of Cross-Organisational Business Processes M21 R, P CO D.A2.5 Validation of Research Results M24 R PU
D.A3.1 SoA and Technical specifications of Ontology Authoring and Management System, with Ontology Modelling Language M12 R+P CO
D.A3.2 Ontology Authoring and Management System for Informational knowledge and Business Processes M20 R+P CO
D.A3.3 Semantic Annotation language and tool for information and Business Processes M20 R+P CO
D.A3.4 System for reconciliation rules specification, storage and management M22 R+P CO
D.A3.5 A reconciliation and mediation engine, capable to efficiently process semantic mediation and reconciliation rules M24 R+P CO
D.A4.1 Requirements for Interoperability Framework, product-based and process-based Interoperability Infrastructures, Interoperability Life-cycle Services
M12 R RE
D.A4.2 Specification of Interoperability Framework and Profiles, Guidelines and Best Practices M36 R PU
D.A4.3 Product-based Interoperability Infrastructure and Profiles M36 R+P RE D.A4.4 Process-based Interoperability Infrastructure and Profiles M36 R+P RE D.A4.5 Interoperability life-cycle Services M33 R+P CO
D.A4.6 Validation of research results – product-based and process-based interoperability infrastructures, Interoperability life-cycle Services M36 R RE
D.A5.1 Perspectives on Service-Oriented Architectures and there application in environments that require solutions to be planned and customisable. M21 R PU
D.A5.2 Model and Specification of service description and usage as well as advanced concepts M18 R RE
D.A5.3 Architecture of SOA platforms M21 R RE
D.A5.4 Execution Framework(s) for Planned and Customisable Service-Oriented Architectures M21 R, P CO
D.A5.5 Validation of Research Results M24 R PU D.A6.1 Specification of a basic architecture reference model M12 R PU D.A6.2 Enhanced Registry/Repository Infrastructure M22 R+P PU D.A6.3 Model-driven and Adaptable Interoperability Framework M24 R+P PU D.A6.4 Model-driven and Adaptable Interoperability Infrastructure M24 R+P PP D.A7.1 Analysis of Industry Best Practice in Business Documents and Protocols M24 R PU D.A7.2 ATHENA approach to Business Document and Protocol management M34 R+P RE D.A7.3 Business Content for Selected Industry Best Practice M36 R+P RE
D.A8.1 Analysis of Interoperability Situation and needs of SMEs and current approaches M24 R PU
D.A8.2 Guidelines and Best Practices for applying the ATHENA Interoperability Framework to support SME participation in Digital Ecosystems M36 R+P RE
D.A8.3 Updated ATHENA tools and infrastructures supporting B5 Sub Projects M36 R+P RE
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Del.No Deliverable Title Delivery Date Nature Dissem.
Level D.B1.1 Charter, statutes, bylaws, policy, structure and services M06 R CO D.B1.2 Business plan of the EIC M12 R CO D.B1.5 Event programme and core activity overview M18 R PU D.B2.1 ATHENA outreach strategy and plan M07 R I D.B2.2 ATHENA conference M24 R PU D.B2.2 ATHENA conference M36 R PU D.B3.1 Business Interoperability Framework M36 R PU D.B3.3 Interoperability Impact Analysis Model M34 R PU D.B3.4 ATHENA Impact Assessment M36 R RE D.B3.5 ATHENA Contribution to Interoperability Policy Action Plan Version 1 M12 R PU D.B3.5 ATHENA Contribution to Interoperability Policy Action Plan Version 2 M24 R PU D.B3.5 ATHENA Contribution to Interoperability Policy Action Plan Version 3 M36 R PU D.B3.6 Business Interoperability Long Term Research Requirements (preliminary) M35 R RE D.B4.1 Dynamic Requirement Definition Principle M06 R RE D.B4.2 Global processes of reference M12 R RE D.B4.3 Scenarios mapped with Interoperability issues M12 R RE D.B4.3 Scenarios mapped with Interoperability issues M24 R RE D.B4.3 Scenarios mapped with Interoperability issues M36 R RE D.B4.4 DRDS M12 O RE D.B4.4 DRDS M36 O RE D.B5.1 Methodology & Technology Testing Report M09 R CO D.B5.1 Methodology & Technology Testing Report M18 R CO D.B5.3 Users Guide to Athena Prototyping Services M36 R PU D.B5.4 Post Test Evaluation M24 R PU D.B5.4 Post Test Evaluation M36 R PU D.B6.1 Target Group Analysis M18 R RE D.B6.2 Curriculum of the Interoperability Training Service M24 R PU D.B6.3 Training courses report M36 R PU
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Del.No Deliverable Title Delivery Date Nature Dissem.
Level D.C1.1 ATHENA Key Results M03 R PU
D.C1.2 Project Reports including: Progress report, Dissemination activity report, Standardisation report, IPR report, Report on using and disseminating of knowledge
M07 R PP
D.C1.2 Project Reports including: Progress report, Dissemination activity report, Standardisation report, IPR report, Report on using and disseminating of knowledge
M13 R PP
D.C1.2 Intermediate Project Reports including focusing on key aspects M19 R PP
D.C1.2 Project Reports including: Progress report, Dissemination activity report, Standardisation report, IPR report, Report on using and disseminating of knowledge
M25 R PP
D.C1.2 Intermediate Project Reports including focusing on key aspects M31 R PP
D.C1.2 Project Reports including: Progress report, Dissemination activity report, Standardisation report, IPR report, Report on using and disseminating of knowledge
M37 R PP
D.C1.3 Interoperability Roadmap up date made available 2 months before submission of detailed implementation plan of the next 18 months M12 R PU
D.C1.3 Interoperability Roadmap up date M24 R PU D.C1.3 Interoperability Roadmap up date M36 R PU D.C1.4 Yearly detailed implementation plan of the next 18 months M12 R PP D.C1.4 Yearly detailed implementation plan of the next 18 months M25 R PP D.C1.5 Submit yearly cost statements M14 R CO D.C1.5 Submit yearly cost statements M26 R CO D.C1.5 Submit yearly cost statements M38 R CO D.C1.6 Sub-project call for the individual projects M06 R CO D.C1.6 Sub-project call for the individual projects M19 O CO D.C1.6 Sub-project call for the individual projects M19 O CO D.C2.1 ATHENA Performance Indicators M03 R CO D.C2.1 ATHENA Performance Indicators – Update M12 M12 R CO D.C2.2 ATHENA Evaluation of Achieved Results and Generated Impact M13 R CO D.C2.2 ATHENA Evaluation of Achieved Results and Generated Impact M25 R CO D.C2.2 ATHENA Evaluation of Achieved Results and Generated Impact M37 R CO
D.C3.1.1 Exploitation Guidelines M12 R PU D.C3.2.1 Athena Exploitation Workshop M18 O RE D.C3.3.1 Joint and Individual Exploitation Plans M24 O RE
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
7.6.2.1 Project A1 – Enterprise Modelling in the Context of Collaborative Enterprises
Project Description Project A1 Enterprise Modelling in the Context of Collaborative Enterprises Leading Participant FHG IPK Starting M01 Ending M24
Participant 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 Total Person-Years 0,4 2,7 0,7 1,1 1,7 2,9 2,7 0,5 0,4 1,9 1,5 16,5 Project Objectives The overall goal of the project A1 is the development of methodologies, core languages and architectures as models, model generated workplaces and services and execution platforms for establishing collaborative on-demand Extended Enterprises and Networked Organizations. A Collaborative Enterprise is an enterprise where teams work together across boundaries, eg. Life-cycle phases, sharing results and knowledge to improve common understanding and enable better performance and quality results. The first sub objective of project A1 is the definition of a method and methodologies for model generated adaptable workplaces. The activity will not redefine the current methodologies for Enterprise Modelling but rather extend them and integrate them with execution platforms. The parallel federated, integrated and work environment integrating approaches for design and implementation of collaborative enterprises will support dynamic business demands. According to the SoA definition in section B.1 of this proposal, the project will develop methodologies for management and modelling of situated processes, flexible resource allocation and assignment and for work management and execution monitoring. For externalising the dynamic dependencies between participants and processes, conceptual methodologies of content based routing and collaborative processes will be developed.
The second sub objective is the development of ”benefit driven Enterprise Modelling User involvement” methodology adapted to each user type, allowing to support daily work based on active knowledge capture over collaborative enterprises. Solutions enabling scalable EM methodologies and infrastructures, repository services and portal server services, according to skills, tasks and relations of lifecycles of products and processes. Processes, new forms of organizations and systems will be developed. In the first 18 month an establishing framework will be defined and existing approaches integrated.
The third sub objective is providing the Collaborative Enterprise Modelling Management Platform to support directly the establishment and the operation of collaborative enterprises. The platform will enable the coordination of interrelated enterprise models independent from their origin language and will be interconnected to the intelligent architecture. This ensures full adaptable connectivity and coordination between the conceptual level and the execution level in solutions to be provided by project A2. For the first 18 month the first version of the platform with the capability to exchange of process model will be elaborated. Until month 24 the second version of the platform will be able to exchange Enterprise Models based on POP*.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Contribution to Milestones Milestone Contribution to Milestone
M.12 − Requirements / State of the Art − Views and constructs to represent collaborative enterprises − Common collaborative enterprise repository definition
M.24 − Service definition for collaborative synchronisation on demand and management of different distributed enterprise models
− Modelling platform for collaborative enterprises first version
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A1.1 State of the Art – re-assessed Leading Participant ESI Starting M01 Ending M22
Objectives The objective of this work package is the assessment of the state of the art on technologies related to modelling of collaborative enterprises. The analysis is based on and consolidates existing resources such as the States of the Art from the IDEAS and the UEML Thematic Network and other resources (e.g. Active Knowledge Management (AKM) approach). An additional objective is the establishment of a framework to structure current information and further inputs on state of the art. This framework will help an ongoing capturing of upcoming approaches during the project. Especially, the common framework is an artefact for the close interaction between this WP and Project A2 with respect to the definition of the SoA according the link between conceptual and execution oriented level of enterprise processes. Description of Work Task A1.1.1: Define a framework for gathering the information related to SoA. This framework
should be flexible enough to allow an extension to manage and include further inputs during the project life.
Task A1.1.2: Assess SoA on technologies for modelling collaborative enterprises. This task includes the integration of previous work in the field such as IDEAS, UEML and AKM SoAs.
Task A1.1.3: Define in detail and adopt the SoA framework for further contributions and SoA updates (every 6th month).
Collaboration with A2.1 State of the Art in CBPs, common framework to represent state of the art Receives from A2.1 DA2.1.1 Cross-Organisational Business Process requirements and the State of the Art in Research, Technology and Standards Provides to A2.1 SoA on EM technologies and Common framework for SoA description and updating.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A1.2 Requirements for Model-driven Collaborative Enterprises and Use-cases
Leading Participant CRF Starting M01 Ending M22
Objectives Based on requirements from other projects and the use cases defined in Activity B4 (Dynamic Requirement Definition) of Action Line B the requirements for model driven collaborative enterprises will be defined. Therefore already existing user requirements (IDEAS-scenario based and UEML- methodology and tool based) will be used for deriving formal requirements coming from B4 for A1.3, A1.4 and A1.5. Description of Work Task A1.2.1: Elaboration of the Initial Set of requirements coming from UEML and IDEAS
(Requirements Framework) and including the requirements from scenarios defined in Activity B4.
Task A1.2.2: First set of requirements for extending the current methodologies will be elaborated. Therefore the four methodologies (EEML-TROUX, IEM-IPK, GRAI-ITREC, ARIS-DFKI-IWI) will be analysed and the gap according to the State of the Art of Task A1.1.1 defined. Also the first set of requirements will be influenced by the Action Line A projects A2 – A6 (namely WPs A2.1, A3.2, A4.2, A5.1 and A6.1)
Collaboration with A2.1, A3.2, A4.2, A5.1, A6.1 for definition of common requirements structure B4 initial requirements and integration of technical requirements into the
user requirements system Receives from A2.1 D.A2.1 Cross-Organisational Business Process requirements and
the State of the Art in Research, Technology and Standards Provides to A2.1, A3.2, A4.2, A5.1, A6.1 Requirements Framework Model A3.2, A4,2, A5.1, A6.1 First set of requirements
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A1.3 Collaborative Enterprise Modelling Languages and Constructs Leading Participant ITREC Starting M3 Ending M11
Objectives The objective of this work package is the development of the core modelling methodology elements for capturing collaborative enterprises design and management. It will take into account the needs of project A2 (Cross-Organisational Business Processes) in terms of collaborative business processes and document routing on the execution level. Therefore the current methodologies will be extended to include business models and visual rules modelling. The work package will include the results of project A3 (Knowledge Support and Semantic Mediation Support) of Action Line A in the language definition. The work package will take into account the influence of approaches for model driven architecture in order to integrate them into the modelling techniques for collaborative enterprises. Approaches coming from the psychological area (e.g. UCINET) will be analysed for incorporation to create a holistic enterprise modelling set. Description of Work Task A1.3.1: Environment for extended EM constructs and development process definition Task A1.3.2: Identification of current existing basic methodologies for collaborative enterprise
modelling languages and constructs, especially already existing methodologies coming from other domains (e.g. psychology) will be analysed
Task A1.3.3: First set of Basic methodologies for collaborative enterprise modelling languages and constructs
Task A1.3.4: Methodology description and guidelines for application of the First set of Basic methodologies
Collaboration with A2.2 incorporate specification into the enterprise modelling construct definition A3 2 ontological issues according to the constructs A4.2 Basic EM methodologies B4 initial requirements and integration of technical requirements into the user requirements
system Receives from
A2.1 DA2.1.1 Cross-Organisational Business Process requirements and the State of the Art in Research, Technology and Standards
A3.2 DA3.2.1: Int: State of the Art on Ontology modelling and tools for informational knowledge. A5.2 D.A5.2.1: Modelling, meta-modelling and specification approaches that facilitate the
designing of mature web services Provides to A2.2, A3.2, A4.3, A4.2, A5.2 DA1.3.2
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A1.4 Establishing and Management Methodology for Model-driven Collaborative Enterprises
Leading Participant FHG IPK Starting M03 Ending M11
Objectives The objective of this work package is the development of an approach for user-centric model driven collaborative enterprises based on the scenarios coming from Action Line B and the set of basic methodologies developed in the previous work package (WP A1.3). These services will support model based enterprise synchronisation on demand approaches and will contribute to a certain collaboration progress. Therefore the following mechanisms and procedures have to be developed: • Scalability of modelling methodologies, model views and tools according to the user types
(skills, role in the enterprise, tasks to be performed). • Model-based collaboration maturity framework for management of the different levels of
collaboration and their optimisation. The maturity framework will enable a save transition from one interoperability level to another. It will be used for fast and stepwise enterprise collaboration.
• Participation modelling approach for benefit driven user involvement in Enterprise Modelling to support collaboration design and establishment.
This WP will define the framework for establishing collaborative enterprises based on the views scalability, maturity and participation. The results will be directly used for the specification of core functions in the succeeding work package (WP A1.5: Development of a Collaborative Modelling Platform to Enable and Manage Collaborative Enterprises). Description of Work Task A1.4.1: Initial version of the establishing and management methodology Task A1.4.2: First version of the establishing and management methodology Collaboration with B4 Scenario building A5.4 Implementation and Service composing Receives from
B4 Scenario definition Provides to
A2 DA1.4.1 Report and Model: First Version of Establishing and management approach
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A1.5 Development of a Collaborative Modelling Platform to Enable and Manage Collaborative Enterprises
Leading Participant TROUX Starting M03 Ending M15
Objectives The objective of this work package is to provide the Collaborative Enterprise Modelling Platform (Intelligent Infrastructure). The platform will support: • the development of collaborative enterprises by using distributed enterprise models and by
providing specific enterprise modelling methodologies coming from A1.3 • the procedure of model driven design, establishment and management of collaborative
enterprises coming from A1.4 For the first project phase, the core functions of the model management platform will be established and the process model exchange environment will be developed as one specific model management function and based on a first repository which will be enriched by the additional modelling methodologies. The exchange will be based on the UEML 1.0 definition and the services for tracing and interdependency management will be established. The service development will be done jointly with project A4 of Action Line A and A1.4. The development of the platform will be interlinked to the development of the Intelligent Infrastructure in projects A5 and A6 of Action Line A. Description of Work Task A1.5.1: Main Methodologies and Tool selection and requirements definition for services Task A1.5.2: Initial version of the distributed Collaborative Modelling Platform Task A1.5.3: Implementation of process model exchange via UEML Version 1.0 and integration into
the Collaborative Modelling Platform Collaboration with A4, A5, A6: Platform definition and integration Receives from
A5.3: Modelling and specification framework for the expression of semantics within service-oriented architectures
Provides to A4, A5, A6: D.A1.5.1 Collaborative Modelling Platform specification, D.A1.5.3 Collaborative Modelling Platform first prototype
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A1.6 Validation of Results Leading Participant SINTEF Starting M05 Ending M24
Objectives Validation of results is essential in order to check alignment with initial requirements. They are also vehicles for facilitating collaboration and consensus among project partners. This work package will focus on incrementally integrating results of the project and validate the project in user scenarios and pilots defined in activity B5 (Demonstration including Test-Bed Coordination and Pilot Infrastructure) of Action Line B. The following sub goals will be achieved:
− Common and detailed methodology for validation and testing (in coordination with activity B5) − Provide a detailed evaluation plan Description of Work Task A1.6.1: Validation concept Task A1.6.2: Validation of results achieved in the initial version Task A1.6.3 Validation of results achieved in the first version Collaboration with
B4 Scenario definition, validation concepts Receives from
B4.4: D.B4.4.1 List of Scenarios, D.B4.4.3 To-Be Scenarios, D.B4.5.4 Analysis Method Validation Provides to
B4: D.A1.6.1 Test Case Descriptions/Models, D4.6.2 Evaluation Criteria List, D.A1.6.3 Benefit-Assessment
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A1.7 Project Management Leading Participant IPK Starting M01 Ending M24
Objectives The aim of project management is to take care of the following issues: progress control, quality assurance and mid term activity planning. The individual work package leaders are responsible for progress control and quality assurance. For the coordination of the overall progress monthly conference calls or web-conferences and Technical Committees Meetings (composed by the work package leaders) every 6 months will be organized by the project lead. The work package leaders and the project leader will provide a progress report every 6 months.
• For mid term planning the project management will provide an adapted detailed implementation plan proposal to the Action Line Coordination 11 months after project start.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A1.8 Revise the POP* framework Leading Participant ITREC/UB1 Starting M19 Ending M22 Objectives The objective of this work package is to update the POP* Methodology according to the lessons learned during the implementation into the MPCE Repository On the other hand the additional aspects of enterprise modelling which were identified in the first period as potential candidates (network analysis methodology) for being integrated into POP* will be taken into account for enhancing the POP* meta model. Description of Work Task A1.8.1: POP* update according to the implementation for the MPCE Repository Task A1.8.2: Integration of additional concepts into POP*
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A1.9 Develop the MPCE for complete EM exchange Leading Participant TROUX/SINTEF Starting M19 Ending M23
Objectives The work-page has these objectives:
• Providing a core integrated modelling and enactment platform to support use-cases, piloting (further developments of the MPCE),
• Developing an open and extensible enterprise architecture, and services for the key actors at each layer, to integrate across sectors and life-cycles
• Enabling all participating tools to be linked to the MPCE The MPCE will be used in the CATS in order to perform evaluation and additional requirements gathering Description of Work Task A1.9.1: Develop Integration Services Task A1.9.2: Implement the POP* Meta model into the MPCE Repository and provide the
interface services Receives from
B4 scenarios for application CATS – expectation and feedback
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A1.10 EIMM – Model Parameter Harmonisation Leading Participant IPK /DFKI Starting M20 Ending M21
Objectives The objective of this work package is the development of an approach which enables companies to deliver and manage their modelling services in an agile and effective manner. The goal is to provide companies the possibility to apply the services that best fit the identified situation. Both elements of the current methodology the Enterprise Interoperability Maturity Model (EIMM) and the modelling parameters to detect suitable establishment concepts (e.g. controlling concept or role concept) will be analysed in order to converge and to harmonise. On the other hand the morphologic box has to be specified and filled with already existing approaches. For that a consolidation and modularisation of the existing approaches is needed. The parameters, the State of the Art concepts and the Establishment Methodology are the basis for this activity. The identified level of maturity is the base for deducing the needed modelling services. These will help to deliver the user the needed support to depict the enterprise model correctly for improving their capabilities for interoperability. This generated enterprise model is the starting point for deriving the required services which allow to deliver a user-specific solution.
Description of Work Task A1.10.1: Converging and harmonise the EIMM and the modelling approach parameters Task A1.10.2: Approach for deducing EKA-services from the TO-BE maturity level of the EIMM and
TO-BE models of an enterprise Collaboration with A1.3, B4, B5, CATS, A4 Receives from
B4 scenarios for applications, A4 generic requirements to be addressed
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Activity Objectives The notion of business processes has received increasing recognition as the “glue” between originally disjoint activities within an enterprise. Business process systems (incl. Workflow Management systems) have demonstrated the applicability of this concept within the boundaries of the enterprise. We envisage that this concept provides a significant opportunity in the cross-organisational context. Therefore we consider interoperability of enterprise systems at the business process level in this project. The goal of this project is to provide a solution that enables execution of Cross-Organisational Business Processes (CBPs). It is envisaged that this requires an approach beyond the currently accepted methods of interface (application programming interface) level. Based on a sound analysis of business requirements, impact and scenarios as well as trading practices that will be provided to a large extend by Activity B3 and B4 we propose modelling techniques to represent business processes from different organisations on a level that considers the privacy requirements of the involved partners. Such models will have two perspectives: (i) enterprise modelling perspective that assigns a process to its context in the enterprise and (ii) a formal aspect to perform computational transformations in order to allow for re-use of process in a cross-organisational environment. Such models need to be enriched through ontological information and need to be executed through IT systems, such as workflow engines. These engines need to be enabled to operate efficiently in an architectural environment that adapts to particular business scenarios. This includes a new approach to messaging where the message content can be interpreted by a routing system and be correlated and batch-processed if required. For each of the work packages we propose an approach that develops the theoretical concepts, whilst verifying those models in prototypes where applicable. There will be an exchange of theory and prototypes between the work packages to strive for an integrated solution for cross-organisational business processes. The achieved research results will be validated in WP A2.6 using the technical requirements. Validated results will be handed over to Activity B5 for validation in use cases to provide valuable user feedback into the research.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
A2.3 Semantic Issues in Cross-Organisational Business Processes
14 - CNR-IASI
25,8 M7 M21
A2.4 Architecture for Enactment and Integration of Cross-Organisational Business Processes
1 – SAP 33,5 M9 M18
A2.5 Enactment of Cross-Organisational Business Processes
1- SAP 24,0 M12 M21
A2.6 Validation of Research Results 5 – CRF 13,9 M9 M24
A2.7 Management 1 - SAP 5,4 M1 M24
164,9 M1 M24
Deliverable List Deliverable
No Deliverable Title Project
/ WP No
Lead Participant Nature
Dissemi-nation level
Delivery Date
D.A2.1 Cross-Organisational Business Process requirements and the State of the Art in Research, Technology and Standards
A2.1 9 – Formula
R PU M21
D.A2.2 Specification of a Cross-Organisational Business Process Model
A2.2 6 – DFKI
R, P RE M15
D.A2.3 Architecture for Enactment and Integration of Cross-Organisational Business Processes
A2.4 1 – SAP R RE M18
D.A2.4 Enactment of Cross-Organisational Business Processes
A2.5 1 – SAP R, P CO M21
D.A2.5 Validation of Research Results A2.6 5 – CRF
R PU M24
Work Document List
Work Document No Work Document Title Project /
WP No Lead
Participant
WD Delivery
Date
WD.A2.1 Cross-Organisational Business Process requirements and the State of the Art in Research, Technology and Standards
A2.1 Formula M04 M09 M15
WD.A2.2 Semantic Annotations to Cross-Organisational Business Process Models
A2.3 CNR-IASI
M21
Contribution to Milestones Milestone Contribution to Milestone
M.12 − Requirements / State of the Art − Modelling method for cross-organisational business processes (CBPs)
M.24 − CBP modelling tool − Semantic annotations for business processes − Integration of non-functional aspects in CBPs − Architecture and execution platform for CBPs − Requirements / State of the Art
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A2.1 Requirements Analysis & State of the Art Leading Participant Formula Starting M1 Ending M21 Objectives The objective of this work package is to identify typical aspects of business process interoperability and to build a metric against which further work on modelling, transforming, workflow engine, and architecting can be measured against. This will be achieved through involvement of users through a close interaction and joint effort with Activity B3 and B4. The activities in this work package will be executed in coordination with Project A1. Results of the user requirements gathering are analysed in order to derive technical requirements used throughout the project. Furthermore, this work package we will provide a state of the art analysis on research, standards, and technology in the field of cross-organisational business processes and related areas, such as messaging and security. The goal is to learn from past experiences and to build upon them. State of the Art analysis will be guided by the identified technical requirements. Description of Work In this work package user scenarios and market models are being evaluated. On this basis we develop typical patters (i.e. aspects) that need to be supported by any cross-organisational business process model, workflow engine, and architecture. The state of the art analysis will be based on academic and industrial material. It will leverage results from previous projects like IDEAS or UEML and will leverage the state of the art produced in the Interop NoE through collaboration. Furthermore, there will be close interaction with Project A1 with respect to a common model for representing the state of the art, derived from models provided by IDEAS, UEML and potentially Interop. Task A2.1.1: Specify a methodology to represent cross-organisational business processes for the
purpose of Task A2.1.1 Task A2.1.2: Aspects of Business Process Interoperability Task A2.1.3: State of the art in Research, Standards and Technology Collaboration with A1.2 Requirements on CBPs A1.1 State of the Art in CBPs, common model to represent state of the art Receives from B3, B4 User and Business Requirements Provides to A2 Technical Requirements on CBPs
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A2.2 Modelling Cross-Organisational Business Processes Leading Participant DFKI Starting M6 Ending M15 Objectives The objective of this work package is to model cross-organisational business processes in liaison with Project A1 of Action Line A and to lay the foundation for Dynamic Document routing. Description of Work This work package develops a cross-organisational business process model and provides the formal methods to integrate private business processes in a coalition whilst maintaining their privacy. Newly created cross-organisational business processes are then being tested to ensure their functionality. Task A2.2.1: Cross-Organisational Business Process Model and Formalisation Task A2.2.2: Computational Operators for Business Process Model Manipulation Task A2.2.3: Dynamic Routing and Document Correlation Task A2.2.4: Cross-Organisational Business Process Modelling Tool Collaboration with A1.3 Modelling constructs and languages for CBPs A6 Cross-Organisational Business Process Model to integrate into MDA approach (especially A6.5) Receives from A2.1 Technical requirements Provides to A2, A1 Cross-Organisational Business Process Model
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A2.3 Semantic Issues in Cross-Organisational Business Processes Leading Participant CNR-IASI Starting M07 Ending M21 Objectives The objectives of this work package is to understand semantic issues in Cross-Organisational Business Processes, create an Ontology for Business Process Modelling, and provide a methodology for semantic annotations to Business Process Models Description of Work This work package will analyse semantic requirements of cross-organisational business processes. On this basis we will develop an approach on how to semantically enrich heterogeneous business process models with a business process ontology. It aims to define a business process ontology in a close working relationship with Project A3 in order to use results achieved there and leverage ontology knowledge. Task A2.3.1: Identify semantic needs of Business Processes Modelling Task A2.3.2: Definition of an Ontology for Business Processes Task A2.3.3: Annotation of semantics to Business Process Models Collaboration with A3.3 Knowledge and Ontology Infrastructure for Business Processes A3.4 Definition of a Semantic Annotation Methodology and Tool Receives from A3.4 Semantic Annotation Methodology and Tool Provides to A3.6 Ontology for Business Processes
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A2.4 Architecture for Enactment and Integration of Cross-Organisational
Business Processes Leading Participant SAP Starting M9 Ending M18 Objectives The objective of this work package is to propose and describe heterogeneous architectural support for cross-organisational business process execution. Results of this work package will contribute to the Reference Architectures defined in Project A4. Description of Work This work package will lay the architectural foundations to effectively integrate/distribute and execute cross-organisational business processes. Furthermore, this work package will comprise research in correlation and validation of messages, based on requirements using results of WP A2.2. Task A2.4.1: Document and Event Correlation Architecture Task A2.4.2: Identify functional and non-functional aspects of cross-organisational business
process architectures. Task A2.4.3: Design of a process-centric architecture Collaboration with
Receives from A4 Reference Architecture Blueprint Provides to A4 Architecture for CBPs
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A2.5 Enactment of Cross-Organisational Business Processes Leading Participant SAP Starting M12 Ending M21 Objectives The objective of this work package is the design and implementation of a cross-organisational workflow engine that is able to execute cross-organisational workflows, considering intra-organisational and inter-organisational entities. Results of this work package will contribute to the interoperability infrastructure developed in Project A4. Description of Work This work package is concerned with the execution of cross-organisational workflows. This requires a workflow engine that is aware of the different nature of publicly visible workflows in addition to the private workflows that implement them. Such engines operate in a larger environment that requires effective architectural support for specific business scenarios. Such engines will require an understanding of the underlying enterprise model and the ontological representation. Furthermore, the approach of transforming the cross-organisational business process model onto a standard based process model and the associated engine (e.g. a BPEL process engine) is investigated. Simulation activities will support the test of cross-organisational business processes prior to their deployment. Task A2.5.1: Cross-Organisational Business Process Engine Task A2.5.2: Simulation of Cross-Organisational Business Processes Collaboration with A6 regarding transformation of models Receives from A4 Guidelines on Infrastructure A2.4 Architecture Provides to A4 Execution Engine for CBPs
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A2.6 Validation of Research Results Leading Participant CRF Starting M9 Ending M24 Objectives The objective of this work package is the validation of the research and development findings using the technical requirements identified in this project. Description of Work By incrementally integrating results of work packages into a platform that can be used for validation in user scenarios, this WP will provide an important feed-back loop into individual WPs of this project and especially to Activity B5 of Action Line B. Collaboration with
Receives from A2.1 Technical Requirements Provides to B5 Research Results A2 Results of Validation
Work Package A2.7 Project Management Leading Participant SAP Starting M1 Ending M24 Objectives The aim of project management is to take care of the following issues: collaborations between projects and action lines, progress control, control of creation and submission of deliverables and results, quality assurance, reporting and detailed implementation planning for the project. The individual work package leaders are responsible for the application of the same scope as the project management. For the coordination of the overall progress monthly conference calls or web-conferences and Technical Committees Meetings (comprising the work package leaders) at least every 6 months will be organized by the project lead. The work package leaders and the project leader will provide alternating a progress report (months 6, 12, 18,…) and a status report every 3 months (months 3, 9, 15, ….) For the yearly planning and review checkpoints the project management will provide an up dated detailed implementation plan proposal to the Action Line Coordination 11 months after project start. Description of Work Task A2.7.1 Technical project management: Task A2.7.1 Mid term action planning
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Objectives This project is aimed at the development of methods and tools for enterprise ontology management, with a focus on supporting enterprise knowledge integration and interoperability for enterprises and software applications. The main objective is to build an ontology environment aimed at supporting the integration of the different sorts of knowledge that can be found in an enterprise. Enterprise knowledge can be divided in two main categories. The first category comprises the knowledge represented by all sorts of documents: from technical reports to emails, from scientific papers to circuit blueprints; this category is mainly conceived to be used by human users. A second category is represented by formal symbolic knowledge, e.g., modelled by using semantic nets or description logics, stored in an ontology, that is mainly organized to be exploited by a computer. The proposed ontology enterprise environment, based on ontology knowledge, will be used in two main enterprise areas: to support the integration of documental knowledge and to achieve enterprise software interoperability. Both of them can be achieved by applying semantic annotation techniques, although our focus will be on the latter. Semantic annotation is based on a reference ontology (that can be seen as a sort of “repository of meaning”) that is used to construct annotation expressions, aimed at giving a clear, agreed, unambiguous meaning to documental (human oriented) knowledge or to enterprise software elements used in co-operative processes. Semantic annotation will be used to associate a formal meaning to enterprise models, and in particular to information structures and Business Processes in order to realize a semantic interoperability platform. On the technological level, semantic annotation will be used to associate meaning to computable services (e-services, agents, software components, etc.) selected to be used in advanced software architectures, such as MDA, SOA, DAI. Semantic annotation is one of the key enabling technologies to implement a number of solutions for achieving interoperability, e.g., from service discovery to matchmaking, to the linking of Business Processes to computable services. In order to discover, on a semantic basis, the suitable e-Services, an advanced query system, and more in general a discovery system will be developed, based on the ontology. When two different e-Services need to co-operate exchanging information and commands, an advanced reasoning services is required, capable of reconciling different formats, structures and organizations to allow for seamless interoperability. Such a reasoning system based on reconciliation rules will be developed.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
WD.A3.1 Periodic reports about coordination and integration activities A3.1 CNR-IASI
M18
WD.A3.2 Report on ontology usage validation – Experiences and lessons learned
A3.1 CNR-IASI
M36
WD.A3.3 Core business ontology A3.2 CNR-IASI
M14
WD.A3.4 Extension of Core business ontology to formal process representation
A3.3 CNR-IASI
M19
WD.A3.5 State of the Art on Ontology based Semantic Annotation methods and tools
A3.4 CNR-IASI
M16
WD.A3.6 Specifications of a system for reconciliation rules specification, storage and management
A3.5 TXT M18
Milestone Contribution to Milestone
M.12 − SoA and Technical specifications of Ontology Authoring and Management System, with Ontology Modelling Language
M.24 − Ontology Authoring and Management System for Informational knowledge and Business Processes
− Semantic Annotation language and tool for Information and Business Processes − System for reconciliation rules specification, storage and management − A reconciliation and mediation engine, capable to efficiently process semantic mediation
and reconciliation rules − Extension of Core business ontology to formal process representation
M.36 − Report on ontology usage validation - Experiences and lessons learned
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A3.1 Management, coordination, integration and validation Leading Participant CNR-IASI Starting M1 Ending M36 Objectives Carry out the management of the Project, with particular attention to the integration with other Projects that need to apply the knowledge-based solutions developed in this Project. Furthermore, validation tests will be performed within this WP.
Description of Work Task A3.1.1: Monitor and manage the different WPs and activities of the Project, verifying milestones,
deliverables, and resources consumption
Task A3.1.2: Organise Integration and Coordination Working Groups with participants from other Projects, to acquire the needs emerging from other Projects, illustrate achieved results, plan subsequent activities.
Task A3.1.3: Organise integration and test sessions to validate the results produced in the other WPs and participate in the validation and monitoring of our results used in other projects.
Collaboration with Receives from Provides to
Work Package A3.2 Knowledge and Ontology Infrastructure for Information Leading Participant CNR-IASI Starting M1 Ending M18 Objectives
Develop an infrastructure aimed at ontology authoring and management, to build ontologies capturing the semantics of different forms of enterprise knowledge, including documents, business models, product blueprints, supporting the development of a unified approach to enterprise knowledge management.
Description of Work Each task involves the definition and, if necessary, the development of languages, methods and tools
Task A3.2.1: State of the Art on Ontology modelling and tools for informational knowledge
Task A3.2.2: Ontology Acquisition and Management for informational knowledge
Task A3.2.3: Ontology Query and Search / Retrieval
Collaboration with A1.3, A2.2 Definition of Ontology and Collaborative Enterprise Modelling languages A2.3 Knowledge and Ontology Infrastructure Receives from Provides to A1.3 Ontology Modelling Language B2, B3, B4 Tool and a Core Business Ontology for Domain Ontology Building A4 Ontology management system for informational knowledge
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A3.3 Knowledge and Ontology Infrastructure for Business Processes Leading Participant CNR-IASI Starting M5 Ending M20 Objectives
Develop a system for modelling the ontological knowledge regarding business processes, and, more in general, the dynamic aspects of an enterprise. The underlying methodology will be based on a sound mathematical basis (such as Process Algebra, Situation Calculus or Graph Grammars) to make it independent of the specific user-oriented notations. Semantics of evolutionary phenomena of interactions and cooperation between business entities will be addressed and suitable representation languages will be identified. Extension to the infrastructure developed in A3_2 is required for management functions and query and retrieval of behavioural descriptions.
Description of Work Task A3.3.1: State of the Art on Ontology modelling and tools for behavioural knowledge
Task A3.3.2: BP Ontology Acquisition and Management
Task A3.3.3: Query and Search / Retrieval over BP Ontology
Collaboration with A2.2 Business Process Modelling Receives from Provides to A1.3 Ontology Modelling Language B2, B3, B4 Tool and a Core Business Ontology for Domain Ontology Building A4 Ontology management system for informational knowledge and Business Processes
Work Package A3.4 Semantic Annotation Methodology and Tool Leading Participant CNR-IASI Starting M10 Ending M20 Objectives
Semantic annotation expressions are constructed starting from a Reference Ontology. They represent the basis of a method to give meaning (more precisely, to associate a formal semantics) to elements of a Conceptual Model, a Business Process, or an e-Service. The objective of this WP is to develop a method and a tool for ontology-based semantic annotation.
Description of Work Task A3.4.1: State of the Art on Ontology based Semantic Annotation methods and tools
Task A3.4.2: Semantic Annotation Solutions for informational knowledge
Task A3.4.3: Semantic Annotation Solutions for business processes
Collaboration with A2.3 Semantic Annotation Receives from Provides to A2.3 Tool and Languages for Semantic Annotation of Business Processes A5.3, A6.2 Tool and Languages for Semantic Annotation of e-Services A4 Semantic Annotation method and tool
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A3.5 e-Services Selection and Semantic Reconciliation Leading Participant TXT Starting M12 Ending M22 Objectives
Define methods and tools to analyse, starting from the Semantic Annotation, the operations and the services required by a BP and identify the e-Services that will satisfy them. Create the reconciliation rules (for information and business processes) necessary to bridge the incompatibilities that arise when the two interacting (Business Process and e-Service) are not compliant.
Description of Work Task A3.5.1: Static Component Analysis
Task A3.5.2: Semantic Reconciliation for Data
Task A3.5.3: Semantic Reconciliation for Operations and Processes
Collaboration with A5.5 Semantic Discovery of e-Services and Mediation Solutions Receives from Provides to A6.3 Semantic Mapping & Reconciliation Technologies A4 System for reconciliation rules specification, storage and management
Work Package A3.6 Semantic Mediation for BP / e-Services Execution Leading Participant Formula Starting M14 Ending M24 Objectives
Develop a reconciliation and mediation platform that, at runtime, is able to intercept data and command messages and transform them to allow for cooperation between loosely compatible software applications. To this end it uses the reconciliation and mediation rules produced by WP3_5.
Description of Work Task A3.6.1: Infrastructure for message handling, dispatching in a peer-to-peer approach
Task A3.6.2: Real-time commands and data harmonisation; data buffering and forwarding, Web Services triggering
Task A3.6.3: Integration of Semantic capabilities into Processes execution engine, with tracking and transaction management
Collaboration with A5.5, A5.6 Runtime Service Discovery and Usage Receives from Provides to A4 Reconciliation and mediation engine
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
From the ATHENA programme point of view, this project represents the way to reconcile and complement the approaches, methodologies and results of the other projects in Action Line A. This project aims at exploiting results and methodologies reached in enterprise modelling and business process management (projects A1 & A2), ICT service-oriented architectures and development platforms (projects A5 & A6) and semantic annotation and ontology-based reconciliation (project A3). Special attention will be given to the user requirements and scenario identification for validation (B5), and it is expected that valuable results would be fed into the activities for Requirements Definition (B4), Interoperability Research (B3). In particular, the A4 project aims at:
Obj1: synthesising the results of the research performed in AL A projects into a conceptual, actuation and technical ATHENA Interoperability Framework (AIF) and instantiating it to the ATHENA Interoperability Profiles (AIP) needed to implement the AL B scenarios;
Obj2: defining the 3 layers of the Framework (AIF) (conceptual applicative and technical), following both a product-based and a process-based Interoperability Approach; According to the POPS (process, organisation, product, systems) and, by adopting the identified AIPs, validating it against the requirements defined in the interoperability scenarios of AL B;
Obj3: defining and implementing a Suite of Software Services to cover the whole life cycle of the integrated interoperability paradigm and validating it against the requirements defined in interoperability scenarios of AL B.
Obj1 will be achieved in different steps: an initial specification (by month 12) will be based on state-of-the-art analysis (including IDEAS and UEML visions and roadmaps) and on the first results coming from the other AL A projects. Such specifications will be constantly updated and adapted to the results achieved by the other AL A projects. Specific instantiations of the general framework will generate the profiles necessary for the implementation and validation. An intermediate specification of will be released at Month 24, while the final specification of the 3 levels of the Interoperability Framework is foreseen at Month 36. Both AIF and AIP specifications will be performed at the Conceptual Level, by defining a Reference Architecture for Interoperability and a Methodology for following it; at the Applicative Level, by defining proper Guidelines and Handbooks and identifying significant Best Practices; at the Technical Level, by defining a Technical Interoperability Infrastructure and Supporting Tools, by applying, adopting and integrating the proper standards and by covering the ICT (Data and Application), Knowledge and Business layers. Obj2 will be the Integrated (see ISO 14258, Concepts and rules for enterprise models) Implementation and Validation of the AIF levels with a particular focus in the Technical Interoperability Infrastructure and Supporting Tools defined in the AIF (Obj1). According to the POPS (process, organisation, product, systems) methodology, we identified two different and distinct interoperability forms: the former (focussing on Product and Organisation POPS) in which knowledge and enterprise models, innovation projects, human competencies, workplace interaction, are the predominant issues (and we called it product-based interoperability), the latter (focussing on Process and Systems POPS) where workflows, e-commerce transactions, business synchronisation and interconnectivity, systems integration represent the core interest (and we called it process-based interoperability). Both product-based and process-based forms and tools will be then validated in the scenarios identified and proposed by AL B projects, following the specifications included in the relevant AIPs (Obj1). Obj3 aims at the design, implementation and validation of Services supporting networked enterprises in planning, establishing, executing and governing inter-operability solutions with partners or inside the enterprises themselves. These application services follow a typical life cycle of an inter-
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
operability solution, from its feasibility study (identifying possible options for implementing inter-operability and selecting the most promising one), to its planning (defining and actuating the implementation plan to pass from the as-is to the to-be situation, which is a situation suitable for inter-operability), to its operations support (to insert the proper inter-operability infrastructure services inside cross-enterprise business processes and to supervise their actuation), to its governance support (to monitor and control the activation of such inter-operability infrastructure services to discover anomalies or non conformant behaviour). The inherently integrating nature of this project exposes it to the obvious risk of not having the expected results available for its continuation. In particular, the maturity of the technologies and results from the service-oriented architecture research areas (projects A5 and A6) and the tools and methodology assessment deriving from the A2 research are critical for the success of project A4. In both cases, special care will be taken to follow directly the mentioned projects’ evolution, with direct participation of their leaders in A4 activities. The results of this monitoring activity, as well as a deeper understanding of the implications coming from the user requirements, would be fed into the work plan both in terms of timing and contents.
Work Package List Work
package No Work package Title Responsible Particip. No
WD.A4.3 Process-based Interoperability Infrastructure 1st issue A4.4 SAP M24
WD.A4.4 Interoperability life-cycle Services including specification A4.5 A4.6
TXT M24
WD.A4.6 Validation of A4 research results A4.3 A4.4 A4.5 A4.6
Formula M24
Contribution to Milestones Milestone Contribution to Milestone
M.12 − Requirements specification for Interoperability Framework D.A4.1 − Initial Specification of Interoperability Framework and Profiles, Guidelines and
Work Package A4.1 Requirements Analysis Leading Participant TXT Starting M7 Ending M12
Objectives The objective of this work package is to select appropriate user scenarios in order to prepare the means for tools validation This will be achieved through involvement of users through a close interaction and joint effort with Activity B4 (Dynamic Requirements Definition) of Action Line B.
Description of Work User Scenarios will be analysed and selected to be the supporting guidance for the evaluation of the dynamic execution of the first interoperable prototype solution.
T.A4.1.1: Requirements for Interoperability Framework T.A4.1.2: Requirements for Product-based Interoperability T.A4.1.3: Requirements for Process-based Interoperability T.A4.1.4: Requirements for Interoperability Life-cycle Support Collaboration with AL B Receives from B4 Dynamic Requirements Definition Provides to B4 Dynamic Requirements Definition B3 Business Interoperability Research
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A4.2 Interoperability Framework & Profiles Definition Leading Participant SINTEF Starting M7 Ending M36
Objectives The WP will combine methodologies and results of the other projects in Action Line A and lead to the definition of the Interoperability Framework that spans across its main axis:
Conceptual Integration: definition of the Interoperability Reference Architecture and Interoperability Methodology
Applicative Integration: definition of Best Practices, Guidelines and Handbooks Technical Integration: definition of an Interoperability Support Infrastructure, and Technical
Architecture. The WP will also instantiate the Interoperability Framework into the ATHENA Interoperability Profiles (AIPs) needed to implement the AL B scenarios;
Description of Work Tasks:
T.A4.2.1: Specification of the Interoperability Conceptual Framework T.A4.2.2: Specification of the Interoperability Applied Framework T.A4.2.3: Specification of the Interoperability Technical Framework Collaboration with AL A Receives from All AL A projects Provides to All AL A projects Programme Key Results
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A4.3 Product-based Interoperability Infrastructure Leading Participant TROUX Starting M10 Ending M36
Objectives The WP will implement the 3 layers of the framework defined in WP A4.2 (conceptual, applicative and technical with a special focus on the latter), following product-based Interoperability Approach. Subject of study will be knowledge and enterprise models, innovation projects, human competencies, workplace interaction aspects of Interoperability within the Programme Interoperability Framework. As part of the results this WP will contribute to the implementation of the AI Profiles the defined in WP2 on selected scenarios in the CDP and Portfolio Management areas.
Description of Work T.A4.3.1: Detailed Specifications of Product-based Interoperability Infrastructure T.A4.3.2: Implementation and Testing of Product-based Interoperability Infrastructure T.A4.3.3: Validation and Verification of Product-based Interoperability Infrastructure Collaboration with AL A projects B5 Technology Testing Networks and Scenarios Receives from D.A4.2 Specification of Interoperability Framework and Profiles, Guidelines and Best Practices (and its interim versions) Provides to D.A4.2 Specification of Interoperability Framework and Profiles, Guidelines and Best Practices (and its interim versions) B5 Technology Testing Networks and Scenarios Programme Key Results
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A4.4 Process-based Interoperability Infrastructure Leading Participant SAP Starting M10 Ending M36
Objectives The WP will implement the 3 layers of the framework defined in WP A4.2 (conceptual applicative and technical with a special focus on the latter), following process-based Interoperability Approach. Subject of study will be the workflows, e-commerce transactions, business interconnectivity, systems integration aspects of Interoperability within the Programme Interoperability Framework. As part of the results this WP will contribute to the implementation of the AI Profiles of the defined in WP2 on selected scenarios in the SCM and e-procurement areas.
Description of Work T.A4.4.1: Detailed Specifications of Process-based Interoperability Infrastructure T.A4.4.2: Implementation and Testing of Process-based Interoperability Infrastructure T.A4.4.3: Validation and Verification of Process-based Interoperability Infrastructure Collaboration with AL A projects B5 Technology Testing Networks and Scenarios Receives from D.A4.2 Specification of Interoperability Framework and Profiles, Guidelines and Best Practices (and its interim versions) Programme Key Results Provides to D.A4.2 Specification of Interoperability Framework and Profiles, Guidelines and Best Practices (and its interim versions), B5
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A4.5 Interoperability Feasibility & Planning (F&P) Services Leading Participant TXT Starting M13 Ending M36
Objectives The WP will provide methodologies and software tools in the form of seamless and configurable inter-connection software components services. The resulting toolset will be the basic set of software and engines that would evaluate the interoperability situation of an enterprise with respect to the need to interoperate with another in a selected context, in order to detect if a request for interoperability (project A2) can be matched against the models (A1), knowledge (A3), services (A5), data (A6) of the enterprise and what architectures to adopt (Feasibility Services) and then plan the roadmap for achieving the desired level of interoperability (Planning Services).
Description of Work T.A4.5.1: Detailed Specifications of Interoperability F&P Services T.A4.5.2: Implementation and Testing of Interoperability F&P Services T.A4.5.3: Validation and Verification of Interoperability F&P Services
Collaboration with AL A project deliverables & prototypes Receives from A4.2 – Athena Interoperability Framework – Guidelines and Best Practices AL A projects Provides to
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A4.6 Interoperability Operations & Governance (O&G) Services Leading Participant TXT Starting M13 Ending M36
Objectives The WP will provide methodologies and software tools in the form of seamless and configurable inter-connection software components services. The resulting toolset will provide:
services aiming at implementing the Integrated, Unified, Federated approaches to Interoperability, with a specific focus on the initiation of the operative e-commerce networked business (Operations Services);
services aiming at �esponsable measuring, controlling and optimising the interoperability quality attributes as well as detecting anomalities, alarms, and launch recovery procedures. (Governance Services)
Description of Work T A4.6.1 Detailed Specifications of Interoperability O&G Services T.A4.6.2: Implementation and Testing of Interoperability O&G Services T.A4.6.3: Validation and Verification of Interoperability O&G Services
Collaboration with AL A projects deliverables & prototypes Receives from A4.2 – Athena Interoperability Framework – Guidelines and Best Practices AL A projects Provides to Programme objectives
Work Package A4.7 Project Management Leading Participant TXT Starting M7 Ending M36 Objectives Project management takes care of the following issues: collaborations between projects and action lines, progress control, control of creation and submission of deliverables and results, quality assurance, reporting and detailed implementation planning for the project. The individual work package leaders are responsible for the application of the same scope as the project management.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Activity Objectives Service-Oriented Architectures are being viewed as the next wave of technology to impact the computing landscape by enabling the utilisation of distributed components by allowing software vendors to provide not only applications to market but a suite of services that can be utilised by a wider audience and charged for through an access or usage business model. This project is concerned with the development of service-oriented solutions that can be more easily planned and then later customised when they are being deployed. This is intended to provide better industry focused solutions that can be adapted better for deployment into client environments. This is to directly counter the problem of high costs of customisation and integration of highly generic industry solutions. The main objectives of this project are:
− to develop modelling and specification systems that accurately express services and service-oriented architectures and particularly assist in the planning of solutions and the marking of intended customisations for the better deployment of a solution into a wide range of client environments;
− to develop technologies that enable the easier composition of services and the brokering, mediation and ultimately the negotiation of pre-specified but customisable services;
− to develop an execution framework for planned and customisable service-oriented architectures utilising user scenarios from the ATHENA community processes (Activity B4); and
− to evaluate the developed technologies and execution framework in proto-typical implementations.
It is foreseen that this project will collaborate bi-laterally with other ATHENA research projects in the areas of semantic knowledge, cooperative business scenarios and mediation. After the first 18 months of this project the following foci will be considered:
− considering user scenarios that widen the industry focus and push towards the development of more generic solutions utilising the previously developed principles of planning and customisation;
− more generic approaches to the development of semantic ontologies, the tools required and the execution frameworks to effectively utilise the captured knowledge; and
− refinement of composition and negotiation frameworks.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
A5.2 Models and Specifications for Service Description (Functional and Non-Functional), Registry, Discovery and Usage
15 – SINTEF 31,1 M1 M18
A5.3 Applying Semantics to Service-Oriented Architectures
1 – SAP 15,6 M7 M15
A5.4 Service Composition 1 – SAP 22 M10 M15 A5.5 Service Brokering, Mediation and Negotiation 6 – DFKI 15 M10 M15 A5.6 Execution Framework(s) for Planned and
Customisable Service-Oriented Architectures 1 – SAP 25,7 M13 M21
A5.7 Validation of Research Results 9 – Formula 10,1 M16 M24 A5.8 Project Management 1 – SAP 5,8 M1 M24
137 M1 M24
Deliverables List
Deliverable No Deliverable Title Project /
WP No Lead
Participant Nature Dissemi-
nation level
Delivery Date
D.A5.1 Perspectives on Service-Oriented Architectures and there application in environments that require solutions to be planned and customisable.
A5.1 ESI R PU M21
D.A5.2 Model and Specification of service description and usage as well as advanced concepts
A5.2 A5.3 A5.4 A5.5
SINTEF & DFKI
R RE M18
D.A5.3 Architecture of SOA platforms A5.2 A5.3 A5.4 A5.5 A5.6
SAP R RE M21
D.A5.4 Execution Framework(s) for Planned and Customisable Service-Oriented Architectures
A5.6 SAP R, P CO M21
D.A5.5 Validation of Research Results A5.7 Formula R PU M24
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
WD.A5.1 Perspectives on Service-Oriented Architectures and there application in environments that require solutions to be planned and customisable.
A5.1 ESI M04 M09 M15
WD.A5.2 Technical architecture and implementation of services and their concepts
A5.2- 6 SAP M12 M18
WD.A5.3 Model of service descriptions and service usage A5.2 SINTEF M12
Contribution to Milestone Milestone Contribution to Milestone
M.12 − Models of service description and usage
M.24 − Model and Specification of service description and usage as well as advanced concepts
− Specification and modelling of service composition framework − Modelling and specification framework for expressing semantics in SoAs − Service brokering & negotiation framework and protocols − Service composition framework − Execution framework for planned and customisable SoAs
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A5.1 Service-Oriented Architectures, Principles, Designs, Models & Methodologies
Leading Participant ESI Starting M1 Ending M21 Objectives
Illustration and understanding of service-oriented architectures with respect to their principles, designs, models and methodologies Assessment of state of the art technologies and evaluation with respect to the project objectives of developing planned and customisable service-oriented architectures Description of Work In this work package knowledge about service-oriented architectural state of the art will be gathered in the areas of principles, designs, models & methodologies. This work will be guided by scenarios from end users (provided by Activity B4) and suggestions for the application of the technology collected. Business requirements will be provided by Activity B3. Input from B3 and B4 will be mapped onto technical requirements and guide the state of the art analysis throughout the project. Specification of requirements for agent technologies in the context of service-oriented architectures will also be considered for the correct positioning of future project work. Task A5.1.1: Develop an understanding of state-of-the-art for service-oriented architectures when
applied to the problem of developing solutions through planning and later customising implementations
Task A5.1.2: Understanding of user scenarios and the strength of the solutions when applied to the principles of planning and customising service-oriented architectures. Identify the criteria for improvement that research results will be measured against.
Task A5.1.3: Requirements of agent technology will be collected with respect to the application within service-oriented architectures and in the focus of the user scenarios.
Collaboration with Receives from B4 User-level requirements and scenarios B3 Business Interoperability Issues Provides to WPs of A5 Technical requirements A4.3 Input
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A5.2 Models and Specifications for Service Description (Functional and
Non-Functional), Registry, Discovery and Usage Leading Participant SINTEF Starting M1 Ending M18 Objectives Define models and their associated specifications, applicable for the representation of service descriptions, involving both functional and non-functional elements Service registries will also be investigated for the collection and effective discovery of services utilising functional and non-functional elements Usage frameworks will be investigated and specified for a service-oriented environment that focuses upon the planning and customisation of solutions Description of Work In this work package particular focus is applied to the modelling and specification of different aspects of service-oriented architectures and how services can mature (initially focusing upon technical elements and later software engineering life-cycle features), be interoperable and contain a representation of high-quality. Task A5.2.1: Identification of modelling and specification approaches to service description,
including results from other partner projects on this (i.e. COMBINE, ACE-GIS) and related OMG UML 2.0 results and DAML-S.
Task A5.2.2: Investigate how FIPA infrastructure specifications (directory services, service descriptions) fit into the overall framework
Task A5.2.3: Specification of meta-modelling and methodology approaches to represent mature, interoperable and high-quality web services.
Task A5.2.4: Generation of web service registries that can foster a business environment for service-oriented commerce (including the certification of the quality of the services offered)
Collaboration with A5.6 Service Descriptions and Registries for Service Oriented Architecture and Execution
Framework A6.2 & A6.5 Service Descriptions and Registries especially the representation non functional
requirements Receives from
Provides to A3.4 Input on WS Repositories Integration Models and Specifications for Service-Oriented Architectures
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A5.3 Applying Semantics to Service-Oriented Architectures Leading Participant SAP Starting M7 Ending M15 Objectives Understand how semantic structures can be applied to service-oriented architectures and in particular to the service solutions that can be planned and customised Description of Work Semantic focused work packages will be undertaken in other ATHENA Projects. The results from these work packages will be applied to service-oriented architectures and in particular their applicability in assisting in the development of solutions using a “plan and customise” approach. It is anticipated that the result of the application of semantics may be either through the annotation of existing specifications such as WSDL to capture both functional and non-functional elements (as contributed in WP A5.2), or the specification of additional standardisation activities. Either result path will be utilised for external impact through ATHENA Action Line B Projects. Task A5.3.1: Semantic Annotation of the Service-Oriented Meta-Model to Specify and Design
Mature Web Services (extending the work of WP A5.2) Task A5.3.2: Investigation of DAML-S Specifications in the Context of Service-Oriented
Architectures. Collaboration with Receives from A3 Especially tools to support capturing of semantics Provides to A3.4 , A3.6 Semantic annotation of services
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A5.4 Service Composition Leading Participant SAP Starting M10 Ending M15 Objectives Design and description of composition models in planned (pro-active) and dynamic (re-active) environments Specify formal requirements for service descriptions especially with respect to plan-based composition of customisable services Development of an executable framework for service composition Investigation of agent-based composition frameworks and there application to the general service-oriented environment Description of Work The subject of service composition will be investigated from both the service provider and service consumer points of view. A focus will be provided to the specification of a composed service’s description, the design of the composition models (including available methodologies and paradigms), the applicability of agent-based technologies and the prototyping of a composition environment as a contribution to the later work package on deployment of a planned and customisable service-oriented architecture. An investigation of agent-based service composition, especially with respect to DAML-S service specifications, will be undertaken. Ultimately, seamless integration of service descriptions with agent execution patterns should be achieved. Applicable notice will be given to existing standards for service composition and areas identified for unique impact will be investigated for standardisation inputs. Task A5.4.1: Development of Models and Specifications for the Composition of Services Task A5.4.2: Development of Composed Service Descriptions Task A5.4.3: Prototyping of Executable Framework for Service Composition that will Explore
Composed Service Descriptions and the Usage of Agent-Based Technologies Collaboration with Receives from
Provides to
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A5.5 Service Brokering, Mediation and Negotiation Leading Participant DFKI Starting M10 Ending M15 Objectives Describe and design service brokering, mediation and negotiation architectures Specify a framework for brokering, mediation and negotiation protocols for service deployment Description of Work This work package is concerned with, but not limited to, the investigation and demonstration of prototype frameworks for resolving problems such as: run-time matching of services (from consumer to provider); service wrapping and decomposition; and run-time dynamic service discovery and usage. Investigation of technologies that allow the brokering, mediation and negotiation of terms and conditions of service executions both from the server’s and the client’s side. Investigation of speech-act-based protocols and their representation for easy protocol execution will be undertaken. Full negotiation of terms and conditions of services is the ultimate goal of this thread of research. Task A5.5.1: Investigation and Specification of Protocols for Negotiation of Functional Service
Properties Task A5.5.2: Frameworks for the Design of Service Brokering, Mediation and Negotiation
Functionality Task A5.5.3: Frameworks for the Execution of Service Brokering, Mediation and Negotiation
Concepts Collaboration with A3.7 Reconciliation of incompatibilities in services Receives from A3.4 Semantic Annotation Methodology and Tool Provides to A3.7 Service Mediation (and semantic service description from WP A5.3) A3.8 Runtime Service Discovery and Usage
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A5.6 Execution Framework(s) for Planned and Customisable Service-
Oriented Architectures Leading Participant SAP Starting M13 Ending M21 Objectives Development of an execution framework(s) that illustrate the service-oriented architectures that can be built to support planned and customisable solutions Description of Work This work package will design and develop the architecture for an execution framework(s) that will enable planned and customisable service-oriented architectures for industry solutions. An agent-based service orchestration framework will be integrated with a particular focus on customisable solutions. A further focus of this agent-based work is also the specification of a database for agent execution patterns. Task A5.6.1: Design and Development of an Execution Framework(s) that enables the Planned
and Customisable Approach towards Service-Oriented Architectures Task A5.6.2: Design, Development and Integration of an Agent-Based Service Orchestration
Platform Task A5.6.3: Development of a Modelling Tool using the UML Profile for Web Services developed
in WP A5.2 Collaboration with A5.7 on validation of the execution framework against the identified technical
requirements A6.6 on general design and software engineering as well as infrastructure Receives from A4.3 Results as input and provide cross-filtering in deliverables of this WP A5.2-A5.5 Specifications for Implementation Provides to A4 Part of Interoperability Support Infrastructure
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A5.7 Validation of Research Results Leading Participant Formula Starting M16 Ending M24 Objectives Validation of the proof-of-concept service-oriented execution framework(s), involving models and tools developed in this project using the technical requirements identified in WP A5.1 and other work packages Results will be collected and provided to Action Line B activities Description of Work The purpose of this work package is to validate the research results achieved in A5 against the initial requirements identified in A5.1 and subsequently in most WPs using the criteria for improvement identified in task A5.1.2. Models, tools and frameworks defined in previous work packages will be iteratively validated and will provide feedback for the definition of high impact results, and important inputs into Action Line B activities. Collaboration with A5.6 on execution frameworks for planned and customisable SOA and their validation Receives from A5.1 technical requirements, user scenarios and criteria for improvement A5 achieved research results Provides to B5 take over results from this project and apply them in user scenarios B5 research results validated against technical requirements A5 results of validation
Work Package A5.8 Project Management Leading Participant SAP Starting M1 Ending M24 Objectives The aim of project management is to take care of the following issues: collaborations between projects and action lines, progress control, control of creation and submission of deliverables and results, quality assurance, reporting and detailed implementation planning for the project. The individual work package leaders are responsible for the application of the same scope as the project management. For the coordination of the overall progress monthly conference calls or web-conferences and Technical Committees Meetings (comprising the work package leaders) at least every 6 months will be organized by the project lead. The work package leaders and the project leader will provide alternating a progress report (months 6, 12, 18,…) and a status report every 3 months (months 3, 9, 15, ….) For the yearly planning and review checkpoints the project management will provide an up dated detailed implementation plan proposal to the Action Line Coordination 11 months after project start. Description of Work Task A5.8.1 Technical project management: Task A5.8.2 Mid term action planning
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Project Objectives The main objective of model-driven and adaptive interoperability architectures is to provide new and innovative solutions for the problem of sustaining interoperability through change and evolution, by providing dynamic and adaptive interoperability architecture approaches. The objective is to advance state of the art in this field, by applying the principles of model-driven, platform independent architecture specifications, and dynamic and autonomous federated architecture approaches, including the usage of agent technologies. This includes the following subgoals
− To support requirements and validate solutions for the involved sectors from project B4/5,A4 − To provide meta models & methodologies for interoperability architecture solutions − To evaluate and extend multiple adaptive autonomous and federated architecture approaches,
including Agent and Peer Technologies and the Model-Driven Architecture approach. − To provide support for non-functional interoperability aspects, through a model-driven approach − To apply the use of ontologies and semantics in model and service Registry/Repositories for
better semantic interoperability − To provide semantic mapping and mediation technologies − To provide executable frameworks and support for active models The initial state-of-the art analysis will also cover component-based and message/document-based architectures, while later phases of the IP may further address others like Grid architectures. A focus on semantic interoperability is based on the use of knowledge and ontology support from project A3.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Detailed Work Package Description Work Package A6.1 Model-Driven and Adaptive Interoperability Architectures, Meta-
Models & Methodologies Leading Participant SINTEF Starting MO1 Ending M12 Objectives To provide a basic architecture reference model. Investigate various approaches to interoperability architectures based on platform independent model-driven descriptions, with a particular focus on adaptive approaches and architectures, meta-models and tools for system descriptions and the associated methodology.
Description of Work A Model-Driven Architecture approach that separates platform independent models (PIMs) from platform specific models (PSMs) with a link to enterprise/business models will provide a good foundation for open and configurable interoperability architectures. The initial focus is on providing basic meta-models and tools for platform independent system descriptions. This work package will have strong interactions with project A4 with regards to reference architecture and user scenarios and requirements, also linked to B4.
Task A6_11: State of the art in research, standards, and technologies – Interaction with INTEROP NoE
Task A6_12: Investigation of meta-models for the various architectural approaches
Task A6_13: Evaluation of existing tools for system model specifications (UML 2.0 based w/extensions)
Task A6_14: Specification of execution Infrastructure to support the various approaches
Task A6_15: Requirements and pilot/demonstrator specifications
Collaboration with A4 Interoperability Reference models Receives from B3, B4 User and Business Requirements Provides to A4 and other A6.x Interoperability architecture reference model
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A6.2 Application of Ontologies and Semantics to MODAIA Registries /
Repositories Leading Participant SAP Starting M06 Ending M22 Objectives To support system descriptions with semantic enhancements by results from ontology research and development, and supported by registries and repositories.
Description of Work Develop semantic interoperability support through registry/repositories extended from a combination of service-oriented registries like UDDI, business-process/information repositories like ebXML RegRep, model-repositories like the OMG MOF (Meta Object Facility) and Ontology-based catalogues. An ontology basis for semantic descriptions will be provided through interaction with project A3.
Task A6_21: Semantic extensions for system descriptions and models
Task A6_22: Flexible Registry/Repository/Catalogue support for both platform independent and platform specific models
Task A6_23: Inclusion of and interfaces to agent technologies
Collaboration with A4 Interoperability Reference models Receives from B3, B4, A4 Semantic Registry/Repository information Provides to A4 and other A6.x Interoperability architecture reference model
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A6.3 Semantic Mapping and Mediation technologies Leading Participant SINTEF Starting M06 Ending M22 Objectives To support various transformations and mapping approaches for mediations between non-matching models, including service and information model transformations based on UML and agent-based dynamic mediation.
Description of Work Various approaches for mapping and mediation will be evaluated and supported, e.g. agent-based mediation and use of speech-act protocols. A model-mapping tool will be provided to integrate and relate platform independent service and information models, with a corresponding execution support on the platform specific level for UML system models. An ontology basis for semantic interoperability will be provided through interaction with project A3.
Task A6_31: Framework for Dynamic Service Mediation and Composition
Task A6_32: Agent-based matchmaking and mediating of services.
Task A6_33: Semantic UML mapping tool – based on UMT (UML Model Transformation) open source toolkit
Collaboration with A3/A5 Semantic mapping and mediation Receives from A2.3, A3.6, A5.5 Semantic mapping/mediation support Provides to A4 and B4/B5 Solution for scenarios
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A6.4 Adaptive Autonomous Architectures: Agent and Peer Technologies Leading Participant DFKI / SIEMENS Starting M01 Ending M24 Objectives − Provide meta-models, tools, and methodology for model-driven interoperable agent and peer-to-
peer architectures − Use autonomous computing vision as a guideline to define adaptive and self-healing systems − Achieve autonomous, goal-oriented, reactive and pro-active problem solving − Provide flexible interaction mechanisms and mapping patterns for a dynamic environment Description of Work Investigate peer-to-peer solutions and technologies as well as agent technologies and multi-agent systems in the context of service-oriented architectures. Such technologies will introduce flexibility and pro-activeness in settings where goal-oriented flexible service discovery, mediation, and composition are the main focus of research.
Task A6_41: Adaptive agent interoperability support architectures
Task A6_42: Protocols for agent-based composition and negotiation of services.
Task A6_43: Adaptive peer-to-peer interoperability support architectures
Task A6_44: Updated execution infrastructure support for the various approaches
Collaboration with A2/A3 Business process models and semantics Receives from A2.2, A3.3 Business process models and semantic descriptions Provides to A4 and B4/B5 Solution for scenarios
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A6.5 Model-driven Service Oriented Architectures Leading Participant ESI Starting M01 Ending M24 Objectives Provide meta-models, tools, and methodology for model-driven interoperable service oriented architectures, in particular to provide better support for variations in platforms and technology representations. Including to provide interoperability support for non-functional aspects like security, roles and policies, safety and trust and Quality of Service (QoS).
Description of Work A model-driven architecture approach that separates platform independent models (PIMs) from platform specific models, and with a link to enterprise/business models will provide a good foundation for open and configurable interoperability architectures. The initial focus is on providing basic meta-models and tools for platform independent system descriptions, including non-functional aspects like Quality of Service, based on the architectural modelling support of UML 2.0.
This work will be coordinated with the service-oriented architecture work in project A5.
Task A6_51: Meta-Models for the Service-Oriented Architectural Approach
Task A6_52: Tools for System Service Model Specifications e.g. WSDL, BPEL/BPML, OWL, DAML-S, …
Task A6_61: Support for non functional interoperability (security , roles/policy, trust, safety, quality of service)
Collaboration with A5 Service oriented architectures Receives from A2.2, A1.3, A3.2, A3.3, A54, A55 Process models and service models and semantic descriptions Provides to A4 and B4/B5 Solution for scenarios
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A6.6 Execution Frameworks and Active Models Leading Participant IBM Starting M06 Ending M24 Objectives − Provide execution frameworks that can support the model-based descriptions for various
interoperability architecture (agent-based and service-based), including incremental support for active and executable models – and simulation models.
− Run-time support for visual scenes, as developed in project A1 − Support adaptive systems through active run-time interpreted models from enterprise to system
models with the supporting intelligent infrastructure Description of Work Specification of an agent-based execution model: Investigation of mappings of models to agent execution concepts (e.g. BDI plans). If necessary, specification of restrictions to models that actually can be transformed. Run-time support for enterprise and system models, as emerging from the visual scene approach from project A1.
Task A6_61: Execution-Time Interoperability Support Frameworks for Agent Based Architectures
Task A6_62: Execution-Time Interoperability Support Frameworks for Service and business process Oriented Architectures
Task A6_63: Model Run-Time Interpreter Infrastructure for Visual Scenes
Collaboration with A5.6 Service oriented architecture execution support Receives from A5.6 Service execution models Provides to A4 and B4/B5 Solution for scenarios
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A6.7 Deployment of Prototypes within Scenario Environments Leading Participant CRF Starting M12 Ending M24 Objectives Iterative deployment and requirements gathering/validation of the proof-of-concept model-driven and adaptive execution framework(s), applying models and tools developed in this project to chosen user scenarios Results will be collected and provided to Action Line B and A4 activities
Description of Work The purpose of this work package is the deployment of the proof-of-concept model-driven and adaptive execution framework in the context of the requirements and scenarios from action line B and A4. The results achieve in this project will be applied to an appropriate number of interoperability scenarios with respect to the initial user requirements collected.
Models, tools and frameworks defined in previous work packages will be iteratively applied to the identified scenario environments and will provide feedback for the definition of high impact results, and important inputs into Action Line B activities.
Task A6_71: Development of User Scenario Deployment Framework Documentation
Task A6_71: Definition of the proof-of-concept Scenarios with respect to the Paradigms and Meta-Models defined in WP A5_2 and B4.
Task A6_71: Integration of Results from other Work Packages into a Service-Oriented Solution Deployed to a Real Business Scenario Environment
Task A6_71: Assessment of the Proof-of-Concept Service Deployment and Composition Scenario
Collaboration with A4 Pilot scenarios Receives from A6.2, 6.3, 6.4, 6.5, 6.6 Solutions Provides to A4 and B4/B5 Solution for scenarios
Work Package A6.8 Project Management Leading Participant IBM /
SIEMENS Starting M01 Ending M24
Objectives
This work package covers the efforts of managing the project
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Activity Objectives Business Documents are the key elements that are exchanged between cooperating business partners. The documents are the external representation of internal Business Objects (also called Business Information) of the partners. Business Protocols define the interaction between partners in terms of which of these documents are exchanged in which order. Efficient and easy management of Business Documents and Protocols is important to improve interoperability of networked organisations. This enhances the scope of the work performed in projects A1 to A6 and is an essential part in enterprise system and application interoperability. A7 relates to the Action Line A projects and makes use of results achieved there. Furthermore, it is embedded in the context of Action Line B especially activities B4 and B5 for industrial user scenarios and piloting. This project focuses on Business Documents as external representation of internal Business Objects and the associated protocols. The objectives of this project are in detail:
- Analysis of Business Document and Protocol standards: o Understand relevant Business Document and Protocol standards for B2B
interactions o Relate Business Document and Protocol standards for B2B interactions to industry
best practice
- Lifecycle management for Business Documents and Protocols: o Create Business Documents and Protocols ensuring consistency and reuse o Store and retrieve Business Documents and Protocols o Mapping external Business Documents to and from internal Business Objects
- Creation of business content using ATHENA tools for selected industry best practice Furthermore the following objectives are orthogonal to these objectives and have to be considered in all activities of the project:
- Evaluate applicability of ATHENA results for business document exchange
- Consider different modelling layers for Business Documents and Protocols (business layer – technical/solution layer – execution layer)
- Support variants of Business Documents and Protocols1
1 A Business Document Variant is considered to be derived from the same document base-type and has most fields in common; but some fields are added, removed, or have changed meaning.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A7.1 Identification and Analysis of Industry Best Practice in Business
Documents and Protocols Leading Participant DFKI Starting M20 Ending M24 Objectives
- Identify and analyze industry best practice for Business Documents and Protocols
- Understand and relate industry relevant standards for B2B interactions to industry best practice in the field of Business Documents and Protocols
Description of Work The identification should be based on market research, ATHENA scenarios and other requirements. The results will be related to relevant Business Document and Protocol Standards. This will lead to the selection of a set of Industry Best Practices and Standards for further consideration. Collaboration with B4 Refine Industrial User Scenarios based on analysis Receives from B4 Industrial User Scenarios and derived requirements Provides to A7 WPs Selection of a set of Industry Best Practices and Standards
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A7.2 Creation of Business Documents and Protocols Leading Participant SAP Starting M25 Ending M34 Objectives
Provide a method and tool support for creating Business Documents and Protocols supporting reuse. In particular, the following aspects have to be considered by the modelling method:
- different modelling layers for Business Documents and Protocols
- internal and external representation of business documents
- support for modelling and implementation of interaction patterns for business protocols
- variants of business documents and protocols Description of Work
Based on the results achieved in the Action Line A projects on methods for enterprise modelling, business process modelling and on semantic annotations we will develop a method for modelling Business Documents and Protocols. The modelling method will also consider appropriate external representations of Business Documents. The modelling layers for Business Documents and Protocols (business, technical/solution, execution) will be related to data modelling concepts (conceptual, logical, physical) and to MDA concepts (CIM/PIM/PSM). It will be investigated which aspects need to be considered on each layer and have to be reflected appropriately in the models for the different stakeholders on each layer. Furthermore, the modelling method has to support reuse of Business Documents and Protocols. Also an efficient variant handling has to be provided. Regarding Business Protocols we will extend the work that has been done in project A2 on business processes to provide modelling and implementation support for interaction patterns. Interaction patterns describe patterns for message exchanges that occur in real-world interaction scenarios but can only partially or not at all be expressed on business process level. For instance, on business process level it is described that an activity (e.g. a bank transfer) has to be executed as a transaction but not which documents and messages have to be sent in which order to realize a valid transaction. This is covered by the interaction patterns. Task A7.2.1: Modelling of Business Documents including variant handling
Task A7.2.2: Modelling and Implementation of Interaction Patterns for Business Protocols Collaboration with A7.3 Requirements for Storing and Retrieving Business Document and Protocol Models
A7.4 Mapping of Business Documents A7.5 Model and tool for creating Business Documents and Protocols Receives from A1 POP* model for Collaborative Enterprise Modelling (D.A1.3.1) A2 Modelling method and tools for business processes: Methodology (Deliverable D.A2.3); CBP modelling tool developed in A2 A3 Tools and method for Semantic Annotation (Deliverable D.A3.2) A5 Method for modelling logical services (Deliverable D.A5.2) A6 Meta-models and tools for platform-independent system descriptions Provides to A7.3/A7.4 Model and annotation of Business Documents and Protocols A4 Provide models and tools to AIF B5 Validation in Pilots
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A7.3 Business Document and Protocol Repository Leading Participant SIEMENS Starting M25 Ending M34 Objectives
- Define repository for Business Documents and Protocols including business, technical and execution layer models
- Provide Storing and Querying capabilities for Business Documents and Protocols
- Support reuse and variant requirements Description of Work Starting from work on repositories and registries for public documents performed in A6 and A1 and building on results of repository work performed in the Action Line A projects we will define an architecture for the Business Document and Protocol repository. The following aspects have to be considered:
- Public repository versus enterprise-internal repository, i.e. will the Business Document and Protocol repository be public available for all partners or does each organization have its own one?
- Integration of multiple repositories, e.g. for flexible business level documents as well as more structured execution level documents, since results from A-line projects have shown that one repository will not fit all needs. Multi-party peer-to-peer approaches and hub-and-spoke approaches with a central reference registry will be explored.
- Storage of models and instances of Business Documents and Protocols: Are models and instances of Business Documents and Protocols stored in the same repository or are different repositories used?
- Also mechanisms for access control will be considered taking into account existing approaches. Task A7.3.1: Repository Architecture Task A7.3.2: Store, Query and Retrieve Interfaces Collaboration with A7.2 Requirements for storing and retrieving Business Documents and Protocols
A7.4 Storing and querying mapping and transformation information for Business Documents A7.5 Business Document and Protocol repository Receives from A3 Results on Repository for Ontology Authoring and Management System (D.A3.1) A6 Enhanced Registry/Repository Architecture (Deliverable DA6.2) and P2P Business Resource Management Framework (Deliverable D.A6.3) A1 Repository results from Collaborative Modelling Platform (Deliverable D.A1.5.1 / D.A1.5.2) Provides to A7.5 Business Document and Protocol repository A8 Repository configuration suitable for SMEs B5 Validation in Pilots
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A7.4 Mapping of Business Documents Leading Participant IBM Starting M25 Ending M34 Objectives
- Validate the results related to mapping and transformation of business documents from A3 and A6 on different scenarios and selected industry best practice for Business Documents
- Provide methods and tool support for mapping external Business Documents to and from internal Business Objects during design time and for transformation of business document instances during runtime covering different user cases
- Provide a method and tool for simulation/visualization and evaluation of Business Documents and Protocols
Description of Work We will validate the results provided by A6 on model transformations and by A3 on business document transformation on different user scenarios and selected industry best practice for business documents and protocols. This will describe which transformation approach is better suited for which use cases. Based on that validation and the tools provided by A3 and A6 we will develop method and tool support to map Business Documents to Business Objects and to transform instances of Business Objects in instances of Business Documents during runtime. One aspect of this mapping is that only the relevant fields of Business Documents should be exchanged.
Mechanisms for simulation and visualization will be developed to be able to check the validity and correctness of modelled Business Protocols, mappings and transformations. These mechanisms will allow to simulate Business Protocols and to evaluate the exchanged Business Documents. They will monitor and validate the mappings and transformations defined. Therefore, we build on work performed in A2 for business process simulation and in A5 for message validation.
Task A7.4.1: Validation of A3 and A6 results related to mapping and transformation of Business
Document Task A7.4.2: Mapping of Business Documents to and from Business Objects and transformation
of Business Document instances building on results from A3/A6 Task A7.4.3: Simulation and evaluation of Business Documents and Protocols Collaboration with A7.2 Models of Business Documents and Protocols A7.3 Requirements for storing and querying mapping and transformation data A7.5 Methods, tool, and operators for mapping Business Documents and Protocols Receives from
A7.1 Selected industry best practice on Business Documents A7.2 Models of Business Documents and Protocols A6 Methods and tools for transformation of Business Documents (Deliverable D.A6.4) A3 Reconciliation rules specification and engine (Deliverables D.A3.3 and D.A3.4) A2 Results on business process simulation (Deliverable D.A2.4) A5 Methods and tools for message validation B4 Industrial user scenarios Provides to
B5 Validation in Pilots
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A7.5 Application of Approach to Selected Industry Best Practice Leading Participant SAP Starting M31 Ending M36 Objectives
- Validate approach for selected Business Document and Protocol standards, ATHENA scenarios and industry best practice
- Creation of business content using ATHENA tools Description of Work Use the ATHENA approach and tools for Business Document and Protocol management and apply them to selected Business Documents and Protocols. The resulting Business Documents and Protocols are stored in the Business Document and Protocol Repository. Collaboration with A7.2/A7.3/A7.4 Apply and validate results achieved in the WPs Receives from A7 ATHENA approach (method, tools) for Business Document and Protocol management A1-A6 Tools, Infrastructures and results to be used for content creation A7.1 Selected Business Document and Protocol industry best practice Provides to EIC Experience using the ATHENA approach
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A7.6 Project Management Leading Participant SAP Starting M20 Ending M36 Objectives
The objective of the Project Management is to coordinate
- the research activities in the project,
- the coordination with other projects,
- the development of deliverables and results, to control
- the performance of quality assurance activities
- the timely submission of deliverables, and to provide reporting on technical progress and costs of the project Description of Work Task A7.6.1: Technical Project Management Task A7.6.2: Progress and Cost Reporting
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Activity Objectives SMEs face growing problems in keeping pace with the rapidly changing technology cycles. In many cases the investments made to resolve existing interoperability problems in products of major ICT suppliers have ended up having the opposite effect, increasing costs and reducing flexibility. The limited organizational structure, IT and resource capacities, together with the often informal organization of SMEs in which one person is responsible for large parts of the internal value chain, make it difficult, if not impossible, for SMEs to apply the same interoperability solutions as larger organizations. It is therefore required to provide interoperability solutions particularly adapted to the special needs and requirements of SME environments, so as to enable them to participate in digital ecosystems. These solutions and the software that realizes them need to be adaptable and configurable by the end-users, in order to allow them to address and support the rapidly changing business and processes that are needed to stay competitive in an ever faster changing economy. Considering the limited organizational, infrastructure and resource capacities of SMEs, it is furthermore essential that interoperability solutions, in order to be feasible for SMEs, can either be easily integrated in the existing ICT infrastructure of SMEs, or be accessed and used via provision channels and interfaces that are decoupled from the organization-internal ICT infrastructure. The objectives of this project are:
- To understand the structural and qualitative differences of interoperability requirements of SMEs compared to those of larger enterprises
- To analyze typical interoperability scenarios in OEM-SME relationships and networks of SMEs
- To evaluate the applicability of ATHENA results in SME environments
- To develop guidelines and best practice reports on how to apply ATHENA results as documented in the ATHENA Interoperability Framework (AIF) in SME environments
o This will include a roadmap on how to establish the core capabilities required for applying and making use of the described solutions,
- To adapt, integrate and target solutions for SMEs, based on ATHENA results and supporting user involvement, flexibility and adaptability.
- To establish a link with the activities of the B5 sub-project calls through the support and maintenance of the tools and solutions used in these piloting activities with SMEs, and the integration of feedback results received.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A8.1 Analysis of Interoperability Situation and needs of SMEs and current
approaches Leading Participant ESI Starting M20 Ending M24 Objectives
- Understand how technical and business interoperability requirements of SMEs are different to those of larger enterprises
- Collaborate with B5 sub projects to identify Interoperability situation and needs for SMEs
- Identify common interoperability scenarios as guidance for A8 Work Packages Description of Work The scenario types to be analysed might include OEM-SME connectivity and SME networks and be based on the same domain, for facilitating the analysis of structural and qualitative differences of interoperability requirements in SMEs and larger enterprises. Sources of scenarios to be analysed include ATHENA partners with relevant experience in the SME domain. Industry best practices regarding technical and business interoperability will be analyzed and a characteristic (SME) interoperability scenario will be defined as a guideline and common problem definition for the A8 workpackages, particularly for the development of integrated and targeted solutions for SMEs based on ATHENA results in WPA.8.4. Task A8.1.1: Analyse interoperability scenarios in OEM-SME settings and SME networks Task A8.1.2: Evaluate differences in interoperability requirements of SMEs and large enterprises. Task A8.1.3: Define a characteristic (SME) interoperability scenario as common problem
definition for A8 workpackages Collaboration with INTEROP WP12 SME situation and requirements Receives from B4,B5 SME requirements Provides to
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A8.2 Aspects of adaptability, configurability and provision Leading Participant TROUX Starting M24 Ending M30 Objectives
- Define requirements and modes of user configuration and composition of interoperability solution services and platforms
- Develop an approach for user performed and model driven adaptation of generic solutions to common interoperability scenarios
- Identify and describe appropriate models for provision and operation of solution services to SMEs
Description of Work The definition of the requirements and modes of user configuration and composition of solutions and platforms will be derived from the results of WP8.1 and take into account the different modes of provision and operation identified in Task A8.2.3. The approach for user performed and model driven adaptation of generic solutions will build on the results coming from the Action Line A projects A1, A5 and A6, respectively. The identification of models for the provision and operation of solutions services will need to address2
- the provision and operation by 3rd parties like ASPs, Brokers, Public Service Libraries, etc.
- the interoperability requirements of service marketplaces which need to integrate solutions from different vendors and/or providers
- the aspect of easy and seamless integration of services into existing IT, Knowledge, and Process infrastructures of SMEs.
Task A8.2.1: Configuration and composition requirements and modes Task A8.2.2: Model driven adaptation Task A8.2.3: Provision and Operating Models. Collaboration with Receives from AL A and B Provides to A8.4, A8.2
2 Initial contacts with the Digital Business Ecosystems (DBE) IP have been established and will be continued, in order to coordinate the work between DBE and ATHENA with the objective to avoid duplication of research activities in this field.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A8.3 Guidelines and Best Practices for applying the ATHENA
Interoperability Framework in SMEs Leading Participant ESI Starting M24 Ending M36 Objectives
- Develop guidelines and best practices on how to apply ATHENA results as documented in the ATHENA Interoperability Framework (AIF) in SME environments
- Provide a Roadmap for establishing core capabilities required for participating in digital ecosystems
- Provide a targeted and integrated conceptual solution for SMEs to the common problem scenario defined in WPA8.1, as an instance of applying the AIF in SME environments
Description of Work The development of the guidelines and best practices for applying the AIF in SME environments will build on the results coming from WPA8.1. The roadmap for establishing core capabilities in SMEs will be based on the Establishing and Management Approach developed in the A1 project, and extend it to meet the purpose of covering all aspects related to enabling SMEs to getting involved in digital ecosystems. As a concrete instance of applying the AIF for solving interoperability problems in SMEs, a conceptual solution for the common problem scenario defined in WPA8.1 will be developed. This conceptual solution will describe a combination of technical prototypes, methodologies, architectures and platforms that can be applied to the scenario. The conceptual solution will be implemented in WP8.4, and verified and validated in the scenario selected in A8.1. Task A8.3.1: Guidelines and Best Practices. Task A8.3.2: Roadmap for involvement of SMEs in Digital Ecosystems Task A8.3.3: Conceptual solution to common problem scenario Collaboration with B3, B5 Identify profit potentials in enterprise networks Receives from A8 Results from all other WP to be integrated in guidelines and roadmap A4 AIF A1 Establishing and Management Approach Provides to A4 Guidelines and best practices on how to apply AIF in SMEs
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A8.4 Application of ATHENA results to provide pre-configured solutions
for SME interoperability Leading Participant SAP Starting M24 Ending M36 Objectives
- Adapt ATHENA results for their application in SME environments
- Establish model driven and –configured solutions to common problem scenario
- Support and maintain tools and solutions used in the B5 sub-project calls
- Evaluate applicability of ATHENA results for SMEs based on feedback received Description of Work The adaptation of ATHENA results for their application in SMEs is primarily concerned with the scalability of the solutions and their functionality, based on the requirements defined in WDA8.3.1. This does not necessarily include the implementation of new features. The conceptual solution to the common problem scenario defined in WPA8.3 and described in WD.A.8.3.1 will be used as the specification blueprint for the implementation of a generic, model driven and user configurable software solution, which addresses and covers the defined problem areas. This software solution will be validated and verified in the scenario selected in A8.1. In order to appropriately support the use of tools and solutions, and maintain them according to the feedback and experiences provided by the B5 sub-project partners, it is necessary to establish appropriate procedures for managing and performing requests for changes and improvements. These requests will derive from the feedback and experiences described in the first versions of the post test evaluations (DB5.4.2 – DB5.7.2) coming from B5. Task A8.4.1: Adaptation of ATHENA results for application in SME environments Task A8.4.2: Develop generic solution to common interoperability scenario (A.8.1) Task A8.4.3: Maintenance and Support for ATHENA tools and infrastructures Collaboration with Receives from A8.3 Conceptual solution to common interoperability problem scenario AL A Tools and Infrastructures B5 Sub Projects Experience and Feedback to improve tools and infrastructures Provides to A8.3 B5 Sub Projects Improved tools and infrastructures
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package A8.5 Project Management Leading Participant ESI Starting M20 Ending M36 Objectives
The objective of the Project Management is to coordinate
- the research activities in the project,
- the coordination with other projects,
- the development of deliverables and results, to control
- the performance of quality assurance activities
- the timely submission of deliverables, and to provide reporting on technical progress and costs of the project Description of Work Task A8.5.1: Technical Project Management Task A8.5.2: Progress and Cost Reporting
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Activity Objectives To mobilise and actively involve the broadest possible number of stakeholders from all constituencies that are interested in /impacted by Interoperability. Communities-of-Interest (COI’s) will be organised to provide systematic and structured communications with the ATHENA IP, both Action Line A projects and other Action Line B activities. The COI’s are expected to evolve and expand into a critical mass, a world-class reference for interoperability work, representing a solid European base of expertise. The communities, their purpose, members, contents and services are initially built up by the partners as research initiatives, but will be formally taken over by an independent, not-for-profit legal entity – the EIC – during the course of the IP. The plan is to establish the EIC after 18 months. It will start up by taking on responsibilities for work packages 2 and 3, acting as a secretariat for all communities and their members, and eventually it will take over and financing and running of all the services in supporting and operating the communities. The goal is that the EIC will be formally launched within 24 months. It is envisaged that after 24 months, the current tasks are entirely driven by the EIC, but then new tasks are ready for prototyping and assessment by the communities. The EIC will itself represent state-of-the-art in interoperable Networked Organisations, providing services from innovative research management to training of solution providers. The specific objectives of Community Building are:
To build a critical mass of stakeholders across Europe and globally. To be the main source for interoperability knowledge and services. To provide open, transparent, credible and stable consensus building To provide approaches, methods, specifications and member services for solutions design and
management. To develop and operate a Solutions Prototyping Community (SPC), assisting industry with platform and
services. To produce visible and measurable impact on vendors, consultants, interest organisations, industry,
standardisation bodies and academic communities. To provide Interoperability Services and solutions for the European Research Area (ERA). To build and support the community infrastructure (contents coming from the other activities) necessary for
the foundation of a long term, self-sustaining EIC, well beyond the time horizon of the present IP. These objectives will be realised in conjunction with other specific activities in Action Line B, which will eventually be hosted by the EIC. The EIC is targeted as the permanent European hub for community and consensus promotion, development, experimentation and dissemination activities. It is envisaged that the knowledge assets created under Action Line B will be used to populate the knowledge base of the EIC. Similarly, the assets created under Action Line A, in as far as they are intended for the public domain, will be vested in the EIC. The long term viability of the EIC will be dependent on membership contributions. The membership base will be built and outreached from the ATHENA IP Consortium. Parties external to ATHENA will be encouraged to become founding members as well. EIC membership is open to all interested parties. The EIC services are planned to be generally recognised with increasing usage at the end of Year 3 of ATHENA. The self-sustainability of the EIC is planned to be achieved towards the end of the planned duration of the ATHENA programme of work (i.e. Year 5). Note: EIC is a legally independent organisation. It is independent from ATHENA and is accountable to the EIC membership. Therefore, the final decisions concerning EIC matters will be made by members of the EIC. Formal documents relating to the establishment of the EIC will be checked with the Commission on the grounds of quality merits and compliance with the applicable formally established and documented Commission policies and regulations which are available in the public domain.
Work Package List
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package B1.1 Define communities, services and structures Leading Participant SAP Starting M1 Ending M36 Objectives Establish the fundamentals for a successful build up of a sustainable EIC as the host for the European Interoperability Community. Make sure that synergies with other similar initiative are identified and materialized and co-operation potentials are explored. Where appropriate similarities with other initiatives will be exploited and synergies established. The experiences of relevant initiatives will be analysed for drawing lessons. The results will be used to start the legal and administrative work.
Description of Work Task B1.2.1. Task Identify the stakeholders, define user categories of each community, and build the
network comprising of academia, research institutes, suppliers, user organisations, associations and other public and private sector partners both on European as well as global level.
Task B1.2.2. Analyse the requirements of the stakeholder as the future members of the EIC. Task B1.2.3. Identify and design the services portfolio for the community taking into account the
diverse nature of the member category and sectors. Task B1.2.4. Identify and define the functional structure of the EIC for hosting of the core activities. Task B1.2.5. Draft and finalise the mission statements, objectives and basic principles of the EIC
Draft of Business Plann. Task B1.2.6. Draft and finalise statutes and bylaws. The relevant stakeholders will be consulted in the
approval process, including Commission DG INFSO, DG Enterprise, ATHENA PCC. Collaboration with B2 / B3 / B4 Receives from B2 Potential Members Provides to
Work Package B1.2 Recruit and organise communities and members Leading Participant IC Focus Starting M6 Ending M36 Objectives Mobilise and recruit communities, organisations, interest groups, key individuals etc to be involved in the ATHENA Community which is to be evolved into the EIC. Structure and organise their participation and contributions to the relevant aspects of the ATHENA programme of work. Engage their commitment. Identify and engage potential sponsors for the EIC.
Description of Work Task B1.2.1 Develop communities, member categories, and recruitment strategy. Task B1.2.2 Implement recruitment strategy, and define membership services. Task B1.2.3 Define a services programme for structured and organised communications with the
ATHENA projects and activities. Collaboration with B2 / B3 / B4 / B5 / B6 Receives from B2 Potential Members Provides to
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package B1.3 Administer communities and services Leading Participant SAP Starting M8 Ending M36 Objectives Establish functionalities and structures to efficiently administer and provide services to the members and communities. Using the results of B1.1 membership activity and B1.2 event programmes, administration and management will be set up based on the capabilities and services provided by C4.
Description of Work B1.3.1: Establish a data base with community groups, authentication and authorisation keys, B1.3.2: Develop portal contents and operate an event/activity programme, B1.3.3: Draft an activity “access plan” e.g. how members and other can participate in the core
activities such as knowledge sharing, requirements definition and more, B1.3.4: Perform membership management and administration Collaboration with B2 / B3 / B4 / B5 / B6 Receives from B2 Potential Members C4 IT Infrastructure Provides to
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Objectives The Knowledge Sharing activity aims to establish the interoperability community of different stakeholders. Extensive and thorough Information exchange and transfer will need to be continuously integrated along the Innovation and Exploitation cycles. Knowledge sharing will need to encompass concepts, models, techniques and solutions taken from all projects inside ATHENA. It will also need to be provided, facilitated and targeted in a variety of contexts, using a variety of instruments, and addressing a variety of needs. Knowledge sharing will be closed linked to all ATHENA projects and activities, especially to the Community Creation and EIC Establishment activity (B1) and the Dynamic Requirements Definition activity (B4) inside ATHENA, in order to provide input and disseminate outputs.
Dissemination activities will be centred on the transfer of results to the industrial, research and standardisation communities in the respective projects/activities. ATHENA will regularly produce newsletters and maintain a news service, and will organize and participate in conferences, workshops, and seminars throughout Europe. The most relevant scientific results will be submitted for publication in international scientific journals. An important activity inside ATHENA will be to publish articles in relevant magazines, journals and conferences.
Collaboration with other projects and initiatives outside ATHENA will be established in order to get inputs and provide outputs that could enrich the relevant initiatives. Specially, to ensure efficient industrial impact, close cooperation with the Network of Excellence INTEROP3 and other projects in support of the IST Strategic Objective on networked businesses will be carried out. Different dissemination actions will recruit new interested members from different countries, who will receive updated information about the ATHENA results. Dissemination will also seek to ensure that the SMEs in the industrial sectors related to ATHENA are aware of the industrial importance of ATHENA’s achievement.
This activity is in close relation to all projects and activities inside ATHENA, but, especially, a continuous programme will be established in coordination with activities B1, B4 and the Piloting including Technology Testing Coordination and Pilot Infrastructure activity (B5) to:
• identity stakeholders and constituencies • disseminate technical and scientific project outputs in the public domain • participate in and organize conferences, seminars, and workshops.
ATHENA will provide support to other relevant research activities for their implementation of the ATHENA results. This activity will also disseminate information to standardization bodies (e.g. ISO, CEN, W3C, OASIS, …), and communicate relevant standardization outputs for use within ATHENA.
The ATHENA consortium aims to establish liaisons with important organizations related to ATHENA, to make links with other initiatives, as well as to cooperate with established regional and global organizations dealing with interoperability issues (e.g. NIST, INTAP etc). As there are different sectors involved inside the ATHENA consortium (Aeronautics, Automotive, Telecommunication and Furniture), it will be possible to receive input from industrial companies, as they are the End Users that will benefit from ATHENA results, taking as a basis the input from the Dynamic Requirements Definition activity inside ATHENA. In summary this activity aims:
• to continuously give and receive relevant information for knowledge sharing purposes during
3 Interoperability Research for Networked Enterprises Applications and Software, selected for contract negotiation under FP6 IST Call One.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
the whole ATHENA programme of work • to develop marketing material such as leaflets, brochures, CD-ROMs, etc. • to provide a new services for disseminating ATHENA activities and results • to keep the public web site up to date within the content management system implemented
within C4.
Description of Work The dissemination and technology transfer activities are an essential for achieving the objectives of ATHENA.. Dissemination will be carried out throughout the project, and not only at the end. The main activities will be:
• publication of public documents and press releases • organization of conferences, seminars and other events to increase the industrial awareness of ATHENA
and Interoperability generally • Maintaining and continuously updating the public website including a news service.
The Diffusion of Innovation (DoI) theory will be followed in the project. According to this DoI theory the technological innovation is communicated through particular channels, over time, among the members of a social system. ATHENA intends to communicate the results and achievements of the project making its innovation within reach of a wide number of agents. The EIC to be created under activity B1 will ensure that dissemination activities continue after the end of the ATHENA programme, and outreaching to all interested agents.
ATHENA will go through five stages of the Diffusion of Innovation theory: knowledge, persuasion, decision, implementation and confirmation:
• Knowledge represents what already exists and the understanding thereof. So the first step will be the exposure of facts and information to show what ATHENA is and what has been reached and achieved.
• The persuasion phase will deal with ways to make people form a favourable attitude towards ATHENA. External people need to be convinced of the quality and suitability of ATHENA’s outcomes.
• Once the recipient of the knowledge has been persuaded, he/she must commit to adoption of the ATHENA outcomes. This is the decision phase. The actor is sufficiently convinced to make a commitment in the sense of putting in practice what has been learnt. At this stage, the knowledge is implemented and put in use. The different ideas have been processed and are set up for a useful change in an innovative way. Only when it has been implemented and proved as positive, the confirmation comes based on reinforcement of knowledge.
The information flow must be multi-directional and must involve both experts and the passive audience, both technical and non-technical.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package B2.1 Outreach Opportunities Leading Participant UNINOVA Starting M1 Ending M36 Objectives The main objective of this work package is to disseminate and facilitate the maximum transfer of information and knowledge resulting from ATHENA to all kinds of external parties in order to achieve critical mass.
Outreach opportunities give the ATHENA dissemination agents several possibilities to reach different users via different means. Conferences, seminars, workshops, and so on will be attended in order to reach audiences from different sectors. ATHENA intends to organise distinct events throughout the programme to enable external parties to interact with ATHENA partners and to follow ATHENA results from conception to implementation.
Description of Work Task B2.1.1 Activities strategy and plan. In a first stage an activities strategy and plan will be
elaborated based on the information available on possible events, conferences and other opportunities that allow ATHENA agents to achieve the maximum interaction with the different stakeholders, target groups, and end users.
Task B2.1.2 Organisation of ATHENA Conference and contribution to conferences as speakers or paper publications. A large conference will be organised in Year 2 and Year 3 to give the different sub-project partners and other target groups to meet and present the goals and achievements of ATHENA as well as the expectations of the target audience. It will serve as a forum for information exchange and will enable a sound platform to be built between all involved actors in and around ATHENA.. The conferences will be a platform to show the results achieved by ATHENA to a wide audience.
Task B2.1.3 Organisation of focus groups and roundtables. Interested parties in different fields will be addressed. Focus groups will be created in order to get a more specialised exchange of information mainly addressed to technical audiences. The roundtables are planned to be organized each 6 months and the objective is to reach a harmonisation of ideas among interested audiences.
Task B2.1.4 Dissemination workshops, Knowledge cafes and seminars. These events will mainly aim to inform external parties of the outputs of the ATHENA results. The objective is to organise one event each 6 months, with the precise modality to be determined in accordance with the targeted scope and audiences of the event. Some of the events may be co-located with external events where appropriate. Appropriate links will be established with academic institutions in collaboration with the training service provided under activity B6. .
Collaboration with All projects/activities in Action Lines A and B to collect results from them and disseminate in conferences, workshops, etc. Receives from All projects/activities Provides to All projects/activities
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package B2.2 Internet Strategies Leading Participant AIDIMA Starting M3 Ending M36 Objectives
The main objectives of this work package are:
• To use information technologies to spread knowledge on interoperability within the scope of ATHENA
• To disseminate the results of ATHENA via the Internet
• To provide content for the ATHENA public Web Site, including a News Service, and keep the content regularly updated.
ATHENA will set up a website in Activity C4, with the content being provided by this B2 work package. Special attention will be dedicated to making the web site attractive and useful. The web site contents will be updated regularly. The provision of multilingual contents will be considered, with the aim of making the key contents available in multiple languages.
ATHENA will also set up a News Service in C4, with the content being provided by this B2 work package. A Newsletter will be published on the website. The main results of the project will be reported, together with interesting news within the scope of ATHENA.
The philosophy of “give as much as you take” will be promoted. The objective is to provide an open forum to involve all the agents in the ATHENA action fields and to provide an interactive way to submit ideas, to identify problems, to provide possible solutions, to express requirements, and to share knowledge.
Feedback mechanisms will be set up in the website to get information about the requirements of the users. Forms will be popped up when downloading information from the website. The aim will be to get as much information as practical on the requirements and opinions of the user in order to improve the mechanisms of dissemination and technology transfer, and to help focus the research on the most relevant issues.
Description of Work Task B2.2.1 Provision and maintenance of ATHENA public web site content. Content for the
ATHENA public website will be created and maintained. The website will incorporate searching facilities feedback mechanisms, and other interactive features.
Task B2.2.2 Provision of contents for ATHENA News Services and eNewsletter. Creation of contents for the ATHENA News Service, including an open forum to involve all the agents in the ATHENA action fields for sharing knowledge and eliciting feedback. A regular newsletter on the developments and results of ATHENA and other relevant information will be published on the website and disseminated to the communities and projects with tight relationship with ATHENA.
Collaboration with All projects/activities in Action Lines A and B to collect results from them and disseminate in conferences, workshops, etc. Receives from All projects/activities Provides to C4 Criteria for website searches C4 Requirements for feedback mechanisms
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package B2.3 Spreading-material activities Leading Participant AIDIMA Starting M1 Ending M36 Objectives To spread material in traditional ways for promoting ATHENA and its achievements.
Description of Work Task B2.3.1 Production and dissemination of material including:
• ATHENA brochure edition. . • Publication of technical and specialised articles. • Banners and posters edition. • Exhibition booth at major events.
Task B2.3.2 Guidelines edition. Publication of good practices guides on the different agreements and/or harmonisations reached in ATHENA on paper. An eGuide will be made available on the website.
Collaboration with All projects/activities in Action Lines A and B to collect results from them and disseminate in conferences, workshops, etc. Receives from All projects/activities Provides to All projects/activities
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
7.6.3.3 Activity B3 – Business Interoperability Research Activity B3 Business Interoperability Research Leading Participant IC Focus Starting M01 Ending M36
Objectives This overall objective of this activity is to lay down the foundation work for long term research into interoperability from a business perspective. Specifically, this activity aims to:
• Determine the strategic business challenges relating to interoperability • Provide a general model for determining the impact of interoperability on businesses • Apply this model to ATHENA for assessing the business impact of the ATHENA results • Provide policy recommendations to the European Commission in respect of interoperability.
Description of Work
The overall context for this activity is the future company, creation and management of dynamic collaborative networks, knowledge management to support innovation, and evolution towards digital ecosystems. The activity will research into the main elements which constitute “Business Interoperability”, set against concrete existing and emerging industrial and organisational contexts. It will research into new organisational forms and structures and related value constellations and models, as well as explore business trust and governance issues, with reference to socio-economic trends and legal and regulatory developments. This activity will seek to collaborate and coordinate with external research initiatives within the IST programme and beyond, specifically research conducted by leading Business Schools and other academic and public institutions in Europe and internationally. This activity will take due account of CEN/ISSS Roadmap for addressing key eBusiness standards issues 2003-2005 (September 2003) among other major publications. This activity will also initiate work on long term research into business interoperability. It will prepare substantive inputs to the preparation of the Business Interoperability Research Sub-Project Call, which is scheduled to be launched in Year 1 of ATHENA in order to enable the sub-project to start at the beginning of Year 2. Under the Sub-Project, work will be carried out for developing techniques, methods and metrics for assessing the impact of interoperability on businesses. The overall impact analysis model will then be applied for assessing the impact of the ATHENA results on the market from a business perspective. Drawing on the work described above and inputs from other ATHENA projects/activities, this activity will provide recommendations on an annual basis to the European Commission in respect of the relevant regulatory, policy and strategic implications and actions in interoperability from a broad, business-oriented perspective. It should however be noted that the scope and substance of the policy recommendations is confined to those areas within the competency of the Consortium. The recommendations will address those aspects in which ATHENA has specific knowledge and expertise. They will be finalised in consultation with interoperability stakeholders in an open manner. As such, the ATHENA Consortium cannot guarantee the quality or representativeness of the results arising from such a consultation process, or the interest of SMEs in such an exercise. The individual workpackages in this activity will be working closely together given their mutual dependencies. In addition, this activity will work closely with all other projects / activities in the ATHENA programme of work. Specifically, Activity B3 will provide business interoperability requirements to Action Line A projects; it will also be the recipient of inputs from Action Line A projects / Action Line B activities especially regarding business assessment of ATHENA results and the policy action recommendations.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
WD.B3.1 Report on Coordination with External Initiatives • Version 1 • Version 2
B3.3 IC Focus M18
M36
WD.B3.2 Business Interoperability Research Sub-Project Call – Draft Technical Annex
B3.4 IC Focus M06
WD.B3.3 Assessment of Networked Organisations and Value Models
B3.1 FORMULA M18
WD.B3.4 Interoperability Impact Analysis Model – Draft
B3.4 INSEAD M22
WD.B3.5 Business Interoperability Framework – Draft B3.1 HSG-ITEM M24
WD.B3.6 B3 Sub-Project Call – Project Plan of new Partners B3.4 HSG-ITEM / INSEAD
M18
Contribution to Milestones Milestone Contribution to Milestone
M.12 − ATHENA Contribution to Policy Action Plan (V1)
M.24 − Business Interoperability Framework – Draft − Assessment of Networked Organisations and Value Models − Interoperability Impact Analysis Model – Draft − ATHENA Contribution to Policy Action Plan (V2)
M.36 − Business Interoperability Framework − Interoperability Impact Analysis Model − ATHENA Impact Assessment − ATHENA Contribution to Policy Action Plan (V3) − Business Interoperability Long Term Research Requirements
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work package B3.1 Business Interoperability Framework Leading Participant HSG-ITEM /
INSEAD Starting M01 Ending M36
Objectives To provide a framework for determining business challenges relating to interoperability. Assess networked organisations and value models in relation to the advancement of business interoperability.
Description of Work Task B3.1.1 Identity Business Interoperability main elements. Identity the main elements which
constitute “Business Interoperability” and explore their contexts and applications in industrial and other business environments. Explore business process integration issues from a business perspective, and the achievement of integration through leveraging ICT and emerging applications and services for supporting business goals.
Task B3.1.2 Establish an initial set of trusted eBusiness requirements. Research, analyse and identity the core elements of trust that enable eBusiness interoperability and their application in industrial environments. Explore the common resources and community services that might be needed in facilitating and enabling a more “trusted” eBusiness environment.
Task B3.1.3 Establish an initial set of Business Interoperability Guidelines. Research, analyse and develop general guidelines for facilitating business interoperability, with due consideration of sector-specific requirements and industrial trends.
Task B3.2.1 Identify and assess different organisational forms and structures. Explore new and emerging networked organisation forms and structures. Review the evolution of different types of value networks, business value propositions and models, with reference to ICT advancements and specifically the various interoperability contexts and dimensions. Provide assessment.
Task B3.2.2 Identify and assess the requirements for design, management models and techniques of value networks. Drawing on the results from the above task, identify current and emerging practices relating to the design and management of business models and the available and emerging techniques for developing value networks. Provide assessment.
Task B3.2.3 Identify and assess the requirements for a dynamic networked business environment. Explore the long-term requirements for a dynamic networked business environment in relation to the evolution of networked organisations and value models. To consider contextual drivers and parameters such as innovation, entrepreneurship, market structures, as well as their relationships and inter-dependencies. Within these contexts, also to consider inter- and intra-organisational relationships, sector specificities and constraints, SME requirements, and the need for “information commons”. Provide assessment.
Collaboration with B4 Investigation and identification of user requirements Receives from Provides to A1 – A6 Business requirements and drivers for interoperability B1 Development of services for the EIC B6 Material for training courses
Note: WP.B3.2 merged with WP.B3.1. B3.2 tasks are included in B3.1 with original numbering.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package B3.3 Coordination with External Initiatives Leading Participant IC Focus Starting M01 Ending M36 Objectives To tap into available resources on business interoperability from relevant research and other initiatives; ensure good exchange of information and, where appropriate, collaboration and coordination.
Description of Work Task B3.3.1 Identify relevant initiatives in Business Interoperability research. Identify relevant work
conducted by relevant FP6 projects, the activities of the leading Business Schools and other institutions in Europe as well as internationally.
Task B3.3.2 Establish contacts / coordination with these initiatives. To access and collaborate with the best expertise and information sources that are available in the field of Business Interoperability Research. Ensure two-way communications and feedback between ATHENA / B3 and the relevant initiatives identified.
Collaboration with Receives from Provides to Other B3 work packages Information
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package B3.4 Long Term Requirements, Impact Analysis and Recommendations Leading Participant IC Focus Starting M01 Ending M36 Objectives To identify the long term requirements for business interoperability research; To provide a model for determining the impact of interoperability on businesses; To apply the above model to ATHENA for assessing the business impact of ATHENA results; To provide policy recommendations to the European Commission in respect of interoperability. Note: This work package will serve as Activity B3’s main interface with other Action Line B activities and Action Line A projects.
Description of Work Task B3.4.1 Identify long term requirements for Business Interoperability research. Requirements
are expected to include: strategic elements for business interoperability; business requirements for a trusted eBusiness environment and related organisational and governance issues, including institutional issues where relevant; networked organisational forms and structures and related value models and constellations; inter- and intra-organisational issues, sector specifications and constraints, and SME requirements for business interoperability; the “information commons” needed to support business interoperability.
Task B3.4.2 Prepare inputs to contents of Business Interoperability Research Sub-Project Call. To prepare the draft Technical Annex of the Sub-Project Call, with the Sub-Project being scheduled to start at the beginning of Year 2.
Task B3.4.3 Develop an Interoperability Impact Analysis Model and apply Model to ATHENA. To develop a general model for determining the impact of interoperability on businesses, including techniques, methods and metrics, and other supplementary material. To apply the developed model for assessing the impact of ATHENA results on the market from a business perspective.
Task B3.4.4 Develop ATHENA contributions to Interoperability Policy Action Plan. Based on the ATHENA experiences/results, to provide recommendations to the European Commission in respect of the relevant regulatory, policy and strategic implications and actions in interoperability from a broad, business-oriented perspective. The recommendation areas are expected to include, but not necessarily limited to: industrial & socio-economic aspects (e.g. cost/pricing issues, value creation/ROI/ROV, digital productivity); organisational aspects (e.g. organisation structures, business cultures, management issues, the “future company”); innovation aspects; education and learning aspects; European competitiveness aspects; legal/regulatory & governance aspects; long term business interoperability research requirements. The recommendations will address those aspects in which ATHENA has specific knowledge and expertise. They will be finalised in consultation with interoperability stakeholders in an open manner. The finalised recommendations will be consolidated into a rolling ATHENA contribution to the Commission’s “Policy Action Plan” relating to Interoperability and delivered annually
Collaboration with All Action Line A Projects and all Action Line B Activities Receives from All Projects and Activities: performance indicators, results, and other relevant information and insight Provides to
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
The dynamic requirement definition activity aims to provide ATHENA with a method and a system to dynamically capture, analyse, manage and respond to requirements coming from user-scenarios concerning interoperability issues.
It aims to support maximum number of functional, support, organisational and commercial processes adapted to wider set of industrial sectors.
It aims to efficiently support research projects in Action Lines A, through A4 project, providing a coherent and common way for defining user requirements for interoperability features and services definition.
It aims to provide a way to easily evaluate and formalise how innovative implementation of the features and services from Action lines A will cover the requirements for any provided scenario, through the ATHENA knowledge based developed approach and capabilities.
It aims to support dissemination to and feed back from different communities concerned and influencing interoperability of enterprise applications and software, linked with business drivers, in order to have a maximum impact on interoperability requirements efficiency and to promote the ATHENA approach through the “Enterprise Interoperability Center (EIC)” and ATHENA tested developed capabilities.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
The principles and methods of Dynamic Requirement Definition to be provided to research ATHENA Action line A projects will be defined at the initiation phase (WPB4.1) in cooperation with all the other projects. A first set of existing business scenarios will be selected, described and detailed to provide knowledge to all projects in order to contribute the first set of requirements. Also requirements will be gathered from other projects like IDEAS and UEML.
These principles will be used to specify a Dynamic Requirement Definition System aiming to formally define, store and retrieve the requirements and to link them with interoperability features, services and technical solutions provided with by ATHENA Action line A projects (WP B4.2). This system will be used and maintained (functional – i.e. dynamic evolution of functional specification of the DRDS – and operational – i.e. using and populating DRDS – points of view (WP B4.7).
Different activities will be undertaken in order to maximise usage of technical solutions to cover a maximum set of business concrete scenarios and in order to orient ATHENA research activities on the more important interoperability features for the largest community:
• Definition of Global Processes of Reference (WP.B4.3) )
• Production of holistic and global scenarios for the different sectors from end users in the ATHENA consortium. Each scenario will concern one or several global processes (WP B4.4).
• Definition of a list of interoperability issues, features, and service specification. These will be defined and maintained from scenarios. The initial list will be derived from results achieved in the IDEAS thematic network. This list will be completed in the course of ATHENA through analysis of results of the different pilots (WP B4.5).
• Definition and usage of an effective and practical mapping approach (WP B4.6) between scenarios and interoperability issues, features and services.
For one given global process, the idea is to obtain scenarios coming from more than one sector in order to analyse and identify:
• Similarities, in order to define generic solutions • Differences, to define generic methods to address specificity. Dissimilarity criteria will be
identified and characterized (e.g. the duration of the lifecycle of a product, the number of produced items, the complexity of a product, certification…)
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Description of Work (2) In summary, the overall aim will be:
• To address maximum number of identified issues concerning interoperability in ATHENA • To allow ATHENA end users to address subjects of prior interest for them, in order to be able
to exploit the results • To allow maximum exploitability from the community
For example, for a domain that is not represented in ATHENA, it should be possible:
• To select a generic process that is closed to the scenario to be addressed • To be able to quickly identify similarity and dissimilarity with its own sector based on a domain
specific scenario and pilot provided by ATHENA, in order to: Quickly identify what can or can not be reused from requirements identified by ATHENA
Propose to ATHENA new scenarios for its sector with identified dissimilarity, in order to enrich the ATHENA scenario basis and to validate the approach
Work Package List Work
package No Work package Title Responsible Particip. No Person
Months Start Month End Month
WP.B4.1 Initialisation 7-EADS 6,6 M1 M6
WP.B4.2 DRD System Development 4-TROUX 12,8 M3 M12
WP.B4.3 Global Processes Development 18-UNINOVA 13,2 M3 M18
Work package B4.1 Initialisation Leading Participant 7-EADS Starting M1 Ending M6 Objectives To define useable and effective principles and methods of Dynamic Requirement Definition:
• that will be shared during ATHENA program with other ATHENA projects and activities,
• and in order to support ATHENA program objectives.
Description of Work The work of this work package will be done through workshops involving end users, enterprise modelling and ontology experts, in strong cooperation with A4 project and B activities in order to clearly define interfaces between the different projects.
Task B4.1.1: Definition of the principles. Based on IDEAS deliverable, the principles of Dynamic Requirement Definition for interoperability will be proposed, discussed and validated by B4 activity partners in a first stage, and consolidated with other ATHENA projects and activities in a second stage, in particular with A4, to be compliant with the ATHENA Interoperability Framework (AIF) and to contribute to the ATHENA Interoperability Profiles (AIP).
Task B4.1.2: Definition of methods and tools for requirement definition. Based on principles defined in B4.1.1, different methods and associated tools will be proposed in order to define the final method and tools that will be used all along B4 activity and ATHENA program for Dynamic Requirement Definition for interoperability. It will be done in a first stage inside B4, and then validated and completed in a second stage with other ATHENA projects and activities.
Task B4.1.3: Technical coordination with the IP. This task will be dedicated to coordination, organisation and realisation of activities that will be done in cooperation with the other ATHENA projects and activities (second phases of B4.1.1 and B4.1.2). It will consist in preparing joint workshops with other ATHENA projects and activities, reporting and exchanges between B4, ATHENA technical coordination and ATHENA other projects and activities:
i. Definition of inputs to provide and B4 objectives and needs to be covered during the joint meetings and workshops
ii. Forwarding of requests for ATHENA program, projects and activities to be covered by B4
iii. Selection of people that will participate to the different joint workshop and meetings with clear attribution of mission and responsibilities (e.g. Cross AL Teams member for a specific ATHENA interoperability profile).
Collaboration with A4 (B4.1.1, B4.1.2), A projects and B activities (B4.1.3)
Receives from A4, B3 (to check with other projects)
Provides to A4, all the projects and activities (DB4.1)
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package B4.2 DRD System Development Leading Participant 4-TROUX Starting M3 Ending M12 Objectives
To develop a Dynamic Requirement Definition System that will allow to define, store, retrieve and share, within ATHENA program and between the different concerned stakeholders and actors, the requirements coming from end users linked with interoperability of enterprise application and software, in order to:
• quickly establish links with potential technical solutions provided by ATHENA,
• identify that the solutions are still to be developed.
Description of Work Task B4.2.1: Requirements collection for the system. Through workshops including different
interoperability actors and stakeholders of ATHENA, to define the different requirements for a DRDS.
Task B4.2.2: Analysis and design of functional solution. The requirements collected will be analysed in order to define a functional model of the DRDS.
Task B4.2.3: Design of technical solution. From functional model and in accordance with environment for knowledge management and IT capabilities of the ATHENA program, the technical solution will be defined. The implementation will be carried out within activity C4.
Task B4.2.4: Validation. The implemented solution will be validated on the basis of functional model provided in task B4.2.2.
Collaboration with A4, B3, B4, C4
Receives from All projects and activities, especially A4: requirements for the DRDS, feedback on the
proposed solution, and feedback from usage for validation. Provides to
C4, B3 => DRDS specification from Task B4.2.3 (intermediate version of DB4.4)
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package B4.3 Global Processes Development Leading Participant 18-UNINOVA Starting M3 Ending M18 Objectives
To explicitly define and describe a continuously growing set of functional, organisational and technical process methodologies of reference::
Design patterns from practical industrial design and development projects, describing approaches, methodologies, platforms and solutions,
that will be considered as a reference bases to categorise the different business scenarios produced and addressed by/to ATHENA
that will be used as reference process methodologies for interoperability issues, design principals and services identification.
That will apply to a number of concrete business scenarios being addressed by interoperability approaches solutions provided by ATHENA projects. Description of Work Task B4.3.1: Identification and choice of process description method and templates. The different
possible choices for process methodology description and templates will be identified and studied by the experts of the different disciplines implied in ATHENA. The method and template will be chosen based on well-defined criteria, such as suitability for comparing and analysing approach, methodology and solutions for logical coherence and mutual compliance, and for support by Athena platforms.
Task B4.3.2: Elaboration of ATHENA Process Typology. From the existing process methodologies typologies and categorizations to develop and apply a processes typology that will be proposed, adapted and described in support of interoperable enterprise applications and software systems. The Athena process typology gives guidelines to developers for how to achieve coherence and compliance in models for these methodology processes of reference, collected from many sources.
Task B4.3.3: Definition of Global Processes of Reference. Most of the existing Global Processes Methodology Reference Models gathered and analysed are developed quite independent of each other (e.g. Zachman, ToGAF, Gartner, DODAF, TEAF, CEAF, DOGIT, PERA, GERAM). This clearly means that there is a great danger of inconsistency and non-compliance between them, that could lead to major conflicts and non-interoperability of solution, if they are implemented as-is in industry. Task will develop a typology to guide harmonization of these reference models.
Collaboration with A1 and A4 (task B4.3.1), A1 (task B4.3.4), 3 (task B4.3.5) and A3 (task B4.3.6)
Receives from
Provides to All projects and activities: D.B4.2 (Global processes of reference) and WD.B4.3.1 (Process
Description Language and Templates)
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package B4.4 Scenarios Identification and Development Leading Participant 2-AIDIMA Starting M1 Ending M36 Objectives
To identify and define industry sector specific and concrete business scenarios of interest for interoperability purpose, describing a holistic way current existing context and practices, and the wished situation concerning interoperability (to-be scenarios). Such scenarios will be used:
As inputs to build use and test cases for Interoperability research projects in ATHENA
To validate and illustrate from a business point of view completeness and efficiency of results provided by ATHENA research projects.
Description of Work Task B4.4.1: Scenarios for inter project initialisation phase. A first set of business scenarios will be
produced to ATHENA research projects, based on IDEAS scenarios linked with Supply Chain Management, Collaborative Process Design, e-Procurement and Portfolio Management. These scenarios will be used as basis for initialisation of different research activities, and first feedbacks from ontology, enterprise modelling and architecture experts will allow to identify how to improve collection of information to define adapted use cases and interoperability requirements.
Task B4.4.2: Identification and choice of scenario description language and templates. Based on different existing methodologies, adapted scenario description languages and templates will be identified, compared, in order to finally define the more adapted choice for ATHENA program.
Task B4.4.3: Development of the four to-be scenarios. Automotive, furniture, aerospace, and telecom scenarios will be developed in parallel using description language and templates chosen in B4.4.2 and feedback from experts of research activity
Task B4.4.4: Collection of other scenarios. Complementary other scenarios will be defined for further usage in ATHENA program, to validate ATHENA DRD principle and defined methods, and for next research activities of the program. Some of these scenarios will be issued from the EIC.
Collaboration with A4, B3, B5
Receives from A4, B3 and B5: feedback on description language and templates B5 new activities based on the sub-project calls: scenario description and analysis using the method and tools provided by B4
Provides to AL A projects: WD.B4.4.1 (Starting business scenarios) and WD.B4.4.2 (Formalize and structured scenarios)
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package B4.5 To-Be Scenarios Analysis Leading Participant 7-EADS Starting M4 Ending M36 Objectives
To define and validate methods to extract interoperability requirements from to-be scenarios.
To analyse to-be scenarios in order to define commonality and differences between them, related to identification of interoperability requirements
To analyse the produced scenarios
Description of Work Task B4.5.1: Definition of Analysis Process, Method and Templates. Scenario analysis process,
method and templates will be defined, based on B4.2.1, B4.2.1, B4.3.2 and B4.4.2.
Task B4.5.2: To-be scenarios analysis. The to-be scenarios (Supply Chain Management, Collaborative Process Design, e-Procurement and Portfolio Management) will be analysed by different teams in parallel in order to provide a list of interoperability per scenario.
Task B4.5.3: Requirements filtering. The lists of requirements will be filtered to separate common requirements from specific requirements.
Task B4.5.4: Validation of analysis process, method and templates. Based on the experience from B4.5.2 and B4.5.3, analysis process, method and templates defined in B4.5.1 will be analysed and validated.
Collaboration with A4, B3, B5
Receives from All projects : contribution to feedbacks on defined analysis process, method and templates
(TaskB4.5.1) and feedback through their usage (Task 4.5.4). B5 new activities based on the sub-project calls: scenario analysis and requirements
specification using the method and tools provided by B4 Provides to
All projects and activities: WD.B4.5.1 (To-Be Scenario Analysis Process, Method and Templates)
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package B4.6 Interoperability Issues Mapping Leading Participant 5-CRF Starting M6 Ending M36 Objectives
To define a mapping approach between interoperability issues/features/services and requirements in order:
to quickly identify potential existing technical solutions and their interchangeability
to quickly identify a need for new or a lack of existing technical solutions
to produce input for ATHENA research projects and way to validate and reuse their results.
Description of Work Task B4.6.1: Mapping approach definition. The approach to map interoperability requirements
coming from scenarios and interoperability issues, features and services will be defined for the Athena program. It will particularly address interchangeability of interoperability issues, features and services, that is especially important due to the fact business context and IT technologies are evolving separately with different periodicities and horizons.
Task B4.6.2: Issue/requirement mapping. Mapping between interoperability issues, features and services, and requirements coming from the B4 scenarios (Supply Chain Management, Collaborative Process Design, e-Procurement and Portfolio Management), will be done using the approach defined in B4.6.1.
Task B4.6.3: Analysis of the approach. The results of B4.6.2 will be analysed in order to validate and improved the proposed mapping approach.
Collaboration with A4, B3, B5
Receives from All projects and activities: feedback on results of the approach.
Provides to All projects and activities: WD.B4.6.1 (ATHENA Mapping Approach Definition between
Requirements and Interoperability Issues) and WD.B4.6.2 (ATHENA Mapping Approach Validation Report)
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package B4.7 DRDS Maintenance Leading Participant 10-FHG IPK Starting M13 Ending M36 Objectives
To maintain the Dynamic Requirement Definition System and to update it according with change requests coming from ATHENA and external communities.
Description of Work Task B4.7.1: Change requirement collection. The change issues concerning DRDS will be
collected, from ATHENA projects and ATHENA activities. These issues will be analysed and grouped in change requirements.
Task B4.7.2: Change requirements instruction. Instruction of change requirements will be realised, and decision concerning implementation of these changes will be taken, based on ATHENA program needs and objectives.
Task B4.7.3: Change implementation. Implementation of changes will be followed and validated. Implementation will be performed by activity C4.
Collaboration with C4
Receives from All projects and activities: feedback on DRDS, that will be traduced in change request
Provides to IT support action line: change orders for the implementation
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Activity Objectives Business process interoperability plays a crucial role in achieving business integration. The complexity of interactions between enterprises, teams of human beings, require sound methods to re-engineer business processes. Interoperable business processes and re-engineering services, developed in Action Line A, need to be tested. The piloting of how the Business Process helps in achieving the bottom line business integration is of paramount importance. Technology testing is the primary step towards exploitation and implementation. They are vehicles for facilitating collaboration and consensus building among stakeholders, as well as catalysts for building critical mass and commitment.
Technology testing will be based on a network of coordinated laboratories. The coordination will include context setting, prioritization and evaluation, as well as ensuring complementarities across thetechnology testing and common methods of work and common IT infrastructure. It is envisaged that the network will cooperate with the relevant testing activities of CEN/ISSS and ETSI in so far as these are within the ATHENA requirements and budgets, and with similar initiatives such as “OAG/NIST Test bed Initiative for knowledge sharing and dissemination”.
The main purpose of the piloting communities is to supply requirements to Action Line A, and to validate the results from Action Line A research activities in a continuous line. In the first period of 18 months four pilot scenarios (automotive, aerospace, furniture, telecom) will be addressed in close coordination with activities B1, B2 and B4. All four use-case scenarios will be modelled and deployed for execution, and shared with the members of the communities. The operations will yield a knowledge base of experiences and practices to be offered to the prototyping communities. Members will be able to access and download the prototypes produced in the Action Line A projects, and to upload their own prototypes for use by other members.
Piloting activities other then the four pilots developed by core members will be carried out in subprojects. Calls for subprojects will be organized in year 2. Activities in ATHENA are already under way to prepare a subproject on piloting interoperability in the SMEs arena.
Description of Work This specific activity can be considered the end station for the development process of the entire
IP. It is therefore devoted to validate and pilot interoperability in all aspects of business, and to prove the overall benefits. It receives inputs from activity B4 (Dynamic Requirements Definition, and To-Be interoperability scenarios), and from the Action Line A projects (developed services, and knowledge and software components). It provides outputs in terms of validation of projects results, as well as feedback on requirements satisfaction. The tasks planned for this activity also include the preparation phase to establish the laboratory networks for testing and prototyping.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
WD.B5.5 Use case for test piloting B5.4 B5.5 B5.6 B5.7 B5.8
5 – CRF M12
M24
WD.B5.6 Post Test Evaluation B5.4 B5.5 B5.6 B5.7 B5.8
5 – CRF M24
WD.B5.7 Use case for test piloting B5.9 B5.10
New contractors
M28
Contribution to Milestones
Milestone Contribution to Milestone
M.12 − International Technology Testing Cooperation Plan − Technology Testing planning and validation framework − Defined tests plans for involved industries
M.24 − Prototyping demonstrations available to community − Tests results for involved industries − Defined test plans for additional industries
M.36 − Pilot results from Technology Testing
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work package B5.1 Technology Testing Coordination Leading Participant CRF Starting M01 Ending M36 Objectives
The goal of this work package is to plan the Technology Testing activities such as establish the laboratory network for test and the common methods of works. Monitor the progress of activities and adopt correction measure, produce periodic planning and progress report. Description of Work Task B5_11: Planning. The task goal is to plan and launch the Technology testing network. The
task will expand on three aspects: the organisation necessary to run the Technology Testing, the method to develop and evaluate test pilot and setting the requirements for the technical aspects of hardware/software (the latter will be developed in C4). A term of reference agreed by the partners will define the mission, the goals, strategy and organisation of the Technology Testing network.
Task B5_12: Define and establish validation-evaluation methodology. The goal of the task is define a common methodology to validate and evaluate the interoperability pilots. The team responsible of pilot test will apply the methodology.
Task B5_13: Test coordination. Develop and maintain a rolling plan for all the activities for the whole IP duration.
Collaboration with A1-A6 Establish validation-evaluation methodology Receives from B3 Business Interoperability Research Provides to A1–A6 Coordinated Validation Plan, Technology testing Quality assurance B6 Material for training courses
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package B5.2 Sub Project Call Preparation and Management Leading Participant SAP Starting M05 Ending M29 Objectives Piloting activities in ATHENA are carried out in subprojects. Piloting needs will be identified and subsequent calls for sub projects defined. Preparatory and organizational activities will be carried out including issuing sub-project calls, evaluating responses, and negotiations with potentially new partners. Two sub project calls are envisaged Year 2. Description of Work Task B5_21: To prepare calls for piloting to be uploaded on the community networks, supplying
portal based templates and guidelines to guide members in their proposal preparation and submission work.
Task B5_22: To prepare and describe the technical services and the effort required to enable members to upload their demonstrators. This will give members direct support when preparing their tasks and budgets for demonstrators and for actually doing the uploading
Task B5_23: To perform the call, the refereeing and the selection of sub-projects. Collaboration with B1 Community Building and EIC Establishment Receives from B1 Community Creation and EIC Establishment Provides to B1 Calls for pilots B1 Describe the technical services and the effort required to enable members to upload their pilots
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package B5.3 Integration and Prototyping Services Leading Participant TROUX Starting M03 Ending M36 Objectives WP B5.3 identifies and specifies a set of services (e.g., web services, toolkits, facilitators, integrators) to assist in the Technology Testing platforms and pilots development. The actual development, deployment and adaptation of these services will be undertaken in Activity C4. These services will aim to make the integration of applications and software easier, facilitating to reach an interoperable environment for the Technology Testing community and pilot developers. Services will become available to the ATHENA community to support activities in Action Lines A and B
Description of Work Task B5_31: Identification and specification of services for Technology testing platforms and pilots
development
Collaboration with C4 IT Integration Receives from A1 Enterprise Modelling in the context of Collaborative Enterprises Provides to C4 IT Integration
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work package B5.4 Aerospace Piloting Leading Participant EADS Starting M03 Ending M36 Objectives The goal of this work package is to plan and design a business scenario tests according to the dynamic requirements definition and requirements validation for the aerospace industry.
Description of Work Task B5_41: Define use case. The goal of the task is to adapt business scenario and business
cases, as defined by dynamic requirements definition, to the results of the requirements validation process. The use case will focus on re-engineered business processes in the Aerospace industry
Task B5_42: Develop & test pilot. The goal of the task is to adapt the technology testing to the use case. The test foundations will be about the content exchanged and its semantic control and the business process monitoring and testing. A plan of experiment will consider the different aspect of system performance and effectiveness to support the business integration and human – system coordination.
Task B5_43: Post-test Evaluation. The goal of the task is to ensure consistency of project results by analyse the pilots’ results and check their consistency versus Athena objectives. The results of the test cycle will be evaluated according a predefined validation methodology, conclusions will be drawn and feedback will be provided to Action line A projects.
Collaboration with A1-A6 and B4 Receives from B4 To-Be Scenario Analysis Process, Method and Templates A4 Validation of research results Provides to A1-A6 Business requirements and drivers for interoperability B4 Requirements for Interoperability refinement B6 Material for training courses
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package B5.5 Automotive Piloting Leading Participant CRF Starting M03 Ending M36 Objectives The goal of this work package is to plan and design a business scenario tests according to the dynamic requirements definition and requirements validation for the automotive industry. Description of Work Task B5_51: Define use case. The goal of the task is to adapt business scenario and business
cases. The use cases for validation will focus on re-engineered business process based on advanced interoperability, definition of class of information to be exchanged. The human coordination will receive appropriate consideration
Task B5_52: Develop & test pilot. The goal of the task is to develop technology testing on defined use cases using the test methodology and metrics. The test foundations will be about the business process monitoring and testing. A plan of experiment will consider the different aspect of system performance and effectiveness to support the business integration and human – system coordination.
Task B5_53: Post-test Evaluation. The goal of the task is to ensure consistency of project results by analyse the pilots’ results and check their consistency versus Athena objectives. The results of the test cycle will be evaluated according a predefined validation methodology, conclusions will be drawn and feedback will be provided to Action line A projects.
Collaboration with A1-A6 and B4 Receives from B4 To-Be Scenario Analysis Process, Method and Templates A4 Validation of research results Provides to A1-A6 Business requirements and drivers for interoperability B4 Requirements for Interoperability refinement B6 Material for training courses
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package B5.6 Furniture Piloting Leading Participant AIDIMA Starting M03 Ending M36 Objectives
To complement the results of the projects in development inside ATHENA, towards the Furniture SMEs enterprise reality. Furthermore, to analyse those core results in the projects inside ATHENA and refining and complement them to better fit the requirements for interoperability of the SME-based enterprises. A “show room” will be structured to be a reference and motivator for the SMEs enterprises in the Furniture sector. As well, this “show room” will be prepared to be a platform for “hand-on” teaching and training.
Description of Work Task B5_61: Define use case. The goal of the task is to adapt business scenario and business
cases. The use cases for validation will focus on re-engineered business process based on advanced interoperability, definition of class of information to be exchanged. The human coordination will receive appropriate consideration
Task B5_62: Develop & test pilot. The goal of the task is to develop technology testing on defined use cases using the test methodology and metrics. The test foundations will be about the business process monitoring and testing. A plan of experiment will consider the different aspect of system performance and effectiveness to support the business integration and human – system coordination.
Task B5_63: Post-test Evaluation. The goal of the task is to ensure consistency of project results by analyse the pilots’ results and check their consistency versus Athena objectives. The results of the test cycle will be evaluated according a predefined validation methodology, conclusions will be drawn and feedback will be provided to Action line A projects.
Collaboration with A1-A6 and B4 Receives from B4 To-Be Scenario Analysis Process, Method and Templates A4 Validation of research results Provides to A1-A6 Business requirements and drivers for interoperability B4 Requirements for Interoperability refinement B6 Material for training courses
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package B5.7 Telecom Piloting Leading Participant Intracom Starting M03 Ending M36 Objectives The goal of this work package is to plan and design a business scenario tests according to the dynamic requirements definition and requirements validation for the telecom industry. Description of Work Task B5_71: Define use case. The goal of the task is to adapt business scenario and business
cases, to the results of the requirements validation process. The use cases for validation will focus on re-engineered business process based on advanced interoperability, definition of class of information to be exchanged.
Task B5_72: Develop & test pilot. The goal of the task is to develop technology testing on defined use cases using the test methodology and metrics. The test foundations will be about business process monitoring and testing. A plan of experiment will consider the different aspect of system performance and effectiveness to support the business integration and human – system coordination.
Task B5_73: Post-test Evaluation. The goal of the task is to ensure consistency of project results by analyse the pilots’ results and check their consistency versus Athena objectives. The results of the test cycle will be evaluated according a predefined validation methodology, conclusions will be drawn and feedback will be provided to Action line A projects.
Collaboration with A1-A6 and B4 Receives from B4 To-Be Scenario Analysis Process, Method and Templates A4 Validation of research results Provides to A1-A6 Business requirements and drivers for interoperability B4 Requirements for Interoperability refinement B6 Material for training courses
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package B5.8 Pilots in other areas Leading Participant SAP Starting M08 Ending M36 Objectives
To grow the industrial participation and contributions to the IP and eventually run the EIC, it is considered vital to engage industry in creative valuable work, such as developing new approaches to solutions development and providing standardised services for tools, applications integration and database content sharing. Industrial demonstrators will be built that apply across most industrial sectors, and that even may have relevance for the general public.
Description of Work
An interoperable solution engineering environment, fitted to general needs of industry, will be provided to cover the principal processes of solutions engineering and prototyping. This work package will mainly consolidate and complement the results of most projects and the community activities in Action line B. Particular emphasis will be on solutions for SMEs.
Task B5_81: Adaptation of methods and techniques developed in Action Line A projects.
Task B5_82: Adaptation and extension of specific methods and techniques required.
Task B5_83: Communications with and involvement of members.
Collaboration with B4 Investigation and identification of user requirements B1 Community Building and EIC Establishment Receives from B1 Calls for pilots Provides to A1-A6 Business requirements and drivers for interoperability B4 Requirements for Interoperability refinement
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work package B5.9 Outbound Logistics based Pilot Leading Participant New contractor Starting M23 Ending M36 Objectives The goal of this work package is to plan and design a business scenario tests according to the dynamic requirements definition and requirements validation for the Outbound Logistics based Pilot.
Description of Work The detailed task description will be provided after the new contractors have joined
Task B5.9.1: Define use case
Task B5.9.2: Develop & test pilot
Task B5.9.3: Post-test Evaluation
Collaboration with AL A on research results to be used in piloting activity B4 on scenario definition and analysis as well as requirements definition B3 on performance measures B2 on dissemination activities Receives from B4 To-Be Scenario Analysis Process, Method and Templates Provides to AL A Business requirements and drivers for interoperability, feedback on applicability of
research results B6 Material for training courses
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work package B5.10 Inventory Visibility based Pilot Leading Participant New contractor Starting M23 Ending M36 Objectives The goal of this work package is to plan and design a business scenario tests according to the dynamic requirements definition and requirements validation for the Inventory Visibility based Pilot.
Description of Work The detailed task description will be provided after the new contractors have joined
Task B5.10.1: Define use case
Task B5.10.2: Develop & test pilot
Task B5.10.3: Post-test Evaluation
Collaboration with AL A on research results to be used in piloting activity B4 on scenario definition and analysis as well as requirements definition B3 on performance measures B2 on dissemination activities Receives from B4 To-Be Scenario Analysis Process, Method and Templates Provides to AL A Business requirements and drivers for interoperability, feedback on applicability of
research results B6 Material for training courses
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Activity Objectives The objective of this activity is to provide education and training services to internal and external parties with interests in Interoperability. The training and education activities will lead to the establishment of an Interoperability Training Service. This service will become part of the Enterprise Interoperability Center (EIC) to be established by Activity B1. The services of this activity will be provided to the community associated with to ATHENA and beyond. It will be open to everybody concerned. Target groups are IT and Business Managers in order to create awareness for Interoperability issues, IT Experts that gain latest research results and hands on experience and Students which need to know the state of the art and trends in research (e.g., MSc and PhDs students). This Training activity will use state of the art training, education and knowledge management IT solutions to support a blended learning approach. Classroom trainings will be carried out as seminars, lectures at universities, tutorials at conference as well as in-house courses at customer or partner sites. Virtual classroom trainings enable geographically distributed participants to join in a session held by an expert. eLearning enables the participant to work offline in a self directed manner. Where appropriate lecture like sessions, hand-on experience using test-beds provided by Activity B5 and show-and-tell sessions will be included in the training. Training will be integral to the realization and sustainability of the ATHENA results, based in the input coming from integrated AL A and AL B results. Next figure depicts the Interoperability Training Service showing its principal components and activities in the scope of ATHENA.
TrainningService
( certified trainerscertified trainees )
“The Thing”
ATHENA IP Major users(trainees/trainers)
classRoomtraining material
(Virtual / Traditional)CONTENTS
ExternalSources
Res
earc
h re
sults
,In
dust
ry re
quire
men
ts,
Pro
toty
pe e
xper
ienc
es
IT and business managersIT expertsAcademia (PhDs, MScs , etc.)
Educ
atio
n, tr
aini
ng,
cert
ifica
tion
Mar
ketin
g,kn
owle
dge
shar
ing,
expl
oita
tion
Major users(trainees)
IT and business managersIT expertsAcademia (PhDs, MScs , etc.)
CONTENTS
TrainningService
( certified trainerscertified trainees )
“The Thing”
ATHENA IP Major users(trainees/trainers)
classRoomtraining material
(Virtual / Traditional)CONTENTS
ExternalSources
Res
earc
h re
sults
,In
dust
ry re
quire
men
ts,
Pro
toty
pe e
xper
ienc
es
IT and business managersIT expertsAcademia (PhDs, MScs , etc.)
Educ
atio
n, tr
aini
ng,
cert
ifica
tion
Mar
ketin
g,kn
owle
dge
shar
ing,
expl
oita
tion
Major users(trainees)
IT and business managersIT expertsAcademia (PhDs, MScs , etc.)
CONTENTS
Enterprise Interoperability Center - EIC
TrainningService
( certified trainerscertified trainees )
“The Thing”
ATHENA IP Major users(trainees/trainers)
classRoomtraining material
(Virtual / Traditional)CONTENTS
ExternalSources
Res
earc
h re
sults
,In
dust
ry re
quire
men
ts,
Pro
toty
pe e
xper
ienc
es
IT and business managersIT expertsAcademia (PhDs, MScs , etc.)
Educ
atio
n, tr
aini
ng,
cert
ifica
tion
Mar
ketin
g,kn
owle
dge
shar
ing,
expl
oita
tion
Major users(trainees)
IT and business managersIT expertsAcademia (PhDs, MScs , etc.)
CONTENTS
TrainningService
( certified trainerscertified trainees )
“The Thing”
ATHENA IP Major users(trainees/trainers)
classRoomtraining material
(Virtual / Traditional)CONTENTS
ExternalSources
Res
earc
h re
sults
,In
dust
ry re
quire
men
ts,
Pro
toty
pe e
xper
ienc
es
IT and business managersIT expertsAcademia (PhDs, MScs , etc.)
Educ
atio
n, tr
aini
ng,
cert
ifica
tion
Mar
ketin
g,kn
owle
dge
shar
ing,
expl
oita
tion
Major users(trainees)
IT and business managersIT expertsAcademia (PhDs, MScs , etc.)
CONTENTS
Enterprise Interoperability Center - EIC
Description of Work
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
The activity B6 sets up the required infrastructure to create and maintain the Interoperability Training Service. It will analyse available technologies and select those that fit the aims of the Training Service. The Interoperability Training Service will be able to provide services in traditional environments (e.g., classroom) and in virtual ones providing a blended learning approach. The content for the training and education program will be designed, collecting input from the ATHENA projects, and from external sources. The curriculum will be designed to meet the requirements of a target group including IT and business managers, IT experts, PhD/MSc students, and ATHENA partners. Additionally, a specific program for training of trainers is considered. Based on the designed program, training material will be produced and the training activities executed. The training and education activities will leverage experience by other projects and organisations in order to provide valuable knowledge transfer to attendants. Training material will be collected from ATHENA and external sources. ATHENA will provide content from achieved research results, industry requirements and piloting experience. Content will be structured and organised in order to simplify the creation and reuse of training material. Acknowledgement of the successful participation of students will be provided. The multi disciplinary approach taken by ATHENA and integration along multiple dimensions requires regular training sessions for members in order to share knowledge and create awareness for other research domains and industry requirements. Based on the flexible infrastructure for content management, training material can be specifically adapted for the target group or the type of training supported by the blended training offered by the training activities. The “Interoperability Training Service” will be equipped for the training of people at their early stages of research and for experienced researchers that wish to improve or to enlarge their expertise or simply do not have the opportunity of having a good training in the fields of competence of ATHENA. Those interested individuals preferentially will come from EU, including less-favoured regions and/or from Associated Candidate Countries. The integration of training material into academic education will be evaluated. Performance Indicators will be used as a guideline, e.g., coverage of training activities and respective training material, number of courses (and other related activities) carried out, number of succeeded certified trainers and trainees, analysis of an evaluation questionnaire (for trainers, trainees and third parties).
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work package B6.1 Management training activities Leading Participant SAP Starting M1 Ending M36 Objectives The objectives of this work package are to initially set-up and support the training activities, continuously manage it on a day-to-day basis and provide support services to the other work packages. The initial set-up of the technical infrastructure will take place in C4 to ensure integration and interoperability with other IT systems for supporting the various Action Line B activities. This work package will be linked to Activity B1 on establishment of EIC which will eventually host the training service. . Ongoing activities include support of training activities on a day-to-day in work package B6.3 and marketing activities in order to create and sustain interest in training. This WP includes project management activities to take care of the following issues: collaborations between projects and action lines, progress control, control of creation and submission of deliverables and results, quality assurance, reporting and detailed implementation planning for the project. The individual work package leaders are responsible for the application of the same scope as the project management. For the coordination of the overall progress monthly conference calls or web-conferences and Technical Committees Meetings (comprising the work package leaders) at least every 6 months will be organized by the project lead. The work package leaders and the project leader will provide alternating a progress report (months 6, 12, 18,…) and a status report every 3 months (months 3, 9, 15, ….) For the yearly planning and review checkpoints the project management will provide an up dated detailed implementation plan proposal to the Action Line Coordination 11 months after project start. Description of Work Task B6.1.1: Training support activities. Management of training participants and certificates,
management of trainers, training organisation including but not limited to location selection and booking, provision of training material. This task directly supports work package WP B6.3. Technical project management: mid term action planning.
Task B6.1.2: Marketing activities. Advertising courses and promote the Interoperability Training Service, proactively identify and contact potential participants. This task will seek a close relationship with Activity B2 (Knowledge Sharing).
Collaboration with B1 Receives from B2 Provides to B1, B5
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package B6.2 Content collection, consolidation, preparation and management Leading Participant UNINOVA Starting M1 Ending M36 Objectives Content for training activities will be collected from various sources including research results from projects of Action Line A, requirements and scenarios from the Activities B3 (Business Interoperability Research), B4 (Dynamic Requirements Definition) and B5 (Piloting including Technology Testing Coordination and Pilot Infrastructure), and external research results and experience from the academic, research and industrial communities. This is an ongoing effort in order to keep it up to date. The collected content will be aggregated and consolidated into meaningful entities. Preparation of training material for classroom, virtual classroom or eLearning settings will be based on these entities of content. Based on the concept developed in Task B6.2.1, content will be classified and addressed to the identified target groups (e.g., IT and business managers, IT experts, PhD/MSc students, ATHENA partners, etc.) and their specific requirements. To get current content in necessary quantity and quality this is an example of another activity that overlay with research projects of Action Line A in order to retrieve the content. This might be done either through joint projects, or researchers coming into the activity and providing the content. Description of Work Task B6.2.1: Identify target groups. This task will guide the procedures to identify the content of
the training material to better fit the profile and requirements of each identified target group, and virtual or traditional infrastructure. Pre-identified target groups are: IT and business managers, IT experts, academia (post-docs, PhD/MSc students), ATHENA partners and Interoperability Training Service trainers.
Task B6.2.2: Collect and maintain content from ATHENA for training and education. Collect content from ATHENA research projects and community building activities for the training and education material following the methodology defined by Task B6.2.1.
Task B6.2.3: Collect and maintain content from external sources for training and education. Collect from external sources the content for the training and education material following the methodology defined in Task B6.2.1.
Task B6.2.4: Consolidation and management of training and education contents and activities. Consolidate and update the content collected from Task B6.2.2 and Task B6.2.3, tailored for the target groups identified. During the preparation of the training material in B.6.3, feedback will be provided for potential refinements.
Collaboration with B2 , B5 Receives from All Action Line A projects, B3 , B4 Provides to B5 , B1
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package B6.3 Training Material Leading Participant UNINOVA &
SAP Starting M7 Ending M36
Objectives The objective of this work package is to provide training material in the area of Interoperability. Training courses of interest to a broad community will be identified as well as special courses focussing on specific topics or industries, as reported by WP B6.2. For each training, the training form or mixture of training forms needs to be identified to be adequate according to pedagogical concerns and the target group. Training authors will be introduced to the tools for training creation selected as part of WP6.1, i.e. for class room trainings, for recording virtual classroom sessions and for creating e-learning trainings. Training material will be developed under supervision of the trainers giving the training, and specifically based on the content available from work package B6.2 tailored for the identified target groups, and according to the identified training forms. Trainings will be translated to several languages as far as useful for the respective target groups. Continuous training of trainers, attracting education specialists and feedback collection of attendees will ensure the high quality of the training. Continuously updated list of available training courses will be provided by work package WP B6.1 and distributed by Activity B2. Description of Work Task B6.3.1: Define curriculum of the Interoperability Training Service. Identify general trainings
and specific training topics, specify adequate training forms and provide list of available trainings and services.
Task B6.3.2: Training the Authors. Define and execute a training program for authors that are responsible for developing new training material.
Task B6.3.3: Development of Training Material. Develop the training material as proposed by WP B6.2, aiming the identified target groups, and the virtual and traditional infrastructure.
Task B6.3.4: Training the Trainers. Execute the training program for trainers, including ATHENA internal training.
Collaboration with B1 Receives from All Action Line A and B2 Provides to B5 , B2
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package B6.4 Executing Training Courses Leading Participant TROUX Starting M18 Ending M36 Objectives Training courses will be conducted by educated trainers supported by skilled researchers and industrial experts, selected from the ATHENA consortium. Training courses will be conducted to train and educate the target groups identified in Task B6.2.1. External trainings will be held at different locations: Classroom, University, at partner sites. The trainings will use a blended learning approach. Training course material will be provided by WP B6.3, based on the curriculum defined there. Internal training to ATHENA members will be conducted on a regular basis. Periodicity to be agreed within ATHENA consortium after evaluation of the WP B6.2 results. Feedback from participants will enable the continuous improvement of the training and education services. Description of Work Execute Training Courses. Executes the training courses in a blended approach using virtual and in traditional environments for the identified target groups. Training courses will be conducted on request. Collaboration with B1 Receives from B6.1, B6.1.3, B6.2 , B6.3 Provides to B5 , B1
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Activity Objectives The Programme Administration makes sure that all functions within the programme work effectively and harmonized and receive the administrative support they require for doing so. The structure, including infrastructure, the processes and methodologies will be put in place to allow for a state of the art project management. The overall programme responsibility is shared by the management team consisting of partners represented in the Technology Council and in the Administration. The two functions focus on the areas that are relevant for the success of the overall programme, namely scientific and technological co-ordination and efficient and effective administrative support and service. The beginning of a programme / project is critical for setting up the culture and attitudes for the rest of the life cycle of an undertaking. Efficient Collaboration needs to be supported by fast and effective communication, not only by clear and transparent planning and controlling mechanisms. Tight monitoring of the individual projects and work packages and the establishment of a self control – early warning system are key ingredients for a low risk operation. Timely reporting of potential or already existing out-of-line situation (e.g. being behind schedule, encountering too many roadblocks that put the results under high risk) provide for the basics of instant reaction and proactive activities to recover or redefine projects. Assurance of quality of results and deliverables as well as maintaining a clean implementation process of the activities will keep the quality of the work at the highest possible level. Strong guidance on knowledge and IPR issues will keep the conflict potential at a low level. Well established approval and negotiation processes and responsibilities will keep barriers for early commercialization of results at a minimum. Transparent and reliable communication of the progress of the programme will keep credibility up and make co-operation internally as well as external highly possibly even in critical situation.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package C1.1 Setting up Infrastructure for Administration and Administration Service and Support
Leading Participant SAP Starting M01 Ending M36 Objectives Provide infrastructure for efficient working between partners, between partners and the programme administration and between project management and programme management. A support and service structure will be developed, implemented and maintained for regular communications with the European Commission, internal communication, reporting, and cost claiming. Methodologies and software tools for process management, cost and time tracking to be used will be identified and put forward for approval to be implemented (implemented and maintained in C4). Clear structure and process descriptions will help keep the collaboration frictionless. That support and service structure will enable the project and activity managers as well as the work package leaders to focus solely on their scientific and technology co-ordination tasks. This ensures that their work will be kept focused and an overall administrative synergy is achieved. Description of Work Task C1.1.1. Programme management structure will be physically set up, including programme
office dedicated staff Task C1.1.2. The programme “business” processes will be defined Task C1.1.3. A handbook for the day-to-day administrative aspects will be issued Collaboration with B1 Receives from A/Bx Information Provides to All Handbook and programme manual
Work Package C1.2 Progress and Cost Reporting Leading Participant SAP Starting M03 Ending M36 Objectives Establish clear reporting structure and processes for the whole programme to the European Commission and for the projects activities within the programme. Provide templates for the reporting instances to all concerned participants. Maintain a document repository for incremental reporting. Submit reports and cost claim on time and in the quality required. Prepare the yearly reviews with administrative and co-ordinate the technology input.
Description of Work Task C1.2.1. Establish a continuous progress and monitoring reporting for internal management
and external reporting. Provide regular reports to the European Commission according to the contract regulations.
Task C1.2.2. Distribute cost claim templates, collect the individual cost claims, consolidate with planning and controlling systems. Submit the cost reports for the yearly review.
Task C1.2.3. Prepare the yearly reviews Collaboration with All Receives from All Cost statements Provides to All Feed back and documentation
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package C1.3 Road-Map and Rolling Plan, including Budget and Resource Planning,
Controlling, Quality Assurance and Risk Management Leading Participant SAP Starting M01 Ending M36 Objectives Provide actual and accurate planning for the various planning exercises the programme has to carry out. Together with the Administration, the Technology Council internal project proposals or external sub project proposals will be proposed to the Programme Co-ordination Committee for approval. The rolling plan that has to be provided each year will be jointly developed by the Administration and the Technology Council and will be submitted to the Programme Co-ordination Committee. The road map for the technology area of ATHENA needs to be kept up to date as a basis for the continuous planning for the programme. The key results will be refined at the start of the programme and made available. This activity is linked to the definition of the performance indictors done in Activity C2. Controlling and quality assurance are ongoing processes that will make sure that the programme stays in line with the initial and evolving planning, and that the quality of the work, the deliverables and the results stay at the highest level for wide acceptance. A close controlling will discover early on any divergence from programme and project plans. That way, it will be possible to develop recovery plans and actions. The risk of jeopardising the programme objectives will be minimised. A contingency provision will be integrated in the detailed planning for the final execution.
Description of Work Task C1.3.1. Establish relationships with projects and organisations that carry out road map work
and/or if that is not existent, establish a technology sub group together with the Technology Council to up date the ATHENA roadmap. Roadmap update to be finished for the yearly 18 months planning update. Refine key result descriptions.
Task C1.3.2. Prepare the yearly 18 month detail implementation plan together with the Technology Council and propose it for approval to the Project Co-ordination Committee. Submit it to the European Commission for the yearly review. The detailed implementation plan will contain appropriate detail level on the resources, budget and schedule for acceptance by the European Commission
Task C1.3.3. A regular meeting sequence will be set up with the Action Line Co-ordinator and Project / Activity Managers to review the progress and status of the individual activities. A quarterly formal review will be scheduled with the Programme Co-ordination Committee. A self assessment on current or future risks for meeting schedule, resource or budget plans will be a key part of the reviews. Beside the review all Project /Activity Mangers are obliged to report anticipated out-of-line situations as soon as detected. If it is necessary create proposals for implementation plan modification and/or recovery plans in case of deviation from initial assumptions and initiate discussion with the European Commission
Task C1.3.4. Establish together with the Technology Council a proof cycle for the results, deliverables and progress reports. A quality subgroup consisting of senior members will be supporting the Administration on that. Besides the technology content also readability aspects will be taken into account.
Collaboration with All Projects and action lines C2 Joint refinement of key results and definition of associated performance indicators Receives from AL C Information, Input for future activities Provides to A4.2 Ontology for the tools
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package C1.4 Management of Knowledge and Intellectual Property and Maintenance of Contracts
Leading Participant SAP Starting M01 Ending M36 Objectives Assure adherence to the provisions on IPR in the model contract’s Annex II and the Consortium Agreement. Guide particularly the dissemination and protection of knowledge to comply with the contractual obligation to make results public while at the same time protecting the knowledge created within the project. In specific cases concerning IPR the Consortium Agreement might need to be amended or modified. Finally, the required IPR activity report will be provided regularly as part of the requested reporting. The administrative activities also support the contractual “maintenance” of amendments of the RTD contract with the European Commission for new partners joining the programme. Amendments of the Consortium Agreement fall also within that scope.
Description of Work Task C1.4.1. Establish awareness for creation of knowledge and the obligations to disseminate
and provide access to it. Support activities to protect, and usage of knowledge and in cases needed initiate activities by the European Commission to play a role in this as defined in the Annex II. Provide help to stay in compliance with the consortium agreement and other regulatory documents. In case new partners join the consortium contracts and agreements particularly in sight of new pre-existing knowledge might need to be updated. Also in case the consortium might consider joint exploitation the according legal documents need to be established. The appropriate support needs to be provided for that.
Task C1.4.2. Process approvals of publications in the programme. Publications will appear amongst others from writing of thesis’s, presentation, press releases and demonstrations at fairs. Proper publication documentation will be maintained.
Work Package C1.5 Sub Project Call Management Leading Participant SAP Starting M01 Ending M27 Objectives To provide the structure, define the processes, and assign the responsibilities to meet the requirements for a scientifically viable call, evaluation, and approval process for sub-project in compliance with European Commission regulations. Provide the managerial interface to all aspect of the administrative sub-project handling such as call cycle processing, formalities and contracting.
Description of Work Task C1.5.1. The processes will be set up so that sub-project can be called for and very timely
can be evaluated and contractual matters negotiated. Evaluation of proposals will be conducted by Programme Management (Administration and Technology Council) and external experts in co-ordination with the European Commission as soon as possible after submission of proposals. The aim is to have time to contract that is as short as possible. Negotiations with issuers of successful proposals will be concluded so that the individual projects can start at the planned schedule. The sub-project contractual matters will be handled by the programme administration after the regulation for the European Commission. Further information regarding management of sub project calls is given in the DoW.
Collaboration with B3 B3 will place a call for proposals in 2004 B5 B5 will place a call for proposal later in 2005 Receives from B3, B5 Specification of call details Provides to B3, B5 Call results for common evaluation
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Activity Objectives Scientific/technology co-ordination comprises one of the main aspects at the programme level. It shall provide the methods and carry out the activities to coordinate the overall programme, the action lines and the integration of domains and user group requirements. The scientific/technology coordination will be carried out by the Technology Council for the overall programme, for that is composed of representatives from the Action Line Coordination, Domain Competence Team, exploitation coordination and User Group Watch Dog.
Work Package List Work
package No Work package Title Responsible Particip. No
Work Package C2.1 Technology Council Leading Participant SINTEF & SAP Starting M1 Ending M36 Objectives The Technology Council will assure the integrity, coherence and relevance of the overall programme with reference to the objectives of the programme and from a scientific and technical perspective. From this perspective, it will oversee the progress and results of the Action Line A and Line B. In particular it will ensure that Research and Development projects will be executed in synergy and collaboration with Community Building activities. It will resolve any conflict that cannot be resolved via Action Line Coordination. The Technology Council will be the final arbiter of the scientific/technology direction of the project. The Technology Council will meet regularly or at the request its member(s). Decision making will be in accordance with the procedures laid down in the Consortium Agreement. A focus will be put on appropriate standards activity involvement for ATHENA, and to follow up the defined technical performance indicators. An Industrial Advisory Group, populated by external industrialists preferably from user industries, will be part of the Technology Council. This group will be associated with the User Watch Dog (C2.4).
Description of Work Task C2.1.1 Monitoring. The Technology Council will regularly monitor the progress of the running
projects and activities via reporting from the respective Action Line Coordinators. Task C2.1.2 Evaluation. The Technology Council will regularly review the results of the running
projects and activities and their scientific/technical direction in accordance with the overall objectives of the programme. Both projects and activities will be evaluated twice a year, guided by the reports provided by the Action Line Coordinators. Risks, including the ability of the technical work to support industry requirements input to the project, will be identified. In case of unexpected difficulties in the execution due to scientific/technical risks, the Technology Council will propose and oversee the execution of contingency plan. If major risks are identified, the Council will take appropriate actions, e.g. cancelling projects and starting new projects on topics where more significant results and impact can be achieved. The technology council will provide an analysis of the progress of ATHENA based on the objectives and results of ATHENA and evaluated against the performance indicators, that need to be defined. This analysis will be based on the input of the Action Line A, B and C projects and activities.
Task C2.1.3 Definition. Where there is a need to define new project, activity and subprojects, the Technology Council will provide the appropriate guidance and support at the technical level (e.g. technical objectives, scope, relevance) and will sign-off the technical annex of any new project / activity call which is at the programme level, on the advice of the Action Line Coordinator.
Task C2.1.4 Standards. The technology council will coordinate activities of ATHENA in the standardisation arena. This will include, based on input from the relevant activities in Action Line A and B, an analysis of standards, standards bodies and gaps and potential input to standardisation activities, both in Europe and globally.
Task C2.1.5 External Cooperation. The technology council will be the cooperation point with initiatives within the framework of DG INFSO’s own FP6 eBusiness Coordination.
Collaboration with B2 Standards, Coordination and Reporting C1.3 Refinement of Key Results and associated Performance Indicators
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package C2.2 Action Line Co-ordination Leading Participant TXT & IC Focus Starting M1 Ending M36 Objectives Action Line Coordination will assure the integrity, coherence and relevance of respectively Action Line A and Action Line B with reference to the objectives of the programme and from a scientific and technical perspective. From this perspective, the Action Line Coordination will safeguard the overall direction of the individual Action Lines and oversee the progress of the individual projects/activities within an Action Line. Action Line Coordination will provide the first reference mechanism for resolving conflict between projects / activities within an Action Line. It will also identify potential conflict between Action Lines which it will be bring to the attention of the Technology Council.
Description of Work Task C2.2.1 Monitoring. Action Line Coordinators will regularly monitor the progress of the running projects
and activities which they will report to the Technology Council. Task C2.2.2 Evaluation. Action Line Coordinators will regularly review the results of the running projects
and activities and their scientific/technical direction at the Action Line level in accordance with the overall objectives of the programme.
Task C2.2.3 Definition. Where there is a need to define new project, activity and subprojects, Action Line Coordinators will advise the Technology Council from the perspective of the Action Line objectives and workplan. Action Line Coordinators will sign-off the technical annex of any new sub- project / activity call which is at the Project Level within an Action Line, on the advice of the Project / Activity Manager.
Work Package C2.3 Domain Competence Team Leading Participant ITREC &
TROUX Starting M1 Ending M36
Objectives The Domain Competence Team will assure that the programme will be addressing the needs of the three domains of Enterprise Modelling, Architectures & Platforms, and Ontologies. It will also be responsible for ensuring that the programme and all its components are aware of significant developments in the domains which may impact on the programme of work. The Team will provide guidance and support in respect of the domains at all levels, working closely with the Action Line Coordinators and the Project/Activity Managers.
Description of Work Task C2.3.1 Monitoring. Domain Competence Team will regularly monitor the progress of the running
projects and activities in respect of meeting the requirements of the domains which they will report to the Technology Council.
Task C2.3.2 Evaluation. Domain Competence Team will regularly review the results of the running projects and activities in accordance with the requirements of the domains and will advise the Technology Council accordingly.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package C2.4 User Group Watch Dog Leading Participant EADS & CRF Starting M1 Ending M36 Objectives The User Group Watch Dog will assure that the programme will be addressing the needs of the user organisations and industry sectors. It will also be responsible for ensuring that the programme and all its components are aware of significant developments in the sectors which may impact on the programme of work. The Watch Dog will provide guidance and support in respect of inputting sector requirements and the validation of such requirements for both Action Line A and Action Line B. They will represent and present User interests at the Technology Council, domains at all levels, working closely with the Action Line Coordinators and the Project/Activity Managers. The User Group Watch Dog will make proposals and recommendations regarding additional user organisations and industry sectors that should be involved in the Programme via Community Building.
Description of Work Task C2.4.1 Monitoring. User Group Watch Dog will regularly monitor the progress of the running projects
and activities in respect of meeting the requirements of industry sectors which they will report to the Technology Council.
Task C2.4.2 Evaluation. User Group Watch Dog will regularly review the results of the running projects and activities in accordance with the requirements of the industry sectors and will advise the Technology Council accordingly.
Objectives This work package is planned to establish and maintain continuous exploitation activity to make sure that at any time in the programme life cycle the full exploitation potential is realised and made available to project participants. It is planned to ensure that the single and joint results of the Athena programme are analysed, expressed and reported according to acknowledged standards and formats. It is intended to ensure that the European Interoperability Institute capitalises and leverages clearly sustainable services and standards.
Description of Work The general approach is to break the work into three separate work packages. The first work package will prepare guidelines and tools that the single participants will use when affronting the analysis activities when extracting results from the project Research and Development phases and introducing them in sustainable exploitation contexts. The second work package will ensure that appropriate knowledge sharing tools and artefacts are available for the partners to allow them to carry out the activities planned in these work packages. The third work package will ensure that the procedures that have been laid down are executed in an appropriate cyclical fashion as results become available, identifying proper usage of developments and the sustainability for the solutions and standards developed in the course of the project. Many of the activities carried out and described hereunder will be carried out repeatedly during the course of the ensuing phases of the project. The deliverables produced will be updated according to the particular needs and resubmitted.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package Description Work Package C3.1 Exploitation Planning and Organisation Leading Participant FORMULA Starting M8 Ending M12 Objectives This Task is planned to ensure a standardised approach to Exploitation of the Athena Results within the consortium. It will reduce the exploitation time learning curve of the participants wishing to exploit project results. Evaluation of exploitation possibilities will be carried out on a continual basis starting with the closing period of the first research and development tasks. This task will provide the foundation for the exploitation evaluation and communication process. It will produce guidelines to outline timing, rights and obligations for the exploitation process. It will clearly outline the process with which participants will define their responsibilities regarding the Intellectual Property rights of the materials that are intended to be exploited. It will also provide partners with templates with which they can express their results in commercially acceptable formats. Standardisation results, analysis metrics, and standardised business models will be developed to assist in the identification of the exploitation potential of project results. This will involve the testing of the commercial viability and exploitation potential of the research and development output. Finally, access will be provided to internationally recognised comparison benchmarking tools with which results will be compared.
Description of Work Task C3.1.1 Exploitation Guidelines This task will prepare the guidelines for exploitation of the Athena
results, which will be presented to the consortium as a Deliverable (Deliverable D.C3.1.1 Exploitation Handbook). The Handbook will initially lay down the calendar and timing for the single activities tied to the exploitation. It will describe the quality procedures to be followed to produce the single components required according to the consortium’s vision of exploitation. It will define the rights and obligations of each participant in relation to the other members of the consortium and to the group as a collective body. To this end the handbook will outline legal rights and obligations in the exploitation process and define the precise procedure to be followed in order to define and agree upon Intellectual Property Rights of each partner for the collective knowledge and the single components in question. The Handbook will be made available three months before the termination of the first Research and development activities at month thirteen of the project.
Task C3.1.2: Exploitation Metrics The task leader will prepare a manual for the participating organisations, which will outline procedures to be followed to prepare project specific business metrics to analyse exploitation potential of the proposed components and standards. These guidelines will specifically deal with procedure with which projects will compare their personal evaluation metrics to industry accepted standards using performance measurement models and techniques including Balanced Scorecard38, Skandia Navigator39 EFQM40 and Intangible Assets Monitor4, in order to illustrate competitive strengths and weaknesses in the proposed approach. This manual will be provided as a template within Deliverable D.C3.1.1 Exploitation Handbook) and made available three months before the termination of the first Research and Development activities at month 12 of the project.
Task C3.1.3: Preliminary Exploitation And Use Plan Guidelines The task leader will plan, develop and circulate guidelines, templates and procedures to be followed to elaborate the individual exploitation plans required for preliminary exploitation and use plans which will be prepared by each of the participants on a regular yearly basis which will start with month eighteen of the project. The material will have the format of a template and will be the basis for a consolidation which the leader of work package 3 will use to complete the Exploitation plans (Deliverables D.C3.3.1)
4
38
Ref. Drs. Robert Kaplan (Harvard Business School) and David Norton (Balanced Scorecard Collaborative).
Work Package C3.2 Exploitation Support Infrastructure Leading Participant SAP Starting M9 Ending M36 Objectives The objective of this task is to create a support function to help bridge the gap between the R&D departments and Business-related departments within the single organisations involved in the Athena Project. It will help Research Departments express encouraging results in the “Athena Exploitation Language” essential to the other areas of their companies and the general community. The objective of the task will therefore be to promote, monitor and assist the partners in communicating promising results according to market standards and using the tools laid down in work package C3.1 in order to identify the exploitation potential of their specific results and bridge the gaps between a successful research phase and a business preparation phase. This will place the research results in a market context and facilitate evaluating risks competitors and opportunities. The format will be articulated in the creation of a literature base including maintaining the guidelines and manuals, a help desk, and the running of a project workshop.
Description of Work Task C3.2.1: Exploitation Materials Library The many research and demonstration activities being
performed in the Athena project will give rise to a wide variety of promising results that many partners may wish to exploit. This task will ensemble the knowledge needed to carry out this task and make it available to the partners. In conjunction with the IT support functions planned the Athena Online Business Library will be integrated into the overall IT infrastructure to help partners find information and resources pertaining to exploitation and business planning specific to the Athena Project as well as from a wider Enterprise application business setting. The documentation, tools and tutorials (literature and software) will be built up under the responsibility of the task manager but will be updated by the numerous partners involved in the project.
Task C3.2.2: Athena Online Network Database The Athena Online Network Database will be a web based universally available knowledgebase made available on the same server as the above mentioned library to access general information including descriptions, contact information and links to existing business planning networks, as well as institutions, initiatives, and organisations at EU/national/regional level which offer additional assistance in business plan matters.
Task C3.2.3: Athena Exploitation Manual Maintenance This task will maintain and update the set of documentation originally prepared as Deliverable D.C3.1.1. It will guide partners in the periodic process of preparing their exploitation and use plans giving detailed explanations on how to prepare the draft exploitation plan. Although physically accommodated in the Athena Online Business Library it is separated as a task because of the continual need for updating and maintenance to ensure coherency with updated market and competitor monitoring carried out in task C3.3.2.
Task C3.2.4: Athena Exploitation Workshop At the beginning of the period in which the partners will be carrying out their periodic exploitation planning the Task leader will organise and hold a workshop to coach partners who need assistance. External experts from the business planning communities will be called to assist and hold specific sessions.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package C3.3 Exploitation Planning Leading Participant Formula Starting M18 Ending M36 Objectives Interoperability of Enterprise applications on the highest level competes in an international market place with other products, services and standards already available in the market place (but usually to resolve specific interoperability problems in particular environments). This work package intends to carryout the several phases of analysis that are common or come before the promotion of Athena results in that marketplace. The objective of this task is to ensure that results are analysed and expressed in a common market ready manner through the creation of individual and joint exploitation planning.
Description of Work Task C3.3.1: Product Definition This task will work with the single areas and provide joint and
separate product definition periodically throughout the project lifecycle, starting at month 19. It will initially set down a framework for describing application scope of software components and architectures that are at the base of the future products that will become available through the Athena Project. It will then map the proposed exploitable components from the research and demonstration projects to the framework thus creating a product definition that will delineate all exploitable results in a common format.
Task C3.3.2: Market analysis This activity will carry out an extensive market analysis to understand the areas in which Athena products and services can compete in the marketplace. Analysis will be undertaken to provide a view of Market segmentation and trends of Enterprise modelling tools, Ontology tools, and Service oriented products.
Task C3.3.3: Market strategy This task will outline Athena participants Market Strategies, Target customers and users, Target customer needs and therefore target markets. It will lay down a recommended market strategy and rollout plan defining market roles and business delivery processes and clearly defining target market segments to be addressed.
Task C3.3.4: Partner’s Joint and Separate Exploitation Plans This activity will consolidate the definition, analysis and strategy activities carried out in the preceding tasks and prepare Exploitation Plans for each of the partners, the European Interoperability Institute and the consortium as a whole. It will be carried out using the templates and guidelines provided in work package C3.1. Each partner will prepare their own plans and maintain them on a continual basis. The Task leader will consolidate the individual plans and prepare a joint exploitation plan for the consortium as a group and provide them to the commission as a single Deliverable (D.C3.3.1) at month 24.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
The objective of the IT Infrastructure and Integration activity is delivering, deploying, operating and supporting a common networking platform on the Internet and Intranets integrated by an intelligent infrastructure. Providing services to integrate methods and new services (tools and applications) to deliver and support operational platforms for all A projects, B community activities, and C management services. The complex ATHENA programme needs transparency in all activities, and must provide easy and safe access for participants and community members. C4 will secure availability of relevant services and applications for research collaboration and performance, for knowledge sharing, for requirements management (DRMS), for use-case scenarios and solutions, for planning and building communities, for providing access to and use of research results, and for dissemination/ exploitation. The IT Infrastructure will be coordinated, supported and managed by an ATHENA enterprise model and sub-models delivered by project A1. The model will include the project description with many structures and dynamic internal and external dependencies. The portal layout will eventually be generated from a sub-model, and contents will also be derived from models. The activity will define and manage a wide spectrum of useful services limited only by resource availability, and will also launch tasks to provide new services by integrating the results produced in research projects as well as accessible web-services. Databases and repositories with project master-data and core will be continuously managed. An operation management concept (ITIL conform) will regulate the service provisioning according to agreed system monitoring principles, problem and order handling (e.g. user access and change request like software integration, portal structure change request, backup handling). The activity will organise and request needed training for using the portal-based user environments and services.
Work Package List Work
package No Work package Title Responsible Particip. No
Person Months
Start Month
End Month
C4.1 Design, delivery and support of User Environments, Contents and Services 4 – TROUX 12,9 M01 M18
C4.2 Provide and support user admin. And infrastructure services, and develop maintenance and backup routines
4 – TROUX 11,6 M01 M18
C4.3 Deleted 1,0
C4.4 Design and delivery of User Environments and Services 4 – TROUX 7,1 M19 M24
C4.5 Provide and support user administration and infrastructure services, and develop maintenance and backup routines
4 – TROUX 1,0 M19 M24
33,6 M01 M24
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package C4.1 Design, delivery and support of User Environments, Contents and Services
Leading Participant TROUX Starting M01 Ending M18 Objectives The main objective of this work package is to provide new versions of the portal-based User Environments to support the running of the IP. The initial version will focus project description, initiation, planning and reporting, and will be using existing hardware and software.
Derived from the first project model version 1.0 of the infrastructure will contain:
User Environment server with user admin.
Services for document and knowledge model sharing and management
In the next version, after 9 months, the complete knowledge model for all projects and activities will be defined and implemented. Requirements to upgrade the hardware will be assessed after the first 6 months, and a hardware plan will govern investments in new servers for new hubs.
Most of the portal content will be defined and generated by the project model, and the public view on the portal with web-site, virtual conference rooms and administration procedures to handle visitors and clients will be designed and implemented. A content management model and services will support the user access to portal content.
Description of Work Specify, define and implement versions of User Environments and contents:
Task C1.5.1. Elaborate the model based content concept and implement the infrastructure services, and user environments into the portal server.
Task C1.5.2. Implement the User Environments, contents and services Task C1.5.3. Deliver the services to all user categories and communities
Collaboration with In particular the Intelligent Infrastructure as developed and delivered by A1, and inter-enterprise business processes from A2. Both will, in due time, be used to support the communities involved in all B activities. Receives from All projects and activities, also C activities, will continuously define their needs for services and contents. Most content will be produced and maintained by knowledge models driven by meta-models. Provides to All projects and activities are using operational platforms derived from the common platform, the IT infrastructure.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package C4.2 Provide and support user admin. And infrastructure services, and develop maintenance and backup routines.
Leading Participant TROUX Starting M01 Ending M18 Objectives This work-package defines and manages user categories and levels of services, and launch development tasks to integrate the various knowledge and software components (e.g. jre 1.4.2), and web-based versions of the software components developed during the project (EM repository and visualisation services). An integration plan will be elaborated and maintained during the whole project, and relevant databases and repository master-data has to be managed continuously.
An operations concept (ITIL conform) will regulate the daily service delivery according system monitoring, problem and order handling (e.g. user access and change request like software integration, portal structure change request, backup handling). Significant changes of the IT infrastructure will be decided during the regular project coordinator meetings.
Description of Work Task C4.2.1. Elaboration of a model based operational concept Task C4.2.2. IT infrastructure operation (monitoring, handling problems and change requests) Task C4.2.3. Implement and maintain Project A and B specific platform infrastructures to integrate
application software environments (on the common platform) Task C4.2.4. Integrate and deliver new versions of the infrastructure Task C4.2.5. Deliver upgrading and back-up services
Collaboration with All A projects and B and C activities Receives from A and B problem and change requests, and requests for new capabilities and services. These will be communicated as requirements to the A projects . Provides to All users and communities an integration plan for software environments, and a release plan for platform changes and upgrades
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package C4.4 Design and delivery of User Environments and Services
Leading Participant TROUX Starting M19 Ending M24 Objectives The objectives for this WP are:
- Rollout the finished ACP version 2.0 with a new server before end of August 2005,
- Bringing all project managers and users up to speed in using the ACP,
- Integration of project management services for deliverables, working documents and results management services – improved C1 portal,
- Integration of Athena results to enable the testing and management of results and various ways of realizing services.
Description of Work Task C4.4.2: Design and development of capabilities and services. The work to design and develop
new capabilities is planned and coordinated at the Oslo meeting within each of projects A1, A6, B4, B6 and C3.
Task C4.4.2: Integration and delivery of new contents and services. Contents and services are also designed and planned at the quarterly ATHENA meetings. Valuable input and validation has been received from projects A1, A6, B3, B4, B6, C1 and C3 regarding new structured contents and services. Some of these will be delivered with version 2.0.
Task C4.4.2: Support to all projects in using the ACP. All projects need support in taking the new capabilities, content structures and services into use.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Work Package C4.5 Provide and support user administration and infrastructure services,
and develop maintenance and backup routines Leading Participant TROUX Starting M29 Ending M24 Objectives The objectives this WP are:
- Integration of selected execution platforms to enable the development, execution and management of various ways of realizing services.
- Supporting all portal managers with guidance as to design and operation of the portals,
- Providing operational support such as backup, and maintenance of contents.
Description of Work Task C4.5.2: User Administration and Infrastructure Services. The work to perform services and
support the project-leaders and users to get access and use the ACP has followed the plans plans. Troux will continue the support in other projects and does not expect to have any resources to transfer, if there are resources left they will go to C2 work.
Task C4.5.2: Performing Maintenance and Backup. The work to maintain the contents and to perform backup has followed the expected progression. A new server with version 2.0 is ready for the roll out of version 2.0.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
8.1 Proposed Changes included in project/activity descriptions of the implementation plan update
8.1.1 Action Line A
Change Number
Project / WP Description Comments
CR.1 DoW Replace Graisoft with ITREC
CR.2 DoW Replace Computas with TROUX
CR.A1.1 A1 Missed final update of A1 during Annex I preparation:
- Duration of A11 and A12
- A11 and A12 text
CR.A1.2 A1 Decreasing CNR-IASI resources in A1 from 4,8PM to 2,5PM (compensated by increase in A2 see CR.A2.3)
CR.A1.3 A1 Removed deliverable D.A1.7.1 ’18 Month Progress report’. Progress report to be included in regular project progress reports (D.C1.2)
No reduction of objectives, ambitions, goals and results.
CR.A1.4 A1 Extended A1 to M24. New WPs, Deliverables and Working Documents included as presented at review and approved.
New change introduced after M12 review
CR.A2.3 A2 Increasing CNR-IASI resources in A2.3 by 2,3PM (compensated by a reduction in A1, see CR.A1.2)
CR.A2.4 A2 Removing task A2.3.4 from Resource and Gantt charts as it was not existent in the DoW.
CR.A2.5 A2 Move M12 Milestone contribution ‘Method for semantic annotations to CBPs’ to Milestone M24.
CR.A2.6 A2 AIDIMA left A2. Resources went to A2 pool. A2 will identify new WP lead and reassign resources.
CR.A3.2 A3 Submission of A3 project re-planning to cope with an earlier delivery of the A3 Deliverables in order to meet other AL A requirements. The manpower distribution has been reallocated differently to the A3 WP’s but the total A3 ( and each partner’s allocation) has remained unchanged. The impact on deliverables in detail:
- D.A3.1 is split in two deliverables. The new D.A3.1 is delivered in M12 and the second half (the new D.A3.2) is delivered in M20
- D.A3.3 (the former D.A3.2) is moved forward by 6 months to M20
- D.A3.4 (the former D.A3.3) is moved forward by 6 months to M22
- D.A3.5 (the former D.A3.4) is moved forward by 6 months to M24)
The impact on WPs in detail:
- A3.3 is now M5-M20 (previously M7-M26)
- A3.4 is now M10-M20 (previously M13-M26)
- A3.5 is now M12-M22 (previously M17-M28)
- A3.6 is now M14-M24 (previously M19-M30)
No reduction in ambition or workprogram; an earlier delivery of A3 deliverables is proposed.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
These changes have direct impact on the milestone table which is adapted accordingly
CR.A3.3 A3 Together with the previous change a deletion of the original WD.A3.3 was proposed. This WD was not necessary as ATHOS was delivered. Other WDs have been moved forward. Due date of WD.A3.6 was moved forward to M18.
New change introduced after M12 review
CR.A4.1 A4 Merge WD.A4.5 into WD.A4.4. Keep Delivery date at M24 New change introduced after M12 review
CR.A5.1 A5 AIDIMA withdraws project A5 and the resources for that project leave as it has been consumed up today:
• A5.1: 0,33 pm The rest of AIDIMA resources are free for other partners : 3,15 pm. A5 to decide on resource re-assignment
CR.A6.3 A6 A6 Mismatch of DA6.2 and WP A6.2 timelines
- Change date for WD.A6.2.1: M12 (from M9)
- Change date for D.A6.2: M22 (from M12)
CR.A6.4 A6 Internal Realignment of A6 reflecting project responsibility for A6 by IBM and SIEMENS as well as better understanding of internal dependencies. See separate available documents detailing the overall realignment of A6.
CR.A7.1 A7 Added Project Management WP New change introduced after M12 review
CR.A8.1 A8 Added Project Management WP New change introduced after M12 review
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
CR. B1.1 B1 Inconsistency between WP description and Gantt
- Start date of B1.2 to be M6
- Start date of B1.3 to be M8
CR.B2.1 B2 All releases (M24, M36) of deliverable D.B2.3 removed. Reporting will be incorporated in regular project progress reports (D.C1.2).
CR.B3.1 B3 Major realignment of B3. Details include:
- Merge WP2 into WP1. Current work in WP2 to be added to WP1.
- Leader of (new) WP1 Contractor selected under sub-project call. Interim leadership is provided by FORMULA.
- Responsibility for deliverables D.B3.1, D.B3.3 and D.B3.4 are handed over to contractor
- Deliverable D.B3.2 to replaced by new WD.B3.3 and merged into D.B3.1
- Initial versions of deliverables D.B3.1 and D.B3.3 are replaced by new WD.B3.4 and WD.B3.5 respectively. Lead participant is handed over to contractor
CR.B3.3 B3 Included new contractors in Activity Plan. Added Working Document (WD.B3.6) detailing the involvement of the new partners in B3.
CR.B4.1 B4 Have Intracom and EADS as Activity Leads
CR.B4.7 B4 Extend duration of Task B4.1.3 till the completion of the program
CR.B4.9 B4 Task B4.2.2 to start on M3 and not on M5. The discussions in Lisbon indicated that it would be better to have something running quickly that will be improved through an iterative process.
CR.B4.11 B4 Have WP B4.6 start on M6 (as indicated in the Gantt Chart) and not on M3 as indicated on the WP description.
CR.B4.18 B4 The scope and objectives of WP.B4.3 should change to reflect the progress already made and to make better use of the resources. The issue was introduced in ATHENA workshop in Rot and further discussed in B4 meeting in Brussels, November 2004. The new workpackage description is now expected from the WP Leader (UNINOVA)
CR.B5.1 B5 Update Activity description Alignment with rules set out for projects / activities (e.g. reducing number of deliverables). In detail:
- D.B5.1 (M12) collects all deliverables containing results of WP B5.1: D.B5.1.1, D.B5.1.2, and D.B5.1.3
- D.B5.2 (M30) collects all deliverables containing results of WP B5.2: D.B5.2.1, and D.B5.2.2
- D.B5.3 (M36) replaces D.B5.3.1
- D.B5.4 (M24, M36) represents results of WPs B5.4, B5.5, B5.6, B5.7, and B5.8: D.B5.4.2, D.B5.5.2, D.B5.6.2, D.B5.7.2 and D.B5.8.2
Furthermore, intermediate results will be documented by new Working Documents.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
CR.B5.2 B5 Added WPs B5.9 and B5.10 to cover scenarios that are expected to be provided through the B5 sub-project call.
New change introduced after M12 review
CR.B5.3 B5 Reduced resources in B5.2 (Sub-Project Call Preparation and Management) as this support is provided by C1. Resources moved to B5.3 for support of testing framework. Deleted deliverable D.B5.2 as this information is provided by the European Commission.
New change introduced after M12 review
CR.B5.4 B5 Removed M24 version of D.B5.4 as this version was planned to be WD.B5.6.
New change introduced after M12 review
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
CR.C1.1 C1 Realign deliverable schedule. In detail:
- Delay releases of D.C1.2 ‘Project Reports’ by one month.
- Provide D.C1.3 ‘Interoperability Roadmap’ on M24 and M36
- Provide D.C1.4 ‘Yearly detailed implementation plan of the next 18 months’ in M25.
- Provide cost statements (D.C1.5) two months after the reporting period.
- Deliverables D.C1.6 for the B5 Sub-project call are planned to be provided in M19.
CR.C2.2 C2 Include reports of WP C2.2 (Action Line Coordination), C2.3 (Domain Competence Team) and C2.4 (User Group Watch Dog) in M12, M24 and M36 into respective versions of D.C1.2 (Project Reports) in M12, M24 and M36. In detail:
- Remove D.C2.3 ‘Action Line Coordination Report to the Technology Council for M12, M24 and M36
- Remove D.C2.4 ‘Domain Competence Team Report to the Technology Council’ for M12, M24 and M36
- Remove D.C2.5 ‘User Group Watch Dog Report to the Technology Council’ for M12, M24 and M36
The content of these reports will be included in D.C1.2 ‘Project Report’ in M12, M24 and M36.
CR.C4.1 C4 Activity to be continued until months 24 to conclude preparation and provision of common technical platform to A and B activities. Maintenance can be covered after that in a B5 WP. New WPs (C4.4 and C4.5) added to cover time between M19 and M24.
CR.C4.2 C4 WP C4.3 is eliminated. AIDIMA has set up a Website under own control and resources will need to be re-allocated.
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
8.2 Proposed Changes to deliverables Changes to aspects of deliverables (Title, Delivery Dates) are highlighted in yellow. 8.2.1 Action Line A
Del.No Deliverable Title DoW Submission Date
Impl. Plan Update
Nature Dissem. Level
D.A1.1.1 First Version of State of the Art in EM technology to support enterprise interoperability M06 M06 R PU
D.A1.2.1 Model and Report: First Set of Requirements M09 M09 R PU D.A1.3.1 Report on Methodology description and guidelines
definition M11 M11 R PU
D.A1.4.1 Report and Model: First Version of Establishing and management approach M12 M12 R PU
D.A1.5.1 Collaborative Modelling Platform specification M04 M04 R CO D.A1.5.2 Collaborative Modelling Platform first prototype M14 M14 P PU D.A1.6.1 Benefit-Assessment M16 M24 R CO D.A1.7.1 18 Month Progress report M18 R CO D.A1.7.2 Detailed Implementation Plan for Month 12 to Month 30 M11 M11 R CO
D.A2.1 Cross-Organisational Business Process requirements and the State of the Art in Research, Technology and Standards M21 M21 R PU
D.A2.2 Specification of a Cross-Organisational Business Process Model M15 M15 R, P RE
D.A2.3 Architecture for Enactment and Integration of Cross-Organisational Business Processes M18 M18 R RE
D.A2.4 Enactment of Cross-Organisational Business Processes M21 M21 R, P CO D.A2.5 Validation of Research Results M24 M24 R PU
D.A3.1 SoA and Technical specifications of Ontology Authoring and Management System, with Ontology Modelling Language
M26 M12 R+P CO
D.A3.2 Ontology Authoring and Management System for Informational knowledge and Business Processes M20 R+P CO
D.A3.3 Semantic Annotation language and tool for information and Business Processes M26 M20 R+P CO
D.A3.4 System for reconciliation rules specification, storage and management M28 M22 R+P CO
D.A3.5 A reconciliation and mediation engine, capable to efficiently process semantic mediation and reconciliation rules M30 M24 R+P CO
D.A4.1 Requirements for Interoperability Framework, product-based and process-based Interoperability Infrastructures, Interoperability Life-cycle Services
M12 M12 R RE
D.A4.2 Specification of Interoperability Framework and Profiles, Guidelines and Best Practices M36 M36 R PU
D.A4.3 Product-based Interoperability Infrastructure and Profiles M36 M36 R+P RE D.A4.4 Process-based Interoperability Infrastructure and Profiles M36 M36 R+P RE D.A4.5 Interoperability life-cycle Services M33 M33 R+P CO
D.A4.6 Validation of research results – product-based and process-based interoperability infrastructures, Interoperability life-cycle Services
M36 M36 R RE
D.A5.1 Perspectives on Service-Oriented Architectures and there application in environments that require solutions to be planned and customisable.
M21 M21 R PU
D.A5.2 Model and Specification of service description and usage as well as advanced concepts M18 M18 R RE
D.A5.3 Architecture of SOA platforms M21 M21 R RE
D.A5.4 Execution Framework(s) for Planned and Customisable Service-Oriented Architectures M21 M21 R, P CO
D.A5.5 Validation of Research Results M24 M24 R PU D.A6.1 Specification of a basic architecture reference model M12 M12 R PU D.A6.2 Enhanced Registry/Repository Infrastructure M12 M22 R+P PU D.A6.3 Model-driven and Adaptable Interoperability Framework M24 M24 R+P PU D.A6.4 Model-driven and Adaptable Interoperability Infrastructure M24 M24 R+P PP
D.A7.1 Analysis of Industry Best Practice in Business Documents and Protocols M24 R PU
D.A7.2 ATHENA approach to Business Document and Protocol management M34 R+P RE
D.A7.3 Business Content for Selected Industry Best Practice M36 R+P RE
D.A8.1 Analysis of Interoperability Situation and needs of SMEs and current approaches M24 R PU
D.A8.2 Guidelines and Best Practices for applying the ATHENA Interoperability Framework to support SME participation in Digital Ecosystems
M36 R+P RE
D.A8.3 Updated ATHENA tools and infrastructures supporting B5 Sub Projects M36 R+P RE
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
Level D.B1.1 Charter, statutes, bylaws, policy, structure and services M06 M06 R CO D.B1.2 Business plan of the EIC M12 M12 R CO D.B1.3 Institute recruitment and operations strategy M12 R CO D.B1.4 Member categories and services M15 R CO D.B1.5 Event programme and core activity overview M18 M18 R PU D.B2.1 ATHENA outreach strategy and plan M06 M07 R I D.B2.2 ATHENA conference M24 M24 R PU D.B2.2 ATHENA conference M36 M36 R PU
D.B2.3 Roundtables, focus groups, Workshops, knowledge cafés, papers, articles and conferences report M12 M12 R PU
D.B2.3 Roundtables, focus groups, Workshops, knowledge cafés, papers, articles and conferences report M24 R PU
D.B2.3 Roundtables, focus groups, Workshops, knowledge cafés, papers, articles and conferences report M36 R PU
D.B3.1 Business Interoperability Framework - Version 1 (initial) M18 R PU D.B3.1 Business Interoperability Framework M36 M36 R PU
D.B3.2 Assessment of Networked Organisations and Value Models Version 1 (initial) M16 R PU
D.B3.2 Assessment of Networked Organisations and Value Models Version 2 (interim) M34 R PU
D.B3.3 Interoperability Impact Analysis Model Version 1 (initial) M18 R RE D.B3.3 Interoperability Impact Analysis Model M34 M34 R PU D.B3.4 ATHENA Impact Assessment M36 M36 R RE
D.B3.5 ATHENA Contribution to Interoperability Policy Action Plan Version 1 M12 M12 R PU
D.B3.5 ATHENA Contribution to Interoperability Policy Action Plan Version 2 M24 M24 R PU
D.B3.5 ATHENA Contribution to Interoperability Policy Action Plan Version 3 M36 M36 R PU
D.B3.6 Business Interoperability Long Term Research Requirements (preliminary) M35 M35 R RE
D.B4.1 Dynamic Requirement Definition Principle M06 M06 R RE D.B4.2 Global processes of reference M12 M12 R RE D.B4.3 Scenarios mapped with Interoperability issues M12 M12 R RE D.B4.3 Scenarios mapped with Interoperability issues M24 M24 R RE D.B4.3 Scenarios mapped with Interoperability issues M36 M36 R RE D.B4.4 DRDS M12 M12 O RE D.B4.4 DRDS M24 M24 O RE D.B4.4 DRDS M36 M36 O RE D.B5.1 Methodology & Technology Testing Report M09 R CO D.B5.1 Methodology & Technology Testing Report M18 R CO D.B5.3 Users Guide to ATHENA Prototyping Services M36 R PU D.B5.4 Post Test Evaluation M36 R PU
D.B5.1.1 Term of Reference for the Technology Testing Network M04 R CO D.B5.1.2 Coordinated Validation Plan, Technology testing Quality
assurance M06 R CO
D.B5.1.3 International Cooperation Plan M09 R PU D.B5.2.1 Portal contents, templates, for proposal preparation M06 R PU D.B5.2.2 Portal technical guidelines for submission and performance M06 R PU D.B5.3.1 Users Guide to Athena Prototyping Services M06 R PU D.B5.4.1 Aerospace Pilot: Test Cases for Validation(version 1) M12 R PU D.B5.4.1 Aerospace Pilot: Test Cases for Validation(version 2 Final) M24 R PU D.B5.4.2 Aerospace Pilot: Post Test Evaluation(version 1) M21 R PU D.B5.4.2 Aerospace Pilot: Post Test Evaluation(version 2 Final) M36 R PU D.B5.5.1 Automotive Pilot: Post Test Evaluation(version 1) M12 R PU D.B5.5.1 Automotive Pilot: Post Test Evaluation(version 2 Final) M24 R PU D.B5.5.2 Automotive Pilot: Post Test Evaluation(version 1) M21 R PU D.B5.5.2 Automotive Pilot: Post Test Evaluation(version 2 Final) M36 R PU D.B5.6.1 Furniture Pilot: Post Test Evaluation(version 1) M12 R PU D.B5.6.1 Furniture Pilot: Post Test Evaluation(version 2 Final) M24 R PU D.B5.6.2 Furniture Pilot: Post Test Evaluation(version 1) M21 R PU D.B5.6.2 Furniture Pilot: Post Test Evaluation(version 2 Final) M36 R PU D.B5.7.1 Telecom Pilot: Post Test Evaluation(version 1) M12 R PU D.B5.7.1 Telecom Pilot: Post Test Evaluation(version 2 Final) M24 R PU D.B5.7.2 Telecom Pilot: Post Test Evaluation(version 1) M21 R PU D.B5.7.2 Telecom Pilot: Post Test Evaluation(version 2 Final) M36 R PU
D.B5.8.1 Pilots in other areas: Extension of specific methods and techniques M24 R PU
D.B5.8.2 Pilots in other areas: Post Test Evaluation M36 R PU D.B6.1 Target Group Analysis M18 M18 R RE D.B6.2 Curriculum of the Interoperability Training Service M24 M24 R PU
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
D.C1.2 Project Reports including: Progress report, Dissemination activity report, Standardisation report, IPR report, Report on using and disseminating of knowledge
M06 M07 R PP
D.C1.2 Project Reports including: Progress report, Dissemination activity report, Standardisation report, IPR report, Report on using and disseminating of knowledge
M12 M13 R PP
D.C1.2 Intermediate Project Reports including focusing on key aspects M18 M19 R PP
D.C1.2 Project Reports including: Progress report, Dissemination activity report, Standardisation report, IPR report, Report on using and disseminating of knowledge
M24 M25 R PP
D.C1.2 Intermediate Project Reports including focusing on key aspects M30 M31 R PP
D.C1.2 Project Reports including: Progress report, Dissemination activity report, Standardisation report, IPR report, Report on using and disseminating of knowledge
M36 M37 R PP
D.C1.3 Interoperability Roadmap up date made available 2 months before submission of detailed implementation plan of the next 18 months
M10 M10 R PU
D.C1.3 Interoperability Roadmap up date M22 M24 R PU D.C1.3 Interoperability Roadmap up date M34 M36 R PU D.C1.4 Yearly detailed implementation plan of the next 18 months M12 M12 R PP D.C1.4 Yearly detailed implementation plan of the next 18 months M24 M25 R PP D.C1.5 Submit yearly cost statements M13 M14 R D.C1.5 Submit yearly cost statements M25 M26 R D.C1.5 Submit yearly cost statements M37 M38 R D.C1.6 Sub-project call for the individual projects M06 M06 R D.C1.6 Sub-project call for the individual projects M09 M19 O D.C1.6 Sub-project call for the individual projects M12 M19 O D.C2.1 ATHENA Performance Indicators M03 M03 R CO D.C2.1 ATHENA Performance Indicators - Update M12 M12 R CO D.C2.2 ATHENA Evaluation of Achieved Results and Generated Impact M12 M13 R CO D.C2.2 ATHENA Evaluation of Achieved Results and Generated Impact M24 M25 R CO D.C2.2 ATHENA Evaluation of Achieved Results and Generated Impact M36 M37 R CO D.C2.3 Action Line Coordination Report to the Technology Council M12 R CO D.C2.3 Action Line Coordination Report to the Technology Council M24 R CO D.C2.3 Action Line Coordination Report to the Technology Council M36 R CO D.C2.4 Domain Competence Team Report to the Technology Council M12 R CO D.C2.4 Domain Competence Team Report to the Technology Council M24 R CO D.C2.4 Domain Competence Team Report to the Technology Council M36 R CO D.C2.5 User Group Watch Dog Report to the Technology Council M12 R CO D.C2.5 User Group Watch Dog Report to the Technology Council M24 R CO D.C2.5 User Group Watch Dog Report to the Technology Council M36 R CO D.C3.1 Exploitation Guideline M12 M12 R PU D.C3.2 Athena Exploitation Workshop M18 M18 O RE D.C3.3 Joint and Individual Exploitation Plans M24 M24 O RE
IP- Project / Programme ATHENA Project - No 507849 ATHENA - Project Programme Administration Project Number C1 Document Deliverable C1.4 Date 14.07.05
9.1 Efforts for the last 24 months (M13 to M36) The resources estimated in the table below are subject to regular internal and external (by the European Commission) reviews and changes throughout duration the implementation of the individual projects might take place.
SAP AIDIMA TROUX CR FIAT DFKI EADS ESI FORMULAFHG IPK ITREC C FOCUSNTRACOMLEKS SINTEF TXT V. BordeUNINOVA IBM SAG INSEAD H.S.G
Projects Action Line A 1 2 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 Total [PY]Enterprise Modelling in the Context of Collaborative Enterprises 0,2 1,5 0,1 0,0 0,3 0,6 2,1 0,2 0,3 0,8 0,7 6,9
9.2 Budget for the last 24 months (M13 to M36) The budget estimated in the table below is based on the resources allocated to the individual projects as can be seen in the previous resource estimation table.
1000 € (EURO)
Partner # CM Total Cost Grant Total Cost Grant Total Cost Grant Total Cost Grant Total Cost Total Funding
SAP 1 FC 2.325,4 1.162,7 0,0 0,0 259,3 259,3 451,2 451,2 3.035,8 1.873,1
