BNYM Failure to Receive Data Sample Clauses

BNYM Failure to Receive Data. BNYM shall not be liable for data or information which the Company, a Permitted User or an agent of either transmits or attempts to transmit to BNYM in connection with its use of a Component System and which is not received by BNYM or for any failure of a Component System to perform a function in connection with any such data or information. BNYM shall not be obligated to ascertain the accuracy, actual receipt by it or successful transmission to it of any data or information in connection with the Company’s or a Permitted User’s use of a Component System or to confirm the performance of any function by a Component System based on the transmission of instructions, data or information to BNYM in connection with such use by the Company or a Permitted User. Sole responsibility for the foregoing shall rest with the party initiating the transmission.
Sample 1Sample 2Sample 3See All (88)
AutoNDA by SimpleDocs
BNYM Failure to Receive Data. BNYM shall not be liable for data or information which the Company, a Permitted User or an agent of either transmits or attempts to transmit to BNYM in connection with its use of a Component System and which is not received by BNYM or for any failure of a Component System to perform a function in connection with any such data or information, except to the extent that such failure to receive data is the result of BNYM’s failure to meet its Standard of Care as specified in the Main Agreement. BNYM shall not be obligated to ascertain the accuracy, actual receipt by it or successful transmission to it of any data or information in connection with the Company’s or a Permitted User’s use of a Component System or to confirm the performance of any function by a Component System based on the transmission of instructions, data or information to BNYM in connection with such use by the Company or a Permitted User. Sole responsibility for the foregoing shall rest with the party initiating the transmission.
Sample 1Sample 2Sample 3See All (6)
BNYM Failure to Receive Data. BNYM shall not be liable for data or information which the Company, a Permitted User or an agent of either transmits or attempts to transmit to BNYM in connection with its use of a Component System and which is not received by BNYM or for any failure of a Component System to perform a function in connection with any such data or information. BNYM shall not be obligated to ascertain the accuracy, actual receipt by it or successful transmission to it of any data or information in connection with the Company's or a Permitted User's use of a Component System or to confirm the performance of any function by a Component System based on the transmission of instructions, data or information to BNYM in connection with such use by the Company or a Permitted User. Sole responsibility for the foregoing shall rest with the party initiating the transmission. For further clarification, this provision does not apply to Section 11(h) of the Main Agreement, nor negate BNYM’s negation of liability for Errant Securities under Section 11(h).
Sample 1Sample 2
BNYM Failure to Receive Data. BNYM shall not be liable for data or information which the Company, a Permitted User or an agent of either transmits or attempts to transmit to BNYM in connection with its use of a Component System and which is not received by BNYM or for any failure of a Component System to perform a function in connection with any such data or information. BNYM shall not be obligated to ascertain the accuracy, actual receipt by it or successful transmission to it of any data or information in connection with the Company’s or a Permitted User’s use of a Component System or to confirm the performance of any function by a Component System based on the transmission of instructions, data or information to BNYM in connection with such use by the Company or a Permitted User. Sole responsibility for the foregoing shall rest with the party initiating the transmission. For clarification: BNYM is responsible for performances of services in accordance with the Agreement and the Documentation, as applicable, with respect to data and information it does receive and the foregoing does not restrict or reduce BNYM’s liability under Section 11(a) for Liable Conduct in the circumstances addressed by this Section 3.4 of Schedule C.
Sample 1Sample 2
BNYM Failure to Receive Data. BNYM shall not be liable for data or information which the Company, a Permitted User or an agent of either transmits or attempts to transmit to BNYM in connection with its use of a Component System and which is not received by BNYM or for any failure of a Component System to perform a function in connection with any such data or information. BNYM shall not be obligated to ascertain the accuracy, actual receipt by it or successful transmission to it of any data or information in connection with the Company's or a Permitted User's use of a Component System or to confirm the performance of any function by a Component System based on the transmission of instructions, data or information to BNYM in connection with such use by the Company or a Permitted User. Sole responsibility for the foregoing shall rest with the party initiating the transmission. For clarification: (i) Consistent with Section 0.2 (Purpose), this Section 3.5 does not apply to BNYM's receipt of data or information in connection with any service BNYM is obligated to perform pursuant to the Main Agreement; the provisions of the Main Agreement alone apply to such services, and (ii) without limiting the generality of clause (i), with respect to files that are customarily received in the ordinary course of business from third party sources identified in advance to BNYM by the Company and acknowledged by BNYM as to the content and timing of the files to be received from such third party sources, and upon such time as procedures are put in place by BNYM to receive such files in the ordinary course of business, BNYM will employ commercially reasonable measures to detect when such files are not received at the customary times, and upon detecting a file has not been received will employ commercially reasonable measures to obtain such file.
Sample 1
BNYM Failure to Receive Data. BNYM shall not be liable for data or information which the Company, a Permitted User or an agent of either transmits or attempts to transmit to BNYM in connection with its use of a Component System and which is not received by BNYM or for any failure of a Component System to perform a function in connection with any such data or information that is not received. BNYM shall not be obligated to ascertain the accuracy, actual receipt by it or successful transmission to it of any data or information in connection with the Company’s or a Permitted User’s use of a Component System or to confirm the performance of any function by a Component System based on the transmission of instructions, data or information to BNYM in connection with such use by the Company or a Permitted User. Sole responsibility for the foregoing shall rest with the party initiating the transmission. For clarification: this Section 3.4 does not apply to BNYM’s obligations under Section 3 of the Main Agreement and in particular does not modify BNYM’s obligation under the proviso to Section 11(h).
Sample 1

