SmartFuel Web Account Types

['Neal Singh]

The Master Controller is designed for two type authorizations;

1.       Local Authorizations

-          The Master Controller itself manages balances (for Account and Vehicle and possibly the Driver) that are downloaded from the Web after every update. This will be downloaded to all sites that are on the network. Should there be no connections to the Master Controller, it has the logic to manage these balances locally as well.

-          This download would include downloading the latest Odometer for each vehicle that was refuelled.

 

2.       Web Authorizations

-          The balances are managed from the Web and the Master Controller will pass the Tag number and Odometer to the Web for an approval. Should fuelling be rejected, a code is sent to the Master Controller to indicate the reason. The Fuel will be limited based on;

-          (a)  Fuel budgets for a period (weekly/monthly etc)

-          (b) Limit to min travel before fuel is allowed and min period before fuelling can be permitted. The Odometer is important for this process.

-          (c) Fuel Grade and Fuel type

-          (d) Tank Capacity

-          (e) Possibly another method: would be based on the fuel consumption, odometer reading and tank size and the system calculates that if the vehicle has done 350 km since the last fill, this system knows based on the consumption there must be at least half a tank of fuel and therefore restrict fuel according. (this feature is not a priority as present )

 

In terms of managing these authorizations, the Web will host two types of Accounts. One will be the typical Homebase type Account that manages the Fuel Litre budgets for various internal departments of the Company owning the Homebase or Homebases. In this type, the value of fuel utilized may have some significance in reporting purposes of rands used but the management  controls is in litres.

The other will be the Financial Type Account and this can be complicated and these are scenarios that would need to be considered.

Type1. The Account Proprietor (User type) being an entity that is independent of the Sites. This could be the Oil Company that has 50 sites. The User would create an Account for every Fleet company that gets onto their network of sites.

The details of these Accounts/ Vehicles will be downloaded to each of these sites so the vehicle tag is recognised on site.

The Account Proprietor will daily/weekly/monthly report of the Amount each site has dispensed. As there will be a need for payments made those Sites. (NB: In the case of the Oil Company, it is sometime offset against their next fuel purchase – but this is only if the User is an Oil Co)

Each of the Fleet Accounts will have a financial record of their payment , credits and transactions  so that fuelling always against a prepared amount.

The Fleet User can log in to see the transactions of the Fleet and their Fuel management information. So when a payment is made by the Fleet User to the Account Proprietor , the Proof of

Payment will need to be emails/Faxed once captured, the Fleet User gets an SMS to say the Account has received a payment. The Fleet User has the ability to use the VO functions etc as well.

Type2. The Account Proprietor being the site owner.  This is almost identical to Type1 but these are effectively Local accounts managed from the Web and would part of the Site Owner profile

Type3. The Cash Account would be an Account that will have Fuel Limits base on a Litre or value (Money) budget but the amount owing is settled on site so there is no accounting of the amount owing and after the limit for that period, the amount available is automatically reinstated. The main difference here between the earlier 2 types is that there is that payments are not required.  NB: The transaction will have a method of payment code that will be part of the sites reconciliation process of takings per shift.

 Type4 .This would be the Loyalty Account as previously developed.