Ability to integrate with GCCR system of XXXX

including data exchange, reporting, analysis

Document title goes here

Requirement

Objective – To fetch the AMR from the stored and updated in the GCCR ( Generation
Control Center Room) to be received and get updated in Standard SAP Tables in the
form of EDM Profile Values
Purpose – Capturing of the Interval based Energy meter Readings as SAP EDM Profile
values for the relevant Energy Meter and getting it uploaded in the EDM Profile as
Profile Values through FTP/Real time for generating the various reports and for other
commercial purposes.

Business Requirement and Process flow diagram

1. To fetch the interval based Energy Meter Readings as SAP EDM Profiles at a frequency
of Every 5 Minutes and getting it updated in the SAP Standard Profiles through File
Transfer protocol method and Real time Method
2. The output file format from the GCCR system will be in (.CSV file)

Interface Details with the required-in infrastructure details to be

provided by the HPGCL (Currently no GCCR is available with HPGCL)

1.1 Design
 The Generation Control Room (GCCR) will be located at the company head office in
Panchkula and will serve the purpose of monitoring of the important plant parameters
including energy related data at a centralized location.
 Each of the plant locations are connected to the GCCR through a 2 Mbps leased line.
The bandwidth allocation through MUX of this dedicated bandwidth being done as
follows
o 1 Mbps for administrative LAN (including proposed SAP data flow requirement
and EPABX IP Phone requirement).
o 128 Kbps for data to be sent to GCCR.
o Around 800 Kbps for Video conferencing purposes.
 The fall back mode of connectivity to GCCR (for real time data only) is through VSAT
with a capacity of 19.2 Kbps per station.
 36 TPS, 9 GTPS and 6 HPS units are to be connected to the GCCR database.
 Among the TPS, 17 units are DCS units and capable of full-fledged automation (real
time data communication through OPC Servers) while the others are non-DCS units.
 Three packages have been implemented at GCCR
o SCADA package for plant parameters (Plant Process parameters, Energy both
ex-bus as well as internal energy consumption parameters)
o ABT (Availability Based Tariff) package (load scheduling).
o MOD (Merit Order Dispatch) package.

2
Document title goes here

2 High Level Design

2.1 Detailed Description

The requirement of various modules in SAP is to capture and store the Energy related data
The GCCR database that consolidates this data from all the locations is the ideal source to meet
the requirement of SAP modules.
The required data of Energy related parameters shall be replicated in the database used in the
SAP landscape for the requirement of various modules and reporting/ MIS purposes.
The Energy related data will be received from the GCCR database in the (.csv) as agreed in the
blue print stage.
A Background job will be set both from the client side to send the energy data to the FTP Link
and the from the LTI side to fetch and update the data in the SAP Database.
An error handling mechanism will be provided to push the datas from the Z-Table back to the
SAP tables through Manual/Excel upload method

2.2 Design Approach

Involved Systems, Message Communication and Interfaces

Overview of Communication
Query to fetch
Every 4 hrs check GCCR records based
SAP R/3 last date and block SAP PI on last date and GCCR databse with
stored in SAP Middleware block in SAP specific View(s),
database
userId created
specially for SAP
purpose
Records sent GCCR records
to SAP

Update every 5 min

energy data at
every 4 hours

energy related data

from all plants

SAP BI

3
Document title goes here

Involved Systems

System I
Name: GCCR database
Use of System: To collect the consolidated plant process and energy related data
Type of System: SAP System
System ID: Client:
Third-Party System
Product Name:
Vendor:
Proprietary System developed using Oracle database

System II
Name: SAP BI system
Use of System: Capturing energy parameter data at 5 min intervals.
Type of System: SAP System
System ID: Client:
Third-Party System
Product Name:
Vendor:
Proprietary System

System III
Name: SAP ECC system
Use of System: Capturing consolidated Plant process and energy parameter data at day end.
Type of System: SAP System
System ID: Client:
Third-Party System
Product Name:
Vendor:
Proprietary System

4
Document title goes here

Design Alternatives

Recommendations and Decision:

GCCR database shall be used in the manner mentioned below

1. A View in the database shall be created for each of the requirements i.e., one view for
Generation related data-fields and one view of process related parameters. Each of
these views shall be common for all the units with data-fields of all the individual units.
2. The Views shall be created by Client Team at GCCR.
3. The Views shall be accessible by username and password created for SAP access
purpose. Through this setup SAP will now be able to access the designated views only
and have no access to the rest of the GCCR database.
4. The ‘pull’ strategy will be employed to pull data from the GCCR database by SAP PI.
5. The frequency of updating the SAP database will be once every 5 Mins.
6. The ‘delta data’ only shall be updated either manually or Excel Upload after the error
handling process in the SAP database. The actual number of records that will be
updated and the bandwidth requirement shall be arrived at once the number data
fields required in the views are finalized.
Design Decisions

1. The triggering for data update shall happen every 5 Mins. The decision on the interval
is based on preliminary requirements of the various SAP modules. This can be changed
depending on the requirement.
2. It was decided that SAP PI will be used to fetch data from GCCR database and send to
SAP in required format.
3. Data will be captured in SAP R/3 in custom table along with latest timestamp. The data
will also be available to plant user for capturing other details like reason for loss. For
any updation in the data, the timestamp will also be updated. At any time only 1 week’s
data will be retained in SAP R/3 as it is assumed that all data will be retained in SAP BI
for reporting (see point below)
4. Simultaneously SAP BI will also fetch the data from SAP R/3 using ‘pull’ strategy (at
every 4 hours). Use of latest timestamp will again enable all changes in SAP R/3 to be
reflected in SAP BI. SAP BI can use this data for other reporting purposes.
5. Day end consolidated data will be stored in another custom table in SAP R/3 which can
be used for transactional purposes. More than 1-week data will also be retained and
not deleted.