From soil science
to dependable irrigation.

Scientific principles have been observed and documented.

The team observes that the sensing element responds differently in wetter and drier samples. That relationship gives a possible scientific basis for estimating moisture near roots. A useful observation still needs a hypothesis, supporting research, and a clear account of the conditions under which it holds.

What changes

A measurable relationship is recorded; there is no irrigation product yet.

Setting

Controlled observation of soil samples · A sample and a sensing element

Evidence to inspect

Research observation. The sensing response varies with moisture in the prepared samples.
Conditions: The same sensing element and sample preparation are used for each observation; other influences are recorded.
Result: The example notebook pairs each sample condition with its observed response and states the proposed hypothesis.
Limit: Other soils, temperature effects, installation depth, and field repeatability remain untested.

Research purpose and team. The research has an identified purpose, interested users, and a place to test the principle.
Conditions: An imagined research team discusses the problem of making local irrigation decisions.
Result: The sample brief identifies the research question, possible users, available facilities, and supporting literature to investigate.
Limit: Interest in the problem does not demonstrate a usable technology or establish demand.

The next gap

Define a useful application and the assumptions that connect the observation to it.

A possible technological application and its concept have been defined.

The team proposes estimating root-zone moisture and using a local controller to request water through a valve. It identifies tomato beds, the intended soil and drip arrangement, a manual override, and the main assumptions. The arrows describe a proposed function: drawing a connection does not establish that it works.

What changes

The observation becomes a defined sensing-and-watering concept.

Setting

Concept design and feasibility studies · A proposed system, shown as a diagram

Evidence to inspect

Application and concept note. The scientific relationship has a plausible use in a defined irrigation application.
Conditions: The proposal states the intended crop, soil, supply, system interfaces, and local operation; performance remains a prediction.
Result: The example architecture identifies the sensing function, decision logic, water-delivery path, and experiments needed to test them.
Limit: A plausible design does not establish the accuracy of the estimate or the behaviour of connected hardware.

User needs and early risks. The team understands the initial use case and principal uncertainties.
Conditions: Imagined user discussions and paper studies consider power interruptions, maintenance access, cost, and measurement reliability.
Result: The sample plan names the intended user, major risks, candidate components, and a proposed experiment for the central assumption.
Limit: These are planning assumptions; neither user interest nor a cost estimate is experimental proof.

The next gap

Test the central assumption with a controlled experiment and compare the result with a prediction.

Experiments support the feasibility of the proposed concept.

A small rig compares the moisture estimate with an independent reference and checks whether it can produce the intended watering trigger. The team repeats the experiment, records its method, and examines disagreement. This tests the central function; the pump, valve, and full irrigation arrangement have not yet been validated together.

What changes

A prediction is compared with observations from a physical experiment.

Setting

Controlled laboratory experiment · A small experimental rig

Evidence to inspect

Prediction versus observation. The moisture-estimation and trigger concept is feasible under the tested laboratory conditions.
Conditions: Prepared samples, an independent reference method, repeated observations, and the same experimental setup are documented.
Result: The sample report compares the predicted response with the observed estimate and trigger, including disagreements and measurement uncertainty.
Limit: Pump behaviour, valve interfaces, line losses, outdoor exposure, and routine use remain outside this experiment.

Laboratory equipment and parts. The parts and laboratory methods required to investigate the concept have been identified.
Conditions: The example rig uses laboratory equipment and individually examined candidate parts.
Result: The sample inventory records component sources, experimental assembly needs, and early questions about making the eventual module.
Limit: Laboratory equipment is not a production process, and individually working parts are not an integrated system.

What a useful result must show. The investigation has explicit performance measures and early scaling questions.
Conditions: The example team defines what to compare and records safety, user needs, and likely interactions with other components.
Result: The sample plan connects the experiment to system requirements and the next integration study.
Limit: Selecting performance measures does not mean the complete system has met them.

The next gap

Connect the components and demonstrate that their interfaces work together in the laboratory.

Connected components or a system have been validated in the laboratory.

The probe, controller, valve, pump, filter, and short drip section are connected. The team checks signals, electrical and water interfaces, and basic failure behaviour. A commanded valve movement and delivered water must be observed separately: software requesting irrigation is not proof that irrigation occurred.

What changes

The key function becomes an integrated sensor-to-water loop.

Setting

Controlled laboratory integration bench · A connected bench assembly

Evidence to inspect

Bench integration log. The connected components perform their basic functions together in the controlled setup.
Conditions: The recorded configuration uses a short drip line, a controlled supply, specified connections, and an intentionally disconnected input.
Result: The sample log follows a soil input through the controller to the valve and separately observes water delivery and the missing-input response.
Limit: A short, supervised bench loop does not represent outdoor stresses, long-line distribution, or farmer operation.

