report

1. A
Project Report
On
Electricity Billing System
Submitted by
Vaishnavi Anil Bettawar
Roll No.: 23305
MCA–I
SEM–I
Under the guidance of
Dr. B. H. Kaulwar
For the Academic Year 2023-24
Sinhgad Technical Education Society’s
Sinhgad Institute of Management
Vadgaon Bk Pune 411041
(Affiliated to SPPU Pune & Approved by AICTE New Delhi)

2. Date:
CERTIFICATE
This is to certify that Ms. Vaishnavi Anil Bettawar has successfully
completed her project work entitled “Electricity Billing System” in
partial fulfillment of MCA – I SEM –I Mini Project for the year 2023-
2024. She has worked under our guidance and direction.
Dr. B. H. Kaulwar Dr. Chandrani Singh
Project Guide Director, SIOM-MCA
Examiner 1 Examiner 2
Date:
Place: Pune

3. DECLARATION
I certify that the work contained in this report is original and has
been done by me under the guidance of my guide.
 The work has not been submitted to any other Institute for any degree
or diploma.
 I have followed the guidelines provided by the Institute in preparing
the report.
 I have conformed to the norms and guidelines given in the Ethical Code
of Conduct of the Institute.
 Whenever I have used materials (data, theoretical analysis,
figures, and text) from other sources, I have given due
credit to them by citing them in the text of the report and
giving their details in the references.
Name and Signature of Project Team Members:
Sr.
No.
Seat No. Name of students Signature of
students
1 Vaishnavi Anil Bettawar

4. ACKNOWLEDGEMENT
It is very difficult task to acknowledge all those who have been of tremendous
help in this project. I would like to thank my respected guide Prof. Dipali Patil
for providing me necessary facilities to complete my project and also for their
guidance and encouragement in completing my project successfully without
which it wouldn’t be possible. I wish to convey my special thanks and
immeasurable feelings of gratitude towards Dr. Chandrani Singh, Director,
SIOM-MCA. I wish to convey my special thanks to all teaching and non-
teaching staff members of Sinhgad Institute of Management, Pune for their
support.
Thank You
Yours Sincerely,
Vaishnavi Anil Bettawar

5. INDEX
Sr. No. Chapter Page No.
1 CHAPTER 1: INTRODUCTION
1.1 Abstract
1.2 Existing System and Need for System
1.3 Scope of System
1.4 Operating Environment Hardware and Software
1.5 Brief Description of Technology Used
2 CHAPTER 2: PROPOSED SYSTEM
2.1 Feasibility Study
2.2 Objectives of the proposed system
2.3 Users of the system
3 CHAPTER 3: ANALYSIS AND DESIGN
3.1 Entity Relationship Diagram (ERD)
3.2 Class Diagram
3.3 Use Case Diagrams
3.4 Activity Diagram
3.5 Sequence Diagram
3.6 Component Diagram
3.7 Module and Hierarchy Diagram
3.8 Table Design
3.9 Data Dictionary
3.10 Sample Input and Output Screens
(Screens must have valid data. All reports must have
at-least 5 valid records.)
4 CHAPTER 4: CODING Sample code
5 CHAPTER 5: LIMITATIONS OF SYSTEM
6 CHAPTER 6: PROPOSED ENHANCEMENTS
7 CHAPTER 7: CONCLUSION
8 CHAPTER 8: BIBLIOGRAPHY

6. 1: INTRODUCTION
1.1 Abstract
Electricity consumers are often faced with the problem of inaccuracy and
delay in monthly billing due to the drawback in reading pattern and
human errors. Thus, it is essential to have an efficient system for such purposes
via electronic platform with consideration to proximity. The proposed
system automates the conventional process of paying electricity bill by
visiting the Electricity Board which is tiresome and time consuming. It is
also designed to automate the electricity bill calculation and payment for
user convenience. The Microsoft Structured Query Language (SQL) server is
also used for creating back-end database. The system would be having two
logins: the administrative and user login. The administrator can view the
user’s account details and can add or update the customer’s information of
consuming units of energy of the current month in their account. The
Admin has to feed the system with the electricity usage data into respective
users account. The system then calculates the electricity bill for every user
and updates the information into their account every month. Users can then
view their electricity bill and pay before the month end.

