Changes Initiated by AMD Sample Clauses

Changes Initiated by AMD. Concurrent with the submission of a request for a Change by AMD, either AMD or a joint project team working on the impacted Service, as appropriate, shall provide to Spansion a Change Proposal containing the information specified in subparagraph (i) above. Within ten (10) business days after receiving such proposal, Spansion shall either approve the Change Proposal, notify AMD that Spansion desires to discuss the Change Proposal further, or reject the requested Change. Spansion’s failure to approve the Change Proposal or notify AMD that Spansion desires to discuss the Change Proposal further within this ten (10) business day period shall be deemed a rejection of such request, and the Change shall not be implemented. If Spansion rejects the request or does not respond to the request, then the AMD Services Advisor may notify all members of the Board of Directors by simultaneous notice, with a copy to the Spansion chief financial officer (or other officer who supervises the Spansion Services Manager, if applicable) and to the Fujitsu Services Advisor, of the rejection of the Change Proposal and may request that the Board of Directors determine whether the Change should be made by or for Spansion.
AutoNDA by SimpleDocs
Changes Initiated by AMD. Concurrent with the submission of a request for a Change by AMD, either AMD or a joint project team working on the impacted Service, as appropriate, shall provide to Spansion a Change Proposal containing the information specified in subparagraph (i) above. Within ten (10) business days after receiving such proposal, Spansion shall either approve the Change Proposal, notify AMD that Spansion desires to discuss the Change Proposal further, or reject the requested Change. Spansion’s failure to approve the Change Proposal or notify AMD that Spansion desires to discuss the Change Proposal further within this ten (10) business day period shall be deemed a rejection of such request, and the Change shall not be implemented.
Changes Initiated by AMD. Within ten (10) business days after Spansion receives a request from AMD for a Change, either Spansion or a joint project team working on the Service to be impacted, as appropriate, shall prepare and provide to AMD an initial written proposal for the Change (a “Change Proposal”), which proposal will include Spansion’s initial proposals regarding (A) the Services and the applicable schedule for performing the Services, including but not limited to AMD’s related obligations, to effect the Change, (B) the resources required to perform Services effecting the Change and resulting from the Change, (C) the Fees for Services, and (D) any additional areas that are reasonably likely to be impacted by the proposed Change. The Change Proposal shall also contain a description of any other anticipated costs that AMD will incur as a result of the Change that it would otherwise not have incurred. Within ten (10) business days after receiving such Change Proposal, AMD shall either approve the Change Proposal, notify Spansion that AMD desires to discuss the Change Proposal further, or withdraw the request for such Change. AMD’s failure to approve the Change Proposal or notify Spansion that AMD desires to discuss the Change Proposal further within this ten (10) business day period shall be deemed a rejection of the Change Proposal, and the Change shall not be implemented.

