Tuesday, October 25, 2016

Remembering Wrigley… a TCP




25 Oct 2016- countdown to this year’s World Series is 2.5 hours to “Play Ball.” Seventy-two hours later game 3 is scheduled to be the first World Series matchup at Wrigley Field since 1945; yep, 71-years. I know Cubs fans are ecstatic that their “Cubbies” are “in it” for the first time in generations. I’m excited, and I’m a Dodgers fan (but have also rooted for the boys in red-white & blue from the northside of Chicago for a long time: my initial game a Dodger Stadium was Cubs vs. Dodgers).
                 
Wrigley Field- under construction
Yeah gotta love fans that are so eternally optimistic (“wait until next year”) and universally positive (“Let’s go Cub-bies”) – unlike some other franchise’s fans that seem to dwell on negativity and aggression (“beat LA”). Wrigley Field is a special place: allow me share memories of my sojourn there.
                  When I was working for the State Historic Preservation Officer in New Mexico, I had the NM Dept. of Transportation as a primary client. Their lead archaeologist (Blake Roxlau) was born in Iowa and raised in the Midwest: he was a life-long Cubs fan. On one of our inspection trips to Lincoln County I learned he’d never been to a game a Wrigley Field. I knew in a heartbeat that we needed to wind-our-way via Southwest Airlines and see some games.
          
Turns out an ol’ NPS Ranger bro (JD Swed) was living/stationed nearby as the Chief Ranger at Indiana Dunes National Lakeshore.  JD was also a Cubs fan (longtime…). Meme & Justin weren’t available to make the trip from the “land of Enchantment,” but JD made the commute into the Second City. We caught two afternoon games: The Cubs were victorious over the Houston Astros (NL Central foes at the time) on day one, followed by Los Dodgers coming to town and turning-the-tables on the hometown crew. After the games we visited some local abrs and eateries: one was Ditka’s, where part way through dinner we noticed “Coach Ditka” had taken up residence at the next table. JD gave him our regards and had a quick chat.
                 
1935
I came to see the games, but as much I also went to see Wrigley Field. It was about 90+ years old and had legend going for it: Babe Ruth & the Red Sox playing the Cubs in the Series, then years later Babe with the Yankees in-the-Series “calling his shot” homerun. I wanted to see if Wrigley Field had the elements to be considered a TCP (“Traditional Cultural Property”). I had posed the question at a training session of the President’s Advisory Council on Historic Preservation, but was quickly shushed by the moderator (at a break he explained that due to the number of Native American tribal representatives present, he didn’t-want-to-go-there). Well, I did and so I did physically. True that TCPs are most often associated with Native Americans and certain other cultural groups, but I was thinking of the elements like
an urban neighborhood that is the traditional home of a particular cultural group, and that reflects its beliefs and practices; a location where a community has traditionally carried out economic, artistic, or other cultural practices important in maintaining its historic identity.”

                  
Let’s face it: Wrigley Field is historic (by U.S. standards & definition), people make periodic pilgramiges to be there, I noticed lots of ritualistic behavior (& imbibing) going on, and lots of what might have been praying. I think it fits. Go CUBS!

Friday, October 14, 2016

Soberanes Fire: my time there...


Our home arroyo (by Meme)
11 Oct. 2016, 11 A.M.- just received a telephone call from Area Code 831 (Monterey County). Since I’d been there just last month I answered (yes, I pay attention to caller-ID) and found that a young lady originally from Santa Fe had been called from a number associated with my LLC @ 4 A.M. It was probably a robo-call, but it spring-boarded me into these reflections:
The phone rang about 8:30 the day after Labor Day; it was Santa Fe Zone inquiring if I was available for an assignment as a Safety Officer to the Soberanes (so-bron-es) incident in California. I soon was scurrying about to get my retiree’s “Casual Hire” approved and bags packed (I’d winterized and cached them the day before).
              

