Project Co Parties Sample Clauses

Project Co Parties. (a) Project Co shall not be relieved of any liability or obligation under this Project Agreement by the appointment of any Project Co Party, and Project Co shall cause each Project Co Party, to the extent such Project Co Party performs or is specified hereunder to perform the Project Operations, to comply with the obligations of Project Co hereunder in the same manner and to the same extent as Project Co.
AutoNDA by SimpleDocs
Project Co Parties. 6.2 Subject to the provision of Clause 30.1.7, Project Co shall not be relieved or excused of any responsibility, liability or obligation under this Agreement by the appointment of any Project Co Party. Project Co shall, as between itself and the Authority, be responsible for the selection, pricing, performance, acts, defaults, omissions, breaches and negligence of all Project Co Parties. All references in this Agreement to any act, default, omission, breach or negligence of Project Co shall be construed accordingly to include any such act, default, omission, breach or negligence of a Project Co Party.
Project Co Parties. Project Co shall not be relieved of any liability or obligation under this Agreement by the appointment of any Project Co Party, and Project Co shall cause each Project Co Party, to the extent such Project Co Party performs, or is specified hereunder to perform, any part of the Project Operations, to comply with the obligations of Project Co to HMQ in the same manner and to the same extent as Project Co. Project Co shall include terms in all Subcontracts requiring such compliance or incorporating the terms hereof insofar as it is relevant to the scope of the Subcontract in question and Project Co shall require Subcontractors to include such terms in other Subcontracts to which those Subcontractors are party and Project Co shall enforce and require the enforcement of all such terms.
Project Co Parties. 31 9.4 Project Co Permits, Licences and Approvals ................................................................ 31
Project Co Parties. Project Co will, as between itself and PUC, be responsible for, and not relieved of or excused from its obligations hereunder by, the acts, omissions, breaches, defaults, non-compliance, negligence and wilful misconduct of each Project Co Person and all references in this Agreement to any act, omission, breach, default, non-compliance, negligence or wilful misconduct of Project Co will be construed accordingly to include any such act, omission, breach, default, non-compliance, negligence or wilful misconduct committed by a Project Co Person.

