Agreement Phase Sample Clauses

Agreement Phase. Initialize lock := ∞, m := mP and k := 0. Repeat the following loop – At time (12k + 16) · ∆: Initiate ΠGBA on input m. – At time (12k + 20) · ∆: • Let (v, g) be the output of P . If lock = ∞ then: ∗ If g = 2, set lock := 1. ∗ If g = 1, then set m := v. ∗ If g = 0, then set m = ⊥. – At time (12k + 24) · ∆: • Initiate ΠGBA on input m. • Let (v, g) be the output of P . If lock = ∞ then: ∗ If g = 1, then set m := v. – At time (12k + 27) · ∆: • Multicast m. ∗ If g = 0, then set m = ⊥. • Set k := k + 1 and denote mj the message received from Pj . Let ℓ denote the output obtained from ΠLeader. • If lock = 0, P outputs m and terminates. • If lock = ∞ and m = ⊥, then P sets m := mℓ. • If lock = 1, then P sets lock := 0.
AutoNDA by SimpleDocs
Agreement Phase. After receiving an offer, supplier and customer may negotiate service properties and the pricing scheme. The parties agree on mutual commitments by the result of a (i) fixed price order, (ii) auction, (iii) tender, (vi) exchange, or (v) bilateral negotiation. Any pricing scheme is regarded as a type of price (e.g., metered-usage pricing).
Agreement Phase. After removing the faulty processors, each fault-free processor can achieve agreement by exchanging its value with one another again. Figure 4. IBA Protocol Figure 5(a). The transmission behavior of faulty processors. Figure 5(b). The ic-tree of processor Pe. Figure 5(c). The result of processor Pe.
Agreement Phase. Pi starts the agreement phase by broadcasting a нelp_req message (line 19) only if it has not previously acquired a certificate (due to the check at line 18). If Xx receives a нelp_req message in round 2 of the agreement phase (line 21), Pi replies via a нelp_reply message (line 22) which includes (1) an acquired certificate (if any), and (2) a partial signature of Pi ’s proposal to allow for a (potential) creation of a specific certificate. Pi executes the logic of rounds 3 and 4 only if it has not previously acquired a certificate (due to the checks at lines 24 and 34). In round 3, Pi aims to acquire a certificate: • If Pi receives a valid certificate in a нelp_reply message (line 25), Pi acquires the certificate (line 26). • Otherwise, Pi checks if it has received the same value from t+1 processes via нelp_reply messages (line 27). If so, Pi constructs a specific certificate by combining the received t + 1 partial signatures into a (t + 1)-combined threshold signature (line 29). • If neither of previous cases occurs, Pi aims to build a general certificate. To this end, Pi broadcasts a illow-iny message (line 32) which carries a partial signature of the “allow any” string. In round 4, Pi either receives a formed certificate from another process (line 35) or con- structs a general certificate (line 39). At the end of round 4, Xx proposes the acquired value- certificate pair to EBA (line 40). Finally, when Xx decides from EBA (line 41), it decides from stronc (line 42). Strong Byzantine Agreement with Adaptive Word Complexity Algorithm 1 stronc: Pseudocode (for process Pi) 1: Uses:

Related to Agreement Phase

  • Development Phase contractual phase initiated with the approval of ANP for the Development Plan and which is extended during the Production Phase while investments in xxxxx, equipment, and facilities for the Production of Oil and Gas according to the Best Practices of the Oil Industry are required.

  • Production Phase contract period in which the Development and the Production are to be performed.

  • PRE-COMMENCEMENT PHASE Part 1 - Pre-commencement Phase Services Part 2 - Construction Documents and Site Plan SECTION 3 – CONSTRUCTION PHASE Part 1 - Construction Phase Services Part 2 - Changes to the Work Part 3 - Time. Part 4 - Correcting the Work, Inspections, Covering and Uncovering Work Part 5 - Subcontractors, Trade Contractors, and Suppliers

  • COMMENCEMENT OF WORK UNDER A SOW AGREEMENT Commencement of work as a result of the SOW-RFP process shall be initiated only upon issuance of a fully executed SOW Agreement and Purchase Order.

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

  • Agreement Overview This SLA operates in conjunction with, and does not supersede or replace any part of, the Agreement. It outlines the information technology service levels that we will provide to you to ensure the availability of the application services that you have requested us to provide. All other support services are documented in the Support Call Process.

  • Construction Phase Part 1 –

  • Construction Phase Services 3.1.1 – Basic Construction Services

  • Pre-Commencement Phase Services The services required to be provided by the Contractor for the Pre- Commencement Phase of the Project in accordance with the Contract Documents.

  • Agreement Review If, pursuant to section 25.10 (Review of Agreement) of the Bilateral Agreement, the Bilateral Agreement is reviewed after three or five years, or both, of the effective date of the Bilateral Agreement, and any changes to the Bilateral Agreement are required as a result, the Parties agree to amend the Agreement as necessary and in a manner that is consistent with such changes.

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