MEPN	MON		TUE	WED	THU	FRI	SAT	SUN
NCS	open		W3YVQ	WB3FTQ	KB3LNM	NI2W	NI2W	open
ANCS	open		WB3FTQ	open	WB3FTQ	open	open	open
WVA¹	K3EE		K3EE	K3EE	K3EE	K3EE	K3EE	K3EE
DE²	WA3QPX		WA3QPX	WA3QPX	WA3QPX	WA3QPX	WA3QPX	WA3QPX¹⁰
3RN³	open		KK3F	open	open	open	open	open
MDD⁴	open		KK3F	open	open	W3YVQ	open	open
BTN⁵	open		open	open	open	W3YVQ	open	open
DRS⁶	WB3FTQ		W4OTN	WB3FTQ	WB3FTQ	WB3FTQ	WB3FTQ	NF8I
WL2K⁷	W3YVQ		W3YVQ	W3YVQ	W3YVQ	W3YVQ	W3YVQ	W3YVQ
EL⁸	(⁸)		(⁸)	(⁸)	(⁸)	(⁸)	(⁸)	(⁸)
ARES⁹	(⁹)		(⁹)	(⁹)	(⁹)	(⁹)	(⁹)	(⁹)
Notes for NCS:
1. WVA:		Assigned by MEPN. If none present ask for volunteer for WVA, 3811, 1800L daily summer, 3811, 1700L daily winter. Liaison assigned day before session.
2. DE:		Assigned by DE weekdays and Saturdays. If none present ask for volunteer for DE, 3905, 1830L.
3. 3RN:		NTS requirement, assigned by MEPN, 3RN/2, 3913-17/7043, 1600L daily.
4. MDD:		NTS requirement, assigned by MEPN. If none present ask for volunteer, MDD/C4, 3557, 1900Ldaily (MDD also meets at 2200L, no MEPN liaison).
5. BTN:		NTS requirement, assigned by BTN. If none present, ask for volunteer, 146.67/R - 145.33/R/Alt., Baltimore area, 1830L daily.
6. DRS:		Liaison to NTS Digital outside of MDC (Digital Relay Station), assigned daily by MEPN. Listed on net as /DRS. May also be a /WL2K liaison.
7. WL2K:		Radio-email MDC Section Primary or NTS Target Station assigned by MEPN per STM.
8. Echolink:		Assigned by MEPN. Stations checked in from Echolink, WB3GXW-L (WASH_DC backup). Net EL liaison is reported first in net report as /EL; Additional QNIs on Echolink only are shown as /EL afterwards.
9. ARES^®:		Liaison from each MDC ARES^® jurisdiction, 23 counties, BACI and DC, expected daily to handle traffic to/from their areas for the public and/or served agencies.
10. DELMARVA Net: 3905, 1830L Sundays (primarily eastern shore ARES^® support).

MEPN NCS PROCEDURES - PRE-NET AND DIRECTED SESSIONS

Directed NTS traffic nets have both a sequence (established by the Net Manager) and a procedural standard (set by the NTS MPG nationally). The MEPN NCS script (presented below) sets the sequence for calling the net and may be voiced literally by the NCS. Standard net operating procedures and syntax are to be used by the NCS and stations for operations per the ARRL Methods and Practices Guidelines, ARRL NTS-MPG, PSCM App. B.

The MEPN conducts an undirected pre-net beginning one half hour before the directed session. The NCS should attempt to be present for the pre-net, and the WVA rep may need to be dispatched during the pre-net. If the NCS does not show up at the directed net start time, the ANC, or a qualified NCS, should pick up the net after a one minute grace period. If traffic needs to be passed during the pre-net, record the time as the start of the directed net session, but call the net and liaisons at the designated start time for the directed session.

The MEPN now meets on 3820 kHz, moving up one as needed to prevent interference (check with the NM). Stacks generally are set up +7, +13, -3, or as available. There is no limit on the number of stacks that may be open at any given time. During emergencies there also may be multiple net sessions called at the same time for different purposes.

WINTER EARLY STARTING TIME

