ADAPT Allied Providers Messaging Storyboard (For May 10, 20016 APC Meeting)

• Slide 1: Title

  • ADAPT: Why it's Important and Why You Should Get Involved

  • ADAPT: A great opportunity for you to enable field operations interoperability
  • ADAPT: How YOU can Enable Field Operations Interoperability!

• Slide 2:  Brief Intro to ADAPT

  • Allied Providers' understanding of ADAPT may be spotty - need to:

    • Give a very quick overview of what it is and what's in it for them

    • Inform of ADAPT Workshop at the MYM

    • Help onboard interested companies

    • Get a process going to empower Allied Providers to participate

• Slide 3: Why you should care (General)

• Allied Providers help others in AgGateway to setup standards, etc.  Manufacturers of machinery, inputs, etc. would want to write plug ins to source reference data or format data to be consumed by a third party, but may not have the ability to write the plugins themselves. It was suggested the Allied Providers can help recruit providers to do this.
• Why they should care - summary slide with what's in it for them looking across benefits of all use cases (summarize at beginning then again at the end)

• Slide 4: 5 Use cases

  • 4 use cases (description of the problem, what the solution looks like, what is the opportunity for them):

    • plug in creation

      • 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

        • Why you care: Make money, get closer to field operations

    • reference data API implementation

      • Opportunity: manufacturers want to field their reference data - opportunity for allied provider to embed themselves firmly in the chain

        • Why you care: Provides tie-in between AIDC work and what is happening in the field; promote adoption from AIDC

    • sourcing of reference data API-bound data

      • Opportunity: service where provider is consistently doing this for a company; integration in supply chain already exists, leverage the relationship to help deliver reference data to chosen API provider.

        • Why you care: provides value to their customers; provides them an opportunity to get closer to field operations

    • End user integration with ADAPT

      • Opportunity: Service providing companies want to start moving field operations data around using ADAPT; need guidance on how to integrate with ADAPT, manage the plugin, etc.

    • Data transfer / messaging platform

• Slide 5: Use case: Plug-in creation

• Slide 6: Reference Data API Implementation

• Slide 7: Sourcing of Reference Data API-bound Data

• Slide 8: End-user integration with ADAPT

• Slide 9: Data Transfer / Messaging Platform

• Slide 10: Why You Should Care (Specifics)

  • 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)
  •  Income Stream

• Slide 11: How you can get involved/next steps - show starting point for ADAPT, SPADE, PAIL and provide onboarding opportunities

  • Inform of ADAPT Workshop at the MYM (June 16, Thursday of Mid-Year Meeting; register separately!) 
  • Inform of onboarding / mentoring process
  • Include links to reference materials.
  • Include link to website
  • Remind them about open-source
  • Emphasize Eclipse public license
  • Encourage working with the OEMs in plug-ins.

asddasdsdasd

A version with different thicknesses, that can be printed in B&W:

Here's an example from a recent talk re how we could explain how the FMIS, the data model, the plug-ins, and the cloud fit together. We could add the RDAPI and have all 4 use cases in one PIC. That PIC (without the reference to Allied Providers) might also satisfy requirements for the ADAPT flyer.

asdsasd

This is a version that addresses the nested use of the FMIS term in previous versions.

Can we simplify this?