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:
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.
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
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.
Project Cost Overruns In the event that the Recipient determines that the moneys granted pursuant to Section II hereof, together with the Local Subdivision Contribution, are insufficient to pay in full the costs of the Project, the Recipient may make a request for supplemental assistance to its District Committee. The Recipient must demonstrate that such funding is necessary for the completion of the Project and the cost overrun was the result of circumstances beyond the Recipient's control, that it could not have been avoided with the exercise of due care, and that such circumstances could not have been anticipated at the time of the Recipient's initial application. Should the District Committee approve such request the action shall be recorded in the District Committee's official meeting minutes and provided to the OPWC Director for the execution of an amendment to this Agreement.
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.
Subprojects 1. The Borrower shall make Grants to Beneficiaries (Small Farmers, Municipalities and Organizations) for Subprojects (Farmers’ Business Initiatives, Infrastructure Subprojects and Environmental Subprojects) in accordance with eligibility criteria and procedures acceptable to the Bank as further detailed in the Project Operational Manual.
Overall Project Schedule The Construction Progress Schedule that is approved by the Owner.
Construction Progress Schedule; Overall Project Schedule The Contractor shall submit for review by the Design Professional and approval by the Owner a Construction Progress Schedule based upon the Design Professional’s Preliminary Design and Construction Schedule and prepared using a CPM (Critical Path Method) process within sixty days after the Effective Date of the Contract, utilizing a full-featured software package in a form satisfactory to the Design Professional and Owner, showing the dates for commencement and completion of the Work required by the Contract Documents, including coordination of mechanical, plumbing, and electrical disciplines, as well as coordination of the various subdivisions of the Work within the Contract. Milestones must be clearly indicated and sequentially organized to identify the critical path of the Project. The Construction Schedule will be developed to represent the CSI specification divisions. It shall have the minimum number of activities required to adequately represent to the Owner the complete scope of Work and define the Project’s (and each Phase’s if phased) critical path and associated activities. The format of the Construction Progress Schedule will have dependencies indicated on a monthly grid identifying milestone dates such as construction start, phase construction, structural top out, dry-in, rough-in completion, metal stud and drywall completion, equipment installation, systems operational, inspections for Material Completion and Occupancy Date, and Final Completion Date. The Contractor shall submit, along with the Construction Progress Schedule, the Submittal Schedule for approval by the Design Professional, correlating the associated approval dates for the documents with the Construction Progress Schedule. Upon recommendation by the Design Professional and approval by the Owner, the Construction Progress Schedule shall become the Overall Project Schedule, which shall be utilized by the Design Professional, Owner and Contractor. The Contractor must provide the Design Professional and the Owner with monthly updates of the Overall Project Schedule indicating completed activities and any changes in sequencing or activity durations, including approved change orders. See also Article 3.3.5.
