Changes Initiated by Spansion Sample Clauses

Changes Initiated by Spansion. Within ten (10) business days after AMD receives a request from Spansion for a Change, either AMD or a joint project team working on the Service to be impacted, as appropriate, shall prepare and provide to Spansion an initial written proposal for the Change (a “Change Proposal”), which proposal will include AMD’s initial proposals regarding (A) the Services and the applicable schedule for performing the Services, including but not limited to Spansion’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 Spansion 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, Spansion shall either approve the Change Proposal, notify AMD that Spansion desires to discuss the Change Proposal further, or withdraw the request for such 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 the Change Proposal, and the Change shall not be implemented.
Sample 1Sample 2Sample 3See All (6)
AutoNDA by SimpleDocs
Changes Initiated by Spansion. Within ten (10) business days after Fujitsu receives a request from Spansion for a Change, either Fujitsu or a joint project team working on the Service to be impacted, as appropriate, shall prepare and provide to Spansion an initial written proposal for the Change (a “Change Proposal”), which proposal will include Fujitsu’s initial proposals regarding (A) the Services and the applicable schedule for performing the Services, including but not limited to Spansion’s related obligations, to effect the Change, (B) the applicable Service Levels resulting from the Change, (C) the resources required to perform Services effecting the Change and resulting from the Change, (D) the Fees for Services, and (E) any additional Systems or 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 Spansion will incur as a result of the Change that it would otherwise not have incurred. Fujitsu will also indicate the areas of the Change Proposal where additional analysis may be required to complete the Change Proposal. On a schedule to be agreed upon by the Parties in the circumstances, but presumed not to exceed thirty (30) days after receipt of Spansion’s request, Fujitsu will deliver to Spansion a completed Change Proposal. Within ten (10) business days after receiving such Change Proposal, Spansion shall either approve the Change Proposal, notify Fujitsu that Spansion desires to discuss the Change Proposal further, or withdraw the request for such Change. Spansion’s failure to approve the Change Proposal or notify Fujitsu that Spansion 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.
Sample 1Sample 2See All (4)
Changes Initiated by Spansion. Concurrent with the submission of a request for a Change by Spansion, either Spansion or a joint project team working on the impacted Service, as appropriate, shall provide to AMD a Change Proposal containing the information specified in subparagraph (i) above. Within ten (10) business days after receiving such proposal, AMD shall either approve the Change Proposal, notify Spansion that AMD desires to discuss the Change Proposal further, or reject the requested 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 such request, and the Change shall not be implemented.
Sample 1Sample 2Sample 3

Related to Changes Initiated by Spansion

  • MINOR CHANGES IN THE WORK 7.4.1 The Architect will have 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. Such changes shall be effected by written order and shall be binding on the Owner and Contractor. The Contractor shall carry out such written orders without delay.

  • 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.

  • Execution of Change Orders Change Orders shall be signed by the Contractor, ordinarily certified by the Design Professional, and approved by the Owner in accordance with the form of Change Order prescribed by the Owner. No request for payment by the Contractor for a Change Order shall be due, nor shall any such request appear on an Application for Payment, until the Change Order is executed by the Owner. In the event of emergency (see Article 1.4.4) or significant impact to the Overall Project Schedule, the Owner shall direct the Change Order to proceed upon a Force Account until the cost and time is resolved in the manner set forth in Paragraph 3.2.7.3 below.

  • 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.

  • CONTRACT ITEM CHANGES A. If a manufacturer discontinues a contracted item, that item will automatically be considered deleted from the contract with no penalty to Contractor. However, H-GAC may at its sole discretion elect to make a contract award to the next lowest Respondent for the item, or take any other action deemed by H-GAC, at its sole discretion, to be in the best interests of its Customers.

  • Shift Changes When an employee is assigned to a specific shift and that assignment is changed, the employee shall be given seven (7) calendar days’ notice prior to the change.

  • Changes in the Work § 6.3.1 The Owner may, without invalidating the Contract, order changes in the Work within the general scope of the Contract consisting of additions, deletions or other revisions. The Owner shall issue such changes in writing. The Construction Manager may be entitled to an equitable adjustment in the Contract Time as a result of changes in the Work.

  • Service Changes PBI may modify its Service by giving written notice to you (a “Service Change Notice”), which will state whether the change is material. After receiving a Service Change Notice, if the change is material, you may terminate Service by giving us a termination notice at the address indicated in Section 22 or you may create a case at xxxxxxxxxxx.xxx/xx/xxxxxxx-xx.xxxx (follow the instructions under “how to create a case”).

  • 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.

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