Presentation is loading. Please wait.

Presentation is loading. Please wait.

SLDC Software SHAKTI Data Dictionary.

Published byBlaze Morgan Modified over 6 years ago

Similar presentations

Presentation on theme: "SLDC Software SHAKTI Data Dictionary."— Presentation transcript:

1 SLDC Software SHAKTI Data Dictionary

2 INDEX Sno Table Name Slide No 1 APP_FOR_IMPORT_EXPORT 4 2
APP_NOT_IN_REA 5 3 DEMAND_FORECAST_AND_ACTUAL 6 EXPORT 7 IMPORT 8 GENERATION_OWN 9 GENERATION_BILATERAL 10 LOSSES 11 NREB_FREQUENCY 12 POWER_STATION 13 REVISION_DRAWAL 14 SCHEDULE_DRAWAL 15 REVISION_ALLTRANSACTION_OA 16 SCHEDULE_ALLTRANSACTION_OA 17 REVISION_IMPLEMENTATION 18 SCHEDULE_IMPLEMENTATION 19 REVISION_ALLTRANSACTION 20 SCHEDULE_ALLTRANSACTION 21

3 Sno Table Name Slide No 19 REVISION_ENTITLEMENT 22 20
SCHEDULE_ENTITLEMENT 23 21 SCHEDULE_VS_ACTUAL 24 SCHEDULE_VS_ACTUAL_AND_OTHER 25 SHARED_PROJECTS 26 SURRENDER_ENERGY 27 SHARE_ALLOCATION 28 SHARE_ALLOCATION_ALL_STATION 29 UI_RATE 30

4 APP_FOR_IMPORT_EXPORT :
It contains the application number of power imported and /or exported to Haryana , Punjab & Delhi etc . This table is used in Day Ahead module. Primary Key : EFFECT_DATE Name Null? Type IMP_APP_NO_ VARCHAR2(15) IMP_APP_NO_ VARCHAR2(15) IMP_APP_NO_ VARCHAR2(15) IMP_APP_NO_ VARCHAR2(15) IMP_APP_NO_ VARCHAR2(15) IMP_APP_NO_ VARCHAR2(15) IMP_APP_NO_ VARCHAR2(15) EXP_APP_NO_ VARCHAR2(15) EXP_APP_NO_ VARCHAR2(15) EXP_APP_NO_ VARCHAR2(15) EXP_APP_NO_ VARCHAR2(15) EXP_APP_NO_ VARCHAR2(15) EXP_APP_NO_ VARCHAR2(15) EXP_APP_NO_ VARCHAR2(15) EFFECT_DATE NOT NULL DATE

5 2. APP_NOT_IN_REA : It contains the application number of All Transaction (Implemented) which is not used, during calculation in REA module. Primary Key : EFFECT_DATE Name Null? Type EFFECT_DATE NOT NULL DATE APP_NO_ NOT NULL VARCHAR2(10) APP_NO_ VARCHAR2(10) APP_NO_ VARCHAR2(10) APP_NO_ VARCHAR2(10) APP_NO_ VARCHAR2(10) ………………………………………………………………………… APP_NO_ VARCHAR2(10) APP_NO_ VARCHAR2(10)

6 3. DEMAND_FORECAST_AND_ACTUAL:
It contains the forecasted demand of Himachal Pradesh for next day and actual demand of the state for the same day. Demands of the state are used in Day Ahead Module. Value stored in 15 minutes block basis for each day in MWH. Code value of field STATION_SNO represents different type of record: a)                        Code 0 for Forecasted, b)                        Code 99 for Actual and c)                        -1 for Template Demand used for forecasting. Primary Key: STATION_CODE, DATE_TIME, REVISION_NO, EFFECT_DATE Name Null? Type STATION_CODE NOT NULL VARCHAR2(10) DATE_TIME NOT NULL DATE REVISION_NO NOT NULL NUMBER(2) EFFECT_DATE NOT NULL DATE TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) ………………………………………………………………………… TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TOTAL_ALL NUMBER(8,1) STATION_SNO NUMBER(3)

