Fuel Monitoring System in Kabirdham: Watching Diesel on Paddy Runs and Maikal Ghats

The paddy pickup. After the kharif harvest, a pickup carries sacks from a village near Pandariya to a rice mill on the edge of Kawardha. It waits at the weighbridge, unloads and heads back for another load. The fuel graph shows a refill in the morning, gentle slopes on each leg and flat stretches in the queue if the engine was switched off. When the owner compares three such pickups across a week, the one using noticeably more diesel per trip stands out at once, and the reason, whether a detour, idling in the queue or a tired engine, can then be checked.

The cane tractor. In the crushing months a tractor hauls two trolleys of cane down field roads to the crushing unit and waits its turn. Kilometres say almost nothing about its diesel. The record pairs litres used between refills with engine-on hours from the tracker, which tells the owner how hard each tractor is really working. Tractor tanks differ widely, so the tank photo comes first.

The ghat truck. A loaded truck leaves Kawardha for the Mandla side, climbing through the Maikal hills beyond Bodla. The slope of the fuel line steepens on the climb and eases on the descent. Signal may drop on the hill stretch; the readings arrive later and the graph fills in. A refill on the far side shows its time and place for matching with the slip.

The school bus. A diesel bus gathers children from scattered villages and brings them into Kawardha each morning. The route is fixed, so weekly diesel should change little. When it climbs for a few weeks in a row, the workshop is the first stop: tyres, filters, injectors. The school office also gets a clean fuel figure per route for its accounts.

A rice mill or transport business in Kabirdham usually has three people interested in diesel. The owner wants to know whether money is leaking, the munshi or dispatcher wants to know where the vehicles are and whether trips run to plan, and the accountant wants figures that match the bills. Trakzee Premium lets the owner create extra logins for each of them, so nobody borrows the owner's password and everyone reads the same dated record.

The owner's habit is a short morning scan. Sudden drops, refills and consumption per vehicle sit on one screen. Anything ordinary is ignored; anything strange, such as a refill bigger than the tank or a fall during a night halt at a dhaba, gets a call. Ten minutes over tea is usually enough to know whether the day needs any action. The rest can wait for the weekly summary.

The munshi reads movement and fuel together. During harvest, when pickups queue at the mill weighbridge, the stoppage report shows how long each waited and the fuel line shows whether engines idled through it. That helps plan loading times so fewer vehicles sit burning diesel. For a school bus, the same view gives diesel per route per week.

The accountant works from the refill log. Each refill has a date, time, place and a rise in litres, so pump slips can be checked one by one at the end of the week. Monthly mileage per vehicle goes in the same file. When all three read from one source, monthly settlements are calmer, and the owner still decides who can see which vehicles and reports.

When a sudden-drop alert arrives, read it as a request to check, not as a finding. Say it comes at night from a truck halted on the road beyond Bodla. Open the map first. Where exactly is the truck, and is the ground level? A vehicle stopped on a hill bend leans, and the diesel inside leans with it, which alone can make the reading jump.

Look next at the graph on both sides of the alert. If the level dipped and recovered, a tilt or a bump is likely. If it stepped down and stayed down while the ignition was off, it is worth asking about. Call the driver in a calm voice. A loose fuel pipe, a tank opened for repair, or diesel lent to a stuck vehicle are all possible and ordinary explanations.

Then compare. Put the last pump slip beside the rise recorded at that refill, and look at the trip history for stops earlier in the day. On the hill stretch, data can arrive late, so check the time of the event, not only the time the alert reached you. Keep a screenshot of the graph so everyone discusses the same facts. A late alert is still useful; it simply needs reading with care.

Finish by recording the outcome: vehicle, date, explanation and action. Over a few weeks, the notes show whether alerts gather around one vehicle, one driver or one halt. Remember what the system is: a recorder with an alarm, not a lock. It cannot stop anyone at the tank, so caps, locks and yard rules stay part of the plan, and the record simply tells you where to look.

Per vehicle, the first-year price is ₹19,999 with GST extra. It buys the cab tracker, the sensor you choose, fitting and calibration, the Trakzee Premium login, the Airtel SIM and a year of warranty with AMC. The choice between Omnicomm, Mercetech and Mielta Fantom leaves that figure unchanged. Renewal from year two is ₹3,000 per vehicle per year, giving ₹22,999 over two years and ₹25,999 over three for a single vehicle; the 2-year and 3-year plans are priced at exactly those amounts.

Take a rice mill in Kabirdham running eight vehicles: five paddy pickups, two trucks and one staff bus. The first year comes to 8 × ₹19,999 = ₹1,59,992. Renewal for eight is 8 × ₹3,000 = ₹24,000 a year. So the running total is ₹1,83,992 at the end of year two and ₹2,07,992 at the end of year three.

One more cost belongs in the plan: the executive's travel and stay for fitting in Kabirdham, paid by the client and told to you before you order. Fitting all eight vehicles in one visit keeps it to a single journey. Any vehicle needing a second tank or sensor is priced on request. Ask for it in writing with the order total.

None of this is a promise of savings. Whether the spend comes back depends on what the records show over a season: perhaps long idling at the weighbridge, perhaps refills that never matched their slips, perhaps a fleet already run with care. Only your own bills can answer that. Payment is due in full at fitting or through token-amount COD for orders outside Bhopal, and there are no returns, so check the numbers with us on 97526 44035.

BearTech has no office or team in Kabirdham. It works from Bhopal, in vehicle tracking since 2014, and for a Kabirdham order an executive travels from Bhopal to wherever the vehicle stands, whether a mill yard in Kawardha, a school in Pandariya or a farm near Sahaspur Lohara. The client pays travel and stay, and BearTech states that amount before you order.

The package itself reaches you in about 2 working days, stock permitting. The visit is then booked for a day when the vehicles are free, which in harvest or crushing season may mean early morning or a Sunday. In the monsoon, the hill roads slow down, so allowing a little extra time is wise. Avoid the days just after rain if your yard turns muddy.

Have ready the vehicle, standing on level ground with its tank reachable and clean enough to work on; a photo of the tank opening, sent beforehand; the registration papers; and a person on site who knows where the vehicle runs and who should get the alerts. Several vehicles in one visit save on travel, so mention them all when you book.

On the day the executive checks the tank, sets the probe length, cuts the opening, trims the probe and seals it in. The FMB920 goes into the vehicle's wiring and pairs with the sensor by cable or Bluetooth. Calibration ties the readings to litres. The vehicle is added to Trakzee Premium and the login is handed over and tested on your own phone. Payment is collected in full at fitting, or token-amount COD outside Bhopal.