# Bridging the Gap to BVLOS Adoption with Enterprise-Ready Software

- Event: NestGen ’23
- Published: March 29, 2023
- Length: 40:01
- Watch: https://nestgen.org/library/watch/zXOL_DsDdcs/

> The transcript of a recorded NestGen session, for reading or for use with an AI tool. It comes from the video's
> captions; automatic captions can mishear names and terms.

## About this session

How to remove the complexities of managing multiple UIs for BVLOS drone ops? Enterprise Ready Software could be the answer. Attend to learn.

## Transcript

**[0:00]** questions okay so hello everyone welcome to one of the most informative sessions of national 23. so with the global emergence of drone autonomy this session will explore how to conduct baby allos operations the safety risk associated with it and the various methods for mitigating these risks we will also focus on how Cloud FlytNow our platform manages to seamlessly combine the existing drone Solutions and provide a comprehensive end-to-end solution for drone operations additionally we will also touch upon developer ecosystems that FlytNow provides and the ways in which it can Empower developers through sdk's help forums simulation tools Etc so let's dive in and learn more about how we can safely and efficiently conduct bblos flights using the latest Technologies and platforms so worry not to show you the way forward we have havishana more with us both lead

**[1:03]** product Engineers here at flightways joining us today has been around since the beginning of the Drone in a box or diab Solutions helping develop technology that makes the open Dia movement possible he's worked with multiple oems across the globe and has overseen various deployments for a range of use cases that being said I think it's safe to say that Havish understands the complexities that may arise while performing bblos operations and as for a MOG he's a graduate from IIT Bombay he's been crucial in the development of flight bases Robotics and web development team which is his expertise in multiple programming languages so okay before we jump into the session I need to share a few housekeeping rules so please type in your questions in the Q a tab of the session and it will be answered after the presentation this session is getting recorded and will be published soon and also there's going to be a poll in the chat so if please put in your votes there and last but not the least please remember to capture your favorite moments of the

**[2:04]** session and share it on Twitter or LinkedIn using the hashtag nestrip a few lucky people who share it might have a surprise in store so before we move on I just want to thank our sponsors so thank you DJI Enterprise who's our title sponsor and volatile Aerospace who's our Platinum sponsor so thank you for supporting us in this mission okay uh with that over to you guys thank you for the great intro let me just share my uh presentation and we can proceed so can you see it okay yes we can all right so hello guys and girls hope you're having a great time at National let's dive into the problem of Bridging the Gap to people's adoption with Enterprise City software so let us begin with why is like why are we even let's break down the terms right like big Wireless and autonomy autonomy and everything so the reliability and availability of resources while operating at scale is critical for Enterprise grown Solutions which are aimed at

**[3:04]** applications like regular inspections augmenting security but in Perimeter security kind of applications responding to emergencies like like uh augmenting the work that First Responders do and any Enterprise scale solution would involve a lot of Hardware it would involve a lot of software and so just imagine like if you had to train somebody and that person had to learn how to use various different type of Hardwares and softwares and they you would have to train a lot of people like that you would have to ensure that there are people acting as redundancy so that every time you have a requirement there is somebody to come and help you out this whole up this whole like system is not very scalable like it's not very easily scalable at least you would need a huge amount of people you would have need you would need to have a lot of training materials and resources to ensure that they even this large group of people are able to maintain a high degree of safety and still meet the needs of the application so in such situations it makes a lot of sense to automate as much of your of your solution as possible right so we believe that the most

**[4:04]** efficient way to scale large-scale Enterprise drone applications is through autonomy we cannot just keep adding visual observers for as the scale increases so for this uh we know that today with docking stations with all the presentations you have already seen and you will see that autonomy is now already a well realized dream due to documentations essentially you don't need anybody on the ground to help you manage the Drone like switched on switch off or change the batteries or anything you just need to deploy your docking station which does all of this for you and by using different kind of Ground Control stations like even FlytNow you're able to give missions and will elaborate the need for any kind of manual flight where somebody needs to hold an RCN fly but what we do need to do is that we need to transfer over the responsibilities and the Technologies of the visual Observer that he's performing on the site to something else like uh that something else is the technology that you need to build to to have your system actually be safely remotely operable right and we need to prove to Aviation

