SPADE Overview April 2015

2 Presenters ( session) Jeremy Wilson Technology Specialist Crop IMS Joe W. Tevis, PhD Director, Agronomic Products and Services Topcon Precision Ag Dennis Daggett Senior VP, Strategic Initiatives ProAg

3 Presenters ( session) Jeremy Wilson Technology Specialist Crop IMS R. Andres Ferreyra, Ph.D. Manager of Special Projects Ag Connections Dennis Daggett Senior VP, Strategic Initiatives ProAg

4 AgGateway Overview

AgGateway North America: Mission Promote, enable and expand eBusiness in agriculture

AgGateway North America Non-Profit Established 10 years ago with 9 member companies Steady growth to what is currently over 230 member companies Does not touch any transactional data, ever!

AgGateway North America: Projects Supply Chain-Related Processes Crop Protection Seed Crop Nutrition Warehouse Management Traceability Field Operations Seeding Operations Harvest Operations Crop Input Applications Irrigation Grain Contracts Shipments Weights Grades Settlement Rail Transport Pricing

8 SPADE Standardized Precision Ag Data Exchange

9 SPADE1 and SPADE2 Scope

Scope? 10 Farm Management Information System (FMIS) Farm Management Information System (FMIS) Mobile Implement Control System (MICS)

SPADE (First project) Focus on Seeding Collected Use Cases Defined 4 core documents Crop Plan Recommendation Work Order Work Record Performed an ISO gap analysis; made recommendations to ISO Worked with AEF on recommending mechanisms to link unique identifiers to ISOXML locally-scoped IDs. Reference Data API Equipment Seed 11

SPADE2 (Second project) Reviewed Seeding Use Cases Mechanical & Non-Mechanical Harvest Crop Protection Geopolitical Context – Dependent data Reference Data APIs Equipment Seed Crop Protection SPADE Conversion Toolbox Proof of Concept 12

Much of the work in SPADE has followed the process above: User stories were obtained from growers and other SMEs. The processes described by the stories were modeled and translated into use cases usable by software companies. Data requirements or “Data Buckets” were identified by the SMEs and technical experts working together. The technical experts looked for, and proposed solutions for, gaps in ISO The final step is publishing the materials. 13 User Stories Use Cases Data Buckets ISO Gap Check Publish

14 User Stories Use Cases Data Buckets ISO Gap Check Publish There are additional aspects to the workflow, such as identifying the Reference Data that is needed to support the process. Reference Data APIs Equipment Seed Crop Protection “Other” Reference Data needs Reference Data needs Ref Data API POC Publish API Docs

MECHANICAL HARVEST Product Owner – Jeremy Wilson, CropIMS Scrum Master – Michael Larsen, Topcon Precision Ag 15

User Stories Completed Cotton Harvest Row Crop Harvest Platform Head Harvest Potato Harvest Forage Harvest Sugar Beet Harvest 16 User Stories Use Cases Data Buckets ISO Gap Check Publish

Process Modeling with BPMN Forage Harvesting Sugar Beet Harvest 17 Forage Harvesting Sugar Beet Harvest

Use Cases Completed Cotton Harvest with Baler Attachment Use Case Cotton Harvest with Traditional Module Use Case Harvest Forage Crops Harvest Row Crops Harvest with Platform Style Header Harvest Lifting Crops (Sugar Beets) 18 User Stories Use Cases Data Buckets ISO Gap Check Publish

Data Buckets Documents Forage Harvest Data Buckets Mechanical Harvest Data Buckets Lifting Crop Data Buckets: Sugar Beet Machine Reference Data 19 User Stories Use Cases Data Buckets ISO Gap Check Publish

Data Buckets Documents CategoryWODataDefinitionHappy PathISO Location WO, TPYClient CTR WO, TPYFarm FRM WO, TPYField PFD WO, MPAMachine Info DVC WO, MPAHeader Type ? WO, TSYLocation (Field BNDRY) PLN WO, PSYCrop CTP/CVT TPY Harvester Company (Contractor) CPY (Extensions) WO, TSM Harvest type (Grain Silage, Bale, etc) CRU (Extensions) WO, USM Storage (location,Type. Maintain Object) PNT (Type 4) TS, PSMCalibration Value (DDI) Missing PS, TSMPNYield per acre (DDI) 83 (volume per area); 84 (mass per area) PS, TSMPNTons/ acre (DDI) 84 (mass per area) 20

Documents to be Published SPADE2 User Stories Use cases Data Buckets ISO gap check results SPADE3 Implementation guidelines 21 User Stories Use Cases Data Buckets ISO Gap Check Publish

22 PAIL Precision Agriculture Irrigation Leadership

Introduction to PAIL SPADE’s irrigation-specific sister project Focused on developing common data formats. Deliverable is set of schemas Will work through ASABE toward a national / international standard. Two main avenues Offsite + Inbound: Water content and weather sensors As-Applied Data: Irrigation equipment manufacturers 23

25 ADAPT Ag Data Application Programming Toolkit

Business Case: Why do we need ADAPT? There are multiple formats used by the farm equipment industry to document activities and move field operations data from various systems. The formats may be proprietary or based on an industry standard. The agricultural industry lacks of a standard application data model that will facilitate the conversion and exchange of field operations data. Original Equipment Manufacturers create multiple field operations data formats (some proprietary, some not) that need to be used by multiple applications. Software companies spend significant resources creating tools to convert and manage the various field operations data formats in the industry. Customers (primarily the users of the data such as farmers and agronomists) find it difficult to extract the value from this data because it is difficult to move field operations data into the applications needed to aggregate, analyze and create insights. It requires a great deal of manual processes.

