Proposed Retrofit Projects Sample Clauses

Proposed Retrofit Projects. The Recipient shall submit to the Province a Project Information Form for each Retrofit Project that it would like funded. The Recipient shall update the Project Information Form in accordance with the Program Guidelines, in the event of a project milestone being achieved and/or in the event of any proposed change.
AutoNDA by SimpleDocs

Related to Proposed Retrofit Projects

  • Proposed Services A description of the Contractor’s proposed services to accomplish the specified work requirements, including dates of completion.

  • 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

  • Annual Work Plans and Budgets The Recipient shall furnish to the Association as soon as available, but in any case not later than September 1 of each year, the annual work plan and budget for the Project for each subsequent year of Project implementation, of such scope and detail as the Association shall have reasonably requested, except for the annual work plan and budget for the Project for the first year of Project implementation, which shall be furnished no later than one (1) month after the Effective Date.

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

  • Building Commissioning Services The Owner may provide as a part of its testing services the Building Commissioning services involving the project’s HVAC and exhaust systems, temperature control systems, fire detection and alarm systems, emergency power and lighting system, fire suppression system, security locks and security locking control systems, food service equipment (if applicable), and laundry equipment (if applicable). In the event the Using Agency’s Program specifies additional commissioning services, the Owner shall procure such services as well. The Owner, through its Executive Administrator, may engage an independent Commissioning Authority. It is the intent of this Article that the Commissioning Authority enforce the requirements mentioned herein and certify that the systems and equipment listed all function properly prior to the initiation of each final inspection.

  • Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least thirty (30) days written notice to the SLDC and GUVNL, of the date on which it intends to synchronize the Power Project to the Grid System.

  • Synchronisation Commissioning and Commercial Operation 8.1 The Developer shall provide at least forty (40) days advanced preliminary written notice and at least twenty (20) days advanced final written notice to ESCOM of the date on which it intends to synchronize the Power Project to the Grid System.

  • Annual Work Plan and Budget 1. The Recipient shall, not later than November 30th of each year, prepare and furnish to the Association an annual work plan and budget (“Annual Work Plan and Budget”) for the Project for the subsequent year, said Annual Work Plan and Budget of such scope and detail as the Association shall have reasonably requested.

  • PROPOSED MOBILITY PROGRAMME The proposed mobility programme includes the indicative start and end months of the agreed study programme that the student will carry out abroad. The Learning Agreement must include all the educational components to be carried out by the student at the receiving institution (in table A) and it must contain as well the group of educational components that will be replaced in his/her degree by the sending institution (in table B) upon successful completion of the study programme abroad. Additional rows can be added as needed to tables A and B. Additional columns can also be added, for example, to specify the study cycle-level of the educational component. The presentation of this document may also be adapted by the institutions according to their specific needs. However, in every case, the two tables A and B must be kept separated, i.e. they cannot be merged. The objective is to make clear that there needs to be no one to one correspondence between the courses followed abroad and the ones replaced at the sending institutions. The aim is rather that a group of learning outcomes achieved abroad replaces a group of learning outcomes at the sending institution, without having a one to one correspondence between particular modules or courses. A normal academic year of full-time study is normally made up of educational components totalling 60 ECTS* credits. It is recommended that for mobility periods shorter than a full academic year, the educational components selected should equate to a roughly proportionate number of credits. In case the student follows additional educational components beyond those required for his/her degree programme, these additional credits must also be listed in the study programme outlined in table A. When mobility windows are embedded in the curriculum, it will be enough to fill in table B with a single line as described below: Component code (if any) Component title (as indicated in the course catalogue) at the sending institution Semester [autumn / spring] [or term] Number of ECTS* credits Mobility window … Total: 30 Otherwise, the group of components will be included in Table B as follows: Component code (if any) Component title (as indicated in the course catalogue) at the sending institution Semester [autumn / spring] [or term] Number of ECTS* credits Course x … 10 Module y … 10 Laboratory work … 10 Total: 30 The sending institution must fully recognise the number of ECTS* credits contained in table A if there are no changes to the study programme abroad and the student successfully completes it. Any exception to this rule should be clearly stated in an annex of the Learning Agreement and agreed by all parties. Example of justification for non-recognition: the student has already accumulated the number of credits required for his/her degree and does not need some of the credits gained abroad. Since the recognition will be granted to a group of components and it does not need to be based on a one to one correspondence between single educational components, the sending institution must foresee which provisions will apply if the student does not successfully complete some of the educational components from his study programme abroad. A web link towards these provisions should be provided in the Learning Agreement. The student will commit to reach a certain level of language competence in the main language of instruction by the start of the study period. The level of the student will be assessed after his/her selection with the Erasmus+ online assessment tool when available (the results will be sent to the sending institution) or else by any other mean to be decided by the sending institution. A recommended level has been agreed between the sending and receiving institutions in the inter-institutional agreement. In case the student would not already have this level when he/she signs the Learning Agreement, he/she commits to reach it with the support to be provided by the sending or receiving institution (either with courses that can be funded by the organisational support grant or with the Erasmus+ online tutored courses). All parties must sign the document; however, it is not compulsory to circulate papers with original signatures, scanned copies of signatures or digital signatures may be accepted, depending on the national legislation. * In countries where the "ECTS" system it is not in place, in particular for institutions located in partner countries not participating in the Bologna process, "ECTS" needs to be replaced in all tables by the name of the equivalent system that is used and a weblink to an explanation to the system should be added. CHANGES TO THE ORIGINAL LEARNING AGREEMENT The section to be completed during the mobility is needed only if changes have to be introduced into the original Learning Agreement. In that case, the section to be completed before the mobility should be kept unchanged and changes should be described in this section. Changes to the mobility study programme should be exceptional, as the three parties have already agreed on a group of educational components that will be taken abroad, in the light of the course catalogue that the receiving institution has committed to publish well in advance of the mobility periods and to update regularly as ECHE holder. However, introducing changes might be unavoidable due to, for example, timetable conflicts. Other reasons for a change can be the request for an extension of the duration of the mobility programme abroad. Such a request can be made by the student at the latest one month before the foreseen end date. These changes to the mobility study programme should be agreed by all parties within four to seven weeks (after the start of each semester). Any party can request changes within the first two to five-week period after regular classes/educational components have started for a given semester. The exact deadline has to be decided by the institutions. The shorter the planned mobility period, the shorter should be the window for changes. All these changes have to be agreed by the three parties within a two-week period following the request. In case of changes due to an extension of the duration of the mobility period, changes should be made as timely as possible as well. Changes to the study programme abroad should be listed in table C and, once they are agreed by all parties, the sending institution commits to fully recognise the number of ECTS credits as presented in table C. Any exception to this rule should be documented in an annex of the Learning Agreement and agreed by all parties. Only if the changes described in table C affect the group of educational components in the student's degree (table B) that will be replaced at the sending institution upon successful completion of the study programme abroad, a revised version should be inserted and labelled as "Table D: Revised group of educational components in the student's degree that will be replaced at sending institution". Additional rows and columns can be added as needed to tables C and D. All parties must confirm that the proposed amendments to the Learning Agreement are approved. For this specific section, original or scanned signatures are not mandatory and an approval by email may be enough. The procedure has to be decided by the sending institution, depending on the national legislation.

  • Traditional Medicine Cooperation 1. The aims of Traditional Medicine cooperation will be: (a) to build on existing agreements or arrangements already in place for Traditional Medicine cooperation; and (b) to promote information exchanges on Traditional Medicine between the Parties. 2. In pursuit of the objectives in Article 149 (Objectives), the Parties will encourage and facilitate, as appropriate, the following activities, including, but not limited to: (a) encouraging dialogue on Traditional Medicine policies and promotion of respective Traditional Medicine; (b) raising awareness of active effects of Traditional Medicine; (c) encouraging exchange of experience in conservation and restoration of Traditional Medicine; (d) encouraging exchange of experience on management, research and development for Traditional Medicine; (e) encouraging cooperation in the Traditional Medicine education field, mainly through training programs and means of communication; (f) having a consultation mechanism between the Parties' Traditional Medicine authorities; (g) encouraging cooperation in Traditional Medicine therapeutic services and products manufacturing; and (h) encouraging cooperation in research in the fields of Traditional Medicine in order to contribute in efficacy and safety assessments of natural resources and products used in health care.

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