Breadboard assembly record. The early assembly and its key making processes have been documented.
Conditions: Available parts form a laboratory breadboard; cable termination, enclosure needs, and fluid connections are examined.
Result: The sample record names part versions and assembly steps and identifies which processes need development.
Limit: A carefully assembled laboratory unit does not establish repeatable production quality.

Initial failure review. Basic system requirements and likely failure consequences have been considered.
Conditions: The example review covers disconnected sensing, unintended valve behaviour, leakage, and loss of power.
Result: The sample review records the effect of each failure and a proposed mitigation linked to a bench check.
Limit: Early fault analysis still needs validation under justified field-like conditions.

The next gap

Keep the laboratory-scale system, but test realistic interfaces and justified conditions from its intended use.

A laboratory-scale system with realistic supporting parts has been validated in a relevant test environment.

The integrated rig is tested with representative soil and selected pressure, heat, dust, and power conditions justified by the intended use. It remains laboratory scale. A relevant environment reproduces the influences that matter to the claim; moving a model outdoors, by itself, does not establish that relevance.

What changes

Realistic interfaces and selected environmental stresses replace ideal bench conditions.

Setting

Laboratory-scale rig with selected field-like conditions · A realistic laboratory-scale prototype

Evidence to inspect

Condition-versus-result record. The realistic laboratory assembly has been examined against selected influences from the intended use.
Conditions: The test plan identifies soil preparation, interfaces, supply variation, heat, dust, and interruption scenarios; it explains why each is relevant.
Result: The sample record separates the controller command from observed delivery. The pressure-drop exercise highlights a delivery limitation that needs an explicit operating limit or further work.
Limit: A response to selected stresses does not prove every expected condition or engineering-scale behaviour. An unresolved critical gap cannot be counted as a passed claim.

Assembly needs assessment. The more realistic prototype has a defined set of assembly needs.
Conditions: Representative connectors, seals, component fit, and access for making and checking the module are considered.
Result: The sample assessment records tools, process steps, inspection points, and remaining quality questions.
Limit: Initial assembly planning does not establish stable manufacturing or production yield.

Use and upkeep assumptions. The proposed use has been considered across installation, operation, maintenance, and replacement.
Conditions: The example plan lists cost drivers and servicing assumptions alongside the test programme.
Result: The sample lifecycle view includes installation effort, energy, cleaning, replacement parts, and operator support without invented cost or savings figures.
Limit: These assumptions need evidence as the prototype and service arrangements develop.

The next gap

Demonstrate a representative engineering-scale pilot, including the behaviour that appears with longer lines and a larger installation.

An engineering or pilot-scale prototype has been demonstrated in a relevant environment.

The same controller serves a monitored experimental plot with longer lines and a representative installation. The pilot examines distribution, interactions, reliability, and maintenance needs. This is an engineering demonstration under a defined test programme; the full intended installation has not yet been demonstrated in normal farm routines.

What changes

The test moves from laboratory scale to representative engineering behaviour.

Setting

Representative experimental plot under supervised operation · Engineering pilot with a longer distribution network

Evidence to inspect

Engineering pilot observations. The representative pilot can be evaluated for engineering feasibility within its stated test envelope.
Conditions: The experimental plot uses a documented layout, supervised operation, representative interfaces, and observations along the water path.
Result: The sample log links supply conditions and controller actions to delivery at near and far locations, and tracks issues needing resolution.
Limit: Supervised pilot evidence does not establish the full installation in its intended operational routine.

Prototype making process. Critical making processes have been prototyped and major production issues examined.
Conditions: The example team builds the pilot controller assembly using documented processes and identifies sources of variation.
Result: The sample record shows process trials, major issues and their resolution, and remaining tooling or quality needs.
Limit: A process demonstrated for the pilot does not yet show stable production over continued use.

System specification and transition plan. The next operational demonstration has a defined system, responsibilities, and support plan.
Conditions: The example specification records intended conditions, interfaces, operating requirements, unresolved issues, and the proposed user's role.
Result: The sample transition plan assigns installation, training, maintenance, and evidence-collection responsibilities and describes the business case assumptions.
Limit: A transition plan prepares operational work; it does not replace that demonstration or constitute an actual signed agreement.

The next gap

Demonstrate the full intended prototype with realistic installation, operator, maintenance, and recovery routines.

A full-scale system prototype has been demonstrated in an operational environment.

The installation now represents the planned system and its normal operating context. An operator follows the instructions, handles a power interruption, uses manual override, and records recovery and maintenance. The demonstration examines the complete system and its safeguards, alongside representative components and making processes.

