Sorry for the 'book'... but I GOTTA vent about this....
NIMS training irks me... they should either call it the "All chiefs and no indians" system, or the "Scapegoat System"... either one is applicable.
Granted, there's a need for order and chain-of-command... he11, all of us should be pretty used to that by now... but this NIMS system is so heavy on red tape, bureaucratic BS, acronyms, and assorted governmental horse manure that calling it 'DISGUSTING' would be giving it a compliment.
First thing... Everyone has to have a special title, an "office", and underlings... "Incident Commander", "Deputy Commander", "Operations Section", "Planning Section", "Special Operations Chief", "Bases", "Helibases", "Camps"... This one talks to that one, that one reports to this one... OK, now that we have the kingdom set up... and all the Gods are on high... who's left to man the incident? Putting a governmental hierarchy on an incident scene sounds like a disaster waiting to happen... Simple, straightforward chain-of-command seemed to work pretty well for the last umpteen years of emergency response... leave it to the government to complicate things. This might work OK in an area that has an overage of manpower to devote to it... but in my area, sometimes during the day, it might take THREE DEPARTMENTS to get enough people together to minimally man ONE INCIDENT. Sure... we can have an Incident Commander... as long as he doesn't mind manning the pump, manning the radio, and filling air pack bottles along with it. Sure I can be the Operations Chief... as long as I can do it from the end of a hose line with an SCBA mask on. Public Information Officer? Sure... he's the guy up on the roof with the K12 in his hand... This system falls apart when manpower is at a premium.
Next, they talk about "Plain English", and "Understandable Communications"... and follow it up with so many acronyms that they need a dictionary at the back of the manual to explain what all the acronyms mean!
Next it's about "keeping it simple"... "streamlining processes"... "reducing workload"... and about halfway through, you get to the "forms section". The FIRST ONE they show is an EIGHT-PAGE DOCUMENT. From the above, that's gonna be easy for me to fill out, as long as I can find a flat surface that isn't on fire to write on, and my pen doesn't melt while I'm writing.
And all through it, they keep discussing "responsibility" and "accountability"... ohhhh yes... the government LOVES accountability (unless it's their own, of course). I keep getting the distinct impression through taking all this "training", that all told, they're less interested in running an incident, than having the names of everyone in charge (with one guy at the top) on an incident, so if something goes wrong, they'll know whose hide they can fry for it. And judging by all the finger-pointing that went on in government after Waco, after Oklahoma City, after 9/11, after Hurricane Ivan, after Hurricane Katrina, etc... etc... It seems to me that they're REALLY looking for a structure to hang someone on if need be.
And to cap it all off, since I think they pretty much know if it was "optional" training, most of us would take one look at it and laugh our ***es off, they got enough backing to FORCE it on us by saying, in a semi-veiled THREAT, that 'noncompliance may affect future availability of grant monies and other benefits'. Typical big-government processes at work.
I'm not saying the whole thing is bad... there's a lot of good ideas in it, but the overall delivery is poor at best. I think I can almost TELL, just from the ideology and verbage, where the good ideas that came from past incidents, off firegrounds, and from people who are actually out there DOING, are; and where the governmental flunkies and bean counters filled in the rest.
Like a good little grunt, I complied... over-complied actually... but it still doesn't make it right. Just one guy's opinion, I guess... unfortunately, it's shared by quite a few others.
NIMS training irks me... they should either call it the "All chiefs and no indians" system, or the "Scapegoat System"... either one is applicable.
Granted, there's a need for order and chain-of-command... he11, all of us should be pretty used to that by now... but this NIMS system is so heavy on red tape, bureaucratic BS, acronyms, and assorted governmental horse manure that calling it 'DISGUSTING' would be giving it a compliment.
First thing... Everyone has to have a special title, an "office", and underlings... "Incident Commander", "Deputy Commander", "Operations Section", "Planning Section", "Special Operations Chief", "Bases", "Helibases", "Camps"... This one talks to that one, that one reports to this one... OK, now that we have the kingdom set up... and all the Gods are on high... who's left to man the incident? Putting a governmental hierarchy on an incident scene sounds like a disaster waiting to happen... Simple, straightforward chain-of-command seemed to work pretty well for the last umpteen years of emergency response... leave it to the government to complicate things. This might work OK in an area that has an overage of manpower to devote to it... but in my area, sometimes during the day, it might take THREE DEPARTMENTS to get enough people together to minimally man ONE INCIDENT. Sure... we can have an Incident Commander... as long as he doesn't mind manning the pump, manning the radio, and filling air pack bottles along with it. Sure I can be the Operations Chief... as long as I can do it from the end of a hose line with an SCBA mask on. Public Information Officer? Sure... he's the guy up on the roof with the K12 in his hand... This system falls apart when manpower is at a premium.
Next, they talk about "Plain English", and "Understandable Communications"... and follow it up with so many acronyms that they need a dictionary at the back of the manual to explain what all the acronyms mean!
Next it's about "keeping it simple"... "streamlining processes"... "reducing workload"... and about halfway through, you get to the "forms section". The FIRST ONE they show is an EIGHT-PAGE DOCUMENT. From the above, that's gonna be easy for me to fill out, as long as I can find a flat surface that isn't on fire to write on, and my pen doesn't melt while I'm writing.
And all through it, they keep discussing "responsibility" and "accountability"... ohhhh yes... the government LOVES accountability (unless it's their own, of course). I keep getting the distinct impression through taking all this "training", that all told, they're less interested in running an incident, than having the names of everyone in charge (with one guy at the top) on an incident, so if something goes wrong, they'll know whose hide they can fry for it. And judging by all the finger-pointing that went on in government after Waco, after Oklahoma City, after 9/11, after Hurricane Ivan, after Hurricane Katrina, etc... etc... It seems to me that they're REALLY looking for a structure to hang someone on if need be.
And to cap it all off, since I think they pretty much know if it was "optional" training, most of us would take one look at it and laugh our ***es off, they got enough backing to FORCE it on us by saying, in a semi-veiled THREAT, that 'noncompliance may affect future availability of grant monies and other benefits'. Typical big-government processes at work.
I'm not saying the whole thing is bad... there's a lot of good ideas in it, but the overall delivery is poor at best. I think I can almost TELL, just from the ideology and verbage, where the good ideas that came from past incidents, off firegrounds, and from people who are actually out there DOING, are; and where the governmental flunkies and bean counters filled in the rest.
Like a good little grunt, I complied... over-complied actually... but it still doesn't make it right. Just one guy's opinion, I guess... unfortunately, it's shared by quite a few others.
Comment