Frequently asked questions

It is a facility launched by the Central Bank of Egypt to finance the conversion of farmland from flood irrigation to modern irrigation systems, with an allocation of 55.5 billion EGP, at zero interest to the farmer and a repayment term of up to ten years.

How it works matters: the initiative does not lend directly. It is the framework under which participating banks extend the financing. Each bank applies its usual credit procedures inside that framework and asks for the documents it ordinarily asks for. What the initiative changes is the rate and the term - not the existence of a credit assessment.

The substantive condition is that the money converts flood irrigation to a modern method - drip or sprinkler - on an identified piece of land with a stated area and location, and that the applicant holds a clear legal position on that land: registered ownership, a valid lease, or a documented usufruct.

In practice, undocumented tenure is the single most common reason a file stalls, and the remedy is administrative rather than technical. Settle that point before anything else, because on its own it can take weeks that you do not want to discover after the rest of the file is ready.

Beyond that, the details vary between banks: minimum and maximum areas, acceptable collateral, and the terms of the particular tranche. Ask the branch you intend to apply to for its written terms sheet, and do not rely on a verbal summary.

Zero interest means the farmer carries no return on the principal: you repay what you borrowed in instalments over the agreed term and the amount does not grow. The difference is compensated to the bank from the initiative's allocation, which is what makes this materially cheaper than any commercial loan.

It does not mean there is no cost at all. There are normally administrative charges to open the file, valuation or inspection fees, and the cost of collateral or insurance where required. These are set by the bank and vary between branches. Together they are small relative to the principal, but they are not zero.

Ask for a written statement of every charge before you sign, and work out the real monthly instalment including them. You are entirely entitled to ask, and any serious branch will answer it on paper.

No. And no supplier can honestly guarantee it. The credit decision belongs to the bank alone and turns on matters entirely outside our reach: your credit history, the collateral available, the branch's assessment of repayment capacity, and the bank's policy at that moment.

What we take on is the technical side of the file, and we take all of it: the system design, a bill of materials with its specifications, an itemised quotation, and pre- and post-conversion consumption based on an actual meter reading rather than an estimate. A complete technical file attracts fewer review questions and shortens the cycle. That is the limit of what a supplier can promise.

If anyone offers you a guaranteed approval, ask to see the source of that guarantee in writing. There will almost certainly not be one.

The range we quote is 25% to 40% against flood irrigation, and it is not a marketing estimate - it is the result of one fraction: application efficiency. Flood irrigation under ordinary field conditions runs at 50% to 65%; drip managed on a soil-moisture schedule reaches about 90%.

The arithmetic: if a crop needs 4,000 cubic metres per feddan inside the root zone, then at 55% efficiency you must pump about 7,273 m³, and at 90% about 4,444 m³. The difference is 39% of the original figure. With well-managed flood on laser-levelled land the difference sits near the lower end of the range.

The actual saving on your land is computed from your land's numbers: crop demand by the FAO Paper 56 method, and your current consumption metered during the baseline study. The savings calculator on this site shows the full working with each crop's coefficients.

Yes, and it is in fact the cheapest installation case and the fastest to pay back. The existing drip network stays as it is; what gets added is the measurement and control layer: a flow meter on the pump outlet, two moisture probes per irrigation zone, and a controller on the valve.

The difference that appears here is the difference between timed drip and genuinely scheduled drip - in the literature, the gap between an efficiency below 75% and one near 90%. Timed drip delivers water on time rather than on need, which explains why many converted fields never achieved the saving they were promised.

We start by inspecting the existing network: emitter discharge uniformity, operating pressure and filter condition. A partially blocked network will produce misleading data, and repairing it comes before automating it.

Because a saving percentage without a measured baseline is not a number, it is a claim. The baseline study meters your current consumption at the pump outlet before anything changes, so that the saving afterwards is a subtraction between two readings from the same meter - something the farmer can audit himself.

Two weeks specifically, because the irrigation cycle for most crops runs five to ten days, and any window shorter than two full cycles captures part of the pattern and misses the rest. The same period exposes things a walkover does not: a pump delivering below its nameplate, or continuous flow during hours when nothing should be irrigated - a leak that would otherwise have been carried straight into the new system.

The output is a written report, and it belongs to the farmer whether or not he proceeds with us.

