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

From Portland NET Wiki
Created original content for page
 
m Instructions For Voicing a Reply: Changed "Communications" to "Operations"
 
(24 intermediate revisions by the same user not shown)
Line 1: Line 1:
(1) 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.
= Instructions For Voicing a Message =
# 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".
# 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"
# 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."
# 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
# The proword "Break" is used to indicate the end of the body of the message or reply.
= Instructions For Voicing a Reply =
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 Operations Center or from one team to another. 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 originating station, date, time and subject of the original message.
# Wait to be given the go ahead with your reply.
# Read your reply using the appropriate keywords.
# (See the sample script below for an example of this process.)


Note: 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)
= Example NET Form 8 with Reply =
[[File:NET Form 8 Request Reply Example.jpg|1000px]]


(2) Field names are voiced, but not punctuation in the field name.  e.g. "Date Two Two August" rather than "Date colon Two Two August".


(3) All digits are individually voiced, e.g. "one five" rather than "fifteen".
= Script for Voicing the Message Above =


(4) 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.
[Prowords are ''italicized'' below]


(4) Time is local time written with 4 digits using a 24-hour clock and does not need to be preceded by "Figures" when it is part of a time field.
'''Receiving Station'''


(5) Punctuation in the message text 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.
[If receiving station is a net control] Does any station have formal traffic with precedence of EMERGENCY or Priority?


(6) In this script, prowords are red and ITU phonetics are blue with the first letter capitalized. Voiced punctuation in the script is written in lowercase blue, e.g., period, to distinguish punctuation from ITU phonetics.
[OR]


(7) The proword "Break" is used to indicate the end of the body of the reply.
[If the receiving station is another station in the net or subnet] I am ready for your traffic.


(Continued on the next page)
'''Originating Operator'''


Example NET Form 8 with Reply
I have a Priority Net Form 8.


(Script on the next page)
''Over''


Script for Voicing the Reply Above
'''Receiving Operator'''


ARO
''Go ahead'' with your Form 8
 
[OR]
 
Standby.
 
'''Originating Operator''' [when to go ahead]
 
''Please copy.''
 
To Incident Team Leader comma All Initials November Echo Tango  Teams
 
From John Smith comma Planning Officer Originating Station Command Net
 
Subject Priority colon Request for snow coverage
 
Date Five October Two Zero Two Two
 
Time One Nine Zero Zero
 
Message Please provide snow coverage in inches at your staging area period ''Break''
 
Approved by John Smith 
 
Position Planning Officer
 
''End of Message''.  How Copy?
 
'''Receiving Operator'''
 
Roger your NET Form 8.
 
          [OR]
 
Please ''fill between'' [word heard] and [word heard]
 
= Script for Voicing the Reply Above =
[Prowords are ''italicized'' below]
 
'''Replying Operator'''


I have a reply to a priority message.
I have a reply to a priority message.


Over
''Over''


SNC
'''Receiving Operator'''


      Go ahead with the originating station, date, time and subject of the original message.
Go ahead with the originating station, date, time and subject of the original message.


Over
Over


ARO
'''Replying Operator'''


Originating Station Command Net  
Originating Station Command Net  
Line 45: Line 99:
Time One Nine Zero Zero
Time One Nine Zero Zero


Subject Request for snow coverage
Subject Priority Request for snow coverage


Over
''Over''


SNC
'''Receiving Operator'''


  Roger
''Roger''


Standby
''Standby''


[SNC finds original message.]
[Receiving operator finds original message.]


    Please go ahead with your reply.
Please ''go ahead'' with your reply.


ARO
'''Replying Operator'''


Reply Figure Six inches Break
Reply Figure Six inches Break
Line 71: Line 125:
Time One Nine Three Zero
Time One Nine Three Zero


End of Message How Copy?
''End of Message How Copy?''


SNC
'''Receiving Operator'''


Roger your message reply.
''Roger'' your message reply.


                [OR]
          [OR]


  Please fill between [word heard] and [word heard]
Please ''fill between'' [word heard] and [word heard]