Category Archives: Humanitarian Technologies

How To Coordinate UAV Deployments During Disasters

My team and I at WeRobotics are partnering with the World Food Program (WFP) to develop practical coordination mechanisms for UAV deployments in collaboration. These will be developed with a range of national & local partners. In this post I want to share the basic coordination protocols we used in the aftermath of Cyclone Pam, a category 5 cyclone that devastated the islands of Vanuatu in 2015. By “we” I mean myself, the World Bank and two UAV companies from Australia (Heliwest) and New Zealand (X-Craft).

The World Bank tasked me with spearheading the UAV response to Cyclone Pam so I recruited the two companies to carry out the aerial surveys. I selected them from a dozen groups that had registered with the Humanitarian UAV Network (UAViators) Global Pilot Roster. When we landed at the international airport in Port Vila, we saw a very common scene. Military cargo aircraft filled with food, water and other relief items. Helicopters were also being chartered to support the relief efforts. And commercial aircrafts like the one that had taken us to Vanuatu were also flying in and out on a daily basis.

We clearly needed to develop coordination mechanisms that would allow us to fly our UAVs in this relatively complex airspace. So within an hour of landing in Port Vila, I organized a joint meeting with the Government of Vanuatu, Air Traffic Control (ATC), World Bank, Australian Defense Force, New Zealand Defense Force and the two UAV companies. By the end of the 1-hour meeting we had agreed on a clear set of coordination protocols that would enable us to fly our UAVs safely in non-segregated airspace. And it wasn’t rocket science.

At 22:00 every night, we would email the Australian Defense Force (ADF) our flight plans for the following day. An example of such a plan is pictured above. By 23:00, the ADF would respond with a yes/no. (They said yes to all our plans). At 23:00, we would email our approved flight plans to controllers at ATC and start programming the UAV flights. We’d get a few hours of sleep and head back when it was still dark to reach the survey sites as early as possible. This was also true for areas near the airport since we could only fly our UAVs between 6am-8am based on the agreed protocols.

Once on site, we’d set up the UAVs and go through our regular check-lists to ensure they were calibrated, tested and ready to fly. Before take off, we would call ATC (we had the mobile phone numbers of 2 ATC operators) and proceed as follows:

“Hello ATC, this is the World Bank UAV Team. We are on site in [name of location] for flight number [x] and ready for takeoff. Do we have your permission?” 

After verbal confirmation, we would launch our UAVs and carry out the aerial survey. We flew below 400 feet (per UAV regulations) and never, ever strayed from our approved flight plan. The Civil Aviation Authority of Vanuatu had given us permission to fly Extended Line of Site, which meant we could fly beyond visual line of site as long as we could keep an eye on general airspace where our UAV was operating. After landing the UAV, we would call ATC back:

“Hello ATC, this is the World Bank UAV Team. We have just landed the UAV in [name of location] and have completed flight number [x]. Thanks.” 

Simple and yet highly effective for the context at hand. We had the mandate, all the right contacts and we everyone followed the coordination protocols. But this is just a subset of protocols required for coordinating UAV flights. There are other components such as data-sharing workflows that need to be in place well before a disaster. What’s more, in the case of Cyclone Pam, we were working with only two professional UAV teams in a Small Island State. Just weeks after Cyclone Pam, a devastating 8.0 magnitude earthquake struck Nepal. The situation there was a lot more complex with at least 15 UAV teams self-deploying to the country.

The UN Office for the Coordination of Humanitarian Affairs (OCHA) in Nepal formally asked me to coordinate these teams, which turned out to be quite the nightmare. The Civil Aviation Authority of Nepal (CAAN) did not have the capacity or expertise to partner with us in coordinating UAV flights. Nor did UNDAC. Many of the self-deployed UAV teams had never worked in disaster response before let alone in a developing country. So they had no idea how to actually support  or plug into formal relief efforts.

