EGI-InSPIRE RI EGI-InSPIRE EGI-InSPIRE RI NA3 – User Community Coordination Activity Review Steve Brewer EGI.eu NA3 – Steve Brewer - EGI-InSPIRE EC Review

EGI-InSPIRE RI Activity Overview This slide will be provided by the PO It will summarise the activity in tables by: –The # partners, # people, # countries –The # PM and #FTE per country It will summarise the activity in graphics by: –The % effort of the activity within the project –The geographical spread across Europe NA3 – Steve Brewer - EGI-InSPIRE EC Review

EGI-InSPIRE RI Objectives DoW states that the NA3 Activity will: integrate the user communities’ current and future use of the infrastructure by: Coordination of effective, responsive support for the EGI user communities (both individual VOs and those represented by VRCs) through the efforts of the national and specialist support units. Coordination of training, documentation and technical requirements from the user communities to improve the EGI user experience and services. Coordination of technical services to support the establishment and management of virtual organisations. (D3.2: users should not be obliged to become experts in the infrastructure itself.) NA3 – Steve Brewer - EGI-InSPIRE EC Review

EGI-InSPIRE RI NA3 Tasks TNA3.1: Activity Management TNA3.2: User & Community Support Team TNA3.3: NGI User Support Teams TNA3.4: Technical Services –training coordination across projects and national teams –application database to support new and existing user communities –basic technical services needed by VOs NA3 – Steve Brewer - EGI-InSPIRE EC Review

EGI-InSPIRE RI Task NA3.1: Activity Management The NA3 activity is managed by the Chief Community Officer (CCO) –The CCO reports to the Project Director for the effective running of these tasks which implement many of the services and functions relating to the User Community Services described in the EGI Blueprint. CCO is member of AMB. The EGI Helpdesk provided by the EGI Operations team is used to route and allocate issues to the various support units through the use of tickets. Committees and meetings used to manage NA3: –User Community Board – monthly telcons and periodic face-to-face meetings –NA3 Task and sub-Task leader meetings – weekly telcons and periodic f2f –RT ticket system used to manage tasks through allocation and prioritisation NA3 – Steve Brewer - EGI-InSPIRE EC Review

EGI-InSPIRE RI Task NA3.2 User & Community Support Team UCS team supports different sized user communities: Proactive support: community engagement Support and nurture Virtual Research Communities In addition to the EGI Helpdesk a Requirements Tracker system has been implemented to capture and process new requirements. –Capture, investigate and analyse new requirements –Requirements processed towards resolution through appropriate channels: NGIs, Partner projects, other WPs within EGI-InSPIRE Reactive support: help tickets and requirement requests EGI Helpdesk, provides a ‘front desk’ for new users, new communities and non-operational issues –requests for changes to the operational tools or deployed middleware, support for setting up new VOs or porting applications to the infrastructure –These requests will be passed to the relevant NGI support teams, teams within EGI.eu and partner projects as required. NA3 – Steve Brewer - EGI-InSPIRE EC Review

EGI-InSPIRE RI Task NA3.3: NGI User Support Teams “NGI teams will provide support relating to dashboards to provide customised views of the resources available to the VOs, and help to establish portals or science gateways.” “Technical experts in the NGIs will be able to provide consultancy to new communities, advice on application porting support and interaction with the application database.” “Trainers for generic grid training and the necessary training resources will be provided through NGI support teams.” (All quotes from the DoW WP3 description, p27.) NA3 – Steve Brewer - EGI-InSPIRE EC Review

EGI-InSPIRE RI Task NA3.4: Technical Services “The training coordination across the different projects and national teams will be facilitated by EGI.eu through a database of registered trainers (across all middleware types) and the advertising of planned training events.” “EGI.eu will also maintain an application database to support new and existing user communities. The application database will provide a registry of all applications that are currently being, or have been ported, to the infrastructure by teams in the NGIs or related projects. Such a resource enables user communities to see if the tools that they require are already available.” “The basic technical services needed by VOs within the infrastructure (e.g. VOMS, VO database, registration, portals, and dashboards, etc.) are coordinated by EGI.eu and delivered through the operations teams and the NGIs.” (All quotes from the DoW WP3 description, p28.) NA3 – Steve Brewer - EGI-InSPIRE EC Review

EGI-InSPIRE RI Summary of work done The work done and results achieved Quality of the results Attainment of the objectives & milestones The issues that arose How they were dealt with The impact of the WP’s work NA3 – Steve Brewer - EGI-InSPIRE EC Review

EGI-InSPIRE RI Work done  results achieved EGI recruitment  UCS team established in Amsterdam NGI contacts established  communication builds with partners VRC model developed  process and MoU template created Tech. services & developers identified  USAG established User Community Board est.  Reqs. Process with TCB Work with HUCs  UCB starts + LSGC VRC Identify new VRCs  extend UCB + new VRCs Requirements Tracker implemented  233 User-related tickets AppDB  Upgraded, 100 new applications added VO services research  wiki with info & services for VOs Training Working Group  Training requirements confirmed Training services development  Training Marketplace launched NA3 – Steve Brewer - EGI-InSPIRE EC Review

