PETROL PUMP MANAGEMENT SYSTEM PROJECT REPORT

PETROL PUMP MANAGEMENT SYSTEM PROJECT REPORT

PROJECT REPORT

PETROL PUMP MANAGEMENT SYSTEM PROJECT REPORT

PETROL PUMP MANAGEMENT SYSTEM DATABASE

PETROL PUMP MANAGEMENT SYSTEM PROJECT REPORT

PROJECT SOURCE CODE

PETROL PUMP MANAGEMENT SYSTEM PROJECT SOURCE CODE

FREE DOWNLOAD ALL THE PROJECT REPORTS WITH SOURCE CODE FROM HERE

                  

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, inventry, 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.

Limitations Of Present System

v As mentioned above most of details are maintained manually. Due to this the data retrieved is time consuming. Due to human calculation errors occur.

v Even when the data is maintained on spreadsheet inconsistency occurs as an order might be missed or wrongly entered or twice.

v Data are stride an excel sheet which takes lot of time and data may be corrupted.

v 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.

v Difficulty in managing multiple forms.

v Lack of security.

Proposed System - PETROL PUMP MANAGEMENT SYSTEM PROJECT

             

                 The proposed system is computerized 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.

Advantages of Proposed System:

v All the information about sale, purchase, stock will be maintain properly in this system.

v All manual calculation of sale or all the money management will be performed by the computer automatically.

v This system will provide timely report information.

v It will produce report for sale, bill and stock information.

v The computer can hold amount of data in its storage device.

v The operation and speed of the computer is very high.

v We can calculate result and print any report within a seconds.

v Any difficulties we can solve easily.

v A database application can be stored in computer effectively.

v It is very user friendly and easy to handle.

So the computerized system is more suitable than the manual system.

Feasibility Of Study - PETROL PUMP MANAGEMENT SYSTEM PROJECT

1. Software Specification:-

         Software requirements for this system are as listed follows:

v FRONTEND                                :          Microsoft Visual Basic 8.0

v BACKEND                                  :          Microsoft SQL Server-2000

v OPERATING SYSTEM     :          Windows XP

        2. Hardware Specifications

Minimum hardware requirements for this System are listed below:

v Processor                            :                  Pentium-4

v RAM                                  :                  256MB.

v HARD DISK                      :                  80GB.

v NETWORK                        :                  LAN.

FRONTEND :- MICROSOFT VISUAL STUDIO 2008

1.     First of all, VB.NET provides managed code execution that runs under the Common Language Runtime (CLR), resulting in robust, stable and secure applications. All features of the .NET framework are readily available in VB.NET.

2.     VB.NET is totally object oriented. This is a major addition that VB6 and other earlier releases didn't have.

3.     The .NET framework comes with ADO.NET, which follows the disconnected paradigm, i.e. once the required records are fetched the connection no longer exists. It also retrieves the records that are expected to be accessed in the immediate future. This enhances Scalability of the application to a great extent.

4.     VB.NET uses XML to transfer data between the various layers in the DNA Architecture i.e. data are passed as simple text strings.

5.     Error handling has changed in VB.NET. A new Try-Catch-Finally block has been introduced to handle errors and exceptions as a unit, allowing appropriate action to be taken at the place the error occurred thus discouraging the use of ON ERROR GOTO statement. This again credits to the maintainability of the code.

6.     Another great feature added to VB.NET is free threading against the VB single-threaded apartment feature. In many situations developers need spawning of a new thread to run as a background process and increase the usability of the application. VB.NET allows developers to spawn threads wherever they feel like, hence giving freedom and better control on the application.

7.     Security has become more robust in VB.NET. In addition to the role-based security in VB6, VB.NET comes with a new security model, Code Access security. This security controls on what the code can access. For example you can set the security to a component such that the component cannot access the database. This type of security is important because it allows building components that can be trusted to various degrees.

