allied providers council - amazon s3s3.amazonaws.com/aggateway_public/aggatewayweb...recap of allied...

2016 Annual Conference: Using Collaboration and Connectivity to Cultivate Success

Allied Providers Council

Annual Meeting

November 2016



2

AttendanceFirst Time AttendeesMinutes RecorderAnti-Trust Guidelines

Welcome!



3

Welcome Steve Daigle, Elemica

New Vice Chair!


Recap of Allied Providers Council

Mission: “To provide an open forum of Agricultural technology and service providers that promote eAgriculture and the AgGateway mission”

4


Recap of Allied Providers Council

• 3 Overarching Goals:

1. Advancing eAgriculture. Provide the AgGatewaymembership with a dynamic and holistic group of technology and service providers who will help advance eAgriculture across the value chain.

2. Awareness and Branding. Support AgGateway by building awareness in our unique networks and communities outside of AgGateway.

3. Advisory and Advocacy. Support AgGateway by acting as an advisory and advocate arm for the Ag industry.

5


ADAPT Conversation

• Featuring special guest Andres Ferreyra, Ph.D., AgConnectionsLLC

6


ADAPT: How YOU can enable Field Operations Interoperability!

A message for the Allied Providers Council

November 7, 2016


Topics

•The field ops interoperability problem

•Quick overview of ADAPT

•What’s in this for the Allied Providers?

•Onboarding, ADAPT Resources

•Next steps: getting a process in motion to empower Allied Providers to participate


Field Operations Interoperability• Modern growers need to keep increasingly detailed and timely records

of field operations (planting, irrigation, spraying, fertilization, harvest, etc.)

• Motivations:

• Keeping their business profitable

• Regulatory pressure, and

• Supply-chain interest in traceability and sustainability.

• Growers and their partners use multiple "documents" to exchange field operations information as part of their business processes.

• Lack of common formats and shared meanings are huge problems

• The effort necessary to make the simplest of comparisons or exchanges with partners makes the documentation burden not scalable or sustainable by the grower.

http://bit.ly/2aQVT5d


10

Seeking a metaphor for field operations data...

Execution

Datacapture

Inputs

Regulatoryimplications

Standards

Fieldoperations

Safety

Equipment

Telematics

Planning

Financials

Insurance

Agronomy

Harvestedcommodity

Sustainability



4 Things we want to agree on• Can we agree on what things mean? (Identity and Semantics)

• For humans: Ag Glossary• For computers: Reference Data

• Can we agree on how things happen (Processes)?• Stories, Process Models, Use Cases

• Can we agree on what we need to know (Data Requirements)?• Core Documents• Irrigation (PAIL)• Telematics (WAVE)• Grain handling (CART)• ContextItems

• Can we agree on how things can talk to each other(Interoperability)?• ADAPT object model, ADAPT plug-in framework• SPADE Reference Data APIs• Upcoming SPADE /PAIL work on data exchange APIs

12



Intro to ADAPT• ADAPT (Ag Data Application Programming Toolkit):

• Intended to enable communications:• Between farm machines governed by onboard Machine / Implement Control

Systems (MICS) and Farm Management Information Systems (FMIS) and

• Between different FMIS.

• Strong emphasis on enabling international use.

• ADAPT contains:• A common object model (or “Application Data Model/ADM”).

• Format conversion plug-ins (both open source and proprietary).

• A conversion framework (a software development kit) that enables all the parts to work together.

• Q: Why is ADAPT so different from the standards used in AgGateway’s supply chain work?

A: The Ag eStandards grew out of OAG Chem eStandards; ADAPT grew out of ISO11783 and other ISO/IEC/OGC standards. The amount of data being exchanged is also very different (HUGE in field operations).


How ADAPT works

• The blue arrows show an FMIS-to-FMIS communication example.

• The red arrows show data import from a farm machine.


5 Use Cases for AP ContributionsWe envision five different ways in which Allied Providers can help their customers better manage field operations processes using ADAPT.


1: Help your clients adopt ADAPT!

In order to use ADAPT, an FMIS or other system must use a set of core DLLs to read/write to/from the data model and to manage plug-ins.


2: Help your clients transfer data

• In the same way that messaging platforms enable the use of the Ag eStandards, field operations data exchange is important (AgXML precedent.)

• Setting up APIs for data transfer has not yet been in scope of SPADE/ADAPT.


3: Help your clients write plug-ins

• Anyone who owns a proprietary format for ag data exchange may be a potential customer for plug-in development.

• OEMS for machines, implements, sensor systems, telematics, data entry...


4: Help stand up Reference Data APIs

Some manufacturers and reference data providers may need help to source data through Reference Data APIs.


5: Help maintain Reference Data

• For a reference data provider, standing up the API is only one step.

• Maintaining the underlying label / product data may be complex.


Your Role

• Allied Providers help other AgGateway members implement standards.

• Manufacturers of machinery, inputs, etc. (more generally, anyone with a proprietary format) may want plug-ins to source data to be consumed by a third party, but may not have the ability to write the plug-ins themselves.

• The Allied Providers Council seems to be a natural source of providers to do this.


Summary of the 5 Use Cases• Helping your clients adopt (i.e., integrate with) ADAPT

• Opportunity: FMIS, DSS, and other service-providing companies want to move field operations data using ADAPT; they need guidance on how to integrate with ADAPT, manage plug-ins, etc.

• Help your clients transfer data• Opportunity: Leverage prior experience with supply-chain messaging to provide solutions for field

operations (albeit with far larger data volumes.)

