Initial Project Scope Sample Clauses

Initial Project Scope. The Project scope as proposed and assumed under the HOA is for the production of approximately 2,250 million standard cubic feet of gas per stream day from the Contract Location from which will be derived approximately 120,000 barrels per stream day of NGL Products and 185,000 barrels per stream day of GTL Products and eventually approximately 98 million standard cubic feet of Ethane per stream day (“Initial Project Scope”).
AutoNDA by SimpleDocs

Related to Initial Project Scope

  • Project Scope The physical scope of the Project shall be limited to only those capital improvements as described in Appendix A of this Agreement. In the event that circumstances require a change in such physical scope, the change must be approved by the District Committee, recorded in the District Committee's official meeting minutes, and provided to the OPWC Director for the execution of an amendment to this Agreement.

  • Development Schedule The Project shall substantially comply with the specific timetables and triggers for action set forth in Article 5 of this Agreement. The parties acknowledge that, as provided in G.S. 160A-400.25(b), the failure to meet a commencement or completion date shall not, in and of itself, constitute a material breach of this Agreement pursuant to G.S. 160A-400.27 but must be judged based upon the totality of the circumstances.

  • Project Schedule Construction must begin within 30 days of the date set forth in Appendix A, Page 2, for the start of construction, or this Agreement may become null and void, at the sole discretion of the Director. However, the Recipient may apply to the Director in writing for an extension of the date to initiate construction. The Recipient shall specify the reasons for the delay in the start of construction and provide the Director with a new start of construction date. The Director will review such requests for extensions and may extend the start date, providing that the Project can be completed within a reasonable time frame.

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

  • Development Plan document specifying the work program, schedule, and relevant investments required for the Development and the Production of a Discovery or set of Discoveries of Oil and Gas in the Contract Area, including its abandonment.

  • Project Specific Milestones In addition to the milestones stated in Section 212.5 of the Tariff, as applicable, during the term of this ISA, Interconnection Customer shall ensure that it meets each of the following development milestones:

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

  • 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

  • Overall Project Schedule The Construction Progress Schedule that is approved by the Owner.

  • Detailed Scope of Work The complete description of services to be provided by the Contractor under an individual Job Order. Developed by the Contractor, after the Joint Scope Meeting and submitted for approval to the County Project Manager.

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