Student Team: Cody Meckes, Julia Pavicic, Roberto Silva, Eric Spurbeck
Advisor: Bob Turner
Sponsoring Organization: City of Spokane
Liaison: Bob Turner
Center for Engineering Design and Entrepreneurship
Civil Engineering Department Student Project
REQUEST FOR PROPOSAL
COMBINED SEWER OVERFLOW (CSO) RESIDENTIAL STORMWATER TREATMENT
Due Wednesday, October 2, 2013
CEDE - Civil Engineering requests a student project proposal for the following project:
DESIGN OF VARIOUS ALTERNATIVES FOR SUSTAINABLE METHODS OF CAPTURING STORM RUNOFF AT THE SOURCE POINT, USING TECHNIQUES SUCH AS BIO FILTRATION SWALES, GRAVEL GALLERIES, OR OTHER CREATIVE METHODS TO PREVENT THE STORM FLOW FROM ENTERING THE STORM WATER NETWORK AND COLLECTION SYSTEM. THESE METHODS WILL BE EVALUATED AND PRESENTED TO THE CITY FOR POTENTIAL APPLICATION CITY WIDE TO REDUCE STORM WATER FLOW AND RESULTING CONTROL COSTS.
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:
Academic Director of CEDE
Gonzaga University School of Engineering and Applied Science,
PACCAR 214, Spokane, WA 99258.
The sponsor of this project is the City of Spokane. The liaison is:
Bob Turner, PE
The CEDE - Civil Engineering Department is requiring a proposal from the group of student engineers to provide comprehensive engineering efforts related to the development of sustainable technologies that will reduce the stormwater contribution to sewer flows by treating runoff at the residential site. The student team is expected to research existing literature and compare design alternatives so that effectiveness, cost, manufacturability, appropriateness of technologies, and overall compatibility with the project goals can be used to select the most desirable solutions.
Tasks will include, but are not limited to the following:
1. Literature Review:
Prepare a bibliographic resources of runoff reduction methods that could be potential candidates for this project. Make summary of methods and use a suitability matrix to evaluate potential alternatives. Estimate costs as a part of the evaluation.
2. Establish Constraints on Methods:
Based on site visits, make categories of constraints that could include: required area, slope, soil, cost, safety, climate, etc..
3. Establish Illustrative Designs for Preferred Alternatives:
Prepare drawings of applications of preferred alternatives.
4. Establish Performance Evaluations of Illustrative Designs:
Develop performance estimates of alternatives and impacts on overall runoff control costs
5. Compare Preferred Alternatives with Methods for New Construction:
Compare retrofit alternatives to new construction alternatives.
6. Prepare Reports and Presentations to City of Spokane:
Make project outcomes useful to sponsor.
The project will also require the implementation of project management techniques in the completion of the engineering efforts, including interaction with the City of Spokane as the project sponsor, liaisons, project advisors, monitoring efforts and progress, updating the project schedule preparing status reports, gathering information required for design of alternative from appropriate regulatory agencies.
The project will produce a draft of a conference publication and a final report to submit to the sponsor.
Students will be responsible to make required presentations of the project activities to the sponsor at other times, and may also attend an appropriate local conference.
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.
The City of Spokane is obligated to separate storm flows from sanitary sewer flows, which now are combined.
This is a Federal mandate and will be a multimillion dollar project reaching over many years.
Large storage basins and tanks are being constructed all over Spokane to retain storm surges so that they will not overflow into the Spokane River.
The more storm flows are reduced, the smaller the storage basins and tanks will need to be, potentially saving the City millions of dollars.
This project will look at innovative ways to reduce storm runoff in established residential areas by using sustainable methods to capture the storm runoff and prevent it from entering the storm water network and collection systems.
PROJECT INFORMATION AVAILABLE
A large amount of information on runoff control exists both in the City of Spokane and in published literature.
The project team must familiarize themselves with the existing condition of the project in order to properly prepare the project proposal.
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
The Student Team will prepare a detailed schedule and Gantt chart that indicates the person hours of effort in each sub-task proposed. The schedule will require a WBS and will identify the critical path of activities.
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
Work collaboratively with project staff and other reliable sources to develop project data suitable for design. Data may include material and labor costs, geology, site survey, water runoff, climate, power requirements, cultural preferences and other data. Proposal submitted is to identify data needs and collection methods for project.
Sub-Task 210 Literature Review
The Student Team will perform a thorough literature review to form the basis for the design of alternatives and the evaluation of those alternatives developed in the project.
Sub-Task 220 Site Data
The Student Team will collect the site information needed to establish designs at representative sites. Data will include at a minimum: soil, area required, predicted runoff, costs, and construction requirements.
Sub-Task 230 Project Context Data
The Student Team will present information distinguishing the alternatives in terms of legal issues, safety and long-term effectiveness.
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.
Sub-Task 310 Alternative Designs
Provide design drawings, details and material selections for various alternatives.
Sub-Task 320 Alternative Evaluations
Develop rational basis to evaluate variety of alternatives proposed using matrix approach.
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.
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 design alternatives, and a summary of issues affecting the maintenance. 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 users’ needs the performances of alternatives and the understanding of the safety, and regulatory requirements, evaluate the preliminary alternatives 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 Reports, Publications and Presentations
The project team is required to prepare a final report suitable for both the CEDE and City of Spokane. Prepare and present findings of the project to groups which could include travel and a requirement to prepare a final draft publication dealing with the project that may be presented at a conference.
Task 700 Deliverables
- Reports, publications and presentations in electronic format in a timely manner.
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
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.