**[5:08]** Regulators that these Technologies can actually replace pilots on the ground and while matching if not increasing the safety of drone operations that is provided by pilots on the ground can you give us an idea of these responsibilities and the risks that uh to Baby loss yes uh thanks a lot Havish for providing us a quick introduction to what we are going to look into today and also a brief introduction on dvdos so right as I wish roughly mentioned uh baby loss operations are the future and there are three primary risk factors to any BB loss operation the first one arises from the vehicle itself so you might be using a drone different kinds of drones different kinds of docking stations probably some additional sensors Hardware Etc all of these inherently are risky you might have failures in drones you might have failures in docking stations and so on and so forth so that is one risk area that needs to be mitigated over the last year we have seen that through the emergence of

**[6:13]** various new docking station Partners so on and so forth we have had a lot of improvements in docking stations so right now there are systems that handle power failures there are multiple redundant systems in place with talking stations so that these failures can be mitigated similarly with drones we have now moved to Triple redundancy when it comes to various critical sensors such as IMU and so on and so forth so this is something that various uh kind of manufacturers in the ecosystem have been taken care of and have been working actively to mitigate this risk the next risk that we uh that is present when it comes to bvloss operations is the area of operation or the airspace within this so This the airspace was something that the visual observer in in vloss operations used to kind of man the visual Observer used to take care that there is no ad there is no uh kind of Rogue aircraft in the airspace or there isn't we don't

**[7:13]** have two aircraft sector on collision course so all of these things are now not possible without a visual Observer and hence this is one area where you need a lot of new technologies to come in so that these risks can be mitigated and BV loss operations can be realized another is that you need to look at is the operational risk itself this is where you need to look at things like are we following the correct checklist procedures before we launch a flight are we looking do we have the correct I'm sorry so when you look at operational risk you need to look at checklist you need to look at fail saves you need to look at whether your drones and are correctly configured Fields so that if there is a low battery drone can return back to the parking station so on and so forth so with all of this we now see that these with these three critical uh kind of ways posed by vvloss operations and to kind of do BV loss operations we need to have systems in place so that we can actively mitigate these risks

**[8:15]** if we can move ahead of which thank you right so looking at systems that can help mitigate airspace risks so with this we have had development in terms of UTM so UTM stands for you traffic management and in this you have various services like altitude Angel who are providing airspace data who are providing data for different aircrafts in your airspace and these can be used to have intelligent algorithms on top to kind of mitigate as base risks we have different sensors that are providing local airspace data systems that are also helping in this space systems like collision avoidance and the dynamic path planning using all of this when it comes to operational risk we are looking at various things such as weather alerts and weather fail saves so these things are helping us to make sure that your drones are not flying in harsh weather customizable checklists to make sure that you are having so everything that you need to check before keeping and launching a

**[9:17]** flight is being ensured these are helpful in making sure that if there is an internet disconnection or there's a connectivity loss the Drone is still doing the commanded Mission and you will still get getting reliable feedback alternate Landing sites to make sure that whenever if there is any situation or the incident your drone is able to correctly identify a safe landing spot in line there this does not this makes sure that there are no large scale incidents that take place during operations systems like parachutes these are the last line of defense when it comes to drones and if there is any sense of area anything that goes wrong you do have a parachute on the Drone so such kind of systems are really important to mitigate operational risk now that we have kind of seen what are the key uh kind of risks when it comes to PV loss and some technologies that are being used to mitigate them let's go back to Hafiz and kind of see why do we need a kind of full scale full stack solution and what is this whole stack solution going to be comprised of right so uh I'm guessing

