Editing SimSig:House Rules
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
== Voice chat etiquette and protocol == | == Voice chat etiquette and protocol == | ||
Line 11: | Line 9: | ||
When joining the session, it is advisable to rename your Discord nickname to your sim and workstation then your name in brackets, e.g. "KXC Palace (Claire)". If doing this, you must remember to update your Discord name if you change panels part way through a session, and when you leave the session, or it is over, that you return your username to what it was beforehand, as to keep the Discord server neat and tidy - it can get very confusing when someone has their name set to a panel they worked two weeks ago starts sending messages! | When joining the session, it is advisable to rename your Discord nickname to your sim and workstation then your name in brackets, e.g. "KXC Palace (Claire)". If doing this, you must remember to update your Discord name if you change panels part way through a session, and when you leave the session, or it is over, that you return your username to what it was beforehand, as to keep the Discord server neat and tidy - it can get very confusing when someone has their name set to a panel they worked two weeks ago starts sending messages! | ||
The sessions start with a briefing, with a short debrief and rebrief at the start and end of the half-time break, and a debrief and handover at the end of the session. Please ensure that the only person transmitting during these periods are the hosts of the sessions unless you have been asked to speak, to ensure that the briefings take as little time as possible and that it is clear to all taking part as to what is going on during the session. Hosts have the ability to server mute people during these briefings if there's too many interruptions, and things begin to take too long. You should also ensure that handovers are undertaken smoothly without any interruption, to ensure that people are aware what is going on in panels. | |||
Pay attention to specific instructions on how to use ROC correctly as it continues to evolve. Please read the [[SimSig:Railway Operating Centre|Railway Operating Centre Manual Page]] before beginning. | |||
=== Keywords and phraseology === | === Keywords and phraseology === | ||
Line 29: | Line 27: | ||
If you can see confusion and delay about to unfold in front of you while everyone else is politely taking it in turns to provide the channel with uninterrupted natter, start your message with '''Break, break'''. Its meaning is "I have an urgent message and need to cut in now, shush for a moment and listen, else there'll be Double Yellows of Confusion, Brake Lever of Delay, etc…", but it's a bit briefer. For example: | If you can see confusion and delay about to unfold in front of you while everyone else is politely taking it in turns to provide the channel with uninterrupted natter, start your message with '''Break, break'''. Its meaning is "I have an urgent message and need to cut in now, shush for a moment and listen, else there'll be Double Yellows of Confusion, Brake Lever of Delay, etc…", but it's a bit briefer. For example: | ||
* "Break, break: Hitchin, Welwyn, 1S69 approaching." | * "Break, break: Hitchin, Welwyn, 1S69 approaching." | ||
=== Communicating with Control === | === Communicating with Control === | ||
Let the channel know before you call Control. Make sure neighbouring signallers know you're aware of any approaching trains, or ask them to set routes within your area if they see a need while you're out of the channel. You should also inform neighbouring signallers of the reason why you are | Let the channel know before you call Control. Make sure neighbouring signallers know you're aware of any approaching trains, or ask them to set routes within your area if they see a need while you're out of the channel. You should also inform neighbouring signallers of the reason why you are causing control, if it is going to cause them a problem, and if a line is blocked due to a technical fault, to not send any trains into the failure to avoid them from getting trapped. | ||
Control must be informed of any incident which has the possibility to cause delays to any train, including any technical fault, or a train which has stopped at a station and will be delayed at that station. You must also inform control of what impact this might have on other train running on nearby lines, so that control are aware and are able to take action to attempt to minimise delays to other services. Control must also be aware of any train running delay in excess of ten minutes, especially if it is a train which is contained within the session, either through a chain or as a result of rules in the timetable. | Control must be informed of any incident which has the possibility to cause delays to any train, including any technical fault, or a train which has stopped at a station and will be delayed at that station. You must also inform control of what impact this might have on other train running on nearby lines, so that control are aware and are able to take action to attempt to minimise delays to other services. Control must also be aware of any train running delay in excess of ten minutes, especially if it is a train which is contained within the session, either through a chain or as a result of rules in the timetable. | ||
Line 42: | Line 39: | ||
When the call ends, let the channel know you're back, and pass on relevant information from Control. Even if it's not relevant information it's probably interesting. | When the call ends, let the channel know you're back, and pass on relevant information from Control. Even if it's not relevant information it's probably interesting. | ||
=== Reminders (the signalling kind) === | === Reminders (the signalling kind) === | ||
Line 73: | Line 54: | ||
You should also make sure to communicate with the controller should you begin to become overloaded or overworked whilst on a panel, as a signaller remaining overworked can cause additional, avoidable delays, and affect other signallers in a multiplayer chain. A controller will always be able to help ease the workload, whether by assisting themselves or finding an extra body to lend a helping hand to get train movements to a neater, more desirable state. | You should also make sure to communicate with the controller should you begin to become overloaded or overworked whilst on a panel, as a signaller remaining overworked can cause additional, avoidable delays, and affect other signallers in a multiplayer chain. A controller will always be able to help ease the workload, whether by assisting themselves or finding an extra body to lend a helping hand to get train movements to a neater, more desirable state. | ||
{{SimSig Sessions}} | {{SimSig Sessions}} | ||
[[Category:SimSig]] | [[Category:SimSig]] |