7 4. EXPORT : It contains detail of power exported to various states/utilities from himachal pradesh in 15 minutes block basis for whole day. Values stored are in MHW. Primary Key: STATION_CODE, DATE_TIME, REVISION_NO, EFFECT_DATE Name Null? Type STATION_CODE NOT NULL VARCHAR2(15) DATE_TIME NOT NULL DATE REVISION_NO NOT NULL NUMBER(2) EFFECT_DATE NOT NULL DATE TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) ………………………………………………………………………… TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TOTAL_ALL NUMBER(8,1) STATION_SNO NUMBER(3)

8 5. IMPORT : It contains detail of power imported from various states/utilities to Himachal Pradesh in 15 minutes block basis for whole day. Values stored are in MHW. Primary Key: STATION_CODE, DATE_TIME, REVISION_NO, EFFECT_DATE Name Null? Type STATION_CODE NOT NULL VARCHAR2(15) DATE_TIME NOT NULL DATE REVISION_NO NOT NULL NUMBER(2) EFFECT_DATE NOT NULL DATE TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) ………………………………………………………………………… TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TOTAL_ALL NUMBER(8,1) STATION_SNO NUMBER(3)

9 6. GENERATION_OWN : It contains detail of power generated from various power houses ( Giri , Larji, Bhabha etc) of Himachal Pradesh in 15 minutes block basis for whole day. Values stored are in MHW. Station_code field contains the name of power House. Station_No field contains the code a)             0 for Forecasted b)            99 for Actual Primary Key: STATION_CODE, DATE_TIME, REVISION_NO, EFFECT_DATE Name Null? Type STATION_CODE NOT NULL VARCHAR2(15) DATE_TIME NOT NULL DATE REVISION_NO NOT NULL NUMBER(2) EFFECT_DATE NOT NULL DATE TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) ………………………………………………………………………… TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TOTAL_ALL NUMBER(8,1) STATION_SNO NUMBER(3)

10 7. GENERATION_BILATERAL :
It contains detail of power generated at various power houses (Shanan,RSD, Yamuna, Khara) from which Himachal Pradesh get the bilateral share in 15 minutes block basis for whole day. Values stored are in MHW. Station_code field contains the name of power House. Station_No field contains the code a)                                                                                          0 for Forecasted b)                                                                                          99 for Actual Primary Key: STATION_CODE, DATE_TIME, REVISION_NO, EFFECT_DATE Name Null? Type STATION_CODE NOT NULL VARCHAR2(15) DATE_TIME NOT NULL DATE REVISION_NO NOT NULL NUMBER(2) EFFECT_DATE NOT NULL DATE TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) ………………………………………………………………………… TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TOTAL_ALL NUMBER(8,1) STATION_SNO NUMBER(3)

11 8. LOSSES: It contains the Losses applicable in northern region. Losses are informed by the NRLDC on weekly basis. Primary Key: SNO, DATE_FROM Name Null? Type SNO NUMBER(10) DATE_FROM DATE DATE_TO DATE LOSS NOT NULL CHAR(10)

12 9. NREB_FREQUENCY: It contains the frequency in 15 minutes block basis. This values are captured from . This values are used in REA module. Primary Key: EFFECT_DATE Name Null? Type EFFECT_DATE NOT NULL DATE TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) ………………………………………………………………………… TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1)

13 10. POWER_STATION: It contains the name of all the power houses. Name Null? Type SNO NUMBER(3) NAME VARCHAR2(30) LOCATION VARCHAR2(30) CAPACITY NUMBER(5) REMARKS VARCHAR2(100) CODE_ VARCHAR2(10) CODE_ VARCHAR2(10) CODE_ VARCHAR2(10) CODE_ VARCHAR2(10) CODE_ VARCHAR2(10)

