Standard Software Titles and Expansion Packs Sample Clauses

Standard Software Titles and Expansion Packs. Publisher shall submit to Microsoft, at least [****] for a Standard Software Title or an Expansion Pack, a completed and signed “Xbox 360 Royalty Tier Selection Form” in the form attached to this Agreement as Exhibit 2 for each Sales Territory. The selection indicated in the Xbox 360 Royalty Tier Selection Form will only be effective once it has been approved by Microsoft. If a Standard Software Title or Expansion Pack does not have an approved Xbox 360 Royalty Tier Selection Form as required hereunder (e.g. as a result of the Publisher not providing a Xbox 360 Royalty Tier Selection Form or because Microsoft has not approved the Xbox 360 Royalty Tier Selection Form), the royalty rate for such Standard Software Title will default to [****] or for such Expansion Pack will default to [****], regardless of the actual Threshold Price (i.e., if Microsoft does not approve an Xbox 360 Royalty Tier Selection Form because it is filled out incorrectly, the royalty rate will default to [****]). Except as set forth in Section 2 (Hits Programs), the selection of a royalty tier for a Standard Software Title or Expansion Pack in a Sales Territory is binding for the life of that Software Title or Expansion Pack even if the Threshold Price is reduced following the Software Title’s Commercial Release.
Sample 1Sample 2See All (6)
AutoNDA by SimpleDocs
Standard Software Titles and Expansion Packs. Publisher shall submit to Microsoft, at **** for a Standard Software Title or an Expansion Pack, a completed and signed “Xbox 360 Royalty Tier Selection Form” in the form attached to the Xbox 360 PLA as Exhibit 2 (or updated through the Xbox 360 Publishers Guide) for each Sales Territory. The selection indicated in the Xbox 360 Royalty Tier Selection Form (or designated electronic form method) will only be effective once it has been approved by Microsoft. If a Standard Software Title or Expansion Pack does not have an approved Xbox 360 Royalty Tier Selection Form as required hereunder (e.g. as a result of the Publisher not providing a Xbox 360 Royalty Tier Selection Form or because Microsoft has not approved the Xbox 360 Royalty Tier Selection Form), the royalty rate for such Standard Software Title will default to **** or for such **** Confidential portion omitted and filed separately with the Securities and Exchange Commission. Expansion Pack will default to Packs ****, regardless of the actual Threshold Price (i.e., if Microsoft does not approve an Xbox 360 Royalty Tier Selection Form because it is filled out incorrectly, the royalty rate will default to ****. Except as set forth in Section 2 (Hits Programs), the selection of a royalty tier for a Standard Software Title or Expansion Pack in a Sales Territory is binding for the life of that Software Title or Expansion Pack even if the Threshold Price is reduced following the Software Title's Commercial Release.
Sample 1See All (4)
Standard Software Titles and Expansion Packs. Publisher will submit to Microsoft, at least [***] business days before placing the first manufacturing order for a Standard Software Title or an Expansion Pack, a completed “Durango Royalty Tier Selection Form” in the form provided via the Durango Publisher Guide (which may be a designated electronic form) for each Sales Territory. The selection indicated in the Durango Royalty Tier Selection Form will only be effective once it has been approved by Microsoft. If a Standard Software Title or Expansion Pack does not have an approved Durango Royalty Tier Selection Form (e.g. as a result of the Publisher not providing a Durango Royalty Tier Selection Form or because Microsoft has not approved the Durango Royalty Tier Selection Form), the royalty rate for such Standard Software Title will default to [***] or for such Expansion Pack will default to [***], regardless of the actual Threshold Price (i.e., if Microsoft does not approve an Durango Royalty Tier Selection Form because it is filled out incorrectly, the royalty rate will default to [***].
Sample 1Sample 2
Standard Software Titles and Expansion Packs. Publisher shall submit to Microsoft, at least [***] business days before placing the first manufacturing order for a Standard Software Title or an Expansion Pack, a completed and signed “Xbox 360 Royalty Tier Selection Form” in the form attached to this Agreement as Exhibit 2 (as may be updated via the Xbox 360 Publisher Guide) for each Sales Territory. The selection indicated in the Xbox 360 Royalty Tier Selection Form (or designated electronic form method) will only be effective once it has been approved by Microsoft. If a Standard Software Title or Expansion Pack does not have an approved Xbox 360 Royalty Tier Selection Form as required hereunder (e.g., as a result of the Publisher not providing an Xbox 360 Royalty Tier Selection Form or because Microsoft has not approved the Xbox 360 Royalty Tier Selection Form), the royalty rate for such Standard Software Title will default to Tier [***] or for such Expansion Pack will default to Packs Tier [***], regardless of the actual Threshold Price (i.e., if Microsoft does not approve an Xbox 360 Royalty Tier Selection Form because it is filled out incorrectly, the royalty rate will default to Tier [***]). Except as set forth in Section 2 (Hits Programs), the selection of a royalty Tier for a Standard Software Title or Expansion Pack in a Sales Territory is binding for the life of that Software Title or Expansion Pack even if the Threshold Price is reduced following the Software Title’s Commercial Release. 1. [***] days after Commercial Release of an FPU in a Sales Territory, Publisher may elect to change the previously elected Royalty Tier for such Software Title to any other valid Royalty Tier set forth in Table 2 (e.g., migrate from Tier A to Tier B or from Tier A to Tier D) in the same Sales Territory. A minimum of [***] days must elapse before Publisher is permitted to make an additional Royalty Tier migration. Software Titles must meet all MOQs to receive approval for a Royalty Tier migration. The Multi-Game Pack program does not support Royalty Tier migration. 2. Publisher must submit to Microsoft, at least [***] business days before placing the first manufacturing order under the new Royalty Tier, a completed and signed Xbox 360 Royalty Tier Migration Form in the form attached to this Agreement as Exhibit 7 (as may be updated via Xbox 360 Publisher Guide which may require electronic submission) for each Sales Territory. Unit Discount accumulation restarts with each Royalty Tier migration.
Sample 1Sample 2
Standard Software Titles and Expansion Packs. Publisher shall submit to Microsoft, at least **** before placing the first manufacturing order for a Standard Software Title or an Expansion Pack, a completed and signed “Xbox 360 Royalty Tier Selection Form” in the form attached to this Agreement as Exhibit 2 for each Sales * Confidential portion omitted and filed separately with the Securities and Exchange Commission.
Sample 1

Related to Standard Software Titles and Expansion Packs

  • Standard Work Week The standard work week for full-time employees covered by this Agreement shall be forty (40) hours, exclusive of the time allotted for meal periods, consisting of five (5) consecutive work days followed by two (2) consecutive days off. The week shall commence with the shift that includes 12:01 A.M. Sunday of each calendar week and end at the start of the shift that includes 12:00 midnight the following Saturday. The Employer retains the right to modify the work schedules to meet operational needs.

  • Technical Specifications and Drawings a) The Goods and Related Services supplied under this Contract shall conform to the technical specifications and standards mentioned in Section VI, Schedule of Requirements and, when no applicable standard is mentioned, the standard shall be equivalent or superior to the official standards whose application is appropriate to the Goods' country of origin. b) The Supplier shall be entitled to disclaim responsibility for any design, data, drawing, specification or other document, or any modification thereof provided or designed by or on behalf of the Procuring Entity, by giving a notice of such disclaimer to the Procuring Entity. c) Wherever references are made in the Contract to codes and standards in accordance with which it shall be executed, the edition or the revised version of such codes and standards shall be those specified in the Schedule of Requirements. During Contract execution, any changes in any such codes and standards shall be applied only after approval by the Procuring Entity and shall be treated in accordance with GCC Clause 33.

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • Alternative Work Schedules Employees may request alternative work schedules such as a nine (9) day - 80 hour two week schedule or a four (4) day - 40 hour week schedule. Management will respond to an employee's request within 15 calendar days. Any changes from existing work schedules will be based on the needs of the service as determined by Management. Employees covered by the Fair Labor Standards Act will not be placed on alternate work schedules that mandate the payment of overtime under the Act.

  • MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.

  • Contract Database Metadata Elements Title: Xxxxxxx-Xxx Xxxxx Central School District and Xxxxxxx-Xxx Xxxxx Teachers Association (2007)

  • Project Specific Milestones In addition to the milestones stated in Section 212.5 of the Tariff, as applicable, during the term of this ISA, Interconnection Customer shall ensure that it meets each of the following development milestones: 6.1 Substantial Site work completed. On or before October 1, 2020, Interconnection Customer must demonstrate completion of at least 20% of project site construction. At this time, Interconnection Customer must submit to Interconnected Transmission Owner and Transmission Provider initial drawings, certified by a professional engineer, of the Customer Interconnection Facilities. 6.2 Delivery of major electrical equipment. On or before October 1, 2020, Interconnection Customer must demonstrate that all generating units have been delivered to Interconnection Customer’s project site.

  • Construction Documents Phase Services 3.4.1 Based on the Owner’s approval of the Design Development Documents, and on the Owner’s authorization of any adjustments in the Project requirements and the budget for the Cost of the Work, the Architect shall prepare Construction Documents for the Owner’s approval. The Construction Documents shall illustrate and describe the further development of the approved Design Development Documents and shall consist of Drawings and Specifications setting forth in detail the quality levels and performance criteria of materials and systems and other requirements for the construction of the Work. The Owner and Architect acknowledge that, in order to perform the Work, the Contractor will provide additional information, including Shop Drawings, Product Data, Samples and other similar submittals, which the Architect shall review in accordance with Section 3.6.4.

  • Hardware and Software Requirements In order to access and retain Disclosures electronically, you must satisfy the following computer hardware and software requirements: access to the Internet; an email account and related software capable of receiving email through the Internet; a web browser which is SSL-compliant and supports secure sessions, and hardware capable of running this software.

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