Supplier’s Request for Change Sample Clauses

Supplier’s Request for Change. 8.2.1. Supplier will make no Change which may (i) increase Clearwire’s total cost of receiving the Services; (ii) require material Changes to, or have an adverse impact on, Clearwire’s operations, facilities, processes, systems, software, utilities, tools or equipment (including those provided, managed, operated, supported and/or used on their behalf by Clearwire contractors); (iii) require Clearwire to install, at their cost or expense, a new version, release, upgrade of or replacement for or to modify any System; (iv) have an adverse impact on the functionality, interoperability, performance, accuracy, speed, responsiveness, quality or resource efficiency of the Services; (v) have an adverse impact on the cost, either actual or planned, to Clearwire of terminating this Agreement, in whole or in part, or on Clearwire’s rights to insource or use third parties; (vi) have an adverse impact on Clearwire’s environment (including its flexibility to deal with future Changes, interoperability and its stability), (vii) introduce new technology to (A) Clearwire’s environment or operations or (B) Supplier’s environment, to the extent that such introduction has or may have an adverse impact on Clearwire’s environment; (viii) have an adverse impact on the functionality, interoperability, performance, accuracy, speed, responsiveness, quality, cost or resource efficiency of Clearwire’s retained systems and processes or (ix) violate or be inconsistent with Clearwire standards without first obtaining Clearwire’s approval in accordance with Section 2.10 of the Agreement. 8.2.2. If Supplier desires to make such a Change, Supplier will notify Clearwire in writing specifying the Change in reasonable detail, the cost impact, the technical consequences and any other known consequence expected to be of interest to Clearwire. The notification will be made to the relevant Governance Operations Committee and will describe: • A description of the requested Change as well as name of the originator and date. • Reasons for the Change including affected Services in Exhibit CStatement of Work or other exhibits under the Agreement. • Special conditions associated with the Change, and the extent to which the desired Change may affect the functionality, performance, price or resource efficiency of the Services and any benefits, savings or risks to Clearwire associated with such Change. CLEARWIRE AND SUPPLIER CONFIDENTIAL Confidential — Subject to Nondisclosure Obligations 8.2.3. Clearwir...
AutoNDA by SimpleDocs
Supplier’s Request for Change. If Supplier wishes to make any change to the Specifications, Supplier shall notify Santarus, and such notice shall describe the proposed change and the impact of such change on the manufacturing process, including details of any changes in manufacturing costs. Santarus may accept or reject, in its sole and absolute discretion, any such change proposed by Supplier.

