ACM copy.odt

7/26/2019 ACM copy.odt

1/73

Utility For Asset Code Modification

Team Members:

Dhruv Bhatt

[ID : 14MCM99] [Enroll. No. : 145303693005]

Nirali Thakkar

[ID : 14MC4!] [Enroll. No. : 1453036930!9]

Submitted to:

MC" D#$art%#nt&

'ar(ar )alla*h*hai +at#l In,titut# o- T#hnolo/& )a,a(.

Internal Guide External Guide

+ro-. u$a% 2u$ta Mr. "nant 'hah

",,i,tant +ro-#,,or 2I' #a(

MC" D#$art%#nt& Tata Con,ultan'#rvi#,&

')IT )a,a(. "l#%*i& Baro(a.


2/73

1. About The Organization


3/73

Company Name:Tata Consultancy Services Ltd.

CEO:Mr. Natarajan ChandrasekaranWebsite:www.tcs.com

Mission:

To help customers achieve their business objectives by providing

innovative, best-in-class consulting, IT solutions and services.

To make it a joy for all stakeholders to work with us.

About Company:

Founded by J.R.D. Tata in 1968, Tata Consultancy Services Limited (TCS) is a

multinational information technology (IT) service, consulting and business solutionscompany, headquartered in Mumbai, Maharashtra.

TCS operates in 46 countries and is a subsidiary of the Tata Group. It is the

largest Indian company by market capitalization and is the largest India-based IT

services company by 2013 revenues. There are more than 300,000 employees

currently working for TCS.

TCS is now placed among the Big 4 most valuable IT services brands

worldwide. TCS is ranked 40th overall in the Forbes World's Most Innovative

Companies ranking, making it both the highest-ranked IT services company and the

top Indian company.

TCS is a leader in the global marketplace and among the top 10 technology

firms in the world. The continued rapid growth of TCS is a testament to the

certainty their clients experience every day. Building on more than 40 years of

experience, they add real value to global organizations through domain expertise

plus solutions with proven success in the field and world-class service.


4/73

Products and Services:

TCS and its 59 subsidiaries provide a range of information technology-related

products and services including application development, business process

outsourcing, capacity planning, consulting, enterprise software, hardware sizing,

payment processing, software management and technology education services.

2. Project Abstract


5/73

Asset Code Modification is one of the utility of GIS (Geographic

Information System) module which is under in RAPDRP Project. R-

APDRP stands for Reformed Accelerated Power Development and Reform

Programme.

The R-APDRP program will cover urban areas-towns and cities withpopulation of more than 30,000.DISCOM under R-APDRP

1. Paschim Gujarat Vij Co.Ltd(PGVCL)

2. Madhya Gujarat Vij Co.Ltd(MGVCL)

3. Dakshin Gujarat Vij Co.Ltd(DGVCL)

4. Uttar Gujarat Vij Co.Ltd(UGVCL)

The DISCOM supplies electricity to all categories of users be they be

domestic, non domestic, small / medium / large industrial oragricultural consumers.

The power distribution set up has large & complex distribution network

infrastructure which carries the energy from the power sub stations

(33/11 KV) through the HT and LT lines up to the consumers premises

and in order to operationalize this DISCOM has huge human work.


6/73

Due to various reasons the technical and commercial losses that occur

in the supply of electricity effects the financial health of the DISCOM

severely. So,to overcome these type of losses GIS is very useful.

GIS issystem designed to capture, store, manipulate, analyze, manage, and

present all types of geographical data. Under GIS module we develop one

utility which isAsset Code Modification(ACM).These utility is developed to

facilitate the end user to reduce the logical gap of Asset code between Old

Feeder network and bifurcated feeders network.

We provide the new code for each electrical asset such as HT Lines, LT Lines,

Pole, DPD, Tapped Lines etc, which is beneficial in pole painting and

identification of owner of particular asset.

Asset Code Modification utility is used by DISCOM's Network Engineer and

