Sensors
Observe voltage, current, flow, level, temperature, humidity and other physical conditions.
SUSTAINABLE OASIS LIVING LAB
Automation Lab
The Automation Lab connects physical Oasis systems to digital intelligence.
Sensors observe. Data records. Logic evaluates. Controllers act. Measurements then verify whether the intended result actually occurred.
SENSE
RECORD
UNDERSTAND
DECIDE
CONTROL
VERIFY
AUTOMATION LAB PRINCIPLE
Do not automate what we do not understand.
Sustainable Oasis automation begins with observable physical systems.
Before a controller is allowed to make decisions, the sensors and measurements feeding that decision should first be tested, compared and understood.
LAB ARCHITECTURE
Six layers create a useful automation system.
Data Logging
Preserve measurements with timestamps, source and data classification.
Logic
Compare measurements with defined operating rules and thresholds.
Controls
Operate pumps, valves, relays, ventilation and other approved devices.
Alerts
Surface abnormal or important conditions before they become larger problems.
Human Override
Preserve a clear human path for understanding and controlling important systems.
SENSOR LAYER
Physical systems become visible through measurement.
The Automation Lab can eventually combine sensor data from every major Sustainable Oasis system.
Electrical Sensors
Voltage, current, power, energy, battery state and other verified electrical measurements.
SO-EMS →Water Sensors
Tank level, flow rate, pressure, pump state and appropriate water-quality indicators.
Water Lab →Environmental Sensors
Temperature, humidity and other conditions relevant to shelter or controlled growing.
Growing Sensors
Irrigation state, environmental conditions and other variables that help document growing performance.
Food Lab →AUTOMATION TELEMETRY
Planned sensors remain clearly marked as planned.
The Automation Lab does not display invented sensor readings. Values remain blank until a physical sensor or verified source is connected.
SENSOR NETWORK
Current Lab Status
NOT CONNECTED
Sensor values will become MEASURED only after physical instrumentation is installed and its readings are validated.
AUTOMATION DATA PIPELINE
Every automated decision begins with information.
SENSOR
CONTROLLER
DATA LOGGER
CONTROL ROOM
DECISION
ACTION
SENSOR DATA RECORD
A number without context is not enough.
Sensor ID
Identify exactly which physical sensor produced the measurement.
Timestamp
Preserve when the measurement occurred.
Value
Store the measured value without separating it from its unit.
Unit
Record litres, volts, amps, degrees, percentage or the correct physical unit.
Source
Preserve whether data came from a sensor, manual entry, import or calculation.
Data Type
Keep DEMO, ESTIMATED and MEASURED classifications visible.
SENSOR VALIDATION
Test the sensor before trusting the automation.
Reference Test
Compare the sensor with a suitable independent reference measurement.
Repeatability
Repeat measurements under unchanged conditions.
Operating Range
Test the sensor across the range expected in the real system.
Failure Detection
Determine how disconnected, frozen or obviously unreasonable readings will be recognized.
Field Validation
Confirm that laboratory performance continues under real installation conditions.
CONTROL LOGIC
Start with rules people can explain.
Early Sustainable Oasis automation should favor simple, transparent logic over unnecessary complexity.
Read Measurement
Receive a validated sensor value or measured system state.
Compare Threshold
Compare the measurement with a documented operating threshold.
Choose Action
Select the predefined action associated with the measured condition.
Execute
Send an approved command to the relevant physical controller or actuator.
Confirm Result
Use a physical measurement to confirm that the desired state actually changed.
EXAMPLE CONTROL LOOP
Water tank protection.
A tank-level sensor provides a simple example of a useful closed control loop.
If water falls below a defined safe level, the controller can stop a pump. A later measurement confirms whether the pump actually stopped and whether the water level remains within the expected state.
EXAMPLE LOGIC
Pump Protection
EXAMPLE
ACTUATOR LAYER
Digital decisions eventually affect physical equipment.
Pumps
Move water according to level, flow, irrigation or process requirements.
Valves
Route or isolate water pathways using defined operating rules.
Electrical Switching
Control approved electrical loads through appropriate switching hardware.
Ventilation
Control fans or ventilation based on environmental conditions.
CLOSED-LOOP CONTROL
A command is not proof of an outcome.
MEASURE
DECIDE
ACT
MEASURE AGAIN
CONFIRM
HUMAN CONTROL
Automation should assist people, not hide the system from them.
Important infrastructure should remain understandable enough that an operator can identify what the automation is doing and why.
Where practical, critical equipment should retain a safe manual control path.
FAIL-SAFE DESIGN
Define what happens when something stops working.
Sensor Failure
Do not continue important automatic actions using obviously invalid or missing sensor data.
Network Failure
Essential local control should not depend entirely on an internet connection.
Power Failure
Define the physical state of valves, relays and other actuators if controller power disappears.
Controller Failure
Critical systems should move toward a known safe state instead of remaining unpredictably energized.
Emergency Stop
Provide direct shutdown capability where the physical system requires it.
ENERGY AUTOMATION
SO-EMS provides the measurement foundation.
Energy automation can eventually respond to measured generation, storage, consumption and recovery.
M01 measures, M02 routes and M03 characterizes storage. The Automation Lab can later provide the rules and controls that coordinate those modules.
ENERGY CONTEXT
Current Control Room
—
WATER AUTOMATION
Level, flow and demand can guide water movement.
Water automation can eventually protect pumps, manage storage and coordinate irrigation or recovery systems.
The first objective is not complexity. It is dependable operation with visible measurement.
Water System
WATER CONTEXT
Current Control Room
—
FOOD AUTOMATION
Automation should support growing, not replace observation.
Irrigation
Use measured conditions and defined schedules to guide water delivery.
Environment
Observe temperature and humidity where controlled growing makes those measurements useful.
Lighting
Coordinate artificial lighting where required while accounting for energy consumption.
Production Record
Connect automation history with harvest and water-use results.
SHELTER AUTOMATION
Understand the building before controlling it.
Thermal Conditions
Observe indoor and outdoor temperature to understand actual building behaviour.
Moisture Conditions
Monitor humidity where moisture management affects comfort, materials or growing systems.
Ventilation
Operate fans or ventilation based on defined and verified conditions.
Building Demand
Connect heating, cooling and ventilation decisions with measured energy consumption.
Shelter System →ALERT LAYER
Some conditions should ask for attention before taking action.
Not every abnormal measurement should immediately trigger automation. Some situations are better handled by an alert and human review.
Information
Record meaningful changes that do not require intervention.
Warning
Surface conditions approaching a defined operating limit.
Action Required
Identify conditions that require operator attention.
Protective Action
Use automatic protective action only where the rule, measurement and safe response are clearly defined.
AUTOMATION → CONTROL ROOM
The Control Room becomes the shared operating view.
Sustainable Oasis Online already accepts DEMO, ESTIMATED, manual and calculated values.
The Automation Lab creates the future pathway for verified sensor measurements, system states and control events to enter the same digital architecture.
EXISTING SYSTEM DATA
Control Room Snapshot
CURRENT MODEL
These values are existing Control Room data and are not necessarily live automation telemetry. Their DEMO, ESTIMATED or MEASURED classification remains authoritative.
AUTOMATION EXPERIMENTS
Reliability itself becomes something we can measure.
Tank-Level Monitoring
Compare practical water-level sensing approaches for accuracy, reliability and installation complexity.
PLANNEDSmart Pump Protection
Test whether level and flow measurements can reliably protect pumps from inappropriate operating conditions.
PLANNEDSensor-to-Control-Room Pipeline
Replace selected manually entered metrics with verified sensor data while retaining source and data type.
PLANNEDFIRST AUTOMATION BENCH TEST
A01 — Sensor → Rule → Relay → Verification
The first Automation Lab bench can use a low-risk sensor input, a simple rule and a low-voltage switched output.
The objective is to prove the complete control chain, including confirmation that the physical state changed after the command.
A01
Closed-Loop Bench
PLANNED
A01 PROCEDURE
Prove the loop in simple steps.
Select Input
Choose one low-risk sensor variable for the bench test.
Validate Sensor
Compare the sensor with an appropriate reference.
Define Threshold
Establish the condition that should trigger an action.
Define Safe State
Determine what the output should do when control or measurement is lost.
Trigger Rule
Change the measured condition until the threshold is crossed.
Execute Action
Send the defined low-voltage control command.
Verify Physically
Confirm the actuator or load actually entered the intended state.
Record Event
Preserve sensor reading, threshold, action and verification result.
Test Failure
Disconnect or invalidate the sensor and confirm the safe behaviour.
Repeat
Repeat the full sequence before moving to larger physical equipment.
AUTOMATION DEVELOPMENT PATH
Manual first. Autonomous only when earned.
MANUAL
MEASURED
MONITORED
ASSISTED
AUTOMATED
Manual
Operate the physical system manually and understand its behaviour.
Instrumented
Add sensors and validate their measurements.
Monitoring
Log system state and generate alerts without automatic control.
Assisted Control
Allow software to recommend or initiate limited, explainable actions.
Automation
Automate proven functions with logging, verification and manual override.
AUTOMATION DESIGN PRINCIPLES
Intelligent infrastructure should remain understandable.
Observable
People should be able to see what the system believes is happening.
Explainable
Important actions should have an understandable reason.
Fail-Safe
Predictable failure behaviour should be designed before deployment.
Overrideable
Critical functions should preserve appropriate human control.
Testable
Control logic should be structured so individual rules can be tested independently.
Logged
Important state changes should leave a record.
AUTOMATION + COMPLETE OASIS
One digital layer can eventually coordinate many systems.
ENERGY
WATER
FOOD
SHELTER
AUTOMATION
CONTROL ROOM
The goal is not to automate everything. The goal is to use measurement and control where they improve reliability, efficiency, resilience or understanding.
Experiments
Define and document automation experiments.
Experiment Registry →Field Tests
Validate sensor and control reliability under real installation conditions.
Field Tests →Results
Document accuracy, reliability, failures and useful outcomes.
Research Results →Methodology
Apply consistent instrumentation and validation standards.
Methodology →AUTOMATION LAB