Development of Specifications Sample Clauses

Development of Specifications. G3 and Spectre will jointly develop mutually acceptable final specifications for the Games and the Deliverables (the “Specifications”). Any change in the Specifications after their adoption will be accomplished pursuant to paragraph b (Change in Specifications) below. If the parties cannot agree to Specifications for any or all of the Games and their related Deliverables (including a change in the Specifications pursuant to paragraph b below), either party will have the right to terminate this Agreement upon three days notice, subject to Spectre’s continuing royalty payment obligation pursuant to Section 7 below.
Sample 1Sample 2
AutoNDA by SimpleDocs
Development of Specifications. The Specifications may be modified or amended by mutual written agreement of the Parties. In the event that TearLab requests changes to the Specifications MiniFAB agrees to use Commercially Reasonable Efforts to accommodate such requested changes.
Sample 1Sample 2
Development of Specifications. Specifications for work and deliverables shall be in accordance with the terms of this Agreement and its Attachments, unless and to the extent expressly modified by a Contract Change Form, Supplemental Agreement, or Project Work Order.
Sample 1Sample 2
Development of Specifications. Customer shall have primary responsibility for the definition of the Software and the development of the functional objectives to be included in the Specifications for each of their Projects. Developer shall have primary responsibility for the development of the technical means for accomplishing such functional objectives, also to be included in the Specifications. The parties shall use their best commercial efforts to prepare their respective portions of the Specifications as promptly as possible. Once the Developer has completed the Specifications it shall submit them to the Customer for final review and acceptance. Specifications will be final when approved by Customer. In the event Developer believes that any change in Specification will have more than a de minimis affect the work being performed by Developer hereunder, Developer shall promptly notify Customer of such affect, including any impact on the Development Schedule and the costs to be incurred by the parties hereunder.
Sample 1
Development of Specifications. (1) Promptly after TearLab’s Acceptance of a New Product as set forth in clause 5.9, MiniFAB shall prepare, on the basis of the most recent Requirement Definitions for such New Product, and provide to TearLab for approval, the definitive Specifications for the applicable Product, for MiniFAB’s use to manufacture, package, label, store and handle the applicable Product. (2) TearLab will review the Specifications submitted by MiniFAB under clause 3.1(1) and may request amendments or modifications to the Specifications if: (a) the Specifications are inconsistent with the Requirement Definitions; (b) the Specifications are inconsistent with the Regulatory Requirements; (c) the requirements of the Specifications are unreasonable or uncommercial having regard to the Price or proposed Price of the relevant Product; or (d) the requirements of the Specifications are unrelated to the Product. (3) MiniFAB must act reasonably and accommodate any requests for amendment to the Specifications made by TearLab under clause 3.1(2). (4) TearLab must accept the Specifications when it is satisfied that the Specifications are consistent with the Requirement Definitions and the Regulatory Requirements, and are reasonable and commercial having regard to the Price or proposed Price of the relevant Product. (5) The Specifications for any Product may be modified or amended by mutual written agreement of the Parties. In the event that TearLab requests changes to the Specifications for reasons other than those set forth in clause 3.1(2) above, MiniFAB agrees to use Commercially Reasonable Efforts to accommodate such requested changes.
Sample 1
Development of Specifications. The CDP fosters the development and evolution of high-quality specifications for the OEC Platform components and interoperability with the same, using a consensus-based approach that produces a specification, project code, a reference implementation (to prove the specification can be implemented), and a technology compatibility kit (typically consisting of a suite of tests, tools, and documentation that is used to test implementations for compliance with the specification).
Sample 1

Related to Development of Specifications

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK

  • Quality Specifications SANMINA-SCI shall comply with the quality specifications set forth in its Quality Manual, incorporated by reference herein, a copy of which is available from SANMINA-SCI upon request.

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

  • General specifications For the purpose of this Regulation, the vehicle shall fulfil the following requirements:

  • The Specifications The Specifications are that portion of the Contract Documents consisting of the written requirements for materials, equipment, systems, standards and workmanship for the Work, and performance of related services.

  • 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 December 31, 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 December 31, 2021, Interconnection Customer must demonstrate that all generating units have been delivered to Interconnection Customer’s project site.

  • Changes to Specifications All Specifications and any changes thereto agreed to by the parties from time to time shall be in writing, dated and signed by the parties. Any change to the Process shall be deemed a Specification change. No change in the Specifications shall be implemented by Catalent, whether requested by Client or requested or required by any Regulatory Authority, until the parties have agreed in writing to such change, the implementation date of such change, and any increase or decrease in costs, expenses or fees associated with such change (including any change to Unit Pricing). Catalent shall respond promptly to any request made by Client for a change in the Specifications, and both parties shall use commercially reasonable, good faith efforts to agree to the terms of such change in a timely manner. As soon as possible after a request is made for any change in Specifications, Catalent shall notify Client of the costs associated with such change and shall provide such supporting documentation as Client may reasonably require. Client shall pay all costs associated with such agreed upon changes. If there is a conflict between the terms of this Agreement and the terms of the Specifications, this Agreement shall control. Catalent reserves the right to postpone effecting changes to the Specifications until such time as the parties agree to and execute the required written amendment.

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Protocols Each party hereby agrees that the inclusion of additional protocols may be required to make this Agreement specific. All such protocols shall be negotiated, determined and agreed upon by both parties hereto.

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