Junior Engineer.

3. Description of

Project


7/73

3.1 Project Overview

Introduction

The Government of India in 10th Plan started Accelerated Power development


8/73

and reforms program for reforms in distribution with following objectives:

Reduction of AT&C losses

Bring about commercial viability

Reduce outages & interruptions

Increase consumer satisfaction

The Govt. of India has proposed to continue R-APDRP during the XI Plan with

revised terms and conditions as a Central Sector Scheme. The focus of the program

shall be on actual, demonstrable performance in terms of sustained loss reduction.

Establishment of reliable and automated systems for sustained collection of accurate

base line data and the adoption of Information Technology in the areas of energy

accounting will be essential before taking up the regular distribution strengthening

projects.

Programme Coverage

It is proposed to cover certain high-load density rural areas with significant

loads, works of separation of agricultural feeders from domestic and industrial ones,

and of High Voltage Distribution System (11kV) will also be taken up.

Further, towns / areas for which projects have been sanctioned in X Plan R-

APDRP shall be considered for the XI Plan only after either completion or short

closure of the earlier sanctioned projects.


9/73

Proposed Scheme

Projects under the scheme shall be taken up in Two Parts. Part-A shall include

the projects for establishment of baseline data and IT applications for energy

accounting/auditing & IT based consumer service centers. Part-B shall include

regular distribution strengthening projects. The activities to be covered under each

part are as follows:

Part - A:

Preparation of Base-line data for the project area covering Consumer Indexing,

GIS Mapping, Metering of Distribution Transformers and Feeders, and Automatic

Data Logging for all Distribution Transformers and Feeders and SCADA / DMS

system (only in the project area having more than 4 lacs population and annual

input energy of the order of 350 MU).

It would include Asset mapping of the entire distribution network at and below

the 11kV transformers and include the Distribution Transformers and Feeders, Low

Tension lines, poles and other distribution network equipment. It will also include

adoption of IT applications for meter reading, billing & collection; energy accounting

& auditing; MIS; redressal of consumer grievances; establishment of IT enabledconsumer service centers etc. The base line data and required system shall be

verified by an independent agency appointed by the Ministry of Power.

Part - B:

Renovation, modernization and strengthening of 11 KV level Substations,

Transformers/Transformer Centers, Re-conductoring of lines at 11kV level and

below, Load Bifurcation, feeder separation, Load Balancing, HVDS (11kV), Aerial

Bunched Conductoring in dense areas, replacement of electromagnetic energy

meters with tamper proof electronics meters, installation of capacitor banks andmobile service centers etc. In exceptional cases, where sub-transmission system is

weak, strengthening at 33 KV or 66 KV levels may also be considered.

Modules: Meter Data Acquisition System ( MDAS )

Energy Audit

GIS based Customer Indexing & Asset Mapping ( GIS )


10/73

GIS based integrated Network Analysis ( NA )

Customer Relationship Management ( CRM )

Management Information System ( MIS )

Meter Data Management ( MDM )

Identity and Access Management System

System Security Requirement Billing

Data Center:Vadodara, Gujarat

Disaster Recovery Center:Pune, Maharashtra

Project Area:84 towns


11/73

3.2 Geographic Information System ( GIS )

A Geographic Information System (GIS) is identification of all network

components & every consumer with geographical reference and their relationship

availability of information at the click of mouse.

A GIS can be thought of as a system it digitally creates and "manipulates"

spatial areas that may be jurisdictional, purpose, or application-oriented. Generally,

a GIS is custom-designed for an organization. Hence, a GIS developed for an

application, jurisdiction, enterprise, or purpose may not be necessarily interoperable

or compatible with a GIS that has been developed for some other application,

jurisdiction, enterprise, or purpose. What goes beyond a GIS is a spatial data

infrastructure, a concept that has no such restrictive boundaries.

In this project, GIS technology is a fundamental requirement to have a

managed electric network, which can help to establish the baseline data of all