EGI-InSPIRE RI Quality of results NA3 – Steve Brewer - EGI-InSPIRE EC Review Virtual Research Community model developed –Accreditation process & MoU template established and road-tested Heavy User Communities – “legacy VRCs” –Life Sciences Grid Community established; WLCG, Astronomy and Astrophysics, Fusion, Earth Sciences in discussion – all in UCB already New VRCs –WeNMR (Structural Biology) (MoU), DARIAH/CLARIN (Arts & Humanities) (Letter of Intent), Hydrometeorology, Requirements Tracker –233 User-related tickets; RT adopted across & beyond project AppDB –A number of upgrades, 100 new applications added; de facto info for NGIs VO services wiki & services offered (NAGIOS SAM – used by 3 VRCs/VOs) & Dashboard for VOs in final testing Training Marketplace launched –with new features & legacy data from Digital Library and calendar

EGI-InSPIRE RI Attainment of objectives and milestones Objectives: Coordination of effective, responsive support for the EGI user communities through the efforts of the national and specialist support units. –Process in place for Support, Requirements and communication Coordination of training, documentation and technical requirements from the user communities to improve the EGI user experience and services. –Technical services in place and have all been through a number of iterations of improvement Coordination of technical services to support the establishment and management of virtual organisations. –Detailed investigation of available resources documented and new services identified to cover omissions Milestones and Deliverables – all submitted: D3.1 - User community Support Process (PM3) D3.2 - Annual Report on EGI’s User Community Support Process (PM11) MS301 – User support contacts (PM1) MS302 – Training Website (PM2) MS303 – Ported Applications Website (PM2) MS304 – User Support Metrics (PM3) MS305 – User feedback and recommendations (PM6) NA3 – Steve Brewer - EGI-InSPIRE EC Review

EGI-InSPIRE RI Issues that arose NA3 – Steve Brewer - EGI-InSPIRE EC Review

EGI-InSPIRE RI Resolution of issues NA3 – Steve Brewer - EGI-InSPIRE EC Review

EGI-InSPIRE RI Impact of WP’s work New VRCs including many in the pipeline Support Services (used by NGIs and VRCs) Requirements identified (233 User- related) User Forum – sessions and booth Technical Forum presence NA3 – Steve Brewer - EGI-InSPIRE EC Review

EGI-InSPIRE RI Use of Resources No major deviation from the plan NA3 – Steve Brewer - EGI-InSPIRE EC Review

EGI-InSPIRE RI Plans for next year TNA3.1: Activity Management TNA3.2: User & Community Support Team TNA3.3: NGI User Support Teams TNA3.4: Technical Services NA3 – Steve Brewer - EGI-InSPIRE EC Review

EGI-InSPIRE RI Plans for next year: NA3.2 UCB meetings with increased frequency –Monthly to generate more interaction Identify more VRCs –Through NGIs and attendance at events Series of Workshops planned –Themes taken form requirements analysis NA3 – Steve Brewer - EGI-InSPIRE EC Review

EGI-InSPIRE RI Plans for next year: NA3.3 The overarching goal for PY2 is to make the output of these developments visible to NGIs. The Application Database, the Requirement Tracking system together with the recently restructured User Support Webpage and the recently established EGI blog will be important tools in achieving this EGI-InSPIRE INFSO-RI © Members of EGI- InSPIRE collaboration PUBLIC 29 / 33 goal. Monitoring the usage of these sites is therefore a key to later evaluate the success of the promotion activity. The ‘NGI road showmodel will also help EGI to promote NGIs’ services and to inform NGIs about the tools that exist for them. –HealthGrid conference in UK early prototype –DCI Summer School in Hungary NA3 – Steve Brewer - EGI-InSPIRE EC Review

EGI-InSPIRE RI Plans for next year: NA3.4 Facilitate the extension of technical tools –towards customisable services that can be embedded into NGI and VRC portals (Relates to strategy point 10): –The “gadget” functionality that has been piloted by the AppDB developer group to browse applications will be reused in the Training Marketplace and will be extended with wrote mode in order to allow richer functionalities to be delivered to VRC and NGI portals. (e.g. in the form of an AppDB write gadget) NA3 – Steve Brewer - EGI-InSPIRE EC Review

EGI-InSPIRE RI Summary Build on communication –With NGIs & ever growing number of VRCs Develop technical Services as gadgets Workshops –Based on emerging Requirement themes User & Technical Forums –meet User Community representatives (especially Application Developers) Outreach: events NA3 – Steve Brewer - EGI-InSPIRE EC Review