NIMS Compliance Checklist

NIMS Compliance ChecklistDeadline for Compliance is September 30, 2006StandardCompliance Requirements1. Adoption ofNIMSAll Governments, non-governmentorganizations, and private sectorincident management/responseorganizations will foiinerly adopt andpromote NIMS compliance duringactivities.Compliance AppliesTo:Each Jurisdiction – Canbe by city or individualdepartments.Recommend cityadoption.Private and nongovernmentalorganizations can adoptin same manner as pubicsector.2. IncidentCommandSystemManage all emergencies and exerciseswith ICS organizational structures asdefined by NIMS. Must includeapplication of Incident Action Planningand Common Communications PlansAll levels responderswithin jurisdictions –County, city, responseagencies, privateresponse agenciesNotesAccomplished by: Formal ResolutionExecutive Order Proclamation Legislation Adoption throughminutes at officialmeeting In plans, policy, orprocedures tendocumentationindicating theadoption ofNIMS; held byadoptingorganizationA formal adoption by acity will cover alldepartments. Alldepartments will then needto assure compliance withguidelinesAdopt ICS through anWrittendocumentation ofexecutive order,proclamation, or legislation adoption andas the jurisdiction's official policies, plansincident response system.and proceduresmaintained byDirect incident managersgovernments andand response organizations private sectorto train, exercise, and useresponderICS during responsesorganizations.Integrate ICS into policies,plans, and procedures.ComplianceDateDateDateDateDate

StandardCompliance RequirementsCompliance AppliesTo:NotesDocumentationRequiredICS Training for allresponders, supervisors,and command levelofficers.3. MultiAgencyCoordinationSystem4. PublicInformationSystem5. Coordinateall FederalPreparednessFacilities, equipment, personnel,procedures, and communicationsintegrated into a common system forincident management activities.Implement processes, procedures,and/or plans to communicate timely,accurate information to the publicduring an incident through a JointInformation System and JointInformation CenterDevelop and implement a system tocoordinate all federal preparednessfunding to implement NIMS across theResponders at all levelsparticipate in ICS-orientedexercises involvingresponders from multidisciplines andjurisdictionsSince most cities/agenciesAll response agencies do not have an establishedCity, response agencies,private response agencies EOC to coordinateactivities, these cities canrefer to the county multihazard planAll government,response agencies, andprivate response agenciesAll government,response agencies, andprivate response agenciesPlans, policies, orprocedures to use a publicinformation system tocommunicate to publicduring an incident (with adesignation of who isresponsible for thisactivity).A City executive order,proclamation, or resolutionwould cover alldepartments within thatgovernmental body.Coordinate all spending ofFederal preparedness fundsto ensure NIMSComplianceDateDateDateDocumentation ofa policy, plan,procedure,executive order, rresolution tosupport thecounty EOCwhen requestedDocumentation ofplans, policies, orprocedures to usea publicinformationsystem tocommunicateinformation to thepublic during anincident.Nodocumentationrequired. ByDateDate

StandardCompliance RequirementsFundingcommunity.6. Revise andUpdate Plans,Policies, andProcedures7. Mutual Aid8, 9, & 10.TrainingRevise and update plans and SOPs toincorporate NIMS principles to includeplanning, training, response, exercises,equipment, evaluation, and correctiveactionsParticipate in and promote intrastate andinteragency mutual aid agreements –including agreements with the privatesector and non-governmentalorganizationsComplete IS-700, IS-800, IS-100 & IS200Compliance AppliesTo:Notescompliance across thecommunityAny jurisdiction thatcurrently has any plans,procedures, or protocolsAll government,response agencies, andprivate response agenciesAll possibly involved inan emergency incident,dependent on level ofinvolvement.Review any plans, policies,or procedures that arecurrently in place andupdate them to incorporateNIMS.If your city is an IMACsignatory, you havesatisfied this requirement.Non-governmentalorganizations and privatesector need to haveagreements in place toshare or obtain resourcesduring an incident, ifneeded.Executive Level: Gov'tLeaders, department headsand/or anyone filling roleof Incident Commander aswell as EOC staff – AlltrainingManagerial Level –Agency and managementlevel personnel betweenExecutive Level and firstlevel; those filling ICSroles as directors,DocumentationRequiredsigning the "SelfCompliancy"letter, you willagree tocoordinate NIMSimplementationefforts.Document anyplans, policies, orproceduresupdated for NIMScompliancyMutual aidagreements mustbe in writing andcan be any of thefollowing:IMAC28E agreementsMOUMOAWrittendocumentationwill be trainingrecords that aremaintained bycity ter ofCompliancyDateDateDate

