Difference between revisions of "User talk:Themystery"

From SgWiki
Jump to navigation Jump to search
m
 
(51 intermediate revisions by 13 users not shown)
Line 1: Line 1:
Hi! If I have made any mistakes in any edit, please pardon me for my errors. I am open to any clarification for any matter if required.
Hi! If I have made any mistakes in any edit, please pardon me for my errors. I am open to any clarification for any matter if required.


==Service 165===
== RE: SBS7557R Recent Edit ==
My apologies. There has been a timetable change for 165, so what was previously a HG slot (SBS7632G) is now a BB slot (SBS7679Y). It is also worth noting that SBS7679Y (and SG5446C suspected) are now on AP shift.
Hi,


== Updep 198 deployments ==
Maybe we can kiv for 1/2 days? He/she may have a simplified/better way to organized it later on?


So far I spotted all updep 198 fleets.. all 6 buses r seen.. 7450 were out
Regards


Based on my own observation, all 6 buses are seen.. only 7450 kena kicked out under new ett..
== Reply: User: Singapore Buses ==
Hi.
 
Thanks for highlighting this.
 
I believe it would be best to just leave your observations there for now. I will help keep a lookout on this user if he reverts once again.
 
== 268B. ==
 
Hi
 
it is reflected on bus app for the 1840 and 1925 trip.
but NO bus appear at bus stop......that the issue.
 
i was at YCK stadium bus two times at 1920.
bus app showing 5 mins 4 mins and then 2 mins..... and stuck at 2 mins till 1930, then it was indicated as NA... but the next stop still show 2 mins.
no 268B bus appear at all.
then after short while, all the arrival timing show NA....
 
==Re: Service Page Descriptor==
Hi Themystery,
 
Thank you for your suggestion regarding the bus service page descriptor. I agree that we should aim to create a unique descriptor rather than simply copying and pasting.
 
I would sincerely appreciate it if you could assist in crafting the unique descriptor or modifying it as needed. As sgWiki is a community-based platform, we highly value your contributions and consider them an invaluable asset.


And according to cfms.. SLBP side is only from sw307 onwards,, so last upd duty on wkdays is sw306.. hope u get the answer
Regards, Supernutorcrazy


But for e n s parts.. i will check wit my bcf again
==Reply==
Hi,


