1.1 Purpose and Applicability

This Standard Operating Procedure provides the single clean reference for the conduct of all official GRDN OPS : DVMP sessions. Guidelines herein shall be complied with in full and shall not be excluded during SOP-compliant operations; Procedures apply on activation by the controlling authority.

• All members are encouraged to familiarise themselves with this document. Staff shall be held to it in full.
• This is a living document and may see frequent revision. Crews shall refer to the current published version and to Command for authoritative guidance.
• Critical information is additionally embedded in the Discord and linked from the rules; crews may acquire much of it through play alone.

1.2 Reading Priority

Audience	Required Familiarity
All personnel	Before You Join · Road Crew · Mandatory Procedures
Staff	The above, plus Controlling and Hosting
Standardisation reference	Operations · Protocols and Procedures · Appendices

Guardian Operations, abbreviated GRDN OPS, is a community organised around operational gameplay. Enjoyment is supported; the core values are Semi-Realism, Respect, and Excellence.

1.3 Server Rules

• The rules of the GRDN OPS server are published under the Info category and apply at all times.
• Rules 7 and 10 apply to operations specifically. Violation shall affect a member’s standing and experience within Operations.

1.4 Roster Progression

• New joiners are carried on the roster under the Newcomer role.
• On full attendance of one official operation the host shall convert the member to the Member role, denoting demonstrated familiarity with our operations.

1.5 Classification of Operations

Class	Oversight	Assurance
Official	Vetted host, CMD oversight	Run IAW this SOP. Reasonable performance expected, bot tooling available, feedback routed to Command for improvement.
Unofficial	None	May be hosted by anybody. No access to bot tools or official resources. No guarantee of modpack, procedure, or conduct is made by CMD.

The Official designation denotes assurance of standard, not preference. No member is required to operate official sessions, and unofficial play shall not be held to be incorrect.

1.6 Joining an Operation

• Operations run to a published schedule. Consult the Events tab in the Discord.
• On entry, select a locomotive for which you are licensed IAW 2.4.
• Set your locomotive number using GRDNConnect.
• Proceed IAW Part 2 - Crews and Part 3 - Mandatory Procedures.
• Questions are welcome and shall not be discouraged. Further project information is published at www.grdnnetwork.com.

1.7 GRDN Bot

Run /setcrew in Discord to allocate your role, train number, and preferred name for the session.

1.8 Approved Mod Suite

Modification	Operational Function
DLE (Derail Logistics Engine)	Consist creation and job assignment backend used by Logistics.
Remote Dispatch	Territory view and switch control, available to all crews. The fork in use is specified per operation.
Double Track	Permits opposing and overtaking movements.
Signals	Provides the signal aspects governing controlled territory.
GRDNConnect	In-game train numbering, voice channel movement, and host functions.
CommsAPI	Required backend for GRDNConnect.
Map Image Changer	Renders the valley map in game.

1.9 GRDNConnect - First-Time Linkage

• Load into the session.
• Operate the cab radio (GRDN Crew or GRDN Radio).
• A linkage prompt shall appear in #ops-chat.
• Confirm the prompt to bind your in-game reported Steam ID to your Discord ID.

Thereafter the Comms radio permits movement between Discord channels without leaving the game. This capability is required for control handovers IAW 3.6.

2.1 Road Crew

• The standard crew type. Carries no insignia by default.
• Road Crew are responsible for the movement of freight, passengers, or empty equipment across the valley.
• Road Crew shall normally operate under the authority of Dispatch.
• Road Crew may be further subdivided by the procedure in force - for example into Locals and Interchange crews when a hub-to-hub system is run.

2.2 Yard Crew (Shunters)

• The secondary crew type, ordinarily denoted by the suffix #S.
• Yard Crew are responsible for the assembly, breaking, and organisation of consists within a nominated yard, under a Logistics Officer or Yardmaster.
• Yard Crew are afforded procedural advantages and are ordinarily not held to strict callout formats, including callsigns, when working directly with a Yardmaster.
• Where no Yardmaster or qualified Controller is available, Yard Crew may own their station as Controller for the duration.

2.3 Brakeman

• A Brakeman does not operate a locomotive; the position works in tandem with a train driver or shunter.
• Brakemen are principally employed during shunting, riding the rear of a consist to pass distance information to the engineer and to couple or uncouple equipment.
  • Distance calls shall be acknowledged by the engineer.
