12 VIMS/FEED
12.1 Overview
FEED is a small company owned by Chris Bonzek who works in association with Virginia Institute of Marine Science (VIMS), a division of the College of William and Mary. In Virginia, the State does not conduct any research or monitoring of the state aquatic resources; VIMS and other universities conduct all aquatic monitoring.
VIMS has been using electronic data collection since 1980’s and ‘FEED’ (Fisheries Environment for Electronic Data) is an app configuration method that VIMS ended up developing to provide customization of their own field data entry software. Now, many people use VIMS/FEED (form software/customization) across the country and in Canada. Thus, FEED was specifically developed for fisheries monitoring and, as a business, provides complete individualized customization of Form and Access database for each specific survey requirements.
12.2 VIMS/FEED: Key Features
- Can read in data from many sources and normally uses access for a database.
- Can create manual backups to csv or backup the whole app database.
- Can view a summary report, based on access queries.
- QAQC queries can be included in the data entry tool (e.g., combo boxes, length/weight checks, out of range values etc).
- Hierarchical structured data.
- Can have multiple data collecting stations that feed into one database.
- Can be programmed such that the collection form adjusts depending on what data you collected for certain species; these adjustments can be based on multiple conditions (e.g., species and size).
- Many different sample applications.
- GPS info collected from any GPS device:
- Tow Distance: app records actual track, not just calculating difference between start and end coordinates.
- Any GPS unit can be used (even the small hand-held version); an NMEA stream starts each sentence with an ID. As long at FEED knows what it is, can parse it out.
Some links for VIMS and FEED:
- Description on VIMS site: https://www.vims.edu/research/departments/fisheries/programs2/multispecies_fisheries_research/feed/index.php
- Main website: https://www.feedapps.net
- Youtube video featuring FEED: https://www.youtube.com/watch?v=ko-Yv3xk7kA
12.2.1 External Device Interface
The VIMS/FEED app is designed to use a Local Area Network in contrast to other app that have an on-line interface or cloud-based data transfer options. Two key advantages of keeping the data collections and storage local: 1. no change in behavior of the tool if the survey loses internet connectivity; and 2. Ease of connection to peripheral devices such as fish boards, scales, GPS systems via a LAN router.
12.2.2 Form Development
The FEED App works in conjunction with the VIMS Form software which is a generic form program writtenm in ____ (a .NET programming language). The FEED ‘App’ consists of an Access database (12.3) and clear text file (12.2) which tells .NET software how to interact with database and how the form appears on the screen.
The FEED approach is not attempting to be a user friendly app development tool, but rather a customization service. Chris Bonzek indicates that, after the initial survey configuration set up, many people learn how to make adjustments to the configuration file independently of his help.
12.2.3 Form Appearance
The VIMS/FEED App provides a clear data entry interface with a variety of controls on the allowable values entered, including drop down, radio buttons, calculated values.
12.2.4 Data Output Format
VIMS/FEED is configured to work with and Access database. Survey data collections are stored in Access db as an intermediate location, but data tables will need to be formatted further to establish the final database format (using a processing script: R, Python, SAS, other).
12.3 Criteria Tables
For in-depth definitions of each criteria, see e-device comparison criteria.
12.3.1 Forms Options
Category | Feature | Available | Description | Group Notes | External Reviews |
---|---|---|---|---|---|
Data entry validation/QC | Geo-referencing | Yes | Can read any data in a NMEA data stream and/or can record continuous GPS data. | ||
Constrained choices from a list | Yes | User entries can be constrained via drop-down boxes, allowed-entry lists, or range checks. | |||
Rules guiding answer series (e.g., “Conditional Questions” and “Skips”) | Yes | Data fields can appear or disappear based on entries made in other fields. Data fields can be defined as ‘required.’ Data fields can appear or disappear based on entries made in other fields. | |||
Constrained choices from an external table or set of rules | Yes | Can compute responses; For example, entered weight data can be checked against predicted values from species-specific l-w regression parameters. | |||
Form Version Control | Yes | ||||
Real-time Data Review | Yes | There are several ways to view entered data. | |||
Real-time Edit (“on the fly”) | Yes | Data can be altered either within the FEED application or directly in the Access data base | |||
Ease of Form Development | Intuitive form design tool | No | The software interprets instructions from a clear text file written in a proprietary scripting language. These instructions tell the software how to interact with the bespoke MS Access data base and with any external devices as well as how to present data screens to the users. | ||
Coding language required? | Yes | See above | |||
Different styles of question types | Yes | ||||
Flexibility to configure in a logical order for field entry (e.g., nested desgin) | Yes | Each application is customized according to the survey’s needs and specifications. | |||
Other IEP Survey needs | Permissions Management | No | Permissions management is not a feature. | ||
Muti-users of an app | Yes | ||||
Off-line capacity | Yes | ||||
User Accessability | Multiple-language options | No | |||
Font adjustment/Speak-to-text | No |
12.3.2 Data Interface
Category | Feature | Available | Description | Group Notes | External Reviews |
---|---|---|---|---|---|
Database interface | Cloud-storage | No | FEED is based on a local access network (LAN). | ||
Direct integration with database | No | Data is stored in a custom MS Access data base specific for app function and collections. The data base can be located either on the user’s local computer or on a file server on a LAN. | |||
Integrate data from local tables | Yes | Specific parameters or reference listings can be added to the FEED app Access db to be used by the app. | |||
Edit after transfer | Editing data ‘on-the-fly’ (data already submitted) | Yes | Edits can be made either in FEED or directly in Access. | ||
Data format | Open (standard) format output | Yes | Data is formated in MS Access relational db tables. | ||
Data format logical / useable | Yes | The data base is in a hierarchical / relational structure. | |||
Data transfer | Real-time data transfer | No | Because FEED is based on a LAN, there is not a way to transfer data to the final database. Further, a data configuration step is required to transfer from FEED Access db to the final db. The FEED CEO says he uses SAS to process the data and it takes him a day or two. | ||
Cloud connectivity & back up | No | ||||
Data change logs | Audit trails (data version control) | No |
12.3.3 Photo Integration and External Sensors
Category | Feature | Available | Description | Group Notes | External Reviews |
---|---|---|---|---|---|
Photo Integration | Collect photo & assoc. with element | Yes | FEED can interact with a camera in two ways. It can activate a Windows Web Cam and associate the image with the particular record. For other cameras, FEED can monitor any particular file folder and when a new image file appears it then can associate the file with the current record. | ||
Ease of interface | Yes | Easy to use. Must be careful in the script programming. | |||
Multi-photo per element (and # limit) | Yes | One photo per data field but can include multiple data fields if multiple photos are needed. | |||
Drawing-on/ Annotating photo | No | ||||
X-tern sensors | GPS from device | Yes | Interaction with external sensors is very easy with a LAN type of app set up. | ||
Integrate data from bar codes | Yes | Interaction with external sensors is very easy with a LAN type of app set up. | |||
Integrate data from external sensors | Yes | Interaction with external sensors is very easy with a LAN type of app set up. |
12.3.4 Hardware Platforms
Feature | Available | Group Notes | External Reviews |
---|---|---|---|
Smart Phones and Tablets | |||
- iOS (phone and tablet) | No | ||
- Android(phone and tablet) | No | ||
Desktop/laptop | |||
- Windows 7,8,10, 11 | Yes | Tablets, laptops, desktops. | |
- MacOS (computer) | No | ||
- Ubuntu Linux | No |
12.3.5 Security Factors
Feature | Available | Description | Group Notes | External Reviews |
---|---|---|---|---|
Where’s the application/product origins from? | U.S. Virginia. | |||
Is the application Cloud based, and if so, where? | N/A | |||
Where is the data being stored for the application? | Either on the local computer or on a file server on a LAN. | |||
Is the data center FedRAMP certified? | N/A | |||
Online Security measures | N/A |
12.3.6 Business Model and Customer Support
Feature | Available | Description | Group Notes | External Reviews |
---|---|---|---|---|
Price (Option 1) | Software costs $2K for each 5-seat license. | 2000 | The price seems very reasonable for the amount of programming/Access db set-up time. | |
Price (Option 2) | N/A | |||
Business model | Application development is a fixed cost once a price is agreed upon and is set until the customer accepts the application. | FEED is a very small company (1 CEO and collaborators at Virginia Institue of Ocean Science) | ||
Technical Support | Support for subsequent updates may be gratis or may require additional costs, again depending upon the complexity. References are available. |