Anonymous

Voice Procedures for Subnet Control Operators: Difference between revisions

From WikiNET

Voice Procedures for Subnet Control Operators (view source)

Revision as of 15:48, 3 October 2023

880 bytes removed ,  3 October 2023
→‎Handling NET Form 8 Traffic from NET Teams Including Triage: Corrected internal link
m (BruceSchafer moved page Subnet Control Procedures to Voice Procedures for Subnet Control Operators: Distinguishes it better from Winlink Procedures for SNCs)
 
(6 intermediate revisions by the same user not shown)
Line 18: Line 18:


==== 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. For example, South Heights might represent the neighborhoods of Rockefeller, South Heights, Dogwood, and Petunia. In another case, the tactical call sign Farthworth might represent a single neighborhood called Farthworth. Here is the recommended format.  Feel free to use a separate sheet of paper to create a similar table.  
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]].
{| class="wikitable"
|Tactical Call Sign
|NET Team or Neighborhood Name(s)
|-
|
|
|-
|
|
|-
|
|
|-
|
|
|-
|
|
|-
|
|
|-
|
|
|}
As an alternative you can make a copy and use the Stations Participating log.
 
You may want to add abbreviations for the tactical call signs that you can use in your log entries. For instance, you could record South Heights as “South Heights (SH)” and use SH in the FROM and TO columns of your Form 6.  Note that teams may have shift changes during an exercise or deployment.  If they do, you may need to use multiple rows for a particular team if you include more than the required information. Keep in mind that logging FCC call signs and operator names is not required.
 
During this exercise you will read the table to Tactical Net.  


==== Recommended Check-In Procedure ====
==== Recommended Check-In Procedure ====
Line 135: Line 105:
[If you hear activity, wait for a quiet time or for Tactical Net to ask for additional check-ins]
[If you hear activity, wait for a quiet time or for Tactical Net to ask for additional check-ins]


<Give your region name as your tactical call sign.>
[You] <Give your region name as your tactical call sign.>


[Tactical Net]: <Your tactical call sign> Go ahead
[Tactical Net]: <Your tactical call sign> Go ahead


[You] I have a team roster to report.
[You] I have a team roster to report.
[In the script below several variations are given to show how you can handle cases where a tactical call sign is representing multiple teams or a single team.]


[Tactical Net]: Ready to copy.
[Tactical Net]: Ready to copy.
Line 147: Line 115:
[You] Please copy,  
[You] Please copy,  


<The tactical call sign of your first check in> which represents <team name 2> [long pause while SNC finds that team in their roster]  
[You]<The tactical call sign of your first check in> representing <Team name> Break [long pause while Tactical Net records the information]  
 
and <team name 2>. Break


[Tactical Net]: Continue.
[Tactical Net]: Continue.


[You] <Second tactical call sign> representing <Actual team name which is longer than the tactical call sign>. Break.
[You] <Second tactical call sign> representing <Team name>. Break.


[Tactical Net] Continue.
[Tactical Net] Continue.


[You] <Third tactical call sign> representing <team name which is the same as the tactical  call sign> Break
[You] <Third tactical call sign> representing <Team Name> Break


[Continue as above until the last tactical call sign. For the last one say the following instead of “Break”]
[Continue as above until the last tactical call sign. For the last one say the following instead of “Break”]


End of roster.  How copy?
[You] End of roster.  How copy?


[Tactical Net] I roger your roster.  
[Tactical Net] I roger your roster.  
Line 199: Line 165:
Both formal messages and tactical messages should be triaged by precedence during exercises and deployments.  Unless PBEM specifies otherwise, standard ARRL precedence levels should be used:  
Both formal messages and tactical messages should be triaged by precedence during exercises and deployments.  Unless PBEM specifies otherwise, standard ARRL precedence levels should be used:  


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. 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 “Preparing Your Traffic and Notifying ECC” in Winlink Procedures for SNCs.
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 “Handling Replies to Winlink Formal Traffic” in Winlink Procedures for SNCs.
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]].


=== Closing your Subnet and Checking Out ===
=== Closing your Subnet and Checking Out ===
Retrieved from "https://volunteerpdx.net/index.php/Special:MobileDiff/3397...3824"