Washington County ARES/RACES

NTS Message Information

National Traffic System Methods and Practices Guidelines Packet Traffic Voice Traffic
updated 7/1/2006


National Traffic System Methods and Practices Guidelines
The Entire NTS-MPG manual in PDF

Manual Section

PDF File Size in bytes

Table of Contents

30 K

Foreword, Acknowledgments

21 K

Chapter 1 The ARRL Message Format

95 K

Chapter 2 Sending Messages On Voice

188 K

Chapter 3 Sending Messages On CW

161 K

Chapter 4 Net Operations

371 K

Chapter 5 Net Control

185 K

Chapter 6 NTSD - NTS Digital

54 K

Chapter 7 Station Reporting - SAR -- PSHR

35 K

Chapter 8 Delivering, Servicing, Originating

65 K

Chapter 9 Tactical Nets, Public Service Events

49 K

NTS Area/Region Net Directory Listing

6 K

NTS Routing, Call/State/Region/Area/Section/Division

    25 K

All of the manual in one ZIP file
985 K

Page Contents: Introduction · Foreward · Objectives · Chapter Summaries · General Information · Acknowledgmentsxxxxx

INTRODUCTION

This document, NTS Methods and Practices Guidelines (NTS MPG), is attached to the ARRL Public Service Communications Manual (PSCM) as Appendix B, and is the working reference manual on Traffic Net and Message Handling Procedures in the NTS. It shall be the uniform reference standard for STMs, Section/Local NMs and Area Staff members.

The NTS MPG document is maintained by the Standing Committee of the three NTS Area Chairs, and selected additional staff persons, under the General Procedures sections of the NTS Terms of Reference (NTS TOR), attached to the PSCM as Appendix A.

This manual will be a working reference document---subject to change as Amateur Radio continuously improves how the tasks are performed. The methods presented are a reasonably accurate snapshot of current practices. They are indeed practices, and not strict rules, but the beginner, Section, Region, Area, and TCC net operators and management alike will find it beneficial to have a uniform protocol reference to be used by operators.

It is further hoped that the wisdom of the founders of the ARRL and its NTS with respect to fundamental operating practices, along with new practices, will be preserved in tact in one collection of documentation as the NTS goes forward. Other essential references such as message Precedences, "Q signals", Handling Instructions, ARRL Numbered Radiograms, etc., are reproduced in this manual although available from ARRL in Newington, CT, in printed form or on the internet. You will need to update these from the ARRL primary source from time to time.

The ARRL NTS system operation is in accordance with the PSCM and NTS TOR. Such matters are left to those separate documents.

This manual deals with station and net operating practices and not with matters of net format or system management. Those issues are dealt with by Net Managers, Section Traffic Managers, and Area Staffs, etc., as appropriate. This manual is not intended to infringe on their discretion in such matters, nor with "job descriptions" imposed at any level.

Instructors may extract the information in the manual for use in their own training lesson plans provided full credit is given to the ARRL source. Some simplified overview tutorial documents may be made available through ARRL Field and Educational Services from time to time, particularly for the introduction of the NTS to newcomers to Amateur Radio.

Requests for further information, explanations, or suggested additions should be submitted to your Net Manager for consideration. After review, such input may be forwarded via either STM's or Area/TCC staff to the appropriate Area Chair for periodic consideration by the NTS standing committee on standards and practices.

FOREWORD

Handling communications for a third party has always been a technology and art form capturing the imagination of people throughout the history of civilization. Such communications have played an important role in the development of the world as we know it. It is no surprise that this fascination persisted and flourished with the introduction of the telegraph and radio.

From smoke signals to semaphore, telegraph to email, the art form has adapted to the prevailing technology of the time. Over the years the mechanism of getting the information from point A to point B may have changed, but the basic steps of creating the transmission-ready final form of the communication, the handling of it through the system, and the reception and delivery have remained essentially the same.

In Amateur Radio today we find many adaptations to the technology of the time and, in fact, are involved in developing new technologies as we go along. The basic underlying purpose and act of communicating for a third party, or for ourselves, is still fascinating and useful regardless whether we are using CW, Voice, RTTY, PSK-31, packet, or WinLink gateways. The use of today's modes has expanded our abilities far beyond the time when Hiram P. Maxim wanted to send his message on CW to order a new tube and seized upon the idea of having a system of scheduled and reliable nets to handle such message traffic.