Related to Changes Initiated by AMD

  • initiated by ICANN Upon reaching 10% of the Emergency thresholds as described in Section 6 of this Specification, ICANN’s emergency operations will initiate an Emergency Escalation with the relevant Registry Operator. An Emergency Escalation consists of the following minimum elements: electronic (i.e., email or SMS) and/or voice contact notification to the Registry Operator’s emergency operations department with detailed information concerning the issue being escalated, including evidence of monitoring failures, cooperative trouble-shooting of the monitoring failure between ICANN staff and the Registry Operator, and the commitment to begin the process of rectifying issues with either the monitoring service or the service being monitoring.

  • Emergency Escalation initiated by ICANN Upon reaching 10% of the Emergency thresholds as described in Section 6 of this Specification, ICANN’s emergency operations will initiate an Emergency Escalation with the relevant Registry Operator. An Emergency Escalation consists of the following minimum elements: electronic (i.e., email or SMS) and/or voice contact notification to the Registry Operator’s emergency operations department with detailed information concerning the issue being escalated, including evidence of monitoring failures, cooperative trouble-­‐shooting of the monitoring failure between ICANN staff and the Registry Operator, and the commitment to begin the process of rectifying issues with either the monitoring service or the service being monitoring.

  • Termination for Changes in Budget or Law The JBE’s payment obligations under this Agreement are subject to annual appropriation and the availability of funds. Expected or actual funding may be withdrawn, reduced, or limited prior to the expiration or other termination of this Agreement. Funding beyond the current appropriation year is conditioned upon appropriation of sufficient funds to support the activities described in this Agreement. The JBE may terminate this Agreement or limit Contractor’s Services (and reduce proportionately Contractor’s fees) upon Notice to Contractor without prejudice to any right or remedy of the JBE if: (i) expected or actual funding to compensate Contractor is withdrawn, reduced or limited; or (ii) the JBE determines that Contractor’s performance under this Agreement has become infeasible due to changes in applicable laws.

  • MINOR CHANGES IN THE WORK If permitted in the agreement between Owner and Architect, the Architect has authority to order minor changes in the Work not involving adjustment in the Contract Sum or extension of the Contract Time and not inconsistent with the intent of the Contract Documents.

  • Claims Initiated by Indemnitee To indemnify or advance expenses to Indemnitee with respect to an action, suit or proceeding (or part thereof) initiated by Indemnitee, except with respect to an action, suit or proceeding brought to establish or enforce a right to indemnification (which shall be governed by the provisions of Section 8(b) of this Agreement), unless such action, suit or proceeding (or part thereof) was authorized or consented to by the Board of Directors of the Corporation.

  • Changes in Work A. Work Previously Submitted as Satisfactory. If the Engineer has submitted work in accordance with the terms of this contract but the State requests changes to the completed work or parts thereof which involve changes to the original scope of services or character of work under the contract, the Engineer shall make such revisions as requested and as directed by the State. This will be considered as additional work and paid for as specified under Article 4, Additional Work.

  • Emergency Escalation initiated by Registrars Registry Operator will maintain an emergency operations department prepared to handle emergency requests from registrars. In the event that a registrar is unable to conduct EPP transactions with the registry for the TLD because of a fault with the Registry Service and is unable to either contact (through ICANN mandated methods of communication) the Registry Operator, or the Registry Operator is unable or unwilling to address the fault, the registrar may initiate an emergency escalation to the emergency operations department of ICANN. ICANN then may initiate an emergency escalation with the Registry Operator as explained above.

  • Reviewed by Attorneys Each Obligor represents and warrants to the Lenders that it (a) understands fully the terms of this Agreement and the consequences of the execution and delivery of this Agreement, (b) has been afforded an opportunity to have this Agreement reviewed by, and to discuss this Agreement and any documents executed in connection herewith with, such attorneys and other persons as Obligors may wish, and (c) has entered into this Agreement and executed and delivered all documents in connection herewith of its own free will and accord and without threat, duress or other coercion of any kind. The parties hereto acknowledge and agree that neither this Agreement nor the other documents executed pursuant hereto shall be construed more favorably in favor of one than the other based upon which party drafted the same, it being acknowledged that all parties hereto contributed substantially to the negotiation and preparation of this Agreement and the other documents executed pursuant hereto or in connection herewith.

  • Limitation on Changes in Fiscal Periods Permit the fiscal year of the Borrower to end on a day other than December 31 or change the Borrower's method of determining fiscal quarters.

  • Changes in Benefits The Bank shall not make any changes in such plans, benefits or privileges previously described in Section 3(c), (d) and (e) which would adversely affect the Executive's rights or benefits thereunder, unless such change occurs pursuant to a program applicable to all executive officers of the Bank and does not result in a proportionately greater adverse change in the rights of, or benefits to, the Executive as compared with any other executive officer of the Bank. Nothing paid to Executive under any plan or arrangement presently in effect or made available in the future shall be deemed to be in lieu of the salary payable to Executive pursuant to Section 3(a) hereof.

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