14 11. REVISION_ DRAWAL: This table stores the all revision of generation schedule of all the power houses which are under NRLDC and from which Himachal Pradesh gets the central sector share. This data is captured from /Scheduling/Drawal Schedule/Himachal Pradesh. NRLDC do the revision in the generation schedule of the power houses as per the actual situation. Normally this revision varies from 30 to 40. Structure of SNO : YYYYMMDDR99 eg R01, eg R12 Primary Key: SNO Name Null? Type SNO NOT NULL CHAR(11) DATE_TIME DATE REVISION_NO CHAR(2) EFFECT_DATE DATE

15 12. SCHEDULE_ DRAWAL: It stores the schedule of generation in 15 minutes block basis of the power houses from which HP gets the central sector share. All this values are in MWH. Generation schedule for all the revision are stored. Revision issue date and effect date is stored in the Revision_Drawal table. Primary Key: SNO Foreign Key: SNO reference Revision_ Drawal Name Null? Type STATION_CODE NOT NULL VARCHAR2(15) DATE_TIME NOT NULL DATE REVISION_NO NOT NULL NUMBER(2) EFFECT_DATE NOT NULL DATE TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) ………………………………………………………………………… TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TOTAL_ALL NUMBER(8,1) STATION_SNO NUMBER(3)

16 13. REVISION_ALLTRANSACTION_OA:
It stores the detail of power imported or Exported from various utilities. This Table stores the detail of the revisions only and the schedule in 15-minute block basis stored in different table. NRLDC do the revision in this schedule as per the actual situation. Normally this revision varies from 30 to 40. Structure of SNO : YYYYMMDDR99 eg R01, eg R12 Primary Key: SNO Name Null? Type SNO NOT NULL CHAR(11) DATE_TIME DATE REVISION_NO CHAR(2) EFFECT_DATE DATE

17 14. SCHEDULE_ALLTRANSACTION_OA:
It stores the schedule of power imported and/or exported from various utilities in 15 minutes block basis. All this values are in MWH. Schedule for all the revision are stored. Revision issue date and effect date is stored in the Revision_AllTransaction_OA table. Primary Key: SNO Foreign Key: SNO reference Revision_AllTransaction_OA Name Null? Type STATION_CODE NOT NULL VARCHAR2(15) DATE_TIME NOT NULL DATE REVISION_NO NOT NULL NUMBER(2) EFFECT_DATE NOT NULL DATE TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) ………………………………………………………………………… TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TOTAL_ALL NUMBER(8,1) STATION_SNO NUMBER(3)

18 15. REVISION_IMPLEMENTATION:
This table stores the final generation schedule of all the power houses which are under NRLDC and from which Himachal Pradesh gets the central sector share. This data is captured from /Implemented Schedules/Form C. As it is the final implemented schedule, so revision no. 99 is given to it. This schedule is posted on NRLDC website after 3 days. This Table stores the detail of the revisions only and the schedule in 15 minute block basis stored in different table Structure of SNO : YYYYMMDDR99 eg R01, eg R12 Primary Key: SNO Name Null? Type SNO NOT NULL CHAR(11) DATE_TIME DATE REVISION_NO CHAR(2) EFFECT_DATE DATE

19 16. SCHEDULE_IMPLEMENTATION :
It stores the final schedule of generation in 15 minutes block basis of the power houses from which HP gets the central sector share. All this values are in MWH. Revision issue date and effect date is stored in the Revision_Implementation table. Primary Key: SNO Foreign Key: SNO reference Revision_ Implementation Name Null? Type STATION_CODE NOT NULL VARCHAR2(15) DATE_TIME NOT NULL DATE REVISION_NO NOT NULL NUMBER(2) EFFECT_DATE NOT NULL DATE TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) ………………………………………………………………………………………. ……………………………………………………………………………………… TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TOTAL_ALL NUMBER(8,1) STATION_SNO NUMBER(3)