We began this Amateur Radio journey in an organized way in 1914 when the American Radio Relay League was founded, and the NTS net system has developed and adapted over the years. Today the ARRL manages and operates the National Traffic System (NTS/NTSD) to assure a continuing and reliable structure to handle formal message traffic in the US. Many other countries participate in the system as permitted by treaty or convention. CW, Voice, and a variety of digital modes and structures are operating to assure the use of all Amateur Radio resources in the public service effort.

There is a large body of experience and literature available to guide amateur operators in using radio to establish contact. This experience is in many ways unique to Amateur Radio due to its flexibility and resourcefulness driven by personal interest and motivation. This manual will not deal with this art except where the specifics of radio operation are conducive to effective message transmission and reception.

The public and our served agencies appreciate our ability to send formal written message traffic efficiently and accurately. When we combine our traffic handling, radio and net operating skills to provide professional service we earn their trust.

The process is simple, yet there are details to learn about how to make it all happen efficiently and with precision. We must interface with those we serve and gather the information required to prepare the message in the proper format. We must be skilled at exchanging the message with another station to pass it along, and be able to participate in and run organized nets to efficiently handle large amounts of message traffic. We must know how to deliver the message to the addressee, and create a reply or a service message back to the originator when required.

The manual, therefore, will deal with the methods used by effective communicators in transmitting and copying message traffic while dealing with language perception, format and protocols, net operating and net control, and managing the completion of the task through to delivery and servicing of messages. Soliciting messages from the public and brief discussions of public service and disaster operations are also presented.

OBJECTIVES:

The primary objective of these methods and protocols is to facilitate transmission of a properly formatted written formal message from point A to point B such that it arrives exactly as written on the original copy, group for group, character for character, space for space.

Messages filed in the NTS must be capable of being transmitted by any mode without message alteration being required.

Voice and CW nets must be run with methods and protocols to operate effectively and uniformly so that message traffic may be exchanged with efficiency.

Stations operating in the NTS have the responsibility to promptly relay messages along, deliver messages in a timely fashion, or service undeliverable messages back to the originator. Stations must honor this responsibility.

Stations operating in the NTS interface directly with the public and served agencies representing all of Amateur Radio. Stations must represent us all well.

The methods and protocols of the NTS MPG are intended to facilitate achieving these objectives.

CHAPTER 1, FORMAT: Chapter 1 presents the standard ARRL formal radiogram format used throughout Amateur Radio today for written message traffic. This format is the expected form of written messages, and is used everywhere except in a few specialized served agency applications where simplified incident reports or customized RACES forms may be used. Other techniques used in some disaster efforts, such as taking lists of contact names for welfare inquiries, and other similar informal traffic handling methods, are beyond the scope of this manual.

CHAPTER 2, VOICE: Transmission of formal written traffic by voice confronts the amateur with the difficulties of voice perception when attempting to convey form and content with precision. The path of the manual temporarily splits accordingly, presenting voice message exchanging protocols in Chapter 2 separate from the CW protocols. The two station voice exchange is presented in this chapter.

CHAPTER 3, CW: Transmission of formal written traffic by CW is presented in Chapter 3. The technique is notably different than on voice. The two station CW exchange is presented in this chapter.

CHAPTER 4, NETS: Managing the voice and CW transmission of messages beyond the two station exchange is handled on nets. The manual paths again converge, presenting both CW and voice traffic net operating guidelines, for both the participating station and the net control, in Chapter 4.

CHAPTER 5, NCS: Additional topics unique to net control are expanded upon in Chapter 5.

CHAPTER 6, NTSD: Messages transmitted with the digital modes use the standard ARRL format for the entire message entered into the text field, thus enabling a message to move from one mode to another without modification. Chapter 6 presents the NTS Digital (NTSD) methods of handling the standard message including the routing information in the "To" and "Subject" blocks. The NTS Digital Guidelines for the system are included in this chapter.

CHAPTER 7, SAR/PSHR: Chapter 7 presents the methods used by stations participating in the National Traffic System for reporting their monthly activity---the SAR and PSHR reports.

CHAPTER 8, PUBLIC INTERFACE: Chapter 8 presents guidelines for delivering messages to the addressees, sending service messages back to the station of origin to report on progress or problems, notes on originating messages from the public and mass mailings.

