Proposals – the Municipality will Sample Clauses

Proposals – the Municipality will. (a) submit a Proposal to the Province for each Wetland Replacement Project that the Municipality wishes to propose for the Province’s approval; (b) ensure that each Proposal meets the Proposal Submission Requirements (“Schedule A”); and (c) aim to submit at least one Proposal per year.
AutoNDA by SimpleDocs

Related to Proposals – the Municipality will

  • Joint Funded Project with the Ohio Department of Transportation In the event that the Recipient does not have contracting authority over project engineering, construction, or right-of-way, the Recipient and the OPWC hereby assign certain responsibilities to the Ohio Department of Transportation, an authorized representative of the State of Ohio. Notwithstanding Sections 4, 6(a), 6(b), 6(c), and 7 of the Project Agreement, Recipient hereby acknowledges that upon notification by the Ohio Department of Transportation, all payments for eligible project costs will be disbursed by the Grantor directly to the Ohio Department of Transportation. A Memorandum of Funds issued by the Ohio Department of Transportation shall be used to certify the estimated project costs. Upon receipt of a Memorandum of Funds from the Ohio Department of Transportation, the OPWC shall transfer funds directly to the Ohio Department of Transportation via an Intra- State Transfer Voucher. The amount or amounts transferred shall be determined by applying the Participation Percentages defined in Appendix D to those eligible project costs within the Memorandum of Funds. In the event that the Project Scope is for right-of-way only, notwithstanding Appendix D, the OPWC shall pay for 100% of the right-of-way costs not to exceed the total financial assistance provided in Appendix C.

  • Contract Supremacy In the case of a conflict between the express terms of this Agreement and the terms of the ISO Agreement, the express terms of this Agreement shall prevail.

  • Proposing Integration Activities in the Planning Submission No integration activity described in section 6.3 may be proposed in a CAPS unless the Funder has consented, in writing, to its inclusion pursuant to the process set out in section 6.3(b).

  • Office of Foreign Assets Control Neither the Company nor any Subsidiary nor, to the Company’s knowledge, any director, officer, agent, employee or affiliate of the Company or any Subsidiary is currently subject to any U.S. sanctions administered by the Office of Foreign Assets Control of the U.S. Treasury Department (“OFAC”).

  • LEAVE FOR REGULATORY BUSINESS AS PER THE TEACHERS’ ACT 1. Upon written request to the Superintendent or designate from the Ministry of Education, an employee who is appointed or elected to the BC Teachers’ Council or appointed to the Disciplinary or Professional Conduct Board shall be entitled to a leave of absence with pay and shall be deemed to be in the full employ of the board as defined in Article G.6.1. 2. Upon written request to the superintendent or designate from the Ministry of Education, a teacher teaching on call (TTOC) who is appointed or elected to the BC Teachers’ Council or appointed to the Disciplinary and Professional Conduct Board shall be considered on leave and shall be deemed to be in the full employ of the Board as defined in Article A.10.1 above. TTOCs shall be paid in accordance with the collective agreement. 3. Leave pursuant to Article A.10.1 and A.10.2 above shall not count toward any limits on the number of days and/or teachers on leave in the provisions in Article G.6.

  • Increasing Seat Belt Use in the United States E.O. 13043, amended by E.O. 13652, requires Recipients to encourage employees and contractors to enforce on-the-job seat belt policies and programs when operating company- owned, rented or personally-owned vehicle.

  • 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

  • PARTICIPATING ENTITY USE AND PURCHASING A. ORDERS AND PAYMENT. To access the contracted Equipment, Products, or Services under this Contract, a Participating Entity must clearly indicate to Supplier that it intends to access this Contract; however, order flow and procedure will be developed jointly between Sourcewell and Supplier. Typically, a Participating Entity will issue an order directly to Supplier or its authorized subsidiary, distributor, dealer, or reseller. If a Participating Entity issues a purchase order, it may use its own forms, but the purchase order should clearly note the applicable Sourcewell contract number. All Participating Entity orders under this Contract must be issued prior to expiration or cancellation of this Contract; however, Supplier performance, Participating Entity payment obligations, and any applicable warranty periods or other Supplier or Participating Entity obligations may extend beyond the term of this Contract. Supplier’s acceptable forms of payment are included in its attached Proposal. Participating Entities will be solely responsible for payment and Sourcewell will have no liability for any unpaid invoice of any Participating Entity. B. ADDITIONAL TERMS AND CONDITIONS/PARTICIPATING ADDENDUM. Additional terms and conditions to a purchase order, or other required transaction documentation, may be negotiated between a Participating Entity and Supplier, such as job or industry-specific requirements, legal requirements (e.g., affirmative action or immigration status requirements), or specific local policy requirements. Some Participating Entities may require the use of a Participating Addendum, the terms of which will be negotiated directly between the Participating Entity and the Supplier or its authorized dealers, distributors, or resellers, as applicable. Any negotiated additional terms and conditions must never be less favorable to the Participating Entity than what is contained in this Contract.

  • CFR PART 200 Domestic Preferences for Procurements As appropriate and to the extent consistent with law, the non-Federal entity should, to the greatest extent practicable under a Federal award, provide a preference for the purchase, acquisition, or use of goods, products, or materials produced in the United States (including but not limited to iron, aluminum, steel, cement, and other manufactured products). The requirements of this section must be included in all subawards including all contracts and purchase orders for work or products under this award. For purposes of 2 CFR Part 200.322, “Produced in the United States” means, for iron and steel products, that all manufacturing processes, from the initial melting stag through the application of coatings, occurred in the United States. Moreover, for purposes of 2 CFR Part 200.322, “Manufactured products” means items and construction materials composed in whole or in part of non-ferrous metals such as aluminum, plastics and polymer-based products such as polyvinyl chloride pipe, aggregates such as concrete, class, including optical fiber, and lumber. Pursuant to the above, when federal funds are expended by ESC Region 8 and TIPS Members, Vendor certifies that to the greatest extent practicable Vendor will provide a preference for the purchase, acquisition, or use of goods, products, or materials produced in the United States (including but not limited to iron, aluminum, steel, cement, and other manufactured products). Does vendor agree? Yes

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