Tag Archives: Protocols

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. 

Data Protection Protocols for Crisis Mapping

The day after the CrisisMappers 2011 Conference in Geneva, my colleague Phoebe Wynn-Pope organized and facilitated the most important workshop I attended that year. She brought together a small group of seasoned crisis mappers and experts in protection standards. The workshop concluded with a pressing action item: update the International Committee of the Red Cross’s (ICRC) Professional Standards for Protection Work in order to provide digital humanitarians with expert guidance on protection standards for humani-tarianism in the network age.

My colleague Anahi Ayala and I were invited to provide feedback on the new 20+ page chapter specifically dedicated to data management and new technologies. We added many, many comments and suggestions on the draft. The full report is available here (PDF). Today, thanks to ICRC, I am in Switzerland to give a Keynote on Next Generation Humanitarian Technology for the official launch of the report. The purpose of this blog post is to list the protection protocols that relate most directly to Crisis Mapping &  Digital Humanitarian Response; and to problematize some of these protocols. 

The Protocols

In the preface of the ICRC’s 2013 Edition of the Professional Standards for Protection Work, the report lists three reasons for the updated edition. The first has to do with new technologies:

In light of the rapidly proliferating initiatives to make new uses of information technology for protection purposes, such as satellite imagery, crisis mapping and publicizing abuses and violations through social media, the advisory group agreed to review the scope and language of the standards on managing sensitive information. The revised standards reflect the experiences and good practices of humanitarian and human rights organizations as well as of information & communication technology actors.

The new and most relevant protection standards relating—or applicable to—digital humanitarians are listed below (indented text) together with commentary.

Protection actors must only collect information on abuses and violations when necessary 
for the design or implementation of protection activities. It may not be used for other purposes without additional consent.

A number of Digital Humanitarian Networks such as the Standby Volunteer Task Force (SBTF) only collect crisis information specifically requested by the “Activating Organization,” such as the UN Office for the Coordination of Humanitarian Affairs (OCHA) for example. Volunteer networks like the SBTF are not “protection actors” but rather provide direct support to humanitarian organizations when the latter meet the SBTF’s activation criteria. In terms of what type of information the SBTF collects, again it is the Activating Organization that decides this, not the SBTF. For example, the Libya Crisis Map launched by the SBTF at the request of OCHA displayed categories of information that were decided by the UN team in Geneva.

Protection actors must collect and handle information containing personal details in accordance with the rules and principles of international law and other relevant regional or national laws on individual data protection.

These international, regional and national rules, principles and laws need to be made available to Digital Humanitarians in a concise, accessible and clear format. Such a resource is still missing.

Protection actors seeking information bear the responsibility to assess threats to the persons providing information, and to take necessary measures to avoid negative consequences for those from whom they are seeking information.

Protection actors setting up systematic information collection through the Internet or other media must analyse the different potential risks linked to the collection, sharing or public display of the information and adapt the way they collect, manage and publicly release the information accordingly.

Interestingly, when OCHA activated the SBTF in response to the Libya Crisis, it was the SBTF, not the UN, that took the initiative to formulate a Threat and Risks Mitigation Strategy that was subsequently approved by the UN. Furthermore, unlike other digital humanitarian networks, the Standby Task Force’s  “Prime Directive” is to not interact with the crisis-affected population. Why? Precisely to minimize the risk to those voluntarily sharing information on social media.

Protection actors must determine the scope, level of precision and depth of detail
of the information collection process, in relation to the intended use of the information collected.

Again, this is determined by the protection actor activating a digital humanitarian network like the SBTF.

Protection actors should systematically review the information collected in order to confirm that it is reliable, accurate, and updated.

The SBTF has a dedicated Verification Team that strives to do this. The verification of crowdsourced, user-generated content posted on social media during crises is no small task. But the BBC’s User-Generated Hub (UGC) has been doing just this for 8 years. Meanwhile, new strategies and technologies are under development to facilitate the rapid verification of such content. Also, the ICRC report notes that “Combining and cross-checking such [crowdsourced] information with other sources, including information collected directly from communities and individuals affected, is becoming standard good practice.”

Protection actors should be explicit as to the level of reliability and accuracy of information they use or share.

Networks like the SBTF make explicit whether a report published on a crisis map has been verified or not. If the latter, the report is clearly marked as “Unverified”. There are more nuanced ways to do this, however. I have recently given feedback on some exciting new research that is looking to quantify the probable veracity of user-generated content.

Protection actors must gather and subsequently process protection information in an objective and impartial manner, to avoid discrimination. They must identify and minimize bias that may affect information collection.

Objective, impartial, non-discriminatory and unbiased information is often more a fantasy than reality even with traditional data. Meeting these requirements in a conflict zone can be prohibitively expensive, overly time consuming and/or downright dangerous. This explains why advanced statistical methods dedicated to correcting biases exist. These can and have been applied to conflict and human rights data. They can also be applied to user-generated content on social media to the extent that the underlying demographic & census based information is possible.