8.     The CLR takes care of garbage collection i.e. the CLR releases resources as soon as an object is no more in use. This relieves the developer from thinking of ways to manage memory. CLR does this for them.

BACKEND: SQL SERVER 2000

IBM developed the original version of SQL, originally called Sequel, as part of the System R Project in the early 1970s. The Sequel language has evolved since then, and its name has changed to SQL (Structured Query Language).Many products now support the SQL language. SQL has clearly established itself as the standard relational database language.

In 1986,the American Standards Institute (ANSI) and the International Organization for Standardization (ISO) published an SQL standard, called SQL-86.ANSI published an extended standard for SQL,SQL-89,in 1989.The next version of the standard was SQL-92 standard followed by SQL:1999;the most recent versions are SQL:2003 and then SQL:2005.

          The SQL language has several parts:

v           Data-definition language (DDL): The SQL DDL provides

commands for defining relation schemas, deleting relations, and modifying relation schemas.

v Interactive data-manipulation language (DML):The SQL DML includes 

a query language based on both the relational algebra (2) and the tuple relational calculus (5).It includes also commands for specifying integrity constraints that the data stored in the database must satisfy. Updates that violate integrity constraints are disallowed.

v View definition: The SQL DDL includes commands for defining views.

v Transaction control: SQL includes commands for specifying the

beginning and ending of transactions.

v Embedded SQL and Dynamic SQL: Embedded and dynamic SQL 

define how SQL statements can be embedded within general-purpose programming languages, such as C, C++.Java, PL/I, COBOL, Pascal, and FORTRAN.

v Authorization: The SQL DDL includes commands for specifying access

rights to relations and views.

Stakeholders

Stakeholders are anyone who has an interest in the project. Project stakeholders are individuals and organizations that are actively involved in the project, or whose interests may be affected as a result of project execution or project completion. They may also exert influence over the project’s objectives and outcomes. The project management team must identify the stakeholders, determine their requirements and expectations, and, to the extent possible, manage their influence in relation to the requirements to ensure a successful project.

The following are examples of project stakeholders:

1.      Project Developers

Project Developers is one who develops software for customer. In my project I am the first stakeholder i.e. Project Developer.

2.     Project customer

Project Customer is one who pays for the developed software. In my project the Chairman of Technovision Automation Pvt. Ltd. is the second stakeholder i.e. Project Customer.

3.      Project user Group

Project User group are those people who use the software on daily basis for the Project Customer. In my project employee’s of Technovision Automation Pvt. Ltd. are the third stakeholders i.e. Project User Group

4.      Project Testers

Project Testers are those who test the software. In my project myself, my project guide and Technical Department of TAPL are the fourth stakeholders i.e. Project Testers.

System Analysis - PETROL PUMP MANAGEMENT SYSTEM PROJECT

Fact Findings

 Introduction

               The Current System is the manual one, hence is not speedy, accurate, efficient as well as time consuming. An essential part of the system analysis, which enables the developer to understand & the system correctly. It is undertaken to obtain details of the system. To understand the physical flow of the information through the current system. Collect various information through various fact finding techniques. Identify the procedural difficulties experienced by the user. Study the bottlenecks find out the redundant work being performed in the system.

        Fact Finding Techniques Employed

 1.  Interviews

           Information was obtained from the employees at the organization by interviewing them at the location and time convention both.

2. Document Searching

           An extensive study of existing document an official correspondence was done to understand the present working status of organization.

System Design - PETROL PUMP MANAGEMENT SYSTEM PROJECT

Converting ERD to Tables

