CORA FINAL REPORT. Grant Agreement number: Project acronym: CORA. Project title: COmmon Reference Architecture

Transcription

1 CORA FINAL REPORT Grant Agreement number: Project acronym: CORA Project title: COmmon Reference Architecture Period covered: from: 08/10/2009 to: 07/11/2010 Name, title and organisation of the scientific representative of the project's coordinator 1 : Dr. Carlo Vaccari, Software Development Manager, ISTAT- Istituto Nazionale di Statistica vaccari@istat.it Project website 2 address: This document is distributed under Creative Commons licence "Attribution-Share Alike ", available at the Internet site: Usually the contact person of the coordinator. The home page of the website should contain the generic European flag and the Eurostat logo which are available in electronic format at the Europa website (logo of the European flag: The area of activity of the project should also be mentioned.

2 1. Final Publishable Summary Report The ESSnet on COmmon Reference Architecture (CORA) started on October 2009 and ended on November 2010 for a total duration time of 13 months. It has involved seven NSIs as participants, specifically: Istat (Italian National Institute of Statistics) as coordinator, DST (Statistics Denmark), SCB (Statistics Sweden), LS (Latvia Statistics), SFSO (Swiss Statistics), SSB (Statistics Norway) and CBS (Statistics Netherlands). In Table 1, for each country participating to the ESSnet, the contact name and a reference e- mail address are listed. Country Contact Name address Italy Carlo Vaccari vaccari@istat.it Denmark Helle Stender hgs@dst.dk Sweden Jacob Engdahl jakob.engdahl@scb.se Latvia Norbert Talers norbets.talers@csb.gov.lv Switzerland Dieter Profos Dieter.profos@bfs.admin.ch Norway Jenny Linnerud jal@ssb.no Netherlands Marton Vucsan mvcn@cbs.nl Table 1. Country contacts In the past, each NSI made different choices with respect to adopted business processes and IT platform; as NSIs share similar goals and surveys, in principle each of them could be supported by a common architecture. The presence of a common reference architecture brings to: (a) stronger cooperation among the different NSIs; (b) sharing of IT solutions and consequent cost reduction; (c) quality improvement of existing solutions for both business and technical aspects of NSIs. These three points can be considered as the main CORA ESSnet objectives. In the CORA website ( a complete description of the project objectives can be found as well as a complete description of each work-package, all the deliverables, meetings and a complete reference list. The work of the ESSnet has been divided into five work-packages. WP5 WP3 WP1 WP2 WP5 WP4 Business Architecture Technical Architecture Organizational Architecture Project Management Requirements Collection State of the Art Project Dissemination Figure 1. WPs organization As shown in Figure 1, two WPs, namely WP3 and WP4, were dedicated to the implementations of the objectives related to the design of the architecture as a result of an integration of the three composing dimensions, i.e. business, technical and organizational dimensions. WP2 was dedicated to the collection of previous work, as well as to a collection

3 of requirements from several NSIs, not only the ones participating to the ESSnet. Finally, WP1 and WP5 were respectively devoted to the management and the dissemination activities. The participation to each WP by each partner is detailed in Table 2. Istat DST SCB LS SFSO SSB CBS Wp1 C P P P P P P Wp2 P P C Wp3 P P P P P P C Wp4 P C P Wp5 C P P P P P P Table 2. Participation to WPs (C=coordination, P=participation) In the following sections, the work done for each WP is detailed. 1.1 WP1: Project Management WP1 started on month M1 and ended on month M13. This WP managed all the administrative aspects of the ESSnet including the preparation of the meetings, the management of the project financial statements and the monitoring and quality assurance of the outcomes of the project. During the ESSnet the following meetings have been held: o Kick-off meeting - Luxembourg, October 2009: Number of participants: 17 Presence of Countries: all participating countries o WPs Leader Meeting The Hague, January 2010: Number of participants: 7 Presence of Countries: all WP leading countries o Intermediate Meeting Rome, March 2010: Number of participants: 20 Presence of Countries: all participating countries o Final Meeting Luxembourg 18 October 2010: Number of participants: 26 Presence of Countries: all participating countries but Latvia, representatives of Eurostat, UNECE, Germany, Iceland, Czech Republic, Slovakia, Portugal, Estonia, France. This WP has produced four deliverables: 1.1 Preliminary Report, 1.2 Intermediate Report, 1.3 Final Report and 1.4 Cost Report. These deliverables, like all the deliverables of the ESSnet, have been published on the CORA wiki, on the CORA web site and on the OSOR portal under the Common Creative Licence WP2: Requirements Collection and State of the Art WP2 started on month M1 and ended on month M6. The objectives of this WP were the collection of requirements to be used as inputs to WP3 and WP4, the production of the state of the art report with respect to the architectures and the software products currently adopted by European NSIs. To this purpose, a questionnaire has been designed (deliverable 2.1) and distributed to 42 NSIs composed of 27 EU, 3 EFTA, 3 candidate countries, 4 potential candidate countries and 3

4 5 other MSIs countries. We had a response rate of about 79% that is 33 NSIs out of 42 contacted, namely 21 EU, 3 EFTA, 3 candidate countries, 3 potential candidate countries and 3 other MSIs countries. Figure 2 shows the graph of the receipt of the questionnaires. Figure 2. Receipt of questionnaires The questionnaire covers the following topics: Statistical business process model adopted by the NSI; GSBPM sub-processes for phase 5 Process ; Enterprise Architecture; Tools: o Shared software: software tools developed by NSIs and currently shared with other NSIs; o Candidate software: software tools under development or developed by NSIs that are not currently shared but that could be further developed to serve a wider number of NSIs; State of the art and comments. The responses to the questionnaire have been summarised in a Set of requirements report (deliverable 2.2). By agreement, all respondents were given access to the individual results from all other respondents in the form of word documents and Excel files. Finally, a report (deliverable 2.3) containing the documents classified and analyzed to point out deficiencies and needs for extensions, has been realized. We had the need to have a clear picture of existing work in order to: (i) highlight critical situations, (ii) highlight possible reuse of previous experiences. A total of 60 documents and 33 links have been collected; Table 3 shows the method followed for document collection. These documents have been first analyzed according to the following features: Number of level 1 blocks of the BPM; Notes on blocks of level 1 and 2; Level 1 GSBM blocks missing in country model; Level 1 country model blocks missing in GSBPM; Mapping documentation available (Yes/No). Such analysis has been presented in a tabular form for the purpose of summarizing principals features.

5 Table 3. Method for document collection With respect to the IT strategies the following aspects have been analyzed: Principles and aim; Organizational structure; Core component; It component; Model of statistical data production and dissemination process; SIS architecture; Principles of system of statistical tasks; Data sources; IT frameworks main tasks; User profile; Main function of SIS; Data flow; Phases of implementation process; Organizational model of SIS; Schedule of implementation domains; IT renewal; Best practice; Outsourcing; IT management. The principal outcomes of the analysis of these documents are: the lack of a SIS architecture (both IT and Organizational) and the collection of a set of principles that have been taken into account for CORA design. 1.3 WP3: Definition of the Technical Architecture WP3 started on month M2 and ended on month M13.

6 The work done in this WP has led to the definition of a technical architecture based on a layered approach, in which lower layers offer services to upper ones. This approach has the advantage of providing clear contracts between the components at each layer that in this way have precise duties and rights. We started studying GSBMP 4 as a business model describing statistical processes from a methodological point of view. Figure 3 shows the GSBPM structure. Figure 3. GSBPM structure We observed that, as it is, GSBPM model risks to be sterile. Thus, we have defined a technical architecture based on a two dimensional approach that links business model and technical implementation. One dimension, called functional dimension, is formed by the categories of the GSBPM, namely: (i) specify needs; (ii) design; (iii) build; (iv) collect; (v) process; (vi) analyse; (vii) disseminate; (viii) archive; (ix) evaluate. The second dimension, called the construction dimension, is determined by the way services make use of one another to deliver their respective products (data and metadata). Specifically (see Figure 4) the layers are: (i) figures, a domain of interest documented by statistical products; (ii) time series, statistical series over time; (iii) statistic, integrated or simple statistical product for a given time; (iv) population, a population at a given time; (v) unit, a statistical unit at a given time; (vi) variable, a statistical variable at a given time; (vii) representation, a logical representation of the value of a variable. 4 GSBPM:

7 Figure 4. Construction dimension layers In the CORA model the GSBPM sub-processes of Level 2 are described as services delivering a certain functionality within a certain layer as shown in Figure 5. Figure 5. CORA model Being the CORA architecture a non-theoretical model, it was not possible for us to test its correctness in a theoretical way, so we developed proof-of-concept prototypes, both in.net and Java languages, testing empirically the validity and feasibility of the model and its independence from the technology used. Moreover, interfaces between layers have been defined in order to guarantee their cooperation. An instruction manual (deliverable 3.3) has been written to help users to correctly use the model. Finally, the deliverable 3.4, containing both example mappings and software prototypes description, has been produced.

8 1.4 WP4: Design of the Organizational Architecture WP4 started on month M2 and ended on month M13. The title of this WP is Organizational Architecture that normally is thought to be a definition of the objectives and the structure of an organization providing products or services. During the project, however, it became more and more clear that the real objective of this WP was to define the commercial and legal foundations for the exchange of software between NSIs. With the aim of defining suitable licensing models of sharing applications, we made a thorough analysis of the available licensing models, detailing characteristics, obligations of the licensees and correspondences between different licenses. Deliverable 4.1 Commercial and legal Foundations for the Exchange of Software between Statistical Offices contains the results of our analysis on: (i) what open source licenses exist today and how do they fit into the legal environments of Europe and of the particular national legislation, (ii) what about total cost of ownership and related questions, and (iii) where to get help for legal or financial questions. Deliverable 4.2 Requirements Checklist for CORA Tools contains our results about the analysis of the technical and commercial requirements for tools that will be used by the CORA users. These tools have been classified according to functional and non-functional categories. Functional categories are: (i) development of the statistical process, (ii) components for the statistical process, (iii) miscellaneous tools (management, planning,...). Non-functional categories are: (i) price, (ii) support, (iii) running costs, (iv) training costs, (v) tool maturity, (vi) maintenance costs, (vii) reaction times, (viii) lifetime, and others. Deliverable 4.3 Recommendations for CORA tools contains the results of an objective of the WP: collecting information about and setting up a list of tools suited to build a statistics oriented architecture as worked out in WP3. The term build is to be interpreted both in its active and passive meaning: Tools (in the meaning of computer science) to build a system, and tools (in the meaning of statistical tool software) to be used as components of the system to build. Finally, a repository 5 of available tools for each phase of a statistical process has been realized and it is actually managed by the Sharing Advisory Board (SAB) 6. Figure 6 shows the list of tools analyzed and their usage in terms of number of NSIs using them

9 Figure 6. Tools and their usage 1.5 WP5: Project Dissemination WP5 started on month M1 and ended on month M13. Among the dissemination activities, a CORA wiki has been set up by Istat: This wiki is accessible only by the CORA partners, the external observers and Eurostat, being a working area. Figure 7. CORA wiki structure As shown in Figure 7, the wiki has the following general structure: Proposal; Partners Contacts; Discussion on WPs by ; WPs Documents; Discussion; Meetings; Additional documents.

10 Figure 8. OSOR Web Page of the CORA project As a further dissemination channel, a cooperation with the OSOR portal 7 started realizing a web page 8 of the CORA project (as shown in Figure 8) in which people can find a detailed description of the project, the deliverables uploaded under the documentation section and delivered under the Creative Commons Licence. Moreover, a web site 9 of the project has been realized hosted by the OSOR portal to reinforce the cooperation. The web site is structured as follows: Home page in which are described the main objectives of the project, and the CORA partners. The link to the CORA software repository is also part of the home page. Features of the CORA ESSnet. An introduction to the WPs and their milestones. A page with a detailed description for each WP Deliverables released under Common Creative License Meetings References In Figure 9, the home page of the web site is shown. Figure 9. CORA web site Finally, the CORA results have been presented at the following international meetings: ITDG event held on Luxembourg October 2009; Joint UNECE/Eurostat/OECD Meeting on the Management of Statistical Information System (MSIS) held on Daejeon, Republic of Korea, April 2010;

11 ESSnet Workshop held on Stockholm, May 2010; CORA Final Meeting held on Luxembourg, October Achievement of Project Objectives The CORA ESSnet stems from the awareness that a common reference architecture brings several benefits to NSIs, namely: (a) a stronger cooperation among the different NSIs, (b) the sharing of solutions among the different NSIs with considerable benefits in terms of cost reduction, (c) a quality improvement of existing solutions for both business and technical layers of NSIs. Thus, the main objectives of the CORA ESSnet were: (1) the definition of the state of the art with respect to the architectures and the software products currently adopted by European NSIs, (2) the design of a common reference architecture, (3) the definition of the commercial and legal foundations for the exchange of software between NSIs. The first objective has been completely achieved. A state of the art report has been realized starting from the results of a survey made between 42 European NSIs, specifically 27 EU, 3 EFTA, 3 candidate countries, 4 potential candidate countries and 5 other MSIs countries. The second objective has been completely achieved. The CORA architecture designed is articulated in three dimensions: (1) business architecture, (2) technical architecture and (3) organizational architecture (see Figure 10). Figure 10. CORA dimensions

12 The business architecture models statistical processes performed by NSIs and the underlying data life cycle. Starting from the GSBPM standard model 10, CORA identifies a set of logical blocks composing a statistical process and maps them into technical blocks, thus bridging the business and the technical dimension. Being based on blocks (technical and logical), CORA is a flexible architecture that can be easily adapted to future changes that may occur. Organizational rules have been defined for the logical blocks thus bridging the organizational and the business dimensions of CORA. The technical architecture is based on a layered approach in which lower layers offer services to upper ones. With this approach, clear contracts are provided between the components at each layer for which precise duties and rights are defined. The technical architecture is based on a two dimensional approach. The primary dimension, called the construction dimension, is determined by the way services make use of one another to deliver their respective products (data and metadata). The second dimension, called functional dimension, is formed by the categories of the GSBPM. The definition of the technical blocks is independent on existing software solutions so that existing solutions can be reused or new, more appropriate, solutions can be developed. Proofof-concept prototypes have been developed both in.net and Java to demonstrate the independence of the CORA architecture from the underlying architectural solutions adopted. Moreover, these prototypes give a demonstration of the validity and feasibility of the CORA model. The technical blocks specify the technical characteristics that the implementation of such blocks must take into account. Moreover, open source solutions have been considered as principal option for the implementation, but, whenever possible, proprietary solutions have been indicated and compared to the open source ones in terms of general features and appropriateness for specific usages. The organizational architecture has been defined in terms of rules that must be respected when developing shared applications. Such rules include: 1. legal aspects; 2. licensing models for sharing applications, and 3. business models for training, support and development of shared applications, with a specific attention to open source software development models. An analysis of the technical and commercial requirements for tools that will be used by CORA users has been performed achieving the third objective of the project. Finally, a list of available tools for each phase of a statistical process has been realized. The software repository 11 realized is actually managed by SAB 12. Finally, CORA ESSnet fulfilled an important and ambitious objective: people from different countries worked closely together ensuring the achievement of the project s objectives, establishing a common language and sharing knowledge and expertise. 3. Work Completion In the following sections, the objectives achieved are detailed for WP2, WP3 and WP4. WP1 (project management) and WP5 (dissemination) objectives achieved are presented respectively in Section 5 and Section GSBPM:

13 3.1 WP2: Requirements Collection and State of the Art WP2 started on month M1 and ended on month M6. The participant NSIs were: Istat, DST and SSB as co-ordinator. The objectives of this WP were: The definition of the overall set of CORA requirements. They were collected through a questionnaire sent to 47 NSIs; The analysis of the state of the art collecting documents related to the project theme, classifications and analysis of such documents in order to point out deficiencies and needs for extensions. The work has been divided into five tasks: Task 2.1: we have designed a questionnaire in order to collect the overall set of CORA requirements. Task 2.2: we have sent the questionnaire, after approval by the project coordinator, to 42 NSIs composed of 27 EU, 3 EFTA, 3 candidate countries, 4 potential candidate countries and 5 other MSIs countries. We had a response rate of about 79%. Task 2.3, the responses to the questionnaire have been summarised in a Set of requirements report. Task 2.4 we have collected state of the art documents from the NSIs contacted for the questionnaire. Task 2.5 we have classified and analysed these documents in order to point out deficiencies and needs for extension. The result of this has been described in a State of the art analysis report. Three deliverables have been released: Deliverable 2.1: Questionnaire, delivered on month M3; Deliverable 2.2: Set of requirements, delivered on month M6; Deliverable 2.3: State of the art analysis, delivered on month M6. The resources have been used as planned at submission time. 3.2 WP3: Definition of the technical Architecture WP3 started on month M2 and ended on month M13. The participant NSIs were: Istat, DST, SCB, LS, SFSO, SSB, CBS as co-ordinator. The objective of this WP was the definition of a layered architecture with the purpose to support the statistical production process. Each layer has been defined so that it acts as a provider of services to the upper layers and as a consumer of services from the lower layers. The work has been divided into four different tasks: Task 3.1 has defined the different layers of the architecture and has detailed each layer. More specifically starting from the logical view provided by the existing model GSBPM, we have considered the elements necessary to implement the described standard processes and created a consistent model that connects the logical statistical process to the bottom level of the physical infrastructure. Task 3.2: in order to guarantee the cooperation of the different layers, interfaces have been defined. These interfaces have been defined as services. Task 3.3: a manual for a correct use of the model has been written.

14 Task 3.4: The development of proof-of-concept prototypes has been added to WP3 activities because, being the CORA architecture a non-theoretical model we have empirically proved the validity and feasibility of the model. Finally we have shown in task 3.4 the viability of the model by mapping a number of current or foreseen solutions in terms of the model. Four deliverables have been delivered: Deliverable 3.1: Definition of the Layered Common Reference Architecture, delivered on month M10; Deliverable 3.2: Interface descriptions of the layers, delivered on month M10; Deliverable 3.3: Instruction manual, delivered on month M13; Deliverable 3.4: Example mappings of the model and update of software repository, delivered on month M13. With respect to the resources usage, there have been some differences compared to the resources initially planned. In fact a modification to the initial balance have been requested and obtained by Eurostat during month M6. In more details: (a) Istat increased the number of person/months because a different distribution of hours among the people was required, due to the actual work performed. Moreover, a new person has been added to the staff in order to develop the proof-of-concept prototype; (b) SSB added a new person to the staff keeping the same number of person/months but making a different distribution of the hours among the people. The new element of the staff was necessary to address needs of WP3; (c) SCB increased the number of person/months adding a new element to the staff. The new element role was to participate to the assessment of the proposed architecture in WP3 and also to contribute to the proposal about how to make a reference architecture operational with respect to a service-based approach; (d) CBS increased the number of person/month adding a new element to the staff because an extra capacity was needed for building the proof-of-concept prototype. 3.3 WP4: Design of the Organizational Architecture WP4 started on month M2 and ended on month M13. The participant NSIs were: Istat, SFSO as co-ordinator and SSB. The objective of this WP was to provide to all partner countries the means to obtain, to license and to technically maintain/extend the concepts and the software of the Common Reference Architecture. The work has been divided into four different tasks: Task 4.1: we have analysed suitable licensing models for sharing applications. In more details we have explained and discussed the current models of software distribution, i.e. open source models, joint development consortia, ownership limited to executable, free executables etc. Task 4.2: we have analysed business models for the support of shared applications. Task 4.3: we have analysed legal frameworks for the shared development because if the development is done in a shared way, questions of (intellectual / commercial) property and rights to use have to be defined.

15 Task 4.4: we have written guidelines and best practices for design, programming, and testing of shared applications, including tools to be used (e.g., forge like OSOR, IDE like Eclipse, CVS, Subversion, modelling tools like EA etc.). We have also realized a repository 13 of shared tools that is actually managed by SAB 14. Three deliverables have been released: Deliverable 4.1: Models for licensing, support and legal properties, delivered on month M8; Deliverable 4.2: Technical and commercial requirements for tools, delivered on month M8; Deliverable 4.3: Recommendation for tools, delivered on month M12. The resources have been used as planned at submission time. 4. Final Deliverables and Milestones tables Table 1: Deliverables List Del. no. Deliverable name Workpackage no. Date due Actual delivery date Comments 1.1 Preliminary 1 M3 M3 Report 1.2 Intermediate Report 1 M6 M6 1.3 Final Report 1 M12 M13 The ending date of the project has been delayed to month M Cost Report 1 M12 M13 The ending date of the project has been delayed to month M Questionnaire 2 M3 M3 2.2 Set of requirements 2.3 State of the art analysis 3.1 Definition of the Layered Common Reference Architecture 3.2 Interface descriptions of the layers 3.3 Instruction manual 2 M6 M6 2 M6 M6 3 M8 M10 We have requested a deferment to realize the prototype. 3 M8 M10 We have requested a deferment to realize the prototype. 3 M12 M13 We have requested a deferment to realize the prototype

16 3.4 Example mappings of the model and update of software repository 4.1 Models for licensing, support and legal properties 4.2 Technical and commercial requirements for tools 4.3 Recommenda tion for tools 3 M12 M13 We have requested a deferment to realize the prototype. 4 M8 M8 4 M8 M8 4 M12 M12 Table 2: Milestones List Milestone no. Milestone name Workpackage no. 1.1 Kick off 1 M1 M1 1.2 WP leaders 1 M3 M3 meeting 1.3 Intermediate Meeting 1 M6 M6 Date due Actual date Comments 1.4 Final Meeting 1 M10 M13 The ending date of the project has been delayed to 2.1 Requirements and State-of-theart 3.1 Layers and Interface of CORA 2 M6 M6 month M13. 3 M8 M12 We have requested a deferment to realize the prototype. 3.2 Usage of CORA 3 M10 M12 We have requested a deferment to realize the 4.1 Design of Organizational Architecture prototype. 4 M10 M12 The ending date of the project has been delayed to month M13

17 5.1 Final Report 5 M10 M13 The ending date of the project has been delayed to 5.2 Report on dissemination activities 5. Project management month M13. 5 M10 M13 The ending date of the project has been delayed to month M13. Project management was carried on by a dedicated WP, namely WP1. WP1 started on month M1 and ended on month M13. The participant NSIs were: Istat as co-ordinator, DST, SCB, LS, SFSO, SSB and CBS. The main objective of this WP was to ensure the project s proper management and the achievement of its aims, objectives, and deliverables in accordance with its schedule and budget. Moreover, we have also managed the quality and timeliness of all project deliverables. We have organized the work of this WP into two main tasks: Task 1.1: this task has considered all the duties of administrative management. The following meetings have been organised: Kick-off meeting between the CORA beneficiaries and Eurostat. This meeting had the purpose of starting the CORA ESSnet work. It has been held in Luxembourg in month M1. WP Leaders Meeting. This meeting enabled the WPs leaders to check the work state of advancement and to discuss any critical point of the project. It has been held in Amsterdam in month M3. Intermediate meeting between the CORA beneficiaries and Eurostat. This meeting enabled all the CORA partners to discuss on the project state of the art and on the future work. It has been held in Rome in month M6. Final Meeting. During the final meeting the CORA ESSnet results have been presented to Eurostat and to all the others NSIs that have been invited to participate to this workshop. It has been held in Luxembourg in M13. The following reports have been produced: Preliminary Report; Intermediate Report; Final Report. Moreover, we have managed project financial statements. Task 1.2: this task regarded the quality assessment of projects results. The main objective of this task was to monitor and ensure the quality of the outcomes of the project. A quality control and criteria strategy was defined in agreement with all the project partners to establish a process for an expert peer review system. Four deliverables have been released:

18 Deliverable 1.1: Preliminary Report, delivered on month M3; Deliverable 1.2: Intermediate Report, delivered on month M6; Deliverable 1.3: Final Report, delivered on month M13; Deliverable 1.4: Cost Report, delivered on month M13. With respect to the costs minor budget adjustments have been requested to Eurostat due to new requirements emerged during the project. Moreover, travel expenses adjustments have been requested by Istat (Italy) and SSB (Norway), new personnel figures have been requested by CBS (Netherlands) with a budget increased of 17%. Finally, the ending date of the project was firstly postponed from August 7 th to October 7 th and secondly postponed from October 7 th to November 7 th to have the final meeting close to the ITDG meeting so that more countries could participate to the presentation of the project results. Moreover, SSB has converted one of the two Amsterdam trips to a Luxembourg trip respecting the real needs of the project and SSB made minor adjustments to plane, hotel and daily allowance reflecting the real cost supported. The travel to Amsterdam has been cancelled because SCB did not participate to the WPs leader meeting held in Amsterdam on January Being the other direct cost reduced the total amount of the funding is unchanged. 6. Dissemination action towards the ESS The dissemination actions have been carried on by a dedicated WP, namely WP5. WP5 started on month M1 and ended on month M13. The participant NSIs were: Istat as co-ordinator, DST, SCB, LS, SFSO, SSB and CBS. The main objective of this WP was the dissemination activity of the CORA results. We have organized the work of this WP into two main tasks: Task 5.1: this task has ensured the actual dissemination activities. More specifically, it has included the following activities: the set-up of a CORA web site ( hosted by the OSOR project to reinforce the cooperation. the presentation of CORA results at international meetings. In particular: o ITDG event held in Luxembourg on October 2009; o joint UNECE/Eurostat/OECD Meeting on the Management of Statistical Information Systems (MSIS) held in Daejeon, Republic of Korea on April 2010; o final meeting organized as a workshop where all the NSIs (also the ones not participating to the ESSnet) have been invited. This meeting was held in Luxembourg on October Task 5.2: this task considered some activities for producing and sharing project results with other NSIs. In particular: The set-up of a CORA Wiki. This working tool has been used for: (a) internal document exchanges, (b) discussion on specific topics, (c) work organization as todo lists, deadlines,.., (d) collection of meetings presentations and documentation. The wiki has been used both at proposal and project stage.

19 A cooperation with the OSOR portal started realizing a web page 15 of the CORA project in which people can find a detailed description of the project, the deliverables uploaded under the documentation section and delivered under the Creative Commons Licence "Attribution-Share Alike " (available at the Internet site: ), to maximize the dissemination of the ESSnet results. Two deliverables have been released: Deliverable 5.1: ITDG Report, delivered on month M4; Deliverable 5.2: Report on Dissemination activities, delivered on month M13. With respect to the dissemination of CORA results at international meetings, the project has been presented at the ITDG event on October Unlike specified in CORA proposal, this event was held on month M1 so the presentation (deliverable 5.1- ITDG report) contains mainly the objectives of the project and the organization of the work. At the final meeting Antonio Consoli, Eurostat project manager, invited people from other countries to discuss CORA results. Joachim Machado(Portugal) commented that Portugal is very interested in the collaboration for implementing CORA results. Jean-Pierre Grandjean (France) said that CORA results can be interesting, and that is why they also participate to CORE proposal. Sigurosson (Island) found interesting CORA results and very useful for his applications. Czech Republic and Malta also showed their interest. Dieter Sarreither (Germany) said that the work of CORA was interesting because structures very well the IT architecture that should support business process models. 7. Status of the final use of the resources TABLE 4. RESOURCES Work package WP1 WP2 WP3 WP4 WP5 TOTAL per Beneficiary Co-ordinator / Co-partner 1. Istat 2,44 2,84 4,06 2,03 1,62 12,99 2. DST 0,61 1,22 0,92 0,31 3,05 3. SCB 0,96 1,91 0,48 3,35 4. LS 1,86 9,31 0,93 12,10 5. SFSO 6. SSB 0,54 2,14 0,54 0,54 0,27 4,02 7. CBS 0,62 4,96 0,31 5,89 TOTAL 7,02 6,21 21,69 2,57 3,92 41,40 Since Switzerland (SFSO) does not receive any funding for project work, no formal resources have been assigned in the Eurostat mandate hence there is no applicable report. 15