Now that we understand the three key components of fieldwork i.e. Organisation, Services and Service Encounter - let's try to understand how Avni works and achieves various functions.

How implementation-specific mobile application is created?

Avni is a generic platform that allows any organisation doing field-based work to use it for their specific purpose. The diagram below explains the steps involved in creating an organisation-specific application from a generic platform.

1440 — Data flow of organisation, services and service encounter definition.

How does avni field user gets all the subject data on his/her device?

As we saw earlier, given the organisation work physically consists of catchments and locations. The subjects are living or located at these locations.

1726 — During organisation setup the implementer or customer IT person sets up catchments with locations and assigns them to the provider (field user)

The diagram below shows how the subjects and the subjects's complete data, which is required by the field user (and only those subjects) are made available.

1580 — Subjects belonging to the catchment of the user downloaded to their device

How Avni works in an offline mode

Avni maintains a database on the mobile device. All the data downloaded from the server is kept on this device. When the user is using the application, all the data is served from this device to the user and all the new data created by the user is stored in the mobile database. When the synchronisation happens this new data is sent to the server.

How does the generic avni mobile application behave as if it has been developed for a specific organisation?

The diagram below explains how avni app customises itself based on the complete organisational setup (explained earlier).

1792 — Avni app customises itself based on the organisation data setup present in the mobile database on the device