**[10:24]** that many from our audience right now are people who have used drones who have used some of the technologies that was mentioned by amok in some way of format so for example you might have used flight radar or you must you might have used some other UTM application to just check on your phone or on your laptop once before you take your drone off and do your mission or you may have opened uh maybe even Google further services or some other web uh weather application to just figure out well if I'm going to fly today is it going to be safe is it going to be or is it going to be too windy is it going to be too rainy and such things right so let us say you did all of that for a particular customer's deployment where there was a specific use case and you figured out very well all the all these sub modules like the app that we're using to check whether the app that you're using to check for airspace and now you have a combination that you know okay I can use these four three or four modules to uh certificate to basically be sure that my flights are going to be safe and they are going to be left but the problem is this particular combination of your

**[11:26]** application of these modules are not going to uh not going to not going to be applicable everywhere neither are they going to be applicable everywhere there sometimes they're not even applicable for each of your use case why does that happen right so it happens because right now when operating in one particular country in one particular place in a one particular place you are uh you're you're making your systems work with the local regulations of that particular area right so the local according to the local regulations let us say you absolutely need to have a certain type of parachute so you ensure that your drone has that kind of parachute right uh you also might might realize that a particular service gives excellent UTM information to you in that area but then let us say you were contacted by a new customer to operate somewhere else you go there and you try to do the same kind of application but you suddenly realize that for some reason the UTM solution does not have enough enough radar you know sensors or something but it does not give you just as accurate enough information that different geographical area but some other application does give right similarly for weather some we have had custom we have

**[12:31]** had experience with customers who claim that one particular Weather Service works very well for them while some other customers claim that a different Weather Service works very well for that now this might be due to sensitive density sensor density of different weathers whether detecting systems or whatever but the thing is the modules that you are using to build up the full stack solution stack is not exact uh it's not going to be uh applicable everywhere now let us say if you were to change your application if you were to change your application to uh initially you were doing something like security Public Safety and now you want to do something like inspection so when you are doing Public Safety and Security you needed a payload that had thermal uh the health capacity to carry a thermal camera it had speakers it has it had lights and such but when you want to go for an inspection application you need the payload to be a camera which has high quality RGB it has again baby thermal uh thermal cameras and uh yeah so the application is also basically changing the stack now the problem is think about managing all of these various modules right

**[13:37]** every module has now its own different dashboard every module has a different way of accessing that data and now you have let us say in your hand a checklist like amok mentioned in which you want to see a check every one of these things before you fly it's ridiculous difficult to manage now imagine just taking all of that information that you have gained and transferring it to five different people and imagine how many how well are they going to execute the same things how what things they might miss what things they might not miss right so currently we have a ecosystem which provides various individual modules and they are all designed for specific use cases what we need to realize next uh is that like I said you have already figured out the full stack combination which to deploy in a particular geography for a particular application now let's talk about the problems like I just mentioned a few of them as to that stack not being scalable and also with the problems in training that to other people now imagine some of those problems are resolved but now you have that stack but in that stack

**[14:37]** for some reason you need to change the type of parachute you use or maybe you need to change the type of drone you use because of something else ideally what you want to do is just plug out that particular component and bring in some other component and nothing else has to change fourth is you need a platform which is which has proper D marketed layers which is modular where it is very clearly defined as to where this these kind of modules fit in and what and what way they exactly behave if you do not have such layers let us say you were to just replace a parachute but the way the power should communicates is totally different or the way it operates is totally different now you have to modify the whole stack to just make to just fit something new right so this is a so you need a platform where it is able to you know diffuse uh it has layers where it's able to bring these modules together so FlytNow is the glue that kind of holds it all together it's a modular platform and it has like defined the rules of communication between the different module layers and because of that the models can swapped in and out and

