Civil 2 - Entre Creek Spawning

Center for Engineering Design and Entrepreneurship

Civil Engineering Department Student Project

REQUEST FOR PROPOSAL

Project Title

ENTÉ CREEK SPAWNING CHANNEL EVALUATION AND DESIGN

 

Due Wednesday, October 2, 2013

 

CEDE - Civil Engineering requests a student project proposal for the following project:

 

DESIGN A STREAM CHANNEL WITHIN THE ENTE CREEK/LAKE ROOSEVELT DRAWDOWN ZONE THAT ALLOWS PASSAGE AND PREVENTS WATER LOSS AND MAINTAINS COMPLEXITY AND RESTING AREAS FOR SPAWNING SALMONIDS.

SUMMARY INFORMATION

Due October 2, 2013, before 4:00 PM PST

 

One digital copy in pdf format and one hard copy of proposal must be submitted.

 

Location for Proposal Delivery:      

 

Toni Boggan,

Academic Director CEDE,

Gonzaga University School of Engineering & Applied Science,

PACCAR 214, Spokane, WA 99258.

509-313-3913

Boggan@gonzaga.edu

 

Project Sponsor

The sponsor of this project is:

Spokane Tribe of Indians-

Department of Natural Resources.

 

The liaisons for the project are:

Dr. Brian Crossley

Casey Flanagan

509-626-4408

crossley@spokanetribe.com

caseyf@spokanetribe.com

 

Project Description:

The CEDE - Civil Engineering Department is requiring a proposal from the group of student engineers to provide comprehensive engineering efforts related to the improvement of fish passage in Ente Creek and within the Lake Roosevelt drawdown zone.  Due to the construction of Grand Coulee Dam, there has been significant loss of fish habitat that was vital to salmon, steelhead and trout populations in the Columbia River, the Spokane River and the surrounding tributaries. Currently Enté Creek flows into the Spokane Arm of Lake Roosevelt and has limited spawning opportunities for salmonids. The creek has excessive beaver activity at the mouth of the stream that creates large pools upstream of the beaver dam for salmonid rearing, but the heights of the dams eliminate passage for salmonid spawning. Kokanee salmon and redband trout stage at the mouth of Enté Creek, but cannot enter the stream to spawn. This stream also submerges into the substrate about ¼ mile from the mouth, so usable habitat for juvenile salmonids is limited. Drawdown by Grand Coulee Dam also blocks passage for spring spawners as the stream can submerge into the sediment at the mouth.

 

The Spokane Tribe would like to improve spawning opportunities for current as well as future salmon and trout populations by designing and creating a spawning channel in Enté Creek. This project will require an analysis of local hydrology and hydraulics, selection of several design options, assessment of those design options based on specified criteria (cost, constructability, effectiveness, etc) and weights, sediment transport analysis, habitat assessment, and hydraulic channel and fish passage design, while accounting for Beaver activity in the area. The goal is to create a stream channel within the drawdown zone that allows passage and prevents water loss and maintains complexity and resting areas for spawning salmonids. By creating a spawning channel like those created in Canada, Enté Creek could provide greater spawning opportunities for the current salmonid populations as well as salmon and steelhead that may be reintroduced into Lake Roosevelt when fish passage at Grand Coulee and Chief Joseph dams are created.

 

The project will produce a conference or journal publication and a final report to submit to the sponsor. Students will be responsible to make required presentations of the project activities and may also attend an appropriate conference.

 

EVALUATION PROCESS

The proposal evaluation process will be determined by the project advisor in conjunction with the CEDE, the project sponsor, and the CEDE Design Advisory Board.  It will be based on the organization of the project efforts reflected in the proposal and the educational goals achieved in the completion of the proposal.  Note that some efforts in the project are oriented to achieve educational goals that are not required to achieve the project sponsors goals.

 

BACKGROUND INFORMATION

The lower Spokane River below Little Falls Dam has become a portion of the Lake Roosevelt reservoir system as a result of Grand Coulee Dam’s backwater. At full pool in Lake Roosevelt, Ente Creek, a sandy tributary to Lake Roosevelt, is filled in with fine sediment deposits smothering spawning gravels. During Lake Roosevelt drawdown, the mouth of Ente Creek returns to a free flowing system with the original channel being exposed during spawning season.  However, shallow depths in Ente Creek make it difficult for native salmon and redband trout to migrate upstream to spawn and with sand covering potential spawning runs within the drawdown zone it also decreases critical spawning habitat. In addition, there is significant Beaver activity in Ente Creek, and their dams create fish passage barriers with the creek. 

 

PROJECT INFORMATION AVAILABLE

The project team must familiarize themselves with the existing condition of the project in order to properly prepare the project proposal.  The sponsor may have survey and field data necessary to complete the modeling and analyses portions of this project.  The sponsor should be contacted by the design team to determine what data is available for use. 

 

STUDENT PROJECT ACTIVITIES REQUIRED

