Voicing a NET Form 8 or its Reply: Difference between revisions

Jump to navigation Jump to search

Voicing a NET Form 8 or its Reply (view source)

Revision as of 10:47, 22 August 2023

48 bytes added ,  22 August 2023
m
Made additional improvements
m (Made additional improvements)
Line 1: Line 1:
# Field numbers are '''not''' voiced. The first word of each field name is voiced, but '''not''' any punctuation in the field name. Example. Incident Simplex Exercise" rather than "One Incident Name colon Simplex Exercise"  
# Field numbers are '''not''' voiced. The first word of each field name '''is''' voiced, but '''not''' any punctuation in the field name. Example. "Incident Simplex Exercise" rather than "One Incident Name colon Simplex Exercise"
# All digits are individually voiced, e.g. "one five" rather than "fifteen".  
# All digits are individually voiced, e.g. "one five" rather than "fifteen".  
# If no Incident Name is provided on the form, that field is not voiced and the voicing starts with the To field.  
# If no Incident Name is provided on the form, that field is not voiced and the voicing starts with the To field.  
# Originating station is a tactical call sign and not the name of the person identified in the From field of the message.  The ARO may add it to the From field in parentheses preceded by the abbreviation "OS".  e.g. (OS Tactical Net)  The originating station is voiced without the parenthesize and "OS" is voiced as "Originating Station".  Example: "(OS South Heights)" is voiced as "Originating Station South Heights"  
# Originating station is a tactical call sign and not the name of the person identified in the From field of the message.  The ARO may add it to the From field in parentheses preceded by the abbreviation "OS".  e.g. (OS Tactical Net)  The originating station is voiced without the parenthesize and "OS" is voiced as "Originating Station".  Example: "(OS South Heights)" is voiced as "Originating Station South Heights"  
# In the date field the format is nnMMMYYYY and does not need to be preceded by the proword "mixed group figures." The name of the month is voiced, even though the month is written as a 3-letter abbreviation. E.g., November is written "NOV" but voiced "November". The current year is usually assumed. If included, the year is four digits. E.g., 05FEB2020.  
# In the date field the format is nnMMMYYYY and does not need to be preceded by the proword "mixed group figures." The name of the month is voiced, even though the month is written as a 3-letter abbreviation. E.g., November is written "NOV" but voiced "November". The current year is usually assumed. If included, the year should four digits. E.g., 5OCT2022 voiced "Five October Two Zero Two Two".
# Time is local time written with 4 digits using a 24-hour clock with the digits given one at a time and does not need to be preceded by "Figures" when it is part of a time field.  Example "Time One Nine Zero Zero" rather than "Time Figures One Nine Zero Zero" or "Time Nineteen Hundred."  
# Time is local time written with 4 digits using a 24-hour clock with the digits given one at a time and does not need to be preceded by "Figures" when it is part of a time field.  Example "Time One Nine Zero Zero" rather than "Time Figures One Nine Zero Zero" or "Time Nineteen Hundred."  
# Punctuation in the message body is voiced. The decimal and any comma(s) in a number are also voiced. E.g., 32,500.75 would be voiced Figures Three Two comma five zero zero decimal seven five.
# Punctuation in the message body is voiced. The decimal and any commas in a number are also voiced. E.g., 32,500.75 would be voiced "Figures Three Two comma five zero zero decimal seven five"
# Field 8 is voiced as if it were two fields -- the first and last and skipping the second: "Approved by <name provided> Position <Title provided>" as the signature is '''not''' voiced  
# Field 8 is voiced as if it were two fields -- the first and last and skipping the second: "Approved by <name provided> Position <title provided>" as the signature is '''not''' voiced
# The the proword "Break" is used to indicate the end of the body of the reply.
# The proword "Break" is used to indicate the end of the body of the message or reply.
# When you are ready to reply to a message during a simplex exercise, it may be obvious to the net controller which message you are replying to.  During an actual deployment, however, there may be several messages sent to NET teams from the Emergency Coordination Center.  This multiplicity of messages makes it critical that the net controller receiving the reply matches it correctly to the original message.  To help do so, the subnet controller logs the originating station, date, time and subject of each message.  Thus to assist the controller in identifying the message you are replying to you should provide this information.  In a more complex situation the controller may also ask for the destinations of replies and messages.
# When you are ready to reply to a message during an exercise, it may be obvious to the net controller which message you are replying to.  During an actual deployment, however, there may be several messages sent to NET teams from the Emergency Coordination Center.  This multiplicity of messages makes it critical that the net controller receiving the reply matches it correctly to the original message.  To help them do so, the subnet controller logs the originating station, date, time and subject of each message.  Thus to assist the controller in identifying the message you are replying to you should provide that information.  In a more complex situation the controller may also ask for the destinations of messages or replies.


=== Example NET Form 8 with Reply ===
=== Example NET Form 8 with Reply ===
Retrieved from "https://volunteerpdx.net/index.php/Special:MobileDiff/3250"

Navigation menu