542
edits
Voice Procedures for Subnet Control Operators: Difference between revisions
Jump to navigation
Jump to search
Voice Procedures for Subnet Control Operators (view source)
Revision as of 15:47, 3 October 2023
, 3 October 2023→Handling NET Form 8 Traffic from NET Teams Including Triage: Added links to further information
BruceSchafer (talk | contribs) (→Handling NET Form 8 Traffic from NET Teams Including Triage: Added internal link) |
BruceSchafer (talk | contribs) (→Handling NET Form 8 Traffic from NET Teams Including Triage: Added links to further information) |
||
| Line 165: | 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 | 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 ECCPreparing 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]]. | ||