Firefighter    ■    Power Dispatcher    ■    Husband    ■    Daddy    ■    Grandpa    ■    Crazy Man
Showing posts with label rant. Show all posts
Showing posts with label rant. Show all posts

Monday, January 3, 2022

Culture

There have been a few challenges in this great reset.  But it seems to be working out so far.

Let me just say, though, that in many ways it is a hell of a lot easier to be a new guy who knows nothing, than a new guy who knows things. How much that helps or hurts, as it turns out, is greatly dependent on the culture of where you land.  Between the cultures of the new power company and the new (old) fire department, the differences have been stark.

It turned out that my new power company historically is known for basically never hiring external power dispatcher candidates. If I had known that going in, there's a fair chance that I would not have even put my name in the bin due to the long odds. But as luck would have it, out of a staff of fourteen dispatchers, they had three openings in short order due to retirements and other factors. Normally they could have handled this because they had enough notice, but COVID gummed up the hiring processes and they ended up behind the ball. As a result, when the logjam was broken, they needed one of the three new hires to be experienced so they could get up to speed within like six months or so instead of the normal 18-24 month training period. And that person ended up being me.

Now it is no secret that I think that I'm really good at what I do, but it still felt pretty good to be the #1 pick for this rare external hire out of a nationwide search. Yeah.

Also, for the record, I put my name in the bin for jobs at other power companies in my plan to relocate. I was offered a job at another one just two days after I was offered this one, before I made it a point to call around and withdraw myself from those other processes.

#1 pick for two nationwide searches in the same week? Yeah, that feels nice.

Anyway... culture.....

At the new power company, open discussion and questioning is encouraged.  My new supervisors and coworkers have all been very open to me talking about my previous jobs. They know very well that this company tends to hire from within, there's not a lot of external influence and therefore not a lot of diversity in ways of thinking about how to do things. When I see something that I think could be done better, they have encouraged me to talk about it, which is pretty amazing really. To be fair, after I say "this is how we did it at this other place", more often than not the response is "that's nice, and interesting, you make some very good points, but we're probably not going to change that right away".  And I'm fine with that.  It's just wonderful being invited to contribute ideas that get a genuine listen. What an amazing culture. Open to discussion, challenges to the norm, respectful discourse. Glorious.

At the fire department, not so much.

I resolved from the very beginning to try to not be "that guy", particularly since in this case I was returning to an agency where there was still some familiarity, a handful of guys I worked with in my earliest Fire days are still here. Still.... mouth shut. Smile and wave. Yeah.... I'm not always very good at that.

Fell in with the old guys well enough for the most part, as I had found and then stayed in touch with many of them via social media, so I was not a total unknown to them.  But there are also of course a lot of newer guys here.  "New" being relative, of course, a lot can happen in 20+ years of absence.  Namely, the agency went through a couple of painful Chiefs, the second of which was so bad that as far as I can tell nearly the entire staff threatened a collective resignation to the City unless something was done. The City got rid of that guy, but the culture damage done over almost two decades of poor leadership had taken root. 

Cases in point: One of the first things I helped with upon rejoining was hose testing. Quite a few recruits and fellow probies there. When three of them grabbed LDH to drag them out, I tried to tell them it was easier work if they'd space themselves out. When multiple people grab hose and they're just a few feet apart, the last person ends up doing the actual pull while the others are carrying just the few pounds of hose in their hands. Also, almost no one was wearing a lid when the LDH and attack lines were pressurized. I've personally seen hoses fail during tests and had couplings launch. That crap can kill you. Tried to suggest people get those helmets on. At least one of the (relatively) older members was greatly affronted by me offering advice (some of it potentially life saving), and he talked crap to a few other members, and that greatly set back my reintroduction to the agency. Maybe I didn't need to give advice about the hose pull and should have just smiled and waved, but I was a trainer for too long, it is in my nature. I won't apologize for suggesting lids be worn, though.

People are just showing up and doing their jobs. People are easily butthurt. People are not open to discussion or mutual improvement to the team. Basically, unless you see something so dangerous that injury is probable, it seems that you mind your own business and look the other way.  And sometimes even in those cases....

This is a horrible culture that is going to get someone hurt or killed.

This has also led to a culture of insecurities and jealousy for some. We don't have room for that in this business. Check your feelings at the door. If I do something wrong or could do it better, I want you to tell me so we can have a rational conversation about it, and if necessary we can do some mutual investigation and fact finding to find the best answers. I might have been right all along, or I might be wrong, and there's also probably more information to inject into the conversation that properly sets context, instead of  just operating with the base assumptions that started the discussion, and until we know, we.... don't. That's how we all improve ourselves professionally. It's not personal. That attitude is lacking amongst several members here, and those members cannot process how much of a barrier that is to their professional development. And as such, in their positions of relative experience and authority, they are passing those errors downstream to new recruits who don't know better.

If I could just bide my time and wait until I am re-established here, then I would be able to gradually try to bend the culture back in the right direction. But there's a wrinkle.... my lovely new bride also decided to join the department.  She is totally new to Fire.  You think you worry about your crew getting home safely, and your trainees being able to absorb enough to keep themselves alive? And now that person is your spouse. Pressure? Worry? Yeah.

So in like our second month back, the wife and I were going over SCBA, just the two of us, with the blessing of the on duty captain whom I've known for a long time. Sean comes into the station, sees us on the floor with a pack.  Being a new (and insecure) Captain who wants to assert his superiority and position, he asks if we need help. Now, I know he is insecure and I want to help him feel better about himself, and I don't want him to feel challenged by me, so I gratefully defer and let him take over.

In my best Dave Barry voice, I swear I am not making this up, he starts going over the various components of the SCBA, and when he gets to the emergency bypass valve, he says "you can use this thing to defog your mask if you need to", and then moves on.  Never identifies it by its actual name. Never mentions what it is actually for, never explains how to operate it, never discusses why you might need to use it.

Dude, you're a Captain.  Really?

Mouth shut. Smile and wave. I can fix this with her later. Right?

Then he moves on and shows her the ICM.... the module with the analog and digital pressure gauges, and the motion sensing unit, that hangs in front of your chest, and says "here's the regulator..."

I can't. I just can't. But still trying to defer to his insecurities and not be "that guy", I try leave him an escape. I know people have different names for the ICM... or just don't know what to call it in the first place.

"What's that? We called it the ICM where I came from, but what is it called here, so I know?", and I casually pick up the actual regulator and make like I'm verifying the bypass is closed.

"We call it the regulator. It's the regulator."

"I thought this was the regulator." I hold it up.

Dave Barry voice. I swear I am not making this up. He doubles down. "No, that just goes on the front of your mask, this is the regulator."

I simply couldn't find the strength to keep my mouth shut. "I've never heard that called the regulator. I'm pretty sure this is the regulator..." (holding it up) "... because this is the emergency bypass which allows higher pressure into your facepiece in case the regulator fails. If that was the regulator, there would not be higher pressure available here at this valve."

I honestly don't remember what all happened after that, but I do know that I basically said we would have to agree to disagree and that he abbreviated the rest of the session and bugged out, but let's just say our relationship has not been the same since. I've watched him bluster through a few other situations, and felt bad for him and his insecurities.... to a point. He's had a couple of times to condescend towards me about "you said you have all this experience when you interviewed, but I haven't really seen it". If you knew how much I wasn't saying, you'd know a thing or two about my experience, Sean.

A part of me dies inside every time we run a call and the chauffeur and officer are more concerned with stomping the Q to death and using the airhorn - through green lights at 3AM - than driving with due regard. Dude, let go of the airhorn chain and put both hands on the wheel.  If something goes wrong, yanking on that chain is not going to be the thing that saves us. Did I mention that our rig, the third out of the house on one of those calls, was halfway out of the bay when the unit that responded before us was canceled by Command, yet we responded anyway by carefully not announcing that we were en route? In order for Sean to sit in the front right seat and make noise and feel important for a few minutes?

Smile and wave.

A few months have gone by since these episodes, and the waters are finally beginning to settle. Thankfully the number of guys with butthurt and insecurity are not in the majority, though their influence is still significant.  There are years of poor formation that will take more years to undo, because so many people just turn the other way because what should be a minor behavioral correction with minimal coaching has turned into hills no one wants to die on.

Next task: Convince certain influential people here that 100psi at the tip is absolutely not appropriate for smoothbore nozzles. They train here to operate all lines for 100psi at the tip no matter what hardware is on the end of the line. Getting zero traction on this so far, but I'm a new guy so I can only push so hard without making those waves. Help.

