Fuel Monitoring System in Mahisagar: Diesel Records Where Every Load Goes by Road

The milk van at dawn. A van leaves a collection point near Khanpur at five, stops at eight villages and reaches the dairy by eight. On the fuel graph, each village halt is a short flat step and the road between them a gentle slope. When the van's litres per round creep up over a fortnight, the owner looks at the halt list first and finds one village stop growing longer each day with the engine on. A word with the driver settles it.

The tipper on a Mahi works site. A tipper carries aggregate from a crusher to a river-bank project and waits at the site for unloading. Its diesel per trip is higher than the distance suggests, and the record shows why: forty-minute waits with the engine running. The contractor uses the figure to discuss unloading arrangements with the site engineer instead of blaming the driver.

The student bus into Lunawada. A bus collects students from villages and reaches the college before classes. Its consumption per circuit sits in a tight band through the term. One month the band shifts upwards; the mechanic finds an injector problem, and after repair the figures return to normal. The college office reads the same record to plan the next year's transport budget.

The upland tractor in Santrampur. After the kharif harvest a tractor hauls maize down to a market yard and spends some nights on remote farm tracks. One morning the graph shows a sharp fall overnight while it was parked. The owner calls the driver, who says diesel was shared with a neighbour's stranded pump set. The neighbour confirms it, and the entry is closed with a note.

Any fuel monitoring system in Mahisagar works in a district where roads carry nearly everything. Mahisagar was formed in 2013 out of Panchmahal and takes its name from the Mahi, which runs along its western side. Lunawada is the headquarters, and the six talukas are Lunawada, Balasinor, Kadana, Khanpur, Santrampur and Virpur. Panchmahal, Kheda and Dahod surround it, with Rajasthan's Banswara to the east.

Lunawada has had no rail link since the narrow-gauge line from Godhra closed in 2002, so milk, produce, building material, students and visitors all go by road. Balasinor sits on a national highway and a state highway and handles through traffic, while the roads into Santrampur and Kadana are hillier, quieter and thinner in mobile coverage. A single vehicle can see very different road quality in one day.

Milk is the daily constant. Vans run short early-morning rounds from Lunawada and Khanpur villages to the dairies, all year. Construction is the heavy end: the Kadana dam and works along the Mahi need sand, aggregate and cement, so tippers and mixers wait at sites for long periods. Upland farms in Santrampur and Kadana send maize, cotton and pulses by tractor and pickup, with kharif crops from autumn and wheat and pulses in spring.

Passenger traffic completes the picture. Student vans and buses bring young people into Lunawada's colleges and schools, and hired vehicles carry visitors to the Raiyoli fossil park near Balasinor and to the Shiva temples around Kaleshwari, especially in Shravan. Navratri, Diwali and Uttarayan bring travel rushes. In all of it, the owner rarely sees the tank, and a level record per vehicle is what shows where the diesel went.

BearTech keeps no staff in Mahisagar. The company works from Bhopal and has been in vehicle tracking since 2014, and for a Mahisagar order an executive travels from Bhopal to the place your vehicles stand: a milk route operator's yard in Lunawada, a contractor's camp near Kadana, a college transport bay or a farm in Santrampur. You pay his travel and stay, and the figure is given before you order.

The kit is delivered in about 2 working days, stock permitting, and the fitting date is fixed around your work. Milk vans are free after the morning round, student buses at weekends or in vacations, and tippers between site shifts. On the day, have the vehicle parked so the top of its tank can be reached, wipe the filler area clean, keep the registration papers and the tank photo from your enquiry at hand, and have someone present who knows the routes and who should get alerts.

The fitting itself is orderly. The executive inspects the tank, settles the probe length, makes the opening, cuts the probe to depth and seals it. The FMB920 goes onto the vehicle's power and pairs with the sensor by cable or Bluetooth. Calibration converts readings to litres, the vehicle appears in your Trakzee Premium account, and you see the live level on your own phone before he leaves. Any doubts about alerts can be cleared on the spot.

If several vehicles need fitting, bring them together for one visit so that one journey covers all. Full payment is taken at fitting, and outside Bhopal a token-amount COD booking is possible too. After fitting, the support line, 99937 84035, helps with logins and alerts.

A milk route operator in Mahisagar might run several vans, a tipper rented to a contractor and a student bus. Diesel matters to three people in that business. The owner wants to know whether fuel money is being spent as it should. The dispatcher wants to know which van can do tomorrow's round without a pump stop. The accountant wants pump bills to match the fills. Trakzee Premium lets the owner add extra user logins with separate passwords, so each reads the same data.

The owner's reading is short. In the morning, the night's falls and refills; once a week, litres per round for each van and per trip for the tipper. A van whose figure rises above its twin on a similar circuit is sent for a check of tyres, filters and injectors before anything is said to the driver. On the computer, the month's figures for every vehicle fit in one table.

The dispatcher reads levels on the live map. Before the dawn rounds he sees which vans have enough diesel and which need a pump stop first, and on site days he watches the tipper's level between loads. When an alert arrives, he checks the vehicle's position and ignition and phones the driver while the moment is fresh.

The accountant reconciles. Every refill has a date, a time and a rise in litres, so pump slips can be ticked off and any slip lacking a matching rise is easy to pick out. Monthly mileage and consumption go into the same register as the bills. With all three working from one source, disagreements over numbers become rare, and month-end takes less time.

An alert means the diesel level fell faster than driving explains. It does not say why. Suppose it arrives late one evening for a milk van parked in a village. Look first at what the screen already tells you: the van was stationary, the engine was off, and the spot was a sloping lane beside the collection point. A tilt like that can trigger an alert on its own.

Next morning, ask the driver calmly what happened. Perhaps a mechanic drained the tank to clear a blocked filter, diesel was lent to a neighbour's tractor, or the van was moved onto a slope. If the van was moved, parking it on level ground and checking again often settles the question. Then put the day's pump slip against the refill log. Many alerts close at this point with an ordinary reason and a short note.

When no ordinary reason fits, read time and place together. A fall at noon on a busy dam-side site is different from one at night on a remote upland track. Save a screenshot with the reading before and after, the place, the ignition record and how long the vehicle stood still, so that any conversation that follows rests on recorded facts.

Last, keep a register of the alerts you follow up, with date, vehicle, driver and conclusion. A month of entries shows whether falls are random or keep returning to one vehicle or one place. Tell drivers plainly what the system does: it records levels and raises alerts, but it cannot lock a tank or physically stop anyone taking diesel. Locks and yard rules are still the owner's responsibility.