Optymalizacja konstrukcji wsporczych morskich farm wiatrowych

Yeah, we are design office. We deal with the ships, yachts, also objects. We are present to the market since 2008. Our headquarters is in Gdańsk, Poland, and we have 25 engineers on board. Now our real structure is a bit more because we are also cooperating with some other companies or freelancers. So I would describe it as 30 people, 30 engineers. And as I said, 25 about we have on board now. We do the services for the industries: basic plus design. I think the basic and plus design is something like FEED stage in the offshore industry. Then we have detailed design, also called as workshop design, and production documentation, which is very detailed, describe info for the fabrication yard, so they have all they need to build an object. We deal with the hull structure, yeah, hull, offshore building and structure generally set for offshore objects. Then we have piping and systems, but this department is not so big in our company, and outfitting. And apart from that, we have a very strong finite element method analysis department. We do a lot of analysis and calculation. We don't do electrical and ship theory at all. So I would say, yeah, this three legs: structure, piping, outfitting. Sorry, we're just on one slide. You haven't moved forward yet, or? Yes. Maybe you are showing the different... Okay, there we go. Yeah, now we see, yeah. Can you see it now? Yes, we can see, yeah. That's it. That's good. Okay. Okay, so as I said, three main legs of our activity: structure, packaging systems, and outfitting. Also, we deal often with some technological tooling objects for shipyards, fabrication yards. Yeah, this is also what we can do for our customers.

We have experience with cooperation with companies from Poland and abroad as well, mostly with Germany, but not only, also Scandinavian companies. I would say our operation area is all around the world. We take part in projects from United States, also offshore projects. So, yeah, we deal with owners, shipyards, and bigger design offices like Stocznia, for example. Our development activity, we focus on the offshore wind objects design methodology. I would like to say a few words more about that in the next few slides and present one of our projects. Unfortunately, Maciej didn't let me carry this presentation up to the evening, so I will focus on one project. We also do some of our in-house software and implement it to offshore structures because we think that since intership building industry, we have a lot of good software solutions. In the offshore industry, there is a lot of things to do more within the software implementation. Okay, so the project, I will present only one of them to show you our capabilities and what we are doing here in our office. The project is about the development... Sorry, the second page. Okay, so... now it is. Now it is. Can you see the slides titled project? Yes, that project. Yeah, the project is about to develop own methodology and tool for having a support in the decision-making at the early stage of jacket support and supporting structure for wind farm objects. Yeah, can you see the slide? Yes, yes. Yeah. Yeah, the goal was to create an environment of connected chain different tools to have an environment which lets us know the main parameters of the objects at the early stage with some accuracy, useful for decision-making within the field of choosing different types, maybe letting us to predict some costs at early stage. We didn't develop every tool separately. We used market standards for that and tried to connect them together. For example, as a parametric model, we used Rhino software. For the analysis tool, we used ANSYS, which is market standard, yes. So we connected different tools. We did some programming, some coding job to connect them together, and... What were the problems? At the beginning, we had to define the objective function. It could be the minimum weight of the object. It could be the minimum cost of the object. The environment is quite flexible, so you can define the objective function according to your wishes and different from project to project. Then we have to select the parameters that are going to be subject of optimization, the analyses which will be included to the process, and of course requirements and evaluation criteria. For now, the environment can have the criteria from the Northcaveritas rules, but we can also add or replace them with the American optional industry standards. It's just the parameters that could be included to the system. Then, of course, a few more steps to make.