• Help your clients write plug-ins• Opportunity: ADAPT team has created a couple of community supported plugins that can be used

as templates for an allied provider to write a plug in to convert a format.

• Get closer to Field Operations!

• Help stand up Reference Data APIs• Opportunity: some manufacturers want to field their reference data - opportunity for allied

provider to embed themselves firmly in the chain

• Provides tie-in between AIDC work and what’s happening in the field; promote adoption of AIDC

• Help source / maintain Reference Data• Opportunity: a service where provider routinely does this for a company; integration in supply

chain already exists: leverage relationship to help deliver reference data to chosen API provider.

• Provides value to your customers


Why You Should Care

• Provide value to your customers

• Position yourself closer to field operations

• Opportunity for tie-in between supply-chain and field operations work (e.g., AIDC, AGIIS)

• Opportunity to leverage prior experience with messaging platforms.


How you can get involved

• Start here: • Find the high-level flyer here: http://bit.ly/1VQQsWR

• Find a big-picture paper here: http://bit.ly/2aQVT5d

• The site at www.adaptframework.org contains links to the ADAPT source code

• It also contains links to data model documentation

• The ADAPT Team provides onboarding / mentoring

• Remember: This is an open-source effort!• The code and materials are distributed according to the Eclipse Public

License

• You can contribute to the code!

• Talk about this with your customers!

http://bit.ly/1VQQsWR


http://www.adaptframework.org/


Thank you!

For more information, contact:

• [email protected]

• [email protected] (ADAPT Chair)

Don’t forget to visit:

• www.adaptframework.org

mailto:[email protected]

mailto:[email protected]

http://www.adaptframework.org/


Old Business

• New Vice Chair! Welcome Steve!

• Committee/Council Representation

• Provider Branding – Enabled By Logo

• Capability Matrix

• Emerging Technology and Thought Leadership

26


Old Business - Matrix

27


New Business

• 2017 Meeting Schedule – Quarterly

• Governance Document

• Appointment of Operational Management Board Director

• 2017 Goals and Objectives

28


Motion to Approve

• Motion to approve the Governance Document as presented to the Allied Providers.

29


Motion to Approve – Operational Board

• Motion to approve THIS COULD BE YOU as the Operational Management Board Director for the Allied Providers Council.

30


Eligibility• AgGateway Member representative of a Voting Member organization in good standing

• A Voting Member of the Council for which they are the representative on the OMB

• A commitment to and understanding of the agricultural and related industries, based on experience

• A commitment to and understanding of AgGateway, with past experience on the council they represent

• Operational level experience within the industry

• Savvy diplomatic skills and a natural affinity for cultivating relationships and persuading, convening, facilitating, and building consensus among diverse individuals

• Personal qualities of integrity, credibility, and a passion for improving the agricultural industry

• Ability to bring an industry perspective rather than just the perspective of their own organization

• Ability to commit the time necessary to fulfill the duties of the role

• Council leadership experience is preferable but not required

•

• Time commitment: Approximately 1-3 hours a month (more if on a task force or working group)

• OMB will meet monthly (1 hour)

• Follow up and reporting to councils (1-2 hours) when they meet

• Attend the Mid-Year Meeting and the Annual Conference in person

•

• Here is a link to a draft OMB role description that helps to describe the role: https://aggateway.atlassian.net/wiki/x/pQEaB

31

https://aggateway.atlassian.net/wiki/x/pQEaB


Motion to Approve

• Motion to approve Randy Kasparbauer as the Operational Management Board Director for the Allied Providers Council.

32


2017 Goals

• Visibility – matrix

• Forum – for new tech, new projects, takeaways, guest speakers

33


2017 Goals and Objectives

34

Goal 1 – Advancing eAgricultureProvide the AgGateway membership with a dynamic and holistic group of technology and service providers who will help advance eAgricultureacross the value chain.

Objective: Determine the long-term maintenance plan for the Matrix, whether it should be public, private, or both, and outline a plan for promotion. [Nov 2017]

Objective: Have at least one Liaison to each Council responsible for representing the network of Allied Providers, and communicating the need for technical expertise for council activities and projects– on an annual basis.



35

Goal 2 – Awareness and Branding of AgGatewaySupport AgGateway by building awareness in our unique networks and communities outside of AgGateway.

Objective: Encourage the use of the “Enabled By” logo among the AgGatewaymembership [Applications for use by at least 5 new companies by May 2017]

Objective: Have a rotating schedule (quarterly) of AP Council members to share AgGateway news and events on our AgGateway Linkedin Group [May 2017]

Objective: Host a guest speaker at our quarterly meetings from an AgGatewayCouncil, Project, or Taskforce.



36

Goal 3 – Advisory and Advocacy for eAgricultureSupport AgGateway by acting as an advisory and advocate arm for the Ag industry.

Objective: Create a plan/committee for the AgGateway Annual Meetings to showcase emerging trends and tech [June 2017 Mid Year Meeting]

Objective: Update our “Allied Provider” Thought Leadership website page to showcase the thought leadership content offered by our guest speakers (quarterly).


Committee and Councils

37

ROLE PERSON

Chair Jody Costa

Vice Chair Steve Daigle

Operational Board

ADAPT

Architecture

Conference

Communications

Data Privacy & Security

Directory Oversight

Education

Membership

Standards and Guidelines

Ag Retail

Crop Nutrition

Crop Protection

Grain and Feed

Precision Ag

Seed

Speciality Chemical

AIDC Task Force


THANK YOU!CONNECT WITH US ON LINKEDIN

38