Related to Supplier’s Request for Change

  • Request for Review Within sixty (60) days after receiving notice from the Plan Administrator that a claim has been denied (in part or all of the claim), then claimant (or their duly authorized representative) may file with the Plan Administrator, a written request for a review of the denial of the claim. The claimant (or his duly authorized representative) shall then have the opportunity to submit written comments, documents, records and other information relating to the claim. The Plan Administrator shall also provide the claimant, upon request and free of charge, reasonable access to, and copies of, all documents, records and other information relevant (as defined in applicable ERISA regulations) to the claimant’s claim for benefits.

  • Notice of Network Changes If a Party makes a change in the information necessary for the transmission and routing of services using that Party’s facilities or network, or any other change in its facilities or network that will materially affect the interoperability of its facilities or network with the other Party’s facilities or network, the Party making the change shall publish notice of the change at least ninety (90) days in advance of such change, and shall use reasonable efforts, as commercially practicable, to publish such notice at least one hundred eighty (180) days in advance of the change; provided, however, that if an earlier publication of notice of a change is required by Applicable Law (including, but not limited to, 47 CFR 51.325 through 51. 335) notice shall be given at the time required by Applicable Law.

  • Bona Fide Request/New Business Request Process for Further Unbundling 6.1 BellSouth shall, upon request of <<customer_name>>, provide to <<customer_name>> access to its network elements at any technically feasible point for the provision of <<customer_name>>'s telecommunications service where such access is necessary and failure to provide access would impair the ability of <<customer_name>> to provide services that it seeks to offer. Any request by <<customer_name>> for access to a network element, interconnection option, or for the provisioning of any service or product that is not already available shall be treated as a Bona Fide Request/New Business Request (BFR/NBR), and shall be submitted to BellSouth pursuant to the BFR/NBR process. 6.2 <<customer_name>> shall submit any BFR/NBR in writing to <<customer_name>>’s Account Manager. The BFR/NBR shall specifically identify the requested service date, technical requirements, space requirements and/or such specifications that clearly define the request such that BellSouth has sufficient information to analyze and prepare a response. The BFR/NBR also shall include <<customer_name>>’s designation of the request as being (i) pursuant to the Telecommunications Act of 1996 or (ii) pursuant to the needs of the business.

  • Request for clarification of the report 1. Within 10 days of the release of the report, either of the disputing Parties may submit a written request to the Panel, a copy of which shall be sent to the other Party, for clarification of any items the Party considers requires further explanation or definition. 2. The Panel shall respond to the request within 10 days following the submission of such request. The clarification of the Panel shall only be a more precise explanation or definition of the original contents of the report, and not an amendment of such report. 3. The filing of this request for clarification will not postpone the effect of the Panel report nor the deadline for compliance of the adopted decision, unless the Panel decides otherwise.

  • Implementation Report Within 150 days after the Effective Date, Ensign Group shall submit a written report to OIG summarizing the status of its implementation of the requirements of this CIA (Implementation Report). The Implementation Report shall, at a minimum, include: 1. the name, address, phone number, and position description of the Compliance Officer required by Section III.A, and a summary of other noncompliance job responsibilities the Compliance Officer may have; 2. the names and positions of the members of the Compliance Committee required by Section III.A; 3. the names and positions of the members of the Board of Directors who are responsible for satisfying the Board of Directors compliance obligations described in Section III.A.3; 4. a copy of Ensign Group’s Code of Conduct required by Section III.B.1; 5. the number of individuals required to complete the Code of Conduct certification required by Section III.B.1, the percentage of individuals who have completed such certification, and an explanation of any exceptions (the documentation supporting this information shall be available to OIG upon request); 6. a summary of all Policies and Procedures required by Section III.B (copies of the Policies and Procedures shall be made available to OIG upon request); 7. the following information regarding each type of training required by Section III.C: a. a description of such training, including a summary of the topics covered, the length of sessions, and a schedule of training sessions; b. the number of individuals required to be trained, percentage of individuals actually trained, and an explanation of any exceptions. A copy of all training materials and the documentation supporting this information shall be made available to OIG upon request. 8. a description of the Disclosure Program required by Section III.E; 9. the following information regarding the IRO(s): (a) identity, address, and phone number; (b) a copy of the engagement letter; (c) information to demonstrate that the IRO has the qualifications outlined in Appendix A to this CIA; (d) a summary and description of any and all current and prior engagements and agreements between Ensign Group and the IRO; and (e) a certification from the IRO regarding its professional independence and objectivity with respect to Ensign Group; 10. a description of the process by which Ensign Group fulfills the requirements of Section III.F regarding Ineligible Persons; 11. a list of all of Ensign Group’s locations (including locations and mailing addresses); the corresponding name under which each location is doing business; the corresponding phone numbers and fax numbers; each location’s Medicare and state Medicaid program provider number and/or supplier number(s); and the name and address of each Medicare and state Medicaid program contractor to which Ensign Group currently submits claims; 12. a description of Ensign Group’s corporate structure, including identification of any parent and sister companies, subsidiaries, and their respective lines of business; and

  • Request for Waiver A. Prior to submission of a request for a partial or total waiver, Bidder/Contractor shall speak to the Designated Contacts of the OGS Office of Minority- and Women-Owned Business Enterprises for guidance. B. In accordance with 5 NYCRR § 142.7, a Bidder/Contractor who is able to document good faith efforts to meet the goal requirements, as set forth in clause VII below, may submit a request for a partial or total waiver on Form BDC 333, accompanied by supporting documentation. A Bidder may submit the request for waiver at the same time it submits its MWBE Utilization Plan. If a request for waiver is submitted with the MWBE Utilization Plan and is not accepted by OGS at that time, the provisions of clauses V(C), (D) & (E) will apply. If the documentation included with the Bidder’s/Contractor’s waiver request is complete, OGS shall evaluate the request and issue a written notice of acceptance or denial within twenty (20) business days of receipt. C. Contractor shall attempt to utilize, in good faith, any MBE or WBE identified within its MWBE Utilization Plan, during the performance of the Contract. Requests for a partial or total waiver of established goal requirements made subsequent to Contract award may be made at any time during the term of the Contract to OGS, but must be made no later than prior to the submission of a request for final payment on the Contract. D. If OGS, upon review of the MWBE Utilization Plan and Monthly MWBE Contractor Compliance Reports determines that Contractor is failing or refusing to comply with the contract goals and no waiver has been issued in regards to such non-compliance, OGS may issue a notice of deficiency to the Contractor. The Contractor must respond to the notice of deficiency within seven (7) business days of receipt. Such response may include a request for partial or total waiver of MWBE contract goals.

  • Request for Proposals A State request inviting proposals for Goods or Services. This Contract shall be governed by the statutes, regulations and procedures of the State of Connecticut, Department of Administrative Services.

  • Procedures for LNP Request The Parties shall provide for the requesting of End Office LNP capability on a reciprocal basis through a written request. The Parties acknowledge that Verizon has deployed LNP throughout its network in compliance with FCC 96-286 and other applicable FCC Regulations. 15.4.1 If Party B desires to have LNP capability deployed in an End Office of Party A, which is not currently capable, Party B shall issue a LNP request to Party A. Party A will respond to the Party B, within ten (10) days of receipt of the request, with a date for which LNP will be available in the requested End Office. Party A shall proceed to provide for LNP in compliance with the procedures and timelines set forth in FCC 00-000, Xxxxxxxxx 80, and FCC 97-74, Paragraphs 65 through 67. 15.4.2 The Parties acknowledge that each can determine the LNP-capable End Offices of the other through the Local Exchange Routing Guide (LERG). In addition, the Parties shall make information available upon request showing their respective LNP-capable End Offices, as set forth in this Section 15.4.

  • Request Procedure The employee shall furnish evidence to the immediate supervisor that leave taken in accordance with the provisions of this section is in connection with family illness. The employee shall notify the immediate supervisor of any of the circumstances necessitating the leave change.

  • Purchase Order Requirements Customers shall use a Request for Quote per section 287.056(2), Florida Statutes, when making purchases off of this State Term Contract. Customers shall issue Request for Quotes to at least 25 vendors approved to provide IT Staff Augmentation services in accordance with section 287.0591(5), Florida Statutes. Customers shall order services from the Request for Quote via a Purchase Order with the Customers’ selected Contractor. The terms of the Purchase Order shall not conflict with the terms and conditions established by this Contract. In accepting a Purchase Order, the Contractor recognizes its responsibility for all tasks and deliverables contained therein, warrants that it has fully informed itself of all relevant factors affecting accomplishment of the tasks and deliverables and agrees to be fully accountable for the performance thereof.

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