Strategic Allocation of Tactical Resources Sample Clauses

Strategic Allocation of Tactical Resources. During the fire season, as necessary, daily meetings include the DNR Statewide Preposition Conference Call, the AFS Tactical Meeting, the Daily Statewide Tactical Meeting, the Statewide Weather Briefing, and Area/Zone/Forest briefings. Each Protecting Agency will decide which resources will be made available for standby, pre-positioning, or commitment to an incident. The USFS Regional Fire Specialist will be the focal point for USFS resources. During the Daily Statewide Tactical Meeting (routinely attended by the DNR Fire Operations Forester, the AFS Chief, Division of Fire Operations, and the AICC Manager, and available to jurisdictional representatives), the final distribution of resources will be made. The location and status of the statewide shared tactical resources will be conveyed to the Agencies and Interagency Fire Dispatch Centers via the teletype, the Daily Statewide Tactical Meeting, and/or Integrated Fire Management (IFM). Considerations for resource distribution include: • Use of all available in-state resources • Ordering of additional resources from the Lower 48 or Canada • Alaska and National Preparedness Levels • Severity funding requests both agency-specific and interagency • Draw-down and Step-up plans Once the distribution of resources has been established, the priority for dispatch of these statewide tactical resources will be based on protection priorities as established in the AIWFMP. Strategic resource decisions determined by the Daily Statewide Tactical Meeting will be communicated to the Agencies and the Interagency Fire Dispatch Centers via the teletype and/or IFM.
AutoNDA by SimpleDocs

Related to Strategic Allocation of Tactical Resources

  • Allocation of Resources Whenever a disaster causes Vendor to allocate limited resources between or among Vendor's customers, vendor will not provide priority over Prudential to any other customers of Vendor. In addition, in no event will Vendor re-deploy or reassign any vendor Key Employee (as identified and defined in an applicable Engagement Schedule) or any Affected Employee (as identified and defined in an applicable Engagement Schdule) to any other Vendor account in the event of a disaster.

  • Project Administration Designation Pursuant to Paragraph (B) of Rule 164-1-21 of the Administrative Code, the Recipient shall designate its Chief Executive Officer, Chief Fiscal Officer and Project Manager in Appendix B of this Agreement. Changes in these designations must be made in writing.

  • Relationship Management LAUSD expects Contractors and their Representatives to ensure that their business dealings with and/or on behalf of LAUSD are conducted in a manner that is above reproach.

  • Certification of Funds; Budget and Fiscal Provisions; Termination in the Event of Non-Appropriation This Agreement is subject to the budget and fiscal provisions of the City’s Charter. Charges will accrue only after prior written authorization certified by the Controller, and the amount of City’s obligation hereunder shall not at any time exceed the amount certified for the purpose and period stated in such advance authorization. This Agreement will terminate without penalty, liability or expense of any kind to City at the end of any fiscal year if funds are not appropriated for the next succeeding fiscal year. If funds are appropriated for a portion of the fiscal year, this Agreement will terminate, without penalty, liability or expense of any kind at the end of the term for which funds are appropriated. City has no obligation to make appropriations for this Agreement in lieu of appropriations for new or other agreements. City budget decisions are subject to the discretion of the Mayor and the Board of Supervisors. Contractor’s assumption of risk of possible non-appropriation is part of the consideration for this Agreement. THIS SECTION CONTROLS AGAINST ANY AND ALL OTHER PROVISIONS OF THIS AGREEMENT.

  • Distribution of UDP and TCP queries DNS probes will send UDP or TCP “DNS test” approximating the distribution of these queries.

  • Special Aggregation Rule Applicable to Relationship Managers For purposes of determining the aggregate balance or value of accounts held by a person to determine whether an account is a High Value Account, a Reporting Financial Institution shall also be required, in the case of any accounts that a relationship manager knows or has reason to know are directly or indirectly owned, controlled, or established (other than in a fiduciary capacity) by the same person, to aggregate all such accounts.

  • Virus Management DST shall maintain a malware protection program designed to deter malware infections, detect the presence of malware within DST environment.

  • Traffic Management 9.2.1 During the Operating Period, Developer shall be responsible for the general management of traffic on the Project. Developer shall manage traffic so as to preserve and protect safety of traffic on the Project and Related Transportation Facilities and, to the maximum extent practicable, to avoid disruption, interruption or other adverse effects on traffic flow, throughput or level of service on the Project and Related Transportation Facilities. Developer shall conduct traffic management in accordance with all applicable Technical Provisions, Technical Documents, Laws and Governmental Approvals, and in accordance with the Traffic Management Plan. 9.2.2 Developer shall prepare and submit to TxDOT and the Independent Engineer for TxDOT approval a Traffic Management Plan for managing traffic on the Project and Related Transportation Facilities after the commencement of traffic operations on any portion of the Project, addressing (a) orderly and safe movement and diversion of traffic on Related Transportation Facilities during Project construction, (b) orderly and safe movement of traffic on the Project and (c) orderly and safe diversion of traffic on the Project and Related Transportation Facilities necessary in connection with field maintenance and repair work or Renewal Work or in response to Incidents, Emergencies and lane closures. Developer shall prepare the Traffic Management Plan according to the schedule set forth in the Technical Provisions. The Traffic Management Plan shall comply with the Technical Provisions and Technical Documents concerning traffic management and traffic operations. Developer shall carry out all traffic management during the Term in accordance with the approved Traffic Management Plan. 9.2.3 Developer shall implement the Traffic Management Plan to promote safe and efficient operation of the Project and Related Transportation Facilities at all times during the course of any construction or operation of the Project and during the Utility Adjustment Work. 9.2.4 TxDOT shall have at all times, without obligation or liability to Developer, the right 9.2.4.1 Issue Directive Letters to Developer regarding traffic management 9.2.4.2 Provide on the Project, via message signs or other means consistent with Good Industry Practice, non-Discriminatory traveler and driver information, and other public information (e.g. amber alerts), provided that the means to disseminate such information does not materially interfere with the functioning of the ETCS.

  • Management Responsibilities The exclusive representative recognizes the right and obligation of the School Board to efficiently manage and conduct the operation of the School District within its legal limitations and with its primary obligation to provide educational opportunity for the students of the School District.

  • Cost Responsibility for Interconnection Facilities and Distribution Upgrades 4.1 Interconnection Facilities 4.2 Distribution Upgrades

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!