Precision Ag Council June 18, 2013 1:00 PM-3:00 PM
2 PAC PRIORITIES FOR 2013 AS PRESENTED AT 2012 ANNUAL MEETING
3 Priorities for 2013 • Strengthen our working • Provide a good initial groups. Recruit leaders home in Ag Gateway for irrigation & sensor • Glossary companies • Prepare it for sharing • Explore standards project • Look for long-term home • Re-launch Telematics • Manage SPADE Working Group deliverables for success • Launch SPADE 2 if • Includes bringing messages needed into Ag Gateway S&G process • Cross-Council Operation • Track results • Data Privacy and Security • Pursue access to CLUs • 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)
6 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 ( S tandardized P recision A g D ata E xchange) 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
7 FOWG Goals/Objectives • 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.
8 SPADE PROJECT Mid Year Meeting, 2013 Joe W. Tevis, PhD (Topcon Precision Ag) SPADE Project Chair jtevis@topcon.com
9 SPADE S tandardized P recision A g D ata E xchange
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
12 Major Accomplishments/Status Phase Status/Complettion % Requirements Design Implementation Deliverable Reference Data Access Seeds 90% 80% 70% Machinery 60% 50% 40% CVT 40% 0% 0% USDA Interface 20% 0% 0% ISO Enhancements FMIS<-> FMIS Plan Development 70% 50% 10% Historical Data 60% 40% 0% FMIS<-> MICS 95% 80% 0%
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 Translators from ISO+AG Data Model to Proprietary data FMIS Data Model Transfer Documents models (ISO+AG Complint TBD) (ISO+AG Compliant) Worker (WKR) @ WorkerId ! WorkerDesignator ? WorkerFirstName Translator FMIS CodedCommentListValue (CCL) FMIS ? WorkerAddress ? WorkerPhone @ CodedCommentListValueId ? WorkerLicenseNumber ! CodedCommentListValueDesignator Company I Company I Open Source Translator WorkerAllocation (WAN) CodedComment (CCT) @ CodedCommentId ! WorkerIdRef ? <AllocationStamp> ! CodedCommentDesignator ? <CodedCommentListValue > ! CodedCommentScope ? CodedCommentGroupIdRef AllocationStamp (ASP) ! {Start | Stop} ? Duration Plans CodedCommentGroup (CCG) ! Type ? <Position> @ CodedCommentGroupId ! CodedCommentGroupDesignator DeviceAllocation (DAN) Translator FMIS FMIS Position (PTN) ! WorkingSetMasterNAMEValue ? WorkingSetMasterNAMEMask ! PositionNorth ? DeviceIdRef Company II ! PositionEast ? <AllocationStamp> Company II ? PositionUp ! PositionStatus ? PDOP Connection (CNN) ? HDOP ? NumberOfSatellites ! DeviceIdRef_0 ? GpsUtcTime ! DeviceElementIdRef _0 ? GpsUtcDate ! DeviceIdRef_1 ! DeviceElementIdRef _1 Device (DVC) @ DeviceId ? DeviceDesignator DataLogValue (DLV) ? DeviceSoftwareVersion Translator FMIS connector Work Orders FMIS ! DataLogDDI ! WorkingSetMasterNAME ! DataLogValue ? DeviceSerialNumber ! DeviceElementIdRef ? DeviceStructureLabel Company III ? DataLogPGN ? DeviceLocalizationLabel Company III ? DataLogPGNStartBit ! <DeviceElement> ? DataLogPGNStopBit ? <DeviceProcessData> ? <DeviceProperty > ? <DeviceValuePresentation > DeviceElement (DET) DeviceProcessData (DPD) @ DeviceElementId @DeviceProcessDataObjectId ! DeviceElementObjectId ! ProcessDataDDI ! DeviceElementType ! ProcessDataProperty ? DeviceElementDesignator ! ProcessDataTriggerMethods FMIS ! DeviceElementNumber ? ProcessDataDesignator ! ParentObjectId ? DeviceValuePresentationObjectId Translator FMIS ? <DeviceObjectReference > Company IV Company IV Work Records Open Source Repository • 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.
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
19 SPADE2 Contacts 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)
20 THANK YOU Your source for eBusiness innovation.
PAIL: Precision Ag Irrigation Leadership Partnership for Faster, Broader Data Standards Development Dan Berne (Next Chapter Marketing)
22 Precision Ag Irrigation Leadership (PAIL) CHARTER Jointly sponsored • NW Energy Efficiency Alliance Provide a common set of • AgGateway data standards and formats to convert weather, soil Driven by business needs moisture and other • Growers and Manufacturers 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 EXTERNAL DATA SOURCES Soil maps Weather LOCALIZED networks HARDWARE Weather stations Moisture sensors ONLINE Pumping plants ADVISORY Smart meters SYSTEMS Flow valves Crop type ET IRRIGATION Schedules SCHEDULING Weather TOOLS SIS VRI SIS
Companies Onboard John Deere Water Ag Connections Lindsay Corporation Agrian Map Shots AgSense Monsanto Campbell Scientific OnFarm Systems CropIMS Ranch Systems Crop Metrics Simplot Decagon Wysocki Irrinet ZedX, Inc. Irrometer
25 Progress to Date • 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
26 Strategies & Challenges • 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
27 Next Steps • 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)
28 + Partnership for Faster, Broader Data Standards Development PAIL: PRECISION AG IRRIGATION LEADERSHIP
Telematics Working Group 2013 Mid Year Meeting Update Project WAVE Ben Studer (AGCO)
30
Recommend
More recommend