When winter propagation causes loss of signals as 1800L approaches, the Net Manager may call for starting the MEPN at 1730L. The starting times given in the NCS script should be voiced accordingly. The MEPN would then run from 1730L and at least until 1805L to allow stations to QNI that can not make the earlier time. The winter pre-net would start at 1700Z. If conditions are poor, the NM or NCS may elect to move the net to alternate frequencies or modes (see below).

The MEPN attempts to coordinate with the WVA net regarding start times, hence on winter schedule, the WVA net may be starting at 1700L coincident with the start of the MEPN pre-net. The MEPN will need to assign and dispatch the WVA rep the previous day or immediately just before the start of the MEPN pre-net so that the liaison may be present at the start of the WVA net.

ALTERNATE FREQUENCIES, MEPN, DTN/DEPN, WVA

If propagation is very poor, the MEPN may shift to alternate frequencies or modes as designated by the Net Manager or NCS:

· 160m on 1920 kHz +/-;

· 7243 kHz +/-;

· 28320 kHz +/- (ground wave);

· ERP 2m net frequencies; 146.82/146.925 ERN, 147.105 CRN, 147.09 WRN;

· Echolink on WB3GXW-L or the *WASH_DC* conference bridge alternate;

· Traffic may be pushed to counties via WL2K, and the STM will take outbound traffic via WL2K as needed;

· Stations may be dispatched to other modes and/or frequencies to exchange traffic, such as CW on the MDD frequency of 3557 kHz, or suitable frequencies for direct exchange using PacTor or WINMOR with the Winlink 2000 client software.

---

· DTN may divert their net from 3905 kHz to 160m at 1905 kHz.

· WVA net may divert from 3811 to 3813 or other nearby frequencies; 1800L summer, 1730L or 1700L winter.

MEPN NET SCRIPT

The MEPN Net Script follows:

CHECK IF THE FREQUENCY IN USE.		MEPN NCS SCRIPT - SEP 2012
PRE-NET: Call the undirected pre-net one half hour before the scheduled directed session. On summer schedule, check for WVA traffic and assign and dispatch the WVA rep to be present at the start of the WVA net. This may be done if WVA begins at 1800L, but will need to be assigned the previous day or immediately before the start of the pre-net if WVA meets at 1700L and the MEPN pre-net begins at 1700Z.
1.	(At the MEPN designated start time.) CALLING THE MARYLAND EMERGENCY PHONE NET. THIS IS [call sign phonetically] NET CONTROL. MY NAME IS [name] IN [location].
2.	ALTERNATE NET CONTROL? (If no response, ignore this job.)
3.	STATIONS WITH EMERGENCY OR PRIORITY TRAFFIC please? (pause for any responders)
4.	THE MEPN IS A SECTION NET OF THE ARRL'S NATIONAL TRAFFIC SYSTEM COVERING MARYLAND AND DC, MEETING HERE DAILY AT [1800 or 1730] LOCAL TIME WITH A PRENET AT [1730 or 1700], AND A SECTION-WIDE EMERGENCY NET AS REQUIRED; INCLUDING LIAISON WITH DELAWARE, WEST VIRGINIA, THE NATIONAL RADIO-EMAIL SYSTEM, AND THE NTSD. THIS IS A DIRECTED NET. ALL STATIONS INCLUDING NEWCOMERS ARE WELCOME TO PARTICIPATE.
5.	QRP, PORTABLE or MOBILE STATIONS? --- ANY RELAYS?
6.	WORDS FOR THE NET please? (Dispatch words, and then ask for fills.)
7.	TRAFFIC FOR WEST VIRGINIA OR DELAWARE please?
8.	DELAWARE REP? (Handle DE traffic, ask rep for comments, and excuse rep. This is a mandatory liaison. If none, assign for 3905 kHz, 1830L daily including DELMARVA, Sun.)
9.	THIRD REGION REPS? (Mandatory liaison. If none, solicit for 3913/17, 1600L, next day. Multiple responders possible. List the primary rep first in the net report.)
10.	MDD REP? (Mandatory daily liaison. If none, assign for 3557 kHz, 1900L.)
11.	BTN REP? (Mandatory daily liaison. If none, assign for 146.67/R, 1830L.)
12.	DRS REPS? (Multiple responders possible, NTSD=/DRS, some also may be /WL2K)
13.	WL2K REPS? (Multiple responders possible, WL2K=/WL2K)
14.	ECHOLINK REP? Daily liaison to Echolink, WB3GXW-L, WASH_DC alt.
15.	STATIONS WITH FORMAL or INFORMAL traffic please? (Multiple responders possible. Acknowledge each by call and then ask each to “please list” their traffic.)
16.	MARYLAND EMERGENCY PHONE NET, [your call], STATIONS WITH OR WITHOUT TRAFFIC? (Multiple responders possible. Acknowledge each by call.)
17.	> LOOP (Begin assigning and dispatching remaining traffic and comments. Stacks off net may be used.)
18.	> Call stations for comments: [call sign], YOUR COMMENTS PLEASE.
19.	< ADDITIONAL OR RETURNING STATIONS? (Loop until business done. Remember to make open calls frequently, giving your call sign at least every ten minutes, and repeat the unassigned traffic list periodically.)
20.	(Closing when all business concluded.) THIS HAS BEEN A REGULARLY SCHEDULED SESSION OF THE MARYLAND EMERGENCY PHONE NET. THANK YOU FOR YOUR PARTICIPATION. THE NET WILL MEET AGAIN TOMORROW NIGHT AT [1800 or 1730] LOCAL WITH THE PRE-NET ONE HALF HOUR EARLIER WHEN THE NET CONTROL IS SCHEDULED TO BE [call sign]. THIS IS [your call] CLOSING THE NET AT [time]Z. 73 AND GOOD EVENING.
21.	FILE THE NET REPORT (due within 48 hours of the session run)
Notes: Acknowledge check-ins by voicing their full call signs. Acknowledge returning stations by repeating their suffix. Repeat calls in specific categories until no further responders.