**[15:41]** these layers clearly distribute the responsibilities and whatever modules exist in a particular layer diff uh you know behave a certain way so it is predictable because of this predictability we can make it reliable for example Flight OS and Doc OS you might have have heard of this before but Flight OS is like a drone agnostic solution which can work with DJI at Rooms APM PX4 drones but it works with FlytNow dashboard so it doesn't matter which drone that you use if you give a mission flight no dashboard it is going to delete either of those type of drone Supply similarly on the FlytNow dashboard if you were to use uh you know you were to give the command to open a talking station now it does not matter if you're using the hextronics box or from one from iitpi or eye deployer or one from the box is going to open because the layers are clearly demarcated you don't need to change the whole software just to make a new box work for you now these layers they all happen through standardized info interfaces they have they happen to be specified communication protocols so it let's go into a little bit more depth because this is kind of very important and

**[16:41]** ammo will explain how flightout is this uh but just before we do that ammo can you tell us about how operational workflows and modules come together like it's not just necessary to have an integration of all the modules you how and why is it necessary that they're part of your workflow right uh thanks a lot I wish for taking this forward um right so as service already mentioned uh I think we are pretty clear on the fact that we do need a lot of modules and it is it is already challenging enough to have all of these modules integrated into a single platform and all of them work seamlessly together however when we look at individual modules they by themselves are not capable of kind of mitigating the BB loss risks that we need them to do for example if we take a specific Weather Service you would need that service to be tightly integrated with the service that is planning your missions that is executing your flights so that if the weather service is able to detect then okay now we have harsh weather outside it's snowing and the Drone cannot fly you do not want the

**[17:45]** Drone to take off so these kind of intelligent workflows are required so that all of these different modules can come together and then they can mitigate the PV loss risk that we want them to do for this FlytNow has carefully built its architecture so that it can enable you with a plug-and-play system it also has a lot of intelligent workflows and lot of Enterprise Integrations so that a lot of the risks that are there with BB laws can be mitigated using FlytNow and FlytNow can also help you with an Enterprise level applications yeah so looking at the high level architecture diagram for FlytNow and how flight now has kind of pieced all of these different modules together so that while they work seamlessly they are also you can also able to quickly kind of plug one in plug one out replace one of these modules and still have your full stack functioning so while we look at this FlytNow essentially works on the hardware layer so we

**[18:46]** have different Hardwares where they have drones docking stations which make up the DIA systems these come with different payloads such as cameras speakers spotlights different kind of grippers which are used in Delivery Solutions or you might have some kind of cash sensors so drones might deploy cash sensors for crowd control and so there are a large variety of these payloads along with the dib system that makes up the hardware layer on top of this Hardware layer sits the entire FlytNow platform the FlytNow platform in communicates with these Hardware layers through the Integrations which is through standardized interfaces as I wish already mentioned you have flight over as stock OS to interact with the drones and the docking station similarly we have separate interfaces that communicate with lot of people with lot of the modules contributing to PV loss enablers such as different UTM providers such as different adsb receivers different weather services so all of these again interact with the FlytNow platform through standardized interfaces and through fixed communication protocols

**[19:50]** so this capability allows FlytNow to kind of plug and play with these different PV loss enablers data processing units as well as drones docking stations payloads you might just replace one of them put another in and since all of these are abstracted they work seamlessly with right now on top of these layers FlytNow provides a lot of intelligence workflows such as fail safes so FlytNow will have configurable fail safe so that let us say your drone suffers a low battery incident it is able to quickly return to the docking station you have pre-flight approvals so once you kind of integrate let us say UTM service so FlytNow with FlytNow you will be able to automatically file your pre-flight plans and then gain approvals which can be please return back to the last line thank you yeah with this you will also have things like configurable checklists and more of such intelligent modules with this FlytNow also takes care of being of security

**[20:51]** and reliability of the entire platform through Enterprise grade authentication Access Control Data encryption and various other things on top of this like at right now we have realized that the key power that will come with this platform will come through our developer tools these developer tools such as our sdks our open apis they will make sure they help other developers to come and contribute to the right now platform and this right so now that we have seen a look at this stack and how on top of this you have very vertical specific apps again built using these developer tools and other Enterprise Integrations now what we'll do is we'll take a quick look at some of the key features in FlytNow that are enabling baby loss okay right so coming to airspace awareness where we at FlytNow have integrated a integrated altitude engine as a UTM provider so with altitude Angel you can file

