Project Grade 7 Engineering & Design

Varnholt Flats Brackish Wells: Designing an RO Pretreatment

A four-session grade 7 project where teams order and justify the treatment steps ahead of a fictional brackish-well membrane plant, then defend the train to the board.

Objectives

  1. Students will match each raw-water problem to a treatment step that addresses it.
  2. Students will order treatment steps into a train and justify the order.
  3. Students will score two competing trains against stated criteria and recommend one.
  4. Students will name the first measurements an operator should take at start-up.

Vocabulary

Key words: brackish, membrane, fouling, pretreatment, recovery, cartridge filter, greensand

Teacher overview

A fictional desert town has drilled three salty wells and bought a reverse osmosis skid, and the membranes keep plugging within months. Teams design the treatment that goes in front of the membranes, choosing from a set of unit-process cards, ordering them, and defending the order against a raw-water report. Over four sessions each team builds a process flow diagram, scores it against a rival train, and presents to a fictional water board. The misconception to confront in the first session is that a membrane is a filter that catches everything, so nothing needs to happen upstream. Students who hold it will put the skid first and add steps behind it. Show the raw-water report early and ask what happens to iron and silt that arrive at a membrane surface with nowhere to go.

Rubric

Criterion 4, exceeds 3, meets 2, approaching 1, beginning
Problems matched to steps Every raw-water problem is matched to all cards that address it, and the gaps are named All four problems are matched to at least one workable step Two or three problems are matched and one is left uncovered Steps are listed without reference to the raw-water report
Order of the train Every placement is justified, including why grit removal precedes the membranes and why nothing is placed after them that belongs before The order is workable and most placements carry a reason The order is mostly workable but reasons are missing or generic Steps appear in an order that would not function
Constraints respected The chosen train meets all five limits and the memo names which limit is closest to breaking The chosen train meets all five limits The train breaks one limit and the team does not notice Cost or the storage-room limit is ignored
Scored comparison Four or more criteria are scored with totals shown, and the recommendation follows the totals with a stated decisive limit Four criteria are scored and the recommendation follows the table Criteria are listed but scoring is partial One train is named with no comparison
Diagram and start-up plan The diagram is complete and readable, and all three start-up measurements name a location and a frequency The diagram shows every step in order and three measurements are named The diagram is missing labels or only one measurement is named No usable diagram or test plan

Differentiation

Support

Give these teams the problem-to-card matching chart already completed so they begin at ordering. Provide the unit-process cards as physical strips that can be laid out and rearranged on a desk before anything is drawn. Reduce the memo to a fill-in form with four headings, and let the start-up plan be answered orally while a partner writes.

Extension

Ask these teams to design a third train under the assumption that the board finds money for a locked chemical room, then argue whether that money would be better spent on pretreatment or on a spare membrane set. Have them mark on their diagram the one step whose failure would shut the plant down fastest and propose a way to detect that failure early.

ELL supports

Pre-teach membrane, scale, and fouling with a labeled sketch of a membrane surface before and after a month of use. Provide the frames "This step goes before ____ because ____" and "We must measure ____ at ____." Allow the process flow diagram to carry picture labels alongside words, and permit the memo in bullet form.

Extensions

Have teams write a short maintenance calendar for the fictional plant, listing what the operator does daily, weekly, and yearly for each step in their train, and then check that calendar against the four-hour-a-day staffing limit. Teams often find that a train that passed on cost fails on labor once the calendar is written out, which is a useful lesson about limits that only appear when a design is made concrete.