MEPN NET REPORT FORMAT - 1209

23 R W3XYZ 24 PODUNK MD OCT 10 W3YVQ =*
MEPN*	SUN*		OCT*		10*	2200Z*
QNS/15*	YVQ/NCS/WL2K		FTQ/ANC/DRS/WL2K		KK3F/3RN/WV	QPX/DTN/3RN
WK/MDD	QAA/BTN		K3CF		DYV	HAM
TNM	GLF/EP		QWO		XYZ	TOM
N3ZZZ/JOHN/GARR/M		QTC/5*		QNF/2223Z*	73*
=* JOE
* Required groups (shown bold above) must be entered in the sequence shown with equal signs (=) framing the text as shown, and 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 after the QNF/####Z. All letters are caps in the entire message, groups 5/line separated by single spaces (only shown separated above for clarity). Net Reports are due within 48 hours of the session run. First Line: Use MEPN, 3 letter abbreviation for the day and month, one or two digits for the date (no leading zeros); and enter net session start time (####Z) in 24 hour UTC format. Second Line: QNS/#, the number of stations checked in including NCS, followed by the beginning of the List of Stations. List of Stations: Call sign suffixes (without numbers) may be used (except for 2x1, 1x1, new calls, or calls with conflicting suffixes in the MEPN QNS database list), otherwise please use the full call sign. Enter a new station’s full call, appending the name and QTH with slashes. Station information is appended with slashes, no spaces, in the following sequence: (Call or suffix)/(Jobs)/(Assignments)/(ERP Liaisons)/(Name)/(QTH)/(EP)/(M)/(P) Jobs: NCS, ANC Assignments: /WV, /DTN, /DEPN, /3RN, /MDD, /BTN, /MSN, /DRS, /WL2K, /EAN, /TCC, /3RNAUX or /MDDAUX, etc., multiples permitted as in: /3RN/MDD/EP, or /DRS/WL2K. Note that the primary rep should be listed first in the List of Stations for each assignment category. 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 jurisdiction abbreviations shown in the table below plus agency designator or other Section designator. Name/QTH: /(name)/(county)/(town) for new stations, and /(name)/(state) for out-of-state stations, should be added. If the town or other information item is more than one word, use the “/” to separate each, or concatenate the groups so there are no spaces in the group. Example: KH6ILR/AL/WASHINGTON/DC, or W3XYZ/BOB/MONT/SILVERSPRING. EP: /EP at end, emergency power, generator or battery (not being charged from the mains), solar, etc. M: /M at end, mobile P: /P at end, portable QTC/# QNF/####Z: Follow the List of Stations with QTC/#, the number of messages passed at the direction of the NCS, and QNF/####Z, the net session closing time in 24 hour UTC format. 73: If any comments are to be added they must follow a 73 after the QNF. (This format may be used for entering a net report into the text of an email or radio-email. Here the equal (=) signs are required to frame the text. To send regular ARRL formatted radiograms the “BT” symbol or “=” may be used to frame the text (see the Batch File format for transferring radiograms to NTSD stations). When sending ARRL formatted radiograms via email or radio-email please include the words “please HXC this email” in the subject line.)

