Project Features Sample Clauses

Project Features. In addition to the Community Benefits, Developer has opted to provide the following additional Project Features as a Public Benefit:
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Project Features. The following elements shall be incorporated in the Project, in addition to the City’s standard development and permitting requirements:
Sample 1
Project Features. The Project features set forth in Paragraphs A through H, below, are intended to be an overview of Project work.VTA intends to seek FTA grant funding for some or all of these features and perform. They are not intended to constitute a comprehensive list of project features and obligations, but are described in this Agreement because they are of particular concern and have a direct impact to the City. A comprehensive list of project features associated with the Project is set forth in the FEIS. Party obligations for work that VTA does not intend to seek FTA grant funding (i.e., Project-Triggered Facility Work) is set forth in Section7 . VTA shall design and build the following:
Sample 1
Project Features. Select the checkbox next to every feature listed below that your project includes and that you intend to address in the current agreement. Standard language is provided in the template for these features. (See Article III Project Specific Features)
Sample 1
Project Features and have a direct impact to the City. A comprehensive list of project features Formatted: Font color: Black The Project features set forth in Paragraphs A through I, below, are not intended to constitute a comprehensive list of project features, but are described in this Agreement because they are of particular concern associated with the Project is set forth in the FEIS. Deleted: <#>Insert an appropriate list of features customized to identify the particular issues relevant to the city.¶
Sample 1
Project Features. The Project features set forth below are not intended to constitute a comprehensive list of Project features, but are described in this Agreement to provide a general description of the elements of the Project. A comprehensive list of Project features associated with the Project is set forth in the FEIR.
Sample 1
Project Features. Project Feature Description Demolition The following existing structures and equipment will be demolished: Influent lift station #2 and oxidation ditch. Coarse Screening Repurpose the existing lift station #1 to a new coarse screen structure (24 MGD total peak flow capacity) with two coarse screens, manual bypass channel, and dumpster building. New Influent Lift Station New lift station with dual wet well configuration and six submersible pumps (12 MGD firm peak flow capacity) expandable to an ultimate firm capacity of 18 MGD. Headworks Facility Expand the existing headworks facility with one additional fine screen (6 MGD), manual bypass screen, replacement of existing mechanical-vortex grit removal unit (12 MGD) including two grit pumps, grit dewatering unit, and new dumpster building. New Splitter Box One new splitter box to split flows from the headworks to the three new aeration basins. New Aeration Basins and Blowers Three new conventional activated sludge aeration basins designed for BOD and ammonia removal. New aeration basins sized to treat 3 MGD at design influent loadings. Basins will include selector zones. New blower building with four blowers (3 duty + 1 standby) for the new aeration basins. New Secondary Clarifiers Two new secondary clarifiers (6 MGD total peak flow capacity each). New RAS Pump Stations Two new return activated sludge (RAS) pump stations for pumping RAS from the new and existing clarifiers to the aeration basins. Each pump station will have 3 pumps (2 duty + 1 standby). New WAS Pump Station One new waste activated sludge (WAS) pump station for pumping WAS from the common RAS header to the rotary drum thickeners. The pump station will have 3 pumps (2 duty + 1 standby). New Scum Pump Station Two scum pumps in one new scum pit for the two new secondary clarifiers. Project Feature Description New Tertiary Filters Two new inside-out type tertiary disk filters for a total capacity of 12 MGD. New UV System Inclined type Ultraviolet (UV) Disinfection system for disinfection of filtered effluent. Three inclined UV modules in a single channel for a total capacity of 12 MGD. Xxxxxxxx Flume New Effluent Channel with Xxxxxxxx Flume measurement. New Mechanical Sludge Thickeners Replace existing mechanical sludge thickening system with two new rotary drum thickeners, flocculation tanks, and polymer feed system. New Aerobic Digesters Blowers Replace existing aerobic digester blowers with two (1 duty + 1 standby) new blowers with a new blower...
Sample 1
AutoNDA by SimpleDocs
Project Features. The PROJECT features set forth below, are not intended to constitute a comprehensive list of PROJECT features, but are certain features CITY would like VTA to consider, coordinate with CITY, and include in the design and construction of the PROJECT. A comprehensive list of project features associated with the PROJECT is set forth in the FEIS.
Sample 1