Entity	TABLE NAME	PURPOSE
Customer	cust_reg.sql	This table is use to store, retrieve information about the customer. The field are cust_id ,cust_name, cust_vehno, cust_mobno, cust_date
Bill	cust_bill.sql	This table is use to store ,retrieve information about the Bill The field are bill_id, cust_id cust_name, cust_vehno, cust_mobno,petrol,deisel,p_amt,d_amt2,totalbill,cust_date
Product	pro_detail.sql	This table is use to store, retrieve information about the Product price and stock. The field are p_id, p_name  , p_stock, p_price
Sales	sales.sql	This table is use store information of sales  The field are bill_id, cust_name, petrol, deisel, p_amt, d_amt2, totalbill, cust_date
Inventory	inventryfile.sql	This table is use to store information about inventory detail The field in the table i_date , i_petrol, i_diesel,Invoiceno.,Prodid,Prodname,type,quantity,mrp,amt, Total. The field in the table are Custcode, CustName, Address,phno,InvoiceNo,Prodid,Prodname, type,quantity,mrp,amt,total.
Employee	addemployees.sql	This table is use store about the employee The field are e_id  ,e_name  ,e_add  ,e_contact bigint, e_age ,e_gender ,e_doj,e_post ,e_shift ,e_salary
Attendance	attendance.sql	This table is use to store employee attendance  The field are eid  ,ename  ,status ,adate ,
Advance	Advance.sql	This table is store the information about advance payment The field are eid   eid  ,ename ,adate ,advance
Salary	Salaryreport.sql	This table is store the information about  employee salary The field are eid   eid ,ename ,smonth ,present ,absent ,doff ,monthlys ,netsal
user	Login.sql	This table is store the information about  User of system and their password The field are eid   Username ,passwrd
user	Logtime.sql	This table is store the information about  Time when the user login to system The field are eid   Username ,logintime

Table List

Sr.No.	Field Name	Datatype	Constraints	Size	Description
1	cust_id	Integer	Primary key		Stores the customer id
2	cust_name	Varchar		20	Stores the customer name
3	cust_vehno	Varchar		20	Stores the customer vehicle number
4	Ph_no	Bigint			Stores the customer ph.no.
5	cust_date	Datetime			Stores the registration date

1.Table name:- cust_reg

   

 2.Table name:- cust_bill

Sr.No.	Field Name	Datatype	Constraints	Size	Description
1	bill_id	Integer	Primary key		Stores the bill id
2	cust_id	integer	Foreign key		Stores the customer id
3	cust_name	Varchar		20	Stores the customer name
4	cust_vehno	varchar		20	Stores the customer vehicle number
5	cust_mobno	bigint			Stores the customer ph.no.
6	petrol	real			Stores the amount of petrol purchased
7	deisel	real			Stores the amount of diesel purchased
8	p_amt	real			Store bill of petrol
9	d_amt2	real			Store bill of diesel
10	totalbill	real			Store total bill
11	cust_date	datetime			Store date of sale

      3.Table name:- pro_detail

Sr.No.	Field Name	Datatype	Constraints	Size	Description
1	p_id	Integer	Primary key		Stores the product id
2	p_stock	Real			Stores product stock
3	p_price	real			Stores product price

       4. Table name:- inventryfile

Sr.No.	Field Name	Datatype	Constraints	Size	Description
1	i_date	datetime			Stores the inventory date
2	i_petrol	real			Stores the amount of petrol invented
3	i_diesel	real			Stores the amount of diesel invented

    

      5.Table name:- sales

Sr.No.	Field Name	Datatype	Constraints	Size	Description
1	bill_id	Integer	Foreign key		Stores the bill id
2	cust_name	Varchar		15	Stores the customer name
3	petrol	real			Stores the amount of petrol purchased
4	deisel	real			Stores the amount of diesel purchased.
5	p_amt	real			Store bill of petrol
	d_amt2	real			Store bill of diesel
	totalbill	real			Store total bill
	cust_date	datetime			Store date of sale

      6 .Table name:- addemployees

Sr.No.	Field Name	Datatype	Constraints	Size	Description
1	e_id	Integer	Primary key		Stores the employee id
2	e_name	Varchar		15	Stores the employee name
3	e_add	Varchar		15	Stores the employee address
4	e_contact	Bigint			Stores the employee ph.no.
5	e_age	real			Stores the employee age
6	e_gender	varchar		20	Stores the employee gender
7	e_doj	datetime			Stores the date of joining
8	e_post	varchar		20	Stores the post of  employee
9	e_shift	varchar		20	Stores the shift employee
10	e_salary	real			Stores the maximum salary

     7 .Table name:- attendance

