Precision Ag Council

June 18, 2013

1:00 PM-3:00 PM

2

PAC PRIORITIES FOR 2013 AS PRESENTED AT 2012 ANNUAL MEETING

Priorities for 2013

3

• Strengthen our working groups. Recruit leaders

• Glossary • Prepare it for sharing

• Look for long-term home

• Manage SPADE deliverables for success • Includes bringing messages

into Ag Gateway S&G process

• Track results

• Pursue access to CLUs

• Provide a good initial home in Ag Gateway for irrigation & sensor companies • Explore standards project

• Re-launch Telematics Working Group

• Launch SPADE 2 if needed

• Cross-Council Operation • Data Privacy and Security

• Glossary

4

Most Important Goal: Ensure YOU are satisfied with your AgGateway experience!

PAC Field Operations Working Group

Jill Stanford (John Deere)

Jaap Van Bergeijk (AGCO)

Field Ops Working Group Update

• A Year in Review (MYM 2012-2013) • Small group drafted a charter “Precision Ag Standards Using Seeding Use Case”

• Spring Working Group Mtg (April 5) Data Exchange Charter vote/approval

• Several additional companies joined from original 15

• Official kick off in Ankeny, IA - August 2012

• Project formally named:

SPADE (Standardized Precision Ag Data Exchange)

http://wiki.aggateway.org/Spade%20Project.MainPage.ashx

• Industry Collaboration • April 26, 2013 – Presented SPADE results at ISO AEF PG9 FMIS Working Group

• ISO WG9 & WG5 have requested AgGateway feedback on proposed standards

6

FOWG Goals/Objectives

7

• Working Group Goals and Objectives • Short term: Identify existing use case/needs and focus on a specific use case

(Seeding Example Selected June 2011 – Chartered SPADE project). Identify existing standards and gaps/needs.

• 2013 - Focus on Harvest use case SPADE 2

• Medium term: Reach consensus on standard needs and adopt existing standard/propose additional changes to this standard or develop an AgGateway standard in order to meet the need.

• Long term: As needs of the industry evolve, continue to work as a group in order to build upon the standard.

• Examples – Upcoming WG5 Standards for Operation/Tasks/Jobs and WG9 ISO DL. Review and provide feedback to AEF.

Mid Year Meeting, 2013

Joe W. Tevis, PhD (Topcon Precision Ag)

SPADE Project Chair jtevis@topcon.com

8

SPADE PROJECT

9

SPADE Standardized Precision Ag Data Exchange

10

SPADE1 Scope

SPADE1 Project Timeline

• SPADE Charter Approved July 2012

• Project Kick-off – Des Moines 10 August, 2012

• Face-to-Face – AGCO, Atlanta 2 October, 2012

• Winter Meeting, Albuquerque 6 November, 2012

• SPADE1 Project End 20 June, 2013

Major Accomplishments/Status

12

Deliverable Requirements Design Implementation

Reference Data Access

Seeds 90% 80% 70%

Machinery 60% 50% 40%

CVT 40% 0% 0%

USDA Interface 20% 0% 0%

ISO Enhancements

FMIS<-> FMISPlan Development 70% 50% 10%

Historical Data 60% 40% 0%

FMIS<-> MICS 95% 80% 0%

Phase Status/Complettion %

13

SPADE2

14

SPADE2 Scope

SPADE2 Project Timeline

• Board Approves Project 30 April, 2013

• Commitment Letter Sent 30 May, 2013

• Commitment Closure 30 June ,2013

• Project Kick-off 20 June, 2013

• Panel Discussion - InfoAg 17 July, 2013

• Winter Meeting 14 Nov, 2013

• Last Day to Join 30 Nov, 2013

• SPADE2 Closed Feb, 2014

SPADE2 16

• Carry all aspects of SPADE1 to implementation

• Expand focus to: • Production reporting not covered in SPADE (harvest, crop protection,

fertilization, tillage)

• Creating infrastructure to deliver SPADE reference data

• Continue USDA Cooperation • Revisit SPADE documents when they release their reporting schemas

• Seek resolution to CLU – Management field conflict

• “Open Source” data translation proof of concept

AgGateway Proposal

• All MICS manufacturers export and import ISO+AG format,

• Open Source component translates to-from ISO+AG format to ISO+AG FMIS data model (TBD)

• Each FMIS manufacturer translates to-from ISO+AG FMIS data model to their proprietary data model.

