|Introductions||Editing & Formatting||Links||Citing sources||sgWiki Buses||sgWiki Trains||Ban & Warning Points|
|sgWiki Buses is the most active section in sgWiki. It currently covers the history of individual bus service and the current fleet deployment. However, there are few important points that editors should obey.
BSEP / BCM Buses
Bus Service Enhancement Programme (BSEP) and Bus Contracting Model (BCM) Buses can be spare buses and must be listed as spare buses if they are spare buses. Any of these buses could ply on any services. Non-BSEP or Non-BCM Buses could ply on BSEP and BCM Buses Service or cover their bus slots.
When updating bus advertisements, editors must include the full name of the advertisement when updating. It could also include the position of the advertisement found on the buses. The first letter of every single word must be capitalised. E.g. "Pepsi Live For Now". Advertisement stated must be the same when there is more than one bus having the same advertisement.
If there is no advertisement on the bus,
Bus Fleet Size
At times, rescheduling will take place for a certain service, which means there might be an addition and/or reduction of duties. When reflecting such changes under deployment by service pages, ensure that the following tallies with one another:
If bus service fleet has more/less than total number of buses/duties, editors should reflect the following under the "Notes" section:
It is not compulsory to state the type of bus model and original fleet size.
Common misunderstanding: Bus redeployed from one service to another ≠ Both services have fleet addition and/or reduction
When updating withdrawal of service(s), editors must only update after the last bus concluded it's last operation trip of the service.
When updating new service(s), editors must only update after the first bus started it's first trip.
Ensure that bus models listed under deployment by service and spare buses (Applicable for SMRT & SBS Transit) pages are arranged according to the following format:
Do note that past deployments listed under Former Deployments page with
Italic font should not be added to buses and bus services transferred over from one operator to another, especially when a Bus Package transition takes place.
When editing newly-registered buses, editors must update the following pages:
The specification section of the deployment by bus model pages must also be updated. These buses must not be reflected as a "Spare" bus under the Former Deployments page, unless it is transferred to another depot.
When there is a change in bus deployment due to redeployment, editors must update the following pages:
Editors must not list the service it belongs to if it only ply on Weekends and Public Holidays (unless the service only operates during Weekends and Public Holidays) or a cameo bus. See above to differentiate between a cameo bus and a bus attached to a permanent service (perm bus).
Retired / Retiring Buses
When editing a retired or retiring buses (such as lay up and de-register), editors must remove the bus listing from deployment by bus model pages. However, editors are required to:
Do note that when updating de-registered buses, they are only to be updated (as "Scrapped", by default) after 2359 hours of the actual de-registration date of the bus (as reflected on One.Motoring). Buses that are scrapped even before they are de-registered should not be reflected as scrapped.
For buses that are awaiting de-registration prior to de-registration, only reflect the status as "Awaiting de-registration" under the non-revenue buses page when there's confirmation based on the physical evidence. Editors are also required to remove their deployment from the following pages:
Editors must spot the differences between a Cameo and a Perm Bus. Any bus that plys on any service is considered as a cameo bus of that particular service. However, if that particular bus meets any of the conditions of the following, it will then be considered as a perm bus:
At times, buses are scheduled to crossover to other services during some parts of the day. Such crossover duties are required to be listed down under deployment by service and bus model pages.
History of Bus Services
When editing the history of bus services, editors must take note to use past tense if the changes have taken effects or future tense if the changes have yet to have taken effect with a known effective date.
Please do not modify the page layout as and when you wish. If you feel that there are much more suitable layouts, it is best to consult other editors first before implementing throughout the deployment pages. This includes any tables in the page.
Photos of Buses
When uploading a photo of a particular bus for a bus model page, ensure that:
When linking a photo in the bus model page, ensure the photo is using 400 pixel wide rendition in a box in the right margin with the bus operator logo, bus registration number and bus service stated in the description. For example:
Photos of retired buses should not be linked, unless it is a retired demonstrator bus.
It is not compulsory to link all swapped out photos to bus gallery page.
Editors are strongly encouraged to upload buses bearing Land Transport Authority (LTA)'s Lush Green livery.
Articles related to any bus enthusiasts, or any articles which have no purpose or meaning, will be deleted. Creating a separate page like "SMB5888H", "SBS Transit Service 117", "Bulim Bus Depot" or "Pasir Ris Bus Interchange" is strongly discouraged, unless further meaningful content could be included.
Template Naming Conventions
sgWiki Buses uses a full exact Naming Convention for templates. Examples are SMRT Buses instead of SMRT, Tower Transit Singapore instead of TTS.