The student project group will, at a minimum, provide the following efforts and deliverables in the completion of the project addressed in this proposal:

 

Scope of Activities Required to Meet Project Goals

 

Task 100                                Project Management and Coordination

The student group shall organize, manage and coordinate the efforts required to accomplish the project using standard project management and contract administration techniques. Key management activities are identified below:

 

            Sub-Task 110                        Kick-off Meeting

The Student Team will conduct a kickoff meeting with their project advisor and sponsor liaison’s to gain familiarity for the project and to solicit input, gather available data and information.

 

            Sub-Task 120                        Routine progress-review meetings

Routine progress-review meetings will be conducted on a regular basis as follows:

a.      Weekly progress reports are required and are to be submitted electronically to the advisor by 5:00 pm each Thursday. Weekly progress reports must include, at a minimum, activities completed by each team member for the current week, expected work for the upcoming week, and updates to the project design budget and schedule.

b.      In addition, a complete hardcopy record of the project reports and files must be maintained by the student team and be made readily available during consultations with the advisor. Typical method would be a project notebook. The advisor and liaison will ask to review this notebook periodically to discover the status of the work being completed. 

 

            Sub-Task 130                        Regular Advisor and Liaison Meetings

After the kick-off meeting, the Student Team will meet weekly with the project advisor, and will also meet when needed with the project liaisons.  All meetings with advisor and liaison’s MUST be arranged by members of the Student Team in advance (at least 2 days prior) and include a proposed meeting agenda sent to the advisor or liaison prior (at least 2 days) to the meeting.  All meetings must be documented by the Student Team in the form of meeting minutes with copies distributed within 3 days of the meeting to all team members and the project advisor and liaison’s, as above.

 

      Sub-Task 140            Quality Assurance/Quality Control

The Student Team will perform a methodical QA/QC effort in a manner suitable to the project advisor and liaison, to prevent incorrect, sub-standard or dangerous results from being included in the end of semester project reports.

 

      Sub-Task 150            Project Schedule / WBS /Gantt Chart

 

 

Task 100 Deliverables

• Electronic copy of agenda for team meetings.
• Electronic updates to project design budget and schedule that includes budget and personnel hours for each sub-task in the entire project.
• Electronic copy of resolutions and action items for each meeting.
• Statement on the QA/QC activities for reports submitted at the end of each semester to describe the review and checking procedure employed.

 

Task 200                                Project Data Collection

Participate in initial site visit to tributary locations. Work collaboratively with project liaison’s, tribal contacts, and regulatory agencies’ staff to develop project data suitable for a design.  Data could include soils, geology, site survey, wetlands evaluations, and other data.  Proposal submitted is to identify data needs and collection methods for project. Existing data that is available will be provided by project liaisons. 

 

Subtasks:

            Subtask 210 - Literature Review on the Use of Beaver in Restoration Design

            Subtask 220 - Literature Review of Spawning Channel Design in Canada Stream

            Subtask 230 - Survey and Topography

            Subtask 240 - Bed and Bank Soil Characterization

            Subtask 250 - Stream Stability and Habitat Characterization

            Subtask 260 - Lake Roosevelt Drawdown Schedules

            Subtask 270 - Rainfall/Hydrologic Analysis

           

Task 200 Deliverables

• Electronic copy of literature, data and mapping, reports or surveys completed for the project and to be included in the project report.
• Bibliographic references and annotations for significant literature used, suitable for use in conference publication.
• Summary of safety and legal issues addressed in design.

 

Task 300                                Project Design Efforts

The student team will develop plans, drawings, analysis, comparisons, and other design work required to successfully achieve the project goals. The specific project approach will be determined by the team in the project proposal. The final scope should include at a minimum the following sub-tasks (more may be added):

            Sub-Task 310                        Stream Physical Characterization

Analyze survey, sediment, and vegetation data to characterize stream stability and habitat conditions.

 

Sub-Task 320                        Stream Biological and Ecological Characterization

Research the spawning characteristics of native fisheries (redband trout and Kokanee salmon). Conduct a habitat analysis to determine barriers to fish movement.  Evaluate macroinvertebrates available for spawning fish.  Evaluate the extent and impact of Beaver activity in the reach. 

 

            Sub-Task 330                        Hydrologic Analysis

Determine flow data for Ente Creek using Spokane Tribe of Indians and USGS Gage flow data (if available).  If no flow data is available, hydrologic analysis methods will be used to develop flow hydrographs for Ente Creek.  The team must determine the best hydrologic method to apply (e.g., SCS, HEC-HMS, etc.)

 

Sub-Task 340                        Hydraulic Analysis and Tributary Barrier Analysis

Conduct a hydraulic study using either HEC-RAS or River2D, depending on the available survey data.  These models will be used to analyze hydraulics and sediment transport within Ente Creek.  The resulting output can help determine fish habitat characteristics and potential barriers to fish movement.

 