To place this into context, Harvard University Professor Gary King, reminded me that the vast majority of medical data is not representative either. Nor is the vast majority of crime data. Does that render these datasets void? Of course not. Please see this post on Demystifying Crowdsourcing: An Introduction to Non-Probability Sampling.

Security safeguards appropriate to the sensitivity of the information must be in place prior
to any collection of information, to ensure protection from loss or theft, unauthorized access, disclosure, copying, use or modification, in any format in which it is kept.

One of the popular mapping technologies used by digital humanitarian networks is the Ushahidi platform. When the SBTF learned in 2012 that security holes had still not been patched almost a year after reporting them to Ushahidi Inc., the SBTF Core Team made an executive decision to avoid using Ushahidi technology whenever possible given that the platform could be easily hacked. (Just last month, a colleague of mine who is not a techie but a UN practitioner was able to scrape Ushahidi’s entire Kenya election monitoring data form March 2013, which included some personal identifying information). The SBTF has thus been exploring work-arounds and is looking to make greater use of GeoFeedia and Google’s new mapping technology, Stratomap, in future crisis mapping operations.

Protection actors must integrate the notion of informed consent when calling upon the general public, or members of a community, to spontaneously send them information through SMS, an open Internet platform, or any other means of communication, or when using information already available on the Internet.

This is perhaps the most problematic but important protection protocol as far as digital humanitarian work is concerned. While informed consent is absolutely of critical importance, the vast majority of crowdsourced content displayed on crisis maps is user-generated and voluntarily shared on social media. The very act of communicating with these individuals to request their consent not only runs the risk of endangering these individuals but also violates the SBTF’s Prime Directive for the exact same reason. Moreover, interacting with crisis-affected communities may raise expectations of response that digital humanitarians are simply not in position to guarantee. In situations of armed conflict and other situations of violence, conducting individual interviews can put people at risk not only because of the sensitive nature of the information collected, but because mere participation in the process can cause these people to be stigmatized or targeted.

That said, the ICRC does recognize that, “When such consent cannot be realistically obtained, information allowing the identification of victims or witnesses, should only be relayed in the public domain if the expected protection outcome clearly outweighs the risks. In case of doubt, displaying only aggregated data, with no individual markers, is strongly recommended.”

Protection actors should, to the degree possible, keep victims or communities having transmitted information on abuses and violations informed of the action they have taken
on their behalf – and of the ensuing results. Protection actors using information provided
by individuals should remain alert to any negative repercussions on the individuals or communities concerned, owing to the actions they have taken, and take measures to mitigate these repercussions.

Part of this protocol is problematic for the same reason as the above protocol. The very act of communicating with victims could place them in harm’s way. As far as staying alert to any negative repercussions, I believe the more seasoned digital humanitarian networks make this one of their top priorities.

When handling confidential and sensitive information on abuses and violations, protection actors should endeavor when appropriate and feasible, to share aggregated data on the trends they observed.

The purpose of the SBTF’s Analysis Team is precisely to serve this function.

Protection actors should establish formal procedures on the information handling process, from collection to exchange,  archiving or destruction.

Formal procedures to archive & destroy crowdsourced crisis information are largely lacking. Moving forward, the SBTF will defer this responsibility to the Activating Organization.

Conclusion

In conclusion, the ICRC notes that, “When it comes to protection, crowdsourcing can be an extremely efficient way to collect data on ongoing violence and abuses and/or their effects on individuals and communities. Made possible by the wide availability of Internet or SMS in countries affected by violence, crowdsourcing has rapidly gained traction.” To this end,

Although the need for caution is a central message [in the ICRC report], it should in no way be interpreted as a call to avoid sharing information. On the contrary, when the disclosing of protection information is thought to be of benefit to the individuals and communities concerned, it should be shared, as appropriate, with local, regional or national authorities, UN peacekeeping operations, other protection actors, and last but not least with service providers.

This is inline with the conclusions reached by OCHA’s landmark report, which notes that “Concern over the protection of information and data is not a sufficient reason to avoid using new communications technologies in emergencies, but it must be taken into account.” And so, “Whereas the first exercises were conducted without clear procedures to assess and to subsequently limit the risks faced by individuals who participated or who were named, the groups engaged in crisis mapping efforts over the years have become increasingly sensitive to the need to identify & manage these risks” (ICRC 2013).

It is worth recalling that the vast majority of the groups engaged in crisis mapping efforts, such as the SBTF, are first and foremost volunteers who are not only continuing to offer their time, skills and services for free, but are also taking it upon themselves to actively manage the risks involved in crisis mapping—risks that they, perhaps better than anyone else, understand and worry about the most because they are after all at the frontlines of these digital humanitarian efforts. And they do this all on a grand operational budget of $0 (as far as the SBTF goes). And yet, these volunteers continue to mobilize at the request of international humanitarian organizations and are always looking to learn, improve and do better. They continue to change the world for one map at a time.

I have organized a CrisisMappers Webinar on April 17, 2013, featuring presentations and remarks by the lead authors of the new ICRC report. Please join the CrisisMappers list-serve for more information.

Bio

See also:

  • SMS Code of Conduct for Disaster Response (Link)
  • Humanitarian Accountability Handbook (PDF)