Voicing a NET Form 8 or its Reply: Difference between revisions
From Portland NET Wiki
BruceSchafer (talk | contribs) m →Script for Voicing the Reply Above: Minor improvement |
BruceSchafer (talk | contribs) m →Instructions For Voicing a Reply: Changed "Communications" to "Operations" |
||
| (11 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
= 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" | # 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 8: | Line 9: | ||
# 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 proword "Break" is used to indicate the end of the body of the message or reply. | # 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.) | |||
= 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] | ||
'''Receiving Station''' | |||
[If receiving station is a net control] Does any station have formal traffic with precedence of EMERGENCY or Priority? | |||
[OR] | |||
[If the receiving station is another station in the net or subnet] I am ready for your traffic. | |||
'''Originating Operator''' | '''Originating Operator''' | ||
| Line 27: | Line 42: | ||
''Go ahead'' with your Form 8 | ''Go ahead'' with your Form 8 | ||
'''Originating Operator''' | [OR] | ||
Standby. | |||
'''Originating Operator''' [when to go ahead] | |||
''Please copy.'' | ''Please copy.'' | ||
| Line 56: | Line 75: | ||
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''' | ||