Related to Project Co Parties

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

  • Sub-projects 1. The Participating Bank shall make Sub-loans to Beneficiaries and appraise, review, approve, and supervise Sub-projects in accordance with the criteria, conditions and procedures set forth in the Operations Manual, including, inter alia, the following eligibility criteria:

  • In-Scope Projects Project Based Information Technology (IT) Consulting Services required by an Authorized User must be obtained via a Mini-Bid process under this Contract. The Authorized User shall issue a Mini-Bid with a SOW for the required Project Based IT Consulting Services. A Mini-Bid may include, but will not be limited to, projects requiring: analysis, data classification, design, development, testing, quality assurance, security and associated customized training for IT based applications. Additional examples of in-scope projects include, but are not limited to:  Technical architecture advisory services;  Business analysis for project development;  Proprietary software application development/customization, programming and integration;  Data information management (including data migration, data conversion, data manipulation, data integration);  Project management project support services - including, but not limited to; project management, project quality assurance and control, and Independent Verification & Validation (IV&V);  Disaster recovery/business continuity and testing;  Quality assurance;  Continuity of operations planning (COOP);  Data categorization; and  Open-source software implementation. Out-of-Scope Work There are service offerings expressly excluded from the scope of these contracts. In many instances, such services and/or offerings are (or will be) covered by another OGS Centralized Contract. Examples include:  Staff augmentation services;  Time and material services;  Web hosting;  Automated network monitoring or any other service provided principally through an automated process;  Hardware maintenance and support;  Software maintenance and support;  Ongoing maintenance and support;  Services priced on a per asset basis;  Services priced on a contingency basis;  Equipment maintenance;  Prepackaged training courses;  E-Learning;  Managed services;  Acquisition of equipment (hardware)  Acquisition of software, either Commercial off-the-shelf (COTS) software or pre-existing software;  Acquisition of non-consulting services, such as network provisioning, voice services (local, long- distance), or video bridging;  Cloud based or “As a Service” offerings, including but not limited to SaaS, IaaS, PaaS, and XaaS;  Any offering that is a combination of equipment, hardware, software, cloud or “as a service offerings”; and  Consulting or other installation work which is considered Public Works is excluded from purchase under the scope of this Contract. Historically, the New York State Bureau of Public Works has maintained that installation, maintenance and repair of equipment attached to any wall, ceiling or floor or affixed by hard wiring or plumbing is public work. In contrast, installation of a piece of equipment which is portable or a “plug-in” free-standing unit would not be considered public work. Thus, this Contract does not authorize installation where the equipment becomes a permanent part of the building structure, or is otherwise incorporated into the fabric of the building (i.e. installation on a wall, ceiling or floor in a fixed location, or affixed by hard- wiring or plumbing). See Appendix A, Clause 6, Wage and Hours Provisions. For questions about whether a proposed work constitutes public work, please contact the New York State Department of Labor’s Bureau of Public Work District Office in a specific area. A listing of district offices and contact information is available at xxxx://xxx.xxxxx.xx.xxx/workerprotection/publicwork/PWContactUs.shtm. Definitions Additional definitions applicable to this Contract can be found in Appendix B. Term Definition Authorized User Agreement The document resulting from the transactional Mini-Bid process, which sets forth the specifics regarding the services to be provided by the Contractor to the Authorized User, under the Project Based Information Technology Consulting Contract. Best Value The basis for awarding all service and technology contracts to the offerer that optimizes quality, cost and efficiency, among responsive and responsible offerers. Such basis shall be, wherever possible, quantifiable (State Finance Law §163 (1) (j)). Billing Contact The name, phone number, e-mail, and billing address a customer uses on a xxxx for contact information. Consultant Disclosure Legislation Chapter 10 of the Laws of 2006 amends State Finance Law § 8 and § 163 by requiring: that the Office of the State Comptroller (OSC) include in the Consulting Services Report it compiles annually on contracts issued by state agencies for consulting services during the previous fiscal year. xxxx://xxx.xxx.xxxxx.xx.xx/agencies/guide/MyWebHelp/Content/XI/18/C.htm Deliverables All services or products created during the performance or provision of Services hereunder or identified as a “Deliverable” in an applicable Mini-Bid. A Deliverable is a building block of an overall project. For the purposes of this Solicitation and the resulting Contract, a deliverable shall not be set forth as a status report, meeting attendance, a block of staff hours, or an invoice submission. Fixed Price Authorized User Agreement An agreement pursuant to the Centralized Contract that provides for a fix cost for a defined project. Government Contract A contract let by a Federal, State, or Local governmental body within the continental United States. Government Entity An entity at the federal, state, county, city or provincial level. Joint Venture A contractual agreement joining together two or more business enterprises for the purpose of performing on a State Contract. Knowledge Transfer The transfer of knowledge from the Contractor to the Authorized User. Knowledge Transfer can include full written system documentation including all system changes, training classes, manuals and other items. Depending on the scope of the transaction, there may or may not be a deliverable cost associated. All materials will be the property of the Authorized User unless specifically negotiated during the award process. May Denotes the permissive in a contract clause or specification. Refers to items or information that the State has deemed are worthy of obtaining, but not required or obligatory. Also see “Should”. Mini-Bid A type of Bid Document used by the Authorized User to obtain Services under the Project Based IT Consulting Services Contracts. Not To Exceed Rates (NTE) Refers to the New York State contract price set forth in Appendix D. Amounts proposed by the Contractor at the transactional level shall not exceed the hourly rates provided under this Contract (which will be defined values in US Dollars). Prime Contractor For the purposes of Technical qualifications, the business entity with whom a government entity directly has a contract. Project Based IT Consulting Services An OGS Centralized Contract which will provide a set of standardized terms and conditions, guidelines, processes, and templates for the development, distribution and award of specific deliverable-based and fixed-price Information Technology projects. Project Plan A formal, approved document used to guide both project execution and project control. The primary uses of the project plan are to document planning assumptions and decisions, facilitate communication among stakeholders, and document approved scope, cost, and schedule baselines. Retainage A portion of the Authorized User and Contractor fixed-price agreement amount that is held back by the Authorized User until the deliverable or project is satisfactorily finished. Should Denotes the permissive in a contract clause or specification. Refers to items or information that the State has deemed are worthy of obtaining, but not required or obligatory. Also see “May”. Term Definition Solicitation A non-competitive periodic recruitment solicitation (“Solicitation”) for vendors that provide Project Based Information Technology Consulting Services. Vendor An enterprise that sells goods or services. Vendor Submission The complete response to this Solicitation submitted by a Vendor to provide, as applicable , the Product and services described in the Solicitation

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

  • Project acronym Use the project acronym as indicated in the submitted proposal. It cannot be changed, unless agreed during the negotiations. The same acronym should appear on each page of the grant agreement preparation documents to prevent errors during its handling.

  • Improvement Plans a. An improvement plan is a clearly articulated assistance program for a teacher/counselor/SLP whose overall summative rating is ineffective.

  • Research Project 3.1 These Materials and Data will be used by Recipient's PI solely in connection with the Research Project, as named and described in the attached research application (insert Research Project name below):

  • PROJECT 3.01. The Recipient declares its commitment to the objectives of the Project. To this end, the Recipient shall carry out the Project in accordance with the provisions of Article IV of the General Conditions.

  • Infrastructure Improvements The design, redevelopment and construction and completion of certain infrastructure improvements, including sewer, stormwater, electrical and water main improvements, along with other similar improvements.

  • Projects The Annexes attached hereto describe the specific projects and the policy reforms and other activities related thereto (each, a “Project”) that the Government will carry out, or cause to be carried out, in furtherance of this Compact to achieve the Objectives and the Compact Goal.

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