bonafide consumers by door to door field survey of all consumers. GIS consists of

Asset Mapping, Consumer Indexing, and Route Sequencing of consumers with

respect to the Poles, DTRs, HT Feeders, HT Substation, Division, Circle & DISCOM.

Asset mapping of the entire Distribution Network up to consumers energy

meters will help the DISCOMs to monitor and reduce losses across the Distribution

Network. Adoption of GIS technology and its integration with other applications for

Meter Reading, Billing and Collection to get more accurate and timely data for

Energy Accounting and it will play a key role to help in management, technical andcost estimation discussion for the Electricity Board.


12/73

3.3GIS Utility Tool

There is utility tool developed for the GIS module in this project which is Asset

Code Modification.

Key Features Of Asset Code Modification:

i.Auto generation of new asset codes for bifurcated feeder.

The new functionality developed for feeder bifurcation will generateasset codes for the bifurcated feeder automatically(monitoredunder GIS expert supervision).

The following figure shows the network before bifurcation, thehighlighted part(bifurcated) is the network that will be affected.Initially, the highlighted bifurcated network is connected toFeeder XYZ and has asset codes as per that feeder.


13/73

[Network Before Bifurcation]

After bifurcation, the highlighted bifurcated network is now connected to

PQR Feeder and the asset codes will be as per its parent feeder which is

now PQR Feeder. The following figure shows that.


14/73

[Network After Bifurcation]

This is a basic overview of Asset Codification .It also involves asset

codification of

Low Tension Lines/LT Poles. These changes in asset codes after

bifurcation will be done automatically.

ii.Lesser Resources and Manual efforts

Changing of asset codes after bifurcation is a tedious task. In present

scenario,process of changing asset codes takes approximately1-2 months

or more with extra resources and processeswhich is very high

and complex.

But, with this functionality new asset codes for the bifurcated feeder will

be generated under GIS expert supervision with less efforts, time

and complications.

iii.Old Parent Feeder not affected

The old feeder will not be affected by feeder bifurcation. That is, the

asset codes and sequencing of the old feeder will not change , this will

save the client from repainting that feeder.


15/73

iv.Easy Identification of an asset in the network

As this utility generates new asset codes of the bifurcated feeder, it will

be of great use for end user or line man who can identify , to which

feeder a particular asset belongs, because after bifurcation an asset

belonging to one network is shifted to another. Hence it will be easy inidentifying asset, in case of a fault or defect.

v.Pole Painting process simplified

Till now there was no provision for updation of asset codes for the

bifurcated feeder through utility, hence there are many feeders for

which pole painting/repainting is pending. However now by the help of

this utility painting of pole can be done by comparing Current and

New asset codes.

Assumption about Asset Code Modification:

i.No user should be working on affected Feeders/Networks.

One of the prerequisites of using this functionality is that, no user is

currently working on affected feeder or network. When another

user updates any asset in the same feeder/network and submits

the job, the work done in feeder bifurcation will get

affected,which in turn will affect asset code updation. Hence, to avoid any dataloss/mismatch, no user should be working on affected

feeder/network.

ii.Job Submission.

Submission of Jobs which belongs to affected Network/Feeder is

necessary, prior to asset code updation.

This solution considers master data(GIS Master version) as its base. Soall the Jobs(affected Feeders) needs to be Posted/Submitted

to Master data prior to Asset codification . If not done then there is a

possibility that the sequencing of assets will be out of order.

iii.Network Tracing.

Its is mandatory that the Network/Feeder participating in the process


16/73

must be traced before hand. As the process runs on the basis of

tracing and any network asset not traced will be left out of the process. Any

changes done in network/asset code will not be reflected in that asset.

So before starting the process, one should ensure entire network is

properly traced.

iv.Sequencing and Modification.

Asset codes of all the poles, DTRs and Lines of the bifurcated network

will be changed as highlighted in the figure.

[Sequencing and modification]


17/73


18/73

4.1 Requirement Analysis

