Stormwater management structures Sample Clauses

Stormwater management structures. Stormwater management structures, including but not limited to ponds, basins, and vaults, shall be located outside of shoreline jurisdiction where possible, as far from the ordinary high water mark as feasible, and shall minimize disturbance of vegetation conservation buffers.
AutoNDA by SimpleDocs
Stormwater management structures. (1) The Developer shall install all storm water management facilities for the Property including related storm water sewers required by Municipal Ordinance and the plans and specifications approved by the Municipal Engineer as set forth in Exhibit D. Developer and Municipality agree to comply by the terms of the Stormwater Maintenance Agreement attached hereto as Exhibit D. (2) Where standards and/or specifications have not been established by the Municipality, all work shall be made in accordance with established engineering practices as designated and approved by the Municipal Engineer. (3) Developer and Municipality acknowledge that a regional stormwater facility (“Regional Facility”) has been constructed on Outlot 1 of CSM 5752 in order to adequately manage the stormwater from the Property and other surrounding properties. Developer shall take all steps necessary to tie in the stormwater management facilities for the Development to the regional facility located on Outlot 1.

Related to Stormwater management structures

  • Management Structure Describe the overall management approach toward planning and implementing the contract. Include an organization chart for the management of the contract, if awarded.

  • Stormwater Notwithstanding any other provisions or terms of this Agreement, Company acknowledges that certain properties within the Premises or on Authority-owned land are subject to stormwater rules and regulations. Company agrees to observe and abide by such stormwater rules and regulations as may be applicable to the Premises, and, if applicable, Company hereby expressly covenants, warrants, and represents to Authority, in connection with Company’s operations on the Premises, the following: A. Company is required to submit a Notice of Intent to use the State of Florida Multi-Sector Generic Permit for Stormwater Discharge Associated with Industrial Activity. Authority and Company both acknowledge that close cooperation is necessary to ensure compliance with any stormwater discharge permit terms and conditions, as well as to ensure safety and to minimize the cost of compliance. Company acknowledges further that it may be necessary to undertake actions to minimize the exposure of stormwater to “significant materials” (as such term may be defined by applicable stormwater rules and regulations) generated, stored, handled, or otherwise used by Company by implementing and maintaining “best management practices” (BMPs) (as such term may be defined in applicable stormwater rules and regulations). Company will establish a BMP plan for the Premises and submit a copy to Authority. B. Company will be knowledgeable of any stormwater discharge permit requirements applicable to Company and with which Company will be obligated to comply. The submittal of a Notice of Intent will be made by Company to the FDEP, and a copy will be submitted to Authority. Company is required to comply with the following requirements including, but not limited to, certification of non-stormwater discharges; collection of stormwater samples; preparation of a Stormwater Pollution Prevention Plan or similar plans; implementation of BMPs; and maintenance and submittal of necessary records. In complying with such requirements, Company will observe applicable deadlines set by the regulatory agency that has jurisdiction over the permit. Company agrees to undertake, at its sole expense, those stormwater permit requirements for which it has received written notice from the regulatory agency and that apply to the Premises, and Company agrees that it will hold harmless and indemnify Authority for any violations or non-compliance with any such permit requirements.

  • Infrastructure Infrastructure serves as the foundation and building blocks of an integrated IT solution. It is the hardware which supports Application Services (C.3.2) and IT Management Services (C.3.3); the software and services which enable that hardware to function; and the hardware, software, and services which allow for secure communication and interoperability between all business and application service components. Infrastructure services facilitate the development and maintenance of critical IT infrastructures required to support Federal government business operations. This section includes the technical framework components that make up integrated IT solutions. One or any combination of these components may be used to deliver IT solutions intended to perform a wide array of functions which allow agencies to deliver services to their customers (or users), whether internal or external, in an efficient and effective manner. Infrastructure includes hardware, software, licensing, technical support, and warranty services from third party sources, as well as technological refreshment and enhancements for that hardware and software. This section is aligned with the FEA/DoDEA Technical Reference Model (TRM) which describes these components using a vocabulary that is common throughout the entire Federal government. A detailed review of the TRM is provided in Section J, Attachment 5. Infrastructure includes complete life cycle support for all hardware, software, and services represented above, including planning, analysis, research and development, design, development, integration and testing, implementation, operations and maintenance, information assurance, and final disposition of these components. The services also include administration and help desk functions necessary to support the IT infrastructure (e.g., desktop support, network administration). Infrastructure components of an integrated IT solution can be categorized as follows:

  • Transportation Management Tenant shall fully comply with all present or future programs intended to manage parking, transportation or traffic in and around the Building, and in connection therewith, Tenant shall take responsible action for the transportation planning and management of all employees located at the Premises by working directly with Landlord, any governmental transportation management organization or any other transportation-related committees or entities.

  • Traffic Management 9.2.1 During the Operating Period, Developer shall be responsible for the general management of traffic on the Project. Developer shall manage traffic so as to preserve and protect safety of traffic on the Project and Related Transportation Facilities and, to the maximum extent practicable, to avoid disruption, interruption or other adverse effects on traffic flow, throughput or level of service on the Project and Related Transportation Facilities. Developer shall conduct traffic management in accordance with all applicable Technical Provisions, Technical Documents, Laws and Governmental Approvals, and in accordance with the Traffic Management Plan. 9.2.2 Developer shall prepare and submit to TxDOT and the Independent Engineer for TxDOT approval a Traffic Management Plan for managing traffic on the Project and Related Transportation Facilities after the commencement of traffic operations on any portion of the Project, addressing (a) orderly and safe movement and diversion of traffic on Related Transportation Facilities during Project construction, (b) orderly and safe movement of traffic on the Project and (c) orderly and safe diversion of traffic on the Project and Related Transportation Facilities necessary in connection with field maintenance and repair work or Renewal Work or in response to Incidents, Emergencies and lane closures. Developer shall prepare the Traffic Management Plan according to the schedule set forth in the Technical Provisions. The Traffic Management Plan shall comply with the Technical Provisions and Technical Documents concerning traffic management and traffic operations. Developer shall carry out all traffic management during the Term in accordance with the approved Traffic Management Plan. 9.2.3 Developer shall implement the Traffic Management Plan to promote safe and efficient operation of the Project and Related Transportation Facilities at all times during the course of any construction or operation of the Project and during the Utility Adjustment Work. 9.2.4 TxDOT shall have at all times, without obligation or liability to Developer, the right 9.2.4.1 Issue Directive Letters to Developer regarding traffic management 9.2.4.2 Provide on the Project, via message signs or other means consistent with Good Industry Practice, non-Discriminatory traveler and driver information, and other public information (e.g. amber alerts), provided that the means to disseminate such information does not materially interfere with the functioning of the ETCS.

  • Drainage Systems (1) Clear culvert inlets, outlets, and sediment catching basins. (2) Maintain waterbars, drainage dips, and other water diversion measures. (3) During active use, patrol and maintain functional drainage. (4) Repair damaged culvert ends.

  • Irrigation An irrigation reduced pressure zone (hereinafter referred to as “RPZ”) is required for any irrigation systems and must be installed by the Developer and/or eventual lot owner and tested in accordance with the Minnesota Department of Health Guidelines for Designing Backflow Prevention Assembly Installations (hereinafter referred to as “Guidelines”). The initial test results and certification shall be submitted to the City of Maple Grove Public Works Department. Subsequently, the RPZ must be tested, per the Guidelines, at least annually by a certified tester with the results reported to the City of Maple Grove Building Department and the RPZ must be rebuilt as needed in accordance with the Guidelines. Test/rebuilt reports shall be mailed or faxed to the City of Maple Grove Building Department at (000) 000-0000. The irrigation system shall be designed, and the Plans shall be modified accordingly, prior to the issuance of any permits for the development of the Property, to accommodate a 1-inch water meter and a maximum flow of 50 gallons per minute.

  • Dewatering (a) Where the whole of a site is so affected by surface water following a period of rain that all productive work is suspended by agreement of the Parties, then dewatering shall proceed as above with Employees so engaged being paid at penalty rates as is the case for safety rectification work. This work is typically performed by Employees engaged within CW1, CW2 or CW3 classifications. When other Employees are undertaking productive work in an area or areas not so affected then dewatering will only attract single time rates. (b) Where a part of a site is affected by surface water following a period of rain, thus rendering some areas unsafe for productive work, consistent with the Employer’s obligations under the OH&S Act, appropriate Employees shall assist in the tidying up of their own work site or area if it is so affected. Where required, appropriate Employees will be provided with the appropriate PPE. Such work to be paid at single time rates. Productive work will continue in areas not so affected. (c) To avoid any confusion any ‘dewatering’ time which prevents an Employee from being engaged in their normal productive work is not included in any calculation for the purposes of determining whether an Employee is entitled to go home due to wet weather (refer clauses 32.4 and 32.5)

  • Master Feeder Structure If permitted by the 1940 Act, the Board of Trustees, by vote of a majority of the Trustees, and without a Shareholder vote, may cause the Trust or any one or more Series to convert to a master feeder structure (a structure in which a feeder fund invests all of its assets in a master fund, rather than making investments in securities directly) and thereby cause existing Series of the Trust to either become feeders in a master fund, or to become master funds in which other funds are feeders.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

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