REMOTE METERING DATABASE PROJECT

PROJECT PROPOSAL

MAY, 2010
 REMOTE METERING DATABASE PROJECT

TABLE OF CONTENTS

PAGES

1.0 INTRODUCTION.................................................................................3

2.0 PROBLEM STATEMENT.......................................................................3

3.0 OBJECTIVES.......................................................................................3

3.1. MAJOR OBJECTIVE...............................................................................................3

3.2. SPECIFIC OBJECTIVES.........................................................................................3

4.0 USER REQUIREMENTS........................................................................4

5.0 SYSTEM DESIGN................................................................................5

5.1. TECHNOLOGIES USED........................................................................................5

5.2. TERMINALOGY:...................................................................................................5
5.3. DATA FLOW DIAGRAM .....................................................................................6

6.0 DATABASE DESIGN..............................................................................7

6.1. ENTITY RELATIONSHIPS......................................................................................7

6.2. ENTITY RELATIONSHIP DATABASE MODEL..........................................................8
6.3. DATA DICTIONARY..............................................................................................9

7.0 SYSTEM REQUIREMENTS..................................................................12

8.0 PROJECT SCHEDULE.........................................................................13

9.0 APPENDIX ......................................................................................14

9.1. ABBREVIATIONS ............................................................................................14

File name: Customer Verification Project

Page 2 of 14
Last saved: 10/07/2010
Ver.1
 REMOTE METERING DATABASE PROJECT

1.0 INTRODUCTION

Accurate and reliable reporting is a key aspect in today’s business. This can be achieved by
automating the manual processes involved in all sections.

2.0 PROBLEM STATEMENT

The records downloaded remotely from substation meters are stored on workstations in
excel files. This makes the records insecure, vulnerable to getting lost, too hard to access
and very cumbersome to process into reports for management.

3.0 OBJECTIVES

3.1. MAJOR OBJECTIVE

To design a centralized database system for remote metering.

3.2. SPECIFIC OBJECTIVES

The system shall deliver automated and integrated tools necessary to increase efficiency
and reliability of reporting on all remote metering activities. This will comprise of the
following key feature:
a) Centralized Database: This will be a secure database which will be housed by a
server on the network for easy access by all users.

b) User Interface: provide ability to authorized users to interact with the system.

c) Dynamic reporting tool: generate quick and accurate reports with all the necessary
graphical representations.

d) Administrative tools: Allow creation and management of users in the system

including assignment of user rights and privileges
e) Search capabilities, e.g. Users should be able to search information for a given
feeder by say using the feeder name.

File name: Remote Metering Database Project

Page 3 of 9
Last saved: 10/07/2010
Page 3 of 14

Ver.1
 REMOTE METERING DATABASE PROJECT

4.0 USER REQUIREMENTS

f) The system should validate the cumulative import readings with the individual
registers readings.
g) The system should compute energy dispatched to a particular feeder in a given
month (variance).
h) The reporting tool should be dynamic to be able to generate reports of different
formats.
i) The system should be able to search by feeder, district, area etc.
j) The system should compare the energy dispatched by the metering department to
the energy reported by Network control department.
k) The system should accept load profile reports from meters and generate graphs
showing the variations in the load on a given feeder in a particular time interval
l) The system should produce reports according to feeder, district, region and the
whole company

File name: Remote Metering Database Project

Page 4 of 9
Last saved: 10/07/2010
Page 4 of 14

Ver.1
 REMOTE METERING DATABASE PROJECT

5.0 SYSTEM DESIGN

5.1. TECHNOLOGIES USED

The following technologies shall be used to design and develop the system:
a) Oracle 10g will be used at the back end for the database
b) C-sharp will be used to implement the business logic and design user interfaces

5.2. TERMINALOGY:
 A feeder: - A power line coming from a substation.

 Interconnector: - A feeder that supplies another substation i.e. from one substation
to another.

 Boundary: - A point on a feeder dividing two districts.

 Cumulative Import:- sum of all the incoming usages recorded by the meter on a
feeder.

 Cumulative Export: - sum of all the outgoing usages recorded by the meter on a
feeder.

 Advance :- it is the usage in kWh of a feeder in a given month i.e. the sum of
r1,r2,r3 for a particular month

 Rates:- units in kWh recorded on the registers

 Maximum demand:- the power used

File name: Remote Metering Database Project

Page 5 of 9
Last saved: 10/07/2010
Page 5 of 14

Ver.1
 REMOTE METERING DATABASE PROJECT

5.3. DATA FLOW DIAGRAM

BULK METER NETWORK CONTROL

• Cum. Import
• Cum. Export
• Varh
• R1 UETCL sales reports
• R2
• R3
• R4
• R6
• R7
• R8
• R9

MAJOR PROCESSES
• Convert wh to kwh
• Convert va to kva
• Convert varh to kvarh
• Compute energy dispatched per feeder(Advance)
• Compute energy lost per feeder
• Validate meter readings sum of registers compared to cum
import & cum exports
• Validate energy parchased to energy dispatched(from
Network Control and metering)