Functional Requirements:

In software engineering, a functional requirement defines a function of a

system or its component. A function is described as a set of inputs, the behavior,

and outputs that define what a system is supposed to accomplish.


19/73

The tool should be able to:

1.Modify the asset codes of HT Lines, LT Lines, Poles, Tapped Line,

DTR etc.

2.Identify foreign lines and poles.

3.Share modified data with NA(Network Analysis).

4.Identify DPD for given feeder.

5.Makes Pole Painting process simple.

6.Easy Identification of an asset in the network.

Non-Functional Requirements:

A non-functional requirement, specifies criteria that can be used to judge the

operation of a system rather than specific behaviors. This should be contrasted with

functional requirement that defines specific behavior or functions.

1.Ease of Use:

The functionality should have a user friendly interface. The user

interface must be familiar to users, and so may need to follow a single

set of rules consistent with those of the operating system, or other

mainstream applications.

2.Reliability:

It should specify the ability of a system to perform its required functions

under stated conditions and the capability of the system tomaintain its performance over time.

3.Extensibility:

The system's ability should be such that the new functionality can be

extended, in which the system's internal structure and data flow

are minimally or not affected.

4.Accuracy:

The system should be able to store and retrieve all the records from

database accurately.

5.Efficiency:

The efficiency partly depends on the hardware and software

configuration of the computer where the software will be

deployed. The software should be able to serve for all inputs by the

user.


20/73

6.Performance:

The performance constraints should specify the timing characteristics of

the system. Certain tasks or features are more time-sensitive than

others.

Software Requirements:

Front End Microsoft Visual Studio

Back End Oracle 11g

Documentation Open Office Writer/Microsoft Word

Designing E-Draw and Paint

Project Schedule:

Task Start Date End Date

Learning and

Understanding of

Technology

24thDecember,2015 11thJanuary,2016

Requirement

Understanding

14thJanuary,2016 17thJanuary,2016

Designing and

Implementation

18thJanuary,2016 22ndMarch,2016

Testing 26thMarch,2016 29thMarch,2016

Documentation 1stApril,2016 11thApril,2016

Final Review of Project 12thApril,2016 15thApril,2016

System Development Methodology:

Types of Models:

1.Waterfall Model

2.V-Model

3.Spiral Model

4.Incremental Model

5.Iterative Model

6.Prototype Model


21/73

7.Evolutionary Model

In this project, We have usedIterative Model.

In Iterative model, iterative process starts with a simple implementation

of a small set of the software requirements and iteratively enhances the evolvingversions until the complete system is implemented and ready to be deployed.

An iterative life cycle model does not attempt to start with a full

specification of requirements. Instead, development begins by specifying and

implementing just part of the software, which is then reviewed in order to identify

further requirements. This process is then repeated, producing a new version of the

software at the end of each iteration of the model.

Iterative Model design:

Iterative process starts with a simple implementation of a subset of the

software requirements and iteratively enhances the evolving versions until the full

system is implemented. At each iteration, design modifications are made and new

functional capabilities are added. The basic idea behind this method is to develop a

system through repeated cycles (iterative) and in smaller portions at a time

(incremental).

Following is the pictorial representation of Iterative and Incremental

model:


22/73

Iterative and Incremental development is a combination of both iterative

design or iterative method and incremental build model for development. "During

software development, more than one iteration of the software development cycle

may be in progress at the same time." and "This process may be described as an

"evolutionary acquisition" or "incremental build" approach."

In incremental model the whole requirement is divided into various

builds. During each iteration, the development module goes through the

requirements, design, implementation and testing phases. Each subsequent release

of the module adds function to the previous release. The process continues till the

complete system is ready as per the requirement.

The key to successful use of an iterative software development lifecycle is

rigorous validation of requirements, and verification & testing of each version of the

software against those requirements within each cycle of the model. As the software

evolves through successive cycles, tests have to be repeated and extended to verify

each version of the software.


23/73