Translators from ISO+AG Data Model to Proprietary data

models

Transfer Documents(ISO+AG Compliant)

Work Orders

Plans

Work Records

Open Source Repository

FMIS Data Model(ISO+AG Complint TBD)

Open S

ourc

e T

ransl

ato

r

! WorkerIdRef? <AllocationStamp>

WorkerAllocation (WAN)

@ WorkerId! WorkerDesignator

? WorkerFirstName

? WorkerAddress

? WorkerPhone

? WorkerLicenseNumber

Worker (WKR)

@ CodedCommentGroupId

! CodedCommentGroupDesignator

CodedCommentGroup (CCG)

! WorkingSetMasterNAMEValue

? WorkingSetMasterNAMEMask? DeviceIdRef

? <AllocationStamp>

DeviceAllocation (DAN)

@ DeviceId

? DeviceDesignator

? DeviceSoftwareVersion! WorkingSetMasterNAME

? DeviceSerialNumber

? DeviceStructureLabel

? DeviceLocalizationLabel

! <DeviceElement>? <DeviceProcessData>

? <DeviceProperty>

? <DeviceValuePresentation>

Device (DVC)

@ DeviceElementId

! DeviceElementObjectId

! DeviceElementType? DeviceElementDesignator

! DeviceElementNumber

! ParentObjectId

? <DeviceObjectReference>

DeviceElement (DET)

! DataLogDDI

! DataLogValue! DeviceElementIdRef

? DataLogPGN

? DataLogPGNStartBit

? DataLogPGNStopBit

DataLogValue (DLV)

! DeviceIdRef_0

! DeviceElementIdRef_0

! DeviceIdRef_1

! DeviceElementIdRef_1

Connection (CNN)

@ CodedCommentListValueId

! CodedCommentListValueDesignator

CodedCommentListValue (CCL)

connector

@DeviceProcessDataObjectId

! ProcessDataDDI

! ProcessDataProperty

! ProcessDataTriggerMethods? ProcessDataDesignator

? DeviceValuePresentationObjectId

DeviceProcessData (DPD)

! PositionNorth

! PositionEast

? PositionUp! PositionStatus

? PDOP

? HDOP

? NumberOfSatellites

? GpsUtcTime? GpsUtcDate

Position (PTN)

@ CodedCommentId

! CodedCommentDesignator

? <CodedCommentListValue>

! CodedCommentScope ? CodedCommentGroupIdRef

CodedComment (CCT)

! {Start | Stop}

? Duration

! Type? <Position>

AllocationStamp (ASP)

Translator FMIS Company I

Translator FMIS Company II

Translator FMIS Company III

Translator FMIS Company IV

FMIS Company I

FMIS Company II

FMIS Company III

FMIS Company IV

Proposal Value Proposition

• Easier for FMIS companies to integrate by handling complex operation,

• Creation and translation of binaries,

• Creation and interpretation of implement device configurations

• Grid types

• Promote adoption of the standard

• Version management

• Coordinate system conversion???

• Promote standard construction of complex device configurations

• TC-FMIS “Conformance” test

SPADE2 Contacts

19

For More Information:

Joe Tevis (jtevis@topcon.com) Andres Ferreyra (andres.ferreyra@agconnections.com)

Also see:

“SPADE Project Update”

To Join SPADE2:

Jim Wilson (jim.wilson@aggateway.org)

Your source for eBusiness innovation.

20

THANK YOU

PAIL: Precision Ag Irrigation Leadership

Partnership for Faster, Broader Data Standards Development

Dan Berne (Next Chapter Marketing)

Precision Ag Irrigation Leadership (PAIL) 22

Jointly sponsored • NW Energy Efficiency Alliance

• AgGateway

Driven by business needs • Growers and Manufacturers

CHARTER Provide a common set of data standards and formats to convert weather, soil moisture and other relevant data from OEM hardware and software programs to be used by irrigation data analysis and prescription programs.

Today’s Standalone Tools Don’t Integrate

LOCALIZED HARDWARE

Weather stations Moisture sensors Pumping plants Smart meters Flow valves

EXTERNAL DATA SOURCES Soil maps Weather

networks

ONLINE ADVISORY SYSTEMS

Crop type ET Schedules Weather SIS

IRRIGATION SCHEDULING

TOOLS VRI SIS

Companies Onboard

