Security and Deferred Improvement Agreement Form Required Before Permits Issued Sample Clauses

Security and Deferred Improvement Agreement Form Required Before Permits Issued. Except as otherwise specifically provided under the “Build and Dedicate” Option (15.18.020.A), no city permits, including building permits, shall be issued for a project unless and until the applicable Security and Deferred Improvement Agreement has been properly executed and filed with the City (Ord. 1744 § 37, 2018).
AutoNDA by SimpleDocs

Related to Security and Deferred Improvement Agreement Form Required Before Permits Issued

  • Performance Improvement Plan timely and accurate completion of key actions due within the reporting period 100 percent The Supplier will design and develop an improvement plan and agree milestones and deliverables with the Authority

  • Educator Plans: Improvement Plan A) An Improvement Plan is for those Educators with PTS whose overall rating is unsatisfactory.

  • School Improvement Plans The School shall develop and implement a School Improvement Plan as required by section 1002.33(9)(n), Florida Statutes and applicable State Board of Education Rules or applicable federal law.

  • School Improvement Plan As permitted under IC § 20-10.2-3-1.5, the Charter shall serve as the Charter School's strategic and continuous school improvement and achievement plan (hereafter, the "School Improvement Plan"). To the extent that IC § 20-10.2 applies to the Charter in its function as the School Improvement Plan, the Organizer shall comply with the requirements under IC § 20-10.2.

  • TIPS Sales and Supplemental Agreements If awarded, when making a sale under this awarded contract, the terms of the specific TIPS order, including but not limited to: shipping, freight, insurance, delivery, fees, bonding, cost, delivery expectations and location, returns, refunds, terms, conditions, cancellations, defects, order assistance, etc., shall be controlled by the purchase agreement (Purchase Order, Contract, AIA Contract, Invoice, etc.) (“Supplemental Agreement” as used herein) entered into between the TIPS Member Customer and Vendor only. TIPS is not a party to any Supplemental Agreement. All Supplemental Agreements shall include Vendor’s Name, as known to TIPS, and TIPS Contract Name and Number. Vendor accepts and understands that TIPS is not a legal party to TIPS Sales and Vendor is solely responsible for identifying fraud, mistakes, unacceptable terms, or misrepresentations for the specific order prior to accepting. Vendor agrees that any order issued from a customer to Vendor, even when processed through TIPS, constitutes a legal contract between the customer and Vendor only. When Vendor accepts or fulfills an order, even when processed through TIPS, Vendor is representing that Vendor has carefully reviewed the order for legality, authenticity, and accuracy and TIPS shall not be liable or responsible for the same. In the event of a conflict between the terms of this TIPS Vendor Agreement and those contained in any Supplemental Agreement, the provisions set forth herein shall control unless otherwise agreed to and authorized by the Parties in writing within the Supplemental Agreement. The Supplemental Agreement shall dictate the scope of services, the project delivery expectations, the scheduling of projects and milestones, the support requirements, and all other terms applicable to the specific sale(s) between the Vendor and the TIPS Member.

  • 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.

  • Performance Improvement Xxxxxx Permanente and the Coalition are competing in a challenging market that is characterized by a limited workforce, changes in technology, changes in clinical practice, cultural diversity, changing demographics and high demand for quality service. The parties are committed to the enhancement of organizational performance so that working in Partnership is the way Xxxxxx Permanente does business. Under this Agreement, the parties will work together to: » develop and invest in people, including the development of and investment in managers, supervisors and union stewards; » engage employees at all levels; » align the systems and processes that support the achievement of organizational and Partnership goals; » enhance the ability of Coalition unions to advance their social mission and the welfare of their members; » recognize and reduce parallel structures; » ensure joint management-union accountability for performance; » grow membership; » redesign work processes to improve effectiveness, efficiency and work environment; » develop and xxxxxx unit-based teams; » share and establish expectations regarding broad adoption of successful practices in areas such as service, attendance, workplace safety, workforce development, cost structure reduction, scope of practice and performance-based pay; and » communicate with employees on an ongoing basis regarding performance goals and targets, as well as performance results at all levels of the organization. Each regional LMP council shall develop approaches aimed at reducing variation between medical centers, facilities and departments in the resources available for partnership. In particular, such a plan should: » ensure at a regional level there is adequate time for teams to review performance, identify opportunities for improvement, and develop and test changes to drive improvement; and » provide regional or facility support to departments as needed to cross-cover or backfill and jointly determine the most cost-effective manner to provide the support.

  • Notice to Proceed - Site Improvements The Recipient shall not commence, or cause to be commenced, any site improvements or other work on the Land until the Director has issued a Notice to Proceed to the Recipient. Such Notice to Proceed will not be issued until the Director is assured that the Recipient has complied with all requirements for the approval of a grant under Revised Code Sections 164.20 through 164.27 and has completed any land acquisition required by the Project. A Notice to Proceed shall be required for all Project prime contractors or direct procurement initiated by the Recipient following execution of this Agreement.

  • Post-Commercial Operation Date Testing and Modifications Each Party shall at its own expense perform routine inspection and testing of its facilities and equipment in accordance with Good Utility Practice as may be necessary to ensure the continued interconnection of the Large Generating Facility with the Participating TO’s Transmission System in a safe and reliable manner. Each Party shall have the right, upon advance written notice, to require reasonable additional testing of the other Party’s facilities, at the requesting Party’s expense, as may be in accordance with Good Utility Practice.

  • Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.

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