Difference between revisions of "User talk:Themystery"

From SgWiki
Jump to navigation Jump to search
m
 
(24 intermediate revisions by 8 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.


== Status of SG5999Z==
== RE: SBS7557R Recent Edit ==
Hi,


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


It appears SG5999Z has been MIA for quite a long time (since early last month) and it has not been seen even in BNDEP. Do you have any idea what happened to the bus? More importantly, is SG5999Z still in SBST's database? (Rumour is that the bus has been returned to LTA)
Regards


Thank you.
== Reply: User: Singapore Buses ==
Hi.


Regards,<br>
Thanks for highlighting this.
Peace & Harmony


== Re : Notes Section ==
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.


Hi Themystery,
== 268B. ==


Thank you for pointing out the error that I have made. Unfortunately I was sleepy and had forgotten to check through the notes that I have made.
Hi


I have made the necessary steps to ensure this does not happen again and have made the changes accordingly.
it is reflected on bus app for the 1840 and 1925 trip.
but NO bus appear at bus stop......that the issue.


Thank you.  
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....


Regards,  
==Re: Service Page Descriptor==
Hi Themystery,


SimonLim88
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.


===Update===
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.
I have made a compilation of all 851e buses and their secondary deployments, as well as a fleet list of 851e for different days of the week on my user page. Have a look at it and let me know if it's correct or if there are any mistakes.


Regards,<br>Peace & Harmony
Regards, Supernutorcrazy


==Reply==
==Reply==
Hi,
Hi,


Please proceed to removed those short service listing at the respective station pages. I believed some user added it in based on full day operations which I may had overlook.
Refer to this [https://sgwiki.com/index.php?title=User_talk%3ATheDonaldTrumpSupport&type=revision&diff=651270&oldid=651226].


Thanks and regards
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.


== RE: Feeder 265 Downroutes from AMK Int ==
Regards


Hi Themystery,<br>
==Reply==
Hi,


I have added the 3AM-3PM / 1E / 2S duty for 262 on Weekdays, but from my observations, both 6594P and 1086J seem to be running together with 1106K 1176H 1232D on weekends, not sure if there are only 4 buses for weekends. As for weekdays, I have seen 6594P being driven by regular AM-PM bus captains often, not sure if those are cameos or 6594P might even be doing a T shift.
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.


As for 265, I have noticed duty 1A starting from a different starting point on weekdays. Duty 1A (SG1080A) used to depart Ang Mo Kio Depot at 0530 hours as the first bus. However, duty 2A (SG1096E) now does this first bus duty on weekdays. Instead, I have been noticing 1080A running between 1158K and 1160C. 1158K (duty 15S) is the first bus to depart AMK Int on weekdays, at 0530, followed by 1160C (duty 16S) which departs at 0541. No 265 buses bound for Ave 10 depart between 0530 and 0541. However, when 1158K and 1160C return to AMK Int after looping at Ave 10, 1080A arrives between them and usually is already carrying passengers, which probably means it did a downroute from somewhere in that AMK Int - AMK Ave 10 - AMK Int sector.
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.


May I know if you are able to identify where Duty 1A does the downroute from on weekdays? It would be a great help if you could!!
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).


Thank you very much!!
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)


Best regards,
Regards
Jonathanchu


== Reply: Service 147 duties ==
==BRBP==
Hi Themystery,
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.


Sorry for the late reply.
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.


Nope for now.
==Opinion==
 
Hi,
== RE: 262 Duties ==
 
Hi Thenystery,
 
I am sorry for reverting your edit, but based on my observation on two days this week, 1086J was doing an AP slot 262-se-404, duty 4A/8P. Initially, it is stated that special weekday duties are 3AM-3PM / 1E / 2S, not sure if the days you observed were special weekday duties.
 
I will continue to observe but for now I will put weekdays as TBC. Sorry for any inconvenience caused!
 
Regards,
 
Jonathanchu
 
== Re: Extra DD in 161 duties. ==


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


Thanks for your prompt reply. As noted in the recent changes of service 161 duties, SBS3086J has been observed to be appearing at certain timings, which might have indicated a possible perm change, prior to SG5513S which was missing for close to 2 weeks, which might have been taken out of HGDEP since it was performing on 154 which is under SLBP. Also, random DDs have been starting to make cameo appearances on 161 (SG5447A 3pm @ IMH, SG5555X 6.05pm @ Woodlands Temp Int etc) Could this be an introduction of random deployments (like SMRT AMDEP)? This has went on for a few days notably from 1 Nov - present where random buses from HGDEP would perform on several services on a day.
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.


Thanks.
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.


- Last Promise
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:


== SG3069X deployment ==
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)


Hello Themystery,
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:


I had read your edit on the BYD K9 page and understand that SG3069X is, as of now, a perm of 807(A). However I had observed today at 11:15am that SG3069X is on 135. Because I don't live near where 807 or 135 passes. I don't know the current deployment of SG3069X, and I don't believe it is a cameo due to how electric buses were previously deployed. Therefore, should I list it as a crossover to 135 until the perm status of SG3069X has been confirmed? (I hadn't observed SG3050Z's deployment yet so I will leave it as it is for now)
Registration No/Livery | Operator/Current Deployment | Advertisement | Former Deployment


Thanks and regards,
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.


AirFan19
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)


== Updating duties ==
Please let me know your thoughts on these proposals. Thank you for your time and feedback.
 
Hi Themystery,
 
How to see the number of duties of bus services.
 
From,
Gohqianyan832
 
== Reply: Proposal to Add Filters ==
Hi.


Have read your proposal to Supernutorcrazy and added in the sortable feature on the deployment section for [[Scania K230UB (Euro IV) (Batch 2)|Scania K230UB (Euro IV) (Batch 2)]]. May I know whether this is what you are trying to request for?
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