Note ID
Give each observation a permanent reference.
SUSTAINABLE OASIS KNOWLEDGE
Field Notes
Field Notes preserve what we notice while building, testing and operating Sustainable Oasis systems.
They capture conditions, unexpected behavior, maintenance lessons, failures, improvements and new questions before those observations disappear.
OBSERVE
RECORD
QUESTION
TEST
LEARN
IMPROVE
FIELD NOTE PRINCIPLE
Record the observation before explaining it.
Field notes should preserve what was actually seen, measured or experienced before assigning a cause.
A useful note can later become an experiment, maintenance improvement, guide, case study or blueprint revision.
FIELD NOTE STANDARD
Every note should preserve enough context to remain useful later.
Date & Time
Record when the observation occurred.
Location
Identify the site, lab, project or system involved.
Conditions
Record environmental or operating conditions that may matter.
Observation
Describe what happened without adding unsupported explanation.
Measurements
Attach relevant readings when physical data exists.
Interpretation
Record possible explanations separately from the raw observation.
Next Test
Define what should be checked, changed or measured next.
FIELD NOTE TYPES
Different observations create different kinds of value.
Observation
Something changed, behaved unexpectedly or deserves attention.
Failure
A component, procedure or assumption did not perform as expected.
Improvement
A modification improved reliability, simplicity, performance or maintainability.
Maintenance
A recurring issue or service requirement should be documented.
New Question
A field observation creates a new experiment worth testing.
Measurement Note
An interesting measurement deserves preservation before deeper analysis.
FIELD NOTE PIPELINE
A small observation can become system knowledge.
FIELD NOTE
QUESTION
EXPERIMENT
RESULT
GUIDE
BLUEPRINT
ENERGY FIELD NOTES
Record what the energy system actually does.
Meter Baseline
Record differences between SO-EMS measurements and a trusted reference during known-load tests.
TO DOCUMENT M01 Energy Meter →Battery Runtime Difference
Record differences between modeled battery runtime and measured runtime under a defined load.
TO DOCUMENT Battery Runtime →Recovery Path Observation
Record measured recovered energy separately from primary generation during recovery experiments.
TO DOCUMENT Energy Lab →WATER FIELD NOTES
Water systems reveal their limitations through real flow.
Gravity Flow Observation
Record changes in flow as tank level, head or piping configuration changes.
TO DOCUMENT Water Lab →Rainwater Capture Difference
Compare modeled rainwater yield with measured tank inflow after a rainfall event.
TO DOCUMENT Rainwater Calculator →Pump Energy Observation
Record electrical energy used and actual water moved under a defined pumping condition.
TO DOCUMENT Pump Testing →FOOD FIELD NOTES
Growing systems change every day.
Irrigation Observation
Record visible crop response alongside measured water input and environmental conditions.
TO DOCUMENT Food Lab →Growing Method Observation
Preserve useful differences between soil, hydroponic or aquaponic trials before drawing conclusions.
TO DOCUMENT Food System →Harvest Record
Capture actual usable harvest and the conditions that affected the growing cycle.
TO DOCUMENT Food Calculator →AUTOMATION FIELD NOTES
Reliability problems often appear outside the bench.
Sensor Drift
Record when a field sensor begins to disagree with a trusted reference.
TO DOCUMENT Automation Lab →Missed Control Action
Record situations where a command was issued but the intended physical change did not occur.
TO DOCUMENT Automation System →Fail-Safe Event
Document how equipment behaved when power, network or sensor information was lost.
TO DOCUMENT Fail-Safe Design →FIELD NOTES BY PROJECT
Every physical site becomes a source of practical knowledge.
Garage Lab Notes
Prototype construction, system integration, measurement, maintenance and practical operating lessons.
Garage Lab →Container Workshop Notes
Modular layout, access, utility routing, water capture and infrastructure lessons.
Container Workshop →Vietnam Oasis Notes
Terrain, water, gravity distribution, pumping, agriculture and field-infrastructure observations.
Vietnam Oasis →Complete Oasis Notes
Future integrated notes connecting energy, water, food, shelter and automation.
Complete Oasis →OBSERVATION ≠ CONCLUSION
One interesting event is a reason to investigate, not a reason to overclaim.
A field note may identify something unexpected or potentially important.
The next step is to convert that observation into a testable question whenever the explanation remains uncertain.
FIELD NOTE TEMPLATE
A simple format we can use everywhere.
The same note structure can be used in the Garage Lab, container prototypes, Vietnam field site or any future Oasis.
Consistent structure makes later searching and comparison easier.
FN-XXXX
Standard Field Note
TEMPLATE
Recommended fields: note ID, timestamp, site, system, conditions, observation, measurements, interpretation, photo or diagram reference, action taken and next test.
EVIDENCE LEVEL
A field note should identify what kind of evidence exists.
Observed
A qualitative observation without a supporting instrument reading.
OBSERVEDEstimated
A planning or approximate value based on assumptions.
ESTIMATEDMeasured
A value recorded using identified instrumentation.
MEASUREDRepeated
A similar observation or measurement occurred across multiple documented runs or conditions.
REPEATEDFAILURE IS DATA
Keep the failed version.
Failed tests, broken components and poor-performing configurations can explain why the next design became better.
A useful Knowledge Base should preserve those lessons instead of showing only successful outcomes.
OBSERVATION → KNOWLEDGE
Promote information only when it earns the next level.
FIELD NOTE
REPEAT / TEST
RESULT
GUIDE
CASE STUDY
BLUEPRINT
DATA + FIELD NOTES
Numbers become more useful when we know what was happening around them.
A Control Room value can show that something changed.
A field note can explain what equipment was operating, what weather occurred, what maintenance was performed or what physical condition may deserve further testing.
Control Room
FIELD CONTEXT
Data + Observation
TRACEABLE
VISUAL DOCUMENTATION
Photos and diagrams can preserve details words miss.
Before
Capture the physical system before a modification.
During
Document important wiring, piping, layout or build details before they become hidden.
After
Capture the final configuration associated with the field note.
Annotated Diagram
Record measurement points, flow direction or observed problem areas.
FUTURE DIGITAL FIELD LOG
Field Notes can eventually become structured records.
A future Sustainable Oasis field-log system can connect notes directly to projects, experiments, photos, measurements and blueprint revisions.
PHONE / TABLET
FIELD NOTE
PROJECT ID
DATA
PHOTO
KNOWLEDGE BASE
Guides
Turn repeated field lessons into practical procedures.
Guides →Blueprints
Use field experience to improve repeatable system architecture.
Blueprints →Case Studies
Combine many notes into the complete story of a project.
Case Studies →Resources
Connect observations with supporting technical references.
Resources →SUSTAINABLE OASIS FIELD NOTES