• In the case of repeated or intentional poor conduct as engine crew, a member shall be demoted to the Brakeman role.
  • Members holding this role are permitted to serve as Brakeman only, not as Road or Yard Crew.
  • Restoration depends on circumstance. A member shall ordinarily be expected to work several operations without incident and in good sport.

2.4 Locomotive Licensing

NOTICE Framework only - published for future implementation. Licensing gates are not yet enforced across all operations.

• Operations may invoke locomotive licensing for crews.
• DE6, S282, S060, and DH4 are given priority to existing members.
• Members may request attendance of a Steam class where required, and may request additional training on other classes.

2.5 Demonstrators

• Demonstrators are awarded to crews who show exceptional usage of their train - including but not limited to efficiency, extremely heavy hauls, speed, and handling.
• Owners are given their train to mark the achievement and to represent the company.
• Owners may pawn a demonstrator out to others but retain driving priority.
• Frequent Controllers may hold a demonstrator but shall share it while controlling.
• Owners are expected to remain active.

3.1 Communication Standard

• Transmissions shall be brief, relevant, and unambiguous. State who you are calling first, then who you are.
• Once a clear back-and-forth is established, callsigns need not be restated on every transmission unless restatement prevents confusion. A break in traffic resets this allowance.
• Critical Information shall be repeated back and confirmed where required.
• Extended discussion, troubleshooting, or training shall be moved to a BCKP channel where practical.
  • Crews in a BCKP channel remain cleared to their stated limit and shall check back in with the Controller for further clearance before proceeding beyond it.
• Crews operating at or above tonnage capacity may append “Heavy” to their callsign, which grants the priorities and exceptions attaching to that status.
• Callsigns may differ between Controllers, yard crews, and demonstrators. The correct callsign shall be used where known.
• A Controller may adopt a callsign representing their scope - for example Logistics - and that callsign shall be used in preference to the general “Dispatch”.
• On first contact a request call may be made to establish communication before passing further information.

3.2 Call Formats

First contact: [who you are calling], [who you are] [train details], [location]. Request: [who you are calling], [who you are], request? Standard traffic: [who you are calling], [who you are], [location / job / track], [request or intent].

First contact - examples

“Harbour, 023 S060, passing Foxtrot 7 wye, inbound to Echo Nine.” “Hub Control, 064 DE6 heavy, approaching from the north with a 500 m consist.”

Standard traffic - examples

“Harbour, 023, Foxtrot 7 wye, requesting fuel service.” “Harbour, 047, holding short military yard, with you looking for E9I.” “Dispatch, 063, with you east of Farm, for FF.”

3.3 Communication Failsafe

Where a crew is unclear which authority controls them, what limit applies, or whether authority to continue exists, the crew shall slow the locomotive and request clarification before proceeding.

3.4 Control Authority - Dark Territory

Dark Territory is any location not under the control of an active Dispatcher.

• Crews shall monitor their surroundings continuously to avoid collision, using Ops Radio (East/West) to coordinate with nearby Road Crew.
• A train arriving at an occupied station shall establish contact and develop a solution. Yard Crew may issue clearances outside active dispatch scope to facilitate coordinated station movements.
• Signals shall be treated as early warning of conflict. Any unexpected aspect or unexpected change shall be reported immediately.
• Movements in Dark Territory or on other than main track are responsible for setting their own switches and verifying routing.
• Movements with no train in the vicinity require no communication or request.

Territory diagram - dark vs controlled zones

3.5 Control Authority - Controlled Territory

• Movement is governed by the Controller holding the area of operation.
• Switches may or may not be lined. The Controller shall clarify on issue of the movement order; where unclear, the crew shall assume switches are not lined and keep active watch.
• Where switch control within an area is delegated to a shunting movement, that movement becomes responsible for those switches.
• Signals shall be obeyed at all times except where explicit permission is given by the Controller.
• A crew approaching a red signal believed to be set incorrectly may query the Controller but shall not break aspect before clearance is granted.

Signal exception - examples

“086, Hub Control, you are clear to proceed through the next red signal.” “077, Harbour Control, you are clear to violate signals on the east side of Echo yard.” “038, Control, break signal aspect and follow company ahead with caution.”

3.6 Control Transfer

• On approach to the limit of the Controller’s zone the crew shall be instructed to transfer. Crews shall not change voice channels before being cleared to do so.
• The crew shall switch to the receiving control zone using the Comms radio and make a clear first contact call to the receiving Controller.
  • Where the channel is occupied with operational traffic, wait your turn.
  • Where the channel is occupied with non-operational traffic, make an assertive request call and await response.
