Replisome convergence and completion of replication Sample Clauses

Replisome convergence and completion of replication. The first step in eukaryotic replication termination involves the convergence of two CMGs. This requires the removal of any proteins that may be bound to the DNA in between the CMGs. In Xenopus extracts, it has been observed that converging replisomes do not slow down or stall as they approach one another, and that opposing leading strands are ligated to downstream Okazaki fragments prior to disassembly of the CMG (Xxxxx et al. 2015). Furthermore, the completion of synthesis and the final ligation step are not affected in the absence of a pathway for removing CMG (Xxxxx et al. 2015). This has led to the proposal that CMGs pass one another and are subsequently removed from dsDNA (Xxxxx et al. 2015).
Sample 1
AutoNDA by SimpleDocs

Related to Replisome convergence and completion of replication

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

  • Supervisory Control and Data Acquisition (SCADA) Capability The wind plant shall provide SCADA capability to transmit data and receive instructions from the ISO and/or the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, as applicable, to protect system reliability. The Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected and the wind plant Developer shall determine what SCADA information is essential for the proposed wind plant, taking into account the size of the plant and its characteristics, location, and importance in maintaining generation resource adequacy and transmission system reliability in its area.

  • State Approval of Replacement Personnel The Engineer may not replace the project manager or key personnel without prior consent of the State. The State must be satisfied that the new project manager or other key personnel is qualified to provide the authorized services. If the State determines that the new project manager or key personnel is not acceptable, the Engineer may not use that person in that capacity and shall replace him or her with one satisfactory to the State within forty-five (45) days.

  • Construction Change Directives 7.3.1 A Construction Change Directive is written order prepared by the Architect and signed by the Owner and Architect, directing a change in the Work and stating a proposed basis for adjustment, if any, in the Contract Sum, or Contract Time, or both. The Owner may by Construction Change Directive, without invalidating the Contract, order changes in the Work within the general scope of the Contract consisting of additions, deletions or other revisions, the Contract Sum and Contract Time being adjusting accordingly.

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

  • Construction Change Directive A written order prepared and issued by the District, the Construction Manager, and/or the Architect and signed by the District and the Architect, directing a change in the Work.

  • Post-Commercial Operation Date Testing and Modifications Each Party shall at its own expense perform routine inspection and testing of its facilities and equipment in accordance with Good Utility Practice as may be necessary to ensure the continued interconnection of the Large Generating Facility with the Participating TO’s Transmission System in a safe and reliable manner. Each Party shall have the right, upon advance written notice, to require reasonable additional testing of the other Party’s facilities, at the requesting Party’s expense, as may be in accordance with Good Utility Practice.

  • Milestone schedule Please state the status and progress of each Milestone and identify any completed Milestone(s) for the previous calendar quarter.

  • Change Management Process If Customer or Oracle requests a change in any of the specifications, requirements, Deliverables, or scope (including drawings and designs) of the Professional Services described in any Statement of Work, the party seeking the change shall propose the applicable changes by written notice. Within forty-eight (48) hours of receipt of the written notice, each party’s project leads shall meet, either in person or via telephone conference, to discuss and agree upon the proposed changes. Oracle will prepare a change order describing the proposed changes to the Statement of Work and the applicable change in fees and expenses, if any (each, a “Change Order”). Change Orders are not binding unless and until they are executed by both parties. Executed Change Orders shall be deemed part of, and subject to, this Addendum. If the parties disagree about the proposed changes, the parties shall promptly escalate the change request to their respective senior management for resolution.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

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