Related to Project Features

  • Contract Database Metadata Elements Title: Whitesville Central School District and Whitesville Central School Educational Support Staff Association (2003) Employer Name: Whitesville Central School District Union: Whitesville Central School Educational Support Staff Association Local: Effective Date: 07/01/2003 Expiration Date: 06/30/2006 PERB ID Number: 10699 Unit Size: Number of Pages: 23 For additional research information and assistance, please visit the Research page of the Catherwood website - xxxx://xxx.xxx.xxxxxxx.xxx/library/research/ For additional information on the ILR School - xxxx://xxx.xxx.xxxxxxx.xxx/ AGREEMENT BETWEEN WHITESVILLE CENTRAL SCHOOL EDUCATIONAL SUPPORT STAFF ASSOCIATION AND THE WHITESVILLE CENTRAL SCHOOL DISTRICT JULY 1, 2003 THROUGH JUNE 30, 2006 TABLE OF CONTENTS ARTICLE TITLE PAGE Preamble 1 I Recognition 1 II Collective Bargaining U n i t 1 III Dues/Agency Fee Ckoffand Payroll Deduction 1 IV Rights of Employees 2 V Rights of Employer ------------- 2 VI Personnel F i l e 2 VII Employee Definitions 3 VIII Permanent Status/Seniority 4 IX Wages 5 X Overtime 7 XI Vacation 7 XII Holidays 8 XIII Sick Leave and Leavesof A b s e n c e 8 XIV Conference, Workshops,Required Courses 10 XV Meal Allowance and M i l e a g e 11 XVI Retirement 11 XVII Insurance 12 XVIII Cafeteria P l a n 14 .XIX Uniform Allowance------------------ 14 XX Hours of W o r k 14 XXI Transfers/Promotions 15 XXII Job Descriptions 15 XXIII Grievance Procedure 15 XIV Copies of the Contract 18 XV Zipper C x x x x x 18 XXVI Legislative Clause 18 XXVII Duration 19 SIGNATURES 19 APPENDIX A Grievance F o r m 20 APPENDIX B Dues Authorization F o r m 21

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • For Product Development Projects and Project Demonstrations  Published documents, including date, title, and periodical name.  Estimated or actual energy and cost savings, and estimated statewide energy savings once market potential has been realized. Identify all assumptions used in the estimates.  Greenhouse gas and criteria emissions reductions.  Other non-energy benefits such as reliability, public safety, lower operational cost, environmental improvement, indoor environmental quality, and societal benefits.  Data on potential job creation, market potential, economic development, and increased state revenue as a result of the project.  A discussion of project product downloads from websites, and publications in technical journals.  A comparison of project expectations and performance. Discuss whether the goals and objectives of the Agreement have been met and what improvements are needed, if any.

  • LAYOUT OF WORK The Contractor shall lay out its Work from base lines and benchmarks indicated on the Drawings, and shall be responsible for verification of all measurements in connection with the layout. The Contractor shall furnish all stakes, templates, platforms, equipment, tools, materials, and labor required to lay out any part of the Work. The Contractor shall also be responsible for maintaining and preserving all stakes and other marks established by Princeton University until authorized to remove them. If such marks are destroyed by the Contractor or through its negligence before their removal is authorized, Princeton University may replace them and deduct the expense of the replacement from any amounts due or to become due to the Contractor. CLAUSE C15 NOISE

  • Developer Attachment Facilities Developer shall design, procure, construct, install, own and/or control the Developer Attachment Facilities described in Appendix A hereto, at its sole expense.

  • Technical Specification As enumerated in Special Conditions of Contract/Scope of Work/attached Drawing/ Details/Schedule of Rates.

  • Solicitations for Subcontractors, Including Procurements of Materials and Equipment In all solicitations either by competitive bidding or negotiation made by the contractor for work to be performed under a subcontract, including procurements of materials or leases of equipment, each potential subcontractor or supplier shall be notified by the contractor of the contractor's obligations under this contract and the Regulations relative to nondiscrimination on the grounds of race, color, or national origin, sex, age, and disability/handicap.

  • System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the NYISO OATT.

  • Project Plans The Contractor: must carry out the Contractor's Activities in accordance with, and otherwise implement, the Project Plans; and for the purposes of subparagraph (i), must: prepare Project Plans based, where applicable, on the draft Project Plans lodged by the Contractor in its tender for the Contractor's Activities, and otherwise in accordance with the requirements of the Contract and submit them to the Contract Administrator so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event no later than the number of days specified in the Contract Particulars after the Award Date for each Project Plan; not commence any of the Contractor's Activities to which any Project Plan applies, unless the Contract Administrator has had the number of days specified in the Contract Particulars for each Project Plan to review the Project Plan and has not rejected the Project Plan; if any Project Plan is rejected, submit an amended Project Plan to the Contract Administrator; in any event, finalise each Project Plan so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event in accordance with the requirements of the Contract to the satisfaction of the Contract Administrator; after each Project Plan has been finalised: regularly review, update and amend each Project Plan in accordance with the process set out in each Project Plan (and otherwise at least on each anniversary of the Award Date); update or amend a Project Plan on request of the Contract Administrator; and continue to correct any defects in or omissions from a Project Plan (whether identified by the Contract Administrator or the Contractor), and submit an updated or amended Project Plan to the Contract Administrator, after which: the Contractor must continue to comply with the requirements of the then current Project Plan until the process in subparagraph (ii) has been completed in respect of the updated or amended Project Plan; and subsubparagraphs B - E will apply (to the extent applicable); and document and maintain detailed records of all: reviews, updates, amendments and submissions of each Project Plan; audits or other monitoring of each Project Plan; and training and awareness programs and communications provided to Contractor and subcontractor personnel in respect of each Project Plan (including each updated or amended Project Plan). The Contractor will not be relieved from compliance with any of its obligations under the Contract or otherwise at law or in equity as a result of: the implementation of, and compliance with, the requirements of any Project Plan; any direction by the Contract Administrator concerning a Project Plan or the Contractor's compliance or non-compliance with a Project Plan; any audit or other monitoring by the Contract Administrator or anyone else acting on behalf of the Commonwealth of the Contractor's compliance with a Project Plan; or any failure by the Contract Administrator, or anyone else acting on behalf of the Commonwealth, to detect any defect in or omission from a Project Plan including where any such failure arises from any negligence on the part of the Contract Administrator or other person.

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