Component Procurement Sample Clauses

Component Procurement. Unless otherwise agreed by the parties, Plexus will procure all Components necessary to fulfill Purchase Orders at lead-times reasonably consistent with the lead-times of such Components at the time of order. Customer acknowledges that Plexus may be required by Suppliers to procure Components in minimum or economic order quantities and that such quantities may exceed Customer’s actual Demand. Plexus will obtain Customer’s pre-approval (by e-mail or other written means) of all such procurements. Customer will be liable for any such minimum or economic order quantities so procured by Plexus. Buy to Forecast, Build to Order Addendum
AutoNDA by SimpleDocs
Component Procurement. The Contractor shall procure all necessary hardware, performance measuring equipment, and software for assembling and testing the FESS at the Contractor’s facility. The Contractor shall make every effort to assure that components are received in a timely manner for adherence to the project schedule.
Component Procurement. Supplier is authorized to purchase raw materials and components for use in manufacturing Products based on the Forecasts and Purchase Orders issued by Ciena hereunder. Specifically, based on quoted component lead times from its suppliers, Supplier will determine when to purchase those raw materials and components necessary to support the current Forecast and Purchase Order(s) issued by Ciena within the delivery intervals under Section 3.5.
Component Procurement. 9.1 Solectron will complete the manufacture of Product from raw materials and components that are (i) in Solectron's Current Component Inventory purchased for Exabyte on hand as of the Effective Date and (ii) materials and components that are supplied to Solectron by Exabyte or for which Exabyte has paid Solectron in advance in full before Solectron purchases such material and components (the "Exabyte Supplied Inventory"). Exabyte shall provide all additional components needed for production no later than seventy-two (72) hours prior to planned use in production. If necessary, Solectron will cooperate with Exabyte in the procurement of parts from Solectron contolled suppliers. Delays in production caused by late delivery of components by Exabyte shall not be grounds for rescheduling payments under Section 6.2.3. Solectron shall have no obligation to purchase or commit to purchase any raw materials or components for the manufacture of Products. Notwithstanding any other provision of this Agreement, Solectron may at its sole discretion extend the Delivery Date for any finished Product to accommodate delays in the delivery of any Exabyte Component Inventory or Exabyte Supplied Inventory.
Component Procurement. 9.1 Approved Vendor Lists. Flextronics agrees to buy all Components from suppliers on the AVL. Use of "brokers" for Components will require specific approval by Agilent, which approval will not be unreasonably withheld, prior to use by Flextronics. In the event that Flextronics is unable to procure a Component(s) as a result of the AVL restrictions set forth herein, Agilent and Flextronics agree to negotiate changes to the AVL. Flextronics will use standard purchasing practices, including long lead-time Component management, minimum and multiple supplier order quantities and SMI programs in order to meet Agilent Forecasts.
Component Procurement. Unless otherwise agreed by the parties, Plexus will procure only those Components necessary to fulfill Demand and for which the Component lead-times require that Plexus procure such items in advance. Notwithstanding the forgoing, Plexus will provide Packeteer with a list (a “LLT Component List”) of all Components having a lead-time longer than ninety (90) days (“LLT Components”) at each QBR. So long as a LLT Component has been included on a LLT Component List previously provided to Packeteer, Plexus shall be entitled to procure the same. If a Component becomes a LLT Component between QBRs, Plexus will notify Packeteer of the same, and add the Component to the LLT Component List, prior to procuring the same. Further, Plexus shall at each QBR, or more frequently if requested by Packeteer, provide Packeteer a list of the lead-times for all required Components and a list of Components subject to minimum or economical order quantities. The LLT Component List may be included in such list so long as Plexus makes clear the lead-time of these Components. Packeteer acknowledges that Plexus may be required by Suppliers to procure Components in minimum or economic order quantities and that such quantity may exceed Packeteer’s actual Demand. Packeteer will be liable for any such minimum or economic order quantities so procured by Plexus, provided that Packeteer has provided Plexus written approval to order such minimum or economic order quantities. Plexus shall notify Packeteer of such instances where minimum or economical order quantities would reduce the Component Value. Should any third party Software be included in the Assemblies manufactured by Plexus hereunder, Packeteer and Plexus will work together to determine (i) whether Packeteer or Plexus will be the direct licensee of such Software, and (ii) in the event Plexus is to be responsible for licensing such third party Software, the scope of an appropriate license to seek from such third party Software provider, including the right to sublicense such Software to Packeteer and Packeteer’s customers. Plexus will install all Software in accordance with the Specifications.
Component Procurement 
AutoNDA by SimpleDocs

