Control Joints Clause Samples

Control Joints. Exterior masonry walls shall have control joints spaced at 30' maximum on centers. The exterior walls shall be designed to withstand a horizontal wind pressure of 20 lbs. per square foot for buildings of less than 30 feet in height.
Control Joints. Square Dowel Basket Assemblies: ¾” x 14” stainless steel square dowel at 14” on center. Side frame supports fabricated from ¼” diameter cold drawn wire per ASTM A108 grade 1010-1020. Square dowel clips extend at least 2” past center of the dowel. PNA clip with foam on each side of dowel extending to within +/- 3/16” of 2/3 length of the dowel to allow for horizontal movement. System as manufactured by PNA Construction Technologies.
Control Joints. (For Controlling Shrinkage Cracks) Differential movement in the floor is caused due to drying shrinkage, thermal changes and carbonation shrinkage. The first is usually the most important. Some shrinkage is expected and can be tolerated. This amount will depend on the design and exposure of the particular structural elements. However when this amount approaches to un-tolerable limit, proportioning, mixing and selection of material deserves careful evaluation and alteration. In floor, shrinkage occurs more rapidly at the exposed surface and causes upward curling at the edges. If the floor is restrained from curling, cracking will occur wherever restrained portion develops stress greater than the tensile strength of RCC floor. Differential movement must be accommodated by control joints spaced at 4.5 M to 7.50 M intervals in both directions; shorter intervals can also be used. Whenever there is reason to expect shrinkage to be high, temperature steel may be used to restrict crack width. For transverse joints 6 mm Plain Asbestos Cement Sheet or PVC sheets having depth up to 2/3 of floor thickness to be fixed before laying concrete for floor. These are fixed simultaneously along with the fixing of from work on the previous day so that it will not be disturbed during concreting. This will help to avoid cracks due to thermal expansion / contraction and also due to drying shrinkage. After the curing work is completed these joints are to be filled with Polysulphide Epoxy mortar having proportion of one part Poly-sulphide Epoxy and two parts silica quartz.
Control Joints. A. Control joints shall be saw-cut into the concrete slab, in pattern indicated on the Contract Documents. B. Joints must comply with requirements per the Massachusetts Architectural Access Board.
Control Joints. 1. Control joints shall be sawcut with scored joints made by scoring into slab surface. 2. Control joints shall be saw-cut according to the Contract Drawings.
Control Joints. A. Control joints shall be saw-cut into the concrete slab, in pattern indicated on the Contract Documents. Joint shall be made after concrete is finished and when the surface is stiff enough to support the weight of workmen without damage to the slab, but before slab has achieved its final set. B. Scoring shall be cut into slab surface 1 inch minimum, but in no case shall scoring be less than 25 percent of slab depth.