20 17. REVISION_ ALLTRANSACTION:
It stores the final schedule of power imported or Exported from various utilities. This Table stores the detail of the revisions only and the schedule in 15 minute block basis stored in different table. This data is captured from /Implemented Schedules/All Transaction. As it is the final implemented schedule, so revision no. 99 is given to it. This schedule is posted on NRLDC website after 3 days. Structure of SNO : YYYYMMDDR99 eg R01, eg R12 Primary Key: SNO Name Null? Type SNO NOT NULL CHAR(11) DATE_TIME DATE REVISION_NO CHAR(2) EFFECT_DATE DATE

21 18. SCHEDULE_ ALLTRANSACTION:
It stores the final schedule of power imported and/or exported from various utilities in 15 minutes block basis. All this values are in MWH. Revision issue date and effect date is stored in the Revision_AllTransaction table. Primary Key: SNO Foreign Key: SNO reference Revision_ AllTransaction Name Null? Type STATION_CODE NOT NULL VARCHAR2(15) DATE_TIME NOT NULL DATE REVISION_NO NOT NULL NUMBER(2) EFFECT_DATE NOT NULL DATE TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) ………………………………………………………………………… TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TOTAL_ALL NUMBER(8,1) STATION_SNO NUMBER(3)

22 19. REVISION_ENTITLEMENT:
This table stores the proposed generation schedule of all the power houses which are under NRLDC and from which Himachal Pradesh gets the central sector share. This data is captured from /Implemented Schedules/Form C. As it is the final implemented schedule, so revision no. 99 is given to it. This schedule is posted on NRLDC website after 3 days. This Table stores the detail of the revisions only and the schedule in 15 minute block basis stored in different table Structure of SNO : YYYYMMDDR99 eg R01, eg R12 Primary Key: SNO Name Null? Type SNO NOT NULL CHAR(11) DATE_TIME DATE REVISION_NO CHAR(2) EFFECT_DATE DATE

23 20. SCHEDULE_ENTITLEMENT:
It stores the proposed schedule of generation in 15 minutes block basis of the power houses from which HP gets the central sector share. All this values are in MWH. Revision issue date and effect date is stored in the Revision_Entitlement table. . Primary Key: SNO Foreign Key: SNO reference Revision_Entitlement Name Null? Type STATION_CODE NOT NULL VARCHAR2(15) DATE_TIME NOT NULL DATE REVISION_NO NOT NULL NUMBER(2) EFFECT_DATE NOT NULL DATE TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) ………………………………………………………………………… TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TOTAL_ALL NUMBER(8,1) STATION_SNO NUMBER(3)

24 21. SCHEDULE_VS_ACTUAL: This table stores the Schedule Drawal, Actual Drawal of HP in 15 minute block basis. It also stores the frequency of the northern region in 15 minute block basis. This data is captured from Primary Key: EFFECT_DATE, TIME_BLOCK Name Null? Type EFFECT_DATE NOT NULL DATE TIME_BLOCK NOT NULL NUMBER(2) FREQUENCY_CODE NOT NULL NUMBER(2) SCHEDULE NOT NULL NUMBER(6,2) ACTUAL NOT NULL NUMBER(6,2)

25 22. SCHEDULE_VS_ACTUAL_AND_OTHER :
This table stores the Schedule Drawal, Actual Drawal , Demand of HP, Frequency in 15 minute block basis. This values is entered by the user in control room as required in Day Ahead Module. Primary Key: STATION_CODE, DATE_TIME , REVISION_NO Name Null? Type STATION_CODE NOT NULL VARCHAR2(10) DATE_TIME NOT NULL DATE REVISION_NO NOT NULL NUMBER(2) EFFECT_DATE NOT NULL DATE TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) ………………………………………………………………………… TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TOTAL_ALL NUMBER(8,1) STATION_SNO NUMBER(3)

