Laserfiche WebLink
<br />~'~\ <br /> <br />l}n~n8 <br />Information Related to Projects <br /> <br />July 7, 1993 <br />Page 2 <br /> <br />(User Interface Note: When designating a demand to be <br />included in a project, the user will have to specify whether that <br />demand is situated downstream from its project reservoir or <br />whether it would have to receive water by exchange. This <br />distinction is necessary in order to assign the ranks that will drive <br />the project deliveries step. It also implies that, if a user changes <br />the project affiliation of a demand, this specification will have to <br />be given with respect to the new project reservoir.) <br /> <br />3; Order of Precedence Among Projects <br /> <br />In order to resolve possible competition for exchange potential <br />among demands belonging to different projects, the projects <br />themselves will need to have a relative ranking. This order will <br />be inferred from the relative priorities of their senior storage <br />rights. Since users cannot modify the priorities of existing <br />storage ranks, the order may be hard-wired as to ,hem and <br />inferred from ,he priori'ies of ,he srorage rig Ius specified for any <br />"potenrial" reservoirs included in a scenario. The network ranks <br />which reflect this ordering will eventually be assigned to links on <br />the demand constructs associated with the respective projects. <br /> <br />4. Order of Precedence Among Demands Within a Project <br /> <br />In order to resolve possible ties among client demands of a given <br />project, when the reservoir/account does not contain sufficient <br />water to satisfy them all, the demands of each project will need to <br />have a relative ranking. This might be generated "invisibly" as <br />the demands are selected by a user and then displayed only if <br />requested. Users will not be given a means of re-ordering the list <br />in the first version of the model, but the implementation should, <br />at least, attempt to facilitate the later addition of that <br />functional ity. <br /> <br />