Petrol Pump Management System

ABSTRACT

In Petrol pump management System use to maintain their sales detail, employee detail in files and folders. They use to keep the record of petrol and diesel sold, inventory, Customers, etc in a register. A daily register is maintained to keep track of sales. Preparing report is very time consuming and tedious task. For searching of single record, whole register is to be searched which is very time consuming task.

This description not a platform or language dependent we can develop a desktop or web application by the given description.We are just providing the basic idea about this project work.

Existing System

There are existing software solutions to manage employee expenses that could potentially address the issues raised in the earlier section. These existing solutions however have issues that are discussed below. Complexity Most of the existing software solutions address a broad and general issues pertaining to financials of a company. Usually such software would be big, feature rich and complex. For a small size company most of the features from such software would not be relevant. Cost The initial and the operating costs of such existing software are huge. No single software There is a need for a single web-based solution that would address the entire requirements specific and focused for the company. To address this issue, lean and focused software needed to be developed to address only the requirements specific for this company instead of using multiple software solutions.

As mentioned above most of details are maintained manually. Due to this the data retrieved is time consuming. Due to human calculation errors occur.Even when the data is maintained on spreadsheet inconsistency occurs as an order might be missed or wrongly entered or twice.Data are stride an excel sheet which takes lot of time and data may be corrupted.As storage and exchange of data is achieved only by use of excel sheets which lack validation capabilities, there is always risk of invalid, inaccurate or incomplete data being fed in computer.Difficulty in managing multiple forms.
The existing system is very slow and needs more time to search and maintain each and every detail.As calculations are done manually it is tedious difficult to major more figures accurately.Retrieval of required information is become difficult and time consuming.Security of data is very critical issue which has to consider in the current system there is no data security.Same data is maintained in various file which is leading to redundancy of data.Report generation is very tedious job. The in-charge of preparing report has to refer more than one file.

Proposed System

The proposed system is computerised and has been developed using advance language therefore it gives more facilities than present system. It provides quick access to any data. In this system user have to enter the data only once and then it get linked with all files. This reduces the workload of user and it is also a time saving process.The information about any Subscriber can be easily retrieved. The system maintains all records easy.

All the information about sale, purchase, stock will be maintain properly in this system.All manual calculation of sale or all the money management will be performed by the computer automatically.This system will provide timely report information.It will produce report for sale, bill and stock information.The computer can hold amount of data in its storage device.The operation and speed of the computer is very high.We can calculate result and print any report within a seconds.Any difficulties we can solve easily.A database application can be stored in computer effectively.It is very user friendly and easy to handle.So the computerised system is more suitable than the manual system.

System Design

In this phase we can understand about the structure of our system. I am giving here a brief idea about modules.We can find so many modules according to our requirement but here few basic modules are given with their definition. By the help of these modules we can easily understand how we design database and what type of fields we will take.It is helpful for designing our system.

Module Structure

Customer Registration
- Customer Id
  - Numeric type (Datatype)
  - Primary Key (Constraint)
- Customer Name
  - String type (Datatype)
  - Not NULL (Constraint)
- Customer Vehicle No.
  - String type (Datatype)
  - Not NULL (Constraint)
- Customer Contact No.
  - Numeric type (Datatype)
  - Not NULL (Constraint)
- Customer Registration Date
  - Datetime type (Datatype)
  - Not NULL (Constraint)
Customer Bill
- Bill Id
  - Numeric type (Datatype)
  - Primary Key (Constraint)
- Customer Id
  - Numeric type (Datatype)
  - Foreign (Constraint)
- Customer Name
  - String type (Datatype)
  - Not NULL (Constraint)
- Customer Contact No.
  - Numeric type (Datatype)
  - Not NULL (Constraint)
- Customer Vehicle No.
  - Datetime type (Datatype)
  - Not NULL (Constraint)
- Petrol Purchase Amount
  - Decimal type (Datatype)
  - Not NULL (Constraint)
- Diesel Purchase Amount
  - Decimal type (Datatype)
  - Not NULL (Constraint)
- Petrol Bill Amount
  - Decimal type (Datatype)
  - Not NULL (Constraint)
- Diesel Bill Amount
  - Decimal type (Datatype)
  - Not NULL (Constraint)
- Total Bill Amount
  - Decimal type (Datatype)
  - Not NULL (Constraint)
- Sale Date
  - Datetime type (Datatype)
  - Not NULL (Constraint)
Product Detail
- Product Id
  - Numeric type (Datatype)
  - Primary Key (Constraint)
