Voice Procedures for Subnet Control Operators: Difference between revisions
From Portland NET Wiki
BruceSchafer (talk | contribs) →Handling NET Form 8 Traffic from NET Teams Including Triage: Added links to further information |
BruceSchafer (talk | contribs) →Calling for Relays: Added links to pages giving detailed procedures for relaying |
||
| (10 intermediate revisions by 2 users not shown) | |||
| Line 13: | Line 13: | ||
(2) Over what amount of time you expect the check-ins to occur. | (2) Over what amount of time you expect the check-ins to occur. | ||
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. | 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. | ||
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. | |||
==== Compiling a Roster of Teams ==== | ==== 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]]. | 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 ==== | ==== 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 Stations Alphabetically by Tactical Call Signs]] | |||
==== Recommended Check-In Procedure for Major Exercises and Deployments ==== | |||
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 sign. | ||
[Check in stations. | [Check in stations. Using the [https://docs.google.com/document/d/1M3TuoKgcmAiWSjhj5dgOAZCkpmaA2fIUSbXxQPXPYf8/edit?tab=t.0 Stations Participating Log], 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. | ||
| Line 75: | Line 79: | ||
J. [If time permits you can allow stations that are checked in to ask questions. Don’t forget to return to the main sequence – Step 7 – to do things like contacting Tactical Net to report your roster.] | J. [If time permits you can allow stations that are checked in to ask questions. Don’t forget to return to the main sequence – Step 7 – to do things like contacting Tactical Net to report your roster.] | ||
What To Do If Stations Attempt to Check-In That Are Not Part of the Exercise | ====== What To Do If Stations Attempt to Check-In That Are Not Part of the Exercise ====== | ||
Most amateur radio nets attempt to be very open to guests. During exercises and deployments, however, it is usually inappropriate for guests to check in. If a station attempts to check in that is not part of the exercise or deployment you should politely explain that the circumstances do not allow the extra time that would be required to communicate with guests. | Most amateur radio nets attempt to be very open to guests. During exercises and deployments, however, it is usually inappropriate for guests to check in. If a station attempts to check in that is not part of the exercise or deployment you should politely explain that the circumstances do not allow the extra time that would be required to communicate with guests. | ||
What To Do If More Than One Operator from the Same Team Tries to Check In | ====== What To Do If More Than One Operator from the Same Team Tries to Check In ====== | ||
A slightly different circumstance occurs when more than one operator from a particular team attempts to check in. If this happens you should explain that only one operator should represent a particular team at a time. You can also mention that they should use the same tactical call sign if they decide to change the operator representing their team during the exercise. | A slightly different circumstance occurs when more than one operator from a particular team attempts to check in. If this happens you should explain that only one operator should represent a particular team at a time. You can also mention that they should use the same tactical call sign if they decide to change the operator representing their team during the exercise. | ||
=== Calling for Relays === | === Calling for Relays === | ||
The strength of communication will vary from exercise to exercise and operator to operator based on factors like location, elevation, available transmission power and sensitivity and selectivity of receivers. Note that there are many combinations of these factors in a region including a subnet controller who may be in a different location and team AROs in varying locations depending on who is available and the nature of the exercise or deployment. This unpredictability of simplex communication means that you and the other operators must be ready to ask for and provide relays. There are at least two cases to consider. | The strength of communication will vary from exercise to exercise and operator to operator based on factors like location, elevation, available transmission power and sensitivity and selectivity of receivers. Note that there are many combinations of these factors in a region including a subnet controller who may be in a different location and team AROs in varying locations depending on who is available and the nature of the exercise or deployment. This unpredictability of simplex communication means that you and the other operators must be ready to ask for and provide relays. There are at least two cases to consider -- stations you cannot hear and stations that cannot hear you. | ||
==== [[Procedure for When Some Operators Cannot Hear Net Control Operator]] ==== | |||
==== [[Procedure for When Net Control Operator Cannot Hear Some Operators]] ==== | |||
=== Appointing a Temporary Subnet Controller === | === Appointing a Temporary Subnet Controller === | ||
There are several circumstances when you may need to leave the subnet and to appoint an interim subset control. Examples of such circumstances are when you are called away by the ECC, when you need to send Winlink messages, and when you need to take a break. In these cases you should consider three criteria (a) The apparent skill level of operators checked into your subnet (b) their ability to hear and be heard by other stations in your region. The latter will be influenced by the equipment they have at their disposal and (c) their location within your region. Choose an alternate who is a good fit for the role and is willing to take it on and inform the operators of your decision. When you return, wait for a break in the communication, announce your return and resume your role as subnet control operator. | There are several circumstances when you may need to leave the subnet and to appoint an interim subset control. Examples of such circumstances are when you are called away by the ECC, when you need to send Winlink messages, and when you need to take a break. In these cases you should consider three criteria (a) The apparent skill level of operators checked into your subnet (b) their ability to hear and be heard by other stations in your region. The latter will be influenced by the equipment they have at their disposal and (c) their location within your region. Choose an alternate who is a good fit for the role and is willing to take it on and inform the operators of your decision. When you return, wait for a break in the communication, announce your return and resume your role as subnet control operator. | ||
=== Transmitting a Roster to | === Transmitting a Roster to the Portland EOC === | ||
After completing checking stations into your subnet, you need to switch to Tactical Net on MC-8 to give them your check-in roster. You should do this even if you’re not sure that all stations in your region have checked in. Before leaving the frequency ask one of the AROs on frequency to serve as temporary subnet control. Then transition to Tactical Net and give them the tactical call signs of the AROs that checked into your subnet. Tactical Net may ask you for clarification of what teams are represented by each tactical call sign. When that information is acknowledged, return to your subnet and resume | After completing checking stations into your subnet, you need to switch to Tactical Net on MC-8 to give them your check-in roster. You should do this even if you’re not sure that all stations in your region have checked in. Before leaving the frequency ask one of the AROs on frequency to serve as temporary subnet control. Then transition to Tactical Net and give them the tactical call signs of the AROs that checked into your subnet. Tactical Net may ask you for clarification of what teams are represented by each tactical call sign. When that information is acknowledged, return to your subnet and resume your subnet controller role. | ||
If additional teams check into your net later, you will need to contact Tactical Net again and provide them the additional stations. Likewise if teams check out before the end of the deployment or exercise. | If additional teams check into your net later, you will need to contact Tactical Net again and provide them the additional stations. Likewise if teams check out before the end of the deployment or exercise. | ||
| Line 139: | Line 142: | ||
[Return to your subnet frequency.] | [Return to your subnet frequency.] | ||
=== Handling Traffic from Emergency | === Handling Traffic from Emergency Operations Center to NET Teams === | ||
You may receive a voice message from the Command operator that is intended to be conveyed to the participating teams in one of the following formats: | You may receive a voice message from the Command operator that is intended to be conveyed to the participating teams in one of the following formats: | ||
| Line 167: | Line 170: | ||
Ask stations in your subnet if they have formal traffic ready to transmit. (Such traffic should be on NET Form 8.) If so, ask them to provide counts of available messages not previously forwarded by the four precedence levels. Use the [[Logging Procedures for Subnet Control Operators#Instructions for using the Traffic Count Worksheet|Traffic Count Worksheet]] to keep track of the number and precedence of messages that are ready for your to handle. Take Emergency messages from all your stations before moving on to take Priority messages. Likewise, take Priority messages before Health & Welfare and take any Routine messages last and only if you have time. | Ask stations in your subnet if they have formal traffic ready to transmit. (Such traffic should be on NET Form 8.) If so, ask them to provide counts of available messages not previously forwarded by the four precedence levels. Use the [[Logging Procedures for Subnet Control Operators#Instructions for using the Traffic Count Worksheet|Traffic Count Worksheet]] to keep track of the number and precedence of messages that are ready for your to handle. Take Emergency messages from all your stations before moving on to take Priority messages. Likewise, take Priority messages before Health & Welfare and take any Routine messages last and only if you have time. | ||
If some of the traffic is addressed to someone at the Emergency Coordination Center (ECC) see [[Winlink Procedures for Subnet Controllers#Preparing | If some of the traffic is addressed to someone at the Emergency Coordination Center (ECC) see [[Winlink Procedures for Subnet Controllers#Preparing Your Traffic and Notifying ECC|Preparing Your Traffic and Notifying ECC]]. | ||
Traffic from teams may include replies to messages from ECC that you delivered to them earlier. See [[Winlink Procedures for Subnet Controllers#Handling Replies to Winlink Formal Traffic|Handling Replies to Winlink Formal Traffic]]. | Traffic from teams may include replies to messages from ECC that you delivered to them earlier. See [[Winlink Procedures for Subnet Controllers#Handling Replies to Winlink Formal Traffic|Handling Replies to Winlink Formal Traffic]]. | ||
| Line 186: | Line 189: | ||
Teams may need to contact other teams to share information or coordinate their activities. These contacts may be (a) tactical communication using a frequency proposed by one of the teams; (b) tactical communication using a prearranged frequency; (c) formal messages between teams in the same region using NET Form 8; or (d) formal messages between teams in different regions. During the exercise you should expect some teams to use option (a). | Teams may need to contact other teams to share information or coordinate their activities. These contacts may be (a) tactical communication using a frequency proposed by one of the teams; (b) tactical communication using a prearranged frequency; (c) formal messages between teams in the same region using NET Form 8; or (d) formal messages between teams in different regions. During the exercise you should expect some teams to use option (a). | ||
==== | ==== Tactical communication between teams using a frequency proposed by one of the teams. ==== | ||
The two teams usually won’t choose a frequency in advance. In this case, the team seeking to initiate the communication should find a frequency that appears to be available and ask the subnet controller for help in communicating the proposed frequency to the other team and asking if they are willing to change frequencies. The team may want to propose a UHF frequency or possibly a VHF frequency unless cell service is available. Unless additional Amateur Radio operators are available to handle the direct communication, one or both of the operators may need to temporarily check out of the subnet and then check back in when they are finished with their direct tactical communication. In this case they should keep their direct communication as short as possible so they won’t miss important communications from the ECC. | The two teams usually won’t choose a frequency in advance. In this case, the team seeking to initiate the communication should find a frequency that appears to be available and ask the subnet controller for help in communicating the proposed frequency to the other team and asking if they are willing to change frequencies. The team may want to propose a UHF frequency or possibly a VHF frequency unless cell service is available. Unless additional Amateur Radio operators are available to handle the direct communication, one or both of the operators may need to temporarily check out of the subnet and then check back in when they are finished with their direct tactical communication. In this case they should keep their direct communication as short as possible so they won’t miss important communications from the ECC. | ||
==== | ==== Tactical communication between teams using a prearranged frequency ==== | ||
Tactical communication may be somewhat easier if the teams involved have agreed to use a particular frequency for such situations. If that is the case they may proceed to attempt to establish communication using the agreed upon frequency, assuming the other team is monitoring the frequency. Otherwise one team may need to use the regional frequency to let the other team know that they want to establish direct communication. Also, if either operator is currently checked into a regional subnet, that operator should find an alternate operator to take over with subnet communications or the alternate operator may handle the inter-team communication. If the former is chosen, the operator currently checked into the subnet should inform the subnet controller before leaving the subnet frequency. If no alternate operator is available and communication with the other team is particularly important, the operator can request to be checked out of the subnet and then check back in when they have complicated their direct communication. | Tactical communication may be somewhat easier if the teams involved have agreed to use a particular frequency for such situations. If that is the case they may proceed to attempt to establish communication using the agreed upon frequency, assuming the other team is monitoring the frequency. Otherwise one team may need to use the regional frequency to let the other team know that they want to establish direct communication. Also, if either operator is currently checked into a regional subnet, that operator should find an alternate operator to take over with subnet communications or the alternate operator may handle the inter-team communication. If the former is chosen, the operator currently checked into the subnet should inform the subnet controller before leaving the subnet frequency. If no alternate operator is available and communication with the other team is particularly important, the operator can request to be checked out of the subnet and then check back in when they have complicated their direct communication. | ||
==== | ==== Routing formal messages within a region ==== | ||
The other major case is when a team has a formal message that they want to route to another team. In some cases they may be able to do this using the tactical communication method above. In other cases it may be better to route a formal message via their subnet controller. If the team to receive the message is in the same region the subnet controller may be able to read the message to them. Or, if there is a strong simplex communication path between the two teams, the subnet controller may give the originating team permission to use the subnet frequency to read the message to the receiving team. | The other major case is when a team has a formal message that they want to route to another team. In some cases they may be able to do this using the tactical communication method above. In other cases it may be better to route a formal message via their subnet controller. If the team to receive the message is in the same region the subnet controller may be able to read the message to them. Or, if there is a strong simplex communication path between the two teams, the subnet controller may give the originating team permission to use the subnet frequency to read the message to the receiving team. | ||
==== | ==== Routing formal messages between regions ==== | ||
The situation is even more complicated if the team to receive the messages is checked into a different regional subnet than the originating team. In that case, the subnet controller may need to route the message through the ECC radio room via the Tactical Net. Alternatively, the controller could transcribe the message into a Winlink ICS 213 and route it to the other subnet via a Winlink gateway. The receiving subnet controller could then read the message to the receiving team. | The situation is even more complicated if the team to receive the messages is checked into a different regional subnet than the originating team. In that case, the subnet controller may need to route the message through the ECC radio room via the Tactical Net. Alternatively, the controller could transcribe the message into a Winlink ICS 213 and route it to the other subnet via a Winlink gateway. The receiving subnet controller could then read the message to the receiving team. | ||
