Difference between revisions of "User talk:SBS9631X"
Apex-LW'21 (talk | contribs) |
|||
Line 2: | Line 2: | ||
Hi, | Hi, | ||
Yes. According to the previous revision rule, all users should state his/her legitimate email prior to edit or face banned. When banned, the user are allowed to appeal with his/her legitimate email if the user has not edit/touch on any other pages. | |||
{{AdminMsg|Supernutorcrazy|28 Feb 2018|13:32}} | |||
{{AdminMsg|Supernutorcrazy|28 Feb 2018| | |||
==Service 7 fleet due to recent introduction of Service 7A & 7B== | ==Service 7 fleet due to recent introduction of Service 7A & 7B== |
Revision as of 13:32, 28 February 2018
Blockage Clarification
Hi,
Yes. According to the previous revision rule, all users should state his/her legitimate email prior to edit or face banned. When banned, the user are allowed to appeal with his/her legitimate email if the user has not edit/touch on any other pages.
Thanks & Regards
--Supernutorcrazy (talk, administrator) 28 Feb 2018 13:32 SGT
Service 7 fleet due to recent introduction of Service 7A & 7B
Reply
Hi SBS9631X,
Thanks for the reply pertaining to Service 7A and 7B.
But then, while the identification of the fleet of Service 7A and 7B is not a rush, the crossover details of Service 7A and 7B to Service 7, can be reflected in the bus deployments for Service 7 first, and a similar note on the crossover should also be reflected on the Service 7A and 7B on the SBS Transit Shortworking Trip Services page. Also, I would say that the fleet size would be about 7 to 8 buses (or maybe 9?), although the confirmed fleet size required KIV, given the frequency of Service 7A and 7B.
As for buses doing 7A and 7B perm status, I am proposing to reflect the perm status as BNDEP 7A/7* (for 7A) and BNDEP 7B/7* (for 7B), rather than the current input as BNDEP 7/7A* (for 7A) and BNDEP 7/7B* (for 7B).
If you have further clarifications, or comments you may need to add on, feel free to post on my talk page.
--Apex-LW'21 (talk) 10:52, 28 February 2018 (+08)