Oregon Packet Operators Certificate Program

Date: 14 October 2001

Author: Tom Mosher - AB7NV

Release Notes

 
Date
Notes
14 Oct 2001
Initial release

Introduction:

This document describes a certificate award program for amateur radio operators who demonstrate proficiency in packet radio operation, as it pertains to emergency communications. The goal of this program is to encourage training, participation in packet radio operations and developing proficient operators. The certificate is awarded by the Oregon Section of the ARRL's Amateur Radio Emergency Service.

Method:

The certificate can be earned by demonstrating the skills necessary for successful packet radio operation in emergency communications.

The Skills:

The following list is the set of skills that must be demonstrated in order to earn the Packet Operator's certificate.
  1. Start TNC and configure
  2. Start computer
  3. Start radio, select frequency and adjustments
  4. Start software and configure
  5. Check communication to Node.
  6. Check communication to BBS
  7. Compose message using ARES/RACES Packet Standard
  8. Determine correct address of receiving station
  9. Verify if receiving station is staffed by ARES/RACES personnel
  10. Post message to BBS
  11. Post bulletin to BBS
  12. Retrieve message from BBS
  13. Retrieve bulleting from BBS
  14. Retrieve file from BBS
  15. Check forwarding status of messages and bulletins on BBS or TNC
  16. Send and receive messages from the TNC mailbox
  17. Print messages, bulletins and files
  18. Log sent and received messages
  19. Reply to received messages
  20. Find alternate nodes and BBS

Demonstrating the Skills

Mastery of the Skills can be demonstrated in a number of ways. The method detailed in this section is one that has been approved by the certificate issuers (Oregon ARES). Other methods that are approved by the certificate issuers can be used to demonstrate the Skills and qualify for the certificate.
This method is based on the "Packet Challenge" activity sponsored by the Marion County ARES group during the first half of 2001. The Packet Challenge was organized to cover many of the necessary packet skills. The following list of exercises (see Table 1) duplicates many of the Packet Challenge activities, with a few new ones created as necessary to cover all of the Skills. Where applicable, the equivalent Packet Challenge activity is noted, as "PC #?".

Note that in some cases, a given activity can be performed in a way that will demonstrate either more or fewer skills than are listed in Table 1.

A Note on Word Counts: Packet radio uses AX.25 which has a very good error correction scheme that makes the need for “word count” unnecessary. All packet traffic starts out in written form. Packet traffic may at times be converted into NTS phone traffic. At that time a word count should be added. The ability to accurately compute the Word Count remains an important aspect of formal traffic handling.

Table 1 - Packet Activities
 
Activity
Skills Demonstrated
  1. Create and maintain a log of all Packet Certificate activities.
