41 Planned Actions for Provide a short summary of actions planned for the next operational Next Operational Period period. Examples: current Incident Management Team will transition out to a “The replacement IMT.” to review operational/ engineering plan to facilitate removal “Continue of the partially collapsed west bridge supports.” refining mapping of the recovery operations and damaged “Continue assets using GPS.” removal of unauthorized “Initiate food vendors.” 42 Projected Final Incident Enter an estimate of the total area likely to be involved or affected over Size/Area (use unit label the course of the incident. e.g., “sq mi”) Label the estimate of the total area or population involved, affected, or – impacted with the relevant units such as acres, hectares, square miles, etc. Note that total area involved may not be limited to geographic area (see previous discussions regarding incident definition, scope, operations, and objectives). Projected final size may involve a population rather than a geographic area. 43 Anticipated Incident Enter the date (month/day/year) at which time it is expected that incident Management objectives will be met. This is often explained similar to incident Completion Date containment or control, or the time at which the incident is expected to be closed or when significant incident support will be discontinued. Avoid leaving this block blank if possible, as this is important information for managers. 44 Projected Significant Enter the date (month/day/year) when initiation of significant resource Resource demobilization is anticipated. Demobilization Start Date Estimated Incident 45 Enter the estimated total incident costs to date for the entire incident Costs to Date based on currently available information. Incident costs include estimates of all costs for the response, including all management and support activities per discipline, agency, or organizational guidance and policy. This does not include damage assessment figures, as they are impacts from the incident and not response costs. If costs decrease, explain in Remarks (Block 47). If additional space is required, please add as an attachment. 46 Projected Final Incident Enter an estimate of the total costs for the incident once all costs have Cost Estimate been processed based on current spending and projected incident potential, per discipline, agency, or organizational guidance and policy. This is often an estimate of daily costs combined with incident potential information. This does not include damage assessment figures, as they are impacts from the incident and not response costs. If additional space is required, please add as an attachment.
41 Planned Actions for Next Operational Period Provide a short summary of actions planned for the next operational period. Examples: “The current Incident Management Team will transition out to a replacement IMT.” “Continue to review operational/ engineering plan to facilitate removal of the partially collapsed west bridge supports.” “Continue refining mapping of the recovery operations and damaged assets using GPS.” “Initiate removal of unauthorized food vendors.” 42 Projected Final Incident Size/Area (use unit label – e.g., “sq mi”) Enter an estimate of the total area likely to be involved or affected over the course of the incident. Label the estimate of the total area or population involved, affected, or impacted with the relevant units such as acres, hectares, square miles, etc. Note that total area involved may not be limited to geographic area (see previous discussions regarding incident definition, scope, operations, and objectives). Projected final size may involve a population rather than a geographic area. 43 Anticipated Incident Management Completion Date Enter the date (month/day/year) at which time it is expected that incident objectives will be met. This is often explained similar to incident containment or control, or the time at which the incident is expected to be closed or when significant incident support will be discontinued. Avoid leaving this block blank if possible, as this is important information for managers. 44 Projected Significant Resource Demobilization Start Date Enter the date (month/day/year) when initiation of significant resource demobilization is anticipated. 45 Estimated Incident Costs to Date Enter the estimated total incident costs to date for the entire incident based on currently available information. Incident costs include estimates of all costs for the response, including all management and support activities per discipline, agency, or organizational guidance and policy. This does not include damage assessment figures, as they are impacts from the incident and not response costs. If costs decrease, explain in Remarks (Block 47). If additional space is required, please add as an attachment. 46 Projected Final Incident Cost Estimate Enter an estimate of the total costs for the incident once all costs have been processed based on current spending and projected incident potential, per discipline, agency, or organizational guidance and policy. This is often an estimate of daily costs combined with incident potential information. This does not include damage assessment figures, as they are impacts from the incident and not response costs. If additional space is required, please add as an attachment.
ics-209-directions.docx