FIRESCOPE TASK FORCE Mulberry Street Riverside, CA FAX

Transcription

1 FIRESCOPE TASK FORCE 2524 Mulberry Street Riverside, CA FAX April 25, 2001 To: From: Subject: California Fire Service Member FIRESCOPE Task Force FIRESCOPE DECAL The decal included was designed to help commemorate the 30 th Anniversary of FIRESCOPE. The intent is to display it on apparatus (preferably on a window where it does not obstruct view) during the year to bring attention to FIRESCOPE and its heritage. Ifyou would like more decals for your department, they can be ordered and purchased from Valley View Conservation Camp for $.50 per decal. Valley View Conservation Camp P.O. Box 27 Elk Creek, Calif Attention: Captain Jack Bogle FIRESCOPE Task Force

2 FIRESCOPE JOINT OPERATIONS TEAM February 22, 2001 Chief Michael Freeman, Chairman FIRESCOPE 1320 North Eastern Avenue Los Angeles, California Dear Chief Freeman: At the Board of Director's meeting held January 10, the Operations Teams were tasked with the assignment to review the position and duties of Safety Officer within the Incident Command System. The item that prompted this assignment was a letter of request received by your Board from Mary McCormack and the Fire Department Safety Officers Association. The letter requested that FIRESCOPE investigate the creation and/or certification of a "Safety Section" within the ICS. Both Operations Teams addressed this matter at their joint meeting held January 25 and 26 at Pismo Beach. I would like to summarize the discussion and conclusions drawn by the members at that meeting. I would also like to offer for your review a white paper submitted by Chief Neamy of Los Angeles Fire Department after discussion at the meeting and review by the members of both Teams. I have also included two other attachments. The first is a copy of the position checklist for the FOG, and the second is a copy of ICS that addresses firefighter accountability. ICS contains a more complete outline of the function and responsibilities of the IC and, subsequently, the Safety Officer and Assistant Safety Officers, if appointed, especially as it addresses accountability. Here is a summary of the discussion and major issues addressed at the meeting. ~ The role of the Safety Officer and his/her assistant officers has been a paramount issue of FIRESCOPE Board, Operations Teams, and Task Force for more than two decades. Much work, thought, and effort has been expended to make sure its importance receives the attention and concern the position is due. Its role has been intimately tied to each operational system FIRESCOPE has developed including structure, wildland, high rise, urban search and rescue, hazardous material, and mass-casualty incident organizational descriptions. Although further refinement will always continue, it is not considered "broke" and, therefore, need not be fixed. ~ The position of Safety Officer should receive the level of authority commensurate with the tasks that must be performed. It was determined the importance of those tasks requires that he/she work directly for the Incident Commander as part of the Command Staff. It was agreed that changing the status of the Safety Officer by reassigning the position to General Staff diminishes the position's authority and adversely impacts his/her direct line of contact with the Incident Commander. In a very practical sense, he/she serves as both an integral member of the incident management team and as a close advisor to the IC.

3 ~ Critical safety and accountability concerns have been addressed in ICS Because of the nature of the topic, the position of Safety Officer, by reference to the duties of the IC, received considerable attention and evaluation. The material was designed to insure personnel safety and delineate the critical role of the Safety Officer when appointed by the IC. ~ The FIRESCOPE organization previously addressed the role of Information Officer when a similar issue arose. In that case, it was determined that the existing organization best suits the needs of the incident and the management team. The Operations Teams found it to be a similar circumstance in many respects to the discussion of Safety Officer and, therefore, further substantiates our conclusions. ~ The current ICS is designed to enable the number of Safety Officer and Assistant Safety Officers to grow as the incident grows in both size and complexity. It also stipulates that Assistant Safety Officers can be appointed to monitor specific tasks or functions unique to any incident. If the ICS is used correctly, there should be no lack of personnel required to oversee the safety needs of an incident. The duties and responsibilities of the Safety Officer will continue to be the subject of assessment and evaluation. I have asked the Task Force to consider whether a working group should be established to oversee further refinement of the position as new issues and incident management needs arise. One concern of the Operations Teams was that the proposal submitted to you regarding a "Safety Section" represents a significant change to structure and may violate the intent of the agreement that established the IMS Consortium. I would hope that those who are considering the change would give due consideration to all of the groundwork that has been laid over the past several years. In the spirit of good will and effective incident management, the Operations Teams would be more than happy to send representatives to discuss the function and derivation of the Safety Officer position. I hope this provides the information you need to respond to Ms. McCormack and the Fire Department Safety Officers Association. If you have questions or require additional information, please do not hesitate to contact Andy Anderson or myself. Sincerely, Andy Anderson, Chair Cary Eckard, Chair Operations Team North and South Attachments