Coastline range
Early flights the next day: the leg into the Monterey Regional Airport I sat across the isle from organizers of a special event that would pose safety concerns & considerations for me in the coming days. More about that momentito.
Picked up at the airport by a driver from the Ground Support Unit; she stayed with me through the check-in process, until I got my own GSU ride (Ford F-150). The Soberanes fire was originally managed by a Cal Fire Type I Incident Management Team (IMT1), and had been going since late July. When I arrived an IMT1 from Alaska was managing the under Unified Command (State & Federal – Los Padres NF). I received my in-briefing from “Team Safety” and learned I was going to be the Safety Officer coordinating safety efforts at the camp established at Andrew Molera State Park near Big Sur. I’d transition with an Alaskan IMT Safety Officer that had been there for several weeks.
A near miss
The incident experienced a fatality (dozer operator from a roll-over) early on: several accidents, mishaps and near misses since were foremost in our risk analysis (due to many narrow, steep, one-way roads) and mitigations (road guards enforcing our one-way travel requirements).



This might be a spot to mention that while I was there this became the most expensive wildland fire in U.S. history (costs now over $250 million). Some may ask, why? From my perspective, there are several factors: the fire being in the vicinity of Carmel & Big Sur (Cal Fire ordered over 300 engines to protect structures); State resources in California are expensive (their contracts call for 24-hour per day pay from portal-to-portal, or from when they leave to when they return home from the incident. Also, when feasible their contract calls for hotel/motel rooms vice camping out at camps & bases. Pretty reasonable when you consider some of the 100+ degree conditions they are asked to perform their suppression efforts); managing a wilderness fire using a confinement strategy means a “Big Box” to geographically hem in the fire, lots of aircraft work ($$$) and plenty-of-patience. All this drives up costs. Has it worked? It remains at 97% contained (10/15 is estimated), with over 1,000 tactical and support personnel assigned  (at one-time I believe it was over 3,000).   
Poison Oak
What were our primary safety concerns? Aircraft usage was very high (as already noted): it is high risk – high gain + drone intrusions at a retardant dip base along Hwy 1 that could have been disastrous; driving and roads were major concerns too. On a day-to-day basis the medical unit was treating a lot of poison oak irritations and the infamous “camp crude” (upper respiratory infection) that seems to love foggy damp conditions, like where our base was located (about ½ mile off the Pacific).


The Best Buddies Ride was the special event referenced above. It featured 1700 participants riding from Carmel south on Highway 1 to Hearst Castle at San Simeon: right past our camp and major ingress/egress points on the busy Saturday following Labor Day weekend. There was a great potential for undesirable conflicts (pods of bicyclists & heavy equipment do not often mix well on narrow curve riddled roads). We were informed that the event sometimes has a medevac necessitating the closure of Hwy. 1 (our escape route), but the event would go on as planned. It did, and without incident.  Yea! https://www.bestbuddieschallenge.org/hc/

We’d had several “near miss” accidents along the narrow Coastal Ridge Road (CRR), but the following day (Sunday, 9-11) was a miss and near fatality: a water tender (WT) working along the CRR rolled off the road and over & over-n-down an 80% slope for 250-300 yards. The tender was stripped of its water tank and the driver was ejected (landing suspended on some brush), with the seat belt remaining buckled. The incident fortunately had a medevac helicopter dedicated for such emergencies (staged at Fort Hunter Liggett), and within well less than a hour the driver was airlifted out and delivered to an ER at a Regional Medical Center in Salinas. As it turns out this wouldn’t be the only time Kern County’s copter would save-our-bacon (next would be a night extraction for a medical condition: presenting like stroke). Night capable helicopters (long-line short-haul), with paramedics, are certainly the way to go amigos. BTW- the WT driver survived with many broken ribs and other painful injuries, but THANKFULLY he is OK (Humdullah!)
The Alaska IMT1 timed-out (3-weeks) while I was there, and were replaced by CA’s Interagency IMT1 Team 4 that I’d worked with last season on the River Complex. They left me “in place” and ordered replacement safety officers for our future transitioning efforts. With fire activity slowing down nationwide, those resource orders got filled sooner instead of later: I had a nice lengthy passing-of-the-baton to my replacement (a retired Forest Supervisor from the Pacific Northwest) and got to come home 2-days early to-boot. Always enjoy getting home safe-n-sound. My thoughts a good wishes to ALL that worked the Soberanes and other incidents this year: GRACIAS!