7. 1.2 Existing System and Need for System
Existing System:
The existing system for an electricity billing system might involve manual
processes or outdated software. The existing system of electricity billing is not
so effective; one staff must visit each customer’s house to note the meter
readings and collect the data. Then, another staff must compute the consumed
units and calculate the money to be paid. Again, the bills prepared are to be
delivered to customers. Finally, individual customer must go to electricity office
to pay their dues.
It is a lengthy process overall. In order to solve this lengthy process of
billing, a web based computerized system is essential. This proposed electricity
billing system project overcomes all these drawbacks.
Need for System:
The need for a new system arises from several factors:
a. Efficiency: Automating the billing process can significantly improve
efficiency by reducing manual data entry and calculation errors.
b. Accuracy: A new system can ensure accurate meter reading and billing,
minimizing disputes and discrepancies.
c. Customer Convenience: A modern system can offer online payment
options, real-time usage tracking, and digital invoices, enhancing the customer
experience.
d. Data Analysis: Advanced systems can collect and analyze data for better
load management and future planning.
e. Cost Reduction: Automation can lower operational costs in the long run.

8. 1.3 Scope of System:
It collectively ensures the efficient management of electricity billing processes,
enhance customer satisfaction, and enable utility providers to maintain accurate
billing records and revenue management.
Designing the system to handle a growing number of customers and data. The
specific scope may vary depending on the project's goals, budget, and the needs
of the electricity provider. It's essential to define the scope clearly at the
beginning of the project to ensure its successful execution.

9. 1.4 Operating Environment Hardware and Software
Server-side requirement
Client-side requirement
Software Requirement Hardware Requirement
Operating System: Windows 7 or above Processor: Ryzen or above
Front End: (Swing and AWT) RAM: 4GB or above
Back End: Java HDD: 512 GB or above
Database: MySQL
Web Browser: Chrome Mozilla Firefox
Software Requirement Hardware Requirement
Operating System: Windows 7 or above Processor: Ryzen or above
Web Browser: Chrome, Mozilla Firefox RAM: 2GB or above
HDD: 512 GB or above

10. 1.5 Brief Description of Technology Used JAVA:
Java is one of the most popular and widely used programming language
and platform. A platform is an environment that helps to develop and run pro-
grams written in any programming language. Java is fast, reliable and secure.
From desktop to web applications, scientific supercomputers to gaming consoles,
cell phones to the Internet, Java is used in every nook and corner. Java is a
programming language and computing platform first released by Sun
Microsystems in 1995. There are lots of applications and websites that will not
work unless you have Java installed, and more are created every day. Java is fast,
secure, and reliable. From laptops to datacenters, game consoles to scientific
supercomputers, cell phones to the Internet, Java is everywhere! Java is a general-
purpose, concurrent, object-oriented, classbased, and the run- time environment
(JRE) which consists of JVM which is the cornerstone of the Java platform. This
blog on what is Java will clear all your doubts about why to learn java, features
and how it works.
JDK:
The Java Development Kit (JDK) is an implementation of either one of the
Java Platform, Standard Edition, Java Platform, Enterprise Edition, or Java
Platform, Micro Edition platforms released by Oracle Corporation in the form of
a binary product aimed at Java developers on Solaris, Linux, macOS or Windows.
The JDK includes a private JVM and a few other resources to finish the
development of a Java Application. Since the introduction of the Java platform,
it has been by far the most widely used Software Development Kit (SDK). On 17
November 2006, Sun announced that they would release it under the GNU
General Public License (GPL), thus making it free software. This happened in
large part on 8 May 2007, when Sun contributed the source code to the OpenJDK.

11. 2. PROPOSED SYSTEM
Proposed System:
A proposed system for an electricity billing system should incorporate modern
technology and features to enhance efficiency, accuracy, and customer
satisfaction. Here are key components and features to consider:
1. Smart Metering: Implement smart meters that can remotely collect consumption
data and transmit it to the billing system in real-time. This eliminates the need for
manual meter reading.
2. User-friendly Web and Mobile Interfaces: Develop user-friendly web and mobile
applications for customers to access their accounts, view usage history, and make
payments conveniently.
3. Automated Billing: Automate the billing process to generate invoices based on real-
time consumption data. Send digital invoices via email or through the mobile app.
4. Payment Options: Offer various payment options such as online payments,
automatic bank transfers, and mobile payment apps to make it convenient for
customers to pay their bills.
5. Energy Usage Analytics: Provide customers with tools to analyze their energy
usage patterns.
6. Customer Support: Implement a responsive customer support system with live chat,
email, and phone support to address customer inquiries and concerns promptly.
7. Security: Ensure robust security measures to protect customer data, financial
transactions, and the integrity of the billing system.

12. 2.1 Feasibility Study:
 Technical Feasibility