Related to BNYM Failure to Receive Data

  • Failure to Make Payment In the event a participating Authorized User fails to make payment to the Contractor for Products delivered, accepted and properly invoiced, within thirty calendar days of such delivery and acceptance, the Contractor may, upon five business days advance written notice to both the Commissioner and the Authorized User’s purchasing official, suspend additional shipments of Product or provision of services to such entity until such time as reasonable arrangements have been made and assurances given by such entity for current and future Contract payments.

  • Failure to Respond If you fail to respond by the date given above, your application will be refused under Section 3A(4)(a) of the Registered Designs Act 1949.

  • Failure to Make Payments If the Company fails to make any payment of interest on this Subordinated Note when such interest becomes due and payable and such default continues for a period of 30 days, or if the Company fails to make any payment of the principal of this Subordinated Note when such principal becomes due and payable, the Company will, upon demand of the Trustee, pay to the Trustee, for the benefit of the Holder, the whole amount then due and payable with respect to this Subordinated Note, with interest upon the overdue principal, any premium and, to the extent permitted by applicable law, upon any overdue installments of interest at the rate or respective rates, as the case may be, provided for or with respect to this Subordinated Note or, if no such rate or rates are so provided, at the rate or respective rates, as the case may be, of interest borne by this Subordinated Note. Upon an Event of Default, the Company may not declare or pay any dividends or distributions on, or redeem, purchase, acquire, or make a liquidation payment with respect to, any of the Company’s capital stock, make any payment of principal or interest or premium, if any, on or repay, repurchase or redeem any debt securities of the Company that rank equal with or junior to this Subordinated Note, or make any payments under any guarantee that ranks equal with or junior to this Subordinated Note, other than: (i) any dividends or distributions in shares of, or options, warrants or rights to subscribe for or purchase shares of, any class of Company’s common stock; (ii) any declaration of a dividend in connection with the implementation of a shareholders’ rights plan, or the issuance of stock under any such plan in the future, or the redemption or repurchase of any such rights pursuant thereto; (iii) as a result of a reclassification of Company’s capital stock or the exchange or conversion of one class or series of Company’s capital stock for another class or series of Company’s capital stock; (iv) the purchase of fractional interests in shares of Company’s capital stock in accordance with the conversion or exchange provisions of such capital stock or the security being converted or exchanged; or (v) purchases of any class of Company’s common stock related to the issuance of common stock or rights under any of benefit plans for Company’s directors, officers or employees or any of Company’s dividend reinvestment plans.

  • Settlement without Consent if Failure to Reimburse If at any time an indemnified party shall have requested an indemnifying party to reimburse the indemnified party for fees and expenses of counsel, such indemnifying party agrees that it shall be liable for any settlement of the nature contemplated by Section 6(a)(ii) effected without its written consent if (i) such settlement is entered into more than 45 days after receipt by such indemnifying party of the aforesaid request, (ii) such indemnifying party shall have received notice of the terms of such settlement at least 30 days prior to such settlement being entered into and (iii) such indemnifying party shall not have reimbursed such indemnified party in accordance with such request prior to the date of such settlement.

  • Failure to Supply If IPC is unable (or anticipates an inability) to manufacture or deliver all or a portion of a Product to Tris as required by a confirmed or accepted Purchase Order pursuant to Section 3.3 of this Agreement, IPC shall promptly notify Tris in writing of the period for which such inability (or anticipated inability) to so manufacture or deliver is expected (an “Anticipated Inability to Deliver”). For avoidance of doubt, so long as IPC uses Commercially Reasonable Efforts and the anticipated inability is a force majeure event, IPC shall not be in breach of the Purchase Order(s) affected nor this Agreement, however, regardless of whether or not IPC has breached a Purchase Order or this Agreement it shall still be liable for Cover and the other obligations set forth in this Section 3.10. In the event IPC is unable to meet Tris’s Purchase Orders or IPC issues a notice of an Anticipated Inability to Deliver, IPC’s obligation to supply shall continue but Tris’ obligation to purchase the Product that IPC is unable to timely supply in accordance with Section 3.3 above shall be suspended and Tris, without relieving IPC of its obligations under Section 3.3, may mitigate its damages by purchasing from another Person the quantity of substitute product that it requires beyond what IPC is able to deliver. Tris shall use Commercially Reasonable Efforts to obtain such substitute product at a reasonable price and communicate same to IPC in writing. Tris shall be entitled to deduct the difference in cost paid by Tris for such substitute product over the cost of the Product (“Cover”), if any, from any amounts otherwise payable to IPC hereunder, and, to the extent not so offset, IPC shall reimburse Tris for such Cover , within thirty (30) days of receipt of invoice from Tris. IPC will not be entitled to any share of positive Net Profits for sale of substitute product not sourced by Tris from IPC hereunder (provided IPC shall continue to fund its share of negative Net Profits), except to the extent IPC has fully reimbursed Tris for the Cover expense with respect to such product. If at any time thereafter during the Term, IPC is able to timely deliver Product in satisfaction of Tris’ Purchase Orders, IPC shall so notify Tris in writing and, subject to Tris’ contractual commitments to third parties, Tris shall undertake commercially reasonable efforts to limit such contractual commitment in order not to exceed IPC’s volume and period it is unable to supply, Tris will resume purchasing the Product from IPC. If IPC’s inability to timely deliver to Tris the quantity of the Product described in this Section 3.3 continues for a period beyond three (3) months, Tris may terminate this Agreement upon thirty (30) days’ notice in writing to IPC. IPC shall reimburse Tris for any failure to supply and late supply penalties and/or damages charged to Tris for late supply or non-supply caused by IPC’s failure to timely supply Product pursuant to Purchase Orders delivered to IPC in accordance with this Agreement. For clarity and audit purposes, such failure to supply penalties shall be supported by appropriate invoices detailing the failure to supply penalties issued by the affected customers and wholesallers of Tris. IPC shall reimburse Tris for such penalties and damages, within ten (10) days of receipt of invoice for same from Tris, provided that if such invoice is not timely paid, Tris may at its option offset such amounts owed against other amounts payable by Tris to IPC.

  • Failure to Elect; Events of Default If the Borrower fails to deliver a timely and complete Interest Election Request with respect to a Eurocurrency Borrowing prior to the end of the Interest Period therefor, then, unless such Borrowing is repaid as provided herein, (i) if such Borrowing is denominated in Dollars, at the end of such Interest Period such Borrowing shall be converted to a Syndicated Eurocurrency Borrowing of the same Class having an Interest Period of one month, and (ii) if such Borrowing is denominated in a Foreign Currency, the Borrower shall be deemed to have selected an Interest Period of one month’s duration. Notwithstanding any contrary provision hereof, if an Event of Default has occurred and is continuing and the Administrative Agent, at the request of the Required Lenders, so notifies the Borrower, (i) any Eurocurrency Borrowing denominated in Dollars shall, at the end of the applicable Interest Period for such Eurocurrency Borrowing, be automatically converted to an ABR Borrowing and (ii) any Eurocurrency Borrowing denominated in a Foreign Currency shall not have an Interest Period of more than one month’s duration.

  • Failure to Deliver Applicable

  • Failure to Go Effective If the Registration Statement required by Section 2.01(a) is not declared effective within 90 days after the Closing Date, then each Holder shall be entitled to a payment (with respect to the Purchased Units of each such Holder), as liquidated damages and not as a penalty, of 0.25% of the Liquidated Damages Multiplier per 30-day period, that shall accrue daily, for the first 60 days following the 90th day after the Closing Date, increasing by an additional 0.25% of the Liquidated Damages Multiplier per 30-day period following the 60th date after such 90th day, that shall accrue daily, for each subsequent 30 days, up to a maximum of 1.00% of the Liquidated Damages Multiplier per 30-day period (the “Liquidated Damages”); provided, however, that the aggregate amount of Liquidated Damages payable by the Partnership per Purchased Unit may not exceed 5.0% of the Common Unit Price. The Liquidated Damages payable pursuant to the immediately preceding sentence shall be payable within ten (10) Business Days after the end of each such 30-day period. Any Liquidated Damages shall be paid to each Holder in immediately available funds; provided, however, if the Partnership certifies that it is unable to pay Liquidated Damages in cash because such payment would result in a breach under a credit facility or other debt instrument, then the Partnership may pay the Liquidated Damages in kind in the form of the issuance of additional Common Units. Upon any issuance of Common Units as Liquidated Damages, the Partnership shall promptly (i) prepare and file an amendment to the Registration Statement prior to its effectiveness adding such Common Units to such Registration Statement as additional Registrable Securities and (ii) prepare and file a supplemental listing application with the NYSE to list such additional Common Units. The determination of the number of Common Units to be issued as Liquidated Damages shall be equal to the amount of Liquidated Damages divided by the volume-weighted average closing price of the Common Units on the NYSE for the ten (10) trading days immediately preceding the date on which the Liquidated Damages payment is due, less a discount to such average closing price of 2.00%. The payment of Liquidated Damages to a Holder shall cease at the earlier of (i) the Registration Statement becoming effective or (ii) the Purchased Units of such Holder becoming eligible for resale without restriction under any section of Rule 144 (or any similar provision then in effect) under the Securities Act, assuming that each Holder is not an Affiliate of the Partnership, and any payment of Liquidated Damages shall be prorated for any period of less than 30 days in which the payment of Liquidated Damages ceases. If the Partnership is unable to cause a Registration Statement to go effective within 180 days after the Closing Date as a result of an acquisition, merger, reorganization, disposition or other similar transaction, then the Partnership may request a waiver of the Liquidated Damages, and each Holder may individually grant or withhold its consent to such request in its discretion. The foregoing Liquidated Damages shall be the sole and exclusive remedy of the Holders for any failure of the Registration Statement to be declared effective.

  • Failure to Fulfill Conditions In the event that either of the parties hereto determines that a condition to its respective obligations to consummate the transactions contemplated hereby cannot be fulfilled on or prior to the termination of this Agreement, it will promptly notify the other party.

Time is Money Join Law Insider Premium to draft better contracts faster.