4 7A (c- fd~ 01(23/0 I NATIONAL ICS-209 DATABASE PROJECT PROPOSAL SUMMARY The objective of this project is to expand the current national Situation Report program database to indude information collected on the ICS-209 form. This expansion can produce an active, realtime database that would improve the efficiency and accuracy of incident information flow and allow for queries and report generation. Overview There are currently a variety of Incident Status Summary (ICS-209) forms being used throughout the country. These forms provide information to complete the large fire namdive portion of the national Situation Report program required by the National Interagency Fn center (NIFC). They also provide information for other incident management purposes from the local to the MACS group level. Incident Management Teams (IMTs) or incidents generally fill out ICS-209s and then fax them to local dispatch offices, GACCs, or other locations that require the information. There are no existing mechanisms for archiving ICS-209 information in a national database that would also accept queries and generate reports. Most incident reporting is done using hard copy, is labor intensive, and is subject to error. Some GACCs are developing or have built their own processing mechanisms or databases to meet critical needs. Alaska uses the lams Fires Program. In California, FIRESCOPE requires online completion ofa web-based 1CS-209 in addition to the Situation Report process required by NIFC. The online 209 is saved in a document storage system foronline posting, document dissemination, and archiving. This process does not involve an information database. The FIRESCOPl;faskforce has been tasked to fllld a more efficient 209 processing system by May A national 209 database may fit these requirements for FIRESCOP~ '. The national Situation Report program is a web-based application available over the Wor1d Wide Web through the Fire &Aviation Management (F&AM) Web Applications page. The national Situation Report program uses an Oracle database. Local dispatch offices and GACCs are required to submit daily fire statistics, resource availability, planned presabtd fires, and other incident management and planning information to this database. Queries of this database are currently used for creating daily and year-to-date summaries ofthe information. At this time, local dispatch centers and Geographic Area Coordination Centers (GACCs) have password access to the program. The national Intelligence Coordinators are pursuing a modification to the existing web-based national Situation Report program. This modification would combine information gathered from the existing Situation Report program and the new ICS-209 program into a single database. This database could be used to generate the information currently required forthe Situation Report. in addition to meeting a variety of other incident management needs. It could also minimize duplication of information and increase reporting accuracy and legibility

5 NATIONAL ICS 209 DATABASE PROJECT PROPOSAL Identified Needs There is a need for a standardized form and mechanism that allows for reporting of incident information on a nationwide level. Incident information data should be entered and stored in a format that can be used for a standard ICS-209 report, or for other queries and summaries as fire managers find appropriate. Information should be collected. processed, and available to users in real time. Data should be stored in a format that is archivable. Data entry and access to reports should be controlled. Information should be available to fire managers on many levels without jeopardizing the security or accuracy of incident reports. A web-based data collection process would be accessible nationwide to traveling IMTs as well as local dispatch centers. Expansion ofthe existing Situation Report database would reduce reporting. redundancies and eliminate the need for the creation ofanother nationwide incident data collection mechanism. Utilization and expansion of an existing program may reduce training and implementation requirements. Electronic data from state or other cooperators that may have existing electronic data collection systems could be uploaded into the database and utilized for reports and queries. Proposal The national Intelligence Coordinators are proposing an expansion ofthe large fire narrative ofthe national Situation Report program to include an ICS-209 database. This database would be based on the revised ICS-209. recenuy approved by NWCG (NFES-1333, 12/00). The basic ICS-209 that is produced by this program would look very similar to the NFES printed version. The ICS-209 information would be a part of the Situation Report database. When the 209 database project is completed, the large fire narrative section of the Situation Report would be discontinued. The Situation Report program is currently used to generate queries for summaries and reports, and can also be used for archiving data. Expanding this program to include 209s would allow for queries and reports on 209 information as well. in addition to archiving capabilities. 1122/01

6 Combining the two programs would minimize duplication ofinformation and data entry into both the 209 forms and the Situation Report program. The resulting database could be used to generate all the information necessary for the Situation Report. This could also increase accuracy and legibility. Implementation of a national 209 database would involve certain provisions to allow Alaska to upload data from an existing data collection system. It would also require California's FIRESCOPE organization to adopt one ofseveral available options to include the state in the national database. The ICS-209 database can be used for all risk management ofincidents. Project Completion This project requires approval and support from NWCG. The goal for completion and irj1)lementation of this project is the 2001 fire season. This goal may serve as a trial implementation date rather than a full implementation date. The eartiest anticipated date for database completion is March 2001, although the entire project may not be corj1)leted until later in the spring. This timeline may vary due to unforeseen progranvning difficulties or other issues. Implementation of this program in areas that already have existing 209 electronic processing mechanisms may take longer due to necessary adaptations and programming time. Long-Term Goals It may be possible for the completed national Situation Report/lCS-209 (situation) database to interface with the Resource Ordering and Status System (ROSS) when that program is implemented. This interface may allow for the importation ofresource, location, or other information into the situation database from ROSS. This process would further increase accuracy and reduce reporting redundancy. Additional investigation into this potential interface would be necessary as ROSS is irj1)lemented. Data Entry and Report Access Uke the Situation Report, data entry can only be accof11>iished through the Wand Wide Web. Users without web access, such as those on remote incidents, would still have to process reports through dispatch centers. The Situation Report program is currently entered through a button on the F&AM Web Applications page. The 1CS-209 data entry location could be located through a separate button below the Situation Report button on the F&AM Web Applications Internet site. Locating 209 program access separately from the Situation Report program should help maintain the security ofboth programs. Although all ofthe information from both programs is entered into the same database, users may not need access to both programs. Incident Management Teams (IMTs) and certain other users would need to be assigned user IDs and passwords allowing them access to enter209s in any 1fl2101

7 geographic area. GACC Intelligence Officers would need to work with fire management staff,lmts, cooperators, and dispatch centers to coordinate this process. Read-only access can be given to incident management staff who do not need data entry access. These accounts and passwords can be set up in the same way other accounts are set up. All password access to the 209 program should allow users complete reading access to current and recent (within the calendar year) 209s from anywhere in the country. This access would most likely include a set ofestablished query reports as wen. All access is set up through W1MS accounts. Intelligence Coordinators may need to be involved with the assignment.ofaccounts and access when the program is implemented. Queries. Reports, Displays, and Archives The basic individual ICS-209 information can be presented in a report that looks very much like the NFES ICS-209 form. A set of queries will be developed by the national Intelligence community with input from the fire community to utilize the information in the database. Queries could be done on most sections ofthe ICS-209, and could include summaries by date, year-to-<:tate, and possibly even by month. Reports and summaries could also be broken down by state or geographic area. Queries ofthe database could be done by 209 "bloc!(. These queries could include, but are not limited to: - Incident Type (fire, earthquake, etc.) - Incident Jurisdiction - IMT Type (I, II, etc.) - Acres - Injuries - Injuries to Date (by incident) Threats - Costs to Date - Structures Threatened ordestroyed - Committed Resources Input from the fire community and the database manager will likely identify other types ofqueries that could be made with this database. Reports, including 209s, can be printed, or saved orcopied electronically. They can then be ed oredited and published on other Internet or intranet sites as incident managers find appropriate. This process is currenuy used by several GACCs for publishing the Detailed or Summary Situation Report on Intelligence web pages. Information in the database would be saved by calendar year. Throughout each calendar year, archived incident information should be available by asking for a date and incident name or number. At the end ofeach year, data from the calendar year can be stored or sent to other databases for archival use based on cooperator needs and requests. Other ICS-209 Database Uses Information from the large fire narrative ofthe Situation Report program is currently used for a variety of other programs. These programs would not be affected by the expansion ofthe Situation Report program to include an ICS-209 database. Other data uses include exporting fire location information into the NIFC Large Fire Map posted on the World Wide Web. Location information is also used for the web

8 based GEOMAC incident mapping program. GACCs can use the GENERATEDgenerated incident maps based on this database information. Arrangements could be made to export data to cooperators or additional mapping or other programs if necessary. Proposal Benefits The incident reporting process would be simplified, as several reporting redundancies would be eliminated. Increased efficiency would reduce the time that is required to generate and disseminate required and often critical reports. National, regional (GACC), or state queries and reports ofincident activity should be able to provide fire managers with more accurate and timely information for incident management purposes. Utilization and expansion of an existing program may reduce training and implementation requirements. The Situation Report program was used effectively during the 2000 fire season with relatively few system bugs orshutdowns. Expansion ofthis database to include the ICS-209 program is not likely to create system problems or maintenance issues. Implementation ofthis proposal would decrease the need to fax reports. Faxing may still be necessary in cases Where Internet access is not available. Faxes could be used as a backup to the database process ifthe system were to go down temporarily. Information is accessible in the database as soon as it is sent. There is no distinguishable layover or processing time before information is available. Accuracy and legibility would be increased with this process. Information would be standardized. Report processes would be standardized throughout the nation. The ICS-209 database can be used forall-risk incident management as well as wildland fires. Implementation Issues Query and report requests and formats should be developed as the database is developed to ensure that the database meets reporting needs. These queries should be developed using input from fire managers and cooperators. Archiving requirements may need to be identified before the database is developed. User names and password access lists would need to be generated for dispatch centers, IMTs, and fire managers. Access to the database will be assigned to each useras data entry and/or read-only, depending on the needs ofthe user. The goal ofthis program is to have participation from each GACC in the national database. However, Alaska, California, and the Northern Rockies Geographic Area have instituted or tried other automated ICS-209 processes. In order to have full participation in a national database, arrangements would need to be made to include data from those areas that have established automated electronic processes for processing 209s. For instance, the Alaska GACC could export data from the lams Fires Program to the national database. California has several options available for 1122/01

9 interfacing in some way with a national database. These options are ouuined in the last section of this proposal. Full implementation ofthis project by the 2001 summer wildland fire season may not be possible. Aggressive education about required processing changes by fire Intelligence staff and other wildland fire managers could lead to a very successful trial program this season that may come close to full implementation of the program. This process may not be completed in time to be published in national and regional mobilization guides. Implementation alternatives may need to be examined ifthe database project is approved. A clear set of user requirements and instructions will be required for any implementation plans. Brochures. worksheets. or other helpful user information could be distributed in those areas that would be utilizing the program. Issues relating to the co-existence of two ICS-209 processing programs may need to be examined during implementation planning for states such as california. Maintenance and continual operation of the F&AM Web Applications site and the database itself is critical to successful program implementation. 1122J01

10 I Implementation Issues for California Considerations This project requires approval and support from FIRESCOPE. California has an existing web-based IC5-209 data collection and archiving process established through FIRESCOPE. This process is currenuy built on a document collection and storage process. The newly approved IC5-209 form (NFES #1333) is not significanuy different from the Incident Status Intelligence Summary form that FIRESCOPE currenuy uses, as FIRESCOPE had significant input to the revised national 209. Therefore, information requested for the national database is very similar to incident information FIRESCOPE requests. Major differences include FIRESCOPE's requirement for resource statusing on truck companies, fixed-wing aircraft, and rescue/medical equipment. Federal dispatch centers and/or GACCs are required by NIFC to enter large fire information (100 acres or larger in timber or 300 acres or larger in brush or grass fuel models) from 209s into the national Situation Report program on a daily basis. This requirement includes non-federal incidents. California's participation in a national database would decrease this reporting redundancy. There are at least four options available at this time that FIRESCOPE could utilize or combine to allow for some sort of interface with a national 209 database. These options should be able to account for the major California irj1)lementation issues listed here. Each option is briefly summarized in the following sections. However, the details ofeach alternative and the advantages and disadvantages ofthem are not discussed in this forum. Each option will have significant implementation issues and differing timelines. These factors will need to be considered, especially ifone system will still be in use while a new system is implemented. I I I I I I I I I

11 Option 1: FIRESCOPE uses the NationallCS-209 Database Under this option, California would use the national IC5-209 database and data entry process instead ofthe existing FIRESCOPE 209 data entry process. The national 209 web site could be entered through the FIRESCOPE web site or the national F&AM Web Applications site.. Considerations FIRESCOPE cooperators would have direct and immediate access to a national database of incident information. FIRESCOPE incident and resource information would be directly entered into a national incident database. FIRESCOPE users would have access to incident information in this database on a real-time basis. Information is available immediately after itis submitted. FIRESCOPE users would also have access to certain queries and reports that would be used to summarize the data. In addition, FIRESCOPE could give input to queries that may be desired when the system is designed. The 209 database would be maintained and supported on a national level. Technical support staff for the database are available 24 hours a day. Implementation ofthis option would involve California in a standardized 209 entry process. Incident Management Teams and other overhead who travel out of state would not need to utilize two different processes for finding or entering Incident information. Some special accommodations may need to be made to include California into a national database while still meeting specific state requirements. These accommodations are ouuined below and are technically feasible. There is potential for the national 209 program to import resource data from ROSS (Resource Ordering and Status System) when it is implemented in the future. This potential interface could eliminate the need to enter resource Information into the IC The information may be able to be automatically i~rted when the incident number is entered. Access to the national 209 program would need to be given to all FIRESCOPE cooperators through the W1MS system. This will involve a usemame and password that is different from the FIRESCOPE web site usemame and password. Implementation Issues User names and passwords for data entry and read-only access would need to be issued as appropriate to all 934 current FIRESCOPE cooperators, departments, dispatch centers, and fire managers. This process is done using WIMS accounts that give access to the national Oracle database. Agencies with existing W1MS accounts would need to be identified. Those WIMS users can be assigned appropriate (read-only or data entry) access to the national 209 program. This process would involve a change in the 209 process for FIRESCOPE. However, the system would be easy to use and user-friendly. Technical support is available

12 through the national cofll)uter hetp desk. and some GACC support may be available as well through Intelligence Officers or other staff. Although the data entry process would look different than the existing FIRESCOPE process. it would not be any more difficult or complicated. Instructions on the data entry process. use ofthe system, and filling out the ICS-209 form itselfwould be available online through the same web site the 209 program will be on. These user guides could also be linked to from the FIRESCOPE web site. The national 209 program would be based on the existing Situation Report program. This program has been used successfully nationwide for more than one fire season. It is easy to use, and has a history of very few technical problems and downtime. Costs Costs for FIRESCOPE cooperator access to the national database would likely be limited. The only fees incurred under this option are for the uploading time for data to be sent to the national database, and for the few seconds ittakes to query the database to get reports. Total costs are not expected to be prohibitive. Each user name and password is assigned a management code and billing agency. Many accounts can be billed to a single entity. so that costs for all new users could be covered by single entity or a few large entities. Cost apportionment should be decided before user names and passwords are requested. California 209 Database Program Additions FIRESCOPE may require an additional input screen in the 209 program for California users. This screen would status fixed-wing aircraft, truck companies, and resaje/medical equipment as well as a block for jurisdiction. FIRESCOPE may also request separate blocks on the 209 report that show both the total number ofinjuries on the fire as well as the total number ofinjuries during the last operational period. FIRESCOPE'S requirement for 209 submission twice a day would require an extra function in the 209 database structure to differentiate a 209 submitted in the morning of a given day (0001 to 1200) from one submitted after noon (1200 to 2400). The national 209 database would not likely be able to archive more than two 209s a day. The archived copy would include the most recent data that was entered for that time period. The report view ofan ICS-209 for California may look a little different than the national form, but this would reflect the above additions. Data Access A national archiving process may meet FIRESCOPE's archiving requirements. Archived data could be sent back to California annually oras otherwise agreed upon. Agencies ororganizations that require information from the national database could make reasonable arrangements for data retrieval. Processes for data transfer, frequency of data transfer. and formatting of data could be set up by database managers. 1122/01

13 Option 2: Database Interfacing Itwould be possible to send information from the national situation database back to California or any other state or GACC for any number ofreasons. This could be done on a daily basis, twice a day, or according to other arrangements. This scheme could be used if.an agency or organization was interested in using data that from a national database for other incident management purposes. Special arrangements would need to be made between agencies regarding programming necessities, database security, financial agreements, and so on. These arrangements may also involve a significant Investment of time for database managers on both ends of the project. The specifics ofthis option would depend on the arrangements being made. Timety implementation ofthis option could be difficult due to programming constraints. Option 3: Data "Uploading" from a Database Fonnat This options involves no visual change to FIRESCOPE users from the current webblilsed document storage system. This change would involve additions or changes to FIRESCOPE's web-based 209 processing system. These changes would involve adding some programming or using macros to collect information from the current 209 document storage system and put it in a format that could be uploaded into a database. This information could then be uploaded to the national 209/situation database hourly, daily, or as otherwise arranged. In this situation, California information would be available to national database users, although California users would have mixed access to the national 209 program. Implementation Issues This process would not involve an obvious change to FIRESCOPE users. Incident information from California could be added to the national 209 database. Incident information in the national database would not arrive in -real-time-, but instead would arrive at pre-arranged data transfer times. This could be an issue for processing 209 information from the GACCs to NIFC ifincident information is not received by data transfer deadlines. In this case, other methods of information transfer could be used, but the reporting redundancy may be further complicated. Type I and II Incident Management Teams or other overhead who work on fire incidents out of state would be required to enter 209s through the national 209 database when they are not working in California. However, under this option, incidents in California would not be entered direcuy into the national 209 database. This issue could cause some confusion. Implementation of this option by the 2001 fire season may be very difficult to accomplish due to programming constraints. 1f22J01

14 ~.~ ~- Option 4: Data "Uploading" from an Oracle Database This option involves no visual change to FIRESCOPE users from the current webbased document storage system. The change to the FIRESCOPE system involves adding an Oracle database "back end" to the web interface where 209 information is currently entered. Information that is entered into the 209 would then be sent to an Oracle database (a very powerful database system) in California. This information could then be uploaded to the national 209/situation database hourly, daily, oras otherwise agreed upon. This option requires FIRESCOPE or one ofits cooperators to establish and maintain an Oracle database. In this situation, California information would be available to national database users, although California users would have mixed access to the national 209 program. Implementation Issues All ofthe i~lementation issues from Option 3 apply to this option as well. Implementation ofthis option by the 2001 fire season would probably not be possible due to the time and expense ofestablishing and building an Oracle database. Establishing, building, and maintaining an Oracle database may be cost-prohibitive. The national Situation Reportl209 database does not require data from an Oracle database format. It will accept data from many types ofdatabase formats

15 _ Task Force Report May 8, th Year FIRESCOPE Celebration A large part of the Taskforce's time this last quarter has been devoted to preparations for this evening's banquet. The 30 th Year Celebration Incident Management Team (IMT) and the Taskforce hope that you enjoy the event and that the festivities will honor the efforts of all of those involved with the FIRESCOPE Process. In the event that there are any funds remaining, the 30 th Year Celebration IMT would like to make the following recommendations: A portion of any remaining funds to be dedicated to hosting a picnic for FIRESCOPE veterans in the Southern California area. Some retirees were unable to attend this Northern California function. If approved, the retirees will be asked to plan and execute the picnic with financial oversight from the 30 th Year Celebration IMT. This event might be scheduled to coincide with the annual kick-off of Fire Season at Camp 2. All remaining funds to be dedicated to a fire-service related nonprofit organization. A suggestion is the Alisa Ann Ruch Burn Foundation. This foundation supports burn centers statewide and wi'll allow the Board to allocate monies to specific burn centers if you so choose. ICS Fire Service Field Operations Guide The latest version of the Field Operations Guide (FOG) should be ready by this time. This is our 30 th Year commemorative version and is dedicated to all of the participants of the FIRESCOPE Process over the last thirty years with special dedication to Rachel Parks. The new version includes improvements recommended by our customers, such as the type of binding and the drilling of the holes to facilitate upgrading.

16 \ Strategic Plan Working Document Chief Freeman sent out the Strategic Initiatives portion of the FIRESCOPE's Future document that was written to be a part of the 30 th Year Celebration publication. The Taskforce is looking for input for our upcoming review of the FIRESCOPE Strategic Plan. The Taskforce feels that this document is a good starting point for that review if the Board concurs. '. Safety Working Group The Taskforce has activated a small Working Group to review Safety in the Incident Command System, recommend changes where required and to clarify the treatment of safety by the Incident Command System. This is a result of the apparent misunderstanding of the utilization of Safety Officers and Assistant Safety Officers fostered by some proponents of Fireground Command. Urban Search & Rescue Specialist Group The Taskforce has solicited recommendations for membership on this reactivated specialist group. The goals of the group will be to review the equipment list and the OSO for currency and compliance with other FIRESCOPE documents and to integrate the Swiftwater Flood Search & Rescue product into the US&R OSO. ICS Form 209 Incident Status Summary The NWCG has adopted a revised Form 209 Incident Intelligence Summary Form. The new form addresses some of the needs of the national fire intelligence and coordination communities. Because the Federal wildland agencies will be required to use the new form and similar issues concerning intelligence and coordination have been raised in California, the Taskforce has adopted the revised form. As a bonus, the new form will be supported by an electronic reporting system managed by NICC (National Interagency Coordination Center). The new system will be a database that will allow real time access to incident information. This system will be maintained at no cost to FIRESCOPE or state or local agencies and has been designed to include California-specific needs. As soon as challenges with the OES IT Branch are negotiated, this new electronic reporting form will be accessible from the current FIRESCOPE web page ICS 209 button. 2

17 ICS 220 Air Operations Summary Worksheet At the request of the California aviation community, the Taskforce has adopted a revised ICS 220 that more closely reflects current technology and aviation management techniques. The new form was developed by representatives of federal, state and local government aviation management subject matter experts and the final draft of the new form was validated at the 2001 California Interagency Incident Management Workshop's Aviation Breakout Session. ICS 230 Vendor/Contractor Evaluation Form Again, at the request of our customers, the Taskforce has adopted a new ICS Form to assist Incident Management Teams report on the contractors and vendors that are hired in support of incidents. The form will be utilized to evaluate all contractors and vendors that are not under a national contract. Copies of the competed evaluation forms will be sent to the contracting officer listed on the contract/agreement. Taskforce Vacancies We are happy to report that one of the vacancies on the Taskforce has been filled by Chief Tim Fike of the Nevada County Consolidated Fire Department. Chief Fike will be representing Volunteer Fire Departments North MACS Orientations The MACS Orientations for this year will be May 30 at OCC Riverside and June 6 at Redding. Since only orientations have been scheduled, this would be a good year to identify and send new or additional representatives to learn about the MACS process. 3

18 FIRESCOPE WORK PLAN Strategic Plan Goal A: Maintain the FIRESCOPE "Decision Process", identify strategies to promote awareness of FIRESCOPE and secure funding sources. Projected Actual Work Task Action Assigned To: Completion Completion Date Date Fire Service Field Operations Guide 30 th Prepare Task Force 06/01 Anniversary Edition (ICS) 420-1: & review (Honeycutt)) for Prepare & review for revision. revision ICS Forms Manual (ICS 230-2): Revise Task Force 06/01 (Honeycutt) contains examples of all ICS proved forms with instructions. 215-S, 202 or 212 ICS Position Curriculum Review: Review/ State Fire 12/99 10/99 Revisions revise Marshal 5-430,3/99 ICS position curriculum in its current format is Office not compatible with NWCG ICS Modules. (component 5-339, 7-00 Need to review each position lesson plan and of Strategic 1/2000 remove subject matter covered through Plan and , modules. After Action 07/2001 Report) (Hutchison) FIRESCOPE WORK PLAN /01/2001

19 Strategic Plan Goal A: Maintain the FIRESCOPE "Decision Process", identify strategies to promote awareness of FIRESCOPE and secure funding sources. FIRESCOPE Strategic Planning: Projected Actual Work Task Action Assigned To: Completion Completion Date Date Identify projects that FIRESCOPE needs to Ongoing Task Force 09/01 pursue in future Work Plans. (Honeycutt) Review and update every other year. Damage Inspection Task Force 06/01 (Hutchison, Develop Damage Inspection Lesson Plans. Plough) Decision Process Synopsis Write Task Force 02/01 (Interaction with NWCG, NFA, etc.) Flow (Rosenberger) Charts MACS Revise Task Force 06/01 (MACS Red Flag Alert): & Weather Make generic for statewide use. Red Flag update Specialist has different meanings for several agencies. Group Get groups together (NWS, IFWU, (Plough) FIRESCOPE) ~ FIRESCOPE Celebration & Reunion Plan Task Force 05/01 (Honeycutt) Create Model Operational System Description Create Task Force 06/01 (La Plant, West) FIRESCOPE WORK PLAN /01/2001 2

20 ; Strategic Plan Goal B: Improve and maintain emergency management leadership through interagency cooperation and provide professional recommendations and technical assistance to the Office of Emergency Services. Projected Actual Work Task Action Assigned To: Completion Date Completion Date ICS Glossary of Terms lics 010-1): Revise as Task Force Ongoing necessary (Glotfelty) ICS contains definition of terms used in ICS. Need to compare document with NWCG version for consistency and add sections for other ICS disciplines (US&R, Multi-Casualty, Hazardous Materials). ICS Typing and Minimum Standards (ICS 020-1): Revise Task Force 06/01 (Domanski) ICS contains listing of resources by ICS kind and type. Changes made to FOG Section on Resource Typing and Minimum Standards need to be included in this document as well as other ICS discipline standards. ~abasas Report Research South Ops Ongoing and take Team Twelve action items were identified requiring action (Eckard)/ research action taken by FIRESCOPE. Items Task Force being addressed need to be monitored for (Colgan) progress made. FIRESCOPE WORK PLAN /01/2001 3