Our application is feasible because we develop this project where a finite
number of software and hardware is required. It requires limited resources that
are readily available or already present almost everywhere. It is economically
feasible as the only cost involved is getting internet access.
 Economic Feasibility
It is the measure of cost effectiveness of the system. At present the
system can use one person to operate so the labor charge is reduced and other
charges for the facility along with maintenance cost is reduced. Our system is less
costly. There is no restriction for use high level or specific printer for printing
bills or records slips. This system can install any lower cost machines.
 Operational Feasibility
we are providing the user interface in our software made as per
standard it would be easy to navigate through my system using interface. There
is very simplified process of login and registration so any one can use it
Operational feasibility that are involved in the project the proposed system offers
greater level of user friendly behavior.

13. 2.2 Objectives of the proposed system:
➢ This project is an innovation, which makes the way of paying electricity
bills simple compared to manual process. It maintains error free database and
easily incorporates the future developments and changes. To develop a well -
designed database to store employee information. We can provide SMS based
alerts and email notifications for billing. User can update the information and be
able to view the updated information after updation is done. It can also be used
to provide referral code concept for referring friends

14. 2.3 Users of the system:
There are 2 Users present in the application:
1. Admin 2. Customer
Admin :
The administrator is the master user of this application
Responsibility of admin includes:
➢ Creating new customers
➢ View Customers Details
➢ Maintaining deposit details of every customer
➢ Update Status of payment
➢ Calculating bill
➢ Sending notification and message
Customer :
Customer’ Functionality includes:
➢ New Customer can register
➢ Login using username and password
➢ View and update their profile
➢ See the bill details
➢ View the generated bill
➢ Can pay bills
➢ Register report and give feedback

15. 3. ANALYSIS AND DESIGN
3.1 Entity Relationship Diagram (ERD):

16. 3.2 Class Diagram :

17. 3.3 Use Case Diagram : (Admin)

18. Use Case Diagram : (User)

19. 3.4 Activity Diagram : (Admin)
Activity Diagram : (User)

20. 3.5 Sequence Diagram : (User)

21. 3.6 Component Diagram :

22. 3.6 Table Design :
 Table:
The given below table is a snapshot of backend view of the localhost and the
structures of the tables present in Electricity Billing System. The tables present
are Login, customer, bill , meter , tax
 Login Table:
Field Type Null Key Default
name Varchar(20) YES primary_key null
username Varchar(30) YES null
Meter_no Varchar(20) YES forgien_key null
password Varchar(20) YES null
user Varchar(20) YES null
 Customer Table:
Field Type Null Key Default
name Varchar(20) YES Foreign
key
null
meter_no Varchar(20) YES Foreign
key
null
address Varchar(20) YES null
city Varchar(20) YES null
state Varchar(20) YES null
email VarChar(20) YES null
phone Varchar(10) Yes null

23.  Tax Table:
Field Type Null Key Default
Cost_per_unit Varchar(20) YES null
meter_rent Varchar(20) YES null
service_charge Varchar(20) YES null
service_tax Varchar(20) YES null
swacch_bharat_cess Varchar(20) YES null
Fixed_tax Varchar(20) YES null
 Bill Table :
Field Type Null Key Default
meter_no Varchar(20) YES Foreign
key
null
month Varchar(30) YES null
units Varchar(20) YES null
totalbill Varchar(20) YES null
status Varchar(20) YES null
 Meter table :
Field Type Null Key Default
meter_no Varchar(20) YES primary
key
null
meter_location Varchar(30) YES null
meter_type Varchar(20) YES null
phase_code Varchar(20) YES null
bill_type Varchar(20) YES null
days Varchar(20) YES null

24. 3.6 Data Dictionary :
Field Name Data Type Size Constraint Description
name varchar 15 Primary key Represents the
name of
customer
username varchar 20 Not Null Represents the
username
from which
customer
should login
password varchar 20 Not Null Represents the
password of
cutomer
meter_no int 20 Primary_key Represents the
meter number
user varchar 20 Not Null Represents the
Who is login
city varchar 20 Not Null Represents the
city of
customer
address varchar 100 Not Null Represents the
customer
address
state varchar 20 Not Null Represents the
customer state
email varchar 20 Not Null Represents the
email id of
customer
phone varchar 10 Not Null Represents the
customer
phone number
cost_per_unit int 20 Not Null Represents the
cost of per
unit consumed
meter_rent varchar 20 Not Null Represents the
rent of meter

