EGI Virtual teams
|EGI Activity groups||Special Interest groups||Policy groups||Virtual teams||Distributed Competence Centres|
|EGI Virtual teams:||Main •||Active Projects •||Closed Projects •||Guidelines|
This page provides information about the Virtual Teams and the NGI International Liaisons of EGI.
- For currently active and already finished projects, please see list of Virtual Team Projects
In 2011 the EGI community revised its user engagement activities and defined a new structure for them to improve efficiency and agility for the community in this area. A new structure has two key elements:
- Virtual Team framework: The Virtual Team framework (see source document) enables NGI and EGI.eu staff to initiate and participate in short-lived projects (also known as Virtual Team projects) that focus on activities that are relevant to the uptake and use of the production infrastructure. Virtual Teams can cover areas such as Marketing & Communication; Strategic Planning and Policy Support; Community outreach and events for new users; Technical outreach and support to new communities. Virtual Team projects typically focus around new communities and/or sustainability. The framework allows the EGI community to plan all related activities in conjunction and collaboration with the NGIs and can help integrate and align effort from multiple projects and countries. The VT project framework is open to all NGIs, countries and regions that are involved or collaborate with EGI. These entities can join existing Virtual Teams and can propose new Virtual Teams.
- NGI International Liaisons: The interaction between the NGIs and EGI.eu on non-operational activities is undertaken through an "NGI International Liaisons"(NILs in short). NILs are responsible within the NGIs for the delivery and interaction of non-operational tasks. Non-operational activities cover areas such as Marketing & Communication; Strategic Planning and Policy Support; Community outreach and events for new users; Technical outreach and support to new communities. The role of the NGI International Liaison recognises the complexity and diversity of each NGIs yet the need for these NGIs to be involved in pan-European, coordinated, non-technical activities of EGI, primarily through Virtual Teams. It is not necessarily the NGI International Liaison who undertake any of the non-technical activities, but instead they make sure the appropriate individuals or teams within the NGIs respond to any particular activity or issue that arises. These activities and issues arise within the Virtual Team framework, typically as requests to join a new Virtual Team or to react to some issue identified by a Virtual Team.
What is a Virtual Team?
The skills needed for EGI to successfully engage as a community with new users exist in many different organisations in the EGI ecosystem. It is foreseen that different members of EGI want to participate in different types of targeted activities that directly or indirectly relate to engagement with new users. The individuals needed to carry out such a targeted activity can be brought together by a Virtual Team in EGI. Virtual Teams provide a flexible and dynamic means to rapidly bring together certain members of the community for a well defined series of tasks to meet a specific goal that needs to be achieved in a relatively short period of time (up to 18 months) before being disbanded. The focus of these Virtual Teams will be to either directly increase the number of EGI users (e.g. through integrating a new application) or indirectly (e.g. by raising the profile of EGI through a hosted event; Performing a study/analysis of a specific area). Virtual Teams have members from multiple NGIs and carry out a targeted action within the following activity domains:
- Marketing & Communication
- Strategic Planning and Policy Support
- Community outreach and events for new users
- Technical outreach and support to new communities (incl. studies, specifications, developments)
Virtual Teams can be established and used to enable the development of a strategy for the long-term evolution of EGI, or to significantly increase both the diversity and quantity of users and communities exploiting the infrastructure for world class research. The application of the framework is limited only by the scope and imagination of the NGIs to commit resources to any particular goal.
Who are the NGI International Liaisons?
EGI members (NGIs and EIROs) as well as partner counteis delegate International Liaisons to EGI. These International Laisions (NILs) have a key networking role in the EGI community. NILs work together with teams in EGI Foundation and with each other to link non-operational activities from their own country/institute with the rest of the EGI community. One of the most important of these non-operational activities is Engagement with new communities. With the NIL acting as a spearhead, each country (or EIRO) is able to connect its non-operational activities to the European landscape to facilitate services for new communities together, and to demonstrate the added value of the country to new communities and to other NGIs.
EGI forms and implements its Engagement Strategy within the NGIs through the NILs, because NILs connect the following activities from the national level to the European level:
- Marketing and communication
- Proactive outreach and support for new communities
The NIL role and about their coordination within EGI
- The NILs are subscribed to the <firstname.lastname@example.org> email list which is used for coordination and discussion of activities. List archive is available at https://mailman.egi.eu/mailman/private/ngi-international-liaisons/.
- The NILs are involved in the development and implementation of EGI's Engagement Strategy (http://go.egi.eu/engagementstrategy), ie. reaching out to new communities, collecting and analysing their requirements, setting up support for them.
- Abstract of the EGI Engagement Strategy document: EGI Engagement reaches out to scientific communities, to national initiatives, to the long tail of science as well as to SMEs and industry and supports them in tackling scientific challenges using reliable and innovative ICT services and solutions. The Engagement Strategy coordinates EGI members’ activities to accomplish this complex mission, ultimately contributing to the European effort of building a sustainable digital e-infrastructure ecosystem for research. The Engagement Strategy document describes the specific goals of the EGI engagement activity, details the various tasks that this activity involves, provides information about the human networks and online resources and tools that help the community implement this strategy, as well as provides an action plan for the upcoming months.
- Regular teleconferences are organised for the NILs (typically once a month). These are titled 'Engagement meetings'. Future and past events are available at https://indico.egi.eu/indico/categoryDisplay.py?categId=36.
- Face-to-face meetings are organised twice per year for the NILs. These meetings are co-located with the main EGI Forums/Conferences (one in the spring and one in the autumn).
- NILs are participating in the creation and implementation of short, focussed projects, called Virtual Teams (Further information: https://wiki.egi.eu/wiki/EGI_Virtual_teams).
- The NIL activity is coordinated by the Technical Outreach Manager of EGI.eu, Gergely Sipos (email@example.com).
Resources for the NILs - To be successful in reaching out and supporting new communities
- EGI Engagement Strategy: http://go.egi.eu/engagementstrategy
- Repository of communication and marketing materials and templates: http://www.egi.eu/news-and-media/publications/
- Registry of upcoming events that can be relevant for EGI members to attend and promote EGI (with planned contributions from EGI): https://wiki.egi.eu/wiki/Community_events
- To see an up-to-date picture of the support cases that are currently in the Engagement workflow, please go to http://go.egi.eu/technicalsupportcases. (An RT queue with public access)
- How to capture details of a new engagement case that should be followed up in EGI:
- Capture the case in the technical-support-cases RT queue, as described in this document: https://documents.egi.eu/document/2478 OR
- Report back during the regular (monthly) Engagement board teleconferences OR Send details in email to firstname.lastname@example.org
- Email lists:
- NILs: email@example.com
- UCB: UCBfirstname.lastname@example.org
- Leaders of EGI-Engage Competence Centres: email@example.com
- NIL table: http://www.egi.eu/community/ngis/NILs.html
- Requirements Tracking: The evolution of the European Grid Infrastructure is driven by the users. Therefore capturing and following up feedback from users reached during Engagement is a key goal for all the three phases of the Engagement activity.
- Capture the support cases in tickets: http://go.egi.eu/technicalsupportcases. If no ticket exists for the case (i.e. community/project), then register it. For further information please refer to https://documents.egi.eu/document/2478.
- To gather requirements from EGI user communities in a systematic way, a standard template has been designed. The template and captured requirements are available at https://wiki.egi.eu/wiki/Communties_Requirements.
- Templates for Virtual Team projects:
List of NILs
Name, Country, Institute, Email:
- Hrachya Astsatryan Armenia IIAP NAS RA firstname.lastname@example.org
- Antun Balaz Republic of Serbia IPB email@example.com
- Yossi Baruch Israel IUCC firstname.lastname@example.org
- Petru Bogatencov Moldova RENAM email@example.com
- Peter Bogatencov Moldova RENAM firstname.lastname@example.org
- Jan Bot Netherlands SURFsara BV email@example.com
- Isabel Campos Plasencia Spain CSIC firstname.lastname@example.org
- Alessandro Costantini Italy INFN email@example.com
- Claire Devereux UK STFC firstname.lastname@example.org
- Marios Dikaiakos Cyprus UCY email@example.com
- Dobriša Dobrenić Croatia SRCE firstname.lastname@example.org
- Feyza Eryol Turkey TUBITAK email@example.com
- Dean Flanders Switzerland SwiNG firstname.lastname@example.org
- Luciano Gaido Italy INFN email@example.com
- Nugzar Gamtsemlidze Georgia GRENA firstname.lastname@example.org
- Andrii Golovynskyi Ukraine V. Glushkov Institute of Cybernetics NAS of Ukraine email@example.com
- Todor Gurov Bulgaria IICT-BAS firstname.lastname@example.org
- Ladislav Hluchý Slovakia IISAS email@example.com
- Vicky Huang Taiwan AS firstname.lastname@example.org
- Soonwook Hwang South Korea KISTI email@example.com
- Nicolai Moldova RENAM firstname.lastname@example.org
- Nicolai ILIUHA Moldova RENAM email@example.com
- Emir Imamagic Croatia SRCE firstname.lastname@example.org
- Boro Jakimovski Macedonia UKIM email@example.com
- Jan Jona Javorsek Slovenia JSI firstname.lastname@example.org
- Bob Jones (CERN) CERN email@example.com
- Jik-Soo Kim South Korea KISTI firstname.lastname@example.org
- Aneta Karaivanova Bulgaria IICT-BAS email@example.com
- Kostas Koumantaros Greece GRNET firstname.lastname@example.org
- Ivana Křenková Czech Republic CESNET email@example.com
- Ramaz Kvatadze Georgia GRENA firstname.lastname@example.org
- Simon C. Lin Taiwan AS email@example.com
- Robert Lovas Hungary MTA SZTAKI firstname.lastname@example.org
- Dana Ludviga Latvia IMCS-UL email@example.com
- Jesus Marco de Lucas Spain CSIC firstname.lastname@example.org
- Luděk Matyska Czech Republic CESNET email@example.com
- Steven Newhouse (EMBL-EBI) EMBL firstname.lastname@example.org
- Nicolin Alexandru Romania Horia Hulubei National Institute for Physics and Nuclear Engineering email@example.com
- João António Tomásio Pina Portugal LIP firstname.lastname@example.org
- Tomasz Piontek Poland ICBP email@example.com
- Maria Poveda Cyprus UCY firstname.lastname@example.org
- Genevieve Romier France CNRS email@example.com
- Serge A. Salamanka Belorus UIIP NASB firstname.lastname@example.org
- Jamie Shiers N.A. (CERN) CERN email@example.com
- Mariusz Sterzel Poland CYFRONET firstname.lastname@example.org
- Jelena Tamuliene Lithuania VU email@example.com
- Jura Tarus Finland CSC firstname.lastname@example.org
- Onur Temizsoylu Turkey TUBITAK email@example.com
- Leo Trukšāns Latvia IMCS-UL firstname.lastname@example.org
- Rosette Vandenbroucke Belgium BEgrid email@example.com
- Martin Laimonis Veicherts Denmark UCPH firstname.lastname@example.org
- Bart Verleye Belgium Vrije Universiteit Brussel email@example.com
- Ilyin Viacheslav Russia E-ARENA firstname.lastname@example.org
- Ilyin Viacheslav Russia SINP MSU email@example.com
- Korenkov Vladimir Russia JINR firstname.lastname@example.org
- Dusan Vudragovic Republic of Serbia IPB email@example.com
- Anders Waananen Denmark UCPH firstname.lastname@example.org
- Zivan Yoash Israel IUCC email@example.com
- Sergio Maffioletti Switzerland UZH firstname.lastname@example.org