Service Specifications Transactional

Operations
Module: All Modules

Transactional Operations

Document Control
Project Name
Customer

TNT Express

Author (s)
Location

Infosys Limited,Pune

Summary & Objective

This document provides the details of transactional operation and service interface
specifications between BPM and ISL of RAPDRP system implemented at UPCL. This
document is intended for internal and external developers who are using these
interfaces. The audience is expected to be technical. Although the interface is system
and software agnostic, only basic XML, Web Service and HTTP Post knowledge is
assumed.

Key Contacts
Role

Name

Process Owner
Process
Manager
Business
Analyst
Technical Team

Reference Documents
Document Name

File Name

SRS Document
Template

Revised_SRS_including_scope_DR.
pdf

Confidential

Page

Page 2

Relevant
Contents

52 of
G2

Module: New
Connection

64 of

Module : GIS

Transactional Operations

Reference Documents
Document Name

File Name

Relevant
Contents

Page

G2

based customer
Indexing and
asset mapping

130 of
G2

Module : GIS
based integrated
network analysis
module

SRS Customizations

Annexure_R_SRS_Customization.p
df

10 of 12

To Be Process
Document

TobeProcess_Process_To_Be_NSC_
1.1.pdf

All

5.0 GIS based

customer
indexing and
asset mapping
Process Flow
Diagrams

Update History

Versi
on

Creation/Up
date Date

Content

Outlin
e
Numb
er

Created/Updated By

Review History
Review
Organization

Confidential

Reviewer

Page 3

Versio
n

Review Date

Transactional Operations

Approval History
Approval Type

Approver

Versio
n

Approval Date

This document is the property of and proprietary to Infinite Computer Solutions (India)
Limited and Phoenix IT Solutions Ltd. Contents of this document should not be disclosed to
any unauthorized persons or companies. This document may not, in whole or in part be
reduced, reproduced, stored in a retrieval system, translatedor transmitted in any form or
by any means, electronic or mechanical outside the Infinite /Phoenix Network.

Confidential

Page 4

Transactional Operations

Table of Contents
1

R-APDRP Applications........................................................................................... 6
1.1

Integration Scope........................................................................................... 6

Transactions List................................................................................................... 7
2.1

Transaction: Retrieve Network Age................................................................7

Confidential

Page 5

Transactional Operations

1 R-APDRP Applications
Under R-APDRP program, the following list of applications shall be implemented at UPCL.
a. Meter Data Acquisition System.
b. Energy Audit.
c. New Connection.
d. Disconnection & Dismantling.
e. Geographical Information System (GIS).
f.

Centralized Customer Care Services.

g. Management Information System (MIS).

h. Web Self Service.
i.

Identity and Access Management System.

j.

Document Management System (DMS).

k. Enterprise Network Management System.

l.

Development of Commercial Database of Consumers.

m. Mail/Messaging System.
n. Metering, Billing&Collections.
o. Asset &Maintenance Management.
Each application has to communicate with different applications during execution of a transaction. In the
next sections, we will identify the transactions of each application and the corresponding interfaces with
other applications.

1.1 Integration Scope

All the applications implemented would be integrated on a continuous basis using an integration
middleware layer. The scope of integration of external systems includes IT systems already existing and
functional internal to the utility. The integration would be on-line real time or batch where appropriate

Confidential

Page 6

Transactional Operations

and would operate in an automated fashion without manual intervention. The scope of applications
integration will be, but not limited to:

Integration with existing messaging system

The integration would use a continuous integration middleware layer. This integration
middleware layer could then be used to undertake any future integration between applications.
The integration middleware is based on Service Oriented Architecture (SOA).

Transactional as well as standing or master data to and from the offered system would
beinterfaced.

Data to be integrated would be validated by the developed interfaces.

The data to be integrated will be mapped, transformed (if required) and reconciled automatically.

All interfaces would to be self checking so that any exceptions or data validation errors are
reported by the system. In addition, integration logs would be maintained that confirm the success
or otherwise of the interface, complete with control totals.

2 Transactions List
2.1 Transaction: Retrieve Network Age
2.1.1 Description
This transaction is initiated from New Connection module to GIS to retrieve age of network where in
New Connection is to be released and also specify the type of network whether it is
development/strengthening network.
Service Provider: GIS
Service Consumer: New Connection
2.1.2 Parameter Definition
Inputs
Field Name

Data Type

Description

Max.
Lengt
h

Required

POLE_NUM/AIN

Varchar

Connecting pole number of service

POLE_ID

Varchar

Primary key reference of pole master in

GIS.

Outputs
Field Name
POLE_NUM
Confidential

Data Type
Varchar

Description
AIN of the connected pole
Page 7

Max.
Length

Transactional Operations

DTR_NUM

Varchar

AIN of the DTR the pole is connected to.

SS_NUM

Varchar

AIN of the sub-station number to the connected DTR

NW_AGE

Number

Age of the Network

NW_TYPE

Varchar

Type of the network can be development network D

or the strengthening network S.

SHAPE

Image

Shape file of the connected network up to substation.

INSTALL_DATE

Date

Pole installation date.

Exception
Field Name

Data Type

Description

Varchar
Varchar
Varchar

Confidential

Page 8

Max.
Length