Data Collection and Analysis in WASH

October 2, 2012 Matt Ball matt@aquaya.org Aquaya

Outline

Aquaya's work What constitutes ICT in WASH? Examples Aquaya's approach Technical options and a demo of Aquaya's Pipeline Questions (live and at the end)

Aquaya's work in the sector

Aquatest and the Water Quality Reporter

o

feature phone application with a supporting website working with NGOs, suppliers and surveillance programs
improving the data management capabilities of African water suppliers and surveillance agencies

Consulting and research

o

Monitoring for Safe Water

o

Components of ICT in WASH

Data collection
o
o o o

operational surveillance sales crowdsourcing

Components of ICT in WASH (cont.)

Data analysis
o
o o o o

periodic reporting and sharing of analyses aggregation live analysis integration with other systems and data sources staff management

Expected benefits

better coverage and increased sustainability real-time data

o

no longer physically transporting information

operational awareness
o
o o

physical and temporal coverage of data

error-reduction data liquidity

digitization and compilation

Example use-cases: Teuk Saat

NGO in Battambang, Cambodia

o
o

operating ~50 small-scale treatment sites operators have many duties

Example use-cases: Teuk Saat

Water Quality Reporter app

o
o o

microbiological data aggregated by central managers not available in Khmer

organization saw a shift in its need for real-time data

Example use-cases: HueWACO

Mid-sized utility in Hue, Vietnam

o

operates ~10 rural treatment plants

Example use-cases: HueWACO

WQR used for physiochemical data

o
o o

transitioned to CommCare added chemical inventory data aggregated by central managers

organization needed an expandable system and backup methods

Example use-cases: MISAU-DNA

traveling surveillance personnel

o
o

operating in 3 Mozambican provinces coordinated with UNICEF

WQR used for physiochemical, inspection and follow-up data

o

weekly and monthly analysis sent to Mozambican officials

organization needed backup methods and managerial guidelines

needed improved institutional buy-in at certain levels

Overall lessons learned

consider backups for storage and transmission find systems that can evolve as user needs evolve delineate management plans

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

Technical options for data collection

IVRHub (Aquaya)
o
o o o o

Voice-based; OSS and SAAS

Android and feature phones; OSS and SAAS Android; OSS and SAAS all platforms; SAAS SMS-based; OSS

CommCare (Dimagi)

FormHub (Columbia Univ.)

EpiSurveyor (Datadyne) FrontlineForms (Kiwanja)
OSS: Open source software SAAS: software as a service

Technical options for data analysis

Pipeline (Aquaya)
o
o o o o

general analysis and reporting

enumerator efficiency and reporting mapping response graphing general analysis and reporting

CommCare

FormHub
EpiSurveyor Excel/SPSS

Demo of Aquaya's Pipeline

Thanks!
Questions?
Matt Ball matt@aquaya.org

UNCs Water and Health Conference, Nov 2 ICT in WASH paper soon