Skill #18
  1. Send a packet radio message to the coordinator containing the bulletin number of the Packet Certificate announcement (PC #1)
Skills:
#1, 2, 3, 4, 6, 10, 12, 13 
  1. Read message from and place a message into a TNC "personal" mailbox (PC #4) 
Skill 16
  1. Connect to a Node and retrieve information on it's Ports (PC #5)
Skill 5
  1. Report the full hierarchical address of an ARES EOC facility (PC #6)
Skill 8
  1. Retrieve a file from a BBS directory (PC #8) and convert ARL radiogram to plain text.
Skill 14
  1. Compose and send an Training/Drill Traffic message
Skill 7
  1. Compose and post a Bulletin to a BBS, verify when it is forwarded.
Skill 11, 15
  1. Create hard-copy printed records
Skill 17
  1. Connect to a Node or BBS by more than one route
Skill 20
  1. Reply to a received message
Skill 19
  1. Verify if a station is actively staffed
Skill 9

 

Notes for each Activity

Activity 1: Maintaining a log of station activity is an important emergency skill. This provides a written record of message traffic and station activity, which can be very helpful when giving way to a relief operator.
For the Packet Certificate program, use the Log as your summary of your Skills demonstration. Note in your Log each activity for which Skills are being claimed. A sample Log file can be found in Addendum B. You must submit your Log to the Certificate coordinator as proof of skills. The Log may be kept either in paper or electronic form. Some Activities require only that information be entered in the Log, while other Activities require a message be sent to the Certificate coordinator as well.

Activity 2: The Certificate coordinator shall post an announcement of the Packet Certificate program on all BBS systems in Oregon (sb ares@or and races@or). The announcement should then appear on all local BBS systems, ideally including those designated in the local communication plan as a primary communication resource. This will encourage operators to be familiar with the same BBS that they would use during an activation. The announcement will appear with a BBS bulletin or message number, and will include the name and packet address of the current Certificate coordinator.

If the Packet Certificate announcement is not available on your local BBS, contact the Certificate Coordinator or an ARES official in your area and ask that Announcement Bulletin be re-posted. This is often necessary due to the limited lifetime of bulletins in many BBS systems.

For the Packet Certificate program, the operator should send a packet message containing the bulletin or message number of the announcement to the Certificate coordinator. The coordinator will return a confirmation message, which the operator should note in their Log.

Activity 3: One method to demonstrate the skill of using a TNC mailbox is to connect via node hopping to the TNC of the Certificate coordinator, read a message, and leave a message there. This would also demonstrate Skill #5. Alternatively, one could exchange messages on the TNC of another operator in your local area. List in your Log any Nodes used to make a remote connection.

Activity 4: If not already demonstrated in Activity 3, the operator could access a remote Node and retrieve information about its Port configuration. Record the information in your Log.

Activity 5:Using Packet Radio means, determine the full hierarchical address of any ARES EOC facility, and record the address and method used in your Log.

Activity 6: For this activity, find and retrieve a file from a BBS file directory that contains a message in ARL radiogram format. Convert the radiogram into plain text and add the correct word count. Enter the plain text message in your Log. The original message file will be distributed by the Certificate Coordinator.

Activity 7: Using the information in Addendum A, send a "Training/Drill" traffic message to your local EOC facility. Receive a confirmation from the EOC that your message was received, and record the date and time in your Log. Note that this could be combined with Activity 6 to demonstrate Skills 7 and 8 in one step.

Activity 8: Post a Bulletin to the "PACKET" category with statewide distribution. Verify that it has been forwarded to other BBSes by connecting to a remote BBS. Enter a description of your bulletin and the approximate time required for the forwarding to take place in your Log.

Activity 9: Practice creating hard copy of packet traffic, and make an entry in your Log. Take the opportunity to check for any spare resources needed (paper, ink cartridges, etc.)

Activity 10: Enter in your log at least two routes you can use to access a remote BBS.

Activity 11: Using the "sr" command, send a reply to a packet message you have received. There should be plenty of opportunity to demonstrate this skill during normal packet activity.

Activity 12: It may be necessary to perform this activity during a training exercise.

Finally, the operator should feel free to use any combination of their own activities to demonstrate the Skills. Please record in your Log whatever means you are using to demonstrate each Skill, and submit the Log for verification of earning the Packet Certificate.

Earning the Certificate

One goal of the Certificate program is to keep the administrative burden to the minimum, so that the activity can be easily self-sustaining. During the startup period of the Packet Operators Certificate program, the Packet Challenge coordinator (Tom Mosher, AB7NV) will serve as the Certificate coordinator. After completing all of the Activities or equivalent, the applicant should send in their completed Log, and any other necessary proofs. The log can be sent as a packet message if desired. The coordinator will verify that the activities listed in the Log match up with the coordinator's records, and to verify any Skills demonstrated by alternate means. Once the Log has been verified, the operator's name will be forwarded to the ARES/RACES Packet coordinator, who will issue the certificate directly to the operator.

Comments?

Contact the author with your comments or questions via packet, or email at ab7nv@arrl.net.

Addendum A

ARES/RACES PACKET ECC TO ECC COMMUNICATIONS STANDARD

===========================================================
ver 10/30/99
DISTRICT #[X]:ARES/RACES Packet Operational Detail

The Amateur Radio callsign used at the [name of ECC] Emergency Coordination Center (ECC) is [call of ECC].

===========================================================

NOTE:

Once a month all stations should send a message about local ARES/RACES activities; meetings, drills, nets, training, meeting minutes or anything that may be of interest to the ARES/RACES groups in the state.

Post messages in the following way:

sb ares@or

sb races@or

============================================================

PACKET RADIO should be the primary means of communication with other ECCs where the traffic is written data.

It may be critical to determine if the receiving ARES/RACES unit has been activated. There may not be any ARES/RACES personnel at the receiving station.

Packet will provide automatic, written copy of all communications with an emphasis on data (example:names and addresses and for lists of supplies and equipment).

Stations with traffic for other ECCs should place the traffic on the closest full service BBS system in their area for automatic forwarding.

Because bulletin forwarding may be reduced during some phases of a drill, exercise or emergency, it is necessary to send all traffic as personal.

All packet traffic received should be acknowledged.

Your message or traffic should include routing information within the destination ECC in the form of a name and/or job function (this saves time and confusion in delivering your message or traffic). Also include

date/time, who the message was originated by and a signature at the end of the message. Because bulletin forwarding may be reduced during some phases of a drill or emergency, it is necessary to send all traffic as

personal.

An example message follows:

SP KC7KKK@KC7KKK.#ABCD.OR.USA.NOAM

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

MESSAGE:14 TURKEYFOOT COUNTY EOC

PRECEDENCE: E

ORIGIN:W7WWW@W7WWW.#ABCD.OR.USA.NOAM

PLACE:Turkeyfoot County ECC

DATE:April 15

TIME:14:23

TO:Bill Jones

Logistics Section

Turkeyfoot county has suffered an earthquake.Disaster declaration in progress. Will transmit via packet radio when available with further information.

Signed:Millie Bowhunt, Emergency Manager

Turkeyfoot County

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

The acknowledgment from the receiving ECC will appear on the BBS system on which you posted the message.Logon to your BBS and check for messages on a periodic basis (every 15 minutes). An acknowledgment of the receipt of the traffic should be returned quickly.

An example follows:

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

DATE:April 15

TIME:14:23

TO:KB7XXX@K7ABC.#ZXYU.OR.USA.NOAM

RE:MESSAGE 14 TURKEYFOOT COUNTY EOC

YOUR MESSAGE NUMBER 14 RECEIVED 14:45 (LOCAL) APR 15

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

NOTE:The receiving station cannot predict when an official response to your traffic will be sent from the ECC or by which mode the response will come (telephone, public safety radio, amateur radio).

Traffic sent to the State ECC should be addressed to the "Duty Officer".

TRAFFIC FORM:

ALL OFFICIAL TRAFFIC to and from ECCs must be in the Official ARRL Traffic Format minus the word count and handling instructions.This includes traffic related to Amateur Radio Communications, but does not include the information required for maintenance of communications links and networks.



TRAFFIC ORDER:

When traffic flow is heavy, operators at ECCs should handle Emergency traffic first, then call for Priority traffic, and finally call for Routine traffic.Low priority traffic will wait for high priority traffic.

COMMUNICATION SYSTEMS:

The appropriate use of a particular communication system or frequency is a complex issue related to current propagation, conditions, frequency usage, type of message, length of message, operator skill and transmission distance.The choice of a communication system or frequency should be left to the ARES/RACES personnel whenever possible.

***** REQUIREMENTS FOR ALL *TRAINING/DRILL* TRAFFIC

1. Messages must be numbered

2. Precedence will be TRAINING Emergency (TE), TRAINING Priority (TP), or TRAININGRoutine (TR).The ECC generally does not handle Health and Welfare traffic.

3. Handling instructions are not used.

4. Station of origin.

5. Check is not required.

6. Place of origin will generally be COUNTY ECC or other official agencies.

7. Date in Month, Day form.NO YEAR!Example:APR 14.

8. Time filed recorded in the 24 hour system using LOCAL TIME.For example:3:06 PM is given as 1506.

9. Address of person in ECC to whom the message is directed or the job function of such an individual.

10. ALL messages must include the following line:

*** THIS IS A TRAINING/DRILL MESSAGE ***.

11. The message must have a signature.

12. All packet traffic received should be acknowledged.

13. All messages will be in plain ASCII text.



*** REQUIREMENTS FOR ALL *REAL-TIME DISASTER* TRAFFIC ***

1. Messages must be numbered.

2. Precedence will be Emergency (E), Priority (P), or Routine (R).

3. Handling instructions are not used.

4. Station of origin.

5. Check is not required.

6. Place of origin will generally be COUNTY ECC or other official agency.

7. Time filed recorded in the 24 hour system using LOCAL TIME.For example:3:06 PM is given at 1506.

8. Date in Month, Day form. NO YEAR!Example:APR 14.

9. Address of person in ECC to whom the message is directed or the job function of such an individual.

10. Messages must have a signature.

11. All packet traffic received should be acknowledged.

12. All messages will be in plain ASCII text.

ver 10/30/99



Addendum B
 
Sample Activity Log
Name:
Call:

Address:

City:

State:

ZIP:

Op: AB7NV

DateTimeSkillActivityNotes

12 Oct 20011830Z14, 18BBS file and HardcopyPrinted "cookie.txt" recipe file from

SRABBS