Sub-Task 350                        Design Options and Assessment of Design Options

Select several spawning channel design options, assess those design options based on specified criteria (cost, constructability, effectiveness, etc) and weights, and recommend a final design option that satisfy sponsor requirements. 

 

Sub-Task 360                        Final Design of Ente Creek Spawning Channel

Design a stream channel within the drawdown zone that prevents water loss and maintains complexity and resting areas for migrating spawning fish. This stream channel should also prevent sedimentation within the drawdown zone and account for Beaver activity while providing spawning habitat. This will include a hydrologic, hydraulic, sediment transport, and habitat analysis to produce the final design. 

 

 

 

Task 300 Deliverables

• Electronic copy of drawings, calculations, data, reports or calculations completed for the project design and to be included in the project report.

 

Task 400                                Project Regulatory Requirements

Determine appropriate regulatory guidelines to use in the completion of the project.  Some codes and regulations that may apply include: FEMA Floodway Regulations, National Wetland Regulations, US Army Corps of Engineers Waterways Permits, Washington Dept of Fish and Wildlife Aquatic Habitat Guidelines (Fish Passage), etc.

 

 

Task 400 Deliverables

•  Provide appropriate written summary of regulations that would apply to the project.

 

Task 500                                Project Costs, Specifications and Maintenance   

The student team will develop specifications, cost estimates for construction of the final spawning channel design, and summary of issues affecting the maintenance of the channel design. The specifics will be determined by the team in the project proposal.

 

Task 500 Deliverables

•  Provide appropriate written summary of results

 

Task 600                                Project Sustainability Evaluation  

Based on the Tribe’s needs and the understanding of the safety, and regulatory requirements, evaluate the preliminary design developed in the completion of the project for overall sustainability and identify other opportunities for increasing sustainability that are potentially achievable.

 

Task 600 Deliverables

• Provide appropriate written presentation that:

a)              Describe the environmental benefits/costs of the project. 

b)              Describe the social benefits/costs of the project. 

c)              Describe the economic/costs benefits of the project. 

d)              Summarize how sustainable the methods used to meet the project goals are. 

 

Task 700                                Project Impacts on Society

The final report submitted for the project will include a discussion, using properly sourced references on what impacts the implemented project will have on the related social systems in the project area.  (Are water supplies depleted?  Are views impacted, is the area better served in other ways?, etc.)

 

Task 800                                Project Reports, Publications and Presentations  

The project will require a written proposal, progress report, final engineering report, draft conference publication, design plans, and several oral presentations on progress. 

1. Proposal will include a project description, proposed tasks, expected timeline, and design cost estimate and will be due during the first semester of work. This proposal must layout out a specific timeline (Gannt Chart) for deliverables and responsibilities for the design tasks.
2. A Progress Report will be due at the beginning of the Spring Semester and will outline the progress that has been made on the project.     
3. A Final Design Report will be due at the end of Spring Semester and will include: (1) an executive summary, (2) a comprehensive report detailing the study area, project management strategy, and all targeted improvements (design of final fish passage recommendation) (3) design drawings and (4) any supporting documentation.

4.      A final draft publication (for conference or journal) dealing with the project that may be presented at a national conference. 

 

Task 800 Deliverables

•  Reports, publications and presentations in electronic format in a timely manner.

 

PROJECT SCHEDULE

Timeliness of project completion is critical. The project schedule contains some specific milestones and also must accommodate the academic calendar. The student group will use the general dates below to develop the comprehensive schedule required for the proposal.

 

Information on Proposals Available:                                   September 4, 2013

Teams Selected:                                                                   September 6, 2013

Sponsor Workshop                                                               September 11, 2013

Civil CEDE Mandatory All Student/Advisor Meeting        September 18, 2013

Labor Day                                                                              September 27, 2013

Proposals Due                                                                      October 2, 2013

Founder’s Day Holiday / Midterms                         October 21, 2013

Roundtable Project 30 % Progress Meeting                     October 30, 2013

Thanksgiving Holiday                                                           November 27 – 29, 2013

Project Status Presentation 50% Progress                       December 11, 2013

Project Status Report Due                                                   December 13, 2013

Reading Days                                                                       December 14 – 16, 2013

Classes Begin                                                                       January 14, 2014

Martin Luther King, Jr., Holiday                                           January 20, 2014

President's Day Holiday                                                       February 17, 2014

Roundtable 60% Progress Meeting / Social                     February 19, 2014

Spring Vacation                                                                    March 10 – 14, 2014

Good Friday – Easter Holiday                                             April 18 – April 21, 2014

Final Reports Due                                                                 April 25, 2014

Final Design Presentation                                                   April 30, 2014

 

PROJECT BUDGET

The student group will include a budget that details the costs of completing the project design tasks. This budget is not the “engineers estimate” to complete the implementation of the design; it is the costs to perform the engineering tasks and does not include the value of project team personnel hours. This requirement is contained in Task 100, but is highlighted here.