While most of UAV teams blamed connectivity issues (slow and intermittent email/phone access) for being unable to follow our coordination efforts online, several of them had no problem live-tweeting pictures of their UAVs. So I teamed up with LinkedIn For Good to developed a very simple Twitter-based coordination system overnight. UAV teams could now tweet their flight plans which would get automatically added to an online map and database. The UAV teams kept tweeting but not a single one bothered to tweet their plan.

To say this was problematic is an understatement. When organizations like WFP are using manned aircraft and helicopters to deliver urgent relief supplies to affected communities, they and ATC need to know which UAVs are flying where, how high and when. This is also true of Search and Rescue (SaR) teams that often fly their helicopters at low altitudes. In due course, we’ll have transponders to track UAVs in real-time. But safety is not the only consideration here. There is also a question of efficiency. It turns out that several UAV teams in Nepal carried out aerial surveys of the exact same areas, which is hardly optimal.

So I applaud the WFP for their important leadership on this matter and look forward to working with them and in-country stakeholders to develop practical coordination mechanisms. In the meantime, WeRobotics has set up Nepal Flying Labs to build local capacity around the use of UAVs and enable local responders to use UAVs safely, responsibly and effectively. All of our Flying Labs will adopt the resulting coordination mechanisms developed with WFP and stakeholders. 

Cargo Drones Deliver in the Amazon Rainforest

Cross-posted from WeRobotics

The Amazon is home to thousands of local indigenous communities spread across very remote areas. As a result, these sparsely populated communities rarely have reliable access to essential medicines and public health services. Local doctors in the region of Contamana report an average of 45 snakebites per month and no rapid access to antivenom, for example. We recently traveled to the rainforest to learn more about these challenges, and to explore whether cargo drones (UAVs) could realistically be used to overcome some of these problems in a sustainable manner. We’re excited to share the results of our latest field tests in this new report (PDF); Spanish version here. For high-resolution photos of the field tests, please follow this link. Videos below.

F8. Frankie 8

Our cargo drone flights were carried out in collaboration with the Peruvian Ministry of Health and local doctors. The field-tests themselves were coordinated by our local WeRobotics lab: Peru Flying Labs. Anti-venom was flown from the town of Contamana to the more remote village of Pampa Hermosa about 40 kilometers away. A regular boat (canoe) takes up to 6 hours to complete the journey. Our drone took around 35 minutes.

At night, we flew the drone back to Contamana with blood samples. While cargo drone projects typically use very expensive technology, WeRobotics prefers to use affordable and locally repairable solutions instead. Behind the scenes footage of the actual cargo drone flown in the Amazon is available in the video below.

Thanks to the success of our first drone deliveries, we’ve been invited back by the Ministry of Health and local doctors to carry out additional field tests. This explains why our Peru Flying Labs team is back in the Amazon this very week to carry out additional drone deliveries. We’re also gearing up to carry out deliveries across a distance of more than 100km using affordable drones. In parallel, we’re also working on this innovative Zika-control project with our Peru Flying Labs; drawing on lessons learned from our work in the Amazon Rainforest.

We’ll be giving a free Webinar presentation on all our efforts in Peru on Wednesday, February 22nd at 11am New York time / 4pm London. Please join our email-list for more information.

PeruDec16-0525-IMG_8379 (1)

To support our local Flying Labs teams in Peru, Nepal and/or Tanzania with donations, kindly contact Peter Mosur (peter@werobotics.org). For media inquiries on the Amazon Rainforest project and WeRobotics, please contact Dr. Patrick Meier (patrick@werobotics). Ministry of Health officials and other local partners are also available for interviews.


About WeRobotics

The mission of WeRobotics is to scale the positive impact of social good projects through the use of appropriate robotics solutions. We do this by creating robotics labs (Flying Labs) that transfer professional skills and robotics solutions locally. We have Flying Labs in Asia (Nepal), Africa (Tanzania), and South America (Peru). WeRobotics is funded by the Rockefeller Foundation, which enabled the recent project in the Amazon rain-forest with our Peru Flying Labs.

First Ever Cargo Drone Deliveries in Amazon Rainforest

Cross-posted from WeRobotics

