When developing anEmergency Operations Plan (EOP)that utilizes theIncident Command System (ICS), planners must prioritizeDetermining needed functions. ICS is a functional management system, meaning it is organized around tasks and objectives rather than specific agency names or job titles. This functional approach is what allows for the modular expansion and contraction of the organization as the incident evolves.
While understanding hazards (Option A) and agency responsibilities (Option B) are necessary for the overall planning process, the "use of an ICS" specifically requires the identification of the five core functional areas:
Command, Operations, Planning, Logistics, and Finance/Administration. For instance, an EOP must define how the "Logistics Function" will be handled-identifying how resources are ordered and tracked- regardless of which specific department (Fire, Police, or Public Works) is actually providing the personnel to staff that function on a given day.
According toNIMS (National Incident Management System)doctrine, the "Function" is the building block of the response. Planners must determine which functions are critical for their specific community and how they will be activated during a disaster. This prevents the confusion of "who is in charge of what" by focusing on the functional requirement (e.g., "Public Information") rather than the agency (e.g., "The Mayor's Office").
For aCEDPprofessional, this means ensuring the EOP is not just a list of names, but a functional roadmap that describes how these ICS modules will interface to stabilize an incident, ensuring that every necessary functional gap is addressed before the "boots hit the ground."