Power Distribution system

CONTENTS
1. INTRODUCTION

2. DESIGN PRINCIPLES & EXPLANATION

2.1. MODULES

2.2. MODULE DESCRIPTIOIN

3. PROJECT DICTIONARY

3.1. DATAFLOW DIAGRAMS

3.3. DATA DICTIONARY

4. FORMS & REPORTS

4.1. I/O SAMPLES

5. BIBILIOGRAPHY
1. INTRODUCTION

Central Power Distribution Corporation Limited (CPDCL) is a division of

Andhra Pradesh Power Distribution Corporation Limited (APDCL), which

distributes the power generated by Andhra Pradesh Power Generation

Corporation Limited (APGENCO) and transmitted by Andhra Pradesh

Power Transmission Corporation Limited (APTRANSCO) through out

the central AP. It deals directly with the customers by distributing

power to them and by billing, and collection. As the corporation

charges for the services provided by them to the customers, they have

to satisfy the customer more. For this reason the corporation

established a “Customer Service Center”, to handle the customer

problems and their complaints. A customer service center was

inaugurated on September 21st. Some of the initiatives being

undertaken are as follows:

Spot Billing - A Single window solution:

For problems like wrong billing and non-receipts of bills, spot billing,

an effective service, which is unique in its operation, is introduced.

This service facilitates meter reading in the presence of the customer

through a hand held computer and issuing of the bill then and there.

Mobile fuse-off call Vans - Always on the more to serve you:

An occurrence of a huge wind or a kite stick may cause a severe power

Breakdown. Can you avoid or stop that? But our mobile fuse-off call
Vans can attend immediately to all such power breakdowns. With a

network of 30 fuse-off call Vans, highly experienced sub engineers and

dedicated O&M staff, we can ensure quick and efficient service

anytime.

Customer Passbooks - Your guide on power consumption:

A novel concept wherein passbooks are issued to the customers

containing the details of units consumed, bill amount, payment

particulars etc. Details of power consumption of different electrical

appliances are added information given in the passbooks.

Customer Service Centers - In your neighborhood:

A massive drive to attend customer grievances is being launched.

Attending to the problems of the customers and solving them

promptly, efficiently and effectively is the sole aim of these camps.

E-seva Centers - Bill payments made easy:

Bill can now be paid at e-seva centers, which are established recently

by the Govt. of AP at various places in twin cities enabling easy and

Centers.
2. DESIGN PRINCIPLES & EXPLANATION

2.1. MODULES
Well-structured designs improve the maintainability of a system. A
structured system is one that is developed from the top down and
modular, that is, broken down into manageable components. In this
project we modularized the system so that they have minimal effect on
each other.

Main Module

Registration Monitoring Reports Administration

Module Module Module Module

2.2. MODULE DESCRIPTION

Registration Module: This module is dedicated to register all the

complaints from the customers whenever they come to compliant. The

process of this module is divided into two sub processes in which one

registers the complete details of the customer who wants to submit

the compliant, other registers the complete details of the compliant

 Registration
Module

Reg. Customer Reg. Compliant

Monitoring Module: This module is dedicated to monitoring the

complaints by searching the complaints and updating the status of

complaints at any time. The process of this module is divided into two

sub processes in which one searches for complaints and other updates

the status.

Monitor
Module

Search Update
Reports Module: Report generation module is dedicated to produce

reports based on the information to given by the user. The process of

this module is mainly divided into two sub processes in which one

gives summary report other gives the detailed report

Report Module

Detailed Report Summary Report

Administration Module:

Administration module is dedicated to administrate the users,

divisions, categories, sections and Eros etc.

Admin
Module

Category Section Div/ERO User

Module Module Module Module
Reports:

The reports generated in project depict the up to date information

about the current status of various records. The various types of

reports that will be generated in this project are as mentioned below.

Time oriented reports: Time oriented reports give the information of

complaints according to the time period given. The time oriented

reports are daily, weekly, monthly, yearly and also includes reports on