What changes

The complete prototype is demonstrated with operational responsibilities and support tasks.

Setting

The intended farm setting with realistic operator tasks · Full intended prototype installation

Evidence to inspect

Full prototype demonstration. The integrated, full intended prototype performs its documented functions in a realistic operating routine.
Conditions: The sample programme covers normal use, a power interruption, manual override, and recovery with the intended type of operator.
Result: The example record connects operator actions, system responses, observed outcomes, and service needs to the intended use.
Limit: An operational prototype demonstration does not complete qualification of every requirement in the final design.

Representative build record. The prototype uses representative parts and demonstrated making methods.
Conditions: The sample build specifies the enclosure, interfaces, materials, assembly procedure, and inspection steps.
Result: The example record identifies configuration and component provenance and documents the demonstrated manufacturing methods.
Limit: A representative build is not proof that every future unit will meet quality requirements.

Operator and service review. Operational hazards and support responsibilities have been identified and addressed in the demonstration.
Conditions: The example review covers loss of power, leakage, service access, manual operation, and return to automatic control.
Result: The sample record pairs each identified hazard with a mitigation, observed check, training need, and responsible role.
Limit: The example is not regulatory approval, a safety certification, or a substitute for site-specific engineering review.

The next gap

Qualify the final configuration systematically against its requirements and complete the associated production and support evidence.

The completed system in its final form has been qualified through testing and demonstration.

The farm can look almost unchanged. What matters now is the final design version and a traceable qualification record connecting requirements to methods, results, and resolved exceptions. Manufacturing quality, materials, training, and maintenance documentation support that final system. A missing critical record leaves its corresponding claim unsupported.

What changes

The physical design stabilizes while requirement-by-requirement qualification becomes the focus.

Setting

Final system tested on its intended platform · Controlled final configuration

Evidence to inspect

Requirement-to-test matrix. The final system must be shown to meet its defined requirements through qualification.
Conditions: Each test must identify the final hardware and software configuration, requirement, method, conditions, and observed outcome.
Result: The illustrative matrix links completed checks to records and exposes a deliberately missing recovery-test record for the learner to find.
Limit: This deliberately incomplete sample cannot support a complete qualification claim. It illustrates what must be resolved, not an achieved certification.

Production and material checks. The final design has supporting evidence for making quality units and obtaining required materials.
Conditions: The sample manufacturing review considers assembly checks, producibility, acceptable quality outcomes, and material availability.
Result: The example dossier identifies what records would connect making processes and inspections to the controlled design.
Limit: A supplier list or attractive finished enclosure alone does not demonstrate production quality or full qualification.

Controlled support documents. Training and maintenance information corresponds to the final configuration.
Conditions: The example manuals and change record use a consistent design version and documented review status.
Result: The sample index ties installation, operator training, maintenance, and revisions to the same system configuration.
Limit: Having a manual does not establish that its instructions were effective in continued operation.

The next gap

After qualification is supported, establish performance through actual operation across the full range of expected conditions.

The actual final system has been proven in operation across the full range of expected conditions.

The final system's operating record must show what happened in actual use, including expected conditions, maintenance, failures, and their resolution. The relevant duration and coverage depend on the intended application. Readiness is bounded by that evidence: a different soil, crop, layout, or control algorithm may need fresh investigation.

What changes

Operational history establishes performance beyond qualification of the final build.

Setting

Continued use in the intended operational environment · Actual deployed system within its defined scope

Evidence to inspect

Operational history and evaluation. Actual performance supports the defined operational concept across its expected conditions.
Conditions: The record must identify the installed configuration, intended conditions, observed coverage, operating events, and evaluation method.
Result: The example history illustrates how normal operation, interruptions, maintenance, failures, and corrective actions should connect to the claimed scope.
Limit: The fictional history is not real trial data. A readiness claim cannot extend to conditions, configurations, or uses the evidence does not support.

Stable design and production. The operational system is backed by stable design and appropriate production control.
Conditions: The sample dossier links installed units to design revisions, controlled processes, inspections, and any recorded changes.
Result: The example register shows how production records and design stability can support confidence in the actual configuration.
Limit: A large sales count does not establish technical performance or justify transferring a claim to a redesigned system.

Completed support and training record. The documentation and support needed for the intended use have been carried through into operation.
Conditions: The example record connects implemented training, maintenance activity, issue closure, and the final document set.
Result: The sample history shows how operator support and documented follow-up contribute to the operational evidence.
Limit: Readiness in a defined use does not guarantee profitability, universal suitability, or performance under every imaginable condition.

The next gap

For a new use or material design change, define the new claim and identify which evidence must be repeated or extended.