26 23. SHARED_PROJECTS: This table stores the Schedule of generation from shared projects (Chibbro , Dhakrani , Dhalipur, Khodri, Kulhal , Ranjit Sagar) from which HP gets the share. These values are stored in MWH and in 15 minutes block basis. This values are captured from Projects. Primary Key: STATION_CODE, EFFECT_DATE Name Null? Type EFFECT_DATE NOT NULL DATE STATION_CODE NOT NULL VARCHAR2(20) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) ………………………………………………………………………… TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TIME_BL_ NUMBER(6,1) TOTAL_ALL NUMBER(8,1) STATION_SNO NUMBER(3)

27 24. SURRENDER_ENERGY: This table is used to store the percentage of power surrender from RF, LF, GF power station. ( Anta,Dadri etc). This table is used in Day Ahead module. Primary Key: EFFECT_DATE,STATION_CODE Name Null? Type EFFECT_DATE NOT NULL DATE STATION_CODE NOT NULL VARCHAR2(10) PER_SURRENDER NOT NULL NUMBER(6,2)

28 25. SHARE_ALLOCATION: This table stores the share allocation in different time block for HP from BairaSiul, Chamera –I , Chamera-II and NJCP power station. Name Null? Type DATE_FROM NOT NULL DATE DATE_TO NOT NULL DATE TIME_FROM NOT NULL NUMBER(2) TIME_TO NOT NULL NUMBER(2) STATION_CODE NOT NULL VARCHAR2(10) GOHP NOT NULL NUMBER(4,2) SOR NOT NULL NUMBER(4,2) UNALLOCATED NOT NULL NUMBER(4,2) TOTAL NOT NULL NUMBER(5,2)

29 26. SHARE_ALLOCATION_ALL_STATION:
This table stores the share allocation in different time block for HP for the power station under NRLDC. Name Null? Type DATE_FROM NOT NULL DATE DATE_TO NOT NULL DATE TIME_FROM NOT NULL NUMBER(2) TIME_TO NOT NULL NUMBER(2) STATION_CODE NOT NULL VARCHAR2(10) GOHP NOT NULL NUMBER(4,2) SOR NOT NULL NUMBER(4,2) UNALLOCATED NOT NULL NUMBER(4,2) TOTAL NOT NULL NUMBER(5,2)

30 27. UI_RATE: This table stores UI_Rate based on Frequency. This table is used to calculate the rate of power based ABT(Availability Based Tariff). Name Null? Type DATE_FROM NOT NULL DATE DATE_TO NOT NULL DATE FREQ_FROM NOT NULL NUMBER(5,2) FREQ_TO NOT NULL NUMBER(5,2) PAISE_UNIT NOT NULL NUMBER(5,1)

Download ppt "SLDC Software SHAKTI Data Dictionary."

Similar presentations

Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.

Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
SLIDE 1 Extended reserve Technical working group 11 September 2014.

SLIDE 1 Extended reserve Technical working group 11 September 2014.
INTRA STATE ABT Necessity Issues Implementation. Some of the features of New National Electricity Policy – Feb.’05 Appropriate Commissions to undertake.

INTRA STATE ABT Necessity Issues Implementation. Some of the features of New National Electricity Policy – Feb.’05 Appropriate Commissions to undertake.
1 THE INDIA ELECTRICITY MARKET TIME LINE REAL TIME 15 MT BLOCKS LONG TERM LOAD FORECAST FUND MOBILISATION 10-5 YEARS POWER PURCHASE AGREEMENTS CAPACITY.

1 THE INDIA ELECTRICITY MARKET TIME LINE REAL TIME 15 MT BLOCKS LONG TERM LOAD FORECAST FUND MOBILISATION 10-5 YEARS POWER PURCHASE AGREEMENTS CAPACITY.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.

Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
1. 2 ENERGY MANAGEMENT SYSTEM AN OVERVIEW AN OVERVIEW.