CHAPTER 9, PUBLIC SERVICE: Chapter 9 ends the manual with a discussion and examples of some tactical public service type operations. Section Emergency Coordinators and local EC's generally stipulate the methods used in this type operation, hence the examples given here are designed to show how the traffic net procedures can be useful in such nets.

GENERAL: Throughout this manual there are tasks presented which are, or may be, handled using various techniques. Different methods for doing the same task are either presented as alternate choices explained in full as separate cases, or included in notes within the chapter section. Often the order of preference is based upon the current "best Amateur Radio practice".

In some cases there are matters for which there is no customary method yet devised or widely used. A few suggestions are made, but plain English is always a default tool for accomplishing the tasks or issuing the commands in these cases.

Some new ice is broken in a few protocols presented in the manual. For example, the continuing problem of how best to handle voicing of different kinds of groups encountered in messages when on the phone nets has been consolidated into one set of guidelines. Although these matters are handled in a variety of ways throughout the system, the presented form will be of assistance in bringing some uniformity. To do otherwise would leave a large number of variable "rules" to use which can be confusing to the newcomer. A variety of rules can lead to misunderstandings and surprises when transmitting message traffic even among experienced operators. The voicing protocols presented here are designed to be mutually exclusive, assuring that every form of message syntax or encountered group will have a unique method applied. The experienced operator may then come to expect a unique meaning of the method in each situation.

Such license is taken only when the presented protocols have been subjected to extensive testing in typical amateur traffic handling situations. When choices were available, those presented first in order were chosen to attempt to optimize message transmission and reception accuracy, then efficiency.

In addition to the chapter texts, some additional attachments are included in both textual and graphics form to aid in the fundamental purpose of the work, i.e., to provide a document for those wishing to have a ready reference for the current "best Amateur Radio traffic handling practices" of the day.

The overall NTS MPG table of contents is presented up front for printed version reference purposes. Each chapter has its own table of contents.

The future of the NTS is in the hands of those who understand the value of formal third party communication and the technology required to make it effective in today's environment. To assure opportunities for all amateurs to enjoy the rewards of public service traffic handling it is essential to pass along the knowledge developed over the years, and to introduce newcomers to this particular subset of Amateur Radio activity. Everyone can participate.

Formal traffic handling is an essential part of Amateur Radio emergency communications public service as well. Effective ARES/RACES operations need not invent a new wheel to accomplish this. Where formal traffic handling is required, cooperative effort and training between NTS operators and those of ARES/RACES will produce benefits for the overall effort. The distinction between the groups with respect to traffic handling can be made to vanish. ARES and RACES operators can become NTS operators within their domain.

It is worthwhile to reduce the number of amateurs encountered at hamfests who have been in the service for ten or twenty years or more who have never heard of the NTS! It is perhaps more important to be certain that newcomers, from the first day they enter the service, are aware of the NTS/ARES/RACES and the skill levels used in serving the public.

Pass the torch!


ACKNOWLEDGMENTS

Many outstanding Amateur Radio operators have contributed to this manual---some without even being aware of it at all. We are specifically referring to all the devoted NTS operators, net controls and managers encountered since way back in the United Trunk Line days. Those individuals were the mentors for all of use coming up through the ranks of the traffic handling community. They are the ones who pioneered the practices we use today, and to each and every one of them we owe our thanks for their devotion to the effectiveness of our traffic handling systems. Remember that H. P. Maxim was doing this at one time... with the same intent as those of us who pound brass, voice messages, or type on keyboards today.

Particular thanks must be given to Bill Thompson, W2MTA, most recent past Eastern Area Chair, who shared a keen interest in this particular work, encouraged its progress, and made it possible to bring it to this level. It is hoped that the manual will satisfactorily justify his trust.

Thanks to Marcia, KW1U, current Eastern Area Chair, who helped carry the work forward, and to Jim, KB5W, Central Area Chair, and Rob, K6YR, Pacific Area Chair, for their assistance, guidance and suggestions in bringing this work of the Standing Committee to final form and submission.

