Identified Risks Clause Samples

Identified Risks. Where in Our view the existing condition / circumstances of any of the Goods indicate that damage to the Goods might be unavoidable (despite using due care and skill in dealing with the Goods), then before dealing with the Goods We will notify You and list that item in the move documentation. If You instruct or direct Us to move the Goods notwithstanding this listing/notification, and loss or damage is caused to the Goods, then We, nor any member of the Company Group, will be liable.
View SourceView Similar (4)
Identified Risks. For purposes of clarification, as part of Tenant’s indemnification obligations pursuant to Section 27.2 above, Tenant hereby expressly agrees to Indemnify Landlord from and against any and all Claims arising from or relating to the Identified Risks (or any of them), including costs incurred in connection with any investigation or site conditions or any clean-up, remedial, removal, or restoration work required by any federal, state, or local governmental agency or political subdivision because of Pollutants present in the soil or ground water on or under the Premises, except to the extent generated or Released by a Landlord Party.
View Source

Related to Identified Risks

  • Trunk Group Connections and Ordering 5.2.1 For both One-Way and Two-Way Interconnection Trunks, if Onvoy wishes to use a technically feasible interface other than a DS1 or a DS3 facility at the POI, the Parties shall negotiate reasonable terms and conditions (including, without limitation, rates and implementation timeframes) for such arrangement; and, if the Parties cannot agree to such terms and conditions (including, without limitation, rates and implementation timeframes), either Party may utilize the Agreement’s dispute resolution procedures. 5.2.2 When One-Way or Two-Way Interconnection Trunks are provisioned using a DS3 interface facility, if Onvoy orders the multiplexed DS3 facilities to a Frontier Central Office that is not designated in the NECA 4 Tariff as the appropriate Intermediate Hub location (i.e., the Intermediate Hub location in the appropriate Tandem subtending area based on the LERG), and the provision of such facilities to the subject Central Office is technically feasible, the Parties shall negotiate in good faith reasonable terms and conditions (including, without limitation, rates and implementation timeframes) for such arrangement; and, if the Parties cannot agree to such terms and conditions (including, without limitation, rates and implementation timeframes), either Party may utilize the Agreement’s dispute resolution procedures. 5.2.3 Each Party will identify its Carrier Identification Code, a three or four digit numeric code obtained from Telcordia, to the other Party when ordering a trunk group. 5.2.4 For multi-frequency (MF) signaling each Party will out pulse ten (10) digits to the other Party, unless the Parties mutually agree otherwise. 5.2.5 Each Party will use commercially reasonable efforts to monitor trunk groups under its control and to augment those groups using generally accepted trunk- engineering standards so as to not exceed blocking objectives. Each Party agrees to use modular trunk-engineering techniques for trunks subject to this Attachment.

  • Self-Evaluation Each regular faculty member shall provide a self-evaluation. It shall address, among other items, the faculty member's fulfillment of professional responsibilities as referenced in Section 18.2.3 and an assessment of his or her own performance. The faculty member will share the self-evaluation with the Faculty Evaluation Committee and the first-level manager or designee. The self-evaluation will become part of the evaluation report.

  • Trunk Types 2.2.1 In interconnecting their networks pursuant to this Attachment, the Parties will use, as appropriate, the following separate and distinct trunk groups: 2.2.1.1 Interconnection Trunks for the transmission and routing of Reciprocal Compensation Traffic, translated LEC IntraLATA toll free service access code (e.g., 800/888/877) traffic, and IntraLATA Toll Traffic, between their respective Telephone Exchange Service Customers, Tandem Transit Traffic, and, Measured Internet Traffic, all in accordance with Sections 5 through 8 of this Attachment; 2.2.1.2 Access Toll Connecting Trunks for the transmission and routing of Exchange Access traffic, including translated InterLATA toll free service access code (e.g., 800/888/877) traffic, between Ymax Telephone Exchange Service Customers and purchasers of Switched Exchange Access Service via a Verizon access Tandem in accordance with Sections 9 through 11 of this Attachment; and 2.2.1.3 Miscellaneous Trunk Groups as mutually agreed to by the Parties, including, but not limited to: (a) choke trunks for traffic congestion and testing; and, (b) untranslated IntraLATA/InterLATA toll free service access code (e.g. 800/888/877) traffic. 2.2.2 Other types of trunk groups may be used by the Parties as provided in other Attachments to this Agreement (e.g., 911/E911 Trunks) or in other separate agreements between the Parties (e.g., directory assistance trunks, operator services trunks, BLV/BLVI trunks or trunks for 500/555 traffic). 2.2.3 In accordance with the terms of this Agreement, the Parties will deploy One-Way Interconnection Trunks (trunks with traffic going in one direction, including one-way trunks and uni-directional two-way trunks) and/or Two-Way Interconnection Trunks (trunks with traffic going in both directions). 2.2.4 Ymax shall establish, at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA, separate Interconnection Trunk group(s) between such POI(s) and each Verizon Tandem in a LATA with a subtending End Office(s) to which Ymax originates calls for Verizon to terminate. 2.2.5 In the event the volume of traffic between a Verizon End Office and a technically feasible Point of Interconnection on Verizon’s network in a LATA, which is carried by a Final Tandem Interconnection Trunk group, exceeds (a) the Centium Call Seconds (Hundred Call Seconds) busy hour equivalent of one (1) DS1 at any time; (b) 200,000 minutes of use for a single month; and/or; (c) 600 busy hour Centium Call Seconds (BHCCS) of use for a single month: (i) if One-Way Interconnection Trunks are used, the originating Party shall promptly establish new or augment existing End Office One-Way Interconnection Trunk groups between the Verizon End Office and the technically feasible Point of Interconnection on Verizon’s network; or,

  • Historically Underutilized Businesses (“HUBs”). In accordance with state law, it is TFC’s policy to assist HUBs whenever possible to participate in providing goods and services to the agency. TFC encourages those parties with whom it contracts for the provision of goods and services to adhere to this same philosophy in selecting subcontractors to assist in fulfilling PSP’s obligations with TFC. If PSP subcontracts with others for some or all of the services to be performed under an Assignment to this Agreement, PSP shall comply with all HUB requirements pursuant to Chapter 2161 of the Texas Government Code. At or prior to the execution of an Assignment with a value that is anticipated to meet or exceed One Hundred Thousand and No/100 Dollars ($100,000.00), PSP must provide a completed HUB Subcontracting Plan, which shall be approved by TFC prior to execution of the Assignment. A copy of the HUB Subcontracting Form is attached hereto and incorporated herein for all purposes as Exhibit G. PSP shall provide the HUB Program of TFC with pertinent details of any participation by a HUB in fulfilling the duties and obligations arising under an Assignment, on the HUB Subcontracting Plan Progress Assessment Report (“PAR”). A copy of the PAR Form is attached hereto and incorporated herein for all purposes as Exhibit H.

  • Categories of Data Subjects Any individual accessing and/or using the Services through the Customer's account ("Users"); and any individual: (i) whose email address is included in the Customer's Distribution List; (ii) whose information is stored on or collected via the Services, or (iii) to whom Users send emails or otherwise engage or communicate with via the Services (collectively, "Subscribers").