ADAPT Goal To create tools for the industry to make it easier and less expensive to exchange field operations data among software applications from a variety of companies and vendors.

28 Geopolitical Context

Requirement: Geopolitical Context AgGateway recognizes three important context categories: Process, e.g., Order-to-Cash Grain Shipments Field Operations Industry (or industry segment), e.g., Seed Chemical Crop Nutrition Geopolitical, e.g., Europe North America United States France European Union NAFTA AgGateway has done its best to leave room in its work for the implementation of the effects of geopolitical contexts other than North America.

The ContextItem Object We’ll implement regulatory data as a set of (potentially nested) name-value-unit of measure tuples, associated with various other objects in the model. The GPCType is a code that identifies what a given ContextItem contains. These objects can be nested 30

31 Regulatory Reporting

User Stories Completed USDA Single Source Reporting RMA Reporting FSA Reporting NRCS Reporting AMS Restricted Use Pesticide Reporting EPA WPS Recordkeeping FDA Reporting California Pesticide Use Reporting 32 User Stories Use Cases Data Buckets ISO Gap Check Publish

Use Cases Completed Report to USDA/RMA Report to USDA/FSA California Pesticide Use Reporting 33 User Stories Use Cases Data Buckets ISO Gap Check Publish

Data Buckets Documents Have identified data buckets for the use cases we worked on. 34 User Stories Use Cases Data Buckets ISO Gap Check Publish

Data Buckets (ex.: RMA Planting Report) 35 Data ItemDescription Field description FSA assigned Farm Serial Number, Tract Number, Field ID Number (the combination of these 3 numbers is known as the Common Land Unit (CLU)) Crop Identifier Crop description from FSA maintained Commodity Validation Table (CVT). This will include the crop Type and Practice as identified in the CVT. Planting Date The actual date the seed was placed in the ground in a field. Field location The Public Land Survey System identification or other acceptable legal location description of the field location. Unit Number The unit identification number assigned by the crop insurance agent. The unit identification number is created under the rules established by the USDA-RMA and designates the type of insurance coverage the entity has selected. Entity Legal Entity in control of the production of the crop. Entity ID Number The identification of the legal entity in control of the crop. This may include any party that has a % interest in the crop being produced (this is known as entities with Substantial Business Interest (SBI)). Entity Address The official address of the entity in control of the production of the crop.

ISO Extensions? This data is not very compatible with the international scope of ISO11783 XML: It is data that would reside in an FMIS and would not be sent to a machine, and it is specific to the US, or to a state or other jurisdiction therein. Instead of trying to include these extensions into the ISO standard, we are introducing them into the ADAPT data model first, including them in ADAPT’s representation / reference data system, and evaluating future action regarding ISO or other standards. 36 User Stories Use Cases Data Buckets ISO Gap Check Publish ADAPT Object Model

37 Glossary

agglossary.org: Purpose  Purpose: Create a comprehensive agriculture glossary.  Goal: Develop a one-stop location in the form of an online wiki for agriculture terms, definitions, acronyms, key words, and synonyms, to be used by all segments of agriculture in support of accurate communication and improved understanding between segments of agriculture and agribusiness. 38

agglossary.org: Structure  Ontological Structure: o The Glossary is structured as an ontological glossary to establish the authority value and accuracy of a term and its definition; giving the Glossary unparalleled credibility. o Ontological structure uses Primary and Contextual terms and definitions. 39

agglossary.org – Contribution of Terms  The Glossary Working Group has reached out to other organizations to contribute terms and definitions.  ASABE  USDA  AEF  ISO  AEM  The Glossary Working Group has placed a priority on placing Legal and Standards terms and definitions into the Glossary. 40

agglossary.org – Contribution of Terms  The Glossary Working Group will be working with AgGateway Councils and Projects to place terms and definitions used within Projects into the Glossary for reference.  The purpose of the Glossary Working Group is to:  Follow an established process to gather terms and definitions from all of agriculture,  Identify and classify the authority value of an agriculture term and definition,  Publish terms and definitions that are credible and accurate,  Maintain public access to the Glossary so everyone can have access to terms and definitions used in agriculture. 41

42 Collaboration

44 SPADE3

SPADE 3 Charter Receive commitments and funding prior to Mid-Year meeting. Potentially kick off at Mid-Year meeting…Monday, June 8 th ? Scope: Focus on documentation and resources needed to implement SPADE and SPADE2 work Crop Nutrition use cases and data buckets Scouting use cases and data buckets Continued Reference Data directory work Management of WAVE (Wireless Asset and Vehicle Data Exchange) Coordination with PAIL (Precision Ag Irrigation Leadership) Coordination with CART (Commodity Automation Rail and Truck) Coordination with ADAPT (Ag Data Application Programing Toolkit) 45

Coordination with AgGateway Europe We understand that AgGateway Europe has agreed to launch a SPADE-like project. We were mindful of the global applicability of our work We’re eager to coordinate with AgGateway Europe to Learn about European precision ag requirements When requested, expain our work to AgGateway Europe 46

Questions?