List of epics
Epics | Description |
---|
Flow
Versions | ||||
---|---|---|---|---|
|
| The ability to add sensors, sensor reading types, and sensor readings to a farm via:
|
|
|
V1, |
V2 |
View sensor |
V1 | |
Retire sensor |
V1 | ||||
|
|
V2 | ||
View pivot | Needs to encompass:
| |
View farm map layers | Needs to encompass:
| |
Create irrigation task | ||
Generate irrigation prescription | Includes:
| |
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 | ||||
---|---|---|---|---|
Sensors | Add sensor via farm map |
| ||
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? | High | |
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 |
Sensors | Edit sensor |
| Do we need to persist history of the sensor location and attributes or is the current state sufficient? | Medium |
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? | Low |
Farm map | List / tile view for all locations with limited filters |
| Low | |
Pivot / Irrigated location | Add irrigated location (via farm map) |
| 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. | High |
Pivot / irrigated location | View irrigated location (via farm map) |
| ||
Pivot / irrigated location | Edit irrigated location |
| ||
Pivot / irrigated location | Retire irrigated location |
| ||
Pivot / irrigated location | Designate existing location as irrigated | |||
Farm map filters | Filter pivot / irrigated location on farm map | |||
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! | ||
Farm map layers |
|
| Will be imported via kml at the farm level | |
Irrigation tasks | Add irrigation task flow (user created) |
| Low | |
Irrigation tasks | View irrigation task (user created) | Low | ||
Irrigation tasks | Mark irrigation task completed abandoned (user created) | Low | ||
Irrigation tasks | Edit irrigation task (user created) |
| ||
Irrigation tasks | Add irrigation task (system created) |
| Important to document changes to the task | |
Irrigation tasks | Automated completion of irrigation task (by system) | Should management be able to mark it complete manually?
| ||
Irrigation tasks | Edit irrigation task (system created) | Don’t allow? Link to irrigation prescription instead? | ||
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 | ||
Notification | View irrigation prescription notification | Link to irrigation prescription | ||
Whole farm characteristics | Upload farm characteristics |
| ||
Insights | Temperature (whole farm or sensors) | Low | ||
Insights | Soil moisture level by sensors over time | Could be based on inputs from readings or soil lab results. | Low | |
Insights | Location history | Low |
Logic:
Understanding various types of readings:
Temperature (component based)
Soil moisture
Data needs
Crops
Add several tables referencing crops:
Crop stages (Maybe?)
ET curve for crop
Locations
APIS
Historical weather actuals:
Year / month / day
Temp max / temp min
Wind in kph
https://acis.alberta.ca/acis/api/v1/imcin/aimm/data/EnchantII22.txt
Crop stages for dry peas
Based on days from planting
Water needs for dry peas
...
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
...