Build & Run a Learned Flow Program

Modified on Wed, 13 Nov at 1:39 PM

This walkthrough will demonstrate how to build and run a learned flow program. By running a Learned Flow program, uses calibrated Expected Flow for a given station. A Learned Flow program can be built like a standard program & include any number of stations. In this Walkthrough, we demonstrate how to quickly build a Learned Flow program that includes all stations. 


Note: A Learned Flow Program must be completed when using low/high deviation flow alarms. It is recommended to Run a Learned Flow at least yearly. For sites with multiple mainlines, the NLP can will allow irrigation on mainlines that have stations that are not in a Learned Flow state. 



  1. Navigate to   Irrigation ControllerPrograms
  2. Click
  3. Under Strategy dropdown, select Sequential
  4. Under Description, enter “Learned Flow Program”
  5. Click CREATE
  6. Click STEPS
  7. Click
  8. Under Target type dropdown, select All and under Type dropdown, select Learn Flow
  9. Click Wait completion A grey oval with a dot in it

Description automatically generated to toggle to A green switch with a dot

Description automatically generated
  10. Click CREATE
  11. Click SAVE
  12. Click  next to your new learned flow program to run
  13. Once the Learned Flow Program is complete, go to Stations  
  14. Under the Station Actions dropdown, select action Apply observed (learned) flow   SAVE.


You can now see the new calibrated flow values as Expected flow. If you disagree with any of the Learned Flow values, manually update Expected flow by editing a station. 


For a summary of Flow Rules, how they work & definitions, use this link:

Flow Rules in the NLP


For more information on Flow Rule Alarms & how to react to them, use this link:

Flow Rule Alarm Handling


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article