Thks
Refer to this [https://sgwiki.com/index.php?title=User_talk%3ATheDonaldTrumpSupport&type=revision&diff=651270&oldid=651226].


== Rwply updep 198 deployments part 2 ==
I am trying to be neutral here. In fact, I did point it out which obviously the user didn't heed and choose to do so.


Hmm.. so far I do see all 6 buses in based on my own observation for past 2 wks. And all doing their respective perm slots..
Regards


Orginally was 7 den now 6 under new ett and 7450 was taken out.
==Reply==
Hi,


Old ett was 6s and 1e
There is currently no provision, or else there are lots of editors who will going to flamed me at discord/youtube/facebook for it, with me already having a bad reputation for enforcing the rule instead of following their nonsense.


And now new ett is 4s and 2e???
Regarding your concerns, I believe that all editors should come into consensus regarding the labeling of such depot. I believe there is confusion now is because of the mixture of tendered package and negotiated package, and either party wished to standardised in one form or another.
Yes i did take note of ur reply.. but i will double check wit my bcf again.. thks


== Reply: 851e SD ==
This was also an issue when the BYD BC12A04 was first launched. The senior editors would prefer to use AMDEP 86 because it was controlled and park at AMDEP, but the junior editors would prefer to use SWDEP 86 due to "leasing" and part of BCM. So there is a conflict, where 86 is in tendered package - meaning it can operates from any depot based on SBS Transit liking (but obviously from an economic point of view, SBS Transit would not put 86 to furthest depot such as BBDEP or BNDEP).


have check and there is indeed 2 SD on 851e. but 1 SD operate from 9am to 9pm
In my opinion, I would prefer to use the original method, to list the secondary depot (instead of primary) for services that overnight parking at secondary depot. This way, no need to put things like "All buses practices overnight parking at secondary depot", because at one glance - it is from the secondary depot (and from the respective bus package page, can also infer from which is the main depot)
the other SD only operate 1 trip on weekday (6pm departure from Yishun). this SD is not doing the return trip at all and does not appear on other timing.
sometime this timing is done by DD.  
are you able to check/confirm whether this is crossover from some other Yishun service instead? (i would believe that it is a SD from 851)


rgds
Regards
lemon1974


== Reply: Suggestion on Notes Section ==
==BRBP==
Hi.
I saw what u wrote at [[User Talk: Supernutorcrazy|Supernutorcrazy's Talk Page]] and I just want to say that the reason why we use the primary depot is because of {{SBST}}'s slot system.
 
On the Driver's Display Unit (DDU) for {{SBST}} buses on the top right corner there will be a block number, e.g. 88-hg-321. As you can see in the example the slot uses the abbreviation for Hougang Depot, back then there was also a slot for Braddell Bus Park so that's why some buses have BRBP as their deployments. Due to the closure if Ang Mo Kio Depot, Braddell Bus Park was given to Hougang Depot to continue their operations but as an overnight parking facility due to lack of proper equipment to function as a depot and it was also used to house ComfortDelgro's Taxis at some part of the Parking Facility. To prevent public outrage and for [[User: Supernutorcrazy|Supernutorcrazy]] to not get flamed by the community, in the former deployments we write BRBP instead of AMDEP, mostly due to the Bus Contacting Model and {{SBST}}'s way of organising their fleet, however in the case of the CGBP deployments, these were made before the Bus Contracting Model and the Driver's Display Unit existed, so editors use their secondary depot to prevent confusion. Now, a lot of buses practice overnight parking at bus parks or depots, due to space concerns or organisation, such as the Bukit Panjang Feeders which park at Woodlands Bus Park, Some Boon Lay services under {{SBST}} are parked at Bulim Bus Depot. Like the services mentioned they are not controlled by the depot they park at but their original depot they came as part of their Bus Contracting Model Package.
 
==Opinion==
Hi,
 
I would like to seek your opinion on the following proposed changes:


Thanks for suggesting this.  
1. Launch of sgWiki Bus Spotting Page
A new page will be created daily and automatically deleted a month later. For example, "Bus Spotting/1 February 2025" would be removed on 1 March 2025. This page is intended to allow editors to document bus registration numbers without the typical edit limitations, enabling infinite edits.


Sure, you may go ahead and reorganise the notes. They look more organised than the current format.
The primary objective is to encourage collaboration among editors and to improve the accuracy of bus deployment data in relation to their permanent services. Many users have noted that the deployment page contains inaccurate and outdated information. By using these pages, we aim to track bus operations more effectively and allocate the correct permanent services, without requiring editors to board the buses to verify duty schedules.


== SG6087Z (HGDEP 161) ==
2. Use of Subpages for Bus Model Deployment
I have received considerable feedback, mostly criticism, regarding the separation and consolidation of bus advertisements across models. Most complaints focus on advertisement changes rather than deployment accuracy, which contributes to the aforementioned inaccuracies. As such, I propose reorganising the Bus Model deployment using subpages as follows:


Good evening Themystery,
Example: Volvo B9TL (WEG Batch 2) will be divided into four subpages:
# Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 1 – (Low Entry, SBS7700T – SBS7729L)
# Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 2 – (Low Floor, SBS3000G – SBS3099Y)
# Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 3 – (Low Floor, SBS3100B – SBS3199S)
# Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 4 – (Low Floor, SBS3200X – SBS3238M & SBS3269Z)


Are you able to check if SG6087Z is still on 163? I still do see SBS3683K on 161 despite being swapped to Service 163.
A navigation bar will be added at the top and bottom of each page, linking the respective subpages. Each page will feature a single table listing up to 100 buses, organised in the following format:
Here’s the edit which I initially thought was vandalism because I have never seen SG6087Z on 161 :  


https://sgwiki.com/index.php?title=Services_161_-_179&diff=480885&oldid=480761
Registration No/Livery | Operator/Current Deployment | Advertisement | Former Deployment


And I also noticed you removed the clause “Any Double decker buses” on Services 21 & 165 respectively. Is there a reason to this? And does SBST follow a flexible deployment like SMRT AMDEP?
This approach seeks to balance different perspectives, and to be more mobile friendly, as I am uncertain why some users are strongly opposed to these changes.


Thanks and hope to hear from you soon.
Alternative Table Layouts:
# Registration No/Livery | Operator/Current Deployment | Former Deployment (Maintain status quo)
# Batch | Registration No/Livery | Operator/Current Deployment | Former Deployment (Merging of Batches, numerical order, maintain status quo)
# Batch | Registration No/Livery | Operator/Current Deployment | Advertisement | Former Deployment (Merging of Batches, numerical order)


Regards,
Please let me know your thoughts on these proposals. Thank you for your time and feedback.


SimonLim88
Regards, Supernutorcrazy

Latest revision as of 16:02, 18 January 2025

Hi! If I have made any mistakes in any edit, please pardon me for my errors. I am open to any clarification for any matter if required.

RE: SBS7557R Recent Edit[edit]

Hi,

Maybe we can kiv for 1/2 days? He/she may have a simplified/better way to organized it later on?

Regards

Reply: User: Singapore Buses[edit]

Hi.

Thanks for highlighting this.

I believe it would be best to just leave your observations there for now. I will help keep a lookout on this user if he reverts once again.

268B.[edit]

Hi

it is reflected on bus app for the 1840 and 1925 trip. but NO bus appear at bus stop......that the issue.

i was at YCK stadium bus two times at 1920. bus app showing 5 mins 4 mins and then 2 mins..... and stuck at 2 mins till 1930, then it was indicated as NA... but the next stop still show 2 mins. no 268B bus appear at all. then after short while, all the arrival timing show NA....

Re: Service Page Descriptor[edit]

Hi Themystery,

Thank you for your suggestion regarding the bus service page descriptor. I agree that we should aim to create a unique descriptor rather than simply copying and pasting.

I would sincerely appreciate it if you could assist in crafting the unique descriptor or modifying it as needed. As sgWiki is a community-based platform, we highly value your contributions and consider them an invaluable asset.

Regards, Supernutorcrazy

Reply[edit]

Hi,

Refer to this [1].

I am trying to be neutral here. In fact, I did point it out which obviously the user didn't heed and choose to do so.

Regards

Reply[edit]

Hi,

There is currently no provision, or else there are lots of editors who will going to flamed me at discord/youtube/facebook for it, with me already having a bad reputation for enforcing the rule instead of following their nonsense.

Regarding your concerns, I believe that all editors should come into consensus regarding the labeling of such depot. I believe there is confusion now is because of the mixture of tendered package and negotiated package, and either party wished to standardised in one form or another.

This was also an issue when the BYD BC12A04 was first launched. The senior editors would prefer to use AMDEP 86 because it was controlled and park at AMDEP, but the junior editors would prefer to use SWDEP 86 due to "leasing" and part of BCM. So there is a conflict, where 86 is in tendered package - meaning it can operates from any depot based on SBS Transit liking (but obviously from an economic point of view, SBS Transit would not put 86 to furthest depot such as BBDEP or BNDEP).

In my opinion, I would prefer to use the original method, to list the secondary depot (instead of primary) for services that overnight parking at secondary depot. This way, no need to put things like "All buses practices overnight parking at secondary depot", because at one glance - it is from the secondary depot (and from the respective bus package page, can also infer from which is the main depot)

Regards

BRBP[edit]

I saw what u wrote at Supernutorcrazy's Talk Page and I just want to say that the reason why we use the primary depot is because of SBS Transit's slot system.

On the Driver's Display Unit (DDU) for SBS Transit buses on the top right corner there will be a block number, e.g. 88-hg-321. As you can see in the example the slot uses the abbreviation for Hougang Depot, back then there was also a slot for Braddell Bus Park so that's why some buses have BRBP as their deployments. Due to the closure if Ang Mo Kio Depot, Braddell Bus Park was given to Hougang Depot to continue their operations but as an overnight parking facility due to lack of proper equipment to function as a depot and it was also used to house ComfortDelgro's Taxis at some part of the Parking Facility. To prevent public outrage and for Supernutorcrazy to not get flamed by the community, in the former deployments we write BRBP instead of AMDEP, mostly due to the Bus Contacting Model and SBS Transit's way of organising their fleet, however in the case of the CGBP deployments, these were made before the Bus Contracting Model and the Driver's Display Unit existed, so editors use their secondary depot to prevent confusion. Now, a lot of buses practice overnight parking at bus parks or depots, due to space concerns or organisation, such as the Bukit Panjang Feeders which park at Woodlands Bus Park, Some Boon Lay services under SBS Transit are parked at Bulim Bus Depot. Like the services mentioned they are not controlled by the depot they park at but their original depot they came as part of their Bus Contracting Model Package.

Opinion[edit]

Hi,

I would like to seek your opinion on the following proposed changes:

1. Launch of sgWiki Bus Spotting Page A new page will be created daily and automatically deleted a month later. For example, "Bus Spotting/1 February 2025" would be removed on 1 March 2025. This page is intended to allow editors to document bus registration numbers without the typical edit limitations, enabling infinite edits.

The primary objective is to encourage collaboration among editors and to improve the accuracy of bus deployment data in relation to their permanent services. Many users have noted that the deployment page contains inaccurate and outdated information. By using these pages, we aim to track bus operations more effectively and allocate the correct permanent services, without requiring editors to board the buses to verify duty schedules.

2. Use of Subpages for Bus Model Deployment I have received considerable feedback, mostly criticism, regarding the separation and consolidation of bus advertisements across models. Most complaints focus on advertisement changes rather than deployment accuracy, which contributes to the aforementioned inaccuracies. As such, I propose reorganising the Bus Model deployment using subpages as follows:

Example: Volvo B9TL (WEG Batch 2) will be divided into four subpages:

  1. Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 1 – (Low Entry, SBS7700T – SBS7729L)
  2. Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 2 – (Low Floor, SBS3000G – SBS3099Y)
  3. Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 3 – (Low Floor, SBS3100B – SBS3199S)
  4. Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 4 – (Low Floor, SBS3200X – SBS3238M & SBS3269Z)

A navigation bar will be added at the top and bottom of each page, linking the respective subpages. Each page will feature a single table listing up to 100 buses, organised in the following format:

Registration No/Livery | Operator/Current Deployment | Advertisement | Former Deployment

This approach seeks to balance different perspectives, and to be more mobile friendly, as I am uncertain why some users are strongly opposed to these changes.

Alternative Table Layouts:

  1. Registration No/Livery | Operator/Current Deployment | Former Deployment (Maintain status quo)
  2. Batch | Registration No/Livery | Operator/Current Deployment | Former Deployment (Merging of Batches, numerical order, maintain status quo)
  3. Batch | Registration No/Livery | Operator/Current Deployment | Advertisement | Former Deployment (Merging of Batches, numerical order)

Please let me know your thoughts on these proposals. Thank you for your time and feedback.

Regards, Supernutorcrazy