1. ER-flow Purpose of the meeting C. Vuerli Contributions by G. Terstyanszky

2. University of WestminsterUoWUnited Kingdom Magyar Tudomanyos Akademia Szamitastechnikai es Automatizalasi Kutato Intezete MTA-SZTAKIHungary Centre National de la Recherche ScientifiqueCNRSFrance Stichting European Grid InitiativeEGI.euThe Netherlands Academic Medical Center of the University of Amsterdam AMCThe Netherlands Technische Universität DresdenTUDGermany Ludwig-Maximilians-Universität MünchenLMUGermany University College LondonUCLUnited KIngdom Trinity College DublinTCDIreland Istituto Nazionale di AstrofisicaINAFItaly Partners: Technology providers: CNRS, EGI.eu, MTA-SZTAKI, UoW Research Communities: Astro-PhysicsINAF Computational ChemistryLMU + TUD Helio-PhysicsTCD + UCL Life ScienceAMC Duration: September 2012 – August 2014 ER-flow Project

3. Project Aim and Services Aim: To provide a simulation platform for research communities to enable seamless execution of workflows of different workflow systems through workflow interoperability To investigate data interoperability issues in the workflow domain and propose solutions Services: To support the whole workflow lifecycle: editing, uploading, browsing downloading and executing workflows To provide coarse-grained workflow interoperability solution To provide GUIs to manage workflows Key actors: Researchers Workflow engine developers Workflow developers

4. Objective No. 1: To further build a European community of workflow developers and users involving a wide range of research communities which already use workflow systems and which are new to this technology. Objective No. 2: To migrate workflow based scientific applications of the supported research communities to the European Grid Infrastructure through the SHIWA Simulation Platform and to use these applications both for production runs and to promote e-Science workflow solutions for research communities. Objective No. 3: To disseminate the workflow interoperability solution of the SHIWA project among the selected research communities and identify further research communities that need the simulation platform to run their experiments. Objective No. 4: To define requirements of the supported research communities on interoperability of the scientific data in the workflow domain and to identify existing and missing protocols and standards needed to support this interoperability. Objective No. 5: To write a study on the interoperability of the scientific data in the workflow domain, make recommendations on how to achieve data and workflow interoperability with existing protocols and standard, and identify research, development and standardisation issues required to be solved in order to achieve workflow interoperability in data-intensive research. Project Objectives

5. No.descriptionM12M24milestonesWP 01new research communities of SSP 24M2.2/M2.3WP2 02number of researchers using SSP 100250M5.2/M5.3WP5 Objective No. 1: To further build a European community of workflow developers and users involving a wide range of research communities which already use workflow systems and which are new to this technology. Objectives and Indicators Questions: -Which communities are we addressing? -How will we reach 250 users? Which communities will they represent? -Will they workflow developers or researchers with basic IT knowledge?

6. Objective No. 2: To migrate workflow based scientific applications of the supported research communities to the European Grid Infrastructure through the SHIWA Simulation Platform and to use these applications both for production runs and to promote e-Science workflow solutions for research communities. No.descriptionM12M24milestonesWP 03Astro-Physics workflows614M5.2/M5.3WP5 04Computational Chemistry workflows 1020M5.2/M5.3WP5 05Helio-Physics workflows614M5.2/M5.3WP5 06Life Science workflows1020M5.2/M5.3WP5 07number of executed workflows 10003000M5.2/M5.3WP5 Objectives and Indicators Questions: -Do we have these workflows? If we don’t have them how will we identify and find them? Will they non-native or meta-workflows? -Do we have “real” users who will run 3000 times workflows available in the repository?

7. Objective No. 3: To disseminate the workflow interoperability solution of the SHIWA project among the selected research communities and identify further research communities that need the simulation platform to run their experiments. No.descriptionM12M24milestonesWP 08dissemination & training events for supported communities 48M2.2/M2.3WP2 09dissemination & training events for new communities 24M2.2/M2.3WP2 10European dissemination & training events 24M2.2/M2.3WP2 11users of the User Forum200400M2.2/M2.3WP2 12publications on research achievements 48M5.2/M5.3WP5 Objectives and Indicators Questions: -What kind of dissemination and training events will we run? How will identify the dissemination and training events? Who will run these events? -How will we run the User Forum? How will we attract users to the forum?

8. Objective No. 4: To define requirements of the supported research communities on interoperability of the scientific data in the workflow domain and to identify existing and missing protocols and standards needed to support this interoperability. No.descriptionM12M24milestonesWP 13requirements specification for data interoperability 22M3.1/M5.1WP2 WP5 Objectives and Indicators Questions: -What kind of data interoperability issues will we target? -How will we identify these requirements? Who identify these requirements?

9. Objective No. 5: To write a study on the interoperability of the scientific data in the workflow domain, make recommendations on how to achieve data and workflow interoperability with existing protocols and standard, and identify research, development and standardisation issues required to be solved in order to achieve workflow interoperability in data-intensive research. No.descriptionM12M24milestonesWP 14recommendations on data interoperability 01M4.2WP4 15publications on data interoperability 04M4.2WP4 Objectives and Indicators

10. Work Packages and Efforts No.titlem/mWP leader startingending WP1Project Management6UoW0124 WP2Knowledge Transfer29SZTAKI0124 WP3Infrastructure & Technical Support 20UoW0124 WP4Data Interoperability in Workflow Domain 30CNRS0124 WP5Application Support76AMC0124

11. partnerswp1wp2wp3wp4wp5 UoW621123 MTA-SZTAKI8424 CNRS15151 EGI.eu624 AMC3319 partnerswp1wp2wp3wp4wp5 TUD29 LMU48 UCL215 TCD18 INAF3215 Partners and Efforts

12. User Communities and Simulation Platform Research communities supported by the project –Astro-Physics –Computational Chemistry –Helio-Physics –Life Science Further research communities –At least four further research communities will be supported –Candidate communities: Hydrometeorology Seismology –Further communities considered

13. Why the meeting at IAA On September 1 st 2013 ER-flow enters in its second year. We collected six astro applications during the first year –Port on SSP will be completed by the end of the 1 st year of ER-flow (31 August 2013) We committed ourselves to port at least eight new astro applications during the second year

14. Why the meeting at IAA New collected applications should be structured in a way that: –It should be possible for them to identify a number of basic constituting workflows which could be used as building blocks for other applications or meta-workflows –Already existing workflows for them should have been created by using workflow systems other than WS-PGRADE/gUSE

15. Why the meeting at IAA First exchange of ideas with Susana at –EGI User Forum in Munich (March 2012) –SHIWA Summer School in Budapest (July 2012) IAA is in the right position to contribute with: –New applications and possibly workflows built with workflow systems other than WS-PGRADE/gUSE –Its experience gained in workflow-oriented projects like Wf4ever and others IAA contributions to ER-flow of two types: –Scientific (new applications) by researchers –Technological (workflow systems, portals, science gateways, etc.) by workflow developers

16. Objectives Make aware all scientists at IAA of the new opportunities offered by workflows and the related technologies for their everyday activity and meet all those interested to port their applications and (non native WS-PGRADE) workflows on SSP Go in deep on all correlated technological aspects with AMIGA group: –Tight collaboration between ER-flow and the AMIGA group on technological aspects like DCIs, workflow systems, workflows sharing, data sharing, portals, science gateways and federations thereof (STAR net ), etc.