Changes Initiated by Spansion Clause Samples

The "Changes Initiated by Spansion" clause grants Spansion the right to make modifications to the products, specifications, or processes covered by the agreement. In practice, this means Spansion can update product designs, alter manufacturing methods, or revise technical requirements, often with a requirement to notify the other party within a specified timeframe. This clause ensures Spansion retains flexibility to improve or adapt its offerings while managing the impact of such changes on its contractual relationships.
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 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. AMD 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, AMD 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 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.
View SourceView Similar (11)
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.
View SourceView Similar (3)

Related to Changes Initiated by Spansion

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

  • COMPLETION OF MEET AND NEGOTIATION 24.1 During the term of this Agreement, the Association expressly waives and relinquishes the right to meet and negotiate and agrees that the District shall not be obligated to meet and negotiate with respect to any subject or matter whether referred to or covered in this Agreement or not, even though each subject or matters may not have been within the knowledge or contemplation of either or both the District or the Association at the time they met and negotiated on and executed this Agreement, and even though such subjects or matters were proposed and later withdrawn.

  • Access to Work District representatives shall at all times have access to the Work, wherever it is, in preparation or in progress. Contractor shall provide safe and proper facilities for such access.

  • Access to Work Locations Reasonable access to employee work locations shall be granted officers of the Association and their officially designated representatives for the purpose of processing grievances or contacting members of the Association concerning business within the scope of representation. Such officers or representatives shall not enter any work location without the consent of the City Manager. Access shall be restricted so as not to interfere with the normal operations of the department or with established safety or security requirements. Solicitation of membership and activities concerned with the internal management of the Association, such as collecting dues, holding membership meetings, campaigning for office, conducting elections and distributing literature, shall not be conducted during working hours.