Advanced Override Cases
This section describes the behaviours where multiple date overrides have been applied.
Behaviours differ if the override is applied on a single batch without constraints vs multiple batches with the same constraint.
Below describe the behaviours where multiple date overrides get applied. B
ehaviour differs if the override is applied on the single batch within constraints vs multiple batches with the same constraint
Simple - Two Subclasses Sharing The Same Constraints (FIC Family)
Below shows deployments without any overrides applied.
Deployments can be edited by selecting Edit Project from the deployment.
A prefiltered modal is opened to edit FIC / SS / DT dates.
FIC Start / End Earlier Than Default (Batch With FIC)
FIC stage is performed at the overridden dates. The remaining stages are as late as possible in time for ETCS.
FIC highlighed in red with warning - manual override.
FIC Start / End Earlier Then Default (Batch Without FIC)
FIC stage is performed on the batch that the override is set on.
FIC highlighted in red with warning - manual override.
FIC Start / End Set Later Than Default (Batch With FIC)
FIC positioned to match FIC date. All remaining stages are pushed back to match constraints.
- Warning on FIC - starting in the past, date overridden.
- Warning on SS - breach of ETCS date.
- Warning on DT - breach of ETCS date.
FIC Start / End Set Later Than Default (Batch Without FIC)
Same as above, but FIC on the opposite subclass.
SS Start / End Earlier Than Default On Earlier SS (Batch With FIC)
SS with override is aligned to the SS start date override. FIC and LC are pushed earlier to satisfy the constraint. The remianing SS and DT are fit in time for ETCS.
SS Start / End Earlier Than Default On Earlier SS (Batch Without FIC)
SS with override aligned with the date the same as above. Remaining overrides are as soon as possible after.
SS Start / End Later Than Default (Batch With FIC)
Earlier SS is aligned to overridden date.
Later SS is chosen to be generated before the earlier SS to satisfy the ETCS date.
SS Start / End Later Than Default (Batch Without FIC)
Later SS is set to match the overridden date.
Remaining deployments are adjusted to match, but impossible to satisfy the ETCS date.
DT Start / End Earlier Than Default (Batch With FIC)
DT with override set to match the date overrides. The remaining deployments are set as soon as possible before that.
DT Start / End Earlier Than Default (Batch Without FIC)
DT aligned to overridden date. Remaining deployments are moved to match.
Simple - Multiple Overrides
Move FIC Earlier, Align The Rest Of The Deployments After FIC
FIC end override and DT end override.
FIC is adjusted to hard set date. DT end override is aligned and deployments scheduled as soon as possible before DT.
Move FIC Earlier, But Provide DT Override Breaking Override Aiming To Complete Deployments Earlier
FIC end override and DT end override too early to fit all deployments.
FIC is set to match the user override. DT is not aligned with forced dates due to constraints.
Move FIC Earlier, But Provide SS Override Breaking Override Aiming To Complete Deployments Earlier
FIC is aligned with the override date. SS is aligned with override date.
Constraints are broken as SS overlaps with LC.
Move FIC Earlier, But Provide SS Override Breaking Override Aiming To Complete Deployments Earlier. Override Another SS
Results are the same as above apart from the second SS aligning with the new override date.
Complex - Various Subclasses Sharing Some Constraints (FIC Family)
FIC Override, 360/1 SS override and 180/1 SS override.
Deployments with overrides align to overriden dates. Remaining deployments scheduled in time for ETCS.
Constraights Editing Functionality.
We will be using Aventra FIC family for this example.
Without constraint changes, it looks like the following:
Batch Exclusion
Removing 730/2 removes the batch from the deployment chain.
TOC RFP Date
This configuration sets the date when the contract for TOC commences - setting the earliest possible FIC date for the TOC.
Setting 1/1/2030 for West Midlands Railway. The remaining interventions are pushed forward.
35 Year Old Trains To Be Changed To "Replace With New Train"
Trains are 38 years old at the ETCS date. We will attempt to change the rule to 40 years.
Effect - trains are keeping their original deployment.
Sequencing Constraint Override - Volume
By default, only one train per TOC class can be installed at the same time. by changing the volume to 2 we can allow two trains to be deployment at the same time for TOC and class.
LC and SS has been halved in duration.
DT is unaffected due to parallel characteristic.
FIC is unaffected due to having one train.
Sequencing Constraint Override - Attributes
Adding ROSCO as an extra constraint to make the constraint - only one train can be deployed per TOC. Train class / ROSCO combination allows for subclass 0 to be done in parallel with subclasses 2 and 3 before of a different ROSCO on subclass 0.
Limitation Constraint Override - Volume
Within the edit modal we are going to edit the LC constraints.
The volume is changed to 10 to enforce 10 trains ato go through the LC stage at once.
10 trains in LC, making a total of 11 trains with FIC. This shows no SS on class 357/2
Limitation Constraint Override - Attributes
Limitation constraint attributes have to be updated to match on all stages.
If this is not completed, Rail BI will display an error.
Added ROSCO as an extra limitation constraint on top of deployment strategies and FIC family. We are enforcing an extra FIC for each ROSCO.
FICs and LCs are not deployed is parallel due to the sequencing constraints being TOC / Class not TOC / Class / ROSCO.
Adding ROSCO to sequencing constraint as above allows for parallel deployment of FICs and LCs.
New Deployment Strategy And Deployment Strategy Override
To Override the deployment strategy,go to advanced settings within the option:
Selecting new deployment strategy for 357/0 subclass.
FIC per deployment strategy. Deployments follow the sequencing constraint restriction.
Rail BI highlights that the deployment strategy was overridden.
Train - Track Mapping Adjustment
This is not a realistic scenario.
To demonstrate the impage, we use Hitachi Javelin Class 395. Without any changes, the deployment looks like this:
The target date is coming from Scheme A.04 on 1/6/2039
We add one of the interlockings of G.05b - Grantham scheme dated 1/12/2033 to the batch to scheme map of 395
Mapping of train branches to interlockings can be adjusted via the advanced setting
We search for 395, then add Grantham.
Upon rebuild, the 395 batch is picking up the date from G.05b as expected
Change of batch to Scheme requires the rebuild of the ETCS Level 2 projects so we need to trigger the option rebuild. This can take around 20 min
This information can also be found in the following PDF - Override Cases Methodology