I'm not trying to bag heavily on my new (old) fire agency.  There are a lot of great people here, and it is a great organization overall, but I remember what it was and know where it can be again. There's work to do here.

If you have a good culture, be ever so thankful for it, and cultivate it constantly.  Recovering it when it is lost is an enormous task. I sure wish some certain new fire compadres could know what it feels like to work in a cooperative atmosphere, one where everyone is on the same team and has the same goals unhindered by sensitive feelings, where a conflict is seen as a growth opportunity, not an attack, without the fear that someone is going to undermine them and pin them with gotchas. Bad culture is toxic. It's not entirely their fault, but they have now become the obstacle to progress... the trick is making some of them realize it. If they were to read this, would they even recognize themselves as such.... or just be offended some more and allow the cycle to continue? I want to bring them to the power company job and let them see what it is like to, you know.... actually selflessly work together.

Or, maybe.... maybe I'm just an insufferable know it all pain in the ass.  Can't rule that out I guess.

All that said, overall it is GREAT to be back.

Stay safe out there, and hug your loved ones.

Friday, January 13, 2017

Seasons

It's been a good long time since I've been on here.

Things at my fire agency went absolutely to crap a couple of years ago after a change in leadership.  That's why the fire stories dried up.  No joy in writing about them any more.

Due to the changing tides of volunteerism, the agency ended up hiring more full time personnel several years ago. Management did not do a good job managing the culture shock.

In an established department, you've got seasoned veterans who kick the new guys in the teeth as often as necessary until they learn to respect the job and the agency's history.  Problem was, management basically established that the new paid guys were essentially "officers", even though most weren't.

Being young and full of bravado and feeling the recentism from being fresh out of school and knowing everything, they failed to respect our older volunteer personnel, who had legitimately earned their commissions.  You see, our volunteer officers were not "elected", they were always appointed after meeting fairly strict training requirements.

On paper, paid or volunteer was not supposed to matter.  Firefighters were firefighters, and officers were officers, period.

So, following fire service tradition going back centuries, our volunteer officers began kicking the new paid guys in the teeth when they were dickheads or disrespectful.  The new guys whined, and the new management backed them up, undermining our agency's entire history and culture, marginalizing our volunteer officers.  Unsurprisingly, our entire base of volunteer officers all left within a single year.

And it just went to hell from there.

Eventually I think the Chief started to figure it out, but it was far too late to repair the damage.  The new guys got their own elected officials in office over the Chief, and then the Chief was fired.  The Deputy Chief was promoted to interim Chief, with no desire to hold the job permanently.  The electeds, totally out of control by now and micromanaging everything, drove the Deputy nuts.  In June of 2015 he announced his retirement effective at the end of the year.  By October, they drove him so batshit crazy he gave his minimum two weeks notice and bailed, unable to stand them even four extra weeks.  That pretty much says it all.

Anyway, with the new management in place, volunteers are being phased out.  On paper, they still exist, but as a mere show.  They get used as abused interns, never allowed to think for themselves and never utilized in a way that promotes their growth within.  Turnover is absurdly high, by design in my opinion, to justify the inevitable ending of the program entirely.  Once upon a time the volunteers were trained to be autonomous, to be community-oriented, to know when to go grab a rig, to be trained enough to respond directly to an emergency scene and size things up or make an EMS intervention, and appropriately meld into the ICS structure when more resources arrived.  No longer, as today none of the volunteers can work without direct career member supervision.  I guess this is partly because all the volunteers who had more training than the paid guys are all gone now.

Also, now the agency only responds from two of its five stations.  They closed and sold a sixth one - without telling the residents in that area beforehand - and are using that money to buy an unnecessarily fancy new fire engine.  There are rigs sitting in the other three stations that literally have responded to zero incidents in over two years.  Zero incidents.  The buildings are abandoned, dusty, leaky ceilings unrepaired, falling apart, with trucks mostly stripped of equipment but holding ceremonial spots for fire insurance rating purposes.  Those stations are mere storage facilities now.  Just a few years ago we would turn out rigs from all of our stations for a structure fire, but those days are over.  The agency still has four tankers, but is lucky to turn out even one for a structure fire because there's no one left to drive them, instead relying on mutual aid for water.  Classy.  In fact, the last few fires, water tankers had to be called from as far as over 20 miles away.  Neighbor agencies are already tiring of carrying this one, but the long term agenda appears to be merger into the neighbor city, and liquidation, leaving the rural people hostage to the city's whims.  Because once your agency has been gutted and you have no assets, no money, and no volunteers, how do you restart from scratch if you don't like what the city is offering?

Bear in mind this isn't a tired retread of the paid vs. vollie debate.  This was the second combo fire agency I've worked at.  I've worked alongside paid guys with lots more training than me, and also alongside paid guys whose hand I needed to hold at many calls.  We're all supposed to be on the same team.  This story is one of too many 2-20 hotheads coming in and no one there to teach them respect.  When they spend their days drawing logos with phrases like "Station 54 - The Filthy Few" for a house that runs less than 300 calls a year.... give me a break.  They want to be big city jakes, and their insecurities turned too many of them into dicks,  Of course, when they did get called in to one of the bigger neighboring cities and got trampled on by busy companies that actually do stuff, their feelings were hurt, and instead of learning respect and humility, they just doubled down.  No, not paid vs. vollie, but rather a total loss of culture by flooding the roster with empowered hotheads while hamstringing the efforts from those of us who've actually done this for a few years to shape their character.

Anyway, if it wasn't already clear to you by now, I am no longer part of this agency, and retired from the fire service myself about a year ago.  I haven't ruled out a return in some sort of rehab/canteen capacity with another agency, but I'm kind of burned out by being treated like whale shit on my way out after a 21-year career.  Just not feeling it any more, and that is genuinely sad.

I still work for the power company though.  Always neat things going on there.

Maybe I'll pick this blog up again, maybe not.  But that's where things are today.

Keep the faith, and stay safe out there.

Thursday, August 20, 2015

Fool me once, shame on you. Fool me twice...

It started out small enough, and by the time the first scout unit arrived at the request of the Forest Service, it was still only about 10'x30'.  Unfortunately, the scout unit wasn't a suppression unit, and the Forest Service didn't have resources nearby.

The scout unit thought they could hold it if only they had water, but it was a 20-30 minute response for something that could throw water.  It was worth a shot, and they called in some help.  We got caught up in that request as well.

Things didn't quite pan out as hoped despite best intentions, and it officially became a crapstorm after the USFS finally did arrive to help and promptly tumbled one of their engines down an embankment and into the path of the fire. At least no one was in it, thank goodness.

By the time I arrived with others from my agency, the unnecessary frenzied tone set by the lost engine was in full effect, and there were also at least two ICs.  We parked our rigs and advised up the chain that we were going to remain in staging until there was only one IC.  That took about 20 minutes to get resolved.

When Squad 51 finally got an assignment from an IC that we were willing to listen to, it was to patrol the fire line established on an access road, where the fire had already burned.  Warning bells are going off in my head, because we're uphill of the fire, and the initial burn did not consume all the fuels.  USFS guys are with us on the line, and I foolishly allowed things to proceed assuming the experts wouldn't do this if there was cause for concern.  The rotor was making drops on the far side of the burn, the active front, but lots of smoke is still rolling up the hill and over our location.

Sure as hell though, a little wind shift pushes the fire around a bit, and then a large slash pile lit off just down the road below our rigs.  25' flames are blowing across the road and into the green between us and our escape route.  Every time the wind blows the heated smoke at us, we have to lean into the bottom of the drainage ditch on the access road to get air.  Eyes and lungs burning.  This is genuinely frightening, been quite a while since I had a true pucker moment like this.

About five years ago, I allowed the very same thing to happen.  Got assigned uphill of a fire that sure as hell came up the hill.  Drop and run was the order, and although we lost several hundred feet of hose we were lucky enough to get the rigs and people out without injury.  I said at the time, after that legit scare, that I wouldn't let it happen to me again.

And here I am, eyes burning and tearing up, rubbing them, trying to see so I can drive my rig out during a momentary lapse in the wind when the fire isn't blowing across the road.  If not for the rotor being diverted to drop water on the fire near the road by us, the outcome might have been different.

I try to keep the language clean here, but in this case I think it is warranted to say fuck that noise, never again!  It is trees and grass, we weren't even protecting any nearby houses.  Not worth it by any stretch of the imagination.  What the hell were we ever even given that assignment for, with such high risk and negligible value in holding that line with limited resources?

Don't be afraid to question orders. The 10 & 18 are there for damned good reasons and paid for with many lives.  We all owe it to those that paid the price to heed their lessons.  Fooled me twice, shame on me.  Never again.

