 I'm going to talk about e-research services and capabilities, which is some work we've been doing within a favor working group for a project called advancing the professionalism of our e-research workforce. So I'll just switch. This is what I'm going to talk about. It's largely based on a talk Birds of a Feather session we ran last week at e-research Australasia, but with the updates from the feedback from that session and with the next steps where we're going to take it after this and the input we want from you in the community. So first, just to recap the those that have not seen this before, we'll talk about favor, we'll talk a bit about the context, the e-research value proposition and chain that forms the basis of our work, then we'll more description about the services and capabilities themselves, mainly the services, and then talk about the next steps of capabilities processes and infrastructure. So first, for those that don't know, favor is Federation for the Advancement of Victorian e-research. It's a collaboration of eight Victorian based universities and it's there to promote collaboration around e-research initiatives, services and infrastructure. There are currently three projects, access to infrastructure, how best to engage with digital humanities research and they ran a great showcase the week before last, and this project about professionalization of the e-research workforce. So this work, this project started because we did some previous work at e-research, there you go, I'll talk about the working group. The aim of the working group is with the long name is to create or to clarify the roles within the e-research workforce. Now, recently I've been talking about the e-research professional workforce, but what as David has just shown us that there's an awful lot of volunteers that do this work as well. So should consider that the e-research, the professionals and the volunteers and researchers who actually provide e-research services. So the idea was to clarify the scope and categorization of these roles to list roles and position descriptions and career paths, but that has evolved because we've come to a different understanding after doing some initial work. So we started off, this builds on some work we've done, modeling roles for e-research where we ran a BOF at 2018 and I presented on it. This is where we took almost 200 roles and we categorized them by six broad services. This was a highly subjective work which I said you categorized these roles title by the primary service. And those services were all specifically tech technology independent, so they were supposed to be very broad idea of a e-research service. So the first question though was categorizing those roles over whether they were e-research or not. So this is the graph that came out of it on the left of the knots. And on the right are the role titles which are the blue nodes categorized into groups and then under each of the services which are the yellow nodes, the six services. So this was useful because it showed that those common themes were the purple nodes, that there was commonality in groupings. But what it turned out is it made it clear that it was very subjective and there was no one-to-one correspondence of roles to services. And that meant that really the skill sets were split. So each role had combinations or parts of roles from different services. So we decided to take a different approach for this project. And rather than going bottom up from the roles, we decided to come top down from the services. So the reasoning being that, as you say, services are like an interface delivered to the researchers. So services are delivered through capabilities and skill sets form part of those capabilities. And that's the ongoing discussion within the group and the start of which was to clarify, broaden those descriptions of services at the last week's buff. So why again, just to talk about the context behind that, we use a really brief version definition or description of e-research. So what is it? It's the application of advanced computing and ICT across the research lifecycle. And there's a value proposition for the workshop effectively to help researchers through various ways. The more important thing is what does the service have? Does the service get delivered? So the value chain is about the outputs that you deliver to researchers. So it's by where I said e-research professionals, the e-research workforce in fact. It's about transforming inputs into those outputs that make up the service and that's done through capabilities. And capabilities can be built up from people, processes and infrastructure required to deliver those services. And by people, we don't mean specific individuals, we mean the skills that they use to execute the processes and work on the infrastructure. So that's the basis. So what we were looking at in our project was six main services. And these are the six of the labels that we use, advise, train and promote, develop, deploy and support. So there's no technology, they're not technology specific. And I know the top three are more about engagement with researchers and the bottom three are more about working with the technology. So I'll go through them briefly just to show because we've already shown them in the in the box, but I'll show what the additional information that we've added based on the feedback. So if we look at advice, it's to provide advice on various aspects, solutions, approaches, principles to support different aspects of the research data lifecycle like data lifecycle, computation and grants and ethics applications. But it's also the triage referral of inquiries to other service units. So the red bit there was what the feedback we got that we need to consider also across all these different parts of the research lifecycle. So the second service is train. Obviously, one of the larger ones, develop, organize, deliver training for researchers across various levels of expertise on various aspects, technical processes, technologies, equipment, platforms. And the additional things that the feedback came back with is also identifying that skills transfer is a way of training through resource provision, interactive research projects. Or through as we saw this morning about getting researchers into active technical projects as well. So you can second them or give them. Yeah, to get them in and transfer over technical skills. The other thing was also referral to external training materials and opportunities. So that was trained. The next engagement type one is promote. It's about promote available technologies to services and services to researchers through various ways, but also to promote policies that impact research technologies and research research activities. So those are the three engagement ones on the develop side, provide advice about development, support development of scripts and software by researchers within projects, develop research technology and referral to third party software development services. And the feedback we also was about developing bespoke workflows and pipelines within projects. So not just software, it's developing other things, other artifacts. So on the deploy service. The only extra focus we got was to also remember it's about infrastructure as well as technologies and systems, but deploying infrastructure and various technologies. And this could include commercial off the shelf units, it's things you not necessarily built yourself. It's about ongoing maintenance and support deployed bespoke deployment of technology to platforms. And the final service is to support support key research infrastructure technologies applications and platforms. And the additional one was to provide access and manage allocations for technical research infrastructure. The six services and the refinements and the additions that came up from the verge of a feather session. So what we want to do now is start to look at the capabilities. Obviously we want to get to the skill sets, but how do we get to the skill sets. So what we wanted to do is first look, well, let's look at a way of identifying the capabilities and then identify the associated skill sets with those capabilities. So what is a capability. Really, it's an expression of what the business does or can do. So it's what how it gets that service delivery. So the people process and infrastructure required to transform the inputs to interactivities into outputs within the activities upon which the service delivery depends. So again, the people through their skills the processes and infrastructure. So as an example, example of three from training. So training planning would be a capability. These are split because they have distinct people processes and skills processes and infrastructure. So for instance, planning would include could include requirements, elicitation solution, solution identification requirements. You could be a process surveying. How do you find out from researchers what training is required. The organization would be about program design session plan and you might have an expression of interest process. And you might then need something like event price to actually plan the sessions. And finally delivering training obviously requires different processes and infrastructure and whether it's online, whether it's in person. These days or whether it's yeah, whether it's virtual. So each of those would have different processes and infrastructure and skill sets associated. So really what we're looking for from that is to focus on the processes and infrastructure first to identify those capabilities. So next steps, we are asking that question. What are the processes and infrastructure that support the delivery of those services? We're going to look at that ourselves, but we're also asking for your input. So we inviting you to look at the Google form where it lays out all those definitions and descriptions as context. And then for each service, we ask three questions. What are the processes involved in delivering the service? What is the infrastructure involved? And other comments about the service. Have we missed something? Do you think that there's other other ways? Other things that we missed as aspects of that service. So then so that's what we're asking from the community. There's the project page. So if you want to actually go and find out more information, we will update it as we make progress. Or you can contact me directly as the project lead project champion. And yeah, so please go in and fill out your thoughts on that survey. So that's all I'd like to say at the moment. If you have any questions.