Ag Connections Agrian AgSense Campbell Scientific CropIMS Crop Metrics Decagon Irrinet Irrometer

John Deere Water Lindsay Corporation Map Shots Monsanto OnFarm Systems Ranch Systems Simplot Wysocki ZedX, Inc.

Progress to Date 25

• Charter completed

• Business use cases completed

• Technical use cases underway (PAIL wiki)

• Inbound Data

• Set-up and Configuration

• Field Operations Data

• Offsite Data

• Building engagement and trust

Strategies & Challenges 26

• Focus on center pivot irrigation for phase 1

• Define data needs around business and technical use cases

• Include growers on the team

• Leverage existing standards wherever possible

• Use virtual testing before approval

• Reaching agreement while protecting IP

• Multiple sources for offsite data, such as weather forecasting and crop coefficients

• Limited time and resources

Next Steps 27

• Complete technical use cases (Mid-July)

• Define datasets and terms (Sept.)

• Document business rules (Sept.)

• Draft data standards (Nov)

• Virtual test

• Approve and document (March 2014)

PAIL: PRECISION AG IRRIGATION LEADERSHIP

Partnership for Faster, Broader Data Standards Development

28

+

Telematics Working Group

2013 Mid Year Meeting Update

Project WAVE

Ben Studer (AGCO)

30

Combine 3 Needs to Unload –

Location Field 1

Tractor 2 Can Unload Combine 3 – Need Fuel – Location Field 4

Fuel to Tractor 2 Location Field 4

Bin 2 Full – Fill Bin 3 –

16% Moisture on

Bin 1

Grain Truck 5 – Fill Bin 3

Running in Field 6 - Need to reload

Scheduled to Run at 1PM

Current temperature

100

Opportunities for collaboration?

32

What Comes Next?

33

Date Milestone

June 2013 Charter sent out for discussion

June 2013 Project charter discussed in detail. Goals, objectives, scope and deliverables agreed upon. Project budget discussed. Funding alternatives proposed. Project charter submitted to Precision Ag Council for approval.

July 2013 Project charter approved.

August 2013 Project Team Launch. Working groups launch. Sub-Teams working; detailed schedules

September 2013 F2f Meeting - TBA

November 2013 AgGateway Annual Meeting. Project will have a demonstration / presentation session associated with the Precision Ag Council program.

March 2014 F2f Meeting - TBA

June 2014 AgGateway Mid-Year Meeting Phase 1 complete. Deliverables communicated.

June 2014 Phase 2 Charter sent out for discussion

34

Thank You

Data Access Points

Cloud (Gateway to machines) Cloud (Gateway

to machines) Cloud (Gateway to machines)

CASE Vehicle

CNH Display Trimble

FMIS or Portal

Proxy

Value Added Services

Machine Directory

JD Vehicle

JD Display

AGCO Vehicle

AGCO Display AM50

JD Vehicle

Raven MTG

MTG 2

1

3

4

Data Security, Privacy & Protection

Deb Casurella (Independent Data Management)

GOAL

The Data Security, Privacy & Protection working group will define standards and guidelines for securing and protecting information. These guidelines will strive to prevent an error in an unsupervised marketplace which could jeopardize the benefits gained by using data collected during field operations.

2013 Mid Year Meeting 37

Accomplishments & Next Steps

Accomplishments

• Defined working group objective

• Updated glossary definitions

• Drafted stakeholders

• Drafted initial security, privacy & protection principles

Next Steps

1. Discussion of initial content on Wednesday from 7:30 – 9:30 in Canada & Mexico Rooms

2. Develop white paper for PA Council review

38

Insurance, Regulation, and Government Relations Working Group

Mid Year Meeting June 18, 2013, 7:30 – 9:30 a.m.

Johnston, IA

Jeff Keiser (John Deere)

2013 IRG Working Group Goals

40

• Collaborate with USDA (e.g. FSA, RMA, NRCS) to create a field identification approach for which sufficient details can be shared with the farmer’s service providers as a standard spatial reference to crop production areas, but does not expose a producer’s Personally Identifiable Information (PII) or other Private Information related to their participation with USDA programs

• Spearhead a cross-Council initiative to capture Data Privacy & Protection concerns from across AgGateway and the ag industry and then create project proposal to design AgGateway’s position and establish its leadership role

IRG Work Summary: To Date, 2013

• IRG Meetings • 3/14/2013

• 4/30/2013

• Data Privacy & Ownership WG

