SIGNATORY WARRANTY The undersigned signatory for the Engineer hereby represents and warrants that he or she is an officer of the organization for which he or she has executed this contract and that he or she has full and complete authority to enter into this contract on behalf of the firm. These representations and warranties are made for the purpose of inducing the State to enter into this contract.
Signatory Each signatory below represents and warrants that he or she has full power and is duly authorized by their respective party to enter into and perform under this Agreement. Such signatory also represents that he or she has fully reviewed and understands the above conditions and intends to fully abide by the conditions and terms of this Agreement as stated.
OFFICER SIGNATURE OFFICER NAME: TITLE Exhibit 2a This exhibit contains three versions of the loss share calculation for foreclosure, plus explanatory notes. Exhibit 2a(1) CALCULATION OF FORECLOSURE LOSS Foreclosure Occurred Prior to Loss Share Agreement 1 Shared-Loss Month May-09 2 Loan no: 364574 3 REO # 621 4 Foreclosure date 12/18/08 5 Liquidation date 4/12/09 6 Note Interest rate 8.100% 7 Most recent BPO 228,000 8 Most recent BPO date 1/21/09 Foreclosure Loss calculation 9 Book value at date of Loss Share agreement 244,900 Accrued interest, limited to 90 days or days from failure 10 to sale, whichever is less 3,306 11 Costs incurred after Loss Share agreement in place: 12 Attorney's fees 0 Foreclosure costs, including title search, filing fees, 13 advertising, etc. 0 14 Property protection costs, maint. and repairs 6,500 15 Tax and insurance advances 0 Other Advances 16 Appraisal/Broker's Price Opinion fees 0 17 Inspections 0 18 Other 0 19 Gross balance recoverable by Purchaser 254,706 Cash Recoveries: 20 Net liquidation proceeds (from HUD-1 settl stmt) 219,400 21 Hazard Insurance proceeds 0 22 Mortgage Insurance proceeds 0 23 T & I escrow account balances, if positive 0 24 Other credits, if any (itemize) 0 25 Total Cash Recovery 219,400 26 Loss Amount 35,306 Exhibit 2a(2)
Signature Date PLEASE INITIAL PAGE 2 Please retain a photocopy of this form for your own records. Terms and Conditions on Reverse Side TERMS AND CONDITIONS
EFFECTIVE DATE AND SIGNATURE This MOU shall be effective upon the signature of authorized officials from Party A and Party B. It shall be in force from (Date to be finalized with Lease-Up) to (Date to be finalized with Lease-Up). Parties A and B indicate agreement with this MOU by their signatures below. Party A Party B By: By: Title: Title: Signed: Signed: Date: Date:
DELIVERY SCHEDULES In accordance with the "Non-State Agencies Participation in Centralized Contracts” and “Extension of Use” clauses herein, this Contract is extended to local governments, political subdivisions and others authorized by law as well as State agencies. The Delivery Schedules (based on Requirement Letter RL182) are available as a guide to indicate proposed delivery points and estimated annual requirements. Delivery Schedules may be revised or clarified as necessary. Any specific questions regarding the site conditions should be directed to the end-user at the telephone number shown on the Delivery Schedule. The Delivery Schedules are available upon request. Contractors shall be obligated to deliver under the Contract to any State agency which places a purchase order under the Contract, whether or not such delivery location is identified in the Delivery Schedules. Any political subdivision or other non-State entity which has not filed a requirement with OGS as of the date of the bid opening shall be eligible to receive deliveries at Contractor's option only, upon placement of a valid purchase order to the Contractor's address as indicated in the award. Contracts created by OGS in response to receipt of Filed Requirements are considered to be binding. At Contractor's request, Contractor will be advised in writing regarding political subdivisions or other Non-State entities which have filed on a timely basis but do not appear on the Delivery Schedule. Where “Standby” is indicated in the Delivery Schedule, this reflects those facilities which normally use a fuel supply (i.e. natural gas) other than fuel oil and will only use fuel oil when alternate fuel is unavailable.
Signatories Each individual signatory hereto represents and warrants that he is duly authorized to execute this Agreement on behalf of his principal and that he executes the Agreement in such capacity and not as a party.
Signature This Section 2 and the exercise form attached hereto set forth the totality of the procedures required of the Holder in order to exercise this Purchase Warrant. Without limiting the preceding sentences, no ink-original exercise form shall be required, nor shall any medallion guarantee (or other type of guarantee or notarization) of any exercise form be required in order to exercise this Purchase Warrant. No additional legal opinion, other information or instructions shall be required of the Holder to exercise this Purchase Warrant. The Company shall honor exercises of this Purchase Warrant and shall deliver Shares underlying this Purchase Warrant in accordance with the terms, conditions and time periods set forth herein.
Student Signature By signing this contract, Resident agrees to pay the contract amount (room, board and association fees) in accordance with Addendum B: Rate and Payment Schedule. Resident may pay the full amount due prior to the due date, at the Resident’s election.
Escrow Format Specification 3.1. 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.