Code approach according to design methodology from the general to detail, and of course the optimization method. Because I have to say, this is not the AI. Our purpose was to create an environment which gives you results based on true calculation, analysis, strength analysis, finite element method calculation. This is not the AI. But the optimization is about to choose the solution from the space of possible solutions, which could be quite a big amount of solutions. So we decided to use the evolutionary algorithm. And, yeah, the system looks like you can put the preliminary parameters of the jacket structure and the structure which is supported by this foundation. And of course you can define some weight of topside module. You can define depth of sea. You can define many more parameters. And then, as a result, you are given the solution chosen from many possible solutions. All of them are checked against buckling, are checked about DNV, for example, strength criteria like von Mises stress. You can also define the criteria which you would like the structure to be checked, and as a result, you can have the solution. Of course, it's not the automatic process of design from scratch to the final. You cannot use it after the process just to build, but you have strong analysis-based result to further design process. Our goal was to obtain such a result in 48 hours after the system will be started. Of course, it depends also on the strength of your computer system and amount of parameters you would like to optimize. It's the end of the presentation, but I would like to also show you some short video. Is it now visible, the screen with the... Okay, so I will change it to other. So maybe, Patrick, quickly for this part so that we have also time for... Yes. Yeah. This is the screen from the system. The system checks different solutions in the background. Now it is about using the Rhino Grasshopper, but it was from the beginning of the system. Now everything is coded in C# and Python. You can define the bracing. You would like to have, could be V or X bracing. You can define many more parameters. The system will take it into consideration and take it as input parameters, and after that you will obtain full parametric 3D model of the structure, which could be also, of course, changed or optimized. Yeah, that's something we do, and it's part of our research and development activity. Of course, apart from that, we are dealing normally with our clients and giving them services about design and documentation. But, yeah, I wanted to focus on this development thing because I think it could be useful on many projects, and I think that together we can make it even better from project to project. Thank you. Thank you. Sorry, is it Gdaniek? Is that Gdaniek? Am I saying that right? Bartosz. Bartosz. Bartosz. The last name is Italian. We are the same. Yeah. I think I saw on your website you developed some monopile...

Solution, yeah. Yes, the second project that we developed together with Polish National Research and Development Center, the goal was to change a bit the design so it could be useful to be built in Polish fabrication yards. And the main problem was the thickness of the plate, which is not possible to get in Polish factories, and also the technology of Polish fabrication yards doesn't let them to build such a thick plate. So we replaced part of the monopile with the structure with thinner plate, but reinforced with the profiles. We did a lot of dynamic calculations and, yeah, that was the project. Yeah, lots more engineering and lots more welding. Yeah, but you can do it in country, of course. Yeah, yeah, I understand. That is interesting just to see that concept. This was the local content-driven project. Yeah. Jan, sorry, because we are running out of time, just quickly, one minute if you may, sorry. Don't worry, I didn't prepare any presentation, so very shortly about me. I'm a design electrical engineer from my background, but I moved from the engineering also to managing the team of the designers almost... 16 years ago, something like that. So during my career, I've collected the designers and the engineers from the multiple industries. I've been working in the steel industry. That was my initial stage. Later on, to the maritime industry, working together with Kongsberg Maritime. I don't know if you are familiar with those companies responsible for the electrical engineering and navigation engineering, where I moved towards the wind industry. So recently, I've been responsible also to build the proper electrical engineering team within Poland, and later moved from the engineering and design towards service, building, commissioning. I've been also working as a commissioning engineer in the past. So probably whatever we will need on site anywhere, probably I've been already there doing that. Are you focusing on LV systems or HV or which elements? Mostly with the LV. HV, I think it is reserved, but I do have also the team that are responsible for the HV with the switchgears. But, you know, if you consider any kind of the wind industry manufacturer, they are not designing that from scratch, just picking up from the shelf whatever is available. Yeah, you've got the main OEMs, of course, who are dictating and driving that market for sure. Yeah, exactly. But I know how to operate that. Yeah, yeah, I understand. Great, thanks, Ian. David, shall we walk through our slides? We have a few slides for you. Of course, we're happy to share this afterwards, and equally, I hope you can share in the other direction. That'd be great. Of course. Yeah, hopefully that's come through okay for everyone. And if you've got time, we'll run pretty quickly through, but obviously happy to follow up. So, Kent overall, a 13,000-employee global engineering and project organisation. Yeah, £2 billion revenue expected this year. The name Kent is now only four years old, maybe. It's come from a range of companies coming together, so bringing a 100-year track record overall back to the original companies, and now operating globally across 26 countries. But focusing a bit more, obviously, for the discussion on offshore wind, as Jason's touched on, we have a 25-year history in offshore wind design across fixed and floating structures, WTG and offshore substations, front-end consultancy through integrity management.

