Contents of Draft Plan. The Staff shall prepare a Draft Plan based upon the ColumbiaGrid planning process that contains:
Contents of Draft Plan Sample Clauses
Related to Contents of Draft Plan
Contents of Personnel File A. Adverse statements prepared by the County shall not be included in an employee's official personnel file unless a copy is provided to the employee.
DISTRIBUTION OF CONTRACTOR PRICE LIST AND CONTRACT APPENDICES Contractor shall provide Authorized Users with electronic copies of the Contract, including price lists and Appendices, upon request. OGS CENTRALIZED CONTRACT MODIFICATIONS Contract Updates will be handled as provided in Appendix C – Contract Modification Procedures.
Application Procedures a) An employee applies for a listing on the system-wide registry through the employee’s Human Resources Department by completing the form in Appendix B.
MUTUAL AGREEMENT PROCEDURES 1. Where difficulties or doubts arise between the Parties regarding the implementation or interpretation of this Agreement, the respective competent authorities shall use their best efforts to resolve the matter by mutual agreement.
Flexible Work Schedules (a) Academic Professional staff members throughout the University may have, as indicated below, flexible work schedules. For example, Academic Professionals often travel on University business and/or work evenings and weekends. A flexible work schedule is defined as having established working hours different from the standard 8:00 a.m. to 5:00 p.m. Monday through Friday schedule, to be followed by an employee for an agreed upon period of time.
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).
Amendment Procedures Amendments to this Agreement may be proposed only by the General Partner. To the fullest extent permitted by law, the General Partner shall have no duty or obligation to propose or approve any amendment to this Agreement and may decline to do so free of any duty or obligation whatsoever to the Partnership, any Limited Partner or any other Person bound by this Agreement, and, in declining to propose or approve an amendment to this Agreement, to the fullest extent permitted by law shall not be required to act in good faith or pursuant to any other standard imposed by this Agreement, any Group Member Agreement, any other agreement contemplated hereby or under the Delaware Act or any other law, rule or regulation or at equity, and the General Partner in determining whether to propose or approve any amendment to this Agreement shall be permitted to do so in its sole and absolute discretion. An amendment to this Agreement shall be effective upon its approval by the General Partner and, except as otherwise provided by Section 13.1 or Section 13.3, the holders of a Unit Majority, unless a greater or different percentage of Outstanding Units is required under this Agreement. Each proposed amendment that requires the approval of the holders of a specified percentage of Outstanding Units shall be set forth in a writing that contains the text of the proposed amendment. If such an amendment is proposed, the General Partner shall seek the written approval of the requisite percentage of Outstanding Units or call a meeting of the Unitholders to consider and vote on such proposed amendment. The General Partner shall notify all Record Holders upon final adoption of any amendments. The General Partner shall be deemed to have notified all Record Holders as required by this Section 13.2 if it has posted or made accessible such amendment through the Partnership’s or the Commission’s website.
Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.
Application Form By electronically signing or submitting the Application Form you:
Induction Procedures a) The parties to this Agreement acknowledge that it is in the interests of the industry that all new employees and employers on a building project understand their obligations to this Agreement and are introduced to their jobs in a manner which will help them work safely and efficiently.
