My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
7955
CWCB
>
UCREFRP
>
Copyright
>
7955
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/14/2009 5:01:46 PM
Creation date
5/22/2009 12:25:03 PM
Metadata
Fields
Template:
UCREFRP
UCREFRP Catalog Number
7955
Author
Burkardt, N., et al.
Title
Technical Clarity In Inter-Agency Negotiations
USFW Year
1995
USFW - Doc Type
Lessons From Four Hydropower Projects, paper no. 94090 of the Water Resources Bulletin
Copyright Material
YES
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
12
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
<br />Technical Clarity in Inter-Agency Negotiations: Lessons From Four Hydropower Projects <br /> <br />TABLE 1. Questions Posed to Evaluate the Clarity of Technical Issues. <br /> <br />1. At this phase, did the parties involved agree to the definition of the instream flow problem? <br />- the geographic extent <br />- the range of flows to be considered <br />- the important species and life stages <br />- the recreation and other water uses to be included <br /> <br />2. Didyou agree with the definition of these technical issues? <br />If"NO": If not now, then when? [Identify phase.] <br /> <br />3. At what point was the study clearly dermed? <br /> <br />4. Once established, was that understanding ever lost? Did it fluctuate, or remain constant? <br /> <br />5. For this phase, please rate the technical bounds on a scale where <br />l=completely obscure - to - lO=complete clear. <br /> <br />For subsequent phases, respondents were asked: <br /> <br />6. Did technical issues change during this phase? <br />If "YES": Were new technical issues introduced, or did the existing issues change? <br />Did you agree to these changes? <br /> <br />7. How clear were the technical issues? <br />l=totally obscure - to - lO=complete clear. <br /> <br />and the project began operating in 1991. The pre- <br />license consultation began in 1980 and focused on <br />issues of stream flow, sedimentation, and public <br />access. These issues were fully resolved before the <br />license was issued in 1986. Participants reported that <br />because the physical impacts of the project were <br />expected to be minimal, the level of conflict was low. <br />In February of 1992, participants in the consultation <br />were interviewed. <br />The negotiated agreement reached in the Koma <br />Kulshan consultation was rated as fully successful <br />according to our study criteria. All parties believed <br />that a successful agreement was reached; eight of the <br />ten stated that the final agreement contained provi- <br />sions for monitoring (the other two did not recall); and <br />each individual reported that he or she would willing- <br />ly negotiate with the same group in the future. In <br />fact, this group of people often find themselves in <br />negotiations with each other. This willingness to <br />negotiate with the same parties in the future was <br />found in all of the cases we studied. <br />Because the physical impacts of the project were <br />not of great concern, there were no intractable con- <br />flicts around the issue of technical clarity. This is not <br />to say that there were no disagreements, only that the <br />disagreements did not halt the consultation process. <br />One area of uncertainty was that of cumulative <br />impacts. Resource agencies requested the applicant to <br />conduct a cumulative impact assessment but were not <br />specific about what this meant. In the words of a rep- <br />resentative of the applicant: <br /> <br />[l]t [cumulative impact assessment] is a valid <br />issue. What I did have trouble with is that no <br />one could really define what they meant by <br />"cumulative impact." I'd say "O.K, what do you <br />want us to do?; what is it that you're really con- <br />cerned about?" When we finally did get things <br />pinned down, it came down to sediment, that <br />was the major thing; that was something that <br />was tractable. <br /> <br />The typical progression in terms of clarifying issues <br />tended to follow the pattern of the cumulative impact <br />issue. When technical issues were initially encoun- <br />tered, they were painted with a very broad brush. <br />This lack of specificity led participants to believe that <br />the problem was unmanageable. However, because a <br />general belief existed that others were acting in good <br />faith, these unclear issues were discussed until the <br />scope was narrowed and strategies were designed to <br />address them. Thus, the trend was for technical clari- <br />ty to increase throughout the course of the consulta- <br />tion. <br />Another reason for increased technical clarity was <br />that many issues simply were not raised in the early <br />part of the negotiation. As the project unfolded, the <br />scope and nature of the appropriate issues became <br />apparent. Applicants and resource agencies began the <br />process cognizant of the fact that certain generic <br />issues would be raised: flow, habitat issues, mitiga- <br />tion, and the like. It was not until the specific site was <br />examined that other issues arose. For example, a <br /> <br />189 <br /> <br />WATER RESOURCES BULLETIN <br />
The URL can be used to link to this page
Your browser does not support the video tag.