25. service_charge date 20 Not Null Represents the
services
charges
service_tax varchar 20 Not Null Represents the
services tax
swacch_bharat_cess int 20 Primary key Represents the
swacch bharat
tax
fixed_tax varchar 20 Not Null Represents the
fixed tax
added in each
bill
units int 20 Primary key Represents the
units
consumed
totalbill int 20 Not Null Shows the
total bill of
customer
status varchar 20 Not Null Represents the
status (paid,
unpaid)
meter_location int 20 Primary key Represents the
location of
metre (inside,
outside)
phase_code int 20 Not Null Represents the
phase code of
meter
bill_type int 20 Not Null Represents the
type of bill
days int 20 Not Null Represents the
days (30 days)

26. 3.10 Sample Input and Output Screens :
 Input Code :

27.  Output Screen:

28. 4 : CODING Sample Code :
 Input Code :
package electricity.billing.system;
import javax.swing.*;
import java.awt.*;
import java.awt.event.*;
import java.sql.*;
public class Login extends JFrame implements ActionListener{
JButton login, cancel, signup;
JTextField username, password;
Choice logginin;
Login() {
super("Login Page");
getContentPane().setBackground(Color.WHITE);
setLayout(null);
JLabel lblusername = new JLabel("Username");
lblusername.setBounds(300, 20, 100, 20);
add(lblusername);
username = new JTextField();
username.setBounds(400, 20, 150, 20);
add(username);

29. JLabel lblpassword = new JLabel("Password");
lblpassword.setBounds(300, 60, 100, 20);
add(lblpassword);
password = new JTextField();
password.setBounds(400, 60, 150, 20);
add(password);
JLabel loggininas = new JLabel("Loggin in as");
loggininas.setBounds(300, 100, 100, 20);
add(loggininas);
logginin = new Choice();
logginin.add("Admin");
logginin.add("Customer");
logginin.setBounds(400, 100, 150, 20);
add(logginin);
ImageIcon i1 = new
ImageIcon(ClassLoader.getSystemResource("icon/login.png"));
Image i2 = i1.getImage().getScaledInstance(16, 16,
Image.SCALE_DEFAULT);
login = new JButton("Login", new ImageIcon(i2));
login.setBounds(330, 160, 100, 20);
login.addActionListener(this);
add(login);
ImageIcon i3 = new
ImageIcon(ClassLoader.getSystemResource("icon/cancel.jpg"));
Image i4 = i3.getImage().getScaledInstance(16, 16,
Image.SCALE_DEFAULT);
cancel = new JButton("Cancel", new ImageIcon(i4));
cancel.setBounds(450, 160, 100, 20);
cancel.addActionListener(this);

30. add(cancel);
ImageIcon i5 = new
ImageIcon(ClassLoader.getSystemResource("icon/signup.png"));
Image i6 = i5.getImage().getScaledInstance(16, 16,
Image.SCALE_DEFAULT);
signup = new JButton("Signup", new ImageIcon(i6));
signup.setBounds(380, 200, 100, 20);
signup.addActionListener(this);
add(signup);
ImageIcon i7 = new
ImageIcon(ClassLoader.getSystemResource("icon/second.jpg"));
Image i8 = i7.getImage().getScaledInstance(250, 250,
Image.SCALE_DEFAULT);
ImageIcon i9 = new ImageIcon(i8);
JLabel image = new JLabel(i9);
image.setBounds(0, 0, 250, 250);
add(image);
setSize(640, 300);
setLocation(400, 200);
setVisible(true);
}
public void actionPerformed(ActionEvent ae) {
if (ae.getSource() == login) {
String susername = username.getText();
String spassword = password.getText();
String user = logginin.getSelectedItem();
try {
Conn c = new Conn();

31. String query = "select * from login where username = '"+susername+"' and
password = '"+spassword+"' and user = '"+user+"'";
ResultSet rs = c.s.executeQuery(query);
if (rs.next()) {
String meter = rs.getString("meter_no");
setVisible(false);
new Project(user, meter);
} else {
JOptionPane.showMessageDialog(null, "Invalid Login");
username.setText("");
password.setText("");
}
} catch (Exception e) {
e.printStackTrace();
}
} else if (ae.getSource() == cancel) {
setVisible(false);
} else if (ae.getSource() == signup) {
setVisible(false);
new Signup();
}
}
public static void main(String[] args) {
new Login();
}
}

