|
| I'll try to outline a few scenarios and what I feel are the best practices.
You perform 100% of the operations on the ground, but you don't own it and the landlord wants to be able to see yield maps.
- Keep the master copy of everything in your organization.
- Give Locations Level 2 access to the landlord to your organization, and use Field Assignment to give them access to just their fields.
- If you don't want them to have access to your account, then you will just need to manually send them the data when operations are complete.
You do custom application work, owner plants and harvests
- This gets trickier. The key thing to keep in mind is where the master source of the important data resides. The key here is the guidance lines and even better... autopath lines. As the custom guy doing application, best case scenario is that you can use the planting data to have an autopath line so you don't have to deal with making / managing guidance lines of your own.
- To do this... two options... 1 - you'd need to move your sprayer etc into the farmers org to take advantage of syncing the data with data sync. If you do a ton of work together, this can make sense to move the machine in and out. 2 - have the owner make a work plan that includes everything you need to execute. If the owner makes it, they can include the autopath lines, correct boundary etc. The Work Plan then functions like a setup file and you can move it to another organization and transfer to the machine.
This is an area we'd like to improve, as this is currently clunky and without diligent management can lead to inconsistent copies of fields / boundaries / lines. | |
|
Operations Center Partner Organization