The Amazon is home to thousands of local indigenous communities spread across very remote areas. As a result, these sparsely populated communities rarely have reliable access to essential medicines and public health services. Local doctors in the region report an average of 45 snakebites per month and no rapid access to anti-venom meds, for example. We recently traveled to the rainforest to learn more about these challenges and to explore whether cargo drones (UAVs) could realistically be used to overcome some of these challenges in a sustainable manner. We’re excited to share that our cargo drone flights in the Amazon rainforest were a big success!

pic-1

This unique and successful pilot project was a big team effort including our Peru Flying Labs Coordinator Juan Bergelund, UAV del Peru and the Peruvian Ministry of Health along with some of Peru’s leading public health experts. We carried out both day and night autonomous flights between local health hub Contamana and the remote village of Pampa Hermosa around 40 kilometers away. The drones delivered life-saving anti-venom medicines as well as blood samples. The flights took around 35 minutes compared to traditional riverboat transportation, which can take up to 6 hours.

pic-2
We have already been asked by multiple local authorities in the region to carry out additional flights in coming months. These flights will test the aerial delivery of medical supplies across 100+ kilometers. A detailed review of our recent flight tests will be released in early January along with high definition pictures and videos. Our Peru Flying Labs will also be working on this Zika reduction project in Peru using cargo drones. For media enquiries, please contact Dr. Patrick Meier (patrick@werobotics) and Juan Bergelund (juan@werobotics). Ministry of Health officials and other partners are also available for interviews.

pic-3

In the meantime, we wish to sincerely thank all our outstanding partners and colleagues in Peru for their invaluable support and partnership over the past two weeks. We are very excited to continue our good work together in coming months and years.


About WeRobotics

The mission of WeRobotics is to scale the positive impact of social good projects through the use of appropriate robotics solutions. We do this by creating robotics labs (Flying Labs) that transfer professional skills and robotics solutions locally. We have Flying Labs in Asia (Nepal), Africa (Tanzania) and South America (Peru). WeRobotics is funded by the Rockefeller Foundation, which enabled the recent project in the Amazon rainforest with our Peru Flying Labs.

The Most Comprehensive Study on Drones in Humanitarian Action

In August 2015, the Swiss humanitarian organization FSD kindly hired me as a consultant to work on the EU-funded Drones in Humanitarian Action program. I had the pleasure of working closely with FSD and team during the past 16 months. Today represents the exciting culmination of a lot of hard work by many dedicated individuals.

Today we’re launching our comprehensive report on “Drones in Humanitarian Action: A Guide to the Use of Airborne Systems in Humanitarian Crises.” The full report is available here (PDF). Our study draws on extensive research and many, many consultations carried out over a year and a half. The report covers the principle actors & technologies along with key applications and case studies on both mapping and cargo drones. Note that the section on cargo delivery is drawn from a larger 20+ page study I carried out. Please contact me directly if you’d like a copy of this more detailed study. In the meantime, I want to sincerely thank my fellow co-authors Denise Soesilo, Audrey Lessard-Fontaine, Jessica Du Plessis & Christina Stuhlberger for this productive and meaningful collaboration.

screenshot-2016-12-02-09-03-23

The report and case studies are also available on the FSD Website.

Reverse Robotics: A Brief Thought Experiment

Imagine a world in which manually controlled technologies simply do not exist. The very thought of manual technologies is, in actual fact, hardly conceivable let alone comprehensible. Instead, this seemingly alien world is seamlessly powered by intelligent and autonomous robotics systems. Lets call this world Planet AI.

PlanetAI

Planet AI’s version of airplanes, cars, trains and ships are completely unmanned. That is, they are fully autonomous—a silent symphony of large and small robots waltzing around with no conductor in sight. On one fateful night, a young PhD student awakens in a sweat unable to breathe, momentarily. The nightmare: all the swirling robots of Planet AI were no longer autonomous. Each of them had to be told exactly what to do by the Planet’s inhabitants. Madness.

