WEBVTT 00:00.000 --> 00:23.220 Hi, everyone. 00:23.220 --> 00:32.060 Okay, let's give a bit of time for everyone to join the call. 00:47.180 --> 00:47.740 Okay. 00:50.440 --> 00:53.140 Just wanted to check, is everyone from Malamud? 00:53.220 --> 00:53.720 Yeah. 01:03.940 --> 01:06.560 We have one more who's joining right now. 01:06.860 --> 01:07.360 Sure. 01:08.640 --> 01:09.400 Bill, right? 01:10.240 --> 01:11.040 Yeah, Bill. 01:12.580 --> 01:14.780 Okay, so just go. 01:17.340 --> 01:22.620 Hello, Matthew, Gillian, Janelle. 01:24.120 --> 01:27.020 I see that Janelle from Enterprise Singapore is here. 01:27.180 --> 01:29.160 Will there be anyone else from Enterprise Singapore joining us too? 01:30.960 --> 01:32.380 Nope, just me today. 01:35.380 --> 01:39.920 Okay, then as for Rolls-Royce, I see Gillian is here, Matthew is here. 01:40.400 --> 01:42.380 Is there anyone else that's joining from Rolls-Royce too? 01:47.580 --> 01:49.760 I think we can kickstart. 01:49.900 --> 01:50.840 Yeah, most of them are here. 01:51.500 --> 01:51.680 Sure. 01:52.400 --> 01:52.700 Okay. 01:53.220 --> 01:58.900 So, we're going to start with a quick introduction of what we're supposed to do today. 01:58.900 --> 02:01.560 And then after this, I'll let both teams introduce each other. 02:01.660 --> 02:04.680 And then I'll just very quickly, you know, start with the team's presentation. 02:05.060 --> 02:08.260 So, just to very quickly run through the goal of today's session. 02:08.340 --> 02:14.400 So, we're here all today for the clarification phase meeting for Malamud and also Rolls-Royce. 02:14.660 --> 02:23.200 So, just to share again the format of today's meeting, it'll be a total of 45 minutes in total with a quick 10-minute presentation by Malamud itself. 02:23.200 --> 02:30.120 Followed by a 20-minute Q&A session between, you know, Rolls-Royce and also Rolls-Royce Singapore, if there are any other questions. 02:30.640 --> 02:32.000 And Malamud. 02:32.260 --> 02:35.500 Afterwards, there's a 10-minute buffer just in case the meeting actually overruns. 02:35.520 --> 02:36.040 So, not to worry. 02:36.120 --> 02:38.620 I'll actually have the time for each of those sessions itself. 02:40.200 --> 02:49.980 Just a gentle reminder, after this phase itself, there is actually a set of deliverables that's required from the Malamud team by 29th of June, Monday. 02:50.660 --> 02:52.700 Of course, 4 p.m. GMP plus 8. 02:53.200 --> 03:00.400 So, the first set of deliverable is a refined proposal deck of up to 20 slides following today's meeting. 03:00.820 --> 03:07.540 So, from today's meeting itself, there might be quite a fair bit of questions that's asked by the Rolls-Royce and Enterprise Singapore team regarding Malamud's solution. 03:07.880 --> 03:13.580 Likewise, this is also a good opportunity for the Malamud team to ask any clarifying questions to the Rolls-Royce team. 03:13.880 --> 03:21.460 So, from all of these questions, you know, there might be some changes or enhancements that the Malamud team may like to make to their slide deck deliverable. 03:21.880 --> 03:22.660 This would be a good opportunity. 03:22.660 --> 03:31.300 So, this is a good opportunity to make these revisions or enhancements and just a gentle reminder again, the total length of this slide deck is up to be 20 slides in total. 03:31.960 --> 03:33.420 So, that's the first deliverable. 03:33.940 --> 03:44.140 The second deliverable is that we also require an introductory two minutes video of the solution by either the founder, the CEO or top management of Malamud, explaining how the solution works. 03:44.380 --> 03:51.760 So, this is really quite a good opportunity for you to do a quick, you know, pitch of your solution as to why the solution should be selected by the Rolls-Royce team itself. 03:51.760 --> 03:53.680 Are there any questions? 03:55.880 --> 03:56.920 Nope, all good for me. 03:57.400 --> 04:02.140 Okay, so in this case, I'll just let the team introduce themselves. 04:02.140 --> 04:06.200 So, would the Malamud team like to introduce yourselves and very quickly start the presentation? 04:08.020 --> 04:11.700 Yeah, good morning here from New York City. 04:11.940 --> 04:13.200 It's great to meet you all. 04:13.200 --> 04:18.340 I am Cara Meyer, the founder of Malamud, and I'm joined by my co-founder, Bill Leon. 04:21.760 --> 04:22.060 I'm sorry. 04:22.300 --> 04:22.660 I'm sorry. 04:22.960 --> 04:23.240 I'm sorry. 04:23.560 --> 04:23.780 I'm sorry. 04:24.120 --> 04:24.300 I'm sorry. 04:24.700 --> 04:25.360 I'm sorry. 04:25.360 --> 04:25.820 Yeah. 04:26.040 --> 04:26.620 Hi, everyone. 04:26.740 --> 04:27.180 Hi, everyone. 04:31.780 --> 04:32.220 Um. 04:32.640 --> 04:32.920 Um. 04:34.760 --> 04:36.820 I think you just got to use one audio. 04:37.460 --> 04:37.740 Yep. 04:39.380 --> 04:40.740 So I see it's just a little. 04:42.780 --> 04:43.760 What's this happening? 04:43.760 --> 04:44.320 What's this happening? 04:44.480 --> 04:44.880 I don't know. 04:45.140 --> 04:45.780 Neither of us. 04:45.960 --> 04:46.660 That's great. 04:46.980 --> 04:47.700 There we go. 04:47.980 --> 04:48.240 Okay. 04:48.640 --> 04:49.540 Apologies, everyone. 04:49.540 --> 04:53.220 Uh, just morning in New York here as well. 04:53.420 --> 04:56.260 Happy to meet, uh, find us in the same room. 04:56.460 --> 04:58.640 So hopefully our audio won't collect too much. 04:59.160 --> 05:00.520 Um, but yeah, I'm Bill. 05:00.660 --> 05:03.280 I am the co-founder of Malamute as well. 05:03.560 --> 05:08.940 Uh, we both sort of work out of New York city, but we've been all up and down, uh, the East 05:08.940 --> 05:13.800 coast here, uh, working with different manufacturers over the last five years and really excited 05:13.800 --> 05:17.880 to meet everyone at Rolls Royce, uh, and hear about your problem set. 05:17.880 --> 05:18.380 Yeah. 05:19.540 --> 05:20.680 We'll talk to you soon. 05:22.840 --> 05:22.940 Okay. 05:22.940 --> 05:24.380 Thank you for introducing yourself. 05:24.920 --> 05:29.940 Uh, would the Rolls Royce team like to introduce yourselves and your roles to the Malamute team 05:29.940 --> 05:31.020 was also just so they're familiar. 05:32.280 --> 05:32.780 Sure. 05:32.980 --> 05:35.820 Uh, firstly, thanks guys. 05:35.980 --> 05:40.120 This must be really we, ours, and I can see the background behind you is not a 05:40.120 --> 05:42.360 wallpaper, but it's literally. 05:42.860 --> 05:43.240 Dawn. 05:43.240 --> 05:44.660 So appreciate that. 05:45.140 --> 05:47.440 Uh, I am Raj. 05:47.500 --> 05:48.960 I am, uh. 05:48.960 --> 05:53.840 the technology strategy lead for disassembly technologies so basically how we take about 05:53.840 --> 05:58.740 engines and put them back together and the reason you are up so early is probably because of me 05:58.740 --> 06:06.480 because i'm based in singapore uh and on the call we have quite a few diverse range i'll just 06:06.480 --> 06:15.680 quickly pass it on to my team here uh sohan and first hi good good morning good evening i'm sohan 06:15.680 --> 06:21.520 uh just like raj i'm based over in singapore here i'm with the technology team so i look after 06:21.520 --> 06:26.840 mro technology projects it's nice to hear from you guys mike 06:26.840 --> 06:35.240 hi good morning good afternoon good evening uh i'm same thing as uh raj and sohan my name is 06:35.240 --> 06:42.000 so i'm doing same thing uh technology for uh smd methods and this is everything yeah 06:42.000 --> 06:45.480 all right let's move a bit closer to you guys 06:45.480 --> 06:45.660 you 06:45.680 --> 06:46.180 John 06:46.180 --> 06:52.520 hi good to meet you john pearson technology lead for the innovation team and part of the future 06:52.520 --> 06:57.620 technologies group to work alongside ariane based in the uk derby 06:57.620 --> 07:00.180 ariane 07:00.180 --> 07:08.300 morning ariana ramad john but based in derby in the future technology team um i'm the lead for 07:08.300 --> 07:12.640 technology horizon scanning and rolls royce and i'm also leading the community of practice for 07:12.640 --> 07:13.800 everything xr related 07:15.680 --> 07:18.100 matt 07:18.100 --> 07:22.160 good morning all my name is matt chamberlain i'm an 07:22.160 --> 07:28.140 industrialization manager in derby civil etns 07:28.140 --> 07:30.180 mick 07:30.180 --> 07:38.980 hi it's uh mick mahal based in bristol uh district product specialists looking at emerging technologies innovation and vr 07:39.580 --> 07:40.520 and 07:40.520 --> 07:43.400 finally uh dan 07:43.400 --> 07:43.680 uh more nor lastly it's a concept it's smoothly but every medium is dynamic yeah i work in helping people become available preserve and develop imagination through crabench application and ні digital plastics looking at emerging technologies innovation and vr answers will need your undenooo workouts please check hotline 3723 Wait Butterfly Feedback website on video web facebook mick mahal hai hi it's uh mick mahal based in bristol a district product specialists looking at emerging technologies innovation and vr 2016 working quality благashawan울 i'm at utiliza right now and finally dan 07:43.680 --> 07:50.680 Morno, yeah, I work at Mekong Basin Bristol, part of the Digital Project Ownership team in Defence. 07:53.680 --> 07:59.680 Thank you. Would the Enterprise Singapore team like to introduce yourself to Malamudu? 08:00.680 --> 08:04.680 Hi, I'm Jane Yeo from Enterprise Singapore. 08:04.680 --> 08:17.680 I oversee the aerospace and space tech industries in Singapore and help to grow the industry and help the local companies here as well as, yeah, we help support the AOC. 08:19.680 --> 08:24.680 Thank you. Actually, I just realised I didn't do a quick introduction of myself too, so sorry about that. 08:25.680 --> 08:28.680 But just to introduce myself, my name is Timothy. I'm actually from the company called Agarice. 08:29.680 --> 08:31.680 We're actually the partner of Enterprise Singapore for this specific challenge. 08:32.680 --> 08:33.680 So my role here today is really to be a coordinator for Agarice. 08:34.680 --> 08:38.940 And then I'm also the head of the 08:39.940 --> 08:41.680 So now that introductions are out of the way, I'll very quickly start, you know, you can just very quickly start your presentation. 08:41.940 --> 08:45.680 I'll help to time it out and you have 10 minutes for the presentation itself. So over to you. 08:50.940 --> 08:51.940 All right, we are sharing our screen now. 08:52.940 --> 08:59.940 Thank you. So we're going to talk to you today about our MRO Master Trainer platform. 09:01.940 --> 09:03.940 Can you go back a second. 09:04.680 --> 09:12.400 slide? Thank you. We are Malamute, a team of builders focused on equipping deskless 09:12.400 --> 09:23.540 workforces with the tools of tomorrow. And the challenge that we're focused on is about 09:23.540 --> 09:29.720 effectively training aerospace technicians to develop with high confidence, error-free 09:29.720 --> 09:37.800 proficiency in all your engine assembly and disassembly. I'll hand it off to Bill to tell 09:37.800 --> 09:43.300 you more about our solution. Yeah. And before you get into the solution, it's really about the 09:43.300 --> 09:49.240 problem here. Given that really long problem statement, one thing that we really click with 09:49.240 --> 09:57.600 is the problem in training a skilled workforce, trying to keep all these MRI operations going, 09:57.980 --> 09:59.240 is that the number one thing, 09:59.440 --> 09:59.700 most of the time, 09:59.700 --> 09:59.720 most of the time, 09:59.720 --> 10:05.120 teams are after is actually product reliability so all of this is what do 10:05.120 --> 10:08.960 you do to keep your product in your customers eyes as the number one thing 10:08.960 --> 10:14.180 in their sort of choice you know continuing to choose Rolls Royce and 10:14.180 --> 10:18.920 that depends on great teams because it takes entire teams to keep especially 10:18.920 --> 10:23.060 complex things together but also great technology and these things have to work 10:23.060 --> 10:28.660 hand in hand and so we've been developing a mixed reality enhanced 10:28.660 --> 10:34.480 collaboration platform over the past couple years and this platform is really 10:34.480 --> 10:40.480 focused around combining mixed reality technologies and spatial computing and 10:40.480 --> 10:45.900 for spatial computing it's really all of the you know technology the math and the 10:45.900 --> 10:50.560 tools around making sure that anything that's digital isn't just locked into 10:50.560 --> 10:54.160 the screen into the two-dimensional space really we're trying to take into 10:54.160 --> 10:58.420 account all this 3d information and mapping it back on to the real world 10:58.420 --> 10:58.640 you know we're trying to take into account all this 3d information and mapping it back on to the real world 10:58.640 --> 11:09.580 so our big pillars for what our solution provides is collaboration a spatial 11:09.580 --> 11:15.240 computing platform and workflows that are tailored for mixed reality and again 11:15.240 --> 11:20.960 mixed reality is mostly expressed in the ability to be wearing a headset that has 11:20.960 --> 11:26.360 three-dimensional information while still using the real physical items in 11:26.360 --> 11:28.400 the workflow or in the workspace 11:28.400 --> 11:33.200 we care a ton about cooperation we think problems are solved when team 11:33.200 --> 11:38.000 members are working together and mostly is that they're working within the actual 11:38.000 --> 11:44.240 space the real space and not just purely in a virtual simulated room or 11:44.240 --> 11:51.320 environment so with that we've developed tools that allow for co-located mixed 11:51.320 --> 11:58.160 reality so workers can be in the same space we've done in the actual lab 11:58.160 --> 12:04.700 setting where production and equipment is being developed as well as 12:04.700 --> 12:11.300 co-location to enable shared multi-user interactions where you can have you know 12:11.300 --> 12:16.700 a worker inside a headset with other workers that are both in headset or in 12:16.700 --> 12:19.760 mobile 12:19.760 --> 12:27.800 and this has been really really a great project and process for us especially mixing what is sort 12:27.800 --> 12:33.620 of these proposed CAD designs as well as actually built both prototype and in deployment 12:34.820 --> 12:39.740 physical equipment so specifically here I'm talking about a partnership we did with a biotech 12:39.740 --> 12:46.760 company for a brand new filtration system that hadn't existed before and a lot of scientists 12:46.760 --> 12:51.260 and researchers that were using it had no idea of what it could do or how it could work and 12:51.260 --> 12:57.740 this allowed them to sort of show this off even without taking one of these bespoke systems as 12:57.800 --> 13:03.260 well as to prototype all of the different parts and pieces that would need to go between consumables 13:03.260 --> 13:04.460 and fixed assets 13:07.160 --> 13:12.380 but the most exciting thing that has come up in the last couple years specifically the last year 13:12.380 --> 13:18.540 that we've been working on most excited to show waltz Royce today is the rapid integration of 13:18.540 --> 13:24.740 real assets into Virtual Space so everyone's probably familiar with CAD models and their 13:24.740 --> 13:25.780 ability to uh integrate 13:25.780 --> 13:27.460 into these virtual spaces and mobile aspects 13:27.800 --> 13:36.360 headsets, we've been working on in the wild scanning of actual components and bringing 13:36.360 --> 13:45.480 those into XR. So this is through just an entire tool set that we've been developing that allows 13:45.480 --> 13:51.640 for 3D Gaussian splatting, it's a very photorealistic method, to then be integrated 13:51.640 --> 13:58.200 directly into the same XR platform that we've used for CAD. This allows for actual overlay of 13:58.200 --> 14:05.240 a photoreal onto the actual object. The scanning pipeline works very quickly, we're talking sub 14:05.240 --> 14:14.680 maybe five to eight minutes, for getting something into your real space in a photoreal way. So I've 14:14.680 --> 14:20.520 been, well I was, this project is already done, but I was rebuilding a rotary engine a while ago 14:20.520 --> 14:21.480 out of an RX-8. 14:21.640 --> 14:29.240 A Mazda and taking these scans along the way and being able to annotate them directly in XR 14:29.240 --> 14:36.920 using MetaQuest headset and Logitech MX Ink pen. Now this 3D Gaussian splatting, if you have not 14:36.920 --> 14:42.680 experienced yet, is kind of an incredible rendering technology that we're mostly excited 14:42.680 --> 14:51.000 about because it runs in real time and so you can very quickly pull this up within other formats 14:51.640 --> 14:57.560 that are available. So I'm going to show it as the real spatial representation. And for example, 14:57.560 --> 15:04.200 here is my car that hit a deer, which I think is the best example, and especially because the 15:05.080 --> 15:10.520 collision center let me scan the car the whole way through. So I have a perfect record of my car 15:10.520 --> 15:21.640 being rebuilt after that collision. Also happy to share those demos as well later on. But what we do, 15:21.640 --> 15:27.320 and what we've been doing for a while, is trying to package these XR headsets and platform 15:27.320 --> 15:33.160 specifically with NVIDIA compute so that you can run all of these things without needing any IT 15:33.160 --> 15:39.480 infrastructure. We ship the IT, the router, the compute, everything can run locally. You don't need 15:40.120 --> 15:45.640 any type of integration, even though we can do that. But we prefer to sort of push for solutions 15:45.640 --> 15:51.400 that work in the field. Now we're really interested here in, especially this challenge, 15:51.400 --> 15:58.200 because as we know, the global MRO market is fairly large, but we believe that this partnership 15:58.200 --> 16:03.480 is going to give us access to the global aircraft engine and parts manufacturing market, especially 16:03.480 --> 16:09.560 to push us to where we really want to be, which is addressing problems across all manufacturing, 16:09.560 --> 16:16.840 heavy industries, precision manufacturing, biotechnology. So right now, we're thinking 16:16.840 --> 16:21.080 of the business model as purely software as a service, and we want to get to somewhere 16:21.080 --> 16:26.200 around platform licensing. The most important thing for us in our business model as we develop 16:26.200 --> 16:31.560 it is we're leaning into the forward-deployed engineering model, where we want ourselves and 16:31.560 --> 16:36.280 our engineers to be deeply integrated with the process, because I think that's where a lot of 16:36.280 --> 16:41.640 the value lies, not just in selling a piece of software and having the customers sort of try 16:41.640 --> 16:46.440 to develop it themselves. The other thing is we're trying to keep the tech really focused 16:47.000 --> 16:51.000 so that we can ship it, we can make it mobile, we can send it to where it needs 16:51.000 --> 16:56.040 to go really quickly. So trying to minimize as much overhead as possible. 16:58.920 --> 17:04.440 Now, really briefly, I want to say that within the competitive landscape, there are a lot of 17:05.640 --> 17:12.520 XR and VR training tools, and they really fall into this bucket where they're learning management 17:12.520 --> 17:19.320 systems that you'll see, and they all are within a controlled environment. And what we've been 17:19.320 --> 17:21.000 doing is we've tried to put a lot of that into the competitive landscape, and we've tried to put 17:21.000 --> 17:28.760 a lot of them into deep learning so that we can actually push ourselves into something that is for 17:28.760 --> 17:34.280 augmenting operations, and it can be used in the field. So it's not meant to be a learning 17:34.280 --> 17:39.400 management system, it's meant to be a spatial computing system. And with that, this is a 17:39.400 --> 17:45.720 two-dimensional chart, there's a third dimension here as well, where a thing I'm really critical of 17:45.720 --> 17:50.760 is that especially in the competitive, or in our competitors, it really feels like video game graphics. 17:51.000 --> 17:57.160 not really about that i want us to be developing distraction-free mixed reality that's using these 17:57.160 --> 18:03.480 real 3d assets that you know the workers uh the workforce really needs and that can help them 18:03.480 --> 18:11.720 actually integrate with their real operational environment so we've been working on a number 18:11.720 --> 18:17.560 of things i think uh aside from more you know industrial partners one of the biggest partnerships 18:17.560 --> 18:24.440 we had was in 2021 we worked with snap inc so snapchat made some experimental augmented reality 18:24.440 --> 18:30.920 glasses and that really kicked us off into integrating what we were which was an ai company 18:30.920 --> 18:35.720 into one that kind of pushed more into system solutions that could be represented 18:35.720 --> 18:42.520 in the spatial physical space and through that we've been able to work with multiple different 18:42.520 --> 18:47.320 companies and different innovation hubs to continue developing this and that's where we 18:47.560 --> 18:57.320 are today and hopefully continuing with rolls-royce this is our team you met cara my co-founder software 18:57.320 --> 19:06.600 engineer developer i'm also a engineer by trade worked in nanoscale and our team includes craig and 19:06.600 --> 19:15.680 ray two kind of amazing people who are very technical yet also deeply love being on the factory floor 19:17.560 --> 19:24.720 and that is it for us i want to thank everyone for this very brief presentation happy to have 19:24.720 --> 19:28.800 a discussion and i know uh you probably have a lot of questions and we're here to answer them 19:29.440 --> 19:32.080 i have tons of extra photos to share as well 19:36.720 --> 19:40.640 thank you so much for your time and presentation uh rolls-royce team over to you 19:45.040 --> 19:47.520 hey um if i may get the ball rolling 19:47.560 --> 19:53.840 oh thanks for that guys that was actually quite uh informative especially you know 19:53.840 --> 20:00.560 seeing that videos because i understand this is a problem statement where a two-dimensional 20:00.560 --> 20:07.360 slideshow is not the best way to demonstrate the capability so i appreciate those videos 20:09.200 --> 20:12.640 i think one thing which you highlighted was that 20:14.880 --> 20:16.560 in my opinion it's a 20:17.560 --> 20:22.720 strength but i'm not sure how it directly answers the problem statement right so don't take that as 20:22.720 --> 20:29.600 a negative comment that the fact that you are able to capture and then overlay in real environment 20:30.400 --> 20:38.000 how would you see this solution being used because what we want to start off with is 20:38.000 --> 20:44.000 used in the training environment because that's where it gets easier to implement due to 20:44.000 --> 20:47.040 airworthiness requirements we don't want to go this this 20:47.560 --> 20:49.520 software to start making decisions, 20:49.520 --> 20:50.520 but in the training element. 20:50.520 --> 20:53.780 So how would you build that? 20:53.780 --> 20:58.780 Would you need some photos and videos of our current engines? 20:59.260 --> 21:04.040 And then we have a set of instructions and SOPs 21:04.040 --> 21:07.340 that tell us how to take it apart and put it back together. 21:07.340 --> 21:12.160 So how would that be built to augment the training 21:12.160 --> 21:15.220 of a new operator or a new technician? 21:17.560 --> 21:22.560 If I'm understanding the statement here is that 21:25.060 --> 21:27.680 you have all of these training materials already 21:27.680 --> 21:31.100 and they are tied to real assets. 21:31.100 --> 21:35.260 And sort of where I may have painted actually 21:35.260 --> 21:37.680 a little too quickly over the fact that like 21:37.680 --> 21:41.260 we have developed this compute that goes with it. 21:41.260 --> 21:44.100 And I think that's the platform for integrating 21:44.100 --> 21:46.100 all of those technical manuals. 21:46.100 --> 21:47.360 And the idea is that 21:47.360 --> 21:49.900 within the software you are using it 21:49.900 --> 21:51.800 as a learning management system 21:51.800 --> 21:54.960 in the sense of you're parsing through this, 21:54.960 --> 21:57.480 a PDF technical manual, for example. 21:57.480 --> 22:01.120 But what we wanna do is provide a way for your teams 22:01.120 --> 22:04.780 to quickly fill in and augment that PDF 22:04.780 --> 22:06.880 with spatial information. 22:06.880 --> 22:09.100 And that's the spatial computing part is 22:09.100 --> 22:12.540 just like you would annotate a PDF with comments and texts 22:12.540 --> 22:14.120 and potentially imagery, 22:14.120 --> 22:17.360 we would provide the way as well with can be done through 22:17.360 --> 22:20.080 the headsets themselves or with mobile devices 22:20.080 --> 22:23.580 to continue to pull in 3D assets. 22:23.580 --> 22:26.180 And I know that you probably have lots of CAD models 22:26.180 --> 22:28.580 that could be processed in this way, 22:28.580 --> 22:32.360 but similarly, you could actually get real variants 22:32.360 --> 22:35.840 as examples scanned and brought in too, 22:35.840 --> 22:39.060 but the source of truth for the platform would be this PDF 22:39.060 --> 22:42.420 that gets put onto this computing platform. 22:42.420 --> 22:45.620 So we're sort of almost taking that as table stakes here, 22:46.500 --> 22:46.900 which we should have made clear, you know, in the beginning, 22:46.900 --> 22:48.640 sort of make clear when, you know, 22:48.640 --> 22:49.840 now that you bring it out. 22:52.580 --> 22:53.740 All right, thanks for that. 22:53.740 --> 22:56.880 And the other question I have is on the hardware. 22:57.760 --> 23:02.000 Is that a off-the-shelf VR solution 23:02.000 --> 23:05.120 and are you hardware agnostic or? 23:07.620 --> 23:09.840 Off-the-shelf hardware agnostic. 23:10.940 --> 23:14.240 Here we're using specifically the MetaQuest 3. 23:14.240 --> 23:16.040 It is right now the best all-in-one headset 23:16.040 --> 23:19.220 that you can just pop off the shelf. 23:19.220 --> 23:22.540 The compute we're using NVIDIA's Orin, 23:23.620 --> 23:25.100 which potentially we would upgrade 23:25.100 --> 23:27.560 to the newer version that's out now, 23:27.560 --> 23:30.800 but those provide all the compute capability 23:30.800 --> 23:32.820 and we, you know, ship a router. 23:32.820 --> 23:36.000 And so, you know, our clients and customers, 23:36.000 --> 23:37.960 they can choose which tech they want. 23:37.960 --> 23:40.000 We sort of code everything very much 23:40.940 --> 23:43.720 to be as interoperable as possible. 23:46.040 --> 23:47.040 Yeah. 23:47.040 --> 23:47.880 Yeah, Arjen. 23:49.960 --> 23:51.200 Thank you. 23:51.200 --> 23:52.020 Two questions. 23:52.020 --> 23:54.100 How, if this is a training platform, 23:54.100 --> 23:56.760 how do you monitor training progress 23:56.760 --> 23:59.520 and how do you monitor training success 23:59.520 --> 24:01.320 and how gets that documented? 24:05.580 --> 24:08.660 Yeah, so we right now don't have a way 24:08.660 --> 24:11.840 to monitor that success aside from integrating 24:13.160 --> 24:15.620 whatever, you know, you would need, 24:15.620 --> 24:18.200 in terms of following that technical manual. 24:19.140 --> 24:20.820 But from that perspective, 24:20.820 --> 24:23.280 since we're sort of kind of coding everything 24:23.280 --> 24:25.260 to a technical manual, 24:25.260 --> 24:26.560 we would just have to work with the teams 24:26.560 --> 24:30.120 to see what are those actual checkpoints that matter. 24:30.120 --> 24:32.800 And then for us, we can sort of build out exactly 24:32.800 --> 24:35.300 what's needed for tracking, for metrics, 24:35.300 --> 24:37.320 and how to get them out to where they need to be, 24:37.320 --> 24:39.400 especially for say like auditing 24:39.400 --> 24:42.160 or tracking that type of learning. 24:42.160 --> 24:45.540 And this is something to add on to what Bill's saying, 24:45.540 --> 24:48.740 is we would love to work with our customer 24:48.740 --> 24:50.800 and to work with you, 24:50.800 --> 24:53.160 because I assume Rolls-Royce already has 24:53.160 --> 24:56.120 a pretty standard training process. 24:56.120 --> 25:00.560 And so to ingest yours and add that into the system 25:00.560 --> 25:04.240 so that we can make sure we're hitting the same benchmarks, 25:04.240 --> 25:05.560 because as technicians, 25:05.560 --> 25:08.960 it doesn't really matter to us what the benchmarks are. 25:08.960 --> 25:10.880 It's really like your source of truth 25:10.880 --> 25:13.220 that we want to be ingesting in our system. 25:15.540 --> 25:17.680 And so that's something that we can do. 25:17.680 --> 25:19.500 And I think that's something that we'll be working on 25:19.500 --> 25:20.400 in the future as well. 25:20.400 --> 25:21.280 So thank you for that. 25:21.280 --> 25:22.580 And I think that's pretty much it. 25:22.580 --> 25:23.840 Thank you for that, Bill. 25:23.840 --> 25:25.320 Thank you. 25:25.320 --> 25:25.820 OK. 25:25.820 --> 25:27.080 Thank you. 25:27.080 --> 25:30.660 OK, you mentioned benchmarking and auditing. 25:30.660 --> 25:34.200 As a training aid, can this be used as an overlay 25:34.200 --> 25:37.080 to make sure all the parts are present 25:37.080 --> 25:38.940 and highlight any that aren't? 25:42.360 --> 25:42.860 Yeah. 25:42.860 --> 25:43.780 So we should . 25:43.780 --> 25:44.280 Sorry. 25:44.280 --> 25:45.300 I was switching audio here. 25:45.300 --> 25:48.380 So this one is about augmentation. 25:48.380 --> 25:52.200 Not only could we structure it as a step 25:52.200 --> 25:54.960 through technical process or a step 25:54.960 --> 25:57.740 through learning experience, you can also just 25:57.740 --> 26:01.080 do this as an overlay for your variant. 26:01.080 --> 26:03.960 You could have, again, the real scan or also 26:03.960 --> 26:07.220 the expected layout of whatever parts that 26:07.220 --> 26:09.540 are needed from CAD models. 26:09.540 --> 26:13.080 And especially if you have set ways 26:13.080 --> 26:15.240 that you organize your parts and materials before you start 26:15.240 --> 26:18.160 You can especially program those in to have overlays 26:18.160 --> 26:19.680 so that people can compare directly. 26:21.800 --> 26:24.380 So would you highlight anything that's missing 26:24.380 --> 26:25.760 that should be there? 26:27.140 --> 26:28.620 You potentially could. 26:28.720 --> 26:30.220 This is something that would have to be scoped 26:30.220 --> 26:33.160 because since we have front-facing cameras, 26:33.860 --> 26:36.660 it's very straightforward to do CV, 26:36.840 --> 26:40.140 but that requires actually running a bit of scoping 26:40.140 --> 26:43.680 to understand how clean those setups would be, 26:43.680 --> 26:46.260 how well the CV will take based on your parts, 26:46.400 --> 26:49.360 if they're too varied and too fine. 26:49.500 --> 26:51.200 But that's just something that we can work on. 26:51.700 --> 26:54.020 The importance of the platform that we're, 26:54.320 --> 26:56.060 or I should say the system that we work in, 26:56.360 --> 26:58.940 is to very quickly enable that pipeline 26:58.940 --> 27:00.900 from sort of the headset experience 27:00.900 --> 27:05.180 to getting it onto an AI-powered device, 27:05.740 --> 27:07.560 something that you can run just generally. 27:07.680 --> 27:10.300 If any of your other teams are running any ML, 27:10.800 --> 27:13.560 it would be fairly straightforward 27:13.560 --> 27:13.660 to run that pipeline. 27:13.680 --> 27:13.700 It would be very straightforward 27:13.700 --> 27:15.660 to get it operating on the compute 27:15.660 --> 27:16.820 that we could send over. 27:18.440 --> 27:18.880 Okay. 27:19.560 --> 27:20.000 Yeah. 27:20.320 --> 27:21.700 But I also know that that's a broader, 27:22.080 --> 27:23.660 kind of like a broader integration 27:23.660 --> 27:25.860 than purely training and learning. 27:26.660 --> 27:28.560 Yeah, I know, Mick, where you're getting at, mate, 27:28.660 --> 27:30.680 because we are looking at comparing engines 27:31.260 --> 27:32.300 coming in and going out. 27:32.360 --> 27:34.300 So can this be effectively the way 27:34.300 --> 27:36.780 we do an engine inspection 27:36.780 --> 27:39.380 to check for missing parts? 27:40.700 --> 27:41.140 Yeah. 27:41.140 --> 27:46.280 The capabilities, and again, 27:46.360 --> 27:48.200 I kind of throw the Quest 3 27:48.200 --> 27:50.420 as being a great device here 27:50.420 --> 27:53.000 just because it does have those front-facing cameras. 27:53.000 --> 27:55.960 So what your technicians see 27:55.960 --> 27:58.380 is also captured in real-time. 28:07.520 --> 28:08.440 Okay. 28:08.820 --> 28:11.120 Any other questions? 28:11.140 --> 28:16.800 Yep, maybe just one from me. 28:17.300 --> 28:18.880 Bill, thanks for your demonstration, 28:19.160 --> 28:21.600 especially on your Gaussian splat. 28:21.780 --> 28:23.180 I think that was quite interesting. 28:24.200 --> 28:27.120 And I also appreciate that you guys chose the Quest 3, 28:27.240 --> 28:28.800 which is one of the, I believe, 28:28.880 --> 28:32.400 one of the latest wearables out there. 28:32.860 --> 28:34.700 And yeah, my question is on training 28:34.700 --> 28:36.920 because as we know, technicians, 28:37.200 --> 28:38.060 when they come for training, 28:38.220 --> 28:39.900 some of them are new to wearables. 28:40.520 --> 28:41.020 And one of the things that I think is important 28:41.020 --> 28:41.120 is that when you're training, 28:41.120 --> 28:42.980 one of the common feedback 28:42.980 --> 28:45.780 is that it's on ergonomics. 28:46.480 --> 28:50.300 And the feedback I got was that 28:50.300 --> 28:53.220 some of them are concerned with motion sickness. 28:53.480 --> 28:55.120 Some may comment that it's heavy, 28:55.340 --> 28:55.780 it's bulky, 28:56.300 --> 28:59.120 and it may be uncomfortable for new users. 28:59.680 --> 29:01.680 So in the perspective of Malamute, 29:02.420 --> 29:06.000 do you expect new users to wear wearables 29:06.000 --> 29:07.480 for a long period of time? 29:08.100 --> 29:09.420 Of course, this is dependent 29:09.420 --> 29:10.780 on the type of training 29:10.780 --> 29:11.000 that you're doing. 29:11.000 --> 29:11.640 So I think that's a very important thing 29:11.640 --> 29:12.440 that we conduct here in Rolls-Royce. 29:12.920 --> 29:14.080 But do you challenge that 29:14.080 --> 29:17.540 they do not have to wear for a long time? 29:17.960 --> 29:19.940 Or that if users have to wear for a long time, 29:20.060 --> 29:22.700 do you think there's other solutions around it? 29:24.280 --> 29:25.820 I have so many answers. 29:26.680 --> 29:27.840 No, I love this question 29:27.840 --> 29:30.720 because there is a thesis that I have, 29:30.760 --> 29:33.920 which is I want to develop a headset experience 29:33.920 --> 29:35.100 where you take the headset off. 29:36.140 --> 29:38.020 I think that's the most important thing 29:38.020 --> 29:39.100 is that the headset is there 29:39.100 --> 29:40.960 to like ingrain an idea 29:40.960 --> 29:41.760 into the brain 29:41.760 --> 29:43.740 and the tech lifts it up. 29:44.520 --> 29:45.640 Some of the ergonomics, 29:45.740 --> 29:47.880 we've kind of re-kitted the headset 29:47.880 --> 29:49.420 with a different headband 29:49.420 --> 29:51.440 and remove the visor, 29:51.660 --> 29:52.640 the light shield, 29:52.740 --> 29:55.260 specifically because we want the user 29:55.260 --> 29:56.640 to be able to flip it up. 29:57.380 --> 29:59.020 So the headset comes down 29:59.020 --> 30:00.180 when you need that overlay, 30:00.380 --> 30:01.500 when you need those instructions, 30:01.640 --> 30:02.620 when you need that guidance. 30:02.880 --> 30:04.880 But we really want sort of the user 30:04.880 --> 30:06.240 to get a lay of the land 30:06.240 --> 30:07.820 and sort of pop it off. 30:07.820 --> 30:08.980 And this is an experience 30:08.980 --> 30:10.320 we had with Snapchat. 30:10.320 --> 30:12.780 When we were using their full AR glasses, 30:13.580 --> 30:15.940 it was actually a power limitation 30:15.940 --> 30:18.080 that we didn't want them using it all the time 30:18.080 --> 30:20.100 because the original engineering ones 30:20.100 --> 30:22.020 could only last for maybe 18 minutes. 30:22.480 --> 30:23.820 But what we wanted them to do 30:23.820 --> 30:25.280 was we wanted all of the workforce 30:25.280 --> 30:26.320 to click them on, 30:26.960 --> 30:29.320 understand the world with the digital overlay, 30:29.640 --> 30:32.020 and then click them off and get to work. 30:32.660 --> 30:34.460 And here in the same sense is 30:34.460 --> 30:37.240 you really want them to get used to the real engine. 30:37.860 --> 30:39.880 And so that is as much guidance 30:39.880 --> 30:40.120 as they take. 30:40.120 --> 30:42.300 I know that motion sickness 30:42.300 --> 30:44.080 is still going to affect people. 30:44.080 --> 30:45.400 The ergonomics are still there. 30:45.400 --> 30:46.900 We don't use controllers. 30:46.900 --> 30:48.820 This is a kind of like a big thing for us. 30:48.820 --> 30:50.980 We try to minimize the headset experience 30:50.980 --> 30:54.120 from to be controller free as much as possible, 30:54.120 --> 30:55.900 just using voice and vision 30:56.680 --> 30:59.320 to minimize that usage, the motion, 30:59.320 --> 31:01.480 the needing to learn how to menu, et cetera. 31:02.440 --> 31:06.360 But we believe that it's worth investing in this 31:06.360 --> 31:08.560 because we're watching the technology 31:08.560 --> 31:09.960 get better and better year over year. 31:10.120 --> 31:13.400 And we've been fortunate enough 31:13.400 --> 31:17.740 to see the AR glasses themselves develop 31:17.740 --> 31:21.020 that in about maybe five years, 31:21.020 --> 31:24.240 we won't even have a headset camera system anymore. 31:24.240 --> 31:27.580 We'll be optical see-through. 31:27.580 --> 31:30.940 They'll just be back to that glasses form factor. 31:30.940 --> 31:33.160 And so developing the system that can support that, 31:33.160 --> 31:34.600 I think is super critical 31:34.600 --> 31:37.340 rather than just building something specifically 31:37.340 --> 31:38.600 for the MetaQuest. 31:40.120 --> 31:41.620 Thank you. 31:41.620 --> 31:42.880 That was really interesting. 31:51.200 --> 31:52.820 Any final questions from the Rolls-Royce team 31:52.820 --> 31:53.820 or that's it? 31:56.880 --> 32:01.380 I think one last question from me would be that 32:03.820 --> 32:06.880 I think it goes back to the previous question I asked 32:06.880 --> 32:09.900 and then kind of following on to what Zohan asked about the headset. 32:10.120 --> 32:15.740 So with the element of training being done, 32:15.740 --> 32:20.580 I can see how the Quest can fulfill that. 32:20.580 --> 32:24.660 But to basically Mick's point about overlaying 32:24.660 --> 32:28.740 on an actual physical asset, 32:30.260 --> 32:34.660 then I'm assuming that's where it gets a lot more challenging 32:34.660 --> 32:38.980 using a Quest-like way because it's not a see-through. 32:40.120 --> 32:41.040 Right. 32:41.040 --> 32:43.160 So if I want to take something and overlay 32:43.160 --> 32:48.000 on an actual physical asset, how would that be achieved? 32:48.000 --> 32:48.500 Oh, no, no. 32:48.500 --> 32:49.960 That would work too. 32:49.960 --> 32:51.900 My credit or the thing I'm pointing out 32:51.900 --> 32:56.240 is that the MetaQuest uses the cameras as see-through. 32:56.240 --> 33:00.240 So there you can still, and actually I 33:00.240 --> 33:04.460 mean this is probably a greater question for people 33:04.460 --> 33:06.800 on an actual operational floor, if they 33:06.800 --> 33:10.080 can wear these video see-through devices, if that's, 33:10.120 --> 33:12.160 you know, fine with the headset, then yes, 33:12.160 --> 33:14.780 the overlay is 100% doable. 33:14.780 --> 33:17.200 The MetaQuest 3 does that perfectly. 33:17.200 --> 33:20.500 It's QR code tracking, works spot on. 33:20.500 --> 33:22.620 So that would work directly. 33:22.620 --> 33:27.280 But it's always this sort of point that there's still video. 33:27.280 --> 33:29.540 Like there's still a camera being re-rendered 33:29.540 --> 33:31.420 of your real world versus where we're 33:31.420 --> 33:35.660 headed in the next couple of years, which is just full optical. 33:35.660 --> 33:36.160 OK. 33:36.160 --> 33:37.280 Got it, got it. 33:37.280 --> 33:40.040 OK. 33:40.040 --> 33:40.840 That's it from me. 33:45.260 --> 33:48.660 Any final questions from the Rolls-Royce team? 33:52.340 --> 33:53.760 What about you guys? 33:53.760 --> 33:58.360 You guys have any questions for us, Malamud? 33:58.360 --> 33:59.160 So many. 33:59.160 --> 34:02.360 I want to save everybody's time. 34:02.360 --> 34:04.020 But I know because I really I would 34:04.020 --> 34:07.040 love to truly understand what this, you know, 34:07.040 --> 34:09.080 the training environment is like and especially 34:09.080 --> 34:11.200 what the working and operational environment. 34:11.200 --> 34:13.900 That's really where the tons of questions that I have, 34:13.900 --> 34:17.000 I want to know what tech you're using on the inside 34:17.000 --> 34:18.340 because we're developing everything 34:18.340 --> 34:21.840 to be agnostic to your tech. 34:21.840 --> 34:25.080 But that doesn't mean that it's not important, you know, 34:25.080 --> 34:27.140 how all of your trainers are interfacing 34:27.140 --> 34:29.940 with the different CAD technologies, ERP, 34:29.940 --> 34:31.580 MES technologies, et cetera. 34:31.580 --> 34:34.020 Like, you know, to understand that can better 34:34.020 --> 34:38.300 help us learn and develop exactly to your workflows. 34:38.300 --> 34:41.540 But those are very, very in the future. 34:41.540 --> 34:42.140 That's fine. 34:42.140 --> 34:44.300 I think at least we can give you an overview. 34:44.300 --> 34:44.800 Yeah. 34:44.800 --> 34:46.800 I can give you the what is the current state, 34:46.800 --> 34:50.800 and I can leave it to experts like Arianne and, well, 34:50.800 --> 34:52.300 pretty much everyone else on the call 34:52.300 --> 34:55.060 to see what future state we are looking at. 34:55.060 --> 34:57.680 But obviously, today, a lot of the training 34:57.680 --> 34:59.800 is done through three modalities. 34:59.800 --> 35:04.060 One of them is the standard paper, right? 35:04.060 --> 35:07.520 So we have procedural steps, what we're doing, 35:07.520 --> 35:08.220 right? 35:08.220 --> 35:10.460 We have different sections of the engine, 35:10.460 --> 35:13.460 which we call modules. 35:13.460 --> 35:16.220 So 01, 02, 03, 04, it's basically 35:16.220 --> 35:23.220 going from roughly front to back with a random 07 and 05 module. 35:23.220 --> 35:25.980 And each of those modules have instructions 35:25.980 --> 35:30.420 on how do we take it apart and put it back together. 35:30.420 --> 35:35.700 And this is all done as an instructional document. 35:35.700 --> 35:37.920 This is complemented by the. 35:38.220 --> 35:41.760 Official document, which we call the engine manuals, 35:41.760 --> 35:45.640 that list down this, which not during training, 35:45.640 --> 35:48.000 but during actual operations, the operator 35:48.000 --> 35:53.040 will refer to step one, check this bolt, step two, 35:53.040 --> 35:57.540 unbolt bolt number 5, 10, and all of that. 35:57.540 --> 36:02.640 Then there is an element of some videos and interactions 36:02.640 --> 36:05.340 on some of these procedures. 36:05.340 --> 36:08.220 And then finally, they go down to the real asset, 36:08.220 --> 36:09.960 and we have some training engines where 36:09.960 --> 36:14.340 they go through this over weeks on how do you physically 36:14.340 --> 36:18.100 do this dismantling and putting it back together, right? 36:18.100 --> 36:19.960 In terms of some of the tech, I'm 36:19.960 --> 36:22.160 not sure if anyone else in the call 36:22.160 --> 36:27.080 is able to elaborate a bit more that we are looking at. 36:27.080 --> 36:28.280 Anything specific? 36:33.980 --> 36:35.460 Not too much, Ariane. 36:35.460 --> 36:38.220 Anything that I guess we are quite, we are not 36:38.220 --> 36:41.220 like, you know, this is a specific tech or a hardware 36:41.220 --> 36:43.940 that we are looking down selected. 36:47.320 --> 36:49.400 I mean, we've got different training scenarios. 36:49.400 --> 36:51.540 So we obviously from very early career, 36:51.540 --> 36:56.420 so we've got apprentices coming in, they're getting trained. 36:56.420 --> 36:58.000 And the way they usually get trained 36:58.000 --> 37:01.720 is generic skills rather than doing a specific procedure. 37:01.720 --> 37:05.500 So they get trained on skills that then transferable. 37:05.500 --> 37:08.080 We're training customers, so we've got customer training 37:08.080 --> 37:11.020 center on specifics that come and help us. 37:11.020 --> 37:15.580 We train up our own people when things and procedures change. 37:15.580 --> 37:22.260 So there's a range of different trainings that we apply. 37:22.260 --> 37:23.860 And Raj, I'm not entirely sure if you 37:23.860 --> 37:25.720 had a specific training procedure in mind 37:25.720 --> 37:29.860 or if that's more general one or if you're doing the process 37:29.860 --> 37:31.360 here, if you don't select something. 37:31.360 --> 37:34.180 But we have different scenarios usually. 37:34.180 --> 37:34.780 Yeah. 37:34.780 --> 37:38.040 So to answer Ariane's question, and I'll 37:38.040 --> 37:40.180 also to make sure Malamud understands, 37:40.180 --> 37:42.960 I think, like Ariane said, for customer training, 37:42.960 --> 37:46.020 there are very specific ones because the customer is only 37:46.020 --> 37:48.480 allowed to do certain things. 37:48.480 --> 37:55.000 In my mind, so for example, if you have seen an engine, 37:55.000 --> 37:58.820 the fan blades, the rotating part that you can see, 37:58.820 --> 38:02.080 the customer is allowed to take that off and put that on. 38:02.080 --> 38:04.200 But if you go all the way down to things 38:04.200 --> 38:06.600 like the combustor, the hot end of the engine, 38:06.600 --> 38:08.040 that's not something that the customer 38:08.040 --> 38:11.220 does, so customer training focuses on that. 38:11.220 --> 38:13.920 And obviously, we have something called LRUs, 38:13.920 --> 38:19.140 line replaceable units, which is outside the engine 38:19.140 --> 38:21.120 where there is no airflow. 38:21.120 --> 38:25.320 You have things like the brain of the engine, the EEC, 38:25.320 --> 38:29.520 the fuel unit, the oil units, the gearboxes. 38:29.520 --> 38:33.220 So these are things that the customer is trained on. 38:33.220 --> 38:37.860 The scope of this is more about Rolls-Royce internal, where 38:37.860 --> 38:41.700 we take apart the entire engine and put it back together. 38:41.700 --> 38:45.420 Now obviously, the extended scope, 38:45.420 --> 38:49.100 it's very nice to have is for us to be providing this 38:49.100 --> 38:52.140 to our customers because then they 38:52.140 --> 38:55.200 can refresh it any time they want rather than depending 38:55.200 --> 38:55.980 on us. 38:55.980 --> 38:59.520 But I think the main scope is for our internal operators 38:59.520 --> 39:02.620 to know how to take apart a full engine 39:02.620 --> 39:04.140 and put it back together. 39:04.140 --> 39:07.860 But for the POC, I think that will be, 39:07.860 --> 39:09.320 of massive scope. 39:09.320 --> 39:12.300 So we will cut it down to, like I mentioned, a few modules. 39:12.300 --> 39:14.460 So we will pick a couple of modules 39:14.460 --> 39:18.180 and focus the POC on those specific modules. 39:18.180 --> 39:19.800 Yeah, no, that makes perfect sense. 39:19.800 --> 39:21.780 But it's good to see that future vision. 39:21.780 --> 39:25.700 I do also imagine you can just throw a kit at your customer 39:25.700 --> 39:29.240 as well so that they don't have to travel too far 39:29.240 --> 39:32.200 and move too much to give them, hopefully. 39:32.200 --> 39:33.640 Especially new customers. 39:33.640 --> 39:37.240 So if I get a new airline, so if American Airlines does not 39:37.240 --> 39:37.740 use engines. 39:37.740 --> 39:41.540 But they start using, even before they 39:41.540 --> 39:44.260 receive their first engine, we can send this kit out for them 39:44.260 --> 39:47.680 to have a feel so that when they come for the formal training, 39:47.680 --> 39:50.520 they are able to ask a lot more questions. 39:50.520 --> 39:54.160 So that is definitely a value add, we can say. 39:54.160 --> 39:55.940 Yeah, that's great. 39:55.940 --> 39:57.300 Thanks for that. 39:57.300 --> 39:59.240 It clears a lot of stuff up. 39:59.240 --> 39:59.860 I appreciate it. 40:04.420 --> 40:07.340 Hey. 40:07.340 --> 40:10.160 Thanks to update training materials today, 40:10.160 --> 40:15.960 such as when those modules were taking the engine apart. 40:15.960 --> 40:18.360 Do you guys frequently change what 40:18.360 --> 40:20.100 would be in the training material? 40:20.100 --> 40:22.880 What's that process like? 40:22.880 --> 40:27.380 We don't change the training material that often. 40:27.380 --> 40:34.820 However, what does happen is we have multiple engine types. 40:34.820 --> 40:37.140 They are called Trend XWB, Trend 1000. 40:37.140 --> 40:38.940 They go on different aircrafts. 40:38.940 --> 40:46.740 But for each engine type, so a Trend 1000 can have seven to nine variants 40:46.740 --> 40:48.900 with very subtle differences. 40:48.900 --> 40:54.420 Now, some of these differences are in terms of the type of parts used. 40:54.420 --> 40:56.700 That usually will not affect the training material, 40:56.700 --> 40:59.340 because it's just the QR code. 40:59.340 --> 41:05.280 But some of the subtle variances can be how the external harnesses or tubes 41:05.280 --> 41:06.520 are routed. 41:06.520 --> 41:12.940 If the internal harnesses are routed because of certain requirements, 41:12.940 --> 41:17.280 then in that case, the training material might be updated. 41:17.280 --> 41:22.280 But in general, especially, we are not using this solution 41:22.280 --> 41:27.760 as a replacement of current training methods, but as an augmentation. 41:27.760 --> 41:33.020 I wouldn't expect every single minute thing to be updated on this. 41:33.020 --> 41:35.220 Now, eventually, if we get there, that's brilliant. 41:35.220 --> 41:35.920 But it should. 41:35.920 --> 41:40.780 We have to really capture the baseline expectations 41:40.780 --> 41:44.700 for a baseline engine variant. 41:44.700 --> 41:45.200 Thank you. 41:52.560 --> 41:53.580 All right. 41:53.580 --> 41:57.680 I guess that's it from all the questions. 42:00.760 --> 42:03.340 All right, so thank you, everyone, for your time. 42:03.340 --> 42:05.560 Just wanted to quickly check also, Janelle, do you 42:05.560 --> 42:07.220 have any questions from Enterprise Singapore's end? 42:07.220 --> 42:15.200 Hi, nope, all good from my side. 42:15.200 --> 42:18.480 OK, thank you very much for everyone's time then. 42:18.480 --> 42:21.200 So just before I quickly end today's session, 42:21.200 --> 42:23.680 let me just do a very quick reminder. 42:23.680 --> 42:28.860 So again, a gentle reminder that we will need to submit two deliverables 42:28.860 --> 42:33.800 by 29th of June, Monday, 12 PM. 42:33.800 --> 42:34.760 Oh, yeah. 42:34.760 --> 42:35.260 12. 42:35.260 --> 42:36.920 Oh, it's 12 AM, basically midnight. 42:36.920 --> 42:40.380 So the first set of deliverable is a refined proposal 42:40.380 --> 42:43.840 slide deck of up to 20 slides following today's session itself. 42:43.840 --> 42:45.640 Please do add the information that's 42:45.640 --> 42:48.460 asked by Rolls-Royce into this slide deck itself, 42:48.460 --> 42:50.740 or further enhancements into this slide deck. 42:50.740 --> 42:53.440 Next, please do send your introductory two minutes 42:53.440 --> 42:57.580 video of your solution on how it best fits Rolls-Royce challenge 42:57.580 --> 42:59.500 statement also. 42:59.500 --> 43:01.540 So please do submit both deliverables 43:01.540 --> 43:03.380 onto the challenge platform. 43:03.380 --> 43:04.460 You can access it all via the challenge platform. 43:04.460 --> 43:09.380 Link by logging into your account and clicking on the MySpace button 43:09.380 --> 43:11.840 on the top right hand corner of the screen. 43:11.840 --> 43:15.600 So if there's nothing else, then thank you everyone so much for your time 43:15.600 --> 43:18.580 for joining today's clarification meeting. 43:18.580 --> 43:20.040 And that's it for me. 43:20.040 --> 43:21.040 Thank you and everyone. 43:21.040 --> 43:22.040 Have a nice day. 43:22.040 --> 43:23.040 Thanks, everyone. 43:23.040 --> 43:24.040 Thank you. 43:24.040 --> 43:25.040 Thank you. 43:25.040 --> 43:26.040 Thank you. 43:26.040 --> 43:27.040 Bye. 43:27.040 --> 43:27.140 Bye.