• “8 Week” USDA Conference Calls with SPADE

• CLU Discussions and Workshop

41

Common Land Unit Concepts

42

Concept Name Description

Alternative Identifier Create Alternative ID for CLU (Farm/Tract/Field)

or CLUID (36 char. Unique identifier) that can be

managed by a USDA “partner” (e.g. AgGateway)

who is able to provide correlation services back to

CLU’s with associated attributes containing PII

USDA GUID The new GUID being utilized by USDA for MIDAS

Spatial intersection Operational boundaries vs. reporting

boundaries/area

Precision Ag Council Glossary

Dennis Daggett (ProAg)

ddaggett@proag.com

AgGateway Glossary - Purpose The creation and maintenance of a “comprehensive

agriculture glossary” will be a coordination point for the multiple agriculture glossaries that exist by business segment today. This “comprehensive agriculture glossary” will… Provide a solution for communication challenges that occur when

existing identical terms or phrases (term/terms) have different meanings and use.

Establish awareness of a new term; and its context and definition.

Establish a standard term and definition resource for AgGateway Councils, Committees, and Projects to support e-Business communications and transactions.

Establish a standard term and definition resource for ag education and businesses to promote effective and efficient communication and training.

44

AgGateway Glossary – Content Following is an outline of the current content of the

“comprehensive agriculture glossary” spreadsheet. Term

Control Category (CC No.) - defined in the glossary spreadsheet

Category (C No.) – defined in the glossary spreadsheet

Sub-Category (SC No.) - defined in the glossary spreadsheet

Space Name – primary user of term

Definition of Term

Key Words

Synonyms

Related Terms

Lexicon – International

Source / Point of Origin – origin of definition and/or submitter/source of definition

Control Council: AgGateway Council assigned to review / control definition

45

AgGateway Glossary – Format

AgGateway will use Wiki or other easily editable format.

The glossary must contain Search/Advanced Search capability.

The glossary must have the capability of linking.

It is recommended that the glossary have an audio recording of the pronunciation of the term attached to each term.

46

AgGateway Glossary – Commitment

AgGateway will: Commit personnel and resources to the creation and maintenance of the

glossary.

Pursue collaboration with the USDA, ag groups and businesses, academia, and standards organizations.

Post the approved terms glossary on the AgGateway wiki.

Use the glossary in internal communications and Projects.

Use the glossary to promote the execution of its mission to promote, enable, and expand eBusiness in agriculture.

47

THANK YOU FOR YOUR ATTENTION!

QUESTIONS - COMMENTS?

Presented by:

Dennis Daggett

ProAg

ddaggett@proag.com

June 17, 2013

48

SPADE COMMUNICATIONS WORKING GROUP

Jonelle Lofton (Monsanto)

Susan Ruland (AgGateway)

49

DISCUSSION OF PAC PRIORITIES

Andres Ferreyra (Ag Connections)

PAC Chair

50

Priorities for 2013

51

• Strengthen our working groups. Recruit leaders

• Glossary • Prepare it for sharing

• Look for long-term home

• Manage SPADE deliverables for success • Includes bringing messages

into Ag Gateway S&G process

• Track results

• Pursue access to CLUs

• Provide a good initial home in Ag Gateway for irrigation & sensor companies • Explore standards project

• Re-launch Telematics Working Group

• Launch SPADE 2 if needed

• Cross-Council Operation • Data Privacy and Security

• Glossary

Priorities for 2013: Feedback

52

• Strengthen our working groups. Recruit leaders

• We should start talking about rotating the leadership.

• Glossary

• Challenge to the group to actively look for terms that need to be defined.

• Challenge to be available to help.

• Manage SPADE deliverables for success

• Where does a lifecycle phase end?

Priorities for 2013: Feedback

53

• Pursue access to CLUs • Ongoing work in IRG.

Renewing the white paper

• Provide a good initial home in Ag Gateway for irrigation & sensor companies • Explore standards project

• Hoped we’d be further along, but getting a lot of momentum recently.

• Ag Gateway is providing opportunities for networking.

• Re-launch Telematics Working Group • Cross-pollination

opportunity

• Launch SPADE 2 if needed • In Progress!

• Cross-Council Operation • Will look for increased

presence from Ag Retail.

54

Most Important Goal: Ensure YOU are satisfied with your AgGateway experience!

• Refocus on looking at agriculture as a whole system. • Will keep grower perspective in mind.