She couldn’t go back to sleep. The thought of having to tell her robotics transport unit (RTU) in the morning how to get from her studio to the university gave her a panic attack. She would inevitably get lost or worse yet crash, maybe even hurt someone. She’d need weeks of practice to manually control her RTU. And even if she could somehow master manual steering, she wouldn’t be able to steer and work on her dissertation at the same time during the 36-minute drive. What’s more, that drive would easily become a 100-minute drive since there’s no way she would manually steer the RTU at 100 kilometers an hour—the standard autonomous speed of RTUs; more like 30km/h.

And what about the other eight billion inhabits of Planet AI? The thought of having billions of manually controlled RTUs flying, driving & swimming through the massive metropolis of New AI was surely the ultimate horror story. Indeed, civilization would inevitably come to an end. Millions would die in horrific RTU collisions. Transportation would slow to a crawl before collapsing. And the many billions of hours spent working, resting or playing in automated RTU’s every day would quickly evaporate into billions of hours of total stress and anxiety. The Planet’s Global GDP would free fall. RTU’s carrying essential cargo automatically from one side of the planet to the other would need to be steered manually. Where would those millions of jobs require such extensive manual labor come from? Who in their right mind would even want to take such a dangerous and dull assignment? Who would provide the training and certification? And who in the world would be able to pay for all the salaries anyway?

At this point, the PhD student was on her feet. “Call RTU,” she instructed her personal AI assistant. An RTU swung by while she as putting on her shoes on. Good, so far so good, she told herself. She got in slowly and carefully, studying the RTU’s behavior suspiciously. No, she thought to herself, nothing out of the ordinary here either. It was just a bad dream. The RTU’s soft purring power source put her at ease, she had always enjoyed the RTU’s calming sound. For the first time since she awoke from her horrible nightmare, she started to breathe more easily. She took an extra deep and long breath.

starfleet

The RTU was already waltzing with ease at 100km per hour through the metropolis, the speed barely noticeable from inside the cocoon. Forty-six, forty-seven and forty-eight; she was counting the number of other RTU’s that were speeding right alongside her’s, below and above as well. She arrived on campus in 35 minutes and 48 seconds—exactly the time it had taken the RTU during her 372 earlier rides. She breathed a deep sigh of relief and said “Home Please.” It was just past 3am and she definitely needed more sleep.

She thought of her fiancée on the way home. What would she think about her crazy nightmare given her work in the humanitarian space? Oh no. Her heart began to race again. Just imagine the impact that manually steered RTUs would have on humanitarian efforts. Talk about a total horror story. Life-saving aid, essential medicines, food, water, shelter; each of these would have to be trans-ported manually to disaster-affected communities. The logistics would be near impossible to manage manually. Everything would grind and collapse to a halt. Damage assessments would have to be carried manually as well, by somehow steering hundreds of robotics data units (RDU’s) to collect data on affected areas. Goodness, it would take days if not weeks to assess disaster damage. Those in need would be left stranded. “Call Fiancée,” she instructed, shivering at the thought of her fiancée having to carry out her important life-saving relief work entirely manually.


The point of this story and thought experiment? While some on Planet Earth may find the notion of autonomous robotics system insane and worry about accidents, it is worth noting that a future world like Planet AI would feel exactly the same way with respect to our manually controlled technologies. Over 80% of airplane accidents are due to human pilot error and 90% of car accidents are the result of human driver error. Our PhD student on Planet AI would describe our use of manually controlled technologies a suicidal, not to mention a massive waste of precious human time.

Screen Shot 2016-07-07 at 11.11.08 AM

An average person in the US spends 101 minutes per day driving (which totals to more than 4 years in their life time). There are 214 million licensed car drivers in the US. This means that over 360 million hours of human time in the US alone is spent manually steering a car from point A to point B every day. This results in more than 30,000 people killed per year. And again, that’s just for the US. There are over 1 billion manually controlled motor vehicles on Earth. Imagine what we could achieve with an additional billion hours every day if we had Planet AI’s autonomous systems to free up this massive cognitive surplus. And lets not forget the devastating environmental impact of individually-owned, manually controlled vehicles.