5. Tools & Technologies


24/73

5.1 The .NET Framework

The .NET Framework is a technology that supports building and

running the next generation of applications and XML Web services. The .NET

Framework is designed to fulfill the following objectives:

To provide a consistent object-oriented programming environment whether

object code is stored and executed locally, executed locally but Internet-

distributed, or executed remotely.

To provide a code-execution environment that minimizes software deployment

and versioning conflicts.

To provide a code-execution environment that promotes safe execution of code,

including code created by an unknown or semi-trusted third party.

To make the developer experience consistent across widely varying types of

applications, such as Windows-based applications and Web-based

applications.

To build all communication on industry standards to ensure that code based

on the .NET Framework can integrate with any other code.

5.2 C# Language

C# is an elegant and type-safe object-oriented language that enables

developers to build a variety of secure and robust applications that run on the .NET

Framework. You can use C# to create Windows client applications, XML Web

services, distributed components, client-server applications, database applications,

and much, much more.

C# syntax is highly expressive, yet it is also simple and easy to learn. As

an object-oriented language, C# supports the concepts of encapsulation,

inheritance, and polymorphism. All variables and methods, including the Main

method, the application's entry point, are encapsulated within class definitions.


25/73

5.3 Oracle 11g

Oracle 11g Database helps customers lower IT costs and deliver a higher

quality of service by enabling consolidation onto database clouds and engineered

systems like Oracle Exadata and Oracle Database Appliance. It's proven to be fast,

reliable, secure and easy to manage for all types of database workloads includingenterprise applications, data warehouses and big data analysis.

5.4 Arc Geographic Information System(ArcGIS)

Esri's ArcGIS is a geographic information system (GIS) for working with maps

and geographic information. It is used for: creating and using maps; compiling

geographic data; analyzing mapped information; sharing and discovering geographic

information; using maps and geographic information in a range of applications; andmanaging geographic information in a database.

The system provides an infrastructure for making maps and geographic

information available throughout an organization, across a community, and openly

on the Web.

When working with geo databases, it is important to understand about feature

classes which are a set of features, represented with points, lines, or polygons. With

shape files, each file can only handle one type of feature. A geo database can store

multiple feature classes or type of features within one file.

Geo databases in ArcGIS can be stored in three different ways including as a

"file geodatabase", "personal geodatabase", and "ArcSDE geodatabase".

5.5 Arc Facilities Manager(ArcFM)

ArcFM is a powerful extension of ESRI's ArcGIS platform that provides a


26/73

complete, enterprise utility solution geared to the needs of utility end users. ArcFM

consists of a family of models and a set of sophisticated tools that provide a

comprehensive application for energy and water/wastewater utilities.

ArcFM allows maintenance and viewing of data, using company specific

business rules, and includes applications to configure the data models and tools to

work together. ArcFM takes advantage of industry standard architecture and

programming environments, an easy-to-use interface, and powerful cartographic

tools, giving utilities an optimized solution for the entire organization.

5.6 Arc Spatial Database Engine (ArcSDE)

ArcSDE technology is a core component of ArcGIS for Server. It manages

spatial data in a relational database management system (RDBMS) and enables it to

be accessed by ArcGIS clients. It is the technology that provides the framework to

support long transactions, which facilitates the versioned editing environment inmultiuser geo databases. The geodatabase is the primary data storage model for

ArcGIS; it provides a single central location to access and manage spatial data.

In ESRIs simple definition, versioning "is the mechanism that enables

concurrent multiuser geodatabase editing in ArcSDE geo databases." This is a good

place to start. Versioning is one of the true benefits of enterprise GIS because it

allows multiple users to be editing the same geographic area and even the same

database record at the same point in time. Each user edits the data within their own

version in the geo database and then ArcSDE provides the tools to merge those edits

into the master public version.

6. System Analysis & Design


27/73

6.1 Analysis


28/73

6.1.1 Context level Diagram:

[6.1.1 Context-Level Diagram of Asset Code Modification]


