Voice Procedures for Subnet Control Operators: Difference between revisions

From Portland NET Wiki
← Older editNewer edit →
VisualWikitext
→Checking in Stations: Added choice of two preamble scripts.
→Checking in Stations: Clarified procedure
Line 15: Line 15:
If you are operating a subnet involving many teams during a scheduled exercise you may find that calling for all check-ins will cause a pile up and a lot of doubling.  More likely, however, the check-ins will naturally spread out over quite a few minutes for two reasons (a) The operators will probably need to check into a Resource Net first and arrive on your frequency over several minutes.  (b) During an actual deployment operators will become ready to check in over an extended period of time. So, unless your subnet is scheduled to open at a particular time and you expect many operators to be ready to check in at that time you probably don’t need to divide the check ins ranges of call-sign suffixes although you are free to do so if you wish. In fact, your challenge may be quite the opposite: Your operators will arrive over an extended period of time and any information you provide before checking people in will only be heard by a few operators.     
If you are operating a subnet involving many teams during a scheduled exercise you may find that calling for all check-ins will cause a pile up and a lot of doubling.  More likely, however, the check-ins will naturally spread out over quite a few minutes for two reasons (a) The operators will probably need to check into a Resource Net first and arrive on your frequency over several minutes.  (b) During an actual deployment operators will become ready to check in over an extended period of time. So, unless your subnet is scheduled to open at a particular time and you expect many operators to be ready to check in at that time you probably don’t need to divide the check ins ranges of call-sign suffixes although you are free to do so if you wish. In fact, your challenge may be quite the opposite: Your operators will arrive over an extended period of time and any information you provide before checking people in will only be heard by a few operators.     


Here are two scripts to choose from:  
==== Compiling a Roster of Teams ====
To facilitate communication between teams and between teams and the ECC you should create a table of ARO tactical call signs and the NET teams or neighborhoods that each team ARO represents. See [[Logging Procedures for Subnet Control Operators#Instructions for using Stations Participating Form|Instructions for using Stations Participating Form]].
 
==== Recommended Check-In Procedure for Short Simplex Exercises ====
Here are two scripts to choose from:


* [[Script for Checking in a Small Number of Stations]]
* [[Script for Checking in a Small Number of Stations]]
* [[Script for Checking in Stations Alphabetically by Tactical Call Signs]]
* [[Script for Checking in Stations Alphabetically by Tactical Call Signs]]


==== Compiling a Roster of Teams ====
==== Recommended Check-In Procedure for Major Exercises and Deployments ====
To facilitate communication between teams and between teams and the ECC you should create a table of ARO tactical call signs and the NET teams or neighborhoods that each team ARO represents. See [[Logging Procedures for Subnet Control Operators#Instructions for using Stations Participating Form|Instructions for using Stations Participating Form]].
 
==== Recommended Check-In Procedure ====
This example of check-in language is provided as a convenience.  Feel free to modify it as circumstances dictate.
This example of check-in language is provided as a convenience.  Feel free to modify it as circumstances dictate.


A.  This is <your FCC call sign, first name> Subnet Control for the <your region name> region.  
A.  This is <your FCC call sign, first name> Subnet Control for the <your region name> region.  


When I call for check-ins, please give your tactical call sign.  When I recognize you, please give your first name, your full team name slowly and then your FCC call sign slowly using ITU phonetics.  Please come now.
When I call for check-ins, please give your tactical call sign.  When I recognize you, please give your first name, your full team name slowly and then your FCC call sign slowly using ITU phonetics.  Your team name should only be the name of the team or neighborhood hosting the deployment and should include the names of other teams that may be participating at that location.  Please come now.  Please come now with your tactical call sing.


[Check in stations. Record at least the tactical call signs and the team name(s) associated with the call sign.  Recording the operator name and FCC call sign is optional.]
[Check in stations. Record each tactical call sign and then ask for the name of the team that is providing the staging area and record that name.  You can also recording the operator name and FCC call sign but that is optional.]


B. [Choose a station already checked in] There may be stations that cannot hear me that would like to check in.  <Tactical call sign>, please call for check-ins on my behalf, mentioning the name(s) of this region. If you receive a response, please acknowledge the information by repeating it.  I will then confirm that I have heard it or ask for a “say again”.  <Tactical call sign> please proceed with a call for check-ins.  
B. [Choose a station already checked in] There may be stations that cannot hear me that would like to check in.  <Tactical call sign>, please call for check-ins on my behalf, mentioning the name(s) of this region. If you receive a response, please acknowledge the information by repeating it.  I will then confirm that I have heard it or ask for a “say again”.  <Tactical call sign> please proceed with a call for check-ins.  
Retrieved from "https://volunteerpdx.net/index.php/Voice_Procedures_for_Subnet_Control_Operators"