Avni Project Documentation

Get Started    

Introduction

A quick overview of Avni software for field data collection and reporting.

Avni is an open-source platform for on-field service delivery and data collection. Designed for the development sector, Avni strengthens field capacity for non-profits and governments across sectors - like health, water, education and social welfare.

This documentation site is geared to introduce Avni to those who would like to implement their program workflows using this system.

Avni consists of 4 major components which perform various functions as explained below:

  1. Avni Field App (Mobile) : This is an Android app designed to be used in the field for data-entry and collection. It can work in offline-mode, and can sync data whenever it has internet connectivity. One can install the field app easily from the Google Play Store or from an APK file.

  2. Avni Web App: This is the Administration Interface where you can configure and setup Avni server, for example configuring master data for Locations, Hierarchies, Users, design the Program Forms, etc. It can also be used for Data Imports, Exports and Data-Entry. It runs in a web-browser.

  3. Avni Reporting and Dashboard: This connects to Avni server to pull out custom reports and dashboards that can be viewed in the web browser, or exported as PDFs and emailed.

  4. Avni Hosted Service: The central instance of Avni server running on the cloud, which stores all the master data, configuration and field-entered data. If you don't want to use the cloud instance, then you can setup your own local instance of Avni in your data-center / server. Avni is fully Open-Source.

See Diagram Below

Documentations

  1. Implementer's guide
  2. Production Environment Setup guide
  3. Design Documentation
  4. Avni Code of Conduct

Updated 9 months ago

Introduction


A quick overview of Avni software for field data collection and reporting.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.