If you had the choice, would you prefer to live on Earth or on Planet AI if everything else were held equal?

How to Democratize Humanitarian Robotics

Our world is experiencing an unprecedented shift from manually controlled technologies to increasingly intelligent and autonomous systems powered by artificial intelligence (AI). I believe that this radical shift in both efficiency and productivity can have significant positive social impact when it is channeled responsibly, locally and sustainably.

WeRobotics_Logo_New

This is why my team and I founded WeRobotics, the only organization fully dedicated to accelerating and scaling the positive impact of humanitarian, development and environmental projects through the appropriate use of AI-powered robotics solutions. I’m thrilled to announce that the prestigious Rockefeller Foundation shares our vision—indeed, the Foundation has just awarded WeRobotics a start-up grant to take Humanitarian Robotics to the next level. We’re excited to leverage the positive power of robotics to help build a more resilient world in line with Rockefeller’s important vision.

Print

Aerial Robotics (drones/UAVs) represent the first wave of robotics to impact humanitarian sectors by disrupting traditional modes of data collection and cargo delivery. Both timely data and the capacity to act on this data are integral to aid, development and environmental projects. This is why we are co-creating and co-hosting global network of “Flying Labs”; to transfer appropriate aerial robotics solutions and relevant skills to outstanding local partners in developing countries who need these the most.

Our local innovation labs also present unique opportunities for our Technology Partners—robotics companies and institutes. Indeed, our growing network of Flying Labs offer a multitude of geographical, environmental and social conditions for ethical social good projects and responsible field-testing; from high-altitude glaciers and remote archipelagos experiencing rapid climate change to dense urban environments in the tropics subject to intense flooding and endangered ecosystems facing cascading environmental risks.

The Labs also provide our Technology Partners with direct access to local knowledge, talent and markets, and in turn provide local companies and entrepreneurs with facilitated access to novel robotics solutions. In the process, our local partners become experts in different aspects of robotics, enabling them to become service providers and drive new growth through local start-up’s and companies. The Labs thus seek to offer robotics-as-a-service across multiple local sectors. As such, the Labs follow a demand-driven social entrepreneurship model designed to catalyze local businesses while nurturing learning and innovation.

Of course, there’s more to robotics than just aerial robotics. This is why we’re also exploring the use of AI-powered terrestrial and maritime robotics for data collection and cargo delivery. We’ll add these solutions to our portfolio as they become more accessible in the future. In the meantime, sincerest thanks to the Rockefeller Foundation for their trust and invaluable support. Big thanks also to our outstanding Board of Directors and to key colleagues for their essential feed-back and guidance.

On Humanitarian Innovation versus Robotic Natives

I recently read an excellent piece entitled “Humanitarian Innovation and the Art of the Possible,” which appeared in the latest issue of the Humanitarian Practice Network’s (HPN) magazine. The author warns that humanitarian innovation will have limited systemic impact unless there is notable shift in the culture and underlying politics of the aid system. Turns out I had written a similar piece (although not nearly as articulate) during the first year of my PhD in 2005. I had, at the time, just re-read Alex de Waal’s Famine Crimes: Politics and the Disaster Relief Industry in Africa and Peter Uvin’s Aiding Violence.

thumb_IMG_5014_1024

Kim Scriven, the author of the HPN piece and one of the leading thinkers in the humanitarian innovation space, questions whether innovation efforts are truly “free from the political and institutional blockages curtailing other initiatives” in the humanitarian space. He no doubt relates to “field-based humanitarians who have looked on incredulously as technological quick fixes are deployed from afar to combat essentially political blockages to the provision of aid.” This got me thinking about the now well-accepted notion that information is aid.