Stay safe out there.

Friday, May 2, 2014

Well, now ya gotta do it anyway

Over four years ago I first told you about the bowling alley.

Within a year of that tale, the bowling alley was torn down.  It has been a gravelly rubble-strewn vacant lot for years.  The only thing left is the dead end power pole that used to serve the building.

Within a few months of the teardown, I submitted a recommendation to our planning group to have the pole, with the 3-phase transformers hanging on it, be removed to reduce our exposure to outages.  It is clear nothing is going to be built there for years, and those energized transformers weren't doing anything but asking to be smacked.  This is sort of what it looks like:


And of course, my dear readers, you can see where this is going.

Tonight we got a call, car vs. pole, wires down, transformers in the road, wires on the car.  This is bread and butter so I didn't think much of it until I pulled up the map.

Oh yes, they did.

Two of the transformers are leaking oil on the road, the haz mat contractor is en route, and we've got a hell of a mess out there.  The road is blocked, and it is very late on a Friday night so my dispatchers are still struggling to get enough manpower rounded up to head out there.

My recommendation is now being followed, out of necessity.

That's all this post is, just one long ungracious I-told-you-so moment.  Carry on and be safe out there.




Friday, September 7, 2012

Would you let this man drive?

Just read the latest post at Notes from Mosquito Hill.

Nostalgia again

While I can't quite yet claim to having spent more than 50% of my lifetime as a firefighter, I am pretty darn close.

Replying to the post was not possible, the network here won't allow Disqus through to add a reply. So hopefully mack505 sees this post and knows that I am not ashamed to admit that it brought me silly goosebump chills. Bells and relay switches and halogens and actual mechanical operating devices.... yes! No, the recruit won't know it was a treat until much later, and even if it was explained now he won't be able to fully appreciate it.

Thanks for taking us along for the ride, 505.

Now then, back to business.

Tooling back to my edge of the world in Engine 51 from an errand across the district, I came upon a transit bus stopped in the road, with the driver in back opening the engine compartment. Apparently a minor uh-oh. The bus is blocking a lane of a busy street, and the driver has no eye at all on traffic, just waltzing out there and exposing his behind to oncoming bumpers.

Let's do him a favor and introduce him to how we turn BRTs into big traffic cones, shall we?

So the passengers are milling, and he tells me that the "check transmission" light came on with an audible warning (he said "beeping"), so he stopped right away. He's telling me he isn't sure what to do, as nothing is smoking or leaking on the ground.

Well, how about we start by checking the transmission fluid level, shall we?

I don't know how to do that, he says.

We have a retired transit bus on our fleet that serves as a mobile command post, so actually I have had some exposure to working on an actual bus. This isn't rocket science. Within a few moments the dipstick tube labeled "TRANSMISSION" has been located.

Wait, he says. I don't know if you're allowed to touch that.

I couldn't help the expression that showed. Are you freaking kidding me? What am I gonna do, make the engine fall out? He deflects the silliness and says he'll check with the bus garage to see if I am allowed to help.

It's not as if we're going to get the bus fixed here on the side of the road, it's just basic early troubleshooting. He asks me what it was I was about to do, and I explain it in simple terms, but the way he describes it to his garage tech by radio it is no surprise the tech declines the help. I hope the tech realizes that the driver is whack in the clue department and that there are not random firemen out there just itching to start pulling his coach engines apart for giggles.

The garage tech asks his driver where the bus is. He looks at me for a second and then says he is on whatever route he was on, on the main route, and if you go past McDonalds you'll find the bus a little ways up.

I should have expected things to keep getting goofy, but this was choice. You see, the McDonalds is about three miles back and in a different municipality. God forbid this guy ever have an emergency and have to describe his location.

Looking about 200' in front of the bus at the intersection with the traffic light, I tried to helpfully tell the driver that he was in fact south of the intersection of 45th and Harper, in the northbound lane.  He got back and the radio and somehow melded McDonalds in with the Harper part, making less sense than before.

That was enough, this guy was a real piece of work. I went back to the Engine and radioed for the City PD to send a unit over for traffic control if one was available.  I wasn't going to stay and play this silliness, but didn't feel like I could leave his passengers alone under his care.

So tell me..... how does a guy get his CDL and expect to make his living by driving when he cannot even locate the transmission dipstick let alone know what it is for, and doesn't know where he is with street signs in his face?

Maybe I am expecting too much, but shouldn't someone who is going to make their living on the road be able to hold a shop rag and dig around a little bit to troubleshoot, and know where he is in broad daylight with clear signage?

With our current levels of unemployment, there has to be better qualified persons out there. That was just scary to me.  Certainly this doesn't reflect on all bus drivers everywhere, but their overall group reputation sure did just take a hit.

Be safe out there.



Monday, August 20, 2012

Happy Birthday, Paul

An email came down from the power company's marbled halls that a new security firm was taking over the contract for the operations facility. It noted that nothing would change other than the uniforms worn by the guys who had been working here all along, that they had moved from one company to the other.

As an aside, I find it a little disheartening that our security is contracted out, for the same reason that I dislike our custodial work and other relatively low-paying jobs on contract. I know there are financial reasons for it, but the loss of entry-level jobs into the business makes it hard to grow local, loyal employees. These days most everyone comes in sideways from another career.

At my first power company gig, the operations center was named for a previous longtime CEO who was well-liked and who led the company through a difficult period into an era of lasting success and growth. Story goes that he used to stop by Dispatch pretty much every morning and chew the fat with the crusty dispatchers, hearing the unedited opinions of how things were.

Today you are hard pressed to get high company leaders into Dispatch even once a year, which is true for my current company. And forget getting them into a truck with a crew for a day.

But what was even better about this legendary CEO was his career path. He moved into upper management after stints as Chief Dispatcher and Superintendent of Operations. Before his dispatch career he was a meter reader, worked at one of the coal power plants, drove heavy equipment, worked in the warehouse. His first job at the utility? Custodian. For real. I saw the old company directory to prove it, a genuine success story, and a lifetime career with a company he knew intimately from top to bottom, a company he loved and who loved him back.

I know those days are over, so no use crying about it.

So (back on topic), I arrived at work and met Paul, one of those security guys, and asked him if he was going to look better in his new black duds that would replace these gawdawful green threads. Paul is in his late sixties and probably does not spend much time thinking about uniform fashion.

"I don't know, I'm not going to be wearing them."

(scratching record - full stop)

Say what?

Turns out Paul was informed about an hour before I saw him that he was in fact not going to be picked up by the new company. And why? He was told it was because he had a DUI back in the 90's on his record. A misdemeanor, for which he paid his debt to society, and a clean record ever since. Not good enough. He said they defined their disqualifying criteria as having been in jail.

Now what the hell is this? At my level of security, especially when I worked at the monster utility and had instant unfettered access to remote transmission and generation controls spanning several U.S. states, you'd think I would have to meet a higher standard. I could have single-handedly blacked out a huge chunk of the USA in about 30 seconds. And guess what?  I've been in jail, too.

Yes, when I was 18 and much dumber than I am now, I was stupid and got caught up with some friends in activities which are not germane to the blog. I was arrested, processed, spent several hours in a holding cell. I was never charged with anything, because I was on the fringe of the stupidity, but the arrest is still on my record and has come up at every power company and FD interview. Nonetheless I keep getting hired because I pass the checks and polygraphs (having not been charged with anything helps, of course).

So here we are. I am in middle management like a division chief at my current power company, with the same full access to everything. Yet Paul, who can't get to any of this stuff, apparently can't otherwise be trusted on the premises or in the fleet yards despite almost 20 years of watching the place for us without a blemish.

And you know what?  It was his birthday. He had arrived to find that the office ladies had brought him pie and ice cream. Had a little social thank you event and then went about his rounds. Two hours later he got the call that he was working his last shift.

And then I showed up and cluelessly asked him a silly-assed fashion question. As if his day wasn't just peaches already. Something doesn't add up here, and we are left to wonder if the new company didn't want to assume Paul's upcoming retirement costs or something equally cold. Sounds like the jail time thing was just an excuse.

Happy birthday, Paul.


Saturday, June 2, 2012

Genius Fail

So, we've got a guy who is not paying his electric bill. It is months and about a grand behind. It finally comes to the point that we cut him off, and a serviceman goes and boots the meter, mission accomplished.

Not so fast.

Because of previous drama at this address, a meter tech went by there to check things out a few days later. Found the lock ring and boot on the ground, meter back in and spinning. This is called a "self-restore" and a "tamper", which is an automatic $400 fine. Plus, we cut you off "more permanently".