NET REPORT JURISDICTION TACTICAL CALL SIGNS

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 tactical call sign alone appended to the amateur call sign usually denotes the emergency management EOC liaison (/HOWA for the Howard Co. EOC), but may also indicate the liaison from the jurisdiction’s ARES^® group.

· The tactical call sign may be modified by adding ARC, SA (Salvation Army), HWC (ARC Hurricane Watch Center), etc., to denote a jurisdiction’s representative for another type organization; as in .../HARFARC or .../HARFHWC. The ARC DLU or ARC CMC offices in Baltimore would be designated by .../ARCDLU or .../ARCCMC; the HWC in Miami as .../HWCMIAMI; Section reps by .../EPA, /WPA, /SNJ, /DE, /VA; etc.

NET REPORT ADDITIONAL LIAISON/DUTY TAGS

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.

· For example, when MEPN, MDD and MSN are all operating simultaneously there are “roving liaisons” required. They are assigned by MEPN, MDD, or MSN as needed. The appended duty is noted as [call sign]/MDD, or .../MSN, etc. It is not usually required to note the jurisdiction of these stations unless they have multiple duties. They are simply net liaisons. Multiple duties may be shown as in: N3ZOC/MDD/MSN, etc.

· When the MDC 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, .../WRN, etc. It is not usually required to note the jurisdiction of these stations unless they have multiple duties - they are simply net liaisons.

MEPN NCS SHEET EXAMPLE

DAY: SUN

DATE: JUN 24

TIME: 2200

MSG#:

QNS/

QTC/

QNF/

NCS

W3YVQ

N3DE

STN

QTC

TEL

QSP

FREQ.

ANC

K3QWO C

K3NNI

ANNAP 682

(2)

3827 1

WVA

N3OK G

WA3YLO C

EDGEWATER

(1)

3827 1

tmw

(OK)

WA3WRT

KGM

3833

DTN

WA3QPX C X

N3KGM

FTQ

ANNAP

3833 2

3RN

KK3F

KB3LNM

NNI

HAGERSTOWN

FTQ

(QPX)

K3CF

YLO

QWO

N3HFC

MDD

N3WK

BTN

(YVQ)

DRS

WB3FTQ

WL2K

(YVQ)

(FTQ)

ECHO

NI2W

--- QNS LIST AREA ---

--- TRAFFIC LIST AREA ---

Syntax (midway through net):

· C = comments made, X = excused; G = gone, strike the G for WVA back;

· Suffixes in parentheses are for noting jobs that are dupes of calls listed elsewhere to help avoid duplicate counting for the QNS total (full calls to the left of the STN column);

· STN = suffix of holding station;

· QTC = station’s listed traffic or other business target (books may be denoted by a bracket around the left side of the destinations); TEL = area and exchange as needed;

· # = quantity, entries are circled (shown as () above) when messages are cleared, slashed if canceled; W = words. QTC is total number of circled formal radiograms passed at NCS command;

· QSP = suffix of station assigned to receive traffic;

· FREQ = location of dispatch - NET for on frequency. (Note the Hagerstown traffic is assigned but not yet dispatched.)

The “traffic list” method records business one traffic destination item per line, dispatched in the most efficient order by the NCS.

3. NET CONTROL PROTOCOLS

NET CALLS FOR CHECK-INS AND PENDING TRAFFIC

NET CALLS: The NCS should make full or abbreviated Net Calls as frequently as possible, usually between transactions or comments, in order not to keep stations waiting to check in or return to the net. The NCS should use the ANC to assist with net calls or relays or ask for help from other net stations as needed. Remember to repeat Net Calls until there are no additional check-ins in a multiple responder category called.

