You are on page 1of 5

Load Flow Calculation and Its Application Project Documentation

Three projects has been developed for performing load flow calculation for low and medium network. Each
projects are available as a final solution. To activate the project, press the Open Data Manager icon on the main
toolbar and activate the necessary project (see Figure 1). Given projects can be used for studies but it is advised
to reconstruct the new projects with given data in the chapter and supporting documents for better learning.

Figure 1: Projects for Load Flow Calculation and Its Application

1. Low Voltage Network Study (Case I)


In case study I, network is configured as radial-ring configuration with six feeders as shown in Figure 2, for detail
see section 1.3.1 Case Study: Low Voltage Network. To start the study, reset the lines type as shown in Figure 3
and then follow the guideline given in the Chapter 1.

Figure 2: Low Voltage Network for case study I

1
Figure 3: Resetting Line Types Setting for Case Study I

2. Medium Voltage Network Study (Case II)


In study case II, network is configured as ring mesh configuration with small generation in-feed as shown in
Figure 4. Required line types and transformer types are assigned already and it is not required to reset them for
this study. Generators parameter are given in section 1.3.2. Case Study: Medium Voltage Network. To start the
study make sure Power-Frequency Controller (ElmSecctrl) and Station Controllers (ElmStactrl) are set to out of
services as shown in Figure 5 and 6. ElmSecctrl and ElmStactrl can be deleted for starting the study and then
recreate them following chapter guideline. Also, it is important to consider the GridA as slack source and GridB
as PQ source. GridB can be replaced with ElmLod having same active and reactive power.

Figure 4: Medium Voltage Network for Case Study II

2
Figure 5: Dialog Window of Power-Frequency Controller

Figure 6: Dialog Window of Station Controller

3. Load Profile Study (Case III)


In case study III, low voltage network that has been developed in case study I (final solution), is used for load
profile analysis (see Figure 1 for network configuration). To start the study, make sure the variation LoadProfile
is not activated (see Figure 7). The objective of the project is to demonstrate the application of DPL to calculate
the load flow over the period of time to be able to generate the load profile of the network. The variation is created
for the Aug-Sep 2014, thus profile is generated from 1st Jan 2014 to 31st Dec 2014.

Figure 7: Load Profile Case Study Project Folders

3
Note that to create the plot and report using ComTablereport, sub DPL script is required with the title Create.
Detail of expansion stages are listed in Table 1.
Table 1: Expansion Stage Configuration

Expansion Stage Activation Time Network Change

Stage A 25th Aug 2014 Load (L21, L23, L25, L27) out of serves

Load (L21, L23, L25, L27) in serves,


Stage B 10th Sep 2014
Load (L17, L19, L24, L26) out of serves
Load (L21, L23, L25, L27, L17, L19,
Stage C 18th Sep 2014
L24, L26) out of serves

4. Customization of Load Profile Project


If variation is not required to consider for generating profile then year and time is not important to adjust, because
the profile is developed per day of the year and the characteristic values in ChaVec are independent of year of
SetTime object. In this case, instruction at line 26 shown in Figure 8 is recommended to use as it will adjust the
SetTime object date to system date. First days of the year will automatically set by the instruction at line 58. But
if variation is required to be considered in the profile then it is necessary to either create the variation for the
analysing year or adjust the year in SetTime object through DPL. In Figure 8 at line 27 the value 1388533039
will adjust the SetTime Object to 1st Jan 2014 at 00:37:19 (h:m:s). This value is calculated in second since 1st Jan
1970 at 00:00:00 (h:m:s).

Figure 8: DPL Script of Load Profile Study

Use the following steps to reconstruct the project for load profile analysis using case study I project.
Import the case study I, rename it to Load Profile and activate the project. Make sure all the lines have
recommended types mentioned in section 1.3.1.

4
Change the feeder scale factor value and assign the characteristics according to the steps describe in
section 1.3.3.
Copy the script LoadProfile and execute.
Table 2: Feeders Scale Factor Value for Load Profile Analysis

Feeders Scale Factor


2_2-6 530
2_2-8 520
2_4-2 555
3_3-5 540
3_3-7 560
3_3-9 550

To create the variation use following steps


Open Data Manager variation folder of network model, press new from the toolbar and select variation
(IntScheme) and press OK. Named the variation LoadProfile. On advanced page of basic data of
IntScheme change the start and end time as required (e.g. start time: 22/08/2014 and end time:
22/09/2014). Adjust only date, time is not necessary as explain early. Enable the option Restricted
Validity Period and press OK.
A dialog box will open for the confirmation to activate this variation. Press yes. The dialog window of
expansion stage will automatically be open. Rename it to Stage A and adjust the activation time as
required (e.g. 25th Aug 2014 according to case study III). Press OK this will create expansion stage. An
info dialog will open, press OK to continue. Further dialog will be open asking to change study time to
expansion stage time, press yes to continue.
Make required changes in the network to record in the newly created expansion stage (e.g. set loads serves
according to Table 1).
Create another expansion stage by press new button from toolbar of data manager inside the created
variation LoadProfile. Rename the expansion stage to Stage B and change the activation time (e.g.
10th Sep 2014). A dialog will open asking to make this stage as active. Press yes to continue. The new
stage will be created. Make required changes as required or according to Table 1.
Similarly, create another expansion stage having name Stage C and activation time 18th Sep 2014.
Again make changes according to Table 1.
Re-execute the script with the variation active.