So the next day, one of our nicest and most laid back servicemen, Paul, arrives in Truck 575 to cut this guy off from the pole's service drop. No one is home, but he chats with an elderly neighbor lady who sees him and comes out to visit. We're the Good Guys, after all. Service dropped, he's done and on his way, mission accomplished.

Not so fast.

Our customer service department gets a call, the recording of which I have not yet had a chance to hear, but the notes tell the story. Apparently the homeowner called in and said he was out of town but had heard from his family that the power was cut. That is to say, 217 members of his family. Yes, that is the precise number of people he claimed were at his home during a family reunion gathering, which was ruined by the power being cut off.

Aside #1: I had about 40-50 people at my house for a Memorial Day gathering. I actually did try to count once but couldn't do it. And I was actually present. How he got 217 while not physically present is an amazing feat.

Aside #2: If this family reunion drew 217 people to his home, then why precisely was he himself as host out of town during such an important event?

Aside #3: His house is 1080 sq ft. If all 217 were inside, they each individually had about 5 sq ft of personal space and were very quiet while Paul was there.

Aside #4: And where did those 217 people park their cars, anyway?

But wait, it gets better.

Dirtbag went on to claim that his grandson had approached Paul to ask "what was going on" when Paul went off and "smacked him with a wrench". He says the grandson is in the hospital and will incur medical expenses, and that a police report has already been filed with "80 witnesses".

Oddly, the brothers in blue did not come to arrest Paul on an assault charge, or even try to interview him, or even call any of us at all for any reason. Curious.

The first Paul heard about it is when I asked him if he carried a wrench on his service truck. A little crescent wrench, he said, that rarely gets used, why? Oh the fun we had telling him all about his violent ways that he kept hidden from us. He must have been plenty mad at the dirtbag's family, because he has no memory of the event at all and obviously blocked everything out except the nice chat with a little old lady in front of a small empty house.

Um, dirtbag, we're the power company, not plumbers. Our one-man service crews don't carry weapons-grade wrenches.... anywhere. Now if you piss one of our guys off you might get brained with a hotstick or something.

A wrench? 217 family members? While you're not home? That all stayed hidden? 80 witnesses? And no arrests?

I've stopped laughing, because it is absurd to the point of tragic. Good luck dirtbag. We'll probably bill you for any legal expenses you incur on us, on top of the arrears and tamper fine. Genius, you FAIL.


Monday, April 9, 2012

I Need a Bigger Hammer

So I am at home dawdling around when my Mayberry Minitor goes off. Diabetic. I skipped on over to Station 51 and picked up the engine to go lend a hand as it was relatively close to 51's. It was an uneventful routine diabetic call. Shortly after the Medic finally arrived from way over yonder in Shiloh, Mayberry banged out another run, a low-priority trauma.

Now, Mayberry only does 120 or so calls a year, so two in the same day is quite uncommon. Two on top of each other is fairly unheard of. Shiloh Medic 11 released us fire guys to the new call as the incident was stable. Medic 12 was assigned. Before we could get out the driveway, there was yet another EMS run elsewhere in Hazzard County, and Medic 12 was diverted. Medic 13 and 14 are all that's left, and both are staffed by callbacks and volunteers. And it is the middle of a weekday when personnel resources are low. Medic 11 directed Hazzard 911 to get us Medic 98 from our side of the line if they heard nothing from the remaining Shiloh ambulances in five minutes.

Well sure enough, five minutes went by. We arrived at the new call and found that our low priority fall was actually an oh-crap trauma call. Hey guys, do we have an ambulance yet?

Then we heard tones on our side drop for Medic 97, dispatching them Code 1 to "Move up for coverage into Hazzard County".

WTF? 97 is farther away than 98, and what's with this generic "move up" thing?

Our dispatcher then elaborated for Medic 97, saying that they got a call from the local private BLS ambulance service. Seems that instead of going 911 center to 911 center, Hazzard 911 called the non-emergent transport service in our county for a Code 3 call. They in turn called the 911 center, and the result was the non-committal and somewhat vague move-up request. A lot was lost in translation, you might say.

Radio traffic cleared the confusion fairly quickly after that and Medic 98 started our way as the closest unit, Code 3.

All said and done, it was 55 minutes from initial Hazzard County dispatch until Medic 98 from our side arrived, though it was only a 15-mile country drive.

ARRRRRRRGH. Why is it so damned hard? I am positive that if I sat in with the Hazzard dispatchers I might understand what is going wrong. But to fix it? This is more than procedural. It is cultural, and I don't have a big enough hammer to swing to change that.

Grit teeth. Keep calm. Carry on.


Friday, February 24, 2012

UnionThink

Can't rule out making some haters from this, but I haven't ranted for a while.... this blog used to be all about ranting and I just haven't had much to rant about since getting into my terrific new job. Summarily, the posts have thinned out to the remaining non-rant topics, and the readership has subsequently dropped. So... rant time!

UnionThink is the warped, disconnected from logical reality way of thinking that doesn't come naturally from the workforce. It pretty much only appears from union members, due to the evolution of unions from an umbrella of protection to a confederation of greed. I understand the need for protection. I've been a dues-paying member myself. If only protection remained the mission. In fact, I've never heard of a union having a mission statement to occasionally verify their bearings and purpose from. Any you know that have one? What is it?

Don't get me wrong, not all dues-paying union members are like this. I am hopeful that most aren't. But nearly all people who do think this way are in a union, and that is where they picked it up. The same way my oldest daughter, who is stunningly beautiful and freak-out intelligent, recently went totally off the rails after a couple of years of bad friend influences despite our efforts. Yes, prevention may not be possible.

Here is the microcosm seed for the rant. The working agreement between my outfit and the IBEW local states that overtime must be shared equally, but does not get into any specifics of how we make that happen. It is quite ambiguous in its definition.

The way we've been managing overtime for years is to keep track of how many OT hours you have accumulated on the year, and release a callout list every week with the lowest OT hours at the top and highest at the bottom. When you have a callout, you start at the lowest hours guy and work your way down until you get someone.

The problem is, some guys frequently don't want OT, or they like to "cherry pick" their OT by asking what the call is. These guys end up at the top of the list because their acceptances are low. Thus, we end up wasting our time on every callout by going through the people who don't answer or say no, and wasting our time describing the incident to someone who only wants the "good" ones, before finally getting someone to take the call down somewhere past the 5th or 6th person.

Since the rules are ambiguous, we are proposing a change. We are being nice and proposing it to them even though the agreement definition does not require us to, and there is no doubt it would survive arbitration. The change is a rolling callout list, and requiring a simple yes or no response without discussion.

Now, I take my callout list and start at the top. If I get the 3rd guy to take it, that is where I will start my calls on the next incident, on the 4th. This spreads the number of callouts to each employee perfectly evenly, and it is up to the employee to take it or not. This saves us time, as we get someone on the road earlier without the guaranteed initial nuisance calls. People with their power out will appreciate that.

This change will also vastly improve some callout acceptance percentages for my guys. For example, I've got one guy who hangs in the middle of the pack who has been working a great deal of OT and actually worked the most OT last week by a wide margin, but relative to how many calls were made to him, his acceptance rate was below 30%, partially because he was worn out and had to say no here and there. Another guy farther down the list who has accumulated his OT by being held over instead of called out has only been called three times, worked two of them, and has not willfully contributed much on callouts historically. Yet, his acceptance rate is 67%. Where's the justice? My hard worker is getting dinged on his performance even though he is by far the better of these two.

Under the rolling list, my hard worker example will get called fewer times and not have to refuse so many, forcing his acceptance rate up without any change in effort on his part. The no-OT people will get called vastly fewer times, and the cherry pickers will be forced to stop cherry picking because (a) they won't be told what the job is first, and (b) the calls will be fewer and far between and they better say yes now and then to get the OT.

So we take this to the guys, and they don't like it. They reason that if you don't have as much OT as other guys, it will be harder or impossible to catch up. Also, with the calls for those at the top farther apart, there will be less chances of them getting calls in the time window that kicks in their premium pay rule.

As a side note to the change, we are also invoking a callout exemption for certain predefined emergency events, where the closest serviceman will be called without regard to the callout list at all. But, the emergency event has to be one we've pre-defined, to avoid claims of gaming the system for anyone. Emergencies are pole damage, wire down, arcing/fire involving equipment, structure fires, and as requested by 911.

They perceive this whole thing as what we are taking away from them, as if it was an evil scheme because managers hate union employees. Where in the rules does it say we are responsible to make sure everyone works the same amount of OT despite the inconsistent OT behavior across the ranks?  The rules talk about equal OT opportunities, not guaranteed OT equity.

