Planning As a Requirement of Economic Assistance Sample Clauses

Planning As a Requirement of Economic Assistance. (a) No later than 90 days after the entry into force of Title Two of the Compact, as amended, and thereafter at intervals no greater than three years from that date, the Government of the Republic of the Xxxxxxxx Islands shall submit to the Government of the United States a “Medium-Term Budget and Investment Frameworkpursuant to section 211(f) of Title Two of the Compact, as amended, (the “MTBIF”). The MTBIF shall be strategic in nature, identify the multi-year priorities, budget and implementation plan of the Government of the Republic of the Xxxxxxxx Islands to promote economic advancement and budgetary self- reliance, and contain the goals for the sectors described in section 211(a) of the Compact, as amended, for the assistance described in section 211(b) thereof, and for the Supplemental Education Grant. Each of the sectors or areas so named, or other sectors as agreed by the Committee, shall be accorded specific treatment in the framework. Such sector or other strategies and goals shall be continuously reviewed and updated though the annual budget process. Those portions of the MTBIF that contemplate use of United States Grant funds require the concurrence of the Committee.
AutoNDA by SimpleDocs
Planning As a Requirement of Economic Assistance. (a) No later than 90 days after the effective date of Title Two of the Compact, as amended, and thereafter at appropriate intervals, the Government of the Federated States of Micronesia shall prepare and submit to the Government of the United States a “Multi-Year Rolling Development Plan” pursuant to section 211(f) of Title Two of the Compact, as amended (the “Development Plan”). The Development Plan shall be strategic in nature and continuously reviewed and updated through the annual budget process. It shall identify the goals and broad strategies of the Government of the Federated States of Micronesia to promote economic advancement, budgetary self-reliance, and economic self-reliance, and contain specific multi-year objectives for the sectors described in section 211(a) of the Compact, as amended. Each of the sectors so named, or other sectors as agreed to by the Committee, shall be accorded specific treatment in the Development Plan. Those portions of the Development Plan that contemplate use of United States Grant funds require the concurrence of the Committee.

Related to Planning As a Requirement of Economic Assistance

  • COMPLIANCE WITH THE CONTRACT WORK HOURS AND SAFETY STANDARDS ACT (1) Overtime requirements. No contractor or subcontractor contracting for any part of the contract work which may require or involve the employment of laborers or mechanics shall require or permit any such laborer or mechanic in any workweek in which he or she is employed on such work to work in excess of forty hours in such workweek unless such laborer or mechanic receives compensation at a rate not less than one and one-half times the basic rate of pay for all hours worked in excess of forty hours in such workweek.

  • Information Technology Accessibility Standards Any information technology related products or services purchased, used or maintained through this Grant must be compatible with the principles and goals contained in the Electronic and Information Technology Accessibility Standards adopted by the Architectural and Transportation Barriers Compliance Board under Section 508 of the federal Rehabilitation Act of 1973 (29 U.S.C. §794d), as amended. The federal Electronic and Information Technology Accessibility Standards can be found at: xxxx://xxx.xxxxxx-xxxxx.xxx/508.htm.

  • Requirement to Utilize HUB Compliance Reporting System Pursuant to Texas Administrative Code, Title 34, Part 1, Sections 20.285(f) and 20.287(b), TFC administers monthly administration HSP-PAR compliance monitoring through its HUB Compliance Reporting System commonly known as B2G. PSP and PSP’s subcontractors/subconsultants shall submit required PAR information into the B2G system. Any delay in the timely submission of PAR information into the B2G system will be treated as an invoicing error subject to dispute under Texas Government Code Section 2251.042.

  • Export Control Compliance User acknowledges that Center is an open laboratory for fundamental research that has many foreign persons as its employees and students. User understands and agrees that under no circumstances will User bring export control-listed items, or unpublished software source code or technical information in the form of defense articles or technical data regulated by the International Traffic in Arms Regulations (ITAR), to Center. Use of Center or facilities for activity subject to the ITAR, including the development, assembly or fabrication of defense articles identified on the US Munitions List, is prohibited.

  • Human and Financial Resources to Implement Safeguards Requirements 6. The Borrower shall make available necessary budgetary and human resources to fully implement the EMP and the RP.

  • Contract Work Hours and Safety Standards Act The following clauses apply to any Federal-aid construction contract in an amount in excess of $100,000 and subject to the overtime provisions of the Contract Work Hours and Safety Standards Act. These clauses shall be inserted in addition to the clauses required by 29 CFR 5.5(a) or 29 CFR 4.6. As used in this paragraph, the terms laborers and mechanics include watchmen and guards.

  • Information Technology Enterprise Architecture Requirements If this Contract involves information technology-related products or services, the Contractor agrees that all such products or services are compatible with any of the technology standards found at xxxxx://xxx.xx.xxx/iot/2394.htm that are applicable, including the assistive technology standard. The State may terminate this Contract for default if the terms of this paragraph are breached.

  • CONTRACT WORK HOURS AND SAFETY STANDARDS As per the Contract Work Hours and Safety Standards Act (40 U.S.C. 3701-3708), where applicable, all Customer Purchase Orders in excess of ,000 that involve the employment of mechanics or laborers must include a provision for compliance with 40 U.S.C. 3702 and 3704, as supplemented by Department of Labor regulations (29 CFR Part 5). Under 40 U.S.C. 3702 of the Act, each contractor must be required to compute the wages of every mechanic and laborer on the basis of a standard work week of 40 hours. Work in excess of the standard work week is permissible provided that the worker is compensated at a rate of not less than one and a half times the basic rate of pay for all hours worked in excess of 40 hours in the work week. The requirements of 40 U.S.C. 3704 are applicable to construction work and provide that no laborer or mechanic must be required to work in surroundings or under working conditions which are unsanitary, hazardous or dangerous. These requirements do not apply to the purchases of supplies or materials or articles ordinarily available on the open market, or contracts for transportation or transmission of intelligence.

  • COMPLIANCE BY CONTRACTOR WITH LAWS AND REGULATIONS/ EQUAL EMPLOYMENT OPPORTUNITY 6.1 In connection with the performance of the Services, the Contractor shall comply with all applicable statutes, laws, regulations, and orders of federal, state, county or municipal authorities which impose any obligation or duty upon the Contractor, including, but not limited to, civil rights and equal employment opportunity laws. In addition, if this Agreement is funded in any part by monies of the United States, the Contractor shall comply with all federal executive orders, rules, regulations and statutes, and with any rules, regulations and guidelines as the State or the United States issue to implement these regulations. The Contractor shall also comply with all applicable intellectual property laws.

  • Standards Compliance DNS. Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn--ndk061n”).

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