Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Digitizing WASH Workflows

70e0dd03af7558936035655768d96700?s=47 Matt Ball
November 02, 2012

Digitizing WASH Workflows

an overview of Aquaya's approach to data collection and management in the WASH sector

70e0dd03af7558936035655768d96700?s=128

Matt Ball

November 02, 2012
Tweet

Transcript

  1. Digitizing WASH Workflows WASH In Real Time at UNC November

    2, 2012 Matt Ball – matt@aquaya.org The Aquaya Institute
  2. Outline • Aquaya's background • data collection and management in

    WASH • Aquaya's ongoing work in Vietnam • how to approach this in your organization • questions
  3. Aquaya – a primer • applied research non-profit, est. 2005

    • San Francisco and Nairobi offices • Water Business Kits • Aquatest • Monitoring for Safe Water • ICT ▫ software development ▫ advising on monitoring programs
  4. Data collection contexts • operational • surveillance • outreach •

    crowdsourced
  5. Analysis contexts • periodic reporting and sharing • aggregation •

    live analysis and alerts • integration • staff management Source: R. Bain
  6. Expected benefits • better coverage and increased sustainability • real-time

    data ▫ no longer physically transporting information
  7. Expected benefits (cont.) • operational awareness ▫ physical and temporal

    coverage of data • digitization and compilation ▫ error-reduction ▫ data “liquidity”
  8. HueWACO • mid-sized utility in Hue, Vietnam ▫ operates 18

    rural treatment plants
  9. Monitoring program • reporting on eight parameters • weekly phone

    calls • manual compilation and internal reporting • How to digitize this workflow?
  10. Data collection – technical choices • CommCare from Dimagi ▫

    mHealth tool ▫ simple form-building and deployment ▫ Nokia C2-02 ▫ localized questionnaires and menus ▫ response restrictions ▫ submissions saved or sent over data network
  11. Data analysis • CommCare and Aquaya’s Pipeline ▫ online data

    management tool ▫ weekly aggregation of data ▫ scheduled automatic email reports
  12. Results and challenges • “Very useful” weekly reports that “save

    time.” • expansion into inventory tracking • app failures during pilot • fallback plans • misspellings ▫ fuzzy text-matching
  13. Impact and sustainability • tightly mapped to previous workflow •

    client-focused development • further work on ROI
  14. Aquaya's approach • separate collection and analysis • aggressively leverage

    Open Source • need-finding • development of management and training procedures • pilot deployments • scale-up and handover
  15. Technical options for data collection • IVRHub (Aquaya) ▫ Voice-based;

    OSS and SAAS • CommCare (Dimagi) ▫ Android and feature phones; OSS and SAAS • FormHub (Columbia Univ.) ▫ Android; OSS and SAAS • EpiSurveyor (Datadyne) ▫ all platforms; SAAS • FLOW (Akvo) ▫ Android; OSS • FrontlineForms (Kiwanja) ▫ SMS-based; OSS OSS: Open source software SAAS: software as a service
  16. Technical options for data analysis • Pipeline (Aquaya) ▫ general

    analysis and reporting • CommCare ▫ enumerator efficiency and reporting • FormHub ▫ mapping • EpiSurveyor ▫ response graphing • FLOW (Akvo) ▫ mapping • Excel/SPSS ▫ general analysis and reporting
  17. Thanks! • discussion of Pipeline here at 10:45a • our

    work ▫ aquaya.org ▫ github.com/aquaya ▫ speakerdeck.com/aquaya • more questions? ▫ Matt Ball – matt@aquaya.org