29/73

6.1.2 Use Case Diagram:


30/73


31/73


32/73


33/73


34/73


35/73


36/73


37/73


38/73


39/73

[6.1.2 System Use Case of Asset Code Modification]


40/73

[6.1.2 User Use Case of Asset Code Modification]


41/73

6.2 Design

6.2.1 Class Diagram:


42/73

[6.2.1 Class Diagram of Asset Code Modification]

6.2.2 Sequence Diagram:


43/73

[6.2.2 Sequence Diagram of Occupying License]

[6.2.2 Sequence Diagram of Fetch Pending Jobs]


44/73

[6.2.3 Sequence Diagram of Validate Feature]


45/73

[6.2.4 Sequence Diagram of Update Data Object]


46/73

[6.2.5 Sequence Diagram of Data Sharing with NA]

[6.2.6 Sequence Diagram of Release License]


47/73

6.2.3 Activity Diagram:

[6.2.7 Activity Diagram of Occupying License]

[6.2.8 Activity Diagram of Fetch Pending Jobs]


48/73

[6.2.9 Activity Diagram of Validate Features]


49/73

[6.2.10 Activity Diagram of Update Data Object]


50/73

[6.2.11 Activity Diagram of Sharing Data with NA]


51/73

6.3 Data Dictionary


52/73


53/73

7. Snapshots


54/73


55/73

[ Fig 7.2 : Screen of Asset Code Modification & select old/new feeder]

[ Fig 7.3 : Screen to select Subdivision Name & its feeder list]


56/73

[ Fig 7.4 : Screen of present & proposed asset code for selected Feeder]

[ Fig 7.5 : Screen to download pending job list ]


57/73

[ Fig 7.6: Screen for confirmation to consider date of asset code modification for tech-loss

report in MDM]

[ Fig 7.7 : Asset Code Modification Request is initialized & return job number ]


58/73

[ Fig 7.7 : job list ]

[ Fig 7.8 : Error generate when all inputs are null ]


59/73

8.Reports


60/73

A single report is generated at the conclusion of theAsset Code

Modification process.

The report gives detailed information about the old and the modified(new) asset

codes of :-1. Ht lines

2. Lt lines3. DTR 4. Poles

5. Tapped line

6. Consumer Index number

or a !i"en #ob t$at is retrie"ed rom t$e database.


61/73


62/73

9. Testing


63/73

9.1 Overview

Software Testing is the process used to identify the correctness,

completeness and quality of developed system. A test strategy is an outline that

describes the testing approach of the software development cycle. It is created to

inform project managers, testers, and developers about some key issues of the

testing process. This includes the testing objective, methods of testing new

functions, total time and resources required for the project, and the testing

environment.

Unit testing is a software testing method by which individual units of

source code, sets of one or more computer program modules together withassociated control data, usage procedures, and operating procedures, are tested to

determine whether they are fit for use. Intuitively, one can view a unit as the

smallest testable part of an application.


64/73

9.2 Test CasesTest Case ID:TC_ACM_01

Test Utility: Asset Code Modification

Module Name:GISTest Case Description:Verify the feature selection by user and send selected

feature data for processing, to carry out the asset code modification process.

Ste

p

No.

Test Step/ Action Expected Result Actual ResultSuccess/Failu

re

1

User enables Asset

Code ModificationJunction

Junction should

be visible.

Junction is

visible Success

2

Store Feeder Name

& subdivision name

into database

Data should be

insert into

database

Data inserted

into databaseSuccess

3

Retrieve User id,

Feeder id, Feeder

asset code & old

Feeder asset code

from database

Data should be

retrieve from the

database.

Data retrieved

from the

database.

Success

4 Find Pending jobs

Pending jobs

should be

retrieve from the

database.

Pending jobs

retrieved from

the database.

Success

5User Sends empty

data for processing

Error message

prompt.

Invalid Input

Error Message

Prompt.

Success

6 Update HT network

