Tower Inspector

• Contents

  1. Tower Inspector
  2. Introduction
  3. Differences between Inspector and Tower Inspector
  4. Features Not Yet Implemented

Introduction

• The Tower Inspector is based on the Rfid Web Application and the Inspector Android App. The original goal was to allow organisations to perform distributed data collection and centralized data processing and reporting.

• The main properties of the system:
  • Two databases are on the server side
    • PostgreSQL database to keep user data and to generate report from (PostgreSQL is ideal for reporting)

    • CouchDB for bi-directional data synchronization between the server and the Inspector Android App (CouchDB is ideal for synchronization)

    • The PostgeSQL database has to be synchronized manually from the CouchDB database from the Rfid Web Application to generate reports with actualized data

  • Same user credentials (email address and password) are used to login to the Rfid Web Application and to connect to the server from the Inspector Android App

    • The user credentials are entered and verified with an email confirmation system on the Rfid Web Application

    • If a user account is confirmed, that the user is getting a registered status on the server side, what is enough to use the Inspector Android App, but has to be changed to access services on the Rfid Web Application

    • There are 4 access level on the Rfid Web Application: registered, viewer, normal and admin. The level of a user can be changed by a user with admin level

  • Configuration for location and inspection data templates are saved in CouchDB and has to be downloaded (synchronized) to the Inspector Android App. Therefore the app can not be used until the user credentials entered and the configuration downloaded.

Differences between Inspector and Tower Inspector

• While the Inspector Android App is used mainly by technical peoples (Ingenieurs, inspectors, etc.) the Tower Inspector Android App has to focus on everybody with any education level. Therefore the following changes where made:

  1. Entering credentials is forced until the app is initialized (first download of location and inspection configuration is done)
  2. Only one location per type can be entered and they appear on the home page of the app as big buttons
  3. Clicking on a location the user is guided through all inspections (questions) belonging to a location
  4. The user is forced to attach photo(s) to the inspections if required (NOT IMPLEMENTED YET)
  5. Photos moved to the inspection edit screen
  6. On the main page a "Verify data and upload" button should help the user to upload his locations, inspections and photos. (NOT IMPLEMENTED YET)

Features Not Yet Implemented

1. Force saving photos if at least one photo is required
2. Question without real input, only photos required
3. Checking if all questions answered and photos saved