| Net reports must be filed by each session NCS and are due in the hands of the Net Manager within 48 hours of the session run. They may be sent via radio, WL2K or internet email. Digital means are preferred for ease of loading into the database. All SAR reports and PSHR reports are due by midnight of the 6th of the following month or they may not be included in Section and ARRL reports. |
| 23 R W3XYZ 24 PODUNK MD OCT 10 |
| W3YVQ |
| = |
| MEPN* | SUN* | OCT* | 10* | 2200Z* |
| QNS/15* | XYZ/NCS | FTQ/ANC | PVO/DTN | KK3F/3RN/WV |
| WK/MDD | QAA/BTN | OR/PKT | DYV | WO3F |
| TNM | GLF/EP | QWO | YVQ | TOM |
| N3ZZZ/JOHN/GARR/M | QTC/5* | QNF/2223Z* | 73 |
| = |
| JOE |
| |
* Required groups in the sequence shown with the list of stations between the QNS/## and QTC/## items. This syntax is required for automated data processing. If any comments are to be added they must follow a 73 at the end of the text. Text groups shown here are separated for clarity. In the emailed text each group would be separated by a single space as in:
23 R W3XYZ 24 PODUNK MD OCT 10
W3YVQ
=
MEPN SUN OCT 10 2200Z
QNS/15 XYZ/NCS FTQ/ANC PVO/DTN KK3F/3RN/WV
WK/MDD QAA/BTN OR/NTSD DYV HAM
TNM GLF/EP QWO YVQ TOM
N3ZZZ/JOHN/GARR/M QTC/5 QNF/2223Z 73
=
JOE
|
| = | (Begin the text with the "=" character on a separate line.) |
| LINE 1: MEPN (day) (mon) (dt) (start time UTC) |
| Group 1 | MEPN must be the 1st group of text. |
| 2 | Day of the week: MON, TUE, WED, THU, FRI, SAT, SUN |
| 3 | Three letter month abbreviation: JAN, APR, JUN, JUL, etc. |
| 4 | Date figure(s), no leading zeros, i.e.: OCT 9 or OCT 10 |
| 5 | Session start time ####Z (4 digits, 24 hour UTC as in 2200Z or 0900Z). |
| LINE 2 begins: QNS/## |
| QNS/### | QNS/### where ## is the total number of stations checked into net, no leading zeros, as in QNS/8 or QNS/12. |
| List of Stations: |
| List of Stations | After the QNS/## enter the list of stations checked into net, call sign or suffix, with appended information, each separated by a space, as noted in the List of Stations section below. |
| Traffic and Closing Time: |
| QTC/## | QTC/## where ## is the total number of messages passed at the direction of the NCS, follwed by number of W, P, or E (emergency) messages handled; as in QTC/10, or QTC/10/2W/3P/1E. |
| QNF/####Z | QNF/####Z where ####Z is the session closing time in 4 digit 24 hour UTC time as in 2223Z or 0923Z. |
| 73 | 73 may optionally be included as the last group before the break. If any comments are to be added they must follow a 73 at the end of the text. |
| = | (End the text with the "=" character on a separate line.) | |
Full call sign or suffix (suffix letters only, no number) may be used, except use the full call sign for conflicting suffix calls such as KK3F and WO3F. Call signs which appear in the latest MEPN QNS list published in the newsletter are in the database enabling the use of the suffix in the reports. Append additional information to each call or suffix as appropriate in the following order:
(Call or suffix)/(Jobs)/(Assignments)/(ERP-Liaisons)/(Name)/(QTH)/(EP)/(M)
|
| Calls, suffixes: | Examples: W3XYZ HAM Y (W3XYZ, W3HAM and KC3Y) If there is ambiguity relative to the net roster using the suffix then use the full call sign. The QNS list is published in the newsletter from time to time. |
| Jobs: | /NCS, /ANC |
| Assignments: |
/WV, /DTN, /DEPN, /3RN, /MDD, /BTN, /MSN, /NTSD,
/WL2K, /EAN, /TCC, /3RNAUX or /MDDAUX, etc. |
| ERP-Liaisons: | /(tactical call sign) for EM EOC's, or
/(tactical call sign+agency) as in:
/ANARARC (for the ANAR ARC),
/AMARS (Army MARS),
/NMARS (Navy-Marine Corps MARS),
/AFMARS (Air Force MARS),
/NWS (NWS office or net), /SKYWARN,
/CGAUX, /CAP, /EPA, /WPA, etc.
Tactical Call Signs are the MDC jurisdiction abbreviations shown in the table below plus agency designator or other Section designator. |
| Name/QTH: | For newcomers (or any call not in the MEPN QNS list) include the
(full call)/(first name)/town or county). No spaces are permitted in the appended information; hence, for a QTH of Bel Air for a newcomer the two names would be joined as in W3ZZZ/JOHN/BELAIR to avoid creating a separate group. |
| EP: | Station operating under emergency power, /EP, generator or battery (not being charged from the mains), solar, etc. |
| M, P: | /M, mobile; /P, portable. | |
| JURISDICTION TACTICAL CALL SIGNS, MDC |
|---|
| CALL | JURISDICTION | CALL | JURISDICTION | CALL | JURISDICTION |
| ALLE | Allegany | DENT | Denton | OC | Ocean City |
| ANAR | Anne Arundel | DORC | Dorchester | PRGE | Prince George's |
| BACI | Baltimore City | FRED | Frederick | QA | Queen Anne's |
| BACO | Baltimore Co. | GARR | Garrett | SOME | Somerset |
| CALV | Calvert | HARF | Harford | STMA | St. Mary's |
| CARO | Caroline | HOWA | Howard | TALB | Talbot |
| CARR | Carroll | KENT | Kent | WASH | Washington |
| CECI | Cecil | MEMA | MD EM Agency | WICO | Wicomico |
| CHAS | Charles | MONT | Montgomery | WORC | Worcester |
| DC | DC | NIH | National
Institutes Of
Health | | |
|
The above appended duty tags inform the NM and Section staff which stations represented functions during the net session in support of the MDC ERP (MDC Emergency Response Plan). Certain other functions will be performed, some the responsibility of the MEPN to assign, others assigned elsewhere in the Section system. Examples:
- When two or more of the Section's nets (MEPN, MDD, MSN and BTN) are operating simultaneously there are "roving liaisons" required. These stations carry traffic back and forth between the nets. One or more stations may be assigned as a roving liaison to all the active nets, reported as in (call sign)/MDD/MSN). It is not usually required to note the jurisdiction of these stations unless they have multiple duties. They are simply net liaisons and are in addition to regular liaisons in the daily schedule.
- When the ERP "Region" VHF nets (CRN, WRN, ERN) are active, liaisons are expected from each to the HF nets. Those coming to MEPN would append a duty tag as in (call sign)/CRN, or (call sign)/WRN, etc. It is not usually required to note the jurisdiction of these stations unless they have multiple duties. They are simply net liaisons.
|
(ARES® is a registered trademark of the ARRL, Inc., Newington, CT.)
Return to top of this document
|
