Voicing a NET Form 8 or its Reply: Difference between revisions
Jump to navigation
Jump to search
BruceSchafer (talk | contribs) m (→Script for Voicing the Reply Above: Minor improvement) |
BruceSchafer (talk | contribs) (Adding additional subhead) |
||
| Line 1: | Line 1: | ||
= Instructions = | |||
# 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". | ||
| Line 10: | Line 11: | ||
# 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. | # 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 = | |||
[[File:NET Form 8 Request Reply Example.jpg|1000px]] | [[File:NET Form 8 Request Reply Example.jpg|1000px]] | ||
= Script for Voicing the Message Above = | |||
[Prowords are ''italicized'' below] | [Prowords are ''italicized'' below] | ||
'''Originating Operator''' | '''Originating Operator''' | ||
| Line 56: | Line 58: | ||
Please ''fill between'' [word heard] and [word heard] | Please ''fill between'' [word heard] and [word heard] | ||
= Script for Voicing the Reply Above = | |||
[Prowords are ''italicized'' below] | |||
'''Replying Operator''' | '''Replying Operator''' | ||
Revision as of 10:03, 22 August 2023
Instructions
- 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.
- 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
Script for Voicing the Message Above
[Prowords are italicized below]
Originating Operator
I have a Priority Net Form 8.
Over
Receiving Operator
Go ahead with your Form 8
Originating Operator
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.
Over
Receiving Operator
Go ahead with the originating station, date, time and subject of the original message.
Over
Replying Operator
Originating Station Command Net
Date Five October
Time One Nine Zero Zero
Subject Priority Request for snow coverage
Over
Receiving Operator
Roger
Standby
[Receiving operator finds original message.]
Please go ahead with your reply.
Replying Operator
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?
Receiving Operator
Roger your message reply.
[OR]
Please fill between [word heard] and [word heard]