Loss Occurrence   A Sample Clauses

The "Loss Occurrence" clause defines what constitutes a single event or series of events that trigger coverage under an insurance policy. In practice, this clause specifies the parameters for grouping related losses—such as those arising from a single accident, disaster, or continuous exposure to the same harmful conditions—into one occurrence for the purposes of claim limits and deductibles. By clearly delineating what counts as a single occurrence, the clause helps prevent disputes over how many claims can be made for related losses and ensures both insurer and insured understand the scope of coverage and financial responsibility.
Loss Occurrence   A. The term "loss occurrence" shall mean the sum of all individual losses directly occasioned by any one disaster, accident or loss or series of disasters, accidents or losses arising out of one event which occurs within the area of one state of the United States or province of Canada and states or provinces contiguous thereto and to one another. However, the duration and extent of any one "loss occurrence" shall be limited to all individual losses sustained by the Company occurring during any period of 168 consecutive hours arising out of and directly occasioned by the same event, except that the term "loss occurrence" shall be further defined as follows:
View SourceView Similar (30)
Loss Occurrence   A. The term "loss occurrence" shall mean the sum of all individual losses directly occasioned by any one disaster, accident or loss or series of disasters, accidents or losses arising out of one event which occurs within the area of one state of the United States or province of
View SourceView Similar (6)
Loss Occurrence   A. Loss occurrence" as used in this Contract shall mean the sum of individual insured losses incurred under Policies resulting from the same covered event. B. "Covered event" as used in this Contract shall mean any one storm declared to be a hurricane by the National Hurricane Center of the National Weather Service or any other division of the National Weather Service, operated by the National Oceanographic and Atmospheric Administration of the United States Government (NHC) which causes insured losses in Florida. A covered event begins when a hurricane causes damage in Florida while it is a hurricane and continues throughout any subsequent downgrades in storm status by the National Hurricane Center regardless of whether the hurricane makes landfall. Any storm, including a tropical storm, which does not become a hurricane is not a covered event. Article 9 -
View SourceView Similar (2)
Loss Occurrence   A. The term "loss occurrence" shall mean severe convective storms and any ensuing losses during any period of 144 consecutive hours arising out of, caused by, occurring during, occasioned by or resulting from the same event. However, the event need not be limited to one state or province or states or provinces contiguous thereto.
View Source
Loss Occurrence   A. The term "loss occurrence" shall mean all individual losses sustained by the Company occurring during any period (a) from and after 12:00 a.m. Eastern Standard Time on the date a watch, warning, advisory, or other bulletin (whether for wind, flood or otherwise) for 20\F7V1012 Page 8 such named storm is first issued by the National Hurricane Center ("NHC") or its successor or any other division of the National Weather Service ("NWS"), (b) continuing for a time period thereafter during which such named storm continues, regardless of its category rating or lack thereof and regardless of whether the watch, warning, or advisory or other bulletin remains in effect for such named storm and (c) ending 96 hours following the issuance of the last watch, warning or advisory or other bulletin for such named storm or related to such named storm by the NHC or its successor or any other division of the NWS. "Named storm" shall mean any storm or storm system that has been declared by the NHC or its successor or any other division of the NWS to be a named storm at any time, which may include, by way of example and not limitation, hurricane, wind, gusts, typhoon, tropical storm, hail, rain, tornados, cyclones, ensuing flood, storm surge, water damage, fire following, sprinkler leakage, riots, vandalism, and collapse, and all losses and perils (including, by way of example and not limitation, those mentioned previously in this sentence) in each case arising out of, caused by, occurring during, occasioned by or resulting from such storm or storm system, including by way of example and not limitation the merging of one or more separate storm(s) or storm system(s) into a combined storm surge event. However, the named storm need not be limited to one state or province or states or provinces contiguous thereto.
View Source

