Scribd Logo
Upload

Welcome to Scribd!

  • 22 views

    SCADA Project Guide - 24

    Uploaded by

    renv
    This document outlines technical specifications for a SCADA/DMS system under an R-APDRP project for a utility in India. It describes tables that the SCADA system will maintain including: (1) a daily energy data table updated from the billing system that is stored for two months; (2) a load priority table that can be updated/overridden by the billing system and SCADA operator; (3) an SOE data table storing switch events that is generated daily and stored for two months. It also specifies daily exchange of energy and load data between the SCADA and billing systems using defined data exchange protocols and formats.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    SCADA Project Guide - 24

    Uploaded by

    renv
    22 views1 page
    This document outlines technical specifications for a SCADA/DMS system under an R-APDRP project for a utility in India. It describes tables that the SCADA system will maintain including: (1) a daily energy data table updated from the billing system that is stored for two months; (2) a load priority table that can be updated/overridden by the billing system and SCADA operator; (3) an SOE data table storing switch events that is generated daily and stored for two months. It also specifies daily exchange of energy and load data between the SCADA and billing systems using defined data exchange protocols and formats.

    Original Title

    SCADA Project Guide_24

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document outlines technical specifications for a SCADA/DMS system under an R-APDRP project for a utility in India. It describes tables that the SCADA system will maintain including: (1) a daily energy data table updated from the billing system that is stored for two months; (2) a load priority table that can be updated/overridden by the billing system and SCADA operator; (3) an SOE data table storing switch events that is generated daily and stored for two months. It also specifies daily exchange of energy and load data between the SCADA and billing systems using defined data exchange protocols and formats.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    22 views1 page

    SCADA Project Guide - 24

    Uploaded by

    renv
    This document outlines technical specifications for a SCADA/DMS system under an R-APDRP project for a utility in India. It describes tables that the SCADA system will maintain including: (1) a daily energy data table updated from the billing system that is stored for two months; (2) a load priority table that can be updated/overridden by the billing system and SCADA operator; (3) an SOE data table storing switch events that is generated daily and stored for two months. It also specifies daily exchange of energy and load data between the SCADA and billing systems using defined data exchange protocols and formats.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 1

    Power Finance Corporation

    SCADA/DMS, system under Part A –R-APDRP


    Model Technical specification
    MGVCL/RAPDRP/SIA/1140

    with the Billing system in Data centre & DR Under R-APDRP IT implementation/
    legacy master billing centre on daily basis and on demand. This table shall be
    created on daily basis. Such daily tables for two months duration shall be stored
    on auxiliary memory. Daily Energy data table for the previous month shall be
    backed up to Magnetic tape by the user on the 10th of every month.

    1.3.5 Load priority table

    ISR system shall maintain a Load priority table containing information such as
    breaker name, number of consumers connected to each Breaker and Load
    priority of each Breaker. This table shall be updated by the Billing system in Data
    centre. Under R-APDRP IT implementation/ legacy master billing centre .
    SCADA /DMS control centre operator can also assign priorities in load priority
    table & the priorities assigned by the Billing system in Data centre & DR Under
    R-APDRP IT implementation/ legacy billing system may be accepted/ rejected by
    him. There shall be suitable alarm/event message including user ID for such
    activity. The table information shall be used by various DMS applications.

    1.3.6 SOE data table

    ISR system shall maintain SOE data table which shall store the SOE data for
    complete distribution system . It shall be possible to sort the table by Time, Date,
    Substation name feeder/line name,device name etc. using SQL commands. This
    table shall be made on daily basis. Such daily tables for two months duration shall
    be stored on auxiliary memory. For the purpose of sizing of table, daily 4 changes
    per SOE point may be considered. All CBs, protection and alarm contacts shall be
    considered as SOE. Tables for the previous day shall be backed up to Magnetic
    tape/ MO disks by the user at 10AM of every day.

    1.3.7 Data exchange with Billing system (Data centre & DR centre) Under R-
    APDRP IT implementation

    The ISR function shall provide daily energy values along with associated quality codes to
    Billing system Under R-APDRP IT implementation or any legacy master billing centre
    once in a day and on demand. SCADA/DMS System shall have the provision to
    import/export energy values with Billing system at data centre/DR Under R-APDRP IT
    implementation. This information of Load priority in ISR system shall be updated by
    Billing system at data centre /DR Under R-APDRP IT implementation shall be used by
    DMS applications. Further data from snapshot table shall be transferred to IT system in
    R-APDRP
    This data exchange shall be done using SOA / Enterprise Services Bus already provided
    by ITIA, over Open XML Models like CIM/XML, or over ICCP / OPC/ODBC.

    SECTION-2, CHAPTER-1 : SCADA FUNCTIONS page 24 of 17

    You might also like