User talk:Themystery

From SgWiki
Revision as of 16:19, 11 January 2025 by Sgbusntrain (talk | contribs)
Jump to navigation Jump to search

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

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

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: Loss of Bus Advertisement Information

Hi,

Regarding your point:

#1: Lost of bus advertisement tracking

The bus advertisement tracking are now consoldilated into Advertisements on Buses. This is because there are 2 distinct group of editors. 1 is just focus on bus advertisement, and 2 is focus on bus deployment. However, majority of the editors belong to group 1, which defeat the original intention of sgWiki Buses - Updates of deployment.

You will notice that bus swap/deployment change/duty change are commonly edited in the past, and with the recent enthusiant, it was focus mainly on advertisement etc.

#2 Large table cell spanning across multiple row

I will take note of it and implement something to improve it, in term of user point of view. Thank you for your feedback.

#3 Deployment by Service & Deployment by Model

I notice that most editor just edit deployment by model and not deployment by service. Even though information should by synchronised, but editors dont edit it and it look independent. Editors are still able to edit it into the new Deployment by Services (i.e. the new Services page still holds those information).

#4 Information on the Changes

The new change was originally to decouple Deployment by Service with Deployment by Model, as editors didn't edit the deployment by Service. However, it was taken into consideration of legacy and we still proceed not to decouple both, while adding more information for general public.

The new Deployment by Service also help to bridge and link the MRT/LRT section with the Bus section, which in the past is stand as two seperate information page as more enthusiastic now become multi-model.

The original intention is to completely remove Advertisements on buses, but for legacy sake, and the request, we had decided to consodilate it into a single page which make it easier to filter, track the respective advertisment, like an excel/Google Sheet table.

An working proposal to streamline Bus history had been brought up and was proposed, with a working draft. But nothing had been set in stone on it moving forward.

The new change will also affect the MRT/LRT section. This include deployment schedule/TRN for the respective line, but nothing had been set in stone due to a lack of information.

In conclusion on the list of changes:

  1. Decouple Bus Deployment with Bus Advertisement as majority of editors only edit Advertidement.
  2. Merging of Bus History and Bus Deployment by Service
    1. Include first/last bus, duty information, frequency and route stop for general public.
    2. Link it with rail section
  3. Consodilation and reorganised of Bus History Page.

To put it simply, the new organisation will attempt to make it more informative for the general public. I.e. which public will focus on advertisment on bus? Duty and bus model may be a more possible scenario - I.e at this timing (duty), I will need to take this bus to work/school (model).

So I hope that it explains the reasons for changes - to fit the purpose of wiki.

I hoped I had cover everything regarding your queries.

Thank you.

Re: sgWiki Buses Huge Table

Hi,

I had remove the column for Livery, and combined it with Registration number, with the background depicting the livery, is this better, as seen in Mercedes-Benz O530 Citaro (Batch 1) and MAN NG363F

Regards

Thank you.

Reply

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

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

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.