Editor’s Note: During the late 1980’s through early 2000’s the CCRA worked with N6VV and the Northern California Packet Association (NCPA) to build out an extensive 1200 baud packet network in northern California. The following article was written by Lew, N6VV shortly after the 1989 Loma Prieta Earthquake.
Notes from the 1989 SF Earthquake from Lew, N6VV
As of today Thursday October 26th, things have started to return to normal around the San Francisco Bay Area. We have learned a lot about the handling of emergency information and Health & Welfare traffic via packet radio.
I thought I would try to get down my thoughts about the performance of packet radio and lessons learned from the recent emergency created by the earthquake while the impressions are still fresh in my mind.
BACKGROUND: The Northern California Packet Association is comprised of and extensive network made up of hilltop node locations and over 30 BBS systems spread from Redding in the far northern part of the state to Kern County in the central part of the state.
The BBS forwarding system employs a 220 MHz and 433 MHz backbone which utilizes 5 mountain top sites and 5 LAN Gateway BBSs. The theory is that each of the 5 LAN BBS systems serve a number of other BBSs on their LAN. The LANs are: NORTH BAY/ W6PW , SACRAMENTO VALLEY/WA6RDH, SANTA CRUZ/ N6IYA, EAST BAY/ N6VV, and a SOUTH BAY LAN with WB6ASR.
The LAN of which I am part of, connects into the Central Valley Backbone which runs the length of the Great Central Valley of California from Southern California to the Oregon Backbone. As a LAN Gateway station, I am responsible for forwarding to the other LAN Gateway stations and to the BBSs on my LAN, which includes: W6FGC, WO6Y, KJ6FY, WB6V, K6RAU, N6OA, WB6ODZ, WB6MIF, N6ECP. In addition since my local node is on the Central valley backbone I also forward North to AL7IN in Oregon and south to K6IYK in Los Angeles.
The Central Valley 220 Backbone is one of 2 trunks to the south. The other is down the Coast Route from WB6ASR and AA4RE.
Recognizing the need for redundancy in the network, a number of backup routes have been created and we have had to use these many times in the past. For example last year, during the heavy fire season, a fire on Mt VACA took out the Sacramento Valley LAN Backbone node WA6RDH-11.
To maintain communications Dennis, WA6RDH had added a 223.54 port on his BBS to be able to communicate directly with N6VV on the East Bay LAN frequency and to be able to pass Inter-LAN traffic without going thru the backbone.
In addition, when selecting 2 meter nodes, considerable planning went into choosing frequencies to provide alternate paths in the event of the loss of the backbone. Most of the nodes in use in this area are triple or quad port nodes and include 2M access into the network. Strategic selection of 2M frequencies has given us the backup which was put to good use during the emergency. More on this later.
N6VV BBS: The N6VV BBS is a 6 port system operating on the following frequencies:
144.99 223.54 433.41 441.50 14.109 21.097
I operate on 2 HF frequencies and provide in addition to N6IYA (14098), N6OA (14107), KB6IRS (14107), N6EEG (10149) the HF Gateway access to the Northern California area.
The system is a 2M IBM PC/AT with 20Meg hard drive. On normal months I handle between 9 and 13,000 messages per month.
BBS forwarding access into our area is therefore via one of the HF Gateway stations listed above or via the 2 southbound 220 links into Los Angeles and the single 220/433 link north to Oregon.
TUESDAY the 17th of October
Like everyone else around here, I spent a considerable amount of time on that Tuesday trying to get tickets to the World Series but by 3:00 PM had decided that I was going to have to content myself with watching the series on television that evening. At about 4:30, me and most of the rest of the office started to migrate towards the exits in order to make it home in time for the TV coverage of the series which was scheduled to start at 5:00 PM local time.
Incidentally, everyone around here is convinced that the World Series saved literally hundreds of lives at places like the Cypress Structure on Highway 880 since many thousands of people around the bay, were doing exactly what we were doing and trying to make it home before 5:00 PM to watch the game. I have driven the 880 stretch that collapsed many times and at 5:00 PM during the height of rush hour there would normally have been hundreds of cars jammed into that 12 block section which collapsed.
I work in Concord only 3 miles from my home in Pleasant Hill so arrived home about 4:45 and walked out to the shack located about 100 feet behind my house, to “check the BBS”, as is my usual habit when coming home.
I was browsing thru the messages going and coming on the system, when suddenly shortly after 5:00 PM my chair started to bounce up and down. At first I thought it was just one of the many little earthquakes that any native Californian has grown accustomed to riding out with little concern.
Suddenly the motion began to get much more violent and things began flying around the shack. A large bookcase to my left fell over and spilled hundreds of books and QSTs across the floor. Loud noises from stuff falling over in my storage area behind the shack convinced me it was time to get out of the building. I dashed for the door and stood just outside the shack looking up at my tower. My main concern at this moment was the tower immediately over my head. The Rohn 45 tower had a 6 element KLM 20M beam and a 4 element KLM 40M beam at 85 feet. The Phillistrand guy wires were alternately snapping and going slack and the beams were jiggling wildly.
I decided it was probably prudent to try to get at least 85 feet away from the immediate area. Dashing thru my back yard to scoop up my 8 year old son we went to the front yard and watched the trees and telephone poles waving wildly in the air. I live on a small knoll and have an excellent view out across the Diablo Valley. For another 10 seconds we stood watching the eerie sight as the whole valley jiggled and shook.
For about 30 seconds we stood there afraid to move. After checking with the rest of the family to see that they were all safe, I ran back to shack to see if it was OK. The power was off and sirens were already screaming all over the area. My neighbors were all out in the streets and some people had their car radios on listening to the first reports. The first serious damage reports were coming in and I heard that part of the Bay Bridge had collapsed.
My first thought was power. I got out my generator and started setting up on the road next to my shack. My neighbors came over and helped me with the gasoline. I started the generator and let it run for a while to settle down. I got out my hand held and began to monitor the 2M repeater in our area. There was a lot of conversation on the air as the hams began to check in. This was a good sign since the repeater is co-located with the nodes that I use for forwarding. It is at a County site which has emergency power so I had assumed that it would be on the air.
In a few minutes I had the VHF/UHF side of the BBS going. Another ham, WA6HAM Steve was bringing over another generator to get the HF station going. The first step was to find out what nodes and BBSs were on the air. I began working my way thru the network to find out who was there. To my horror, W6PW in San Francisco did not respond. In addition the Southbay LAN Backbone node on Crystal peak did not seem to be on. N6IYA the Santa Cruz LAN Gateway was not there. I started to get worried but was hopeful that it was just power that prevented them from being on the air. The SAC Valley stations including WA6RDH were up and the central valley guys and circuits all seemed to be OK.
Without hearing any real news reports I began to assume that the worst areas were San Francisco and particularly the Santa Cruz and Gilroy areas. It turned out that I was right. I began working my way thru the Santa Cruz BBSs who I do not normally forward to because of our LAN Gateway structure when suddenly I got a connect with N6MPW. At least one BBS in that area was on. I started receiving messages from the other SysOps who were doing the same thing I was. We spent the first hour or two trying to put our network back together. WD6CMU from the Northbay LAN sent around a message saying he was taking over Gateway duties for the Northbay LAN. N6MPW took over gateway duties for the Santa Cruz LAN. That meant 4 of the 5 LANs were covered, but we still had no word from Roy AA4RE or Greg WB6ASR from the Southbay LAN. We later learned that the Crystal nodes had received severe damage since they were so close to the epicenter.
I contacted Brad WA6AEO who is the control SysOp for most of our nodes in Contra Costa County and suggested that we put some of our emergency plans into place. We had already set up one node in the south part of the county on 144.93 which was WB6ASRs user port frequency but I could not raise Greg on that port. We were able to move our Berkeley node on BALD to 144.99 which is the user port frequency of both W6PW and AA4RE. This would provide an alternate path for Roy into the network while his 220 access was down.
The channel selection of 2 meter nodes and the frequency agility proved to be vital in reestablishing paths to these locations since Roy has returned to the air and at this time is still using the BALD 144.99 node as his access to the network.
That was the first lesson learned. HAVE SOME BACKUP PLANS for alternate paths when backbone nodes go away !! In our case it worked and all 5 LANs were back on the air within hours of the quake.
I had started to compile a list of BBSs that were on and began to modify my forward files to get traffic to the right general area. Thankfully N6LDL was reachable on the 2M Northbay port of 144.97 and I set him up to receive all San Jose, Los Gatos ZIPs. CMU was taking all the NORTHBAY LAN ZIPS. and N6MPW was taking Santa Cruz. One thing I learned during this rework of the forward files was that I would have been better off to have had independent files set up BY BBS instead of by LAN as it was a painstaking process rekeying all of the ZIP information. In that way I could have just moved my files around by BBS to reflect the crazy 2M forwarding patterns which evolved during the emergency.
By this time the other generator had arrived and I was now up on 20 Meters on the 14109 NET. It was getting fairly late and I just had enough time to fire off a message to Dave W9ZRX that I was on before the band closed up. Sometime around this time K6IYK in Los Angeles connected to me and told me that the Coast route was gone but that the central valley 220 route had survived and to expect lots of NTS traffic. I gave him a brief rundown on the situation and told him that we were ready.
By now traffic was starting to flow all around the network and Health and Welfare stuff was starting to come in from AL7IN in Oregon and K6IYK in Los Angeles. We sent out bulletins calling for a halt to ALL non essential bulletins on the network and I composed messages for the HF Networks requesting the same thing.
Listening to the 2M and UHF repeaters into the Santa Cruz area it became apparent that the voice circuits were a zoo and that if any H&W traffic was going to make it into that area it was going to have to be on packet.
The surviving repeaters were all tied up with tactical information and most of the net control stations did not want to hear about Health and Welfare traffic. Actual fights broke out on some of the repeaters over the handling of H&W traffic and I was very pleased when I started to hear people on the repeaters tell people “PUT IT ON PACKET”. We had let them know that we had established routes into all the affected areas and we started to see traffic coming in from the outlying areas who seemed to be taking H&W traffic off of the 20M nets and dumping it onto the local BBS system.
From my own experience I can tell you that phone service into the 408 area code was very spotty and some areas in the southbay were not available. HF SSB stations taking traffic for these areas had no way to deliver the traffic and most ended up just dumping the traffic into the local BBS system anyway. 415 was not bad after about 12 hours and was returning within 24 to many areas but I tried all night to reach the Santa Cruz BBSs by phone and could not get thru. All during this period I was forwarding packet traffic for hours on end to N6MPW in Santa Cruz !!
By 4AM in the morning I realized that I would have to also modify my outbound forward files and adopted the theory that I should just try to get it out of here to anybody so made heavy modifications to my forward files to get as much traffic to W9ZRX and W3IWI who are usually my best connects on 20 and 15 meters.
As the sun came up and the HF bands started to come alive the traffic began to pore in. ZRX connected to me and had a 2 hour forwarding session. The inbound volumes were unbelievable. At some times I had W9ZRX on 20M, W3IWI on 15M, K6IYK from So. Cal on the 220 port, AL7IN from Oregon on the 433 port all forwarding to me at the same time. I only had 2 outbound ports to try to handle the 4 inbound ports which never stopped. I called for help and remote SysOps Brad WA6AEO and Dennis KA6FUB came over to the station and for the next 48 hours the BBS here was fully manned around the clock. We never went thru a normal forwarding cycle but had to use force forwards to try to stay up with the imbalance in inbound/outbound traffic. The number of messages on the board kept increasing since we could not keep up with it. I believe that the peak came on Wednesday night with a total of about 800 active messages on the system. I had many hours before deleted all my bulletins so all of these messages were NTS.
By the weekend we had handled over 5000 messages which had mostly been forwarded on into the Santa Cruz and Bay Areas. We had recruited a core of local hams to check in and handle the NTS destined for our area but even that was getting out of control. I was actually outside the seriously affected area and had power and phones back by the end of the first night, so I could imagine that the guys like MPW and PW were really starting to get jammed up.
I started to receive messages from several SysOps that they wanted me to stop sending them traffic and one night got a call from Larry WB9LOZ, SysOp at W6PW that he already had 700 NTS messages backed up and could I just stop for a while. I explained to him that the message flow was like a freight train and that we could not just stop at certain points but would have to stop the whole flow. If I stopped forwarding out to the destination BBSs, I would have thousands of messages here and ultimately blow up. We would have to shut it off farther back stream or just shut down the gateways.
We tried to contact KA6ETB the NCN Packet coordinator to see if we should send out a national bulletin asking everyone to please slow down the H&W and eventually one was originated. I knew that it would take several days for an @USA bulletin to make it around sufficiently to have any effect so we had no alternative but to keep on forwarding.
We need to think more about this flood problem and figure out a better solution. I am sure we will be discussing it heavily in the future but we did the best we could in the first 3 days after the quake.
One important lesson learned here in the SF area is that packet turned out to be the most efficient means of delivering H&W traffic and while I have not heard the numbers from other gateway stations, I am now over 6000 pieces of traffic since the quake and I am sure the total will be in excess of 10,000 messages handled via packet. This is quite impressive since this is a tremendous increase in normal packet traffic and the software, systems, network and operators were able to respond wonderfully to this flood of traffic.
I have heard horror stories from the guys who were handling H&W on the HF SSB Bands about jamming and poor organization. I am happy to tell you that other than the normal RTTY Jammers on 21097 (They don’t like us there) we were able to move tremendous volumes of messages on HF Packet.
LESSON LEARNED :
1. You need to have a backup Plan. I list this one first because we had a plan of sorts but had to make a lot of it up as we went.
2. Packet is wonderfully adapted to handling very high volumes of Health and Welfare traffic during emergencies, but probably shouldn’t be used for tactical information handling. Voice circuits are better and the packet channels get jammed up with H&W anyway…
3. Because of networking possibilities, packet networks can respond better than any other form of Ham Communications to changes in the emergency situations. We completely rerouted traffic throughout the entire system in less than 3 hours…
4. We need a quicker way to handle network management bulletins. Maybe we need an emergency bulletin designator that EVERYONE supports, but is not used except under extreme emergency.
5. Every ham who uses a packet bulletin board should become familiar with packet NTS procedures. Under circumstances like this you have to get anyone with a TNC involved to handle the traffic. The vast majority of traffic handled locally at N6VV was NOT handled by our normal NTS liaison people. We were recruiting people off the 2 meter repeaters to help. Fortunately we had a file called HOWTO.NTS in the file section that these people were able to download and read. Instant NTS handlers !! Many of the regular NTS people were working 24 hours a day in Red Cross facilities or emergency centers and never did check in to a BBS. Even with the thousands of hams in this area, we did not seem to have enough to go around. The emergency sites were recruiting hams from as far away as Sacramento to man sites in Santa Cruz.
6. A major problem we had on this end was the misaddressed or non-addressed traffic that required manual intervention before it would flow thru the automated forwarding system. I only had 3 hours sleep by Friday night and the main reason was fixing this mail. Mail simply addressed NTSCA @ NTSCA with no further information was being received here. Each message like this required us to read them and in some cases to have a USPS ZIP code book lookup to get them on their way. When you are dealing with thousands of messages this can be a tedious job. I actually received personal mail addressed N6VV @ N6VV with a list of 25 friends they wanted me to contact. These BOOK type messages simply DO NOT WORK in the packet environment and require far too much manual intervention at the disaster site.
All NTS traffic here and I thought elsewhere was ZIP code routed. personal mail is routed by BBS and ZIP code does not work for it but the NTS ZIP delivery system is well established and each NCPA BBS is provided with a complete list of zip codes for all of northern California and where they are supposed to be delivered.
Messages received without ZIP code, die until manual intervention.
These are just some of the lessons which we have learned. I am sure many more will be thought of in our afteraction meetings.
In summary I think that the San Francisco Earthquake was the first great test for this new technology which we call packet and although I’m sure we will be able to find some faults, in general packet performed wonderfully under what at times seemed like an impossible situation. My thanks to all the SysOps around the country who helped…
p.s. An interesting sidebar. All of these thousand of messages that were delivered were transmitted on 220.90 MHz. I can only hope that UPS will be able to utilize that frequency as effectively as we hams did during the Quake of ’89
On Health and Wellness Traffic
From : WB9LOZ @ W6PW.#NOCAL.CA.USA.NA
To : NI6A.#NOCAL.CA.USA.NA
Date : 900610/0943
Msgid : PY 3248@W6PW, 764@W6CUS $3248_W6PW
Subject : INFO ON H&W MTG SENT TO ME BY DAVID, AA6RM, SF EC
Path : W6PW
I was able to attend the NCPA H&W traffic meeting. It was felt by all of the EC administrators that what is needed most in an emergency packet system is a way to turn off bulletins and H&W inquiries coming into an affected area and to limit the use of selected systems to emergency logistics and outgoing H&W messages. Incoming H&W inquires are inappropriate, especially in the first days following a disaster, because they are normally undeliverable within the affected area due to inoperable telephones and displaced addressees. Someone affected by the disaster would not be at their home but at a shelter or other relocation center and relatives and friends would not know where the affected person was until they received an outgoing message from the individual. Incoming messages addressed to individuals not directly affected by the disaster may be deliverable but are of lower priority and clog up the system, slowing the passing of priority traffic.
We explored some ideas on how this could be done and came up with the concept of putting HF gateways and other principal BBS’s into emergency mode, which would result in the automatic rejection of non-emergency traffic and all incoming H&W inquiries with an appropriate message or prompt to a user attempting to pass other than emergency traffic. The SYSOP would be able to put the BBS into emergency mode as needed. We also identified the need to be able to send bulletins out of the affected area, providing information about the situation.
We discussed implementing two new send commands, identifying the message as either incoming or outgoing emergency traffic, outgoing H&W traffic or outgoing status reports. Apparently using the commands SY and SZ for such purposes would make it easy for the software writers to filter out SB, SP and ST traffic. SZ would be used for the highest precedence traffic, such as emergency logistics and outgoing H&W traffic, and SY could be used for status bulletins.
One way of initiating outgoing H&W welfare traffic is to have it all originate at the shelters or other central locations within the affected area. (We tried this four days into the October earthquake recovery but used voice rather than packet.) Currently the Red Cross uses postcards for this purpose, with an expected delivery within three days. Any packet system used for this purpose would have to achieve an equal or better delivery rate. Evidently there is software available that can preformat H&W messages, so that all that has to be entered is the identifying info on the sender and the addressee.
I hope this summary is useful to you. If you have any questions please let me know.
From : NI6A @ W6CUS
To : NI6A
Date : 900610/2100
Msgid : PN 770@W6CUS $770_W6CUS
Subject : tnx for copy
Larry; Appreciate the copy of David’s synopsis. I did not expect to be able to educate any one anymore (I guess I am a poor communicator) and did not have any high hopes for the meeting, so didn’t attend. I guess things could have been worse.
Yes, you are right, w0rli has refused such a scheme, so it wouldn’t matter if the other sysops implemented it or not, it would bog down at the first bbs, but… didn’t ANYBODY learn anything during the Earthquake.
It SHOULD be clear that
1) The committee was tasked originally to achieve something on improving H&W facilitation via packet not killing it. If it refuses H&W incoming during the first 48 hours then, as most have observed, H&W incoming past the first 48 hours becomes even older and even less relevant. Also the network congestion caused by letting it come in after 58 hours would be logarithmically worse than to let it come in at the beginning.
2) There is no difference between H&W traffic priorities for inquiries if the addressee is a victim or is not affected. The inquirer in EITHER case is worried sick, and just needs an answer. The facts are that 99.9 percent of the inquiries during the earthquake were for unaffected people, yet the relief they felt (even though maybe less than 10% were received before long distance incoming service was restored) is exactly the same as the relief the inquirer would feel if the person was at a shelter. That is, the inquirer feels a need to help and to ascertain Health and welfare status. A message back saying I am ok, is all that is needed regardless if they are at a house or a shelter.
All this seems real logical to me, but either I cant communicate anymore or my brain works too weirdly for others.
You know as well as every other sysop, there was no need for outbound out of state EMERGENCY type traffic nor inbound and the chances of it being so is very very low. It seems ridiculous to me to close down the entire packet network for traffic that will probably never occur.
Realtime bbs links could be useful for direct connect. like the contra costa county linked bbs system, but we are set up to be able to fwd with each other directly not via intermediary BBS fwding.
Outgoing H&W traffic is easy. Just go into a shelter and offer it. We did in Oakland but there was no takers. There was little response in SF as well. Given a larger disaster there would probably be more takers, but tat is a matter of the local ARES group or local hams arranging to go into shelters to offer the service. The BBS system can take the outgoing as it normally accepts “T” type messages BUT IT WOULDNT GO ANYWHERE if they limit P, B, AND T in favor of Z and Y type traffic unless as you say, they make Y type really T welfare type.
Oh well, it just upsets me the more I think about it *-) … packet could get the inquiries across the country if we had guidelines etc. Without it, it will work the way it worked during the Earthquake and MOST LIKELY there will be very little other traffic to handle.
Experienced ECs should know that the only out of region radio needs from their local area would be OES region 2 HQ in Pleasant Hill if they were serving a government agency and/or their County OES. For Red Cross, it may include also Western Operations HQ in Burlingame (which n6iiu BBS acts as a gateway). The BBS at State OES Region 2 is KI6WE BBS and it can be reached via n6vv-2.
State OES in Sacto has requested us to go to Region 2, and not the Sate OES direct in Sacto. This is official RACES policy. Granted if OES Region 2 is wiped out, then there may be a need to talk directly to State OES in Sacto, but if its emergency traffic, it should be done direct, or at least direct to wa6nwe-1 bbs, I would think.
The only scenario for longer distance emergency communications needs, is that of FEMA’s plan for VERY LARGE DISASTERS such as very large earthquakes. Here we are talking about 100 ties greater than the October Quake. If it occurred in the SF region, headquarters would be set up in LA. If it occurred in the LA region, HQ would be set up in San Francisco, thus the furthest packet links would be about 400 miles. Granted that could be done via HF GateWays, but if it was emergency traffic, It would be best to arrange a direct 40 M or 80 M (evening) bbs link of which we have none now. The 10, 15, and 20 M HF GateWays as you know would not be able to handle such short skip and only n6eeg on 30 M would have a chance.
Oh well, maybe you want to pass a copy of this on to Dave, or is it just my normal pedantic ravings? Anyway, Larry, guess I have gone to too many unproductive meetings and seen too many plans and hopes squashed to be as positive as I would have been years ago, about actually utilizing packet in a functional and efficient manner during a disaster. Of course technically there is no problem, the network is there, but people wise, there is no plan, no functional dedicated, nor educated organization to plan it or to effect it, but I give those who attended a lot of credit for spending their time in an honest attempt.
Will probably be moving in about 10 days and the antennas will be down then. If I am still around, I could check in from time to time with the portable, but will definitely send some traffic from Oregon. I need a long rest by the river. 73, don
Msg# : 64174
TR : PY
Size : 7135
From : NI6A
To : NI6A
@ BBS : W6CUS
Date/Time : 0611/1326
Title : Thanks
I understand about the committee. All you can do as chairman is to facilitate the meeting and try to guide it as best you can. Other than that, it would have been dictatorial or “political” or whatever. In a sense, from what I have head from others it could have been worse.
As you have observed before and I agree, if you put a moratorium on incoming inquiries for the first 48 hours, then you are ensuring the inquiries to be old and stale when you deliver them. You also ensure that when the bbs open back up for NTS inquiries, that the system would be flooded even more so than if we would let it come in gradually in the beginning. In other words it would guarantee even a bigger mess and even less of a timely and valuable service than the plan we had before the earthquake (which of course wasn’t really a plan at all). Talk about making some steps backwards…hi.
Of course the above would occur only if there was national agreement and organization that was capable of putting “T” type incoming traffic on hold anyway, which at this time doesn’t exist. Also you would have to have the bbs distinguish between incoming and outgoing “T” type traffic in order to pass the outgoing “T” type and to hold the incoming. Nothing exists so far for that either.
IN regards to “EMERGENCY” type traffic via packet bbs, there should be almost zero need to fwd such. The plan in Contra Costa County is to link the various bbs directly in direct connections for emergency traffic that is no emergency traffic would be fwded from one bbs thru a second bbs to a third bbs, except for County Wide emergency bulletins. All bbs would be using AA4re bbs software capable of multiple connect on the same freq and simultaneous fwding on any frequency.
None of us project a need for long distance EMERGENCY type traffic except to OES REGION 2 HQ in pleasant Hill (KI6WE BBS) which of course is already part of Contra Costas linked nns system. State RACES policy is to have all State OES traffic from our area sent to region 2 and not to Sacto. We are directed to use Sacto only if region 2 is destroyed/disabled. Most of the Pacific Division high population areas are within region 2, hence there may reason for SCV, EBAY, and SF section BBs to set up a plan how to link with ki6we direct if needed.
Going to Sacto is a bit more complicated, but the hoe bbs for State RACES is OESSAC or WA6NWE-1 BBS. Which you might want to make sure can enable you for emergencies if ki6we fails. This type of planning of course has been relegated to wa6aeo, the NCXPN Emergency Packet Coordinator, and he may have some more mature thoughts about this than I.
Only in a major disaster, will there be a need for long distance packet links. FEMA, for instance, has a plan in where a large debilitating earthquake or other disaster in the San Francisco Area would be Headquartered in Los Angeles and likewise a large disaster in LA would be handled in SF. Such a scenario could benefit greatly from packet bbs links direct on HF but only n6eeg has one on 30 m and that is to w8akf near Santa Barbara. 20, 15, and 10 m would be too long skip to do statewide communications, and there are currently no NORCAL BBS on 40 or 80 M (although w6pw, w6cus, ke6bx used to do the SCAL link to KD6SQ and w8AKF on 40M years ago with very good throughput.
The point being, there has appeared no need in the past to do emergency traffic out of state and there is very likely not going to be a need as this is not in any State, county, or City scenario at this time. The idea of BBS fwding emergency type traffic through more than one bbs makes me a bit uncomfortable, and I am not sure what type of emergency traffic some of the ECs expected during disasters.
These comments are based on a couple of reports that I received from what occurred at the H&W/Packet Meeting on Saturday, June 9; but not being there, of course, I may have received inaccurate information. From what I gathered, it still seems that the largest challenge is to educate ECs on what the packet bbs systems are capable of offering, and for the ECs to communicate to the packet association (NCXPN) what they need.
Since WA6AEO is both a packet sysop, a net/rom sysop, Chairman of the NCXPN Emergency Comm Committee, and also a long time ARES/RACES member in Contra Costa County, I will end a copy of this to him as well, and maybe a meeting covering these topics can be implemented.
Walter, I think you and the H&W Committee served an important function. It is obvious to both of us, that packet has allowed us to handle high quantities of H&W traffic (more so than ever before in the history of Amateur radio) in and out of disaster areas; but it is still the local interface (For delivery and origination) that still suffers. This is not a new problem to those of us who have struggled with this for many years, still I think that local delivery is possible (as shown by the great work at w6pw and wd6cmu bbs during the earthquake where close to 4000 messages were delivered).
Obviously, most inquiries will be for those who are unaffected and who are safe. THIS IS ALWAYS THE CASE, BUT IT DOESNT MEAN THAT THE INQUIRY IS ANY MORE INVALID. HERE THE SERVICE IS FOR THOSE RELATIVES AND FRIENDS WHO ARE SUFFERING REAL MENTAL ANGUISH. Their relief is not any different if the person is alright in a shelter or is alright in their home. The point is that they are alright and do not need assistance from the family. Of course, some hams like to put this service down completely by saying the inquirer is some distant cousin or uncle twice removed but in my experience they are MOTHERS AND FATHERS, DAUGHTERS AND SONS who are worried sick. When that worriedness extends 3, 4, or more days and the media has reported casualties ham radio can and has provided a much valued service to these families, and I am for you 100% in trying to achieve this service as long as other disaster communications does not suffer, which I am sure can be achieved; but only so if we have educated, intelligent, informed, and dedicated hams willing to implement a plan. Barring that, it is difficult to watch….hi.
Anyway, Walter, I hope that the above comments reflect somewhat on some of the conclusions came to by the committee. I realize that you have expended a great effort in this regard and are to be congratulated. I hope that most of the participants went home a little more educated as to packet’s potential and perhaps in the future, given enough information and development, some sort of practical service could be planned for and implemented in which families who are separated by commercial communications blackouts for many days, can communicate with each other via our system. The point of NTS, from the beginning was to be there when the chips were down for third party communication, but as you have found out, the NTS leadership really does not intend that to occur. I will take the liberty of sending a copy of this to my SEC, STM, and to WA6AEO, the NCXPN EMERG. COMM. CHAIR. Thanks again for the fine efforts… hope all is well. 73, Don CC: KB6TKL – Chairman, NCXPN
Orientation for Message Center Runners
Thanks for volunteering at the Red Cross Message Center!
The message center is a part of the Disaster Communications Center who attempts to accurately and quickly facilitate communications between the Red Cross Operations Center and the various shelters, feeding stations, first aid stations, government agencies, and other disaster support agencies.
In order to do this accurately and quickly the following points are offered:
1) The message center manager should orientate all runners.
2) All messages should be legible. Look at it before it’s “run”. If it is not readable to you it will not be readable to others. Ask for legibility improvements before you run it.
3) All messages should have a time (also date is helpful). If a time is not entered please write it in. This is most helpful.
4) “Most” messages should have a “TO” and “FROM” name, title, and location. The message center manager should decide whether or not the message is either “DELIVERABLE” or “ANSWERABLE” according to the amount of adequate information.
5) Messages concerning donations goes to FUNDRAISING. ” “FOOD ” ” FOOD PRODUCTS/FEEDING ” “SUPPLIES ” ” SUPPLY ” “VOLUNTEER RECRUITMENT ” VOLUNTEER COORDINATOR ” ” STAFFING & PROCEDURES ” MASS CARE ” ” MEDICAL PROBLEMS & NURSES HEALTH SERVICES ” ” FEEDING, FOOD, FOOD DONATIONS FOOD PRODUCTS ” ” ADMINISTRATION /AUTHORITY ADMINISTRATION
The above are just some of the most common places where runners may have to deliver or pick-up from. Locations and exact titles *WILL* change but the basic departments above should prove to be adequate in almost all cases.
Besides illegible and incomplete messages one of the biggest problems for delay, confusion, and even lost messages is when a message requests a response and supplies from more than one department in the same message. For example if a message reads:
TO: Oakland Red Cross Service Center
FROM: Joan Doe (Notice no Title) Shelter Manager Oakland High School
Request 20 blankets, 20 cots, 3 chairs, 30 diapers, 2 nurses, and lunch for 80 people.
If this message were left on the SUPPLY desk for a few hours in order for SUPPLY to act on the 3 chairs, then the other departments would not be notified in good time or at all. The solution to this is not always simple. This is why we ask all of you to help in making this work by spotting possible problems *BEFORE* they arise and bringing them to the MESSAGE CENTER MANAGER. Thanks for your great efforts.