Document Sample
GIS RFP Powered By Docstoc

The draft specifications for proposed GIS / GPS based sof
***(The APCPDCL management has right to change the specification at any point of ti

1   The scope of work.

    The scope of work would entail:

    1        Supply of Open GIS 1            Supply of open GIS software - Software confirming to
             software,     application       Open GIS standards
             customization, training & 2     Development/ customization of application software as
             annual maintenance of           per the Terms of Reference („TOR‟) i.e. Energy Audit,
             software.                       Asset Management, Network Analysis, etc.

                                         3   Implementation of GIS System using data furnished in
                                             open GIS files and customer indexing in database etc.,
                                             confirming to TOR. The activities will have to be
                                             conducted for certain pre-selected division . Please
                                             note that the customer indexing data and the GIS maps
                                             will be provided by the APCPDCL and the selected
                                             vendor will be required to interact/ co-ordinate with the
                                             other agency for integration with the GIS application

                                         4   Training for the client‟s personnel on the application

                                         5   Annual maintenance of software for 3 years

    Details of the services required and the scope of work for the bidder will be provided after the
    time of Pre-bid conference.

2       Information to Bidders

2.1.1   Eligibility Criteria:

        The Client desires that bidders who meet the following eligibility criteria should Participate in
        pre-bid for this Project:

        .   The invitation to pre-bid is open only to the reputed and experienced computer
        software companies in the field of carrying out GIS work in India having facilities
        and capabilities for comprehensive maintenance & support during and after
        warranty period. The company must should undertaken/executed atleast 3
        Electricity utility related projects in India or Abroad during last Three years.
            1. The bidder should have adequate experience in the field of software
               development and systems integration. The bidder must have at least CMM
               LEVEL 5 Certification.
            2. The bidder should have executed/in process of execution at least 3 orders of
               for electricity distribution company in the area of GIS & consumer indexing
            3. The bidder should have at least 200 GIS workstations and 300 GIS
               professionals with infrastructure facilities available to perform the
               assignment properly and expeditiously within the time period specified. The
               evidence shall consist of written details of the installed infrastructure
               facilities and present commitments (excluding the assignment under this
               specification) of the Bidder.
            4. The bidder should be able to demonstrate at least two instances of GIS
               implementation for a Power Utility, in India or Abroad. Failure to provide
               proof will invite immediate disqualification of the concerned bid.
            5. Bidder must be ISO 9001:2000 certified. The Bidder should follow SEI CMM
               level      5     procedures     for    software      development/customisation
               appropriate certification should be enclosed.

        Bidder should have the necessary infrastructure with at least 100 GIS workstations
        with relevant peripherals

        Preference will be given to turnkey solution providers who can undertake supply &
        installation of required hardware and software as well as carryout the services for
        land based map creation and Electric network capture.

        The company should have sufficient experience and infrastructure in conducting
        training program necessary certificates should be enclosed.

        The company should have at least 50 skilled GIS experts with at least 10 of them
        should have Electrical engineering background whose CV with name and
        qualifications shall be given.

2.1.2   Key considerations
        The following key points are to be noted during the scope of this segment –

           The vendor is required only to customise an COTS GIS application/package of
            INTERNATIONAL repute and use and under no circumstance should it involve
            any fresh/ground-up development of the software

           The principle software developer should be a Member of the Open Geospatial
            Consortium Inc. (OGC) and should take undeniable lead in supporting
            interoperable solutions that “geo-enable” mainstream IT and affirms its strong
            commitment to open geospatial interoperability. Licence requirement for the

              Note:- The bidder should not be black-listed or having been invoked bank guarantee in any
              of the power sector in India .

          If the bidder chooses to enter into a consortium arrangement, the lead bidder must be
          identified and must satisfy all the eligibility criteria mentioned in 2.1.1 above.   Technical Proposal

2.2       Project name, objective and other details

             Name of the Project: Supply of GIS Software, application development/ Customization,
              integration with the GIS maps and databases, implementation and training etc., for
             Objectives and the description of the Project: As detailed in the attached Terms of
             The project should also cover the following details:

          Sl. No.      Particulars

                       Mapping & Documentation of Distribution Network and
                       Existing Customers

          2            Database of Electrical Network

                       Ability to segregate customer‟s feeder wise and Distribution
                       Transformer wise

                       Load Flow studies of 33 KV, 11 KV and LT Network

          5            Generation of single line diagrams

          6            Version management feature of Software

                       Integration with billing system and outage management

                       Integration with SCADA and network analysis software

2.2.1   Technical specifications of the GIS software
        Following are the technical requirements for the proposed solution. The criticality
        column (Cr) indicates the importance of each parameter as per the following:

        V- Vital; E – Essential; D – Desirable

        The system must incorporate current technologies and open-systems components
        that are commercially available for both software and hardware computing systems.
        The intent is to use the standard Intel PC platform for all hardware, the Microsoft
        Windows XP/2000 software as the operating system, and a standard commercial
        relational database system (RDBMS), Oracle. It is expected that the system will be
        based on commercial off-the-shelf (COTS) application products, instead of a custom
        solution, built just for CCPDCL. Client/Server system architecture is (Vital). The
        Windows XP/2000 operating system must be used on every computing node within
        the proposed system.

        CPDCL wants a common database across the entire system. The intent is to acquire,
        learn, and administer a single database, such as Oracle, across the entire system.

        The proposal should clearly define how the proposed system satisfies CPDCL’s
        requirements.   This Request For Proposal (RFP) states the scope of the
        requirements and specifies the general rules for preparing the proposal.


              The System should allow easy integration with the Electric industry’s
               implementation of Enterprise Resource Management (ERP) solutions. (Vital)

              The system should use a single, Relational database for storing all geospatial
               data, including spatial data, attribute data and Metadata/configuration data.
               The system should allow application configuration through the extensive use
               of metadata.

              The system should support creation and editing of landbase and related
               geographic information and support Geospatial analysis. (Vital)

              Should support distribution of the data model via Intranet and thin client
               applications (Vital)

              The system should use the native OLE/COM object model and automation.

              The system should incorporate Dynamic display Cache technology (DDC) for
               fast display, while maintaining complete use of underlying relational
               database system for transaction management. (Vital)

              System should provide tools for landbase backgrounds in raster Orthoimage
               format from aerial photography or satellite imagery so that the system will
               automatically turn raster images on and off as the user moves around the
               service territory. (Vital)

              Reporting should be configured into the metadata, thus eliminating the need
               for each user to redefine the report and standardize the reports for easy
               availability on user request. (Vital)

WEB Enabling & Integration
System should support the easy web enabling of the enterprise data
The web solution should have ease of administration,           without   extensive
customisation It should have a      Single "geo-centric" interface that links all
information, reports, documents and produces it on a map in a simple user interface
across technologies and platforms. It should maximize deployment flexibility by
making this interface web-based

The Web solution must provide the following functionalities

      Facility to create Web enabled maps and browser components.

      End users should be able to access the GIS data through standard Web
       browsers such as Microsoft Internet Explorer and Netscape Navigator.

      Vector based smart map capability.

      Facility for clients to make simple spatial queries.

      Facility for clients to browse GIS information in real-time.

      The software should operate just like all other familiar Windows based tools.

      Should allow users to combine data from different sources on a single map
       (for example, allow end users to retrieve data from a utilities database and a
       land-use data base, and display them together in a map.

      Each feature in the smart map should know which, database to search for it’s
       attribute information.

      Automatic publishing of intelligent maps on the Web, in response to end-user
       queries, once the feature-database relationship is defined.

      ALLOW users to use these above data server seamlessly from any
       combination of these sources into a single output map.
    Administration Tool

          -     Intuitive, No Programming

          -     Easily Configurable


    Security

          -     Attribute Based Security

          -     LDAP Active Directory

          -     Configuration Sets

    Multiple Languages Support

          -     Including Hindi & English

    Customizable User Interface

    Cascading Maps

    Multi-Level Join

          -     Link multiple data sources

           Map Tabs

           Measure

           Reporting

           Documents Viewer

           Link to any Web Pages or Web Applications

           Map Tips

          WEB Administration Tool -

          The administration tool should enable building sophisticated web GIS
          applications and publish GIS web services complete with full security and
          provision for multiple languages without writing large amount of code.

          The windows application based Administration Tool should be fully configurable
          to add layers, bring in data sources from different map providers and connect to
          any external databases or business systems.

          The Bidder should have extensive experience on application development using
          the basic software platforms proposed to be used and shall furnish details of his
          experience along with the bid.

          Application Architecture should provide a framework and the necessary
          programming interfaces to enable complex applications to be developed and
          integrated with applications that already exist within CPDCL

2.3   Pre-bid Conference date and address
      You can write to the following address for getting any clarifications. Any clarifications on this
      projects can also, be obtained during the pre-bid conference proposed to conduct at General
      Manager (IT) office on 6th October 2008 at 11.00Hrs.

      Address, General Manager (IT),,,Corporate office, CPDCL,IIIrd Floor, Singareni Bhavan

      Red Hills,,Hyderabad.,Phone: +91-040 – 23431086 / 23431287 Fax: +91-040 - 23431090, Cell
      phone 9440813911.

2.4   Project execution period
      Time is the essence of the work under this contract. The job should be completed within four (2)
      months from the date of issue of Letter of Intent („LOI‟). The bidder shall workout a detailed bar
      chart for each activity separately indicating the start & finish times of each activity along with
      the resources that he plans to deploy in each case and submit the same as a part of bid document.
      The detailed bar charts for all the work activity shall however, be discussed and agreed to by the
      successful Bidder with the client / owner before start of the execution of work.

  2.4.1         Work plan

                                                Week-wise Work plan (in form of Gantt Chart)
Serial No              Task
                                            1   2     3       4      5       6      7      …   N

   1        Supply and Installation of

   2        Porting of GIS maps,
            integration with customer
            indexing database etc.,

   3        Software Development        /
            GIS     Enablement          /
            Customization etc.,

   4        Report Generation / On-line

   5        Performing            User-
            Acceptance tests

   6        Any other, please specify

3     Term s of Reference

      Technical specification for GIS based software and application
      development with GIS maps and indexed customer database

3.1   Objectives
         The primary objective of this project is to enhance the efficiency of distribution system in
          terms of quality of power and increased revenue earning by reducing T & D losses (both
          technical and commercial), outages and to merge the factions of independent offices into the
          main stream operational hierarchy with the help of organization wide networking
         The project envisages the following:
          -   Developing/ customizing a GIS software application for integration of single line
              diagrams of the distribution network with updated customer related data and network
              attribute data for distribution planning, data analysis and reporting facilities
          -   The customer indexing data would be provided by the APCPDCL. The successful
              bidder would be required to interact with the agencies involved in collating this data for
              the purpose of integrating with the GIS application.
          -   GIS maps developed on GPS survey data (in any of the open GIS formats)of
              Transmission and Distribution network covering 33 KV sub-stations, 11KV feeders,
              distribution transformers will be provided by the APCPDCL for integration with the
              application software. The Bidder has to interact with the agencies involved in
              development of GIS maps for integrating with the GIS application.
         Training for the client‟s personnel on the application software and annual maintenance of
          software for 3 years will also be carried out by the selected vendor.

      The following schematic illustrates at a high level the key modules required and the areas where
       the modules are expected to play an important role:

                                                               •   Applications
                                                               •   Internal validations
                                                               •   Power supply arrangements
            New customer management
                                                               •   Cost estimates
                                                               •   Charges payable by the customer
                                                               •   Agreement formats, etc.

                                                               •   Load flow analysis
              Analysis, optimization                           •   Optimization studies
              planning and design of                           •   What if analysis
               distribution systems                            •   Load forecasting
                                                               •   Long term planning, etc.

                                                               •   Energy sales
                                                               •   Technical and commercial losses
            Energy audit and accounting
                                                               •   Customer vigilance
                                                               •   Reliability indices, etc.

                                                               • Asset database
                Asset Management                               • Outage management
                                                               • Maintenance management

        The key work-steps required include:
           Procurement of GIS maps data. This will be provided to the vendor by the APCPDCL.
           The APCPDCL will also provide the vendor with the customer index data.
           The vendor will be responsible developing/ customizing the application and for creating and
            updating the customer databases, single line maps/ diagrams, etc. as per the TOR.
        Please note that the vendor will be required to co-ordinate extensively with the other agencies
        involved with customer indexing data collection, etc. for integration with the application.

3.2     Exclusive Clauses

        The physical networking along with stabilized data communication links would be provided by
        Owner and would not be in the scope of work of the bidder. However, customization of data
        communication link for accessing through browser on internet/ intranet relevant to the
        application would be bidder‟s responsibility.

3.2.1   GIS application software should support:

           Creation of spatial data models using the Interactive tools which help creating the spatial
            (Map) database by creation of Entity-Relation diagrams
           Editing of spatial data (Map) by the different users simultaneously.
           Version Management of the spatial data. Changes/ updates made to the base line drawing
            should be tracked as different versions

         Ability to see the latest drawing on the system which should be union of all the changes
          made by all of the users/multiple users at same time on single work order and manage
          conflicts arising due to the merge / post of different versions.
         Must be highly scalable. (Should support the easy expansion of the system in future without
          the rebuilding)
         Must have Tiered Architecture.
         Must be easily Customizable to meet the end user requirements.
         Must be object-oriented GIS to have the following advantages:
          -   Application is faster
          -   Less expensive to develop
          -   Easy Maintenance
          -   The GIS should be able to support the Enterprise wise central database and remote users
              over the WAN and should be web enabled even for the creation and editing operations
              without degrading the performance over the net.
          -   Support seamless data access between applications, which allow information in existing
              systems to be used without a need for migration or translation, ensuring a maximum
              return on existing investment.

3.3   Internals
      The proposed system should have facility of representing internals. For example with a click of
      mouse on the substation user should be able to see internals of the sub station.

3.4   Land base information
      The proposed GIS system should support Land base information such as:
         Contours
         Spot Heights
         Street
         Campus
         Complex
         State Boundary
         District Boundary
         Distribution circle / Division boundaries
         Water bodies
         Building
         Address (Customer Location point)
         Associating Address to a structure or a Network Element (e.g. Associating Address to
          Electric pole etc.)

3.5   User defined land base objects
      The system should have facility for including the user-defined land base objects in the land base
      data model.

3.6   Structural/ network information
      The proposed GIS system should support Structural / Network information such as:
         Under ground Route
         Conduits
         Electric Cables
         Aerial Route
         Poles
         Man holes

3.7   Graphical representation
      System should allow the user to customize the graphical representation for each of entities/
      objects/ elements such as:
         Point
         Line
         Polygon
         Text
         Color
         Hash pattern
         Line style (Dashed, Dotted….)
         Font
         Point shape (Round, square, user defined…)

3.8   User defined attributes
      Attributes associated to each of the entity/object/element should be user definable
         Data type
         Length
         Access restriction
         Pull down list
         Mandatory / Optional
         Entities/Objects/Elements can exist without Attributes. E.g. Simple line, Simple point

3.9   Object representation
      User should be able to dynamically select one or more of the attributes of an object, to be
      displayed as label of the object. This can be for viewing, plotting and printing purposes.
         System should support representation of the Entities/Objects/ Elements in different colors
          based on the attribute criterion
         Should be able to display different objects at different scales. It should be a one-time
          definition as well as the user should be able to define it dynamically. Example, at 1:50000
          scale road network, state / district boundary, railways, water ways etc. and at 1:1000 scale
          only road network, water bodies, buildings, footpath etc.
         The system should have Dimensioning Capabilities

   Should be able to perform move, copy, rotate, mirror and offset
   Should specify the real time measurement / length while drawing the lines.
   Should be able to save and restore views / workspace / layouts.
   Support raster Images / scanned photographs
   Registration and rectification of both raster and vector data.
   The system should support WYSIWYG Plotting and Printing of graphical areas
   Placement of Own Legend, Scale, North Arrow and various Texts styles in plotting template.
   List the supported Plotters and Printers
   System should support Import / Export the data (E.g. Access, Excel, DXF, DWG, MIDI,
    MIF, TAB, E000, and DGN)
   List of formats for import/export to be provided
   The system should have facility for connecting the external databases such as Oracle so that
    the data from these RDBMS can be readily accessed without the need of importing it. Should
    also provide the data synchronization between the databases.
   Should be able to open / attach all standard format files like Visio, Power Point, Excel,
    DWG etc. for Schematic representation without importing into the GIS system.
   System should support User defined Reports.
   Customization of symbols should be possible.
   Should be able to define set of rules for the object connectivity (for example when Main road
    crosses a street the street should get separated into two which eliminates the necessity for
    drawing the streets twice)
   System should provide query builder and support multiple / complex SQL queries
   Should support Sorting, Filtering and display records in Tabular / Browser formats
   Should be able to save the queries as well as the output in text format.
   On Query, the system should be able to highlight the objects based on the user specified
    boundary or attributes for visualization
   The response of the system to queries in near and remote locations should be adequately fast
    to answer customers on the phone.
   User should be able to place the pointer at a desired location on the graphics window and get
    the X-Y-Z co-ordinates of the location
   GPS point recording directly to the map with Vendor specified utility.
   System should support the easy web enabling of the application.
   Should have security Authorization information such as login name, password
   Separate module for administration module required to Grant/revoke authorization to various
   The system should be available to customer care throughout round the clock.
   Reports runs and any other batch jobs should not affect system availability
   Context based and user friendly help should be available
   Help should be available at different levels: novice, expert etc
   Online tutorial should be available
   Online help through Internet must be available for queries.
   Enable high productivity, performance, user friendliness, user interface, and ease in

            Backup and Recovery module for managing the backup and recovery operations of the
            The GIS should have interface with Outage and Distribution Management system and the
             energy accounting, billing and revenue management system etc.,
            The GIS should have been developed using present day technology like C, C++, Java, etc.
            The software should be OS independent.

3.10     Additional features and capabilities of software system

3.10.1   Tracking changes

         Proper relationships shall be established in the database between the various entities. Further,
         hierarchical relationships should be established between various elements to link and group them
         at any voltage level. It should be possible to change the hierarchical parent of any element i.e.
         any element along with all its children in a hierarchical relationship can be made child of any
         other element. Such shifting should be possible only where voltage levels match. The time of
         making such changes shall be tracked. This arrangement would enable alternate feed
         arrangements during outage conditions to be accounted for automatically.

         The energy accounting software supported by the proposed customer indexed data base shall be
         able to recognize the transfer of any group of customers fed by any particular line to any other
         neighborhood / alternate line by switching of isolators or modification of jumpers during the
         operation, for the purpose of improving the availability of supply. To facilitate the above, all
         switching devices in the system shall be properly identified in the database. Such changes may
         also be effected due to system modifications such as addition of a new distribution transformer
         or additional line or a new substation. The software shall provide user-friendly screens for
         inputting the information for all manual switching operation carried out. The software shall also
         be capable of recognizing any automatic switching wherever provided at a later date.

         The database shall keep track of all such changes in any of the customer attributes such as
         change in name, connected load, tariff category, connection status, meter changes etc.

3.10.2   Codification

         Each of the entities in the database like Customer, LT pole, LT feeder, DT, 11 kV feeder, power
         transformers and substations shall have a unique identifier. The codification shall be carried out
         based on the utilities preferred practice described in Annexure-A.

3.10.3   Edge matching

            When the map sheets are mosaiced together the various sheets should be able to be matched
            The graticules on adjacent map sheets should match, both in terms of value of the graticules
             and continuity

3.10.4   Geometrical accuracy

            Every feature has to be captured accurately under the object classes.

            Orthogonal of the corners has to be maintained as it is
            Symbols have to be produced same as paper map
            Lines have to be captured accurately- and where ever bend is there arc elements should be
            Polygons should be captured accordingly

3.10.5   Positional Accuracy

            There should not be any displacement of the digital element from the GIS map provided by
             the APCPDCL.
            All features should be captured with respect to original position in paper map provided by
             the APCPDCL.
            Miscellaneous elements will be kept as it is in old position

3.10.6   Information Accuracy

            Every feature should be captured. No missing will be accepted.
            Digital image should be verified with paper map (Scanned Map in the Backdrop)

3.10.7   Data model for Data Conversion

         GIS Application Architecture („GAA‟) should provide a framework and the necessary
         programming interfaces to enable complex GIS applications to be developed and integrated with
         applications that already exist within the company. GAA should support the distribution of the
         functionality of a GIS application across a number of components, which should interact as
         separate processes via a process communication and control mechanism.

3.10.8   Residual discrepancies

         The residual discrepancies can be used to assess whether the rectification can be carried out
         correctly with the defined control points. The residual discrepancies on the x and y axes as well
         as the total discrepancy has to be listed for each control point. The residual discrepancies are
         acceptable if they are the same size as a pixel. The transformation can be carried out if the
         residual discrepancies are sufficiently small.

         If the errors are larger, individual incorrect control points should first be discarded or translated.
         Incorrect control point positions can be identified by their residual discrepancy being too large.
         This is also noticeable with neighboring control points. The further the distance from one control
         point to another, incorrectly entered, control point, the less the residual discrepancy. With binary
         data this is the only way of reducing the residual discrepancies. This completes the control point
         definition stage.

3.10.9   Rectify

         Rectification allows two images or one image and a map to be aligned geometrically.
         This is necessary to create an aerial or satellite image or if image data and a map are to be

3.10.10   Resampling Feature

          When rectifying gray-scale and true-color images, the rectified image is usually created
          indirectly, i.e. the position of each pixel in the distorted image is determined by the associated
          pixel in the rectified image. With this reverse calculation, it often happens that the calculated
          values are not integers and therefore do not refer to image point positions in the distorted image

          Digitization software should have the following re-sampling methods:

          1.     Nearest neighbor

          2.     Bilinear interpolation

          3.     Cubic interpolation

3.10.11   Other features

          The proposed geographical Information system should include the following-

              The system should provide a tool for user to digitize and capture the base map and electrical
               network information & make a seamless map database.
              The proposed system should capture different type of drawing such as Land base (cadastral
               maps). Existing data available by Owner‟s office in graphic and textual format should be
               transformed or converted into the proposed system.
              Proposed system is required to provide the facility to document the electric supply networks.
               The assets information is able to access by accounting, operations, maintenance and
               customer service application system via Owner‟s zonal offices Local Area Network („LAN‟)
               or Wide Area Network („WAN‟). For example, the entire recorded asset can be accessed by
               the financial system.
              All data should be structured by defined hierarchical attributes, many of which spatial, for
               access, retrieval or display of asset management information via a map-based medium. For
               example, the proposed system should have the capability to show the lengths and type of a
               cable need to replace in the next few months or whatever will be worth a mountain of written
              Proposed system is required to provide a feature for the planning engineer to design and plan
               a network. The system should be able to calculate the current consumption and estimated
               implementation cost for the plan network. Vast potential for such measures lies in optimizing
               the planning of supply networks with regard to equipment capacity utilization.
              Proposed system should be able to help the engineer to plan an optimization of power
               distribution to ensure the power demand in different zones continues to fulfill the need.

3.10.12   System features

          The proposed solution would be built with the following features: Land Base
          The land base shall be made intelligent. Various queries shall be made available for different
          geographic entities in a land base area of the owner‟s power network premises. Each geographic
          entity will contain a minimum of five to six attributes to carry the basic information like Name,
          Address, Zone, Service Number, Telephone Number, etc. if any. The software shall be able to
          build the topology on its own to ease this query process through the intelligence.

                                                                                                         17 Substation
         Substation is a building location at which various electrical accessories are connected together to
         serve the load centers. Following are the electrical equipment in a substation, which are normally
         installed and electrically connected.
            High Voltage (HV) Cables
            Isolators
            Transformers
            Fuse section pillars, LT Boards
            LV Cable feeders
            Bus couplers

         Other requirements are:
            The land base information shall be displayed on demand by just clicking on the substation
             diagram and the complete database of substation shall be displayed.
            The substation symbol library shall be made available to the users to enable them to select
             the type of substation and insert into the geographical base. The selected type of substation
             name and its details shall be displayed in the software Geo-client‟s toolbar always until the
             selection is replaced. This will be useful to identify the type of substation that is active in the
             selection list.
            There shall be user-friendly methods available in the software to define and integrate any
             new network symbols into symbol library.
            The substation‟s database should contain the details like Accommodation, History,
             Maintenance and Remark etc. These details shall also have to associate the electrical
             accessories details installed in the same premises.
            The electrical connectivity shall be established at all times between substation or from any
             nodes. It shall be linked so that the connectivity shall be checked at all times through the
             logical checks which is being performed by the software internally
            It shall be possible to edit the associated text for its presentation. This shall be achieved for
             the users with the proper security rights.
            During the placement of equipment, it shall be possible of being rotated, scaled and moved
             about its insertion point. The placement shall be assisted by a “rubber band” to assure a
             proper position.
            All of the electrical entities and accessories shall be identified by their name, geographical
             information of the substation in addition to their alpha-numerical database information of
             interest, which is associated with each items.
            An interactive tool like icons in a toolbar, graphical user interface (GUI) shall be available to
             enable the users to perform their graphics handling operations such as zooming, panning,
             highlighting, selection, clicking an item for its alpha-numerical details etc.
            The following information shall be queried using the user-friendly GUI by just selecting the
             category of the query. The results shall be made available in the graphics by highlighting
             them and/or in the non-graphical text report forms.
             -   Based on the connected load information which is fed from the substation
             -   List of customers based on the connected load
             -   History information of load readings of the transformer and outgoing LV distributor
                 cables etc.

            The selection criteria and query of a substation / transformers / cables / pillars/ joints / ducts/
             sleeves / manholes/ AD pillars/ Capacitors/ Switch Gear etc. may follow the patterns listed

             -   Name of the substation. This will enable to highlight the selected elements
             -   Name of the area of the substation
             -   Display of service numbers of the customer fed from the substation
             -   The entities located in the downstream of the substation
             -   Through a polygon retrieval i.e selecting a window area from the overview map, the
                 software shall highlight and retrieve all the substation
             -   The software shall highlight the respective substation by the geographical base query i.e.
                 substation located in a particular zone, substations located in a particular area

            The software shall be able to attach and retrieve any scanned image, video clips, sound files
             or any multi-media clippings to the substation.
            Following reports shall be made available after the non-graphics query:
             -   List of substation connected on a particular Feeder
             -   List of substation based on capacity of switchgears/transformers
             -   List of substation based on make of electrical entities
             -   List of substation based on breakdowns
             -   List of substation commissioned during the period of specified time.
            The software shall be able to compose the various types of cables with its technical
             information like type, material of the conductor, cross-section in the network cable symbol
             library. The list of cable type shall be available in the cable symbol library for selection in
             advance and for laying purpose in the field. The chosen cable type shall be displayed always
             in the geo-client‟s toolbar space until the selection is replaced. Cables and other electrical components

            During the selection process, there shall be a provision to set the runtime environment
             settings i.e. the geometry of the cable e.g. Line, Arc, Tangential Arc, Tangential Line and
             also the type of connection like Begin and End. The distance information shall be made
             available to enter in case of different cable laying path.
            All of the functions shall be available in terms of menu and/or toolbar icons.
            There shall be a provision to click on the existing laid cable in the field by a mouse button
             and to accept that cable type as the current one. This enables wherever the existing cable
             may be extended or continued.
            The software shall have the facility for maintaining the electrical attributes of the network
             like resistance/reactance of the lines, cables, ratings of the transformers, rating of breakers
            The software shall provide the facility to set the line spacing distance information while
             creating a parallel line to the existing line.
            There shall be some facilities to consider the cable laying procedures through the rounding
             lines tangentially or by specifying a radius. Icons shall enable the same. This facility will be
             used wherever the cable-laying route has any obstructions or restricted area
            The software shall have the mechanism to incorporate Loop-In-Loop-Out (LILO) facility in
             the existing cables. The network node symbol will be chosen earlier to use the same in
            The software shall include the facility to compose different types of cable for laying the
             multiple feeders at a stretch. The GUI can be used to make the composition of the type for
             multiple feeder cables. The GUI shall contain the facility to add, delete the cable type
             selection for multiple feeders along with the parameter of line spacing distance and cable

    alignment. In addition to this, editing facility of the individual cable line type shall be made
   The software shall carry out the multiple feeder cable laying procedure through simple icon
    clicks. It shall also have the facility to continue existing multiple feeder cables to another
    location. Similarly connecting two different multiple lines with proper selection of individual
    cables in the multiple feeders through a rounding way or by an arc.
   There must be very simple methods available to establish the edition of a transmission lines
    and/or distribution cables. The edition could be achieved as listed below:
    -   Drawing the two different end points of the feeder together by just clicking on to the end
        points of the feeder
    -   Connecting two different lines at an intersection point project from the same angle and
    -   Extending a single line by intersecting it with another line
    -   Unlinking the positions of the feeder from the cable
    -   Linking the positions of the feeder into the cable
    -   Moving the line points from a selected position to a new position through a dragging
    -   Deleting the entire line/multiple line by just clicking on to the line / multiple line to be
    -   Deleting the portion of the line segment through the identification of the start and end
    -   Replacing the line designation by selecting a new line designation. This is nothing but
        the “changing the line type” method
    -   Updating the cable‟s non-graphical data through an interactive GUI mask
    -   Displaying the cable‟s non-graphical data on to the graphical space
   The software shall be able to check the electrical network line continuity for the power flow
    through graphical and non-graphical data as listed below:
    -   The electrical line tracing till the end of the line by considering the switch positions on
        the line. The line will have to be highlighted after the tracing
    -   By ignoring the switch position conditions, the line shall be traced for its continuity and
        same shall be highlighted
    -   By selecting the text attributes attached to a line, the tracing shall be possible.
    -   Through a non-graphical data. On the basis of the start element (net point) identified,
        the set of network elements found as a result of network tracing based on non-graphical
        data. The searching pattern could be of type net point, lines and net objects. The results
        may be highlighted in the graphics and/or the results will be printed in the table, which
        may be displayed on request.

   It shall be possible to insert an electrical element in to an existing cable. This will split the
    existing cable into two sections and each section‟s alpha data will be displayed in a mask for
    update. Accordingly the graphical and non-graphical data will be updated.
   It shall be possible to insert any of the chosen electrical devices on a multiple feeder cables.
    For instance, the electrical device will be connected with all of the lines in the multiple
    cables. Similarly, there shall be a provision to insert the electrical device net point on to
    individual cables in the multiple cable lines. The other functions shall be made available as
    listed below through a simple clicks by mouse button:
    -   Deleting a electrical net point
    -   Replacing a net point. The existing electrical net point will be replaced with the new
        electrical netpoint.

    -   Switching a net point from open to close or vice versa positions
    -   Moving and rotating the net point
    -   Scaling up or down of the net point
   It shall be possible to update or change the non-graphic master data of the net point. Any of
    the net point can be selected by simple mouse clicks and the respective net point‟s master
    data should appear in the mask for the new values. Similarly, there shall a provision to
    display the data based on the selection of the net points.
   The bus bar shall be able to accommodate the increase in number of feeder points. It shall be
    possible to redefine the number of feeder entry/exit points in the bus bar to a higher number
    as per the requirement. The software shall internally replace the bus bar with more number
    of feeder entry/exit points by retaining the technical information associated with the bus bar.
   It shall be possible to perform the following tasks in the software

    -   Inserting a cable into a station/bus bar/distribution box
    -   Laying a protective pipes on the cable route
    -   Laying protective pipes with dimension defined
    -   Creating a manhole
    -   Creating a cross section for Trench, Man-hole, Protective Pipes
    -   Defining the cable route
    -   Labeling

   It shall be possible to insert “ cable beneath cable”
   During the insertion of cable, if there is change between any segment, e.g. if there is change
    in type of cable between joint J2 and J3,the software shall allow the user edit the same.
   After inserting the cable/joint, the software shall carry out on-line electrical connectivity
    establishment checks internally and all related databases tables shall be updated
   The software shall have facility so that cable of same voltage levels can only be connected
    with each other, i.e. if user by mistake connects LV cable /equipment with HV /EHV
    cable/equipment, the software shall generate error message.
   If parts of the cable are running across more than one sheet, the software shall be able to
    carry out merging of the two cables into one cable. The cable may be redesigned
   It shall be possible to represent cables/switchgears/HV-EHV cables under existing scenario.
   It shall be possible to calculate the length of downstream or upstream from the selected
   It shall be possible to change the color of selected elements.
   It shall be possible to retrieve / query the elements like cable within the polygon
   It shall be possible to split the existing cable/LC for the insertion of new customer cable /
   It shall be possible to trace electrical connectivity, geographically, of a customer. By default,
    the connectivity should be traced up to its feeding substation /Pole Mounted Transformer
   It shall be possible to attach scanned image of service SKETCH to a particular service

             It shall be possible to search and zoom into the user-defined distance around that service
              without any drawing sheet boundaries. The default distance shall be 100 meter around the
              service point.
             The software shall have the geographical database engine, through which the geo data and
              alpha data shall be maintained for the consistency at all times and stored in a single
              database. The software should be able to retrieve the geographical and/or alpha-numeric data
              instantly to the user.
             The software shall include the data administration features. This facility enables the
              administrator to grant rights to access to the limited area of the geographical space to the
              particular user. Through which, the same area shall be locked for the other users, which they
              can access to the same area. Hence, the software ensures the proper usage of the
              geographical area at all times
             The software shall include the Project Administration features. The software shall enable
              the facility to address multi-project environment.
             The software shall include the User Administration features. The privileges to access to
              the limited functions and other access rights shall be administered through this facility
             The software shall include the Layer Management features. This function shall enable to
              assign descriptions to the layer. The composition of various objects shall be allocated in
              unique layers, depending on the user requirements.
             The software shall include the features of Task Management, by which the geographical
              data access will be controlled and monitored. This feature utilizes the security features
              administered by Data, Project and User administrators. It should also administer the interim
              backup storage mechanism internally
             Different accessing modes of geographical area shall be possible in the software. Some of
              the modes are listed below:
              -   Co-ordinate
              -   User specific
              -   Area
              -   Map sheet number
              -   Polygon or any shape of interest

             The software shall also include the dimension, construction and transformation features

             Hierarchical object model shall be included in the software, which uses the well-defined
              geographical data dictionary in the system.

             Automatic creation of relationship between the network components while creating them
             The software shall have the facility to seamlessly integrate the network analysis and
              calculation software and all available data, can be accessed directly by Owner‟s Geographic
              Information System Application (GISA).            Asset data for accounting, operations,
              maintenance and performance modeling, are required to be accessed Owner‟s network.
             Besides that, the system is necessary to have facilities to generate, store, retrieve, edit, delete
              and display information on infrastructure assets, customers through proposed system. The
              system should provide the facility to plot or print the base map or facility map to plotter or
              printer as well.

3.10.13   Operating environment

             The proposed system should be based on open standards.
             The proposed system is required to comply with the following IEC standard protocols:
              -   IEC 61968-1 which is based on an integration bus approach focussing on integration of
                  major utility applications relating to distribution management.
             The proposed GIS software shall comply with OGC (open GIS consortium) standard.
             It is mandatory that the proposed system is required to store the alpha data and graphical data
              into RDBMS database.
             The system should be user-friendly environment where required functions can be quickly
              developed, efficiently operated and maintained.
             The system provides a separate data entry tools to capture alpha data.
             It is highly desirable that the proposed system can read and transform existing data which
              available in graphical and textual.
             It is highly desirable that the proposed system can import data from other system in standard
              data formats such as ASCII.
             It is highly desirable that the proposed system is able to overlay raster image.
             The proposed system is required to provide facilities to prepare hardcopy maps up to A0
             The proposed system can input/capture the vector and raster data through standard input
              devices such as scanner, digitizer, etc.
             It is highly desirable the proposed system supports simultaneous display of raster and vector
             It is mandatory that the proposed system – drawing sub-system supports the following
              processes prior to System Acceptance Date
              -   Capture and Maintain network asset including substation, transformer, switchgear, pole,
                  service point, cable and etc.
              -   Capture information of the asset including substation name, feeder number, switch
                  status, meter no, cable type, cable size, geographic reference point and etc.
              -   Maintain Land Information such as plot , road etc.
              -   Capture and Maintain schematic diagram for different types of network such as 11KV

3.10.14   Linkages and Interfaces
           Software should have a provision that the proposed system can be integrated (access to data )
          to the following systems with features :
             SCADA
             Customer Care Centre
             Customer Information and Billing System (CIBS)
             Project management

          Security and audit ability
           It is mandatory that the proposed system‟s security and access control facility identifies and
             verifies each user and/or workgroup of users.
             It is mandatory that the proposed system‟s security and access control facility restricts access
              to individual displays and processes to individually verified users or workgroup of users.
             It is mandatory that the proposed system‟s security and access control facility restrict
              individual authorized users to read only or read/update functions within the system.

3.11   Software Functionalities
          The software should be suitable for running with server installed at respective circles
           headquarter and client at divisional and sub-divisional headquarters. The entire data shall be
           centrally controlled and monitored at circle level. The read and write facility shall be
           available at circle level and Division Level and also at sub-Divisional level. The master file
           shall be maintained and updated at Division level and sub-division level. The information of
           sub-division level is to be compiled at regular interval in the form of a file and
           communicated to Division headquarters for its monitoring and updating in the Master file.
           Apart from the circle level server, there should also be one main server at APCPDCL
           headquarters from where the data pertaining to all circles can be accessed and monitored.
          The software should be user friendly, easy and quick to implement.
          The software should be driven by the latest state of art technologies and adequately proven
           in diverse field environments and should be capable of future Updating of Geographical
           maps, Network Documentation and Customer database.
          The Database of distribution network assets and updated customer data with verified and
           updated data related to the distribution network assets with different inter relationships
           should be built in industry standard RDBMS software, in order to populate for various
           Operational and commercial functions.
          The GIS based software application should have the facilities to view the details of
           customers and assets of Distribution Company like substations, feeders, transformers,
           distribution networks and utility offices etc. It also should act as an intelligent analysis and
           report generation tool for plugging loopholes and revenue leakages, aiding in perform
           network planning & management activities.
          The application shall facilitate in taking inventory of distribution poles connected to each
           distribution transformer under each feeder with location and landmarks facilitates for
           effective organization of distribution network.
          The application shall have facility to conduct Energy audit transformer wise or feeder wise
           for detection of malpractices and pilferages by linking the billing data of customers feeder
          The energy accounting software supported by the proposed customer indexed data base shall
           be able to recognize the transfer of any group of customers fed by any particular line to any
           other neighborhood / alternate line by switching of isolators or modification of jumpers
           during the operation, for the purpose of improving the availability of supply. To facilitate the
           above, all switching devices in the system shall be properly identified in the database. Such
           changes may also be effected due to system modifications such as addition of a new
           distribution transformer or additional line or a new substation. The software shall provide
           user-friendly screens for inputting the information for all manual switching operation carried
           out. The software shall also be capable of recognizing any automatic switching wherever
           provided at a later date.
          The software shall have the geographical database engine, through which the geo data shall
           be maintained for the consistency at all times and stored in a single database. The software
           should be able to retrieve the geographical and/or alpha-numeric data instantly to the user.
          As a part of development of Software the following documents are to be prepared according
           to the ISO standards and submitted for approval;

           -   Software Development Plan (SDP)
           -   Functional requirements specifications. (FRS)
           -   Interface requirements specification (IRS)
           -   Software Design Documents. (SDD)
           -   Database design description. (DBDD)
           -   Interface Design description. (IDD)

             -   Source Code Documentation
             -   Flow charts
             -   Software test plan (STP)
             -   Software Users manual (SUM)
             -   Software quality assurance plan (SQAP)
             -   Software configuration management plan (SCMP)
            The software shall also include the dimension, construction and transformation features

3.12     Integration, Mapping and Documentation of network using APCPDCL
         GIS maps provided in shape files/DXF etc.

         The indexing and GIS mapping using GPS survey data will be carried out by the APCPDCL.
         The GIS application should be integrated with indexed electrical sub-transmission and
         distribution network in the specified circle from 33KV, 11 kV to LT based on the coding
         methodology to be adopted by the APCPDCL as shown in Annexure-A. Each of the elements
         like 33 KV and 11 kV feeders, feeder branches, Distribution transformers shall be uniquely
         indexed with defined relationships based on the normal mode of feeding envisaged
             Network documentation is required to have the Electrical address and feeding arrangement
             of localities and customers of for carrying out Energy Accounting and maintenance of
            The coding shall be such that any additions/ modification to the network can be assigned
             codification without any difficulty
            Based on the details of Network available, with the circles, divisions and sub-divisions of
             CPDCL, pole to pole survey of 11kV and L.T lines existing in area will be conducted by the
             APCPDCL and Distribution Network from 11kV to L.T System is to be developed. During
             survey of Lines, the line length, type and size of the conductor used, type and number of
             various types of poles existing will be documented by the APCPDCL. The Sub Transmission
             and Distribution Network indicating details of 33kV Substation, 11kV feeders, 11/0.4 kV
             Distribution Transformers and the L.T. lines is to be developed and superimposed on the
             geographical map so that the physical position of the lines, substation is known on the Map.
             The interconnections between section to section are also to be compiled and marked
            The Network Documentation shall have the facility for tracing the electrical connectivity for
             any part of the network. That is, it shall be possible to find out all elements Electrically
             connected to any particular line or transformer and distinguishing points are to be clearly

3.12.1   Integration, mapping and indexing of the customer data provided by the

            The purpose of Mapping and Indexing of the customers is to identify and locate all the
             customers on geographical map(using GPS Survey), which are being fed from distribution
             Mains of APCPDCL.
            The APCPDCL will develop proper indexes for each customer in the specified area in line
             with the methodology detailed in Annexure-A.

3.12.2   Integration of database (provided by the APCPDCL) for electric network

   The database of the Network should be made in suitable software so that the changes in the
    network can be updated and queries may be used to find out the Network details, like the
    details of the equipment at the substations, the length of lines, number of transformers and
    breakers etc. in any part of the Network. The same should be possible to update and maintain
    on periodic basis
   The database should have the following details in respect of 33kV, 11kV and L.T Substation,
    Lines and Distribution Transformers. These may be the indicative details, which are required
    in the database. However, the Bidder may suggest and incorporate further details considered
    to be useful and meaningful
   The following data in respect of 33/11 kV S/s. equipment installed on these substations,
    33kV Lines, 11kV Feeders, 11/0.4 kV Distribution Transformers Data will be provided by
    the APCPDCL
   Data of 33 kV Feeder
    -     Name of the feeder
    -     Code No. of the feeder
    -     Name of the feeding EHT S/s
    -     Length of the line
    -     Details of meter installed




               Multiplying factor
   Data of 33kV/11 kV S/s
    -     District
    -     Mandal
    -     Panchayat
    -     Village
    -     Habitation/Hamlet
    -     Name of the Division
    -     Name of the Sub Division
    -     Name of the Section
    -     Name of the Substation
    -     Code No. of the Substation
    -     Capacity of the substation with particulars of transformer (No. Of transformers
          installed, capacity and voltage ratio wise)

        Transformer No                 Voltage   Capacity     Total Capacity
                                       Ratio     (MVA)
                                                              Voltage Ratio     Capacity



    -   Name of the feeding primary substation
    -   Name and length of 33kV Line feeding the substation from the primary substation
    -   Date of commissioning of substation
    -   Total No. Of 11 kV Switchgears installed
             Incoming (Nos.)
             Feeders (Nos.)
             Bus Couplers (Nos.)
    -   Total no. of feeders connected
   Data of each Power Transformer in the Substation
    -   Sl. No. of the transformer
    -   Make of the transformer
    -   Capacity
    -   Date of commissioning
    -   Voltage ratio
    -   Current rating
    -   No. of Taps on the transformer
   Data of Station Transformer in the Substation
    -   Sl. No. of the transformer
    -   Make of the transformer
    -   Capacity
    -   Date of commissioning
    -   Voltage ratio
    -   Current rating
   Data of 11 kV switch gears on the substation
    -   Total No. of switch gear installed at the S/s

        Incoming switch gear Nos,

        Feeder‟s switchgear Nos.

        Bus Couplers Nos.
    -   Rating of each switch gear

        Make of the switch gear

        Manufacturer‟s S.No

        Name of the connected 11 kV feeder

        Code of the feeder

        Date of commissioning

        Current rating

        Rupturing capacity

        Maximum load recorded with date and year

        Type of protection provided

        Details of relay installed

        Details of C.T installed


               C.T Ratio Available

               Connected CT. Ratio

               Class of Accuracy

               V.A. Burden

    -   Details of P.T installed

        Make of P.T.

        Voltage Ratio

        V.A. Burden

        Date of Voltage Ratio testing

        Next due date of testing
    -   Details of meter installed




        Multiplying factor
   Data of 11kV Feeder
    -   Name of the feeder
    -   Code No. of the feeder
    -   Name of the feeding S/s
    -   Length of the line
    -   No. of circuit


S        Name                          From          No. th of                                  Configurati
                Divisio      Feede             T               Conduct       Number        of
N        of the                        EHV/H         of  Ckt                                    on       of
                n            r code            o               or Size       supports
o.       Line                          V S/s         Ckt (in                                    conductor

                                                                             Single      Doub
                                                                             pole        le/

    Details of each customer being fed at 11 kV
     -     Total No. of customer being fed at 11kV
     -     Details of each customer connected at 11kV to be listed as detailed below:-

           S. No.

           Name of 11kV feeder and code

           Pole No

           Name and Address of the customer

           S.C. No

           Contracted Load
    Data of Distribution Transformer
     -     District
     -     Mandal
     -     Panchayat
     -     Village
     -     Habitation/Hamlet
     -     Connected to 11 kV Feeder
     -     11 kV Feeder No./Code No.
     -     Location of D.T
     -     Capacity of Transformer
     -     Voltage Ratio
     -     Code of the Transformer
     -     Name of the Manufacturer
     -     Manufacturer‟s Serial No.
     -     Year of the Manufacturer
     -     Date of Commissioning
     -     Meter Details

           meter no

         name of meter manufacturer

         Year of manufacture


         Meter on primary/ secondary (side)

   Data of L.T Feeder
    -    Connected to D.T.R (code No:)
    -    Location of D.T.R
    -    D.T.R Code No.
    -    L.T. Feeder Name
    -    L.T. Feeder No.
    -    Length of Line –the length of three phase, two phase and single phase line is to be
         worked out and segregated conductor wise

         3 Phase Line --Conductor Size

         Single phase Line --Conductor Size

Details of L.T. Lines to be collected and documented in the for of following Performa

        Respective 11kV Respective        L.T      Section   Conductor
        Feeder Code     of Dt Code        Ckt      of L.T    Size and
                                          Code               Length

                                                             3-Phase       2-       Single
                                                             Line          Phase    Phase
                                                                           Line     Line

   Data of connected Customers

         Details of D.T & Pole        Details of Customers                              Nature of supply (3
         L.T. Ckt         No.                                                           Phase   @    Single

         D.T.     L.T Ckt             Sc. No.    Book   Name & Load          Cate
         Code     Code                           No.    Address              gory

3.12.3   Integration of customer database with the application

            Database of Customers based on the outcome of door-to-door survey will be made available
             by the APCPDCL
            Following data in respect of various customers existing in the area of the town will be made
             available in CUSTOMER DATABASE. This is indicative:
             -   Customer Details





                 Habitation/ Hamlet

                 Pole Number

                 Name of the Customer

                 Father/Husband name

                 Door no

                 Building Name

                 Street name

                 Locality name

                 Customer code no

                 Date of connection

                 Pole No. of L.T. mains to which the connection is connected

                 Service connection Number

                 Contracted load


                 Tariff Applicable

                 Type of supply (single phase/three phase/CT meter)

                 Customer class

                 Incoming Phase (In case of Single phase)

                 Phase Sequence (In case of Three phase)

                 Name of the




                 Monthly Assessment of the customer based on connected load & status.

                 Type of Service line – Overhead line/Cable Service
             -   Meter Details

                 Meter Number

                 Type of Meter

                 Make of Meter

                 Year of Manufacture

                 Physical Condition of the Meter & Seal

                      Viewing Glass

                      Seal on the meter body / meter terminal plate

                      Sign of Tampering (if any)

                 Physical Location of the Meter

                      Approachability - Inside or approachable from outside

                      Readability - Height of mounting

                      Identifiably - Clustering of Meter for multiple customers

                 Operational status of meter: OK/ Dial not rotating/ Digits not visible/ Smoky / Damaged/
                 Digits not Changing/ Figure upset

                 Status of wiring/service cable: OK/ Cuts/ Joints/ tampering/ Clustered

3.12.4   Customer segregation
         The Software should have the feature of Segregation of customers, 11 kV Feeders wise and
         Distribution Transformer Wise
            The connected customers are to be identified and segregated Distribution transformer wise
             and 11 kV feeders wise. The meter reading of distribution transformers is to be segregated
             11KV feeder wise. The segregated meter readings identified for particular DT should contain
             the entire customers connected to the respective DT
            To identify the areas of high Energy Losses it is essential to work out the losses, Distribution
             Transformer wise and 11kV feeder wise. The losses are to be assessed by subtracting the
             total energy of all the customers billed, connected to the Distribution
             Transformer/11kV feeder, from the energy sent/metered on Distribution ransformer/33kV
             Feeder respectively. For doing so it is essential that the connected customers are segregated
             Distribution Transformer wise and 11kV and 33kV Feeder wise.
            At present APCPDCL is maintaining Meter reading books of customers, 11kV feeder wise
             but there are cases where the meter reading books pertaining to the feeders contains
             customers of other feeders or lines also. These meter reading books are to corrected or

             updated such that all the customers are segregated 11kV feeder wise and Distribution
             Transformer wise
            The details of segregated customer, which requires change from one Meter Reading Book to
             the other, shall be worked out and furnished to APCPDCL in prescribed Performa for
             effecting the change in respective billing data of computer billing systems.
            Bidder shall involve Owner‟s IT personnel and Field engineers of respective circles at all the
             stages of the project execution (i.e. System Design, development, Field data compilation,
             work flow modeling, implementation, Server/Work station installation-Commissioning,
             documentation etc.) so that they are able to maintain the complete system in future
            During the annual maintenance contract period, the bidder has to put one Graduate Software
             Engineer at each district headquarter and at APCPDCL Headquarters to look after the
            Develop proper indexes for each customer in the specified area in line with the indicative
             methodology prescribed in Annexure-I. However the exact manner of indexing shall be
             subject to Owner‟s approval before commencement of work. For this purpose, the bidder
             will be provided with the as available category wise list of customers in each area along with
             the particulars such as contract demand / connected load, name of customer, address of
             customer etc.

3.12.5   Integration with customer database
         The Application should be integrated with the indexed customer database and the application
         shall be capable of following:
            The customer indexing data provided will have the capability of allocating a unique
             identification number known as Customer Identification Number (CIN) to each customer.
            The system shall keep track of the location in the network from where a particular customer
             is fed. This shall be achieved in conjunction with the network data created.
            Provision shall be provided for linking and maintaining records (in Registers/Ledgers) of the
             utility‟s Customer‟s identification number as parameter, existing before
             implementation/adoption of the customer indexing work under this specification.
            The application and the database shall be flexible for making changes in the customer profile
             as required. This means changes such as customer name, location, connected load, category
             of connection, maximum demand, type of connection (HT/LT), tariff related information.
            Sorting and viewing electrical area or feeder/administrative area wise customer details.
            Handling requests for new connections. This shall enable a paperless handling of all events
             from receipt of request to processing / tracing the request at all stages within the Owners
             business process and providing the connection and updating of customer database.
            Tracking the customer meters and recording meter changes, meter re-calibration etc.
             Keeping track of customers who are required by the billing system to be disconnected and
             reconnected and the details of actions taken in response to such requests received.
            The application software and the integrated database shall generate color graphic displays of
             the system network which can be zoomed in / out. This shall represent each of the elements
             in the electrical system with suitable differing colors for the elements. It shall be possible to
             get a view of the details of the customer or customers connected to particular distribution
             transformer in a list form using a pointing device. This view shall be enabled in the phase
             one of indexing work. It shall be possible to zoom in / out on this view to obtain the desired
             degree of information on a particular customer. Menus shall be provided for viewing various
             combination of information related to any groups of customers. For example it shall be
             possible to view only the list of commercial customers fed from a particular feeder. Similarly
             electrical equipment parameters shall also be possible to be viewed.
            The graphic user interface shall have a modular structure with main menus and sub-menus
             that allow users to dynamically configure their own user interface to required level.

            It shall be possible to view the system elements such as customer location, location
             coordinates, geographical location details with reference points etc on completion of phase
             two of the indexing work. It shall be dynamically possible to switch from one mode of view
             to the other by use of a pointing device. It shall be possible to view the physical system
             details in the background of the area maps created.
            The bidder shall hand over the software developed along with any third party soft wares used
             for the creation of the database with full rights to the Owner for its unrestricted future use.
            The databases shall have password protections with varying degree of access definable by
             the administrator. The security shall be adequate considering the web-enabled usage of the
             customer related information for connection status, load profiles and revenue related
            The minimum resolution of GIS mapping shall be 5 meters.

         The GIS application software should have the following capabilities in the application software

3.13     New customer management
         This application should broadly support functionalities pertaining to the receipt of completed
         application forms; verification and appraisal of new connection request; and approval/rejection
         intimation to the applicant. The appraisal process envisages identification of customer on GIS,
         planning works to be executed to extend, power supply as per standards, checking technical
         feasibility and preparation of estimate of works. The application also shall be capable of
         handling the service release process with all its activities like payment of deposits, issues of
         work orders, monitoring of works, test reports and release of service on GIS. The system‟s
         functionalities should aim at enhancing customer convenience, capturing customer data
         accurately and ensuring that the same is available seamlessly to all other applications like CRM
         (Customer Relationship Management), MBC (Metering, Billing and Collection) system etc., as
         well as to other systems. Details of the requisite functionalities, which the module should
         provide for, are listed hereunder:

3.13.1   Applications

            The system should generate a unique application number for every application form.
            The system should have the provision of accepting application form fee payment details and
             issue a receipt to customer.
            The system should be capable of capturing the details of the customer from the application
             form. The system should offer the flexibility of indicating mandatory and non-mandatory
             fields for customer details. It should not accept forms where the mandatory fields are left

3.13.2   Internal Validations

            The system should accept the customer details and check the applicant‟s particulars against
             the set of existing customers and rejected applications. In case of a match in records an
             exception should be raised. This exception should be flagged off to the relevant approving
            It should also be possible to check whether all the formalities like approval of building plan,
             industrial license, environmental clearance etc., are complied or not by the customer.
            The system should be able to assess the load for each applicant based on the predefined
             standards and then validate the customer‟s self-assessment of the load and advise.

             Identification of Customer on the GIS map: It should be possible to identify the customer on
             the GIS map, provided the nearest pole number to the premises or service connection of the
             neighboring customers or the street in which the premises is located and the approximate
             distance from the landmarks is given as input in the application form.
             Inspection of premises: The system should provide the functionality of generating an
             intimation letter to the customer informing him of the customer premise inspection, if
             required and also recording the inspection report by competent authority. It should be
             possible to define the inspecting authority for each type of application.

3.13.3    Power Supply arrangements:

            It should be possible for the user to simulate power supply arrangements by digitizing the
             new line, installation of distribution transformers, installation of substations, increasing of
             the conductor sizes of feeder sections, installations of voltage booster, capacitors etc., to
             ensure supply as per the standards of the utility. Once the supply arrangements are
             completed, the programme should perform load flow analysis and display the voltage profile
             and the losses of the concerned network to enable the engineer to judge the technical
             adequacy/feasibility of the arrangements proposed to meet the technical standards. Where
             the proposed lines have to be run along the roads, facility shall be available to consider the
             road cross sections, turnings and any other physical obstacles as shown in GIS map for
             running the line. The system should be capable of identifying and displaying the nearest
             transformer or the nearest pole from which supply can be extended to the customer.
            It should be possible to provide simulation of supply arrangements for the individual
             customer or a group of customers in the area like the cases of extension of power supply to a
             complete new colony/hamlet.
            It should be possible to generate more than one proposal for extension of power supply for
             the same customer or group of customers and compare both the arrangements, with
             regard to the voltage profile, losses etc. to enable the engineer to take a decision which
             arrangements is best.
            It should be possible to invoke the design module of Power network analysis software to
             check the design of the lines, loading of the conductors etc. proposed.

3.13.4   Cost estimates

            Estimate module should display the quantities of lines & equipment, from the            supply
             arrangements module.
            It should be possible to prepare cost estimates for the supply arrangements approved by
             selecting the complete technical parameters of the lines like span, type of pole and
             equipment proposed, type of transformer etc.
            The system should be capable of tracking the process of sanction of estimate and generating
             a sanction number by competent authority.
            The system should also be capable of generating bill of material for the work.
            Display of Network: All the new services proposed, sanctioned, under construction and
             commissioned should be displayed in different colours on the GIS mapping. At any point of
             time user should get the complete view of all the applications pending.

3.13.5    Charges payable by customer

             The system shall be capable of generating all the charges payable by the customer like
              development charges, service line charges, security deposit etc. based on the works planned
              and the electricity usage provided in the application.
             The system should also be capable of accepting the charges paid by the customer and
              generating the receipt.
             The system should also be capable of generating an intimation letter to the customer asking
              for payment.
             The system should also be capable of monitoring whether the payment is made by the
              customer, otherwise remind him by giving a suitable notice and delete his application if
              payments are not made by the stipulated date as per the standards of utility.

3.13.6    Agreement formats
          The system should have the facility to generating the agreement formats and scan the agreement
          signed by both the parties and store the document with necessary security features for future
          reference and correction.

3.13.7    Work order

             The system should be capable of issuing a work order on receipt of required amount from the
             The system should also be capable of allocating of the meters and other material for release
              of the work as per the bill of materials already approved.

3.13.8    Test Report

             The system should be capable of generating a test report format and also recording the
              results of the test report.
             It should also be possible to download the test report format from main computer system to
              MRI and also upload the test report duly filled in by engineer from MRI to main computer
             The system shall provide for storing the photograph of the meter, meter seals and the
              terminal cover seal etc., with the serial number and also keep it as a reference for future
              comparison, when suspected tampering of seals is observed.

3.13.9    Service connection number
          The system should be capable of generating unique service connection number for each
          customer. The customer number shall be generated as per the business logic of the utility.

3.13.10   Generation of first bill
          The system should be capable of monitoring the generation of first bill to the customer after the
          service is released.

3.13.11   Reports
          The following reports shall be generated:
             The list of services released during the month with all details.
             Report on number of applications received during the month and their status.
             Report on pending applications, giving the number of applications pending before the month,
              number of services released during the month and balance applications pending.
             Report on the status of all the applications pending as on date.
             Analysis report on the pending applications cause wise, time period wise as defined by the
             Report on the amounts collected towards service line charges, development charges and
              security deposit during the month
             Report on the work orders released during the month
             Report on the agreements entered with the customers and stored.
             Report on the test reports approved and the authority released the service
             Report on the estimate sanctioned and cost of estimate.
             Report on the length of lines erected, transformers installed and other works done during the
             Report on meters installed at the customer premises.

3.14      Software for Analysis, Optimization Planning and Design of
          Distribution Systems
          The Distribution Analysis optimization planning and design package should have the capability
          to perform the broad functions: Creation and editing of network, load flow analysis, optimization
          studies like network reconfiguration, conductor upgradation, express feeder, shunt capacitors,
          series capacitors and voltage regulators, what if analysis, load forecasting, long term planning,
          fault analysis and protection coordination, line and substation design, reports, cost estimates,
          financial analysis.

          All the modules should be tightly integrated and it should be possible to do any number of
          studies either sequentially or at random. The package should be comprehensive, cover all
          aspects of analysis, optimization planning & designing and should have tightly integrated with
          GIS package. The package should share the database of the GIS and should not require a
          separate database. The features of each of the applications listed above are described in
          subsequent sections.

3.14.1    Load Flow Analysis

             It should be possible to calculate the system and operating parameters from the data e.g.,
              calculation of resistance, impedances, susceptances of the lines and cable at different
              temperatures and equivalent impedance of the transformers in a substation. It should be
              possible to define the spacing, configuration, temperature, etc.
             It should be possible to define / evaluate annual load factor and loss load factor from the load
              duration details.
             It should be able to allocate the total demand of a substation (KW and KVAR) among the
              feeders of the substation in relation to KW or connected KVA on the feeders or diversity
              factor of different loads.

             It should be possible to allocate the total demand of the feeder among the line sections/
             distribution transformers in proportion to connected kVA or KW of the distribution
            It should be possible to increase / decrease load levels for each line section of a feeder or all
             sections of a feeder with a single multiplier.
            It should be possible to model bulk loads as well as uniformly distributed loads.
            It should be possible to carry out load flow analysis of mixed, integrated, radial and looped,
             3/2/1 phase balanced and unbalanced networks. Provision shall be there for three phase 4
             wire and 3 phase 5 wire system operating at user defined voltage and parallel operation with
             different sizes of conductors / cables.
            Load flow calculations should give power flows in MW & MVAR (or KW & KVAR)
             current in each section, load at each node, voltage and % voltage regulation at each node.
            It should give the peak power loss and the energy loss in each line section and the
             transformation loss in each transformer. The iron losses and the copper losses (load losses)
             should be indicated separately. It should also be possible to get a summary of the losses of
             the entire network under study. It should be possible to use the iron and copper loss values
             defined in user created library for the same.
            It should be possible to conduct load flow analysis for nominal voltages or user defined
             voltages. It should also be possible to conduct load flow analysis for different tap positions
             of the transformers.
            The load flow analysis should indicate violation of loading voltage and current limits.

3.14.2   Optimization Studies

            It should be possible to determine the optimum reactive compensation in respect of number,
             location, discrete size and switching time to minimize losses and maximize the net economic
            It should be possible to determine the number, location and size of primary substations
             required to meet the growing demand at minimum total cost (annual fixed charges and cost
             of network losses).
            It should be possible to determine the optimum network configuration for formation of new
             links to nodes on a existing feeder, tie points for changing feed area from one substation to
             another to balance load among substations and augmentation of distribution transformer
            It should be possible to identify overloaded sections and determine optimal conductor size
             for each feeder segment.
            It should be possible to determine the location, capacity of shunt capacitors for improvement
             of voltage profile while minimizing losses.
            It should be possible to determine the optimal number and location of voltage regulators in
             the network for bringing the voltage profile to meet statutory limits.
            It should be possible to determine the length of express feeder and the point of isolation in
             the existing network.

3.14.3   What if analysis
         The programme should provide for system study and analysis of alternate network scenarios
         involving cost implications considering the following options:
            Capacitor placement and sizing

            Selective reconductoring
            Selective reconfiguration
            Selective rerouting
            Substation sizing and location
            Network addition / augmentation by feeders / new transformers
            Selective and across the network load variation

3.14.4   Load Forecasting
         Software shall indicate the systems maximum demand in KW when the energy consumption for
         a set of customers is worked out. Software should have module for distribution load forecast
         which means forecast of geographical locations as well as quantum of future load growth
         considering extrapolation, simulations and econometric methods. Load forecast analysis should
         have these features:
            Analysis of past trends of growth in electricity demand and energy consumption.
            System load forecast viz., forecasts of load for the entire study area
            Spatial or small area load forecast viz. divide the utility service area into sufficiently large
             number of small areas and forecast for each small area.
            Trend analysis –
             -   Growth rate of energy year wise and cumulative growth rate of energy for the period.
             -   Share of electrical energy consumption among different sector year wise and the average
                 for the period.
             -   Energy consumption per service year wise and the average for the period.
             -   Growth rate of service connections year wise and cumulative growth rate for the period.

         Connected load per service connection year wise and the average during the period.

3.14.5   Long term planning

            It should be possible to re-configure the existing network as High Voltage Distribution
             System with the user give constraint of maximum length of LV feeder and the transformer
            It should be possible to simulate the network additions namely Power transformer capacity
             enhancement, additional distribution transformers, additional feeder segments or feeders etc.
             to meet the demand forecasted.
            It should be possible to inactively generate alternate network configurations to meet he
             projected demand year wise or at any given period and determine the lease cost network
             expansion plan, to satisfy the demand year after year.

3.14.6   Fault Analysis & Protective Coordination

            Fault current calculations should give symmetrical and asymmetrical fault currents and short
             circuit MVA at each bus / node for the following faults. It should be possible to simulate the
             conditions of fault involving additional impedances in the fault.
             -   Three phase faults
             -   Line to line faults

             -   Line to ground faults
             -   Double line to ground faults
            It should be possible to compute the source impedances at the feeder bus from the
             impedances at the high voltage side of the substation transformers and the step down
             transformer data.
            It should be possible to check the adequacy of the protective devices viz. circuit breaker
             withstand capacities etc.
            It should be possible to compute the settings of transfer differential and O/L & E/L relays
             schemes and coordinate for them to avoid mal-operation.

3.14.7   Line and Substation design

            It should be possible to determine the economic and break-even loading                 limits of
             conductors and cables.
            It should be possible to evaluate the design of distribution feeders, to check adequacy of
             support strength and statutory clearances etc.
            It should be possible to evaluate the design of earth mats and earth electrodes.
            It should be possible to compute, positive sequence, negative sequence and zero sequence
             impedances with and without mutuals.

3.14.8   Reports

            The programme should provide for generation of various reports for example feeder wise,
             transformer wise, voltage wise etc.
            The programme should provide for importing reports to standard packages like MS Word,
             MS Excel etc.
            The programme should provide for:
             -   Tabular as well as graphical report generation
             -   Power flows and power & energy losses in each section and transformer. In case of
                 transformers, the iron losses and the copper losses (load losses) should be indicated
                 separately. It should be possible to use the iron and copper loss values defined in user
                 created library for the loss calculation.
             -   Summary and individual reports should be available by bus, voltage level and zone /
             -   Abnormal condition reports for sections with voltage violations and / or over loads.
            The programme should provide for identification of network element / equipment through
             colours code on a single line diagram in case of abnormal operating condition.
            The billboard printing provides for enhanced printing of diagrams along with results on the
             diagram itself.

3.14.9   Cost Estimates
         The module should be capable of preparing cost estimates of lines, substations based on the cost
         data. Provision should be available to input user input of the costs for special structures like
         river crossings, railway crossings. Capability to input the cost of storing line material, substation
         equipment, generating cost, data estimates and non-standard estimates. The module should be
         capable of preparing project estimates consisting of several lines and substations. Facility to

          store the cost data of several areas and more than one version of the project report shall be

          The module should be capable of capturing the works proposed under various studies and
          crating the estimates of the studies performed by transferring the initial works proposed in the
          studies without again entering those details. In other words, there should not be a need for the
          user to in put the works proposed in the cost estimation module separately. When he picks up
          the study, the cost estimate gets created automatically interactively by selecting the complete
          details of the lines and equipment proposed.

3.14.10   Financial Analysis
          The software should have module for cost benefit analysis of any network under different
          proposed alternatives. The software should provide for evaluation of project and cost
          calculations for system improvement options under considerations. Software should be able to
          calculate the financial parameters such as internal rate of return, discounted cash flow, pay back
          period, present worth, sensitivity analysis etc. with relation to system losses so as to optimize the
          investment for an electrical distribution system. Module should also give the optimal solution for
          any given network. Module should have provisions for minimization of losses so as to maximize
          the net benefit i.e., the present worth of loss reduction is more then the annual cost of capital
          investment. Financial analysis of each loss reduction measures shall be done through NPV

3.15      Software for Energy Audit & Accounting
          The application should be capable of accounting Energy input to feeder, transformer, and
          substation with the following inputs:
             Meter readings and multiplying factors of the 11kV feeders/ transformers
             Meter readings of the individual customers incident on the feeder/ transformer, giving the
              customer indexing.
             The network data required for conducting analysis.
             Typical customer load curves.

          The application should also provide comprehensive energy audit and analysis:
             Energy input: It should be possible to compute the energy input into the system from the
              meter readings on prorata basis for the period for which audit is to be performed. The dates
              of the period for energy audit and the dates of the meter readings may not be identical.
             Energy Sales: The application should be capable of identifying customers on the feeder/
              distribution transformer using customer indexing, taking into consideration the dynamic
              changes in network configurations and compute the aggregate energy sales of all the
              customers incident on the feeders. In this case also, the dates of the meter readings may not
              be identical with dates of energy audit and the programme should be capable of computing
              prorata consumption to each customer for the purpose of computing energy sales. There
              may be customers who have not been read in this period, such customers must be identified.
             Technical Losses: The application should be capable of calculating the technical losses
              rigorously using load allocation algorithm based on energy sales/ Demand on each
              transformer/ pole. It should be possible to allocate load based on typical daily load curve of
              the customer. The energy losses should be calculated using load loss factor, typical daily
              load curve and load duration of the feeder/ transformer. The State Estimator function should
              run when the demand on the feeder as well as transformers is available. It should be possible
              to perform unbalanced load flow analysis and also integrated load flow of 11kV and LT
             Commercial Losses: The application should be computing the commercial losses on the
              feeder/ transformer as the difference between the total losses and technical losses.

          Customer Vigilance: The application should be capable of comparing consumption of
           similar class of customers, taking into account the specific consumption per kVA of
           contracted MD or the production figures whichever data is available and identify the
           customers that need to be watched.
          Dedicated feeders: The application should be capable of comparing the hourly load curve
           of the feeder and hourly load curve of the customers incident on the feeder and identify the
           hours when there is a mismatch between the feeder demands and aggregate sum of demands
           of the customers and identify the customers who are suspected to be indulging in pilferage.
           This exercise is possible in respect of dedicated feeders for a small group of HT & LT
           Industrial/ commercial customers, who are having load survey capability meters.
          ATC Losses: Application should be capable of computing the energy for which payments
           were received from the customers when the database of the customer payments is made
           available. The energy for which payment received should be computed tracing the account
           of each customer rather than by prorata basis, as done manually. The ATC losses shall be
           computed as the difference of energy sent out and energy for which payment received. This
           will be expressed as percentage of energy sent out on the feeder.
          Hours of supply: The application should be capable of monitoring the hours of three phase,
           single phase supply, no supply provided on the feeders when the load survey data of the
           feeder is made available.
          Reliability Indices: The application should be capable of identifying the feeder breakdowns
           & interruptions and provide facility for a detailed analysis when the causes of breakdown,
           the locations of the breakdown are given as an input. The application shall compute system
           and customer reliability indices.
          Reports: It should be possible to generate the following reports
           -   The feeder wise, transformer wise total losses,
           -   Feeder wise, transformer wise breakup of technical losses, commercial losses,
               ATC losses,
           -   The number of customers incident on each feeder and number of customers whose
               energy consumption could not be reckoned for want of data and the percentage of such
           -   The comparison of the energy losses month wise, feeder wise or transformer wise.
           -   Exception list identifying the feeders/ transformers having high losses as per the
               threshold limits fixed by the user.

3.16   Asset management

       The objective of this application is enhancement or better utilization and management of assets
       through computerised Maintenance management and outage management of assets. The
       application should provide for creation of database of technical particulars, maintenance of the
       assets and outage of the assets. The application should share the database of the GIS; shall have
       user-friendly screens for handling all transactions, shall have extensive MIS reporting.          The
       details of the requisite functionalities the application should provide for are listed hereunder:

       Asset Database
          Capable of handling all the types of assets with facility to add, delete new asset types
          Facility for the user to define the database of technical particulars for each type of asset
          Facility for the user to define the format of inspection reports of assets like Half yearly
           inspection of Substations, Pre-monsoon inspection of Lines
          Facility to create format for testing and commissioning of an asset.

         Identification / Selection of an individual facility or group of facilities in an area defined by
          network like substations, feeders etc and administrative jurisdictions like sub- division,
          division etc.
         Report on the assets available in areas defined by network like substations, feeders or/ and
          administrative jurisdictions like division, sub-division, circle.

       Facility for user definition of maintenance schedules for each type of asset as per utility
         Facility to define the various activities under each maintenance work, like facility to record
          the IR (Insulation resistance) Values HV to earth, LV to earth and HV to LV, under
          maintenance head Measurement of IR for Transformer
         Ability to define complex maintenance works like overhaul as a suite of regular maintenance
          works plus additional items.
         Facility to prescribe target values for various tests conducted on assets under different
          operating conditions.
         Facility to compare the test results obtained during the maintenance with target values to
          keep a track on the health of the asset.
         Management decision support system to monitor the present status of the maintenance
          carried out on the assets and identification of the backlog in the maintenance work.
         A report on historical the maintenance carried out on the assets.

       Facility for the user to define the format of outage reports,

         Report on the number of outages on a facility during its life cycle.
         Report on the assets failed at a particular location.
         Monitoring the amount spent on a particular asset towards repair and refurbishment during
          its life cycle.
         MIS reports on failure of assets type wise in areas defined by network like substation, feeder
          or/ and administrative jurisdictions like division, sub-division, circle.
         Facility to create format for inspection carried out on the asset after its outage.

      Valuation of Assets
       Provide for entry of the book value or cost of acquisition of asset

         Computation of depreciation of asset at the end of period say year by different methods
         Valuation of Asset for purpose of Tax, and Financial accounting Methodology adopted by
          the APCPDCL for customer indexing and asset coding

      This section describes the methodology adopted by the APCPDCL in customer indexing and
      asset coding. The methodology is presented here to inform the vendors of the likely data
      formats which will need to be integrated with the system to be developed by them.

A.1   Intent
      Intent of this methodology is to develop a system of coding of various elements of Distribution
      Network. These are 33kV Power Sub-stations, 33/11 kV Power Transformers, 11 kV Feeders,
      distribution transformers (DTs) and LT network.
         The entire information of all the assets and object elements should be stored in a database by
          unique computer generated 6 digit alphanumeric code. The coding should be on a structured
          pattern and have provision for insertion of new component into the system. This code is
          primarily for quick mapping and sorting of the asset element.

   On query, either on a Graphic display of network showing element on a computer screen or
    based on asset code, database should be able to furnish all the information of the particular
    element. The Geographical location of electrical division & sub-division and a candidate
    power sub-station, electrical connectivity and technical parameters where ever applicable
    etc. Shall be made available on query for tracking any asset or customer.
   The indexing has to be carried out in a way by which it would be possible to relate the
    -   The location of the network in relation to geographical area of the Circle/Division/sub-
    -   The 33 KV feeder from EHT SS to the 33/11 KV sub-station
    -   The 33 kV/11 kV power sub-stations
    -   The 33 /11 kV power transformers.
    -   The main road, the branch roads and the lane through which 11 kV feeder passes from
        the 11 kV feeder code.
    -   The 11/0.443 kV distribution transformers
    -   The location of LT lines and their poles with respect to the main road, branch roads and
        lanes from the index of poles.
    -   The customer code to indicate the type of customer and the serial number of customer.
    -   The customer and the „DT‟ from which, he is served.
   Each of the Customers, indexed on the basis initial record available with the owner and later
    verified by field survey, shall be given an exclusive 6 digit alphanumeric code. This code
    shall also be generated by the system. The customer code shall provide complete identity of
    the customer as well as his connectivity to the electrical system profile.
   Customer code number shall be used for Metering, billing and all other service functions.
    Hence this code number will be available on the front end.
   Asset code number is meant for internal linkage of customer with nearest element and asset
    element with others.
   The power of computer based data sorting and combining is to be used for providing support
    for Billing, Customer service, MIS etc.