Local and Regional Governmental Entity Transfer Process Sample Clauses

Local and Regional Governmental Entity Transfer Process. The White Pine County Conservation, Recreation, and Development Act of 2006 (P.L. 109-423, Division C, Title III, provides that the BLM shall transfer funds to local and regional governments for Park, Trail, and Natural Area projects authorized by the Secretary of the Interior and approved for expenditure. The BLM will utilize the Automated Standard Application for Payment (ASAP) system to implement this transfer process. Funds will not be considered “approved for expenditure” until the following conditions set out by the Secretary have been met: • A notification of availability of funds has been issued; • A cooperative agreement between the entity and the BLM has been fully executed; • A work plan has been submitted by the entity and accepted by BLM where the plan includes a schedule of periodic expenditures reflecting logical phases of the project, generally quarterly; • A start point for an identified phase and its associated funding start date have been reached; and • Any other conditions which may be imposed by the Secretary of the Interior in the future. The quarterly report required by BLM will meet the last two requirements by providing an annual work plan at the commencement of the project and estimated quarterly funding needs for the fiscal year, as well as accomplishments related to the project deliverables; and actual funds needed for the quarter the report is submitted. BLM will provide the entities with a reporting format, preferably electronically, which includes all approved projects for each entity. This format will allow entities to designate amounts to be transferred through ASAP or funds to be reimbursed for project which are still under the reimbursement process. ASAP is an all-electronic payment and information system which was developed jointly by the Financial Management Service (FMS) and Federal Reserve Bank of Richmond. The latter, in its capacity as Treasury’s fiscal agent, operates the ASAP system. ASAP is a system through which organizations that are receiving Federal funds can draw down from accounts pre-authorized by Federal agencies. Local and Regional governmental entities may initiate draw downs on the ASAP system through the internet. Draw downs may be initiated daily, weekly, monthly, or quarterly to meet the immediate needs of the local and regional governmental entities to cover necessary expenses for the approved project. Treasury Circular 1075 (31CFR 205) addresses Treasury rules for transferring (paying) funds betwe...
Sample 1
AutoNDA by SimpleDocs

Related to Local and Regional Governmental Entity Transfer Process

  • Statewide HUB Program Statewide Procurement Division Note: In order for State agencies and institutions of higher education (universities) to be credited for utilizing this business as a HUB, they must award payment under the Certificate/VID Number identified above. Agencies, universities and prime contractors are encouraged to verify the company’s HUB certification prior to issuing a notice of award by accessing the Internet (xxxxx://xxxxx.xxx.xxxxx.xx.xx/tpasscmblsearch/index.jsp) or by contacting

  • TECHNOLOGY/KNOWLEDGE TRANSFER ACTIVITIES The goal of this task is to develop a plan to make the knowledge gained, experimental results, and lessons learned available to the public and key decision makers. • Prepare an Initial Fact Sheet at start of the project that describes the project. Use the format provided by the CAM. • Prepare a Final Project Fact Sheet at the project’s conclusion that discusses results. Use the format provided by the CAM. • Prepare a Technology/Knowledge Transfer Plan that includes: o An explanation of how the knowledge gained from the project will be made available to the public, including the targeted market sector and potential outreach to end users, utilities, regulatory agencies, and others. o A description of the intended use(s) for and users of the project results. o Published documents, including date, title, and periodical name. o Copies of documents, fact sheets, journal articles, press releases, and other documents prepared for public dissemination. These documents must include the Legal Notice required in the terms and conditions. Indicate where and when the documents were disseminated. o A discussion of policy development. State if project has been or will be cited in government policy publications, or used to inform regulatory bodies. o The number of website downloads or public requests for project results. o Additional areas as determined by the CAM. • Conduct technology transfer activities in accordance with the Technology/Knowledge Transfer Plan. These activities will be reported in the Progress Reports. • When directed by the CAM, develop Presentation Materials for an Energy Commission- sponsored conference/workshop(s) on the project. • When directed by the CAM, participate in annual EPIC symposium(s) sponsored by the California Energy Commission. • Provide at least (6) six High Quality Digital Photographs (minimum resolution of 1300x500 pixels in landscape ratio) of pre and post technology installation at the project sites or related project photographs. • Prepare a Technology/Knowledge Transfer Report on technology transfer activities conducted during the project. • Initial Fact Sheet (draft and final) • Final Project Fact Sheet (draft and final) • Presentation Materials (draft and final) • High Quality Digital Photographs • Technology/Knowledge Transfer Plan (draft and final) • Technology/Knowledge Transfer Report (draft and final)

  • Authority; No Conflict; Required Filings and Consents (a) The Fund has all requisite power and authority to enter into this Agreement and, subject to the approval of this Agreement by the Partners under the FRULPA and the Fund LP Agreement, to consummate the transactions contemplated by this Agreement. The execution and delivery of this Agreement and the consummation of the transactions contemplated by this Agreement by the Fund have been duly authorized by all necessary action on the part of the Fund, subject to the approval of this Agreement by the Partners under the FRULPA and the Fund LP Agreement. This Agreement has been duly executed and delivered by the Fund and constitutes the valid and binding obligation of the Fund, enforceable in accordance with its terms, except that the enforceability of this Agreement is subject only to the approval of this Agreement by the Partners under the FRULPA and the Fund LP Agreement. (b) The execution and delivery of this Agreement by the Fund does not, and, subject to the approval of this Agreement by the Partners under the FRULPA and the Fund LP Agreement, the consummation of the transactions contemplated by this Agreement will not, (i) conflict with, or result in any violation or breach of, any provision of the Fund LP Certificate, the Fund LP Agreement or the charter, bylaws, or other organizational document of any of the Fund’s Subsidiaries, (ii) except as set forth on Section 4.3(b) of the Fund Disclosure Schedule, conflict with, or result in any violation or breach of, or constitute (with or without notice or lapse of time, or both) a default (or give rise to a right of termination, cancellation or acceleration of any obligation or loss of any material benefit) under, require a consent or waiver under, or result in the creation of a security interest, lien, claim, pledge, agreement, limitations in the Fund’s voting right, charge or other encumbrance of any nature on any of the properties or assets of the Fund or any of its Subsidiaries pursuant to any of the terms, conditions or provisions of, any note, bond, mortgage, indenture, lease, license, contract or other agreement, instrument or obligation to which the Fund or any of its Subsidiaries is a party or by which any of them or any of their properties or assets may be bound, (iii) subject to compliance with the requirements specified in clauses (i), (ii), (iii) and (iv) of Section 4.3(c), conflict with or violate any permit, concession, franchise, license, judgment, injunction, order, decree, statute, law, ordinance, rule or regulation applicable to the Fund or any of its Subsidiaries or any of its or their properties or assets; or (iv) except as set forth on Section 4.3(b) of the Fund Disclosure Schedule, require the Fund under the terms of any agreement, contract, arrangement or understanding to which it is a party or by which it or its assets are bound, to obtain the consent or approval of, or provide notice to, any other party to any such agreement, contract, arrangement or understanding, except in the case of clauses (i), (ii), (iii) and (iv) of this Section 4.3(b) for any such conflicts, violations, breaches, defaults, terminations, cancellations, accelerations, losses, failure to obtain consent or approval or failure to notify which could not, individually or in the aggregate, reasonably be expected to have a Fund Material Adverse Effect. (c) No consent, approval, license, permit, order or authorization of, or registration, declaration, notice or filing with, any Governmental Entity is required by or with respect to the Fund or any of its Subsidiaries in connection with the execution and delivery of this Agreement or the consummation of the transactions contemplated by this Agreement, except for (i) the filing of the Acquisition LLC Articles of Merger with the Maryland Department of Assessments and Taxation, the filing of the Fund Articles of Merger with the Florida Department of State, and appropriate corresponding documents with the Secretaries of State of other states in which the Fund is qualified as a foreign corporation to transact business, (ii) the filing of reports with the SEC in accordance with the Exchange Act, (iii) the compliance with any state securities laws, and (iv) any consent, approval, license, permit, order, authorization, registration, declaration, notice or filing, which, if not obtained or made, could not, individually or in the aggregate, reasonably be expected to have a Fund Material Adverse Effect. (d) As of the date of this Agreement, the General Partners have (i) unanimously approved and declared advisable this Agreement to which the Fund is a party, (ii) determined that the transactions contemplated hereby are advisable, fair to and in the best interests of the Partners, (iii) resolved to recommend approval of this Agreement, the Merger, and the other transactions contemplated hereby to the Partners and (iv) directed that this Agreement be submitted to the Partners for their approval and authorization. As of the date of this Agreement, none of the General Partners have withdrawn, rescinded or modified such approvals, determination, and resolutions to recommend. The affirmative vote of all of the General Partners and the holders of a majority of Fund Interests is the only vote of the holders of any interest in the Fund necessary to approve and authorize this Agreement, the Merger and the other transactions contemplated hereby. (e) Except as set forth in Section 4.3(e) of the Fund Disclosure Schedule, to the Fund’s Knowledge, there is no agreement or order binding upon the Fund or any of its Subsidiaries or any of their assets or properties which has had or could reasonably be expected to have the effect of prohibiting or materially impairing any current business practice of the Fund or any of its Subsidiaries or the conduct of business by the Fund or any of its Subsidiaries as currently conducted or as proposed to be conducted by the Fund or any of its Subsidiaries. To the Fund’s Knowledge, neither the Fund nor any of its Subsidiaries is subject to any non-competition, non-solicitation or similar restriction on their respective businesses. “Fund’s Knowledge” means knowledge of a particular fact or other matter by Xxxxx X. Xxxxxx, Xx. or Xxxxxx X. Xxxxxx, if such individual is actually aware of such fact or other matter.

  • Corporate and Governmental Authorization; No Contravention The execution, delivery and performance by the Borrower of this Agreement and the Notes are within the Borrower's corporate powers, have been duly authorized by all necessary corporate action, require no action by or in respect of, or filing with, any governmental body, agency or official and do not contravene, or constitute a default under, any provision of applicable law or regulation or of the articles of incorporation or by-laws of the Borrower or of any agreement, judgment, injunction, order, decree or other instrument binding upon the Borrower or result in the creation or imposition of any Lien on any asset of the Borrower or any of its Material Subsidiaries.

  • Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES

  • Necessary Governmental Approvals The parties shall have received all approvals and actions of or by all Governmental Bodies which are necessary to consummate the transactions contemplated hereby, which are either specified in Schedule 5.3(B)(ii) or otherwise required to be obtained prior to the Closing by applicable Requirements of Laws.

  • Required Governmental Approvals All governmental authorizations, consents and approvals necessary for the valid consummation of the transactions contemplated hereby shall have been obtained and shall be in full force and effect. All applicable governmental pre-acquisition filing, information furnishing and waiting period requirements shall have been met or such compliance shall have been waived by the governmental authority having authority to grant such waivers.

  • Tax Status Non Jurisdictional Entities Tax Status.‌‌ Each Party shall cooperate with the other Parties to maintain the other Parties’ tax status. Nothing in this Agreement is intended to adversely affect the tax status of any Party including the status of NYISO, or the status of any Connecting Transmission Owner with respect to the issuance of bonds including, but not limited to, Local Furnishing Bonds. Notwithstanding any other provisions of this Agreement, LIPA, NYPA and Consolidated Edison Company of New York, Inc. shall not be required to comply with any provisions of this Agreement that would result in the loss of tax-exempt status of any of their Tax-Exempt Bonds or impair their ability to issue future tax-exempt obligations. For purposes of this provision, Tax-Exempt Bonds shall include the obligations of the Long Island Power Authority, NYPA and Consolidated Edison Company of New York, Inc., the interest on which is not included in gross income under the Internal Revenue Code. LIPA and NYPA do not waive their exemptions, pursuant to Section 201(f) of the FPA, from Commission jurisdiction with respect to the Commission’s exercise of the FPA’s general ratemaking authority.

  • E1 Authority Data E1.1 The Contractor shall not delete or remove any proprietary notices contained within or relating to the Authority Data.

  • Reporting Obligations and Regulatory Approvals Applicable laws and regulations may require holders and beneficial owners of Shares, including the Holders and Beneficial Owners of ADSs, to satisfy reporting requirements and obtain regulatory approvals in certain circumstances. Holders and Beneficial Owners of ADSs are solely responsible for determining and complying with such reporting requirements and obtaining such approvals. Each Holder and each Beneficial Owner hereby agrees to make such determination, file such reports, and obtain such approvals to the extent and in the form required by applicable laws and regulations as in effect from time to time. Neither the Depositary, the Custodian, the Company or any of their respective agents or affiliates shall be required to take any actions whatsoever on behalf of Holders or Beneficial Owners to determine or satisfy such reporting requirements or obtain such regulatory approvals under applicable laws and regulations.

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