certain period of time etc.

Status oriented reports: Status oriented reports give the

information of complaints according to the status given. The status

oriented reports are completed, pending and delayed reports.

Division wise reports: Division wise reports give the information of

complaints according to the division given.

Compliant wise reports:

Compliant wise reports give the information of complaints according to

the compliant type given.

Employee wise reports:

Employee wise reports give the information of complaints according to

the employee referred to solve the compliant.

Detailed Or summary:

For all the above types of reports, we can get detailed which shows

complete information or summary that shows limited information.

3. PROJECT DICTIONARY

3.1. DATAFLOW DIAGRAMS

A graphic tool used to describe and analyze the moment of data

through a system – manual or automated – including the processes,

stores of data, and delays in the system. Data flow diagrams are the

central tools and the basis from which other components are

developed. The transformation of data from input to output, through

processes, may be described logically and independently of the

physical components associated with the system.

Compliant
Compliant
Details
registration
Consumer and
Monitoring
Acknowledgement System

Reports

CONTEXT ANALYSIS
DIAGRAM
 Authentication data
User data User data

User

Login
Process

Emp Store
Acknowledgement

User data

Control

Admin
Process
Authorization
Compliant Details
Div/Cat/Sect
Div/Cat/Section/ero
ion/ero

ation
Process
Registr
Consumer

Div/Cat/Section/ero

Div/Cat Store
Acknowledgement

LEVEL 1 DFD
Administrator
Compliant Details

Report
Process
Compliant Details

Comp. Store
Compliant Details
Process
Monitor

Reports
Report Data
 Consumer Consumer
Register
Details Details
Consumer
Details

Service No
Consumer

Consumer Store
Div Store

Category Store

Div/Sub div Ctgr/Sub Ctgr

Register
Compliant
Compliant Details Compliant
Details Details
Section

ERO

Compliant Store

Section Store ERO Store

LEVEL 2 DFD
(REGISTRATION PROCESS)
Search Key Data Compliant Details
Search
Complaints

Compliant ID
Compliant Store

Compliant Status Update

Complaint
Compliant Details
Status

LEVEL 2 DFD
(MONITORING PROCESS)
 Administrator

User Details
Div/Sdiv/Ero
Details

Cat/SCat

Section
Details
Details

Store Store
Store Store
Div/Sub Cat/Sub
Section Users

User Details
Div/Sdiv/Ero

div/ERO Cat
Details

Cat/SCat

Section
Details

Details

Div Store Cat Store Sec Store User Store

LEVEL 2 DFD
(ADMIN PROCESS)
3.2. DATA DICTIONARY

A data dictionary is a catalogue – a repository – of the elements in a

system. As the name suggests, these elements center around data the

way they are structured to meet user requirements and organization

needs. In a data dictionary you will find a list of all the elements

composing the data flow through a system.

Employee Data Structure: This data structure describes the

authentication elements of operator or administrator.

Name Type & Size Constraints Description

USER_ID Varchar2 (15) PRIMARY KEY User

identification
PWD Varchar2 (15) NOT NULL User password
PRIV Varchar2 (10) NOT NULL User privileges
EMP_NAME Varchar2 (15) NOT NULL Name of the

user

Main Compliant Category Data Structure: This data structure describes

main compliant category attributes.

Name Type & Size Constraints Description

MCTGR_CODE Varchar2 (10) PRIMARY KEY Code describing
 the main

category of

compliant
MCTGR_NAME Varchar2 (15) NOT NULL Name of the

category

Sub Category Compliant Data Structure: This data structure describes

the elements to represent a compliant sub category.

Name Type & Size Constraints Description

SCTGR_CODE Varchar2 (10) PRIMARY KEY Code describing

the sub

category of

compliant
SCTGR_NAME Varchar2 (10) NOT NULL Name of the sub

category
MCTGR_CODE Varchar2 (10) FOREIGN KEY Code of main

category to

which this sub

category

