Voicing a NET Form 8 or its Reply: Difference between revisions
BruceSchafer (talk | contribs) m (Improved guidance on voicing Form 8) |
BruceSchafer (talk | contribs) (Added started of voicing instructions for top of form) |
||
Line 19: | Line 19: | ||
=== Example NET Form 8 with Reply === | === Example NET Form 8 with Reply === | ||
[[File:NET Form 8 Request Reply Example.jpg|1000px]] | [[File:NET Form 8 Request Reply Example.jpg|1000px]] | ||
=== Script for Voicing the Message Above === | |||
'''ARO''' | |||
I have a NET Form 8 Priority message. | |||
=== Script for Voicing the Reply Above === | === Script for Voicing the Reply Above === |
Revision as of 16:57, 21 August 2023
(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.
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)
(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".
(3) All digits are individually voiced, e.g. "one five" rather than "fifteen".
(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.
(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 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.
(6) In this script below, 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.
(7) The proword "Break" is used to indicate the end of the body of the reply.
Example NET Form 8 with Reply
Script for Voicing the Message Above
ARO
I have a NET Form 8 Priority message.
Script for Voicing the Reply Above
ARO
I have a reply to a priority message.
Over
SNC
Go ahead with the originating station, date, time and subject of the original message.
Over
ARO
Originating Station Command Net
Date Five October
Time One Nine Zero Zero
Subject Request for snow coverage
Over
SNC
Roger
Standby
[SNC finds original message.]
Please go ahead with your reply.
ARO
Reply Figure Six inches Break
Replied by Jane Smith
Position: Initials India Tango Lima South Heights
Date Five October
Time One Nine Three Zero
End of Message How Copy?
SNC
Roger your message reply.
[OR]
Please fill between [word heard] and [word heard]