View source for Winlink Procedures for Subnet Controllers

=== Handling Winlink Formal Traffic from ECC ===
During the exercise you may receive formal messages from ECC in the form of Winlink messages with attached ICS 213s.  Normally, Winlink will automatically open a web browser window or tab to display the message in a format that looks much like a printed ICS 213.  If it doesn’t and you receive a message that has a subject starting with “213-”, you should also see a paperclip icon  in the left-most field of the summary line in your Inbox.  If you click on the paperclip icon, Winlink should open the message in a browser window.  When you are ready to enter a reply to the message, you should use the steps described in Instructions for sending a REPLY to a ICS213.  Note, however, you should not have more than one reply open at once as it's easy to confuse Winlink about which message is being replied to and it may lose a reply if you have more than one open at a time.

When you receive a formal message from ECC, please route it to the appropriate teams by contacting the corresponding AROs and reading the message to them as a NET Form 8. 

=== Handling Replies to Winlink Formal Traffic ===
When an ARO informs you that they have a reply to such a message, ask for its precedence if you don’t already have it. If the precedence is equal to or greater than  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.
* Assuming you received the original message by Winlink use these substeps. Otherwise see Handling Replies to ECC Traffic Originally Received by Voice.
** Find the original message in your Winlink Inbox or your Read Items folder.
** Follow steps 2 through 5 of [[#Instructions for sending a REPLY to an ICS213|Instructions for Sending a Reply to an ICS213.]] As part of step 5, type the reply directly into the Winlink template while you have the ARO read it to you.  Ask for any fills you need.  Note: Winlink Express will allow you to create multiple replies to the same ICS 213 message. You will find this useful as you will probably have more than one team reply to each message from ECC. Do not, however, have more than one reply open at a time as this will confuse Winlink Express.
** Before you post the reply in your Outbox or your Draft Folder, change the From address from your FCC call sign to your regional Winlink tactical address by clicking on the down arrowhead next to your call sign.

* You will notice that Winlink will automatically fill in the To field of the Winlink message (not the attached ICS 213) with the address in the From field of the original Winlink message, whether it was an FCC call sign or a Winlink tactical address.
* Before you post the reply in your Outbox or your Draft Folder, change the From address from your FCC call sign to your regional Winlink tactical address by clicking on the down arrowhead next to your call sign.
* Depending on the precedence of the reply relative to other traffic, post the reply to your Outbox or save it in your Draft folder and move it to your Outbox later. 

When you are ready to transmit the replies in your Outbox to the ECC, see [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|Transmitting and Receiving Traffic Using a Gateway]].

=== Special Procedure for Handling Multiple Replies to a Winlink Message from the Emergency Coordination Center ===
If you have several teams checked into your subnet and you have read their AROs a Winlink message from the ECC, you should consider whether you will are likely to receive several replies in a row to this message.  If so, it may be more efficient to use one ICS 213 reply than to use several separate replies.  You will find a procedure of accomplishing this below. You should only use this procedure when the following three conditions are true:

# The message from ECC did not have a precedence of Emergency.
# It is reasonable to expect that more than one ARO will have a reply ready in a short amount time. (The most likely situation when this would be true is when the AROs are in a position of answering the message themselves rather than routing the message to their Incident Team Leader. For example, a simplex request asking for the weather conditions in the neighborhoods.)
# You are not handling replies to other messages at the same time. 

If any of the the above conditions is not true, use separate ICS 213 replies for each reply as described in [[Winlink Procedures for Subnet Controllers#Handling Replies to Winlink Formal Traffic|Handling Replies to Winlink Formal Traffic]] above.  

If all three conditions above are true, you may want to use the following steps to combine multiple replies into one ICS 213 reply.

*Find the original message in your Winlink Inbox or your Read Items folder.
* Follow steps 2 through 5 of [[#Instructions for sending a REPLY to an ICS213|Instructions for Sending a Reply to an ICS213.]] As part of step 5, type the name of the team replying to message followed by a colon. Then type the reply directly into the Winlink template while you have the ARO read it to you. When the ARO reads field 10 (the name and position of the person replying), add that information after the reply rather than in field 10 of your reply template. 
* Ask for any fills you need.
* Repeat step 5 for reach team's reply.
* Once you have all the replies or you expect some time will elapse before you get any more replies, fill in Field 10 with your name and position and click on Submit.
* Before you post the reply in your Outbox or your Draft Folder, change the From address from your FCC call sign to your regional Winlink tactical address by clicking on the down arrowhead next to your call sign
* Depending on the precedence of the reply relative to other traffic, post the reply to your Outbox or save it in your Draft folder and move it to your Outbox later.
When you are ready to transmit the replies in your Outbox to the ECC, see [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|Transmitting and Receiving Traffic Using a Gateway]].

=== Handling Replies to ECC Traffic Originally Received by Voice ===

# Use Winlink to create a new message.  The reason we’re not asking you to put the replies from the teams in the reply section of a Winlink ICS 213 in this case is that Winlink Express doesn’t allow you to fill in the reply section unless you previously received the ICS 213 by Winlink.  In this case you received the original message by voice.
# If the reply is to a message that came from the ECC, put the appropriate tactical address or W7ECC in the To field of the Winlink message. (You can leave the Subject field blank because the next step will fill it in automatically.) 
# Then select the ICS 213 template.  See Checklists for Winlink Tasks for details.  
## In the To field of the 213, put the person that sent the original message. 
## In the From field put your Simplex Region name followed by the word “Region”.  
## In the Subject field of the 213 template, Put the word “Reply” followed by the subject of the original message.  
## In the Message body of the 213, put the name of the team providing the reply followed by a colon and the reply.  If you receive multiple replies to the same message in rapid succession, add each to the message body field of the same ICS 213, labeling each with the corresponding team name.  Otherwise, submit the message and post it to your Outbox. 

Note: Avoid having more than one Winlink template at once. If you open another one, be sure and Save or Submit the first one before opening another.

# When you are ready to transmit the replies in your Outbox to the ECC, see Transmitting and Receiving Traffic Using a Gateway.

=== Addressing Winlink Messages ===
Winlink messages can be addressed to FCC call signs as long as the person associated with that call sign has registered with Winlink.org. For NET exercises, I recommend that you use tactical addresses instead.  Tactical addresses have several advantages as they can be associated with particular functions like ICS roles at the ECC and regional subnets. When you start a new message, Winlink Express will automatically fill in your Winlink address in the From field.  Notice, that next to your call sign is a down arrow head.  If you click on it, Winlink will list any tactical addresses that you have enabled.  If you click on a tactical address it will replace your FCC call sign in the From field.

==== Tactical Addresses for ICS Roles at the ECC ====
During an actual disaster or a major exercise, Portland Emergency Coordination Center’s situation room will be staffed by a wide variety of people serving in various Incident Command System roles like Safety Officer and Planning Section Chief.  The ECC will also have shift changes where the person serving in a particular role will leave and someone else will take their place. We can use Winlink tactical addresses in the From field of Winlink messages (not the From field of the ICS 213) to provide a way of tracking which role originated the message so when replies come back from NET teams they can be grouped using these addresses and routed to the right desk in the ECC situation room.  Here are the tactical addresses we have established so far:

* Message Center: PDXECCMSGC-1
* Planning Section Chief: PDXECCPLAN-1
* Safety Officer: PDXECCSFTY-1

Note: When the ECC radio room uses one of these addresses in the From field of a Winlink message, when you use Winlink to reply to the message the tactical address will automatically be placed in the To field of your reply. 

==== Tactical Addresses for Regional Subnet Control Operators. ====
During an exercise or deployment, there may be shift changes.  If a Winlink message is addressed to the FCC call sign of a particular subnet control operator and that operator completes a shift before receiving it, the message will not be received by the next operator for the same region. By using a tactical address for a particular subnet, the messages will be available to the next controller who enables that address on their copy of Winlink Express using the password associated with the address.  Here is a list of the tactical addresses for the NET simplex regions:

* Alameda North: PDXNETAN-1
* Alameda South: PDXNETAS-2
* Columbia: PDXNETCO-1
* New Northeast: PDXNETNN-1
* Outer East: PDXNETOE-1
* River North: PDXNETRN-1
* River South: PDXNETRS-1
* Southeast: PDXNETSE-1
* Westside: PDXNETWE-1

=== Enabling and Disabling a Tactical Address ===
To receive messages addressed to the tactical address for your region you will need to enable that address.  Before you enable the address you will need to set it up on your copy of Winlink Express. To do so, use the steps described in Using Winlink Tactical Addresses.  Assuming the address is set up, you can enable it by returning to the Winlink Express Setup dialog, selecting the address, selecting "Edit Entry", and check "Enabled", them "Save", then "Update'.

At the end of an exercise or deployment or when a shift change means that someone else will be taking over your role as subnet controller, you should disable the tactical address for your region.  To do so use the Winlink Express Setup dialog to select the tactical address, select “Edit Entry” and uncheck “Enabled”; then select “Save” and select "Update."

=== Preparing Your Traffic and Notifying ECC ===
If you have Emergency or Priority messages, prepare these messages by creating Winlink messages using the ICS 213 template. 

Note: If the message you are transcribing does not have approval information, put “...” in the corresponding fields of the Winlink Form so it allows you to submit it. 

After you have filled out the template, clicked on Submit and closed the browser window, you will see the content of the 213 in the body of a Winlink message.  Please

* Update the From field by clicking on the the "V" shape next to your FCC call sign and selecting your region's tactical address. If no tactical address is shown, see the section above regarding enabling a tactical address. 
* Update the To field of the Winlink with one of the ECC tactical addresses.  When in doubt use PDXECCMSGC-1.

If you have Emergency messages you should post them to your Winlink Outbox and then contact Tactical Net on MC-8 informing it of these messages before taking Priority messages. Tactical Net may

* take your Emergency messages by voice;
* give you immediate access to the Winlink gateway to transmit your Emergency traffic; or
* tell you that Command Net will call you back on your frequency to either take your message by voice or give you time on the Winlink gateway to transmit them by Winlink. 

Note: If you transmit an Emergency message by voice, you should delete it from your Winlink Outbox so you don’t accidentally send a duplicate copy.  If you are asked to use a Winlink gateway to transmit your Emergency messages, you should temporarily move any Priority messages already in your Outbox to another folder and then move them back to your Outbox box when you have been given a gateway to send them.

If you have previously posted Emergency messages in your Outbox that have not yet been transmitted and you have just transcribed a new Priority message, it is best not to put it directly in your Outbox as you shouldn’t tie up the gateway transmitting messages of two or more precedence levels. Instead of posting the lower precedence message directly to your Outbox, click on Save in Drafts. You can move the messages in your Draft folder to your Outbox after you have transmitted your higher priority messages. Alternatively, you can copy messages in your Draft folder to personal folders named “Priority”, “HealthWelfare” and “Routine” and later copy messages of a particular precedence to your Outbox.

If you have Priority messages and you have already handled any Emergency messages, you should post your Priority messages to your Winlink Outbox or copy any Priority messages you have previously saved in other folders to your Outbox and then follow the instructions in Transmitting and Receiving Traffic Using a Gateway.

If you have Health & Welfare or Routine messages you can prepare them in the same way as described above, but do not put them in your Winlink Outbox until ECC has told you that it is taking messages at those precedence. Instead select “Save in Drafts” and wait until it is time to transmit them to move them to your Outbox.

=== Transmitting and Receiving Traffic Using a Gateway ===
After listening to the gateway frequency until it appears to no longer be busy, open and start a Packet Winlink or VARA FM Winlink session. If the exercise instructions indicate that a pair of experimental gateways have been set up at Portland Emergency Coordination Center, use one of the following gateways. Otherwise choose any gateway after asking Winlink Express to update its table of gateways.  See “Steps for Updating a Table of Available Gateways” in Checklists for Winlink Tasks.
{| class="wikitable"
|Function
|Name
|Frequency (MHz)
|-
|Experimental Packet Gateway
|KI7QIB-12
|145.010 (use VFO mode or channel 488 in the MCARES 2023 Standard Template)
|-
|Experimental VARA Gateway
|KI7QIB-12
|145.010 (use VFO mode or channel 488 in the MCARES 2023 Standard Template)
|}
When you access a gateway you may receive a warning message "The server you are connected to does not currently have an Internet connection.  Do you want to connect to this server?" This will occur if there is an Internet outage or we are simulating one.  Please confirm that you want to proceed.

Try once or twice to send your message and then stop using the gateway regardless of whether you succeeded so they can be allocated to another subnet control operator.

If you don’t succeed in using one of the experimental gateways, try these alternatives and log which alternative you end up using: 

# Contact Tactical Net and request voice transmission if you have messages with a precedence Emergency.
# Use another gateway if you are relatively certain that the gateways can access the Internet to exchange mail with the Common Message Servers.  
# If you have Internet access, use Telnet Winlink.
# Transmit by regular email.  For instance, PDXECCMSGC-1@winlink.org.  Put the following at the begging of the subject to facilitate obtaining “white list” status for your message: //WL2K
# Hand deliver if that’s possible.

After successfully contacting a gateway, check your Inbox for new messages including messages from ECC and respond accordingly.  Use the precedence of such messages to determine when you will forward them to the intended team or person.  When voicing a message add “This is an Exercise.” to the beginning of the body of each message unless such words are already included.  If you receive a message that it is a reply to a previous message, inform the associated ARO that it is a reply and give the subject, date and time of the original message before reading the reply so the ARO can record the reply in the reply section of the original Form 8.

=== Instructions for sending a REPLY to an ICS213 ===
1. Close the open browser Window to return to Winlink Express.

2. Back in Winlink Express, Double CLICK on the the Message line for the 213.

[[File:Selecting Message.png]]

3. This will open up the plain text version of the message.

4. Now click on the REPLY menu item.

[[File:Selecting Reply.png]]

The Reply to message template will open up in the browser. 

5. Now type in the response and when done click SUBMIT.
=== Instructions for Generating an ICS 309 ===
After an exercise or at the end of a deployment shift you should generate an ICS 309 using Winlink Express. This report will list all traffic you have sent and received using Winlink Express. See [[Checklists for_Winlink Tasks#Steps for Generating an ICS-309|Steps for Generating an ICS 309]]. Any Winlink traffic listed on the resulting ICS 309 does not need to be listed on a NET Form 8. You should still use NET Form 8 or a regular ICS 309 to list traffic you sent or received by voice, however.