The farm data model of SAP Intelligent Agriculture is an entity relationship model deeply embedded into the solution. It is enhancing the standard SAP One Domain Model capabilities with farming specifics.
It provides all necessary entities that are enabling agribusiness companies to establish and maintain a digital model of their organizational structure around farm and fields, called farming master data. In addition to that, the model offers capabilities to store and work with farming transactional data, like tasks.
Farm master data categorizes all farm data that describes the context for transactional data, and is classified through the following attributes:
- Has no fixed business validity timeframe
- Provides context for transactional and / or seasonal data
- Is not an Indicator definition
Farm transactional data categorizes all farm data that describes transactions within and across systems, and is classified through the following attributes:
- Usually data with frequent changes
- Process related data
- Data with a fixed business validity timeframe
A third layer in the farm data model enables configuration patterns for customers to adapt the data model to a certain extent.
Types of configuration data are as follows: Characteristics, Entity Types, and the KPI concept that spans across all layers of the farm data model.
Characteristics are descriptive, non-measured attributes that are enhancing master data entities to be configured individually according to customer needs.
Entity types allow you to categorize and classify certain entities within the data model to be better able to organize, filter, and analyze them (for example, Location Type could be used to segregate mills from storages or used for process related purposes, classifying locations).
KPIs allow you to track performance indicators within the solution and are attached to master data entities. A KPI value can be measured from the field, like total tonnage of yield extracted, it can reflect a prediction by a data science service, or it can be an estimate based on historical knowledge or the outcome of a planning process.
The most central master data entities are Farm, Field, Area, Season, Crop, Variety, and Resource.
- Farm - A farm is an organizational entity that runs farming operations.
- Field - A field is an organizational entity that represents a certain area where farming activities are conducted.
- Area - An area is a generic entity to represent geospatial areas. Areas are used in different contexts in the system - for example, associated to a field to represent field boundaries.
- Season - Season is an entity to describe a defined timeframe during which agricultural activities are executed.
- Crop - A crop is an entity to identify different categories of plants cultivated by farmers. Crops can be cultivated as annual crops or perennial crops.
- Variety - Varieties are used to represent different plant varieties that can be or are cultivated for a specific crop.
- Resource - Resources are people, animals or equipment which could be used to execute a Task.
The most central transactional data entities are Work Order, Farming Task, Task Record, Recommendation, and Prediction:
- Work Order - Work Orders can be used to group tasks that are belonging together from a controlling or order management perspective. The different tasks in one work order can span across different fields.
- Farming Task - A task represents a farm activity that is planned to be executed, in execution, or has been executed.
- Task Record - Represents a record about the actual execution of a task.
- Recommendation - Represents a farming related recommendation - for example, from an expert or decision support model.
- Prediction - Represents a farming-related prediction - for example, a yield prediction calculated by an AI model.
The Crop Zone entity is marked in green because it has both aspects of master data and transactional data since it's used for seasonal planning.