• Where the transfer is into Dark Territory, the crew shall announce themselves and their intentions.
• No crew shall leave a control zone until clearance is explicitly granted.

4.1 General

• Qualifications are issued by the approving authority for the matter concerned. A team of Controller quals ordinarily vets Controller exams, hosts vet hosting exams, and so on for other classes. Command holds final say.
• To obtain a qualification a candidate shall pass the exam where one exists.
• No candidate shall pass an exam by exemption. Prior experience and recommendation may shorten preparation only.

4.2 Training Structure

A qualification path comprises one or more of the following stages. Not all stages apply to every qualification.

Stage	Standard
Class	Reading or briefing material supporting the related qualification. Where a qualification is class-only it is for personal knowledge and attendance is not required to function in an operation. May be delivered as linked material, a group session, or a 1:1 sit-down.
Exam	Paired with a class where the qualification affords additional quality of life or lifts a limitation. Unproctored; the candidate is trusted not to cheat.
Assessment	Proctored, and ordinarily requires presence in an official capacity to enact the qualification. The strictest route, and the usual path to staff qualifications.
Qualification	Issued on completion of the required stages.

4.3 For All Personnel

• Road Crew Class. Covers general information about our operations, the required sections of this SOP, and operating tips. The qualification received is the Member role, replacing Newcomer.
• Steamer Class. Covers effective use of steam locomotives in the valley and includes an exam. The qualification received is Steam Cert.

4.4 For Staff

• Controller Qual. Controllers are considered low-level staff. Requires an exam and an assessment; a class is available and optional.
• Hosting Qual. Hosts are low to medium-level staff. Requires an exam and an assessment; the class is mandatory.

4.5 Removal or Suspension

Qualifications may be suspended or withdrawn by administrative authority where necessary for performance, conduct, inactivity, or other operational concern.

5.1 Basics

• Controllers are low-level staff who take operational control during an operation. Their focus is moving trains toward their objectives and destinations.
• Controllers shall work together where required to accomplish that mission, and are strongly advised to communicate in a defined, efficient manner to prevent confusion and incident.
• Controllers requiring a framework are advised to adopt common defined procedures IAW Part 8.
• A Controller may wear all, some, or none of the roles below. An operation may not field a Controller of every type.
  • For example, a Controller may claim Dispatch clearance over East but not West, and may additionally hold Logistics Officer for Harbour but not for all stations.
• Controllers may submit incident reports via Op-Records.

5.2 Dispatching

• Dispatchers are responsible for the movement and clearance of Road Crew on the main line between stations.
• Dispatchers shall aim to route consists by the most efficient route at the highest practical speed with minimal delay, accounting for consist weight, estimated top speed, weather conditions, and traffic en route.
• In higher-traffic operations Dispatch may be split East and West of the central river, or by any other defined split.
• The Remote Dispatch mod is used to view consists and set switches across the valley.

5.3 Hub Control / Yardmasters

• Yard Controllers are responsible for all movements, clearances, and signals within the yard or set of yards they control.
• A Controller shall not clear traffic onto, or set switches on, main track without the permission of the relevant Dispatcher or a defined procedure. This shall ideally be conducted through transfer procedures IAW 8.4.
• A Controller shall act to create the least wasted time for inbound and outbound Road Crew, to include:
  • Ensuring shunters do not obstruct the main when traffic is inbound.
  • Having outbound consists ready for departure at all times.
  • Coordinating with the Logistics Officer to allocate freight to crews.
• Hub Control is ordinarily responsible for directing one or more yard crews in the conduct of these operations.

5.4 Logistics

• Logistics Officers are responsible for creating and assigning consists using the Derail Logistics Engine, or acting as a valley-wide Yardmaster assigning locomotives and jobs without DLE.
• Logistics decides which crew runs to which station with which load.

6.1 Fundamentals

• Hosts shall communicate well in English, hold good standing with Command and the community, hold a stable connection and adequate PC specification, and demonstrate leadership.
• Prior to seeking the qualification a candidate shall hold C/W qualification and be familiar with the entire SOP.
• Hosts shall run operations IAW this SOP and shall select a save file fitting the requirements of the operation planned.
• Hosts are advised against purchasing the in-game dispatcher licence, and shall double-check mod settings, to limit trolling.
• Remote Dispatch permissions shall be limited to qualified individuals filling a role that requires them for that session.
  • Hosts may require sign-in under common usernames to avoid cluttering UMM settings - for example Yard Crew for junction permissions, Dispatch for junction and signal permissions.
