InteliMains
NT
, SW version 3.2.0
InteliMains-NT-MCB-MGCB-3.2.0-Reference Guide.pdf,
©ComAp – April 2015
85
Case #3:
Gen-set 1 running hours = 250 -> running hours considered in RHE = 100 (150-RunHoursBase)
Gen-set 2 running hours = 450 -> running hours considered in RHE = 200 (250-RunHoursBase)
Gen-set 3 running hours = 750 -> running hours considered in RHE = 250 (500-RunHoursBase)
The gen-set 1 has the lowest RHE1 = 100 h. By applying the SwapTime formula, we get the run time
of gen-set 2 before next swapping:
SwapTimeG1 = 200
– 100 + 10 + 1 = 111
Till the step 5, the evolution of the gen-set swapping is the same as in the case #1, just gen-set 1 and
gen-set 2 involve. In the step 6 the gen-set 2 can run only 17 hours (previously 22 hours) because the
gen-set 3 involves. The evolution of RHE1, RHE2 and RHE3 is shown on the figure below.
240
250
260
270
280
290
300
310
RHE
Step
1
2
3
4
5
6
7
8
9
10
11
12
13
Figure:
Running Hours Equalization example, 3 gen-sets with different initial RHE
step
0
1
2
3
4
5
6
7
8
9
10
11
12
13
RHE1
100 211 211 233 233 255 255 255 272 272 272 288 288 288
RHE2
200 200 222 222 244 244 261 261 261 277 277 277 294 294
RHE3
250 250 250 250 250 250 250 266 266 266 283 283 283 299
Run G1 (
Δ RHE1)
0
111
0
22
0
22
0
0
17
0
0
16
0
0
Run G2 (
Δ RHE2)
0
0
22
0
22
0
17
0
0
16
0
0
17
0
Run G3 (
Δ RHE3)
0
0
0
0
0
0
0
16
0
0
17
0
0
16
N
OTE
:
Setting
Pwr management:
#RunHrsMaxDiff
= 5 does not mean that gen-sets swap every 5 hours.
The Swap time is determined by the formula stated above. Please read the entire chapter Running
hours equalization for better understanding.
In the case
Pwr management:
#RunHrsMaxDiff
is set to 0 and all gen-set in the group are at the
same initial point (RHE are equal), the gen-set swapping happens every hour.
N
OTE
: