Anonymous

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

From WikiNET
m
Updated instructions
m (BruceSchafer moved page Voicing a Reply to a NET Form 8 to Voicing a NET Form 8 or its Reply: Just added voicing instructins for the top half)
m (Updated instructions)
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.
# 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".  
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)
# 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"  
(2) Field numbers are '''not''' voiced. Field names '''are''' voiced, but '''not''' punctuation in the field name. Example. "Time One Nine Zero Zero" rather than "Six Date colon One Nine Zero Zero".
# 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.  
 
# 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."  
(3) All digits are individually voiced, e.g. "one five" rather than "fifteen".
# 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.  
 
# 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  
(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.  
# The the proword "Break" is used to indicate the end of the body of the 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.
(4) 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."  
 
(5) 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.  
 
(6) 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  
 
(7) The proword "Break" is used to indicate the end of the body of the reply.


=== Example NET Form 8 with Reply ===
=== Example NET Form 8 with Reply ===