Development of Specifications Sample Clauses

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
AutoNDA by SimpleDocs
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
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. 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
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.
Sample 1
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

Related to Development of Specifications

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

  • 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 Packaging process shall be deemed a Specification change. No change in the Specifications shall be implemented by PCI, whether requested by Client, requested by PCI 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 Pricing). PCI 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, PCI 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. PCI reserves the right to postpone effecting changes to the Specifications, or in the case of changes requested or required by any Regulatory Authority postpone Packaging under this Agreement, until such time as the parties agree to and execute the required written amendment.

  • Specifications That part of the Contract Documents consisting of written requirements for materials, equipment, systems, standards, and workmanship as applied to the Work, and certain administrative requirements and procedural matters applicable thereto. The term "Specifications" shall also include all written matter in the Project Manual or on the drawings and any Addenda or Change Orders thereto.

  • Commercialization Reports Throughout the term of this Agreement and during the Sell-Off Period, and within thirty (30) days of December 31st of each year, Company will deliver to University written reports of Company’s and Sublicensees’ efforts and plans to develop and commercialize the innovations covered by the Licensed Rights and to make and sell Licensed Products. Company will have no obligation to prepare commercialization reports in years where (a) Company delivers to University a written Sales Report with active sales, and (b) Company has fulfilled all Performance Milestones. In relation to each of the Performance Milestones each commercialization report will include sufficient information to demonstrate achievement of those Performance Milestones and will set out timeframes and plans for achieving those Performance Milestones which have not yet been met.

  • Development Schedule The Project shall substantially comply with the specific timetables and triggers for action set forth in Article 5 of this Agreement. The parties acknowledge that, as provided in G.S. 160A-400.25(b), the failure to meet a commencement or completion date shall not, in and of itself, constitute a material breach of this Agreement pursuant to G.S. 160A-400.27 but must be judged based upon the totality of the circumstances.

  • Product Specifications The Company agrees that all Products sold to Xxxx hereunder shall conform to the respective specifications set forth on Schedule A or to such other specifications as are from time to time agreed upon by the Parties.

  • Project Scope The physical scope of the Project shall be limited to only those capital improvements as described in Appendix A of this Agreement. In the event that circumstances require a change in such physical scope, the change must be approved by the District Committee, recorded in the District Committee's official meeting minutes, and provided to the OPWC Director for the execution of an amendment to this Agreement.

  • Development Plan document specifying the work program, schedule, and relevant investments required for the Development and the Production of a Discovery or set of Discoveries of Oil and Gas in the Contract Area, including its abandonment.

  • Development Reports Beginning six months after Effective Date and ending on the date of first commercial sale of a Licensed Product in the United States, LICENSEE shall report to Cornell progress covering LICENSEE's (and Affiliate's and Sublicensee's) activities and efforts in the development of rights granted to LICENSEE under this Agreement for the preceding six months. The report shall include, but not be limited to, activities and efforts to develop and test all Licensed Products and obtain governmental approvals necessary for marketing the same. Such semi-annual reports shall be due within sixty days (60) of the reporting period and shall use the form as provided herein as Appendix C.

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