Yeah, obviously these numbers change frequently as we carry on to design, but an idea of the scale of projects we'd be involved with. And for us, that really is across the full project lifecycle and across the full range of offshore wind and associated power assets. So, yeah, from very front-end supporting developers with seabed lease applications, wind farm layouts, design, various early feasibility studies, through to, I guess, the real core of our offshore wind service offering around the engineering and design for projects, but then a lot of work also at the back end in integrity management, operations and maintenance, life extension studies, and, yeah, covering full range of fixed and floating structures, and through in-house capability, but also a network of trusted partners expanding more into the onshore and wider power business as well. And, yeah, I guess I've covered this, but really providing a full holistic, multidisciplinary design offering across the offshore wind projects. Range of projects, yeah, I won't go through all these. I guess just to illustrate a bit of the global spread. Notably missing any Polish projects currently, so hopefully that's something we can shortly start to add to this map as well. And then, yeah, so we cover the full lifecycle bookend. So this conversation focuses a bit on the kind of design and engineering aspects that are most relevant. A bit of a track record of our substructure design projects covering fixed and floating monopile, jacket, gravity base, pin piles, driven piles, suction buckets, TP-less monopiles, yeah, all sorts over the years that we've been involved with from early concept right through detailed design and fabrication, installation support for these structures. Zooming in on, just to highlight a few of these, Triton Knoll and Seabreea projects, one monopile, one jacket that we've relatively recently completed the full detailed design on both those farms now fully operational. And Mona and Berwick Bank are jacket design projects that we're currently in the middle of detailed design for both of those, looking now at jacket foundations in relatively deep water, up to kind of 65 metres, and now looking at 15 and 21 megawatt turbines. The foundations there. So there are current flagship live detailed design projects. We similarly have a long track record going back to 2009 when we were first involved in offshore substation design. And again, we have the full multidisciplinary design capability for topsides and foundations, and have been involved in, yeah, over 25 installed platforms now, from lightweight modular designs to full multi-deck platforms, and a range of floating substation concept studies, a range of designs and structures now in the water. And a similar snapshot of some of these where we've been involved with, say highlighting, yeah, kind of lightweight modular designs, jacket monopile foundations, Baltic Eagle, one installed.

A couple of years ago now for Iberdrola in the Baltic Sea, fully enclosed topside, given the climatic conditions, and one we've done through a local design house partnering in China for the Chinese market. And, yeah, last couple of slides, as I whiz through this, obviously have, yeah, a range of, very similar in many ways to what you've presented, Bartosz, in terms of the design and optimisation software that we have. We work really around the DNV software suite, so Sesam and Bladed for main analysis and APIS for detailed design, but have built up a comprehensive suite of pre- and post-processing tools. Yeah, various snapshots of this to automate and optimise the designs of structures. And again, I guess just a bit of a flick on this stage, we appreciate the actual realisation of these projects and getting through it, there's a huge amount of complexity and interfacing and detailing, particularly around the secondary structures and electrical designs. And again, that's we've got a significant track record, experience, and... Go by example projects for all these kind of concepts and different aspects there. And that, yeah, I just want to do that very quickly to leave us a bit of time to wrap up, but a brief overview, and obviously we'll send slides through and happy to follow up on any details. Thanks very much. The general purpose of this meeting was to present ourselves in details, so we will share all these materials. Actually, as I've been involved in the talks with Jason since a couple of weeks, so we are kind of up to date in terms of the questions that I would like to raise. But maybe Anna, Banka, Maciej, Jan, Bartosz, maybe any questions toward Kent for the moment? Thank you. Okay, I think I also put through the most important things that we've been discussing, so maybe also that's why we do not have any at the moment questions. So if I may propose just to maybe scheme the next steps, because at the moment what we have is a specific market opportunity, yes, because we can cooperate, I believe, in various streams. But at the moment we have this upcoming RFP for detail design plus FEED, in which I circulated also to Jason, and they need the RFI that PG was delivering earlier this year. And so for me the next step would be to decide if we enter some specific discussions how to approach this market opportunity. We agreed here in the Baltic engineering group that we would like to try to... Yeah, take it with you. But it would, of course, require your kind of positive response on that. So there would be kind of three steps. If your kind of understanding of our capabilities of Stopd and Navard are satisfactory, then we would need to sign the remaining NDAs between Stopd and Navard and Kent bilaterally most probably, and not to complicate that. We've got hours, so it's not a problem. The second would be to somehow give the initial information, because we had this week the PGC meeting with Stopd and Navard, and we've been asked just to give the information if we are going to try to make it together with you, because we said that believably you would be interested in some format to enter this bid. And the first step would be to somehow, as soon as possible, to make this division of work and how we can approach commercially on that.