SINGLE RESPONDER CALLS

· SPECIFIC NET CALLS: The NCS may make specific net calls for a specific individual station or liaison, as in: W1AW? or MDD REP? Station checks in with the 1 step method.

· THE ONE STEP CHECK-IN METHOD: A single responder checks in with the full call sign, jobs, assignments, and either “no traffic” or their “[full traffic list] OVER.” The NCS acknowledges the station by [full call sign] STAND BY, or may dispatch it to exchange traffic.

MULTIPLE RESPONDER CALLS

· OPEN NET CALL WITH ID, NCS:
MARYLAND EMERGENCY PHONE NET, [your call], STATIONS WITH OR WITHOUT TRAFFIC please.

· SHORT OPEN NET CALLS, NCS:
ADDITIONAL STATIONS (WITH OR WITHOUT TRAFFIC), or
ADDITIONAL OR RETURNING STATIONS, or
MEPN, ADDITIONAL STATIONS, etc.

· THE TWO STEP CHECK-IN METHOD: Multiple responders check in with the call sign, jobs, assignments and either “no traffic” or “with traffic,” then stand by. The NCS acknowledges the no-traffic station(s) (usually in a batch list) with [full call sign] asking them to STAND BY, or may dispatch station(s) to exchange traffic. The NCS acknowledges each station with traffic by [full call sign] PLEASE LIST. The listing is acknowledged ROGER STAND BY, or the station may be dispatched to exchange traffic.

· SPECIFIC NET CALLS: The NCS may make net calls for specified categories of any type such as a call for an outlet for a certain locality, outlets for a list of unassigned traffic, a relay to another net, a station to store-and-forward traffic, stations with a range of suffixes, stations in a range of locations, etc. These Specific Net Calls can result in multiple responders. Stations not in the category should pause before calling. (Example: “STATION TO HANDLE DC?”) New stations check in and are acknowledged using the 2 step method indicating in comment that they can handle the traffic, net stations respond with their suffix with comment that they can handle the traffic. The NCS may also ask specific stations if they can handle listed traffic for their area, if they can relay via VHF/UHF, if they would receive and store it for later forwarding, or take it to another net.

TAIL-ENDING: The NCS may allow tail-ending at the end of transactions, accepting new station check-in calls (2 step method), returning stations, or net station suffix calls. Stations thus may obtain NCS recognition without waiting for a Net Call. The NCS may optionally accept a series of such tail-end calls without acknowledgment, replying to all in list fashion when they are done. If the NCS does not wish to accept such a series, it may interrupt with acknowledgment of the first station, thus sending a message to others regarding the preference. The NCS must ID with full call sign at least once every ten minutes of continuous net operation, which may be included in an open net call.

TRANSACTIONS: A transaction generally consists of an intended exchange between the NCS and a station for a question or being dispatched or excused, or between 2 stations exchanging traffic or words. It is considered poor practice to interrupt transactions unless urgent. Stations ID in full at the end of transactions as a signal to the NCS that they are done, and to meet ID requirements.

UNDELIVERABLE TRAFFIC:

· It is customary to ask the holding station its pleasure regarding traffic not able to be assigned. The station may cancel the traffic or request other resolution of the problem such as having another station store it for later forwarding or volunteer to take it to another net. (See Assigning Traffic below.)

STATIONS REQUESTING TO TRANSMIT

· STN: (suffix), NCS: repeats (suffix) to grant permission to transmit.

STATUS OF STATIONS:

· New stations checking in for the first time, addressed by full call sign.

· Stations already checked into the net requesting permission to transmit or responding to specific net calls, usually addressed by call sign suffix.

· Returning stations, using full call signs or suffixes, acknowledged by suffix. Example: STN: (full call) from West Virginia No Traffic; NCS: (suffix); or station returning from stack off net: STN: (suffix) BACK; NCS: (suffix)

ASSIGNING TRAFFIC

· Assigning traffic is the process of determining which station(s) will take listed traffic. Traffic is assigned to liaisons for their nets or functions by default. Traffic to other outlets is voluntary and the NCS should frequently announce to the net a list of any pending traffic not yet assigned. The NCS should be aware of the locations of stations and which traffic they might handle. The NCS typically will ask such stations directly if they will take the traffic.

