Difference between revisions of "User talk:Wekelwrady"

From SgWiki
Jump to navigation Jump to search
(2 intermediate revisions by the same user not shown)
Line 2: Line 2:




==Re: Alternative Travel Options==
==Re: Runtime==
Hi
Hi,


Noted about your opinion about keeping the entire line for the ease of dispersal and waiting time during large-scale disruption.
The MRT Runtime have been fully updated. It actually mirror closer to the actual runtime.


In the example of what I seek earlier, if there is a large-scale disruption where the whole line is affected (Using Pasir Ris – Boon Lay), FBB are activated based on the following cases.
I had also futureproof the runtime for TEL1-3 in case SMRT decided to add padding to it, just like other lines, because so far the dwell time for TEL is much shorter than the rest, on par with the dwell time SBS Transit uses.
* Ad-hoc/Unplanned disruption (To be confirmed/ Waiting for case study as recently there isn’t):
** Operators in charge of any affected sectors (in the case of EWL: All operators) will ply the full route – 1FBB service from end to end, e.g. Pasir Ris to Tuas Link. I had seen Tower Transit bus plying Route familiarisation for TEL TE1 to TE9 even though is under SMRT, and SMRT doing it for TE9 to TE22 even though is under Tower Transit
** In the event of large-scale disruption, special express variants will be operated, plying at KEY MRT stops (or high commuters flow stops only, e.g. Skipping stations like Kembangan, Simei)
* Planned disruption:
** Operators in charge of the affected sectors ply only its affected sectors. Commuters are advised to change shuttle to continuing their journey.


Regarding alternative, I thought that the West is similar to the East where finding alternative is easier within the same area in those sections. I only know the North is screwed-up as alternative is very complicated due to the limited bus route. Hahaha. But nevertheless, let us try our best to provide the best route, we would not know if someone managed to find another better alternative.
So - NEL, DTL, TEL will have a longer runtime (±3 mins) as compared to the actual runtime in case dwell time increases.


Thanks for your help in maintaining & updating sgWiki! :)
I will spend some time for LRT due to the line is a loop in nature, and the data value for the table it may not necesaaty be symmetrical.


Regards
Regards

Revision as of 21:20, 24 April 2024

Just discuss below.


Re: Runtime

Hi,

The MRT Runtime have been fully updated. It actually mirror closer to the actual runtime.

I had also futureproof the runtime for TEL1-3 in case SMRT decided to add padding to it, just like other lines, because so far the dwell time for TEL is much shorter than the rest, on par with the dwell time SBS Transit uses.

So - NEL, DTL, TEL will have a longer runtime (±3 mins) as compared to the actual runtime in case dwell time increases.

I will spend some time for LRT due to the line is a loop in nature, and the data value for the table it may not necesaaty be symmetrical.

Regards