**[21:52]** pre-flight plans directly through the dashboard of the single click of the button with sensors such as cassia G which are local debt which are local detect and avoid sensors you can get warnings when a specific aircraft or a rogue aircraft has come in your in the vicinity of your airspace so with these Technologies you are able to kind of very easily demonstrate that you have replaced a visual Observer and now BB loss can be the very next step in your operation next we will look at a lot of weather services that have been integrated in FlytNow so with flight knob also provides you intelligent workflows with Weather Services with in the in the form of whether fail safes so these weather services are now integrated into your mission management so once let us say whether service is able to detect that now you have harsh weather going in the weather failsafe will automatically trigger get the Drone back if the Drone is flying will not allow the Drone to fly if it is still inside the dock and all of

**[22:55]** these intelligent workflows now make sure that your operations are safe and you are mitigating risk that are that you do better once we move next we can see that right now has also integrated with with parachutes so drones that are that have parachutes integrated on them you can directly remotely trigger these parachutes from the dashboard you can monitor your parachute you can make sure that your parachute is healthy your parachutes are all online and are ready in case there is an incident with the Drone so these kind of Integrations with FlytNow and again on FlytNow with different intelligent workflows around these Integrations make sure that you are actually running a tight shape you are running safe operations lastly we will look at two key modules in FlytNow which are part of the core platform at FlytNow one of them is the ability to configure no-fly zones with no

**[23:56]** fly zones users are able to configure their airspace to make sure that drones are not entering at the restricted ad space and operators are able to comply with local airspace restrictions so many a times when you fly you might have seen that there are space restrictions around airports sometimes airspace restrictions might dynamically come up if there is any specific event that is going to takes place let's say so with these things and with FlytNow you have the ability to configure all of these no-fly zones and have Dynamic path planning along these no fly zones you can also configure geofences on the FlytNow dashboard with this you are able to restrict the area in which the Drone can fly make sure that it is always in vicinity of the operational area that you are allowed to fly to with both of these modules and you have got a complete configurability of your operational area such of such things are really key when it comes to ensuring that vocabulary doing an entire safe right and safe operation

**[24:56]** thanks so with this I think what we'll need we'll move to Havish again and we'll have a look at how FlytNow is adding modules that will bootstrap PV loss and help with everyone get healthy operations getting the Las Vegas right so one of the most common uh you know think that thing that we hear when we talk to talk to customers and potential customers as to why have they not already begun with BB loss operations is that it's a kind of a chicken and egg problem right so you need to show evidence that all of your operations are safe to get a BBL waiver but then most people don't start any operations until they get a BV loss waiver so then how do you show the evidence right so the solution to this and what we uh suggest to most people is that start your operations with a visual Observer but make the visual Observer as random as possible right so just let the person stand there for maybe a few months like that the amount of the duration that is

**[25:58]** required to to gather enough evidence while everything is run remotely is everything is run autonomously let the person be on the secondary RC or the you know these the binary RC the secondary RC just in case something goes wrong while you do operations and all of these operations will generate data they will generate data as to how much you have flown where you have you where you have flown and this evidence can be used and presented to regularity authorities to show that yes our BB loss operations are safe because for this duration we have we have had a visual Observer and this is how independently our systems could operate so along these lines one of the main things that FlytNow helps with is by uh generating FlytNow logs and reports so on these right now logs and reports we can see things like when was a failsafe triggered what action was taken when a field trip was triggered if uh if manual control is required then what happened then when was manual control taken what was it used to do and there's also features like you can play back the path of the whole

**[27:04]** drone as it goes through uh its Mission you can uh also see all the videos and photos it collected right so this can coherently give you evidence of how your drone is operating and how did it handle emergency situations this helps build confidence with TV loss authorities that yes their operations are safe and if they are able to do this much safe operations with the visual Observer it is not going to make so much of a difference but it's removed from the picture so that's how you can apply for bvloss waivers uh right so let us talk about so right uh until now we have talked about the reliability of the hardware that we are using the drones uh the docking stations and we are accounting for things like whether we are accounting for things like other aircrafts in the airspace let us now talk about the reliability and security of FlytNow itself right so right now being such a big part of the developers drone Enterprise applications there are three pillars on which our liability is based on so one is Fault tolerance second is monitoring and third is incidence response so