1. 2 ENERGY MANAGEMENT SYSTEM AN OVERVIEW AN OVERVIEW.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.

Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
With amendments w.e.f. 53.5.2010.  (1) In these regulations, unless the context otherwise requires,-  (a) ‘Act’ means the Electricity Act, 2003 (36.

With amendments w.e.f  (1) In these regulations, unless the context otherwise requires,-  (a) ‘Act’ means the Electricity Act, 2003 (36.
14-1 Goals of Database Design A database should provide for efficient storage, update, and retrieval of data. A database should be reliable—the stored.

14-1 Goals of Database Design A database should provide for efficient storage, update, and retrieval of data. A database should be reliable—the stored.
The Functions of Operating Systems Desktop PC Operating Systems.

The Functions of Operating Systems Desktop PC Operating Systems.
LOAD FORECASTING T SRINIVAS MANAGER SRLDC. MAIN COMPONENTS OF THE GRID  GENERATION  LOAD  TRANSMISSION NETWORK DETAILS.

LOAD FORECASTING T SRINIVAS MANAGER SRLDC. MAIN COMPONENTS OF THE GRID  GENERATION  LOAD  TRANSMISSION NETWORK DETAILS.
GRID OPERATION AND CONTROL. MAIN COMPONENTS OF THE GRID  GENERATION  LOAD  TRANSMISSION NETWORK.

GRID OPERATION AND CONTROL. MAIN COMPONENTS OF THE GRID  GENERATION  LOAD  TRANSMISSION NETWORK.
Quiz questions. 1 A data structure that is made up of fields and records? Table.

Quiz questions. 1 A data structure that is made up of fields and records? Table.
SCHEDULING METHODOLOGY The station-wise (Ex-bus) capability would be submitted by the ISGSs in the specified format. ISGSs would declare the capability.

SCHEDULING METHODOLOGY The station-wise (Ex-bus) capability would be submitted by the ISGSs in the specified format. ISGSs would declare the capability.
HYDRO TARIFF Commission Tariff Notification 26/03/01 Commission Tariff Notification 26/03/01 Applicable Period 01/04/01 to 31/03/04 Applicable Period 01/04/01.

HYDRO TARIFF Commission Tariff Notification 26/03/01 Commission Tariff Notification 26/03/01 Applicable Period 01/04/01 to 31/03/04 Applicable Period 01/04/01.
GLOBEX INFOTEK Copyright © 2013 Dr. Emelda Ntinglet-DavisSYSTEMS ANALYSIS AND DESIGN METHODSINTRODUCTORY SESSION EFFECTIVE DATABASE DESIGN for BEGINNERS.

GLOBEX INFOTEK Copyright © 2013 Dr. Emelda Ntinglet-DavisSYSTEMS ANALYSIS AND DESIGN METHODSINTRODUCTORY SESSION EFFECTIVE DATABASE DESIGN for BEGINNERS.
1 INTRA – STATE AVAILABILITY BASED TARIFF (ABT) A Presentation on INTRA – STATE AVAILABILITY BASED TARIFF (ABT)

1 INTRA – STATE AVAILABILITY BASED TARIFF (ABT) A Presentation on INTRA – STATE AVAILABILITY BASED TARIFF (ABT)
IT APPLICATIONS TO ELECTRIC POWER PROJECT GUIDE : DR NDR SARMA GROUP - 10 PROJECT MEMBERS ABHISHEK DIXIT, ANUBHAV AGARWAL, E. GIRISH, SANDEEP CHANDNA.

IT APPLICATIONS TO ELECTRIC POWER PROJECT GUIDE : DR NDR SARMA GROUP - 10 PROJECT MEMBERS ABHISHEK DIXIT, ANUBHAV AGARWAL, E. GIRISH, SANDEEP CHANDNA.
Mr C Johnston ICT Teacher

Mr C Johnston ICT Teacher
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Chapter 9 Designing Databases 9.1.

Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Chapter 9 Designing Databases 9.1.

Similar presentations

Ads by Google