Insert reality here. Let's try to remember what we do, why we exist, and who we work for.

We keep the lights on.

We exist to keep the lights on.

We work for the people whose lights we keep on.

The new callout procedure will help us get personnel on the road earlier, especially in emergencies, and will save us money by eliminating the rules nuance that some of the guys play to get into premium time situations. Premium time will still happen, but it will be nearly impossible to "arrange" it any more. We are making OT available to everyone as fairly as possible, and it is up to you, the employee, to take it or leave it. It is not up to us to help you catch up if you get behind.

Faster response, save money. Wow, imagine that. As managers, that's in line with what we are charged with. We know our mission.

Some of my union people have forgotten what we do and why we're here, and only concern themselves with what they feel entitled to, especially if a change reduces that "entitlement".

That is why unions are broken. And it's too bad, because they once had a noble and necessary purpose. Sadly, UnionThink has detached from reality.

The new callout procedure will probably go into effect anyway, because it is the right thing to do for the ratepayers. Because in reality, it is the ratepayer that pays us money and actually has an entitlement to what they pay us to do. That's reality.


Tuesday, December 6, 2011

Charlie Foxtrot


Engine 54, Engine 21, Engine 51, Medic 97, traffic accident.....

This is in the middle of 54's area. 21 will come from the north and I will come from the south in 51, to meet at the scene if 54 still needs us.

The next update has a chilling effect.

Rollover and over an embankment, six patients, some ejected. However, dispatch does not actually know where the scene is. The call came through Hazzard County 911, and Mayberry FD is already looking for it on their side of the line along with the Mayberry ambulance service.

The place they dispatched us to is associated with info that Hazzard County gave our dispatchers regarding a cell phone ping. But then our dispatchers mention a road name that was in the conversation that is nowhere remotely near where we've been sent. In addition, the caller is apparently one of the patients, and is describing terrain in no-man's land way down south that fits with the alternate possible location.

54, 21 and the medic will continue to the original scene to check, but the new spot is now behind me and closer to Mayberry. I divert to the new location, which will make me drive back right past Station 51, and flop from our TAC channel over to the Hazzard County channel to see what they know. Not much, except that the Hazzard County ambulance is already on scene asking for assistance yet no one seems to quite know where they are or how to interpret their directions. Units are scrambling to communicate on our TAC channel, Hazzard County's dispatch channel, and a shared inter-op channel that we should all be using but not everyone has access to. This in addition to the fact that we're on the fringe of radio coverage for any of these channels.

54 and 21 arrive, UTL. 21 returns, and 54 starts my way with Medic 97 right behind them.

I arrive at the end of the world, where roads stop having reliable names. A couple of Mayberry units are there. The Mayberry Chief hustles up to me to let me know a second Hazzard County ambulance just went by them a few minutes before, but they don't know where it went.

Seriously? You didn't think of following the medic if it seemed to know where it was going? Oh well, this is their call, we are the mutual aid, so I tell the MFD Chief that we have another engine on the way and ask how we can help.

He gives me a blank stare for a half second, and then as if he didn't hear me, he asks me where the call is at and what we want them to do.


We have thus descended into Charlie Foxtrot status.

We thought it was their call, and they apparently thought it was our call. No one has Command, no one knows where the ambulances are, and everyone is scattered on three radio channels.

Cue the Southwest Airlines catchphrase: Wanna get away?

We are - in our present literal location - technically in our district by about 15 feet, though the roads into no-man's land head mostly into Mayberry territory. This could be anyone's call. But OK, I can take it.

Now with a reliable starting place to work from, I managed to get enough information from the ambulance to guess where they are, and with that, we're off into darkness.

After about five miles of that we come over a rise and find an ambulance coming toward us. Great, are we ALL lost?

No, as it turns out, this medic has two patients aboard. The other Hazzard medic has one patient aboard and is coming up behind them. There were never more than three patients, they are all loaded, and there is nothing left to do. They thank us for showing up, and off they go to the hospital.

You could just sense the deflation of everyone's adrenaline when I got on the radio and told everyone to just go home.

So, what happened?

True to past performance, massive communication breakdowns between 911 agencies. Hazzard County 911 gave our dispatchers an address near a cell phone tower in our area, and the other road names out of our area carried no meaning and were ignored. We got sent to the tower. The tower.

Too many radio channels, with too many people talking on them. The Command vacuum empowered everyone to chatter until confusion reigned.

The first unit on scene failed to initiate Command. The first officer on scene also failed, as did the first Chief. It should never have fallen to me as first-arriving M/A representative to recognize that and try to fill it.

We're not perfect, I make plenty of mistakes, but this Charlie Foxtrot was worse than usual, and oh-so-preventable with basic communication skills.

It could have been worse, I guess. Argh.


Tuesday, April 12, 2011

Don't Be Owned

Originally posted 9/12/2009, removed during a spate of paranoid content cleanup 5/26/2010, and now re-posted after some review and editing.

My company isn't unlike most electric utilities in North America, belt-tightening and cutting back everywhere in the 15 or so years following deregulation. Maintenance deferred, projects dropped, upgrades delayed, and my personal pet peeve... strict adherence to lowest bidder crap instead of paying a bit more for something of exponentially more value.

C'mon... in real life, if you have a choice between a truly great product at a certain cost, or a lousy crappy one for a little less, you put out a little extra and get the job done right the first time, else you pay for the savings later. Usually you pay more than you saved.

Some of us know that.

The company does not. Lowest bidder. Least cost. Period. And we continually pay for it through all available orifices as well as some new ones created for the situation. Overtime, emergency outages, repairs, lost time from dealing with crap. You get the idea.

That wasn't really the rant I meant to share when I started, though.

So, due to this lowest bidder - least cost - maintenance deferred frame of mind, One of my guys gets yet another routine alarm on a high voltage circuit breaker that is low on its arc-extinguishing internal gas (SF6).

He refers to the callout list. It's after-hours, you see. And these breakers can't be allowed to run out of SF6 gas while in service. They will either automatically trip before the gas gets too low, degrading the grid slightly, or they will "block closed", meaning if something happens that would normally trip this breaker, the trip signal will instead be sent to every adjacent breaker. It puts a big dent in your grid when you get a breaker fail operation like that.

So, (once again) due to this lowest bidder - least cost - maintenance deferred frame of mind, there are not very many guys assigned to this area any more. They're not being replaced as they retire or quit or move on. Three guys (including the designated on-call guy) don't answer calls to their home or cell numbers. The one guy that does answer is with his wife at the hospital. Bless his heart, he volunteers to go if we really need it. To hell with that, I'll see a substation burn violently to the ground on my watch to teach this company a lesson before I pull a guy from his sick wife's hospital bedside.

And let me not harp too much on the good old days, when we didn't have an "on-call" guy, we had an on-duty guy assigned exclusively to a trouble truck and waiting for action, fire department-style.

Grrrr.

So, anyway, I call the field supervisor for that area.

Field Supervisor: Hello?

Grumpy Dispatcher: Hey, this is Grumpy, Shift Supervisor at the ECC, We've got a critical low gas alarm at Outback Sub, and my dispatcher can't raise any of your area guys. You have anyone else available or know how we can reach your crews?

FS: Really, you couldn't get Tom or Dick?

GD: No answer on home or cell. we got Harry, but he's with his wife at the hospital and can't go.

I didn't reveal that Harry offered to go anyway, lest this guy glom onto that idea.

FS: Low gas, huh? Well, I don't have anyone around here, I'd have to call someone on OT from Far Away Service Center, that's three hours away. It'll probably be fine until morning.

An aside: I love that our phones are recorded.

GD: All right then, I understand you're assuming responsibility for this incident, and are choosing to defer work on the critical gas alarm until tomorrow. If anything worsens, can I call you?

Silence ensues.... field boss just remembered that our calls are recorded.

FS: Well. ........ You know ..... you know, let me make some calls and see if I can reach anyone.

Uh-huh. Go team.

GD: Sounds good, I'll wait to hear back from you when when you've assigned a crew.

Don't be owned.

If I had let this guy put off the work and something blew up or got someone killed, you know where responsibility lies? The Dispatcher is In Charge. And as the Dispatcher's Supervisor, I am In Charge-In Charge.

When stuff has to get done, make it clear where responsibility lies. I took that burden off and placed in unequivocally in his lap. He knew it, and he knew why. He didn't want to bear that liability. Guess what Captain Cavalier, I don't either. They pay you field supervisor pay. Go earn it. Find your guys, and get it fixed.