**[28:06]** fault on tolerance is where we have multiple redundancies we have failovers to uh handle any issues that might come up when those issues come up we have very robust monitoring systems to immediately raise it to the technical team so that they can take a look in and see what's happening while they are responding to this these incidents we are also communicating the status of the incidents and the issues very clearly to our customers and our partners so they are aware of what's happening this builds a reliable uh this makes the whole platform reliable and increases trust with anybody who is using FlytNow their experience with FlytNow is something that is trustworthy when it comes to security again there are three major pillars that it is built on which is like infrastructure access and data so when we say access security what we mean is basically authentication so it's an Enterprise uh solution so you have single sign-on to uh you know get into uh FlytNow and there's Access Control to manage

**[29:08]** who can fly certain drones who cannot so like for example people with on only with only people who have proper licenses can you know start start a mission with a drone others cannot uh people who do not have access to certain resources are not given so that is how Access Control kind of ensures that authorized people can only use certain resources we have data privacy to keep your data isolated and protected from anybody who does not want to see or who wants to see what you're doing for example uh we have all the data goes into uh S3 and these other cloud and bucket Services those are all predicted that those can only be viewed by you who generated the data and lastly we need to talk about a developer ecosystem so the Drone automation industry is still growing Innovation is still happening at breaking speed so every use case doesn't have a ready built module for it right now for every possible geography so even if this motives become available like for example there's a UTM uh

**[30:10]** available for every corner of the Earth right now it is not possible for the flight now team to integrate all of these ourselves and what we need is a way to let people do this integration themselves so that is where the developer ecosystem comes into play right so people developers who are outside of light now they can use our apis tag they can use the simulators they can use our tools to integrate their own modules into into the FlytNow platform without necessary relief right now uh the engineering team right now stepping up together this is the only way to scale uh scale uh Integrations and also to make open div such a huge success otherwise it would all be concentrated so for example take Android right so so many people make apps on Android it's not like only Google make apps on Android because of that Android is such a widespread uh accepted and used platform similarly that's how FlytNow platform also needs to be treated uh so I think we're at the end of our

**[31:13]** session uh flight uh so among this has been a very long and heavy session for everybody I believe can you summarize this in a few short points for everyone right uh I think uh some of the key takeaways from this session are definitely that we initially looked at how BB loss regulations do vary with geography they vary as different modules need to be deployed based on where we intend to deploy and the type of application that we need to serve a FlytNow as a solution is unique in terms of that it enables you to mix and match these modules and create a full stack solution that is suitable for a specific application in a specific geography so that is something that we looked at next we see we also saw that how FlytNow is able to provide a lot of customizable workflows and lot of intelligent kind of modules on top of these basic Integrations that cut across different PV loss providers different modules that are used to mitigate safety risks and also serve specific use cases and lastly we saw how flight

**[32:18]** now is automating data collection and it is record it is kind of providing you a platform from where you can do a lot of tests and finally do a lot of operational evidence and build a strong safety case for your VV loss waiver application so with these four points I think I'd like to leave the audience with as part of the end of a session and over to you Natasha for the next one thank you thank you thank you for sharing these insights so looking to scale their baby loss operations um so yeah let's jump in let's go to the let's open the house for a round of q a so uh I see a lot of people have asked questions so I'm just gonna throw them at you about um right okay so okay so Mike Gilly asked how open of a system is your software solution that you are developing I heard amok mention about an open API every time a new drone or a new