• Operations and events shall be professionally posted and led.
• Where a host faces a decision without an answer, or an administrative issue, the host shall state that any decision made is temporary and route the issue to an administrator or Command. A host may time out a member causing issues.

6.2 Session Setup

Hosts receive a private channel; setup resources are pinned within it. This procedure assumes Windows.

Resource	Purpose
Save.zip	Career save for the operation.
grdn_ops_ruleset	Ruleset attached to the save.
Mod Preset	Approved mod suite for the session.

• Extract the career archive and copy the Career folder to AppData › LocalLow › Altfuture › Derail Valley › Users › [user] › Career, alongside existing saves. Hidden files may require display to be enabled.
• Place the ruleset file in the DV subdirectory under GameData › Assets. Create the Assets folder where it does not exist.
• Install the host mods as modifications are ordinarily installed.
• Verify by loading Derail Valley that the save is present with the ruleset attached.
• Access mod settings with CTRL+F10 and make the required changes, to include the Remote Dispatch password.
• Under dispatcher permissions set the Default entry to junctions off, loco control off, player blips on, and loco visibility on.
  • As a consequence the host shall grant Dispatch and Harbour permissions to change junctions when those Controllers come online.

6.3 Remote Dispatch Domain

For security, and for compatibility with our bot and mod functions, hosts shall publish Remote Dispatch through a Cloudflare tunnel rather than traditional port forwarding. The tunnel is comparable in concept to Hamachi or ZeroTier but provides a safer path than port forwarding, DNS configuration, or Hamachi.

• Obtain cloudflared from the Cloudflare Tunnel documentation downloads page, by installer or CLI command for your operating system.
• Contact Guardian for assistance. You shall be issued an elevated command-prompt entry that attaches your access token to the cloudflared application.
• You shall then be issued a domain - for example grdn.grdnnetwork.com - for Remote Dispatch, and by proxy a hidden URL through which GRDNConnect functions.

6.4 Debrief

• Hosts shall conduct a debrief.
• Gather information on the particular issues of that operation first, then gather general feedback as the debrief closes.
• Performance information shall be requested for each role.
• Learning is the priority. Personnel shall not be flamed for communications in a debrief environment.

6.5 Op Records

• Log files document issues and provide feedback to our developers. Open a new post in Op-Records, formerly Log Dumps.
• Title the post by class - Event, Operation, or Stress Test - followed by the date in MMDD format.
• Identify clearly which logs are the host’s and attach the files.
• Where many issues were observed, or for a stress test, all participants shall be encouraged to post logs.
• Log files are located at AppData/LocalLow/Altfuture/Derail Valley/player.log.
• The channel may also be used for debrief notes and Controller incident reports; #hosting may be used in the alternative.

7.1 Basics

• This Part carries information shared across all operations that is not detailed elsewhere. Operation-specific detail is held in the subordinate sections.
• Procedures applying to a specific operation are found in Part 8 - Protocols and Procedures.
• An operation may enforce stricter requirements than those published here but shall not lift restrictions.

7.2 Official Operations

Official operations are held to the standard set in 1.5 and run per SOP. This document is followed substantially one-to-one; deviations shall be declared by the host.

7.3 Company Realistic

Company Realistic, formerly US OPS, is our flagship operation style, focused on semi-serious gameplay, communications, and presentation. Created and led by our founder, Guardian.

7.4 Continuously Better Transport

Continuously Better Transport, abbreviated CBT, is an extra-hardcore operation style in which the road to success is nowhere to be seen and mistakes are severely punished. Created and led by our host, Arnoldio.

Area	Standard
Comms	Required at all times.
Main / Dark / Yard	Mainline is always covered by a Dispatcher. Destination stations are assigned to the first Road Crew to arrive and revoked on departure unless otherwise specified. A station not in use is considered mainline and is off limits.
Usernames	In-game usernames are kept as-is.
Locomotive rating	All locomotives are free to use. Passing a trial reserves a specified locomotive number for your use per the leaderboard; you may use all locomotives up to and including the one earned. An obtained licence does not guarantee a free locomotive where all of that type are in use.
Trials	One unified run on a predetermined route and yard against a reference time and tonnage, completed within the allowed deviation.
Server restart	Every 150 - 180 minutes.

NOTICE CBT job-taking and logistics advisory pending publication per the CBT FAQ.

