FieldVizion for Android: Basics
FieldVizion is the mobile app (available for iOS and Android) for the OneVizion platform that allows data collection in the field. Data input is structured using WorkFlows set up by OV administrators on the web platform of OneVizion; whoever then needs to enter the data installs the app, receives the relevant WorkFlows, and enters the data in a smooth and comprehensible fashion.
FieldVizion makes assignments like equipment inspection, smooth and intuitive by breaking them into easily manageable tasks and providing each task with comprehensive instructions and easy-to-follow steps for acquiring and entering the necessary information.
The Anroid App supports devices running version 10+ or greater.
Installation and login
FieldVizion is available in Google’s Play Store. Installation is the same as any other Android app: open the app’s page (FieldVizion UAT if you use OneVizion UAT platform) in Play Store and tap “Install”.
After the app is installed, there are two ways for you to log into the system:
You can open the link provided in the notification message with the FieldVizion app. This scenario will log you in with access to only the specific WorkFlow instance, the one that the email was notifying you about. Or,
You can manually enter your regular OV link and credentials. In this case, you’ll have access to all of the WorkFlow instances assigned to you.
A WorkFlow is a template reflecting the specifics of a certain work process. For example, an on-site equipment inspection WorkFlow will:
Provide the worker with data entry points for the time of their arrival to the site, for every relevant parameter (e.g. model, S/N, photo, hours in operation, overall condition, last maintenance date/time, etc) for each piece of equipment (e.g. battery, PSU, antenna, etc), and inspection finish time;
Allow the worker to mark the inspection complete and automatically assign the finished dataset to a supervisor for inspection;
Depending on their decision, assign the WorkFlow instance back to the worker for refinement, to a maintenance crew if maintenance is necessary, or mark the inspection complete and finish the instance.
A WorkFlow template is set up by the OneVizion Administrator in the web platform, for each type of work process. WorkFlow instances will be created for each specific site or job, for which the work process will need to be done.
WorkFlow
So, we’re done with the initial setup and logged in. The WorkFlow template used in this example is called Advanced Checklist. For the purpose of this document, WorkFlows and Checklists will be used interchangeably, as a Checklist is a type of WorkFlow that allows the collection and validation of data from the Field. If multiple instances of the Advanced Checklist is assigned to the User, they will see all the instances listed under ‘Advanced Checklist’. Users can choose to download specific instances of the Checklist, if they need it available offline. Tapping the download icon will start the download of the specific Checklist. Downloaded WorkFlow instances are available for offline work; changes will be uploaded to OneVizion when FieldVizion goes online.
WorkFlow instances in Offline mode are completely functional with just a few restrictions:
For previously uploaded media only the preview thumbnails will be available offline.
Fields configured as Db Selector, Selector, Trackor Selector, Calculated, Multiselector, Rollup, and Calculated Data Types depend on connectivity and will contain locally stored data if there’s any available, otherwise they will be empty.
Note the “Sort by” switch at the top of the list. WorkFlows can be sorted by name or by distance from your location to the site (if the location is available).
WorkPlan instances attached to sites with set locations will also be available on the map. This feature allows the users to select and open sites from the map and to create routes easily.
Let’s open a WorkPlan instance.
Collecting Data - WorkFlow Steps
A WorkFlow can be grouped into further categories to make it easier for the FieldVizion users to collect data. Fields, typically for collecting photos, yes/no answers, and any additional data are grouped logically into Steps or Checklist Items. WorkFlows can be approved/rejected at this level. Checklist Items/Steps can then be grouped, optionally into Sections. Allowing a tiered approach (WorkFlow → Sections → Steps/Checklist Items → Fields) makes it easier for the user to collect, submit and review the data from the Field.
In the screenshot below, each of the displayed entries is a WorkFlow Step. Steps can contain a set of fields to be populated in the course of your work. Here, the “Start - Sign IN/OUT” step contains fields for everything having to do with a worker signing in and out at a site:
The sign-in time in this WorkFlow should be filled as the worker arrives on site and the sign-out time – as they leave. In this example, only the two timestamp fields are required (see the asterisks).
Also present in this screenshot are the four options for uploading photos or videos: “Photo”, “Photo & Edit”, “Video” and “Files”. “Photo” and “Video” will simply take you to the camera to take the photo or video. “Files” allows the user to select an already existing photo or a video, and “Edit” will launch the editor after the photo is taken. The editor provides basic instruments: Exposure, Crop, and Orientation. It also allows drawing over the picture and adding text and stickers.
Here’s what the second Step in this WorkFlow might look like when it’s completed:
The barcode icon opens a barcode scanner, allowing the user to quickly capture serial numbers.
Fields like Equipment Type, Item Pass/Fail, and Item Approved need the user to pick one of the already existing options:
Once a Step is completed (i.e. all the necessary fields are populated) its Status will be automatically set to “Pending Acceptance” until it is accepted or rejected by another OneVizion user. This user can be a supervisor or a peer: all of this behavior is highly customizable and is set up by the WorkFlow Administrator in the OneVizion web platform.
Completing the WorkFlow
When the necessary data is collected for all the Steps, the user can then ‘Complete the WorkFlow’. The exact process after this point is also highly customizable. In our example, a completed WorkFlow will be removed from the work queue, marked accordingly, and assigned to the relevant reviewer, who will determine whether the WorkFlow needs more work, in which case it can be assigned back to the employee, or contains all the necessary information and is approved.