• Energy dispatches report

• Energy loss report • Energy
Exceptions Report
• Exceptions Report dispatches report
• UETCL Report

LOSS REDUCTION METERING BILLING DEPT

DEPT DEPT

File name: Remote Metering Database Project

Page 6 of 9
Last saved: 10/07/2010
Page 6 of 14

Ver.1
 REMOTE METERING DATABASE PROJECT

6.0 DATABASE DESIGN

6.1. ENTITY RELATIONSHIPS

a) A company has one or more major substations

b) A major substation dispatched to one or more minor substations

c) A substation has one or more meter

d) A substation dispatches energy to one or more feeders.

e) A feeder dispatches energy to one or more districts.

f) A feeder has one or more meters

g) A meter has one or more readings

h) A feeder has one or more transformers

i) A transformer has only one meter

j) The company has one or more regions

k) A region has one or more districts

l) A district has one or more offices

File name: Remote Metering Database Project

Page 7 of 9
Last saved: 10/07/2010
Page 7 of 14

Ver.1
 REMOTE METERING DATABASE PROJECT

6.2. ENTITY RELATIONSHIP DATABASE MODEL

Has Has
REGION DISTRICT OFFICES
1:* 1:*
PK REGION_ID PK DISTRICT_ID PK OFFICE_ID
1:*
Has REGION_NAME DISTRICT_NAME OFFICE_NAME
REGION_ID DISTRICT_ID
Feeds
1:1
1:*
Supplies 1:*
SUBSTATIONS FEEDERS

PK SUBSTATION_ID PK FEEDER_ID

SUBSTATION_NAME Has Has FEEDER_NAME

LOCATION METER_ID

Belongs to
COMPANY_ID VOLTAGE
METER_ID FEEDER_TYPE
REGION_ID 1:* 1:* DISTRICT_ID
METERS SUBSTATION_ID
LOCATION
PK METER_ID
1:1
METER_NO
METER_MAKE
Has METER_TYPE

1:*
TRANSFORMERS
READINGS
PK TRANSFORMER_ID
PK READING_ID
TRANSFROMER_NAME
READING METER_ID
READING_DATE VOLTAGE
READING_TYPE DISTRICT_ID
METER_ID FEEDER_ID
LOCATION

File name: Remote Metering Database Project

Page 8 of 9
Last saved: 10/07/2010
Page 8 of 14

Ver.1
 REMOTE METERING DATABASE PROJECT

6.3. DATA DICTIONARY

REGIONS
COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINT
REGION_ID Unique id of region NUMBER PK
REGION_NAME Name of region VARCHAR2 NOT NULL

DISTRICTS
COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINT
DISTRICT_ID Unique id of district NUMBER PK
DISTRICT_NAME Name of district VARCHAR2 NOT NULL
REGION_ID Id of region VARCHAR2 FK

OFFICES
COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINT
OFFICE_ID Unique id of district NUMBER PK
OFFICE_NAME Name of district VARCHAR2 NOT NULL
DISTRICT_ID Id of region VARCHAR2 FK
FEEDER_ID

SUBSTATIONS
COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINT
SUB_ID Unique identifier of substation NUMBER PK
SUB_NAME Name of the substation VARCHAR2 NOT NULL
SUB_TYPE_ID Substation type NUMBER NOT NULL
LOCATION Address of the substation VARCHAR2 NOT NULL
METER_ID Substation meter NUMBER FK
COMPANY_ID Company owning the substation NUMBER NOT NULL
DISTRICT_ID Substation region NUMBER FK

SUBSTATION_TYPES
COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINT
SUB_TYPE_ID substation type unique identifier NUMBER PK
SUB_TYPE_NAME substation type name VARCHAR2 NOT NULL

File name: Remote Metering Database Project

Page 9 of 9
Last saved: 10/07/2010
Page 9 of 14

Ver.1
 REMOTE METERING DATABASE PROJECT

FEEDERS
COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINT
FEEDER_ID Feeder unique identifier NUMBER PK
FEEDER_ NAME Name of feeder VARCHAR2 NOT NULL
VOLTAGE Size of feeder eg 11 kv or 33 kv NUMBER NOT NULL
REGION_ID Region where feeder is located VARCHAR2 NOT NULL
METER_ID Feeder meter NOT NULL
SUB_ID Substation to which feeder is connected NUMBER NOT NULL
F_TYPE_ID Feeder type Number NOT NULL

TRANSFORMER
COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINT
TRANS_ID Transformer unique identifier NUMBER NOT NULL
TRANS_NAME Name of transfromer VARCHAR2 NOT NULL
ADDRESS NUMBER NOT NULL
DISTRICT_ID District where transformer VARCHAR2 NOT NULL
METER_ID Transformer meter

FEEDER TYPES
COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINT
F_TYPE_ID Reading type unique identifier NUMBER NOT NULL
F_TYPE_NAME Reading type name VARCHAR2 NOT NULL

