Skip to content

Commit 86ea256

Browse files
committed
edit pass: data-manager-for-agri-concepts
1 parent 677c570 commit 86ea256

File tree

3 files changed

+105
-86
lines changed

3 files changed

+105
-86
lines changed

articles/data-manager-for-agri/concepts-isv-solutions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,4 +57,4 @@ To install the preceding solutions, see the [article about working with ISV solu
5757

5858
## Next steps
5959

60-
* [Test the Azure Data Manager for Agriculture REST APIs](/rest/api/data-manager-for-agri).
60+
* [Test the Azure Data Manager for Agriculture REST APIs](/rest/api/data-manager-for-agri)

articles/data-manager-for-agri/concepts-llm-apis.md

Lines changed: 25 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -9,58 +9,57 @@ ms.date: 3/19/2024
99
ms.custom: template-concept
1010
---
1111

12-
# About Generative AI and Data Manager for Agriculture
12+
# Generative AI in Data Manager for Agriculture
1313

14-
The copilot templates for agriculture enable seamless retrieval of data stored in Data Manager for Agriculture so that farming-related context and insights can be queried in conversational context. These capabilities enable customers and partners to build their own agriculture copilots. Customers and partners can deliver insights to users around disease, yield, harvest windows and more, using actual planning, and observational data. While Data Manager for Agriculture isn't required to operationalize copilot templates for agriculture, the Data Manager enables customers to more easily integrate generative AI scenarios for their users.
14+
The copilot templates for agriculture enable seamless retrieval of data stored in Data Manager for Agriculture so that farming-related context and insights can be queried in conversational context. These capabilities enable customers and partners to build their own agriculture copilots.
1515

16-
Many customers have proprietary data outside of our data manager, for example Agronomy PDFs, market price data etc. These customers can benefit from our orchestration framework that allows for plugins, embedded data structures, and sub processes to be selected as part of the query flow.
16+
Customers and partners can deliver insights to users around disease, yield, harvest windows and more, using actual planning, and observational data. While Data Manager for Agriculture isn't required to operationalize copilot templates for agriculture, the Data Manager enables customers to more easily integrate generative AI scenarios for their users.
17+
18+
Many customers have proprietary data outside of our data manager, for example Agronomy PDFs, market price data etc. These customers can benefit from our orchestration framework that allows for plugins, embedded data structures, and sub processes to be selected as part of the query flow.
1719

1820
Customers with farm operations data in our data manager can use our plugins that enable seamless selection of APIs mapped to farm operations today. In the time to come we'll add the capability to select APIs mapped to soil sensors, weather, and imagery type of data. Our data manager focused plugin allows for a combination of results, calculation of area, ranking, summarizing to help serve customer prompts.
1921

2022
Our copilot templates for agriculture make generative AI in agriculture a reality.
2123

2224
> [!NOTE]
23-
>Azure might include preview, beta, or other pre-release features, services, software, or regions offered by Microsoft for optional evaluation ("Previews"). Previews are licensed to you as part of [**your agreement**](https://azure.microsoft.com/support) governing use of Azure, and subject to terms applicable to "Previews".
24-
>
25-
>The Azure Data Manager for Agriculture (Preview) and related Microsoft Generative AI Services Previews of Azure Data Manager for Agriculture are subject to additional terms set forth at [**Preview Terms Of Use | Microsoft Azure**](https://azure.microsoft.com/support/legal/preview-supplemental-terms/)
25+
> Azure might include preview, beta, or other prerelease features, services, software, or regions offered by Microsoft for optional evaluation. Previews are licensed to you as part of [your agreement](https://azure.microsoft.com/support) governing use of Azure, and are subject to terms applicable to previews.
2626
>
27-
>These Previews are made available to you pursuant to these additional terms, which supplement your agreement governing your use of Azure. If you do not agree to these terms, do not use the Preview(s).
27+
> The preview of Azure Data Manager for Agriculture and related Microsoft generative AI services are subject to [additional terms](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). These additional terms supplement your agreement governing your use of Azure. If you don't agree to these terms, don't use the previews.
2828
2929
## Prerequisites
30+
3031
- An instance of [Azure Data Manager for Agriculture](quickstart-install-data-manager-for-agriculture.md)
3132
- An instance of [Azure OpenAI](../ai-services/openai/how-to/create-resource.md) created in your Azure subscription
3233
- You need [Azure Key Vault](../key-vault/general/quick-create-portal.md)
3334
- You need [Azure Container Registry](../container-registry/container-registry-get-started-portal.md)
3435

35-
> [!TIP]
36-
>To get started with testing our Azure Data Manager for Agriculture LLM Plugin APIs please fill in this onboarding [**form**](https://forms.office.com/r/W4X381q2rd). In case you need help then reach out to us at [email protected].
36+
## High-level architecture
3737

38-
## High level architecture
39-
The customer has full control as key component deployment is within the customer tenant. Our feature is available to customers via a docker container, which needs to be deployed to the customers Azure App Service.
38+
The customer has full control as key component deployment is within the customer tenant. Our feature is available to customers via a docker container, which needs to be deployed to the customers Azure App Service.
4039

4140
:::image type="content" source="./media/concepts-llm-apis/high-level-architecture.png" alt-text="Screenshot showing high level feature architecture.":::
4241

43-
We recommend that you apply content and safety filters on your Azure OpenAI instance. Taking this step ensures that the generative AI capability is aligned with guidelines from Microsofts Office of Responsible AI. Follow instructions on how to use content filters with Azure OpenAI service at this [link](../ai-services/openai/how-to/content-filters.md) to get started.
42+
We recommend that you apply content and safety filters on your Azure OpenAI instance. Taking this step ensures that the generative AI capability is aligned with guidelines from Microsoft's Office of Responsible AI. Follow instructions on how to use content filters with Azure OpenAI service at this [link](../ai-services/openai/how-to/content-filters.md) to get started.
4443

4544
## Current farm operations related uses cases
4645

47-
We support seamless selection of APIs mapped to farm operations today. This enables use cases that are based on tillage, planting, applications, and harvesting type of farm operations. Here's a sample list of queries that you can test and use:
46+
We support seamless selection of APIs mapped to farm operations today. This enables use cases that are based on tillage, planting, applications, and harvesting type of farm operations. Here's a sample list of queries that you can test and use:
4847

49-
* Show me active fields
50-
* What crop was planted in my field (use field name)
51-
* Tell me the application details for my field (use field name)
52-
* Give me a list of all fields with planting dates
53-
* Give me a list of all fields with application dates
54-
* What is the delta between planted and harvested fields
55-
* Which farms were harvested
56-
* What is the area of harvested fields
57-
* Convert area to acres/hectares
58-
* What is the average yield for my field (use field name) with crop (use crop name)
59-
* What is the effect of planting dates on yield for crop (use crop name)
48+
- Show me active fields
49+
- What crop was planted in my field (use field name)
50+
- Tell me the application details for my field (use field name)
51+
- Give me a list of all fields with planting dates
52+
- Give me a list of all fields with application dates
53+
- What is the delta between planted and harvested fields
54+
- Which farms were harvested
55+
- What is the area of harvested fields
56+
- Convert area to acres/hectares
57+
- What is the average yield for my field (use field name) with crop (use crop name)
58+
- What is the effect of planting dates on yield for crop (use crop name)
6059

6160
These use cases help input providers to plan equipment, seeds, applications, and related services and engage better with the farmer.
6261

6362
## Next steps
6463

65-
* Fill this onboarding [**form**](https://forms.office.com/r/W4X381q2rd) to get started with testing our copilot templates feature.
66-
* View our Azure Data Manager for Agriculture APIs [here](/rest/api/data-manager-for-agri).
64+
- Fill in [this onboarding form](https://forms.office.com/r/W4X381q2rd) to get started with testing the copilot templates feature.
65+
- Test the [Azure Data Manager for Agriculture REST APIs](/rest/api/data-manager-for-agri).

0 commit comments

Comments
 (0)