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 Module

Monitoring Module

Reports Module

Administration 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 Module Reports:

Section Module

Div/ERO Module

User Module

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.

Consumer

Compliant Details Acknowledgement

Compliant registration and Monitoring System

Reports

CONTEXT ANALYSIS DIAGRAM

Authentication data User data User Login Process

Emp Store Acknowledgement Authorization Control

User data

Admin Process Div/Cat/Sect Div/Cat/Section/eroion/ero Registr ation Process Div/Cat/Section/ero Compliant Details Div/Cat Store

User data

Compliant Details Consumer

LEVEL 1 DFD Report Data Comp. Store Compliant Details Monitor Process Reports

Administrator

Acknowledgement

Report Process

Compliant Details

Consumer Details

Register Consumer Details

Consumer Details

Consumer Service No

Div Store

Consumer Store

Category Store

Div/Sub div

Compliant Details Section

Register Compliant Details

Ctgr/Sub Ctgr

Compliant Details ERO

Compliant Store

Section Store

ERO Store

LEVEL 2 DFD (REGISTRATION PROCESS)

Search Key Data

Search Complaints Compliant ID

Compliant Details

Compliant Store

Compliant Status

Update Complaint Status

Compliant Details

LEVEL 2 DFD (MONITORING PROCESS)

Div/Sdiv/Ero Details

Cat/SCat Details

Div/Sdiv/Ero Details

Cat/SCat Details

Div Store

Cat Store

Section Details

Sec Store

User Store

LEVEL 2 DFD (ADMIN PROCESS)

User Details

Store Div/Sub div/ERO

Store Cat/Sub Cat

Section Details

Store Section

User Details Store Users

Administrator

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 USER_ID PWD PRIV EMP_NAME

Type & Size Varchar2 (15) Varchar2 (15) Varchar2 (10) Varchar2 (15)

Constraints PRIMARY KEY NOT NULL NOT NULL NOT NULL

Description User identification User password User privileges Name of the user

Main Compliant Category Data Structure: This data structure describes main compliant category attributes.

Name MCTGR_CODE

Type & Size Varchar2 (10)

Constraints PRIMARY KEY

Description Code describing the main

category MCTGR_NAME Varchar2 (15) NOT NULL compliant Name of category

of the

Sub Category Compliant Data Structure: This data structure describes the elements to represent a compliant sub category.

Name SCTGR_CODE

Type & Size Varchar2 (10)

Constraints PRIMARY KEY

Description Code describing the category sub of

SCTGR_NAME MCTGR_CODE

Varchar2 (10) Varchar2 (10)

NOT NULL FOREIGN KEY

compliant Name of the sub category Code of category main to

which this sub category OFF_ATTEND Varchar2 (10) NOT NULL belongs Officer to attend for this type of OFF_SPRV Varchar2 (10) NOT NULL complaints Officer supervise this type to for of

TIME_LIMIT

Number

NOT NULL

complaints Time limit solve

to this

compliant type Division Data Structure: This data structure describes the

elements to represent divisions.

Name DIV_CODE

Type & Size Varchar2 (10)

Constraints PRIMARY KEY

Description Code describing a unique the

DIVE_NAME

Varchar2 (15)

NOT NULL

division Name of division

Sub Division Data Structure: This elements to represent sub divisions.

data

structure

describes

the

Name SDIV_CODE

Type & Size Varchar2 (10)

Constraints PRIMARY KEY

Description Code describing a unique sub

SDIVE_NAME

Varchar2 (15)

NOT NULL

division Name of the sub division

DIV_CODE

Varchar2 (10)

FOREIGN KEY

Code of division to sub which this

division

belongs to

ERO Data Structure:

This data structure describes the elements to

represent Electricity Revenue Office (ERO).

Name ERO_CODE ERO_NAME DIV_CODE

Type & Size Varchar2 (10) Varchar2 (15) Varchar2 (10)

Constraints PRIMARY KEY NOT NULL FOREIGN KEY

Description Code describing a unique ERO Name of the ERO Code of division to which this

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

elements to represent sub divisions.

Name SEC_CODE

Type & Size Varchar2 (10)

Constraints PRIMARY KEY

Description Code describing a unique the

SEC_NAME DIV_CODE

Varchar2 (15) Varchar2 (10)

NOT NULL FOREIGN KEY

division Name of

division Code of division to sub which this

division sub

SDIV_CODE ERO_CODE

Varchar2 (10) Varchar2 (10)

FOREIGN KEY FOREIGN KEY

belongs to Belonging

division code Belonging ERO code

Consumer Data Structure:

This

data

structure

describes

the

elements to represent the consumer who make the compliant.

Name SRVC_NO CNSMR_CTGR AREA_CODE CNSMR_NAME HNO STREET LOCATION

Type & Size Varchar2 (10) Varchar2(10) Varchar2 (10) Varchar2 (20) Varchar2 (15) Varchar2 (15) Varchar2 (15)

Constraints PRIMARY KEY

Description Service number Category Service area code Name of

consumer House number Street name Location in town

CTY_TWN_VLG PHONE CMPLT_MODE

Varchar2 (15) Varchar2 (10) Varchar2 (10)

City or town or village name Phone number Mode of compliant

Compliant Data Structure:

This data structure describes the data

elements to represent complaints.

Name CMPLT_ID SRVC_NO

Type & Size Varchar2(15) Varchar2 (10)

Constraints PRIMARY KEY FOREIGN KEY

Description Unique id for each compliant Service number of consumer

CMPLT_DATE MCTGR_CODE SCTGR_CODE ADDR_TO OFF_ATTEND OFF_REF URBAN_RURAL STATUS

Date Varchar2 (10) Varchar2 (10) Varchar2 (15) Varchar2 Varchar2 Varchar2 Varchar2 (15) (15) (10) (15)

NOT NULL FOREIGN KEY FOREIGN KEY

complained Complained date Compliant category Compliant category Compliant addressed to Officer to attend Officer to refer Urban or rural Status of compliant sub

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 Principles of database systems Database Management Systems System Development: Fundamentals Of System Concepts System Analysis And Design Software Engineering: Jerry Fitz Gerald Elias M Awad Roger P Pressman Oracle Press Jeffery D Ullman C J Date