Product Lifecycle Management Sample Clauses
The Product Lifecycle Management clause defines the processes and responsibilities for overseeing a product from its initial development through to its retirement. It typically outlines how products are introduced, maintained, updated, and eventually phased out, specifying roles for monitoring performance, implementing improvements, and managing end-of-life procedures. This clause ensures that all parties understand their obligations throughout the product's lifespan, promoting efficiency, compliance, and smooth transitions at each stage of the product's existence.
POPULAR SAMPLE Copied 11 times
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 ▇▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇▇▇.▇▇▇, 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.
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.
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.