Voice Procedures for Subnet Control Operators: Difference between revisions

From Portland NET Wiki
m Using Voice to Transmit a Roster to the Portland EOC: Added a new subhead and moved two existing ones under it
 
(12 intermediate revisions by the same user not shown)
Line 75: Line 75:
I. I will now read the roster of stations again.  This time, when I read your tactical call sign, please respond by saying “I can hear” followed by the tactical calls of the stations that you can hear fairly well including Net Control. Then end by saying “This is” followed by your own tactical call sign, your FCC call sign and the proword “Out”.  I will acknowledge each response. If any station hears a response that I did not acknowledge please give the proword “Relay.”
I. I will now read the roster of stations again.  This time, when I read your tactical call sign, please respond by saying “I can hear” followed by the tactical calls of the stations that you can hear fairly well including Net Control. Then end by saying “This is” followed by your own tactical call sign, your FCC call sign and the proword “Out”.  I will acknowledge each response. If any station hears a response that I did not acknowledge please give the proword “Relay.”


[Read list of tactical call signs, pausing for each station to reply with the list of tactical call signs they can hear followed by their own tactical and FCC call signs. Confirm that you have heard by saying “Thank you <tactical call sign>”.
[Read list of tactical call signs, pausing for each station to reply with the list of tactical call signs they can hear followed by their own tactical and FCC call sign.  Record their report in one or more rows of a copy of [https://docs.google.com/document/d/1mNd2me-VK364JbsJBel-n4TWf2RZ30CpkOSQkE5Ixlo/edit?usp=sharing this Station Signal Reports form]. Confirm that you have heard by saying “Thank you <tactical call sign>”].


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 [[Subnet Control Operator Standard Operating Procedure]] and proceed with Step 7.


====== 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 ======
Line 95: Line 95:


=== Transmitting a Roster to the Portland EOC ===
=== Transmitting a Roster to the Portland EOC ===
There are two procedures for reporting your roster of teams checked into your regional subnet to the EOC. 
# [[Voice Procedures for Subnet Control Operators#Using Voice to Transmit a Roster to the Portland EOC|Reporting by Voice]]
# [[Winlink Procedures for Subnet Controllers#Using the Winlink Check-in Form to Report a Roster to the Portland EOC|Reporting by Winlink]].
Command Net should inform you which of these procedures you should use.


==== Using Voice to Transmit a Roster to the Portland EOC ====
==== Using Voice to Transmit a Roster to the Portland EOC ====
Line 142: Line 148:


[Return to your subnet frequency.]
[Return to your subnet frequency.]
==== Using the Winlink Check-in Form to Report a Roster to the Portland EOC ====
[Rough draft. This section will be completed by May 18, 2026]
Winlink includes a template called Check In.  This is a very general form that allows operators to use Winlink to check in during a drill, exercise, or deployment.  We sometimes ask subnet control operators to use this form to report the roster of NET teams that have checked into their regional subnet. 
* Finding the check-in template
* Filling in the basic information
* Providing the subnet roster in the Comments field.
* Submitting the form
* Placing the message in the Outbox
* Starting a Winlink session


=== Handling Traffic from Emergency Operations Center to NET Teams ===
=== Handling Traffic from Emergency Operations Center to NET Teams ===
Line 186: Line 180:


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]].
=== Closing your Subnet and Checking Out ===
At the end of an exercise or deployment you should close your subnet. One method for doing so is to call the role of tactical call signs and expect each station to respond with <FCC call sign> operating as <tactical call sign> Clear.  You should then close the net by saying “This is <FCC call sign> closing this <regional name> Region Subnet Clear at <nowiki><time> local time.”</nowiki>
You should then transition to Tactical Net and check out.


=== Transferring Control to a New Subnet Controller ===
=== Transferring Control to a New Subnet Controller ===
Line 198: Line 187:


Like all other events, the change of control operator should be logged with the same information as you announced over the air.
Like all other events, the change of control operator should be logged with the same information as you announced over the air.
You should then transition to Command Net and inform them that you have transferred control of your subnet and check out.
=== Closing your Subnet and Checking Out ===
At the end of an exercise or deployment you should close your subnet. One method for doing so is to call the role of tactical call signs and expect each station to respond with <FCC call sign> operating as <tactical call sign> Clear.  You should then close the net by saying “This is <FCC call sign> closing this <regional name> Region Subnet Clear at <nowiki><time> local time.”</nowiki>
You should then transition to Command Net and check out.


=== Facilitating Communication Between Teams ===
=== Facilitating Communication Between Teams ===