Related to Component Procurement

  • Manufacturing Services Jabil will manufacture the Product in accordance with the Specifications and any applicable Build Schedules. Jabil will reply to each proposed Build Schedule that is submitted in accordance with the terms of this Agreement by notifying Company of its acceptance or rejection within three (3) business days of receipt of any proposed Build Schedule. In the event of Jabil’s rejection of a proposed Build Schedule, Jabil’s notice of rejection will specify the basis for such rejection. When requested by Company, and subject to appropriate fee and cost adjustments, Jabil will provide Additional Services for existing or future Product manufactured by Jabil. Company shall be solely responsible for the sufficiency and adequacy of the Specifications [***].

  • Service Level Service Provider will classify incidents at its own discretion. Such classifications shall be consistent with the priorities Service Provider set for itself as a recipient of services. Incidents classified using this methodology will be triaged as documented in Attachment A.

  • Benchmark Replacement Notwithstanding anything to the contrary herein or in any other Loan Document, if a Benchmark Transition Event and its related Benchmark Replacement Date have occurred prior any setting of the then-current Benchmark, then (x) if a Benchmark Replacement is determined in accordance with clause (a) of the definition of “Benchmark Replacement” for such Benchmark Replacement Date, such Benchmark Replacement will replace such Benchmark for all purposes hereunder and under any Loan Document in respect of such Benchmark setting and subsequent Benchmark settings without any amendment to, or further action or consent of any other party to, this Agreement or any other Loan Document and (y) if a Benchmark Replacement is determined in accordance with clause (b) of the definition of “Benchmark Replacement” for such Benchmark Replacement Date, such Benchmark Replacement will replace such Benchmark for all purposes hereunder and under any Loan Document in respect of any Benchmark setting at or after 5:00 p.m. (New York City time) on the fifth (5th) Business Day after the date notice of such Benchmark Replacement is provided to the Lenders without any amendment to, or further action or consent of any other party to, this Agreement or any other Loan Document so long as the Administrative Agent has not received, by such time, written notice of objection to such Benchmark Replacement from Lenders comprising the Required Lenders. If the Benchmark Replacement is Daily Simple SOFR, all interest payments will be payable on a quarterly basis.

  • Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.

  • Product Changes IDSI reserves the right to make design and other modifications in the Equipment at any time but shall not be obligated to implement such modifications in Equipment that has previously been delivered.

  • TECHNICAL SUPPORT SERVICES 2.1 The technical support services (the "Services"): Party A agrees to provide to Party B the relevant services requested by Party B, which are specified in Exhibit 1 attached hereto ("Exhibit 1").

  • Administrative Support Service Fees Within forty-five (45) days of the end of each calendar quarter, the Fund will make payments in the aggregate amount of 0.0625% (0.25% on an annual basis) of the average during that calendar quarter of the aggregate net asset value of the Shares computed as of the close of each business day (the "Service Fee"). Such Service Fee payments received from the Fund will compensate the Distributor for providing administrative support services with respect to Accounts. The administrative support services in connection with Accounts may include, but shall not be limited to, the administrative support services that a Recipient may render as described in Section 3(b)(i) below.

  • Financial testing The financial covenants set out in Clause 20.2 (Financial condition) shall be tested by reference to each of the financial statements and/or each Compliance Certificate delivered pursuant to Clause 19.2 (Compliance Certificate).

  • Commercialization Reports After the First Commercial Sale of a Licensed Product anywhere in the Territory, LICENSEE shall submit to Cornell semi-annual reports on or before each February 28 and August 31 of each year. Each report shall cover LICENSEE’s (and each Affiliate’s and Sublicensee’s) most recently completed calendar half-year and shall show:

  • Benchmarking 6.5.1. Not earlier than [***], Company shall have the right, but not the obligation, to conduct a measurement and comparison benchmarking process to compare [***] to ensure that Company is receiving [***], given the nature, volume and type of Services provided by Amdocs hereunder (taking into account the volume of Services, the skill sets and geographical location of the Personnel and other such factors necessary to ensure a like-for-like comparison to the benchmark comparator group) (the “Benchmarking Process”). Upon Amdocs’ receipt of notice of Company’s intent to exercise its benchmarking right, the Parties shall agree on a pool of suitably qualified, experienced and independent benchmarkers generally in the business of conducting such measurements and comparisons. The pool of benchmarkers shall not include any Person that is an Amdocs Competitor. It is the Parties’ intention that they shall jointly select the benchmarker to carry out the Benchmarking Process. However, in the event that the Parties are unable to agree as to the identification of such benchmarker, after escalation of this matter to Company’s Senior Vice President (IT) and Amdocs’ Vice President, then Company may utilize any Third Party benchmarker from the pool to perform the Benchmarking Process (the “Benchmarker”). The Benchmarker will review its benchmarking methodology with Company and Amdocs and the Parties shall agree to the criteria used for selection of the benchmark comparator group prior to commencement of the Benchmarking Process. Amdocs shall have reasonable * Confidential treatment has been requested. The redacted material has been separately filed with the Commission. opportunities to make submissions to the Benchmarker as to the performance of the Services and the related pricing. Company shall pay the fees and expenses charged by the Benchmarker (which fees will not be contingency-based). Amdocs’ cooperation with the Benchmarker shall be conditioned on the Benchmarker’s compliance with Amdocs’ commercially reasonable confidentiality requirements; provided, that, Amdocs shall not be obligated to disclose Confidential Information related to any of Amdocs’ or its Affiliates’ other clients to the Benchmarker. The Benchmarking Process shall be conducted so as not to unreasonably disrupt Amdocs’ operations under this Agreement (including so as not to lead to any material impact on the Service Levels).

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