Emergency Management Assistance Compact Sample Clauses

Emergency Management Assistance Compact. (EMAC) Membership National Incident Management System (NIMS) Implementation Maintenance of Effort Cost Match Criteria
Sample 1
AutoNDA by SimpleDocs
Emergency Management Assistance Compact. (EMAC)‌ Per Ohio Revised Code (ORC) 5502.4, the purpose of this compact is to provide for mutual assistance between the states entering into this compact in managing any emergency or disaster that is duly declared by the governor of the affected state(s), whether arising from natural disaster, technological hazard, man-made disaster, civil emergency aspects of resources shortages, community disorders, insurgency, or enemy attack. This compact shall also provide for mutual cooperation in emergency-related exercises, testing, or other training activities using equipment and personnel simulating performance of any aspect of the giving and receiving of aid by party states or subdivisions of party states during emergencies, such actions occurring outside actual declared emergency periods. The EMAC process may be used to support a Public Health Emergency at either a State, or local jurisdiction level. When local resources are exhausted, resource requests may be sent to the Ohio EMA. The process for these requests will be made in the same way as above (Authorized by the Health Commissioner and sent by the Logistics Chief to the local EMA). The local EMA Director will then forward the request to the State EMA. When the request reaches the State EMA, the state sources the resource need to IMAC, federal, private sector, volunteer, or EMAC. All EMAC requests must follow Ohio EMA instructions and procedures. The request for EMAC resources is an executive level decision. The Ohio Department of Health Director, the Director of State Department of Public Safety, the State EMA Executive Director, and the Governor’s Office decide if EMAC assistance will be sought. To request EMAC resources the Governor will declare an emergency or disaster, authorizing funds to be expended for response and recovery, and activating EMAC. The affected state’s EMAC Authorized Representative or EMAC Designated Contact opens an event in the online EMAC Operations System, alerting both the National Coordinating State and National EMA that a request for resources is likely. See also Attachment XV: EMAC Request and Fulfillment Process. RPH or SCHD may also receive a request for EMAC. Receiving states will only accept resources from the State of Ohio. For local resources to qualify as State Once the provision of the resource has been approved by the RPH/SCHD Health Commissioner, the asset is found and released by the applicable Director. Ohio EMA will begin a dialog with the requesting state, in co...
Sample 1
Emergency Management Assistance Compact. (EMAC) or other mutual aid agreements for medical and public health mutual aid to support coordinated activities and to share resources, facilities, services, and other potential support required when responding to public health emergencies.
Sample 1
Emergency Management Assistance Compact. The Emergency Management Assistance Compact is a national interstate mutual aid compact that facilitates the sharing of resources, personnel, and equipment across state lines during times of disaster and emer- gency. EMAC was legislated by each member state legislature and governor and ratified and signed into law by the U.S. Congress (P.L. 104-321) in 1996.1 The 50 states, the District of Columbia, Puerto Rico, and the U.S. Virgin Islands have enacted EMAC legislation.2 EMAC is envisioned as the cornerstone of national mutual aid, intended to facilitate the efficient and effective sharing of resources between member states during times of emergencies or disasters affect- ing a member state. In 1992, Hurricane Xxxxxx slammed into Florida. In response, the Southern Governors Association began development of a mutual aid compact. In 1993, 17 governors signed the Southern Region Emergency Management Assistance Compact, later expanded to EMAC, the first national compact since the Civil Defense Act of 1950. EMAC was activated for the first time during Hurricane Opal in 1995, with the National Emergency Management Association (NEMA) assuming the role of administrator (Bea 2006; Kapucu 2005; NEMA 2006b, 2000; Xxxx 2003; Xxxxxxxxx 2002). Currently, all 50 states, the Dis- trict of Columbia, Puerto Rico, and the U.S. Virgin islands are members of EMAC. The compact is ad- ministered by NEMA and includes key provisions for reimbursement, liability, and workers compensation (NEMA 2006b). EMAC establishes an implementation plan whereby member states agree to standard operating procedures for requesting and providing assistance. EMAC requires that the legislatures of each member state ratify the compact language, which eliminates confusion over who is a member of the compact and provides a legal framework to facilitate assistance and reimbursement. EMAC addresses all of the issues associated with re- questing assistance, reimbursement of services, workers’ compensation, insurance, and liability in advance of a disaster (Xxxxxxxx 2006; Xxxxxxxxx 2002). EMAC allows states to assist each other with some certainty of the expectations and responsibilities involved, which, in turn, increases the likelihood of them doing so at con- siderably reduced risk of suit or great expense. EMAC activation, in simplified terms, occurs in four steps: (1) a disaster occurs, and a state governor de- clares a state of emergency; (2) the state emergency management agency assesses the state’s ...
Sample 1
Emergency Management Assistance Compact. Guidebook and Operating Procedures. Lexington, KY: NEMA. ———. 2006a. EMAC Post-Deployment Survey Results. xxxx://xxxx.xxxxxxx.xxx/?866 [accessed December 1, 2008]. ———. 2006b. NEMA 2006 Biennial Report: Organizations, and Operations, and Funding for State Emergency Management and Homeland Security. Lexington, KY: NEMA. ———. 2006c. 2005 Emergency Management Assistance Compact Hurricane Season After- Action Report. xxxx://xxx.xxxxxxx.xxx/ [accessed December 1, 2008]. Xxxxx, X. Xxxxxxx, and Xxxx X. Xxxxx. 1990. Loosely Coupled Systems: A Reconceptualization. Academy of Management Review 15(2): 203–23. Xxxxxx, Xxxxxx. 1990. Governing the Commons: The Evolution of Institutions for Collective Action. New York: Cambridge University Press. X’Xxxxx, Xxxxxxxx X., Jr. 2000. American Intergovernmental Relations: Foundations, Perspectives, and Issues. 3rd ed. Washington DC: CQ Press.
Sample 1
Emergency Management Assistance Compact. (EMAC) Membership
Sample 1

