Packet & CERT - Santa Clara County Ares/Races

Amateur Packet Radio 

and CERT in 

Santa Clara County 

Michael E. Fox, N6MEF 

ADEC/DCRO – Santa Clara County ARES/RACES/ACS (http://www.scc-ares-races.org) 

Jim Oberhofer, NN6PE 

EC/CRO – City of Cupertino ARES/RACES (http:www.cupertinoares.org) 

Inventor of Outpost Packet Message Manager (http://www.outpostpm.org) 

ARES and Amateur Radio Emergency Service are registered servicemarks of the American Radio Relay League Incorporated and are used by permission. 

© Copyright 2012 Santa Clara County ARES®/RACES. All rights reserved. 1

Agenda 

• What is packet radio 

• Why use packet radio 

• Outpost Packet Message Manager & PacFORMS 

• Example: Cupertino ARES/RACES & CERT 

• Example: Mountain View ARES/RACES & CERT 

• Example: Santa Clara County EOC 


WHAT IS PACKET RADIO 


What is Packet Radio 

• One of many digital modes available in Amateur Radio 

• Transmitted information is received 100% error free! 

• Sends a “packet” of data (envelope + payload) at a time 

– Differs from character-at-a-time modes; adds error checking 

– AX.25 protocol: similar to X.25 standard; callsigns for addresses 

– Envelope contains header at beginning and checksum at end 

– Header contains addressing information (to, from) 

– Checksum used to determine if packet was received error-free 

– Payload contains the data to be sent 

Header Payload CHK 

• Can operate as connection-oriented (reliable) or connectionless 

(unreliable – use higher-level protocol) 

• Typically operates at 1200 or 9600 baud 


Some Common Packet Radio Usage Types 

• APRS (Automated Packet Reporting System) 

– Typically used to provide location, weather, short messages 

– Access maps, weather on web or via radio 

– Wide variety of small, portable “trackers” available (GPS & radio) 

– Track vehicles, individuals, … 

Internet 

OR 

OR 



• Keyboard – to – keyboard 

– Similar to text messaging 

– Short, interactive messaging between individuals 

– Connect direct or navigate a network of “nodes” to reach farther 

– O.K. for information message traffic; not good for formal messages 

Node 

Node 

*** CONNECTED to KN6PE 

Hi Jim – Are you there 

Yup - what's up 



• Bulletin Board Systems (BBS) 

– Multiple mailboxes, distribution lists (like a corporate email system) 

– Bulletins (may be organized into topic areas for selective reading) 

– Store and forward – other person can pick up message later 

– May use nodes between BBSs or between users & BBS to extend reach 

– May be networked to other BBSs via RF (or Internet links) 

– May include gateway to Internet e-mail 

– Ideal for larger organizations, multi-user, formal message traffic 

BBS1 

BBS2 

Internet 

E-mail 

RF 

or 

Internet 


Typical Packet Radio Station Components 

Simplex 

Simplex 

BBS 

City or County 

Radio (HT, Mobile, Base) 

Radio-specific Cable 

TNC (Terminal Node Controller) 

RS-232 Cable 

PC Running Outpost and PacForms 

© Copyright 2012 Santa Clara County ARES®/RACES. All rights reserved. 

8

Block Diagram: Typical BBS 


9

BBS Physical Installation (W2XSC) 


Santa Clara County BBS Locations 

W4XSC 

W3XSC 

W1XSC 

W2XSC 

Also: W5XSC 

Training/Extra BBS 

Location Varies 

No Internet required to reach anywhere in the county! 


WHY USE PACKET RADIO 


It’s FAST! 

• Yes, that’s right, FAST! 

• WAY faster than voice! 

• Voice 

– Speak the message, phonetics, copying (legibly), multiple recipient fills, 

logging, duplicating 

• Packet 

– Type it in, press send, walk away 

– Messages are transferred faster than the operator can type them 

– Multiple recipients all get the exact same message 

– Can be received with no operator intervention at all 

• Real world results: 

– At a recent Santa Clara County drill, the county EOC processed over 80 

messages in about 1.5 hours. All were received, numbered, 

acknowledged, logged, printed in triplicate, and perfectly legible, with zero 

errors in either the messages or the ICS 309 Communications log. All 

managed by just one person (and some software). No waiting and no 

backlog. 


It’s ACCURATE! 

• 100% accurate! 

• Checksum in each packet must match 

• Voice: 

– Transmission errors, reception errors, transcription errors, legibility 

problems, duplication errors 

– Fatigue, stress due to high volume, complexity of messages adds to 

probability of error 

• Packet 

– Data out equals data in, all day, all night, all week long 

– Long, complex, technical, high volume makes no difference 

• Real world results 

– Zero errors, ever, when using packet 


It’s DEPLOYABLE 

• Where, when will you need to deploy 

– Hint: it probably won’t have power, phone, Internet 

• VHF and UHF are well suited for field deployments 

– Don’t need special/extra radios, antennas 

– Transmit over long distances using just an HT 

– Much more tolerant of line-of-site issues than higher frequencies 

• Easy to extend with nodes and digipeaters 

• Real world results: 

– An HT is sufficient to connect from most places in Santa Clara County 

– In more difficult locations, use a roll-up J-pole antenna and mast 

– Each city can reach at least two of our BBSs 

– Surrounding counties can reach at least one of our BBSs 


It’s EASY 

• Hardware 

– Just about any modern amateur radio can be used for packet 

• Several even have built-in TNCs 

– Hardware TNCs are readily available (software TNCs, too) 

– Pre-built cables are available at reasonable prices, or make your own 

– Connections are straight forward (radio to TNC, TNC to computer) 

• Software 

– If you can use e-mail, you can use Outpost 

• Other tools are also available, but Outpost is VERY simple to use! 

– If you can fill in a form on the web, you can use PacFORMS 

– The combined solution uses skills we all exercise every day 

• Procedures 

– Outpost can automate many (numbering, acks, logging, …) 

– Simple user interface helps ensure operator readiness 


It Fits our Served Agencies’ Needs 

• The most important reason! 

• Our served agencies have many formal message formats 

– ICS 213 Message Forms 

– SCCo Logistics Request Form 

– City Scan / Flash Report 

– DEOC 9 Hospital Form (several flavors) 

– Others … 

• There are informal message requirements as well 

• Some messages are long, complex (drug names, addresses, …) 

• All must be error free, perfectly legible, properly number, 

logged, acknowledged, tracked, and printed in multiple copies 

• Must work even if phone, Internet and power are down 

– All SCCo BBSs have UPS and backup generator power 


What about Innovation & Experimentation 

• Isn’t amateur radio supposed to be about innovation and 

experimentation 

• Yep! 

• In Santa Clara County, our focus on innovation is on: 

– Radio network design, operations, traffic/channel optimization 

– Software user interface design 

– Data gathering, aggregation and presentation 

– Automation of high-volume operations 


OUTPOST PACKET MESSAGE MANAGER 


Packet Radio and 

Emergency Communications with 

Outpost Packet Message Manager 

San Mateo County CERT 

San Mateo, CA 

25 October 2012 

Jim Oberhofer KN6PE

Topics 

1. Introduction to Outpost 

2. Aligning features with needs 

3. Supporting the mission 

32 An Overview of Outpost Packet Message Manager

Introduction to Outpost 


Overview 


What is Outpost 

• A Windows-based packet messaging client 

• Supports ARES, RACES, and other amateur radio emergency response 

teams and their need to pass digital traffic 

• Helps automate the packet message handling environment 

• Manages all message-handling between you and the BBS 

• Lets you read, delete, create, reply to, or forward messages back to the BBS 


Overview 


Why use Outpost 

1. Leverages the existing packet hardware, network, and BBS 

infrastructure 

• Uses your existing TNC and packet radio equipment 

• Compatible with many existing BBSs and TNC PBBSs 

• Only your packet client (end-user program) changes 

2. Hides the complexity of the packet operating environment 

• Similar look and feel to contemporary email programs 

• Shorter learning curve for packet operations 

• Allows users to… “focus on the message, not the medium” 

3. Implements most local emergency management policies for digital 

communications 

4. Still under active development based on user requests and on-going 

alignment with the Outpost mission 


Overview 


Mission 

The Outpost Packet Message Manager program supports the 

Emergency Communications Packet User community with a 

contemporary amateur radio packet messaging client that 

allows users to focus on the message, and not the medium. 

Goal 

Help get local ARES/RACES teams on the air with digital 

messaging using their existing hardware and BBS 

infrastructure. 


Overview 


Feature highlights 

• Message support 

• Private, NTS, and Bulletin messages 

• Text formatting in a free-form message window 

• NTS Message Maker with ARL message support 

• On-line report builder 

• Address Book 

• Send/Receive Session (connection) control 

• Serial, AGWPE, and Telnet interfacing with over 20 PBBS and BBSs 

• Controls connecting, sending messages to and retrieving messages from the BBS 

• Configurations and Setups 

• BBS, TNC, and Interface configurations 

• message type and retrieval options 

• supports 3 ways for automatically initiating send/receive sessions 


Overview 


Message support 

• Familiar email-app look & feel 

• Separate folders for message 

storage 

• Clear message identification 

(unread=BOLD, urgent=Red) 

• Formal message workflow 

• BBS and interface setups 

• Additional settings control how 

Outpost behaves 


Overview 


Creating Messages 

• Supports Private, Bulletin, and 

NTS message types 

• Message formatting before 

sending 

• Set messages to Urgent 

• Request delivery or read 

receipts 

• Different ways for originating 

messages 

• NTS Message Maker 


Overview 


Viewing messages 

• Supports viewing, printing, 

deleting or saving a message 

to a local file 

• Reply and Forward message 

formatting 


Aligning features to needs 


Aligning features to needs 

Policy: 

Mission: 

Definition: a high-level overall plan that embraces the 

general goals and acceptable procedures especially of 

an organization. 

In a community of packet users, what policies do we 

adopt to ensure order, consistency, and efficiency in 

what we do 

Definition: the task with which we are charged. 

How do we support our served agencies in their efforts 

to minimize loss of life and property, and speed the 

recovery 


Elements of a packet operating policy 

and how Outpost enables them 

1. All stations will identify with a tactical call sign 

2. All messages are uniquely identified 

3. All messages are sent as private messages 

4. All stations will poll the BBS on a periodic basis 

5. All stations will poll for specific message types 

6. All message traffic becomes part of the official event 

documentation package 


Policy #1: Tactical Calls 

Setup > Identification 

Definition: a call sign that identifies a tactical 

location; is operator-neutral allowing the 

operators to change, without having the 

assignment name change. 

General Implementation: 

No readily available and supported BBS offers 

native tactical call support. 

The Outpost approach supports most BBSs; 

connect with the Tactical Call; Outpost 

manages the legal identifier. 

Santa Clara County municipalities are 

assigned Tactical Calls such as: 

• MTVEOC Mountain View EOC 

• SJCEOC San Jose EOC 

• LAHEOC Los Altos Hills EOC 

• CUPEOC Cupertino EOC 

• CUPDZA De Anza College, Cupertino 

• CUPSSA Seven Springs Ark 


Policy #2: Unique Message Identification 

Tools > Message Settings > Msg Numbering 

Policy: Each packet message sent within the 

operational area must be uniquely 

identified. Replies to messages must 

reference the message identifier. 

Implementation: 

•Unique identifiers are generated by each 

Outpost station based on the entered Report 

Settings 

•When enabled, the next “Message Number” 

or “Tactical_ID + Message Number” is placed 

in the subject line. 

•Subject line can be appended to 

or overwritten at message create 

time. 


Policy #3: Send Private Messages 

Tools > Message Settings > New Messages 

Policy: Private messages are addressed to a 

specific station and retrievable only by that 

station. Private messages should be sent 

when the message is intended for one ore 

more specifically named stations. 


•A Private message policy contributes to lower 

channel traffic by ensuring only the intended 

station retrieves the message. 

•This option sets the default message type to 

either private or public. 

•Option can be overridden at the time the 

message is created. 


Policy #4: BBS polling period 

Tools > Send/Receive Settings > Automation 

Policy: Each packet station should poll the 

BBS at a rate sufficient for timely message 

retrieval without creating excessive 

channel congestion. 


•Example: Santa Clara County has 4 BBS’s 

with about 4 to 6 city EOC stations accessing 

each. Cities also have city field stations that 

may be using the BBS as well. 

•A policy of periodic polling every “X” minutes 

allows for unattended operation. 

•Consideration should be given to… 

• the number of stations accessing a 

specific BBS on a given frequency, 

and 

• the phase of the emergency (for 

instance: heavy traffic: longer 

period… light traffic, shorter period). 


Policy #5: Poll for specific message types 

Tools > Send/Receive Settings > Retrieving 

Policy: All stations will poll for specific message 

types. This approach also reduces channel 

congestion. 


•Select the message types that will be sent 

within your operational area 

• Private messages: between 2 stations 

• NTS messages: standard ARRL 

protocol 

• Bulletins: all-station broadcast 

messages 

• Selected Bulletins: specific messages 

found on a public bulletin board 


Policy #6: Documentation 

File > Save All; File > Expert 

Policy: All message traffic becomes part of the 

official event documentation package. 


•Message archiving… 

• Save All: writes a single text file of all 

messages, with embedded Form 

Feeds 

• Archive: writes one or more folders to 

an Outpost archive file. Can be reimported 

later if required 

•Message Logging… 

• ICS 309 Communications Log… 


Policy #6: Documentation 

Forms > ICS 309 Communications Log 


Supporting the mission 


Mission support 


• Understanding the mission and purpose of the agencies we 

serve. 

• Ensure our mission aligns with the needs of our served 

agencies. 

• What our served agencies need from us… 

• message handling 

• Documentation 

• Audit trail 


Mission support: Message origination 

Requirement: Originate messages 

based on the content and format 

of our served agencies. 


•Direct entry with cntl-Tab formatting 

•Cut-and-paste from other apps 

•PacFORMS 

•NTS Message Maker 

•On-line report builder 

•Import text from a file 

•Remote message origination 







•Direct entry (with cntl-Tab 

formatting) 


•PacFORMS 











•Direct entry (with cntl-Tab 

formatting) 


•PacFORMS 






Mission support: Documentation 

Requirement: All packet message traffic must 

be submitted to the EOC for disposition. 


•Incoming message distribution 

•Outgoing message printing record 

keeping, specify # copies 


Mission support: Message Alerts 

Requirement: Prioritize traffic 

according to the needs of our 

served agencies. Identify priority 

traffic on its arrival. 


•Identify incoming urgent messages 

•Set message priorities for 

outgoing messages 


Need more information 

•User Guide… www.outpostpm.org#documentation 

• A complete description of all features, forms, fields, and controls in Outpost 

•HOW-TO pages… www.outpostpm.org/howto.html 

• Specific How-To’s for the most common tasks performed 

•Application Notes… www.outpostpm.org#documentation 

• Write-ups with more details on a specific topic. 

•Troubleshooting page… 

www.outpostpm.org/troubleshooting.html 

•Users group… 

http://groups.yahoo.com/group/outpostpacket/ 


Area: 

10.9 Sq. Miles 

Population: 

59,220 

EXAMPLE: 

CUPERTINO ARES/RACES & CERT 


The Cupertino Response 

Initial Response Assignments 

City EOC Staff 

County Fire 

County Sheriff 

Citizen Corps 

Packet Radio and Cupertino CERT 

• Manage the event (EOC) 

• Inspect City facilities 

• Deploy city resources as required 

• Fire suppression 

• Search and Rescue 

• Public Safety 

• Law and Order 

• CERT/MRC activities: 

• Area Response Centers (ARCs) 

• Organized neighborhoods 

• SAR, medical, care and shelter, etc. 

• CARES activities: 

• EOC support 

• Preliminary Safety Assessment 

• ARC communications support 

• Infrastructure Safety Assessment

Cupertino ARC Strategy 

• Regional ARCs 

– The City has 6 storage containers, called ARCs, that are strategically 

located around the City that contain emergency response supplies and 

non-perishables used by the CERT, MRC, and CARES teams. 

– These sites will be emergency gathering places for the local community 

volunteers. Block Leaders or individuals can request assistance and 

receive information about the disaster at the ARCs. 

– ARC Teams help with: 

Animal Care Documentation Search & Rescue 

Child Care Feeding & Sheltering Supplies Management 

Clerical Support Incident Report Intake Translation 

Communications Safety/Security Transportation 

Packet Radio and Cupertino CERT

Addressing in Cupertino 

A 

A 

A 

A 

A 

EOC 

A 

CUPSSA 

Packet Radio and Cupertino CERT 

A

Cupertino ARC Site 










Situation 

1. Today, Cupertino uses packet to pass digital message traffic 

between Cupertino EOC and County EOC. 

2. There are ham radio operators (some CARES, some not) 

staffing ICS positions at the ARCs. 

3. During a full-scale emergency response, we may not have the 

staffing to cover voice communications and packet support at 

the ARCs. 

4. Some alternatives for ARC communications staffing are: 

• SUVs… but first need to be trained 

• CERT as Packet Operators… with a Ham as a “Control Operators” 

5. Cupertino OES has invested in packet kits for the ARCs 


How will we deploy packet 

1. Operate in the EOC for EOC to County message handling 

2. Start with the ARCs for ARC-to-City EOC message handling 

3. Need to define the message requirements and develop 

message templates for ARC-to-EOC (structured) message 

handling 

4. Leverage the County Packet infrastructure (BBSs) 

5. Continue to align to the state message hierarchy protocol 


Aligning Packet in California 

Logical information flow… 

FEMA 

State OES… 

CA State OES 

Three state regions… 

Coastal Region 

Inland Region Southern Region 

Counties… 

Op Area/SCC 

… 

Op Area/SMC Op Area/Napa 

Local Level 

towns and 

cities 

… 

CBL CUP LGT MTV SJC 

DZA 

GGA 

MVA 

SSA HYA LSA 

Within Cupertino 


Area: 

12.3 Sq. Miles 

Population: 

75,235 

EXAMPLE: 

MOUNTAIN VIEW ARES/RACES & CERT 


Communications Path 

Neighborhoods (CERT Groups) 

FRS Radios 

FRS Radios 

FRS/GMRS & 

Amateur Radio 

Neighborhood ICP 

FRS Radios 

Amateur Radio 

City EOC 

Amateur Radio 

County EOC 


Neighborhood Information Gathering 

• Each CERT Unit (neighborhood) is assigned 

– Unit name 

– FRS channel 

– Tactical Call Sign 

– Message Number prefix 

– Fire Station for backup communications 

• Information gathered 

– Uncontrolled fires 

– Hazards: gas, water, electrical, chemical 

– Extent of building damage 

– # of people injured, trapped, dead 

– Road obstructions or blockages 

– Other threats to life 


How Information is Accumulated 


Form Used for Voice Communications 

• Summary information is 

placed in a formal message 

form 

• Modified version of the 

county ICS-213 Message 

Form 

• Reduces training time for 

new operators 


Packet Version of Form (preferred) 


Ready for Transmission by Packet 

• PacFORMS automatically 

extracts the data from the 

form 

• Only the data is sent over 

the air 

• The form is recreated at the 

other end for display, 

printing and processing 

• Format is compatible with 

standard county ICS-213 

PacFORM so it’s readable 

even if the recipient does 

not have the special version 

of the form 


Automated Receive, Summarization, Display 

Projected onto a screen in the Mountain View EOC 


Video Demo 


Area: 

1,304 Sq. Miles 

Population: 

1,809,378 

EXAMPLE: 

SANTA CLARA COUNTY 


Santa Clara County EOC Radio Room Packet Station 

LAN 

PC1 

Automatic 

Receive 

Processing 

KVM 

PC2 

Transmit 

Printer 

JNOS 

BBS 

• One PC normally configured for auto receive, log, print 

• One PC normally configured for transmit only (auto log, print) 

• Both perform automated printing, logging 

• If a PC fails, one PC can perform both transmit and receive 

• Private LAN connection to BBS (keeps high traffic off the air) 

– Backup over-the-air connection, if needed 


Advanced Packet Logger 

• Written by Andy Rose, KI6SEP (Mountain View) 

• Runs on each Outpost Send/Receive 

– Outpost set to automatically poll BBS at regular intervals 

• Hands off operation 

– All logging and printing is automated 

– Just pull the received messages from the printer 

• Prints multiple copies; routing slip at bottom of page 

• Advanced interactive log with sorting & display options, if desired 

• Dynamic scoreboard-style summary maintains key info like 

– # of messages from each station 

– time last heard from each station 

• Automatically backs up Outpost messages and logs to multiple 

locations 

• … and more 

• For more info, contact Andy 


Advanced Packet Logger 


Thank You! 

Questions, comments, suggestions 

Santa Clara County Packet Network: Michael Fox – n6mef at arrl.net 

Outpost, Cupertino ARES/RACES/CERT: Jim Oberhofer – kn6pe at arrl.net 

PacFORMS: Phil Henderson – kf6zsq at yahoo.com 

Mountain View CERT: Rick Van Mells – vanmells at ix.netcom.com 

Automated Packet Reporting Apps: Andy Rose – ki6sep at gmail.com 

Santa Clara County EOC Operations: Scott Morse – sccdec at mail.com 

Also, feel free to visit us: http://www.scc-ares-races.org 


73

Packet & CERT - Santa Clara County Ares/Races

Create successful ePaper yourself

Delete template?

Save as template?