Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Duncan: forward looking to the next epic. With the revamped scope sensors is going to be a quick module from the dev side. Are we in touch with a manufacturer already?

    • Loïc: no, we don’t even have the name of the manufacturer. We have gotten in touch with Farming Smarter but in order to avoid a repeat of the sensor situation, we need to talk to the tech team of a manufacturer ASAP

    • Anto: since it’s relating to the grant, Farming Smarter should know who these manufacturers are

    • There are 4 farms per year for 3 years in this grant. There COULD be as many as 4 manufacturers per year involved! (Worst case scenario)

    • Farming Smarter has given us general guidelines about how the pivots behave and how the irrigation subscription is communicated to the pivots (manually via USB transfer of the file; pivots should be considered as low-tech) – these points will all have to be checked though

    • Tentatively speaking we have some early assumptions about what e.g. the add flow looks like but these have to be checked as well – whole team consensus that we don’t want to repeat what happened with sensors

      • The constraints we encounted were not coming from necessarily the user experience, nor the technology, but what the partners were assuming; it is a partner communication issue

    • Loïc: We need less second hand discussion and getting all parties in the same room (Joyce: including Ensemble would be my preference when it comes to talking to the manufacturers, if we even have those conversations -- I don’t think the pivot manufacturers will be meeting with us if they aren’t grant partners)

    • Anto: the .vri file being downloaded and given to the pivot is enough for the sake of the grant (this needs to be verified though); there might not be any communication here at all

      • Duncan: We need to confirm if we are integrating with a pivot API at all – otherwise it’s manual entry into LiteFarm and a totally different situation

    • Action items moving into pivots:

      • Loic Sans to get the actual manufacturers from Farming Smarter

      • Confirm with Divya Chayanam the scope of the grant and whether talking to the pivot is part of the requirements or not. (Farming Smarter should know this as well) – need to confirm the end of the flow Anto Sgarlatta (in shared channel) and whether the .vri file is the end of our responsibility

      • ALSO need confirmation of the beginning of the flow (which requires the names of manufacturers) to know if they have read APIs (i.e. if it is a Ensemble situation or not when it comes to importing data about pivots in the app)

    • Dev and Design discussed array and sensor icons on the map – points have been added to Figma

TO DO

(Just noticed this table!)

Task

Owner

Due date

Notes

Get the actual manufacturers of the pivots used by our grant partner farms from Farming Smarter

Loic Sans

ASAP

Via email

Confirm with Divya Chayanam the scope of the grant regarding communication with the pivot (initial flow and end of the flow)

Anto Sgarlatta

ASAP

In Slack channel

Confirm Wednesday release of consent with Divya Chayanam

@dev

Jan 24th

In Slack after ag conference