· If no outlet is found for assigning the traffic, ask for a station to relay it to another net, such as a club or ARES net, BTN, MDD, etc.; ask another liaison for a suggested outlet; or ask a net station to “store and forward” the traffic for later handling. The later case should be arranged immediately for visiting liaisons and TCC reps which might check in from time to time.

DISPATCHING TRAFFIC

· As soon as traffic is assigned it may be dispatched off net. NCS may wish to check in most liaisons and call for traffic from other stations before beginning the dispatching in order to get a better picture of the total incoming traffic load and to plan station stacking off frequency.

· Traffic is usually dispatched off the net frequency with the objective of moving the maximum amount of traffic per unit of time and to permit other net business to continue on the net frequency.

· Traffic may be dispatched on the net frequency if necessary (such as involving the ANC, or when net business and time permits). This is sometimes done after comments are completed so as not to make a number of stations wait for a number of messages to be passed, and is delayed only with the permission of the involved stations.

Stacks:

· A stack is a frequency off the net on which two or more stations are assigned to exchange traffic. Stacks are usually limited to two stations exchanging, one waiting, except in the case of books to be sent to multiple stations where all those stations are dispatched at once, or when a station is sent to relay between two stations.

· Customary stack frequencies for dispatching MEPN traffic are 3827 and 3833 as available. The NCS should check for clear frequencies prior to starting the net, by using receiver memories, or use other stations to verify same as the net goes on if desired.

Moving off net frequency to the stack - calling order.

· Off net, the receiving station (RX, for two stations), or sending station (TX, for bulletins or books to multiple stations), or relay station (RLY), checks the stack frequency and calls the other station(s). If the stack frequency is busy, the initiating calling station (RX, TX, or RLY) moves farther away from the net to find a clear frequency and calls. If no contact, all the dispatched stations should return to net within about one half minute.

RADIO-EMAIL:

· Traffic may be listed as Radio-email. The NCS may solicit stations to accept such traffic, and then dispatch it to be sent via WL2K or peer-to-peer as desired. Stations can therefore coordinate and confirm handling Radio-email on the voice net.

DISPATCHING TRAFFIC ON NET FREQUENCY

Dispatches on net:

· W3RX W3TX HERE PODUNK ONE (W3RX initiates the exchange.), or

· W3TX W3AA W3BB W3CC… HERE BULLETIN [to group] (W3TX initiates the exchange.)

· W3TX W3AA W3BB W3CC… HERE BOOK [of (quantity)] (W3TX initiates the exchange.) If the book recipients or TX station have not been able to hear the assignments for the book, the dispatch may be expanded to indicate the destinations:
W3TX W3AA DC W3BB BOWIE W3CC LA PLATA … HERE BOOK [of (quantity)].

