|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 services and the current fleet deployments. However, there are a few important points that users should obey.
When updating new bus advertisements, users must state the main details of the advertisement.
The first letter of every single word must be capitalised. E.g. "Pepsi Live For Now".
Advertisement details must be standardised across the bus model pages when there is more than one bus having the same advertisement.
If the advertisement has been removed from the bus (also known as 'Adless'),
The following is a compilation of advertisement legends:
Bus Fleet Size
Rescheduling of bus services will take place over a period of time, which means there might be a/an addition/reduction of bus fleet/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, users should reflect the following under the "Notes" section:
It is not compulsory to state the type of bus model and original fleet size.
Bus redeployed from one service to another ≠ Both services have fleet addition/reduction
Several bus services practice CLOWBus (Crew Lay-Over Without Bus) (also known as 'jumpbus'), which involves the same bus being rostered to multiple drivers to minimize unproductive layover time. Their bus fleet may vary as they may require lesser buses than the number of scheduled duties.
The following is a summary of the duty notation across the operators deployment pages.
When a new bus service is being introduced, users must only update on the actual day of introduction. Ensure that the route details, depot and bus package allocation are reflected correctly. Bus fleet and duty details can be updated at a later date.
Operation days/timings must be reflected for Short-Trip/Express/Supplementary services or any service that only operates on selected days at certain timings. Departure timings for Short-Trip/Express services must be listed under a table. This does not apply to Express services that operate daily.
When a bus service is slated to be withdrawn, users must only update after the last bus concluded its last departure.
Ensure that the information is synchronised across the respective train station pages if the bus service ply any bus stop near the train station.
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, users 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 editing a non-revenue bus (Bus awaiting de-registration, Laid up bus, Retired bus, Retiring bus), users must remove the bus listing from deployment by bus model pages. However, users 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 deregistered should not be reflected as scrapped until they are officially deregistered.
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. Users are also required to remove their deployment from the following pages:
When there is a change in bus deployment status due to redeployment, users must update the following pages:
See below to differentiate between a cameo bus and a bus attached to a permanent service (perm bus).
Users should only add the following trips in the Notes section:
Users must spot the differences between a Cameo and a Perm Bus. Any bus that ply 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 can be listed down under deployment by service and bus model pages. Trips done by buses under Outside Schedule (OS) must not be reflected as they are unscheduled.
History of Bus Services
When editing the history of bus services, users must use
When making changes, please ensure that there are no operations of the said bus service as the last bus (plying the old routing) may still be in operation past midnight.
Please do not modify the page layout as and when you wish. If you feel that there is room for improvement, we strongly encourage you to consult any administrator/user first before implementing them to the other deployment pages. This includes duty tables listed in the bus deployment by service pages.
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, or meant for a retired bus model page.
It is not compulsory to link all swapped out photos to bus gallery page.
Users 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.