Laserfiche WebLink
FINDINGS <br />Eastman Falls Project <br />Located on the Merrimack River in New <br />Hampshire, this project is distinctive in that it was <br />one negotiation within the larger framework of the <br />Merrimack River Comprehensive Fish Passage <br />Plan. The major issue was up- and downstream <br />fish passage. As part of negotiations on the <br />Comprehensive Plan a requirement for the project <br />operator to install fish passage facilities had been <br />discussed and agreed upon before the application <br />for a renewal license on the Eastman Falls project <br />was filed. As a result of these earlier discussions, <br />there was a great deal of clarity on technical issues <br />before the license consultation began. Through the <br />Comprehensive Plan, the parties had developed a <br />clear understanding of the scope and scale of the <br />issues, as well as the appropriate methods to <br />resolve those issues. Comments from two <br />respondents illustrate the clarity of technical issues: <br />Yeah, I think there was agreement <br />on the technical issues, both with <br />respect to instream flow and fish <br />passage. As I said, there was <br />agreement on the method to be <br />used. <br />Technical issues [were] very clear, just <br />from the things that I've cited in the <br />application, that they agreed before they <br />even met with us...when I read this, I was <br />pleased... Basically, my little notes in the <br />margin here were `concur, concur.' <br />The respondents' rating of a high level of technical <br />clarity is illustrated further by the numerical scores. <br />The average score for technical clarity in the <br />consultation was 8.5. This does not mean there <br />were no technical controversies. <br />For example, controversy surrounded the <br />technical responsibilities of the parties, specifically <br />in terms of jurisdiction. Members of the Technical <br />Committee for the Comprehensive Plan formulated <br />recommendations which they passed on to the <br />Policy Committee. The Policy Committee, in turn, <br />constructed the Comprehensive Plan. In the <br />Eastman Falls consultations that followed, the <br />negotiators were bound to adhere to the terms of <br />the Comprehensive Plan. However, some Eastman <br />Falls negotiators believed that they should have <br />been part of the Technical Committee because they <br />were the appropriate parties to provide input on <br />technical issues and boundaries. In fact, the usual <br />practice <br />was for these negotiators to take the lead in <br />formulating technical recommendations, and the <br />reversal in roles was a stumbling block in <br />completing the consultation. <br />We judged this negotiation to be <br />successful. There was complete agreement on <br />resolution of the issues and a strong commitment to <br />implement. All parties were willing to negotiate <br />again and respondents reported that relationships <br />improved. Success scores range from 7-10. <br />Koma Kulshan Proiect <br />Like the Eastman Falls project, Koma <br />Kulshan had a distinctive characteristic. This <br />characteristic was that the consultations' main <br />issues--streamflow (i.e., How much water should <br />remain in the bypassed reach?), sedimentation (i.e., <br />How much sediment would be washed into a <br />downstream lake?), and public access to the small <br />reservoir created by the project--were fully <br />resolved. The respondents credited this to the fact <br />that the physical and biological impacts of the <br />project were expected to be minimal. Once the <br />parties realized the straightforward nature of the <br />environmental effects little conflict ensued. <br />Developing that realization was not easy. Agreeing <br />on a resolution required numerous meetings over <br />several years in which the participants learned to <br />work together, developed a shared technical <br />understanding of project operations (including the <br />difference between pre- and post-project <br />conditions), and constructed a solution. One <br />respondent summarized technical clarity well when <br />he said: <br />[I]t [cumulative impact <br />assessment] is a valid issue. What <br />I did have trouble with is that no <br />one could really define what they <br />meant by `cumulative impact.' I'd <br />say `O.K., what do you want us <br />to do?; What is it that you're <br />really concerned aboutY When we <br />finally did get things pinned <br />down, it came down to sediment, <br />that was the major thing; that was <br />something that was tractable.