32.  Output Code :
package electricity.billing.system;
import javax.swing.*;
import java.awt.*;
import java.awt.event.*;
import java.sql.*;
public class GenerateBill extends JFrame implements ActionListener
{
String meter;
JButton bill;
Choice cmonth;
JTextArea area;
GenerateBill(String meter) {
this.meter = meter;
setSize(500, 800);
setLocation(550, 30);
setLayout(new BorderLayout());
JPanel panel = new JPanel();
JLabel heading = new JLabel("Generate Bill");
JLabel meternumber = new JLabel(meter);
cmonth = new Choice();
cmonth.add("January");
cmonth.add("February");
cmonth.add("March");
cmonth.add("April");
cmonth.add("May");

33. cmonth.add("June");
cmonth.add("July");
cmonth.add("August");
cmonth.add("September");
cmonth.add("October");
cmonth.add("November");
cmonth.add("December");
area = new JTextArea(50, 15);
area.setText("nnt--------Click on the---------nt Generate Bill Button to
getntthe bill of the Selected Month");
area.setFont(new Font("Senserif", Font.ITALIC, 18))
JScrollPane pane = new JScrollPane(area);
bill = new JButton("Generate Bill");
bill.addActionListener(this);
panel.add(heading);
panel.add(meternumber);
panel.add(cmonth);
add(panel, "North");
add(pane, "Center");
add(bill, "South");
setVisible(true);
}
public void actionPerformed(ActionEvent ae) {
try {
Conn c = new Conn();
String month = cmonth.getSelectedItem();
area.setText("tReliance Power LimitednELECTRICITY BILL
GENERATED FOR THE MONTHntOF "+month+", 2022nnn");

34. ResultSet rs = c.s.executeQuery("select * from customer where
meter_no = '"+meter+"'");
if(rs.next()) {
area.append("n Customer Name: " + rs.getString("name"));
area.append("n Meter Number : " + rs.getString("meter_no"));
area.append("n Address : " + rs.getString("address"));
area.append("n City : " + rs.getString("city"));
area.append("n State : " + rs.getString("state"));
area.append("n Email : " + rs.getString("email"));
area.append("n Phone : " + rs.getString("phone"));
area.append("n---------------------------------------------------");
area.append("n");
}
rs = c.s.executeQuery("select * from meter_info where meter_no =
'"+meter+"'");
if(rs.next()) {
area.append("n Meter Location: " +
rs.getString("meter_location"));
area.append("n Meter Type: " + rs.getString("meter_type"));
area.append("n Phase Code: " + rs.getString("phase_code"));
area.append("n Bill Type: " + rs.getString("bill_type"));
area.append("n Days: " + rs.getString("days"));
area.append("n---------------------------------------------------");
area.append("n");
}
rs = c.s.executeQuery("select * from tax");
if(rs.next()) {

35. area.append("n");
area.append("n Cost Per Unit: " + rs.getString("cost_per_unit"));
area.append("n Meter Rent: " + rs.getString("cost_per_unit"));
area.append("n Service Charge: " +
rs.getString("service_charge"));
area.append("n Service Tax: " +
rs.getString("service_charge"));
area.append("n Swacch Bharat Cess: " +
rs.getString("swacch_bharat_cess"));
area.append("n Fixed Tax: " + rs.getString("fixed_tax"));
area.append("n");
}
rs = c.s.executeQuery("select * from bill where meter_no = '"+meter+"'
and month='"+month+"'");
if(rs.next()) {
area.append("n");
area.append("n Current Month: " + rs.getString("month"));
area.append("n Units Consumed: " + rs.getString("units"));
area.append("n Total Charges: " + rs.getString("totalbill"));
area.append("n-------------------------------------------------------");
area.append("n Total Payable: " + rs.getString("totalbill"));
area.append("n");
}
} catch (Exception e) {
e.printStackTrace();
}
}
public static void main(String[] args) {
new GenerateBill(""); }}

36. 5 : Limitations of System
 The traditional billing process is often slow, inaccurate, and prone to
errors. To overcome these limitations, several existing methods of
electricity bill management have been developed using various
programming languages such as Java, PHP, Python, and C#.
6 : Proposed Enhancement
7 : Conclusion
 In conclusion, the implementation of an online electricity billing
system offers significant advantages, including convenience for
users and improved accuracy in bill calculations. The user-
friendly interface, automated algorithms, real-time usage
tracking, and transparent billing breakdowns contribute to an
efficient and reliable system. Continuous monitoring, updates,
and user feedback mechanisms are essential for maintaining and
enhancing the system's effectiveness over time. Overall, the
online electricity billing system not only streamlines processes
but also enhances customer satisfaction through accessibility
and error-free calculations.
8: Bibliography