Implementation & Operations Program (IOP) Sample Clauses

Implementation & Operations Program (IOP). The goal of the IOP is to develop a comprehensive program that will verify system readiness for revenue service in a safe, efficient, and reliable manner by conducting a systematic series of tests, training, demonstrations, and operational drills that will provide confidence that the system can be placed into revenue service. 2.1.1. The IOP will provide input for the following activities in this phase of the project: • Create/implement system performance tests for system integration • Obtain necessary input from affected organizations such as Sun Metro, Emergency Services Departments, EPDOT, Utility Companies, and others. • Provide CRRMA an opportunity to include participants in addition to CRRMA and the Consultant to help create, along with help approve/reject start-up tests • Identify and address training needs for COEP/Sun Metro staff • Address stakeholder issues This scope includes project activities of the IOP during Preconstruction Phase Services, including preparation of implementation plans as noted below. Execution of the IOP during construction, start-up, and revenue operations is not included in this scope. Establishing the IOP, its responsibilities, and requirements necessary to accomplish IOP goals. This scope of work takes the initial documents from the Interim Phase of work and advances them in preparation for contractor bidding. It is assumed that these will be living documents that will continue to evolve beyond this phase of services during construction, start-up, and testing. 2.1.2. Advance the System Safety and Security Certification Plan (SSCP) The SSCP will provide documentation for when service begins. It promotes a safe and secure environment for employees, public safety personnel, and the general public. The SSCP identifies the processes, deliverables, and responsibilities and outlines a formal program to systematically review and verify all systems, equipment, facilities, plans, procedures, and training programs for compliance with established system safety and security requirements prior to implementation of revenue service.
Sample 1
AutoNDA by SimpleDocs