- Product Stock
  - Decimal type (Datatype)
  - Not NULL (Constraint)
- Product Price
  - Decimal type (Datatype)
  - Not NULL (Constraint)
Inventory Detail
- Inventory Date
  - Datetime type (Datatype)
  - Not NULL (Constraint)
- Inventory Petrol
  - Decimal type (Datatype)
  - Not NULL (Constraint)
- Inventory Diesel
  - Decimal type (Datatype)
  - Not NULL (Constraint)
Sales Detail
- Bill Id
  - Numeric type (Datatype)
  - Primary Key (Constraint)
- Customer Name
  - String type (Datatype)
  - Not NULL (Constraint)
- Petrol Purchase Amount
  - Decimal type (Datatype)
  - Not NULL (Constraint)
- Diesel Purchase Amount
  - Decimal type (Datatype)
  - Not NULL (Constraint)
- Petrol Bill Amount
  - Decimal type (Datatype)
  - Not NULL (Constraint)
- Diesel Bill Amount
  - Decimal type (Datatype)
  - Not NULL (Constraint)
- Total Bill Amount
  - Decimal type (Datatype)
  - Not NULL (Constraint)
- Sale Date
  - Datetime type (Datatype)
  - Not NULL (Constraint)
Employee Details
- Employee Id
  - Numeric type (Datatype)
  - Primary Key (Constraint)
- Employee Name
  - String type (Datatype)
  - Not NULL (Constraint)
- Employee Address
  - String type (Datatype)
  - Not NULL (Constraint)
- Employee Contact
  - Numeric type (Datatype)
  - Not NULL (Constraint)
- Employee age
  - Numeric type (Datatype)
  - Not NULL (Constraint)
- Employee Gender
  - String type (Datatype)
  - Not NULL (Constraint)
- Employee Date of Joining
  - Datetime type (Datatype)
  - Not NULL (Constraint)
- Employee Designation
  - String type (Datatype)
  - Not NULL (Constraint)
- Employee Shift
  - string type (Datatype)
  - Not NULL (Constraint)
- Employee Salary
  - Numeric (Decimal) type (Datatype)
  - Not NULL (Constraint)
Employee Attendance
- Employee Id
  - Numeric type (Datatype)
  - Primary Key (Constraint)
- Employee Name
  - String type (Datatype)
  - Not NULL (Constraint)
- Status
  - String type (Datatype)
  - Not NULL (Constraint)
- Attendance Date
  - Datetime type (Datatype)
  - Not NULL (Constraint)
Employee Advance Detail
- Employee Id
  - Numeric type (Datatype)
  - Primary Key (Constraint)
- Employee Name
  - String type (Datatype)
  - Not NULL (Constraint)
- Advance Date
  - Date Time type (Datatype)
  - Not NULL (Constraint)
- Advance Amount
  - Numeric (Decimal) type (Datatype)
  - Not NULL (Constraint)
Employee Salary Report
- Employee Id
  - Numeric type (Datatype)
  - Primary Key (Constraint)
- Employee Name
  - String type (Datatype)
  - Not NULL (Constraint)
- Salary Month
  - String type (Datatype)
  - Not NULL (Constraint)
- Number of Present
  - Numeric type (Datatype)
  - Not NULL (Constraint)
- Number of Absent
  - Numeric type (Datatype)
  - Not NULL (Constraint)
- Monthly Salary
  - Numeric type (Datatype)
  - Not NULL (Constraint)
- Net Salary
  - Numeric type (Datatype)
  - Not NULL (Constraint)
Employee Login
- User Name
  - String type (Datatype)
  - Primary Key (Constraint)
- Password
  - String type (Datatype)
  - Not NULL (Constraint)
Employee Working Time Detail
- User Name
  - String type (Datatype)
  - Primary Key (Constraint)
- Login Time
  - Time type (Datatype)
  - Not NULL (Constraint)
- Logout time
  - Time type (Datatype)
  - Not NULL (Constraint)
- Working Date
  - Date type (Datatype)
  - Not NULL (Constraint)

Feature Enhancement

Being a computer system, the system has good scope to be improved further.
Future Enhancements are as listed below

Administrator can be given more rights,so that he will be able to change order details.
Type 4 driver will be used so that system will work faster.
I will develop the system on LAN to setup the connection between other petrol pump of same company.

Conclusion

System helps to store all the data about the customer order in computer and there is no need to do paper work. Data is going to be preserved carefully for longer period hence proper backup is required otherwise there is chance of losing entries or data.

References

www.hindustanpetroleum.com

Petrol Pump Management System | Projects