Tech currency audit help
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
17 hours ago
I'm working on a Tech Currency / EOL reporting initiative after an acquisition, and I'm trying to understand what the end-to-end process should look like from a ServiceNow perspective.
The goal is to produce a report that looks like below, refer row 3
For now, forget the App Code and Short Name, its something internal
"Technology" column means models.
What I know so far:
- Most of the asset and technology inventory data is in ServiceNow.
- For SAM, roughly half of the lifecycle information can be sourced from ServiceNow Content Library. The remaining information is being researched manually by our SAM analyst.
- For HAM, it looks like we'll need to identify the hardware owners and obtain EOL/EOS information for devices and infrastructure components.
- There are governance requirements around technology currency. For example:
- If a technology reaches EOL within the next 2 years, is there a remediation request or project in place?
- If EOL is within 6 months, are there additional approvals, exceptions, or remediation activities required?
- If EOL has already passed, should there be a change record, risk acceptance, exception, or remediation plan?
- One thing that confuses me is that for some software technologies we're not tracking actual EOL dates. Instead, the team is populating something closer to a "next upgrade phase" or "next lifecycle milestone."
Can someone help me with this?
Has anyone done this kind of activity before?
Any help would be highly appreciated
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
17 hours ago
@dreinhardt — Will you please take interest in this question?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11 hours ago
Hi @NOW_seeker,
What you're describing for me sounds more like Enterprise Architecture (TPM and TRM) and Integrated Risk Management (IRM) rather than HAM or SAM use cases. Sure, the CMDB/Asset data will support it, but no out-of-the-box functionality exists to tackle this. Yes, EoL / EoS will be presented in both workspaces, but apart from replacing them, no remediation is available.
Hope this helps!