Related to Control Joints

  • Control Data <<customer_name>> will send one confirmation record per pack that is received from BellSouth. This confirmation record will indicate <<customer_name>> received the pack and the acceptance or rejection of the pack. Pack Status Code(s) will be populated using standard ATIS EMI error codes for packs that were rejected by <<customer_name>> for reasons stated in the above section.

  • Assignment and Change of Control a. Seller shall not and shall cause its affiliates not to, directly, indirectly, voluntarily or involuntarily, in each case, whether by transfer, operation of law, Change of Control (as defined in subparagraph b below) or otherwise assign this Contract, assign any of its rights or interest in this Contract, delegate any of its obligations under this Contract, or subcontract for all or substantially all of its performance of this Contract (each, an “Assignment”), without Buyer’s prior written consent after advance written notice by Seller. No purported Assignment, with or without Buyer’s consent, shall relieve Seller of any of its obligations under this Contract or prejudice any rights or claims that Buyer may have against Seller, whether such obligations, rights or claims, as the case may be, arise before or after the date of any purported Assignment; provided however, that Seller may assign its right to monies due or to become due under this Contract, and this Article does not limit Seller’s ability to purchase standard commercial supplies or raw material in connection with its performance of this Contract. b. For purposes of this Contract, the term “Change in Control” shall mean any of the following, whether in a single transaction or a series of related transactions and whether or not Seller is a party thereto:

  • Change of Control; Assignment and Subcontracting Except as set forth in this Section 7.5, neither party may assign any of its rights and obligations under this Agreement without the prior written approval of the other party, which approval will not be unreasonably withheld. For purposes of this Section 7.5, a direct or indirect change of control of Registry Operator or any subcontracting arrangement that relates to any Critical Function (as identified in Section 6 of Specification 10) for the TLD (a “Material Subcontracting Arrangement”) shall be deemed an assignment. (a) Registry Operator must provide no less than thirty (30) calendar days advance notice to ICANN of any assignment or Material Subcontracting Arrangement, and any agreement to assign or subcontract any portion of the operations of the TLD (whether or not a Material Subcontracting Arrangement) must mandate compliance with all covenants, obligations and agreements by Registry Operator hereunder, and Registry Operator shall continue to be bound by such covenants, obligations and agreements. Registry Operator must also provide no less than thirty (30) calendar days advance notice to ICANN prior to the consummation of any transaction anticipated to result in a direct or indirect change of control of Registry Operator. (b) Within thirty (30) calendar days of either such notification pursuant to Section 7.5(a), ICANN may request additional information from Registry Operator establishing (i) compliance with this Agreement and (ii) that the party acquiring such control or entering into such assignment or Material Subcontracting Arrangement (in any case, the “Contracting Party”) and the ultimate parent entity of the Contracting Party meets the ICANN-­‐adopted specification or policy on registry operator criteria then in effect (including with respect to financial resources and operational and technical capabilities), in which case Registry Operator must supply the requested information within fifteen (15) calendar days. (c) Registry Operator agrees that ICANN’s consent to any assignment, change of control or Material Subcontracting Arrangement will also be subject to background checks on any proposed Contracting Party (and such Contracting Party’s Affiliates). (d) If ICANN fails to expressly provide or withhold its consent to any assignment, direct or indirect change of control of Registry Operator or any Material Subcontracting Arrangement within thirty (30) calendar days of ICANN’s receipt of notice of such transaction (or, if ICANN has requested additional information from Registry Operator as set forth above, thirty (30) calendar days of the receipt of all requested written information regarding such transaction) from Registry Operator, ICANN shall be deemed to have consented to such transaction. (e) In connection with any such assignment, change of control or Material Subcontracting Arrangement, Registry Operator shall comply with the Registry Transition Process. (f) Notwithstanding the foregoing, (i) any consummated change of control shall not be voidable by ICANN; provided, however, that, if ICANN reasonably determines to withhold its consent to such transaction, ICANN may terminate this Agreement pursuant to Section 4.3(g), (ii) ICANN may assign this Agreement without the consent of Registry Operator upon approval of the ICANN Board of Directors in conjunction with a reorganization, reconstitution or re-­‐incorporation of ICANN upon such assignee’s express assumption of the terms and conditions of this Agreement, (iii) Registry Operator may assign this Agreement without the consent of ICANN directly to a wholly-­‐owned subsidiary of Registry Operator, or, if Registry Operator is a wholly-­‐owned subsidiary, to its direct parent or to another wholly-­‐owned subsidiary of its direct parent, upon such subsidiary’s or parent’s, as applicable, express assumption of the terms and conditions of this Agreement, and (iv) ICANN shall be deemed to have consented to any assignment, Material Subcontracting Arrangement or change of control transaction in which the Contracting Party is an existing operator of a generic top-­‐level domain pursuant to a registry agreement between such Contracting Party and ICANN (provided that such Contracting Party is then in compliance with the terms and conditions of such registry agreement in all material respects), unless ICANN provides to Registry Operator a written objection to such transaction within ten (10) calendar days of ICANN’s receipt of notice of such transaction pursuant to this Section 7.5. Notwithstanding Section 7.5(a), in the event an assignment is made pursuant to clauses (ii) or (iii) of this Section 7.5(f), the assigning party will provide the other party with prompt notice following any such assignment.

  • Resolution of Jointly Owned Parsonage Local Church and any other church with which it jointly owns a parsonage property must resolve the ownership of the parsonage by one party conveying its interest to the other by agreement (on any terms to which those parties may agree) or by process set out in the Discipline, or otherwise sell the parsonage and divide the proceeds on a pro-rata basis.

  • Notice of Change of Contact Person or Key Personnel The Grantee shall notify in writing the assigned System Agency contract manager within ten business days of any change to the Grantee’s Contact Person or Key Personnel.