UPDATES AND BUG FIXES Sample Clauses

UPDATES AND BUG FIXES. The Contributor does not undertake to update the Contribution or to fix problems which subsequently emerge with it. However, any such updates or bug fixes provided to NAG after the initial Contribution is delivered will be deemed to be part of the Contribution and so to be covered by this agreement.
Sample 1Sample 2
AutoNDA by SimpleDocs
UPDATES AND BUG FIXES. Maintenance Agreements are required for the first year on all new Licensed Software sold. Subsequent maintenance renewal is optional. OEM Partner shall pay Synopsys the maintenance fees set forth in Exhibit B. Updates and Bug Fixes shall be provided to OEM Partner in regular maintenance releases. Maintenance releases will be provided every six (6) months or whenever Synopsys, using reasonable commercial efforts, issues them. Only End Users who have entered into Maintenance Agreements may receive maintenance releases. Upgrades are not automatically included in maintenance releases. Critical bugs (to be defined by the parties) reported by OEM Partner will be addressed by Synopsys' engineering support team on a high priority basis. Bug Fixes will be delivered to OEM Partner at the earliest possible date for OEM Partner to provide to End Users: provided, however, that Synopsys will provide such Bug Fixes to OEM Partner when it makes them generally available to its other resellers and OEM partners. OEM Partner will be entitled, directly or indirectly through OEM Partner's Resellers, to distribute Bug Fixes and Updates to each End User of OEM Partner or OEM Partner's Reseller who is a party to a maintenance Agreement for the same, or Bug Fixes to each such end User to whom a warranty obligation is owed.
Sample 1
UPDATES AND BUG FIXES. Various types of updates are performed on the VotingCrowd system on an ongoing basis. These might include, but not be limited to, updates such as new system functionality, bug fixes on existing functionality, developer tool updates and server software maintenance and updates. We do test all updates as thoroughly as possible in a test environment, however there is always a chance that an update might influence existing functionality. Please inform us on xxxxx@xxxxxxxxxxx.xx.xx, of any scenario where you feel that the system is not working as intended or that something that use to work is no longer functioning correctly. We will endeavor to get the problem rectified as soon as possible.
Sample 1
UPDATES AND BUG FIXES. Evergreen shall maintain ECential and correct bugs and programming errors in ECential. Within a commercially reasonable time, Evergreen shall provide maintenance fixes, corrections, and patches to Caldera for distribution by Caldera to end users under licenses sold by Caldera. Such maintenance fixes, corrections, and patches shall be governed by this Agreement as part of ECential. When possible, Evergreen shall provide work-around solutions and temporary fixes as soon as possible while Caldera and end users are awaiting such maintenance fixes, corrections, and patches. Caldera shall use commercially reasonable efforts to provide to Evergreen information known to Caldera necessary (including, where appropriate, reproducible test cases and other diagnostic information) to diagnose and correct or repair such problems as Caldera may report to Evergreen. Caldera makes the same promises to Evergreen. Evergreen shall deliver Updates to Caldera as soon as they become available. Updates shall be governed by this Agreement as ECential. Caldera makes the same promises to Evergreen. As Evergreen creates commercial versions of ECential for other operating systems or platforms, Evergreen will also port such commercial versions to OpenLinux and provide the same to Caldera as Updates, provided that the port to OpenLinux is commercially viable. In the event Evergreen elects to not make any such port to OpenLinux, then Caldera may do so at its expense.
Sample 1

Related to UPDATES AND BUG FIXES

  • Updates and Upgrades Contractor grants to the Department a non-exclusive, non-transferable license to use upgrades and updates provided by Contractor during the term of the Contract. Such upgrades and updates are subject to the terms of the Contract. The Department shall download, distribute, and install all updates as released by Contractor during the length of the Contract, and Contractor strongly suggests that the Department also downloads, distributes, and installs all upgrades as released by Contractor during the length of the Contract. Contractor shall use commercially reasonable efforts to provide the Department with work-around solutions or patches to reported software problems that may affect the Department’s use of the software during the length of the Contract.

  • Updates “Updates” are changes that do not require a change to the established Centralized Contract terms and conditions. Updates may include: Centralized Contract changes and updates made in accordance with the previously approved pricing formula (e.g. discount from list price); adding new products or services within the established, previously approved pricing structure; lowering pricing of products or services already on Contract, deleting products or services available through the Centralized Contract, adding product or service that do not fall under the previously established price structure or discounts under the Contract, re-bundled products, and other updates not listed above that are deemed to be in the best interest of the State and do not result in a change to the established Centralized Contract terms and conditions. Updates must be submitted to OGS for review, and must be accompanied by a justification of reasonableness of price if the change results in a change in pricing methodology. OGS will notify Contractor in writing if approved.

  • Training Materials Training Materials will be provided for each student. Training Materials may be used only for either (i) the individual student’s reference during Boeing provided training and for review thereafter or (ii) Customer’s provision of training to individuals directly employed by the Customer.

  • Time and Materials If this contract is designated as a Time and Materials contract, invoicing and payment shall be as follows: (a) Consultant shall submit invoices, not more often than once a month during the term of this agreement, based on the cost for work performed in accordance with the Rate Schedule in the Scope of Work and authorized reimbursable expenses incurred prior to the invoice date. Invoices shall contain the following information: (i) Serial identifications of bills, i.e., Xxxx No. 1; (ii) The beginning and ending dates of the billing period; (iii) A summary containing the total contract amount, the amount of prior xxxxxxxx, the total due this period, percentage of work completed, the remaining balance available for all remaining billing periods, and a brief description of work completed during the billing period. (b) City shall make monthly payments, based on such invoices, for satisfactory progress in completion of the Scope of Work, and for authorized reimbursable expenses incurred.

  • Promotional Materials In the event that the Fund or the Adviser makes available any promotional materials related to the Securities or the transactions contemplated hereby intended for use only by registered broker-dealers and registered representatives thereof by means of an Internet web site or similar electronic means, the Adviser will install and maintain, or will cause to be installed and maintained, pre-qualification and password-protection or similar procedures which are reasonably designed to effectively prohibit access to such promotional materials by persons other than registered broker-dealers and registered representatives thereof.

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

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

  • Development Records Each Party shall maintain complete, current and accurate records of all Development activities conducted by it hereunder, and all data and other information resulting from such activities. Such records shall fully and properly reflect all work done and results achieved in the performance of the Development activities in good scientific manner appropriate for regulatory and patent purposes. Each Party shall document all non-clinical studies and Clinical Trials in formal written study reports according to Applicable Laws and national and international guidelines (e.g., ICH, cGCP, cGLP, and cGMP).

  • Deliverables Upon satisfactory completion of the work authorization, the Engineer shall submit the deliverables as specified in the executed work authorization to the State for review and acceptance.

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