Related to Emergency Management Assistance Compact

  • Emergency Assistance Both Parties shall exercise due diligence to avoid or mitigate an Emergency to the extent practical in accordance with applicable requirements imposed by the Standards Authority or contained in the PJM Tariffs and NYISO Tariffs. In avoiding or mitigating an Emergency, both Parties shall strive to allow for commercial remedies, but if commercial remedies are not successful or practical, the Parties agree to be the suppliers of last resort to maintain reliability on the system. For each hour during which Emergency conditions exist in a Party’s Balancing Authority Area, that Party (while still ensuring operations within applicable Reliability Standards) shall determine what commercial remedies are available and make use of those that are practical and needed to avoid or mitigate the Emergency before any Emergency Energy is scheduled in that hour.

  • Enterprise Information Management Standards Grantee shall conform to HHS standards for data management as described by the policies of the HHS Office of Data, Analytics, and Performance. These include, but are not limited to, standards for documentation and communication of data models, metadata, and other data definition methods that are required by HHS for ongoing data governance, strategic portfolio analysis, interoperability planning, and valuation of HHS System data assets.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • STATEWIDE CONTRACT MANAGEMENT SYSTEM If the maximum amount payable to Contractor under this Contract is $100,000 or greater, either on the Effective Date or at any time thereafter, this section shall apply. Contractor agrees to be governed by and comply with the provisions of §§00-000-000, 00-000-000, 00-000-000, and 00- 000-000, C.R.S. regarding the monitoring of vendor performance and the reporting of contract information in the State’s contract management system (“Contract Management System” or “CMS”). Contractor’s performance shall be subject to evaluation and review in accordance with the terms and conditions of this Contract, Colorado statutes governing CMS, and State Fiscal Rules and State Controller policies.

  • Utilization Management Contractor shall maintain a utilization management program that complies with applicable laws, rules and regulations, including Health and Safety Code § 1367.01 and other requirements established by the applicable State Regulators responsible for oversight of Contractor.

  • 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.

  • Transportation Management Tenant shall fully comply with all present or future programs intended to manage parking, transportation or traffic in and around the Building, and in connection therewith, Tenant shall take responsible action for the transportation planning and management of all employees located at the Premises by working directly with Landlord, any governmental transportation management organization or any other transportation-related committees or entities.

  • Emergency Manager An Emergency Manager appointed under Local Financial Stability and Choice Act is authorized to reject, modify, or terminate this Agreement as provided in the Local Financial Stability and Choice Act, 2012 Public Act 436.

  • Routing for Operator Services and Directory Assistance Traffic For a Verizon Telecommunications Service dial tone line purchased by CBB for resale pursuant to the Resale Attachment, upon request by CBB, Verizon will establish an arrangement that will permit CBB to route the CBB Customer’s calls for operator and directory assistance services to a provider of operator and directory assistance services selected by CBB. Verizon will provide this routing arrangement in accordance with, but only to the extent required by, Applicable Law. Verizon will provide this routing arrangement pursuant to an appropriate written request submitted by CBB and a mutually agreed-upon schedule. This routing arrangement will be implemented at CBB's expense, with charges determined on an individual case basis. In addition to charges for initially establishing the routing arrangement, CBB will be responsible for ongoing monthly and/or usage charges for the routing arrangement. CBB shall arrange, at its own expense, the trunking and other facilities required to transport traffic to CBB’s selected provider of operator and directory assistance services.

  • Emergency Room Services This plan covers services received in a hospital emergency room when needed to stabilize or initiate treatment in an emergency. If your condition needs immediate or urgent, but non-emergency care, contact your PCP or use an urgent care center. This plan covers bandages, crutches, canes, collars, and other supplies incidental to your treatment in the emergency room as part of our allowance for the emergency room services. Additional services provided in the emergency room such as radiology or physician consultations are covered separately from emergency room services and may require additional copayments. The amount you pay is based on the type of service being rendered. Follow-up care services, such as suture removal, fracture care or wound care, received at the emergency room will require an additional emergency room copayment. Follow- up care services can be obtained from your primary care provider or a specialist. See Dental Services in Section 3 for information regarding emergency dental care services.

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