We value your feedback and suggestions as they are essential to our goal of providing you with the best possible user experience. This page enables you to track your suggestions in our product roadmap. If you don’t see what you want here, please submit a new feature request at https://forms.koidra.ai/feature_request .
‣
In progress
Standardize metric names
Standardize metric names
Comparisons are currently not feasible due to inconsistent metric names. The issue will be fixed in the end of June.
While running autopilot, limit the CO2 setpoint, set the minimum vent for day and night time
While running autopilot, limit the CO2 setpoint, set the minimum vent for day and night time
Limit the CO2 setpoint of autopoilot to 600 ppm. Set the minimum for the vent to 5% night and 10% during the day because the humidity is high.
We already supported to limit the CO2 setpoint. High humidity is a valid issue, however, we prefer to update the vent control logic rather than open vent at 5% night and 10% day.
Disable unready setpoints in Opera
Disable unready setpoints in Opera
Whenever Opera operates, it operates all the setpoints even the setpoints that are under development. Temporarily, users have to delete the formulas of these setpoints.
This feature is definitely necessary, we added to our roadmap. It will be released in July.
Easily replicate a formula for new compartments
Easily replicate a formula for new compartments
Quickly replicate a formula and change the variables inside the formula for other compartments
We introduce the feature group setpoint, this feature allow users to configure one formula for multiple compartments. It will be released in July.
‣
P1
Add additional values from the PLC/SCADA/Priva
Add additional values from the PLC/SCADA/Priva
- Short-term: We will add any requested value
- Long-term: Make it more configurable by the users so the user can enable the data on KM by themselves
The test feature of Opera is very slow
The test feature of Opera is very slow
We will fix this issue ASAP
‣
P2
Export charts to report
Export charts to report
Need to clarify how this feature is used.
Support the FFT function to analyze vibration
Support the FFT function to analyze vibration
Need to clarify how this feature is used.
Search bar for Alias
Search bar for Alias
We already had it on our roadmap. Plus, we’ll move the Alias to the tab Automate as well.
‣
P3
Personalized alerts per phase: option to toggle on and off existing alerts per user
Personalized alerts per phase: option to toggle on and off existing alerts per user
We make it a P2 item because a zone (or phase) should have a single decision making grower who would set up the alerts for that zone.
Ability to compare across years
Ability to compare across years
This is nice to have; however it would require some nontrivial design thinking
Calculate some variables such as average 24 hour greenhouse temperature, achieved RTR
Want to see it in the table format
Calculate some variables such as average 24 hour greenhouse temperature, achieved RTR
Want to see it in the table format
Support calculation of the temperature or other metrics from sunrise to sunset
Check the bug as there is only data of calculated RTR available in the past 24 hours
Some other formular such as night dry back of substrate water content and weight
Some other formular such as night dry back of substrate water content and weight
WS will get back to us for their reference information and user stories on how they want to use these information
Calculate the expected daily radiation based on historical averages
Calculate the expected daily radiation based on historical averages
Math: can be done easily with linear regression.
UX: how to enable it?
Skip the reason to change when I only change a constant in the formula
Skip the reason to change when I only change a constant in the formula
We need to clarify other use cases.