· Relay:
W3RLY RELAY W3RX W3TX HERE PODUNK ONE (W3RLY initiates the exchange and relays traffic between TX and RX on the net.

· Conditional dispatch:
W3RX CALL W3TX IF OKAY HERE PODUNK ONE (Stations check copy, and if okay W3RX initiates the exchange. If no copy the dispatch is aborted and NCS makes other arrangements to move the traffic.)

DISPATCHING TRAFFIC OFF NET TO STACKS

MIXED STACKS ARE NOT PERMITTED: No station, having completed a stack exchange, should have to wait on the stack for another station’s exchange to be completed before doing another assignment on that same stack. This would be difficult, confusing, and generally unworkable.

UNASSIGNED EXCHANGES ARE NOT ADVISED: Stations dispatched to a stack should handle only the traffic dispatched (the NCS may have other stations assigned to additional traffic). If errors are made, or other traffic discovered, the stations may return to net to get the dispatches in order. Moderate increases in quantity or addition of a few messages to the exchange can be done if reasonable and would ultimately save total net time. Stations dispatched to stacks are responsible for advising the NCS of any changes in the traffic or quantities exchanged. Stations dispatched to stacks should not engage in conversations or otherwise delay the net business. Net stations should not go to stacks unless assigned.

· Dispatch first two stations:
W3RX W3TX 3827 PODUNK ONE (Stations acknowledge RX GOING, TX GOING, in the order dispatched.)

· Dispatch a third station:
W3XX 3827 W3TX AFTER W3RX HOMETOWN TWO (Station acknowledges XX GOING. W3XX calls W3TX when W3RX is done and receives two messages.)

· Adding More: Dispatching an additional station (4^th or more) to the stack can be done after the first station returns, or as needed to maintain the stack’s size - two exchanging, one waiting. A second or additional waiting station can be dispatched to the stack, particularly if it is to be excused after the exchange. In all cases the “AFTER” statement in the dispatch is critical to maintaining the stack sequence and the dispatched stations must observe the order. Mixed stacks are not permitted. The established sequence will enable all traffic to be passed with each station knowing its turn.

· Bulletin and Book traffic to multiple stations:
W3TX W3AA W3BB W3CC… 3827 BOOK [of (quantity)].
Stations acknowledge going in order as above. Note that the sending station (TX) is dispatched first in the syntax, and also calls first off frequency and conducts the polling and book transmission. If the book recipients or TX station have not been able to hear the assignments for the book, the dispatch may be expanded to indicate the destinations:
W3TX W3AA DC W3BB BOWIE W3CC LA PLATA … 3827 BOOK [of (quantity)].

· Relay Exchange (RX and TX can not copy each other, RLY copies both):
W3RLY RELAY W3RX W3TX 3824 PODUNK ONE (Stations acknowledge RLY GOING, RX GOING, TX GOING. RLY initiates the exchange and relays traffic between TX and RX.)

· Conditional Dispatch - check copy first:
W3RX CALL W3TX HERE IF OKAY 3827 PODUNK ONE (Stations check copy, and then acknowledge RX GOING, TX GOING. W3RX initiates the stack exchange.)

· Dispatch Relay of Dispatch:
W3RLY DISPATCH W3RX W3TX 3827 PODUNK ONE (RLY repeats the dispatch to RX and TX, both stations acknowledge going, and RLY ID’s to conclude the transaction.

· Dispatch Relay of Dispatch and Relay Exchange:
W3RLY CALL AND RELAY W3RX W3TX 3827 PODUNK ONE (W3RLY repeats the dispatch in case RX or TX are not copying NCS, as follows):
W3RLY FOR RELAY W3RX W3TX 3827 PODUNK ONE. (Stations acknowledge RX GOING, TX GOING, RLY GOING. RLY initiates the exchange at the stack and relays the traffic.)

RETURNING STATIONS

After an exchange at a stack frequency the stations pause for a moment to listen for any calls by new stations coming to the stack frequency (whether the stack stations are excused in advance or not). Failure to listen for calls can cause a missed assignment. If stations are excused in advance and fail to make contact or complete the assignment they should return to net frequency and try to catch the NCS, or should later advise the NCS of their inability to complete their assignment. The stations should make any possible arrangements on their own to move the traffic in such cases.

· Returning station, job completed:
(suffix) BACK. NCS: repeats (suffix) to acknowledge.

· Returning station, job failed:
(call sign) NO JOY (with optional explanation). NCS: repeats (suffix) to acknowledge, may ask for explanations, and will re-list the traffic for subsequent handling.

· Liaisons returning from other nets:
(call sign) (net name) NO TRAFFIC, or
(call sign) (net name) WITH TRAFFIC
NCS: repeats (suffix) to acknowledge or if with traffic the NCS asks the station “(call sign) PLEASE LIST,” lists the traffic, and may dispatch the traffic at this time.

EXCUSING STATIONS

· Excusing Individual Stations directly from the net: The NCS syntax:
(call sign) [THANK YOU, 73, etc.] YOU ARE EXCUSED.

· Excusing in Advance. Although seldom done on MEPN, one or more stations may be excused in advance by appending the following to the end of an off-net dispatch:
… (call sign) EXCUSED, or … BOTH EXCUSED, or … ALL EXCUSED (for multiple stations dispatched for bulletins or books)

__________________________

Page last updated SEP 12, 2014

“Windows” operating system references are trademarks of Microsoft.

ARES^® is a trademark of the ARRL, Newington, CT