Yeah, absolutely. And just a couple of questions, maybe. So, Stogard, Navart and Electrical Engineering team represented by Ian, have you guys worked together before, or is this you've come together as a collective now to look for a partner to look at this particular opportunity or opportunities? I will answer, yes. Stogard and Navart have been in those contracts and some commercial cooperation since a couple of years. Yes, a couple of years, I believe, yeah. Yes. Yeah. Gotcha. Okay. And Ian, your electrical team, you guys have been working — you subcontracting to Navart, or...? Actually, I've been working with the various of the contractors, mostly as a freelancer, but not only. I'm also hired with one of the Danish company, and the team we've been working through. But with Navart and Stogard, we didn't get that chance because they are more with the maritime coming up out of the maritime, and I'm coming from the other side. At the maritime time, it wasn't that task done together. However, I do have my strong feelings about it, that we already see each other multiple times, meeting each other, so... We had the division of scope, like internally in this collective, so we've been doing many workshops on that, so to understand who's putting in what. Understand, understand. And of course, as you say, the next step is to understand what a division of responsibility could look like, so, and an NDA to enable us to make that commitment together to perform that piece of work. So that makes sense. A quick question, Matt, for you is the local content requirement of 30%, you know, is that— I'm just trying to understand if that's, if you look at it from a foundation perspective, is it 30% of the overall delivery of the foundations needs to be local content, or is it each element? So engineering needs to be 30% procurement. So first of all, there is no kind of very specific and formal and legal requirement of this percentage, because we are in the European Union, so there is no— No, this is an official ambition of the Polish developers Orlen slash PGE, because right now 21% is some benchmark from Baltic Power, which has been right now commissioned, so the step up towards 30. And it all includes, of course, CAPEX and OPEX at the end of the day. Some people say 45%, which is of course not possible, but of course it would be, at the end of the day, somehow communicated at the project level, not on the each. However, on this early, so on this DevEx phase, the developers like to say we've got 92%, yes, or something like that, but all depends on the... Yeah. On the, yeah, stage. Yeah, yeah. But of course, you're on a journey in Poland. You want to do more work locally, so the more we can do, the better. Yeah, but the DOR will tell the story, right, on where we sit comfortably to... Yeah, we can deliver through a more conservative lens, and we can deliver through a more ambitious lens. We can do both of those things, which I think would be sensible. But no, okay, so if we share our presentations now, and then David and I will have a catch-up and come back to you, Matej. But, you know, it's been really good to meet you. I think there's some potential here, so which could be exciting for us. Let's get the NDA in place, and then we can take it from there on the DOR. My team, sorry to say that, but can we stay on the Polish side? Any teams? Any, sorry, questions? No, no. Okay. Good, excellent. It's been lovely to meet you. Thank you very much for bringing us all together. We appreciate that. Have a good day and a good weekend. Thank you. Thank you for today.