Product Lifecycle Management Sample Clauses

Product Lifecycle Management. Famic implements a lifecycle based on the following stages for any version of a Product: Availability: Date on which a version of a Product is available for sale. Activation: Date on which Licenses are sent by Famic to User. Commercial End: The Commercial End of a version of a Product generally occurs two (2) years after Availability of said version. After this date, the User will no longer be able to order this version of the Product. End of Support: The End of Support for a version of a Product will be indicated on Famic’s website xxxxx://xxx.xxxxxxxxx.xxx, after the Commercial End of said version. After this date, the User will no longer be able to submit support requests regarding this version of the Product. All Users are informed of this date at least six (6) months in advance. No support for the concerned version of the Product is offered after this date.
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Product Lifecycle Management. The parties agree to conduct reviews at least once per [ * ] to evaluate: (a) [ * ] and [ * ] to the Products to ensure customer satisfaction; (b) [ * ] and [ * ] orders; (c) [ * ] to [ * ] Product [ * ] and [ * ]; (d) [ * ] opportunities and (e) [ * ] decisions regarding particular versions of the Product and the [ * ] of support with respect to such Product versions. For Product changes to be implemented following such reviews, the schedule, allocation of costs (if any), and other details for such changes shall be set forth in change orders agreed upon by the parties. Motorola will provide Danger written notice, at least [ * ] prior to discontinuing production (“end of life”) of a Product or parts for a Product.
Sample 1Sample 2
Product Lifecycle Management. Sharp and Danger agree to conduct reviews at least once per quarter to evaluate: (a) bug fixes and necessary enhancements to the Danger Software and each Party’s Product Designs to ensure customer satisfaction; (b) hardware changes and engineering change orders; (c) feature upgrades to enhance Product positioning and drive additional sales; (d) expense reduction opportunities and (e) end-of-life decisions regarding particular versions of the Product and the eventual phase out of support with respect to such Product versions. Sharp will provide Danger at least six (6) months notice prior to discontinuing production (“end of life”) of a Product or parts for a Product.
Sample 1Sample 2

Related to Product Lifecycle Management

  • Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity 1.1.02 Identify at least one individual to act as the program contact in the following areas: 1. Immunization Program Manager;

  • Project Management Plan Developer is responsible for all quality assurance and quality control activities necessary to manage the Work, including the Utility Adjustment Work. Developer shall undertake all aspects of quality assurance and quality control for the Project and Work in accordance with the approved Project Management Plan and

  • Program Monitoring The Contractor will make all records and documents required under this Agreement as outlined here, in OEC Policies and NHECC Policies available to the SRO or its designee, the SR Fiscal Officer or their designee and the OEC. Scheduled monitoring visits will take place twice a year. The SRO and OEC reserve the right to make unannounced visits.

  • Marketing Services The Manager shall provide advice and assistance in the marketing of the Vessels, including the identification of potential customers, identification of Vessels available for charter opportunities and preparation of bids.

  • Contract Management Contractor shall report to the Health and Human Services Agency Director or his or her designee who will review the activities and performance of the Contractor and administer this Contract.

  • Virus Management DST shall maintain a malware protection program designed to deter malware infections, detect the presence of malware within DST environment.

  • Quality Management System Supplier hereby undertakes, warrants and confirms, and will ensue same for its subcontractors, to remain certified in accordance with ISO 9001 standard or equivalent. At any time during the term of this Agreement, the Supplier shall, if so instructed by ISR, provide evidence of such certifications. In any event, Supplier must notify ISR, in writing, in the event said certification is suspended and/or canceled and/or not continued.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Project Management Project Management Institute (PMI) certified project manager executing any or all of the following: • Development of Project Charter • Development of project plan and schedule • Coordination and scheduling of project activities across customer and functional areas • Consultation on operational and infrastructure requirements, standards and configurations • Facilitate project status meetings • Timely project status reporting • Address project issues with functional areas and management • Escalation of significant issues to customers and executive management • Manage project scope and deliverable requirements • Document changes to project scope and schedule • Facilitate and document project closeout

  • STATEWIDE CONTRACT MANAGEMENT SYSTEM If the maximum amount payable to Contractor under this Contract is $100,000 or greater, either on the Effective Date or at any time thereafter, this section shall apply. Contractor agrees to be governed by and comply with the provisions of §§00-000-000, 00-000-000, 00-000-000, and 00- 000-000, C.R.S. regarding the monitoring of vendor performance and the reporting of contract information in the State’s contract management system (“Contract Management System” or “CMS”). Contractor’s performance shall be subject to evaluation and review in accordance with the terms and conditions of this Contract, Colorado statutes governing CMS, and State Fiscal Rules and State Controller policies.

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