Disaster Response Activities Sample Clauses

Disaster Response Activities a. Participating Jurisdictions will coordinate their emergency response activities with and through SCEM in order to endeavor to minimize death, injury, and damages to property, the economy, and the environment during natural, technological or human-caused disasters. b. During, or in anticipation of, disasters as defined by RCW 38.52.010(6), affected Participating Jurisdictions will activate their incident management structure and Emergency Operations Plan, and notify SCEM as soon as practicable. c. When activated, Participating Jurisdictions will request County, state and/or federal resources through established emergency management protocols, d. Participating Jurisdictions shall submit incident-related information to the SCECC and the SCECC shall develop and provide comprehensive situation reports to the Participating Jurisdictions, as well as to regional and state partners. e. Participating Jurisdictions will identify appropriate points of contact with whom the SCJIC will communicate to form the information network commonly referred to as the Joint Information System (JIS). f. When requested and practicable, Participating Jurisdictions will deploy liaisons to the Spokane County ECC to enhance communication between the SCECC and the incident site(s). g. Upon determining that a disaster as defined by RCW 38.52.010(6) has happened or is imminent, Participating Jurisdictions will, under the provisions of
AutoNDA by SimpleDocs

Related to Disaster Response Activities

  • Disaster Recovery and Business Continuity The Parties shall comply with the provisions of Schedule 5 (Disaster Recovery and Business Continuity).

  • Workplace Violence Prevention and Crisis Response (applicable to any Party and any subcontractors and sub-grantees whose employees or other service providers deliver social or mental health services directly to individual recipients of such services): Party shall establish a written workplace violence prevention and crisis response policy meeting the requirements of Act 109 (2016), 33 VSA §8201(b), for the benefit of employees delivering direct social or mental health services. Party shall, in preparing its policy, consult with the guidelines promulgated by the U.S. Occupational Safety and Health Administration for Preventing Workplace Violence for Healthcare and Social Services Workers, as those guidelines may from time to time be amended. Party, through its violence protection and crisis response committee, shall evaluate the efficacy of its policy, and update the policy as appropriate, at least annually. The policy and any written evaluations thereof shall be provided to employees delivering direct social or mental health services. Party will ensure that any subcontractor and sub-grantee who hires employees (or contracts with service providers) who deliver social or mental health services directly to individual recipients of such services, complies with all requirements of this Section.

  • BUSINESS CONTINUITY/DISASTER RECOVERY In the event of equipment failure, work stoppage, governmental action, communication disruption or other impossibility of performance beyond State Street’s control, State Street shall take reasonable steps to minimize service interruptions. Specifically, State Street shall implement reasonable procedures to prevent the loss of data and to recover from service interruptions caused by equipment failure or other circumstances with resumption of all substantial elements of services in a timeframe sufficient to meet business requirements. State Street shall enter into and shall maintain in effect at all times during the term of this Agreement with appropriate parties one or more agreements making reasonable provision for (i) periodic back-up of the computer files and data with respect to the Trusts; and (ii) emergency use of electronic data processing equipment to provide services under this Agreement. State Street shall test the ability to recover to alternate data processing equipment in accordance with State Street program standards, and provide a high level summary of business continuity test results to the Trusts upon request. State Street will remedy any material deficiencies in accordance with State Street program standards. Upon reasonable advance notice, and at no cost to State Street, the Trusts retain the right to review State Street’s business continuity, crisis management, disaster recovery, and third-party vendor management processes and programs (including discussions with the relevant subject matter experts and an on-site review of the production facilities used) related to delivery of the service no more frequently than an annual basis. Upon reasonable request, the State Street also shall discuss with senior management of the Trusts any business continuity/disaster recovery plan of the State Street and/or provide a high-level presentation summarizing such plan.”

  • Disaster Services In the event of a local, state, or federal emergency, including natural, man-made, criminal, terrorist, and/or bioterrorism events, declared as a state disaster by the Governor, or a federal disaster declared by the appropriate federal official, Grantee may be called upon to assist the System Agency in providing the following services: i. Community evacuation; ii. Health and medical assistance; iii. Assessment of health and medical needs; iv. Health surveillance; v. Medical care personnel; vi. Health and medical equipment and supplies; vii. Patient evacuation; viii. In-hospital care and hospital facility status; ix. Food, drug and medical device safety; x. Worker health and safety; xi. Mental health and substance abuse; xii. Public health information; xiii. Vector control and veterinary services; and xiv. Victim identification and mortuary services.

  • Incident Response Operator shall have a written incident response plan that reflects best practices and is consistent with industry standards and federal and state law for responding to a data breach, breach of security, privacy incident or unauthorized acquisition or use of any portion of Data, including PII, and agrees to provide LEA, upon request, an executive summary of the written incident response plan.

  • Requester and Approved User Responsibilities The Requester agrees through the submission of the DAR that the PI named has reviewed and understands the principles for responsible research use and data management of the genomic datasets as defined in the NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy. The Requester and Approved Users further acknowledge that they are responsible for ensuring that all uses of the data are consistent with national, tribal, and state laws and regulations, as appropriate, as well as relevant institutional policies and procedures for managing sensitive genomic and phenotypic data. The Requester certifies that the PI is in good standing (i.e., no known sanctions) with the institution, relevant funding agencies, and regulatory agencies and is eligible to conduct independent research (i.e., is not a postdoctoral fellow, student, or trainee). The Requester and any Approved Users may use the dataset(s) only in accordance with the parameters described on the study page and in the 1 If contractor services are to be utilized, PI requesting the data must provide a brief description of the services that the contractor will perform for the PI (e.g., data cleaning services) in the research use statement of the DAR. Additionally, the Key Personnel section of the DAR must include the name of the contractor’s employee(s) who will conduct the work. These requirements apply whether the contractor carries out the work at the PI’s facility or at the contractor’s facility. In addition, the PI is expected to include in any contract agreement requirements to ensure that any of the contractor’s employees who have access to the data adhere to the NIH GDS Policy, this Data Use Certification Agreement, and the NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy. Note that any scientific collaborators, including contractors, who are not at the Requester must submit their own DAR. Addendum to this Agreement for the appropriate research use, as well as any limitations on such use, of the dataset(s), as described in the DAR, and as required by law. Through the submission of this DAR, the Requester and Approved Users acknowledge receiving and reviewing a copy of the Addendum which includes Data Use Limitation(s) for each dataset requested. The Requester and Approved Users agree to comply with the terms listed in the Addendum. Through submission of the DAR, the PI and Requester agree to submit a Project Renewal or Project Close-out prior to the expiration date of the one (1) year data access period. The PI also agrees to submit an annual Progress Update prior to the one (1) year anniversary2 of the project, as described under Research Use Reporting (Term 10) below. By approving and submitting the attached DAR, the Institutional Signing Official provides assurance that relevant institutional policies and applicable local, state, tribal, and federal laws and regulations, as applicable, have been followed, including IRB approval, if required. Approved Users may be required to have IRB approval if they have access to personal identifying information for research participants in the original study at their institution, or through their collaborators. The Institutional Signing Official also assures, through the approval of the DAR, that other institutional departments with relevant authorities (e.g., those overseeing human subjects research, information technology, technology transfer) have reviewed the relevant sections of the NIH GDS Policy and the associated procedures and are in agreement with the principles defined. The Requester acknowledges that controlled-access datasets subject to the NIH GDS Policy may be updated to exclude or include additional information. Unless otherwise indicated, all statements herein are presumed to be true and applicable to the access and use of all versions of these datasets.

  • User Responsibilities i. Users are required to follow good security practices in the selection and use of passwords; ii. Users shall ensure that unattended equipment is protected; and iii. Users shall adopt a clear desk policy for papers and removable storage media and a clear screen policy for information processing facilities.

  • Primary Frequency Response Developer shall ensure the primary frequency response capability of its Large Generating Facility by installing, maintaining, and operating a functioning governor or equivalent controls. The term “functioning governor or equivalent controls” as used herein shall mean the required hardware and/or software that provides frequency responsive real power control with the ability to sense changes in system frequency and autonomously adjust the Large Generating Facility’s real power output in accordance with the droop and deadband parameters and in the direction needed to correct frequency deviations. Developer is required to install a governor or equivalent controls with the capability of operating: (1) with a maximum 5 percent droop ± 0.036 Hz deadband; or (2) in accordance with the relevant droop, deadband, and timely and sustained response settings from an approved Applicable Reliability Standard providing for equivalent or more stringent parameters. The droop characteristic shall be: (1) based on the nameplate capacity of the Large Generating Facility, and shall be linear in the range of frequencies between 59 and 61 Hz that are outside of the deadband parameter; or (2) based on an approved Applicable Reliability Standard providing for an equivalent or more stringent parameter. The deadband parameter shall be: the range of frequencies above and below nominal (60 Hz) in which the governor or equivalent controls is not expected to adjust the Large Generating Facility’s real power output in response to frequency deviations. The deadband shall be implemented: (1) without a step to the droop curve, that is, once the frequency deviation exceeds the deadband parameter, the expected change in the Large Generating Facility’s real power output in response to frequency deviations shall start from zero and then increase (for under-frequency deviations) or decrease (for over-frequency deviations) linearly in proportion to the magnitude of the frequency deviation; or (2) in accordance with an approved Applicable Reliability Standard providing for an equivalent or more stringent parameter. Developer shall notify NYISO that the primary frequency response capability of the Large Generating Facility has been tested and confirmed during commissioning. Once Developer has synchronized the Large Generating Facility with the New York State Transmission System, Developer shall operate the Large Generating Facility consistent with the provisions specified in Articles 9.5.5.1 and 9.5.5.2 of this Agreement. The primary frequency response requirements contained herein shall apply to both synchronous and non-synchronous Large Generating Facilities.

  • Customer Responsibilities Notwithstanding the above, Customer agrees that except as provided by this DPA, Customer is responsible for its secure use of the Services, including securing its account authentication credentials, protecting the security of Customer Data when in transit to and from the Services and taking any appropriate steps to securely encrypt or backup any Customer Data uploaded to the Services.

  • Disaster Recovery Plan Contractor agrees that upon request of System Agency, Contractor shall provide copies of its most recent business continuity and disaster recovery plans.

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