Preparatory Painter Sample Clauses

Preparatory Painter. Persons who by their qualifications can satisfactorily clean, sand and mask work preparatory to being painted, and also apply paint in a satisfactory manner to parts of vehicles not requiring high grade or varnish finish, such as floors, outside roof and bottom of vehicle, shall be considered a Preparatory Painter.
AutoNDA by SimpleDocs

Related to Preparatory Painter

  • Manufacturing (a) The Supplier shall without limitation be responsible, at no additional cost to the Purchaser, for: sourcing and procuring all raw materials for the Products; obtaining all necessary approvals, permits and licenses for the manufacturing of the Products; providing sufficient qualified staff and workers to perform the obligations under this Purchase Agreement; implementing and maintaining effective inventory and production control procedures with respect to the Products; and handling other matters as reasonably requested by the Purchaser from time to time. (b) The Supplier shall not change any process, material, component, packaging or manufacturing location without the Purchaser’s express prior written approval.

  • Load Shedding The systematic reduction of system demand by temporarily decreasing Load in response to a transmission system or area Capacity shortage, system instability, or voltage control considerations under the ISO OATT. Local Furnishing Bonds. Tax-exempt bonds issued by a Transmission Owner under an agreement between the Transmission Owner and the New York State Energy Research and Development Authority (“NYSERDA”), or its successor, or by a Transmission Owner itself, and pursuant to Section 142(f) of the Internal Revenue Code, 26 U.S.C. § 142(f). Locality. A single LBMP Load Zone or set of adjacent LBMP Load Zones within one Transmission District within which a minimum level of Installed Capacity must be maintained. Local Reliability Rule. A Reliability Rule established by a Transmission Owner, and adopted by the NYSRC to meet specific reliability concerns in limited areas of the NYCA, including without limitation, special conditions and requirements applicable to nuclear plants and special requirements applicable to the New York City metropolitan area. Locational Based Marginal Pricing (“LBMP”). A pricing methodology under which the price of Energy at each location in the NYS Transmission System is equivalent to the cost to supply the next increment of Load at that location (i.e., the short-run marginal cost). The short-run marginal cost takes generation Bid Prices and the physical aspects of the NYS Transmission System into account. The short-run marginal cost also considers the impact of Out-of-Merit Generation (as measured by its Bid Price) resulting from the Congestion and Marginal Losses occurring on the NYS Transmission System which are associated with supplying an increment of Load. The term LBMP also means the price of Energy bought or sold in the LBMP Markets at a specific location.

  • Negotiation Process (a) If either the Chief Executive Officer of ICANN (“CEO”) or the Chairperson of the Registry Stakeholder Group (“Chair”) desires to discuss any revision(s) to this Agreement, the CEO or Chair, as applicable, shall provide written notice to the other person, which shall set forth in reasonable detail the proposed revisions to this Agreement (a “Negotiation Notice”). Notwithstanding the foregoing, neither the CEO nor the Chair may (i) propose revisions to this Agreement that modify any Consensus Policy then existing, (ii) propose revisions to this Agreement pursuant to this Section 7.7 on or before June 30, 2014, or (iii) propose revisions or submit a Negotiation Notice more than once during any twelve (12) month period beginning on July 1, 2014. (b) Following receipt of the Negotiation Notice by either the CEO or the Chair, ICANN and the Working Group (as defined in Section 7.6) shall consult in good faith negotiations regarding the form and substance of the proposed revisions to this Agreement, which shall be in the form of a proposed amendment to this Agreement (the “Proposed Revisions”), for a period of at least ninety (90) calendar days (unless a resolution is earlier reached) and attempt to reach a mutually acceptable agreement relating to the Proposed Revisions (the “Discussion Period”). (c) If, following the conclusion of the Discussion Period, an agreement is reached on the Proposed Revisions, ICANN shall post the mutually agreed Proposed Revisions on its website for public comment for no less than thirty (30) calendar days (the “Posting Period”) and provide notice of such revisions to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval (as defined in Section 7.6) and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (d) If, following the conclusion of the Discussion Period, an agreement is not reached between ICANN and the Working Group on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (the “Mediation Notice”) requiring each party to attempt to resolve the disagreements related to the Proposed Revisions through impartial, facilitative (non-­‐evaluative) mediation in accordance with the terms and conditions set forth below. In the event that a Mediation Notice is provided, ICANN and the Working Group shall, within fifteen (15) calendar days thereof, simultaneously post the text of their desired version of the Proposed Revisions and a position paper with respect thereto on ICANN’s website. (i) The mediation shall be conducted by a single mediator selected by the parties. If the parties cannot agree on a mediator within fifteen (15) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the parties will promptly select a mutually acceptable mediation provider entity, which entity shall, as soon as practicable following such entity’s selection, designate a mediator, who is a licensed attorney with general knowledge of contract law, who has no ongoing business relationship with either party and, to the extent necessary to mediate the particular dispute, general knowledge of the domain name system. Any mediator must confirm in writing that he or she is not, and will not become during the term of the mediation, an employee, partner, executive officer, director, or security holder of ICANN or an Applicable Registry Operator. If such confirmation is not provided by the appointed mediator, then a replacement mediator shall be appointed pursuant to this Section 7.7(d)(i). (ii) The mediator shall conduct the mediation in accordance with the rules and procedures for facilitative mediation that he or she determines following consultation with the parties. The parties shall discuss the dispute in good faith and attempt, with the mediator’s assistance, to reach an amicable resolution of the dispute. (iii) Each party shall bear its own costs in the mediation. The parties shall share equally the fees and expenses of the mediator. (iv) If an agreement is reached during the mediation, ICANN shall post the mutually agreed Proposed Revisions on its website for the Posting Period and provide notice to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the agreed Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (v) If the parties have not resolved the dispute for any reason by the date that is ninety (90) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the mediation shall automatically terminate (unless extended by agreement of the parties). The mediator shall deliver to the parties a definition of the issues that could be considered in future arbitration, if invoked. Those issues are subject to the limitations set forth in Section 7.7(e)(ii) below. (e) If, following mediation, ICANN and the Working Group have not reached an agreement on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (an “Arbitration Notice”) requiring ICANN and the Applicable Registry Operators to resolve the dispute through binding arbitration in accordance with the arbitration provisions of Section 5.2, subject to the requirements and limitations of this Section 7.7(e). (i) If an Arbitration Notice is sent, the mediator’s definition of issues, along with the Proposed Revisions (be those from ICANN, the Working Group or both) shall be posted for public comment on ICANN’s website for a period of no less than thirty (30) calendar days. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators), and information regarding such comments and consideration shall be provided to a three (3) person arbitrator panel. Each party may modify its Proposed Revisions before and after the Posting Period. The arbitration proceeding may not commence prior to the closing of such public comment period, and ICANN may consolidate all challenges brought by registry operators (including Registry Operator) into a single proceeding. Except as set forth in this Section 7.7, the arbitration shall be conducted pursuant to Section 5.2. (ii) No dispute regarding the Proposed Revisions may be submitted for arbitration to the extent the subject matter of the Proposed Revisions (i) relates to Consensus Policy, (ii) falls within the subject matter categories set forth in Section 1.2 of Specification 1, or (iii) seeks to amend any of the following provisions or Specifications of this Agreement: Articles 1, 3 and 6; Sections 2.1, 2.2, 2.5, 2.7, 2.9, 2.10, 2.16, 2.17, 2.19, 4.1, 4.2, 7.3, 7.6, 7.7, 7.8, 7.10, 7.11, 7.12, 7.13, 7.14, 7.16; Section 2.8 and Specification 7 (but only to the extent such Proposed Revisions seek to implement an RPM not contemplated by Sections 2.8 and Specification 7); Exhibit A; and Specifications 1, 4, 6, 10 and 11. (iii) The mediator will brief the arbitrator panel regarding ICANN and the Working Group’s respective proposals relating to the Proposed Revisions. (iv) No amendment to this Agreement relating to the Proposed Revisions may be submitted for arbitration by either the Working Group or ICANN, unless, in the case of the Working Group, the proposed amendment has received Registry Operator Approval and, in the case of ICANN, the proposed amendment has been approved by the ICANN Board of Directors. (v) In order for the arbitrator panel to approve either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions, the arbitrator panel must conclude that such proposed amendment is consistent with a balanced application of ICANN’s core values (as described in ICANN’s Bylaws) and reasonable in light of the balancing of the costs and benefits to the business interests of the Applicable Registry Operators and ICANN (as applicable), and the public benefit sought to be achieved by the Proposed Revisions as set forth in such amendment. If the arbitrator panel concludes that either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions meets the foregoing standard, such amendment shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator and deemed an Approved Amendment hereunder. (f) With respect to an Approved Amendment relating to an amendment proposed by ICANN, Registry may apply in writing to ICANN for an exemption from such amendment pursuant to the provisions of Section 7.6. (g) Notwithstanding anything in this Section 7.7 to the contrary, (a) if Registry Operator provides evidence to ICANN's reasonable satisfaction that the Approved Amendment would materially increase the cost of providing Registry Services, then ICANN will allow up to one-­‐hundred eighty (180) calendar days for the Approved Amendment to become effective with respect to Registry Operator, and (b) no Approved Amendment adopted pursuant to Section 7.7 shall become effective with respect to Registry Operator if Registry Operator provides ICANN with an irrevocable notice of termination pursuant to Section 4.4(b).

  • Solution The Supplier’s contractually committed technical approach for solving an information technology business objective and associated Requirements as defined and authorized by the scope of the Contract or any order or Statement of Work issued under the Contract. Solution means all Supplier and Supplier’s third-party providers’ components making up the Solution, including but not limited to Software, Product, configuration design, implementation, Supplier-developed interfaces, Services and Work Product.

  • Operator Materials Operator retains all right, title and interest in and to any and all of Operator’s software, materials, tools, forms, documentation, training and implementation materials and intellectual property (“Operator Materials”). Operator grants to the LEA a personal, nonexclusive license to use the Operator Materials for its own non-commercial, incidental use as set forth in the Service Agreement. Operator represents that it has all intellectual property rights necessary to enter into and perform its obligations in this DPA and the Service Agreement, warrants to the District that the District will have use of any intellectual property contemplated by the Service Agreement free and clear of claims of any nature by any third Party including, without limitation, copyright or patent infringement claims, and agrees to indemnify the District for any related claims.

  • Laboratory a. Drug tests shall be conducted by laboratories licensed and approved by SAMSHA which comply with the American Occupational Medical Association (AOMA) ethical standards. Upon advance notice, the parties retain the right to inspect the laboratory to determine conformity with the standards described in this policy. The laboratory will only test for drugs identified in this policy. The City shall bear the cost of all required testing unless otherwise specified herein. b. Tests for all controlled substances, except alcohol, shall be by oral fluid testing and shall consist of two procedures, a screen test and, if that is positive, a confirmation test. c. To be considered positive for reporting by the laboratory to the City, both samples must be tested separately in separate batches and must also show positive results on the confirmatory test. d. In the event of a positive test, the testing laboratory will perform an automatic confirmation test on the original specimen at no cost to the Covered Employee. In addition, the testing laboratory shall preserve a sufficient specimen to permit an independent re-testing at the Covered Employee’s request and expense. The same, or any other, approved laboratory may conduct re-tests. The laboratory shall endeavor to notify the designated MRO of positive drug, alcohol, or adulterant tests results within five (5) working days after receipt of the specimen.

  • Engineering Forest Service completed survey and design for Specified Roads prior to timber sale advertisement, unless otherwise shown in A8 or Purchaser survey and design are specified in A7. On those roads for which Forest Service completes the design during the contract, the design quantities shall be used as the basis for revising estimated costs stated in the Schedule of Items and adjusting Timber Sale Account. (a) A7 to show Purchaser’s performance responsibility. (b) The Schedule of Items to include costs of survey and design, as provided under B5.24, and adjust Timber Sale Account, as provided in B5.

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