Farmer's Future

Edited and updated for changes made in code

Web, Mobile App, or Something Else?

Our solution that we are creating is a web service that is tailored to the crew leader for data collection. It would be accessible on a tablet or similar internet accessible device to gather the information of the farm workers in a sleek and simple way. Future versions or updates to our system would include empowering the farm workers by giving them access once on the farm to check in themselves and take these surveys without the need for a crew leaders interventions and to boost that sense of anonymity.

Executive Summary

We are building a web application where data can be gathered from farm workers about their health and their working conditions on a farm. This data will be stored and collected by the crew leader that will go to the farm owner to make sure that his farm meets OSHA requirements. The main purpose of this is to ensure that OSHA regulations for work and safety are met in each farm as results are collected from farms across the region. The farm owner will be able to see “red flags” in the data collected, such as work health and safety violations, and fix them before the data collected goes to OSHA or they visit for a random visit.

Inspiration

We have a few members who have had relatives working on farms just like the ones we are building a system for today. One key part we wanted to capture and improve upon is the relationship between the farm workers and the higher ups, including the crew leader and farm owner in regards to data collection regarding the workers health and safety.

What it does

Our goal for this project is to design a web based data collection application that will streamline and modernize part of the Crew Leader’s duties. Currently, the crew leader uses pen and pencil to take down the information of 1-20 farm workers who may not speak English, Spanish or may have little reading capabilities. Add that to an already existing mistrust of the crew leader and the farm owners, these farm workers are hesitant to give out any information. Our hope is with a universally understood UI and form input solution, that the farm workers will have a better time giving important and valuable information regarding their health and safety to their crew leader. This information will go up the ladder to the farm owner, minus their names, and then eventually OSHA for analysis across multiple farms that will help each farm that is giving out any “red flags” and may need attention for policy violation. Our end goal is to create more trust from the farm workers and to empower them to take better care of themselves when working on the field.

How we built it

Web application; Ability to work for majority of users with mobile phones or tablets. Makes it easy for Crew Leader to gather data on the go. We will use PHP as the web service with the database, both hosted on Amazon Web Services (AWS), and have a front end that is designed with Bootstrap, which is also hosted on AWS.

Challenges we ran into

Creating a universally understood and accepted UI so that any of the farm workers can interact with it through the crew leader.
Creating thorough use cases that will allow us to refine and flush out our system so it works for as many possible cases.
Finding a way for the crew leader to be alerted to a possible emergency or what we call a “red flag” where a farm worker isn’t taking breaks or hydrating.
Breaking down tasks to simple components for each member to work on and have a say in.

Milestones

Database
Test data in database
HTML pages
Javascript to make it more functional
Bootstrap to improve aesthetic
PHP to make REST API for CRUD operations
Functional leader, owner, log in
Crew Leaders signing in farm workers
Farm workers taking survey
OSHA policies and regulations posted on we service accessible by farm workers
Anonymous complaint system functional

Functional Requirements

The system will gather complaints from farm workers
Allow gathered data to be anonymized
The system shall gather information about shifts, breaks, water breaks, restroom breaks, etc.
The system will gather all data into a database
The system will be able to be used to register a new employee ##Nonfunctional Requirements *The system shall only collect data when the worker is at the job site *The system should not reveal who submitted a complaint *The system shall not allow the database of survey results or complaints to be modified after original insertion

Accomplishments that we're proud of

Getting our thoughts together in a cohesive manner and creating a working SRS for our planned system. Learning alongside each other and discovering our individual strengths and weaknesses.

What we learned

Learned how we we best as a team, how to give constructive criticisms in our conversations and keep each other on task.

What's next for Farmer's Future

Refine and fully develop our system so that it can be expanded upon so the scope of our project can be expanded to include the wants and needs of other actors in the case.

Design Features

Our web service will ideally be run on a tablet like piece of hardware that the crew leader can carry around. After logging into the system using unique identifiers, the crew leader will then be able to assist or allow the farm workers to enter their data such as check in time and names when the work day starts. Towards the end of the day the system can then be used again for check out times and a survey of sorts that focuses on the workers health and quantifying how many bathroom or water breaks and if they are hurt or sick. The workers will be met with a friendly UI that focuses more on visual representations to try and overcome any language or literacy barrier that may be present. After any data is submitted by the user, the data is sent to a PHP Api via jQuery AJAX.

Roles

Team Leader Augustine Orozco yesthisisaugustine@gmail.com Back end
Jashmit Singh jashmit04@gmail.com German Ortega germang.ortega@gmail.com Front end Design Vanessa Cruz vcruz1221@gmail.com

Functionality
Jesus Lopez Reynosa     jesuslopezreynosa@fastmail.com  
Augustine Orozco            yesthisisaugustine@gmail.com

Built With

Submitted to

Build A Farmer's Future
- Winner First Place

Created by

As the team leader i made sure that my team stayed on task and limited the scope to what we could actually deliver and do within the time provided. I also acted as the liaison between our team and the mentors/organizers that were there to help us. This included asking questions that covered either specific parts of our system or ones that were apart of our vision for the system we are going to create. I assisted in assigning tasks to each member based off their strengths and what part of the design documentation they will be doing. I worked on the SRS via Google Docs so my team could view my progress and edit along side me. I will also be contributing on the functional front end of the system when we get to the programming stage.

Augustine Orozco
Created Database schema. And the ERD. Started conversations that allowed us to refine our requirements.

Jashmit Singh
Helped develop database schema and ER diagram. Creating back end services for team use.

German Ortega
I worked on both the front and back end of the web application. I helped create the database schema. I alsocreated the wireframe mockups. I will be working on the web design, making the web application responsive by using bootstrap.

Vanessa Cruz
I helped with the planning for the project so that it flows together. I will also be working on the Functional front end, the Web UI.

Jesus Lopez Reynosa

Updates

Augustine Orozco started this project — Nov 03, 2016 05:59 PM EDT

Leave feedback in the comments!

Log in or sign up for Devpost to join the conversation.