**[33:21]** camera or a new sensor type is introduced it seems like there'll be an onus on a manufacturer or FlytNow how are you future proofing this system so that the customer investment in software and drones will be usable for a long period of time yeah I'll take this up so thank you for asking this question and uh what we are doing here is through a lot of these uniform interfaces so for drones we have our own Flight OS program which works on top of different industry accepted autopilots at this point which is PX4 autopilot or the DJI autopilot so if you have any if you have a custom drone which is either using a PX4 or an autopilot or using a DJI drone Flight OS will be able to seamlessly integrate with that and then it will enable the entire deep right now stack on top so and through all of these interfaces we are kind of future proofing the platform as well so let

**[34:21]** us say tomorrow you have a new type of an autopilot the only layer that needs to change in the entire flight entire flight based stack is the Flight OS layer so that is how we make sure that it is the entire setup is modular and that only minor modifications that are needed and the entire stack is now available with the new configuration um all right there's another question from Amit is lidar in discussion to scan the surroundings so Amit that's an interesting question right so what we are talking about here is integrating a new sensor which brings in data like from a lidar to flight node for some kind of I'm guessing post processing operation where you want to maybe map something you want to uh I think lighters are mostly used for mapping uh are you if there is another application of Lighters I believe is for collision avoidance and obstacle detection right so yes these kind of Technologies can also be integrated to FlytNow we

**[35:24]** haven't done it right now but like amok said we have the interfaces ready where we should be able to bring in the sensor data and also show whatever is required on the dashboard so that there is complete visibility of the system right thanks thanks um all right another one could you please tell us what Integrations and features FlytNow offers which can help enable BB laws operation safely so uh right as we saw in the session as well uh basically what FlytNow offers is some internal features that are very core to the platform such as Geo fencing no-fly zones and as well as lot of Integrations with different providers such as provide us for track for utms providers for parachute Integrations you might have different uh manufacturers who are generated who are making sensors for let's say detect and avoid systems for the Drone so FlytNow is able to integrate with them

**[36:27]** as well and through all of these we are able to kind of create a singular platform where you can mitigate all of these DV loss risks and kind of scale up your applications and have large scale bvloss operations for your application thanks a lot all right there's another one how many users can your live video stream support in a one is to end setup with a stream from the Drone and multiple viewers also does your system provide a capability for the users to interact with each other through video call during the live drone session I wish you want to take this yes sure so uh the way our system is built is you should be you able to open the FlytNow dashboard on National devices as you want so as many people as required should be able to see the video feed and the Drone of a video feed of the Drone that is currently performing its operation that's the answer to the first question the answer to the second question where you want to know if there is any uh

**[37:31]** intercommunication capability within the dashboard we currently don't have that built in we do not we currently don't have a road to town or a roadmap but if let us say we find that it we find that it's a very important uh module for bblance and automation of systems then it would be probably picked up great thanks okay I think let's close with one last question um let me see I see okay what uh how are runaway drone situations handled right so uh runaway drones I think is something that is uh really become something of the past right now we've not really had much incidents with runaway drones recently but uh right if some if that is indeed a possibility with let's say a specific drone or something then we would have probably work with the Drone manufacturers work with others in the ecosystem and then again as through our

**[38:33]** Integrations through our plugins we would have systems in place to make sure that if such a situation even occurs you might have failed safes too let's say kill the motors have a parachute deployed and retrieve the Drone so these kind of workflows can be built on top and again through the FlytNow platform and through the open apis uh all of this customizability can be easily done so said you would have the button to deploy the parachute the buttons which deploy the parachute automatically kill kill the motors so the Drone would not move too far from its last position and if it is actually flying away it should still be able to deploy the parachute and like you saw in the presentation with flight logs where you can actually track the location of the Drone in uh in the logs of the Drone you should also be able to retrieve it is what we would have to say regarding runaway drones but yes it is actually becoming uh more rare and rare appearance these days with the development with any with all the new developments in drone technology

**[39:37]** great great all right I think let's uh wrap up now thank you for sharing these insights um I'm sure uh this definitely helps us see the path forward to adoption of baby loss operations so thank you thank you everybody for joining today I hope everyone's learned something worthwhile and uh right let's close thank you thank you everyone thanks a lot thank you everyone bye