>> This video will cover how to relate projects
to water management strategies and the application.
For this example, I will use a project shown in Appendix 15 of the RDVP Guidelines
for Data Deliverables Document, also known as Exhibit D, which is available
by a link on the application Help page.
Projects may be related to WMS at either the WMS level or the WMS 1 level.
All entities related to a strategy are dependent on a project being implemented
to receive their strategy of supplies, then the project should be related to the strategy
at the WMS level on the WMS Edit Create page.
Alternatively, if only select entities related to a strategy are dependent
on a project being implemented to receive their strategy supplies,
then that project should be related to the strategy
for those specific WUGs oat the WMS WUG supply level on the WMS WUG Supply Edit Create Page.
In the Appendix 15 diagram, entities A, B, and C's WMS supplies
from the availability increase strategy are dependent
on WMSP 1 being implemented to build the new reservoir.
Therefore, this project should be related at the WMS level on the WMS Edit Create page.
To do this on the application, I will open the WMS module,
and select this availability increase strategy from the list
by clicking its hyper linked WMS name.
At the bottom of the WMS Edit Create page that opens, I will click the "Add Project" button.
This will bring up a pop-up window where I will select the project I want
to relate using the checkbox to the left of the name,
and clicking the "Submit Selected Projects" button at the top.
After this has been processed, my project will be visible under the Related Projects heading
at the bottom of the page, where I will update the Project Tier field with the order
of implementation if multiple projects are associated with the same WMS.
In this example, WMSP 1 is the only project assigned to the WMS at the WMS level.
So, I can leave the Project Tier field blank.
You will also need to select a recommendation type each time a project is related to a WMS.
The recommendation type value is recommended, and should be updated to Alternative only
if there are more than one projects associated with a recommended WMS,
and the project is considered an alternative version of the recommended project.
Or, if the WMS is labeled Alternative,
and therefore the related project should also be alternative.
Once you have confirmed that the project tier
and recommendation type values are correctly entered, and click the "Save" button
on the WMS Edit Create page, you will follow the same process twice for WMSP 2,
since it's related to two WMSs in the Appendix 15 diagram.
In the Appendix 15 diagram, entity B is depended on WMSP 3 being implemented
to build an additional pipeline to receive WMS supplies
from both the availability increase strategy, and the WMS existing availability strategy.
Since entities A and C will not require this additional project to receive their supply,
this project should only be related to entity B in the WMS WUG Supply Edit Create Page.
To do this in the application, I will select entity B
from below the Related WMS WUG Supply Entities Heading on the WMS Edit Create page.
This will open the WMS Edit Create page for the WUG, which will show a list
of all strategies associated with it.
From here, I will click the hyperlink name of the availability increase strategy I'm working
with to expand its WMS WUG supply details.
I will scroll down to the bottom, and click the "Add Project" button to bring up a pop-up window
where I will select the project I want to relate
to the specific WMS supply source using the checkbox to the left of the name,
and clicking the "Submit Selected Projects" button at the top.
After this has been processed, my project will be visible under the Related Projects heading
at the bottom of the page, where I will update the project tier filed with the order
of implementation if multiple projects are associated with this WMS WUG.
In this example, WMSP 3 is the only project assigned to entity B
to this WMS WUG supply source, so I can leave the Project Tier filed blank.
You will also need to select a recommendation type each time a project is related
to a WMS WUG supply record.
The recommendation type default value is recommended, and should be updated
to Alternative only if there are more than one project associated
with a recommended WMS WUG supply,
and the project is considered the alternative version of the recommended project.
Or, if the WMS WUG supply is labeled Alternative,
and therefore the related project should also be alternative.
If a project is assigned to at least one WMS or WMS WUG Supply record as recommended,
the project will be labeled Recommended in the regional and state water plans.
If every time the project is related to a WMS or WMS WUG Supply record,
it is assigned an alternative recommendation, then the project will considered alternative
in the regional and state water plans.
Once you have confirmed that the project tier
and reformation type values are correctly entered for the WMS WUG Supply source,
and click the "Save" button on the WMS Edit Create page,
you will follow the same process assigning the project to the WMS existing availability WMS.
By scrolling to the top of the page, locating the WMS name in the grid,
and repeating the process as depicted in the Appendix 15 diagram.
To learn more about WMS and project relationships, please the RDVP Guidelines
for Data Deliverables document also known as Exhibit D,
which available via a link on the Application Help page.