Thanks also must be extended to Gary Ferdinand, W2CS, who likewise shared a keen interest in this effort. His considerable time and effort in precise and detailed review and criticism of the articulation of techniques helped capture in the written word efficient methods and syntax at all levels of operating activity. To a large extent the capturing of best current practice in this manual is due to his sharp eye and experience.

Thanks to Nick, N4SS, Eastern Area NTSD, and Cal, N3QA, former 3DC, who both made extensive contributions to Chapter 6 on the NTS Digital system.

Appreciation must also be extended to all the currently active net controls and operators who answered questions or set the example along the way. This was always done with the friendly spirit of cooperation in Amateur Radio that makes our service unique.

And thanks, too, to all the NTS operators in the MDC Section who put up with the constant experimentation with traffic handling quality control tests, training and exercises, SET workloads, and constant preaching. The MDC SEC, WA1QAA, was first in line insisting on having this kind of document, and spent untold hours helping to review content. Thanks also to John, KO4A, who invested his time and effort in early formatting of material which helped move the project forward.

All of those operators, Section and national, contributed a great deal to this manual by proving what works, and reminding us all daily why we do this.

73, Al, W3YVQ, EAS Associate Member, ORS, OES,
MDC ASM RACES-ARES/NTS Coordinator.



Packet Traffic
National Traffic System Methods and Practices Guidelines 
 
INTRODUCTION TO PACKET RADIO - PART 12 - by Larry Kenney, WB9LOZ

The National Traffic System, known as NTS, is the ARRL sponsored Amateur Radio message handling network.  Packet radio is now playing a very important part in the network, so let's take a look at the system and give you some tips on handling NTS traffic by packet.

Handling third party traffic is the oldest tradition in amateur radio. Nationwide, the National Traffic System has hundreds of local and section nets meeting daily in order to facilitate the delivery and origination of such messages.  More and more of this traffic is being originated, relayed, and delivered on packet.  If you enjoy traffic handling, you can easily get involved in NTS via packet.  If you're on packet but know nothing about NTS, this part of the series will get you off to a good start.  At the end you'll also find some references for further information on NTS.

Local packet BBSs have to be checked daily for traffic that needs to be delivered or relayed.  When you check into your local BBS, enter the LT command, meaning "List Traffic".  The BBS will display a list of all NTS traffic awaiting delivery.  It'll look similar to this example:

MSG# STAT SIZE TO     FROM   @BBS   DATE/TIME SUBJECT
37893 TN    486 60625  KB6ZYZ NTSIL  1227/0712 CHICAGO, IL 312-267
37802 TF    320 06234  WB6DOB NTSCT  1227/0655 NEW HAVEN, CT
37854 TF    588 93432  KA4YEA        1227/0625 CRESTON, CA 93432
37839 TN    412 94114  KA8UHL        1227/0311 SAN FRANCISCO 415-821
37781 TF    298 94015  W1KPL         1226/2356 DALY CITY, CA 415-992

You might see traffic that is being relayed by your local BBS to some other part of the country as well as traffic for your local area. The "Subject" or "Title" column of the listing will show the destination of the traffic.  If you see a message that is within your local area, help out and deliver it.

RECEIVING A MESSAGE: To take a message off of the Bulletin Board for telephone delivery, or for relay to a local NTS net, enter R followed by the message number.  Using the list above, R 37839 would send you the message from KA8UHL for San Francisco.  You'll find the message in a special NTS RADIOGRAM format, with a preamble, address, telephone number, text and signature, ready for delivery.  After the message has been saved to your printer or disk, the message should be erased from the BBS.  Use the K command, as you do for killing your own messages.  To kill message 37839,
for example, you'd enter: K 37839.  This prevents the message from being delivered again by someone else.

DELIVERING OR RELAYING A MESSAGE: Once you have received the NTS Radiogram, it should, of course, be handled expeditiously.  If it's for your immediate area, you should deliver the message by telephone.  If you took the message
for delivery to the local traffic net, you should make an effort to see that it gets relayed as quickly as possible.  If you're unable to deliver the message, due to an incorrect phone number, no answer after several tries, or some other problem, send a return message to the originator advising him of the non-delivery, and why.

