Statement of Purpose:
To provide guidance for implementing a standardized file name format when saving digital copies of messages, forms, or other traffic generated by AmRRON station operators.
This standard aids in the following ways:
1.Standardization avoids multiple message naming formats that could lead to confusion, lost message traffic, or duplication of traffic.
2.Helps to keep traffic stored in a chronological order
3.Aids in searching for, and retrieving, previously handled traffic by key search words or phrases, such as traffic handled on a certain day or time of day, a general location, an individual station, etc.
Much of this information will also be contained (and should be reflected) in many of the FLMSG standard forms and AmRRON Custom forms and reports once they are filled out. The file name should contain the DTG (Date/Time Group), the precedence level of the traffic (Routine, Priority, Immediate, etc.) in TRIPLICATE, the state where the station initiating the traffic is located, the callsign suffix (last three characters) of the station generating the traffic, and the sequential number that station has designated identifying the message or traffic, using three digits.
Each item separated by a (-) dash. See Figure 1.
ROUTINE (R): Non-Emergency information, News Reports, Health/Welfare, Administrative, etc.
PRIORITY (P): Non-Emergency but very important and/or time sensitive
IMMEDIATE (I): EMERGENCY TRAFFIC. Danger of loss of life or limb is occurring or is Imminent
FLASH (O): Flash ‘Command & Control’ traffic overrides all other traffic. Is NOT initiated by individual radio operators.
Extreme national security or other strategic threat.
Precedence level indicated 3 TIMES in case portions of the message are garbled, and so that it more easily catches the eye.
In some cases other traffic-generating station indicators may be encountered instead of a callsign suffix:
– State or Regional Level NCS operator or SIGCEN is indicated either by ‘NCSO’ or ‘SIGCEN’
– AmRRON National is indicated by ‘NATL’
Files will (of course) end with the file extension depending on the type, such as a text file (.txt) or an flmsg form (.k2s)
The following is an example of an flmsg file saved in its proper format:
DOWNLOAD THE PDF VERSION OF THIS WHITE PAPER HERE