Sr.No.	Field Name	Datatype	Constraints	Size	Description
1	e_id	Integer	foreign key		Stores the employee id
2	e_name	Varchar		20	Stores the employee name
3	status	Varchar		20	Stores the status of employee (present/absent/off)
4	adate	datetime			Stores the date

  8 .Table name:- advance

Sr.No.	Field Name	Datatype	Constraints	Size	Description
1	e_id	Integer	foreign key		Stores the employee id
2	e_name	Varchar		20	Stores the employee name
3	adate	datetime			Stores the date advance
4	advance	real			Stores the amount taken

                 

       9 .Table name:- salaryreport

Sr.No.	Field Name	Datatype	Constraints	Size	Description
1	e_id	Integer	Foreign key		Stores the employee id
2	e_name	Varchar		20	Stores the employee name
3	smonth	Varchar		20	Stores the month of salary
4	present	integer			Stores the number of days present
5	absent	integer			Stores the number of days absent
6	doff	integer			Stores the number of days off
7	monthlys	real			Store maximum salary
8	netsal	real			Store net salary

      
10. Table name:- login

Sr.No.	Field Name	Datatype	Constraints	Size	Description
1	username	varchar	Primary key	10	Stores the user name
2	passwrd	Varchar		10	Stores the password of user

    

   

        11. Table name:- logintime

Sr.No.	Field Name	Datatype	Constraints	Size	Description
1	username	varchar	Foreign key	10	Stores the user name
2	logintime	Varchar		10	Stores the time of login

    

Program List                         

NO	FORM NAME	PURPOSE
1	splash.vb	This form display the title of system name of organization & copyright of the system
2	Login.vb	This form is used for security with the help of password
3	MDI.vb	This is the multiple document interface for the all of the form in the project
4	c_ragistration.vb	This form is use for registration of customer
5	c_billgeneration.vb	This form is use  to calculate bill and store bill information
6	c_search.vb	This form use to search and delete customer information
7	price.vb	This form is use to set and get product price
8	frmstock.vb	This form is use to set and get product stock
9	addemployee.vb	This form is use for to add new employee with unique id
10	searchemp.vb	This form is use to search ,delete ,update employee information
11	attendance.vb	This form use to store attendance of employee
12	advance.vb	This form use to allocate advance payment to employee
13	salary.vb	This form use to calculate salary of employee
14	account.vb	This form use to create new user account
15	chgpass.vb	This form use to change password of user
16	printbill.vb	This form use to print bill of  individual customer

Report List

                                 

NO.	REPORT NAME	PURPOSE
1	CrystalReport11.rpt	This report is use to print and show the customer report
2	Crystalemp.rpt	This report is use to print & show the list of the employee
3	Crystalsalary.rpt	This report is use to print & display salary report
4	Crystalsales.rpt	This report is use f to print and show sales report
5	Crystalinventry.rpt	This report is use to print and show  inventory detail

SYSTEM CONTROLS AND STANDARDS - PETROL PUMP MANAGEMENT SYSTEM PROJECT

1.   Access control:-

 System gives access by valid password.

2.   Input control:-

System validates every textbox. It allows textual values for fields like customer name. It also validates some numeric data only for fields like phone no.

3.   System Generated control:-

In Order details it automatically calculates total price of the product. Similarly in Receipt details it automatically deducts the amount from the actual amount.

4.   Range control:-

In Order Transaction the system checks whether quantity given by the user is not more than the available product.

Future 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 sytem will work faster.

·         I will develop the system on LAN to setup the connection between other petrol pump of same company.

Conclusion - PETROL PUMP MANAGEMENT SYSTEM PROJECT

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.