Laserfiche WebLink
<br />. <br /> <br />Technical Clarity in Inter-Agency Negotiations: Lessons From Four Hydropower Projects <br /> <br />willing to engage in the work of defining the technical <br />issues. In the absence of this willingness, it is not dif- <br />ficult to imagine frustrating and fruitless negotiations <br />leading to a series of studies that fail to provide the <br />necessary information. This was the case in the <br />Ashton-St. Anthony consultations, where studies of <br />Ashton Reservoir were conducted without prior agree- <br />ment on a precise definition of the problem and fish <br />passage studies were conducted in the face of dis- <br />agreement over proper methods. As a result, resource <br />agencies and the applicant had different expectations <br />and never agreed on study results. <br /> <br />Maintaining Technical Clarity When Issues Change <br /> <br />A natural progression of these consultations was <br />that as the effects of the proposed project become <br />clearer, the technical issues changed. This was exem- <br />plified in Koma Kulshan. As the project design <br />emerged, the effects of the project became more tangi- <br />ble. Participants believed that these changes were a <br />natural and inevitable function of increased infonna- <br />tion. <br />However, changing the scope of the technical issues <br />is not always so readily accommodated. In Cataract, <br />new issues were introduced as project impacts became <br />more apparent. Up to a point, this created no <br />intractable problems, but when the state opened the <br />issue of requiring the utility to provide flows for waste <br />assimilation, the consultations broke down. The utili- <br />ty did not argue that the technical issue was invalid, <br />only that it was not properly addressed within the <br />FERC consultation process. Moreover, the utility <br />viewed the state's action as an unfair attempt to <br />introduce a new issue at the eleventh hour and to <br />bypass the negotiation process. Interestingly, the <br />applicant pointed to this episode as one that dramati- <br />cally decreased the level of technical clarity, while the <br />state resource agency representative stated that it <br />greatly enhanced technical clarity. <br />Other issues in the Cataract project were raised <br />and then dropped during the process. For example, <br />discussions of comprehensive river planning were dis- <br />continued because the applicant had recently had an <br />unsuccessful experience with a comprehensive plan in <br />another river system. Because the issue had not been <br />resolved and was dropped without consensus, some <br />participants believed that the negotiation was a fail- <br />ure because it did not resolve a key issue. The key to <br />maintaining technical clarity when the issues change <br />is to share information and reach consensus about <br />adding or deleting issues from the negotiation. <br /> <br />Describing a Problem Versus Crafting a Solution <br /> <br />A common pattern was that parties reached agree- <br />ment on problem definition and accepted most new <br />technical issues as they arose. Mter agreeing on these <br />issues, however,it often became problematic to define <br />appropriate studies. If studies were defined, interpre- <br />tation of study results - and making decisions about <br />what actions to take based on those interpretations - <br />sometimes led to lengthy disagreements. Even in <br />Koma Kulshan, general agreement on the scope of the <br />technical issues did not translate into easy agree- <br />ments on how to study the problems. Although they <br />agreed on the need to conduct a study of the fishery, <br />resource agencies and applicants disagreed on <br />methodologies and target species. <br />Negotiators in the Oswegatchie license consulta- <br />tions agreed that the consultations were single-issue, <br />focusing on flows in bypass and downstream reaches, <br />but agreement was not achieved for flows in each of <br />these stretches. Participants speculated that lack of <br />agreement on appropriate study design, the inability <br />to reach consensus on study interpretations, and dif- <br />fering goals all contributed to the lack of success in <br />defining technical issues and, ultimately, in reaching <br />a satisfactory agreement. <br />During the Cataract consultations, all parties <br />agreed to study fish passage. Respondents verified <br />that this was broadly accepted as a legitimate techni- <br />cal issue. They then went on to describe the difficulty <br />of making decisions about how to provide fish passage <br />and how to monitor the results. During the Ashton- <br />St.Anthony negotiations, resource agencies and the <br />applicant bitterly disagreed about whether fish pas- <br />sage was an issue. The applicant contested resource <br />agency studies that indicated the need for fish pas- <br />sage. Once fish passage was made possible by remov- <br />ing boards from the diversion dam, the resource <br />agencies questioned the validity of the technique cho- <br />sen by the applicant to study the effectiveness of the <br />solution. <br />The Ashton Reservoir study was another example <br />of a study conducted without clear understanding of <br />how the results would be applied. The applicant con- <br />sidered the study an avenue for evaluating the poten- <br />tial for a cutthroat trout fishery, while the resource <br />agencies viewed it as an opportunity for detennining <br />which fish species might do well in the reservoir. <br />When asked what factors stood in the way of reaching <br />an agreement, one resource agency representative <br />commented: <br /> <br />I think lack of consensus on what the informa- <br />tion said. Doubt on [the utilities'] part that this <br />data was representative of what was going on <br /> <br />195 <br /> <br />WATER RESOURCES BULLETIN <br />