Overview:
Crop Plans and Field Plans might sound similar, but they function differently in Traction Enterprise.
Requirements:
- Fields/Boundaries and Inputs must be set up before making Crop Plans and Field Plans.
Answer:
Crop and Field Plans were intentionally designed in Traction Enterprise to interact with each other minimally... For example:
Say you make a single Crop Plan for wheat fields. On Field Plans page you drag over the plan to all 10 of your wheat fields for this year. Two months later in "Field 7" there is an insect outbreak, so you add a "Spraying Task" to that one field, assign Work Orders, etc. In this case, you wouldn't want an additional "Spraying Task" added to your wheat Crop Plan template, nor would you want it added to all your other fields containing that Crop Plan template either.
The only interaction between Crop Plans and Field Plans is that Crop Plans are assigned to fields and become a Field Plan.
Crop Plans
- Crop Plans are templates that are used as a foundation for Field Plans.
- Once applied to fields, you can customize Crop Plans to the individual field.
- Changes to a template on the Crop Plans page do not affect fields where the plan was already assigned.
- Create Crop Plans on the Operations>Plans>Crop Plans page.
Field Plans
- Make changes at the field level via Task Manager.
- Changes you make at the field level do not change the Crop Plan template.
- Create Field Plans on the Operations>Plans>Field Plans page.
Related Articles:
How can I quickly modify my Crop Plans?
How should I work with an existing field plan when I need to replant a crop?
How do I remove a Crop Plan from a Field Boundary?