Site Sections Sample Clauses

Site Sections. Include as needed to explain changes in levels within the proposed building as related to the site.
AutoNDA by SimpleDocs

Related to Site Sections

  • Typical Sections The Engineer shall prepare typical sections for all proposed and existing roadways and structures. Typical sections must include width of travel lanes, shoulders, outer separations, border widths, curb offsets, managed lanes, and ROW. The typical section must also include Proposed Profile Gradeline (PGL), centerline, pavement design, longitudinal joints, side slopes, sodding or seeding limits, concrete traffic barriers and sidewalks, if required, station limits, common proposed and existing structures including retaining walls, existing pavement removal, riprap, limits of embankment and excavation, etc.

  • The following sections of Section 4 OGS Centralized Contract Terms and Conditions have been renumbered as depicted in the following chart: Current Amended Section Title 4.25 4.26 Severability 4.26 4.27 Entire Agreement

  • RELATED SECTIONS Not Used

  • Contractor’s General Responsibilities The Contractor, regardless of any delegation or subcontract entered by the Contractor, shall be responsible for the following when providing information technology staff augmentation services:

  • GEOGRAPHIC AREA AND SECTOR SPECIFIC ALLOWANCES, CONDITIONS AND EXCEPTIONS The following allowances and conditions shall apply where relevant: Where the company does work which falls under the following headings, the company agrees to pay and observe the relevant respective conditions and/or exceptions set out below in each case.

  • Reciprocal Compensation Arrangements Pursuant to Section 251(b (5) of the Act

  • Title of Parts and Sections Any titles of the sections or subsections of this Agreement are inserted for convenience of reference only and are to be disregarded in interpreting any part of the Agreement's provisions.

  • Pursuant to Section 2.1 of this Agreement, the Seller conveyed to the Trust all of the Seller’s right, title and interest in its rights and benefits, but none of its obligations or burdens, under the Purchase Agreement including the Seller’s rights under the Purchase Agreement and the delivery requirements, representations and warranties and the cure or repurchase obligations of AmeriCredit thereunder. The Seller hereby represents and warrants to the Trust that such assignment is valid, enforceable and effective to permit the Trust to enforce such obligations of AmeriCredit under the Purchase Agreement. Any purchase by AmeriCredit pursuant to the Purchase Agreement shall be deemed a purchase by the Seller pursuant to this Section 3.2 and the definition of Purchased Receivable.

  • Accessibility of Web-Based Information and Applications For State Agency Authorized User Acquisitions: Any web-based information and applications development, or programming delivered pursuant to the contract or procurement, will comply with New York State Enterprise IT Policy NYS-P08-005, Accessibility of Web-Based Information and Applications as follows: Any web-based information and applications development, or programming delivered pursuant to the contract or procurement, will comply with New York State Enterprise IT Policy NYS-P08- 005, Accessibility of Web-Based Information and Applications as such policy may be amended, modified or superseded, which requires that state agency web-based information and applications are accessible to persons with disabilities. Web-based information and applications must conform to New York State Enterprise IT Policy NYS-P08-005 as determined by quality assurance testing. Such quality assurance testing will be conducted by the State Agency Authorized User and the results of such testing must be satisfactory to the Authorized User before web-based information and applications will be considered a qualified deliverable under the contract or procurement.

  • Coordination of Definitions with U.S. Treasury Regulations Notwithstanding Article 1 of this Agreement and the definitions provided in the Annexes to this Agreement, in implementing this Agreement, [FATCA Partner] may use, and may permit [FATCA Partner] Financial Institutions to use, a definition in relevant U.S. Treasury Regulations in lieu of a corresponding definition in this Agreement, provided that such application would not frustrate the purposes of this Agreement.

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