21 Strategic Plan Goal B: Improve and maintain emergency management leadership through interagency cooperation and provide professional recommendations and technical assistance to the Office of Emergency Services. Projected Actual Work Task Action Assigned To: Completion Completion Date Date FIRESCOPE Website IT Specialist Information Ongoing Group is Technology developing Assist with development of FIRESCOPE standards to Specialist Website. be given to Group OES IT for completion. Task Force (Plough) NWCG ICS Modules: Distribute Ongoing Task Force Need exists to make the NWCG developed (Colgan) ICS modules easily available to the fire service user. Placing curriculum on an electronic medium has been identified as the best solution to addressing this need. FIRESCOPE Orientation Package Develop Task Force 06/01 Develop complete orientation package. (Honeycutt) ~ FIRESCOPE WORK PLAN /01/2001 4

22 Strategic Plan Goal C: Maintain and improve methods for coordinating multi-agency resources for planned and unplanned events. Projected Actual Work Task Action Assigned To: Completion Completion Date Date GIS Specialist Group Develop GIS 07/01 training. Specialist Develop Lesson plans for this discipline Group (Plough) MACS Exercise Conduct Task Force 07/01 ~ South Orientation MACS (Honeycutt) ~ North Exercise Orientation US&ROSD: Revise, Task Force 09/01 discuss (Olney) Revise US&R Operational System Description to include Swiftwater, Technical Rescue, Water, High Angle, Confined Space, Trench, etc. 209 Review & Task Force 06/01 vise the 209, request FIRESCOPE IT to implement (Plough) implement on Website, forward to Document Control for distribution. ICS 220 Air Operations Summary Review & Provides air operations units with the Revise Task Force 05/01 number, type, location and specific Establish (Plough) assignments of helicopters and air tankers. Working Group Vendor/Contractor Form (New ICS-230) Develop Task Force 05/01 (Plough) FIRESCOPE WORK PLAN /

23 , GOAL 0: Maintain and improve common all risk management systems for planned and unplanned events. Projected Actual Work Task Action Assigned To: Completion Completion Date Date I. ICS High Rise: Develop High Rise 04/01 Specialist Specialist Group working on developing High Group Rise Lesson Plans. Task Force (Marrone) SEMS BOD,Ops Ongoing Ongoing Teams North Work with SEMS Technical Committee Group and South, & to clarify issues, insure compliance with the Task Force law. Form alliance between SEMS and (Honeycutt) FIRESCOPE to insure compatibility between the two programs. Communications Issues Com Spec 12/01 1. FIREMARS viability North & 2. Radio system usage guide South 3. Expand Appendix A in FOG 4. Communication center integration Task Force 5. Is low band still out there - what do (Marrone) agencies have FIRESCOPE Weather Specialist Group Re- Plough Re-activate the group; revise charter, Task activate Force to assign projects. SAFETY WORKING GROUP Initiate Task Force 06/01 Identify numbers and activate. (West, La Plant) FIRESCOPE WORK PLAN /

24 Fire and Rescue Service Advisory CommitteeJFIRESCOPE Board of Directors TELEPHONE AND MAILING LIST Member P. Michael Freeman, CHAIR Chief, Los Angeles County Fire Department 1320 N. Eastern Avenue Los Angeles, CA Russell Richards, VICE CHAIR Fire Warden Stanislaus County 1100 "W Street, 2 nd Floor Modesto, CA rdrichards@worldnet.att.net Dennis Smith Chief, Sacramento City Fire Department 1231 "I" Street, Suite 401 Sacramento, CA Chip Prather, Chief Orange County Fire Authority 180 South Water Street Orange, CA John Scherrei, Chief Santa Barbara County Fire Department 4410 Cathedral Oaks Road Santa Barbara, CA Bob Roper, Chief Ventura County Fire Protection District 165 Durley Avenue Camarillo, CA William R. Bamattre Chief Engineer Los Angeles City Fire Department 200 North Main Street Los Angeles, CA Stewart W. Gary Chief Livermore-Pleasanton Fire Department 4550 East Avenue Livermore, CA Daniel G. Clark, Chief Kern County Fire Department 5642 Victor Street Bakersfield, CA VOTING MEMBERS Representing FIRESCOPE* FAX Also represents: Metro Fire Chiefs County Fire Departments FAX Also represent: Fire Districts Assn of California City Fire Departments FAX Also represents: Metro Fire Chiefs FIRESCOPE* FAX FIRESCOPE* FAX FIRESCOPE* FAX FIRESCOPE* FAX City Fire Departments FAX County Fire Departments FAX BOD

25 Member Hank Weston Chief, Grass Valley Fire Department 125 East Main Street Grass Valley, CA Kim Zagaris. Chief (Acting Chief) Office of Emergency Services Fire and Rescue Branch 2800 Meadowview Road Sacramento, CA Representing Volunteer Fire Departments FAX Also represents: OES Region IV Coordinator Non-voting Ex-officio Secretary or FAX Also represents: FIRESCOPE * ; Douglas Sporleder, Chief Santa Clara County Fire Department Winchester Blvd. Los Gatos, CA Doug_sporleder@cnt.co.santa-clara.ca.us Roger K. Purdie Chief Vista Fire Department 175 N. Melrose Drive Vista, CA rpurdie@ci.vista.ca.us Glen Newman Deputy Director Califomia Department of Forestry & Fire Protection 1416 Ninth Street Sacramento, CA John Tennant California Dept. of Forestry and Fire Protection Office of the California State Fire Marshal P.O. Box Sacramento, CA Fire Districts FAX Fire Districts FAX California Department of Forestry & Fire Protection FAX Also represent: FIRESCOPE* State Fire Marshal FAX Also represent: State Board of Fire Services John_tennant@fire.ca.gov Ray Quintinar Director Fire &Aviation Management, USDA Forest Service 1323 Club Drive Vallejo, CA rquintanar@fs.fed.us U.S. Forest Service FAX PGR Also represent: FIRESCOPE* Tom Nichols Regional FMO National Parks Service Branch of Fire Management 600 Harrison Street, Suite 600 San Francisco, CA Tom_nichols@nps.gov National Park Service FAX BOD

26 \ Member Ed Wehking Fire Management Officer U.S. Department of Interior Bureau of Land Management Federal Office Building 2800 Cottage Way, #W-1924 Sacramento, CA Representing Bureau of Land Management FAX Brian Hatch, Director Governmental Affairs 1780 Creekside Oaks, Suite 200 Sacramento, CA John Jansen Northern Director 2701 K Street, Suite 201 Sacramento, CA Andy Anderson Chief, Quincy Fire Department P.O. Box 846 Quincy, CA aa@quincyfire.net Cary Eckard Kern County Fire Department 5642 Victor Street Bakersfield, CA Gary Glotfelty Assistant Chief, Fire & Rescue Branch Office of Emergency Services Juniper Street Murrieta, CA SPECIAL ADVISORS (NON - VOTING) Non-Voting California Professional Fire Fighters FAX Non-Voting California State Fire Fighters Association FAX Work Non-Voting Operations Team North, Chair FAX Non-Voting Operations Team South, Chair Pager FAX Non-Voting Fax Dallas Jones Director, Office of Emergency Services 2800 Meadowview Road Sacramento, CA Jean Colyer OES, Fire & Rescue Branch 2524 Mulberry Street Riverside, CA jean_colyer@oes.ca.gov Non-voting FAX Non-Voting FIRESCOPE Decision Process Technician FAX or Pager BOD

27 ; Andrea Tuttle, Director Califomia Department of Forestry and Fire Protection 1416 Ninth Street Sacramento, CA Dave Driscoll, OES Region II Regional Coordinator Region Chief, CDF Coast-Cascade Region/Santa Rosa 135 Ridgeway Avenue Santa Rosa, CA Jeff Jones, OES Region III Coordinator Region Chief, CDF Coast-Cascade Region/Santa Rosa 6105 Airport Road Redding, CA Tim Tumer, OES Region IV Coordinator Region Chief, CDF -Sierra South Region 1234 East Shaw Avenue Fresno, CA Bob Martines, OES Region VI Coordinator (Acting) Assistant Region Chief, CDF Sierra - South Region/Operations 2524 Mulberry Street Riverside, CA Gary Pavusko Deputy Chief, Fire & Rescue Branch Office of Emergency Services 2800 Meadowview Road Sacramento, CA Pat Cooney Deputy Chief, Fire & Rescue Branch Office of Emergency Services 2800 Meadowview Road Sacramento, CA Paul Beckstrom Assistant Chief, Fire & Rescue Branch Office of Emergency Services 2800 Meadowview Road ~ Sacramento, CA Dan Tinnel Assistant Chief, Fire & Rescue Branch Office of Emergency Services 176 Nelson Avenue Oroville, CA Califomia Department of Forestry & Fire Protection FAX Also represent: FIRESCOPE* Non-Voting FAX Non-Voting FAX Non-Voting FAX Non-Voting Ext Fax Non-Voting Fax Non-Voting Fax Non-Voting Fax Non-Voting Fax Jim Marquis Non-Voting Assistant Chief, Fire & Rescue Branch Office of Emergency Services Fax P.O. Box 688 Penn Valley, CA BOD

28 .~ Neil Honeycutt Assistant Chief, Fire & Rescue Branch Office of Emergency Services clo USFS 3735 Neely Way Mather, CA John Kraushaar National Park Service 3735 Neely Way Sacramento, CA Len Chesmore Assistant Chief, Fire & Rescue Branch Office of Emergency Services 2800 Meadowview Road Sacramento, CA Bob Kephart Assistant Chief, Fire & Rescue Branch Office of Emergency Services 2800 Meadowview Road Sacramento, CA Ishmael Messer Assistant Chief, Fire & Rescue Branch Office of Emergency Services clo CSU Channel Island Fire Station # South Lewis Road Camarillo, CA Bill Bondshu Assistant Chief, Fire & Rescue Branch Office of Emergency Services P.O. Box 1429 Mariposa, CA Jon Olney Kern County Fire Department 5642 Victor Street Bakersfield, CA Non-Voting Fax Non-Voting Fax Non-Voting Fax Non-Voting Fax Non-Voting Fax Non-Voting Fax Non-Voting FIRESCOPE Task Force Chair Fax Pager FIRESCOPE Board of Directors - Department/Agency shall be represented on this committee for duration of the FIRESCOPE Program. BOD /2001

29 State of California MEMORANDUM Governor's Office ofemergency Services TO: FROM: DATE: May 7, 2001 FIRESCOPE B.O.D. I Fire & Rescue Service Advisory Committee Pat Cooney, O.E.S. Fire & Rescue Branch SUBJECT: California Incident Command Certification System - UPDATE The CICCS Task Force has met three times since the January meeting ofthe FIRESCOPE Board of Directors I Fire and Rescue Service Advisory Committee. Much progress has been made toward finalizing the implementation the CICCS. Several questions were generated at the January meeting; I'll update the status ofthose issues: Costs should remain minimal. There will be no costs for the issuance of certificates for training at the ICS 100 through ICS 400 levels. Local fire departments will handle certification issues for their own personnel at the ICS 100 and ICS 200 levels. At the ICS 300 and ICS 400 levels the appropriate Peer Review Committee will issue the certificates at no charge. For Certification at the ICS 500 and ICS 600 levels the State Fire Marshal's Office PACE V Committee will issues certificates at the same cost as CFSTES Training, $55. per certificate. The StateFire Marshal will issue certificates, notthe State Board offire Services as earlier outlined. Recommended new date to begin the two-year Historical Recognition process is July I, A Draft "Application Form for Peer Review" has been developed. This single form, complete with instructions and examples may be used at all levels ofpeer Review, as well as for the Historical Recognition process. The Incident Qualification System (lqs) software program developed under contract by the National Association ofstate Foresters is in a continuing Beta-Test through several areas in the nation. Five California fire department have been involved in the Beta-Test. The system has displayed numerous problems. Work continues at the software development level. There is no cost associated with the use ofthis program, it is downloaded from an Internet ftp site. Additional information has been developed since the January meeting ofthe Board. Currently there is no single document to share with the California fire service that gives direction in support ofthe CICeS. A Draft letter to be jointly issued by the State Fire

30 Marshal and the OES Fire & Rescue Branch Chiefhas been developed, to be used as a 'kick-off' document for CICCS. The idea at this time is to send a copy ofthis signed letter along with appropriate support documents, i.e. the Peer Review Application Form to each Fire Chiefin the state. Are-write ofthe State Fire Training Policies and Procedures "ICS Instructor" Requirements in its second Draft form at this time. This document has been updated to include the ICS Position Training within the Command and General Staffcontained in the CICCS and it also outlines the PACE II Peer Review for ICS Instructors. The State Fire Marshal has recommended a revision ofthe Appeal Process. Originally the concept was to have appeals reviewed at the appropriate Peer Review level. The SFM has decided to appoint an Appeals Board to function in his office. Tentatively membership will include representation from the State Board offire Services, a representative from Northern Training Officers and another from Southern Training Officers. A Technical Specialist may also be appointed or used for assistance. The supporting document entitled "Recognition ofnwcg Course Equivalencies" commonly known as the Equivalency Matrix is being reviewed one more time to verify its completeness and accuracy. The California State Firefighters Association has taken the formal position ofapproving the CICCS. Flex~ IOU. Pom 2

31 , CALIFORNIA INCIDENT COMMAND CERTIFICATION SYSTEM FREQUENTLY ASKED QUESTIONS 1. Will all fire department personnel need to be re-trained to meet the California Incident Command Certification System (CICCS) requirements? No. Many fire department personnel probably already meet a lot ofthe elements ofthe new system. CICCS is based on National Wildfire Coordinating Group (NWCG) 310-1, the Wildland and Prescribed Fire Qualification System Guide, which has been in use for several years by the Federal Wildland Fire Agencies, as well as by many local fire agencies throughout the state. Typically ICS classes that are taught by California fire protection agencies, and ICS classes provided at training facilities around California, as well as around the country, meet CICCS standards. In addition, one ofthe aspects ofthe CICCS is a two-year "Historical Recognition" period. During this time frame, the system includes the ability for an agency or organization to recognize the training and experience ofexisting personnel. Historical Recognition should reduce the need to provide additional training or experience for personnel that meet or exceed minimum standards. 2. Will the new CICCS develop a "Certs and Quais" process that excludes the involvement or approval ofthe local fire department chief? No. The local fire chiefis required to approve the participation ofhislher personnel at several phases ofthe training process. In fact, the local fire chiefis the certifying official for all positions at the ICS 100 and ICS 200 levels. The local fire chiefmust also be involved in several steps of the certification system in the ICS 300 through the ICS 600 levels. For example, part ofthe application process for Peer Review includes a letter from the applicants fire chiefindicating that the individual meets certification requirements. The applicant will be awarded a SFMO Certificate upon passing the Peer Review Committees evaluation. The decision whether a certified individual meets the physical fitness and currency requirements and may be designated "Qualified" to fill the position within the state mutual aid system rests with the home agency fire chief. It's not possible for a fire department member to achieve advancement through the CICCS without the fire chiefapproving steps along the way. 3. Is a fire department "required" by the California State Fire Marshal or the Office of Emergency Services to participate in the CICCS? No. These standards will apply to those hazard risks that historically involve statewide movement ofresources from one agency to the other. These typically include incidents such as 1

32 wildfire, floods, urban search and rescue, civil disturbances, earthquakes and major hazardous material incidents. These standards would not necessarily apply to incidents that are routine first level responses within an agency or department. 4. To be "Certified" by the SFMO, local government fire department personnel will be required to submit an application package to a Peer Review Committee. What will the cost be, in this process, to receive the SFMO Certificate? At the ICS 100 and ICS 200 levels, individuals are certified by their home fire department. There is no cost outside the local fire department at these levels. In the existing State Fire Training System, California Fire Service Training and Education (CFSTES) Certificates, cost about $55 per certificate. In the current Fire Service Training and Education Program, (FSTEP) Certificates cost about $5 per certificate. It is anticipated that a SFMO Certificate issued for ICS 300 through ICS 600, as part ofthe CICCS process, will be much closer in cost to the $5.00 cost. 5. How are the Peer Review Committees organized, and who sits on them? At the ICS 100 and ICS 200 levels, the local fire chiefprovides the review and approval process for certification ofthe members ofhis/her department. The California Fire Service and Rescue Emergency Mutual Aid System, provides the framework for the organization ofthe Peer Review. Committees at the ICS 300 and ICS 400 levels. Applications for Certification at the ICS 300 level will be submitted for review and approval by a multi-agency committee created and maintained at the Mutual Aid Operational Area level throughout the state. The Peer Review Committee membership ofeach local Operational Area is composed, where applicable, ofone representative from each ofthe following: California Department offorestry and Fire Protection, OES Fire and Rescue Branch, Federal Wildland Fire Agency, Federal Military Agency, Native American Reservation Fire Agency, Fire Protection District, Contract County, City Fire Department, Metro Fire Department, Labor Organization, Independent Volunteer Fire Departrnent/Fire District and a Qualified ICS Training Specialist. Applications for Certification at the ICS 400 level will be submitted for review and approval by a multi-agency committee created and maintained at the Fire Service and Rescue Emergency Mutual Aid Regional Coordinators level. The Peer Review Committee membership at the Regional level is composed ofthe same type offire service representatives as outlined at the Operational Area level Peer Review. Applications for Certification at the ICS 500 and ICS 600 levels will be subrnitted for approval by the SFMO, and reviewed by the PACE V Committee. PACE V will be a permanent standing committee ofthe State Board offire Services, with a chairperson elected by the committee members. 2

33 6. What happens ifa fire department decides not to participate in the California Incident Command Certification System? Essentially participation in the CICCS is not required. However CICCS will soon be recognized as the "industry standard" for Wildland Fire Training throughout the California Fire Service, just as NWCG is held as a national standard in the wildland fire community. Generally, safety organizations like Cal-OSHA hold public safety agencies accountable for conforming to existing standards. All ftre departments in California are encouraged to participate in the CICCS. The standards for the CICCS are being written into the new Five Party Agreement (Cooperative Agreement for Local Govemment Fire Suppression). Not meeting the CICCS standards could impact the ability offire department to qualify to being reimbursed by the Forest Agencies who are signatories to this agreement. In addition, the State Board offire Services, FIRESCOPE, California Fire Chiefs Association and NIOSH have approved the CICCS. 7. Explain the Application process for Peer Review. ICS 100-ICS 200 An individual applying for position certification shall submit to their local agency ftre chiefthe following documents: 1. Appropriate Course Completion Certificates 2. Appropriate Completed Position Task Book ICS 300-ICS 600 An individual applying for level ICS position certiftcation shall submit to the appropriate Peer Review Committee the following documents: 1. Application (SFMO fonnat) 2. Appropriate Course Completion Certiftcates 3. Appropriate Completed Position Task Book 4. Letter from his/her ftre chiefindicating that the individual meets certiftcation requirements. 5. Fees, necessary to cover handling costs ofthe position certificate and postage. (See #4 above). 8. What is the status of the "Incident Qualification System" software that was developed to permit fire departments to maintain a computer based training, experience and education tracking system for each member? Is IQS only suited to track wildland fire training issues, or will it also record data for "au risk" applications? Will the IQS be compatible with the CICCS? Is this software available and what is the cost? The National Association of State Foresters (NASF) and the National Wildftre Coordinating Group developed the Incident Qualifications System (IQS),jointly. It is based on NWCG IQS Version I was distributed and tested outside ofcalifornia beginning in January of Development ofversion 2 was funded by the NASF in October of Version 2 is now being beta-tested. It is anticipated that this version will be available for use in California sometime 3

34 during the 2001 fire season. Once the beta testing is completed, IQS Version 2 will be available for downloading from the Internet, at no cost to the user fire departments. Some ofthe features ofthe IQS include: Tracking oftraining, experience, fitness, and incident data; ability to add agency specific courses to the database, not just those in the NWCG Guide; training needs analysis; task book tracking, availability of individuals for dispatch; provisions ofdiffering security levels for those using the system, individual tracking needs and listing ofall individuals qualified for a specific position, etc. Being PC based, IQS offers flexibility in hardware system specifications and an economical operating environment. This package was developed in Visual Basic using Microsoft Access, a standard, relatively low cost software program. Because the CICCS and IQS (Version 2) are both based on the January 2000 edition ofnwcg 310-1, they are compatible. 9. Will California fire departments start issuing "Red Cards" to all personnel? A Red Card is a federal wildland agency, wallet sized card (sometimes printed on red card stock) that is issued annually to federal employees who meet NWCG and agency standards. The value ofthe Red Card is that it is a portable written record, carried by the individual, which can be checked at an incident to verify the ICS qualifications ofthe holder. Several fire departments in California voluntarily participate in a local Red Card system. The CICCS will not specifically use the federal Red Card. However, the IQS software (described in #8) will print "Incident Qualification Cards" to a laser printer, singly, all at once, or batched. IQS also has the capability to enter a course roster and have all ofthe student records updated for that course, or to enter a number ofcourses for one person at a time. Training Officers will be able to provide fire program administrators with critical management information by documenting all qualifying training experience for each individual. Such information is vital in staffing incidents, documenting employee safety briefings, and qualifying training for individual employees pte 4/01 version 3.0 4

35 California Incident Command Certification System (CICCS) What is the California Incident Command Certification System? CICCS Is:»A certification system for positions within the Incident Command System.»A "Performance Based System" utilizing established minimum training standards and documented experience. CICCS Terminology Certification: The process whereby the State Fire Marshal's Office confirms through the issuance ofa certificate that an individual has met the required coursework and documented experience. Qualification: The process whereby the fire chief affirms physical fitness and currency ofposition and makes the individual available to the mutual aid system. Background OfCICCS 1995 SFM, OES, Cal Chiefs met with 230 Chiefs and Training Officers to discuss the design, use and implementation ofics 1997 Calabasas Report Presents Findings 1998 California Incident Command Certification (CICCS) Task Force Established 1999 CICCS Task Force Presents Recommendations November 2000 CICCS Adopted by State Board of Fire Services

36 Why Do We Need The CICCS? Gordon Graham's Risk Matrix Calabasas After Action Report Findings:» Development of qualification and experience requirements for personnel assigned to wildland/urban interface incidents» Develop minimum training standards» Mandatory shelter training» A standard should be developed defining the qualification and experience requirements for pe",onnel in key field positions Low Frequency Low Frequency High Risk High Risk ~ For MOlt Municipal Firt Department' Wildland PlrenllatiDI,.U. Into Tht Low F~ueDcylHilh Risk Mockl, I.e.dine T. Hieber UabiJIty CICCS Task Force Recommendations Historical Recognition oftraining and Experience ofexisting Personnel for a 2 year period System Components - Peer Review Boards - Position Task Books's - NWCG Cou",es orequivalency Use ofnational Wildfire Coordinating Group (NWCG) Fonnat National Wildfire Coordinating Group 310-1»Only "Certs & Quais" Model In Existence»Easily Adapted To All Risk Applications»Compatible With Incident Qualifications System (Computer Database Program)»Adopted By - Five Party Agreement ledf. OES. USFS. BLM <\ NPS) - State Board offire Services - FlRESCOPE - California Fire Chiefs Association - NIOSH & OSHA 2

37 NWCG System Components State Fire Marshals Office California Incident Command Certification System Level Minimum Training Standards Experience Physical Fitness Standards Computer Tracking System - IQS (Incident Qualification System) Currency Requirements eue ars s ce California Incident Command Certification System ICS Level PEER Review Local-ByHome Agency >ICS 100 & 200 Level Positions >Fire ChiefAuthorization DES Operational Area >ICS300 Level Positions >ICS "Leader" Level Positions DES Regional Area >ICS 400 Level Positions >ICS Command & General StalfLever SFMD PACE V Committee >les SOO-6OO Position Level 3

38 Historical Reco&,nition >Two Year Period to submit Application (from time ofciccs implementation) > Position Specific > Application to include experience and training... o. :Ir.. ~',;.::: w..u c. NWCG Eguivalencies ""':::110' Co.,,...,......,. T, laol. 'n.... T... II I Co.",... '10.11., Il. C.,lolo O, U... 1 lou... I ~ III"""'J h II '0 t hu., I J '1...rr c. u "....'I...,.,~'~',';'.:~:'::..;::.::...._... ":..';! {;:.:: NWCG Eguivalencies.,.. M......,... ( H... c., :~.'~.,11, M 'n.., ". c.. CI'... I J" NWCG Eguivalencies II[FI1 'E 4

39 ( ICS Level Peer Review Implementation OfThe ICS Level Peer Review Committees "'Level OfAuthority-LoctJIAgmey Fl,. Chltl Delegated Authority-OES Operati onalarea I> NWCG Firelighter I &0 n Coordinator Or OES Regional Coordinator I> NWCG Appar1Itus Operator ;. ()pcratiomi Area CoordinatorIRcgional Coordinator AceeptJ I> NWCG Company Olli<:er Applationa For Committee Manbenhip From Applicable Orpn&zations And Agencies I> NWCG ICS "Manager" Level ;. Opentional Area Coordinator/RegiouJ. Coordinator Appoinu Peer Ilcview Committee (Initially) }.o Ch.irpenon To Be Elected By CommitteeMembm ;.. Chairpenon Serves A One Year T )... Committee Memben Serve ATwo Year Term mmittee Cannot Hold Additional Positions On The Comminee. i.e. L.A. County..contrac;t Coonty. Metro Department, Fire Di.trict. City Department "'Local AgencyAffirms Qualifications "'UtUiVltion OfIncident Qualification System (IQS) Software Is Recommended )0. An Aatney Represented On The Co ICS PEER Review Committee Membership Representation (Where Applicable) I>City Fire Department I>Metro Fire Department I>Fire Protection District I>CDF I>OES Fire &0 Rescue I>ContnlCt County l>fedeni Wildland Fire Agency I>FedenI Military Fire Agency I>Native American Reservation Fire Agency l>labor Organization I>lndependent Volunteer Fire Department 1>00aIilied ICS Trainin. Soecialist ICS PEERReview Committee Responsibilities "'Meet At LeastAnnually "'Review Applicants Qualifications ).. SMFO Applicatioa ;;. CollfM Completion cnflula ;.. Completed Position Tuk Boob ;.. Lett«From FlJ'e Chid' "'Determine That The Applicant Meets SFMO Standards ).. Chairperson Notifies The Applieant and Hill'Her ChiefOfThe Rcsulu "'Award SFMO Certificate Upon Successful Committee Evaluation 5

40 \ ICS PEER Review Appeal Process ~Applicant Must Appeal In Writing Within 30 Days OfNotification OfDenial To State Fire Marshals Appeals Board. ~SFM Appeals Board Shall Respond To The Appeal Within 30 Days OfReceipt OfAppeal ~Decision OfThe Board Shall Be Final IQS Dalllbase system will be made available to users free ofcharge. ns ~ "'0 "---..f o~ ff" <!" '-91". s~.a'" '>-"l /-fern O\,,~ ~v- '4//V. s'so 'FIvG OFF\C"-?' 6

41 SAFETY OFFICER AND ASSISTANT SAFETY OFFICERS SAFETY OFFICER The Incident Commander (IC) should appoint an Incident Safety Officer at all significant emergency incidents. Complex incidents or those that cover a large geographic area may require the appointment of Assistant Safety Officers. These Assistant Safety Officers can be assigned to geographical areas or functional positions such as Branch Directors, or Division and Group Supervisors. Nothing restricts an Incident Commander from assigning Assistant Safety Officers. Assistant Safety Officers carry the same authority to change unsafe conditions at an incident as the Incident Safety Officer. The following items should be considered regarding the appointment of an Incident Safety Officer. The Incident Safety Officer must be assigned as early in the incident as possible. The Incident Safety Officer reports directly to the IC. The Incident Safety Officer patrols the incident to surveying to identify existing or potential hazards and informs the Incident Commander. The Incident Safety Officer recommends to the IC any changes to the incident action plan as a result of the on-going surveys. At an emergency incident where the Incident Safety Officer judges activities unsafe or involve an imminent hazard, the Incident Safety Officer shall have the authority to alter, suspend, or terminate those activities. The Incident Safety Officer needs to immediately inform the incident commander of any actions taken to correct imminent hazards at the emergency scene. At an emergency incident where an Incident Safety Officer identifies unsafe conditions, operations, or hazards that do not present an imminent danger, the Incident Safety Officer should take appropriate action through the Incident Commander to mitigate or eliminate the unsafe condition, operation, or hazard at the incident scene. When operating in forward or otherwise hazardous positions, the Incident Safety Officer must be attired in appropriate personal protective equipment (PPE), including self-contained breathing apparatus (SCBA); have radio communication equipment; and must be accompanied by another firefighter.

42 Function of the Incident Safety Officer The Incident Safety Officer is integrated within the Incident Command System and identified as a member of the Command Staff. Fire departments should define the standard operating procedures for the response of an Incident Safety Officer. The IC should consider Assistant Safety Officers assist the Incident Safety Officer in covering the geographic areas of the incident. The Incident Safety Officer shall be instructed to patrol the scene and report to the IC the status of conditions, hazards, and risks. The Incident Safety Officer shall ensure the fire department's personnel accountability system is being utilized and an incident scene rehabilitation tactical level management component is established. The IC shall provide the Incident Safety Officer with the incident action plan. In the initial stage of the incident, this could be as simple as a verbal report. The Incident Safety Officer shall provide the IC with a risk assessment of incident scene operations. The Incident Safety Officer responsibilities include: Ensuring established safety zones, collapse zones, hot zone, and other designated hazard areas are communicated to all members on scene. Evaluating motor vehicle scene traffic hazards and apparatus placement and take appropriate actions to mitigate hazards. Monitor radio transmissions, and stay alert to transmission barriers that could result in missed, unclear, or incomplete communications. Communicate to the IC the need for Assistant Safety Officers due to the need, size, complexity, or duration of the incident. FIRE SUPPRESSION The function of incident scene safety shall be carried out at all incidents. It is the responsibility of the IC, who cannot perform this function due to the size or complexity of the incident, to assign or request response of a Safety Officer to fill this function. However, there are incidents that require immediate response or on-scene designation of an Incident Safety Officer that has technical expertise. This could include such incidents like a hazardous materials or special operations incidents. These types of incidents should be defined in the fire department's response policy or procedure to ensure the Incident Safety Officer responds. Likewise, some situations require an Incident Safety Officer to 2

43 respond after personnel are on the scene, such as a working fire or at the request of the Incident Commander. A fire department should develop response procedures for an Incident Safety Officer that is on call or designated to respond. Examples could be as follows: ~ Commercial fires ~ Multiple alarm ~ Firefighter injury or firefighter transported for treatment ~ Hazardous materials incident ~ Technical rescue incident ~ At the request of the IC The Incident Safety Officer shall confirm with the IC that a Rapid Intervention Crew/Company is available and ready for deployment and a Rescue Group Supervisor is considered for multiple crews. Where fire has involved a building or buildings, the Incident Safety Officer should advise the IC of hazards, collapse potential, and any fire extension in such buildings. The Incident Safety Officer shall evaluate visible smoke and fire conditions and advise the IC, tactical level management component supervisors, or company officers of the potential for flashover, backdraft conditions, unsafe structural conditions, or other fire events that could pose a threat to operational teams. The Incident Safety Officer should monitor the accessibility of entry and egress of structures and the effect it has on the safety of members conducting interior operations. The need, size, complexity, or duration of an incident can necessitate the need for additional Assistant Safety Officers. Incidents such as high-rise fire, hazardous materials, incidents, and special operations may require additional assistance. In these cases, the Incident Safety Office should request from the IC the need to establish Assistant Safety Officers under the direction of the Incident Safety Officer. Assistant Safety Officers can be assigned to handle scene monitoring, action planning, risk management, interior safety at a high-rise incidents, complex incidents, or operations such as hazardous materials incidents or special operations, or serve as relief for the Safety Officer during extended incidents. Some tasks of the Safety Officer are best performed by individuals with specific expertise. This is particularly true in highly technical areas. Assistant Safety Officer(s) may be appointed to handle the more specialized assignments. Fire departments should endeavor to have more than one qualified individual to perform all essential functions within the Incident Command System. 3

44 " The Incident Safety Officer responsibilities include documenting pertinent information about the incident, including assignments given by the IC, the incident safety plan, obstacles encountered, and significant accidents and/or injuries. It is important to include successful actions as well as those actions that require training or procedural changes to improve incident safety and health for all members. The information that has been provided is not inclusive of all aspects of Safety. The intent was to provide information to fire departments across the country of the need to address this very important Safety Officer area, and to provide additional safety for personnel working in a very dangerous occupation. The area of safety is being addressed in many different ways in the fire service. This area continually needs to be addressed by Incident Commanders and fire departments through training. FIRESCOPE has developed a position description for a Safety Officer and will continue to enhance this very important area. The NFPA 1500 Standard on Fire Department Occupational Safety and Health Program sets a minimum requirement for a fire service related occupational safety and health program. FIRESCOPE members recommend that fire service employees read this document and become familiar with its recommendations. This NFPA 1500 Standard covers a fire department's: Organization; Risk Management Plan; Safety and Health Policy; Roles and Responsibilities; Occupational Safety and Health Committee; Records; Functions of the Health and Safety Officer; Laws, Codes, and Standards; Training and Education; Accident Prevention; Accident Investigation, Procedures, and Review; Risk Management and Data Analysis; Apparatus and Equipment; Facility Inspection; Health Maintenance; Training Frequency and Proficiency; Special Operations Training; Fire Apparatus, Equipment and Driver/Operators; Riding on Apparatus; Inspection, Maintenance, and Repair of Fire Apparatus; Tools and Equipment; Protective Clothing and Protective Equipment for Structural Fire-Fighting and Proximity Fire-Fighting Operations; Protective Clothing for Emergency Medical Operations; Chemical-Protective Garments and Disposal; Protective Clothing and Equipment for Wildland Fire Fighting; Respiratory Protection Equipment and Breathing Air; Fit Testing for SCBA masks; SCBA cylinders; Life Safety Rope and System Components; Eye and Face Protection; Hearing Protection; Emergency Operations - Incident Management; Risk Management During Emergency Operations; Personnel Accountability during Emergency Operations; Members Operating at Emergency Incidents; Rapid Intervention for Rescue of Members; Rehabilitation During Emergency Operations; Civil UnrestlTerrorism; Post Incident Analysis; Facility Safety; Safety Standards; Medical and Physical Requirements; Health and Fitness; Confidential Health Data Base; Infection Control; Fire Department Physician; Member Assistance and Wellness Program; and a Critical Incident Stress Program. 4

45 By reviewing this NFPA Standard, firefighters can obviously see that NFPA 1500 Standard addresses the area of "Safety." This subject is very broad based and there are many different aspects of safety. Fire departments have many obligations which include providing safety equipment and to develop standard operating procedures for their individual members to follow. But, it is incumbent on individual department members to use the personal protective equipment issued and follow Department operational procedures to ensure the safety of all personnel operating on the fire ground. Members that are provided safety clothing shall use the protective ensemble for the type of incident that they are exposed, such as: structural fire fighting, wildland fire fighting, emergency medical incidents, proximity fire fighting, hazardous materials incidents, and other type of incidents. Department members must wear the appropriate respiratory protection when exposed to IDLH atmospheres and a Personal Alert Safety System (PASS) shall be activated prior to entry. Eye, face, and hearing protection needs to be worn when appropriate for protection. Risk Management During Emergency Operations The incident command system starts with the arrival of the first Department company. The first company to arrive shall integrate risk management into the routine functions of incident command. As indicated in NFPA 1500: The concept of risk management shall be utilized on the basis of the following principles: 1) Activities that present a significant risk to safety of members shall be limited to situations where there is a potential to save endangered lives 2) Activities that are routinely employed to protect property shall be recognized as inherent risks to the safety of members, and actions shall be taken to reduce or avoid these risks. 3) No risk to the safety of members shall be acceptable when there is no possibility to save lives or property. As indicated in #2 above, "actions shall be taken to reduce or avoid risks." Identifying potential safety concerns to members and taking actions to reduce risks to firefighters is without a doubt one of the most important things that can be accomplished. The following are just some of the ways to reduce the overall risks to members operating at the scene of an emergency incidents. 5

46 Written guidelines shall be established and used that provide for the tracking and inventory of all members operating an emergency incidents. All members operating at an emergency are responsible to actively participate in the Department's accountability system. The Incident Commander shall be responsible for the overall personnel accountability for the incident. The Incident Commander shall initiate an accountability worksheet at the beginning of the incident and maintain the system throughout the operation. The Incident Commander shall maintain an awareness of the location and function of all companies assigned to an incident. The Incident Commander shall implement Branch Directors, Division/Group Supervisors when needed to reduce the span of control for the Incident Commander. Branch Directors, Division/Group Supervisors shall directly supervise and account for companies operating under their command. Company Commanders are accountable for all company members and company members are responsible to remain under the supervision of their assigned Company Commander. Members shall be responsible for following the personnel accountability system procedures, which shall be used at all incidents. The Incident Command System shall provide for additional accountability personnel based on the size, complexity or needs of an incident. The implementation of Division and Group Supervisors can assist the Incident Commander in this area by reducing the span-of-control. The Incident Commander shall provide for control of access to the incident scene. A Department shall adopt and routinely use a standard personnel identification system to maintain accountability for each member assigned to an incident. There are several accountability systems used during structural fire fighting. The Personnel Accountability System shall provide an accounting of those members actually responding to the scene on each company or apparatus. 6

47 The Incident Command System shall include standard operating guidelines that uses "Emergency Traffic" communication to evacuate personnel from an area where imminent hazard is found to exist and to account for their safety. The fire department standard operating procedure provides direction in the use of clear text radio message for emergency incidents. The standard operating procedure shall use "Emergency Traffic" as the designator to clear the radio traffic. This "Emergency Traffic" can be declared by the Incident Commander (IC), Tactical Level Management Component SupeNisor, or member in trouble or subjected to emergency conditions. As described in the FIRESCOPE ICS-910 document, the radio term "Emergency Traffic" should be used as a designator to clear radio traffic. Clear text should be used to describe the emergency conditions present. Examples of emergency conditions that could be used include: "Firefighter down" "Firefighter missing" "Firefighter trapped" Serious conditions - "All Members Evacuate the Building" Change in conditions - "Wind changed direction from north to south" Hazard identification - "Power line has energized a fence or metal roof' Change in tactics - "Change from offensive to defensive" When a member has declared "Emergency Traffic," that person shall use clear text to identify the type of emergency, change in conditions, or tactical operations. The member who has declared the "Emergency Traffic" shall conclude the condition by transmitting "All Clear, Resume Radio Traffic" to end the emergency situation or to re-open the radio channels for communication after announcing the emergency message. A position description that addresses Firefighter Incident Safety and Accountability is available from FIRESCOPE and is published in the ICS-910 publication. A fire department shall have an operational retreat policy. In addition to an emergency traffic radio message, fire departments could use an additional signal, such as an apparatus air horn, to cause an "evacuation" of personnel. Some departments have incorporated a series of three 10 second short blasts on an air horn with a 10-second silence between each series of blasts of an air horn. For fire departments that adopt this system, it is very important for the Incident Commander to select apparatus away form the command post to reduce the possibility of missing radio messages while the air horns are sounding. 7

48 The Incident Commander should conduct a Personnel Accountability Report (PAR) from each Division or Group Supervisor whenever a change in conditions that could create an unsafe operation such as "Emergency Traffic" announcement to "All Companies Evacuate the Building." When a Division or Group Supervisor is requested to conduct a "PAR," this supervisor is responsible to report on the accountability of all companies or members working within their area of responsibility. This retreat policy and PAR procedure is covered in ICS-910. An Incident Safety Officer shall be appointed by the Incident Commander whenever the IC cannot perform this vital function due to the size or complexity of the incident. At an emergency incident where activities are determined by the incident Safety Officer to be unsafe or to involve an imminent hazard, the incident safety officer shall have the authority to alter, suspend, or terminate those activities. The Incident Safety Officer shall immediately inform the Incident Commander of any actions taken to correct imminent hazards at the emergency scene. At an emergency incident where an Incident Safety Officer identifies unsafe conditions, operations, or hazards that do not present an imminent danger, the Incident Safety Officer shall take appropriate action through the Incident Commander to mitigate or eliminate the unsafe condition, operation, or hazard at the incident scene. The Incident Safety Officer (ISO) shall be designated by the Incident Commander and be integrated with the incident management system as a command staff member. The Incident Safety Officer shall monitor the scene and report the status of conditions, hazards and risks to the incident commander. The Incident Safety Officer can have designated Assistant Safety Officers based upon the need, size, complexity, or duration of the incident. The Incident Commander shall be provided with reports of elapsed time-onscene at emergency incidents in 15 minute intervals from the emergency service organization communication center, until reports are terminated by the Incident Commander. Members operating in hazardous areas at emergency incidents shall operate in crews of two or more. In the initial stages of an incident where only one crew is operating in the hazardous area at a working structure fire, a minimum of four individuals is required. The complement must consist of two individuals working as a crew in the hazard area and two individuals present outside this hazard area available for assistance or rescue at emergency operations where entry into I 8

49 j the danger area is required. The standby members shall be responsible for maintaining a constant awareness of the number and identity of members operating in the hazardous area, their location and function, and time of entry. The standby members shall remain in radio, visual, voice, or signal line communications with the crew. The "initial stages" of an incident shall encompass the tasks undertaken by the fist arriving company with only one crew assigned or operating in the hazardous area. The following examples from NFPA 1500 indicate how a department could deploy a team of four members initially at the scene of a structure fire: a) The team leader and one firefighter could advance a fire-fighting hoseline into the IDLH atmosphere, and one fire fighter and the pump operator become the stand-by members. b) The team leader could designate the pump operator to be the Incident Commander. The team leader and one firefighter enter the IDLH atmosphere, and one firefighter and pump operator remain outside as the standby members. c) The two firefighters could advance the hoseline in the IDLH atmosphere, and the team leader and pump operator remain outside as stand-by members. Once a second crew is assigned or operating in the hazardous area, the incident shall no longer be considered in the "initial stage," and at least one rapid intervention crew/company shall comply with the following requirements: 1) On-scene members designated and dedicated as rapid intervention crew/company; 2) On-scene members performing other functions but ready to re-deploy to perform rapid intervention crew/company functions. The assignment of any personnel shall not be permitted as members of the rapid intervention crew /company if abandoning their critical task(s) to perform rescue clearly jeopardizes the safety and health of any member operating at the incident. As the incident expands in size or complexity, which includes an Incident Commander's requests for additional resources beyond the fire department's initial attack assignment, the dedicated rapid intervention crew/company (RIC'S) shall upon arrival of these additional resources be either one of the following: 1) On-scene members designated and dedicated as rapid intervention crew/company; 9

50 2) On-scene crew/company or crews/companies located for rapid deployment and dedicated as rapid intenention crews; 3) During firefighter rescue operations each crew/company shall remain intact. At least one dedicated rapid intenention crew/company shall be in a "Standby Mode" with equipment to provide for the rescue of members that are performing special operations or for members that are in positions that present an immediate danger of injury in the event of equipment failure or collapse. When more than one RIC is deployed, consider implementing a Rescue Group SupeNisor to manage the multiple Rapid InteNention Companies and to coordinate any rescue attempts when in the "Deployment Mode." Whenever a RIC is deployed, the Incident Commander shall designate another RIC in the "Stand-by Mode" to provide for firefighter safety. Additional areas that are also very important in reducing risks to members are: ~ Effective training ~ Rest and rehabilitation ~ Continuous evaluation of changing conditions ~ Past experience The above information is being provided to supplement fire departments that need assistance in developing or enhancing their standard operating procedures in regards to safety and accountability of their members. 10

51 \.. '.,, ~ J :' llj. ".Ii;,..,;,' ::\'.~ ~ ~.;-.~. FIRESCOPE 30TH YEAR CELEBRATION 2524 MULBERRY STREET RIVERSIDE, CA OFFICE: (909) FAX: (909) " 1/ From: The Olney Family To: lean Collyer Dam: 04/26/2001 TIme: 8:43:00 AM Page 4 oflo March 1, 2001 P. Michael Freeman, Chief Los Angeles County Fire Department 1320 N. Eastern Avenue Los Angeles, CA Dear Chief Freeman, The FIRESCOPE Task Force has reviewed the FIRESCOPE'S Future document developed by the futuring sub-committee of the 30 th Year Celebration Working Group. We feel that the Strategic Initiatives and Objectives portions (attached) may be a good starting point for the Task Force's planned review and validation of the current FIRESCOPE Strategic Plan. Therefore, we ask that the FIRESCOPE Board of Directors review, and if appropriate validate, the Strategic Initiatives and Objectives portions of the FIRESCOPFS Future document. This direction from your Board will make our update of the Strategic Plan more meaningful. If you have any questions. please contact me at Sincerely, ~ Jon Olney Task Force Chair tiar 6 todi

52 From: The Olney Family To: Jean Collyer Dab!!: 04/26/2001 TIme: 8:43:00 AM Page 3 oflo COUNTY OF LOS ANGELES FIRE DEPARTMENT 1320 IoIORTH EASTERN AVENUE los ANGELES. CALFORNIA 1lOO (323) J P. MICHAEL FREEMAN FIRE CHIEF f'oaester a FIRE WARDEN March 7,2001 Chief Mike Dougherty Fire and Rescue Branch Office of Emergency Services 2800 Meadowview Road Sacramento, CA Dear Chief Dougherty: I received the attached correspondence from Chief Jon Olney requesting that the FIRESCOPE Board of Directors review and, if appropriate, validate the Strategic Initiatives and Objectives portions of the FIRESCOPE's Future document. He would like the Board of Directors to review as soon as possible, and thought that maybe they can come to some agreement during the May meeting and provide feedback to him. Therefore, I would like to ask that you please provide a copy to each member of the FIRESCOPE Board of Directors and ask that they send their comments to me no later than March We can then set this as an agenda item for the May meeting and try and reach a consensus. If you have any questions, please feel free to contact me. PMF:cg c: Chief Jon Olney, Task Force Chair AGOURA HILLS ARTESIA AZUSA BALDWIN PARK BELL BELL GARDENS BELlfLOWER BRADBURY CAI.A8ASAS CARSON CEMITOS CLAREMONT COMMERCE COVINA SERVING THE UNINCORPORATED AREAS OF LOS ANGELES COUNTY AND THE CITIES OF: CUDAHY HAWTHORNE LUAIRADA LWJ8U POUONA DIAMOND BAR HIDDEN HILLS LA PUENTE MAYWOOD R...CHO PALOS VERDES DUARTE HUNTINGTON PARK lakewood NOAWAU< ROLLING HILLS EL MON1E 'NDUS1RY lanc"s'er PALMDAlE ROLUNG HillS ESTATES GARDENA INGLEWOOD LAWNDAlE PALOS VERDES ESTATES ROSEMEAD OUENDDRA 'RW'NOAUE LOMITA PARAMOUNT SAN DIMAS HAWAIIAN OAROENS LA CANADA FLINTRIDGE LYNWCOD PICO RIVERA SANTA ClARITA SIGNAL HILL SOUTH ELMO SOUTHGATE TEMPUECITV WALNUT WEST HOLLYWOOD WESTL.'KE VILLA(;~ WHITTIER

53 From: The Olney Family To: Jean Collyer Dab!: 04/26/2001 TIm.,: 8:43:00 AM Page 2 of10 '. STATE OF CA.L1l'ORNIA GOVERNOR'S OFFICE OF EMERGENCY SERVICES Fire and Rescue Braoe" 2800 Meadowview Road SID.nlo, CA Phone (916) Nlght Weekeads: (916) 26%-1621 Fa.: (916) E-M.Il: OES_Flre@ougOY GRAY DAVIS, Goverao. OES #ijj* March 14,2001 Dear FIRESCOPE Board Members: Attached you will find a document titled FlRESCOPE's Future. This document was prepared by the committee consisting ofchiefbob Roper VNC (Chair), Fire Director Ray Quintanar USFS, ChiefRaIph Alworth CDF, ChiefGary Glotfelty OES, and ChiefMike Dougherty OES. Also attached is a letter from Task Force Chair Jon Olney, and ChiefP. Michael Freeman requesting that FIRESCOPE Board members review this document and provide ChiefFreeman feedback by March 31, Thc FIRESCOPE Future: document will be on thc agcnda for the;: May 2001 Fire Advisory CommitteelFlREScOPE Board ofdirectors to develop a final consensus document. If there are any questions please feel free to contact either ChiefFreeman or myself. Sincerely, MICHAEL W. DOUGHERTY, Chief Fire and Rescue Branch c: P. Michael Freeman, Fire Chief, COWlty oflos Angeles Jon Olney, Chief, Task Force Chair File MWDIBea n flexii La

54 ...-'" :;. '.. ' :..,.- -:... "... ",', ",", '.. '.," :.,-...;. ~.,"' ~ ", w ",.....~...' "...,.. :. '. ":..". ~..."..:"..'.."..'::. _ '",. I.,", ". j".'.',. >;". ",.: ".. : : ~n.ln::J... '.'. ".w _~. : r.. _,: - S,3dOJS3~I:I

55 Strategic Initiatives \ The key to planning FIRESCOPE's future is to understand its history and its successes. There were three reports studied that made prior recommendations for FIRESCOPE's future: 1) the 1987 Ryland Research Report, ''Needs Assessment and Sludy ofthe FIRESCOPE Program", 2) the 1991 FIRESCOPE Operations Team "Proposed Five-Year FIRESCOPE Expansion and Implementation Plan", and 3) the 1998 FIRESCOPE "Strategic Plan." The Mission Statement and Vision Statement need to be reviewed regularly for ICS current and future applications. Mission Statement FIRESCOPE's mission is to provide recommendations and technical assistance to the Office of Emergency Services (OES), to maintain the FIRESCOPE "decision process," and to continue the operation, development and maintenance ofthe FIRESCOPE Incident Command System (ICS) and the Multi-Agency Coordination System (MACS) components. Vision Statement The FIRESCOPE vision is to lead the development ofan all-risk management and coordination system, enhance and encourage participation in the statewide mutual aid system for the Fire Services of California and the nation. A working group offirescope members conducted several meetings to review prior documents and discuss FIRESCOPE's future. The following items were composed as strategic initiatives needed to guide the completion ofpat FIRESCOPE projects as well as direct the future offlrescope: A. Creating a Common Voice Within the California Fire Service Unite the California fire service into a common voice to achieve unified goals. Establish a network system to build upon the synergy ofdiverse organizations and individuals. One ofthe foremost ingredients to FIRESCOPE's success was the networking ofits originators. This informal network began to erode barriers to communications and established trust within this group. By personnel simply contacting each other, people could resolve everyday and emergency operational issues. These communications and the synergy ofthe mixed fire service agencies working collectively proved FIRESCOPE could accomplish daunting tasks. An example ofthis is the formation ofics and its impact on national and international emergency response agencies. Those planning the fulure of FIRSCOPE need to remind themselves ofthis type achievement and its benefits. TaskForce Creating a common voice ofthe fire service can harness the power ofdiverse agencies toward unified goals. Today, the California fire service is divided up between many organizations: Metro Fire Chiefs, California Fire Chiefs, Cal Rural Fire Chiefs, Fire Districts' Association, National Wildfire Coordinating group, Western Fire Chiefs, California State Firefighters' Association, California Professional Firefighters, League ofcities Fire Chiefs, Association ofcontract Counties, local area fire chiefgroups, and federavstate fire agencies. The same approach toward achieving goals can be accomplished using the basic tenets that created FlRESCOPE. 4/2001

56 B. Marketing FIRESCOPE and its Products FIRESCOPE needs to be marketed as a process and its products. Active marketing offirescope and its products needs to occur to maintain its position as a leader in the emergency management arena and obtain funding. Marketing will cause technology to adapt to FIRESCOPE's needs rather than FIRESCOPE adapting to the ever-changing field oftechnology. J The marketing success offirescope has been remarkable considering it was performed via word of mouth and by actual demonstrations. The originators offirescope professed its merits to obtain financial support and then directed their own agencies to use its tenets. Actual use ofics on emergency incidents finally put the writing into action where the system was tested and refined for operational efficiency. The success ofics and FIRESCOPE proves itselfas a national model and is now the exclusive organizational management system being instructed at the National Fire Academy. While ICS has been used since 1981, there remains a large group ofemergency management agencies that do not use a common management system and is impacted by the same issues that caused FIRESCOPE to be created. Marketing is essential to maintain the FIRESCOPE process and its products. Vendors and other fire service groups continue to modify ICS and unless maintained, ICS may fall victim to a dilution ofits basic tenets. Marketing does not prevent ICS modifications; it only channels modifications through a decision-making process established by FIRESCOPE. C. Maintain and Improve All-Risk Management Systems FIRESCOPE should never rest on its laurels and should always seek improvement. The key area toward improvement is adopting the latest technology into all-risk management systems, safety, and prevention activities. It is paramount that FIRESCOPE dedicate energy toward the on-going maintenance and improvement of its all-risk management systems. ICS, MACS and other FIRESCOPE products need to be constantly reviewed for non-emergency events and multi-disciplined agencies. Technology is the key area that needs to be endorsed and utilized. All areas offirescope can benefit from the latest technologies and data sharing, but the challenge is to try and keep up with changing technology. The thought then becomes iffirescope can drive the technology market by establishing standards and formats and let the technology market develop their products around them. This direction will allow those agencies that can afford to use the latest technology to still share basic data with other agencies. Mutual aid agreements within California have proven themselves as a model for the nation. Mutual aid philosophies need to be reinforced as they create an actual regionalized fire service, which is quite cost effective for all taxpayers. The California fire service needs to also value the diversity ofthe people and organizations in the DIRESCOPE decision-making process and the all-risk management tool maintenance and development. Diversity has been proven by the 1986 inclusion ofthe OES Advisory Committee into FIRESCOPE and the January, 200I, "Swiftwater/Flood Search and Rescue, ICS-US&R-120-2, and the Law Enforcement Mutual Aid Plan (SAR) Annex." We should continue to seek other diverse interests within the fire service and multi-disciplines in the future. Task Force 2 4/2001

57 Objectives Creating a Common Fire Service Voice Objectives: Improve and maintain emergency management leadership through interagency cooperation. Promote participation for all agencies within California in the Mutual Aid System and provide assistance to these agencies to prepare and participate in planned or unplanned events. Promote MACS training and exercises. Create common public safety prevention and response strategies. B. Marketing FIRESCOPE and Its Products Objectives: Establish a FIRESCOPE Board ofdirectors group to develop mechanisms to promote awareness ofthe FIRESCOPE philosophy. Develop the Board ofdirectors as the focal point to identify other organizations that may influence FIRESCOPE and promote FIRESCOPE philosophies with these organizations. Charge the Board ofdirectors to develop a business and financial plan to support the administrative support offiescope. Utilize fire service public education as a marketing tool. C. Maintaining and Improving AIl-Risk Management Systems Objectives: Support multi-agency training on FIRESCOPE developed components and products. Develop statewide certification and qualifications standards. Provide Training regarding new technology. Continue to evaluate and refine FIRESCOPE products. Research potential and/or improved methods offorecasting fire behavior and weather patterns. Initiate a working group to research and participate in development oftechnologies to improve on prevention, safety, and on-scene incident command needs. Provide improved incident information and intelligence mechanisms for media and regional command purposes. Maintain and improve methods for coordinating multi-disciplined agency resources for planned and unplanned events. Coordinate with Regional Emergency Operations Centers (REOe) for improving multiagency coordination. Provide a system that assists Emergency Operations Centers and SEMS to interface. Improve methods ofmulti-agency communications by using new technologies. Promote the need to develop an interstate communications system. Maintain and explore new mutual aid options. Maintain the California Fire Service Mutual Aid Communications agreement. Implement a common statewide mapping system. Review and update standard terminology for improving incident management. Create common data standards and formats to drive new technology. TaskForce 3 4/2001

58 meeting 3