Related to Implementation & Operations Program (IOP)

  • Project Implementation The Borrower shall:

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Development Plans Shipper has provided Gatherer with a report attached hereto as Exhibit D (the “Current Development Plan”) describing in detail, as of January 1, 2017, the planned development, drilling, and production activities to take place with respect to Dedicated Production for the applicable Development Period. The information contained in the TERMS IN THIS EXHIBIT HAVE BEEN REDACTED BECAUSE CONFIDENTIAL TREATMENT FOR THOSE TERMS HAS BEEN REQUESTED. THE REDACTED MATERIAL HAS BEEN FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION, AND THE TERMS HAVE BEEN MARKED AT THE APPROPRIATE PLACE WITH TWO ASTERISKS (**). Current Development Plan is broken out on a Subsystem-by-Subsystem basis and, with respect to the first three Years covered by the Current Development Plan, on a Quarter-by-Quarter basis, and with respect to the remaining Years covered by the Current Development Plan, on a Year-by-Year basis. The Current Development Plan attached hereto has been approved by the Parties. (a) From time to time during each Year of the Term, the Parties shall meet to discuss the planned development, drilling, and production activities that Shipper expects to take place with respect to Dedicated Production for the then-applicable Development Period. Shipper and Gatherer shall each make their respective representatives available to participate in such meetings and discussions. No later than August 1 of each such Year, Shipper shall provide (or cause to be provided) to Gatherer a proposed update of the then-currently agreed Development Plan, prepared on the same basis as the Current Development Plan and describing in detail the planned development, drilling, and production activities to take place with respect to Dedicated Production for the then-applicable Development Period (any such update, an “Updated Development Plan” and, together with the Current Development Plan, each, a “Development Plan”). Notwithstanding anything herein to the contrary, in no event shall Gatherer be required to agree to any Updated Development Plan and corresponding updated Gathering System Plan that contains a Committed Build-Out that (i) has a corresponding Target Completion Date that occurs after the end of the Initial Term, and (ii) Gatherer, in its sole discretion, does not wish to approve. (b) Each proposed Development Plan shall include information as to the following, in each case, broken out on a Subsystem-by-Subsystem basis and, with respect to the first three Years covered by such Development Plan, on a Quarter-by-Quarter basis, and, with respect to the remaining Years covered by such Development Plan, on a Year-by-Year basis: (i) all Xxxxx that, as of the date such Development Plan was delivered, are currently in existence and (A) the production therefrom is being delivered into the Gathering System, or (B) are awaiting connection to the Gathering System; (ii) the Xxxxx that are expected to be drilled during the time period covered by such Development Plan (each such Well reflected in such Development Plan, a “Planned Well”), and the estimated timing of the drilling of such Planned Xxxxx; (iii) forward-looking production estimates for the applicable time period covered by such Development Plan for all Shipper Gas (A) that Shipper reasonably and in good faith believes will become owned or Controlled by Shipper during the time period covered by such Development Plan, and/or (B) that will be produced from (I) in the aggregate, all Xxxxx then-existing and (II) in the aggregate, any Planned Xxxxx included in such Development Plan (such collective estimates described in subsections (A) and (B), both with respect to a particular Quarter and an entire Year, the “Dedicated Production Estimates”); TERMS IN THIS EXHIBIT HAVE BEEN REDACTED BECAUSE CONFIDENTIAL TREATMENT FOR THOSE TERMS HAS BEEN REQUESTED. THE REDACTED MATERIAL HAS BEEN FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION, AND THE TERMS HAVE BEEN MARKED AT THE APPROPRIATE PLACE WITH TWO ASTERISKS (**). (iv) forward-looking estimates for the applicable time period covered by such Development Plan of the aggregate volumes of those Shipper Injected Liquids that Shipper intends to Tender to the Injection Points hereunder to receive the System Services (such estimates, both with respect to a particular Quarter and an entire Year, the “System Liquids Estimates” and, together with the Dedicated Production Estimates, the “System Production Estimates”); (v) (A) each new receipt point (including the location thereof) proposed by Shipper with respect to the System Production Estimate reflected in such Development Plan (each such receipt point, including those located at the site of a Planned Well, a “Planned Receipt Point”), (B) each Receipt Point at which Shipper expects to Tender Shipper Gas and/or Shipper Injected Liquids reflected in such Development Plan into the Gathering System, and (C) the estimated portion of the System Production Estimate contained in such Development Plan that Shipper expects to Tender at each such Receipt Point and Planned Receipt Point; (vi) the earliest date on which each Planned Well included in the Development Plan is estimated to be completed and producing, which date shall not be earlier than three Months after the January 1st that is immediately subsequent to the date that the Development Plan that initially reflected such Planned Well was delivered to Gatherer hereunder; (vii) the anticipated characteristics of the production from the Xxxxx and Planned Xxxxx reflected in such Development Plan (including liquids content and gas and liquids composition) and the projected production volumes and production pressures applicable thereto; provided that Shipper may utilize the existing and historical production information from similarly situated Xxxxx; (viii) (A) each new delivery point (including the location thereof) proposed by Shipper with respect to the System Production Estimate reflected in such Development Plan (each such delivery point, a “Planned Delivery Point”), (B) each Delivery Point at which Shipper expects Shipper Gas produced from the Xxxxx and Planned Xxxxx reflected in such Development Plan to be redelivered to Shipper, (C) each Delivery Point at which Shipper expects any Drip Liquids allocated to Shipper in accordance with this Agreement and/or Shipper Injected Liquids to be redelivered to Shipper, and (D) the estimated portion of the System Production Estimate contained in such Development Plan that Shipper expects to be redelivered to Shipper at each such Delivery Point and Planned Delivery Point; (ix) any (A) proposed revision to the then-existing Dedicated Area and/or any then-existing Dedicated Contract and/or (B) any new contract that Shipper proposes to be a Dedicated Contract; and (x) other information reasonably requested by Gatherer that is relevant to the design, construction, and operation of the Gathering System, including (A) any Subsystem Extension proposed by Shipper, (B) the relevant Receipt Point, Planned Receipt Point, Delivery Point and Planned Delivery Point facilities applicable to such TERMS IN THIS EXHIBIT HAVE BEEN REDACTED BECAUSE CONFIDENTIAL TREATMENT FOR THOSE TERMS HAS BEEN REQUESTED. THE REDACTED MATERIAL HAS BEEN FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION, AND THE TERMS HAVE BEEN MARKED AT THE APPROPRIATE PLACE WITH TWO ASTERISKS (**). Development Plan, and (C) any treating, processing, or liquids handling facilities proposed by Shipper that may be required for any Shipper Gas and/or Shipper Injected Liquids to meet applicable Downstream Facility specifications at the Delivery Points.

  • Development Activities The Development activities referred to in item “b” of paragraph 3.1 include: studies and projects of implementation of the Production facilities; drilling and completion of the Producing and injection xxxxx; and installation of equipment and vessels for extraction, collection, Treatment, storage, and transfer of Oil and Gas. The installation referred to in item “c” includes, but is not limited to, offshore platforms, pipelines, Oil and Gas Treatment plants, equipment and facilities for measurement of the inspected Production, wellhead equipment, production pipes, flow lines, tanks, and other facilities exclusively intended for extraction, as well as oil and gas pipelines for Production Outflow and their respective compressor and pumping stations.

  • 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 Concession Area, including its abandonment.

  • Verizon Operations Support Systems Verizon systems for pre- ordering, ordering, provisioning, maintenance and repair, and billing.

  • Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.

  • Implementation Plan The Authority shall cause to be prepared an Implementation Plan meeting the requirements of Public Utilities Code Section 366.2 and any applicable Public Utilities Commission regulations as soon after the Effective Date as reasonably practicable. The Implementation Plan shall not be filed with the Public Utilities Commission until it is approved by the Board in the manner provided by Section 4.9.

  • Implementation and Review The Parties shall consult annually, or as otherwise agreed, to review the implementation of this Chapter and consider other matters of mutual interest affecting trade in services. (10) 10 Such consultations will be addressed under Article 170 (Free Trade Commission) of Chapter 14 (Administration of the Agreement).

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

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!