SgWiki:Guidebook/sgWiki Buses

Introductions

Editing & Formatting

Links

Citing sources

sgWiki Buses

sgWiki Rails

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.

Bus Deployments

Format

Bus models listed under service deployment and spare buses pages must be arranged in the following format:

• Non-Wheelchair Accessible buses, followed by Wheelchair Accessible buses.
• Starting off with Single-deckers/Midibuses, Double-deckers followed by Articulated buses in alphabetical order

Do note that past deployments listed under Former Deployments page with

• Italic font
  Indicates that the service was withdrawn and re-introduced with another route variation (E.g. Service 5).
• Strikethrough font
  Indicates that the service has been withdrawn.

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.

Bus Fleet Size

Rescheduling of bus services will take place over certain period of time. This would mean that there might be an adjustment of bus fleet/duties. When such changes are known, ensure that the following tallies with one another:

1. Bus Service fleet
2. Number of duties
3. Total number of buses

If the service deployment fleet does not tally with the total number of buses, users should reflect the following under the "Notes" section:

• (Number) missing bus(es). (E.g. 1 missing bus/2 missing buses.)
• (Number) extra bus(es). (E.g. 1 extra bus/2 extra buses.)

It is not compulsory to state the specific type of bus model or the original fleet size.

Bus redeployed from one service to another service ≠ Respective 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. Specific duty allocation tables should not be reflected for jumpbus services.

The following is a summary of the duty notation across the operators deployment pages.

Shift	SBS Transit	SMRT Buses	Tower Transit	Go-Ahead
Morning	AM	AM	A	AM
Afternoon	PM	PM	P	PM
Split	S	S1	S	SS
Extended	E	S2	N/A
Three Quarter	T	TQ	T	TQ

• Duties are separated by a slash for easier reference.
• Total bus fleet count must be indicated at the end.
• Total duty count will be added instead if the service practices jumpbus or total bus fleet size is unknown.
• Specific depot/bus park names must be included before the duties if the service is under dual depot control.
  E.g. Bukit Batok 10AM-12PM / 7S / 2E / 1T; Bedok 5AM-3PM / 2S / 5T (32 buses)
  • Note that several SBS Transit services have their extended duties slotted before split duties under their block numbers, hence the different arrangement of duties.

Special Departures

Users should only add the following trips in the Notes section:

1. Scheduled down-route trips,
2. Scheduled early trips, and
3. Scheduled interlining trips.

Ensure that the timings are matched accordingly in the notes section:

Before 0630	before ~ AM Peak
0630 to 0900	during ~ AM Peak
0901 to 1659	during ~ AM Off-Peak
1700 to 1930	during ~ PM Peak
After 1930	during ~ PM Off-Peak

Bus Services

When a new bus service is introduced, users can only update the deployment page on the actual day of introduction. Ensure that the following are reflected correctly:

1. Bus route details
2. Bus depot allocation
3. Bus service operator (Includes table colour code)
4. Bus package allocation.
5. Bus fleet and duty details (Can be updated at a later date)

Operation days and timings must be reflected for services that do not operate daily. Departure timings must be presented in a table for Short-Trip and Non-Basic services.

When a bus service is slated to be withdrawn, users must only update after the last bus concluded its final departure.

Ensure that the information is synchronised across the respective train station pages if the bus service calls along any bus stop near any train station.

New Buses

When editing newly-registered buses, users must update the following pages:

1. Specific bus model deployment,
2. Bus Lifespan Expiry Date,
3. Singapore Bus Fleet,
4. Main bus deployment, and
5. Spare buses (Only applicable for SMRT & SBS Transit buses, if newly deployed).

Non-Revenue Buses

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:

1. List the listing in the Non-Revenue Buses page (Former service deployment and status)
2. Bus Lifespan Expiry Date page (if necessary).

Do note that de-registered buses can only be updated as 'De-registered' (by default) after 2359 hours of the actual de-registration date of the bus.

Buses that are scrapped even before their deregistration date must be reflected as 'Scrapped & Awaiting de-registration' until they are officially deregistered.

For buses that are awaiting de-registration prior to de-registration, they should be reflected as 'Awaiting de-registration' in the non-revenue buses page. Users are also required to remove their deployment from the following pages:

1. Deployment by service,
2. Deployment by bus model,
3. Former deployment by bus model,
4. Buses in depots by bus model, and
5. Spare buses (Only applicable for SMRT & SBS Transit buses).

Redeployments

When there is a change in bus deployment status due to redeployment, users must update the following pages:

1. Deployment by service,
2. Deployment by bus model,
3. Former deployment by bus model (Spare status should not be listed if newly deployed to a permanent service),
4. Buses in depots by bus model (if there are changes in depots), and
5. Spare buses (Applicable for SMRT & SBS Transit redeployment, if deployed to a permanent service or removed from a permanent service).

See below to differentiate between a cameo bus and a bus attached to a permanent service (perm bus).

Bus Advertisements

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 more than one bus is bearing the same advertisement.

If the advertisement has been removed from the bus (also known as 'Adless'), the {{N/A}} template must be reflected under the "Advertisement" column. Do amend the rowspan count if necessary.

Cameo/Perm Bus

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:

1. Bus has been deployed on the same service over a long period of time (including newly introduced services).
2. Perm stickers have indicated the deployment changes. (for SBS Transit buses only)

At times, buses are scheduled to interline to other services during some parts of the day. Such crossover duties can be listed down under deployment by service and bus model pages. Bus trips deployed under Outside Schedule (OS) must not be reflected.

History of Bus Services

When editing the history of bus services, users must use

• Past tense
  If changes have taken effect, or
• Future tense
  If changes have not have taken effect with a known effective date.

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.

Page Layout

Please do not modify the page layout as and when you wish. We strongly encourage you to consult any administrator/user first before implementing them to the other deployment pages.

Photos of Buses

When uploading a photo of a particular bus for a bus model page, ensure that:

1. Name of the photo is uploaded under the standardised format:
   Registration number & Service (E.g. SBS1Z 2.jpg)
2. Photo consists of front and nearside/offside of bus. Any full front/rear, rear paired with nearside/offside or 'head' shots are strongly discouraged.
3. Bus is captured on revenue service or when its deployed for training purposes (for buses that are deployed under Training).
4. Front Electronic Display System (EDS) of bus is not corrupted in the photo.
5. No advertisement is pasted on the bus, except for buses with in-house advertisement. (E.g. SBS8000Z, SBS8001X, SBS8002T, SG4001J, etc.)

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:

[[File:SBS1Z 2.jpg|thumb|right|400px|{{Go-Ahead Singapore}} SBS1Z (Service 2)]]

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.

Redundant Pages

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.