Background and Initial Obligations Sample Clauses

Background and Initial Obligations. 1.1 The “Buyer” is: Elance ID: Legal Name: Type of Legal Organization or Proprietorship: Jurisdiction of Organization: Address of Principal Place of Business: The “Service Provider” is: Elance ID: Legal Name: Type of Legal Organization or Proprietorship: Jurisdiction of Organization: Address of Principal Place of Business: 1.3 The “Project” is: Elance Project ID: Elance Project Name:
AutoNDA by SimpleDocs
Background and Initial Obligations 

Related to Background and Initial Obligations

  • FINANCIAL OBLIGATIONS There will be no transfer of funds between the Parties under this Agreement and each Party will fund its own participation. All activities under or pursuant to this Agreement are subject to the availability of funds, and no provision of this Agreement shall be interpreted to require obligation or payment of funds in violation of the Anti-Deficiency Act, (31 U.S.C. § 1341).

  • BACKGROUND AND INTRODUCTION The Federal-aid Highway Program (FAHP) is a federally-assisted program of State-selected projects. The Federal Highway Administration (FHWA) and the State Departments of Transportation have long worked as partners to deliver the FAHP in accordance with Federal requirements. In enacting 23 U.S.C. 106(c), as amended, Congress recognized the need to give the States more authority to carry out project responsibilities traditionally handled by FHWA. Congress also recognized the importance of a risk-based approach to FHWA oversight of the FAHP, establishing requirements in 23 U.S.C. 106(g). This Stewardship and Oversight (S&O) Agreement sets forth the agreement between the FHWA and the State of Florida Department of Transportation (FDOT) on the roles and responsibilities of the FHWA and the State DOT with respect to Title 23 project approvals and related responsibilities, and FAHP oversight activities. The scope of FHWA responsibilities, and the legal authority for State DOT assumption of FHWA responsibilities, developed over time. The U.S. Secretary of Transportation delegated responsibility to the Administrator of the FHWA for the FAHP under Title 23 of the United States Code, and associated laws. (49 CFR 1.84 and 1.85) The following legislation further outlines FHWA’s responsibilities: • Intermodal Surface Transportation Efficiency Act (ISTEA) of 1991; • Transportation Equity Act for the 21st Century (TEA-21) of 1998; • Safe, Accountable, Flexible, Efficient Transportation Equity Act: A Legacy for Users (SAFETEA-LU) of 2005; and • Moving Ahead for Progress in the 21st Century Act (MAP-21) of 2012 (P.L. 112-141). The FHWA may not assign or delegate its decision-making authority to a State Department of Transportation unless authorized by law. Xxxxxxx 000 xx Xxxxx 00, Xxxxxx Xxxxxx Code (Section 106), authorizes the State to assume specific project approvals. For projects that receive funding under Title 23, U.S.C., and are on the National Highway System (NHS) including projects on the Interstate System, the State may assume the responsibilities of the Secretary of the U.S. Department of Transportation under Title 23 for design, plans, specifications, estimates, contract awards, and inspections with respect to the projects unless the Secretary determines that the assumption is not appropriate. (23 U.S.C. 106(c)(1)) For projects under Title 23, U.S.C. that are not on the NHS, the State shall assume the responsibilities for design, plans, specifications, estimates, contract awards, and inspections unless the State determines that such assumption is not appropriate. (23 U.S.C. 106(c)(2)) For all other project activities which do not fall within the specific project approvals listed in Section 106 or are not otherwise authorized by law, the FHWA may authorize a State DOT to perform work needed to reach the FHWA decision point, or to implement FHWA’s decision. However such decisions themselves are reserved to FHWA. The authority given to the State DOT under Section 106(c)(1) and (2) is limited to specific project approvals listed herein. Nothing listed herein is intended to include assumption of FHWA’s decision-making authority regarding Title 23, U.S.C. eligibility or Federal-aid participation determinations. The FHWA always must make the final eligibility and participation decisions for the Federal-aid Highway Program. Section 106(c)(3) requires FHWA and the State DOT to enter into an agreement relating to the extent to which the State DOT assumes project responsibilities. This Stewardship and Oversight Agreement (S&O Agreement), includes information on specific project approvals and related responsibilities, and provides the requirements for FHWA oversight of the FAHP (Oversight Program), as required by 23 U.S.C. 106(g).

  • Payment of Project Activities County will reimburse Subrecipient for eligible project-related costs only. Subrecipient shall submit requests for reimbursement to County on a monthly basis beginning on August 1, 2021, and must provide adequate documentation as required by County in accordance with the OC Community Resources Contract Reimbursement Policy, as set forth in Exhibit 1, attached hereto and incorporated herein by reference. In addition, Subrecipient will provide a progress Grantee Performance Report (“GPR Information Form”) for the time period covered, as prescribed by County. Failure to provide any of the required documentation and reporting will cause County to withhold all or a portion of a request for reimbursement, or return the entire reimbursement package to Subrecipient, until such documentation and reporting has been received and approved by County.

  • Background and Instructions History of Agreement- This agreement has been drafted by the Texas Student Privacy Alliance (TXSPA). The Alliance is a collaborative group of Texas school districts that share common concerns around student and data privacy. The Texas K-12 CTO Council is the organization that sponsors the TXSPAand the TXSPA is the Texas affiliate of the national Student Data Privacy Consortium (SDPC). The SDPC works with other state alliances by helping establish common data privacy agreements unique to the jurisdiction of each state. This Texas agreement was drafted specifically for K-12 education institutions and included broad stakeholder input from Texas school districts, statewide associations such as TASB, TASA, and TASBO, and the Texas Education Agency. The purpose of this agreement is to set standards of both practice and expectations around data privacy such that all parties involved have a common understanding of expectations. This agreement also provides a mechanism (Exhibit E- General Offer of Terms) that would allow an Operator to extend the ability of other Texas school districts to be covered under the terms of the agreement should an Operator sign Exhibit E. This mechanism is intended to create efficiencies for both Operators and LEAs and generally enhance privacy practices and expectations for K-12 institutions and for companies providing services to K-12 institutions.

  • Project Background 6.1.1. Brief description of Contracting Agency’s project background and/or situation leading to this Project

  • Financial Obligation While this contract is in effect, the student is required to meet the financial obligations of this contract. Housing fees are charged through the Account Services Office. Students must pay their accounts per the policies of that office.

  • Schedule for Completing Agreement Closeout Activities Provide All Draft and Final Written Products on a CD-ROM or USB memory stick, organized by the tasks in the Agreement. Products: • Final Meeting Agreement Summary (if applicable) • Schedule for Completing Agreement Closeout Activities • All Draft and Final Written Products

  • PROJECT ACTIVITIES Grantee must perform the project activities set forth on Exhibit A (the “Project”), attached hereto and incorporated in this Grant by this reference, for the period beginning on the Effective Date and ending June 30, 2021 (the “Performance Period”).

  • Background Investigations OSC policy requires that background investigations be conducted on Contractor Staff who will have access to OSC’s IT systems, access to OSC confidential information/data, or routine access to any OSC facility. For purposes of this policy, “routine access” is defined as access to an OSC facility for five consecutive business days or 10 business days over the annual term of the engagement. Accordingly, with the signing of this Agreement, the Contractor certifies that it has or will conduct a background investigation on Staff to whom the policy applies within the 12 months prior to the Staff commencing Services under this Agreement. The Contractor agrees to undertake a background investigation of any new/replacement Staff during the term of the Agreement. At a minimum, background investigations shall include a review/evaluation of the following: • identity verification, including Social Security Number search; • employment eligibility, including verification of U.S. citizenship or legal immigration status where appropriate; • criminal history/court records (Federal, State and local for the past five years); • work experience/history for the past five years; • pertinent skills, qualifications, and education/professional credentials; and • references. The Contractor must obtain the consent of its Staff to allow OSC, upon request: (i) to review the background investigation records, including all supporting documentation, and (ii) to conduct its own background investigation. Only Staff who have passed the background investigation, and provided such consent shall be assigned to provide Services to OSC under this Agreement. During the term of the Agreement, and in accordance with Appendix A (Section 10, Records), the Contractor must maintain records related to the background investigations performed.

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