Epics | Description | Versions | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| The ability to add sensors, sensor reading types, and sensor readings to a farm via:
| V1, V2 | ||||||||||||||||
| View sensor (
| V1Retire sensor | ||||||||||||||||
|
| V1 | ||||||||||||||||
| Add “Pivot irrigated field” to location types and build a creation flow for this. | V2 | ||||||||||||||||
View pivot | Needs to encompass:
| V2 | ||||||||||||||||
View farm map layers | Needs to encompass:
| V2 | ||||||||||||||||
Irrigation task supports depth based irrigation types (see
| Support for both volume based and depth based irrigation types. | V1 | ||||||||||||||||
Generate irrigation prescription | IncludesPotential scope:
| V2 | ||||||||||||||||
View irrigation prescription |
Work in progress…
Questions:
Assignments for pivot or other system based irrigation that is automated?
Will need to be able to mark complete if you’re not the assignee.
Area | Epic | Details | Questions / Notes | Version | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
SensorsAdd sensor via farm map |
|
| May or may not be needed, to be explored. | TBD | ||||||||||
Sensors |
| Bulk add sensors via csv upload Where does this live? Could live on the default “+” on the farm map with a modal to differentiate individual vs. bulk. At the end of the flow, what does the user see? Farm map? Filtered only for sensors? | HighV1 [DELIVERED] | |||||||||||
Sensors | View sensor detail
|
| Default readings ranges by sensor type? Pre-defined? e.g. 24 hours, 7 days, 30 days? If longer term, maybe goes to insight Need to know the types of sensors, e.g. temperature, soil moisture, precipitation, wind speed Could each of the types be at different depths? Different lat / long, something else? For sensors that had multiple readings types, how would you display them? Stacked? Choosable with a picklist / tab | Medium | V1 [DELIVERED] | |||||||||
Sensors | Edit sensor |
| Do we need to persist history of the sensor location and attributes or is the current state sufficient? | MediumV1 [DELIVERED] | ||||||||||
Sensors | Retire sensor | Can’t retire if planned task associated with it? | How to view retired sensors? Could have something like a farm map history insight where you drag a timeline and locations appear / disappear. Probably should be closer to an archive than a traditional retire so that the reading history is still available. What’s the best way to do this? | LowV1 [DELIVERED] | ||||||||||
Farm map | List / tile view for all locations with limited filters |
| Low | Pivot / Irrigated location | Add irrigated location (via farm map)TBD | |||||||||
Pivot irrigated field |
|
| Schedule is how frequently the irrigation prescription should be updated, always > 24 hours How do users upload kml? What do we need to check for here:
Is the assignee the system and LiteFarm does everything or is a human in the loop and responsible for marking something complete once the actual irrigation has taken place. | HighV2 | ||||||||||
Pivot / irrigated locationfield | View Pivot irrigated location field (via farm map) |
| V2 | |||||||||||
Pivot / irrigated locationfield | Edit Pivot irrigated locationfield |
| V2 | |||||||||||
Pivot / irrigated locationfield | Retire Pivot irrigated locationfield |
| V2 | |||||||||||
Pivot / irrigated locationfield | Designate existing location as irrigated | May or may not be needed, to be explored. | TBD | |||||||||||
Farm map filters | Filter pivot / Pivot irrigated location field on farm map | V2 | ||||||||||||
Farm map layers | View current moisture readings (via farm map layer + filter) | Likely best to just show point data overlaid on sensor. Try to generate a gradient? Should be overlaid over other locations? Filter vs. layer Need to investigate! | V2 | |||||||||||
Farm map layers |
|
| Will be imported via kml at the farm level or pulled and overlaid from Soilgrids. | TBD | ||||||||||
Irrigation tasks | Add irrigation task flow (user created) |
| LowV1 [DELIVERED] | |||||||||||
Irrigation tasks | View irrigation task (user created) | LowV1 [DELIVERED] | ||||||||||||
Irrigation tasks | Mark irrigation task completed abandoned (user created) | LowV1 [DELIVERED] | ||||||||||||
Irrigation tasks | Edit irrigation task (user created) |
| V1 [DELIVERED] | |||||||||||
Irrigation tasks | Add irrigation task (system created) |
| Important to document changes to the task | V2 | ||||||||||
Irrigation tasks | Automated completion of irrigation task (by system) | Should management be able to mark it complete manually?
| V2 | |||||||||||
Irrigation tasks | Edit system created irrigation task (system created) | Don’t allow? Link to irrigation prescription instead? | TBD | |||||||||||
Irrigation tasks | Automated abandonment of irrigation task (by system) | System marks as abandoned If the irrigation prescription was rejected Should management be able to mark it abandoned manually? If so, remove that irrigation prescription | TBD | |||||||||||
Notification | View irrigation prescription notification | Link to irrigation prescription | V2 | |||||||||||
Whole farm characteristics | Upload farm characteristics |
| May or may not be needed, to be explored. | TBD | ||||||||||
Insights | Temperature (whole farm or sensors)Low | May or may not be needed, to be explored. | TBD | |||||||||||
Insights | Soil moisture level by sensors over time | Could be based on inputs from readings or soil lab results. | LowMay or may not be needed, to be explored. | TBD | ||||||||||
Insights | Location historyLow | May or may not be needed, to be explored. | TBD |
Iceboxed for V1
View irrigation prescriptions (list view)
View historical irrigation prescription
Filter irrigation prescriptions
View proposed irrigation prescription
Accept proposal
Roll-back to previous irrigation prescription
Reject and do not replace prescription