7.5 Stress Testing

NOTICE Section reserved. Stress test conduct, tolerances, and reporting requirements not yet published.

8.1 Protocols

• A Protocol is a grouping of Procedures.
• An operation may not run a specific protocol at all times but may hold a standard protocol. Company Realistic may ordinarily run Protocol US OPS, while a Controller may log on and change the protocol or the individual procedures.
• Controllers are not compelled to run a protocol, but where a protocol is activated by a Controller it shall be followed by crews.

8.2 Procedures

• Procedures are standardised sets of expectations, which may include restrictions, requirements, and other pertinent information.
• A Controller may or may not activate a procedure. Where a procedure is chosen it shall be followed by crews.
• Unlike protocols, multiple procedures may be activated together where they do not conflict, and may be run under a New Procedure.
• New procedures may be devised by a crew or Controller and are not required to appear in this document. Once tested and in frequent use they may be standardised and published here.

8.3 Protocol List

Protocol	Constituent Procedures
US OPS	Harbour Default
EU OPS	Central Hump
EU 2 OPS	Central Vanilla

NOTICE EU OPS carries one further unnamed procedure pending publication.

8.4 Transfers

A transfer occurs whenever a locomotive or consist leaves a Controller’s zone.

• Handover. The consist is immediately entering the zone of another Controller. The Controller shall instruct the driver to change voice channels to, and make contact with, the receiving Controller.
  • On double track: the consist shall be lined to the right-hand track; clearance shall be granted up to but not past the end of double track; the receiving Controller may be notified but need not be.
  • On single track: the receiving Controller shall be notified and the XFER accepted before clearance is given. An accepted transfer is a confirmed /xfer command or a verbal or written confirmation. Clearance shall be granted up to the next switch.
• Exit. The consist leaves into Dark Territory. No channel change or contact is required, but it shall be made clear that the Controller no longer holds jurisdiction.

Handover - example

“086, HB Control, your transfer is approved. Switch to and contact Dispatch East.”

8.5 Hubs - Central

The purpose of the Central Hub is centralised sorting, such that Road Crew may take longer jobs without requiring matching destinations at departure. On arrival at the hub a crew is assigned a new train already prepared to depart. Loading tracks are designated L; storage tracks are designated S.

• All inbound signals shall be set to Stop by default. Use the merging point of double track as the entry signal to retain flexibility where Dispatch is late with the XFER.
• On an inbound XFER request from any station, determine when the train will arrive.
  • Where arrival is imminent and a free track of sufficient length is available, set the switches and corresponding entry signal while accepting the transfer.
  • Where space is unavailable and arrival is imminent, ensure the train has stopped at the entry signal and accept the transfer.
  • Where arrival is not imminent, plan ahead to avoid a shunting manoeuvre in progress at the train’s ETA.
• Manoeuvres conflicting with an inbound train shall be commenced only where they are expected to finish before that train arrives.

NOTICE Central Vanilla inherits the defaults above; specifics not yet expanded.

8.6 Central Hump Procedure

Applies where an unsorted train is received into either empty yard connected to the hump track.

• Assign tracks. Review the destinations held and assign a compatible track in the yard opposite the hump track according to car count.
  • Keep one track free for sudden inbound trains and to permit running around to the far side of the yard.
  • Where destinations exceed available tracks, assign a mismatch track for a later hump in the opposite direction.
  • Two destinations lying close together may share a track where the resulting shunting demand at the first drop-off remains minimal.
• Prepare cars. Couple all cars together, dump the air without recharging, uncouple all cars from each other, then release the brakes on all cars.
• Hump. Push with a power-limited or carefully controlled locomotive, not exceeding the speeds tabled below. Pushing speed governs the rate cars enter the yard and therefore the time available to flip junctions; keep speeds low for laggy operations.
• Flip junctions. A junction may be flipped for the following car as soon as the preceding car is completely clear of it.
  • Junctions may require throwing in parallel, or in reverse order, where pushing speed is high.
  • Where a switch is missed, do not attempt to fix it - a drifting car would be detrimental. Reassign tracks to keep future shunting demand low, or re-hump later.
• Apply handbrakes. Apply as a car approaches the end of a track, maintaining half a car length of clearance to the next switch at all times, as following cars may push it along.
• Post-hump. Couple all loose cars together again. Where this is not done in external view, keep a handbrake applied at both ends of the consist to prevent coupling from pushing cars apart.

