Bus Contracting Model (part 2)
-
Originally posted by TPS Timothy Mok:
SBS is not stupid to do all these kind of things. Only SMRT does, change here change there.
They will only use the BCM thing if it uses the existing depot.
Because they got many depots.Indirectly SMRT 61 & 67 is still dual depot although they're using KJDEP buses.Amdep BCs still work as per normal.
About this Seletar i got strong feelings only two operators is shortlisted...Not SBST or SMRT or GAS...and one more candidate is Busway.
My instinct for Bukit Merah is only 3 operators shortlisted:GAS and two new operators.
-
Being wanted to say this for awhile le but got no time to post it so:
Not sure is it me or I noticed most SMRT AMDEP trunk services which uses the expressway are going damn slow (I not sure about 963 965 966). I noticed 969 has being going damn slow on the eway which now 161 168 858 overtook it along the way.About svc 171, there was one morning I took, it went like 30kph along BKE. Wonderful
-
Originally posted by bus555:
Being wanted to say this for awhile le but got no time to post it so:
Not sure is it me or I noticed most SMRT AMDEP trunk services which uses the expressway are going damn slow (I not sure about 963 965 966). I noticed 969 has being going damn slow on the eway which now 161 168 858 overtook it along the way.About svc 171, there was one morning I took, it went like 30kph along BKE. Wonderful
Very true leh... whenever i took 89/109 to changi village..... kept noticing DD 969(A95) going very slowly on leftmost lane and other sbst buses had to overtake it..... similar for 965(only once)/969 >> Yishun when taking 161
-
Originally posted by rajboi37:
Very true leh... whenever i took 89/109 to changi village..... kept noticing DD 969(A95) going very slowly on leftmost lane and other sbst buses had to overtake it..... similar for 965(only once)/969 >> Yishun when taking 161
Runtime and buses added over the years,If they travelled 60kmh they're prone to bunch at Yishun..I agreed that runtime should be cut 2-3 mins.
-
how about at night? few months back when 969 still had half citaro fleet it topped 60..
-
Originally posted by SMB5007J:
how about at night? few months back when 969 still had half citaro fleet it topped 60..
After 8.30pm where split shift buses went back,Then you see them travel 60 and sometimes overtake other SBST/GAS buses.
-
Originally posted by carbikebus:
Runtime and buses added over the years,If they travelled 60kmh they're prone to bunch at Yishun..I agreed that runtime should be cut 2-3 mins.
In fact i rmb their run time for khatib to tamp is like 40 min, which is like 10 min extra compared to last time. But with the 3 new bus stops along Tamp conc, i think 5 min extra is sufficient. But yes, 969 has been going pretty slow, and maybe what was discussed is true, where during off peak will be faster
-
Originally posted by carbikebus:
Runtime and buses added over the years,If they travelled 60kmh they're prone to bunch at Yishun..I agreed that runtime should be cut 2-3 mins.
Hello, 2-3 mins cut is not sufficient, svc 969 runtime can easily shave at least 5 minutes.
Standard timetable from Tampines (3rd last bus out from Tampines):
+01 min: Tampines Concourse stops
+02 mins: Stop at Tamp Ave 9
+16 mins: TPE stop
+33 mins: First stop at Lentor Ave
+38 mins: Khatib MRT
+43 mins: Yishun MRT
+48 mins: Last stop at Yishun
+54 mins: 3M @ Gambas Ave
+57 mins: Admiralty MRT
+64 mins: Woodlands MRT/IntAs you can see, SMRT has scheduled a grand total of 22 mins between the TPE stop and the stop at Khatib MRT during the off-peak hours. Pre-GCM, this journey took about 12 mins in off-peak hours, and 15 mins in peak hours. Of course if you artificially add 10 mins into the schedule, then the svc 969 buses have to crawl between Punggol and Yishun!
Another observation: Almost all svc 969 buses depart Tampines Int at least 5 mins later than the timing indicated on their DDUs. This seems to allow the buses to travel at normal e'way speeds to Punggol, but after that they all slow to a crawl anyway ...
Last mind-blowing observation: SMRT has given svc 858 the exact same runtime between the TPE stop and the first stop at Lentor Ave (in spite of the detour to Jln Kayu), which clearly shows that SMRT is sandbagging the svc 969 schedule for no obvious reason ...
-
Originally posted by orange28:
Hello, 2-3 mins cut is not sufficient, svc 969 runtime can easily shave at least 5 minutes.
Standard timetable from Tampines (3rd last bus out from Tampines):
+01 min: Tampines Concourse stops
+02 mins: Stop at Tamp Ave 9
+16 mins: TPE stop
+33 mins: First stop at Lentor Ave
+38 mins: Khatib MRT
+43 mins: Yishun MRT
+48 mins: Last stop at Yishun
+54 mins: 3M @ Gambas Ave
+57 mins: Admiralty MRT
+64 mins: Woodlands MRT/IntAs you can see, SMRT has scheduled a grand total of 22 mins between the TPE stop and the stop at Khatib MRT during the off-peak hours. Pre-GCM, this journey took about 12 mins in off-peak hours, and 15 mins in peak hours. Of course if you artificially add 10 mins into the schedule, then the svc 969 buses have to crawl between Punggol and Yishun!
Another observation: Almost all svc 969 buses depart Tampines Int at least 5 mins later than the timing indicated on their DDUs. This seems to allow the buses to travel at normal e'way speeds to Punggol, but after that they all slow to a crawl anyway ...
Last mind-blowing observation: SMRT has given svc 858 the exact same runtime between the TPE stop and the first stop at Lentor Ave (in spite of the detour to Jln Kayu), which clearly shows that SMRT is sandbagging the svc 969 schedule for no obvious reason ...
Hello,Popular svc they make it crawl so ppl got no choice or use other options..
-
Originally posted by orange28:
Hello, 2-3 mins cut is not sufficient, svc 969 runtime can easily shave at least 5 minutes.
Standard timetable from Tampines (3rd last bus out from Tampines):
+01 min: Tampines Concourse stops
+02 mins: Stop at Tamp Ave 9
+16 mins: TPE stop
+33 mins: First stop at Lentor Ave
+38 mins: Khatib MRT
+43 mins: Yishun MRT
+48 mins: Last stop at Yishun
+54 mins: 3M @ Gambas Ave
+57 mins: Admiralty MRT
+64 mins: Woodlands MRT/IntAs you can see, SMRT has scheduled a grand total of 22 mins between the TPE stop and the stop at Khatib MRT during the off-peak hours. Pre-GCM, this journey took about 12 mins in off-peak hours, and 15 mins in peak hours. Of course if you artificially add 10 mins into the schedule, then the svc 969 buses have to crawl between Punggol and Yishun!
Another observation: Almost all svc 969 buses depart Tampines Int at least 5 mins later than the timing indicated on their DDUs. This seems to allow the buses to travel at normal e'way speeds to Punggol, but after that they all slow to a crawl anyway ...
Last mind-blowing observation: SMRT has given svc 858 the exact same runtime between the TPE stop and the first stop at Lentor Ave (in spite of the detour to Jln Kayu), which clearly shows that SMRT is sandbagging the svc 969 schedule for no obvious reason ...
Hi mr orange28, finally got somebody realize smrt 969 is slightly slower than in the past. This is what I have observed too. Cheers. Thanks.
-
Originally posted by orange28:
Hello, 2-3 mins cut is not sufficient, svc 969 runtime can easily shave at least 5 minutes.
Standard timetable from Tampines (3rd last bus out from Tampines):
+01 min: Tampines Concourse stops
+02 mins: Stop at Tamp Ave 9
+16 mins: TPE stop
+33 mins: First stop at Lentor Ave
+38 mins: Khatib MRT
+43 mins: Yishun MRT
+48 mins: Last stop at Yishun
+54 mins: 3M @ Gambas Ave
+57 mins: Admiralty MRT
+64 mins: Woodlands MRT/IntAs you can see, SMRT has scheduled a grand total of 22 mins between the TPE stop and the stop at Khatib MRT during the off-peak hours. Pre-GCM, this journey took about 12 mins in off-peak hours, and 15 mins in peak hours. Of course if you artificially add 10 mins into the schedule, then the svc 969 buses have to crawl between Punggol and Yishun!
Another observation: Almost all svc 969 buses depart Tampines Int at least 5 mins later than the timing indicated on their DDUs. This seems to allow the buses to travel at normal e'way speeds to Punggol, but after that they all slow to a crawl anyway ...
Last mind-blowing observation: SMRT has given svc 858 the exact same runtime between the TPE stop and the first stop at Lentor Ave (in spite of the detour to Jln Kayu), which clearly shows that SMRT is sandbagging the svc 969 schedule for no obvious reason ...
In addition, they did a stupid thing of adding 3 more bus stops for 969 in Tampines which was totally not required. 969 during peak hours already full from interchange; no on can board 969 along Concourse and no one will alight as people will not stand in long queue, rather take 72, 127 or walk.
I really hope they revert 969 to express between Tampines and TPE Punggol once svc 68 starts plying Concourse.
-
Originally posted by orange28:
Hello, 2-3 mins cut is not sufficient, svc 969 runtime can easily shave at least 5 minutes.
Standard timetable from Tampines (3rd last bus out from Tampines):
+01 min: Tampines Concourse stops
+02 mins: Stop at Tamp Ave 9
+16 mins: TPE stop
+33 mins: First stop at Lentor Ave
+38 mins: Khatib MRT
+43 mins: Yishun MRT
+48 mins: Last stop at Yishun
+54 mins: 3M @ Gambas Ave
+57 mins: Admiralty MRT
+64 mins: Woodlands MRT/IntAs you can see, SMRT has scheduled a grand total of 22 mins between the TPE stop and the stop at Khatib MRT during the off-peak hours. Pre-GCM, this journey took about 12 mins in off-peak hours, and 15 mins in peak hours. Of course if you artificially add 10 mins into the schedule, then the svc 969 buses have to crawl between Punggol and Yishun!
Another observation: Almost all svc 969 buses depart Tampines Int at least 5 mins later than the timing indicated on their DDUs. This seems to allow the buses to travel at normal e'way speeds to Punggol, but after that they all slow to a crawl anyway ...
Last mind-blowing observation: SMRT has given svc 858 the exact same runtime between the TPE stop and the first stop at Lentor Ave (in spite of the detour to Jln Kayu), which clearly shows that SMRT is sandbagging the svc 969 schedule for no obvious reason ...
SMRT sucks at operating public transport.
-
Originally posted by dupdup77:
Hi mr orange28, finally got somebody realize smrt 969 is slightly slower than in the past. This is what I have observed too. Cheers. Thanks.
Yes, above I posted the timetables from the DDU from the 3rd last svc 969 bus. Mind that in the day, the runtimes are actually even longer!
-
Originally posted by BusAnalayzer:
In addition, they did a stupid thing of adding 3 more bus stops for 969 in Tampines which was totally not required. 969 during peak hours already full from interchange; no on can board 969 along Concourse and no one will alight as people will not stand in long queue, rather take 72, 127 or walk.
I really hope they revert 969 to express between Tampines and TPE Punggol once svc 68 starts plying Concourse.
In my experience there are like one or two passengers who actually alight at the second Tampines Concourse stop, maybe they find it a hassle to walk to sv 127's berth? (But svc 127 is much faster to the Concourse stops anyway ...)
There are also several passengers boarding svc 969 at the first stop, most likely transfers from svc 18/39/129 passengers?
But two things that I would say that needs to be improved:
- Improve the traffic light timings along Tampines Concourse. Right now they have ridiculously short cycle times, which should be extended.
- Just reduce the runtime for svc 969 by 10 minutes will do! So that svc 969 will return to its regular speeds along TPE ...
-
Originally posted by SBS3004X:
SMRT sucks at operating public transport.
The Mandai contract ought to be awarded to another operator other than SMRT ASAP ...
-
Originally posted by SBS3004X:
SMRT sucks at operating public transport.
Not so la...
-
Originally posted by orange28:
In my experience there are like one or two passengers who actually alight at the second Tampines Concourse stop, maybe they find it a hassle to walk to sv 127's berth? (But svc 127 is much faster to the Concourse stops anyway ...)
There are also several passengers boarding svc 969 at the first stop, most likely transfers from svc 18/39/129 passengers?
But two things that I would say that needs to be improved:
- Improve the traffic light timings along Tampines Concourse. Right now they have ridiculously short cycle times, which should be extended.
- Just reduce the runtime for svc 969 by 10 minutes will do! So
that svc 969 will return to its regular speeds along TPE
...
Do you know who plan all these?Why you see bus stop at Bus stops?
-
Originally posted by SBS3004X:
SMRT sucks at operating public transport.
Er no they dont.
If you want to base your judgement based on DDU timings I can easily say that SBST is equally culpable to this, if not worse.
-
it's true, I seen ppl taking 969 from tmi & alighting like the 2nd stop of tamp concourse
-
Once again,
This thread is only for GCM / BCM discussions.
Non-GCM / Non-BCM stuff, please discuss at other threads.
At the rate replies are posted, this thread will be filled up in less than one year since it was created in June last year!
The earlier thread lasted for around two years, and this, around one year only?
I'm okay if there has been strong discussions about BCM, but it seems that many a times, it's not related to the BCM contracts at Bulim, Loyang, Seletar or Ulu Pandan, or even the negotiated contracts (when was the last time we discussed about negotiated contracts?)
and, @carbikebus, enough about your "prediction" on which operator might win which tender, or which depots might remain and where new depots might be located. You have been writing this repeatedly for many times already. It's time to write something else.
For discussions about 969, it can be done at other threads like the bus interchange thread and bus loading thread.
Those about bus deployment can be discussed at other threads like the bus depot thread.
Please stop filling this thread with replies not related to GCM / BCM.
Thanks.
-
Originally posted by gekpohboy:
Once again,
This thread is only for GCM / BCM discussions.
Non-GCM / Non-BCM stuff, please discuss at other threads.
At the rate replies are posted, this thread will be filled up in less than one year since it was created in June last year!
The earlier thread lasted for around two years, and this, around one year only?
I'm okay if there has been strong discussions about BCM, but it seems that many a times, it's not related to the BCM contracts at Bulim, Loyang, Seletar or Ulu Pandan, or even the negotiated contracts (when was the last time we discussed about negotiated contracts?)
and, @carbikebus, enough about your "prediction" on which operator might win which tender, or which depots might remain and where which depots might be located. You have been writing this repeatedly for many times already. It's time to write something else.
For discussions about 969, it can be done at other threads like the bus interchange thread and bus loading thread.
Stop filling this thread with replies not related to GCM / BCM, please.
Thanks.
-
Originally posted by SMB3163D:
nice one.
-
and FYI 883 also crawling at 20-30 km/h, it is not just 969.
i think even 858 crawls at that as well.
-
To be honest, it does not matter to me if the quality of this forum is at stake. Soon, I will return to JB for good, and would probably not observe Singapore buses anymore. ��
-
Originally posted by gekpohboy:
Once again,
This thread is only for GCM / BCM discussions.
Non-GCM / Non-BCM stuff, please discuss at other threads.
At the rate replies are posted, this thread will be filled up in less than one year since it was created in June last year!
The earlier thread lasted for around two years, and this, around one year only?
I'm okay if there has been strong discussions about BCM, but it seems that many a times, it's not related to the BCM contracts at Bulim, Loyang, Seletar or Ulu Pandan, or even the negotiated contracts (when was the last time we discussed about negotiated contracts?)
and, @carbikebus, enough about your "prediction" on which operator might win which tender, or which depots might remain and where new depots might be located. You have been writing this repeatedly for many times already. It's time to write something else.
For discussions about 969, it can be done at other threads like the bus interchange thread and bus loading thread.
Those about bus deployment can be discussed at other threads like the bus depot thread.
Please stop filling this thread with replies not related to GCM / BCM.
Thanks.
Judgment reserved.
We dismiss this application as it has absolutely no merit.