InteliMains
NT
, SW version 3.2.0
InteliMains-NT-MCB-MGCB-3.2.0-Reference Guide.pdf,
©ComAp – April 2015
82
EXAMPLE:
The system structure is shown on the figure above. The InteliMains controller assumes the role of
master in priority swapping and swaps priority of the engines based on their running hours.
3 cases are considered:
Case #1: 2 gen-gets available
Case #2: 3 gen-gets available with same initial RHE.
Case #3: 3 gen-gets available with different initial RHE.
Case #1:
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)
Both gen-sets have the same nominal power of 700 kW. Originally, priority of gen-sets was G1 = 2,
G2 = 1. Load demand in this example is constant and it is 500 kW (i.e. only one engine is running at
any time). In this case, the InteliMains controller sets the engine priority of the gen-set 1 to 1 because
it has the lowest considered RHE and the difference between RHE2 (i.e. considered RHE of gen-set
2) and RHE1 is higher than #RunHrsMaxDiff that is set to 10h.
The gen-set 1 runs for 100 hours to equalize the RHE of both gen-sets. The gen-set 1 keeps running
until the difference between RHE1 and RHE2 exceeds #RunHrsMaxDiff (i.e. 10h). The gen-set 1 runs
100 + #RunHrsM 1 = 100 + 10 + 1 = 111 hours. After 111 hours the gen-sets 2 has the lowest
RHE and the difference between RHE1 and RHE2 is higher than #RunHrsMaxDiff. The gen-set 2 runs
11 hours to equalize the RHE of both gen-sets and then additional #RunHrsM 1 hours (i.e. 11
+ 10 + 1 = 22 hours). The evolution of RHE1 and RHE2 is shown on the figure below.
Run hours #RunHoursBase
RHE
Gen-set #1
250
150
100
Gen-set #2
450
250
200