The creation of a task can be initiated from 3 applications within the solution: from the Task Scheduling, the Task List, or the Farming Cockpit.
After selecting Create Task, the user must fill in information. The task entity has several attributes that help to plan and organize farming activities, some of them are mandatory during task management and are marked with an asterisk "*". Different fields are required at different stages to move to different statuses (learn more about Task Status Rules).
Here’s an overview of the header attributes available:
- Task Name*:
The speaking name of the task to be executed.
- Start Date and End Date*:
The planned start date and end date of the task associated to start time and end time. This information is required before changing the status to In Progress.
- Status*:
The task status is a field that will be automatically populated and changed based upon the actions performed.
Here are the various statuses available in SAP Intelligent Agriculture:
- Draft: When the task is created and saved, it will be set to Draft status by default. This means it’s not finished or not ready to be published.
- Open: When all the mandatory data is maintained, the user will be able to set the status to Open to indicate it’s a final version, but not released/started yet.
- In Progress: When the processing of the task has started, status will be set to In progress.
- Completed: When the processing is finished, the status will be set to completed, at which point it cannot be edited anymore.
- Canceled: The task can also be canceled and will become inactive. Only Open and In progress tasks can be canceled. A reason is required to change the status to canceled.
- Delayed: If the task is set as delayed (using the available checkbox in the header section), the user must provide a reason and will be able to track these delayed tasks through the Task Scheduling app.
- Work Order:
Work orders can be used to group tasks that belong together from a controlling or order management perspective. The different tasks in one work order can span across different fields.
Note
For additional details, see the following figure: Work Order, Tasks and Task Item Operations.
- Assignee*:
The task needs to be assigned to a user in the system, who’s assigned to role(s). The assignee is the owner of the task. Not necessarily the executor of the task, but someone who needs to look after the task from a business process perspective, such as follow-up on the statuses.
- Priority*:
A field to organize tasks by priority. The options are as follows: Very High, High, Medium, or Low.
Task information attributes include the following:
- Task Type*: Allows to group tasks into certain farming categories. For example, irrigation, fertilization, harvesting, and so on.
- Description: A free text description of the task to be performed.
- Farm*: The task needs to be associated to an existing farm. A farm is the organizational entity that runs farming operations and is responsible for the field. A farm does not need to be set up following legal/company structure. For instance, a legal entity active in farming can run multiple operational farms.
- Field*: The task needs to be associated to an existing field that is assigned to the farm previously selected. A field is an organizational entity that represents a certain area of a farm where farming activities are conducted. A field is linked to an area that defines the current field boundaries, or if the boundary is not available, giving the field size. Field and area association is one to one.
- Crop Zone: The task can be associated to a crop zone that is assigned to the field previously selected. A crop zone is an entity to identify an area where a specific crop/variety is grown during a specific season.
- Task Dependencies: A task can have a dependency on other tasks, so the user can select tasks to indicate this dependency, which will be visible in the Task Scheduling app.
- Crop Pattern Elements: These represent individual instances of spatial pattern elements in which crops are grown such as individual rows or cross-rows that should be considered for the task.
- Soil Samples: The user can associate soil samples. The soil samples need to have been previously defined in the system.
The following attributes can also be maintained on the task:
- Task Item Resources: The user can assign resources to the task, which can be a machinery (for example, a tractor), a person (for example worker, agronomist), a resource group or any other resource previously recorded in the system. Resources must be created using APIs and are further explained below.
- Task Input Materials: The task input materials are the materials that are consumed during the task. This could be water, fertilizers, or any object necessary for the given activity of the task.
- Task Item Operations: The user can assign task operations to track different activities associated to the task or to detail sub-activities of a task. A tangible example is a combine that can do multiple activities, such as cutting and cleaning simultaneously during one task. Task Item Operations need to be predefined in the system.
Here are some examples of different tasks: