TERMINAL USE PRIORITIES. (Established t o determine priority access during Modes 3 end 4) Coordination or Resources end Situation Information within

Transcription

1 8/2/81 1. F. ~~~/?! TERMINAL USE PRIORITIES (Established t o determine priority access during Modes 3 end 4) Priority 1 Coordination or Resources end Situation Information within the FlRESCOPE Region. 1. Terminals at MUlti-Agency Coordination Centers: e.g., Operational Areas, Regional Fire end Rescue Coordinators, CDF, ECC and USFS South Zone. 2. Terminals at Agency Coordination Centers; e.g.' Forests, Ranger Units 3. Terminals assigned at incidents Priority 1 users. ECC RRU ANF BLM cov SEC BDF NZF DNY SDC Bro RO 6 H/W GLN VNC CNF SZF H/W LAC MAC Hjw INF Fire 1 LFD OC1 Hjw LPF Fire 2 LOB OC2H/W MW Fire 3 ORC RAA SNF Fire 4 RDB RYA SQF Fire 5 Priority 2 Official need for information provided through FIMS software. E.g., Weather, FIREMOD, INc 209, Advisors, etc. No direct coordination or input through FIMS except electronic mail. Not 1imdted to FIRESCOPE Region.

2 Priority 2 users 13IF CDF/SAC CFA (IONG) JOB (wo) R05 SZA OES Priority 3 Authorized access 'for electronic mali, procedures development and program maintenance. Priority 3 users PROGRAMMERS ( 9) 3 Hjw PROG. OFF (2) MOM Hjw SSM Hjw TEM.JAM CDI CFP GHQ JWC SC3 SC7 SIMULTANEOOS USER CAPACITY Now Possible Expansion Total l4 TELENET 9 Dial In 8 Hard vired 3l 28 TELENET and/or l6 Dial In 8 Hard vired 52

3 ' Alhuh ment B. 8/3/81 T.f. sf, /!1 RESOURCES DESIGNATION SYSTEM 1. BACKGROUND To rapidly and accurately identify Strike Teams, Task Forces and increments used in multi-agency applications within the FIRESCOPE Region it is necessary to have a standard inter-agency system. A system for designating Strike Teams and Task Forces was developed by the FIRESCOPE Task Force in 1976,' tested, and made a part of the Incident Command System in A modification to that system was recommended and implemented in June of The inter-agency planning group responsible for the development of the Resources Status Keeping Unit Training Course at!one has recommended to the FIRESCOPE Task Force that the system now in use within the FIRESCOPE Region be expanded to include a way to designate the kind of Strike Teem (i.e., engine crew or dozer) as well as to differentiate between agency owned resources and mixed agency Strike Teams and Task Forces. The system modification will now also provide for the dispatch of Task Forces to an incident. (Previously in the ICS, Task Forces could only be formed at the incident.) The FIRESCOPE Task Force has reviewed the recommendation of the Training Group end with some minor modifications is recommending approval of that system for testing, with planned implementation within the FIRESCOPE Region in Training Course materials 1

4 being prepared under contracts et!one would include the recommended changes. The system change recommendation makes only minor changes to the existing system. The changes ere co~tible with both, the FIMS Resource Status system (RES~T) and the manuel T-cerd system in use at incidents and at some agency dispatch centers. The changes ere: 1. The kind of Strike Team is now indicated in the designation. 2. OES owned equipment is indicated with a Region ID No. 3. Mixed Agency equipment is seperetely designated with e Region ID No. 4. CDF Ranger Units would use individual three letter ID's. 5. More numbers ere provided for Agency formed Strike Teems end Task Forces. 6. Agencies may now dispatch Task Forces to incidents. 2. GENERAL FORMAT The Forces and single program or in the the way in which Strike Teams, Task designated within the FIMS RESTAT Detailed examples of specific iven in Section 3. 2

5 1-4 numbers indicating number assigned., ~----~ numbers indicating kind end type of resource. (Not applicable to Task Forces.) L ~~--~--- 2 letters indicating Strike Teem (ST) or Tesk Force {TF). (Not applicable o increments.) 3 characters indicating ownership. 3. STRIKE 'I'.EAM3 AND TASK FORCES 3.1 Agency Identification Assigned three letter designators will be used for ell agency owned resources in Strike Teems end.task Forces. CDF resources would now use three letter designators for individual ranger units. Example: VNC ST 1101 LPF TF 5 RRU ST 1311 (Ventura County Strike Teem) (Los Padres Net. Forest Task Force) (CDF Riverside Ranger Unit Strike Teem) OES owned apparatus when formed into Strike Teems or Task Forces will be assigned en OE designation followed by the region number which formed the Strike Teem/Task Force. 3

6 ' Example: OEl ST 1101 OE6 TP' {OES owned equipment-strike Team from Region 1) {OES owned equipment-task Force from Region 6) ~ed agency equipment when formed into Strike Teems or Tes~ n -~) oe s (mas ~r fm.. ~lm'jl AI Forces will be designated by en MA followed by the region number rom which t:enbd: the resources.were +orw.t~. ) " Example: ST 1213 TF 7 (Mixed Agency Strike Teem formed within Region 6) {Mixed Agency Task Force formed within Region 1) 3.2 Strike Teem end Task Force Numbering The first number indicates the kind of resource: {Not applicable to Task Forces Engines = 1 Crews = 2 Dozers 3 LA c. sfr (j)z o 'I ~ The second number designates the ~of the resource: (Not applicable to Task Forces Type 1 = 1 Type 2 = 2 Type 3 = 3 Type 4 = 4 L AC S/r t(j) OLf A Third and fourth number indicates the Strike Team or Task Force number. Agency assigned 1-79 Incident assigned ao-99 (Agencies will use the same rw'pbsr qrs*e= for designating Strike Teams and Task Forces.) ~ 4

7 3. 3 Examples Strike Teams ~F S/T 1301 =Engines, Type 3, First S/T assembled from SHNF. BDF S/T 2102 = Handcrews, Type 1, Second S/T assembled from SHNF. I ANF S/T 328( = Dozers, Type 2, First S/T formed et en incident. LAC S/T 1205 = Engine, Type 2, Fifth S/T assembled from Los Angeles County Mixed Agency Strike Teem An example of e Strike Teem made up of mixed agency resources would be: 3 LAC engines 1 LFD engine 1 GLN engine RESTAT Format S/T 1123 (~ S"rrikt_ Tu~ {u).,w c.ovjj. k trhy\ (4y ~~ency Task Forces Radio Call 'MA one strike team eleven twenty three" If e Task Force is formed, the initials T/F ere used instead of S/T. For example: RESTAT Format ANF T/F 03 Radio Call Angeles Task Force three" AgettCj asstgtted Incident aaa1smai If e Mixed Agency Task Force was formed on en incident, it would have the following RESTAT format end radio cell: RESTAT Fonnet. T/F 81 Radio Cell ''MA one task force eighty one 5

8 3.3.4 Agency Combined Resources Within the USFS, CDF 1 and OES statewide system, Strike Teams may be made up of resources from more than one forest, more than one ranger unit, or more than one OES region. Such combinations WQ~i resources. For example: 2 type 3 engines from the Angeles 2 ANF 3 type 3 engines from the San Bernardino 3 BDF The Strike Team Leader is from the'11i1a'iff.adl tibte. RESTAT Fo:nnat BDF SfT Radio Call "San Bernardino Strike Team thirteen zero one" 3 type 3 engines from Riverside Ranger Unit 3 RRU 2 type 3 engines from San Bernardino Unit The Strike Team Leader is from lim JLI e ~a~~ Ran!!;El L 2 BW RESTAT Format RRU S/T type 1 OES engines OES Region 1 2 type 1 OES engines OES Region 6 Radio Call "Riverside Strike Team thirteen eleven" 3 OEl 2 OE6 The Strike Team Leader is from OES Region 1. RESTAT Format OEl SfT 1105 Radio Cell "OEl Strike Team eleven zero five" 6

9 . 4 INCREMENT DESIGNATIONS Increment designation remains the same with the exception of CDF and OES: Examples: RESTAT Format :BDF LAC RRU OEl Radio Call "San Bernardino engine four thirteen" ''Los Angeles County crew seven one" ''Engine Sixty one eighty five" "OES one forty six" 5. :BLOCK NUMBER ASSIGNMENTS (Ross and :Barrows) ~~I Rufiol\ I, J. 5,2.. ~;dl1 '. 7

10 ~1Al STRIKE TEAM DESIGNATOR AND NUMBER FOR MIXED AGENCY RESOURCES REGION I Los Angeles Area "A" Coordinator II " " Area "B" 11 II " " Area "C 11 " Area 11 II D" 11 " Area II E II " " Area "F" II " " Area "G" Orange Area Coordinator Santa Barbara Area Coor.dina tor Ventura Area Coordinator San Luis Obispo Area Coordinator Los Padres NF, USFS Angeles NF, USFS EXAMPLE: 3 LFD Eng. 2 SMA Eng. LFD S/T Leader RESTAT Format S/T 1101 (LFD Formed S/T) Radio Call MA One Strike Eleven-if" One zc.~o Team 2 ARC Eng. 2 MRV Eng. 1 SMD Eng. MRV S/T Leader S/T (ARC Formed S/T) MA One Strike Eleven Twenty Team Six 2 ANF Eng. 2 LAC Eng. 1 LFD 1 LAC S/T Leader S/T 1377 (ANF Formed S/T) MA One Strike Team Thirteen Seventy Seven

11 STRIKE TEAM DESIGNATOR AND NUMBER FOR MIXED AGENCY RESOURCES OES REGION 6 Imperial County Area Coordinator Inyo County Area Coordinator Mono County Area Coordinator Riverside County Area Coordinator San Bernardino County Area Coordinator San Diego County Area Coordinator San Bernardino National Forest USFS Cleveland National Forest USFS San Bernardino Ranger Unit CDF San Diego Ranger Unit CDF Inyo National Forest USFS EXAMPLES 3 BDF Engines 2 BDU Engines BDF S/T Leader 3 BDO Engines 2 BDC Engines BDC S/T Leader 3 BDU Engines 2 BDC Engines BDU S/T Leader RESTAT FORMAT RADIO CALL S/T 1351 MA Six Strike Team Thirteen Fifty One (BDF Formed Strike Team) S/T 1321 MA Six Strike Team Thirteen Twenty One (BDC Formed Strike Team) S/T 1363 MA Six Strike Team Thirteen Sixty Three (BDU Formed Strike Team)

12 8/4 GOAL 4 OBTAIN MOST APPROPRIATE AVAILABLE RESOURCES There are basically two problems to overcome to achieve this goal. 1. Knowing where the closest resources are In certain instances resources of other agencies may be actually closer to an incident than those of the responsible agency. Using the resources of another agency in an initial or extended attack may prove to be the difference in prompt suppression. There are many existing automatic aid agreements now in effect which allow for using another agencies resources. Resources already on assignment or just relieved of assignment can on occassion be much closer to another agencies new incident than the resources of that agency. This could include, engines, crews, helicopters etc. FIMS RESTAT does not keep track of resource assignments other than by major incident. Thus there is no present way to find these resources except through the agency which owns them. This process is some times time consuming and sometimes not even thought about. Consequently responsible agency resources may be dispatched when closer in resources 2. are actually available. Paying for the use of the resource.~~ rft~jt ~ 1.4(U' At the :present time, except fora t ~e master mutual aid agreement, there is no easy way to reimburse an agency for the use of its resources in situations outlined above. Reciprocity as such is often times a one way street.

13 FIRESCOPE OPERATIONS COORDINATION CENTER DOCUMENTATION CONTROL UNIT P.O. BOX RIVERSIDE. CALIFORNIA TO: FROM: Bob Irwin FIRESCOPE Program Manager Claude Creasey, Chairman FIRESCOPE Task Force DATE: August 11, 1981 SUBJECT: Document Control FIMS Manual The Task Force on August 5, 1981, agreed that the FIRESCOPE Information Management System (FIMS) Users Manual, dated June 1981 should be included in the Multi-Agency Coordination System Document Control System.as per FIRESCOPE Publication The present manual that has been distributed to many of the FIMS Users in the FIRESCOPE Region does not conform to the MACS Document Control format. The manual should be updated, a table of contents developed, and the master document sent to the Task Force for review prior to inclusion in the document control system. The Task Force decided that the most expedient way to correct the situation is to send copies of the approved FIMS Manual table of contents to each FIMS user. Then if the user finds any portio~s missing, then additional chapters could be ordered to complete the manual. It is anticipated that each section of the FIMS Manual will be reviewed and a routine reprinting job done within the next year. pe Claude Creasey, Chairman FIRESCOPE Task Force

14 FIRESCOPE OPERATIONS COORDINATION CENTER DOCUMENTATION CONTROL UNIT P.O. BOX 5"5157 RIVERSIDE. CALIFORNIA TO: Roger Land DATE: August 11, 1981 Service & Support Manager FROM: SUBJECT: Claude Creasey, Chairman FIRESCOPE Task Force FIRESCOPE Information Management System Prime Computer Use Audit In order to accurately assess the potential for "overloading" the access ports of the Prime during high use periods, the Task Force requests that you produce an audit showing the maximum number of users at any one time during high use periods. This information is necessary in order to determine the actual need for limiting the number of computer LOGIN Identifiers. pe Claude Creasey, Chairman FIRESCOPE Task Force

15 FIRESCOPE OPERATIONS COORDINATION CENTER DOCUMENTATION CONTROL UNIT P.O. BOX RIVERSIDE. C.ALIFORNIA TO: Bob Irwin, Chairman FIRESCOPE Operations Team DATE: August 11, 1981 FROM: SUBJECT: Claude Creasey, Chairman FIRESCOPE Task Force FIRESCOPE Information Management System Terminal Use Priorities As directed by the OPS Team at their July meeting, the Task Force has developed criteria for establishing priority access to FIMS during Modes 3 & 4. Additionally, all current LOGIN ID's have been identified by priority. According to the ADP Computer System Manager, it has not been proven that a problem of "systems overloadn, in fact, exists. The Task Force has asked the SSM to establish system audit procedures to provide this information. The ADP personnel have assured us that system access can be controlled or restricted by priority during any mode, either electronically or by self-discipline. Since these system Gontrols can be employed, the Task Force recommends that the Operation Team continue issuing LOGIN Identifiers, but assigning the user to on~ of the three listed priority categories. (See the attached draft.) Attachment pe Claude Creasey, Chairman FIRESCOPE Task Force.