Transaction Specification Approval and Confirmation Sample Clauses

Transaction Specification Approval and Confirmation. Section 8.1 Specification and Approval of Transactions; Pricing and Commissions. (a) Overview. The parties acknowledge and agree that (i) Buyer shall resell to third-party purchasers all of the Ethanol that Buyer purchases from Seller hereunder, along with any associated RINs or LCFS Credits made available to Buyer under this Agreement, (ii) the amounts payable hereunder by Buyer to Seller for Ethanol, RINs and LCFS Credits shall be a function of the amounts that Buyer is able to obtain in such resale transactions, (iii) Buyer shall have a duty, acting in good faith and with commercially reasonable efforts, to attempt to obtain the maximum aggregate value in such resale transactions (taking into account the resale prices of Ethanol, RINs and LCFS Credits), and (iv) Buyer shall receive a commission in the manner calculated below in connection with its purchase and resale of Ethanol, RINs or LCFS Credits hereunder. (b) Specification and Approval of Ordinary Course Transactions. Buyer will present alternative transactions to Seller for (i) the sale of Ethanol, which will vary in delivery location, volume, price and delivery time, and (ii) for the sale of RINs or LCFS Credits, which sales are subject to specification in terms of price, time of delivery and other factors (each proposed transaction, being a “Transaction”). For each Transaction (and for multiple Transactions where permitted or required by the Regulatory Credit Protocol), Buyer shall present Seller with a written bid in a format mutually agreed by the parties (a “Bid”) setting forth following information as applicable (and any other information that may reasonably be requested from time to time by Seller): (i) name/identity of the proposed purchaser; (ii) number of Net Gallons, RINs and/or LCFS Credits proposed for sale; (iii) proposed Delivery date(s) and or Transaction term, as applicable; (iv) proposed sales price per Net Gallon (and if applicable proposed price per RIN and/or LCFS Credit); (v) a listing and the amount of all applicable Transaction Costs; (vi) a listing and the amount of all applicable Buyer Taxes; (vii) the Transaction Gross Purchase Price; (viii) the applicable Commissions; (ix) the Transaction Net Purchase Price; (x) the point of transfer of title to Ethanol, if not the Delivery Point (required with respect to LCFS Credits to be in California); (xi) such other Transaction information as may be relevant; and (xii) the time by which the Seller must accept the bid. Seller shall...
AutoNDA by SimpleDocs
Transaction Specification Approval and Confirmation 

