Garage Lab
Prototype environment for energy, water, food, automation and integrated-system testing.
DEVELOPMENT SITE View Case Study →SUSTAINABLE OASIS KNOWLEDGE
Case Studies
Case studies document what happens when Sustainable Oasis systems leave the drawing board and operate in the real world.
They preserve the design, conditions, measurements, problems, modifications and lessons that transform a project into reusable knowledge.
CONTEXT
DESIGN
BUILD
MEASURE
IMPROVE
REPLICATE
CASE STUDY PRINCIPLE
Show the full story — including what did not work.
Sustainable Oasis case studies are not intended to be promotional summaries.
They should preserve the starting conditions, original assumptions, real measurements, design changes, failures and limitations that shaped the final system.
CASE STUDY LIBRARY
Real projects become long-term learning platforms.
Container Workshop
Compact infrastructure for practical construction, system integration and repeatable modular design.
DEVELOPMENT View Case Study →Vietnam Oasis
Field site connecting elevation, water, growing, distributed infrastructure and gravity-based systems.
FIELD SITE View Case Study →Mobile Oasis
Future deployable infrastructure intended to combine mobility, resilience and modular systems.
CONCEPT View Case Study →Complete Oasis
Future integrated site combining validated energy, water, food, shelter and automation systems.
FUTURE View Case Study →CASE STUDY STANDARD
Every project should answer the same core questions.
Context
Where is the project and what problem is it trying to solve?
Starting Conditions
What infrastructure, constraints and resources existed before the work began?
Design
What system architecture was selected and why?
Build
What was actually installed or constructed?
Measurements
What physical performance data was recorded?
Problems
What failed, underperformed or became difficult to maintain?
Changes
What modifications were made after observing real performance?
Lessons
What can future projects reuse or avoid?
Replication Status
Which parts are still experimental and which are ready for another build?
CS-001 · GARAGE LAB
Montreal prototype environment.
The Garage Lab functions as an accessible development site where Sustainable Oasis systems can be assembled, observed and modified before larger deployment.
Its value is not only the equipment inside it. The site creates a place where energy, water, food and automation experiments can interact physically.
CS-001
Garage Lab
DEVELOPMENT SITE
GARAGE LAB LEARNING MODEL
Prototype small enough to change quickly.
Accessibility Matters
Components that cannot be easily inspected, measured or serviced make experimentation slower.
Measure Before Scaling
Small bench systems allow instrumentation and comparison before purchasing larger equipment.
Integration Reveals Problems
A subsystem that works alone may behave differently when connected to pumps, storage, automation or other infrastructure.
CS-002 · CONTAINER WORKSHOP
Modular infrastructure as a repeatable platform.
The Container Workshop explores how compact structures can contain practical workshop, utility and demonstration systems.
Containers create a useful test for repeatable dimensions, transportability, utility routing, access and modular deployment.
Container Workshop Project
CS-002
Modular Infrastructure
DEVELOPMENT
CONTAINER CASE STUDY QUESTIONS
What makes compact infrastructure truly reusable?
Service Access
Can critical equipment be inspected or replaced without dismantling the entire structure?
Space Efficiency
Which layouts create the best balance between usable space and accessible infrastructure?
Utility Routing
How should energy, water and data pathways be separated and maintained?
Replication
Which construction decisions can become repeatable details in future modular blueprints?
CS-003 · VIETNAM OASIS
Terrain becomes part of the infrastructure.
The Vietnam field site provides the opportunity to test how elevation, water supply, storage and growing zones interact across a real landscape.
Gravity creates an especially important research opportunity because elevated water can support downstream distribution without continuous pumping.
CS-003
Vietnam Field Site
FIELD SITE
TERRAIN-BASED WATER LOGIC
Pump once. Use elevation many times.
WELL
PUMP
HIGH STORAGE
GRAVITY DISTRIBUTION
GARDEN / USE
The value of the architecture depends on measured pumping energy, available head, flow, water demand, storage losses and real field performance.
VIETNAM RESEARCH QUESTIONS
The site can answer questions a bench cannot.
Pumping Energy
How much electrical energy is required to raise useful water to elevated storage?
Gravity Distribution
How much useful flow can the terrain deliver without continuous pumping?
Productive Water Use
How much food can the site produce per litre of new water added?
Micro-Hydro Opportunity
Where water must already descend, can useful energy be recovered without undermining the primary water function?
CS-004 · MOBILE OASIS
A future case study in deployable resilience.
The Mobile Oasis remains a concept until a physical prototype is built and measured.
Its case-study framework is already useful because it defines what a future prototype would need to prove.
Movement
Measure energy required for propulsion and terrain movement.
Deployment
Measure how quickly and reliably the unit can transition from transport to operating infrastructure.
Autonomous Systems
Test energy, water, communications and shelter functions as one mobile platform.
Maintainability
Evaluate whether critical components remain accessible in a compact mobile design.
CS-005 · COMPLETE OASIS
The future integration case study.
A Complete Oasis becomes more than five independent systems installed on the same property.
The real research question is how energy, water, food, shelter and automation interact as one operating system.
ENERGY
WATER
FOOD
SHELTER
AUTOMATION
COMPLETE OASIS
COMPLETE OASIS EVIDENCE
One case study can connect the whole system.
Energy Balance
Generated, consumed, stored and recovered energy.
Water Balance
Collected, stored, consumed, filtered and reused water.
Food Production
Harvest, area, water use and infrastructure demand.
Operating Cost
Track the resources and expenses required to keep the site working.
Waste & Recovery
Track where material or energy is lost and where useful recovery occurs.
Reliability
Record failures, maintenance, downtime and system stability.
EVIDENCE DISCIPLINE
Keep what we know separate from what we think.
Measured
Instrumented values tied to a documented source.
MEASUREDCalculated
Values mathematically derived from documented inputs.
CALCULATEDEstimated
Planning values based on assumptions or incomplete measurement.
ESTIMATEDObserved
Qualitative field information that may create a new research question.
OBSERVEDCASE STUDIES INCLUDE FAILURE
A failed version may be one of the most valuable versions.
Case studies should preserve systems that leaked, consumed too much energy, produced too little food, failed to communicate, were difficult to maintain or simply did not perform as expected.
Those failures can become the reason a future blueprint works better.
VERSION HISTORY
Show how the project evolved.
V1 BUILD
TEST
PROBLEM
V2 CHANGE
RETEST
V3
A case study should make design evolution visible so a future builder understands why the final version looks different from the first.
CASE STUDY + CONTROL ROOM
A project story becomes stronger when its data can be traced.
The Control Room can organize energy, water, food and recovery data while a case study preserves the physical context surrounding those values.
Together, they explain both what changed numerically and what was happening physically.
Control Room
CASE STUDY DATA
System Evidence
TRACEABLE
CASE STUDY → BLUEPRINT
Real projects refine repeatable designs.
FIELD NOTES
CASE STUDY
LESSONS
GUIDE
BLUEPRINT
NEXT BUILD
BEFORE REPLICATION
Ask what belongs to the system and what belonged only to the site.
Climate
Would the design behave differently in another climate?
Terrain
Does the system depend on elevation, orientation or physical geography?
Resources
Which local water, energy or material resources made the original project possible?
Scale
Does the design behave similarly when made larger or smaller?
Regulation
Are there local building, electrical, water or safety requirements that change the implementation?
Maintenance
Can another site realistically maintain the same system?
CASE STUDY TEMPLATE
One structure for every future Oasis project.
A standardized template allows the Garage Lab, Vietnam site, containers and future Oasis properties to be compared more easily.
The exact measurements will differ, but the documentation logic remains consistent.
CS-XXX
Standard Case Study
TEMPLATE
Field Notes
Capture individual observations that later become part of a larger project story.
Field Notes →Guides
Convert useful lessons into practical procedures.
Guides →Blueprints
Apply field lessons to repeatable infrastructure.
Blueprints →Resources
Connect project experience with supporting technical references.
Resources →SUSTAINABLE OASIS CASE STUDIES