Related to Loss Occurrence   A

  • Name Collision Occurrence Assessment 6.2.1 Registry Operator shall not activate any names in the DNS zone for the Registry TLD except in compliance with a Name Collision Occurrence Assessment provided by ICANN regarding the Registry TLD. Registry Operator will either (A) implement the mitigation measures described in its Name Collision Occurrence Assessment before activating any second-­‐level domain name, or (B) block those second-­‐level domain names for which the mitigation measures as described in the Name Collision Occurrence Assessment have not been implemented and proceed with activating names that are not listed in the Assessment. 6.2.2 Notwithstanding subsection 6.2.1, Registry Operator may proceed with activation of names in the DNS zone without implementation of the measures set forth in Section 6.2.1 only if (A) ICANN determines that the Registry TLD is eligible for this alternative path to activation of names; and (B) Registry Operator blocks all second-­‐level domain names identified by ICANN and set forth at <▇▇▇▇://▇▇▇▇▇▇▇▇.▇▇▇▇▇.▇▇▇/en/announcements-­‐and-­‐ media/announcement-­‐2-­‐17nov13-­‐en> as such list may be modified by ICANN from time to time. Registry Operator may activate names pursuant to this subsection and later activate names pursuant to subsection 6.2.1. 6.2.3 The sets of names subject to mitigation or blocking pursuant to Sections 6.2.1 and 6.2.2 will be based on ICANN analysis of DNS information including "Day in the Life of the Internet" data maintained by the DNS Operations, Analysis, and Research Center (DNS-­‐OARC) <▇▇▇▇▇://▇▇▇.▇▇▇-­‐▇▇▇▇.▇▇▇/▇▇▇▇/▇▇▇▇/▇▇▇▇>. 6.2.4 Registry Operator may participate in the development by the ICANN community of a process for determining whether and how these blocked names may be released. 6.2.5 If ICANN determines that the TLD is ineligible for the alternative path to activation of names, ICANN may elect not to delegate the TLD pending completion of the final Name Collision Occurrence Assessment for the TLD, and Registry Operator’s completion of all required mitigation measures. Registry Operator understands that the mitigation measures required by ICANN as a condition to activation of names in the DNS zone for the TLD may include, without limitation, mitigation measures such as those described in Section 3.2 of the New gTLD Name Collision Occurrence Management Plan approved by the ICANN Board New gTLD Program Committee (NGPC) on 7 October 2013 as found at <▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/en/groups/board/documents/resolutions-­‐ new-­‐gtld-­‐annex-­‐1-­‐07oct13-­‐en.pdf>.

  • Commercial General Liability – Occurrence Form The policy shall include bodily injury, property damage, personal and advertising injury and broad form contractual liability coverage. • General Aggregate $2,000,000 • Products – Completed Operations Aggregate $1,000,000 Products and completed operations coverage shall be maintained for three (3) years after completion of design • Personal and Advertising Injury $1,000,000 • Blanket Contractual Liability – Written and Oral $1,000,000 • Damage to Rented Premises $50,000 • Each Occurrence $1,000,000 $0 to $5,000,000 $1,000,000 Each Occurrence; $2,000,000 Aggregate $5,000,001 to $15,000,000 $5,000,000 Each Occurrence; $5,000,000 Aggregate $15,000,001 to $50,000,000 $5,000,000 Each Occurrence; $10,000,000 Aggregate $50,000,001 & up $25,000,000 Each Occurrence; $25,000,000 Aggregate a. The Consultant shall be responsible for monitoring the Contract value as it increases and the Consultant shall be responsible for purchasing additional insurance to be in compliance with this Contract should the increase in Contract value require a higher limit of insurance. The Consultant shall provide a new certificate of insurance that reflects the increase in limits as required in 4.20(E) below. b. The policy shall be endorsed to include the following additional insured language: “The State of Arizona, its departments, agencies, boards, commissions, universities and its officers, officials, agents, and employees shall be named as additional insureds with respect to liability arising out of the activities performed by or on behalf of the Consultant.” Such additional insured shall be covered to the full limits of liability purchased by the Consultant, even if those limits of liability are in excess of those required by this Contract. c. The policy shall contain a waiver of subrogation endorsement in favor of the State of Arizona, its departments, agencies, boards, commissions, universities and its officers, officials, agents, and employees for losses arising from work performed by or on behalf of the Consultant.

  • Name Collision Occurrence Management 6.1. No-­‐Activation Period. Registry Operator shall not activate any names in the DNS zone for the Registry TLD (except for "NIC") until at least 120 calendar days after the effective date of this agreement. Registry Operator may allocate names (subject to subsection 6.2 below) during this period only if Registry Operator causes registrants to be clearly informed of the inability to activate names until the No-­‐Activation Period ends.

  • Loss of Shared-Loss Coverage on Shared-Loss Loans The Receiver shall be relieved of its obligations with respect to a Shared-Loss Loan upon payment of a Foreclosure Loss amount, or a Short Sale Loss amount with respect to such Single Family Shared-Loss Loan, or upon the sale without FDIC consent of a Single Family Shared-Loss Loan by Assuming Institution to a person or entity that is not an Affiliate. The Assuming Institution shall provide the Receiver with timely notice of any such sale. Failure to administer any Shared-Loss Loan or Loans in accordance with Article III shall at the discretion of the Receiver constitute grounds for the loss of shared loss coverage with respect to such Shared-Loss Loan or Loans. Notwithstanding the foregoing, a sale of the Single Family Shared-Loss Loan, for purposes of this Section 2.7, shall not be deemed to have occurred as the result of (i) any change in the ownership or control of Assuming Institution or the transfer of any or all of the Single Family Shared-Loss Loan(s) to any Affiliate of Assuming Institution, (ii) a merger by Assuming Institution with or into any other entity, or (iii) a sale by Assuming Institution of all or substantially all of its assets.

  • Umbrella/Excess Liability The A/E may employ an umbrella/excess liability policy to achieve the above-required minimum coverage.