HT network

should be

updated.

HT network is

updated in

database

Success

7 Update DTRDTR should be

updated.

DTR is

updated in

database

Success

8 Update LT network

LT network

should be

updated.

LT network is

updated in

database

Success

% &pdate 'rom pole to 'rom Pole To Pole 'rom Pole To (u))ess


65/73

pole s$ould be updated.Pole is updated in

database.

1*&pdate Consumer index

no

Consumer index no

s$ould be updated.

Consumer index

no is updated in

database.

(u))ess

11 &pdate tapped lines

Tapped lines s$ould

be updated

Tapped lines are

updated inDatabase (u))ess

12Cal)ulate +e,

(e-uen)e

+e, (e-uen)es$ould be )al)ulated

stored in database.

+e, (e-uen)e is)al)ulated

stored in

database.

(u))ess

13&pdate /t$er 'eeder

pole

/t$er 'eeder pole

s$ould be updated.

/t$er 'eeder poleis updated in

database.

(u))ess

14 &pdate ne, (e-uen)e+e, (e-uen)es$ould be updated.

+e, (e-uen)e isupdated in

database.

(u))ess

15 Data s$are ,it$ +0L s$ould be send

to +0.

L is send to

+0.(u))ess

160ssi!n Completed #ob

to net,or en!ineer

Completed #ob

s$ould be assi!ned to

+et,or en!ineer.

Completed #ob is

assi!ned to

+et,oren!ineer.

(u))ess

1 I net,or not properl)onne)ted

Dis)onne)ted lines

,ill not appear innet,or tra)in! and

$en)e ,ill not be

modiied

0s expe)ted (u))ess


66/73

10. Future Enhancement


67/73

instead of modifying the asset codes of the entire network traced under

a particular feeder users can specify one or two endpoints and only change the asset

code of a particular sub-network by giving a range .


68/73


69/73

11. Bibliography


70/73

$ttp77edndo).esri.)om7ar)ob#e)ts7%.27ComponentHelp7esri8eometr

$ttp77$elp.ar)!is.)om7en7sd71*.*7ar)ob#e)ts9net7)omponent$elp7index.$tml

$ttp77,,,.sspinno"ations.)om7blo!72*117*67*17"ersionin!:dummies:part:1.$tml

$ttp77,eb$elp.esri.)om7ar)!isser"er7%.37dotnet7index.$tml

$ttp77resour)es.ar)!is.)om7en7$elp7main71*.17index.$tml

$ttp77,iipedia.or!7,ii70r)8I(
http://edndoc.esri.com/arcobjects/9.2/ComponentHelp/esriGeometry/IPolygon.htmhttp://help.arcgis.com/en/sdk/10.0/arcobjects_net/componenthelp/index.htmlhttp://www.sspinnovations.com/blog/2011/06/01/versioning-dummies-part-1.htmlhttp://webhelp.esri.com/arcgisserver/9.3/dotnet/index.htmlhttp://resources.arcgis.com/en/help/main/10.1/index.htmlhttp://wikipedia.org/wiki/ArcGIShttp://edndoc.esri.com/arcobjects/9.2/ComponentHelp/esriGeometry/IPolygon.htmhttp://help.arcgis.com/en/sdk/10.0/arcobjects_net/componenthelp/index.htmlhttp://www.sspinnovations.com/blog/2011/06/01/versioning-dummies-part-1.htmlhttp://webhelp.esri.com/arcgisserver/9.3/dotnet/index.htmlhttp://resources.arcgis.com/en/help/main/10.1/index.htmlhttp://wikipedia.org/wiki/ArcGIS


71/73

12. Glossary


72/73

12.1 Terminologies

Terms Terminology

TCS TATA Consultancy Services

R-APDRPRestructured Accelerated Power Development &

Reforms Programme

GIS Geographic Information System

NA Network Analysis

DISCOM Distribution Company

DTR Distribution Transformer


73/73

Documents

ACM copy.odt