Subnet Control Operator Standard Operating Procedure: Difference between revisions

From Portland NET Wiki
← Older edit
VisualWikitext
Added sub-precedence to Priority messages
m Updated cross reference
 
(4 intermediate revisions by the same user not shown)
Line 13: Line 13:
* Return to your regional subnet frequency and announce your return.
* Return to your regional subnet frequency and announce your return.
* Handle message traffic based on [[Message Precedence|precedence]].  If you receive a surge of Priority messages use the following sub-precedence:
* Handle message traffic based on [[Message Precedence|precedence]].  If you receive a surge of Priority messages use the following sub-precedence:
**# EOC traffic to teams
# EOC traffic to teams
**# Teams' replies to EOC
# Teams' replies to EOC
**# Team to Team traffic
# Team to Team traffic
**# Team to EOC traffic
# Team to EOC traffic
* Log voice messages you receive on your Form 6. See [[Logging Procedures for Subnet Control Operators#Instructions for Using a NET Form 6 (ICS 309) for Logging NET Form 8s or ICS Form 213s|Instructions for Using a NET Form 6 for Logging NET Form 8s]].
* Log voice messages you receive on your Form 6. See [[Logging Procedures for Subnet Control Operators#Instructions for Using a NET Form 6 (ICS 309) for Logging NET Form 8s or ICS Form 213s|Instructions for Using a NET Form 6 for Logging NET Form 8s]].
* If Resource Net or Command Net has given you a time to check into Command Net for an update, ''transition to MC-9 at that time'' and wait for instructions.
* If Resource Net or Command Net has given you a time to check into Command Net for an update, ''transition to MC-9 at that time'' and wait for instructions.
Line 31: Line 31:
* There is a chance that Command Net will give you a reply to an earlier message. If you receive such a reply, handle it based on its precedence and when you contact the intended team’s ARO, inform the ARO that it is a reply before reading it so the ARO can record the reply in the reply section of the original Form 8.  
* There is a chance that Command Net will give you a reply to an earlier message. If you receive such a reply, handle it based on its precedence and when you contact the intended team’s ARO, inform the ARO that it is a reply before reading it so the ARO can record the reply in the reply section of the original Form 8.  


* Ask the stations on your frequency if they have any traffic for EOC or replies to any previous requests from EOC. See [[Voice Procedures for Subnet Control Operators#Handling NET Form 8 Traffic from NET Teams Including Triage|Handling NET Form 8 Traffic from NET Teams Including Triage]]. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]].  
* ''Handling Formal Traffic to EOC.'' Ask the stations checked into your subnet if they have any traffic for the EOC or replies to any previous requests from EOC. See [[Voice Procedures for Subnet Control Operators#Handling NET Form 8 Traffic from NET Teams Including Triage|Handling NET Form 8 Traffic from NET Teams Including Triage]]. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]].  
** ''Handling Formal Traffic to EOC.''  If a station has a new message, ask for its precedence if you don’t already have it. Ask other stations whether they have any traffic of higher precedence. Use Winlink to create a new message and then select an ICS213 template. See [[Checklists for Winlink Tasks#Steps for Creating an ICS 213 for Transmission|''Checklists for Winlink Features'']] for details. Ask the first station with the highest precedence traffic to voice the message while you enter it directly into the Winlink ICS213 template. ''If you are concerned that operators will voice their messages faster than you can type into the template, consider telling them to say “Break” at the end of each field and wait for you to say “Continue” before proceeding to the next field.'' After you have clicked on Submit and returned to Winlink, change the From field of the message to your region’s tactical call sign by clicking on your FCC call sign to get a drop-down menu that should include your tactical address.  Change the To field to the tactical address that best matches the To field of the NET Form 8 / ICS 213.  See [[Winlink Procedures for Subnet Controllers#Addressing Winlink Messages|Addressing Winlink Messages]].
** If a station has a new message, ask for its precedence if you don’t already have it. Ask other stations whether they have any traffic of higher precedence.
** ''Handling Replies to Formal Traffic from EOC.''  If a station has a reply, ask for its precedence if you don’t already have it. If the precedence is equal or greater than to the traffic you are currently handling,  
** If the message has a precedence of ''Emergency'',
*** Ask the ARO for the subject and time of the message to which they are replying.  
*** Transcribe the message onto a NET Form 8 or an ICS Form 213.
*** Find the original message in your log.
*** Ask for any fills for the message you just received and update your transcription with the additional information.
*** If you received the original message by Winlink, see [[Winlink Procedures for Subnet Controllers#Handling Replies to Winlink Formal Traffic|Handling Replies to Winlink Formal Traffic]].
*** [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appoint a temporary SNC]].
*** If you received the original message by voice, see [[Winlink Procedures for Subnet Controllers#Handling Replies to EOC Traffic Originally Received by Voice|Handling Replies to EOC Traffic Originally Received by Voice]].
*** Contact Tactical Net on Simplex MC-8 (147.580 MHz) informing it that you have Emergency Traffic.
*** Ask your stations whether they have any more traffic for EOC. If they do, ask them for the precedence of the traffic.  If it is the same or higher precedence as the traffic you just transcribed, ask them to go ahead by returning to step a above.  If it is lower in precedence proceed to step d below.
*** Tactical Net will (a) take your message by voice; (b) tell you that Command Net (MC-9, 146.460 MHz) will call you back on your frequency; or (c) ask you to transmit your message using Winlink. (See steps for non-Emergency messages below.)
*** Note: If a real emergency occurs during an exercise, someone should call 911 and the real emergency should take precedence over all other traffic.  
*** Log the message that your transcribed and then read to the EOC as a pair of lines on your NET Form 6.
** If the message ''does not'' have a precedence of Emergency,
*** Use Winlink to create a new message and then select an ICS213 template. See [[Checklists for Winlink Tasks]] details.  
*** Ask the first station with the highest precedence traffic to voice the message while you enter it directly into the Winlink ICS213 template.  
*** If you are concerned that operators will voice their messages faster than you can type into the template, consider telling them to say “Break” at the end of each field and wait for you.
*** Ask for any fills for the message you just received and update your transcription with the additional information.
*** After you have clicked on Submit and returned to Winlink, change the From field of the message to your region’s tactical call sign by clicking on down arrowhead next to your FCC call sign to get a drop-down menu that should include your region's tactical address.  See [[Winlink Procedures for Subnet Controllers#Addressing Winlink Messages|Addressing Winlink Messages]].
*** Set the To field in the main Winlink message to W7ECC.
*** Log the message you transcribed on your NET From 6.  You can rely on Winlink to create a log of the messages it sends when you open and start a session later. See [[Checklists for Winlink Tasks#Steps for Generating an ICS-309|Steps for Generating an ICS-309]].
* ''Handling Replies to Formal Traffic from EOC.''  If a station has a reply, ask for its precedence if you don’t already have it. If the precedence is equal or greater than to the traffic you are currently handling,  
** Ask the ARO for the subject and time of the message to which they are replying.  
** Find the original message in your log.
** If you received the original message by Winlink, see [[Winlink Procedures for Subnet Controllers#Handling Replies to Winlink Formal Traffic|Handling Replies to Winlink Formal Traffic]].
** If you received the original message by voice, see [[Winlink Procedures for Subnet Controllers#Handling Replies to EOC Traffic Originally Received by Voice|Handling Replies to EOC Traffic Originally Received by Voice]].
** Ask your stations whether they have any more traffic for EOC. If they do, ask them for the precedence of the traffic.  If it is the same or higher precedence as the traffic you just transcribed, ask them to go ahead by returning to step a above.  If it is lower in precedence proceed to step d below.
* When you have transcribed the available traffic at a particular precedence level,  
* When you have transcribed the available traffic at a particular precedence level,  
** [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appoint a temporary SNC]].
** [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appoint a temporary SNC]].
** Change frequency to the frequency of the experimental gateway.  If the frequency is not in use, use Winlink Express to open a Packet or VARA session to send and receive messages. (VARA is preferred because it will take less time and allow the gateway to become available sooner to the next operator.)   
** Change frequency to the frequency of the [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|experimental gateway]]. If the frequency is not in use, use Winlink Express to open a Packet or Vara session to send and receive messages. (Vara is preferred because it will take less time and allow the gateway to become available sooner to the next operator.)  If the experimental gateway does not appear to operational see [[Winlink Procedures for Subnet Controllers#What To Do If the EOC Gateway Appears To Be Unavailable.|What To Do If the EOC Gateway Appears To Be Unavailable]].
** '''Exception:''' If you have Emergency traffic, you may contact Tactical Net informing it that you have Emergency Traffic. Tactical Net will (a) take your message by voice; (b) tell you that Command Net will call you back on your frequency; or (c) ask you to transmit your message using Winlink.  '''Note''': If a real emergency occurs during an exercise, someone should call 911 and the real emergency should take precedence over all other traffic.
** '''Exception:''' If you have Emergency traffic -- as described earlier -- you may contact Tactical Net informing it that you have Emergency traffic.
* [[Voice Procedures for Subnet Control Operators#Facilitating Communication Between Teams|Facilitate communication between teams]] while keeping in mind precedence. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]].
* [[Voice Procedures for Subnet Control Operators#Facilitating Communication Between Teams|Facilitate communication between teams]] while keeping in mind precedence. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]].
* Repeat the above steps starting at step 6. (It may seem unnecessary to repeat Step 6 and 7, but during real deployments AROs may become available over an extended period of time and during an exercise there is always a chance that some will arrive late.)
* Repeat the above steps starting at step 6. (It may seem unnecessary to repeat Step 6 and 7, but during real deployments AROs may become available over an extended period of time and during an exercise there is always a chance that some will arrive late.)
Retrieved from "https://volunteerpdx.net/index.php/Subnet_Control_Operator_Standard_Operating_Procedure"