Susan,
I don?t usually drop into ?Around the Campfire? but I was giving a heads up on your questions? and I just happened to be spending the day updating a PowerPoint Presentation on this very topic.

I work for a fire department that is part of the Phoenix Metro Automatic Aide System. This system is very uncommon, where the closest appropriate unit goes regardless of jurisdiction? period! My Paramedic/Engine Company answers over 70% of our calls in other cities than our own. On a simple house fire we can have battalion chiefs from two different cities, three engine companies each from a different city and a ladder from a forth city! Add PD, utilities, and an ambulance from private ambulance company and we have a cornucopia of agencies on scene! And it all works seamlessly more often than not. An effective ICS is only one hurdle in making this happen, but it is an important one.

Organizing numerous resources at an incident doesn?t begin with the ICS, it ends with it. Before ICS can work on a call some other issues have to be address before it can be implemented effectively. First, all the agencies have to be on the same page? all of them. This is often easier said than done. Each involved agency must have common communications, common policies and procedures (where appropriate), common terminology and radio codes, and joint training on the ICS. In addition, every member from the most senior officer to the newest boot needs to buy into the system completely! If everyone is on the same radio system using the same policies that they have trained on together ICS works? but it can still fail if not done properly.

I have seen the ICS fail, I have caused the ICS to fail <img src="/images/graemlins/blush.gif" alt="" />? Where I have seen it fail the most is with departments and communities where the agencies can?t get along well enough to make things work. And departments with young members with inadequate supervision and low call volume.

Here are links to my Presentation in
PPT format and PDF Format