Remote Metering Project

8/8/2019 Remote Metering Project

1/14


2/14

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


3/14


1.0 INTRODUCTION

Accurate and reliable reporting is a key aspect in todays 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 necessarygraphical representations.

d) Administrative tools: Allow creation and management of users in the systemincluding assignment of user rights and privileges

e) Search capabilities, e.g. Users should be able to search information for a givenfeeder by say using the feeder name.

File name: Remote Metering Database Project

Page 3 of 9


Page 3 of 14

Ver.1


4/14


4.0 USER REQUIREMENTS

f) The system should validate the cumulative import readings with the individualregisters 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 tothe energy reported by Network control department.

k) The system should accept load profile reports from meters and generate graphsshowing 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


Page 4 of 9


Page 4 of 14

Ver.1


5/14


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 databaseb) 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 substationto another.

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

Cumulative Import:- sum of all the incoming usages recorded by the meter on afeeder.

Cumulative Export: - sum of all the outgoing usages recorded by the meter on afeeder.

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


Page 5 of 9


Page 5 of 14

Ver.1


6/14


5.3. DATA FLOW DIAGRAM

BULK METER

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)

Cum. Import Cum. Export Varh R1 R2 R3 R4 R6 R7 R8 R9

NETWORK CONTROL

UETCL sales reports

METERINGDEPT

BILLING DEPT

Energy dispatches report Energy loss report Exceptions Report UETCL Report

Energydispatches report

LOSS REDUCTIONDEPT

Exceptions Report


Page 6 of 9


Page 6 of 14

Ver.1


7/14


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


Page 7 of 9


Page 7 of 14

Ver.1


8/14


6.2. ENTITY RELATIONSHIP DATABASE MODEL

REGION

PK REGION_ID

REGION_NAME

DISTRICT

PK DISTRICT_ID

DISTRICT_NAMEREGION_ID

SUBSTATIONS

PK SUBSTATION_ID

SUBSTATION_NAMELOCATIONCOMPANY_IDMETER_IDREGION_ID

FEEDERS

PK FEEDER_ID

FEEDER_NAMEMETER_IDVOLTAGEFEEDER_TYPEDISTRICT_IDSUBSTATION_IDLOCATION

READINGS

PK READING_ID

READINGREADING_DATEREADING_TYPEMETER_ID

Has

Feeds

Has

1:*

1:*

1:*

1:*

METERS

PK METER_ID

METER_NOMETER_MAKEMETER_TYPE

Has

Has

Supplies

Has

1:*

1:1

1:*

OFFICES

PK OFFICE_ID

OFFICE_NAMEDISTRICT_ID

Has

1:*

TRANSFORMERS

PK TRANSFORMER_ID

TRANSFROMER_NAMEMETER_IDVOLTAGEDISTRICT_IDFEEDER_IDLOCATION

1:* B e

l o n g s t o

1:1


Page 8 of 9


Page 8 of 14

Ver.1


9/14


6.3. DATA DICTIONARY

REGIONS

COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINTREGION_ID Unique id of region NUMBER PKREGION_NAME Name of region VARCHAR2 NOT NULL

DISTRICTS

COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINTDISTRICT_ID Unique id of district NUMBER PKDISTRICT_NAME Name of district VARCHAR2 NOT NULL

REGION_ID Id of region VARCHAR2 FK

OFFICES

COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINTOFFICE_ID Unique id of district NUMBER PKOFFICE_NAME Name of district VARCHAR2 NOT NULLDISTRICT_ID Id of region VARCHAR2 FKFEEDER_ID

SUBSTATIONSCOLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINTSUB_ID Unique identifier of substation NUMBER PKSUB_NAME Name of the substation VARCHAR2 NOT NULLSUB_TYPE_ID Substation type NUMBER NOT NULLLOCATION Address of the substation VARCHAR2 NOT NULLMETER_ID Substation meter NUMBER FKCOMPANY_ID Company owning the substation NUMBER NOT NULLDISTRICT_ID Substation region NUMBER FK

SUBSTATION_TYPESCOLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINTSUB_TYPE_ID substation type unique identifier NUMBER PKSUB_TYPE_NAME substation type name VARCHAR2 NOT NULL


Page 9 of 9


Page 9 of 14

Ver.1


10/14


FEEDERS

COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINTFEEDER_ID Feeder unique identifier NUMBER PKFEEDER_ NAME Name of feeder VARCHAR2 NOT NULLVOLTAGE Size of feeder eg 11 kv or 33 kv NUMBER NOT NULLREGION_ID Region where feeder is located VARCHAR2 NOT NULLMETER_ID Feeder meter NOT NULLSUB_ID Substation to which feeder is connected NUMBER NOT NULLF_TYPE_ID Feeder type Number NOT NULL

TRANSFORMER

COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINTTRANS_ID Transformer unique identifier NUMBER NOT NULLTRANS_NAME Name of transfromer VARCHAR2 NOT NULLADDRESS NUMBER NOT NULLDISTRICT_ID District where transformer VARCHAR2 NOT NULLMETER_ID Transformer meter

FEEDER TYPES

COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINTF_TYPE_ID Reading type unique identifier NUMBER NOT NULLF_TYPE_NAME Reading type name VARCHAR2 NOT NULL

COMPANIES

COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINTCOMPANY_ID Company unique identifier NUMBER NOT NULLCOMPANY_NAME Company name VARCHAR2 NOT NULL

METERS

COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINTMETER_ID Meter unique identifier NUMBER NOT NULLMETER_NO Meter number VARCHAR2 NOT NULLM_TYPE_ID Meter type VARCHAR2 NOT NULLLEVEL_ID Meter Level

FEEDER CATEGORIES

COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINTCAT_ID Category unique identifier NUMBER NOT NULLCAT_NAME category name VARCHAR2 NOT NULL


Page 10 of 9


Page 10 of 14

Ver.1


11/14


12/14


READING_DATE Date when reading is taken NUMBER NOT NULLR_TYPE _ID Reading type NUMBER NOT NULLMETER_ID Id of the meter NUMBER NOT NULL

READING TYPES

COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINTR_TYPE _ID Reading type unique identifier NUMBER NOT NULLR_TYPE _NAME Reading type name VARCHAR2 NOT NULLUNITS units VARCHAR2

UNITS

COLUMN_NAME DESCRIPTION DATA TYPE CONSTRAINTUNITS _ID Unit identifier NUMBER NOT NULLUNITS _NAME Unit name VARCHAR2 NOT NULL

7.0 SYSTEM REQUIREMENTS

NO. REQUIREMENT DEPARTMENT STATUS1 Oracle 10 database software for windows IT Pending

2 Visual studio 2008 software IT Pending

3 Server space for the database IT Pending4 Laptop IT covered


Page 12 of 9


Page 12 of 14

Ver.1


13/14


8.0 PROJECT SCHEDULE


Page 13 of 9


Page 13 of 14

Ver.1

NO. MAIN TASK SUB TASK START DATE END DATE STATUS

1 Analysis andDesign

Proposal writing 3rd may,2010 10th may,2010 FinishedBusiness Analysis 11th May,2010 28th May, 2010 pendingRequirements Analysis 18th June,2010 25th June,2010 pendingSystem Analysis & Design 28 th June,2010 9 th July,2010 pending

2 Development

Computing energy dispatches

and generate energy dispatches

Reports(per feeder, per district,

per region) and the exceptions

report

12 th July 30 th July pending

Validating UETCL sales report 9 th Aug,2010 13 th Aug,2010 pending

Data Uploading tool 16 th Aug,2010 27 th Aug,2010User logon 6 th Sept,2010 10 th Sept,2010

pendingUser management 20 th Sept,2010 24 th Sept,2010

Passwords management 27 th Sept,2010 30 th Sept,2010

Reports module 4 th Oct,2010 29 th Oct,2010 pending

Load profile graphs 4 th Nov,2010 26 th Ocy,2010 pending

Training

Help module 6 th Dec,2010 10 th Dec,2010 pending

User Manual10 th Jan,2011 14 th Jan,2011

pending

User training pending

Testing User Acceptance Testing 17 th Jan,2011 21 st Jan,2011 pending

Implementation Implementation 24 th Jan,2011 4 th Feb,2011 pendingGo live Go live 8 th Feb,2011 pending


14/14


9.0 APPENDIX9.1. ABBREVIATIONS

RMDS Remote Metering Database System IT Information T e chnolo g y


Page 14 of 9


Page 14 of 14

Documents

Remote Metering Project