belongs
OFF_ATTEND Varchar2 (10) NOT NULL Officer to attend

for this type of

complaints
OFF_SPRV Varchar2 (10) NOT NULL Officer to

supervise for
 this type of

complaints
TIME_LIMIT Number NOT NULL Time limit to

solve this

compliant type

Division Data Structure: This data structure describes the

elements to represent divisions.

Name Type & Size Constraints Description

DIV_CODE Varchar2 (10) PRIMARY KEY Code describing

a unique

division
DIVE_NAME Varchar2 (15) NOT NULL Name of the

division

Sub Division Data Structure: This data structure describes the

elements to represent sub divisions.

Name Type & Size Constraints Description

SDIV_CODE Varchar2 (10) PRIMARY KEY Code describing

a unique sub

division
SDIVE_NAME Varchar2 (15) NOT NULL Name of the sub
 division
DIV_CODE Varchar2 (10) FOREIGN KEY Code of division

to which this

sub division

belongs to

ERO Data Structure: This data structure describes the elements to

represent Electricity Revenue Office (ERO).

Name Type & Size Constraints Description

ERO_CODE Varchar2 (10) PRIMARY KEY Code describing

a unique ERO
ERO_NAME Varchar2 (15) NOT NULL Name of the

ERO
DIV_CODE Varchar2 (10) FOREIGN KEY Code of division

to which this

ERO belongs to
SECTION Data Structure: This data structure describes the

elements to represent sub divisions.

Name Type & Size Constraints Description

SEC_CODE Varchar2 (10) PRIMARY KEY Code describing

a unique

division
SEC_NAME Varchar2 (15) NOT NULL Name of the

division
DIV_CODE Varchar2 (10) FOREIGN KEY Code of division

to which this

sub division

belongs to
SDIV_CODE Varchar2 (10) FOREIGN KEY Belonging sub

division code
ERO_CODE Varchar2 (10) FOREIGN KEY Belonging ERO

code

Consumer Data Structure: This data structure describes the

elements to represent the consumer who make the compliant.

Name Type & Size Constraints Description

SRVC_NO Varchar2 (10) PRIMARY KEY Service number
CNSMR_CTGR Varchar2(10) Category
AREA_CODE Varchar2 (10) Service area

code
CNSMR_NAME Varchar2 (20) Name of
 consumer
HNO Varchar2 (15) House number
STREET Varchar2 (15) Street name
LOCATION Varchar2 (15) Location in town
CTY_TWN_VLG Varchar2 (15) City or town or

village name
PHONE Varchar2 (10) Phone number
CMPLT_MODE Varchar2 (10) Mode of

compliant

Compliant Data Structure: This data structure describes the data

elements to represent complaints.

Name Type & Size Constraints Description

CMPLT_ID Varchar2(15) PRIMARY KEY Unique id for

each compliant
SRVC_NO Varchar2 (10) FOREIGN KEY Service number

of consumer

complained
CMPLT_DATE Date NOT NULL Complained

date
MCTGR_CODE Varchar2 (10) FOREIGN KEY Compliant

category
SCTGR_CODE Varchar2 (10) FOREIGN KEY Compliant sub

category
ADDR_TO Varchar2 (15) Compliant

addressed to
OFF_ATTEND Varchar2 (15) Officer to attend
OFF_REF Varchar2 (15) Officer to refer
URBAN_RURAL Varchar2 (10) Urban or rural
STATUS Varchar2 (15) Status of
 compliant

4. FORMS & REPORTS

4.1.I/O SAMPLES
5. BIBILIOGRAPHY

Visual Basic 6.0:

The Complete Reference VB6

Database programming with Visual Basic Michael and Smith

Oracle 8.0:

PLSQL Complete Reference Oracle Press

Principles of database systems Jeffery D Ullman

Database Management Systems C J Date

System Development:

Fundamentals Of System Concepts Jerry Fitz Gerald

System Analysis And Design Elias M Awad

Software Engineering: Roger P Pressman