StandardCompliance RequirementsCompliance AppliesTo:NotesDocumentationRequiredsupervisors, leaders,specialists, leaders, etc. –All trainingResponder Level – Entrylevel to managerial levelIS-700, IS-100.DateAll involved personnel atthe supervisory level andabove should also take theIS-200 training.11, 12, 13.ExercisesIncorporate NIMS/ICS into all local andregional training and exercises.All government,response agencies, andprivate response agenciesParticipate in a NIMS all-hazardexercise program that involvesresponders from multiple disciplinesand multiple jurisdictions.Incorporate corrective actions intopreparedness and response plans andprocedures14. InventoryResponseAssetsInventory community response assets toconform to Homeland SecurityResource Typing standardsAll cities/responseagencies must participatein an all hazards exerciseprogram that incorporatesNIMS and ICS into theexercises. The programmust incorporate afteraction reports andcorrective action plans.ComplianceDateDateDocumentparticipation withsign-in sheets,after-actionreports, or otherdocumentation toindicateparticipation in aNIMS compliantexercise program.DateNon-governmental andprivate sectororganizations must alsoparticipate in NIMScompliant exercises.All government,response agencies, andprivate response agenciesThis is an on-goingactivity to remain NIMScompliant.In many cases, you maynot possess and of the 120resources. DO NOTinventory any resourcesunless the resources matchKeep andmaintain the listof any of the 120typed resourcesyour jurisdictionDate

StandardCompliance RequirementsCompliance AppliesTo:Notesexactly to one of the 120typed resources.15. EquipmentStandards16. Applystandardizedand consistentterminology,including theestablishment ofplain Englishcommunicationsstandards acrosspublic safetysectorTo the extent permissible by law, ensurethat relevant national standards andguidance to achieve equipment,communication, and datainteroperability are incorporated intolocal acquisition programsCommunicate using "Plain English" forall responses according to guidancereceived (Law enforcement may utilize10-codes for officer safety orcommunications within theirdepartment).All government,response agencies, andprivate response agenciesAll government,response agencies, andprivate response agenciesNote: This requirement isin addition to any countybased resource typing thatmay include resourcesbeyond the 120-typedresources.The jurisdiction (all) willassure that relevantnational standards will beapplied when determiningequipment purchases usingFederal Preparednessfunds.DocumentationRequiredhas available.Nodocumentationrequired. Bysigning the "SelfCompliancy"letter, you willagree to applynational standardsto equipmentpurchases.Documentequipmentpurchases forperiod specifiedin grantThe use of 10-codes willNobe eliminated except fordocumentationlaw enforcement protection required. Byor within law enforcement signing the "Selfagency communicationsCompliancy"letter, you agreeto utilize "PlainEnglish" inresponsecommunicationsComplianceDateSignedLetter ofCompliancySignedLetter ofCompliancy

ODUMMIO3ali00I -S1(0L-SI '00Z-SIri-si apvittio;i)fOL-SI '00Z-SII -si apidtHOD' I uto--saA1O1 pip si.mrI11JUO1inoA" ioj aputu suoispapsa1lUMIS1110dSOItioS O(j00L-Si00 T-S1 alaldlua0upg/s low)010Saospuadlispunt juoli atp HOpuppulU1 ko:p Stwatp puods4,1110S."stiontuadapURTIMI01angom Jo pud q noS HimSmaintua JO

NIMS Compliance Checklist Deadline for Compliance is September 30, 2006 Standard Compliance Requirements Compliance Applies To: Notes Documentation Required Compliance Date 1. Adoption of NIMS All Governments, non-government organizations, and private sector incident management/response org