SENDING MESSAGES: Any amateur can originate a message on behalf of another individual, whether the person is a licensed amateur or not.  It is the responsibility of the originating amateur, however, to see that the message is in proper form before it's transmitted.  A special format is used for NTS traffic so that the messages are compatible across the entire network. 
Each message should contain the following components in the order given: 
number, precedence, handling instructions (optional), the station of origin, check, place of origin, time filed, date, address, telephone number, text and signature. 
The destination of all NTS traffic must be to a point in the US, its possessions, or Canada.

When the message is ready to be entered into your local BBS, you must use the ST command, which means "Send Traffic", followed by the zip code of the destination city, then @ NTS followed by the two letter state abbreviation.  The form used is ST ZIPCODE @ NTSxx.  A message being sent to Boston, MA 02109 would be entered as follows:  ST 02109 @ NTSMA  and a message for Iowa City, IA 52245 would be entered as ST 52245 @ NTSIA.  The message SUBJECT or TITLE should contain the destination city and state and the telephone area code and exchange, if available.  See the examples in the
listing above.  Only one NTS message should be included in each packet message (no "book" messages).  The actual radiogram should be included entirely within the TEXT of the packet message, including all of the components listed above.  End the message with the usual Control-Z or /ex.

IN TIME OF EMERGENCY: The National Traffic System functions on a daily basis as a public service for both your fellow hams and the general public.  It serves another function as well.  The NTS provides a well oiled and trained national system of experienced traffic handlers able to handle large volumes of third party traffic accurately and efficiently during
disasters.  Your participation now will help prepare you for that time of emergency.  Following the Loma Prieta Earthquake in October of 1989, over 7000 NTS messages were handled by packet BBSs in the San Francisco Bay Area.  We needed and used all of the help we could get.

REFERENCE MATERIAL:  The ARRL booklet "An Introduction to Operating an Amateur Radio Station" offers detailed information on handling and preparing NTS Radiograms.  There are also many files with detailed information on NTS available for downloading from your local BBS.  They give a complete rundown on how to prepare and send an NTS message on packet, how to deliver NTS messages, etc.  Check your local BBS files section for them if you want to get involved.  Your help will certainly be welcome!



Voice Traffic
NTS "Cheat Sheet" 
National Traffic System Methods and Practices Guidelines

Outgoing NTS Traffic Routes

Formal traffic is handled on most all nets. The timing and handling method for entering traffic into the NTS depends on the time of day. Outgoing traffic in Washington County is handled most conveniently on the following nets and times:

  • NTTN (Northwest Traffic and Training Net) (also called the 605 net) at 6:05 pm on the linked repeaters of the Western Oregon Radio Club including the 145.27, 145.43, 145.47, 146.80, and 443.150 MHz repeaters, all having a pl tone of 107.2 which is timed to pass to OSN (Oregon State Net).
  • ARES D1 (Amateur Radio Emergency Service District 1) net at 7:30 pm on the 147.320 MHz repeater. Traffic passed on this net usually will be sent the next day either on DRN7 (Daytime Regional Net 7) or the Noon time net.

Outgoing messages should be passed before 6:30 pm to a CW operator who is going to OSN1 if it is to go out that day. If the message may wait it can go to an operator who will take it to DRN7 or the Noon time net the following day.

  • The OSN1 is at 6:30 pm (CW on 3587 kHz).

  • The DRN7 is at 9:45 am (SSB on or about 7236 kHz).

  • The Noon time net is between 10 am and 1 pm (SSB on 7268.5 kHz).

Outgoing traffic can also be handled on the afternoon DRN7 at 3:15 pm (SSB on or about 7236 kHz) although this net is usually for incoming traffic.
The people who go to DRN7 regularly are:

  • K7PMB Ralph
  • N7DRP Betty
  • And sometimes N7CM Claire

KC7ZZB Hal frequently goes to the Noon time net.
And traffic handlers to OSN1 often are:

  • N7YSS Dave
  • N7CM Claire
  • KK1A Karl
  • WS7L Carl

Outgoing traffic from the NTTN, ARES traffic net 5:30 pm (SSB on 3993.5) or BSN (Beaver State Net) 5:45 pm (SSB on 3920) can go out at 6:30 pm if it gets to one of the CW operators soon enough. Otherwise it goes out on DRN7 or the Noon time net the next day.

Traffic can be handled by any HF operator; the people listed are those that are usually willing and often available to handle it. You are also encouraged to check into any of nets within your capability and operating privileges to enter NTS traffic into the system and take messages for delivery.