Movement	Track	Pushing Speed
FM to OWC	Hump track	2 - 5 km/h
FM to OWC	Normal track (no Double Track)	7 - 10 km/h
OWC to FM	Hump track	2 - 10 km/h

FM to OWC on normal track is the most demanding mode, as cars enter the yard at a materially faster rate.

Locomotive	Hump Handling
DE2	Notch 1. Where tonnage exceeds one locomotive, add a second DE2 also in notch 1 to prevent slipping and overheating. A crew member shall stand by to cut or reduce power as the train is nearly fully humped.
DM3	First gear, throttle between 1 and 6 according to load. No standby crew required, as first gear will not catch the humped cars.
S060	Crew shall be in the cab at all times. Not yet tested.
DH4	Crew shall be in the cab at all times. Not yet tested.

NOTICE Harbor, Signals, Traffic Patterns, Crop Circle, and High Flow procedures reserved - not yet published.

This Part carries auxiliary information referenced by the remainder of the document.

A.1 Tonnage Sheet

Figures are maximum rated tonnage. RT Flat denotes level road, RT 2% denotes sustained grade, RT WX 2% denotes sustained grade in adverse weather.

Train Type	RT Flat	RT 2%	RT WX 2%
DE2	1,200	300	250
DH4	2,000	600	500
DM3	2,000	500	400
DE6	3,000	1,200	1,000
S060	1,500	400	350
S282	3,000	1,000	800

A.2 Valley Map

Valley map - territory and hub boundaries

A.3 Definitions

Term	Meaning
Advisory	Informational traffic providing warning, planning, status, or expectation. Does not of itself authorise movement, and requires no response unless acknowledgment is specifically requested.
Aspect	The indication given by a signal.
Call	An initial contact transmission establishing communication with a specific party before passing further information, requests, or instructions. Normally identifies who is being called and who is calling, then awaits acknowledgment.
Clearance	A positive instruction authorising movement, entry, occupancy, or route use within stated limits.
Consist	The entire train and the cars attached.
Contact Point	The point at which Road Crew are expected to swap channels or make first contact with the receiving side.
Control Boundary	The point or limit at which one Controller’s authority ends and another’s begins.
Coordination Point	The point at which Controllers begin working a handoff, before the train reaches the boundary.
Critical Information	Any information capable of immediately affecting movement, authority, occupancy, routing, or operational safety if delayed, omitted, or misunderstood.
Dark Territory	An area with no active local Controller or dispatch authority assigned. See Valley Map.
Dispatch / RTC	Subdivision-level control responsible for through traffic, inter-area flow, and broader routing.
Expedite	Safely move as fast as possible; complete the order promptly or without delay.
Foul / Fouling	Equipment blocking a track without occupying it, including standing too close to a switch such that a movement on an adjacent route could strike it.
FYSA	For Your Situational Awareness.
Guidelines	SOP material that shall be complied with and shall not be excluded during SOP-compliant operations.
Heavy	A callsign appendix applied to a train operating near, at, or above the defined heavy-tonnage threshold. Subject to special restrictions, handling considerations, or procedural priority.
High Tonnage	A train meeting the current tonnage-sheet threshold, or declared operationally restrictive by crew and accepted as such by Dispatch.
Hold / Hold Point	An instruction to remain clear of a stated limit or hold in place until further direction. May be predetermined or given on the spot.
Hub	A yard or set of yards operating under one Controller, separate from Dispatch.
Hub Control	The title used for the Controller in charge of an operational hub.
IAW	In Accordance With.
Logistics	Controller responsible for directing the location and job assignment of Road Crew and shunters.
Main Track	All tracks connecting one station to another.
Other Than Main Track	All tracks within yard limits or sidings, or otherwise not labelled main track.
Procedures	General guidelines governing how movements and operations shall be executed.
Road Crew	The crew operating a consist on main track.
Traffic Advisory	A warning or heads-up call that does not of itself authorise movement.
Without Delay	To complete promptly, often urgently. Includes permission to interrupt ongoing conversation, and may carry critical information or movements.
With You	Initial contact language denoting that the crew is on that Controller’s channel and ready for direction.
XFER	Transfer of control of a train from one Controller or controlled area to another.
Yard Crew	The crew operating a locomotive inside a yard and moving cars, ordinarily under a Hub Controller. Also referred to as shunters.
Yard Main	A main track running through a yard, ordinarily called by the phonetic for the yard followed by main - the E yard main as “Echo Main” - while still falling under other than main track.