My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CCP 01-22-2006 Work Session
ArdenHills
>
Administration
>
City Council
>
City Council Packets
>
2000-2009
>
2006
>
CCP 01-22-2006 Work Session
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/8/2007 1:29:06 PM
Creation date
2/16/2007 9:57:29 AM
Metadata
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
223
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
<br /> Ramsev Countv- H'ide f:"mcrgc/lcv Opcrafio/1S Plall Revisio/l 5.1. ./ulle. 2005 <br />. <br /> Incident Action Plan (lAP) <br /> An Incident Action Plan (lAP) will be developed for each operational <br /> period of the incident and: <br /> . Includes the overall incident objectives and strategies established by <br /> the IC or UC. <br /> . Adequately addresses the mission and policy needs of each <br /> jurisdictional agency in the case of UC. <br /> . Adequately addresses the interaction between jurisdictions, functional <br /> agencies, and private organizations in the case of UC. <br /> . Addresses tactical objectives and support activities required for each <br /> operational period, generally 12 to 24 hours. <br /> . Contains provisions for continuous incorporation of "lessons learned" <br /> as incident management activities progress. <br /> . Is developed when resources or authorities from multiple agencies <br /> and/or jurisdictions are involved. <br /> . Is developed when the incident will effectively span several operational <br /> periods. <br /> . Is developed when changes in shifts of personnel and/or equipment <br /> are required. <br />. . Is developed when there is a need to document actions and/or <br /> decisions. <br /> Information and Intelligence <br /> The analysis and sharing of information and inteiiigence are important <br /> elements of ICS. In this context, intelligence includes not only national <br /> security or other types of classified information but also other operational <br /> information, such as risk assessments, medical intelligence (i.e., <br /> surveillance), weather information, geospatial data, structural designs, <br /> toxic contaminant levels, and utilities and public works data, that may <br /> come from a variety of different sources. Traditionally, information and <br /> intelligence functions are located in the Planning Section. However, in <br /> exceptional situations, the IC may need to assign the information and <br /> intelligence functions to other parts of the ICS organization. In any case, <br /> information and intelligence must be appropriately analyzed and shared <br /> with personnel, designated by the IC, who have proper clearance and a <br /> "need-to-know" to ensure that they support decision-making. <br /> Regardless of how it is organized, the information and intelligence function <br /> is also responsible for developing, conducting, and managing information <br /> related security plans and operations as directed by the IC. These can <br /> include information security and operational security activities, as well as <br /> the complex task of ensuring that sensitive information of all types (e.g., <br />. classified information, sensitive law enforcement information, proprietary <br /> and personal information, or export-controlled information) is handled in a <br /> way that not only safeguards the information but also ensures that it gets <br /> 1,7 <br />
The URL can be used to link to this page
Your browser does not support the video tag.