Field Activity Data Collection & MI Best Practices
Mobile App | Machine Integration | Back Office |
This article is a direct result of the third customer training webinar of 2024. Here is the full webinar if you would like to see some of this information in action.
Checklist
☐ (Previous training session) > Advance Crop Year & Assign Crops to Fields
☐ Sort out how data will be collected for each equipment/activity
☐ Mobile Device Users: Download new app, Login & make practice tickets
☐ Machine Integration Users: Clear out Needs Attention Items
☐ Work Order Users: Create appropriate work orders for spring work
☐ Back Office Users: Understand how to create single & bulk tickets for data not recorded in the field
☐ Utilize your Customer Success Manager – We are here to help!
Field Activity Data Collection [Mobile App]
Steps for each user:
Download latest version for Android and iOS
Confirm everyone can login
Have each operator demonstrate that they can create a ticket, use directions and more
Mobile App Navigation:
Work Orders
Machine Integration: Work Orders may be used to communicate and track progress, but the application data will come through machine integration.
Manual Entry: Work Orders may be used with Manual Entry as a recommended way to communicate and track progress + enter field activity data.
Create Work Orders From Field Plans: Work Orders may be created from Field Plans. This can speed up the work order process and utilize work already done earlier in the season.
Manual Entry
If Machine Integration is not used, this is the preferred method of collecting data in the field
Many operations run a hybrid of Machine Integration and Manual Entry
Not all equipment is connected
Not all activities are uploaded to JD and/or Fieldview, so manual entry is the best way to provide that data
Field Activity Data Collection [Machine Integration]
Add inputs to Conservis account
Train operators to utilize products already in list vs. create new which can result in duplication
Assign crops
Add any new equipment
Establish plan to capture data that is not collected through integration
Proactively monitor and address any needs attention items
Unmatched fields, inputs & equipment
Unreviewed auto-setup items
Unit of measure mismatches
Confirm your account is authorized
Confirm Autocreate Started on Date is set to beginning of crop year
Note: Utilizing machine integration allows geo-spatial collection of data allows capturing data of each application. When combined with a full season + harvest data Zone Economics can be used to gain valuable insights into each field.
Field Activity Data Collection [Back Office]
Create tickets in bulk when appropriate.