Over the years I’ve been fortunate to have worked from camps and/or bases at some fairly nice locations (and some less-than-stellar). I must say being at Big Sur was definitely a nicer locale.

Thursday, October 6, 2016

NiXfinity: or my RDK-03060 journey




I had every intention of writing about my recent fire assignment (Soberanes), and hope to do that soon. However, I thought my saga of following the Comcast/Xfinity (C/X) RDK-03060 error message trail might be worthy. Not just for a quick documentation, but it might help along some other Internet traveler.
I have been a C/X customer since 2002, and when I recently returned home from the Soberanes (at Big Sur, CA) I found that when I turned on my TV the screen had an intermittent message: “Unfortunately, this isn’t working
Make sure your HDMI cable is connected to an HDCP-capable device.
Or, if your set-top box has a component video connection, you can use a component cable to connect  to your TV…”
I had upgraded to C/X’s X1 box & bundle earlier in the year and hadn’t seen this message before. I decided to try un-hooking the X1 receiver and rebooting the entire system. That worked until the TV was turned off and restarted – the above message returned. That was day #1.

On day #2, when the “Unfortunately…” message appeared I called C/X customer service. They tried several fixes, none of which worked, then transferred me to Tier 3 X1 customer support. I worked with a technician that updated my systems firmware and tried various system tweaks – none of which worked. He felt a new HDMI cable would be the fix. While working with him, I discovered that by unplugging the HDMI cable and reinserting it in the back of the TV a picture would arrive. He suggested I change the HDMI cable and schedule a technician to bring a new X1 receiver.
On day #4, I made the 40+ mile round trip to C/X and obtained a new HDMI cable. It didn’t correct the problem.  I called Tier 3 X1 customer support (again) and got a different technician (the one I’d worked with was in training the next 2-weeks, and he’d closed out my work order as successful). We started over, unplugging and re-installing everything: it worked until turned-off and re-energized (as it had been doing). The tech was fairly certain a new X1 box would resolve the issue.
On day #8, C/X delivered a new X1 box and got it going: it worked for the day, but the next day it too had the same message and symptoms. The in-home visit tech had started with thinking it was the TV (as one of his Tier 3 colleagues had also suggested). However, after making several tests he had determined it wasn’t the TV. Since it, didn’t work I called all three technicians involved (on day #9) and left a voice-mail message to please call me. It is now day #16 and no call-backs from anyone. C/X did send me an e-mail survey and asked about my willingness to recommend C/X to friends & family: I gave them a zero (and they wondered why).

                  
While waiting for the return call, I did some on-line troubleshooting and found that tis issue is not mine alone. Several discussions and Q/A strings indicate the issue is due to a C/X update sent automatically to systems. C/X techs are telling folks to go out and buy new TV displays (mine was $3,000 – so, no thanks) and do the changes noted above. Eventually these info-strings indicate that none of the fixes tried will work = you have to ditch the HDMI cable altogether and go back to using your component cables (which C/X told me to ditch when upgrading to X1). I’ve gone back to component cables without incident. The question posed by on-line customers asking C/X: when are you going to provide a remedy for the problem you created, has gone unanswered. I find myself reflecting on the hole C/X cut in my driveway asphalt earlier this year when doing the X1 upgrade: they stated someone would be out soon to repair the hole (soon would’ve been 6-months ago), and the above. Now when I see the C/X commercial stating how much they care about customer service I laugh. I wonder how long it’ll be before I get a return call?