Operational Error Sample Clauses

Operational Error. Buyer may never receive Tokens and may lose the entire amount Buyer paid to Company for such Tokens as a result of interruptions and operational errors in the process of purchasing or receiving the Tokens.
AutoNDA by SimpleDocs
Operational Error. Notwithstanding any other provision contained herein, no Event of Default under subparagraphs (i), (ii), (iii), (iv) or (ix) of paragraph 11 of the Agreement shall have occurred if (i) the relevant failure to pay or transfer is caused solely by an error or omission of an operational nature or by the failure of the defaulting party or a custodian of the defaulting party to make any payment or delivery to the nondefaulting party after the defaulting party has issued instructions; (ii) assets were available to such party to make the relevant payment or transfer when due; and (iii) the defaulting party has upon the non-defaulting party’s request, provided to the nondefaulting party, written verification of clauses (i) and (ii) above that is reasonably satisfactory to the nondefaulting party and (iv) such payment or transfer is made by the close of business on the day after notice of the relevant failure to pay or transfer is given to the defaulting party.
Operational Error. DEVIATION INVESTIGATION,REPORTING AND REVIEW BOARD
Operational Error. In the event of error made by Launchpad systems and/or staff, Launchpad will do its best diligence to provide adequate accommodation or compensation. Launchpad cannot assume liability for lost wages or revenue due to operational errors outside of our control.
Operational Error. Notwithstanding any other provision contained herein, no Event of Default under subparagraphs (i), (ii), (iii), (iv) or (ix) of paragraph 11 of the Agreement shall have occurred if (i) the relevant failure to pay or transfer is caused solely by an error or omission of an operational nature or by the failure of the defaulting party or a custodian of the defaulting party to make any payment or delivery to the nondefaulting party after the defaulting party has issued instructions; (ii) assets were available to such party to make the relevant payment or transfer when due; and (iii) the defaulting party has upon the non-defaulting party’s request, provided to the nondefaulting party, written verification of clauses (i) and (ii) above that is reasonably satisfactory to the nondefaulting party and (iv) such payment or transfer is made by (x), if the relevant failure to pay or transfer is caused by the defaulting party, the close of business (New York time) on the first Business Day after notice of the relevant failure to pay or transfer is given to the defaulting party or (y) if the relevant failure to pay or transfer is caused by a custodian of the defaulting party, the close of business (New York time) on the third Business Day after notice of the relevant failure to pay or transfer is given to the defaulting party.
Operational Error. Purchaser may never receive Coins and may lose the entire amount Purchaser paid to Company for such Coins as a result of interruptions and operational errors in the process of purchasing or receiving the Coins.
Operational Error. Purchaser may lose the entire amount Purchaser paid to Company for such USG Tokens as a result of interruptions and operational errors in the process of purchasing or receiving the USG Tokens.
AutoNDA by SimpleDocs

Related to Operational Error

  • Operational Control Directing the operation of the Transmission Facilities Under ISO Operational Control to maintain these facilities in a reliable state, as defined by the Reliability Rules. The ISO shall approve operational decisions concerning these facilities, made by each Transmission Owner before the Transmission Owner implements those decisions. In accordance with ISO Procedures, the ISO shall direct each Transmission Owner to take certain actions to restore the system to the Normal State. Operational Control includes security monitoring, adjustment of generation and transmission resources, coordination and approval of changes in transmission status for maintenance, determination of changes in transmission status for reliability, coordination with other Control Areas, voltage reductions and Load Shedding, except that each Transmission Owner continues to physically operate and maintain its facilities.

  • Emergency Mode Operation Plan Contractor must establish a documented plan to enable continuation of critical business processes and protection of the security of electronic DHCS PHI or PI in the event of an emergency. Emergency means any circumstance or situation that causes normal computer operations to become unavailable for use in performing the work required under this Agreement for more than 24 hours.

  • Operational All expenses for running and operating all machinery, equipments and installations comprised in the Common Areas, including elevators, diesel generator set, changeover switch, pump and other common installations including their license fees, taxes and other levies (if any) and expenses ancillary or incidental thereto and the lights of the Common Areas and the road network.

  • Accounting System Requirement The Contractor shall maintain an adequate system of accounting and internal controls that meets Generally Accepted Accounting Principles or “GAAP.”

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Maintenance Manual No later than 60 (sixty) days prior to the Project Completion Date, the Contractor shall, in consultation with the Authority’s Engineer, evolve a maintenance manual (the “Maintenance Manual”) for the regular and preventive maintenance of the Project Highway in conformity with the Specifications and Standards, safety requirements and Good Industry Practice, and shall provide 5 (five) copies thereof to the Authority’s Engineer. The Authority’s Engineer shall review the Maintenance Manual within 15 (fifteen) days of its receipt and communicate its comments to the Contractor for necessary modifications, if any.

  • Service Level Standards In addition to all other requirements in this Agreement, and in accordance with the Best Claims Practices & Estimating Guidelines, Vendor shall use reasonable and good faith efforts to meet the Service Level Standards set forth below.

  • Construction Management Plan Contractor shall prepare and furnish to the Owner a thorough and complete plan for the management of the Project from issuance of the Proceed Order through the issuance of the Design Professional's Certificate of Material Completion. Such plan shall include, without limitation, an estimate of the manpower requirements for each trade and the anticipated availability of such manpower, a schedule prepared using the critical path method that will amplify and support the schedule required in Article 2.1.5 below, and the Submittal Schedule as required in Article 2.2.3. The Contractor shall include in his plan the names and resumés of the Project Superintendent, Project Manager and the person in charge of Safety.

  • Implementation Report Within 120 days after the Effective Date, Xxxxxxxx shall submit a written report to OIG summarizing the status of its implementation of the requirements of this CIA (Implementation Report). The Implementation Report shall, at a minimum, include:

  • Change Management BellSouth provides a collaborative process for change management of the electronic interfaces through the Change Control Process (CCP). Guidelines for this process are set forth in the CCP document as amended from time to time during this Agreement. The CCP document may be accessed via the Internet at xxxx://xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxx.

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