Definition of SAM - EOL (End of Life) and EOS (End of Support)

[Dale W]

Looking for the EOL/EOXS/EOS definitions.

I've searched for quite some time - I cannot find ServiceNow's glossary/definition of terms that include End of Life (EOL) and End of Support (EOS).   Not all companies/publishers use the same terms/reference and I'd like to know how ServiceNow Define these in the 'End of Life Products'.   I did find links, and the Developer Glossary, but it doesn't include these terms.  

As an FYI, this is how i use these terms, being careful of the EOS, since it can mean more than what I have listed in my short-list, below.

• EOS – End of Support  (this is he paid/support date, usually yearly and allows you to get tech. answers and free upgrades -also when you lose the right to use Subscription software)
  • End of Subscription (when you lose the right to use Subscription software)
  • End of Service -  (I prefer to use EOM to avoid ‘EOS’ confusion – when it’s no longer supported/patched for vulnerabilities)
  • End of Sale - (See EOA)
• EOxS – End of Extended Support (premium cost to keep things supported/patched, past the ‘General EOS/EOM’ dates)
• EOM -End of Maintenance (the date something is no longer supported/patched for vulnerabilities)  
• EOSL – End of Service Life -  usually, same as EOM
• EOL -  End of Life (The date the publisher will not answer questions, allow trade-ins, renew support, or allow downgrades)
• EOA – End of availability (the last date the public can purchase the App/version,  some use End of Sale) 

Thanks. 

[Dale W]

Found the info in a PDF:

Software Product Lifecycle related list
Field	Description
Publisher	Name of publisher.
Product	Name of the software product.
Version	Licensable version of the software
Edition	Edition of the software.
Full Version	The granular licensable version of the software.
Phase start date	Date the life-cycle phase starts.
Lifecycle type	Lifecycle type values include:
	Internal
	Publisher
Risk	The risk level to an organization with regards to the lifecycle phase. For example, the risk for the end of support phase for a publisher maybe moderate or the end of life phase maybe high.
	Risk type values include:
	Very High
	High
	Moderate
	Low
	None
Lifecycle phase	Lifecycle phase values include:
	Pre Release: Date the software was pre-released.
	General Availability: Date the software became generally available to the market.
	Upgrade
	Note: Only shown when theLifecycle
	type field is Internal.
	End of Life: Date by which the software will no longer be manufactured by the publisher.
	End of Support: Date by which the software will not be enhanced by the publisher.
	End of Extended Support: Date by which the publisher will no longer provide any support or updates to the software
Active	Indicates if the lifecycle is to be considered or not while evaluating the risk of the software.
	Note: By default, only active lifecycles are displayed.
Source	Source of the lifecycle. If the record is created manually, it's set to Internal. If it's created automatically, the field is set to ServiceNow.
Description	Description of the software product lifecycle.

[Lionel Falk]

Dear @Dale W 

Following this initial query and for the same topic, I was wondering if you could also explain how the risk assessment is done within ServiceNow? How the risk for a software product is qualified as "high" or "very high"? Apparently this is not related to the lifecycle status. Thank you.