What kinds of political blockages exist vis-a-vis the provision of information (communication) during or after humanitarian crises? “For example,” writes Kim, “the adoption of new technology like SMS messaging may help close the gap between aid giver and aid recipient, but it will not be sufficient to ensure that aid givers respond to the views and wishes of affected people.” One paragraph later, Kim warns that we must also “look beyond stated benefits [of innovation] to unintended consequences, for instance around how the growing use of drones and remote communication technologies in the humanitarian sphere may be contributing to the increased use of remote management practices, increasing the separation between agencies and those they seek to assist.”

I find this all very intriguing for several reasons. First, the concern regarding the separation—taken to be the physical distance—between agencies and those they seek to assist is an age-old concern. I first came across said concern while at the Harvard Humanitarian Initiative (HHI) in 2007. At the time, ironically, it was the use of SMS in humanitarian and development projects that provoked separation anxiety amongst aid groups. By 2012, humanitarian organizations were starting to fear that social media would further increase the separation. But as we’ve said, communication is aid, and unlike food and medication, digital information doesn’t need to hitch a ride on UN planes and convoys to reach their destination. Furthermore, studies in social psychology have shown that access to timely information during crises can reduce stress, anxiety and despair. So now, in 2016, it seems to be the turn of drones; surely this emerging technology will finally create the separation anxiety that some humanitarians have long-feared (more on this in a bit).

The second reason I find Kim’s points intriguing is because of all the talk around the importance of two-way communication with disaster-affected communities. Take the dire refugee crisis in Europe. When Syrians finally escape the horrid violence in their country and make it alive to Europe, their first question is: “Where am I?” and their second: “Do you have WiFi?” In other words, they want to use their smartphones to communicate & access digital information precisely because mobile technology allows for remote communication and access.

Young humanitarian professionals understand this; they too are Digital Natives. If crisis-affected communities prefer to communicate using mobile phones, then is it not the duty of humanitarian organizations to adapt and use those digital communication channels rather than force their analog channels on others? The priority here shouldn’t be about us and our preferences. But is there a political economy—an entrenched humanitarian industrial complex—that would prefer business as usual since innovation could disrupt existing funding channels? Could these be some of the political & institutional blockages that Kim hints at?

The third reason is the reference to drones. Kim warns that the “growing use of drones and remote communication technologies in the humanitarian sphere may be contributing to the increased use of remote management practices, increasing the separation between agencies and those they seek to assist.” Ironically, the same HPN magazine issue that Kim’s piece appears in also features this article on “Automation for the People: Opportunities and Challenges of Humanitarian Robotics,” co-authored by Dr. Andrew Schroeder & myself. Incidentally, drones (also as UAVs) are aerial robots.

Kim kindly provided Andrew and I with valuable feedback on earlier drafts. So he is familiar with the Humanitarian UAV Code of Conduct and its focus on Community Engagement since we delve into this in our HPN piece. In fact, the header image featured in Kim’s article (also displayed above) is a photograph I took whilst in Nepal; showing local community members using a map created with aerial robots as part of a damage assessment exercise. Clearly, the resulting map did not create physical separation—quite on the contrary, it brought the community and robotics operators together as has happened in Haiti, Tanzania, the Philippines and elsewhere.

(As an aside, a number of UAV teams in Ecuador used the Code of Conduct in their response efforts, more here. Also, I’m co-organizing an Experts Meeting in the UK this June that will, amongst other deliverables, extend said code of conduct to include the use of aerial robotics for cargo transportation).

What’s more, Andrew and I used our article for HPN to advocate for locally managed and operated robotics solutions enabled through local innovation labs (Flying Labs) to empower local responders. In other words, and to quote Kim’s own concluding paragraph, we agree that “those who focus on innovation must do a better job of relocating innovation capacity from HQ to the field, providing tools and guidance to support those seeking to solve problems in the delivery of aid.” Hence, in part, the Flying Labs.