The field controller runs locally and does not need connectivity to take an irrigation decision. The schedule and the moisture thresholds are stored in the unit itself, so if the link to the platform drops, irrigation continues on the stored rules and readings accumulate in the unit's memory until the link returns and they upload in full. What is lost is live visibility, not operation.

If the unit itself fails, the manual valves remain in place and the zone can be run by hand exactly as it was before the system. We design for this deliberately: any automation system whose failure stops irrigation is not fit for productive land.

The platform raises an alert when a device stops reporting for longer than the configured interval, so that a fault is not discovered from the crop.

There is no technical minimum: a single irrigation zone can be equipped with a meter, two probes and a controller. The real limit is economic, and it is set by comparing the cost of that equipment against the value of the water and fuel it will save in a year - figures that differ enormously between a mains-powered farm and one on a diesel pump.

In practice smaller holdings benefit most when they combine: one gateway serves several neighbouring farms and its cost is shared. Some forms of the financing initiative were designed to allow group applications, and that is a question worth putting to the bank.

The correct way to answer this for your own land is to work out your current cost per cubic metre first. The minimum then becomes a number you calculate rather than an opinion you are handed.

We do not quote a figure before the site survey, and that is a deliberate position rather than evasion. Cost is set by four things that differ from farm to farm: area, the number of irrigation zones (which sets how many controllers and probes are needed), pumping head and pump condition, and the quality of connectivity on site, which determines whether an additional gateway is required.

A general number given over the phone is either inflated to cover the worst case, or suppressed to win the meeting and then revised upwards at contract. Both harm everyone involved.

What we do commit to is the sequence: a site survey, then a two-week baseline study, then an itemised quotation with each line priced separately - comparable against any other offer, and submittable to the bank as it stands.

Irrigation does not stop. Most of the work - probes, controllers, solar panels, the gateway - is done alongside normal operation. The only item requiring a shutdown is fitting the flow meter on the pump outlet, and that is scheduled between two irrigation events and takes hours rather than days.

Total duration scales with the number of irrigation zones far more than with area. A single zone is equipped in a working day, and a multi-zone farm is phased so that each zone goes into service as it is finished rather than waiting for the whole project.

Installation is followed by a commissioning and training day in the field: setting thresholds per zone, verifying that both probes respond sensibly after the first irrigation, and training whoever will run the system daily - in Arabic, without jargon.

The field units need no mains power. Each runs from a small solar panel and a battery sized to carry it through several consecutive overcast days, because power on Egyptian farmland is not dependable and a system requiring a cable run to every valve does not get built.

For connectivity the units use LoRaWAN, which does not need internet at each device - one gateway collects transmissions from up to several kilometres across open ground. Only the gateway needs an internet connection, normally over the mobile network, and it needs either mains power or a larger panel.

Where no cellular coverage reaches at all, we site the gateway at the highest available point, or use NB-IoT for scattered outlying points, depending on what the site survey finds. This is one of the reasons the survey precedes the quotation.

Post-installation support operates at two levels. Remote: device health monitoring on the platform, alerts when a device stops reporting or a reading leaves its plausible range, and help for the operator in adjusting thresholds as the crop moves between growth stages. On site: periodic inspection and calibration visits.

Calibration is not a formality. A moisture probe loses contact with the soil after a season of swelling and shrinking, and a flow meter's reading drifts with deposits in the line. Both keep reporting a number that looks plausible and is wrong, which is worse than no number. We calibrate against a reference and record the date of every calibration.

We also insist that the operator knows how to sanity-check a reading himself: a simple check after the first irrigation exposes most installation problems. Sensor failures are rare; the common faults are a probe displaced during weeding or a cable cut by tillage equipment.

The data belongs to the farm. We operate the platform that stores it and we use it to run your service and to improve the engineering, and we do not sell it or share it with third parties. Anything used in public material is aggregated, anonymised, and only with prior written consent.

Export is available at any time: CSV for raw readings and PDF for the monthly reports. We keep the raw reading exactly as the device sent it and never overwrite it with processed values - reports are built on top of the raw record. That is what keeps any figure auditable years later, which matters particularly when a report is submitted to a bank or a regulator.

Platform access uses separate accounts with separate permissions per site, so a farm operator can be given what he needs without opening the data of other sites.