My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
IBCC Meeting Notes June 19 2007
CWCB
>
Interbasin Compact Committee
>
Backfile
>
IBCC Meeting Notes June 19 2007
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/15/2009 11:55:18 AM
Creation date
7/12/2007 8:53:40 AM
Metadata
Fields
Template:
Interbasin Compact Committee
Title
IBCC Meeting Notes
Date
6/19/2007
Interbasin CC - Doc Type
Meeting Notes
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
17
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
a single text negotiating document , and it would give Roundtables a good framework to <br />work from. <br /> <br />Melinda Kassen : In addition to the list of questions, there is also the methodology of h ow <br />you’re going to go about answering the questions. Some of us may be able to ask <br />questions, but don’t know about methodology. If we’re really writing a scope of work <br />someone is going to have to do, engineers might disagree about th e methodology and that <br />has to b e part of the discussion as well . There might be different views on methodology <br />with this gro up, the R oundtables or the CWCB. It would be good to have information on <br />proposed methodology before we look at it at the August meeting. <br />th <br />Rick Brown : The CWCB B oard meeting is July 13 . Randy Seaholm is not here today, <br />however I think it makes sense to try and get revised draft by July, and put more context <br />than what we have here currently. <br /> <br />Eric Wilkinson: I think if you arrange the scope of work from a procedural standpoint, <br />and outline a list of questions already identified, then I think the Roundta bles will be <br />more comfortable . Right now, when I look at this scope of study, I can’t see the end, and <br />people will want to see that so they know how those questions are going to be addressed <br />and answered. The more transparent you can make this and the mo re self - explanatory the <br />more success you’ll have with the R oundtables. <br /> <br />Carl Trick : After the comments heard at yesterday’s Four Roundtable meeting, I think we <br />have to be careful a bout withholding this from the R oundtable s. The sooner we get this <br />out the better. I would be cautious about with holding this too long from the R oundtables <br />and not getting their input. <br />th <br />Rick Brown : Do you think that A ugust 6 is too late? Many R oundtables meet the <br />following week. <br />Carl: I don’t think there is a perfect timet a ble. They wanted it yesterday . <br />Dan B irch : would be encouraging to add some of the items that came from yesterday’s <br />meeting to the scope of work. <br /> <br />Eric H ecox : I think if we combine the summary from yesterday and the minutes from our <br />last meeting, we ca n distribute something, and you folks can seek whatever input you <br />want. We’ll get it out as soon as we can with those pieces included. If you have <br />ro undtable meetings after it comes out and before the A ugust IBCC meeting, you can <br />seek feed back. <br /> <br />Jeris D anielson : Do you really think you’re going to go out to 8 R oundtables and get <br />consensus? I think the Arkansas basin is going to view it very differently than others. <br />Where does the buck stop, and who makes the final decision? <br />Rick Brown : M y hope was that the IBCC would do that , so that it wouldn’t end up on me. <br />We s pent 18 months on SWSI, getting buy - in at every phase, giving opportunities to <br />comment, and at the end people still didn’t think that it was okay. The idea was that this <br />body would help us fi nd that compromise. The study team would like the IBCC to help <br />us find the way it meshes. <br /> <br /> 8 <br />
The URL can be used to link to this page
Your browser does not support the video tag.