In fact, we’ve already started co-creating Kathmandu Flying Labs, and thanks to both the relevant training and the appropriate robotics technologies that we transferred to members of Kathmandu Flying Labs following the devastating earthquakes in 2015, one of these partners—Kathmandu University—have since carried out multiple damage assessments using aerial robotics; without needing any assistance from us or needing our permission for that matter. The Labs are also about letting go of control, and deliberately so. Which projects Kathmandu Flying Labs partners decide to pursue with their new aerial robotics platforms is entirely their decision, not ours. Trust is key. Besides, the Flying Labs are not only about providing access to appropriate robotics solutions and relevant skills, they are just as much about helping to connect & turbocharge the local capacity for innovation that already exists, and disseminating that innovation globally.

Kathmandu University’s damage assessments didn’t create a separation between themselves and the local communities. KU followed the UAV Code of Conduct and worked directly with local communities throughout. So there is nothing inherent to robotics as a technology that innately creates the separation that Kim refers to. Nor is there anything inherent to robotics that will ensure that aid givers (or robots) respond to the needs of disaster-affected communities. This is also true of SMS as Kim points out above. Technology is just a tool; how we chose to use technology is a human decision.

The fourth and final reason I find Kim’s piece intriguing is because it suggests that remote management practices and physical separations between agencies and those they seek to assist are to be avoided. But the fact of the matter is that remote management is sometimes the most efficient solution; in some cases, it is the only solution, as clearly evidenced in the protracted response to the complex humanitarian crisis in Syria. In fact, the United Nation’s Inter-Agency Standing Committee (IASC) suggests bolstering remote management in some cases. And besides, the vast majority of humanitarian interventions engage in some level of remote management.

So if we can use aerial robotics to deliver essential supplies more quickly, more reliably and at lower cost (like in Rwanda), then how exactly does using fewer motorbikes or trucks to deliver said supplies create more separation between agencies and those they seek to assist? In the case of Rwanda, aerial robotics solutions are airlifting much-needed blood supplies to remote health clinics across the country. I’d like to know how exactly this creates a separation between the doctors administering the blood transfusion and the patients receiving said transfusion. As for using aerial robotics solutions to collect data, we’ve already shown that community engagement is key and that local partners can expertly manage the operation of robotics platforms independently. The most obvious alternative to aerial imagery is satellite imagery, but orbiting satellites certainly don’t allow local partners and communities to participate in data collection.

So are there “political and institutional blockages” against the use of robotics in humanitarian efforts? Might humanitarian organizations receive less funding if aerial robotics solutions prove to be cheaper, more effective and more scalable? Is this one reason, to quote Kim, that “Emerging ideas get stuck at the pilot stage or siloed within a single organization unable to achieve scale and impact”? Are political & institutional barriers curtailing in part the entry of new and radically more efficient solutions to deliver aid? If these autonomous solutions require less international staff to manually operate, will the underlying politics of the $25 billion dollar-a-year aid industry allow such a shift? Or will it revert to fears over (money) separation anxiety?

We should realize that disaster-affected communities today are increasingly digital communities. As such, Digital Natives do not necessarily share the physical separation anxieties that aid organizations seemingly experience with every new emerging technology. Digital Natives, by definition, prefer a friction-free world. But by the time we catch on, we’ll no doubt struggle to understand the newer world of Robotic Natives. We’ll look on incredulously as the new generation of Robotic and AI Natives prefer to interact with Facebook chatbots over “analog humanitarians” during disasters. Some of us may cry foul when Robotic Natives decide to get their urgent 3D-printed food supplies delivered to them via aerial robotics while riding a driverless robotics car to their auto-matically built-in-time shelter.

In conclusion, yes, we should of course be aware and weary of the unintended consequences that new innovations in technology may have when employed in humanitarian settings. Has anyone ever suggested the contrary? At the same time, we should realize that those same unintended consequences may in some cases be welcomed or even preferred over the status quo, especially by Robotic Natives. In other words, those unintended effects may not always be a bug, but rather a feature. Whether these consequences are viewed as a bug or a feature is ultimately a political decision. And whether or not the culture and underlying politics of the aid system will shift to accommodate the new bug as-a-feature worldview, we may be deluding ourselves if we think we can change the world-view of Robotics Natives to accommodate our culture and politics. Such is the nature of innovation and systemic impact.