Laserfiche WebLink
<br />Technical Clarity in Inter-Agency Negotiations: Lessons From Four Hydropower Projects <br /> <br />Clean Water Act (Federal Water Pollution Control <br />Act; 33 U.S.C. ~ 1251-1376). The FERC post-dated the <br />license to include the 401 Water Quality Certification <br />so that conditions of the certification were included in <br />the FERC license. At the time of our interviews, in <br />July of 1992, the applicant was contesting this action. <br />The negotiations associated with re-licensing the <br />Cataract project were considered minimally success- <br />ful because of those unresolved issues. <br />During the first phase of the Cataract negotiation, <br />several general areas of agreement existed..AlI par- <br />ties agreed on the need for aquatic base flows <br />throughout the project area, the desirability of design- <br />ing a comprehensive river plan, and the need for fish <br />passage. Parties did not agree about the geographic <br />extent of salmon restoration efforts or the need for <br />determining minimum flows below Cataract darn to <br />protect the estuary below the darn. Disagreements <br />also surfaced about appropriate timetables for con- <br />structing fish passages. When asked to rate the clari- <br />ty of the technical issues at this time, respondents <br />rated clarity between six and eight on a ten-point <br />scale. <br />In the second phase, some of the earlier issues were <br />clarified, but other issues were raised. For example, <br />the effect of the project on the estuary was recognized <br />as an important potential impact, while the fish pas- <br />sage issue was clarified because parties reached <br />agreement on how to approach the problem. When <br />discussing the consultation process in terms of its <br />ability to define and resolve issues, the following <br />interchange occurred: <br /> <br />Q: Once established, during that first phase, was <br />the understanding of what the technical issues <br />were, ever lost? <br />A: I think what the consultation does, and cer- <br />tainly what it did in Cataract, is, it better <br />defines [issues]. As we went through this pro- <br />cess, we better defined maintenance drawdown <br />as a potential habitat concern. Better defined <br />certain fish passage issues. So I don't think any- <br />thing was lost, just better defined, which is the <br />goal of that process. <br /> <br />While some issues were clarified as the process <br />moved forward, others became muddier or were <br />dropped altogether. For example, earlier discussions <br />about a comprehensive river plan were discontinued <br />so that, rather than studying the Saco River as a <br />whole, only the portion of the river affected by the <br />Cataract project was considered. The applicant had <br />attempted comprehensive river planning on another <br />river, but the plan was never implemented. Thus, <br />there was reluctance to repeat this costly exercise. <br />The subsequent exclusion of comprehensive planning <br /> <br />for the Saco River effectively limited the scope of the <br />issues in a way that was unsatisfactory to some par- <br />ticipants. The question was not one of clarity. The <br />issues were clear, but not all parties agreed with the <br />scope and definition. <br />A more controversial issue that arose during the <br />second phase concerned the lack of a Section 401 <br />Water Quality Certificate for waste discharges of the <br />cities of Biddeford and Saco below Cataract Darn. <br />During the course of the consultations, the state agen- <br />cy realized that although the discharges had been <br />occurring for a number of years, no minimum flow <br />agreements were in place. The state agency requested <br />that project operators release flows to assimilate the <br />discharges and planned to make these flow releases <br />part of the license. However, the operators replied <br />that because the darn was built first, the utility had <br />no responsibility to provide present or future assim- <br />ilative capacity. The position of the utility was that <br />the problem was due to the state's mistake and that <br />the state had no authority to require assimilative <br />releases from the utility. Ultimately, the utility <br />entered into agreements with both cities to provide <br />this capacity. The applicant stated that the attempt to <br />include this issue at the eleventh hour detracted from <br />technical clarity; the resource agency believed that <br />addressing this issue led to increased technical clari- <br />ty. At the heart of the debate was whether the issue of <br />flows below the Cataract darn was properly included <br />as part of the license consultation, even though it was <br />clear that diluting the waste stream was a legitimate <br />issue. <br />The disagreement about the state's authority to <br />require 401 certification as a license condition carried <br />over into the post-license phase and was still alive at <br />the time of our interviews. In the final phase, the <br />applicant stated that the clarity of the technical <br />issues dropped, largely due to the lack of resolution <br />on the minimum flow issue below Cataract darn. Dur- <br />ing this phase, the applicant rated the clarity of tech- <br />nical issues at three on a ten-point scale. All other <br />participants gave ratings between eight and ten. <br />Flow-related questions are usually central in con- <br />sultations of this kind. Debates tend to focus on selec- <br />tion of or choice of methodologies and interpretation <br />of study results. From the outset of the Cataract con- <br />sultation, agencies and the applicant agreed to study <br />fish passage. The more intense discussions carne <br />later, when decisions were made about how to provide <br />fish passage and how to monitor the results. <br /> <br />Ashton-St. Anthony <br /> <br />The Ashton-St. Anthony project is located on the <br />Henry's Fork of the Snake River in eastern Idaho. <br /> <br />191 <br /> <br />WATER RESOURCES BULLETIN <br />