Difference between revisions of "User talk:Apex-LW'21"

From SgWiki
Jump to navigation Jump to search
 
(102 intermediate revisions by 13 users not shown)
Line 1: Line 1:
===Welcome to my talk page!===
===Welcome===
Please post on my user talk page (not my user page) if you want me to delete any outdated / unrelated articles or any unused images existed in sgWiki. Also, please provide the links to the uploaded images (if any) when requesting to delete the articles.<br>
Welcome to my talk page! Before you start using sgWiki, please read the [https://sgwiki.com/wiki/SgWiki:Guidebook sgWiki Guidebook] carefully and abide by all the rules in sgWiki.<br>


I will review the pages first before I will delete, but however, should any of the pages that requires cleanup or is sufficiently related, it will not be deleted, unless there is a reason to believe that the article is the above-mentioned. Pages (including its talk page of a current page) which are blanked out, unanswered or remained for a certain prolonged period will be deleted in the event of any routine house-keeping or cleanup in sgWiki.<br>
Please use this talk page for the following:<br>


If your account is mistakenly banned due to posting of false or unrelated information, etc, please ask the administrator who had originally banned you by writing on the user's talk page to appeal, unless if you are mistakenly banned by me. If an information is mistakenly marked as false statement, you had to clarify with the administrator and provide justification that the information is true and accurate. However, the decision will be made by the administrator and the decision of the appeal is final, after the investigation is complete.<br>
(1) Request deletion of outdated articles or any articles that you feel that it is not required to be in sgWiki.<br>
(2) Feedback or suggestion to improve existing pages in sgWiki.<br>
(3) Appeal of bans. Remember that ban appeals can only be done once, and if you are re-banned, there will be no further appeals. Please indicate clearly if you are banned by mistake. Note that appeal decision would be final once the final outcome is made.<br>
(4) Any questions regarding about editing in sgWiki or the sgWiki Guidebook.<br>
(5) Removal of Autoblock function. If necessary, please also specifically indicate the actual autoblock so that I can locate it and I will remove it.<br>


Do note that the successful appeal of the ban (only for those accounts banned by me) can only be done '''once'''. Once the ban appeal is successful, you are to comply with the [[SgWiki:Guidelines|sgWiki Guidelines]]. '''Appeals for repeated bans will not be considered.'''<br>
'''Do not''' use this talk page for:<br>


The appeal procedures will also apply to the warning points imposed to the account.<br>
(1) Captcha issues - please direct queries to the administrator 'Jason' talk page.<br>
(2) Request to retrieve or restore deleted revisions of an existing sgWiki article or restoring deleted articles including outdated ones - all requests will be rejected and persistent/disruptive requests will subject to a ban.<br>
(3) Spamming/advertising purposes. This will lead to an immediate ban.<br>
(4) Other actions that would be deemed disruptive, prohibited or inappropriate in sgWiki. Severe violations will result in permanent ban, depending on the situation.<br>


If any articles or uploaded photos are deleted by mistake, please use my talk page to appeal. Please note that any deleted articles/photos will be subjected to further review and decision. This appeal only applies to articles/photos that were previously deleted by me. If you wish to appeal on any articles/photos that were previously existed in sgWiki that were deleted by any other administrators, please write on the respective talk pages.<br>
Please write your message below this line. Thank you.<br>
 
Any accounts that are in severe violation of the rules as stated on the [[SgWiki:Guidebook|sgWiki Guidebook]] will not be unbanned. Please ensure that all edits and articles are complied with the sgWiki Guidelines.<br>
 
If your account is being affected by any Autoblock function caused by the user being blocked for spam advertising, etc, please use my talk page so that I can remove the Autoblock.<br>
 
For any Captcha issues, please refer to the administrator 'Jason' by writing on his talk page.<br>
 
For bus-related pages, if you find any mistakes in any pages (only those edited by me), please use my talk page to point out the mistakes and clarify with me. I will make the necessary corrections as soon as possible.<br>
 
----
 
==Summary of Issues==
===[Half-Resolved] Redundancy of Tower Transit Bus Deployment By Service===
Supernutorcrazy has suggested that the pages for Tower Transit Bus Deployment by Services was redundant as lack of quality information.
 
SBS3602U suggested that we will wait for a period of time to see if the deployment will be stabilised if not the whole pages and subpages to be deleted.
 
Request for a dateline before the pages to be deleted.
 
====Comments====
Tower Transit deployments for the day is somehow irregular. But I found that the Enviros running on Service 106 are much stablised and certain Wrights on 78, 79 and 143 as well.<br>
 
Also, I think we can change the title page as Bus Contracting Model Deployment by Service, since there would be Go Ahead coming next month.<br>
 
--[[User:Apex-LW&#39;21|Apex-LW&#39;21]] ([[User talk:Apex-LW&#39;21|talk]]) 23:46, 9 August 2016 (SGT)
 
===[Unsolved] Messy Headers and Format especially with a single model with multiple long headers===
Supernutorcrazy had suggested to merged it to a single table with a new columns that represent the operator which operates it and include a sortable table to reduce the need of long headers as the operators who operates the buses may not get it in running order.
 
However, SBS3602U highlight that if we will to get rid of it and follows [[Volvo B9TL (Wright Eclipse Gemini 2) (Batch 4) By Registration]], it will cause editor to scroll down pretty far and may causes mobile devices to crash while editing. The long section names etc was still messy.
 
In light of this, it is possible to semi-get rid of it, but limit the number of rows per table to about 200 and also retain certain element like not in running order. (Eg: SBS1Z – SBS23K; SBS3449X – SBS3482Z & SBS3487K – SBS3523P; SG5000E - SG5120S & SG5176G – SG5185E; SG5300P – SG5395R & SG5397K – SG5399E; SG5546Y – SG5555X)
 
====Comments====
This page is for experimental purposes. Since these buses would be transferred to the respective operators (such as Go Ahead next month) and some will remain on their respective incumbent operator, this page would be useful especially when those existing bus registration plates might be re-registered to the SG plate in the near future. So this page will be kept for now.<br>
 
--[[User:Apex-LW&#39;21|Apex-LW&#39;21]] ([[User talk:Apex-LW&#39;21|talk]]) 23:46, 9 August 2016 (SGT)
 
----
 
== Lay up buses in the existing lists ==
 
I have observed that lay up buses and buses that are missing but not laid up have been removed from the lists. While it doesn't matter for retiring buses, doing so for types of buses which are nowhere near retirement causes inconvenience for users who need to edit it when the buses are back from repairs/missing. It also causes inconvenience for users who have to check the lifespan expiry page for layup buses. I therefore suggest that layup buses be retained in the lists while only removing deregistered buses, especially when the pages do not have a link to the lifespan expiry page.
 
--Scania 16:08, 13 August 2016 (SGT)
 
==BCM mess==
Bus Deployments to be listed by packages w.e.f 1 Sept where BCM would complete transitioning and all 11 packages operated by SMRT and SBST would be under BCM (but still operated by the 2 operators).
 
'''Confirmed actions'''<br>
1. [[Bus Deployments by Package]] to replace:
*[[SMRT Bus Deployments from Depots]]
* [[SBS Transit Bus Deployments from Depots]]
*[[Bus Contracting Model (BCM) Bus Deployments from Depots]]
 
2. [[Bus Deployments]] to replace:
* [[SBS Transit Bus Deployments]]
* [[SMRT Bus Deployments]]
* [[Bus Contracting Model (BCM) Bus Deployments]]
 
'''Proposed actions:'''<br>
1. ''By SMB315C:''<br>
[[Spare Buses]] to replace:
* [[SMRT Spare Buses]]
* [[SBS Transit Spare Buses]]
* [[Bus Contracting Model (BCM) Spare Buses]] (would-be page for TTs and GA spare buses)
Listed by packages as well.
 
===Comments:===
I would go with having individual Spare Buses pages for each operator as each package is not allocated with a fixed batch of Spare Buses (that would be atrocious.)
 
Spare buses will only be shuffled among the operator itself.
 
--[[User:SBS3602U|SBS3602U]] ([[User talk:SBS3602U|talk]] | [[Special:Contributions/SBS3602U|contribs]]) 00:25, 22 August 2016 (SGT)
 
==Mercedes-Benz O530 Citaro Batch issues==
 
As for the Mercedes-Benz O530 Citaro Batch Identification Problem, I would suggest the SBS Transit Batch to change from Batch 1 --> Batch 2 etc. (Increment of Batch by 1), with SMRT Batch takes Batch 1 purely, as all buses under BCM will undergo "Refurbishment" with standardise interior fitting sooner or later, similar to the mock-up DD.
 
--Supernutorcrazy
 
For the Mercedes-Benz O530 Citaro mess, there is a need to clear the conflict as Bus Deployments by Service pages may look like this in the future:-
<blockquote>
 
<big>Service example (7 buses) {{WAB}}</big>
----
----
'''SMB136C SMB141L SMB188C'''<br>
3 Mercedes-Benz O530 Citaro ''(1 Demonstrator / 1 Batch 1 / 1 Batch 2)''
'''SG1691L SG1699R SBS6000L SBS6001J SBS6444P'''<br>
5 Mercedes-Benz O530 Citaro ''(2 Batch 1 / 1 Batch 2 / 2 Batch 3)''
</blockquote>
And this of course doesn't make sense. There are 2 ways I could think of:-
* Rename [[Mercedes-Benz O530 Citaro]] to [[Mercedes-Benz O530 Citaro (SMB-plated)]]
: I wouldn't recommend this as in the worst case scenario, these buses may be re-registered to the SG-prefix plate.
* SMRT Citaros to use [[Mercedes-Benz O530 Citaro (Batch 1 & 2)]]
* SBST spec Citaros to use [[Mercedes-Benz O530 Citaro (Batch 3)]] (former B1), [[Mercedes-Benz O530 Citaro (Batch 4)]] (former B2) and [[Mercedes-Benz O530 Citaro (Batch 5)]] (former B3)
I would recommend this more, though it may take some time for the community to adjust to which pages they were in the past. To solve this problem, we could have notices above the pages informing visitors.
Opinions are welcome.
Regards.
--[[User:SBS3602U|SBS3602U]] ([[User talk:SBS3602U|talk]]) 15:00, 14 August 2016 (SGT)
'''Citaro suggestion'''<br>
It could be as such:<br>
Citaro (SMRT spec)<br>
Citaro (SBS Transit Spec B1)<br>
Citaro (SBS Transit Spec B1)<br>
Citaro (SBS Transit Spec B3)<br>
--Scania 17:22, 15 August 2016 (SGT)
With regards to the Citaros, I think that the title naming should remain as such, like Batch 1, Batch 2, Batch 3 etc.<br>
For the case of the classification of an example of a Citaro with SBST specification Batch 1, this can be applied to the respective "Specifications" table of the bus deployment list. This can distinguish the specifications on the table itself rather than placing it as a title of a bus deployment page list.<br>
--[[User:Apex-LW&#39;21|Apex-LW&#39;21]] ([[User talk:Apex-LW&#39;21|talk]]) 21:09, 15 August 2016 (SGT)
:However, the problem with the conflicting Batch names still occur and bus deployments by service pages may face problems should a service have both SMRT-spec and SBS-spec Citaros like in the example above (will just put it here for convenience)
<blockquote>
<big>Service example (8 buses) {{WAB}}</big>
----
'''SMB136C SMB141L SMB188C'''<br>
3 Mercedes-Benz O530 Citaro ''(1 Demonstrator / 1 Batch 1 / 1 Batch 2)''
'''SG1691L SG1699R SBS6000L SBS6001J SBS6444P'''<br>
5 Mercedes-Benz O530 Citaro ''(2 Batch 1 / 1 Batch 2 / 2 Batch 3)''
</blockquote>
Therefore, I feel that the page names still need to change.
--[[User:SBS3602U|SBS3602U]] ([[User talk:SBS3602U|talk]] | [[Special:Contributions/SBS3602U|contribs]]) 22:48, 15 August 2016 (SGT)
For the case of that scenario as highlighted, may I suggest that the bus deployment pages of the respective Citaros be distinguished in terms of the specifications that every SBST/SMRT Citaros has it.<br>
Which means for instance "Batch 1 (SBST spec)" for Citaros with Batch 1 SBS Transit specifications can be used as such.<br>
--[[User:Apex-LW&#39;21|Apex-LW&#39;21]] ([[User talk:Apex-LW&#39;21|talk]]) 20:59, 16 August 2016 (SGT)
'''Re: Reply No. 4 [http://sgwiki.com/index.php?title=User_talk:SBS3602U&oldid=353559#Reply_No._4]'''
I feel that it may look weird with SBS-spec / SMRT-spec included when it is listed in the Bus Deployments by Service pages:
<blockquote>
<big>Service example (8 buses) {{WAB}}</big>
----
'''SMB136C SMB141L SMB188C'''<br>
3 Mercedes-Benz O530 Citaro (SMRT-Spec) ''(1 Demonstrator / 1 Batch 1 / 1 Batch 2)''
'''SG1691L SG1699R SBS6000L SBS6001J SBS6444P'''<br>
5 Mercedes-Benz O530 Citaro (SBST-Spec) ''(2 Batch 1 / 1 Batch 2 / 2 Batch 3)''
</blockquote>
Both solutions have their bad points. Hence, this is more of a preference issue.
* Have SMRT-Spec/SBST-Spec in the page titles
** May look weird as a page title itself and when listed in deployments by service pages as it is a little too long.
* SMRT spec Citaros to use (Batch 1 & 2), SBST spec Citaros to use (Batch 3) (Batch 4) (Batch 5)
** May cause confusion with the visitors and editors.
Of course, I'm not one to decide how the wiki should turn out (the way I like it) and just stating my point of view on the suggestions. As this issue is more towards preferences, I'd like it if we could get more opinions from the community or the editors here :)
Regards.<br>
--[[User:SBS3602U|SBS3602U]] ([[User talk:SBS3602U|talk]] | [[Special:Contributions/SBS3602U|contribs]]) 16:45, 18 August 2016 (SGT)
== Question of reference about overall Batches 2 & 3 of all Citaros. ==
Greetings.
I have taken note of the ongoing discussions with some of the more actively contributing users in here, with regards to the labeling of Citaros. While I currently do not have any ideas for that, but I would like to pose a question of reference to you all.
While SMB149R to SMB188C was classified as "SMRT - Batch 2" which also means that it is the overall second batch of the Citaros, and that SBS6000L to SBS6285G are classified as "Batch 3" (overall in the suggestion of the other users), in actual, SBS6000L was registered much earlier in April 2011 as compared to SMB149R which was registered in October 2011. In my view, there is a confusion as to whether there was a specific rule; in which the first bus of a particular batch (in this case the SBST's Batch 1) had to be registered earlier, to constitute an overall earlier batch than another batch (the SMRT's Batch 2) which first bus was registered later? If there is such a rule, shouldn't SBS6000L to SBS6285G be labelled as overall Batch 2 and SMB149R to SMB188C be labelled as overall Batch 3?
--[[User:ASA1234|ASA1234]] ([[User talk:ASA1234|talk]]) 20:53, 21 August 2016 (SGT)
==Reply==
In terms of specifications and the date of the first roll-out, I would say that for SBS6000L to SBS6285G & SBS6300X to SBS6341C, it would be labelled as Batch 2 and SMB149R to SMB188C would be labelled as Batch 3 in overall and so on, although the Batch 3 Citaros (SMRT Batch 2) were entirely rolled out, while the Batch 2 Citaros (SBST Batch 1) were ongoing rollout.<br>
--[[User:Apex-LW&#39;21|Apex-LW&#39;21]] ([[User talk:Apex-LW&#39;21|talk]]) 05:28, 23 August 2016 (SGT)
== Request: Coordinating history of buses page(s) ==
Hi, may I suggest that the various separate pages on the [[History of Bus Services|history of buses]] be merged, such that they are <u>no longer discriminated by bus operator</u>? Unlike the bus deployment page where the operator must be distinctively differentiated, the bus history page does not need its articles to be separated as such. This is also onsidering the onset of GCM, which makes continuously switching between history pages irritating (e.g. service 82), and makes finding a specific service difficult from the main page (when there are so many operators).
One way to still show the bus operator of that particular service would be to insert a long thin coloured column to the left of each service's table, for example deep purple for SBST, red for SMRT, green for TTS and pink for GAS, such that every time the service changes hands, it would be clearly reflected. The header of the service can still bear the colour matching its current operator's. This removes the need to have separate pages, so a common and tabulated article page for "2-20", "161-180", etc would suffice.
[[User:Dragomir7|Dragomir7]] ([[User talk:Dragomir7|talk]]) 11:39, 22 August 2016 (SGT)
== Wrights batch 4 for GA tables ==
Hi,
Since the buses are now owned by LTA, and are transferred to GA now, the type of purchase does not matter now. Indeed, it is already the case for the SBS SG plate buses for the Wrights and Citaro pages, where the BSEP range is consolidated together with the non BSEP range (BSEP 51xx, 55xx, Non BSEP, 53xx, 54xx), for these two pages, due to the large amount of tables, it is good if we are consistent in following the SBS style of tables (SBS plate one table, SG plate one table), what I suggest is that, if the numbers are small enough after the handover, we could combine the SBS regos into one table.
Moving forward, because of the GCM, the type of purchase doesn't really matter anymore if the buses are owned by LTA, although for older buses (eg Batch 1-3 Wrights) owned by SBS/SMRT, we should keep those models' pages as it is.
This message was my own comment copied from a conversation with another user.
--Scania 17:12, 22 August 2016 (SGT)

Latest revision as of 08:19, 9 March 2020

Welcome[edit]

Welcome to my talk page! Before you start using sgWiki, please read the sgWiki Guidebook carefully and abide by all the rules in sgWiki.

Please use this talk page for the following:

(1) Request deletion of outdated articles or any articles that you feel that it is not required to be in sgWiki.
(2) Feedback or suggestion to improve existing pages in sgWiki.
(3) Appeal of bans. Remember that ban appeals can only be done once, and if you are re-banned, there will be no further appeals. Please indicate clearly if you are banned by mistake. Note that appeal decision would be final once the final outcome is made.
(4) Any questions regarding about editing in sgWiki or the sgWiki Guidebook.
(5) Removal of Autoblock function. If necessary, please also specifically indicate the actual autoblock so that I can locate it and I will remove it.

Do not use this talk page for:

(1) Captcha issues - please direct queries to the administrator 'Jason' talk page.
(2) Request to retrieve or restore deleted revisions of an existing sgWiki article or restoring deleted articles including outdated ones - all requests will be rejected and persistent/disruptive requests will subject to a ban.
(3) Spamming/advertising purposes. This will lead to an immediate ban.
(4) Other actions that would be deemed disruptive, prohibited or inappropriate in sgWiki. Severe violations will result in permanent ban, depending on the situation.

Please write your message below this line. Thank you.

Retrieved from "https://sgwiki.com/index.php?title=User_talk:Apex-LW%2721&oldid=473396"