 And at the end, we can take further questions and I say further questions because if you think of any questions as we go through the presentation, as Dan says, please enter them into the chat box and we'll pick them up as and when is appropriate. Can we move on to the next slide, please, then? You probably are well aware of it. The open networks project is a major project for the electricity supply industry and it is helping the country deliver net zero carbon. And as I say, the electricity industry has got a very large part to play in this by delivering a smart flexible energy system. Workstream one, if we take one a and one be together and looking at me, the processes and the data that is required to deliver this smart flexible network. Working one a really is looking at more the commercial side of flexibility. We'll hear today so about one be a one be is really about with technical elements that network companies need to develop in order to deliver a smart system and a whole system. It's not distribution and transmission separately. It's the whole system development. So that is the objective of working one be to put in place processes and data exchange between network companies and primarily between transmission and distribution. But also between distribution companies themselves and ID and those and distribution companies. So, as I say, there are five sub products, but as we've seen, that's the way we're going to run through them this morning. And so the focus is on transmission to distribution processes for others as well to support that. And so we'll move on to the, I'll hand over now to to to John and move on to the next slide where John's going to start to talk to you prox two and five. Okay, good morning, everybody. It's John West here. I'm happy for a few years now supporting the the open networks project. This year I'm I'm sort of quite steeped in in the work stream one be and also do a bit of work on work stream to which is more about connection processes and customer information. But less about me more about work stream one be we thought we would start with products to and product five product to picks up the feature energy scenarios and product five is about how we go about identifying network companies go about identifying capacity limitations. So these two products are quite closely linked and we think it's probably good to think about them both together so that we can we can be sort of quite clear about where one product sort of starts and the other. And then and where the other product ends. So the little diagram on the slide at the moment just sort of illustrates at a high level what product to and product five are so. Product two on on on the left hand side it it's about future energy scenarios. It's it considers what those scenarios should be. You know, typically the scenarios that are developed for the. National grid published fares, you know, things like steady progression. It then goes on to think about well within those scenarios which should be the specific forecasts of various elements like. Local technologies or distributed generation different different types of. And then the other part of the scenario. The best part of it is to take those those forecasts of the different elements and turn them into an electricity forecast, which means thinking about well okay. At. At what times or or. Those digger elements likely to be active and how much energy are they likely to require how much electricity are likely to require. So. That's what's in in product to. In product five, then we we take those those forecasts those scenarios and start to sort of apply them to the the actual physical. Networks and start to work out where there may be limitations or constraints going forward. So the. The two blocks on the right hand side, those evaluate network capacity and constraints. And then what product five is also trying to do as well as working out or agreeing ways of identifying those constraints is, is, is putting in place the. Reporting that network companies will use going forward to to. Publish where those constraints are and what those limitations are. So, that's a sort of introduction to product two and product five. We've now got a few slides, which will go into that in a bit more detail. I can see we've got 1. 1 question that's come up from from Graham. In respect of whole system. So, Graham is, is, is, is asking, please reassure me that it, that this is right. From the generator terminals to the end user hence generator losses. Or a relevant consideration. I think that's that's a good definition of whole system. I think what we're doing in. Workstream 1 B is, is much more focused on the networks part of that and, and particularly the, the distribution to. Transmission interfaces and trying to make sure that the data exchange elements, the. Processes there are effective or. That part of the whole system operation. So. I think I agree. With your definition of whole system, but I think work stream 1 B. Is, is more focused into the, the T D elements of that. So, could we go to the next slide, please. Okay. So, the next slide just, just picks up a little bit on whole system future energy scenarios. So, this is an area that is. Starting to mature, I think, I mean, obviously, the national grid ESO has been publishing future scenarios for many years now, and it's, it's got a, you know, a very mature sort of annual process, which. Is, is well established and full of state building engagement. Over the last, probably 2 to 3 years distribution companies have started to, to publish future energy scenarios as well. And, you know, you can see some. Pictures are, which, which illustrate their recent 1. So, we've got a, we've got a sort of process, which is starting to mature around the production of future energy scenario documents. What we have in this particular product is, is really. Trying to, to, to build on that and, and, and probably. In, in 2020, the, the. Big areas of focus have been across the distribution. Future energy scenarios and trying to work out how we get. Greater consistency of approach really across those scenarios and. We will come a bit more to that on the slide. But also the, the, the 2nd part is, is sort of working out how. Those distribution. Energy scenarios are produced alongside the, the scenarios and making sure that. There's good consistency there. There's, there's good exchange of information so that they. The distribution scenarios can learn from the first scenario, the TV scenarios and vice versa. There becomes a good sort of flow of information really between. Distribution companies and the national grid so to make all of that happen well. So, it's it's those 2 things that we've been really focusing on this year. Which are, which are done there really is elements 1 and element 2. Developing the more consistent defes is. And improving data exchange so that we get better. There's an anti-fes I should say. I use the term sort of building blocks there. And building blocks are really just the, the different elements of the forecast. This is for the language that we started to use. So it's, it might be a type of generator or, or an amount of each charging or. Some other on the metal component, which goes to make up the, the electricity forecast. And it just gives us a language or a set of things that we can use and start to compare across scenarios in an easier way. The third element there is, is just one that we have on our radar. We're always conscious of the fact that we may need to put in place some code obligations or some license changes to, to try and make these things more permanent going forward. As yet in this sort of area, we haven't seen a need to do this, but we've got our sort of mind open to that. Let's move to the next slide please. So this slide just picks up on, on the distribution phase standardization. And what you can see there is a set of blocks on the, the left hand side. So on, on, on this product, whole system players, as with all of the other products that were streamed one day, there is each of the products has a, has a team, which is sort of sourced from the network company. So in this particular case, it will have representatives from each of the DNOs, also from the TO companies and from the National Grid ESL. And each team is, is, has got a product lead. So in the case of product two, it's a guy called Hadi Kazani who works with SS EN. And Hadi and the team have, have approached product two by sort of this, this part of it by breaking the, the task into those sort of five blocks on the left hand side. So what they've done really to date, they've made pretty good progress really with, with DFS standardization. So they've got a high level framework agreed, which is essentially the, how the scenarios are used, how regional aspects are built in, how the forecasts are done and, and right through to, to publication. They've got a process agreed for beef as standardization, which is, is to some extent about how the beef as sort of interacts with the, the GB phase and how sort of feedback between the two work. The third block there, they've identified the elements that are subject to standardization, which, which is important in terms of getting consistency between the DFS and to some extent with the GB phase. And the fourth block there then is, is that agreed timeline and process for how the DFS is, and this is sort of interact. And you can see the timeline along the bottom, you know, we've got a, essentially, if you go to the middle, you'll see the, the GB phase is published about July of each year. And the plan will be going forward that distribution phase is published around about sort of November, December of each year. So there'll be a sort of five or six month gap between the two. And this will allow a bit of feedback, I guess, really are learning to come from the GB phase into the DFS and then from the DFS is after they're published into the GB phase. And you can see to support that process. There's a couple of touch points which have been agreed around about sort of December and February time where there will be quite a high level of sort of interaction between the ESO and the B&M to make sure that the right sort of things are being projected into the GB phase and DFS going forward to make it work. So there's a timeline that has been agreed to which the never companies will work to going forward. And then the final bit of the final of the five blocks is just thinking about, well, okay, if we do start to see differences between, let's say a regional forecast of something and how that forecast is working in the national GB phase scenarios, we've got a bit of a process developed as to how that gets narrowed down, how the never companies understand that and start to make decisions about whether particular models or sub models that might have in the phase processes need to be updated or changed or made more consistent. So there's a process which tries to keep the GB phase, the DFS is reasonably consistent and tries to make sure that the elements that make up those things get adjusted if they need to be adjusted. So that's product two, DFS. I wasn't going to say anything further on product two but move on to product five now. So if anyone does have any questions on product two just pop them up. So product five then sort of moves on to the right hand side of that earlier slide and thinks about how do capacity shortfalls get identified by never companies and reported. So this is quite a wordy slide I should say this this particular product is led by Jill Williamson who works with electricity northwest limited. And again Jill has a product team that is working on this. So the three objectives that Jill and the team have identified is is to first of all to identify a more consistent or common system of evaluating network capacity which is objective A. And then objective B is sort of putting in place a standard report for our capacity shortfalls or limitations are made known. And objective C then is is once and being done putting in place some monitoring really to to to to understand how that's been done and make sure it's been done in a consistent way and obviously learning from it. So the the just below that that little objective ABC block. There's a there's a little bit on on the there what Jill and the team did in in the early part of the year which was to prepare a report on what network operators are currently doing in the reporting that they do for for network capacity and a report was published on to the open networks were extreme one be sort of web pages back in May. Which goes into some detail on the existing capacity reports that are published by network companies. And I think it showed that there's a lot of different reports but there is a third degree of consistency already in place, particularly where reports are mandated. And it also I think was helpful in it. It showed that you could start to characterize reports in different ways by sort of what parts of the network they cover. What dates cover what scenarios they use that sort of thing and by and large all of all of these reports, you know, there's good reasons for having them that can develop to do particular things. So that that report. Published in May provides a, you know, a bit of a base or Jill and the team to work on. So I think we've got another slide on product five, but I think we've got a couple of comments or questions that have come in, which I'll just pick up on. And Dan will keep you right if I miss any of these hopefully. So, Graham again. GB says, first, what they did your decision to make this top down to be fairs rather than the other way Ryan. Okay. Great points. I. And apologies if it if it sounded like it was top time. I think we, as you might imagine, there was a lot of discussion about this, whether it was top down or or bottom up. And I think we probably ended up in a place where it's a bit of both really the it's meant to be. Top on in the sense of all recognizing that perhaps having the, the four scenarios which are being developed for DB is, is quite a good thing to have in in the, in the defense situation as well so that you can start to make some direct comparisons. But bottom up in recognizing that some of the, the interfacing really between. Distribution companies and let's say local authorities. As an example, we'll probably get much closer to the reality of what's happening in in regionally and therefore it's it's good to. Allow that sort of of understanding to be built into the regional scenarios and find a way of sort of feeding that back up into the. DB scenarios. So that's that's what we're we're trying to do. So I again. I think I would emphasize it. It's not intended to be top down. It's intended to be sort of both ways or a two way flow of information. There's a question from a mirror. Would there be any coordination between the fairs and fairs frameworks, for example, as has introduced you different access with defers adapt any futures changes in this framework. I think that's that's a quick answer. That's that's yes. We're trying to keep the. Consistency or scenarios the same cross and defers. And. So, so, therefore, the, the 4 scenarios, for example, in, in the DB, as we would expect to see in the defense going forward, but that doesn't preclude the defense, let's say. In a particular area. Saying, well, yes, we need we need to produce a further scenario here because there is something that is is more important locally that we need to bring up. So, there's a another question here from Matthew. Age. Objective a what is the capacity need across TD boundary won't be the same as embedded demand generation. What figure for TV TD capacity is decided and how. And how recorded as as formal rights, no tech. For D and O interface currently. Transition from grid podcasting to formula, so specific actually needed. I think that there's there's a lot of. A lot of detail there, which, which I probably sort of can't go into here other than to say. I think the. Identifying network. Capacity needs. Well, probably probably be better done when we go on to the next slide, maybe, maybe do that and you'll get a better sense of it, but it's, it's. Trying to to really work out. Consistency of high profiling is done that sort of thing across network companies. So, so maybe, maybe come back to that after the next slide. Could we go to the next slide please? Yeah. Okay. So. This is what Jill and the team of are currently working on really as a standard report. So they're referring to it as a standard network capacity reports. It's a strong man on the left hand side. You can you can start to see what what the. Report is trying to do. So for the first 10 years. It might be it might show a set of capacity requirements, which it does for every year sort of 1, 2, 3, 4, 5, 6, 7, 8, 9, 10. And it'll base those on some sort of central forecaster scenario. And then for moving across, then maybe, you know, after the first 10 years, let's say 2030 2035 2040 right out to 2050. It'll produce some information for all of the details scenarios. It'll do that. And there's been a fair bit of discussion about, you know, is this. Just really what does it consider so it's looking at demand. And generation capacity so trying to to identify. Capacity network capacity issues both for generation and demand. And there will be a focus on both. Thermal loading and fault level, but probably not going too much into the detail of. Of voltage at this stage so. Recognizing that it's it's probably going to be a fairly high level before focusing on thermal on fault level. And then in terms of coverage. Focusing on bulk supply points and primary substations with some sort of tabular format used. So. That's what the team is considering at the moment and there's a report in draft, which. Price to capture all of that and what the team will be discussing that. In a bit more detail over the next few meetings of the next month or so before producing a report in in October. So. That's what. The product five team are doing at the moment I should say the other aspect of this really is is there is a lot of overlap with some of the work that does and often are doing at the moment on the. Clean energy package and some of you may be aware of the proposed network development plan. I think there's a lot of overlap or synergy really here between what the standard network capacity report might be and what the. Network development plan report or requirement that that is likely to be placed on network companies going forward will be so we see. Perhaps would potentially this this report sort of filling that need going forward in consistent way. So. That's product five. Can we move on to. Before we do John, there's there's a final question from Charlotte and asking is network capacity also to be broadly aligned for each scenario and specifically around the team and the interface. Do you want to pick that up? Yes, I will try to I think again, I think, but that's probably 1 we need to think about a little bit more in the product team. As part of the detail and 1 to take back, but yes, certainly that that idea of alignment is there that idea of scenarios is there. And that so I think the simple answer is yes, but I think yeah, we probably need to do a bit more detail and exactly how that will look. Okay. Right, I shall pick up product 4, which is looking at data exchange in planning time scales. And at the moment, the, the, the data exchange requirements between T and D are enshrined in the grid code. And they have been relatively unchanged for many years and it's new that they don't really provide enough data exchange to allow us to develop an efficient network as we as we move into this brave new world of smart flexible network. So, product 4, look to look at that data exchange and build on that to say what what actually do we need to do to make sure that we can plan more efficiently with some of the major issues in front of both transmission and distribution companies going forward. So, the 2020 work for this product is really building and carrying forward the work and the 2019 work. What they did in 2019 was to provide a report that said, well, this is the, this is the enhanced requirement for data exchange. Both on distribution companies and on transmission. And, and reports were produced by that by the product and published in January of this year. I say reports, what one of the reports was to detail the enhanced data exchange requirements. The other report was to look at how you would do that. It's fair to say that the enhanced planning data exchange is is quite is exchanging a significantly more amount of data than is currently done. Probably the data is exchanged by exchange of Excel workbooks, which contain all the data to provide models of the network. But the enhanced enhanced data exchange requirements would mean that this will be extremely resource intensive exercise. So, the second report was published in January looked at ways that we could do this, this data exchange in an electronic fashion. By, I think it recommended the, the use of the common information model and to exchange the data as set of models that represent certain, certain demand and generation profiles. I'll come on to that in more detail on the next slide. Well, basically, those reports were done just in January of this year. And the work of this year has been to get those, those proposals or recommendations enshrined into various codes. So I'm leading a green code modification GC 0139, which looks to introduce the enhanced requirement for data exchange and is also considering how we would do that data exchange. So it's looking at how you would mandate an electronic data exchange as well as the new enhanced level of data exchange. But there is a knock on effect than that. Some of the data that the DNOs need to provide to the national grid is not nowadays all in their own gift. A lot of it is held by third parties, whether they, you know, the DNOs on the like, who have a lot of generation connected to their network, which is vital that we understand both from the planning and distribution network, but also planning them the transmission system. So what we identified last year's work was there was a need to strengthen the distribution code requirements to mandate an annual exchange of data, which will feed into the distribution network planning, but also into the green code data exchange. So for that, I'm leading a working group on a distribution code modification. And you can see the number you need title there with DC, RP, MP slash 20 slash oh four. When you get these slides, you'll find that those are links that will take you to the website that will give you far more detail on those modification proposals and intend to go through at this point. Are there any questions here at this point? P5 shows a thermal and fault level capacity. What was the reasoning not also to show voltage limitations? We're getting a bit of feedback somewhere, but I'll just pick that up. So it's a further question on P5. Yeah, as we were talking about the scope of that report. We stuck with thermal and fault level for the moment, recognizing that, you know, there'll be a huge volume really for DNOs with bulk supply points and primaries. And one thing I suppose to learn to walk before we can run, but it was felt that these are, you know, thermal fault level are probably the key ones. It would be good to show voltage, but that might be, I think that's probably a step too far at this stage that might be something that can get added in later. Really, I think it's a transfer to that. If we can move on to the next slide. Which is continuation and talking about product for this really just details the proposed enhancements to the data exchange requirements. We'll be looking at the left hand box first, which details transmission to distribution data exchange. Presently, the data is exchanged at week 42, where national green ESO provide DNOs with models or models. Depending on which company it is that represent a maximum demand maximum fault panel scenario. So what we're proposing going forward is that grid will provide probably different points in the year, not just week 42. And you understand that this is ongoing work at the moment. It's felt that they provide some of this data all in one go with one meter data being out of date. But also would lead to a large amount of work for people all at one time and not spend the work throughout the year. So I think we're heading towards national grid providing DNOs data throughout the year. And that would come as a single switch level model that represents the following scenarios and demand and generation dispatch. And so we'd have a model that represents and this is in addition to the maximum fault level scenario. We would have a model that represents the transmission system at the time of national peak at the time of summer minimum. At the time of solar peak and GSP minimum demand. And then there would then be a further two models that would represent a high power flow north to south and a low power flow scenario on the transmission system. On the distribution system or distributions transmission data exchange on the right hand side. At the moment, we provide data at both week 42 and week 50. And that's both structural system data presented in the former and one of spreadsheets again. The proposal is really to align the system data and requirements with the statement of works requirements. And so that will include full details of the sun transmission network and any connections directly to that sun transmission network. Whether those connections be to a dno or an idea no owned piece of network. So you can see here we're touching on again the requirement for idea those to provide detail where they have such large connections to a distribution. It also includes the details of any distribution energy resource connections that are bigger than one megawatt. So it's very basic details, but it's where it's connected the size of that connection and the type of energy and fuel source that that will. That that is and that will align with the requirements of the reason to choose a change proposal 350 which requires distribution network companies that that means both. The no's and idea no's to publish all the connection data above one megawatt. So there's an alignment here between the to the exchange and also what what has to be published in an open forum. And they'll also be details of the connections that are not a great one megawatt and I'm not expecting to be connected. Well, this is given a little bit more of a forward view of what likely is likely to be the stresses on on the the transmission system caused by distribution generation and the like on the distribution. We'll also be exchanging aggregated fuel type data for the connections less than one megawatt. So what that will be is for in the typical distribution network where you've got grid supply points and then the next level down is bulk supply points. We will be providing the aggregated and the connected to that part of the network, but we'll disaggregate that by fuel type. And what we'll also be providing is the impact of all this will be above one and below one megawatt generation will be providing the impact on system demand and fault flow on system demand and fault flow. I think the question is there a plan to publish distribution connected and many capacity individually. Unit type. I'm assuming. Yes, there is. There is currently a requirement to publish and all embedded the above one megawatt that has been mandated by the introduction. I think it's fair to say that anything that we are looking to do in this with the decode modification and the the grid code modifications. Part of that work will be looking to see how we fulfill the requirements and to publish data more openly. And the best way to do that. So that might be publishing CIM models. And that is open to base at the moment. We're certainly looking to make all this data freely available bearing in mind any confidentiality requirements. And Graham's asked a question aggregated less or megawatt the will be an ideal also provide to yourself accepted as well as connected for this category. At this stage, that hasn't been the intention. It's quite a fast moving picture if all less than one megawatt. So what we what we do do is provide that. And as I say, we give an updated view when we have the statement of work process. So when we're applying for a statement of works one new corrected generation, we would update grid on the actual position for less than one megawatt. But at the moment it's not anticipated that accepted world will be published at that stage. Okay, that was all I had to say on product for if there's any more questions and drop them in. If not, I'll just plow straight on to look at product one, which is looking at cold system investment planning. Essentially miss this product is building on the work of primarily products to and for IE. We're looking at whole system requirements based on the forecasting that we're doing for the demand and generation and using the data and the enhanced data exchange that we're proposing for. And it's this product is looking at developing a process that will will deliver the best whole system solution. And that would be looking at whether the best solution might be a, let's take for example, a transmission system issue. The best solution might be a transmission network reinforcement solution. It could be a reinforcement to a DNL network, which would provide support to the transmission system. It could be transmission connected flexibility or it could be DNL connected flexibility. So we're looking at processes that will encourage the submission of different solutions and also the way that those solutions are considered against each other in an equitable fashion. So we've been market testing that some of the processes that we've developed as you can see on the flow diagram on the left. We've been marking testing those through a couple of projects that NGSL are developing at the moment. They're high volts pathfinder projects. One is in the Merzy region and one is in the Pennine region. So we're National Green have sought solutions from the transmission owner. It's sought solutions in saying the Pennine one from both electricity northwest and from Northern Power Grid to the high volts problems in that area. And they're also going out to market to invite flexible solutions. And it could be that the solution is not just one of those different reinforcement or flexibility solution. It could be a combination. So what we've been doing is developing a whole system CVA, which will allow us to identify which is the best whole system solution. And also we've been investigating them and working with off-gem to look at funding, the line of funding issues. It's quite clear how if the solution is a transmission owner solution, how that's funded, not quite so clear at the moment how if it was a distribution solution, how that will be funded. And so we've been working with off-gem to see what would be the way forward and hopefully introducing new funding routes that will be applicable from the Rio ED2 period. Right, I just noticed a question come up there from Matthew Page. Does this include whole system, most economic connection solutions for a given user, not just for wider reinforcement, i.e. user could connect to D, but it's cheaper overall to connect to D. We are looking, I'm trying to understand exactly what you're driving at with that question. But if the connection is cheaper overall to D, that is anticipated, but that will come out in, if any flexibility is looking to connect to either the TOD, then we would anticipate that the most economic solution will come by the flexibility provided understanding the connection costs to them of connecting to TOD and that will be reflected in their costs. I hope that answers your question. If not, please come back to me on that one. Any further questions? If not, I will probably hand over now to John. Yeah, let's move on. Yeah, okay. This is product three, which is real-time data exchange and forecasting. So this picks up really short-term, sort of real-time data transfers. It's looking at a number of different activities, such as the operational intertripping of distributed resources, how service conflicts are managed, how a connect and manage situation might operate. So that's where there might be sort of limited network capacity and you're trying to make the best use of that. And also, we're starting to do a bit of work into operational forecasting. So I've been supporting the team here that has been set up to do product three. It will be going forward. It'll be Ali Amidi from UKPN who will lead this area. So you can see along the bottom there, there's just a timeline of some of the things that some of the outputs. So there was a fairly comprehensive reports of the 2019 work, which was published back in January. And a month or so ago, we published a report into operational tripping schemes, which I'll come on to in the next slide. And then there's a bit more work towards the end of the year. So we could move to the next slide, please. So just on operational tripping schemes. So what, first of all, really what operational tripping schemes are, they're about trying to help manage flows on the transmission efforts, primarily at the moment. So it's looking where there might be an overload following a system fault or outage condition where if you can trip some generation and that generation may be transmission connected or could be distribution connected, then you can manage down the overload. And what that lets you do is make better use of the transmission capacity and ultimately connect and operate more generation of demand. So this particular area has been sort of drawing on three operational tripping schemes, which have been developed by National Grid ESO and NGET with the 3DNOs that you can see there, the ESFZN and UKPN to help manage flows along and into the sort of south coast transmission system. So the reports covers the sort of functional design of those operational tripping schemes. And it goes into the data exchange requirements at a reasonable level. And in those particular schemes at the moment, they're being developed. The UKPN scheme should, one that's been developed with National Grid, should go live around September, October of this year. So at some point over the next month or two. And the other two schemes will sort of follow in 2021. So you can see a bit of the sort of architecture there for the UKPN scheme. The schemes tend to be sort of built from the DNO side, built as extensions to the distribution management systems in the case of WPD and UKPN. They're taking their power on systems and building extra functionality into those to enable the distributed resources to be managed back when needed. And in the case of SSEN, they're putting in place, they're building the operational tripping functionality into the southwest active network management scheme that they're developing and installing at the moment. So there's a lot of how the distribution management systems work. There's then also the secure links, the so-called ICCP or Inter-Controlled Centre Protocol links from control centre to control centre, which are needed to exchange information as to what generation might be available to be, to be tripped or reduced. And how much generation, let's say the NGESO might want to call on a bit of co-time. So these three schemes are being developed and put in place. There will, across them, there should be about sort of 1500 to 1800 megawatts of VR, which will be available. So if you go to the next slide on this, apologies, we're sort of running over a few minutes. This just sort of outlines some of the further work that we're doing in product three. So the operational tripping scheme report will update that again in November after we've got some experience of the EKPN scheme going live and some further development experience of the other two schemes. There is also work going on in the Connect and Manage and Service Conflict Management space, which will primarily draw on the so-called regional development programme that National Grid, ESO and EKPN are working on. And there's quite a lot of work that's already been done in that space, but at the moment the focus is more on the commercial side and sort of working out the commercial framework for other services would be used. And then the other area which is sort of mentioned there on the slide is operational forecasting work. So it's looking at how the ESO goes about doing its forecasting and also how DNOs go about doing their forecasting, sort of looking at what sort of learning can be sort of exchanged between the different parties here. And obviously with the view to improving the quality of forecasts and allowing sort of better information to be exchanged perhaps on embedded generation views, that sort of thing. So there is another area of work here which I'll just mention really, which is looking at data transfers really to improve network management under emergency conditions. So I think we're recognising and some of you may have seen an off-gen call for evidence on EG visibility which sort of follows the 9th of August event last year. And I think we're picking up on some aspects of that in this particular product as well, sort of starting to consider how information on super good transformer close or frequency or distributed generation can be made more available really between TND so that those sort of emergency situations can be better managed. So with time in mind, I'll call it there and maybe we'll go to the final slide and any sort of final questions. You want to pick this one up Ian? Yeah, if there's any further questions, we're probably up, we're slightly over time and we're probably up five minutes if you want to submit them now. For further information on the Workstream 1B products, you can go click on that link there and that will take you to all the products and all the reports that John and I have been discussing this morning. And if you want to have more detailed information, you can contact the open networks at that address below. Okay, thanks. I would also say, I mean, this is the first time we've, I mean, we're doing this particular webinar really at because of some feedback that we got, I think on one of the earlier the ID consultations. I think it would be good to know whether this sort of thing is a useful way of getting information across to people in an easy way. So any feedback you have on that would be really helpful. And indeed, whether there's any of the particular products, maybe you would want us to think about doing a deeper dive into as well. Do you have any final questions, Dan? I can't see any come in. So unless there's anything else from you guys, just from me to say that we'll send the recording and the slides around to everyone that registered. So feel free to send them around to people you might think would be interested. I've got one more. I'm sort of promoting another bit of open networks work here. I think there would be, there were one or two questions there on getting visibility of distributed resources going to a megawatt and maybe below a megawatt. And one of the other products that we have in Workstream 2 is looking at, we're starting to do some work just looking at the value to stakeholders to customers of maybe moving those embedded capacity registers below one megawatt. And I think it would be really helpful to us if we had input from stakeholders or views coming back to open networks about how that might be useful and where it might be useful. It would help us to form our thoughts on that because it's an area that we haven't made any decisions on yet. Okay. Great. Thanks Sean. And thanks everyone for dialing in. We'll send around the recording and the slides shortly. Thank you very much everyone. Have a good morning. Thank you everybody. Thank you.