Reference Data API Stakeholder Communications/Talking Points

Stakeholders:

• Equipment Manufacturers (high importance)
• Seed and CP Product Manufacturers (high importance)
• Consumers of API - i.e. FMIS (lower importance)
• Reference Data Providers (CDMS, SST, Agrian, etc.)

Equipment Manufacturers:

• Goal: get them to host or have a 3rd party host Rest API for someone to consume / make reference data available
• How they engage:
  • Ask host information, make available through API, directory recognizes API to find content by defined categories
• Use flyer from mid-year meeting for WIFM - targets both types of manufacturers - more technically oriented - need something that packages it up and makes compelling sales case for engagement
  • Flyer can also be adapted for consumers as well 
• intention of communications team is to develop brief elevator speeches to use verbally or via email - sales slant
• Ask to put information out about equipment that can be picked up by Reference data API (offsets, connection times, power information, etc.).  New model information available in API - expose directory service to find this equipment
  • no work on FMIS side to find this information 
• Feedback from Manufacturers is needed regarding - subject matter expert from manufacturer to review and provide feedback on the current model to identify gaps and validate information currently incorporated

Input Manufacturers:

• Same as equipment manuf above, but specify API in reference to pertinent products
• Syngenta example - introduce new chemistry - they provide information such as product density, post harvest interval, re-entry interval time, worker protection standards, condensed label - ingredients, concentration, make traceability easier to do
• Seed - relative maturity, embedded traits, refuge in a bag, GMO products, requirements for planting their products,
• Action - cross reference talking points with model in place - identify any gaps in current model and align with these examples (either remove from examples or add to model) - both types of manufacturers

Consumer:

• mention pain points of getting manufacturers to get data into your system
• Value of having this data all in one spot to pick up the information without waiting for updates from various companies and loading to your systems. 
• If your partners/  push FMIS providers to contact the most prevalent manufacturers they receive reference data from and create reference data API; get them to engage and spend more time developing products and spend less time communicating information about current products to FMIS providers
• FMIS providers spend less time scouring internet to find information - immediate reference if manufacturer makes part of API
• Agreement/validation of current model - identify any gaps (lower importance than manufacturer input) are we offering the best we can?

Reference Data Providers:

• Easier to consume their reference data from their sites and be willing to pay for it - their data is more marketable due to ease of engagement 
• potentially allow them to add custom extensions to API that they would like to expose
• Agreement/validation of current model - identify any gaps (lower importance than manufacturer input)