I'm sorry about the cutbacks and all, but no part of the cutbacks includes the requirement that I retain the liability for getting people killed or blowing stuff up simply because you couldn't/wouldn't do your job. You see, despite the clear transfer of the burden to the field boss, I would still be held at least partially accountable for not pushing harder and finding someone somehow to get it done. Frankly, spending 45 minutes on the phone and playing voice mail tag is not my job. We are running critical national infrastructure. When I want help, I want it right now. If I can't get it, I will make the boss of that area assume that burden. If he doesn't like that, maybe he'll ensure his guys aren't impossible to reach in the future, huh?

Captain Cavalier shouldn't tolerate being owned by me, either, He should be using the same approach to his bosses to put responsibility where it belongs: Sorry boss, I can't help the OT costs, because you won't hire help and we're behind on scheduled maintenance, so stuff is breaking all around our ears. If we fall behind, and especially if something big breaks because of it, we get fined big bucks.

Push responsibility where it belongs. And deal with it if it is truly yours.

Don't be owned.



Wednesday, March 16, 2011

No! You're Doing it Wrong!

Originally posted 7/28/2009, removed during a spate of paranoid content cleanup 5/26/2010, and now re-posted after some review and editing.

I apologize if this post offends, but it is how I feel right now. I get a little punchy after these calls.

First off, if you're going to end your life, you should realize how few will seriously have sympathy for you. They're not going to cry over your grave with a special leaning towards how wronged you were and how they wished they had done whatever differently. Or, if they do, you won't be around to know about it, so what's the point? This helps you how?

The mess you create, the pain, the baggage of closing out your story..... it is very selfish to unceremoniously dump your problems and obligations onto others by leaving them behind like that. I understand you have issues. I have had issues too. Issues I wouldn't seriously mind escaping from. But taking the final exit on purpose is seriously inconsiderate, to put it lightly, and that is the main way you will be remembered. Just so you know.

If you choose to pop a cap into your brain, it will make things much easier on your local emergency services if you do a little anatomical research first. Find out which part of the brain is important, and aim there. Aiming elsewhere usually will still do the trick, but on a much slower and more painful schedule. What could have been a tight, clean operation requiring only the intervention of law enforcement and ServiceMaster is then extended into a major operation which ties up an ambulance and its medics, a gaggle of firefighters to assist, and in some cases, even more firefighters to set up and monitor the LZ for the helicopter, not to mention the helicopter itself. All of these resources could have been better utilized to save the lives of those who want to still be alive.

Lastly, if you are ever dealt the agonizing hand of being present or arriving to find that someone else has taken the final exit, a final pointer to speed the response of help:

Our safety comes first. Until we know the scene is safe and that the person is not actively still trying to die and willing to kill anyone who attempts to prevent that attempt, we stay out and wait for law enforcement. We can act on our discretion if we get assurances from the dispatchers that the scene and the weapon are secured. It is not helpful to tell the dispatcher that someone has been shot and then hang up without providing all the details. It is not helpful to ignore the phone when the dispatcher calls back. Result: We wait up the road until our brothers in blue arrive. So, stay on the phone and answer all questions to get the fastest intervention.

A final rebuttal to myself: Actually.... doing it this way provides an excellent candidate for organ donation, leaving us a short-term viable patient so steps can be taken to save the lives of others. If that is your plan, I guess this is an example of doing it right. I sincerely and fervently hope that the person who inspired this post did not have any conditions that prevented this from happening. If it all works out, I guess we firefighters are OK with going through all that to save other lives, but the preferred alternative is to ask for and get help. Those resources are out there for the finding. It is better for all involved if you just stay with us.

Thanks.



Wednesday, December 29, 2010

It's Just Not the Same

Once upon a time, my current agency was all-volunteer. There was a lot of overhead and administrative work to do, and a lot of equipment and facilities to maintain, so the department hired a part-time Chief. The Chief ultimately was also hired by a neighboring agency to be their part-time Chief, making for what amounted to a net full-time position. Still more help was needed. An Assistant Chief was hired full-time by my agency to help the part-time Chief. Then an admin assistant. The other agency brought on an admin assistant. Then each hired a single full-time Captain.

This genealogy is getting boring, sorry. Today, the two agencies have been fully merged, there is one FT Chief, two FT BC's, three FT Captains, five FT firefighters, and three FT admin assistants. We're still mainly a volunteer agency with an authorized force of around 60 members, but with the thinning of the local ranks, of the type that we're seeing across the country, a lot of work that needed to be done to keep up is now being done. Not just facilities and apparatus, but training mandates and the like. It was a couple of years ago that we started staffing one of our stations 24x7, and a second one just came online as a 24x7 house as well.

This was supposed to be a godsend for the volunteers. It was made clear that the career staff was there to relieve the volunteers. Relieve them from long post-fire equipment cleanups at 3AM. Relieve them from tedious weekly apparatus maintenance inspections. Relieve them from housekeeping duties. Relieve them from the tiresome 2:34AM "help I have a sideways nosehair" medical runs. Relieve them from state and federal mandated documentation tasks, equipment inspections and re-certifications, training development plans, etc. etc. etc. etc. ad nauseum.

But what did we get? About half of the longtime volunteers have subsequently left us in the past year or so.

It seems many felt sidelined about not running first due calls any more. Responding to the station and only needing to standby as staffing backfill. This didn't do it for them any more.

In my first gig, we volunteers were always expected to backfill for EMS runs, to take the second call that might come in. And of course for major incidents it was grab the second, third, fourth rig, etc, and go. This is what we did, providing backfill most of the time, and we were happy to help. It wasn't bad duty, really, coming down to the big house and spending an hour or two with our brethren and maybe drilling a bit while awaiting the return of the ambulance.

Now here in my latest gig, it seems these volunteers we lost recently were not happy with backfill. No matter that our service area enjoys faster and more organized emergency response than ever. They would rather have the career staff taken away so they themselves can drive big red trucks and be heroes, but before the FT staff got beefed up, they bitched about the crap work.

One of the guys posted to his Facebook status shortly after resigning, "Quit the Fire Department. It's just not the same any more".

Boo-freaking-hoo. Are you kidding me? Get over yourself. Honestly.

No one was kicked out from the calls or the duty shifts. Anyone is welcome to work a 12 or a 24 with the career staff or even ride out with the City medics, and get the fairly generous stipend that comes with it. Heck, for that matter, feel free to take a one-off part-time shift vacancy and get paid an hourly wage for it. If you like playing fireman, all you have to do is show up.

At whatever point it became all about you, because you only wanted to be the big boy driver or officer, it was time to show you the door.

The career-minded volunteer probies who have joined to fill the holes were happy to see the vacancies open up, to be sure. And while those probies certainly are a lot of work, at least they want to be here.

So, thanks for taking your leave, disgruntled volunteers, leaving the rest of us career and volunteer alike free of your collective whiny self-serving burdens so that we can do what we are here for: Save lives and property. Even if my contribution is often just waiting for the next call.


Wednesday, December 1, 2010

Bureaucracy

The power company has mandatory safety training annually.

This is good, no? Of course it's good.

It's just that, in regard to their requirements for my job in the control center, I am already trained well in excess of power company standards in all the areas they are worried about through my fire department gig. Now if I was a field grunt, the story would be different. But, I'm not.

I've ducked the mandatory power company training for years, leaving them with a fresh photocopy of my most current EMS cert, professional caregiver CPR cert, and Haz Mat Ops cert every December.

Until this year. The bureaucracy decided that it was not going to be flexible this year. It was do the company-provided training, or forfeit the end-of-year 10% performance bonus.

OK, fine. Whatever. Money talks.

Oh, just so you know, there's only one day left this year that you can make it. Guess what. It's smack in between two 12-hour night shifts, from 0800-1500.

Freaking terrific. I'm not even sure that making me attend this between two night shifts, making for 31 working hours inside of 36 clock hours (with a couple of parking lot catnaps wedged in) is legal or not, but when you're talking about the year-end 10% performance check, I can try to stay awake for a few hours.

Erg.

First off, it had been forever since I had seen first aid training videos not intended for emergency service professionals. The acting was worse, but it was the background music .... now that was so very realistic, just like the music we hear when our tones drop, when we drive to the calls, when we arrive. Very dramatic, just the way we like it piped in wherever we go with our big red trucks. Gripping. Perfect. I told my closest compadre in the class that we have a looping audio cassette in many of our rigs that plays that sort of music when we're running hot, just to get is in the hero mood groove.

I like how the video showed compressions-only CPR, with two people taking turns. Except that the person taking a break is doing nothing to maintain an airway. Airways are overrated, I guess.

Or how the instructor said that someone who is not breathing will always be in cardiac arrest. Don't assess for a pulse, just start compressions. ???

