As a staff person I want to create a RUP with a plan end date beyond the current agreement expiry date so that pre-decision processes (ex. consultation) and approval can be complete before livestock turnout

[LisaMoore1]

Explanation

• grazing agreements are replaceable meaning it is unusual for a plan not to be replaced for an additional term at the time of expiry
• staff must work on the assumption that the agreement WILL be replaced
• before a RUP can be signed by the decision maker it must go through extensive consultative (and other) processes which take time
• waiting until agreements ARE replaced (always on January 1st of the year following expiry) does not allow sufficient time for those processes and decision making before turn out -- and a RUP must be in place at time of turnout
• the processes of preparing a new RUP for approval must begin before the agreement expires even though the new RUP in question may have one or both of plan start and end date beyond current agreement expiry

Considerations

• key data in RUPs is pulled from FTA -- most notably the usage data
• usage data is relatively stable but can change somewhat over time (ex. non-use, temporary increase, or permanent allocation change)
• usage data does not exist in FTA for dates beyond the current agreement expiry -- usually entered early January following expiry
• annual usage data is an essential part of the RUP and critical for an agreement holder preparing schedules
• the last year of the current agreement term (meaning the year of expiry) is more often than not the usage that will continue for the foreseeable future -- but as noted above that may not be the case if the final year reflects a non-use or temporary increase
• the final year of the agreement AUM allocation (usage) may be use to populate all upcoming years (we'll call that post-expiry data) in the new RUP recognizing that:
  - staff may need to overwrite that data if final year is mid-stream in a non-use or temp increase
  - FTA will need to overwrite the post-expiry data once the replaced agreement and usage has been entered in FTA
  - there is potential at the time of overwrite that the FTA data differs from the data entered in by staff therefore the differences need to be identified and staff will need to knows what they need to address

Sub-elements

• staff generate new RUP with date(s) extending past agreement expiry
• system populates all post-expiry usage data with the AUMs from the final agreement year AUM usage for 'past agreement date RUPs' #152
• staff can overwrite the usage data for specific years
• at time of FTA data update post-expiry usage data overwritten with FTA-current data
• staff are notified if any FTA-current data differed from post-expiry data
• staff can enter amendment process to update data if needed