Incident Command System (ICS)
A suitable command structure is required in every rescue operation. Most rescues in an alpine environment are done by one or a few local rescue teams who have a good understanding of each team‘s systems and capabilities. They often train together and coordinate with each other. In such situations, often the command structure is informal, simple and based upon the needs of the situation. This is normal and understandable, but still a structure exists.
Although most alpine operations are small in scale, larger incidents are possible, with many moving parts both at and away from the rescue site. This type of incident may even involve more than one country. This calls for a more complex command structure, which rescue teams have to be able to adapt to.
It is important to use a command system that is flexible, cabable of scaling from the smallest size to larger multi-agency incidents.
Incident command system should be:
- Scalable and modular: easily support the incident command team from 1 person to a large group.
- Usable for small scale local incidents to a large disaster stretching between communities or countries without the need to change the system.
- Standardized structure and terms.
- Workable in all environments.
- Integrated into national incident command system.
- Able to allow timely transmission of data and personal information under the laws of each country.
3. Explanatory notes
- Scalable and Modular: It is very important not to change the system due expanded incident needs.
- Usable for all scenarios: As features expand, it is important that everyone understands the system and can merge directly into it.
- Standardized: Structure and terms that everyone is familiar with and trained in.
- Workable in all environments: On land, at sea and in the air.
- Integrated: Into national incident command system.
Integrated Communications: Able to allow timely transmission of data and personal information under the laws of each country.
For the glossary please download the file!