The review of how to read haz mat labels and MSDS sheets, something a shade beneath the annual haz mat ops training we go through every year at the FD.

Scene safety? What's that? The first-aid-trained actors arrived at a traffic accident at night and just left their car in the road without even hazard flashers on, never looked for scene safety problems, just waltzed straight into the thick of it.

I like how a rescuer actor carefully donned their PPE gloves before administering the Heimlich. That choking guy can just hang on while you go get your gloves, you know. Where did I put them anyway?

When doing the hands-on CPR run through, not even one person (except for me) managed to get chest rise from the practice doll. No matter. Next!

(Sorry this is so disjointed and choppy, my bad form comes from about three total hours of sleep over the previous 40 hours or so.)

A particular favorite scene: a couple of actors are talking, one asks the other, "So Kenny, how is that new project you're working on going?" Kenny opens his mouth, draws up a pained expression, and collapses. My compadre behind me wasted not even a second before piping up with "Oh my God! They killed Kenny!" FTW!!


Then we did Halon awareness training. Zzzzz.

And fire extinguisher inspections and discharge practice. I've taught this class myself many times. Zzzzzzzzzz.

Let us not forget I was up most of the day before, did 12 hours awake on shift overnight, and then had to sit through seven hours of this for my 10% check before rolling back into another 12 hours of babysitting power lines overnight. ZZZZZZZZZZZZZZZZZZZ.

I didn't want to come off as a smartass, and was determined to keep my mouth shut. Still, a couple of times the instructor said some well-meaning but half-baked stuff that I felt obligated to do damage control on. It didn't go over with her very well despite my overly deferential approach, so I stopped trying. Oh well.


I did learn something new though. Our Halon tanks have symbol signage which clearly endorses pranking your friends with portable marine air horns. Note that there is no circle with a slash through the pranking action to imply prohibition. How cool is that?

Nap time. Please hold all 911 calls for about ten hours or so. Sorry my attitude sucks today, it's only temporary. Thanks.


Tuesday, November 16, 2010

Kiss It

I was out on a call that was running a little on the long side, and had to get clear so that I could get to work at the full-time power company gig. Ironically, it was a tree on power lines call that I had to break away from.

To be on the safe side, I called the control center to the dispatcher I was supposed to relieve, to let him know that I was in a pickle but was doing what I could to be at work on time. This was a good 90 minutes before I was due at work, mind you.

I made it to work on time, as it turned out. If I had not called in, no one would have known the difference. Some folks ask me how I do both jobs, but to be honest I can think of only three times in around ten years that I got pinned by a fire call and couldn't get to work on time because of it. Sure, other things make me late here and there, but not the fire department. It's just rarely ever an issue. I know when to skip calls based on time of day, and type of call, to prevent that from happening..

Still, the guy I was supposed to relieve complained to the boss. I didn't hear about it right away (probably because I was on time in the first place), but eventually it came out. The way it was phrased was along the lines of how he didn't want to be stuck while I was out "playing fireman".

As a volunteer, I hear that a lot. I imagine many of my readers, career and volunteer, hear it too.

Well, you guys who think this is fun and games can kiss my pale and hairy ass.

I've seen far too many people bleeding and dying, had my feet nearly frozen in my boots and icicles caked on my helmet, lost nights of sleep while running calls or waking up to certain nightmares, consoled grief-stricken family members, had ceilings fall on me and once nearly fell through a floor, jumped out of the way of drunk drivers while trying to extricate and save another, held dead children in my arms, and paid for the privilege of all that and much more by missing time with my family and greatly increasing my chances of early death by various nasty cancers.

When you think it is fun and games for us and make wisecracks about our job and its been only two hours since I worked on a guy who blew the top of his head off and I had to bag my turnout gear because of all the blood we were mucking around in......

Fun and games? Playing fireman? Some game. Some fun.

I don't ask for love or medals, I just do it because it needs to be done.

If you can't just take that at face value and leave it be.... if you have to mock and belittle what I do, well you can substitute "kiss my ass" for what I really think about you. If you call 911 for whatever, or drop with cardiac arrest right in front of me, you bet I'll be the first one to help you. But respect? You get none.


Friday, September 24, 2010

Unplanned Kitchen Update

I actually thought the kitchen saga was more or less over. The work was done, illogically and haphazardly, and we had moved on. But no, someone had to kick the beehive again.

If you're new to this blog, there is a long, long history to this. I dare you to put on your favorite Dilbert pocket protector, refill your coffee, and read all the posts tagged Kitchen Remodel, from the oldest post forward.

Came in for the day shift a few days ago to find a slight modification. Specifically, a new counter.


No one asked for it. We sure didn't need it. There's no plumbing, no electric, and no nearby anything else you want in that corner. And, so far, nothing to put on it.

We just added clutter and cleaning space, usage pending. Important stuff.

I suspect we could have used this money to move the fridge as previously intended, but as usual I am not privy to the master plan.



Wednesday, September 15, 2010

Owning the Incompetent with Humor

In another life, I spent some time in the software industry. I had been in the electric utility business for a few years when I was offered a job with one of our vendors. At the time, it seemed like a good idea. OK, I'll admit that in retrospect it actually was a good idea, as my three years there looks really good on the ol' resume now that I am back in the system operations and dispatch circle of the industry.

I became sympathetic to the lives of software engineers, as I worked with them at length while dealing with dispatchers and power marketers using the software. I became a liaison of sorts, telling the software wonks about life in the control center, and telling dispatchers about software wonk life trying to make lots of people with often conflicting opinions all happy at the same time.

Sympathetic to a point, that is. I've never been able to tolerate blatant incompetence. My own included, I must add.

Unrelated to that, as yet, is that I am also a wise-ass at work. Many many years ago the senior dispatcher on my shift would always react the same way when a line tripped. The first thing he would do was quote Robot (voiced by Dick Tufeld) from Lost in Space: "Danger! Danger, Will Robinson!" Then he'd get up, refill his coffee, and saunter back to the console to fix the broken stuff.

The quote inspired me, and it was very easy to find a WAV file of that quote online. I added a toolbar shortcut to it, and could play it loudly with a single click every time a line tripped. Hilarious. You had to be there.

I soon expanded my WAV collection and built an interface to instantly play back any of the 75 or so witty one-liners I collected over time. Some examples:

"I've felt a great disturbance in the force." (Obi-Wan Kenobi/Alec Guinness, Star Wars: A New Hope)

"Scotty, I need warp speed in three minutes or we're all dead!" (James T Kirk/William Shatner, Star Trek II: The Wrath of Khan)

"Look, I'm gonna tell you about an accident and I don't wanna hear about an 'act of God', OK?" (Jack Burton/Kurt Russell, Big Trouble in Little China)

"No sense worrying about it now." (Raymond Stantz/Dan Akroyd, Ghostbusters)

"I think it is time we demonstrated the full power of this station." (Grand Moff Tarkin/Peter Cushing, Star Wars: A New Hope),

"Finally, we shall bring order out of chaos." (Egg Shen/Victor Wong, Big Trouble in Little China)

"I'm sorry, but this is a highly sophistamicated doowacky, you don't treat it responsibly, ka-BLAM-o!" (Homer Simpson/Dan Castellaneta, The Simpsons).

You get the idea. So where the heck am I going with this?

Do you remember how reserve sharing works? If not, go refill your coffee now, then come back and review Tutorial 4: Basic ACE, and Reserve Sharing before proceeding here.

So one day we're testing a new reserve sharing application built by my former vendor employer. It's not tied to anything yet so it can't actually make things happen, but you can tell it to do stuff and see how it would theoretically react. I have a sneaking suspicion (aka insider info) that it isn't quite ready for prime time, and evilly relish the thought of breaking it. I am suspicious that they are testing it while it has known deficiencies, hence is a waste of everyone's time. Test it when you really think it is ready, instead of pretending you're making good progress and hoping no one exposes you by breaking it. Their bad luck I was on duty.

Every utility in the entire reserve sharing pool had someone in on the conference call. Our turn came up, and we were to simulate requesting replacement energy for loss of a power plant in our system. I selected a large, 550MW plant that was shared contractually with three utilities. The software threw down an ugly error message to everyone's screens. Exposed. Software guys fumble mumbled apologetically about how the application was not configured to handle shared units yet.

So why are we testing it? Grrr.

OK, I say, let me try something else. When picking off the big 550MW unit, I noticed that their drop-down list of power plants included every single dinky unit we had. So this time I picked a tiny 0.85MW (850kW) hydro plant. Submit.

