 Well, hello, and good afternoon, good evening or good morning, depending on where you are joining us from. Welcome to Engineering for Change, or E4C for short. Today, we're pleased to bring the latest in E4C's 2017 webinar series, focusing on mobile data collection with our Joy 5 Magpies. My name is Yana Aranda, and I'm the current president at Engineering for Change. And I'll be the moderator for today's webinar. The webinar you're participating in today is part of E4C's professional development offerings. Information on upcoming webinars in this series, as well as our prior videos of past presentations, can be found on the E4C webinars page, as well as our YouTube channel. Both of the URLs are listed here for your reference. If you have any questions, comments, or recommendations for future topics and speakers, please contact the E4C webinar series team at webinars.engineeringforchange.org. If you're following us on Twitter today, please join the conversation with our hashtag, hashtag E4C webinars. Now, before we move on to our presenter, I'd like to tell you a bit about Engineering for Change and who we are. E4C is a knowledge organization and a global community of more than one million engineers, designers, development practitioners, and social scientists. We are leveraging technology to solve quality of life challenges faced by underserved communities worldwide. Some of those challenges include access to clean water and sanitation, sustainable energy, improved agriculture, healthcare services, and more. We invite you to become a member of E4C. E4C membership is free and provides access to news, data on hundreds of essential technologies in our solutions library, professional development resources, and opportunities such as jobs and fellowships. E4C members enjoy a unique user experience based on their site behavior and engagement. Essentially, the more you interact with the E4C site, the better we will be able to serve you resources aligned to your interests. For more information, please see our website, engineeringforchange.org, to learn more, and sign up. Our next webinar is on July 19th, and will be on the topic of equity crowdfunding, and will be joined by Meg Wurth, who is the co-founder of Matcher NOVA. Please join to learn about how to fundraise for your organization. For more details, please see the E4C professional development page for details on registration. If you're an E4C member ready, we'll be sending you an invitation to the webinar directly. Now, a few housekeeping items before we get started. Let's back to using this platform by asking you where you're from in the world. In the chat window, which is located at the bottom right of your screen, please type your location. I'm going to go ahead and get us started so that everybody sees what I mean. All right, so we have folks from Chicago, from Portland, from Ghana, Africana, Indiana, South Carolina, Charleston, and more. Thank you so much for joining us. Please do let us know. There you go, South Korea, Ohio, Egypt, but living in Japan. Paraguay. Assumption. Paraguay. Well, welcome. Welcome. So excited to see all of you from around the world. Please feel free to continue this chat to make comments to your fellow attendees or if you observed something interesting. Share your remarks in that window. For questions related to the platform itself, just send a private chat to Engineering for Change admin. During the webinar, please use the Q&A window, different to the chat, located below the chat to type in your questions for the presenter. That way we can keep track of those. Again, if you don't see the chat or the Q&A window, please click on the top right-hand corner of your screen for the webinar platform. And I see already some folks using the Q&A window. So please do be sure to use the chat window for all your remarks. And again, welcome to everybody from India to Jersey City to Boulder, Colorado to Georgia, all of those places. If you're listening to the audio broadcast and encounter any trouble, try hitting stop and then start. You may also want to try opening up Webbacks in a different browser. E4C webinars qualify engineers for one professional development hour. To request yours, please follow the instructions on the top of the E4C professional development page after this presentation. And the link is listed right here. And we encourage all of you to get your PDHs. Now, I'd like to take a moment to tell you a bit about the mobile data collection series, which includes this webinar. The widespread availability of mobile communications offers international development researchers, practitioners, and students new tools and techniques for collecting field data and determining success of projects. The E4C mobile data collection series includes seven webinars that introduce a sample of survey software tools and demonstrate how to implement each tool in practice. Some of the other examples include the open data kit and organizations like Primus. For a recorded introduction to the series, please visit the E4C home page. Today's webinar is the seventh in the series, and we are featuring Matt Pye, introduced by Dr. Joel Salonikio, who's the CEO and co-founder of this organization. He also is an award-winning physician, head seeker, inventor, emergency responder, and consultant working in the fields of technology, healthcare, entrepreneurship, innovation, artificial intelligence, big data, child health, global health, and disaster response. Makes for a very long business card. He is the winner of the Wall Street Journal Technology Innovation Award for Healthcare and the 100,000 Lemelson-MITO Award for Sustainable Innovation for his role in development of both the Matt Pye mobile data system and the software as a service model for international development technology. We're honored and excited to have Joel join us today, and I will turn it over to him to introduce you all to Matt Pye. Hello? Yes, there you are. I think you were muted before. Welcome. Can you hear me? Very well. Loud and clear. Yeah, sorry. So thanks again for having me, and especially for going through that very long, I think, excerpt from my LinkedIn profile. I'm happy to be here. What I'd like to do first is to go through a set of slides that kind of introduces the concepts of Matt Pye, and I think that will wet people's appetite perhaps for a selective demo, or we can just kind of run through and give a general demo. So if you'll, I'm not sure if the screen is shared with me yet, but if you'll share the screen with me or I guess yield control, I'll start to show my slides, and we can go through and then answer questions, and as I said, then go through with the demo. You are having control, so yes, feel free to advance the slides. Perfect. Just a second. And share my screen. Share application. Perfect. And you guys should be seeing my slides as of now. It's a slide of two people wearing blue heart hats. We are seeing that slide, and heart hats are always good for engineers. Absolutely. Safety first. Okay. So, you know, I have to always change this first slide, because we keep extending the capabilities of Matt Pye, which started out really focused on mobile data collection. And by mobile data collection, I really just mean replacing any situation in which you are filling out a paper form, usually on a clipboard, and replacing that with an electronic method that provides greater efficiency. But we've added messaging and visualization, data visualization components as well in the last two years, and I'll talk to you about those things as well. Probably the most significant, I think, long-term aspect of Matt Pye is that Matt Pye was the first cloud-based system created for international development and nonprofits and global health. So, way, way back, you know, going back 10 plus years, we were working on a version of Matt Pye that was a locally installed program, kind of like the way you install Microsoft Word on your desktop or laptop. And we observed, of course, things like Hotmail and all the web-based software that was being created for commercial purpose, and we thought, you know, this would be an efficient way to create tools for the international development and nonprofit and global health communities that would give the same kind of efficiencies. And so, we really consciously emulated, again, programs like Hotmail and programs like Gmail and Google Maps, et cetera, by producing a cloud-based system so you don't install the Matt Pye design software on your desktop or laptop but you just access it via a browser. And the other, I guess, technological aspect which we borrowed was this concept of self-service. Really, where the idea was, we recognized that in most nonprofit-oriented activities that involved computers, by far the greatest cost was the cost of the personnel that were required to set up those computerized systems. And, of course, when you look at things like, you know, no one ever hires a programmer if they want to use Google Maps, no one hires a programmer to use Facebook, and we realized that the strategy of those companies was to design software that was so simple while providing complex features but was so simple to use that the average user could just sign up and therefore those companies could scale rapidly. So we borrowed that approach to that self-service approach. And it's been documented many, many times, not surprisingly, that when you use a system like MagPy, which is primarily self-service, because you don't need to hire technical people or you don't need to devote the time of the technical people you already have, the costs of running MagPy are typically at least 70% less than systems that do require you to have technical personnel running them. Another aspect, not a technological model, but a business model which we borrowed from these Silicon Valley companies was the so-called premium or tiered pricing model. And the idea here was recognizing that, you know, if you look at a product like Skype, everybody's used Skype. They've got a great free product which allows us to make either video or audio calls between computers, between computerized devices, I guess I should say. But that charges if you want to use an additional feature which is making calls to an actual phone, whether landline or mobile phone. And this idea that you would price based on features, but that your basic free version would have a great set of functionality for people to use, this is quite different from the idea of giving people, let's say, a crippled version that is time limited. And we decided to adopt this premium pricing model to make sure that we could achieve really our primary organizational goal which is allowing every organization to use efficient data collection regardless of what their budget is. And as a result of this particularly unique approach, we have been recognized not only within the global health community, and I'm a physician and epidemiologist, and our initial focus with MagPy was really on health-related activities, but we're happy that we've been recognized not only for our activities within global health but really within technology and even within business with, for example, the Wall Street Journal Tech Innovation Award. So again, I mean awards only go so far, but we're quite happy to have been recognized for that activity. What you can see on the graph that shows up right now is this is not the full history of MagPy, which really begins as an organization back in 2003. This is the history of MagPy as we shifted from the pre-Mobile, pre-Mobile phone stage to the mobile phone era. And you can see on the bottom left, the initial mobile component of MagPy way back in the day was the Palm Pilot. For the younger members of the audience, Palm Pilots or PDAs were mobile devices that had a lot of the same functionality as mobile phones, but zero connectivity. And of course it's hard to explain to people today why you would buy something like that with zero connectivity, but basically it was the best tool that we had. But we shifted from these unconnected PDAs to the basic mobile phones back in 2008, 2009. And as you can see, as we've added Android and iOS compatibility and later SMS, our user base has grown and we've actually just exceeded 70,000 registered users of the system, including all the organizations that you can see on the screen there. So one of the, I think, really unsought and unexpected aspects of MagPy that has been really the most, among the most delightful for us within the organization has been that we tried to create a tool to help people collect health data around immunizations. And once we put that tool online and made it freely available to people where they don't have to ask us to use it, there's no process you just go and sign up, once we made it so easy and inexpensive to use MagPy, people have begun using it in a whole variety of different sectors. And I would say it's amazing to us when we have educational organizations or engineering organizations or agricultural organizations using MagPy for great nonprofit-oriented projects, rather. It's also, I have to say, quite amazing to us when we see commercial organizations in construction or energy, et cetera, using MagPy for commercial applications, particularly since those organizations tend to get paid subscriptions to MagPy, which helps, of course, to support the system for everyone else. Now, I mentioned that we started MagPy with the data collection component. A few years back, we added an aspect where you can send broadcast SMS or even voice or audio messages. And most recently, in the past year, we've refocused to add a component for data visualization. Prior to last year, we really just told people MagPy was to get your data. And once you got it, you'd have to send it somewhere else to be visualized. And we've modified that based on just tons of feedback from users to add visualization within the actual MagPy product itself. So, again, we've been around since 2003, and this is by far the longest running continuous mobile data system within the development sector. And as I mentioned, well, it's kind of hard to keep track of our users or rather keep our slides up to date, because I just revived this maybe three weeks ago, and now we've got 70,000 users registered on the system. Now, like so many things, MagPy involves this online component. So if you wanted to collect information about any particular topic, you wanted to create a form, you would do it online using our online form design system, works in any browser. You do need to be connected during the design process. And then importantly, you can deploy your form for the data to be filled in to any device at all. And this could be Android, the old-time Symbian phones, SMS, iOS, or indeed by voice. So you could even collect data with MagPy from landline phones that are touch-tone enabled, any device in any language or alphabet. This slide, and by the way, I should mention, at the end of the slide, I'll provide for your audience a link to download this set of slides. That may already have been provided, but I'll provide it again at the end of this. And many of the links within the presentation, many of the items within the presentation, like down at the bottom of this screen, are active links that can provide further information. Of course, those will all be active within the PDF file that I'll provide at the end of the talk. Now, this slide showing the four methods currently available with a MagPy for data collection, I think is probably the most important slide of the presentation. Much more extensive than we ever imagined it would be, and we've removed the POM pilot from this since no one really uses those anymore. But I'll start from the left and I'll work my way to the right. The left-hand side where it says app-based, this is probably the most familiar to folks in terms of folks who have experience doing electronic mobile data collection. This is where you install an app on your mobile device, and the app essentially is a player for form files. So you can create your forms online, and then you can play them or display them and fill them in in the app on the mobile device. And the nice benefits of the app are, one, it's got a nice interface. Two, it provides logical branching. You know, if they answer this, then jump to question X. Range checks, lots of quality controls, and it can be operated offline. So once you have your form downloaded to the app, you can take it to some rural location that has no connectivity, continue to collect your data and just upload the data to the MagPy system once you've gone back into a connected area. Again, this runs on iOS devices, both iPhones and iPads, Android devices, and even the older Symbian devices. Moving from the left into the middle, MagPy has two completely distinct SMS-based methods of data collection. Of course, these run on any SMS-enabled device, any device with a SIM card, basically. And although you can see one is depicted on an iPhone and one is depicted on a basic Nokia phone, these SMS-based approaches will run on any device. Any of them will run on any device. I'll take the Nokia phone on the right first. This is our structured SMS, and it's designed to enable you to collect simple data from any device. Really, the idea here is that if you're collecting a very short form, a very short collection of data with few variables that will fit into a single SMS message, someone in the field, some respondent, can send the information of the form where they send a keyword and then a hash sign, then the answer to the first question, hash sign, answer to the second question, hash sign, et cetera. The example you can see on the phone pictured, this is an actual example taken from during the last Ebola crisis a couple years ago in West Africa, where numerous countries under the auspices of the Centers for Disease Control were sending in reports of the number of suspected Ebola cases that had been seen at a particular facility each day. So every day the reporters from these facilities would send a single text message with the keyword Ebola, a hash sign, and then a number representing the number of suspected cases of Ebola seen that day. And, of course, this is simplicity itself, very easy for people to be trained to do this. It doesn't provide any interface, doesn't provide any logical branching or anything like that, but it is a very cost-effective and simple way to have routine, frequent reporting of simple data. Now, the iPhone pictured in the middle is depicting our much more complex interactive SMS. And this really is much more like using the mobile app. With interactive SMS, which again could run on any SIM-equipped device, with interactive SMS, Magpie sends out the first question of your form as an SMS. The person receives it on their mobile device, they reply just as they would to any other SMS, and Magpie will receive the reply and evaluate it. Now, the nice thing about this is when you're using the mobile app, you can have logic and skip patterns, et cetera, because the mobile app is running on a smartphone, and there's enough of a computer inside the smartphone to provide that kind of logical branching, et cetera, and those evaluations. The nice thing about interactive SMS is that the brains of interactive SMS are not on the mobile device as they are when you're using the app. When you use interactive SMS, the mobile device really just acts as a screen and a keyboard. It acts as an input-output device. But all the thinking and evaluation goes on back at the Magpie server computer, which might be 10,000 miles away from where the actual data collection is going on. For interactive SMS, you have to have a connection, but each time you send a response into the system, Magpie looks at the response back on the Magpie server, evaluates the logic, decides which question should be sent next, and then proceeds accordingly. And the great thing about this is it means that you can get a lot of the benefits of using the mobile app, such as logic and range checks, but on any mobile device. The real downside of the interactive SMS system is that you do have to be connected during the entire data collection process, because you have to be able to talk to the Magpie system while the data is being collected. And similar to the interactive SMS, it is the system that's based all the way on the right, the voice-based system, or interactive voice response, IVR. This basically is deployed as a phone call. So you create a form, as you would for any other Magpie deployment. But instead of sending out the question as an SMS, or instead of displaying the first question on the screen of the mobile app, the respondent's phone will ring, and when they pick up, they'll hear Magpie speaking the first question, and the respondent can respond by pressing the number keys on the phone. So the great thing about voice-based data collection, or IVR, is that you can collect data even from illiterate respondents. They just have to know the numbers of the keypad. But of course there are some limitations. One is it's more expensive to make phone calls, particularly to remote areas, than it is to send an SMS or a series of SMSes. And the second is that responses are limited only to numeric responses. But again, given that you can collect data using voice from even illiterate responses, it's actually quite a powerful addition to the toolbox within Magpie. Another aspect we added within the past year is the concept of business logic and workflows. Basically what this means is that it allows Magpie to incoming data from the field to trigger a workflow of different events and actions. And none of this involves any programming at all. All this involves is menu choices and points and clicks. And the big idea is that you can have your Magpie data coming in, and as your Magpie data comes in, it will trigger a variety of actions. For example, as the data comes in, you could send an SMS message back to the data collector to confirm that you'd received the data. You could even create calendar appointments or reminders. Again, based on either just the fact that a data record has been submitted, that a form has been submitted, or based on the fact that it matches certain values. And again, with no programming. I'm going to skip this slide. It's a little complex for our demo. Magpie also recognizes that many of the organizations that use Magpie are large organizations with many different units, or sometimes they're groups of organizations in some kind of a confederation. An example might be the Federation of the Red Cross, which is a Geneva-based organization that helps to coordinate national Red Cross societies around the world. And so we've added enterprise management that makes it easier for folks to be able to share both, to have centralized billing and to share forms and templates. If there's more interest in this, I can mention this further. An important thing about Magpie is that, just like any other computerized system, Magpie is completely customizable, but we never require you to have us customize it. What I mean by this is that all the features of Magpie currently are available for you to use with no programming, without having to hire us, without having to pay a programmer or any other tech support person. However, if you find that Magpie is missing a feature and you want to add it, it's certainly possible for us to add that feature based on your input and feedback. We can also, using our Magpie APIs or application program interfaces, that allows programs that your organization writes potentially to connect with Magpie as well. So it's possible to customize and modify Magpie both internally, modifying the Magpie program, or by building software that integrates with Magpie based on our APIs. Now, I mentioned data visualization. This is, as I mentioned, the latest addition to our toolbox. We've just added this over the course of the past year. Prior to that, you would be able to make maps and a column chart with your Magpie data. Now you can make a very, very wide array of data visualizations, such as depicted here, and you can do that, again, with no programming and in real time, so that your Magpie reports reflect the data as it comes in and change as more data comes in. Our messaging system, which I mentioned a moment ago, involves several different channels. This enables you to set up broadcast messaging systems, broadcast messaging arrangements within just minutes. The three channels are SMS, where you import or type text messages, and it goes out as an SMS text message. Text to speech, where you type the messages in or import them, but it goes out as a phone call and Magpie reads the message. And the third is recorded audio, where if the language you want to send the messages out is not supported, it's not one of the roughly 15 languages supported by text to speech, you can record an audio message in any language and have it go out as a phone call. Of course, there are many different possible uses for broadcast messaging, both to coordinate staff or to reach people within your organization and potentially beneficiaries of programs or projects for customers. The cost is quite low to do this, and so, for example, you can set up an automated SMS messaging system to send out messages to 1,000 people weekly. So that would be, of course, 52,000 messages, 1,000 messages times 52. And the cost of that for an entire year would be about $1,000, including the message cost. You wouldn't have to pay for subscription to Magpie, no programmers, et cetera. We don't know of any other method to send out broadcast messages that isn't this inexpensive for an entire year. Now, I have many different examples of field activity with Magpie, but I'm going to go through them rather quickly because I'd really like to make sure we have time for questions and answers and a demo. And I'd also like to hear about any people on the call who might be using Magpie or thinking about using Magpie. The Federation of the Red Cross is one of our oldest users. They've been using Magpie for, gosh, maybe eight years. This is being used by the Federation in Geneva and by probably at least 20 different national Red Cross societies for a very wide variety of data collection activities, including water and sanitation, lots of disease activities or immunization activities, Ebola, certainly. Westside, one of my favorite examples, this is a commercial energy company that does natural gas drilling, and they replace their paper-based checklist, the safety checklist, at drilling sites with a Magpie-based system, which is a large organization operating within international development, does work to evaluate and quantify and reduce child labor in mining and use Magpie very recently for data collection around that in Congo. Another one that we're very proud of is for many years now, WHO, the World Health Organization's Polio Eradication Initiative, which is close to eradicating polio all around the planet, has used Magpie as the data collection tool to evaluate their activities and essentially determine how successful are they being at eradicating this disease from the Earth. John Snow, another health-oriented organization, has used Magpie for supply chain management, mostly around malaria medicine supplies as part of the President's Malaria Initiative, and I'm just going to go quickly through these other examples. Again, lots of activity with Magpie during the Ebola crisis, but certainly not limited to health activities. Again, when I finish this slide, I'll show you a link where you can download all of these, including the Read More links. And here we are. So I'm going to pause here for a moment and allow people to see on the screen toward the top right where it says Download These Slides. If you use that link, and note there's no WWW or anything like that, if you just type that link into your browser, starting with bit.ly, then you'll be able to download the slides that I just gave in a PDF format. So that's the slide presentation. I'd be happy to go back over any of the slides. Be happy to answer any questions. And as I said, we've got, I think, plenty of time to do a focused demo of any aspect of Magpie that people would like to see. So I'm going to, let's see, I'm going to reduce my screen here and see if I can get back to the interface for WebEx. I see, Joel, I did ask the question of the audience. If anybody is already using Magpie, I haven't received any responses yet in the chat. And of course, if anybody is using Magpie already, please let us know. But I think it would be worthwhile to have a demo. It says it seems that most folks would be new to the platform. Sure. And do I need to keep the slide up that shows the link to download the slides, or is that going to be provided? No, actually, our admin already posted that link in the chat. So if anybody didn't catch it, it's in the chat. So, again, if you can go ahead and move that slide. Okay. I'm going to stop sharing now. And so I'll take a moment. I see that there are a few questions, if that's all right, before we move on to the demo to those quickly. Sure. Feel free. Sure. So let's see. I can read them out so that everybody can hear them. So what if we have a... Everyone can see them. It's possible some folks can. So if they can't just in case, we try to make sure that just as you do communicate via voice, SMS, and other methods, so do we. So this is my first intro to Magpie, one of our participants' writing. I'm currently using Kobo Toolbooks exclusively. Kobo allows for surveys to be conducted using audio and selecting image, quote, unquote, buttons for response options. This actually enables respondents to self-survey rather than having survey questions be read by an enumerator. Does Magpie offer something similar? Sure. So I'm not... I think maybe we're talking about two different concepts in terms of audio and image buttons, because, obviously, you wouldn't be able to see image buttons on audio. But Magpie, as I mentioned, uses IVR, so we do have the ability for people to self-respond using IVR, interactive voice response. So this happens over a phone call. We do have that. We don't have image buttons, or at least I might not be certain of what image buttons are. Let's see, MP3 is inside the mobile survey. Oh, I see. So I think what Kristen is asking this question about doing surveys conducted using audio and playing audio inside the mobile app, I suspect. Kristen is smiling. Kristen keeps smiling. Yes, that is what Kristen means. So Magpie does not have audio inside the mobile app, but Magpie allows you to collect audio, information by audio from any phone, not just the type of smartphone that can run Kobo and without having to install an app. So what we've seen people do successfully to self-survey folks, to have regular folks in the community answering questions, is by using the interactive SMS approach, or by using the IVR approach. So those are two approaches, again, that work on any phone that allow you to be able to essentially get information from anyone in your organization or the community, but the IVR one is not text-based. We also have something called crowd sourcing, which basically means that, for example, with Kobo, and Kristen, correct me if I'm wrong here, but I believe that with Kobo, first of all, people have to install the Kobo application on a smartphone. And second of all, the person who's running the Kobo system needs to be able to communicate with those folks to sort of say, here's a form, go ahead and fill this out. What Magpie allows you to do that, allows you to send forms or provide forms to people that you already know of. But Magpie also allows you, for our interactive SMS, to essentially create a local phone number and then post that phone number in some publicly available spot with a sign that might say something like, we're interested in your feedback, please text this keyword to this number to provide feedback or answer our questions. Now, we've all seen this type of thing in developed countries and usually it takes quite a bit of money and time to set these things up, but with Magpie, you can set up that kind of crowd sourcing approach really just in the space of minutes. So, again, to get back to Kristen's question, we do have audio data collection with IVR and we also have, again, and I think this is different from Kobo, we have several different methods to collect data without people having to install a mobile app on their phone. Now, I can go ahead and, if it's okay, I'll go ahead and read the next question. Sure, go for it. I see, I'm going to alternate between these sessions. I see someone says, do you sell collected data? No, absolutely not. We don't have access to the data that you collect unless you explicitly share it with us. That's both by legal contract with you, our terms of service says that we don't look at your data and also because we've designed the system to make it difficult for us to do that without you actually sharing that information with us. So, no, we don't look at or sell or exert any ownership over collected data. Let's see, does Magpie allow the recording of mobile sensor data using the API? Yes, we do. So, this is what I had mentioned before about having Magpie APIs that allow folks in the community to create software that interacts with Magpie without us really having to be involved at all. For those in the audience that don't know what an API is, it's basically the little piece of Magpie software code, and that code allows programmers out in the community to write programs that can interact with Magpie. This is just the same way that if you were writing a website, you're creating a website, you might decide to use the Google Maps API to display maps within your software. You don't have to contact Google or make an arrangement with Google or partner with Google. The Google Maps API is designed to allow your programmers to connect with Google Maps for mutual benefit. Let's see, a couple of people have asked about what features are available with the free version. I'm going to show you that in just a sec. Let's see. Again, I'll get back to the free version versus paid in just a sec. A question about where is the data stored? Where is the server? Yeah, sure. Again, part of the aspect of using cloud-based software and the reason that cloud-based software is so much less expensive is because you share resources. What this means, of course, is this is completely against the idea of saying every organization should have its own server storing data in its own country. To some extent, the cloud-based model generally works against the idea of everybody having data stored in a particular place. I live in Washington, D.C., and I might like to have my information stored in Washington, D.C., but I'm not willing to spend the thousands or tens of thousands of dollars extra to have my data stored in Washington, D.C. In fact, like most people, I just use Gmail and have my email data stored wherever Google stores it. With MagPy, currently, our storage is both in Europe and in the United States. We're actually shifting from previously we had everything, both the primary server and the backup server, stored in the United States. We've now moved our backup server to Frankfurt, Germany, and our... Let me just a second. Okay. We've moved our backup server to Frankfurt, Germany, and we're going to be moving our primary server to Dublin, Ireland because those countries have very good data protection laws. MagPy's primary servers in the United States and backup server is in Frankfurt, Germany. We do, of course, allow our users to either manually or automatically move their data to wherever they want MagPy, their MagPy data to be. So we don't in any way constrain you, but our primary MagPy servers basically... We're never going to have a system where our MagPy servers are located in every country of the world because if we had that system, we'd have to charge you a lot more information. Now, people have asked lots of information about the free versus the paid, and so what I'm going to do now is I'm going to share my browser and then see if I can answer some of those questions and then we can move into a demo. So let me open up a browser window and... And while Joel says that, please feel free to continue asking questions related to the demo or the software in a Q&A window and we'll try to tackle them to the best of our ability once the demo is done. Sure. And just keep in mind that I can't see your questions while I'm sharing a screen with you, so it's not that I'm ignoring you. I will get back to those as soon as we finish. So I'm looking at the MagPy website right now at www.magpy.com, and I think everyone should be able to see that. And I'm just going to go up to the top to the pricing page and click on Pricing. And here's where we can see both the cost of MagPy and what features are available at which levels of payment. So MagPy has... Even though there's four columns here, it basically has three different versions. The free version, the pro version, and the enterprise version. The reason there's four columns is you can pay for the pro either month to month or you can pay on an annual basis, which you can see with the blackheading there. So what you see in the top, in the column heading there, is what is the monthly cost of each of those different systems. But again, only the... Well, the free doesn't involve any billing. The pro monthly, you pay each month and you can join for a month and then stop and then join for another month and then stop. With the pro annual or the enterprise, you are billed annually. So you pay once and that lasts for the entire year. But if we divide those costs, those yearly costs by 12, so you can compare, then you get the figure in the box. Pro monthly is $500 a month. Pro annual boils down to $417 a month. So essentially you get a discount if you pay for a year at a time for a pro version. And the enterprise, which is $10,000 a year, divided by 12, that gives us $834. So talking about the differences between the free account, probably one of the most important ones is that if I look here at the features listed along the left-hand side, one is the questions per form. So with a free version of Magpie, your forms can have up to 100 questions in them. With all the other versions, there's no limit on the number of questions per form. Now probably the most important limitation to the free is how many uploads per year or how many uploads per period of time. For us, an upload means that you've filled out a form on your mobile device and you want to send it up into the Magpie system. And so basically for the free version, every single month you get 500 credits, 500 upload credits. So let's suppose that you have a form that's got 20 questions and you fill it up in the field and you upload it. Okay, now you've got 499 credits remaining. And you go ahead and do 10 more. Okay, now you've got 489 credits remaining, et cetera. So again, free users get 500 a month and they draw down against that upload credit over the course of the month. At the end of the month, any unused credits disappear and you get 500 new ones. So an important aspect of the free version is that it's not possible using a free account to upload more than 500 completed forms per month. Now, we have many people who get around this by creating more than one free account. And that's certainly possible. Sometimes they report this to us somewhat sheepishly or in an embarrassed way. We don't think it's embarrassing. We don't think it's a problem. There's a reason the free version exists and you're welcome to make two free accounts if you need to collect 1,000 records per month. That's totally fine with us. Generally what happens is that people are collecting very large volumes. They find it more convenient eventually to upgrade to a paid version. But let's keep in mind that of the 70,000 Magpie users, easily less than 1% of them pay us anything. So again, 99% plus of our Magpie users only use the free version. And they find ways to get around the limits as much as they can. So for all the other, the non-free versions of Magpie, they all come with an allocation of upload credits as well. But the difference between the free version is that when they run out of upload credits, they can buy more. So for example, both the free and the pro monthly, each get 500 upload credits per month. But with the free one, once you've finished the 500, you've got to wait for the month to finish. With the pro one, if you want to collect, let's say 600 records in a month, you would use up your 500 credits and then you buy 100 more. So that'll be 100 times 25 cents. That's $2.50 that you'd have to pay to collect that additional data. Let's see. Online storage, another limitation of the free version is that you can only store up to 500 data records online. So if you're collecting a lot of data, you'd have to upload it and then eventually export it, for example, to Excel. And again, finally, probably the most important or one of the most important ones is that free users can have up to 15 Magpie accounts contributing data into their form database. So what I mean by this is that if I were to create a form, initially it's only available to me and only I can submit data into that form. Only I can fill out the form and upload it to the system. But let's suppose I wanted five of the people on this call to go out into the field to work with me and I wanted them also to be able to upload data. That's very easy to do. I would share the form with them. They would receive notification that they now have access to that form and they can then upload data. They can see the form in the field. They can upload data to it. And that data goes into my form database because I'm the owner of that particular form. So Magpie, of course, understands that people want to be able to collaborate easily and so we provide that easy ability to share forms and data with people. And this can happen at a variety of different levels. You can share forms so that people can only fill them out in the field and upload data. Or you could share forms in such a way that people could edit the data online or could export it or could analyze it, et cetera. There's a pretty fine level of granularity, as they say. Lots of different levels of roles and privileges that you decide exactly what aspect or what level of access you want to give to people when you share a form with them. So again, I encourage people, if you have questions about this, please do go to our website and click on the pricing page. I also want to point out one thing that's quite distinct from many other systems is that Magpie has free technical support available to all users, including the free users. So if we click on the support link here, you can request support. You can create a support ticket by clicking on this link or by filling out the form that's a little bit lower here on the screen. And we will get back to you usually within 24 hours, even for free users. So if you find that you have questions about the pricing of Magpie or the support of Magpie or Magpie feature, we're very happy to answer them. We are, as far as I know, the only mobile data collection system that does provide actual human support by email to every user, even the users that are completely free. So again, two key aspects of our website, one is the pricing page, which shows you what features are available per price, and the other is the support page, which allows you to go through our knowledge base and create a support ticket to ask us a question or request our help. So what I'm going to do now is I'm going to briefly stop sharing again so I can see what questions people have. I think that this one, that is quite relevant and kind of come back to your pricing. I don't know if we want to repeat this again, but what would be the cost per account? For example, IRC has one account per user or per organization. Right. So IRC actually is a Magpie user, or I'm not sure if they currently are, but I know they have been in the past. So IRC, the way organizations usually do it is many kinds of organizations want to have the paid features of Magpie. For example, they don't want to have a limitation on the number of uploads per, let's say, per month. So in order to get around the free user limits, you'd have to have at least one paid account. So a typical organization like IRC might have one pro-annual account, and then all the other users within the organization would be free users. So the cost would be that cost that one pro-annual account, which is $5,000 a year, and then let's say I'm the key person at IRC. I might arrange for the paid account, and then when I want people to collect data, the data collectors only need to have free accounts. Or if I want to have someone I work with, I want to give them the ability to modify my forms, to edit them and change the questions, et cetera. Again, I can share that with them even if they only have a free account. So the cost structure behind MagPy, most organizations only require one paid account at most rather than having multiple ones. Now I do know of many organizations, particularly the larger ones, where because of project billing, aspect, et cetera, they want to have more than one paid account, maybe per division or something like that. But again, the most common method I've seen people use MagPy in terms of pricing is to have one paid account to the organization, and all the other users are free accounts. Okay, so what I want to show, first I'm going to go back to sharing my browser application. And again, we'll get back to some more questions shortly. But I'm shooting back now, and you should be able to see the MagPy webpage. I'm going to click on Login, so I can go ahead and log into MagPy. And okay, so let me go, I see a question popping up, are the specifications for the API available for free? Yes, they are, absolutely. So let's see. What I'm pulling up here is my main MagPy screen. Sorry, I should have logged into account that has fewer forms in it. And let's pull up all my forms. I'm not sure if anybody on the call uses DHS2 or is familiar with it, but we're pretty happy as you can see up at the top of the screen that we now have integration with DHS2. But what I'm looking at on the screen right now is the MagPy form dashboard. This is really by far the screen that people interact with the most. And what I'm seeing here is a list of forms that either belong to me or are shared with me. And I'll point out that, again, I can't see your forms unless you share them with me. All the forms that we're looking at on the screen here have been shared with me, and the people who shared them understand that I may use these forms for demonstration purposes. So, again, just to emphasize, we can't see data unless you share it with us, and we certainly would never share your data with folks without asking you permission to do so. As you can see when I click on a particular form, I can see information on the right-hand side about where the data was, about when the data was collected and by home. And so that's just kind of basic information, but let me find a basic form that's got a little bit of data in it, and I can show you what the data looks like. So I'm going to click on this test form called GIA Mining, and I'm going to click Open. And when I open it, the first thing it's going to do is it's showing me here the list of questions in the form. And we can see that as I scroll down, there's 43 different questions. And I can click on any question to see more information about it. For example, this question, were you born here? When I click on it, I can see the parameters for the question, the prompt which appears on the form screen, the name of the variable or the data field. And because this is a radio button or multiple choice question, I see a table of possible responses. In this case, it's just yes or no. As I look at that table of possible responses, I can also see that using our pull-down menu system, they program logic into this such that if the person answers yes, they were born here, it jumps to question five. But if they answer no, it just goes to the next question. So it's possible to create very simple logical branching, again, with no programming. Now, I'm going to jump back to the... You can see that a lot of the stuff on the screen here is grayed out. It's not modifiable by me, and that's because the form doesn't belong to me. I'm going to jump back to the form screen and open one that does belong to me, so we can go ahead and make some edits. So let's see. Yeah, this one. So let me open up this other form. And here we can see a form that's in French. And if I click on the Data tab, I can see that there's no data in the form. But if I want to, one of the methods you can enter data into Magpie, which I didn't mention during the presentation, because it's infrequently used, I can click the Add button and then fill out the form on a screen online, as you can see here, and create a data record. So let's go ahead and do that. I'll just answer a few questions here and save it. And what we can see behind me, I can see that a line has been added, a row has been added to the database. And here we can see the data record that I just collected, that I just entered on screen. You'd see exactly the same thing if you were uploading data from the mobile device or if you were uploading information by means of SMS or by IVR. So now, again, so the basic idea with forms is that you have a design screen where you have a list of your questions. If you want to add additional questions, you just go to this new question menu. So I'm going to go over here and I'll say, let's say I want to add another multiple choice or radio button question. I select that. And it adds the question at the end of the form. Well, of course, I can move it to some other position. And let's just say here, I want to add a question that is, what is your favorite fruit? And I'll call the data field just fruit or fruit save. And the possibilities, whoops, aren't auto-correct. And the possibilities might be apples, oranges, and I'm going to add a couple more options. So I'm going to go ahead and move this in the list, being the second form. And what you can see here is that I can, for example, say if they answer oranges, do I want it to jump as it does by default to the next question? Or do I want to pick any of the subsequent questions and say, no, if they answer apples, I want to jump to question 35. So assigning skip logic in Magpie is really just a point-and-click process. Very, very simple to do. And again, no programming required, as with everything else in Magpie. You go ahead and I'm going to delete this because I don't want to leave that test question in the form. So I just deleted the question. I'm going to save the form again. So again, this is the Magpie form dashboard. You just click new to create a new form or click open to open an existing form. And very, very simple to do. I'll point out, if I jump back for a moment to our support page on our Magpie website, one of the other things on the Magpie website under support include data collection basics, messaging basics, report basics, introduction to logic, et cetera. So some of our most popular support videos are available here on the Magpie homepage under the support link, and those will lead you right through the process of creating your first form, et cetera. Now, another aspect that we have of Magpie besides the forms is the Magpie reports. So I'm going to click on the report tab and go over to my report dashboard. And here, let me open up one of these reports. When I click on it, I see a preview of the report on the right-hand side. And again, remember that these reports are shared with me for the purpose of sharing with you. They're not private information, and I wouldn't be able to see your reports unless you did share them with me. Now, I want to go ahead and open this report for editing. And just as with the form, with the form when you open it, you see a list of questions. With the report when you open it, I see a list of report elements like a logo and some text. I'm going to open up another tab to see what this report actually looks like. Here, we can see the back end structure of the report and which elements are in it. But if I open it up into another window, now I can see what the actual report looks like. So here, we can see the first element is a logo, and then there's some text, and then there's a picture. If I go back to the report structure, I see that it matches exactly. Here's the logo, here's the text, and here's an external image. Magpie allows you to enter a wide variety of different graphs and charts and external elements. And unlike in the form design screen where you see a new question menu, for reports, you see a new report element menu. And here, we can see a variety of different types of graphs and charts. Let me show you some of these on the actual report. So here, we can see that, you know, yep, go ahead. Oh, sorry, I just wanted to let you know, Joe, that we are approaching time. But please go ahead and show the report, and then we might have to cut the demo. But please go ahead. No problem. And I'll also provide a link so people can see a sample report. But as you can see as I scroll down, we're looking at a variety of report elements, including a map. And all the report elements you see are in real time. That is to say, as data is uploaded to Magpie forms, it will change these graphs and charts. Some of the graphs and charts are interactive. For example, here on this graph of gender, I can click on the mail segment to see the answer to the question about marital status. And then go back to the main graph. And again, we call this drill down. So you can drill down into some of the charts to see a second variable. Instagrams and charts and, again, a whole wide variety of bar and column and stacked charts, et cetera. All of them in real time. All of them available without any kind of programming, which, again, is great. And as you can see, the Magpie report is really a webpage with its own URL. You can password protect it if you like, or you can share it freely with folks to have a look at. So that's the Magpie report. I'm going to go ahead and stop sharing my browser screen. Oh, thank you. And I'm going to type... I'm not sure where the best place to put it, but I'm going to go ahead and send a message to all the participants. Yep. Bitly Magpie underscore report. If you want to see a Magpie sample report, you can click on this link that I'm providing. Great. And let me see if we had any other questions that accumulated while I was not able to see that. Let's see where the data is stored. Yeah, we have just concerning users and organizations have one admin account, and they're able to create other users' accounts, which I believe you addressed, but if you'd like to speak to again. Yes, you can do that. So you can have an admin account and create other user accounts. Yeah. Fantastic. I think this was an incredibly thorough demo, and certainly for me, the visualization aspect was very exciting to see in real time. Please, for all of you attendees, you can see that there is a URL listed here, bit.ly forward slash magpie underscore report so that you can take a look at some of those samples. With that, I would like to thank Joel for a very rich conversation, a great demo, and a good throwback to the Palm Pilot Day. Thanks for the explanation for those folks on the line. So don't remember I've never been seen a Palm Pilot. I had spent to have had one if I'm going to admit my age. I'd like to thank all of you. Yeah, I found it once in a drawer and just had a moment of reflection. So I would like to thank everybody for attending. I truly appreciate your attention. The apologies for running a little bit over. For those of you who are looking for professional development hours to submit the form, please use the code JS2806. Again, that code is JS. JS and John. If you have any questions that we didn't cover, feel free to email us at webinarsandengineerforchange.org. And don't forget to become an E4C member so you can get info on upcoming webinars from our series. Thank you to everyone. Have a great morning, afternoon, or evening, depending on where you are. And we look forward to catching you on the next E4C webinar. Take care. Bye-bye now.