Product life cycle

agent vi products’ end of life policy is explained below, allowing customers to better plan and manage the transition process from their existing agent vi installation to newer product versions as they become available this policy explains the type of support services available at agent vi for licensed software at various points during the applicable product’s life cycle the rendering of support services by agent vi may be subject to additional terms and conditions end of life policy this end of life (eol) policy is effective as of january 1, 2010 the eol process guides the final operations associated with the product life cycle, and consists of a series of technical and business milestones and activities that, once completed, make a product obsolete by the end of the process, the product will typically have been replaced by a newer version or other product with similar functionality once obsolete, the product is no longer sold, manufactured, improved, repaired, supported or maintained this policy is intended as a “guideline” as agent vi reserves the right to treat each product line independently, or agree to new or different terms with individual parties agent vi also reserves the right to change this policy at any time without notice the general policy guidelines are as follows a product enters the eol state by either being discontinued or by a newer software version being released the general software life cycle is as follows major release (example version 3 x > 4 x) after the release date of a major release, the previous major release will start its eol transition process minor release (example version 4 1 > 4 2) after 2 minor releases or 18 months (whichever comes first), a minor release will begin its eol transition process end of sale notice period as a general rule, agent vi will provide three (3) months’ notice of the affected product’s end of sale (eos) date and/or the last day when the affected product can be ordered this notice will appear on agent vi’s website (below), and you are encouraged to visit this page regularly to review the information regarding the eol program the eos date represents the final date after which the product can no longer be ordered through agent vi’s point of sale mechanisms end of life transition period three (3) months after notice of the affected product’s eos date, the affected product starts an eol transition period of six (6) months during this transition period, entitled customers will receive maintenance and support for the affected product limited support period at the end of the eol transition period, the limited support period (lsp) will begin during the lsp, which lasts 6 months, agent vi will still assist entitled customers regarding eol products, but will not create software fixes to solve problems associated with the product version; it may be necessary for a customer to upgrade to a non eol software version to correct a reported problem and/or for the purpose of migration to a supported agent vi product software upgrade plan customers can upgrade to more current software versions, which have not entered eol period, through agent vi's software upgrade plan (sup) go to support policy docid\ cycffwcith7kbdcofffqt for further details about the sup support entitlement agent vi provides support to various customers based on individual support agreements and a general support policy please click the link to review agent vi's support policy docid\ cycffwcith7kbdcofffqt milestones of agent vi’s end of life policy end of sale notice period end of sale date end of life transition period limited support period 3 months x 6 months 6 months end of life products product name product version end of sale date innovi edge model 200 1 jan 19 product name product version end of sale date savvi version 5 0 1 oct 14 savvi version 5 1 1 feb 15 savvi version 5 2 1 jul 15 savvi version 5 3 1 jul 18 savvi version 5 4 27 apr 20 savvi version 5 5 31 mar 21 bi portal savvi 5 3 & 5 4 1 apr 18 product name product version end of sale date vi system version 3 2 1 jun 10 vi system version 3 3 0 1 dec 11 vi system version 3 3 sp1 1 jan 13 vi system version 3 3 sp2 1 jan 13 vi system version 4 0 30 dec 13 vi system version 4 1 1 jan 14 vi system version 4 2 30 jun 15 product name product version end of sale date vi search version 1 0 1 jan 13 vi search version 1 1 1 jan 13 vi search version 1 2 1 jan 14 vi search version 2 1 30 jun 15 vi search offline all versions 31 dec 19