Everyone's alarms went off, as you could hear over the phone. So the application alarm was working fine. Then the comments started. "I got the alarm, but no megawatt contribution". "Same here". "Yeah, we see the event but are not being asked to provide assistance" Then the largest utility, with the biggest prorated share of the pool, said "I got one megawatt on my display". Mind you, they are so big that they can swing 100MW every few minutes as a matter of routine. 1MW to them is rather less than a day-old fart in the wind.

Software guys were feeling pretty burned now. But I knew these guys, and was not exactly a big fan of their work to begin with. Finally I played along and picked a "safe" 220MW sole-owned plant, and the application worked OK and let everyone see numbers like they wanted to.

As we continued through the round-robin testing, a couple of other dispatchers followed my lead and started trying to break the thing on purpose with new tricks. A few were successful.

As the call wound down and a sort of debrief was being held, I grabbed my PC speaker and pulled up the WAV interface. Holding the speaker by the phone, the entire conference call was treated to:

"So far, this is not blowing my skirt up, gentlemen." (Spencer Trilby/Charleton Heston, True Lies).

Several rather rewarding snickers were heard from other participants. Conference call anonymity is nice.  The software guys were silenced for a few seconds, and then went on like it hadn't happened.

Next time we tested the application a few weeks later, shared units worked, and no plants below 25MW were in the pick list.


Tuesday, August 17, 2010

They Waited an Hour to Call

We arrived a little late to the party.

As it turned out, it took the bystanders something along the lines of an hour for someone to decide a 911 call was in order.

An hour.

The three of us made our way into the Mayberry district and pulled up in Engine 56 at about the same time the Heavy Rescue from nearby Kinda Big City was unloading its crew.

A quick look down the trail to the river bank showed the surreality of a few local rescuers and bystanders frantically attempting to free someone from under a log in the river, who was struggling to get air while held down by the water, as well over fifty others continued sunbathing, only a few paying attention.

By the time we got down to the edge, the kid had been pulled free.

The kid.

And he was blue.

He had been weakly flailing and fighting to escape when we looked down. Only a few minutes had passed. Now he was limp. They broke his leg to get him out when he lost consciousness.

Shit.

We worked him for a long time. The medics of course threw epi and lidocaine at him, but the monitor gave us nothing but asystole. Still, we kept working.

Now a few people were paying attention.

We loaded him onto a basket and rigged up to take him up to the bridge. No way were the medics going to call it in front of the crowd.

I thought of my own kids as I bagged him all the way up the grade. Don't we always do that?

His dulled eyes stared in different directions under drooping lids. One-handed compressions continued as best as could be done by the guy across from me as we stumbled over the rocks. It was a miracle that I didn't dislodge the tube with the BVM as I was climbing. There was blood coming up the tube, from the tissue damage we were causing while working him.

Tried not to look at his parents, but how can you not?

It was after the ambulance departed for the landing zone to the helicopter, when we found out about the hour delay.

The entire freaking hour, the kid fought, screamed, struggled, his head not quite level with the water as the few bystanders who found the capacity to give a crap tried to free him, to help him get air.

An hour. Good God.

So, for the record, and I think I speak for all 911 dispatchers as well as my brothers and sisters on the BRTs and bone boxes, we would all rather hear about a problem ten times than never.

For the love of all that is good and right, pick up the phone and CALL.

For what it is worth, against all odds, the medics got a faint rhythm on the way to the helo. The kid was hypothermic, so the chance was there. The helicopter took him. He survived. Expected to make a full recovery.

Are you serious?

God was looking out for this one. He was about as dead as dead gets.

I guess that's a save.  No thanks to the spectators.


Thursday, July 29, 2010

Of Yardsticks and Manly Measurements

Like the day I broke the FD tanker, the shift at the power company started like any other routine day destined for minor excitement.

If you haven't read the tutorials (check the tag cloud on the right), some of this might be a bit overly technical, but I'll try to keep it simple. It won't however, be short. Sorry.

There we were, routinely minding our business, the grid more or less running as it was supposed to.

Suddenly, our ACE (the instantaneous difference between how much electricity we are producing, and how much is being consumed, adjusted for expected flows to other utilities, which should nominally be 0), jumped to about 650.  Then it started bouncing every few minutes by as much as 250MW up and down, pushing us way out of bounds on both sides.  That's an attention getter.

If the ACE thinks you have an extra 650 megawatts, only three things can have happened (or at least the AGC computer was led to believe one of these three things). Either (1) a generator suddenly decided to give you an extra 650MW (equal to a very large coal-fired plant), (2) you lost 650MW of consumer demand (equal to blacking out a very large metropolitan area), or (3) one of the power lines attaching you to another utility suddenly increased its flow by 650MW for some unexplained reason.

1 and 2 fall somewhere between impossible and extremely unlikely, and both would give you other clues such as an abrupt change in system frequency from the nominal 60Hz, and in the case of that much theoretical lost load, an overwhelming number of open circuit breaker alarms.

That leaves option 3. A flow meter, for whatever reason, decided that it needed to give us a vastly different number.  With no other tie lines also changing for a real-world event, this means the input went bad, a single false number.

The result of the instantaneous +650 ACE was that the automatic generation controller suddenly was being told that our generation/load balance was way, way out, and immediately started to control numerous power plants downward.

Remember the movie Star Trek: Insurrection, when Riker went to "manual mode" to fly the Enterprise? A flying controller deployed that amounted to a joystick, causing the audience to chuckle.

 
That's figuratively what I did. Went to manual AGC control and started flying by the seat of my pants to control our balance. Ultimately, we would end up running like this for about two hours. It was complicated.

While on manual control, the wind started to blow, wouldn't you know? Remember my wind power rants, about controlling around the serendipitous wind? This extra (real) generation output caused the units I was regulating balance with to go down to their minimum outputs.

This was about the time that the retired senior manager/engineer (RSME), who is now a contractor, arrived to save the day.

Now, to keep you interested in the story, I will break the monotony by sharing with you this completely unrelated picture, which always cracks me up.



OK, cute. Now, where were we? Oh yes, the RSME was now in the house.

I was periodically disabling the automatic controller while tweaking numbers, and the first thing he noticed was that the controller was off. He jumped to the conclusion that our excitement was centered on trying to get this thing back on.

This is key. He wanted to help us turn something on that I had deliberately turned off for cause.

So, what kinds of things would cause the automatic generation controller to automatically disable itself, you ask?

Any known bad input value will disable it, though in this case the software was not figuring out the value behind today's excitement was bad. Also, in theory, if the generation plants you are using to control output get all the way to the edge of their capability high or low, it is supposed to come off, though we have it set up to not do that.

RSME noted that, while I was flying in manual, the regulation units were almost bottomed out. If he had taken a few extra seconds, he might have realized that this was mainly because four major wind farms had a front blowing through and were giving us hundreds of unplanned MWs that we had to back out of the way to accommodate.

So we dispatchers are discussing the situation, flying manual, trying to resolve the problem, and RSME interrupts to tell us we have to move a couple of other power plants down so that the regulation units can move back into the middle of their bandwidth.

WTF are you talking about? (I didn't quite ask it that way, but I was helpless to control my tone).

You need to get your AGC back on.

No I don't, I manually disabled it on purpose, because I want it off.

Well, it needs to be on, and you have to direct those other plants to move up.

No it doesn't, and no I don't. That's not the problem.

He raised his voice and started to repeat himself.

It was then that I grabbed the hammer, broke the glass, pulled out the book, and invoked the Dispatcher is In Charge Rule.

You are not helping, you don't know what is wrong, you are interrupting us trying to tell us how to fix something that is not broken, and you need to leave the room.

Whoa, if looks could kill. He opened his mouth, closed it, then said he was going to bite his tongue this one time, and then left. Pardon me while I shed a tear of regret. Oh, and point of correction, it will be always, not "this one time". Thanks. OK, onward.

After affairs were settled a few hours later, I went to his office to clear things up, conciliatory and assuming good intent and all that. I related back the problem as he stated it and what he thought should be done to fix it, and he agreed with me. I then reiterated that the problem was now solved and had indeed turned out to be completely unrelated to his diagnosis. I told him his directives were 100% irrelevant to the incident.

There it was. We had pulled out the yardsticks, unzipped, and measured. I won on both counts: Authority to kick him out, and correct diagnosis in the first place.

He closed the conversation by ignoring my revelation, and by saying he wasn't going to worry about it, but that I should work on my people skills.

I'll get right on that, thanks.

I doubt I'm getting a Christmas card from him this year. It's too bad, though, because on the whole he is actually a really good guy. Which is not remotely enough to keep you from getting booted from my control room kingdom if you piss me off.