Mining Development Contract Sample Clauses

Mining Development Contract. The Mining Development Contract (MDC) provides a mechanism for the transfer of ownership of LMC assets (works and facilities) to the State. The importance for closure planning is both liability and risk are extinguished as soon as title is vested in the State. Lihir Management Company Limited Lihir Gold Mine — Mine Closure Plan Update 2004 Clause 5.1 of the MDC identifies “Works and Facilities” which are capable of being used by the State. However, the following three categories are excluded (Appendix B): • Administrative and accommodation buildings for the company’s workforce; • Installations and infrastructure directly used in the mining and processing of ore; and. • Roads in the mining area. In the 1999 MCP, the following loans and agreements were noted as expiring in 2003. It is understood these loans and agreements have now expired. • Export Finance and Insurance Corporation Agreement • Multilateral Investment Guarantee Agency • Mining Industry Consultants Agreement
AutoNDA by SimpleDocs

Related to Mining Development Contract

  • Project contract 1. For each approved project a project contract shall be concluded between the Programme Operator and the Project Promoter.

  • Project Development a. Collaborate with COUNTY and project clients to identify requirements and develop a project Scope Statement.

  • Development Agreement As soon as reasonably practicable following the ISO’s selection of a transmission Generator Deactivation Solution, the ISO shall tender to the Developer that proposed the selected transmission Generator Deactivation Solution a draft Development Agreement, with draft appendices completed by the ISO to the extent practicable, for review and completion by the Developer. The draft Development Agreement shall be in the form of the ISO’s Commission-approved Development Agreement for its reliability planning process, which is in Appendix C in Section 31.7 of Attachment Y of the ISO OATT, as amended by the ISO to reflect the Generator Deactivation Process. The ISO and the Developer shall finalize the Development Agreement and appendices as soon as reasonably practicable after the ISO’s tendering of the draft Development Agreement. For purposes of finalizing the Development Agreement, the ISO and Developer shall develop the description and dates for the milestones necessary to develop and construct the selected project by the required in-service date identified in the Generator Deactivation Assessment, including the milestones for obtaining all necessary authorizations. Any milestone that requires action by a Connecting Transmission Owner or Affected System Operator identified pursuant to Attachment P of the ISO OATT to complete must be included as an Advisory Milestone, as that term is defined in the Development Agreement. If the ISO or the Developer determines that negotiations are at an impasse, the ISO may file the Development Agreement in unexecuted form with the Commission on its own, or following the Developer’s request in writing that the agreement be filed unexecuted. If the Development Agreement is executed by both parties, the ISO shall file the agreement with the Commission for its acceptance within ten (10) Business Days after the execution of the Development Agreement by both parties. If the Developer requests that the Development Agreement be filed unexecuted, the ISO shall file the agreement at the Commission within ten (10) Business Days of receipt of the request from the Developer. The ISO will draft, to the extent practicable, the portions of the Development Agreement and appendices that are in dispute and will provide an explanation to the Commission of any matters as to which the parties disagree. The Developer will provide in a separate filing any comments that it has on the unexecuted agreement, including any alternative positions it may have with respect to the disputed provisions. Upon the ISO’s and the Developer’s execution of the Development Agreement or the ISO’s filing of an unexecuted Development Agreement with the Commission, the ISO and the Developer shall perform their respective obligations in accordance with the terms of the Development Agreement that are not in dispute, subject to modification by the Commission. The Connecting Transmission Owner(s) and Affected System Operator(s) that are identified in Attachment P of the ISO OATT in connection with the selected transmission Generator Deactivation Solution shall act in good faith in timely performing their obligations that are required for the Developer to satisfy its obligations under the Development Agreement.

  • Program Development NWESD agrees that priority in the development of new applications services by XXXXX shall be in accordance with the expressed direction of the XXXXX Board of Directors operating under their bylaws.

  • Design Development Documents See Section 2, Part 1, Article 2.1.5.

  • Commencement of Development 7.3.1 In the event that development on the Lands has not commenced within four (4) years from the date of registration of this Agreement at the Registry of Deeds or Land Registry Office, as indicated herein, the Agreement shall have no further force or effect and henceforth the development of the Lands shall conform with the provisions of the Land Use By-law.

  • Project Contracts Authority shall upon its election, succeed, without the necessity of any further action by the Concessionaire, to the interests of the Concessionaire under such of the Project Contracts as the Authority may in its discretion deem appropriate, and shall upon such election be liable to the Contractors only for compensation accruing and becoming due and payable to them under the terms of their respective Project Contracts from and after the date the Authority elects to succeed to the interests of the Concessionaire. For the avoidance of doubt, it is hereby agreed, and the Concessionaire hereby acknowledges, that all sums claimed by such Contractors as being due and owing for works and services performed or accruing on account of any act, omission or event prior to such date shall constitute debt between the Concessionaire and such Contractors, and the Authority shall not in any manner be liable for such sums. It is further agreed that in the event the Authority elects to cure any outstanding defaults under such Project Contracts, the amount expended by the Authority for this purpose shall be deducted from the Termination Payment.

  • Compliance Between Individual Contract and Master Agreement Any individual contract between the Board and an individual employee, heretofore or hereafter executed, shall be subject to and consistent with the terms and conditions of this Agreement. If an individual contract contains any language inconsistent with this Agreement, this Agreement, during its duration, shall be controlling.

  • 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 Work Do, or cause to be done, such development and other work as may be reasonably necessary to protect from diminution and production capacity of the Mortgaged Property and each producing well thereon.

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