COMPANIES
COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINT
COMPANY_ID Company unique identifier NUMBER NOT NULL
COMPANY_NAME Company name VARCHAR2 NOT NULL

METERS
COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINT
METER_ID Meter unique identifier NUMBER NOT NULL
METER_NO Meter number VARCHAR2 NOT NULL
M_TYPE_ID Meter type VARCHAR2 NOT NULL
LEVEL_ID Meter Level

FEEDER CATEGORIES
COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINT
CAT_ID Category unique identifier NUMBER NOT NULL
CAT_NAME category name VARCHAR2 NOT NULL
File name: Remote Metering Database Project
Page 10 of 9
Last saved: 10/07/2010
Page 10 of 14

Ver.1
 REMOTE METERING DATABASE PROJECT

METER_LEVELS
COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINT
LEVEL_ID Level unique identifier NUMBER NOT NULL
LEVEL_ NAME Level name VARCHAR2 NOT NULL

METER_TYPES
COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINT
M_TYPE_ID Meter type id NUMBER NOT NULL
M_TYPE_NAME Type name VARCHAR2 NOT NULL

METER MAKES
COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINT
MAKE_ID Meter make identifier NUMBER NOT NULL
MAKE_NAME Meter make name VARCHAR2 NOT NULL

METER STATUSES
COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINT
STATUS_ID NUMBER NOT NULL
STATUS_NAME VARCHAR2 NOT NULL

DISPATCHES
COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINT
LAST_UPDATE_USER NUMBER PK
LAST_UPDATE_DATE VARCHAR2 NOT NULL
DISPATCH_ID NUMBER NOT NULL
FEEDER_ID VARCHAR2 NOT NULL
CURR_DISPATCH NOT NULL
PREV_DISPATCH NUMBER NOT NULL
ADVANCE Number NOT NULL

READINGS
COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINT
LAST_UPDATE_USER
LAST_UPDATE_DATE
READING_ID Readings unique identifier NUMBER NOT NULL
READING Reading Level DATE NOT NULL

File name: Remote Metering Database Project

Page 11 of 9
Last saved: 10/07/2010
Page 11 of 14

Ver.1
 REMOTE METERING DATABASE PROJECT

READING_DATE Date when reading is taken NUMBER NOT NULL

R_TYPE _ID Reading type NUMBER NOT NULL
METER_ID Id of the meter NUMBER NOT NULL

READING TYPES
COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINT
R_TYPE _ID Reading type unique identifier NUMBER NOT NULL
R_TYPE _NAME Reading type name VARCHAR2 NOT NULL
UNITS units VARCHAR2

UNITS
COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINT
UNITS _ID Unit identifier NUMBER NOT NULL
UNITS _NAME Unit name VARCHAR2 NOT NULL

7.0 SYSTEM REQUIREMENTS

NO. REQUIREMENT DEPARTMENT STATUS

1 Oracle 10 database software for windows IT Pending
2 Visual studio 2008 software IT Pending
3 Server space for the database IT Pending
4 Laptop IT covered

File name: Remote Metering Database Project

Page 12 of 9
Last saved: 10/07/2010
Page 12 of 14

Ver.1
 REMOTE METERING DATABASE PROJECT

8.0 PROJECT SCHEDULE

NO. MAIN TASK SUB TASK START DATE END DATE STATUS
Proposal writing 3rd may,2010 10th may,2010 Finished
1
Analysis and Business Analysis 11th May,2010 28th May, 2010 pending
Design Requirements Analysis 18th June,2010 25th June,2010 pending
System Analysis & Design 28th June,2010 9th July,2010 pending
Computing energy dispatches
and generate energy dispatches
Reports(per feeder, per district, 12th July 30th July pending
per region) and the exceptions
report
2 Development Validating UETCL sales report 9th Aug,2010 13th Aug,2010 pending
Data Uploading tool 16th Aug,2010 27th Aug,2010
User logon 6th Sept,2010 10th Sept,2010
User management 20th Sept,2010 24th Sept,2010 pending
th th
Passwords management 27 Sept,2010 30 Sept,2010
th
Reports module 4 Oct,2010 29th Oct,2010 pending
th th
Load profile graphs 4 Nov,2010 26 Ocy,2010 pending
th th
Help module 6 Dec,2010 10 Dec,2010 pending
Training User Manual pending
10th Jan,2011 14th Jan,2011
User training pending
th st
Testing User Acceptance Testing 17 Jan,2011 21 Jan,2011 pending
th th
Implementation Implementation 24 Jan,2011 4 Feb,2011 pending
Go live Go live 8th Feb,2011 pending

File name: Remote Metering Database Project

Page 13 of 9
Last saved: 10/07/2010
Page 13 of 14

Ver.1
 REMOTE METERING DATABASE PROJECT

9.0 APPENDIX
9.1. ABBREVIATIONS
• RMDS – Remote Metering Database System
• IT – Information Technology

File name: Remote Metering Database Project

Page 14 of 9
Last saved: 10/07/2010
Page 14 of 14

Ver.1