Related to Transaction Specification Approval and Confirmation

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Inspection Checklist (Check one)

  • Project Completion Report At the completion of construction and once a Project is placed in service, the Subrecipient must submit a Project Completion Report that includes the total number of units built and leased, affordable units built and leased, DR-MHP units built and leased, an accomplishment narrative, and the tenants names, demographics and income for each DR-MHP unit.

  • Drug-Free Workplace Certification As required by Executive Order No. 90-5 dated April 12, 1990, issued by the Governor of Indiana, the Company hereby covenants and agrees to make a good faith effort to provide and maintain a drug-free workplace at the Project Location. The Company will give written notice to the IEDC within ten (10) days after receiving actual notice that the Company, or an employee of the Company in the State of Indiana, has been convicted of a criminal drug violation occurring in the workplace. False certification or violation of this certification may result in sanctions including, but not limited to, suspension of payments under the Agreement, termination of the Agreement and/or debarment of contracting opportunities with the State for up to three (3) years. In addition to the provisions of the above paragraph, if the total amount set forth in the Agreement is in excess of $25,000.00, the Company agrees that it will provide a drug-free workplace by: A. Publishing and providing to all of its employees a statement notifying them that the unlawful manufacture, distribution, dispensing, possession or use of a controlled substance is prohibited in the Company’s workplace, and specifying the actions that will be taken against employees for violations of such prohibition;

  • Implementation Report Within 150 days after the Effective Date, Ensign Group 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: 1. the name, address, phone number, and position description of the Compliance Officer required by Section III.A, and a summary of other noncompliance job responsibilities the Compliance Officer may have; 2. the names and positions of the members of the Compliance Committee required by Section III.A; 3. the names and positions of the members of the Board of Directors who are responsible for satisfying the Board of Directors compliance obligations described in Section III.A.3; 4. a copy of Ensign Group’s Code of Conduct required by Section III.B.1; 5. the number of individuals required to complete the Code of Conduct certification required by Section III.B.1, the percentage of individuals who have completed such certification, and an explanation of any exceptions (the documentation supporting this information shall be available to OIG upon request); 6. a summary of all Policies and Procedures required by Section III.B (copies of the Policies and Procedures shall be made available to OIG upon request); 7. the following information regarding each type of training required by Section III.C: a. a description of such training, including a summary of the topics covered, the length of sessions, and a schedule of training sessions; b. the number of individuals required to be trained, percentage of individuals actually trained, and an explanation of any exceptions. A copy of all training materials and the documentation supporting this information shall be made available to OIG upon request. 8. a description of the Disclosure Program required by Section III.E; 9. the following information regarding the IRO(s): (a) identity, address, and phone number; (b) a copy of the engagement letter; (c) information to demonstrate that the IRO has the qualifications outlined in Appendix A to this CIA; (d) a summary and description of any and all current and prior engagements and agreements between Ensign Group and the IRO; and (e) a certification from the IRO regarding its professional independence and objectivity with respect to Ensign Group; 10. a description of the process by which Ensign Group fulfills the requirements of Section III.F regarding Ineligible Persons; 11. a list of all of Ensign Group’s locations (including locations and mailing addresses); the corresponding name under which each location is doing business; the corresponding phone numbers and fax numbers; each location’s Medicare and state Medicaid program provider number and/or supplier number(s); and the name and address of each Medicare and state Medicaid program contractor to which Ensign Group currently submits claims; 12. a description of Ensign Group’s corporate structure, including identification of any parent and sister companies, subsidiaries, and their respective lines of business; and

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Completion Schedule 6.1 The proposed schedule for the completion of the Project is presented in “Attachment D” and is made a part hereof. 6.2 ENGINEER shall adhere to all time limits stated in this Agreement or included in any accepted time schedule. All such time limits shall be of the essence to this Agreement. 6.3 In all events the various stages and phases of ENGINEER’S services are to be completed in such sequence and at such times, and with approved or agreed upon time limits, as may be required to assure the timely, continuous, efficient and diligent prosecution of the work and services provided for by this Agreement. 6.4 OWNER may at any time, by written order, make changes within the general scope of the Agreement in the services of work to be performed. If ENGINEER believes that such a change justifies an increase in ENGINEER’S contract time or contract price required to perform the series under this Agreement it must assert such claim in writing within thirty (30) days of receipt of OWNER’S written order giving rise to the claim. No claim for adjustment in the contract time or contract price will be valid if not submitted in accordance with this paragraph. No services for which ENGINEER will charge additional compensation shall be furnished without the written authorization of OWNER. 6.5 ENGINEER shall carry on all work required under this Agreement and maintain the schedule for services during all disputes or disagreements with OWNER. No work shall be delayed or postponed pending resolution of any disputes or disagreements except as permitted in Article 8, or as ENGINEER and OWNER may otherwise agree in writing. 6.6 If the commencement, prosecution or completion of the services under this Agreement, or of the construction of the Project is delayed by any act, omission, delay, neglect or default of ENGINEER, or anyone employed by ENGINEER, or by any damage or acts caused by the negligent acts or omission by ENGINEER, then ENGINEER shall be liable to OWNER for any and all costs, assessments, expense, liabilities or damages caused thereby, in accordance with Section 4.8. 6.7 ENGINEER shall not be responsible for any time delays in the Project, or in the performance of services under this Agreement, to the extent such delays are caused solely by any act, omission, neglect or default of OWNER or anyone employed by OWNER, or by the unreasonable delay of any review agency or utility, or for any delay or damage caused by fire or the combined action of workers and which are in no way chargeable, in whole or in part, to ENGINEER, or by any other conditions or circumstances beyond the control of ENGINEER, its employee, agent, or other persons for whose acts or omissions ENGINEER is responsible. In the event of such delay, ENGINEER shall be entitled to an adjustment in the schedules or agreed time limitations for the performance of services, and this Agreement shall be modified in writing accordingly. Any claim of ENGINEER for adjustment under this cause must be asserted in writing within thirty (30) days from the date of the occurrence of the event giving rise to the claim, unless OWNER grants a further period of time before the date of final payment to ENGINEER. The adjustment of time for the performance of services, as provided in this paragraph, shall be ENGINEER’s sole exclusive right, entitlement and remedy in the event of such delays, and ENGINEER shall have no claim against OWNER for adjustment for increase in costs of performance, or other damages occurred in connection therewith.

  • Attachment  C_ CONTRACT AFFIRMATIONS For purposes of these Contract Affirmations, HHS includes both the Health and Human Services Commission (HHSC) and the Department of State Health Services (DSHS). System Agency refers to HHSC, DSHS, or both, that will be a party to this Contract. These Contract Affirmations apply to all Contractors and Grantees (referred to as “Contractor”) regardless of their business form (e.g., individual, partnership, corporation). By entering into this Contract, Contractor affirms, without exception, understands, and agrees to comply with the following items through the life of the Contract:

  • Packing Specifications 7.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

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