Fuel Monitoring System in Botad: Fuel Records for Cotton Trucks and Pilgrim Buses

Every fuel monitoring system starts with a measuring probe in the tank, and on a Botad cotton truck that probe is the first link in a short chain. It goes in through a hole made in the top of the diesel tank and stands upright, trimmed to the tank's depth. The deeper the diesel around it, the stronger its reading; as the truck burns fuel, the reading eases down.

Link two is the Teltonika FMB920 tracker behind the dashboard. It picks up the probe's signal along a cable if you chose Omnicomm, or over Bluetooth if you chose Mercetech or Mielta Fantom. The tracker also knows where the truck is, how fast it is moving and whether the ignition is on. Link three, the Airtel SIM, sends all of that to Trakzee Premium, the app and web screen you open.

Calibration makes the numbers trustworthy. When the sensor is fitted, the executive matches its readings with known volumes of diesel in that particular tank, so the screen can display litres rather than raw signal. If the tank is ever swapped, welded or the probe removed, calibration must be done again, otherwise the litres shown will slowly part ways with reality.

Here is how a cotton truck's day reads on your phone. A fill at a pump near Botad is a step up with the pump's location. The run out to a farm and back is a gentle slope down. The wait outside a ginning yard is flat if the engine is off and a slow slide if it idles. A sudden fall is a step down that triggers an alert. Mileage reports then total the day in litres and kilometres.

Botad became a district in 2013 and has four tehsils: Botad, Barwala, Gadhada and Ranpur. It is tucked between Ahmedabad and Bhavnagar, with Surendranagar to the north-west, Rajkot to the west and Amreli to the south, so most outbound loads change district within a couple of hours. Botad town is the market centre and a railway junction, and roads fan out from it to Gadhada, Barwala and Ranpur. Rail sidings at the junction also draw trucks that wait for wagons to be loaded.

Farm freight sets the main rhythm. The land is flat with black cotton soil, and cotton, groundnut, wheat and cumin are the crops people discuss. Cotton picking and marketing run through the cooler months, groundnut arrives in autumn and wheat in spring. Trucks then queue at ginning yards and oil units, and much of their diesel is spent standing in line rather than driving.

Industry and passengers add two more streams. Ginning and oil mills send mini-trucks with edible oil, yarn and fabric to buyers along the Ahmedabad to Bhavnagar corridor. Private buses and staff shuttles run between Botad, Gadhada and Barwala on timetables. Salangpur, in Barwala tehsil, draws large crowds to its Hanuman temple, especially on Saturdays and festival days such as Hanuman Jayanti, and Gadhada's Swaminarayan temple brings visitors throughout the year.

Summer adds water tankers serving villages and wedding bookings for buses and cabs, and the monsoon fills seasonal streams such as the Ghelo near Gadhada, closing some low crossings for a spell. All of these patterns burn fuel differently. A tank record for each vehicle shows which job, which season and which route accounts for the diesel bill.

In a Botad ginning business or travel agency, diesel concerns three desks. Trakzee Premium lets the owner create extra user logins, so the dispatch desk and the accounts desk can open the same fuel record on their own phones or computers. The owner's password stays private, and all three see identical figures.

The owner's interest is the unusual. Each morning, scanning the drop alerts and the refill list for a few minutes picks out what needs a question: a tempo traveller that lost diesel while parked at Salangpur, a fill larger than the tank can hold, a truck whose consumption rose sharply this week. Normal entries need no time at all. The phone app is enough for this check, wherever the owner happens to be.

The dispatch desk works from the live map. Before Saturday's pilgrim trips, which vehicles need diesel? Before a cotton truck heads to a far village, will it make the round trip? During the day the desk sees halts and idle time alongside fuel, and when an alert arrives, it is usually the dispatcher who calls the driver first and notes the answer.

The accounts desk works from dates and quantities. Every refill shows a time and a rise in litres, which can be ticked against pump slips each week, and monthly consumption by vehicle is filed with the fuel bills. Over a season, the yard's story and the ledger's story start to match. If an employee leaves, the owner removes that login and the history remains for the next person. A shared weekly look at the screen keeps all three desks in step.

BearTech is a Bhopal company that has worked in vehicle tracking since 2014, and it keeps no staff, agent or outlet in Botad. For your order, a BearTech executive travels from Bhopal to wherever the vehicles are kept, whether a ginning yard, an oil mill compound, a bus depot or a travel agent's parking area. The client pays for that travel and stay, and the amount is told to you before you commit.

Choose the day with your own calendar in mind. Avoid Saturdays for tempo travellers and the peak cotton weeks for trucks; a weekday after the rush works well. Park every vehicle with the top of its tank reachable and the filler area wiped clean. Have the registration papers and the tank photos you sent at hand, and keep one person on site who knows the routes and who should get alerts.

For each vehicle, the executive inspects the tank, decides the probe length, drills the opening, cuts the probe to the tank's depth, and fixes and seals it. Then the FMB920 is wired in and paired with the sensor, and calibration is completed on the spot. Finally the vehicle is entered in Trakzee Premium, and you are shown the live level and a test alert on your phone.

Delivery of the package takes about 2 working days, stock permitting. Full payment falls due at fitting, and a token-amount COD route exists for orders outside Bhopal. As there are no returns, refunds or exchanges, confirm every tank detail first. If your vehicles are spread across tehsils, gathering them in Botad town for the day saves time.

Imagine a sudden-drop alert at night from a cotton truck parked outside a ginning yard, waiting to unload in the morning. All it tells you is that the level fell faster than normal running would explain. Treat it as a question with several possible answers, most of them ordinary, and approach it in a fixed order.

Begin on the map. Note the time and place, and whether the truck stood still. Yard approaches are often rutted, so a truck may have been parked at an angle, and a tilted tank gives a lower reading that recovers once it moves. Then view the graph for the whole day. A dip that bounces back is tilt or slosh; a step down that persists while the truck stands level is the case to follow up. Write down the exact minute the alert arrived.

Check for any coverage gap around the alert, since delayed data can make a slow change look abrupt. Then speak to the driver politely, while the night is fresh in memory, and listen to the explanation. Set it against the last pump slip and the place of the last refill on the record before drawing any conclusion.

Close the loop in a register: date, truck, place, explanation and outcome. Over a season the register shows whether alerts gather at one yard, one truck or one driver, which is worth far more than any single night. Keep the system's limits clear. It records and warns; it cannot lock a tank or stop anyone. Locking caps and clear rules for overnight parking remain your own measures.